Second-Round Interview Questions: What to Expect + 30 Questions for CS New Grads (2026)

What is a second-round interview?

A second-round interview is the round that follows the phone screen. It runs 60-90 minutes (sometimes a half-day onsite split into 3-5 back-to-back sessions) and is led by the hiring manager, the team you'd join, and sometimes a senior engineer acting as a bar-raiser. Pass it and you advance to a final round or an offer call. Fail it and the loop ends, usually with a polite rejection email two to five business days later.

The second round is a different animal from the phone screen. The phone screen tested whether you could write working code while talking. The second round tests whether you have depth, whether you fit the team, and whether the hiring manager wants to spend the next 12 months working with you. Same candidate. Different bar.

This guide is for the CS new grad who just got the second-round invite, possibly the first one in eleven months of applying, and has no map for what's about to happen. Three of them on the calendar in the next two weeks. The recruiter said one is "with the hiring manager," another is "the team round," and a third is "a deeper technical screen with one of our senior engineers." None of that wording is in the LeetCode patterns you've drilled. This guide is the map.

What's the difference between a first and second-round interview?

The first round is a filter. The second round is a decision. That single sentence covers most of the practical difference, but four shifts deserve their own attention.

Shift 1: questions get more specific. A phone-screen behavioral opener is "Walk me through a project on your resume." A second-round behavioral opener is "Walk me through the hardest technical decision you made on that project, and what you'd do differently with more time." The level of specificity doubles. The interviewer is not asking what you did, they're asking why you did it that way.

Shift 2: the bar shifts from correctness to trade-off reasoning. A phone-screen interviewer is satisfied when your code passes test cases. A second-round interviewer is not. A working solution at minute 25 is the floor. The conversation between minute 25 and minute 45 is where the signal lives. "What's the time complexity?" "What if we couldn't use a hash map?" "What if the input was 100 million entries instead of 1,000?" Trade-off reasoning is graded explicitly. Silence after a working solution is no longer rewarded.

Shift 3: behavioral questions get heavier. Phone-screen behaviorals are a 5-minute opener and a 5-minute closer. Second-round behaviorals can be an entire 45-minute session. The hiring manager round is almost entirely behavioral. Conflict, failure, ownership, judgment. The questions probe things you'd rather not think about. The new grads who skip behavioral prep get screened out here.

Shift 4: you meet the team you'd actually work with. The phone screen put you in front of one engineer running through one problem on a script. The second round puts you in front of 2-5 humans who would be your coworkers. They grade whether they want to spend their workdays around you. This is the round where likability, energy management across multiple sessions, and basic warmth start counting.

Why CS new grads get blocked at the second round specifically

Eleven months of applying. 487 applications. 14 phone screens. Zero offers. Now three second-round invites in two weeks. This is the moment new grads have been training for, and it's also the moment they most commonly bomb. The prep model that gets you to a second round is not the prep model that gets you through one.

Six failure patterns dominate at the new-grad level:

Pattern 1: under-preparing behavioral. "It isn't technical, so I'll wing it." The hiring-manager round kills more new-grad loops than the coding rounds. New grads spend the 48 hours before a second round on LeetCode and walk in technically sharp but unable to answer "tell me about a time you disagreed with a teammate" without a 90-second pause and a thin story.

Pattern 2: repeating the same internship story across every behavioral answer. You only had one real internship. So the project from that internship becomes the story for ownership, for conflict, for failure, for impact. The hiring manager hears the repetition and grades it correctly: thin experience, narrow self-reflection.

Pattern 3: generic motivation answers. "I want to work at Google because it's a great company." The interviewer wanted: "I want to work on the Search Ads measurement team specifically because of the post you published three months ago about cross-device attribution." Specificity reads as preparation. Generality reads as you-could-be-anywhere.

Pattern 4: trade-off reasoning collapse. You solve the coding problem at minute 22 and then go silent. The interviewer asks "what would you do differently?" You blank. The first solution was the easy part. The conversation after the first solution is the actual second-round test.

Pattern 5: closing-question failure. You burn your 5 minutes of own-questions on things you could have Googled. "What's the culture like?" "What does a typical day look like?" Both are recruiter questions. By second round you should have specific questions about the team's work that prove you read the blog and looked up the people.

Pattern 6: the energy curve collapse. Half-day onsites have 3-5 sessions back to back. Most new grads bring strong energy to session 1 and 2, fade in session 3, and are visibly flat by session 4. The interviewer in session 4 doesn't know you were great in session 1. They grade what they saw. Pacing matters as much as preparation.

If any of these read like your last second round, you're not alone. They're predictable enough that the fix is also predictable. The rest of this guide is the fix.

The 30 questions you should rehearse before a second interview

Five categories of question repeat across companies. Rehearse one answer per question out loud before the second round. The wording will not be exact, but the shape and the underlying probe will be.

Behavioral questions (judgment + self-awareness)

These are the hardest questions for CS new grads because the prep model is unfamiliar. Use STAR (Situation, Task, Action, Result) or PAR (Problem, Action, Result). 90-120 seconds per answer. Different story per question. Do not recycle.

1. Tell me about a time you disagreed with a teammate on a technical decision. What did you do?
2. Describe a project that didn't go the way you expected. What did you learn?
3. Walk me through a time you had to make a call without complete information.
4. Tell me about the most challenging thing you've worked on, and why it was challenging.
5. Tell me about a time you got harsh feedback. How did you handle it?
6. What's a strength of yours that has also caused problems?
7. Tell me about a time you owned something end-to-end. What was the scope and what was the outcome?

Technical-deepening questions (depth beyond the first answer)

These come during or after the coding portion of the round. The phone screen ended with the working solution. The second round starts there.

8. What's the time complexity? Walk me through it.
9. What if the input doesn't fit in memory? How would you change your approach?
10. What if we had 100 million users instead of 1,000? What breaks first?
11. What would you do differently with more time?
12. What's the hardest decision you made during this problem, and why?
13. How would you test this code if you were the one shipping it?
14. Where would this code fail in production, and how would you instrument to find out?

Scope-and-ownership questions (judgment at the new-grad level)

These probe whether you can reason about responsibility at scope, not just at task level.

15. What would you do in your first 30 days on this team?
16. What would you change about your last internship if you could go back?
17. Tell me about a time you took initiative without being asked.
18. If we hired you and you saw something on the team you thought was being done wrong, what would you do?
19. What's something you've done in the last six months to grow as an engineer?

Motivation questions (do you actually want THIS role)

The interviewer is filtering out candidates who would take any job. They want signal that you specifically chose this team.

20. Why this team, not just any team at the company?
21. What about our work specifically interests you?
22. You've interviewed at other companies. Why are you talking to us?
23. What would make you turn down our offer?
24. Where do you see yourself in three years?

Cultural-fit questions (would you be miserable to work with)

These look harmless but carry weight. The interviewer is grading whether you'd be a problem on the team.

25. How do you handle conflict with someone more senior than you?
26. What kind of manager brings out the best in you?
27. Tell me about a time you helped a teammate who was struggling.
28. What do you do when you're stuck on a problem and your manager is unavailable?
29. Describe your ideal team culture.
30. What's one thing you wish you'd learned in school but didn't?

Don't memorize answers. Memorize the shape: opening sentence (situation), middle (action), close (specific result with a number where possible). Practice five of these out loud per night for the three nights before the second round. Out loud is non-negotiable. Saying it in your head is not the same skill as saying it to another human.

Honest aside from someone who's screened a lot of new grads: the candidates who walk out with offers are almost never the ones with the cleanest delivery. They're the ones whose stories sound like things that actually happened, with the awkward parts left in. A pause to think mid-answer reads better than a paragraph that flows perfectly but feels rehearsed. Don't ChatGPT-polish these.

How to prepare for a second-round interview (24-72 hours)

A second-round invite usually lands with 24-72 hours of prep time. Here is the five-step cycle for that window.

1. Get the format from the recruiter in writing. Email the recruiter the moment the invite lands. Ask: single call or half-day onsite, who is interviewing you and their roles, what topics each session covers, remote or in-person. Recruiters answer this email the same day at most companies. Prepping for the wrong format is the single biggest avoidable mistake.

2. Read everything public about the team and the role. Engineering blog posts from the last 12 months. Job description line by line. The hiring manager's LinkedIn if findable. Recent press or product launches the team was involved in. Write down three specific things you'd want to ask about the team's work. Specific beats generic at every turn.

3. Prepare four behavioral stories using STAR or PAR. Map four distinct stories to the four common buckets: ownership, conflict, failure, impact. 90-120 seconds out loud each. Different story per bucket. Do not reuse the same internship project four times. The hiring manager hears the repetition.

4. Drill technical-deepening on every project on your resume. For every project, prepare answers to three questions: what was the hardest decision, what would you do differently, what happens at 10x or 100x scale. Second-round interviewers ask exactly these follow-ups.

5. Prepare five real questions to ask each interviewer. Different questions per interviewer. Read off a list during the round. That reads as prepared, not robotic. End every session with the same closing question: "Knowing what you know about this role, what kind of candidate would excite you most?"

Sleep matters more than one extra hour of LeetCode the night before. Coffee, water, plugged-in laptop, tested headset, reviewed notes. All hygiene, not prep. Do not learn a new framework on day-of.

Second-round interview format by company size

The second-round format varies more by tier than the phone-screen format does. Here is what new grads actually see in 2026:

The 2026 shift to watch: per Entrepreneur's August 2025 reporting, Google, Cisco, and McKinsey were simultaneously reintroducing in-person rounds. At many large employers, the second round (or at minimum the final round) is now in person at a campus or office. SHRM's January 31, 2026 guidance documented the same shift industry-wide. If the recruiter offers travel assistance, take it. The in-person leg is not optional at the tier where it's offered.

Second-round technical interview: what changes from round 1

The technical portion of a second round is one full step harder than the phone screen, and the interviewer's posture changes. Four concrete shifts:

Problem difficulty rises by a step. Phone-screen mediums become second-round medium-pluses. Phone-screen easy-mediums become second-round mediums. The interviewer assumes you're past the basics. You wouldn't be here if you weren't. The bar for "working solution" is the floor, not the ceiling.

Fewer hand-holds when you're stuck. Phone-screen interviewers nudge stuck candidates within 90 seconds because they want to give you a chance to recover. Second-round interviewers wait. They want to see your recovery instincts. Named-stuck-moment recovery ("I'm going to think about this for 30 seconds and try a different angle") is graded explicitly. Silence past 60 seconds without naming what you're stuck on is a flag.

Trade-off reasoning is graded as the main signal. After your first solution works, the interviewer will ask one of three questions: "What's the time complexity?" "What would you do differently?" "What if we changed the constraints?" Going silent here is the single biggest cause of second-round technical rejections. Practice talking past the first solution.

System-design vocabulary comes in. Even at the new-grad level, the second round often includes 15-20 minutes of system-design-lite. "Design the data model for a basic feed feature" or "how would you structure the API for this product." Not full senior-bar system design. Vocabulary check: do you know what a queue is, can you reason about an API endpoint, can you name a basic database trade-off. The system design basics for new grads guide covers the vocabulary the second round expects.

The deeper change is psychological. Phone screens reward clean execution. Second-round technicals reward engineering judgment. Engineering judgment is a different muscle. The new grads who pass the second round are the ones who treat the coding problem as the starting point of a conversation, not as the end.

Second-round behavioral interview: the questions that filter the new grad

The behavioral round is the round most CS new grads under-prep and most second-round loops end in. The hiring manager is the primary behavioral interviewer. They will spend 30-45 minutes on behavioral alone if you're at a mid-tier-or-larger employer.

The questions cluster around four probes:

Probe 1: judgment under conflict. "Tell me about a time you disagreed with a teammate on a technical decision." The hiring manager is filtering for whether you can disagree productively, not whether you'll roll over or whether you'll dig in unreasonably. Wrong answer: "I just deferred to the senior person." Wrong answer: "I refused to budge because I was right." Right shape: I heard them out, I tested their reasoning against my own, I escalated to data or to a third opinion, I went with the path that won the argument and not the path my ego wanted.

Probe 2: failure and recovery. "Describe a project that didn't go the way you wanted." The hiring manager is filtering for whether you can identify your own contribution to failure, not just the team's or the situation's. Wrong answer: "Everything went great." Wrong answer: "It failed but it was my teammate's fault." Right shape: here's what went wrong, here's specifically what I owned in it, here's what I'd do differently next time.

Probe 3: ownership at scope. "Tell me about a time you took initiative without being asked." The hiring manager is filtering for whether you wait for direction or whether you spot work that needs doing and do it. New grads often lack stories here. Internships are structured. School is structured. Work for hire is structured. If you're thin on initiative stories, mine your hobbies, your open-source contributions, your side projects, your community work. Scope is the variable, not domain.

Probe 4: self-awareness. "What's a strength of yours that has also caused problems?" The hiring manager is filtering for whether you can talk about yourself honestly. Wrong answer: "My perfectionism." (Read as evasive.) Wrong answer: "I work too hard." (Read as canned.) Right shape: a real strength that has a real shadow, with a specific example where the shadow showed up and a specific thing you've done to mitigate it.

The behavioral round in a second-round interview is not a vibe check. It is the round where the hiring manager decides whether they want to manage you for 12-24 months. The new grads who walk in with four prepared stories, mapped to these four probes, drilled out loud, beat the candidates with stronger LeetCode performance. Almost every time. The STAR vs SOAR vs CAR vs PAR frameworks guide maps the five competing behavioral frameworks and which one fits which probe.

I'd add one thing here. If you only have one real story for "tell me about a time you failed," practice it three different ways. The lipsync-during-a-coding-screen story. The internship project that got cancelled. The class group project where you let the team down. Pick one. Tell it like it actually happened. Don't try to make yourself the hero of your own failure. The hiring manager has heard 200 versions of "my biggest failure was caring too much" and stopped buying it in 2019.

What questions to ask the interviewer in round 2

The questions you ask in a second round are different from the ones you ask in a phone screen, in three ways: you have more time (5-10 minutes per interviewer instead of 5 minutes total), you see more interviewers (2-5 instead of 1), and you have specific information about the team you didn't have on the phone screen.

Different question categories for different interviewers:

For the hiring manager: Direction and success questions. "What does success look like for this role at the 6-month mark?" "What's the most important thing the team needs to ship this quarter?" "How do you think about ramp-up for new engineers on the team?"

For engineers on the team: Codebase and engineering-culture questions. "How does the team structure code review?" "What's the on-call rotation like for new engineers?" "What's a recent engineering decision the team has wrestled with?"

For the senior engineer or bar-raiser: Judgment and trade-off questions. "What's a technical decision you've made on this team that you'd revisit if you had it to do over?" "What's the engineering principle this team holds that you'd defend even when it's inconvenient?"

Universal closing question for everyone: "Knowing what you know about this role, what kind of candidate would excite you most in the next round?" This question consistently surfaces real signal. It invites the interviewer to tell you what gap they see, and gives you 90 seconds to address it before the round ends.

Avoid: "What's the culture like?" (recruiter question). "Tell me about a typical day" (the JD covered this). "What's the comp range?" (recruiter conversation, never an interviewer conversation). "How fast can I get promoted?" (signals you're focused on the wrong thing).

The deeper guide on this, including the 12 questions that consistently signal high-quality candidate, is in the best questions to ask your interviewer guide. The frame is the same. The second-round application is what's covered above.

How to follow up after a second-round interview

The post-interview follow-up matters more after a second round than after a phone screen. Three reasons: you saw more interviewers, the gap between the round and the decision is longer (1-5 business days vs. 1-3 business days for a phone screen), and the hiring manager specifically grades thoughtful follow-up as a signal of how you'd communicate on the job.

The structure:

Send a separate thank-you email to each interviewer. Within 24 hours. 100-150 words each. Different content per email. Reference a specific thing that interviewer said, not a generic "great chat." If you saw four interviewers, that's four separate emails, sent to each by name. Hiring managers compare notes. Same email to four people gets flagged.

Reference something specific from the conversation. "Your point about the trade-off you made on the caching layer was interesting. I've been thinking about whether the same approach would apply to the project I mentioned." This signals you were paying attention.

Mention what you'd think more about. "You raised a great follow-up question on the in-memory vs. on-disk trade-off. I want to read more about how teams handle that at scale." This signals intellectual engagement.

Do not follow up with the recruiter until day 7 of silence. The internal debrief takes 1-3 business days. The response email arrives 2-5 business days after that. Following up on day 3 reads as anxious, not eager. The post-interview thank-you guide covers the templates, the silence timelines, and what to do at the 7-day, 10-day, and 14-day marks.

Common reasons CS new grads bomb the second round (and how to recover)

Seven patterns. Most second-round rejections trace back to one of these. The recovery is the same shape: identify the pattern from the rejection email or your own honest replay, fix it, screen again at a calibration-tier employer before the high-priority one.

Reason 1: Treated the behavioral round as a vibe check. The hiring-manager round is graded with the same rigor as the coding round. Fix: prepare four stories with STAR or PAR. Drill out loud.

Reason 2: Repeated the same internship story across every behavioral question. Thin signal reads as thin experience. Fix: identify four distinct experiences, even if some are school projects or hobbies. Map one to each behavioral probe.

Reason 3: Generic motivation answers. "I want to work at Google" instead of "I want to work on this specific team because of X." Fix: read the team blog. Identify three specific things. Reference them by name.

Reason 4: Trade-off reasoning collapse. Solved the coding problem, then went silent when asked "what would you do differently." Fix: for every project on your resume and every LeetCode pattern you've drilled, prepare a 60-second "what would I change with more time or different constraints" answer.

Reason 5: Closing-question failure. Used the 5-10 minutes of own-questions on things you could have Googled. Fix: prepare different questions for each interviewer, written down. Reading off the list is normal.

Reason 6: Energy curve collapse. Strong in session 1, flat by session 4. Fix: treat the half-day onsite as a five-hour athletic event. Eat before. Water between sessions. Stand up and stretch for 60 seconds between sessions. The 7-minute walk between sessions matters as much as the prep.

Reason 7: Didn't know the role. Asked questions that the JD already answered. Fix: read the job description line by line. Twice. Three days before. Then again the morning of.

If a second round just ended in rejection and any of these read like the autopsy, the interview rejection feedback loop guide covers the recovery cycle in detail. The pattern is the same: ask the recruiter for honest feedback within 24 hours, identify the pattern, run 3-5 targeted mocks against that pattern, calibrate at peer-tier employers before re-applying to the highest-priority targets.

Key terms

Second-round interview / 2nd round / Round 2

The round that follows the phone screen. 60-90 minutes (single-call format) or 3-6 hours (half-day onsite format). Led by the hiring manager. The decision round at most companies: pass it and you're at offer or final round; fail it and the loop ends.

Onsite

Historically meant the in-person, multi-session interview day at the company's office. In 2025-2026 may mean virtual: a 4-6 hour video-call onsite with 3-5 back-to-back sessions. The 2026 shift at major employers is back to in-person, at least for the final-most leg.

Hiring manager round

The 30-60 minute session with your would-be direct boss. Almost entirely behavioral and conversational at the new-grad level. The highest-stakes session in the second round: this is the human who decides whether to fight for an offer for you.

Bar-raiser round

A session with a senior engineer from outside the hiring team whose role is keeping the company's overall hiring bar consistent. Has veto power over the offer. Typically a coding round at the harder end combined with deep behavioral probing. Amazon and Google formally run this; mid-tier companies often have an informal version.

Team-fit round

A session (or part of one) with one or two engineers on the team you'd actually work with. Grades whether they want you on the team day-to-day. Tends to feel more casual than the hiring-manager round but is graded with the same rigor.

Take-home

A 2-4 hour coding project given as a phone-screen or second-round substitute. Treated as real signal: interviewers read the code and ask specific follow-ups in the next round.

Debrief

The internal meeting after the second round where all interviewers compare notes and the hiring manager decides hire / no-hire / level. Takes 1-3 business days; response email comes 2-5 business days after the round.

How the second round connects to the rest of the loop

The second round sits between the phone screen and the offer. Five adjacent cornerstones cover the rest of the loop:

• Behavioral interview frameworks (STAR vs SOAR vs CAR vs PAR): the five competing behavioral scaffolds, and which one fits which probe. The framework that makes 90-120 second answers feel natural instead of canned.
• Questions to ask the interviewer: the 12 questions that consistently signal high-quality candidate, with the specific application to multi-interviewer rounds.
• Thank-you email after interview: the templates, the silence timelines, and the second-round-specific rule of separate emails per interviewer.
• Technical phone screen tactics: the phone-screen prep that gets you to the second round in the first place. Useful for understanding the contrast.
• Mock interview practice: the four-mode practice cycle, including the specific second-round mock format that drills hiring-manager behavioral.
• CS new-grad interview loop: the map of the full five-stage loop and how the second round fits inside it.
• Interview rejection feedback loop: the recovery cycle after a bombed second round. Same shape across all rejection patterns.
• System design basics for new grads: the vocabulary the second round expects even at the new-grad level.

Pick the gap your last second round surfaced or the gap your next second round is most likely to expose, jump to the matching cornerstone, close the gap, then screen again.

The honest-prep frame for the second round

Every tactic in this guide assumes the candidate is walking into the second round alone and owning the live performance. The alternative (silently using an AI tool in the live interview) does not work in 2026 because the second round is the round where in-person verification, behavioral consistency across sessions, and first-90-days job performance all start mattering.

The math: a candidate who performs at one level on the phone screen and a notably different level in the second-round in-person leg gets flagged in the debrief. A candidate who lands an offer using live-overlay help in the interview and then can't perform on day 3 of the job gets fired and blacklisted. The short-term cheat becomes a longer-term loss the moment the gap surfaces. The candidates who land good roles and keep them are the ones whose second-round performance is an honest sample of what they'd do on the job from day one.

Use AI to prepare. Mock interviews, behavioral story drilling, technical-deepening practice, coding-pattern review. Walk in earned. The honest interview prep guide covers the line and why crossing it costs more than it saves.

The second round in 2026 is a different animal from the phone screen. Same candidate. Different bar. The questions get more specific, the behavioral weight doubles, the trade-off reasoning gets graded explicitly, and the team you'd work with grades whether they want you in the room. The tactics in this guide (get the format from the recruiter, read the team blog, prepare four stories with STAR or PAR, drill technical-deepening on every project, prepare five real questions per interviewer) are the patterns that separate the new grads who land offers from the new grads who walked in technically capable but bombed the wrong round. None of them are clever. All of them are reps.

InterviewChamp.AI is built for exactly this kind of prep: realistic mock second-round interviews with the hiring-manager behavioral block, live feedback on your STAR answers, and an honest read on whether your stories are landing the way you think they are. Start a practice session and walk in earned.

About the author: Alex Chen is the founder of InterviewChamp.AI, building AI interview prep for the new-grad CS market and writing about the modern interview gauntlet from the inside.