Job Interview Preparation: Research and Your One-Page Prep Sheet
CareerLesson 1 of 45 min read
What you'll learn
- Decode a job description into the skills and signals it really asks for
- Research a company in about an hour using a fixed checklist
- Map your own experience to each requirement with specific evidence
- Fill in a reusable one-page prep sheet for any role
On this page
Two candidates sit in the same interview. Both are qualified. When asked "Why do you want to work here?", the first says she is passionate about growth and challenging work. The second says she read that the company moved from paper manifests to live tracking last year and that her college project on route planning dealt with the same kind of messy data. The interviewer remembers the second answer. The difference was not talent; it was about one hour of preparation and a place to write it down.
Read the job post like an analyst
A job description is a list of someone's worries. The hiring manager has a problem, such as reports that are always late, and the post is their attempt to describe the person who would fix it. Your first task is to translate it.
- Copy the post into a document so it cannot disappear when the listing closes.
- Highlight the repeated words. A skill that appears in the title, the responsibilities and the requirements is a core need.
- Separate must-haves from nice-to-haves. Phrases such as "required" and "you will own" matter more than "familiarity with".
- Look for the problem behind the post. "Build dashboards" and "work with stakeholders" together suggest that people ask for numbers and do not trust what they get.
- Compare with similar roles. Browse a few related openings on the jobs page and see which skills they all share. The skills directory shows how each skill is used in other roles, which helps you tell a core skill from a company-specific quirk.
An hour of company research
You do not need a deep dive. You need a handful of facts you can bring up naturally. Use a fixed checklist and a timer so research does not turn into a day of scrolling.
| Source | What to look for | Time |
|---|---|---|
| Company website and product pages | What they sell, to whom, and how they describe themselves | 15 min |
| Careers page and the team's own posts | Values, team structure, tools they mention | 10 min |
| Recent news or announcements | A launch, a new market, a change that creates work for this role | 10 min |
| Product itself, if you can try it | One thing you like and one you would question | 15 min |
| Your network and professional profile search | Someone who works there or did, for context | 10 min |
If you can find someone in your network, a short message asking for ten minutes of their time is often worth more than any article. Our post on how to get a referral covers how to approach this without being awkward.
Match your evidence to each requirement
A claim such as "I have strong analytical skills" is forgettable. A claim attached to a specific story is not. For each of the top five requirements, write one piece of evidence: a project, a result, a situation you handled. If you have none, note it honestly as a gap and decide how you will address it, either by being ready to explain how you would learn it, or by building a small project before the interview.
ROLE: Junior Data Analyst, Northfield Freight (a fictional logistics firm)
REQUIREMENT MY EVIDENCE STRENGTH
Write SQL queries Final-year project: 6-table queries Strong
on bus-timetable data; can describe
one slow query I rewrote
Build dashboards One dashboard for a student society Medium
(events attendance); used by 3 people
Explain findings to Presented project results to a Medium
non-technical people class of 40; got questions on slide 4
Works with messy data Cleaned a 20,000-row CSV with Strong
inconsistent dates; wrote down the
rules I used
Experience with forecasting None yet Gap
-> Plan: be honest, mention a short
online exercise I am completingYour story: three pieces to prepare
Almost every interview asks you to introduce yourself, explain a choice and describe a challenge. Prepare three building blocks and you can adapt them to most questions. The first is a 60-second introduction: who you are now, one or two relevant highlights and why this role. Our guide on how to answer "tell me about yourself" walks through the structure in depth.
The second is three stories of roughly two minutes each: one about solving a problem, one about working with other people under friction, and one about a mistake you made and what changed afterwards. Structure them using the approach in behavioural interview questions and the STAR method. The third is your reasons: why this field, why this company and why now, each in a sentence or two. Having these written down stops you from improvising an answer to the most predictable question in the room.
The one-page prep sheet
Everything above goes onto a single page that you can reuse for any interview. Keep it short enough to glance at in the final minutes before you join.
COMPANY / ROLE / DATE / FORMAT: ______________________
INTERVIEWERS (names, titles): ______________________
LINK TO JOB POST (saved copy): ______________________
THE PROBLEM BEHIND THIS ROLE (1 sentence):
______________________________________________________
TOP 5 REQUIREMENTS -> MY EVIDENCE
1. ______________ -> ______________ (strong / medium / gap)
2. ______________ -> ______________
3. ______________ -> ______________
4. ______________ -> ______________
5. ______________ -> ______________
COMPANY FACTS I CAN USE NATURALLY
- What they sell and to whom:
- One recent development:
- One thing I noticed about the product or team:
MY 60-SECOND INTRO (3 bullet points only):
-
-
-
MY THREE STORIES (one-line label each)
A. Solved a hard problem:
B. Worked through disagreement:
C. Made a mistake and changed:
WHY THIS COMPANY / WHY THIS ROLE / WHY NOW:
______________________________________________________
QUESTIONS I WILL ASK THEM (pick 3):
1.
2.
3.
MY GAPS AND HOW I WILL ADDRESS THEM:
______________________________________________________Common mistakes
- Only reading the company's homepage. Symptom: you say things like "I love your mission" and the interviewer asks which part. Add one specific, recent fact.
- Preparing generic strengths. Symptom: answers such as "I am a hard worker" with no example. Attach every claim to a story.
- Hiding gaps. Symptom: you freeze when asked about a tool you have not used. Decide in advance how you will answer honestly.
- Researching only the company, not the interviewers. Symptom: you cannot tailor answers to a hiring manager versus a peer. Check titles and backgrounds.
- Starting with the resume instead of the job post. Symptom: your stories do not match what the role needs. Start from the requirements and work backwards.
How this shows up in real projects and interviews
Real interviewers frequently say they can tell within a few minutes who prepared. They rarely expect deep company knowledge from a junior candidate, though. What they notice is whether you connected what you have done to what they need. The prep sheet is how you make that connection visible. It also keeps your resume honest: anything you cannot back with a story should be reconsidered. If your resume needs work before you start, see how to write a resume that passes ATS.
Try it yourself
Pick a real job post you would like. Copy it into a document, highlight the repeated skills and write the problem behind the role in one sentence. Then complete the one-page prep sheet, including the requirement-to-evidence map with at least one honest gap and a plan for it.
Show a hint
If you cannot attach a story to a requirement within two minutes, mark it as a gap rather than stretching the truth. Interviewers probe weak claims quickly.
Key takeaways
- Read the job post as a list of the hiring manager's problems and highlight repeated skills.
- A timed research checklist gives you a few usable facts without hours of scrolling.
- Map each top requirement to one piece of specific evidence and mark the gaps honestly.
- Prepare a 60-second intro, three reusable stories and your reasons for this company.
- Keep everything on a one-page sheet of bullet points, not scripts.
Test yourself
A trick from this lesson's ride: A job post is a list of the manager's worries, and repeats are the loudest ones. Four more tricks like it wait along the route, each followed by a question.
Frequently asked questions
How do I research a company before an interview?
Spend about an hour on a fixed checklist: what they sell and to whom, one recent development, their careers page and values, the product itself if you can try it, and anyone in your network who knows the team. Note two or three facts you can mention naturally.
What should I put on an interview prep sheet?
The role and interviewers, the problem behind the job, your top five requirements matched to evidence, company facts, a short introduction, three stories, your reasons for applying, three questions to ask and your honest gaps with a plan for each.
How many stories should I prepare for behavioural questions?
Prepare about three solid stories of two minutes each, covering solving a problem, working through disagreement and learning from a mistake. Most behavioural questions can be answered by adapting one of these.