Evidence checklist before interview
After resume and JD paste, the app should ask for missing metrics, before/after outcomes, architecture scale, and incident examples before starting the interview.
Evidence console
A public-safe UI for the CV-driven InterviewCoach experiments: recent job corpus, mobile interview runs, Spark answer simulations, LangSmith evaluation, and measurement surfaces.
Investors and employers should not need to open raw markdown first. The UI separates product proof, job-fit evidence, and known blockers.
Used the same mobile session/report/history API path with private CV held locally and raw answers excluded from public artifacts.
Five-answer interview loops covered project deep dives, RAG failures, LangGraph support agents, tool safety, coding recovery, and design evolution.
Highest current company averages: Trase Systems, Extreme Networks, Bold Business, Pinterest, Elastic, Grafana Labs, and OLX.
Failures are tracked as runtime/stress issues, not hidden. Public reports keep job URLs and sanitized failure causes while excluding raw private answers.
These roles came from recent public job pages and were tested against the local CV persona in the mobile interview flow.
The tests are not one generic chat. They cover common real interview shapes: architecture, coding recovery, RAG incidents, tool safety, and project defense.
40 submitted answers, average score 4.37.
25 submitted answers, average score 4.38.
15 submitted answers, average score 4.46.
15 submitted answers, average score 4.38.
5 submitted answers, score 4.50.
5 submitted answers, score 4.45.
Use these links when reviewing the run. Human-readable UI comes first; JSON and markdown stay available for audit trails.
These files remain useful for audit and automation, but the main review path should be the evidence console above.
The evidence points to client-journey improvements inside the app, not just more reports.
After resume and JD paste, the app should ask for missing metrics, before/after outcomes, architecture scale, and incident examples before starting the interview.
Show the user which interview shapes are likely for the selected job: project deep dive, RAG incident, coding recovery, architecture review, or tool-safety discussion.
Expose a polished public-safe demo path that shows coverage, scores, and sources without raw private answers.
Long Spark scenarios should keep timeout cleanup and retry controls visible so runtime failures are interpreted separately from interview fit.