TL;DR
A double opt-in intro means that a developer has reviewed your role, answered your screening questions, and explicitly opted in. You then confirm interest before we connect you. This flow ensures every conversation starts with mutual intent.
How a double opt-in intro works
Role goes live
Your approved brief and questions are shown privately to matched developers.
Developer opt-in
The developer reviews the role, answers your questions, and signals interest.
Candidate brief sent to you
You review their details, including answers to your screening questions.
Your confirmation
You approve moving forward with the candidate.
Introduction made
We connect both sides via email to start the conversation.
Why this matters for recruiters
No cold outreach: You never send unsolicited messages.
Less ghosting: Developers already committed before you meet.
High intent: Both sides chose the conversation.
Important:
If either side declines, no introduction happens. This protects trust and ensures every intro is high-signal.
FAQs
Q: How does this reduce ghosting?
Because developers have already opted in and answered questions, they are more likely to follow through.
Q: Can I request more information before confirming?
Yes. You can ask for clarification or adjustments before approving the intro.
Q: Where does the intro happen?
We introduce you via email. From there, you continue the process in your normal workflow.