Knowing a company’s founding date is rarely enough to explain why you want to work there. Useful interview research connects the organisation’s customers, products and priorities with the role you would perform. A short research brief helps you make those connections without memorising an entire website.
This guide shows how to build a company research brief before an interview, with UK and Australian applications in mind and a method that works across markets. It focuses on understanding the business and preparing thoughtful questions. It assumes you have separately checked that the vacancy and recruitment contact are legitimate.
Start from the role’s contribution to the business
Read the vacancy and write one sentence describing what the role helps the organisation accomplish. A warehouse coordinator might help orders move accurately and on time. A junior marketing assistant might help produce and check campaign materials. Use the duties in the advertisement rather than inventing a strategic role that sounds more impressive.
Identify the people the role serves: external customers, another department, suppliers or colleagues. This gives your research a direction. You need to understand the parts of the company that affect the work, not every product line and executive biography.
The National Careers Service’s interview preparation guidance recommends reviewing the job description, researching the employer’s website and preparing questions. The brief below turns that general preparation into a practical working document.
For an international UK application, the UK job-search guide covers separate questions about sponsorship and eligibility. Keep those checks visible, but do not let them replace preparation for the actual job. An interviewer may need to assess both your circumstances and your understanding of the work.
Build a source list before writing conclusions
Begin with the employer’s official website, the vacancy page and public product or service information. Add relevant official announcements or reports where available. Note the page title, date and link so you can return to the source and distinguish current information from an old announcement.
Treat each source according to its purpose. A marketing page explains how the company presents its offering; it is not an independent assessment of quality. An annual report may discuss the whole group, while the vacancy belongs to one local business unit. Keep that difference in your notes.
Use outside reporting selectively to understand context, but verify major claims before repeating them in an interview. Avoid relying on a search snippet when the underlying article says something more qualified. Anonymous reviews can suggest questions, but they should not become confident claims about every team or manager.
Do not collect sources simply to fill a page. For each one, ask what it helps you understand about the role. A small set of relevant, traceable information is easier to use than twenty tabs containing facts you cannot connect to the work.
Map the customer, offering and delivery process
Write a plain-language description of who uses the company’s product or service, what problem it addresses and how it reaches the customer. If you cannot explain the offering simply, continue reading before drafting an answer about why the business interests you.
Follow one plausible customer journey using public information. How does someone discover the service, make a purchase or request, receive support and resolve a problem? Do not submit fake enquiries or create work for customer-service staff merely to prepare for an interview. Public help pages and demonstrations may provide enough context.
Now place the advertised role within that journey. A support role may handle questions after purchase. A finance assistant may help maintain accurate records behind the transaction. This connection helps you ask questions about priorities and handovers rather than reciting general admiration for the brand.
Mark gaps honestly. You may not know whether a process is managed locally or by a central team. Write that as a question. A research brief is useful partly because it distinguishes what you know from what you need the interviewer to explain.
Separate facts, interpretations and questions
Use three simple labels in your notes. A fact is something the source actually states. An interpretation is your explanation of what it might mean. A question tests that interpretation or explores a gap. Keeping these separate prevents a reasonable guess from becoming an unsupported assertion.
For example, a company may publicly announce a new service location. That is a fact if the announcement is current and clear. You might infer that coordination demands will change, but the announcement does not prove the advertised role will manage expansion. Ask how the new location affects the team rather than stating that it must be the job’s main challenge.
This method also helps when information conflicts. A vacancy may name one location while an older company page lists another office. Record the discrepancy and seek clarification through the recruitment contact. Do not silently choose whichever version makes the application more convenient.
For Australian roles, the Australia application guide provides broader location and work-arrangement checks. In the company brief, focus on the particular employer and team. General knowledge of a national market cannot tell you how one organisation divides its work.
Connect company needs with your own evidence
Choose two or three requirements from the vacancy and pair each with a truthful example from your experience. Then explain how that capability could support the advertised work. Keep the connection modest and specific; you do not need to claim that you can solve the organisation’s largest strategic problem.
Suppose a fictional company sells equipment with detailed order specifications, and the role involves checking customer records. An applicant who has verified forms during a placement can explain the checking process they used and why accuracy mattered. They should not claim technical product expertise they have not acquired.
Prepare a short motivation answer using a researched fact, the relevant work and your own interest or evidence. Avoid praising the organisation with phrases that could apply to any employer. If your reason is based on a product, service model or type of responsibility, name that connection clearly.
Keep copies of the application you submitted so your interview examples remain consistent. Research should help you explain your suitability more clearly, not lead you to rewrite your history around what you think the company wants to hear. Honest limits are easier to discuss than inflated claims.
Write questions that help you assess the opportunity
Prepare questions about the work, support and expectations. Ask what a successful first few months would involve, how priorities are set or how the role works with another team. These questions can reveal information you need while showing that you have thought about the responsibilities.
Build some questions from a source, but keep the opening brief. “I saw that the service is available through both branches and online. How does this team handle handovers between those channels?” is more focused than a long speech summarising the company website before finally reaching a question.
Avoid questions whose answers are clearly stated in the vacancy unless you need clarification. Also avoid presenting a public criticism as an accusation. If a topic is relevant and appropriate, ask neutrally about the process or challenge rather than assuming a report describes the whole organisation accurately.
For US opportunities, the USA job-research guide helps with the broader application context. Your interview questions should still relate to the specific role. Work-authorisation or practical eligibility questions deserve direct treatment through the appropriate contact, alongside the questions about daily responsibilities.
Assemble a brief you can actually use
Keep the main brief to a manageable length, ideally a page of concise notes with source links stored separately if needed. Include the role’s purpose, the customer and offering, a few verified facts, your evidence connections and the questions you most want answered.
Put the most important unresolved point near the top. If the work location or reporting line is unclear, do not hide it beneath interesting company history. The brief should support a decision as well as a performance in the interview.
Read it aloud as a short explanation of the business and role. If you rely on acronyms you cannot explain or repeat marketing phrases without understanding them, rewrite in ordinary language. You should be able to discuss the material naturally even if you cannot look at your notes.
Update the brief close to the interview if important information has changed. You do not need to monitor every news item, but a revised vacancy or a direct message from the recruiter may alter your preparation. Record the date of the final review so you know which version you used.
Use the interview to test and improve the brief
During the conversation, listen for information that confirms or corrects your assumptions. If the interviewer explains that the role serves internal teams rather than external customers, adjust your questions. Do not insist on your researched interpretation when someone with direct knowledge clarifies the work.
Take brief notes if appropriate, without letting note-taking replace attention. You can ask permission to write down an important detail. Keep the discussion conversational and avoid reading every prepared question regardless of what has already been answered.
- Verify the vacancy and identify the role’s practical purpose.
- Gather a few current, relevant sources and preserve their dates.
- Describe the customer, offering and likely work process.
- Label facts, interpretations and unanswered questions separately.
- Connect requirements to evidence from your own history.
- Prepare questions that improve your understanding of the role.
- Revise your brief after the interview while the details are fresh.
Afterward, compare the actual role with your initial understanding and priorities. Note new questions before an offer stage. A good research brief does more than help you sound prepared: it gives you a clearer basis for deciding whether the opportunity fits the work you want to do.
Frequently Asked Questions
How much company history should I memorise?
Learn enough to understand the organisation, but prioritise current products, customers and the advertised role. Founding dates and executive names are less useful if you cannot explain how the team contributes to the business. Follow any specific preparation instructions from the employer.
What if the company has very little public information?
Use the vacancy and verified official channels to establish what you can, then prepare clear questions about the work. Keep unknowns visible. Limited public information is a reason to seek clarification, not permission to invent a business model or assume every claim is true.
Can I use an AI summary for the brief?
It can help organise public material, but check important statements against the original sources and do not upload confidential recruitment documents without permission. A fluent summary may omit dates or blend facts from different companies with similar names.
Should I propose improvements during the interview?
If asked, explain your assumptions and offer a proportionate idea rather than a confident diagnosis based on limited public information. Questions about the team’s current process often demonstrate better judgement than announcing how you would fix a system you have not yet seen.
