A task represents the challenge you'll be sending to candidates. It's the starting point of every assessment.
When you create a task, Codebie generates a dedicated Git repository for it. Your reviewers can then push code, instructions, or templates into that repository. When a candidate accepts an invitation, Codebie automatically duplicates the repository content into their own private assessment repository.
You have complete freedom in how you structure your challenge. You can include a README with instructions, provide unfinished functions or classes, or offer a partially implemented solution for the candidate to complete.
Creating a Task
Task creation involves three steps:
Step 1: General Information
Give your task a name. Codebie will automatically generate a URL-friendly identifier based on the name, but you can customize it if needed.
Step 2: Responsible Employees
Select which team members should receive notifications when something happens with this task's assessments. This doesn't limit who can review — it just controls who gets notified.
Step 3: Evaluation Questions
Add internal evaluation questions that reviewers will score from 1 to 5 after reviewing a candidate's submission. These are never shown to candidates.
For example, for a backend task, you might ask:
- Did the candidate follow SOLID principles?
- Is the code clean and readable?
- Does the solution handle edge cases?
- Is the time/space complexity appropriate?
After Creation
Once the task is created, your reviewers need to push the challenge content into the task's Git repository before HR can start inviting candidates.