TL;DR
When you approve a developer for an intro, their profile is automatically created in your ATS under the correct job requisition. As they move through your hiring funnel, their status updates flow back into daily.dev, giving you full visibility without extra work.
What happens step by step
Approval
You approve a developer for an intro in Slack or Teams.
Push to ATS
The candidate is automatically added to your ATS under the right job requisition.
Sync status
As you move the candidate through stages in your ATS (interview, reject, hire), those updates sync back to daily.dev.
Stay in sync
Both systems reflect the same information, ensuring no manual entry or duplicate effort.
Why this matters for recruiters
Zero manual entry: Candidate data flows into your ATS instantly.
Clean pipeline: Deduplication ensures no duplicate profiles are created.
Full visibility: You can see candidate progress inside daily.dev, tied directly to each intro.
Prove ROI: Every hire can be attributed back to daily.dev introductions.
Important:
The ATS is treated as the source of truth for candidate status. Any changes in your ATS are synced back to daily.dev.
FAQs
Q: What candidate data is synced?
Candidate profile details, role association, and status updates. Resumes and attachments are not yet included.
Q: When does the sync happen?
Immediately after you approve a candidate for an intro. Status updates are pulled continuously.
Q: What if a candidate already exists in my ATS?
Deduplication logic prevents duplicates. The existing record will be updated instead of creating a new one.