Design the database for a to-do list

A guided warm-up: a coach at every step, templates to fill in, and no countdown. Never seen one done? Read a worked interview first.

Checking your subscription…

How this interview works

1. The interviewer gives you a vague problem, the way real ones do.
2. Propose the requirements before designing, as you would in the first five minutes of a real one. The interviewer settles the scope, and the review grades your proposal.
3. Write the schema. A hidden battery runs it on a real Postgres.
4. 1 follow-up change the requirements. Each opens once you pass 80% of the tests, and keeps every earlier test.
5. Explain your decisions, then read the debrief and an annotated answer.
6. Stuck on syntax? A Postgres syntax sheet is one tab away. The interview grades decisions, not memory.