Employee Onboarding
11 templates · Updated 2026-08-11
Onboarding templates that make the first weeks count: engineers debugging code nobody on the team wrote, a first PR inside two weeks, 30-60-90 plans drafted with the manager, day-one AI ground rules. All are built for teams, sized to the window a new hire actually gets.
- Luca — How to Debug Code You Did Not Write
How to debug code nobody on your team wrote, 1:1 with a tutor that declines to name the cause. Four parts from a reliable reproduction to git bisect, ending when a week-two engineer can explain a real production cause in three sentences.
- Lucius — The Manager's 30-60-90 Day Plan for New Hires
30 60 90 day plan for new hires, drafted 1:1 with a tutor that interviews the manager before writing a line. Four sessions to what good looks like at day 90, with check-ins at day 7 and day 30, ending when the day-30 deliverable ships.
- Ludmila — AI Training for Employees: Day One, One Task
AI training for employees that fits in forty-five minutes on day one, 1:1 and taught only from your own approved tool list. Four parts on what never goes into a prompt, ending when a joiner finishes one real task and correctly refuses two of five paste-or-not scenarios.
- Luka — Software Engineer Onboarding: First PR in Two Weeks
Software engineer onboarding for remote hires in an undocumented monorepo, 1:1 with a tutor that asks for the exact error text first. Two weeks from an unblocked build to a first pull request small enough to review in ten minutes, ending when it merges.
- Lumi — Contractor Onboarding Process: Useful by Day Ten
A contractor onboarding process built for twelve-week workers, run 1:1 as short judgement scenarios instead of the induction written for permanent staff. Five days from access and the compliance floor to handover, ending when a restricted-access contractor ships one real deliverable by day ten.
- Lyra — Working With Legacy Code: Your First Change
Working with legacy code, taught 1:1 by a tutor that makes engineers predict a function's behaviour before running anything. Four modules from characterization tests to blast radius, ending when a joiner can name every caller, the rollback and the test that would have caught it.
- Mabel — Knowledge Transfer Plan Before the Expert Retires
A knowledge transfer plan for the weeks before your only expert retires, rehearsed 1:1 against a tutor that answers in war stories. Three weeks of case-based interviews producing runbooks a stranger could follow at 2am, ending when the successor resolves two past incidents unaided.
- Madeleine — M&A Integration: Day One for Acquired Staff
M&A integration HR for the first week after close: a 1:1 tutor that answers privately the questions acquired staff never ask HR. Five days from title and pay to approvals, ending when a joiner files a correct expense claim and their manager passes the retention role-play.
- Magnus — Customer Service Training: First Solo Ticket
Customer service training for new hires who freeze on severity and wording, run 1:1 as live tickets with an impatient customer. Four modules from triage to escalation, ending when an agent clears five tickets at correct severity with no missed escalation before their first solo shift.
- Mahin — Frontline Employee Onboarding on a Phone
Frontline employee onboarding for staff with no laptop or email until day three, delivered 1:1 on a phone in fifteen-minute sessions. Six spoken scenarios on spills, lifting, hygiene and the customer who refuses to leave, cleared two sessions running before a starter's first live shift.
- Maisie — Understand a Large Codebase in Two Weeks
How to understand a large codebase without reading all of it, taught 1:1 in timed five-minute explorations rather than a walkthrough. Two weeks across a half-million-line monorepo, ending when a new engineer traces a feature from request to database and merges a change by day ten.
Questions, answered
How do I debug a failing service in a codebase I just joined?
How to debug code nobody on your team wrote, 1:1 with a tutor that declines to name the cause. Four parts from a reliable reproduction to git bisect, ending when a week-two engineer can explain a real production cause in three sentences. Explore the Luca — How to Debug Code You Did Not Write template.
What should a 30 60 90 day plan for a new hire include?
30 60 90 day plan for new hires, drafted 1:1 with a tutor that interviews the manager before writing a line. Four sessions to what good looks like at day 90, with check-ins at day 7 and day 30, ending when the day-30 deliverable ships. Explore the Lucius — The Manager's 30-60-90 Day Plan for New Hires template.
How do we run AI training for new employees in their first week?
AI training for employees that fits in forty-five minutes on day one, 1:1 and taught only from your own approved tool list. Four parts on what never goes into a prompt, ending when a joiner finishes one real task and correctly refuses two of five paste-or-not scenarios. Explore the Ludmila — AI Training for Employees: Day One, One Task template.
How do I get my first pull request merged in an undocumented monorepo?
Software engineer onboarding for remote hires in an undocumented monorepo, 1:1 with a tutor that asks for the exact error text first. Two weeks from an unblocked build to a first pull request small enough to review in ten minutes, ending when it merges. Explore the Luka — Software Engineer Onboarding: First PR in Two Weeks template.
How do we onboard a three-month contractor with restricted access quickly?
A contractor onboarding process built for twelve-week workers, run 1:1 as short judgement scenarios instead of the induction written for permanent staff. Five days from access and the compliance floor to handover, ending when a restricted-access contractor ships one real deliverable by day ten. Explore the Lumi — Contractor Onboarding Process: Useful by Day Ten template.
How do I get new engineers safely shipping changes in our legacy codebase?
Working with legacy code, taught 1:1 by a tutor that makes engineers predict a function's behaviour before running anything. Four modules from characterization tests to blast radius, ending when a joiner can name every caller, the rollback and the test that would have caught it. Explore the Lyra — Working With Legacy Code: Your First Change template.
How do we capture what our retiring specialist knows before his last day?
A knowledge transfer plan for the weeks before your only expert retires, rehearsed 1:1 against a tutor that answers in war stories. Three weeks of case-based interviews producing runbooks a stranger could follow at 2am, ending when the successor resolves two past incidents unaided. Explore the Mabel — Knowledge Transfer Plan Before the Expert Retires template.
How do we onboard acquired employees in the first week after close?
M&A integration HR for the first week after close: a 1:1 tutor that answers privately the questions acquired staff never ask HR. Five days from title and pay to approvals, ending when a joiner files a correct expense claim and their manager passes the retention role-play. Explore the Madeleine — M&A Integration: Day One for Acquired Staff template.
How do I get a new support agent ready for their first solo shift?
Customer service training for new hires who freeze on severity and wording, run 1:1 as live tickets with an impatient customer. Four modules from triage to escalation, ending when an agent clears five tickets at correct severity with no missed escalation before their first solo shift. Explore the Magnus — Customer Service Training: First Solo Ticket template.
How do we onboard deskless staff with no laptop before their first shift?
Frontline employee onboarding for staff with no laptop or email until day three, delivered 1:1 on a phone in fifteen-minute sessions. Six spoken scenarios on spills, lifting, hygiene and the customer who refuses to leave, cleared two sessions running before a starter's first live shift. Explore the Mahin — Frontline Employee Onboarding on a Phone template.
How can a new engineer get productive in our monorepo within two weeks?
How to understand a large codebase without reading all of it, taught 1:1 in timed five-minute explorations rather than a walkthrough. Two weeks across a half-million-line monorepo, ending when a new engineer traces a feature from request to database and merges a change by day ten. Explore the Maisie — Understand a Large Codebase in Two Weeks template.