Smart Questions to Ask Your Interviewer
Your questions are not filler — they’re signal. They show how you think, what you value, and whether you can evaluate trade-offs (exactly what senior engineers do every day). The “any questions for me?” moment is also your best chance to reduce risk: teams can look great on a job description and still be chaotic, under-resourced, or mismatched to your goals. This guide gives you a practical set of high-signal questions, grouped by interviewer type, with follow-ups and red flags so you can turn the last 5–10 minutes into a real data-gathering conversation.
What does success look like in the first 30/60/90 days?
This question forces specificity. A healthy team can describe outcomes, milestones, and what “good” looks like beyond vague phrases like “own features.” It also helps you understand whether the role is mainly execution, firefighting, or foundational work.
Best follow-ups: “Which metric or outcome would you be happiest about at day 90?” and “What would cause someone to fail in the first 90 days here?” The second follow-up often reveals hidden constraints: unclear ownership, poor onboarding, frequent priority churn, or unrealistic scope.
- Follow-up: What project would I likely start with?
- Follow-up: Who are my main partners (PM, design, data, platform teams)?
- Follow-up: What does ‘great’ look like vs ‘good enough’ for this role?
How does this team decide what to build vs. what to fix?
Strong teams have a visible decision process for prioritization. Weak teams operate on interrupts, “loudest voice wins,” or leadership-driven urgency without a technical strategy. Ask about the trade-off mechanism: how they balance customer asks, roadmap, reliability, and technical debt.
Good follow-ups: “How do you balance technical debt reduction with feature delivery?” and “When priorities change mid-quarter, how do you adjust without burning out the team?” These questions surface process maturity and leadership behavior under pressure.
- Follow-up: What’s the current biggest tech debt or reliability risk you’re actively paying down?
- Follow-up: Who makes the final call in disagreements (EM, tech lead, PM, architecture council)?
- Red flag: No one can name a single measurable reliability or quality goal (SLOs, latency, defects, incident targets).
What is the hardest technical problem on the team right now?
This is the question that separates generic curiosity from real engineering judgment. Great interviewers will light up and give you a clear, concrete challenge: scaling limits, correctness risks, migration complexity, cost constraints, security/privacy issues, ML evaluation, etc.
If the answer is too polished (“we just need smart people”), ask for an example incident or failure mode: “What broke recently and what did you learn?” A team that never breaks is either extremely mature or not being honest.
- Follow-up: What have you tried so far, and what’s still uncertain?
- Follow-up: If I joined tomorrow, where could I help most quickly?
- Red flag: The answer is purely organizational politics with no technical substance.
How is engineering culture enforced in practice (not in slides)?
Most companies can describe values. Fewer can explain the mechanisms that make those values real. Ask about the operating system: code review standards, incident process, how they share knowledge, and how they handle mistakes.
The best answers include specific rituals (design reviews, weekly tech talks, postmortems), expectations (“no PR without tests for critical paths”), and leadership behaviors (“we protect focus time, we don’t ship in panic”).
- Follow-up: How do you handle production incidents and postmortems? Are they blameless and action-oriented?
- Follow-up: What does a great PR look like here?
- Red flag: “We move fast” is used to justify skipping testing, reviews, or rollback plans.
How does the manager support growth and performance reviews?
If you’re speaking to the hiring manager or an engineering manager, use this opportunity. Ask how performance is evaluated, how promotions work, and how feedback is delivered. You want clarity and predictability — not surprises every six months.
A strong manager can explain: what they look for at your level, how they give feedback, and how they create opportunities (ownership, mentorship, scope). A weak manager focuses on vague “impact” without examples.
- Follow-up: How often do you do 1:1s and what do you use them for?
- Follow-up: Can you share an example of someone growing on your team in the last year?
- Red flag: The manager can’t describe the expectations for the level you’re being hired into.
What does collaboration look like across PM/design/data/platform?
Many engineering roles succeed or fail based on cross-functional friction. Ask how decisions are made, what the handoff points are, and where typical bottlenecks happen.
If the role involves ambiguous product work, ask how experiments are run and how success is measured. If the role is platform-focused, ask how internal customers are supported and how requirements are gathered.
- Follow-up: How do you handle disagreements between PM and engineering about scope or timelines?
- Follow-up: Are engineers involved early in product discovery, or mainly in delivery?
- Red flag: “PM decides everything” or “engineering decides everything” with no negotiation mechanism.
What should I ask different interviewers (recruiter vs manager vs engineer)?
Aim your questions at the right person. Recruiters are best for comp bands, process, benefits, remote policy, and logistics. Hiring managers are best for scope, success metrics, roadmap, and team health. Engineers are best for technical reality: tooling, on-call, quality bar, and day-to-day execution.
A simple rule: ask the person what only they can answer. It shows judgment and respect for time.
- Recruiter: What’s the compensation band and how is leveling decided?
- Manager: What does success look like in 90 days? What’s the team’s biggest risk?
- Engineer: What broke recently? What’s the code review bar? How heavy is on-call?
How do I end strong if time is short?
If you only have time for 1–2 questions, prioritize the ones that are both high-signal and high-leverage: success metrics and the hardest technical problem. Then ask one closing alignment question: “Is there anything you’re concerned about from my interviews that I can clarify?”
That final question gives you a chance to correct misunderstandings and often triggers valuable feedback.
- Best 1-question option: What does success look like in the first 90 days?
- Best 2-question option: Biggest technical challenge + how priorities are decided.
- Close: Is there anything you’d like me to clarify or go deeper on?
Final Takeaway
The goal is not to impress — it’s to learn. High-signal questions turn interviews into two-way evaluation and protect you from joining the wrong team. Prepare 6–10 questions, pick 2–3 based on who you’re speaking to, and use follow-ups to turn answers into evidence. The best candidates don’t just pass interviews — they choose teams intentionally.