Workbench/resume/projects/proj_b26deec99d84b14304cb4831
Interview Copilot
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_b26deec99d84b14304cb4831
- sessions
- 0
- highlights
- 2
- 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 with grounded QA and resume deep dives.
Highlights
Highlights give the deep-dive session concrete material to probe.
Implemented structured source ingestion and parse review workflows.
Added retrieval trace visibility for every grounded answer.
Suggested deep-dive questions
Suggested prompts come from the structured project entity and seed the first session turns.
What problem was Interview Copilot solving, and what part did you personally own?
Why did you choose TypeScript and Next.js for Interview Copilot?
Walk through the hardest part of Interview Copilot and how you delivered "Implemented structured source ingestion and parse review workflows.".
What outcome, metric, or business impact proves Interview Copilot worked well?
Tech stack
The stack is visible before the user starts answering follow-ups.
TypeScriptNext.jsSQLiteOpenAI
Session history
Session history stays beside the project, not hidden behind the generic QA route.
Empty state
No sessions yet
No deep-dive sessions exist for this project yet.
- Start a deep-dive session from this page.
- The first turn will seed from the project's suggested questions.