Everything else in interview prep — your messages, your bridges, your rehearsal — assumes you already know what the interview is actually about. Reporter research is how you find that out before you’re in the room. A reporter’s beat, their last ten stories, and their history with your organization tell you more about the shape of this interview than the topic line in the request ever will. Skip this step and you’re preparing for the interview you were told about. Do it well and you’re preparing for the interview you’re actually going to get — which are not always the same thing.
1. Where to look
Start with the reporter’s own archive. Most outlets have an author page listing their recent bylines — read the last ten to fifteen stories, not just the headlines. You’re building a picture of what they cover, how often, and how they write, not fact-checking yourself against every sentence.
Next, check the outlet’s beat page or section front. A reporter’s individual output is one signal; what their editors are assigning across the beat is another. If the section has run three stories this month on the same underlying issue, your interview is probably feeding a fourth.
Then look at their social presence — wherever they’re actually active, which for most reporters still means a platform like X or LinkedIn. What do they post about outside their own stories? Whose work do they amplify, quote, or argue with? A reporter who regularly boosts accountability journalism from other outlets brings that same lens to your interview, even on a routine topic.
Finally, search for any past coverage of your organization or sector by this reporter or this outlet. A clean history is useful to know. A history with an unresolved thread — a story that ended with “the company did not respond to a request for comment” — is more useful still, because that thread is often exactly what this interview is trying to close.
None of this takes long. Thirty minutes across an author page, a beat section, a social profile, and a search of your own organization’s name is usually enough to walk in knowing more about the reporter than most spokespeople ever bother to learn.
2. What you’re actually looking for
Reading ten stories is not the goal; extracting a few specific things from them is. First, their angle — the thesis they keep returning to. Reporters on a beat develop a working theory of what’s going on, and most of their questions will test or extend that theory rather than start from zero.
Second, their sourcing pattern. Do they lean on data and documents, on named critics and advocacy groups, on official spokespeople, or on anecdote from affected people? A data-and-documents reporter will ask you to reconcile numbers. An anecdote-driven reporter will ask you to respond to a specific person’s experience. Knowing which one you’re talking to changes what you bring to the conversation.
Third, tone. Read a few paragraphs out loud. Does the writing explain, or does it prosecute? An explanatory reporter is trying to help readers understand a complicated situation. An adversarial one is building a case. Neither is wrong to work with, but you prepare differently for each.
Put those three together and you usually get a tell — a reasonable guess at where this particular story is headed. It won’t be exact. It doesn’t need to be. Even a directional read is enough to stop you from being surprised by the second question.
3. Red flags worth knowing before you say yes
Some patterns are worth spotting before you agree to the interview, not just before you walk into it. A reporter whose recent stories are visibly building toward an accountability piece — repeated FOIA requests, a pattern of “did not respond to multiple requests for comment,” documents cited from a source clearly inside or adjacent to your organization — is not calling for a routine feature.
A beat history that doesn’t match the stated topic is another. If a reporter covers litigation and regulatory enforcement, and this interview was pitched to you as a “profile” or a “trend piece,” that mismatch deserves a direct question back to them before you commit to a time.
Last, watch for signs the story is already largely written. A request for comment with an unusually tight deadline, questions phrased as statements (“isn’t it true that…”), or a reporter who already seems to have your internal numbers is often not asking to learn something — they’re asking for a quote to round out a draft. None of this means you decline. It means you go in knowing which interview you’re actually in.
4. Turning research into prep
Research that sits in a doc nobody reopens didn’t help you. The point of all of it is to change three concrete things: your talking points, your anticipated questions, and your spokesperson choice.
If the reporter favors data, bring the specific numbers and their sourcing, not a general assurance. If they favor anecdote, prepare a human, specific answer to the individual case you expect them to raise — a vague policy answer will read as dodging a real person’s story. If their tone is adversarial, rehearse the two or three hostile framings you now expect, out loud, before the interview, not during it.
If their past coverage of your sector leans a particular direction, decide in advance whether you want to address that history directly or let it go unmentioned unless raised. Either can be right; deciding in the moment is how spokespeople get caught flat-footed on something they actually knew was coming.
The test is simple: if you finished the research and your talking points look identical to what they would have been without it, you didn’t actually use what you learned. Good reporter research doesn’t just make you sound more informed. It changes what you choose to lead with, what you decide to preempt before it’s asked, and who in your organization should be the one answering.
Frequently asked questions
How long should reporter research take?
About 30 minutes: an author page, the outlet's beat section, the reporter's social profile, and a search of your own organization's name. That is usually enough to walk in knowing more about the reporter than most spokespeople bother to learn.
What is the most important thing to learn about a reporter?
Their angle: the working theory of the beat that most of their questions will test or extend. A reporter who has spent two years covering safety failures will ask about safety whatever the stated topic of your interview is.
What are the warning signs that an interview will be adversarial?
Recent stories building toward an accountability piece, repeated 'the company did not respond to requests for comment' lines, documents cited from a source inside your organization, a beat history that does not match how the interview was pitched, and an unusually tight deadline.
Should I research the outlet or the individual reporter?
Both, but the individual reporter matters more. The outlet tells you the audience and general standards; the reporter's own recent work tells you the angle, the sourcing habits, and the tone you will actually face.
Doing this before a real interview? Press Prep automates the reporter-research step: it pulls a reporter’s beat, recent bylines, and social presence, and uses it to draft the questions and talking points you actually need. See media interview preparation for the full pre-interview checklist, or crisis communications media training if the story is already going badly.