The orchestration layer decides what happens next on a requisition, retries when something fails, and refuses to act when a guardrail says no. It is the reason a customer can be invoiced for what the agent does.
Planning, sequencing and retry behaviour across six pipeline stages running in parallel on hundreds of requisitions.
Evaluating every action against customer policy before it happens — cadence caps, rate ceilings, off-limits accounts, suppression lists.
Requisition ingest and submission write-back across staffing ATS platforms, each with its own idea of what a candidate record is.
Making every decision reconstructable after the fact, including the ones that led nowhere.
Evidence over credentials. Having done something close to this and being able to explain the decisions you made counts for more than the title you held.
You have built systems where a wrong action has a real-world cost, not just a failed test.
You are comfortable with long-running, partially-failing, retryable workflows rather than request and response.
You have integrated with third-party APIs that were undocumented, inconsistent, or both.
You write code someone else can debug at 2am without calling you.
Email careers@ariascout.com with the subject line Agent and backend engineering. Include:
No cover letter needed. We reply either way.
This is an open application, not an active search. We read every one and come back to strong applicants when a role opens. If you would rather be told when that happens than wait, say so and we will keep you on the list.
We will run AriaScout against a live req from your desk and show you exactly what comes back — the candidates, the scoring rationale and the screening transcripts.