0
Challenge · 82Production & the Interview Gauntlet
Debug-on-sight gauntlet
Interviewused in ~70% of apps
The other half of the Supabase interview is a screen of SQL and platform code that compiles, runs, and looks correct — and one question: "what's wrong here?" Reviewers don't hand you six novel bugs. They hand you the same six or seven that ship to production every year, because juniors keep making them look identical to the correct version.
Core idea. Almost every Supabase bug that survives code review falls into a short, recognizable set: a policy missing its TO clause or its real predicate, a policy that recurses on its own table, an aggregate inflated by a fan-out join, a secret key shipped to the browser, a SECURITY DEFINER function with an unpinned search_path, and an UPDATE policy missing WITH CHECK. Learn the symptom-to-cause map and you debug by recognizing the shape, not by re-deriving Postgres from first principles under pressure.
poke it, drag it,
try to break it
try to break it
no slides here.
you drive.
you drive.
Playground, this isn't a screenshot
bug 1 / 6 missing TO + true
Every anonymous visitor reads every draft
create policy "Read published posts" on public.posts for select using ( true );
what a reviewer / user actually sees
curl the API with no auth header at all — drafts, everything, comes back.
Name the bug family before you reveal. Cycle all 6 — this is the actual pattern-matching interviewers grade.
↑ play a little first, then dig in