21 Killer Second Interview Questions to Ask Candidates (and What Good Answers Sound Like)

The best second interview questions build on what you learned in round one. They test how the candidate would handle the actual job, how they work with your team and manager, and whether they’re ready to accept an offer. A first interview checks whether someone can do the job. A second interview checks whether they’ll do it well here.

At Apollo Technical, our recruiters have conducted thousands of second interviews across IT and engineering disciplines. Below are the 21 questions we rely on most, grouped by what each one tests. For each one we explain why to ask it, what a strong answer sounds like, and the red flag to note.

All 21 second interview questions at a glance

What makes a second interview different

The first round is a screen. It confirms basic qualifications and whether the candidate is worth more of your time. (Our list of questions to ask an interviewee covers that stage.) The second round usually brings in peers, senior leaders or cross-functional partners. The goal shifts from “is this person qualified?” to “is this the person we want in this seat?”

Candidates also have fewer rehearsed answers left by round two. Questions that build on specifics from the first conversation are much harder to answer with a script, so you get a more honest picture.

How to prepare as the hiring manager

• Reread your round-one notes. Mark vague answers, claims without examples, and anything you’re still unsure about. Those are your follow-up questions.
• Split topics across the panel. If several people are interviewing, give each person a topic (technical depth, teamwork, motivation) so nothing is asked twice and nothing is missed.
• Tailor at least half the questions to this candidate. If they mentioned a specific project, go deeper on it. If an answer sounded rehearsed, come back to it from another angle.
• Bring a real problem. Pick a real challenge the team is facing to use in the situational questions below. It tells you far more than a made-up scenario.
• Decide what a strong answer looks like before you start. A benchmark written in advance keeps you consistent when comparing two or three close finalists.
• Be honest about the role. Share the hard parts of the job. People who accept an offer based on an accurate picture are less likely to leave early.
• Leave 10–15 minutes for their questions. What they ask tells you as much as what they answer.

Questions that follow up on round one

1. Is there anything from our first conversation you’d like to add or revisit?

Candidates often replay an answer they wish they’d given differently. Letting them revisit it early puts them at ease for the rest of the interview, and what they choose to revisit is revealing.

• A strong answer: a thoughtful correction or addition that shows they reflected on the conversation.
• Red flag: nothing at all to add after a long first interview, or a complete change of story.

2. Last time you mentioned [a specific project]. Walk me through the hardest decision you made on it.

This question is built from your round-one notes, so it can’t be rehearsed. It checks that the experience on the résumé is really theirs.

• A strong answer: specific trade-offs, who was involved, what they chose and why, and what they’d do differently now.
• Red flag: the detail gets vaguer the deeper you go, or the story doesn’t match what they said before.

3. What have you learned about us since our first interview?

Strong candidates use the time between rounds to research your products, customers, competitors and team.

• A strong answer: new, specific information and questions that go deeper than your homepage.
• Red flag: the same general knowledge they had in round one.

Questions about doing the actual job

4. Our team is dealing with [a real problem]. How would you approach it in your first month?

This is the closest thing to a preview of how they’ll work. Using a real problem gets you a much better answer than a hypothetical.

• A strong answer: clarifying questions first, then a structured plan with priorities and trade-offs, and a sense of who they’d need to talk to.
• Red flag: jumping straight to a confident answer without asking anything about your situation.

5. Walk me through how you’d handle [a core task from the job description].

For technical roles, this can be a whiteboard walk-through, a design review or a short work sample. It shows skill directly instead of asking the candidate to describe it.

• A strong answer: they explain their reasoning out loud, check their assumptions, and are comfortable saying what they don’t know.
• Red flag: only buzzwords, or unwillingness to go into detail.

6. What would you need from us to be productive in your first 90 days?

It shows self-awareness about how they ramp up, and it gives you a head start on onboarding.

• A strong answer: concrete needs: access to specific people, systems, documentation or early feedback.
• Red flag: “nothing, I’ll figure it out”, or a list of demands unrelated to the work.

7. Which part of this job do you expect to find hardest?

Everyone has gaps. You want to know whether the candidate can see theirs.

• A strong answer: an honest, relevant answer and a plan for closing the gap.
• Red flag: “nothing”, or a disguised strength like “I care too much”.

8. What skills make you a fit for this role, and which ones would you still need to build?

The second half of the question matters as much as the first. People who keep learning tend to name their gaps easily, and usually already have a plan for closing them.

• A strong answer: strengths tied to the job’s must-haves, plus one or two real development areas.
• Red flag: a generic list that could apply to any job.

9. What impact did you make in your last job?

This shows whether they think in terms of process, people or results, and which of those matters most in your role.

• A strong answer: measurable results, or a clear before-and-after, with their personal contribution separated from the team’s.
• Red flag: they describe their duties instead of their results.

10. Tell me about a time you failed at something more than once. What did it teach you?

Repeated failure tests resilience and honesty more than a single mistake does. It pairs well with behavioral interview questions from the first round.

• A strong answer: they own the failures, explain what they changed each time, and show what they do differently now.
• Red flag: a short, safe answer. Ask for a second example. Someone who can’t admit to failing may never have taken a real risk.

Questions about the team and manager

11. What have you done to help a colleague succeed?

Second-round interviewers are often future teammates. They want to know if this person will make the team better.

• A strong answer: a specific example of mentoring, unblocking or supporting someone, told with pride in the other person’s success.
• Red flag: struggling to think of an example, or taking credit for the other person’s work.

12. Tell me about a time you disagreed with a decision made above you. What did you do?

It tests courage and professionalism at the same time.

• A strong answer: they raised the concern respectfully, with evidence, and then committed to the decision even if it went against them.
• Red flag: they always go along with it, or they still hold a grudge.

13. Have you ever not gotten along with a coworker? What happened?

Friction happens on every team. How someone handles it predicts how they’ll behave on yours.

• A strong answer: they focused on the work, tried to understand the other person, and fixed or improved the relationship.
• Red flag: a story where the other person was entirely to blame.

14. What management style gets the best work out of you?

Compare the answer with the actual style of the manager they’d report to. A mismatch isn’t always a dealbreaker, but you should know about it.

• A strong answer: clear self-knowledge, such as how much autonomy, feedback and structure they need, plus some flexibility.
• Red flag: a rigid preference that clearly clashes with their future manager.

15. If you had been the manager in your last job, what would you have changed?

It shows leadership thinking and how they talk about former employers.

• A strong answer: constructive, specific improvements, described without blaming anyone.
• Red flag: a list of complaints about their old boss. That’s likely how they’ll talk about you one day.

Questions about motivation and readiness to accept

16. What should our company be doing better?

Candidates don’t know how things work inside yet, but a sensible suggestion shows research and initiative. It might be about your hiring process, your product, or how you present information to new staff, for example with an interactive digital booklet instead of a stack of PDFs.

• A strong answer: a respectful, specific idea based on something they actually saw.
• Red flag: “nothing, everything looks great”, or harsh criticism with no suggestion attached.

17. What interests you about our industry?

People who care about the industry tend to stay longer than people who just need a job.

• A strong answer: real curiosity: trends they follow, problems they find interesting, and why.
• Red flag: a generic answer that could apply to any industry.

18. Where does this role fit into your plans for the next five years?

It ties the usual “where do you see yourself” question to this specific job.

• A strong answer: a clear line from this role to where they want to go, and it’s a path you can support.
• Red flag: the role is obviously a short stop on the way to something else.

19. What are your salary expectations for this role?

It’s far better to find a big gap now than after an offer is declined. Many states and cities ban asking about salary history, so ask about expectations instead. (See our questions to avoid.)

• A strong answer: a researched range, and openness to discussing total compensation.
• Red flag: no idea of market rates, or a number far outside your budget with no flexibility.

20. Where are you in your job search, and what will decide your choice?

Good candidates at this stage often have other offers. This tells you how fast to move and what matters most to them.

• A strong answer: a straight answer about their timeline and the two or three things that will decide it.
• Red flag: evasiveness, or a decision based on nothing but money when you can’t win on money.

21. What’s a question I should have asked you but didn’t?

It’s a good closing question. It gives a strong candidate one last chance to show you something your questions missed.

• A strong answer: a relevant strength or piece of context you didn’t know about.
• Red flag: a shrug. At this stage, you want people who have thought about why they’re the right choice.

Red flags to watch for in a second interview

• No new research since round one. Strong candidates arrive knowing more than they did last time.
• No specific examples. Hypothetical answers to behavioral questions usually mean a lack of experience, or a story that doesn’t hold up. Push for specifics and watch how they respond.
• A changed story. Some change between rounds is normal. A different reason for leaving, or different key accomplishments, deserves a direct follow-up.
• Negativity about former employers. Everyone has had a hard boss. The people worth hiring can talk about it without bitterness.
• No curiosity about the work. Questions only about time off and remote work, and none about the team or the problems they’d solve, suggest shallow interest.
• Salary far outside your range with no flexibility. Better to know now than at the offer stage.
• Low energy or distraction. They may be treating your role as a backup. Ask directly how it ranks against their other options.

How to decide after the second interview

Get written feedback from every interviewer within 24 hours, before the group discusses the candidate. Otherwise the loudest opinion tends to win. Score each answer against the benchmark you set in advance (the four-point scale in our interview scoring guide works well). Then compare finalists on the role’s must-haves. Before making an offer, confirm what you heard with reference check questions.

If you’re the candidate: how to prepare for a second interview

The questions above are the ones hiring managers actually use in round two, so they are a good guide to what you will face. Expect the interviewer to build on your first conversation and push for more detail. To prepare:

• Reread your notes and the job description. Anything you said in round one may come back as a follow-up question.
• Prepare four or five specific stories. A hard decision, a failure, a conflict with a coworker and a measurable result will cover most of the questions in this list.
• Do new research. Learn something about the company, its customers or its competitors that you did not know last time, and mention it.
• Know your numbers. Have a researched salary range ready, and be honest about where you are with other offers.
• Bring better questions than last time. Round two is your chance to find out whether you want the job.

Good questions to ask the employer in a second interview:

• What does success look like in this role after six months?
• What is the biggest challenge the team is facing right now?
• How will my performance be measured?
• Is there anything about my background that gives you pause?
• What are the next steps, and when do you expect to decide?

For more ideas, see our list of questions to ask the interviewer.

Frequently asked questions

Need help hiring?

Apollo Technical recruits engineering, IT and supply chain talent, and we can handle screening and first-round interviews so your team only meets finalists. Talk to us about our engineering staffing services or IT staffing services, or reach out today.