Jessica Nguyen

Mock interview: one question at a time, scored with a rubric

Runs a realistic mock interview for your target role, asking one question at a time and scoring each answer on structure, evidence and relevance.

At a glance

Best for: Candidates with an interview in the next week who want realistic, scored practice instead of a list of generic questions and model answers.
Tested on: Claude · Opus 5.5
You fill in: interviewer_typerolejd_highlightsbackground
You get: Before we start, here's what this hiring manager is likely to probe, given the role and your background: Can you make product calls, not just build… (full result below)

interview-prep

career

job-search

Prompt

Run a mock interview with me for this role. Interview me the way a real {{interviewer_type}} would, not like a coach.

Role and company: {{role}}
Job description highlights: {{jd_highlights}}
My background: {{background}}

Rules:

• Ask ONE question per message, then stop and wait for my answer. Never answer for me.

• Plan 6 questions: 2 behavioral, 2 role-specific, 1 about a failure or weakness, 1 curveball based on my background. Don't show me the list.

• After each of my answers, score it before asking the next question:

- Structure (1-5): clear situation, action, result
- Evidence (1-5): specific numbers, tools, and my own actions rather than the team's
- Relevance (1-5): tied back to this role
- One sentence: the strongest part of my answer
- One sentence: what a hiring manager would doubt
- If the total is under 11, ask one realistic follow-up probe before moving on.

• Keep scores short, then return to character.

• After question 6: the top 2 patterns I should fix, and the one answer I should rehearse again.

Start with a 3-bullet read on what this interviewer is likely to probe, given the job and my background. Then introduce yourself in character and ask question 1.

Fill in

{{interviewer_type}}: Who you're practicing for: recruiter, hiring manager, panel, technical lead, executive.e.g. hiring manager
{{role}}: Job title and company (or type of company).e.g. Product Manager, Merchant Onboarding at a Series C payments company
{{jd_highlights}}: The 3-6 responsibilities or requirements that matter most in the posting.e.g. Owns the merchant onboarding funnel; works with risk and compliance; writes PRDs; defines success metrics
{{background}}: Your name and a two-line summary of your experience.e.g. I'm Priya. Five years as a backend engineer at an e-commerce company; led the checkout rewrite; no formal PM title.

Example input

interviewer_type: hiring manager
role: Product Manager, Merchant Onboarding at a Series C payments company
jd_highlights: Owns the merchant onboarding funnel from signup to first transaction; works closely with risk and compliance; writes PRDs; defines and reports success metrics; SQL a plus
background: I'm Priya. Five years as a backend engineer at a mid-size e-commerce company; led the technical side of our checkout rewrite in 2025; no formal PM title, but I ran our team's planning for the last year.

1.3k0

Generated Outputs (1)

3 hours ago

Claude

Opus 5.5

3 hours ago

Generated Output

Before we start, here's what this hiring manager is likely to probe, given the role and your background:

• Can you make product calls, not just build them? The checkout rewrite is strong material, but they'll want to know who decided what to build and why, and how much of that was you rather than a PM.

• Metrics ownership. You'd own the onboarding funnel from signup to first transaction. Expect pressure on how you'd define activation and move it, not just ship features.

• Working with risk and compliance. Onboarding in payments means identity and risk checks that add friction on purpose. They'll test whether you treat compliance as a design constraint to work with, or as an obstacle.

OK, in character from here.

---

Hi Priya, I'm Marcus. I lead product for merchant onboarding, so this role would sit on my team. Thanks for making the time. I've read your background, so I'm going to skip the "walk me through your resume" part and go straight into questions. I'll leave space for yours at the end.

First question: you led the technical side of the checkout rewrite. Tell me about a decision during that project where the team had to choose what not to build. What were the options, who disagreed, and how did it actually get decided?

Why it works

"ONE question per message, then stop" is what makes this feel like an interview rather than a quiz sheet; without it, most models dump all six questions at once.

The rubric with three 1-5 scores gives feedback you can compare across answers, and the two single-sentence lines (strongest part, what they'd doubt) keep it honest without turning into a lecture. The "total under 11 triggers a follow-up probe" rule mimics what real interviewers do when an answer is thin. Asking for a 3-bullet read of the interviewer first means you walk in knowing what they're testing for.

When not to use it

Text practice can't train delivery: pace, filler words, eye contact. Use voice mode or record yourself for that. For live-coding or case interviews, use a dedicated practice format with a timer. And the model's scores are a practice signal, not a prediction of how a specific company grades.

Comments (0)

No comments yet. Be the first to share your thoughts!