Research to make the interview a useful conversation
Company research helps you explain why the work interests you, connect your evidence to the role, and ask questions that support your own decision. It is more useful than memorising a company slogan. By the end, you will have a short research brief with verified findings and questions to clarify.
Begin with the vacancy and official employer sources. You are trying to understand what the organisation does, who it serves, and how the role contributes. A beginner does not need to know confidential strategy or every product detail. It is reasonable to acknowledge what you have not been able to confirm.
Research also helps you assess whether the opportunity fits your needs. Mentoring, working arrangements, responsibilities, and management can matter as much as the organisation’s reputation. Prepare questions that investigate these areas without assuming the marketing language describes every team.
Investigate four main areas
Keep notes under four headings so the research stays focused. Distinguish a verified fact, an interpretation, and a question. A product page can establish what is advertised; it cannot establish exactly what a particular team does each day.
Professional profiles can help you understand the kinds of roles in a team, but titles and dates may be incomplete or outdated. Do not infer private reporting relationships or contact people repeatedly to obtain interview information. Use only professional information relevant to your preparation.
| Area | What to investigate | Useful sources |
|---|---|---|
| Company overview | Products, services, customers, purpose, and business context | Official website, product pages, published reports. |
| Role and team | Responsibilities, tools, reporting line, and initial expectations | Vacancy, careers page, recruiter clarification, relevant professional profiles. |
| Recent developments | Relevant product changes, announcements, or business developments | Dated official announcements and reputable reporting. |
| Working environment | Location, collaboration, learning, support, and working arrangements | Careers information plus questions to the interviewer; employee accounts as perspectives. |
A simple 20-minute research plan
Use a time limit to avoid collecting pages of information you will never use. This is a flexible starting point; a more complex role may require additional research.
If you cannot find a reliable recent development, do not invent one. Focus on the product and role instead. If a company name is shared by several organisations, verify the website and recruiter identity independently before sharing documents or personal details.
- Minutes 0–5: Read the vacancy and the employer’s main product or service page. Summarise the role and the user or customer it supports in your own words.
- Minutes 5–10: Read the careers page and identify what is stated about the team, working arrangement, and development support. Mark anything not confirmed.
- Minutes 10–15: Check one relevant, dated announcement or reliable report. Note the source and whether it is still relevant to this interview.
- Minutes 15–20: Connect one finding to genuine evidence from your background. Draft three questions about responsibilities, support, and expectations.
Connect a finding to your skills and interests
A good connection names what you learned, why it matters to you, and an example that supports your interest. Keep the claim narrow enough to defend.
The example shows informed curiosity without claiming expertise in the employer’s product. A career changer might connect a customer-facing background to understanding user needs, then support it with a relevant project rather than pretending to have commercial development experience.
Ask questions that fill real gaps
Choose questions you genuinely need answered. Avoid asking only facts already clear in the vacancy; use those facts as the starting point for a more useful conversation.
Treat employee reviews as individual perspectives, not definitive evidence about every team. Look for dates, context, and recurring questions to investigate. If a review raises a concern, ask a neutral question about the relevant process rather than presenting an anonymous account as established fact.
- What would a person in this role be expected to contribute during the first few months?
- How are junior team members supported when they encounter unfamiliar problems?
- How does the team review work and share feedback?
- How are priorities set, and how do people communicate when a deadline or requirement changes?
- What does the stated hybrid or remote arrangement look like for this particular team?
- What would success look like, and how would it be discussed with the manager?
Company research worksheet and activity
Record the source URL and date checked alongside each important finding. The worksheet is for preparation notes, not confidential information. Its copyable output helps you keep the brief with your interview plan.
- Choose a real employer and spend 20 minutes using the plan above.
- Record at least two sourced findings, one connection to your own evidence, and three questions.
- Check whether each statement is a fact, an assumption, or a question. Remove anything you cannot support.
- Practise a short answer to “Why are you interested in this role?” without reading the company’s wording.
Notes are saved in this browser when storage is available. They are not synced and may be cleared with site data. Copy a backup before leaving; avoid confidential or sensitive information.
Company research brief
Company research brief Company and role: Not recorded Company overview: Not recorded Role and team: Not recorded Recent developments: Not recorded Working environment: Not recorded My connection: Not recorded Questions: Not recorded Preparation notes only. Review accuracy and personalise before use.
Common mistakes and further reading
Avoid confusing the employer with a similarly named company, relying on old announcements without checking dates, or flattering the company without connecting to the actual work. Research should make the conversation specific, not make you sound as though you already know the internal team.