What the work involves
You write structural problems the way they arrive in practice — a framing plan, a governing load case, a set of constraints — and then you write the reference answer, including the code clauses and the load path reasoning that carry each decision. Scenarios range across gravity and lateral analysis, member sizing, drift and serviceability checks, foundation reactions, and steel or concrete connection design. The second half of the job is evaluation: you read model-generated solutions and grade them for structural soundness, code compliance, and internal consistency between the analysis and the detail that follows from it.
The most valuable output is often the failure annotation. Models produce work that looks like an engineer wrote it — correct units, plausible clause numbers, a tidy summary table — while dropping a load combination, applying an ACI 318 provision outside its scope, or specifying a moment connection the erector could never bolt up. You mark those, explain why the answer reads competent and is still wrong, and say what a licensed engineer would have caught.
What the platform screens for
AfterQuery's screen is AI-led and pushes on depth. Expect to be asked which code edition you work from and why the change mattered, to walk a load from roof diaphragm to footing without hand-waving, and to distinguish a conservative answer from an unsafe one. Vague code familiarity does not survive follow-up questions; specific project recall, specific clauses, and specific judgment calls do. Written clarity is graded directly, since your reference rationales are the training signal.
Logistics
- 100% remote, fully asynchronous — no standing meetings, no client calls
- Minimum commitment around 10 hours per week, scheduled by you
- Paid weekly via Stripe; $110–195/hr is the observed range, with placement varying by licensure, specialty depth, and task complexity
- Ongoing project work rather than a fixed-term engagement, with volume that fluctuates by lab demand