
API Documentation
Docs + Word14 pages
Free
New engineers lose days to missing access, stale set-up steps and not knowing whom to ask. This guide fixes that with a dated two-week plan: a welcome page with the manager and buddy, a milestone timeline, one-command environment set-up, a codebase tour, a first-task checklist, a who-to-ask page and a glossary.
The sample follows Valemont Digital, a fictional software company. A new hire starts on Monday, March 15, 2027, merges a first pull request by day 5 and ships to production by day 10. Replace the people, commands and repositories with your own, rerun the set-up on a clean laptop and link a real first issue.
Click Make a copy in Google Docs, then confirm on the Google page. The copy is saved to your own Google Drive.
Replace the manager, buddy, tech lead and channel names on the welcome page and the who-to-ask page with your own.
Rerun the set-up steps on a clean laptop, fix anything that fails and update the commands and timings.
Swap the codebase tour for your repository list and link a good first issue on the first-task page.
Delete the guide page, then share the document with the new hire.
No. Valemont Digital, its people, channels and every figure in the guide are fictional sample data. Replace them with your own team's details.
A small change shipped early proves access, tooling and the review path all work. The sample targets a merged pull request by day 5 and a deploy by day 10.
The pages focus on the first two weeks. The make-it-yours page tells you to add three outcomes for each of days 1 to 30, 31 to 60 and 61 to 90.
More Google Docs templatesMore developer workflows templates

Docs + Word14 pages
Free
Slides + PowerPoint12 slides
Free
Docs + Word3 pages
Free
Docs + Word7 pages
Free
Docs + Word7 pages
Free