9.2: Interview Techniques
- Page ID
- 124589
\( \newcommand{\vecs}[1]{\overset { \scriptstyle \rightharpoonup} {\mathbf{#1}} } \)
\( \newcommand{\vecd}[1]{\overset{-\!-\!\rightharpoonup}{\vphantom{a}\smash {#1}}} \)
\( \newcommand{\dsum}{\displaystyle\sum\limits} \)
\( \newcommand{\dint}{\displaystyle\int\limits} \)
\( \newcommand{\dlim}{\displaystyle\lim\limits} \)
\( \newcommand{\id}{\mathrm{id}}\) \( \newcommand{\Span}{\mathrm{span}}\)
( \newcommand{\kernel}{\mathrm{null}\,}\) \( \newcommand{\range}{\mathrm{range}\,}\)
\( \newcommand{\RealPart}{\mathrm{Re}}\) \( \newcommand{\ImaginaryPart}{\mathrm{Im}}\)
\( \newcommand{\Argument}{\mathrm{Arg}}\) \( \newcommand{\norm}[1]{\| #1 \|}\)
\( \newcommand{\inner}[2]{\langle #1, #2 \rangle}\)
\( \newcommand{\Span}{\mathrm{span}}\)
\( \newcommand{\id}{\mathrm{id}}\)
\( \newcommand{\Span}{\mathrm{span}}\)
\( \newcommand{\kernel}{\mathrm{null}\,}\)
\( \newcommand{\range}{\mathrm{range}\,}\)
\( \newcommand{\RealPart}{\mathrm{Re}}\)
\( \newcommand{\ImaginaryPart}{\mathrm{Im}}\)
\( \newcommand{\Argument}{\mathrm{Arg}}\)
\( \newcommand{\norm}[1]{\| #1 \|}\)
\( \newcommand{\inner}[2]{\langle #1, #2 \rangle}\)
\( \newcommand{\Span}{\mathrm{span}}\) \( \newcommand{\AA}{\unicode[.8,0]{x212B}}\)
\( \newcommand{\vectorA}[1]{\vec{#1}} % arrow\)
\( \newcommand{\vectorAt}[1]{\vec{\text{#1}}} % arrow\)
\( \newcommand{\vectorB}[1]{\overset { \scriptstyle \rightharpoonup} {\mathbf{#1}} } \)
\( \newcommand{\vectorC}[1]{\textbf{#1}} \)
\( \newcommand{\vectorD}[1]{\overrightarrow{#1}} \)
\( \newcommand{\vectorDt}[1]{\overrightarrow{\text{#1}}} \)
\( \newcommand{\vectE}[1]{\overset{-\!-\!\rightharpoonup}{\vphantom{a}\smash{\mathbf {#1}}}} \)
\( \newcommand{\vecs}[1]{\overset { \scriptstyle \rightharpoonup} {\mathbf{#1}} } \)
\(\newcommand{\longvect}{\overrightarrow}\)
\( \newcommand{\vecd}[1]{\overset{-\!-\!\rightharpoonup}{\vphantom{a}\smash {#1}}} \)
\(\newcommand{\avec}{\mathbf a}\) \(\newcommand{\bvec}{\mathbf b}\) \(\newcommand{\cvec}{\mathbf c}\) \(\newcommand{\dvec}{\mathbf d}\) \(\newcommand{\dtil}{\widetilde{\mathbf d}}\) \(\newcommand{\evec}{\mathbf e}\) \(\newcommand{\fvec}{\mathbf f}\) \(\newcommand{\nvec}{\mathbf n}\) \(\newcommand{\pvec}{\mathbf p}\) \(\newcommand{\qvec}{\mathbf q}\) \(\newcommand{\svec}{\mathbf s}\) \(\newcommand{\tvec}{\mathbf t}\) \(\newcommand{\uvec}{\mathbf u}\) \(\newcommand{\vvec}{\mathbf v}\) \(\newcommand{\wvec}{\mathbf w}\) \(\newcommand{\xvec}{\mathbf x}\) \(\newcommand{\yvec}{\mathbf y}\) \(\newcommand{\zvec}{\mathbf z}\) \(\newcommand{\rvec}{\mathbf r}\) \(\newcommand{\mvec}{\mathbf m}\) \(\newcommand{\zerovec}{\mathbf 0}\) \(\newcommand{\onevec}{\mathbf 1}\) \(\newcommand{\real}{\mathbb R}\) \(\newcommand{\twovec}[2]{\left[\begin{array}{r}#1 \\ #2 \end{array}\right]}\) \(\newcommand{\ctwovec}[2]{\left[\begin{array}{c}#1 \\ #2 \end{array}\right]}\) \(\newcommand{\threevec}[3]{\left[\begin{array}{r}#1 \\ #2 \\ #3 \end{array}\right]}\) \(\newcommand{\cthreevec}[3]{\left[\begin{array}{c}#1 \\ #2 \\ #3 \end{array}\right]}\) \(\newcommand{\fourvec}[4]{\left[\begin{array}{r}#1 \\ #2 \\ #3 \\ #4 \end{array}\right]}\) \(\newcommand{\cfourvec}[4]{\left[\begin{array}{c}#1 \\ #2 \\ #3 \\ #4 \end{array}\right]}\) \(\newcommand{\fivevec}[5]{\left[\begin{array}{r}#1 \\ #2 \\ #3 \\ #4 \\ #5 \\ \end{array}\right]}\) \(\newcommand{\cfivevec}[5]{\left[\begin{array}{c}#1 \\ #2 \\ #3 \\ #4 \\ #5 \\ \end{array}\right]}\) \(\newcommand{\mattwo}[4]{\left[\begin{array}{rr}#1 \amp #2 \\ #3 \amp #4 \\ \end{array}\right]}\) \(\newcommand{\laspan}[1]{\text{Span}\{#1\}}\) \(\newcommand{\bcal}{\cal B}\) \(\newcommand{\ccal}{\cal C}\) \(\newcommand{\scal}{\cal S}\) \(\newcommand{\wcal}{\cal W}\) \(\newcommand{\ecal}{\cal E}\) \(\newcommand{\coords}[2]{\left\{#1\right\}_{#2}}\) \(\newcommand{\gray}[1]{\color{gray}{#1}}\) \(\newcommand{\lgray}[1]{\color{lightgray}{#1}}\) \(\newcommand{\rank}{\operatorname{rank}}\) \(\newcommand{\row}{\text{Row}}\) \(\newcommand{\col}{\text{Col}}\) \(\renewcommand{\row}{\text{Row}}\) \(\newcommand{\nul}{\text{Nul}}\) \(\newcommand{\var}{\text{Var}}\) \(\newcommand{\corr}{\text{corr}}\) \(\newcommand{\len}[1]{\left|#1\right|}\) \(\newcommand{\bbar}{\overline{\bvec}}\) \(\newcommand{\bhat}{\widehat{\bvec}}\) \(\newcommand{\bperp}{\bvec^\perp}\) \(\newcommand{\xhat}{\widehat{\xvec}}\) \(\newcommand{\vhat}{\widehat{\vvec}}\) \(\newcommand{\uhat}{\widehat{\uvec}}\) \(\newcommand{\what}{\widehat{\wvec}}\) \(\newcommand{\Sighat}{\widehat{\Sigma}}\) \(\newcommand{\lt}{<}\) \(\newcommand{\gt}{>}\) \(\newcommand{\amp}{&}\) \(\definecolor{fillinmathshade}{gray}{0.9}\)-
Identify the primary aim of interviews.
-
Describe what makes interview techniques unique.
-
Define the term "interview guide" and describe how to construct an interview guide.
-
Outline the guidelines for constructing good interview questions.
-
Define the term "focus group" and identify one benefit of focus groups.
-
Identify and describe the various stages of interview data analysis.
-
Identify the strengths and weaknesses of interviews.
Conducting Interviews
Interviews might feel more like a conversation than an interview to respondents, but the researcher is, in fact, usually guiding the conversation with the goal of gathering information from a respondent. Interviews contain open-ended questions. As the name implies, open-ended questions are questions that a researcher poses without providing answer options. Open-ended questions are more demanding of participants than closed-ended questions, for they require participants to come up with their own words, phrases, or sentences to respond.
In an interview, the researcher usually develops a guide in advance that they then refer to during the interview (or memorize in advance of the interview). An interview guide is a list of topics or questions that the interviewer hopes to cover during the course of an interview. It is called a guide because it is simply that: it is used to guide the interviewer, but it is not set in stone. Think of an interview guide like an agenda for the day or a to-do list: both probably contain all the items you hope to check off or accomplish, though it probably will not be the end of the world if you do not accomplish everything on the list or if you do not accomplish it in the exact order that you have it written down. Perhaps new events will come up that cause you to rearrange your schedule just a bit, or perhaps you simply will not get to everything on the list.
Interview guides should outline issues that a researcher feels are likely to be important, but because participants are asked to provide answers in their own words and to raise points that they believe are important, each interview is likely to flow a little differently. While the opening question in an in-depth interview may be the same across all interviews, from that point on, what the participant says will shape how the interview proceeds. This is what makes in-depth interviewing so exciting. It is also what makes in-depth interviewing rather challenging to conduct. It takes a skilled interviewer to be able to ask questions, actually listen to respondents, and pick up on cues about when to follow up, when to move on, and when to simply let the participant speak without guidance or interruption.
Interview guides can list topics or questions. The specific format of an interview guide might depend on the researcher's style, experience, and comfort level with the topic. For instance, in a study interviewing young people about their experiences with workplace sexual harassment, the guide might be topic-based. There might be few specific questions contained in the guide; instead, the researcher might use an outline of topics to cover, listed in an order that makes logical sense, noted on a sheet of paper. That guide can be seen in Figure 9.1.
Figure 9.1 Interview Guide Displaying Topics Rather Than Questions
When beginning to construct an interview guide, brainstorming is usually the first step. There are no rules at the brainstorming stage: simply list all the topics and questions that come to mind when you think about your research question. Once you have a pretty good list, you can begin to pare it down by cutting questions and topics that seem redundant and grouping like questions and topics together. If you have not done so yet, you may also want to come up with question and topic headings for your grouped categories. You should also consult the scholarly literature to find out what kinds of questions other interviewers have asked in studies of similar topics. As with quantitative survey research, it is best not to place very sensitive or potentially controversial questions at the very beginning of your interview guide. You need to give participants the opportunity to warm up to the interview and to feel comfortable talking with you. Finally, get some feedback on your interview guide. Ask your friends, family members, and your professors for some guidance and suggestions once you have come up with what you think is a strong guide. Chances are they will catch a few things you had not noticed.
In terms of the specific questions you include on your guide, there are a few guidelines worth noting. First, try to avoid questions that can be answered with a simple "yes" or "no," or if you do choose to include such questions, be sure to include follow-up questions. Remember, one of the benefits of interviews is that you can ask participants for more information, so be sure to do so. While it is a good idea to ask follow-up questions, try to avoid asking “why” as your follow-up question, as this particular question can come off as confrontational, even if that is not how you intend it. Often people will not know how to respond to “why,” perhaps because they do not even know why themselves. Instead of “why,” it is recommended that you say something like, “Could you tell me a little more about that?” This allows participants to explain themselves further without feeling that they are being doubted or questioned in a hostile way.
Even after the interview guide is constructed, the interviewer is not yet ready to begin conducting interviews. The researcher next has to decide how to collect and maintain the information that is provided by participants. It is probably most common for interviewers to take audio recordings of the interviews they conduct.
Recording interviews allows the researcher to focus on the interaction with the interview participant rather than being distracted by trying to take notes. Of course, not all participants will feel comfortable being recorded, and sometimes even the interviewer may feel that the subject is so sensitive that recording would be inappropriate. If this is the case, it is up to the researcher to balance excellent note-taking with exceptional question asking and even better listening. It is difficult to understate the challenge of managing all these feats simultaneously. Whether you will be recording your interviews or not (and especially if not), practicing the interview in advance is crucial. Ideally, you will find a friend or two willing to participate in a couple of trial runs with you. Even better, you will find a friend or two who are similar in at least some ways to your sample. They can give you the best feedback on your questions and your interview demeanor.
All interviewers should be aware of, give some thought to, and plan for several additional factors, such as where to conduct an interview and how to make participants as comfortable as possible during an interview.
Although our focus here has been on interviews for which there is one interviewer and one respondent, this is certainly not the only way to conduct an interview. Sometimes there may be multiple respondents present, and occasionally more than one interviewer may be present as well. When multiple respondents participate in an interview at the same time, this is referred to as a focus group. Focus groups can be an excellent way to gather information because topics or questions that had not occurred to the researcher may be brought up by other participants in the group. Having respondents talk with and ask questions of one another can be an excellent way of learning about a topic; not only might respondents ask questions that had not occurred to the researcher, but the researcher can also learn from respondents’ body language around and interactions with one another. Of course, there are some unique ethical concerns associated with collecting data in a group setting.
Analysis of Interview Data
Analysis of interview data typically begins with a set of transcripts of the interviews conducted. Obtaining said transcripts requires having either taken exceptionally good notes during an interview or, preferably, recorded the interview and then transcribed it. Transcribing interviews is usually the first step toward analyzing interview data. To transcribe an interview means that you create, or someone whom you have hired creates, a complete, written copy of the recorded interview by playing the recording back and typing in each word that is spoken on the recording, noting who spoke which words. In general, it is best to aim for a verbatim transcription, one that reports word for word exactly what was said in the recorded interview. If possible, it is also best to include nonverbal cues in an interview’s written transcription. Gestures made by respondents should be noted, as should the tone of voice and notes about when, where, and how spoken words may have been emphasized by respondents.
If you have the time (or if you lack the resources to hire others), it is often best to transcribe your interviews yourself. Researchers are often amazed by the things they recall from an interview when they transcribe it themselves. If the researcher who conducted the interview transcribes it, that person will also be able to make a note of nonverbal behaviors and interactions that may be relevant to analysis but that could not be picked up by audio recording. Researchers often see interviewees roll their eyes, wipe tears from their face, and even make obscene gestures that speak volumes about their feelings but that could not have been recorded had the interviewer not remembered to include these details in their transcribed interviews.
The goal of analysis is to reach some inferences, lessons, or conclusions by condensing large amounts of data into relatively smaller, more manageable bits of understandable information. Analysis of interview data often works inductively (Charmaz, 2024). To move from the specific observations an interviewer collects to identifying patterns across those observations, interviewers will often begin by reading through transcripts of their interviews and trying to identify codes. A code is a shorthand representation of some more complex set of issues or ideas. In this usage, the word "code" is a noun. But it can also be a verb. The process of identifying codes in one’s qualitative data is often referred to as coding (Saldaña, 2021). Coding involves identifying themes across interview data by reading and rereading (and rereading again) interview transcripts until the researcher has a clear idea about what sorts of themes come up across the interviews.
Many qualitative researchers describe coding as a multistage process. There are two primary phases of coding: open coding and focused coding. To analyze interview data, one can begin by open coding transcripts. This means that you read through each transcript, line by line, and make a note of whatever categories or themes seem to jump out to you. At this stage, it is important that you not let your original research question or expectations about what you think you might find cloud your ability to see categories or themes. It is called open coding for a reason: keep an open mind. Open coding will probably require multiple go-rounds. As you read through your transcripts, it is likely that you will begin to see some commonalities across the categories or themes that you have jotted down. Once you do, you might begin focused coding.
Focused coding involves collapsing or narrowing themes and categories identified in open coding by reading through the notes you made while conducting open coding. Identify themes or categories that seem to be related, perhaps merging some. Then give each collapsed/merged theme or category a name (or code), and identify passages of data that fit each named category or theme. To identify passages of data that represent your emerging codes, you will need to read through your transcripts yet again (and probably again). You might also write up brief definitions or descriptions of each code. Defining codes is a way of making meaning of your data and of developing a way to talk about your findings and what your data mean. Guess what? You are officially analyzing data!
As tedious and laborious as it might seem to read through hundreds of pages of transcripts multiple times, sometimes getting started with the coding process is actually the hardest part. If you find yourself struggling to identify themes at the open coding stage, ask yourself some questions about your data. The answers should give you a clue about what sorts of themes or categories you are reading. In their text on analyzing qualitative data, Lofland, Snow, Anderson, and Lofland (2022) identify a set of questions that are very useful when coding qualitative data. They suggest asking the following:
-
Of what topic, unit, or aspect is this an instance?
-
What question about a topic does this item of data suggest?
-
What sort of answer to a question about a topic does this item of data suggest (i.e., what proposition is suggested)?
Asking yourself these questions about the passages of data that you are reading can help you begin to identify and name potential themes and categories.
Still feeling uncertain about how this process works? Sometimes it helps to see how interview passages translate into codes. In Table 9.1, two codes are presented that emerged from the inductive analysis of transcripts from interviews with child-free adults. A brief description of each code is included, along with a few (of many) interview excerpts from which each code was developed.
| Code | Code description | Interview excerpts |
|---|---|---|
| Reify gender | Participants reinforce heteronormative ideals in two ways: (a) by calling up stereotypical images of gender and family and (b) by citing their own “failure” to achieve those ideals. | “The woman is more involved with taking care of the child. [As a woman] I’d be the one waking up more often to feed the baby and more involved in the personal care of the child, much more involved. I would have more responsibilities than my partner. I know I would feel that burden more than if I were a man.” |
| “I don’t have that maternal instinct.” | ||
| “I look at all my high school friends on Facebook, and I’m the only one who isn’t married and doesn’t have kids. I question myself, like if there’s something wrong with me that I don’t have that.” | ||
| “I feel badly that I’m not providing my parents with grandchildren.” | ||
| Resist Gender | Participants resist gender norms in two ways: (a) by pushing back against negative social responses and (b) by redefining family for themselves in a way that challenges normative notions of family. | “Am I less of a woman because I don’t have kids? I don’t think so!” |
| “I think if they’re gonna put their thoughts on me, I’m putting it back on them. When they tell me, ‘Oh, Janet, you won’t have lived until you’ve had children. It’s the most fulfilling thing a woman can do!’ then I just name off the 10 fulfilling things I did in the past week that they didn’t get to do because they have kids.” | ||
| “Family is the group of people that you want to be with. That’s it.” | ||
| “The whole institution of marriage as a transfer of property from one family to another and the supposition that the whole purpose in life is to create babies is pretty ugly. My definition of family has nothing to do with that. It’s about creating a better life for ourselves.” |
As you might imagine, wading through all these data is quite a process. Just as quantitative researchers rely on the assistance of special computer programs designed to help with sorting through and analyzing their data, so, too, do qualitative researchers. Where quantitative researchers have software like SPSS, qualitative researchers traditionally use Computer-Assisted Qualitative Data Analysis Software (CAQDAS) such as NVivo and ATLAS.ti. These programs work by allowing researchers to import electronic transcript files, label or code passages, search for specific words or phrases, and organize complex interrelationships among passages and codes.
In recent years, the landscape of qualitative software has evolved significantly with the integration of artificial intelligence (AI) and Large Language Models (LLMs). Traditional platforms have upgraded their suites with AI capabilities; for example, ATLAS.ti incorporates generative AI to suggest automated codes and perform sentiment analysis, while MAXQDA offers an AI assistant to summarize massive text documents and paraphrase entries. Simultaneously, a new generation of cloud-based, AI-native platforms has emerged, such as Dovetail and Delve, which lean heavily into automated thematic extraction and real-time data organization.
While these algorithmic tools are incredibly useful for handling massive datasets and speeding up the initial labor of sorting through hundreds of transcript pages, contemporary researchers emphasize a human-in-the-loop framework. AI can efficiently identify surface-level word patterns and generate fast summaries, but it lacks the deep sociological imagination, cultural context, and critical interpretation required to understand the true nuances of human stories. Ultimately, software serves to assist the organization, but the human researcher remains the primary analytical instrument.
Strengths and Weaknesses of Interviews
As the preceding sections have suggested, interviews are an excellent way to gather detailed information. Whatever topic is of interest to the researcher employing this method can be explored in much more depth than with almost any other method. Not only are participants given the opportunity to elaborate in a way that is not possible with other methods such as survey research, but they also are able to share information with researchers in their own words and from their own perspectives rather than being asked to fit those perspectives into the perhaps limited response options provided by the researcher. And because interviews are designed to elicit detailed information, they are especially useful when a researcher’s aim is to study social processes, or the "how" of various phenomena. Yet another, and sometimes overlooked, benefit of interviews that occur in person is that researchers can make observations beyond those that a respondent is orally reporting. A respondent’s body language, and even their choice of time and location for the interview, might provide a researcher with useful data.
Of course, all these benefits do not come without some drawbacks. As with quantitative survey research, interviews rely on respondents’ ability to accurately and honestly recall whatever details about their lives, circumstances, thoughts, opinions, or behaviors are being asked about. However, a major methodological critique of relying solely on interviews is that what people say is often a poor predictor of what they actually do. As sociologists Jerolmack and Khan (2014) argue, self-reports can be of limited value in explaining situated behavior, meaning researchers should be cautious about conflating verbal accounts with actual action. Because of this "attitudinal fallacy," if you want to know what people actually do, you should often supplement interviews with direct observation.
Further, as you may have already guessed, interviewing is time-intensive and can be quite expensive. Creating an interview guide, identifying a sample, and conducting interviews are just the beginning. Transcribing interviews is labor-intensive, and that is before coding even begins. It is also not uncommon to offer respondents some monetary incentive or thank-you for participating. Keep in mind that you are asking for more of participants’ time than if you had simply mailed them a questionnaire containing closed-ended questions. Because qualitative methods are more resource-intensive, sample sizes tend to be much smaller, which limits a researcher's ability to generalize findings to a broader population. There is also a risk of participant bias, where individuals may adjust their answers based on what they think the interviewer wants to hear.
Conducting interviews is not only labor-intensive but also emotionally taxing. When interviewing young workers about their sexual harassment experiences, researchers often hear stories that are shocking, infuriating, and sad. Seeing and hearing the impact that harassment has had on respondents can be difficult. Researchers embarking on an interview project should keep in mind their own abilities to hear stories that may be difficult to hear.
-
Interview Guides: Interview guides can vary in format but should contain some outline of the topics you hope to cover during the course of an interview.
-
Analysis Software that is AI-Enhanced: Software programs like NVivo and ATLAS.ti are tools that qualitative researchers use to help them with organizing, sorting, and analyzing their data.
-
Utility: Interviews allow respondents to share information in their own words and are useful for gathering detailed information and understanding social processes.
-
Drawbacks: Drawbacks of interviews include reliance on respondents’ accuracy and their intensity in terms of time, expense, and possible emotional strain.
-
Question Critique: Come up with a research question and write a few open-ended questions you could ask were you to conduct in-depth interviews on the topic. Now critique your questions. Are any of them "yes/no" questions? Are any of them leading?
-
Self-Interview: Read the open-ended questions you just created, and answer them as though you were an interview participant. Were your questions easy to answer or fairly difficult? How did you feel talking about the topics you asked yourself to discuss? How might respondents feel talking about them?




