• Title: Develop a RESTful API for a Task Management System
• Objective: Assess the candidate’s ability to design, implement, and document a RESTful API that allows users to manage tasks, including creating, updating, retrieving, and deleting tasks.
• Requirements:
  • Design and develop a RESTful API that supports CRUD (Create, Read, Update, Delete) operations for a task management system.
  • Implement basic authentication and include at least one endpoint that requires user authentication.
  • Document the API using a tool like Swagger or Postman, including clear instructions for using the API.
  • Ensure the API follows RESTful principles and is secure and scalable.
  • Submit the source code, documentation, and a brief explanation of your design choices.
• Time Frame: 5 days to complete and submit the task.

‍

• Question: "How did you ensure that your API follows RESTful principles in the task management system?"
  • Expected Answer: The candidate should explain their approach to ensuring statelessness, proper use of HTTP methods (GET, POST, PUT, DELETE), resource-based URIs, and how they handled errors and responses.
  • Sample Answer: "I ensured the API was stateless by making each request self-contained, used appropriate HTTP methods for each operation, and designed resource-based URIs like /tasks/{id}. I also implemented consistent error handling and used proper HTTP status codes in responses."
• Question: "What security measures did you implement to protect the API, and why?"
  • Expected Answer: The candidate should discuss implementing basic authentication, rate limiting, input validation, and how they protected the API against common threats like SQL injection and cross-site scripting (XSS).
  • Sample Answer: "I implemented basic authentication using tokens and ensured all endpoints required authentication. I also added input validation to prevent SQL injection and set rate limiting to protect against brute-force attacks."
• Question: "How did you document the API, and why did you choose that method?"
  • Expected Answer: The candidate should explain their choice of documentation tools (e.g., Swagger, Postman) and describe how they ensured the documentation was clear, comprehensive, and easy to follow for other developers.
  • Sample Answer: "I used Swagger to document the API because it provides an interactive interface for developers to test endpoints. I made sure to include detailed descriptions, sample requests/responses, and authentication instructions to make the documentation user-friendly."