2025-10-21
30-60-90 Day Check-Ins: Ensuring Placement Success
30-60-90 Day Check-Ins: Ensuring Placement Success
Placing a developer is only half the battle. The real test of your recruitment success happens in the weeks and months after they start. The 30-60-90 day period is the critical window where most placements either stabilize or fall apart. New hires are evaluating the role, the team, the tech stack, and the company culture. Your job as a recruiter doesn't end at the offer letter—it intensifies.
This guide walks you through a systematic approach to check-ins that keeps placements on track, prevents costly turnover, and builds the kind of placement longevity that generates referrals, repeat business, and a reputation for quality sourcing.
Why 30-60-90 Day Check-Ins Matter for Your Placements
The first 90 days of employment are predictive. Research from the Society for Human Resource Management (SHRM) shows that 50% of new hires who quit do so within the first six months, with the majority of departures happening between months two and four. For technical roles, the risk is even higher—developers have options, and a bad onboarding experience or misaligned expectations can send them right back to the job market.
As a recruiter, a failed placement doesn't just hurt your commission. It damages your credibility with both the hiring manager and the candidate, makes the role harder to fill the second time, and wastes everyone's time.
The purpose of structured check-ins is to:
- Catch misalignment early, when it's still fixable
- Demonstrate that you care about both sides succeeding
- Gather intelligence that improves future placements
- Build trust that keeps candidates from ghosting mid-probation
- Identify at-risk placements before they become terminations
The Three-Phase Check-In Framework
Day 30: The Orientation Check-In
Timing: Schedule this call no later than the 32nd day of employment
The 30-day mark is when the initial excitement fades and reality sets in. This is your first real opportunity to take a true temperature reading.
What to assess: - Has the candidate received proper onboarding materials and access? - Do they understand the role expectations and success metrics? - Have they met their direct manager and key team members? - Is there clarity on first project assignments? - Are there any immediate red flags with tooling, documentation, or culture?
What to ask:
- "Walk me through your first week. What went well, and what was confusing?"
- "Have you had a 1-on-1 with your manager yet? How did that go?"
- "What's been the biggest surprise so far—positive or negative?"
- "Is there anything you expected to have that you haven't received yet?"
- "On a scale of 1-10, how are you feeling about the decision so far?"
What you're listening for: - Enthusiasm level. A lukewarm response at day 30 is a warning sign. - Clarity gaps. If they don't know their goals or how they'll be measured, that's on the hiring manager, but it's your problem to flag. - Technical onboarding speed. Can they pull code? Can they run tests? If basic setup is stalled, they're losing momentum. - Team chemistry signals. Are they connecting with people?
Your role: Document notes, but don't sound like you're filling out a form. This call should feel like a genuine check-in from someone who cares. Flag any serious issues (missing onboarding, manager unavailability, access problems) with the hiring manager immediately. These are fixable problems at day 30.
Day 60: The Progress Check-In
Timing: Schedule between days 55-65
By day 60, the candidate has shipped code or completed meaningful work. They've attended meetings, participated in standups, and started forming opinions about whether this role is sustainable. This is when cultural friction becomes apparent.
What to assess: - Have they completed initial projects or responsibilities? - Are they contributing independently, or are they blocked? - How's the relationship with their manager and teammates? - Is the tech stack matching what was discussed? - Are there any compensation, benefits, or logistics issues? - Do they see a career path here?
What to ask:
- "You've been here about two months. What's your honest take on how it's going?"
- "Describe a project or task you've completed. How did that go?"
- "Are there any surprises—positive or negative—compared to what you expected?"
- "How much are you learning? Is the work matching your skill level?"
- "Tell me about your manager. Do you feel supported?"
- "If you had to tell a friend why they should or shouldn't take this job, what would you say?"
What you're listening for: - Momentum indicators. Are they building confidence and getting wins, or spinning on trivial tasks? - Manager quality signals. The single biggest predictor of placement success is manager satisfaction. If the candidate doesn't respect or trust their manager, the placement is at risk. - Culture fit. By day 60, they can tell if they belong. Listen for language about inclusion, psychological safety, and whether they feel heard. - Commitment signals. Are they talking about "when I figure out the system" (good) or "if I stay here" (bad)?
Red flags to escalate: - Candidate mentions looking at other jobs - Manager has been unavailable or dismissive - Compensation or benefits don't match what was promised - Technical setup is inadequate for the role - Team dynamics are toxic or exclusionary
Your role: If there are fixable issues, mediate directly with the hiring manager. Many placements fall apart at day 60 because small problems went unaddressed. A 15-minute conversation between you and the hiring manager can often prevent a resignation.
If the candidate is genuinely mismatched, have that conversation honestly. Sometimes a role swap or team reassignment saves the placement.
Day 90: The Commitment Check-In
Timing: Schedule between days 85-95, or around probation end
The 90-day mark is the moment of truth. The probation period (if one exists) is ending or about to end. Formal or informal, this is when both sides decide: are we keeping this relationship?
What to assess: - Is the candidate being offered permanent status, or is there hesitation? - Are they planning to stay long-term? - What would make this role a keeper? - What unresolved issues remain? - Are there growth or development opportunities ahead?
What to ask:
- "As we hit the 90-day mark, how do you feel about your decision to join?"
- "What's one thing that's exceeded your expectations, and one thing that hasn't?"
- "Have you gotten feedback from your manager on how you're performing?"
- "What would make this an amazing place for you to grow over the next year?"
- "Are you planning to stay and build something here, or are you still evaluating?"
What you're listening for: - Clarity on permanence. Do they have written feedback on their 90-day performance? Is the company planning to convert them to permanent status? - Vision alignment. Can they articulate a career path at this company? - Unresolved issues. If they're still waiting on compensation adjustment, promised training, or a team change, that's a failure of the hiring manager.
Your role: At day 90, your job is partly about securing the placement and partly about gathering information for future improvements.
If there's hesitation from the candidate, understand why. Is it manageable (salary negotiation, team adjustment) or fundamental (wrong tech stack, bad culture fit)?
If there's hesitation from the company, push back. By day 90, you should have a clear yes or no. Limbo is dangerous—candidates lose motivation when they don't know their status.
Best Practices for Running Check-Ins
Schedule Proactively, Not Reactively
Set up all three check-in dates in your calendar the day the candidate starts. Send them a brief message: "I'll be checking in with you around day 30, 60, and 90 to make sure everything's going well. These are low-pressure conversations—just want to make sure you're settling in."
This manages expectations and shows professionalism.
Use Phone or Video, Never Slack
Text-based communication obscures tone and nuance. A 15-minute phone call tells you far more than a paragraph of written responses. You need to hear hesitation, enthusiasm, and frustration in their voice.
Document Everything, Share Appropriately
Keep detailed notes on each call. If there's an issue, summarize it and send a brief recap to the hiring manager: "Spoke with [candidate] on [date]. They're excited about the work but mentioned uncertainty about the code review process. Could you clarify that in your next 1-on-1?"
Don't share the candidate's notes with the hiring manager without context. They need to know if there's a problem, but you're not reporting on the employee.
Be a Mediator, Not a Therapist
You're checking on job fit, not providing career counseling. If the candidate is struggling with impostor syndrome or personal issues unrelated to the job, acknowledge it but don't try to fix it. Point them toward employee resources (EAP, mentor, manager support).
Know When to Escalate
| Issue | Action | Timing |
|---|---|---|
| Missing onboarding or tools | Contact hiring manager immediately | Within 24 hours |
| Manager unavailability or conflict | Schedule call with both parties | Within 48 hours |
| Role misalignment | Discuss team reassignment options | Within 1 week |
| Compensation discrepancy | Involve HR and hiring manager | Before day 60 |
| Performance concerns from manager | Request formal feedback plan | Before day 90 |
| Candidate actively job hunting | Have honest conversation about expectations | Immediately |
Common Placement Problems and How Check-Ins Prevent Them
Problem: "The role was different than described"
Prevention: At day 30, ask about project assignments and day-to-day work. If it doesn't match the job description, address it immediately. Sometimes this is a miscommunication by the hiring manager; sometimes the role genuinely changed. Either way, day 30 is the time to correct it.
Problem: "My manager doesn't seem to know what I'm supposed to be doing"
Prevention: By day 30, the candidate should have met their manager and discussed their first 90 days. If the manager hasn't scheduled that conversation, that's your flag to push for it.
Problem: "The tech stack is outdated / different than expected"
Prevention: A technical check-in at day 60 (ideally with someone technical from your team or the hiring company) catches this. If the candidate is supposed to work in Rust but the team runs PHP, that's a misalignment worth addressing.
Problem: "I'm being asked to do work outside my level"
Prevention: This often shows up as frustration at day 60. Ask about the types of work they're doing and whether it matches their experience level. A junior developer asked to architect systems will burn out quickly.
Problem: "Nobody here looks like me / I don't fit the culture"
Prevention: You can't fix culture from the outside, but you can amplify the signal early. If a candidate mentions feeling excluded or different at day 30 or 60, that's something the company needs to take seriously. This is also why diverse hiring practices matter—sourcing developers from diverse backgrounds requires intentionality, and retaining them requires company culture that's genuinely inclusive.
Sample Check-In Email Templates
30-Day Check-In Request
Subject: Quick check-in on your first month at [Company]
Hi [Name],
Hope you're settling in well! I wanted to schedule a quick 15-minute call to see how your first month has gone. This is just between us—I want to make sure you're getting what you need to succeed.
Are you available for a quick call this week? [Link to calendar]
Looking forward to hearing how it's going.
[Your name]
60-Day Check-In Request
Subject: How's [Company] treating you two months in?
Hi [Name],
We're two months in! You've probably shipped some code by now and gotten a real feel for the team. I'd love to do a quick check-in and hear your honest take on how things are going.
Let's grab 20 minutes this week. [Link to calendar]
[Your name]
90-Day Wrap-Up Request
Subject: 90-day check-in + next chapter
Hi [Name],
We're hitting the 90-day mark! This is a good moment to talk about how you're feeling about the role, the team, and where you see yourself going from here.
Can we hop on a call this week? [Link to calendar]
[Your name]
Metrics That Matter: Tracking Placement Success
Start measuring your check-in effectiveness with these metrics:
- Placement retention at 90 days: What percentage of your placements make it to the 90-day mark? (Target: 95%+)
- Placement retention at 1 year: Beyond the initial period, how long do placements stay? (Target: 85%+)
- Issues caught at day 30 vs. day 90: How many problems surface early enough to be fixed?
- Manager satisfaction score: Are hiring managers reporting that candidates integrated well?
- Repeat placement rate: Do companies keep hiring from you because your placements work out?
If your 90-day retention is below 90%, your check-in process isn't working—or something deeper is wrong with your sourcing or vetting.
Technology to Support Check-Ins
You don't need fancy tools, but some structure helps:
- Calendar reminders: Set alerts for day 25, 55, and 85 to schedule check-ins
- Notes app or CRM: Log every conversation with date and key takeaways
- Spreadsheet tracker: Simple columns for candidate name, company, day 30 status, day 60 status, day 90 status, outcome
- Zumo integration: If you're sourcing developers through GitHub activity analysis, use your existing candidate data to inform check-in conversations. Reference their growth areas or technical interests.
The Long-Term Play: From Placements to Partnerships
Successful check-ins do more than save placements—they build trust with both candidates and hiring managers. A candidate who feels cared for becomes a referral source. A hiring manager who sees you catching and fixing problems wants to work with you again.
At 30 days, you're a troubleshooter. At 60 days, you're a partner. At 90 days, you've earned the right to be called back for the next hire.
This is how you build a recruiting business that scales—not by quantity of placements, but by quality and longevity of relationships.
FAQ
What if the candidate isn't answering my calls or being responsive during check-ins?
Unresponsiveness is a red flag. It usually means either they're too busy to care about the relationship (possible, especially in the first weeks), or they're mentally checked out. Send a brief message: "Hey, I know you're busy. Just want to make sure you're doing okay. When you have 15 minutes, let me know." If they're still unresponsive at day 60, loop in the hiring manager quietly. Sometimes candidates are struggling and don't know how to tell you.
Should I charge the client for check-in calls, or is this built into the placement fee?
Check-ins are built into your service. They're not billable—they're part of ensuring the placement succeeds so you get your full fee and build the relationship for future hires. If you're not doing check-ins, you're already pricing those risks into your fees; you might as well do the work and increase your success rate.
What if the candidate tells me they want to quit before day 90?
Listen first, don't panic. Ask why. If it's something fixable (team dynamics, onboarding gap, wrong project), see if the hiring manager can adjust. If it's fundamental (role mismatch, culture, compensation), have an honest conversation. Sometimes the best outcome is helping them find a better fit elsewhere, which preserves your relationship and reputation. A forced placement that lasts 45 days is worse than an honest conversation at day 30.
How do I handle check-ins for remote developers?
Exactly the same way, but be more intentional about maintaining connection. Remote developers can feel isolated, so check-ins sometimes matter even more. Video calls are better than phone calls when possible—you pick up on engagement and energy better. Ask specifically about remote team dynamics and whether they feel connected to their teammates.
What if the company says they don't want me calling the candidate during the onboarding period?
This is rare, but some companies have strict policies about external contact. Respect it, but push back if they're absolute. Explain that check-ins improve retention and reduce turnover. Offer to do check-ins after hours or on the candidate's personal time. A reasonable company will work with you—they want placements to succeed too.
Keep Your Placements Strong
The 30-60-90 check-in framework isn't complicated, but it's transformative. It turns placement into partnership, catches problems early, and demonstrates that you actually care about outcomes—not just commissions.
If you're sourcing developers through platforms like Zumo, which helps you identify engineers through their GitHub activity and open-source contributions, the same rigor applies. You've done the work to find the right person; now finish the job by making sure they succeed.
Start with your next placement. Set three calendar alerts. Make three 15-minute calls. Log the outcomes. Watch your retention rate climb.
That's how you build a recruiting practice that companies and candidates want to work with repeatedly.