The ATS connection is the only integration a customer owns, which makes it the only thing standing between them and value. This work owns that connection and everything around it — the configuration, the first submissions, and the moment a recruiter decides whether to trust the agent.
ATS connection, client rules, off-limits lists, suppression records and guardrail configuration — phase 01 of the deployment model.
Sitting with customers while they compare the agent output against their own desk, and turning what they find into product feedback.
Making requisition ingest and submission write-back work against each ATS, including the ones that fight back.
Recruiters decide whether a tool survives its first quarter. Winning them is part of this job, not marketing’s problem.
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 are technical enough to debug an API integration and human enough to run the call where it broke.
You have owned customer outcomes rather than tickets.
You can tell a customer no, with a reason, and keep the relationship.
You are willing to learn how staffing desks, margins and submissions actually work.
Email careers@ariascout.com with the subject line Customer engineering and ATS integrations. 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. This one is Austin-based because the early customer work is easier in person.
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.