Rehearsal - Research. Practice. Get Hired.

The problem Candidates rehearse “tell me about yourself” and “greatest weakness,” then walk into a room where the conversation is about this posting, this stack, and what the company shipped last month. The gap between generic prep and a real interview is where people lose. Those specifics are public — the posting, the company page, the news — but almost nobody works through them systematically the night before. What we built Rehearsal is a three-tab workspace: Research · Rehearse · Relive. 1. Research — Paste a job link. Three live scrapes land as cards (job, company, news) with source domain and timestamp. A prep brief and optional resume-based fit match sit inside the same dossier. 2. Rehearse — Choose Voice or Text. An interviewer (named, role-framed) asks questions grounded in that dossier — e.g. Deltek Playwright/LLM-as-judge QA, or Dodo Payments developer onboarding — not recycled bank questions. Source labels show where each question came from. 3. Relive — Answers are scored with missed points and model answers so practice produces a verdict, not just a feeling. Why it is different Every question is meant to be traceable to scraped evidence. A generic tool asks about test pyramids; Rehearsal asks how you would build an LLM-as-judge pipeline because that sentence is in the posting, and it can show you the line. Design Institutional dossier aesthetic — paper and ink, mono for facts, signal red only when the mic is live. Not a chat UI. Not a SaaS dashboard. A file being assembled on a candidate. Scope One job at a time, night-before practice: research → rehearse → review. Not job search, not mass apply, not a career LMS. Demo / status End-to-end research and interview paths run against live services. Demo film uses product stills + music-led cards (screenshot cut under time). Live product: https://rehearsal.nryn.dev Made by Narayan SS · nryn.dev