Practice the English used when onboarding a new engineer: welcoming phrases, context-setting, explaining team processes, and first-week check-ins.
0 / 8 completed
1 / 8
What is the most important thing to communicate to a new team member on their first day?
On day one, new joiners need psychological safety (who to ask), orientation (where things are), and clarity (what is expected of them). Technical depth comes later.
2 / 8
Which phrase sets the right tone for a first-week check-in?
Good onboarding language is supportive and removes barriers. Asking about blockers and encouraging questions signals psychological safety, which is critical for new team members.
3 / 8
How would you introduce the team's code review process to a new joiner?
Explaining the code review process clearly — approval requirements, templates, response expectations — prevents confusion and helps the new joiner contribute confidently from day one.
4 / 8
What does 'buddy system' or 'onboarding buddy' mean in a professional context?
An onboarding buddy is an informal guide — not the manager. They answer the questions new joiners are hesitant to ask officially: 'What does that acronym mean?', 'How does this team actually work?'
5 / 8
How would you explain 'unwritten rules' or 'team norms' to a new joiner?
Making implicit norms explicit helps new joiners integrate faster and avoids awkward situations. It is kinder to explain upfront than to let someone inadvertently break a team norm.
6 / 8
Which sentence is the best way to set expectations about asking questions?
Good onboarding sets a time-based heuristic (15-20 min) so new joiners know when to ask for help without feeling they are being a burden or too dependent.
7 / 8
What is a 'knowledge handover' in the context of onboarding?
Knowledge handover ensures continuity when someone joins, transitions roles, or takes over a code area. Good handovers cover: what the system does, known issues, key contacts, and decisions made in the past.
8 / 8
How would you communicate the team's 'definition of done' to a new engineer?
Making the definition of done explicit prevents misalignment. New joiners often assume 'done' means the code is written, but professionally it typically includes tests, deployment, and documentation.