Practise the standard verbs for designing a solid engineering onboarding checklist.
0 / 5 completed
1 / 5
Fill in: 'We ___ a concrete onboarding checklist for every new engineer, so their first two weeks are a defined path rather than whatever their manager remembers to mention.'
We 'build a checklist' — the standard, simple collocation for creating a structured onboarding plan. The other options are less idiomatic here.
2 / 5
Fill in: 'Relying on a manager's memory instead of a written checklist can ___ a new hire missing a basic access request that then blocks their very first task.'
We say an unwritten checklist will 'leave' a new hire missing a basic step — the standard, natural collocation for the resulting gap. The other options aren't idiomatic here.
3 / 5
Fill in: 'We ___ each item off as it's completed, in a shared, visible place, so both the new hire and their manager can see real progress at a glance.'
We 'check off an item' — the standard, simple collocation for marking a step complete on a shared list. The other options aren't idiomatic here.
4 / 5
Fill in: 'We ___ every new hire a specific buddy on day one, someone other than their manager, so a small question always has somewhere low-stakes to go.'
We 'assign a buddy' — the standard, simple collocation for pairing a new hire with a dedicated point of contact. The other options are less idiomatic here.
5 / 5
Fill in: 'We ___ the checklist itself after every new hire finishes it, since the exact step that confused the last three people is worth fixing before the next one arrives.'
We 'review a checklist' — the standard, simple collocation for improving a process based on real feedback. The other options are less idiomatic here.