26. Reverse Interview: Questions YOU Should Ask

[!NOTE] "Do you have any questions for me?" is NOT a formality — it is your final interview. The questions you ask reveal your priorities, your seniority level, and whether you have done your homework. Strong questions have gotten borderline candidates hired. Weak questions (or no questions) have gotten strong candidates rejected.

Questions That Signal SSE-Level Thinking

• "What does the on-call rotation look like? How does the team handle production incidents?"
• "What''s your tech debt strategy? How do you balance feature work with infrastructure improvements?"
• "How are code reviews done? What does the PR process look like?"
• "What does a typical sprint cycle look like?"
• "What testing practices does the team follow?"

Questions That Signal Lead Engineer-Level Thinking

• "What''s the biggest technical challenge the team is facing right now?"
• "How are architectural decisions made? Is there an RFC or ADR process?"
• "What does the promotion process look like for senior ICs?"
• "How does the team balance autonomy with alignment across the org?"
• "What''s the ratio of building new features vs. maintaining existing systems?"

Questions That Signal Manager-Level Thinking

• "What are the team''s biggest people challenges right now?"
• "How does engineering leadership measure team health?"
• "What''s the company''s approach to engineering culture at scale?"
• "How does cross-functional collaboration work between engineering, product, and design?"
• "What does success look like for this role in the first 90 days?"

Questions to AVOID

• ❌ "What does the company do?" — Shows zero research
• ❌ "How many vacation days?" — Not for the interview stage
• ❌ "Will I have to work weekends?" — Signals clock-watching
• ❌ "I don''t have any questions" — Signals disinterest

The Power Question Framework

Ask questions that demonstrate you are already thinking like a team member:

1. Challenge question: "What''s the hardest problem the team hasn''t solved yet?"
2. Culture question: "How does the team handle disagreements about technical direction?"
3. Growth question: "What opportunities exist for engineers to grow into technical leadership?"
4. Impact question: "What would you want me to accomplish in my first 6 months?"

[!TIP] Prepare 5-7 questions for each interview. Some will be answered during the conversation. Having extras shows thorough preparation. Customize at least 2 questions to the specific interviewer''s role or background.