Full Stack Developer Technical Expected

duration: 1-2
Assignment hours

Thank you for applying. This assignment is designed to assess practical full stack skills across frontend,
backend, API design, and general code quality. Please focus on a working solution with clean structure
rather than advanced styling or unnecessary complexity.

Assignment summary What we are looking for

Build a small Task Manager application with a Clear structure, working API integration, basic
frontend and backend. validation, and thoughtful error handling.

1. Objective
Build a simple Task Manager app that allows a user to create, view, update, and delete tasks. The goal is
to evaluate both frontend and backend fundamentals within a short, practical exercise.

2. Core Requirements
Frontend
• Display a list of tasks.
• Provide a form to add a new task.
• Allow a task to be marked as completed.
• Allow a task to be deleted.
• Show loading and error states where appropriate.
Backend
• Expose a simple REST API.
• Handle basic validation for incoming data.
• Return clear JSON responses.
• Organize code in a clean and readable structure.

3. API Endpoints
Method Endpoint Description

GET /tasks Return all tasks.

POST /tasks Create a new task.

PATCH /tasks/:id Update a task status.

DELETE /tasks/:id Delete a task.

4. Task Data Model

Field Type / Notes

id Unique identifier

title Task title

Page 1
 completed Boolean status

createdAt Timestamp or date string

5. Technical Notes
• You may use any reasonable stack. Examples: React, Vue, Angular, or plain JavaScript on the
frontend; [Link], Laravel, Django, Spring Boot, or similar on the backend.
• A database is optional. In-memory storage or simple file-based storage is acceptable for this exercise.
• Keep the interface simple. Functionality, structure, and correctness matter more than visual design.
• Please include a short README with setup and run instructions.

Important: Keep the solution intentionally small. The assignment is expected to be completed in
1-2 hours, so scope control is part of the exercise.

6. What We Will Evaluate

Area What we assess

Component structure, state handling, API integration, form behavior,

Frontend
and user feedback.

API design, routing, validation, response structure, and code

Backend
organization.

Readability, naming, separation of concerns, basic error handling, and

General
completeness.

7. Optional Bonus
Only attempt bonus items if the core requirements are complete.
• Filter tasks by completed or incomplete status.
• Edit an existing task title.
• Persist tasks after refresh.
• Add basic tests.
• Provide a simple Docker setup.

8. Submission
• A repository link containing the source code.
• A README with setup and run instructions.
• A short note describing any assumptions or trade-offs made.

Submission note
Please submit a working solution that reflects your normal coding approach for a small feature. We
value clarity, correctness, and sensible trade-offs.

Prepared for candidate distribution.

Page 2