Given a FastAPI project with two working endpoint functions (create and read) and shared Pydantic models, implement the remaining update and delete endpoints to complete CRUD. Requirements: a) match the existing request/response schemas and status codes; b) preserve idempotency and return 404 vs 204 appropriately; c) validate inputs and handle exceptions; d) write unit tests for all four endpoints; e) explain how you would approach this if you have never used FastAPI before, by leveraging the existing endpoints as templates and the framework documentation.

This question evaluates a candidate's ability to implement RESTful CRUD endpoints with FastAPI, focusing on API contract consistency, HTTP status codes and idempotency, input validation and exception handling, and unit testing.

How do I approach System Design interview questions?

System Design questions require understanding of core concepts and practice. PracHub provides solutions with explanations to help you master system design interviews.

What difficulty level is this interview question?

This is a medium difficulty System Design question, commonly asked during Technical Screen rounds at Credit Genie.

What role is this question designed for?

This question is commonly asked for Software Engineer candidates at Credit Genie during technical interviews.

Implement FastAPI CRUD endpoints from skeletons | Credit Genie Interview Question

Implement Update and Delete Endpoints in a FastAPI CRUD Service

Context

You are given a FastAPI project that already has working Create and Read endpoints and shared Pydantic models for request/response. Extend the service to complete CRUD by adding Update and Delete endpoints that are consistent with the existing code style and API contracts.

Assumptions (adjust to match the actual project):

The resource is an "Item" stored in memory or a repository abstraction.
Existing endpoints follow typical REST conventions:
- POST /items → 201 Created with response body of the created item.
- GET /items/{item_id} → 200 OK with item body, or 404 if not found.
The same Pydantic models are reused across endpoints (e.g., ItemCreate, ItemUpdate, ItemRead).

Requirements

Implement Update and Delete endpoints that match existing request/response schemas and status codes.
Preserve idempotency where applicable and return 404 vs 204 appropriately.
Validate inputs and handle exceptions cleanly (e.g., 422 for invalid input, 404 for not found).
Write unit tests covering all four endpoints (Create, Read, Update, Delete), including success and error paths.
Explain how you would approach this if you have never used FastAPI before, leveraging existing endpoints as templates and the FastAPI documentation.

Context

Assumptions (adjust to match the actual project):

The resource is an "Item" stored in memory or a repository abstraction.

Existing endpoints follow typical REST conventions:

POST /items → 201 Created with response body of the created item.
GET /items/{item_id} → 200 OK with item body, or 404 if not found.

The same Pydantic models are reused across endpoints (e.g., ItemCreate, ItemUpdate, ItemRead).

Requirements

Implement Update and Delete endpoints that match existing request/response schemas and status codes.

Preserve idempotency where applicable and return 404 vs 204 appropriately.

Validate inputs and handle exceptions cleanly (e.g., 422 for invalid input, 404 for not found).

Write unit tests covering all four endpoints (Create, Read, Update, Delete), including success and error paths.

Explain how you would approach this if you have never used FastAPI before, leveraging existing endpoints as templates and the FastAPI documentation.

Implement FastAPI CRUD endpoints from skeletons

Quick Overview

Implement Update and Delete Endpoints in a FastAPI CRUD Service

Context

Requirements

Solution

Comments (0)

Implement FastAPI CRUD endpoints from skeletons

Quick Overview

Implement Update and Delete Endpoints in a FastAPI CRUD Service

Context

Requirements

Solution

Comments (0)