Assessment Portal Private candidate access
Your ideas.
A working solution.
Show how you think, solve problems, and build software in our six-hour engineering assessment.
Sign in with emailThree briefs. One choice.
Choose the problem that interests you. Every challenge uses the same marking criteria.
ASupport Ticket TrackerView brief
Help a small support team track requests from arrival to resolution.
- Create a ticket with a title, description, priority (low, medium, high), and a unique ID.
- List tickets and search by title; filter by status and priority.
- Move tickets through Open, In progress, and Resolved. Record creation and last-update times.
- Reject empty titles, invalid priorities, and invalid statuses.
- Show total tickets and counts grouped by status.
All solutions need persistent data, validation, meaningful tests, and setup instructions.
BInventory TrackerView brief
Help a small business understand what is in stock and when it needs attention.
- Create a product with a unique SKU, name, opening quantity, and low-stock threshold.
- List products and search by name or SKU; filter to low-stock products.
- Record stock additions and deductions with a quantity, reason, and timestamp.
- Reject duplicate SKUs, negative opening quantities, non-positive movements, and deductions exceeding available stock.
- Show total products, total units in stock, and products at or below their thresholds.
All solutions need persistent data, validation, meaningful tests, and setup instructions.
CTask PlannerView brief
Help an individual organise work and see what needs attention next.
- Create a task with a title, description, due date, priority (low, medium, high), and unique ID.
- List tasks and search by title; filter by status and priority.
- Move tasks through To do, In progress, and Done. Record creation and last-update times.
- Reject empty titles, invalid dates, priorities, and statuses. Past due dates are allowed.
- Show counts by status and overdue tasks. An overdue task has a due date before today and is not Done. Document the timezone used.
All solutions need persistent data, validation, meaningful tests, and setup instructions.