How to Research a Company for an Interview and Turn It Into Better Answers
By Daniel Okafor
Use a 20-minute company research method, a sourced example and a fact-to-answer framework to prepare specific interview answers without guessing.
Interview Strategy | Published 2026-04-21
Research the company, role and one current primary source before an interview. Then separate what you observed from what you infer and connect it to a real example from your own work.
Research the employer's site, the actual job description and a dated primary source before an interview. Record a fact, identify any inference as a question, and connect the stated role requirement to a verifiable example from your work. This guide includes a 20-minute first pass and a Microsoft FY2026 filing example.
Use a fact, an inference, and a question Useful interview research does not mean collecting everything about a company. Find one dated fact from a credible source, connect it cautiously to a stated requirement in the current job posting, then write one question about what the public information cannot tell you. Fact: record what the source says, where it says it, and the date or period it covers. Inference: explain why that fact might matter to this role. Label the connection as your interpretation, not a company statement. Question: ask about the team or work detail you could not verify publicly. Research gives you context, but it cannot tell you what an individual interviewer intends to assess. U.S. Office of Personnel Management guidance on structured interviews describes job-related questions about past behavior or hypothetical situations. That guidance applies to structured formats, not every employer's interview. Choose sources that answer different questions Start with primary sources for what the company or employer has stated. Use reporting for outside context, and keep each source's limits beside the note. Source What it can show What it cannot establish Company website, annual report, or filing How the company describes its products, customers, results, and stated priorities for a particular period. Whether an open role or specific team owns that work. Current job posting The responsibilities, qualifications, and outcomes the employer chose to include. Unlisted team priorities or the questions an interviewer will ask. Recent company news or reliable industry reporting A dated launch, business change, or market event that may add context. That the event changes this team's work. Check its date, scope, and connection to the posting. A practical 20-minute research method Minutes 1 to 5: find one recent company fact in an official company source. Save the link and the period it covers. Minutes 6 to 10: mark one or two exact responsibilities in the current job posting. Treat the posting as evidence of the advertised role. Minutes 11 to 15: write one possible connection between the company fact and a listed responsibility. Mark it as an inference and keep it only if the link is reasonable. Minutes 16 to 20: choose one true example from your work and write a question about the team detail you still cannot verify. Keep a four-line research note Fact: [source, date, and what it states] Role requirement: [exact responsibility from the posting] My evidence: [my action and a result I can verify] Question: [what I need the interviewer to explain] Worked example: read a 10-K without guessing about the role Microsoft's FY2026 Form 10-K, filed July 29, 2026 , reports that Microsoft Cloud revenue increased 27% to $214.4 billion and that Azure and other cloud services revenue increased 41%. These are company-reported figures for the fiscal year ended June 30, 2026. Microsoft Cloud is a combined measure described in the filing, not another name for Azure alone. Fact: copy the measure, figures, source, and fiscal period accurately. Inference: if the job posting mentions cloud operations or reliability, these figures may give you a reason to explore scale. They do not show that this team works on Azure or owns a particular problem. Question: ask, “Which reliability or capacity decisions would this role own?” Use a company filing to understand reported context, not to claim knowledge of an unseen team's goals. Turn the note into a natural answer Use only the parts that fit the question you are asked. Connect the posting's actual requirement to your own evidence, and leave uncertain team priorities as a question. Answer structure “I read [source and date] reporting [relevant fact]. The posting asks for [stated responsibility]. In my work, I [specific action] and can show [verifiable result]. How does this role approach [the point I could not verify]?” Drop any detail you cannot support or explain in your own words. For a focused framework on one common interview question, see how to answer “Why do you want to work here?” . Ask about the information you could not find Choose one or two questions tied to the role rather than asking every question on a generic list: Which outcomes would matter most for this role in its first few months? Which responsibilities in the posting will take the most attention from this team? How does this role work with the teams that own related work? Common research mistakes Presenting your inference as a fact about the company or team. Using a result without naming the period it covers. Repeating company praise that could fit any employer. Using a combined financial measure as if it described one product or team. Next step Turn company research into sharper interview answers Use AskMyCareer to organise your role research, examples, and talking points so your answers sound more specific, more relevant, and less rehearsed. Read the “Why should we hire you?” guide Explore AskMyCareer