Common Interview Questions: 340 Real Interviews Show

Almost every list of common interview questions is a guess dressed up as data. Someone remembers a few interviews, adds the classics, and publishes. We took a different route: we counted. This piece is built on 4,136 questions pulled from 340 real interviews, so the ranking below reflects what candidates actually heard on live calls, not what a career blog assumes they heard.

What 340 real interviews are actually made of

In our anonymized analysis of 340 real interviews recorded with MeetAssist between 16 July and 1 August 2026, 187 candidates fielded 4,136 standalone questions. The average interview contained 12.2 questions. The shortest had a single question; the longest ran to 38.

When we sorted every question into a type, the split was lopsided in a way most listicles never show:

• Technical: 54% (2,247 questions), present in 292 of 340 interviews (86%)
• Experience: 15% (633 questions), present in 245 interviews (72%)
• Logistics: 14% (564 questions), present in 185 interviews (54%)
• Behavioral: 11% (450 questions), present in 132 interviews (39%)
• Motivation: 6% (241 questions), present in 139 interviews (41%)

Two things jump out. First, technical questions dominate by volume but the non-technical categories are almost universal: 72% of interviews included at least one experience question, and more than half included logistics. Second, even heavily technical loops open and close with the same handful of human questions. That matches wider data too. A 2025 analysis of 9,247 technical interviews found that a generic opener like "tell me about yourself and your experience" showed up in 68% of interviews, even in coding-focused roles. Interviews are mixed-mode. Preparing only for the technical part leaves most of the conversation to chance.

The 15 most common interview questions, ranked by real frequency

Here is the top of our corpus, ordered by how many times each question was asked, with the number of distinct candidates who heard it in brackets. This is the flagship list, and it looks nothing like the tidy "strengths, weaknesses, five years" template you usually see.

1. Can you give a brief introduction about yourself? 76 times, from 57 candidates
2. Do you have any questions to ask me? 61 times, from 40 candidates
3. Tell me about yourself. 31 times, from 25 candidates
4. What is your expected salary? 21 times, from 16 candidates
5. What attracted you to this job? 15 times, from 14 candidates
6. Why are you looking to change jobs? 14 times, from 11 candidates
7. When would you be able to start? 14 times, from 10 candidates
8. Tell me about a time you solved a difficult problem. 11 times, from 11 candidates
9. How are you? 10 times, from 9 candidates
10. What is your notice period at your current company? 9 times, from 8 candidates
11. Describe a time you worked with a difficult team member, supervisor, or customer, how you handled it, and the outcome., 9x (7)
12. Where are you located?, 8x (8)
13. Can you tell me about yourself and why you're interested in this role?, 8x (8)
14. How does TypeScript support safer development tooling like autocomplete and refactoring?, 8x (2)
15. Where are you currently employed?, 7x (6)

The pattern is clear. Some form of "tell me about yourself" occupies the top spot and reappears three times in the top 13. The reverse question, "do you have any questions to ask me?", is the second most common thing a candidate hears. Salary, start date, and motivation questions crowd the rest. Only one technical item cracks the top 15, and it was asked to just two candidates, which shows how role-specific technical questions fragment while the human questions repeat across almost everyone.

The takeaway for prep: a short list of high-frequency questions covers a huge share of what you will face. External research lines up with this. One 2025 survey found that "tell me about yourself" is asked by 87% of interviewers, making it the single most trackable question in hiring.

Experience questions: 'tell me about yourself' and how to answer

Experience questions made up 15% of everything asked and showed up in 72% of interviews. Two openers dominate this category: "Can you give a brief introduction about yourself?" (76x) and "Tell me about yourself." (31x). A distant third is "Describe a recent project you're proud of and its impact." (6x).

The mistake candidates make here is treating the opener as small talk and rambling through their resume in chronological order. Interviewers decide fast: 75% say they know within the first 15 minutes whether a candidate fits. Your answer to this question is where that impression forms. Keep it to 60-90 seconds, structured as present, past, then why-you're-here. We break the full approach down in our guide to building a story bank instead of a script, but here are copy-ready models for three common situations.

Experienced individual contributor:

I'm a backend engineer with six years building payment systems, most recently at a fintech where I owned the transaction service that handled about 40 million requests a day. Before that I spent three years at a smaller product company, which is where I learned to ship fast without breaking things. What pulled me toward this role is that you're scaling the same kind of high-throughput infrastructure I've spent my career on, and I'd rather go deep on a problem I already care about than start over somewhere adjacent.

Career changer:

I spent five years in operations before moving into data analysis, and I made the switch on purpose. In my ops role I kept building spreadsheets and dashboards to explain why our numbers moved, and I realized that was the part of the job I actually looked forward to. So I finished a data bootcamp, rebuilt our team's reporting in SQL and Python, and cut our monthly close from three days to one. This role is the natural next step: analytics full-time, on a bigger dataset, with a team I can learn from.

Junior or recent graduate:

I graduated last year in computer science, and I've spent the time since then building real projects rather than just coursework. My capstone was a scheduling app that about 200 students at my university actually used, and maintaining it taught me more about handling bug reports and edge cases than any class did. I also did a summer internship where I shipped two small features into production. I'm looking for a first full-time role on a team that reviews code carefully, because I want to get good habits early.

Logistics questions people underestimate (salary, notice, 'any questions for me?')

Logistics questions were 14% of the total and appeared in 54% of interviews. People treat them as filler and then fumble the two that matter most. The top item in the whole category is "Do you have any questions to ask me?" (61x, 40 candidates), followed by "What is your expected salary?" (21x), "When would you be able to start?" (14x), and "What is your notice period at your current company?" (9x).

The reverse question is not a formality. It is the second most common question in our entire dataset, and a weak answer here undoes a strong interview. Have three real questions ready. Our breakdown of good questions to ask an interviewer covers what 192 real interviews reveal about which ones land, but a reliable set looks like this:

What does success look like for someone in this role in the first six months? What's the biggest challenge the team is dealing with right now? And how do you personally like to give feedback?

Salary is the other landmine. The safe move is to anchor with a researched range and stay collaborative, not defensive. Our full set of salary expectation scripts goes deeper, but this works when you're put on the spot:

Based on my research for this role and market and my experience, I'm targeting somewhere in the range of X to Y. That said, I'm flexible depending on the full package and the scope of the role. Do you have a band budgeted for this position? That would help me be more specific.

Behavioral questions and the STAR answers that pass

Behavioral questions were 11% of the corpus and showed up in 39% of interviews. The most common were "Tell me about a time you solved a difficult problem." (11x), "Describe a time you worked with a difficult team member, supervisor, or customer" (9x), "Describe a time you disagreed with a coworker" (7x), "What are one or two of your key strengths?" (6x), and "What is your greatest weakness?" (4x).

Here is the counterintuitive part. These are the most predictable questions in hiring, yet candidates rate them the hardest. In one 2025 survey, 83% of employers use behavioral questions and 47% of candidates say they are the toughest. People over-prepare technical trivia and under-prepare their own stories. The fix is STAR: Situation, Task, Action, Result. Build a small bank of stories in advance so you're not inventing under pressure; our system for that lives in the guide to "tell me about a time" questions. Here are complete answers you can adapt.

Tell me about a time you solved a difficult problem:

Our checkout API started timing out during peak hours, and support tickets were climbing. My job was to stop the bleeding without a full rewrite. I traced it to a database query that scanned an unindexed table every time a cart loaded, added a composite index, and cached the most common lookups. Response times dropped from around four seconds to under 300 milliseconds, and the timeout tickets went to zero within two days. The bigger win was that I documented the query-review step so it wouldn't happen again.

Describe a time you disagreed with a coworker:

A senior colleague wanted to ship a feature using a new framework none of us knew well, and I thought it added risk right before a launch. Rather than shut it down, I asked to spike both approaches for a day so we could compare. My task was to make the case with evidence, not opinion. The prototype showed the new framework would have cost us a week of debugging, and he agreed to hold it for the next cycle. We shipped on time, and we did adopt his framework later, once we had room to learn it properly.

What is your greatest weakness:

I used to hold onto work too long trying to make it perfect before showing anyone. It bit me on a project where I spent two extra days polishing a report that my manager would have redirected after five minutes. Now I share rough drafts early and ask for direction at the 30% mark. It felt uncomfortable at first, but it's saved me from a lot of wasted effort, and my managers get to steer sooner.

What are one or two of your key strengths:

My strongest skill is turning a vague problem into a plan people can actually follow. When a project lands with no clear scope, I'm the one who writes the one-page breakdown of what we're solving and in what order. On my last team that cut our kickoff meetings roughly in half because people stopped arguing about scope and started building. The second is that I'm calm under production incidents, which comes from having handled enough of them to know panic doesn't help.

Motivation questions: why this job, why leaving, five years

Motivation questions were 6% of everything asked (241 questions) but appeared in 41% of interviews. The most common were "What attracted you to this job?" (15x), "Why are you looking to change jobs?" (14x), and "Where do you see yourself in five years?" (5x). These reward specifics. A generic "I love your mission" answer is forgettable; naming something real about the company is not. We cover the full method in our piece on answering "why do you want to work here" without sounding fake. Two models:

What attracted you to this job:

Two things. The role is squarely on the problem I've spent the last three years on, real-time data pipelines, so I can contribute on day one instead of ramping for months. And when I read your engineering blog, the post on how you handle schema migrations without downtime told me this is a team that cares about doing things properly, not just shipping. That combination of relevant work and high standards is exactly what I'm looking for.

Why are you looking to change jobs:

I've learned a lot where I am, but the product is stable and mature, so the interesting technical problems are mostly behind us. I'm ready for a stage where the architecture is still being decided and I can have a real say in it. Nothing went wrong at my current job; I'd just rather move toward growth than wait for it.

How to prepare for (and survive) these questions in the real call

The data points to a simple prep strategy. Because 86% of interviews include technical questions and 72% include experience questions, you cannot skip either, but the experience, logistics, behavioral, and motivation questions are the ones that repeat verbatim across candidates. That is where preparation pays off most, because you can write and rehearse the exact answers in advance.

Concretely: prepare a 60-second "tell me about yourself," a salary range with a fallback line, three questions to ask back, and four STAR stories that can flex to cover problem-solving, conflict, failure, and a strength. That short list maps directly onto the top of our ranking and will carry most of any interview. For the technical portion, prep is role-specific; if you're going for engineering roles, our system design interview prep guide covers what changes between mid-level and senior.

The hard truth is that questions land live and unscripted. You can rehearse perfectly and still blank when a curveball hits mid-call. That is the gap real-time help closes: MeetAssist listens to the live Zoom, Google Meet, or Microsoft Teams call and surfaces answer suggestions on your screen, staying invisible while you share your screen. It works during the actual interview, not a practice session, which is exactly when the pressure is highest and your prepared answer decides to leave your head.

Frequently asked questions

What are the 7 most common interview questions?

Based on our analysis of 340 real interviews, the seven most frequent were: some form of "tell me about yourself," "do you have any questions to ask me?", "what is your expected salary?", "what attracted you to this job?", "why are you looking to change jobs?", "when would you be able to start?", and "tell me about a time you solved a difficult problem." Notice how few are technical. The questions that repeat across almost every candidate are personal and logistical.

How many questions are asked in a typical job interview?

In our corpus the average interview contained 12.2 questions. The range was wide: the shortest interview had a single question and the longest had 38. Most 45-minute interviews land in the 10 to 15 question band, split across technical, experience, and logistics.

What are the most common behavioral interview questions?

The most common behavioral questions we recorded were "tell me about a time you solved a difficult problem," "describe a time you worked with a difficult team member," "describe a time you disagreed with a coworker," "what are your key strengths," and "what is your greatest weakness." Answer each with the STAR structure so the interviewer gets concrete context, action, and result rather than a vague claim.

What is a good answer to 'tell me about yourself'?

Keep it to 60-90 seconds and structure it as present, past, then why you're here: what you do now, one or two relevant highlights from your background, and why this specific role fits. Skip the full chronological resume and lead with what matters to the job. This question opens roughly 87% of interviews and shapes the first impression, so it is worth rehearsing until it feels natural.