How Many Interviews Are Enough in a Software Engineering Study? Preliminary Findings on Sample Size and Saturation
This paper analyzes empirical software engineering studies published between 2016 and 2025 to reveal that interview sample sizes typically range from 13 to 24 participants, while justifications for sample adequacy and saturation remain inconsistently reported and often rely on implicit reasoning rather than explicit methodological discussion.
Original paper licensed under CC BY 4.0 (http://creativecommons.org/licenses/by/4.0/). This is an AI-generated explanation of the paper below. It is not written or endorsed by the authors. For technical accuracy, refer to the original paper. Read full disclaimer
Imagine you're trying to figure out the perfect size for a group chat to solve a mystery. Do you need a tiny squad of three experts, or a massive army of fifty? A team of researchers from universities in Canada, the USA, and Brazil decided to investigate this exact question, but instead of mystery solvers, they looked at software engineers who use interviews to study how people build and work with technology.
They didn't just guess; they went on a digital treasure hunt through the most important software engineering conferences and journals from 2016 to 2025. They sifted through thousands of papers, filtering out the noise until they found 429 studies that actually used interviews. In total, these studies talked to 7,444 people.
The "Goldilocks" Zone of Interviews
When the researchers looked at the data, they found that there is no single "magic number" for how many people you need to interview. It's not like baking a cake where you must use exactly two eggs. Instead, the size of the group depends entirely on the recipe you're cooking.
However, if you had to pick the most common size, the researchers found that the "sweet spot" for most software engineering studies is between 13 and 24 interviewees. This was the most frequent range, appearing in 152 of the papers they studied.
But the range was wild!
- Some studies were tiny, talking to just one person (like a deep dive into a single hacker or a specific manager).
- Others were massive, interviewing over 100 people.
- The average study talked to about 17.35 people.
The researchers suggest that if you are planning a study and need a starting point, aiming for that 13 to 24 range might be a safe bet, as it's what most other researchers are doing. But they are very clear: this isn't a strict rule. If you are studying a super-specialized group (like senior security experts) who are hard to find, a small group of fewer than 5 people is perfectly normal and acceptable.
The "Stop Sign" Mystery
In the world of interviews, there's a concept called saturation. Think of it like filling a bucket with water. You keep pouring (asking questions) until the bucket is full and no new water (new ideas) can fit in. Once you hit that point, you stop.
The researchers found that many software engineers are a bit vague about when they hit that "full bucket" moment.
- The Good News: Most studies explained why they picked the people they did (like "we needed someone from the security team" or "we wanted to see different companies").
- The Missing Piece: Many studies didn't clearly explain when they decided to stop interviewing. They often just stopped without saying, "Okay, we heard the same thing three times in a row, so we're done."
The researchers noticed that clear discussions about this "stopping point" were mostly found in studies using a specific method called grounded theory. In other types of studies, the decision to stop was often just a guess or based on practical limits (like running out of time or money), rather than a strict methodological rule.
What This Paper Says "No" To
It is important to know what this paper does not say.
- It does not say that small studies (like those with only 5 to 12 people) are bad or "too soft." The researchers argue that if you have a good reason (like studying a rare expert), a small group is totally fine.
- It does not say that you must use a specific number of people to be a "real" scientist. They explicitly argue against the idea that there is one universal number that works for every single study.
- It does not claim to have solved the problem of how to pick a sample size forever. Instead, they suggest these findings are preliminary and emerging. They are like a first draft of a map, showing the general terrain but promising to explore more in the future.
The Takeaway
The main message is that in software engineering, the "right" number of interviews is a flexible thing. It depends on who you are talking to, how hard they are to find, and what you are trying to learn.
The researchers suggest that instead of worrying about hitting a magic number, scientists should be more honest about why they picked their group size and how they knew they were done. They want the field to move away from rigid rules and toward clear explanations, so that a study with 3 experts is judged on its depth, not just its count, and a study with 50 people is judged on its breadth.
For now, the data suggests that 13 to 24 is the most common path, but the journey is open to many different routes.
Drowning in papers in your field?
Get daily digests of the most novel papers matching your research keywords — with technical summaries, in your language.