Jonas Schmidt

Questions to ask the interviewer that help you decide

Builds end-of-interview questions tailored to who you're meeting and your real concerns, with what good and worrying answers sound like.

At a glance

Best for: Candidates in later rounds who want to use their last five minutes to test real concerns, like workload or how decisions get made, without sounding difficult.
Tested on: Claude · Opus 5.5
You fill in: role_companyinterviewerknown_infoconcerns
You get: What success looks like "A year from now, what would this designer have changed about how product and design work together?" Why: Arjun owns the… (full result below)

interview-prep

job-search

career

Prompt

Prepare the questions I'll ask at the end of my interview. I want questions that help me decide whether to take the job and show I've thought about the role, not ones I could ask anywhere.

Role and company: {{role_company}}
Who I'm meeting (name, title, stage): {{interviewer}}
What I already know from the posting and earlier rounds: {{known_info}}
My biggest concerns or dealbreakers: {{concerns}}

Give me:

1. 6 questions grouped by purpose: what success looks like, the team and manager, my concerns (asked tactfully), and the business. Tailor them to who I'm meeting: don't ask a recruiter about code review, or a VP about PTO policy.

1. For each question: why ask it, and what a good vs. a worrying answer sounds like (one line each).

1. Mark the 3 to ask if only 5 minutes are left.

1. 3 questions to avoid with this person, and why.

Don't include any question that's already answered by what I know.

Fill in

{{role_company}}: The job title and a short description of the company.e.g. Product Designer at Loomcart, a 60-person B2B SaaS
{{interviewer}}: Who you're meeting, their title, and which round it is.e.g. Final round, 30 minutes with Arjun Mehta, VP of Product
{{known_info}}: Facts you already have, so the questions don't repeat them.e.g. 2 designers today; ships weekly; remote in US time zones
{{concerns}}: What would make you turn the job down.e.g. Design only decorating PM specs; AI features pushed without research

Example input

role_company: Product Designer (mid-level) at Loomcart, a 60-person Series B B2B SaaS for wholesale ordering
interviewer: Final round, 30 minutes with Arjun Mehta, VP of Product. The Head of Design, who would be my manager, interviewed me in round 2.
known_info: Two designers today, hiring a third. Design reports to the Head of Design, who reports to Arjun. They ship weekly. They're adding AI-assisted reorder suggestions this year. Remote within US time zones.
concerns: Whether design is involved early or just decorates PM specs; whether the AI features are being pushed without customer research; workload, with two designers covering web and a mobile app.

7960

Generated Outputs (1)

2 hours ago

Claude

Opus 5.5

2 hours ago

Generated Output

What success looks like

1. "A year from now, what would this designer have changed about how product and design work together?"

• Why: Arjun owns the product process; this shows whether he sees design as a partner or as output.

• Good: something concrete, like designers joining discovery or running customer interviews. Worrying: only speed, like "ship more screens faster."

Team and manager

1. "When product and design disagree on a direction, how do you and the Head of Design settle it? Is there a recent example?"

• Why: tests how much weight design carries above your manager.

• Good: a real example where design's view changed the plan. Worrying: "product has the final say," with no example.

Your concerns

1. "Could you walk me through how a recent feature went from idea to launch, and when design got involved?" (5-min)

• Why: your first concern, asked as a story instead of a challenge.

• Good: design at problem framing. Worrying: design received a finished spec.

1. "For the AI reorder suggestions, what have you learned from customers so far, and what would make you change or delay it?" (5-min)

• Why: your second concern; it checks whether research drives the roadmap.

• Good: specific findings, and a real condition for delay. Worrying: "competitors have it, so we need it."

1. "With two designers covering web and mobile and weekly releases, how do you decide what design doesn't get to?" (5-min)

• Why: your workload concern, framed as prioritization.

• Good: an explicit trade-off process. Worrying: "everyone pitches in," or no trade-offs named.

The business

1. "What's the biggest risk to Loomcart's goals this year, and where does design help with it?"

• Why: shows you think beyond the screens and tells you what pressure the team is under.

• Good: a specific risk with a clear role for design. Worrying: a vague answer, or no link to design.

Avoid with Arjun

• Remote setup or time zones: already answered, and asking again suggests you weren't listening.

• Salary, PTO or benefits: take these to the recruiter; he doesn't own them.

• "What does a typical day look like?": your future manager covered the day-to-day in round 2. Use the VP for direction and decision-making.

Why it works

"Tailor them to who I'm meeting", with examples of mismatches, is the key constraint: the same question can be sharp with a VP and wasted on a recruiter. Asking what good vs. worrying answers sound like turns questions into a decision tool; you learn what to listen for, not just what to say.

Framing concerns as questions "asked tactfully" lets you test dealbreakers without sounding negative. The 5-minute shortlist reflects reality, since this part of an interview usually gets squeezed, and the questions-to-avoid list stops you spending a VP's time on things the recruiter can answer.

When not to use it

Questions can't replace backchannel research; if you have a mutual contact, ask them how design really works there. In a first-round screen, keep it to one or two simple questions. And if an interviewer's answers already sound alarming, don't rely on better-phrased questions; ask to speak to a current designer on the team.

Comments (0)

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