How to Handle a New Hire Who Doesn't Work Out

You spent weeks sourcing, interviewing, and negotiating. The offer was accepted. They started strong on day one. But three months in, your new hire is missing deadlines, their code quality is below expectations, or they're simply not integrating with the team.

This situation costs recruiters and hiring managers thousands of dollars. The average cost of a bad hire is 30% of the employee's first-year salary—for a mid-level software engineer earning $120,000, that's $36,000 in wasted resources. Beyond the financial hit, a poor cultural fit or underperformer can damage team morale, slow project delivery, and create additional friction in your organization.

The question isn't whether to act—it's how to handle the situation professionally, legally, and humanely while minimizing damage to your team and company.

Why New Hires Fail: The Root Causes

Before taking action, understand why your hire isn't working out. The causes fall into distinct categories:

Misaligned Expectations

The role description promised one thing; the actual job delivers another. They were hired to build microservices but spend 70% of their time on legacy monolith maintenance. This mismatch emerges within the first 4-6 weeks and compounds frustration on both sides.

Skill Gaps

The technical interview didn't adequately assess their capabilities. They claimed proficiency in React and TypeScript but struggle with intermediate-level architecture patterns. When you're hiring React developers, this gap becomes evident within the first sprint.

Cultural Misfit

They possess the skills but clash with your team's values, communication style, or work pace. A developer comfortable in chaotic startups may struggle in structured, process-heavy organizations—and vice versa.

Onboarding Failures

Your company didn't invest in proper onboarding. No mentor assigned, no clear first-week objectives, documentation gaps, and they're left feeling lost and unsupported.

Personal Circumstances

External factors—relocation stress, family issues, health concerns—impact their early performance. These situations sometimes resolve with support and patience.

Poor Manager Fit

Your new hire's direct manager isn't engaged, offers minimal feedback, and hasn't created psychological safety. Strong developers can disengage quickly under poor leadership.

The First 90 Days: Early Warning Signs

The most important intervention window is the first 90 days. This is your opportunity to identify problems early and course-correct before investing additional time and emotional labor.

Track these key indicators during the probationary period:

Code quality metrics: Are pull requests meeting your standards? How many revisions do their PRs require before merging?
Velocity and task completion: Are they shipping features at an expected pace, or are estimates consistently missed?
Communication patterns: Do they ask clarifying questions, report blockers, and participate in standups?
Feedback receptiveness: When you provide direction, do they implement it or defend their approach defensively?
Relationship building: Are they connecting with team members, attending social events, and building rapport?
Initiative and ownership: Do they take ownership of problems or wait to be told what to do next?

If these indicators are consistently red within the first 30 days, escalate the situation. Don't wait until month four to act.

Step-by-Step Process for Managing Underperformance

Step 1: Document Everything From Day One

Documentation is your legal and operational foundation. Before you ever need to address performance issues, establish a baseline:

Save onboarding materials and role expectations in writing
Record completion of onboarding tasks with dates
Document feedback provided in one-on-ones (summarize in email follow-ups)
Keep copies of code reviews, performance metrics, and project assignments
Note any discussions about performance concerns with timestamps

Why this matters: If the situation escalates to termination, you need a clear paper trail showing the employee understood expectations and had opportunities to improve. Without documentation, you expose your company to legal vulnerability and wrongful termination claims.

Step 2: Schedule a Formal Check-in Conversation

Once you've identified consistent performance gaps (typically by week 4-6), don't gossip about the problem or hope it resolves itself. Schedule a private, structured conversation with the new hire's direct manager.

The check-in agenda:

Open with curiosity, not accusation: "I've noticed you've had some challenges settling in. How are you feeling about the role and team?"
Share specific observations: Reference concrete examples. "In the last three code reviews, we've had significant comments on architecture patterns. Have you worked with this pattern before?"
Listen actively: They may reveal onboarding gaps, unclear expectations, or personal circumstances you weren't aware of.
Clarify expectations: Explicitly restate what success looks like in the role over the next 30, 60, and 90 days.
Offer support: Propose a mentor, training resources, adjusted responsibilities, or additional one-on-ones.
Document the conversation: Send a follow-up email summarizing key points and next steps.

This conversation often resolves minor issues. A developer who felt lost might thrive once they have clear direction and a mentor. Onboarding gaps can be filled. Misaligned expectations can be corrected.

Step 3: Implement a Structured Improvement Plan (If Needed)

If the check-in doesn't resolve the issue, escalate to a Performance Improvement Plan (PIP). A PIP is a formal document that outlines specific performance gaps, measurable improvement targets, and a timeline (typically 30, 60, or 90 days).

A solid PIP includes:

Element	Description	Example
Specific Goals	Clear, measurable outcomes	"Complete sprint deliverables with zero critical bugs in code review feedback"
Success Metrics	How you'll measure improvement	"Code review feedback averages 2 comments per PR (down from 8); completes 85% of story points per sprint"
Support Resources	Training, mentoring, or tools provided	"Daily 15-minute pairing sessions with senior engineer; Udemy course access"
Check-in Cadence	Frequency of feedback	"Weekly one-on-ones with manager; bi-weekly check-ins with HR"
Timeline	Duration of the improvement period	"60-day PIP, final review on December 15, 2025"
Consequences	What happens if targets aren't met	"Failure to meet objectives may result in termination"

Legal note: PIP requirements vary by jurisdiction. Consult your HR department or employment attorney to ensure your PIP complies with local labor laws. In some regions, PIPs are legally required before termination; in others, they're optional but recommended.

Step 4: Provide Active Support During the Improvement Period

A PIP isn't a punitive tool—it's a genuine attempt to salvage the hire. Your success depends on providing real support:

Assign a mentor or senior peer who invests time in helping the employee improve
Provide training resources relevant to their skill gaps
Increase feedback frequency with structured weekly check-ins
Adjust projects to allow them to demonstrate improvement in a supportive environment
Celebrate small wins to rebuild confidence and momentum

Some of your best long-term employees have come through successful PIPs. Conversely, your most valuable team members remember when the company invested in their growth during difficult periods.

Step 5: Evaluate Outcomes at the PIP Review

At the end of the improvement period, conduct a formal review with HR present:

Outcome 1: Successful Improvement

The employee has met the measurable goals. Congratulate them, remove the PIP, and transition to standard feedback cycles. Continue monitoring—some employees revert to old patterns once the PIP ends.

Outcome 2: Partial Improvement

They've made progress but haven't fully met targets. Decide whether to: - Extend the PIP for another 30 days with adjusted goals - Negotiate a different role that better suits their strengths - Move forward with separation discussions

Outcome 3: No Improvement

They've failed to meet the objectives and show no trajectory toward success. This is your green light to proceed with termination—if that's your decision.

When to Cut Losses: The Termination Decision

Not every underperforming hire can or should be salvaged. Sometimes the best decision for everyone is a clean break. This is particularly true when:

The role isn't recoverable: The position requires skills fundamentally mismatched to the employee's capability
Cultural misfit is severe: They reject core company values or create a toxic dynamic
Improvement is unlikely: Despite genuine support and a clear PIP, they show zero progress
Cost exceeds benefit: The resources invested in support, management, and lost productivity outweigh the value they'd bring if they improved
Time is critical: You're in a scaling phase or competitive market where your team can't afford to carry underperformers

When you decide to terminate, consult with HR and legal counsel to ensure compliance with local employment laws, severance agreements, and documentation requirements.

Managing the Separation Process

If you proceed with termination, handle it professionally to minimize legal risk and maintain your employer brand:

Before the Meeting

Coordinate with HR and legal
Prepare severance terms (if applicable)
Brief the employee's manager on the decision and messaging
Plan IT logistics (access revocation, equipment return)
Have a transition plan for their work

The Termination Meeting

Schedule early in the week (avoids weekend despair)
Keep it brief and direct
Deliver the news clearly: "This isn't working out. We're parting ways, effective today/[date]."
Provide written documentation of severance, benefits continuation (COBRA in the US), and next steps
Avoid ambiguous language that could be interpreted as constructive dismissal
Have HR and a witness present
Don't debate or litigate—this conversation isn't negotiation

After Termination

Communicate transition plan to the team (brief, professional, no disparaging comments)
Revoke access immediately
Process final paycheck and benefits paperwork
Send written confirmation of severance terms and obligations

How to Avoid This Situation: Prevention Strategies

The best approach is preventing bad hires before they happen.

Strengthen Your Technical Interviews

Bad hires often slip through flawed interviewing processes. When you're hiring JavaScript developers or TypeScript developers, ensure your technical assessments actually validate job-critical skills. Use:

Practical coding exercises relevant to your tech stack
Architecture discussions to assess design thinking
Code review simulation where candidates critique real (anonymized) code samples
Pair programming sessions to evaluate communication and problem-solving style

Assess Culture and Communication Style

Technical skills are table stakes. Culture fit and communication patterns often determine success:

Value alignment interviews: Ask questions about how they approach failure, feedback, and collaboration
Team interviews: Have 2-3 team members meet candidates to assess interpersonal dynamics
Reference calls: Ask previous managers about communication style, coachability, and team dynamics—not just technical ability

Invest in Comprehensive Onboarding

Poor onboarding creates friction for even strong hires. Establish a standard onboarding playbook:

Pre-boarding: Send welcome packet, set up accounts, assign mentor before day one
Week 1: Clear objectives, environment setup, team introductions, cultural orientation
Weeks 2-4: Pair programming, code review experience, smaller tasks to build confidence
Month 2-3: Increased responsibility, feedback on integration, mid-probation check-in
Month 3: Formal performance review with explicit expectations for the next quarter

Use Data to Improve Your Hiring

After each hire (successful or failed), conduct a brief retrospective:

How did they perform versus interview predictions?
Which interview components were most predictive?
What onboarding gaps emerged?
If they didn't work out, could earlier intervention have helped?

Track hiring quality metrics: Time-to-productivity, 90-day retention, performance ratings by source. Use this data to double down on hiring practices that work and eliminate those that don't.

Leverage GitHub-Based Sourcing

One often-overlooked way to reduce hiring risk is assessing actual work samples before investing in interviews. Platforms like Zumo analyze GitHub activity to evaluate whether candidates can actually ship code, collaborate on pull requests, and work in your tech stack—not just talk about it in interviews.

This early filtering catches skill mismatches before they become expensive problems, and helps you focus interview time on cultural fit and communication.

FAQ: Handling Underperforming New Hires

How long should I wait before addressing a performance problem?

Don't wait beyond week 6. Performance issues are easiest to address early. If you notice consistent red flags in the first 4-6 weeks, schedule a check-in immediately. Waiting three months compounds the problem—you've invested more resources, your team has likely lost confidence, and the employee may have disengaged.

Can I avoid a PIP and just terminate?

Legally, it depends on your jurisdiction. At-will employment in the US generally allows termination without a PIP, but having a documented improvement plan protects you against wrongful termination claims. In Europe, many countries legally require a warning period and opportunity to improve. Consult your legal counsel, but treat PIPs as a best practice even where not legally required.

What if the employee quits during a PIP?

That's often the intended outcome. Some employees sense they're on a path to termination and choose to resign—which is sometimes easier for both parties. If they quit, process it normally. They'll likely forfeit severance and have a quit on their record (which affects future references). This is fine; you've made your expectations clear.

Should I stay in touch with the terminated employee?

Professionally, no. Once someone is terminated, limit all communication to HR and legal-approved channels. Don't engage in casual conversations or offer informal advice. Your company's legal liability ends cleanly once they're off payroll.

What if I realize I made the hiring mistake?

Own it. Hiring mistakes don't reflect personal failure—they're part of recruiting. The difference between good and great recruiters is how they respond. Use the experience to improve your process, talk openly with your hiring team about what went wrong, and implement changes so it doesn't happen again. Your credibility comes from learning, not from never making mistakes.

Stop Wasting Time on Bad Hires

Handling underperformance is never pleasant, but it's an essential skill in technical recruiting. The key is early detection, clear documentation, genuine support, and decisive action when improvement isn't viable.

If you're frustrated with hiring quality, part of the solution is improving your sourcing process. Rather than discovering skill gaps after someone starts, use data-driven tools to validate candidates before they join your team. Zumo's GitHub-based sourcing helps you assess whether developers actually ship code, work well on distributed teams, and match your tech stack—reducing expensive hiring mistakes before they happen.

The goal isn't to be harsh with underperformers. It's to respect everyone's time and create space for the right fits to thrive.