How to research a company before an interview
5 min read

"Do your research" is the piece of interview advice everyone gives and almost nobody explains. So people open a dozen tabs the night before, skim the homepage, memorise a line from the mission statement and walk in carrying facts they never get to use. Research is only worth the evening if it changes what comes out of your mouth. You are trying to leave with three things: a clear sense of what this employer needs right now, proof from your own work that you can supply it, and a couple of questions no other candidate will think to ask.
That takes one focused evening and a single page of notes. Here is a good way to spend it.
The posting tells you more than the website
Start with the job posting, because it is the one document where the company had to commit in writing to what it will pay someone to do. Read it twice with a pen. The verbs matter most: a role that will "rebuild" a process is a different job from one that will "maintain" it, even when the title is identical. Named tools and methods tell you how the team works today rather than how it would like to work. Anything mentioned twice usually marks the thing the hiring manager is worried about. From those marks, write down the three or four problems this hire exists to solve and put them at the top of your page. Every fact you gather afterwards either connects to one of them or does not make the cut.
Then read the company's own pages as someone who starts on Monday, not as a customer. Ask who pays this business, for what, and what would make them stop. A firm that sells to large enterprises lives on long contracts and careful change; one that sells to consumers lives on growth and quick releases. That difference will set the pace of your working week, and it is worth being able to say so.
Before you close the careers page, look at the company's other openings. Most candidates skip this, and it takes five minutes. Several openings in one department mean that area is growing. A new manager role posted beside a cluster of junior roles means a team is being assembled, and you might be one of its first hires. You can see an employer's current roles on the jobs list, and each listing links back to the company's own page.
Recent change is what interviews are really about
Old facts rarely come up in an interview. Recent ones often explain why the role is open at all. Search the company name with words like "launches", "acquires", "expands", "appoints" or "restructuring", and read what appeared over the last few months. A new product, a new market or a new leader all change what a team is under pressure to deliver. Pick the two or three changes most likely to reach this team and write one line on each.
If the company is publicly listed, its annual and quarterly filings are free to read[1]. You can ignore the accounts. The letter from leadership and the section on risk factors show, in the executives' own words, what keeps them up at night, and those worries have a way of becoming team goals.
It is also worth reading your interviewer's public professional profile, if you know who it is. You are not hunting for something to compliment. You want to know whether you are talking to someone who came up through sales or through engineering, because they will hear the same story differently. Search your own name while you are at it; they will.
Employee and customer reviews belong here too, read with care. One furious review tells you very little. The same complaint repeated across many months is a pattern worth a question, phrased neutrally: "How has the way the team works changed over the last year?" invites a real answer, where repeating a complaint from a review site starts an argument you cannot win.
Turning notes into answers
This is the step that makes the rest pay off, and the one most people skip. Next to each problem at the top of your page, write a short story from your own work: the situation, what you did, and what changed because of it. Then tie one company fact to each story. Suppose the company has just entered a new region and the role involves training customers. Your account of getting a reluctant client team comfortable with a new system is now directly relevant, and you can explain exactly why. When the interviewer asks why you want to work there, your answer draws on the posting, the news and your own history, and it sounds nothing like a recited mission statement.
Your questions should come from the gaps in what you found. After real research you can ask what a strong first few months would look like given the recent changes, which of the problems in the posting is costing the team most right now, or where the hand-offs with other teams tend to get difficult. Ask one or two per round and treat the answers as research for the next one.
Keep the whole thing to a page you can reread in a few minutes before you walk in or join the call, and keep a separate page per employer so details do not blur together. The tracker holds applications and notes on your own device. Leave out founding dates and office counts; they add nothing. If you only have one evening, read the posting twice, scan the recent news, check the other open roles and write your stories. That alone puts you ahead of most of the field. And if you are still choosing where to apply, browse remote jobs or search all jobs, and do a lighter version of this before each application rather than waiting for the invitation.
References
- Search Filings, U.S. Securities and Exchange Commission. Read on November 12, 2026.