Submit a brief. Receive a validated shortlist.
The form below is our strategic query interface. Fill it with the same precision you'd write a design doc — the more signal you give us, the faster the sandbox boots.
What makes a strong brief
The most useful briefs read like an internal design document, not a job description. Tell us what the engineer will own at the system boundary — which services they will inherit, which failures the team has absorbed in the last twelve months, what the on-call topology looks like, and what shipping looks like in their first ninety days. Specify the runtime, the language, the deployment target, and the observability surface; we will translate those into the sandbox manifest.
The more honestly you describe the painful parts of the role, the faster the laboratory can grade against them. We do not need polished marketing language. We need the unvarnished surface area. Once the brief lands with us, a senior reviewer will respond inside one business day with clarifying questions, an estimate, and a proposed manifest structure. From there the only thing left is to seal the sandbox and run the cycle.