Which status codes would you return for create, update, and delete in a pragmatic REST service?
PICTURE THIS: RAG CHATBOT
Simple meaning
Create: 201 with Location, or 200 if the body includes the resource.
WHY — REST instead of guessing?
Why interviewers care about REST:
who only read docs from people who shipped.
and tied to Backend work.
Name the idea, why it exists, then one short example.
End with when you use it and one common pitfall.
STEPS — What happens step by step?
Before you speak the answer, walk the interviewer through these steps:
- 1Create: 201 with Location,
or 200 if the body includes the resource.
- 2Update: 200 with body
or 204 if empty.
- 3Delete: 204, or 200
with a payload if clients need confirmation.
- 4If the resource was
already gone, many teams still return 204 so DELETE stays idempotent.
- 5Common mistake
What juniors usually get wrong.
- 6Close
When you pick this over the alternative.
EXAMPLE — See it in action
Here's a short line you can speak, broken into clear beats:
Note: Adapt this scaffold to your own project — keep it under 60–90 seconds.
Key takeaway
Create: 201 with Location, or 200 if the body includes the resource. Update: 200 with body or 204 if empty.