A screen should answer a small number of role-relevant questions cheaply for both sides.
What to look for
- 01
Test the capabilities the later interview assumes.
- 02
Use a modest exercise and consistent prompts.
- 03
Keep the initial screen distinct from a complete assessment of engineering ability.
Keep in mind
The examples reflect older programming environments and should be adapted. Language trivia is not a substitute for work-relevant evidence.
Try this next
Write a twenty-minute screen with one skill, one exercise, agreed hints, and a clear explanation of what happens next.
Get the hiring templateNotes and exercises by Awesome CTO. The original work belongs to Jeff Atwood.