Practice technical onboarding vocabulary: buddy systems, 30-60-90 day plans, runbooks, dev environment setup, and asking for help during onboarding.
0 / 5 completed
1 / 5
'Your ___ will walk you through the architecture.' Which noun describes an assigned helper during onboarding?
An onboarding 'buddy' is a colleague assigned to help a new joiner navigate the team, codebase, and culture. Buddy programs accelerate time-to-productivity and reduce overwhelm.
2 / 5
'We have a 30-day, 60-day, ___ onboarding plan.' Which day milestone completes this?
The '30-60-90 day plan' is a structured onboarding framework. 30 days: learn the basics. 60 days: begin contributing independently. 90 days: fully productive and owning tasks.
3 / 5
'The ___ describes how to set up your dev environment.' Which noun fits a step-by-step process document?
A 'runbook' (or sometimes README/setup guide) contains step-by-step instructions for operational tasks like dev environment setup. 'Runbook' is most common in engineering team contexts.
4 / 5
'___ out to the team channel if you're blocked.' Which verb starts this advice?
'Reach out' is the standard phrase for contacting someone for help. 'Reach out to the team channel' means posting in a shared Slack/Teams channel to ask for assistance.
5 / 5
In technical onboarding, what is a 'first task' or 'starter issue' typically designed to do?
A 'starter issue' or 'good first issue' is intentionally scoped to be achievable in 1–3 days. It gives new joiners a concrete win, introduces the development workflow, and builds codebase familiarity.