Backend · AI-first engineering
Build with AI, defend without it
Engineers now build with AI. What sets you apart is knowing whether it's right. Build a real API with any AI tools you like and deploy it; our server checks it live — including the race conditions AI code often gets wrong. Then explain and change it in a voice interview, without AI. What you can show at the end is evidence, not a certificate of attendance.
1Build it — with any AI tools you like
A clinic's appointment API: doctors open time slots, patients book and cancel them. Build it in any language and framework, using any AI tools you like, and deploy it to a public https address.
| Endpoint | What it must do |
|---|---|
| GET /health | 200 with JSON that includes "verification": "<your code>" |
| POST /slots {"doctor": "Dr Rao", "start": "2030-01-15T10:00:00Z", "durationMinutes": 30} | 201 with the slot: id, doctor, start, durationMinutes, status "open". 400 for a duration ≤ 0 or a start in the past. 409 if it overlaps another slot of the same doctor. |
| GET /slots/{id} | 200 with the slot (status "open" or "booked"); 404 if unknown |
| GET /slots?doctor={name} | 200 with a JSON array of that doctor's slots |
| POST /slots/{id}/bookings {"patientName": "Asha", "patientPhone": "9800000000"} | 201 with the booking: id, slotId, status "booked". 409 if the slot is already booked — even when many requests arrive at once. 404 for an unknown slot, 400 without a patientName. |
| DELETE /bookings/{id} | 200 or 204; the slot is open again. A second cancel returns 404 or 409. |
- JSON in, JSON out. Ids may be numbers or strings.
- Times are ISO 8601 in UTC.
- A 400 may be a 422 if your framework prefers it.
- Deploy anywhere with a public https address — Render, Railway and Fly.io all have free tiers.
AI tends to get booking code subtly wrong. Warm up with Review the AI's code — the same bugs our checks look for.
2Verify it — our server checks your live API
All 12 live checks, and why each matters
- Health check answers with your verification code — Proves the deployment is yours
- Creates a slot — The basic write path works
- Reads a slot back, and 404s an unknown one — Reads return what was written; missing data isn't invented
- Lists a doctor's slots — Queries filter correctly
- Books an open slot — The core flow works end to end
- Refuses a second booking of the same slot — The bug AI code most often ships: two patients, one slot
- Exactly one of 10 simultaneous bookings succeeds — A check-then-insert race passes every single-request test and still double-books
- Cancelling frees the slot for someone else — State is updated, not just the booking row
- A second cancel is refused — Operations are idempotent and honest
- Rejects bad input (no patient name, zero duration, a past start) — The API defends itself instead of storing nonsense
- Refuses overlapping slots for the same doctor — Business rules hold, not just the schema
- A booking for an unknown slot is a 404 — Errors are specific and correct
3Defend it — without AI
A voice interview with Aria about your code: how a booking flows through it, how you stop double booking, why a check failed, and a change she asks you to plan on the spot. Like a real design review — no AI, just you.
Unlocks once your project is verified.
Share your proof
A link for your resume or your placement cell: what was verified, how, and when.