The First 30 Days for a New Engineer — Mentoring Engineers, Part 1
The first 30 days set the next 30 months. A great onboarding compounds. A bad one means months of recovery — or losing the engineer.
Step 1: Plan Before Day One (10 min)
A week before they start:
Equipment ordered + arrived
Accounts created (GitHub, Slack, etc.)
First-week buddy assigned
30-60-90 plan drafted
First meaningful task identified
Welcome message sent
Engineers showing up day one to "wait for laptop access" feel discarded.
Step 2: Day 1: Welcome, Not Firehose (10 min)
Don't:
Schedule 8 hours of meetings
Hand them docs to "read everything"
Ignore them after intro
Do:
Brief intro to the team (each member)
Walk through their workstation setup
Give them lunch with someone
Light reading; not overwhelming
A relaxed day one builds trust. They'll go hard later.
Step 3: Week 1: Make a Small PR (15 min)
By end of week one, they should:
Have a working dev environment
Make a tiny PR (typo fix, doc update, simple test)
Get it merged
The dopamine of shipping something matters. It also surfaces:
Setup issues
Process gaps
Tooling problems
Fix those for the next hire.
Step 4: Pair Frequently (15 min)
Days 2-15: pair multiple times per week.
Senior driving while explaining
New hire driving with senior supporting
Mixed: solve a small problem together
Pairing transfers tacit knowledge that docs can't.
After 2 weeks, taper. They need solo time too.
Step 5: Define a 30-60-90 Plan (15 min)
Week 1 of their work:
## 30 days
- Dev environment running
- 5+ PRs merged
- Met every team member 1:1
- Owned one bug fix
## 60 days
- Owns a small feature start-to-finish
- Comfortable in 2-3 areas of codebase
- Participating in code review
- Oncall shadow
## 90 days
- Full member of team rotation
- Designs and ships features independently
- Code review contributor
- Oncall primary (with backup)
Specific. Adjustable. They know what success looks like.
Step 6: Don't Overschedule (10 min)
New hires often book 6-7 hours of intros in week one. Exhausting.
Better:
1-2 intros per day max
Buffer time for note-taking + reading
Heads-down time for setup
Energy for the work
Spread intros over the month. They retain more.
Step 7: Assign a Real Buddy (10 min)
Not just a pointer — an actual person committed for the first 30 days:
Daily check-in (5 min)
Available for questions
Lunches together
Lower-stakes than the manager
Buddy isn't manager. Buddy isn't extra HR. Buddy is the friend at work.
Step 8: Stupid-Question Tax (5 min)
Every new hire has 100 stupid questions. They feel dumb asking.
Tell them explicitly:
"Your job is to ask. Ask anything. The team prefers questions over
silent confusion. If you're stuck >30 minutes, ask."
The team needs to mean this. Reward question-asking; never penalize.
Step 9: Be Patient with Output (10 min)
First 30 days: low output. Normal.
Expecting feature-shipping speed in week 2 = punishing the wrong thing.
Output ramps over months:
Month 1: small things, learning
Month 3: contributing
Month 6: ownership
Month 12: leverage
Don't panic about velocity. Panic about engagement and learning.
Step 10: 30-Day Check-In (10 min)
After 30 days, 1:1:
How is the onboarding going?
What's confusing?
What did we get wrong?
What's missing from this team?
Their feedback is gold. Use it to improve the next hire's experience.
What You Just Did
Onboarding: pre-arrival, day 1, week 1 PR, pairing, 30-60-90 plan, sustainable schedule, buddy, encourage questions, output patience, 30-day retro. The first month set up.
Common Failure Modes
Equipment not ready. First impression: "they don't care."
Firehose week 1. Burnout before they start.
No buddy. They drift; isolated.
Expect production output in week 2. Punishing learning curve.
No 30-day retro. Same mistakes every hire.
