Practice the key verb+noun collocations used when onboarding new engineers, setting up environments, and guiding new team members in English.
0 / 5 completed
1 / 5
Fill in: 'We always ___ a buddy to every new engineer so they have someone to ask questions.'
We 'assign a buddy' — 'assign' is the standard collocation when formally pairing a mentor or peer with a new joiner. 'Give a buddy' is too informal; 'attach' is used for files or appendices; 'allocate' suits resources or budget, not people in a mentoring context.
2 / 5
Fill in: 'Before your first PR, please ___ your local development environment following the README.'
We 'set up a development environment' — 'set up' is the fixed collocation for configuring a local workspace. 'Build' refers to compiling code; 'install' covers individual packages; 'prepare' is vague and not idiomatic here.
3 / 5
Fill in: 'Your tech lead will ___ you ___ the codebase on your first day.'
We 'walk someone through the codebase' — this is the standard phrase for explaining a system step by step. 'Show around' implies a physical tour; 'take through' is used but less idiomatic; 'guide across' is not a natural collocation.
4 / 5
Fill in: 'You should ___ the onboarding checklist within your first two weeks.'
We 'complete the onboarding checklist' — 'complete' is the natural collocation for working through a formal list of tasks. 'Finish' is close but less formal; 'close a checklist' collocates with tickets; 'clear' is informal in this context.
5 / 5
Fill in: 'DevOps will help you ___ the local services so you can test end-to-end without a staging environment.'
We 'spin up local services' — 'spin up' is the dominant DevOps collocation for quickly starting containers or processes. 'Start up' is generic; 'boot' refers specifically to operating systems; 'launch' suits applications or products, not services in a local stack.