A well-crafted task can make all the difference — both for the candidate and for your team.
Whatever you put into your task repository is exactly what the candidate will see when they start. Think of it as your first impression — it reflects your team's values around clarity and developer experience.
What to Include
At a minimum, we recommend:
- A README.md file explaining the challenge, expected deliverables, setup instructions, and any constraints
- Optionally: function stubs, test cases, or partial implementations for candidates to complete
Tips for Effective Tasks
- Keep it focused — The task should be completable within 2–4 hours. Don't send a full-blown project.
- Be realistic — Simulate actual work your team does, not abstract puzzles or trick questions.
- Avoid surprises — Document everything clearly. Candidates shouldn't have to guess what's expected.
- Encourage creativity — Leave room for candidates to go above and beyond if they choose.
- Make it easy to run — Provide clear setup instructions, scripts, or Docker files so candidates can get started quickly.