What real interviews are made of
Most lists of mock interview questions are the same twenty general questions: tell me about yourself, your greatest weakness, where you see yourself in five years. Those are worth preparing, but a real interview process is several rounds, and each round tests something different. Mock interview practice is most useful when it covers the rounds you’ll actually face.
To see what that looks like, we analyzed 331 interview rounds from 71 hiring processes at 22 companies, including Amazon, Google, Stripe, Netflix, and OpenAI. The research behind them draws on nearly 600 sources and 617 questions that candidates reported being asked. The typical process had five rounds (between two and seven), and the usual round ran about 40 minutes. Here’s how many of the 71 processes included each kind of round:
- Behavioral
- 69 of 71 processes. Nearly every role, technical or not, at every company.
- Case or product problem
- 37 of 71. Product sense, design challenges, business cases, and diagnosis problems.
- Coding
- 31 of 71. Engineering and some data roles, often twice in one process.
- System design
- 18 of 71. Mostly mid-level and senior engineering roles, usually around 60 minutes.
- Portfolio review
- 16 of 71. Design, writing, and research roles.
- Presentation
- 15 of 71. Often a prepared case or strategy you present and then defend.
- Written exercise
- 10 of 71. A memo, an assessment, or interface copy written under time.
- Role-play
- 8 of 71. A colleague who disagrees with you, played by the interviewer.
These counts come from our own research: each company’s hiring pages, its current job postings, and what recent candidates shared. They describe what a candidate should expect, not an official schedule, and the same company can run a different process for a different role. The questions below are grouped by round type, and many come from that research.
Opening and screening questions
The first conversation is usually a recruiter or hiring-manager screen. It checks that your background fits, that you know why you applied, and that practical things like timing line up. These questions also open most later rounds, so they’re the best place to start any mock interview.
- Tell me about yourself and what brings you to this role.
- Why this company, and why now?
- Walk me through one project on your résumé that you’d want us to ask about.
- Why are you leaving your current role, or what are you looking for next?
- What do you know about what this team works on?
- What are your salary expectations?
For “tell me about yourself,” aim for about a minute: where you are now, one experience that shows a skill this job needs, and why this role is the logical next step. Then stop and let them ask. Our interview preparation guide covers how to research the company before this conversation.
Behavioral questions
Behavioral rounds ask what you actually did in a past situation, because how you handled the last disagreement is the best evidence of how you’ll handle the next one. The question is only the start: the interviewer’s follow-ups are where most answers fall apart. These come from our research for specific roles:
- Tell me about a time you used data or analysis to influence a decision when others weren’t yet convinced.
- Tell me about a time you changed the priority of a feature that several teams already expected to build.
- Tell me about a time engineering, operations, and business leaders wanted different outcomes from the same decision.
- Tell me about a technical decision you made that turned out badly, where the failure was yours.
- Tell me about a time you got critical feedback on your work. What did you change?
- Describe a time you had to deliver when something you depended on slipped.
- Tell me about a time you disagreed with someone more senior than you.
- Tell me about a goal you didn’t reach, and what you did afterward.
- What was your part, specifically?
- What did you consider and decide against?
- How did you know it worked?
- What would you do differently now?
The STAR method keeps a story in order, and our 25 behavioral questions with answers go deeper on this round.
Case and product questions
Case rounds give you a problem with no single right answer and watch how you work through it: who you pick as the user, which problem you choose, what you trade away, and how you’d know it worked. Product, design, program, and business roles get these most. Examples from our research:
- A payment platform wants to help software startups recover more failed subscription renewals. Choose the first user, problem, and product bet.
- Critique the moment a rider sees an upfront fare in a ride-hailing app. Explain why it may look this way today, and choose one improvement that also accounts for drivers.
- A global onboarding program hits its completion targets, but first-month defect rates vary threefold by region. Diagnose the gap and design a fix.
- Design a mobile experience that helps a traveler recover when the language they need isn’t available offline.
- An issuer is deciding whether to launch a student rewards card. Using the numbers given, recommend whether to launch.
A good case answer starts by asking one or two clarifying questions, states the assumption it’s making, and commits to a recommendation before time runs out. Practicing it with someone who interrupts with “why that user?” is much harder, and more useful, than working it out on paper.
Coding and system design questions
Coding rounds check whether you can turn a problem into working code and explain your thinking as you go. System design rounds check whether you can shape a system around its real requirements and talk through trade-offs. In both, the interviewer cares about the reasoning they can hear, not only the final answer.
Coding
- Given a string, return the index of the first character that appears exactly once, or −1 if every character repeats.
- Given an integer array, return an array where each position holds the product of every other element, without using division.
- Implement a rate limiter with a capacity, a refill rate, and a check that allows a request only if its full cost is available.
- A small document store returns search matches for words that are no longer in a document. Find and fix the bug.
System design
- Design a payment ledger for a marketplace that records customer charges, refunds, and payouts. Start with the smallest useful design and say what’s out of scope.
- Design a system that removes unhealthy servers from a load balancer within seconds.
- Design the client architecture for a photo feed that works offline.
Explain your approach before you write code, test it on a small example, and say what you’d check next. In a mock round, ask your interviewer to stay quiet for the first few minutes and then push on edge cases, the way a real one would.
Portfolio, presentation, and writing questions
Design, writing, research, and some product roles ask you to show your own work. These rounds feel familiar because the material is yours, which is exactly why people under-prepare them: the interviewer will challenge choices you made months ago.
- Walk me through one project where you made a consequential decision. Make your personal scope clear.
- Present a three-year product strategy for a problem we give you, including what you would not do.
- Write a decision memo recommending whether to change a delivery promise, using the data provided.
- Write the interface text for a flow where a seller’s payout is delayed and the cause is still being investigated.
Time your presentation, leave room for questions, and practice answering “why did you do it that way?” about your weakest slide.
Role-play questions
A few roles include a round where the interviewer plays a colleague who disagrees with you. It tests whether you can hold your position, listen, and still reach a decision together.
- “I’m the design lead. Your conversion target removes a trust explanation at the moment users need it most. Resolve the trade-off with me.”
- “I’m the engineering lead. The launch promise implies a workflow we won’t support this release. Resolve the claim and the scope.”
- “I’m the product manager. Your quieter design is losing the short-term metric this launch was meant to improve.”
These are almost impossible to prepare by reading. You need someone, or something, to push back.
Mock interview questions and answers
Here are three of the questions above with example answers. The candidates are made up, but the shape is what interviewers listen for. Use them to check the structure of your own answers, not as scripts to memorize.
Opening: “Tell me about yourself and what brings you to this role.”
“I’m a data analyst at a regional grocery chain, where for the last two years I’ve owned our weekly sales reporting. The part I enjoy most is when a number changes a decision. Last spring I noticed our promotions were lifting sales but cutting margin in three categories, and that analysis changed how we plan discounts. I’m applying here because your analyst roles sit closer to product decisions, and that’s the work I want more of.”
Why it works: it’s about 40 seconds, it gives one concrete example instead of a list of duties, and it ends on why this role, which hands the interviewer an easy next question.
Behavioral: “Tell me about a time you used data to influence a decision when others weren’t yet convinced.”
“Our marketing team wanted to extend a free-shipping promotion because orders were up. I was asked to confirm it was working. Orders were up, but most of the increase came from existing customers who would have ordered anyway, and the cost per new customer had doubled. The marketing lead disagreed, so instead of arguing in the meeting I split the numbers by new and returning customers and walked her through them one-on-one first. We kept the promotion for new customers only, and over the next quarter shipping costs fell by about a fifth while new orders held steady. What I learned is to bring the person who disagrees into the analysis before the big meeting.”
Why it works: the situation is short, the candidate’s own decisions are clear (splitting the data, talking to the lead first), there’s a result with a number, and it closes with something learned. Expect a follow-up like “What would you have done if she still disagreed?”
Case: “Help software startups recover more failed subscription renewals. Choose the first user, problem, and product bet.”
- Clarify: “Are we the payment provider, and do we know why renewals fail? I’ll assume card declines are the biggest cause.”
- User: early-stage startups with monthly plans, because they lose the most revenue to declines and have no one to chase them.
- Problem: a declined card ends the subscription silently, and the customer often didn’t mean to leave.
- Bet: automatic retries at better times, plus a short, branded message asking the customer to update their card.
- Measure: the share of failed renewals recovered within 14 days, while watching complaints about too many messages.
Why it works: it asks one clarifying question, commits to a single user and a single bet, and names how success would be measured, including what could go wrong. For more worked answers, see our behavioral interview questions and answers and the full answer example.
How to run a mock interview
A mock interview works when it feels like the real thing: one round at a time, timed, with follow-up questions and no notes.
- Pick the round
- Practice the round you’re least ready for, not the one you enjoy. If you don’t know the rounds yet, look up how the company interviews for this role, or start with behavioral, which almost every process includes.
- Set a timer
- Use the real length, usually 30 to 45 minutes, and about an hour for system design. Running out of time is useful information.
- Ask for follow-ups
- Give your interviewer two or three follow-ups for each question, like the ones above. A question with no follow-up only tests your opening line.
- Speak your answers
- Say every answer the way you would in the room, rather than thinking it through or writing notes. That’s where filler, rambling, and missing results show up.
- Record or take notes
- Listening back once is uncomfortable and very effective. Note the moments you hesitated or went long.
- Answer again
- Redo your weakest answer right away, while the feedback is fresh. That second attempt is where most of the improvement happens.
The same steps work for a behavioral mock interview or a technical mock interview; only the questions and the length change. You can run one with a friend, a mentor, a career center, or do a mock interview with AI. Each has trade-offs, which we compare in AI mock interview vs. practice partner vs. coach.
How to judge an answer
“That was good” isn’t feedback. After each answer, check it against a few concrete questions. These are the kinds of standards we use to score practice rounds:
- Was your part clear?
- Someone listening could say exactly what you decided or did, not what “we” did.
- Was there a real decision?
- You named the options and why you chose one. An answer where everything went smoothly usually hides the interesting part.
- Was there evidence?
- A number, an outcome, or a concrete change that shows it worked, or an honest account of what didn’t.
- Did it survive the follow-up?
- When pushed with “why?” or “what would you do differently?”, you added detail instead of repeating yourself.
- Was it the right length?
- Most behavioral answers land between one and two minutes. Technical answers should keep the interviewer with you as you go.
Questions to ask at the end
Practice these too. The end of the interview is your chance to show you’re thinking about the actual work.
- What would success look like in the first six months?
- What’s the hardest problem the team is working on right now?
- How does the team make decisions when people disagree?
- What do people who do well here have in common?
- What are the next steps in the process?
Practice the rounds for your actual interview
The questions above are a good start, but your interview will be specific to one company and one role. With RoundHound, you paste the job posting and we find out how that company interviews for that role: the rounds, their order, and what each one tests. Then an AI interviewer runs each round with you, by voice or by typing, asks follow-up questions, and tells you plainly what went well and what to work on.
Run a mock interview for your job
Paste the job posting and practice each round with follow-up questions and clear feedback. Your first 60 minutes are free.
You can also read how specific companies interview in our company guides, such as Amazon, Google, and Stripe.
Common questions about mock interviews
What are the most common mock interview questions?
“Tell me about yourself,” “Why this company?”, “Tell me about a time you disagreed with someone,” “Describe a goal you didn’t reach,” and “What questions do you have for us?” come up in almost every mock interview. Beyond those, the most useful questions depend on which rounds your real interview includes.
What is a good question to ask in a mock interview if I’m the interviewer?
Ask about a specific past situation, then follow up. “Tell me about a time you had to change a plan at the last minute” is a good start, and “What was your part?” and “What would you do differently?” are what make it useful. Avoid hypotheticals like “What would you do if…”, which are easier to answer well than real situations.
How do I practice for an interview with no experience?
Use classes, group projects, clubs, volunteering, and part-time jobs as your examples; interviewers expect that from students and career changers. Write down five experiences and practice telling each one in under two minutes. Our internship interview guide shows how.
How many questions are in a mock interview?
For a 30- to 45-minute round, plan on three to five main questions, each with two or three follow-ups. More questions with no follow-ups feels productive but tests much less.
What should I practice first?
Behavioral questions, unless you know your interview doesn’t include them. They appeared in 69 of the 71 processes we researched.
Can I do a mock interview on my own?
Yes. Record yourself answering a question, set a timer, and ask yourself the follow-ups above. It’s harder to stay honest without someone else asking, which is why a partner or an AI interviewer helps.
How many mock interviews should I do?
Enough to run each round you’ll face at least once, and your weakest round two or three times. Two well-reviewed rounds teach more than five rushed ones.
Are mock interview questions the same as the real ones?
Rarely word for word. Companies vary their questions, but the kind of round and what it tests stay much more stable. Practice the type of round, not a script.