Onsite Interview Questions: 40 Questions by Round and What a Strong Answer Shows

The most common onsite interview questions fall into six groups, one for each typical round: behavioral, coding or technical, system design, a deep dive into your past work, the hiring manager conversation, and culture or values. Below are 40 of them, grouped by round, with what a strong answer shows for each so you know what the interviewer is listening for.

Each onsite interviewer is usually assigned one area, so the same question can be judged differently depending on the round. A project story in a behavioral round is scored on ownership and collaboration; the same project in a deep dive is scored on technical decisions. These questions are representative examples we wrote based on common practice, not questions from any particular company. For first-round staples like "tell me about yourself", see our common interview questions and answers, and for later-stage conversations see second interview questions.

What questions are asked in an onsite interview?

Expect questions that go deeper than your phone screens. Earlier rounds check whether you meet the bar on paper; the onsite checks how you think, how you work with people and how you handle follow-ups. The mix depends on the role and level, as this summary shows.

Onsite interview questions by round

Behavioral questions (1 to 8)

1. "Tell me about a time you disagreed with a teammate." A strong answer shows you separated the person from the problem, used data or a small test to resolve it, and kept the relationship intact. Name what you conceded.
2. "Tell me about a project that failed." Shows ownership without blame. Interviewers listen for what you personally got wrong and what you changed afterward, not a story where someone else caused the failure.
3. "Describe a time you had to deliver with incomplete information." Shows how you handle ambiguity: what you clarified, what you assumed and wrote down, and how you checked those assumptions early.
4. "Tell me about a time you influenced a decision without authority." Shows persuasion through evidence and relationships. A strong answer explains why the other side resisted and what changed their mind.
5. "Tell me about the hardest feedback you have received." Shows coachability. Describe the feedback plainly, how you reacted at first, and the specific change you made.
6. "Describe a time you had too many priorities." Shows judgement about trade-offs. Explain how you ranked the work, who you told, and what you chose not to do.
7. "Tell me about a time you helped someone else succeed." Shows team orientation. Mentoring, unblocking a colleague or sharing credit all work if the result is concrete.
8. "Tell me about a mistake you made that affected others." Shows accountability under pressure. Cover how fast you raised it, how you limited the damage and what process you changed.

Every behavioral answer should follow a clear structure, such as the STAR method, and land in about two minutes. Our STAR examples show the level of detail that holds up to follow-ups.

Coding and technical questions (9 to 15)

9. "Given a list of meeting times, find the minimum number of rooms needed." Shows that you clarify inputs (overlaps, empty lists), state a brute-force approach, then improve it, with time and space complexity.
10. "Return the k most frequent items in a stream of events." Shows data-structure choice and trade-offs. A strong candidate compares a heap with sorting and asks whether memory is limited.
11. "Find whether a path exists between two nodes in a large graph." Shows graph traversal basics, plus judgement about cycles, disconnected components and very large inputs.
12. "Here is a function with a bug. Find and fix it." Shows debugging discipline: reproduce, form a hypothesis, test it, then fix. Reading code carefully matters more than speed.
13. "How would you test the function you just wrote?" Shows that you think in edge cases: empty input, duplicates, large values, invalid types. Strong candidates write tests without being asked.
14. "Write a SQL query to find users who were active in three consecutive weeks." Common in data roles. Shows window functions or self-joins, and a check of what "active" and "week" mean.
15. "Walk me through what happens when you type a URL into a browser." Shows breadth across DNS, networking, servers and rendering. Interviewers often stop you and dig into whichever layer you know best.

System design questions (16 to 21)

16. "Design a URL shortener." Shows scoping before drawing: read-to-write ratio, scale, link expiry. A strong answer covers ID generation, storage and caching, and explains the trade-offs of each.
17. "Design a news feed." Shows understanding of fan-out on write versus read, ranking, and how the design changes for users with very large followings.
18. "Design a rate limiter." Shows knowledge of algorithms such as token bucket or sliding window, where the limiter sits, and what happens when it fails.
19. "Design a notification system that sends email and push messages." Shows queues, retries, idempotency and user preferences. Mention what you would monitor.
20. "How would you scale this design to ten times the traffic?" Shows that you can find the bottleneck first, rather than adding components everywhere.
21. "What would you change if this had to work offline or across regions?" Shows reasoning about consistency, latency and conflict resolution. Naming the trade-off clearly matters more than picking the perfect option.

For a structure you can reuse, see what a system design interview is and our system design cheat sheet.

Project deep-dive questions (22 to 27)

22. "Walk me through a project you are proud of." Shows depth and clarity. Start with the problem and its impact, then your role, then the key decisions, in under three minutes before the interviewer starts probing.
23. "Why did you choose that approach over the alternatives?" Shows that decisions were deliberate. Name at least one alternative you rejected and why.
24. "What would you do differently if you built it again?" Shows reflection. A strong answer names a real weakness in the design, not a cosmetic one.
25. "What was your specific contribution, as opposed to the team's?" Shows honesty. Say "I" for your work and "we" for the team's; interviewers notice when they blur.
26. "How did you measure whether it worked?" Shows a results focus. Bring the metric, the baseline and the change.
27. "What was the hardest bug or obstacle, and how did you get past it?" Shows persistence and method. Walk through the steps, including the wrong turns.

Hiring manager questions (28 to 34)

28. "Why do you want this role, on this team?" Shows motivation tied to the actual work. Mention something specific about the team's problem, not just the company's brand.
29. "What do you need from a manager to do your best work?" Shows self-awareness. Be honest and specific, for example clear priorities and direct feedback.
30. "What would you focus on in your first 90 days?" Shows a realistic plan: learn the system and the people first, deliver something small, then take on bigger work.
31. "Tell me about a time you went beyond your role." Shows initiative with judgement. Choose a story where stepping in had a clear reason and result.
32. "How do you prefer to work with product, design or other teams?" Shows collaboration habits. Give a concrete example of how you handled a disagreement across teams.
33. "Where do you want to be in two or three years?" Shows ambition that fits the role. Connect your goal to skills this job would build.
34. "What questions do you have for me?" Shows preparation and genuine interest. Ask about the team's biggest challenge or what success looks like in the first six months. See our questions to ask a hiring manager.

Culture and values questions (35 to 40)

35. "Tell me about a time you put the customer first at a cost to yourself or your team." Shows that customer focus is a habit, not a slogan. The cost should be real.
36. "Describe a time you raised a concern that others did not want to hear." Shows courage and tact. Explain how you raised it and what happened next.
37. "Tell me about a time you had to make a decision quickly with limited data." Shows a bias for action balanced with risk awareness. Say how you limited the downside.
38. "What kind of team culture brings out your best work?" Shows fit and self-knowledge. Be honest; a mismatch found now is better than one found after you join.
39. "Describe a time you changed your mind after hearing a different view." Shows openness. Interviewers want to hear what the new information was.
40. "Tell me about a time you worked with someone very different from you." Shows respect and adaptability. Focus on what you changed in how you worked together.

If a company publishes its values, prepare one story per value. Values rounds often use the published list directly.

Onsite questions by role

The rounds above are the common core. Each role adds its own specialist rounds, and our role guides list the questions for each:

• Software engineer onsite interview questions: coding, design and behavioral rounds
• Senior software engineer onsite interview: deeper design and leadership signals
• Engineering manager onsite interview: people management and delivery
• Machine learning engineer onsite interview: ML fundamentals and ML system design
• Product manager onsite interview questions: product sense, execution and strategy
• Data scientist onsite interview questions: statistics, A/B testing and product cases
• Data analyst onsite interview questions: live SQL and business cases
• Product designer onsite interview: portfolio presentation and design challenge

To see how interviewers turn your answers into a decision, read how onsite interviews are scored. For the full preparation timeline, start with our guide on how to prepare for an onsite interview.

How do I prepare answers that hold up across onsite rounds?

• Build a story bank, not a script. Six to eight stories, each tagged with the competencies it shows, cover most behavioral and values questions. Write bullet points, not full sentences, so your answers stay natural.
• Prepare for the second question. Onsite interviewers dig. For every story, know the numbers, the alternatives you considered and what you would change.
• Do not reuse one story across rounds. Interviewers commonly compare notes in the debrief. Telling the same story to three people can suggest you have only one.
• Think out loud in technical rounds. Silence makes it hard for the interviewer to give you credit. Say what you are considering, even when you are unsure.
• Keep answers to about two minutes. Long answers leave less time for the follow-ups that earn the strongest ratings. Our guide on how to stop rambling in interviews has five fixes.

Practice it

Reading questions is not the same as answering them. Pick ten questions from this list, set a two-minute timer and answer out loud. To get feedback, practice with an AI interview assistant like CoPilot Interview: its Mock Interview builds questions from your résumé and the job description, reads them aloud, and scores each spoken answer out of 10 with what to fix and a model answer. You can set the mix to behavioral, technical, system design or coding to match your onsite. It is free for 15 minutes a day with no account. Follow each employer's rules on AI tools, and use AI to prepare beforehand.

FAQ

What kind of questions are asked in an onsite interview?

Most onsites combine behavioral questions, role-specific technical or case questions, a deep dive into a past project, a hiring manager conversation and often a values round. Engineering onsites commonly add coding and system design.

Are onsite interview questions harder than phone screen questions?

They are usually deeper rather than trickier. Onsite interviewers ask more follow-up questions, expect specific numbers and decisions, and spend longer on each topic than a phone screen does.

How many questions are asked in each onsite round?

A behavioral round of 45 to 60 minutes often covers three to five questions with follow-ups. A coding round is often one or two problems. A design round is usually a single open-ended problem explored in depth.

Should I use the same stories in different onsite rounds?

Try not to. Interviewers commonly share notes, and varied stories show a broader range of experience. You can mention the same project in a deep dive and a behavioral round if you focus on different aspects.

What should I ask at the end of each onsite interview?

Ask each interviewer one question related to their role, such as what a teammate would want from you or what the team is working on next. Avoid asking every interviewer the same thing.

How do I prepare for onsite questions in one week?

Get the agenda from your recruiter, spend the first days on your weakest round, build six to eight STAR stories, and do at least one full mock with back-to-back sessions before the day.