Workbench/resume/projects/proj_0d8f0fe0a65fde750f528118
Open Interview
One project stays anchored as the deep-dive unit: context on the left, session history on the right, and explicit project prompts ready to practice.
- project_id
- proj_0d8f0fe0a65fde750f528118
- sessions
- 1
- highlights
- 3
- tech_stack
- 4
Project context
Project context stays visible because the deep-dive flow should practice storytelling, not generic chatting.
Built a local-first interview prep workbench that turns messy notes and resume bullets into structured questions, grounded QA, and project deep-dive sessions.
Highlights
Highlights give the deep-dive session concrete material to probe.
Led end-to-end import, review, question bank, and grounded QA flows.
Added retrieval trace, citations, and project deep-dive coaching support.
Reduced prep time for interview review by making local knowledge searchable.
Suggested deep-dive questions
Suggested prompts come from the structured project entity and seed the first session turns.
What problem was Open Interview solving, and what part did you personally own?
Why did you choose Next.js and TypeScript for Open Interview?
Walk through the hardest part of Open Interview and how you delivered "Led end-to-end import, review, question bank, and grounded QA flows.".
What outcome, metric, or business impact proves Open Interview worked well?
Tech stack
The stack is visible before the user starts answering follow-ups.
Next.jsTypeScriptSQLiteOpenClaw
Session history
Session history stays beside the project, not hidden behind the generic QA route.