A strong candidate accepted a competing offer after waiting eight days. What should change?

Decide within a day or two of the final interview, have the hiring manager make the offer call with specific reasons and the first-year picture, and address concerns honestly.

What's in a good 30-60-90 day plan for a new engineer?

Learning and first changes in the first 30 days, end-to-end ownership of a medium piece of work and joining on-call by 60, and ownership of a project aligned with the role's scorecard by 90 — with written check-ins at each point.

Why should a hiring manager be honest about the role's challenges during the close?

Candidates who join with accurate expectations are more likely to succeed and stay; surprises after joining lead to early regretted departures.

Closing Candidates and 30-60-90 Onboarding — The Engineering Manager Handbook (Development Manager)

Scenario

Example organisation: after a strong loop, a candidate waits eight days for an offer, receives a generic email, and accepts a competing offer that came with a call from the future manager. Another hire joins, but nobody has planned her first month; after 90 days nobody can say whether she's on track.

What you see on the team

Offers declined for competitors who moved faster or felt more personal.
Candidates unclear about the role's scope and growth.
New hires without clear goals for their first months.
Probation reviews based on impressions.

The common mistake

Treating the offer as paperwork and onboarding as HR's job, instead of the last two stages of hiring that the manager owns.

Why it happens

After the effort of interviewing, managers relax. Recruiters handle offers; IT handles laptops. But candidates decide based on the people and clarity they experience, and new hires succeed or fail based on the first months.

The playbook

Close fast and personally:

decide within a day or two of the last interview;
the hiring manager calls with the offer, explains why the team wants them (specific evidence from interviews) and what their first year could look like;
answer concerns honestly — on-call, growth, the team's challenges;
offer conversations with future teammates.

Write a 30-60-90 plan before day one, aligned with the scorecard's first-year outcomes:

Days 1-30   Learn: environment, architecture, team; ship first changes;
            1:1s weekly; meet key partners.
Days 31-60  Contribute: own a medium-sized piece of work end to end;
            join on-call rotation; first design review.
Days 61-90  Lead: own a project aligned with scorecard outcome #1;
            give feedback on onboarding.
Checkpoints: written check-in at day 30, 60, 90 against this plan.

Assign a buddy, plan their capacity, and make sure access and equipment are ready before day one.

Check in formally at 30, 60 and 90 days, in writing, against the plan — no surprises at the end of probation.

What to say

Offer call:

"We'd love you to join. In the design interview, the way you planned the migration with a rollback at every step is exactly what the platform team needs. In your first six months you'd lead the pipeline migration. What questions or concerns do you have — including anything that would make this a harder decision?"

Trade-offs

Speed vs thoroughness: a well-designed loop gives enough evidence to decide fast.
Honesty about challenges may lose some candidates; it prevents early regretted departures.
Detailed 90-day plans should adapt as you learn about the person.

Signals it's working

Offer acceptance rate rises; fewer losses to competitors on speed.
New hires can state their 90-day goals in week one.
30-60-90 check-ins happen on time and in writing.
New hires reach independent contribution sooner and stay.

Key points

Decide within a day or two; the hiring manager makes the offer call personally.
Be specific about why you want them and honest about the role's challenges.
Write a 30-60-90 plan aligned with the scorecard before day one.
Check in formally at 30, 60 and 90 days.