31 items

Job Interview Prep & Research

A per-interview worksheet for serious candidates — covering company research, your professional narrative, five behavioral stories, targeted questions, and post-interview follow-up. One focused hour here separates candidates who walk out thinking 'I think that went okay' from candidates who walk out with offers. For more background and examples, see the guidance below; for built-in tools and options, use the quick tools guide.

Author

Checklistify Editorial Team

Last Updated

Checklist Items

0 done•31 left•6 of 7 sections collapsed

Record the company name exactly as it appears on the job posting or recruiter email

Use the official company name — not a common abbreviation or parent company — so your notes, follow-up emails, and application tracker are consistent. If the recruiter's email signature shows a different entity name than the job posting, note both: some companies hire through holding companies or subsidiaries, and referencing the wrong name in correspondence is an easy avoidable error.

Write down the full position title, job ID, and any requisition number

Job IDs matter more than they seem. When emailing your recruiter contact, referencing the requisition number ensures the right role is discussed, especially if the company is hiring for multiple similar positions simultaneously. If you're tracking several applications at once, the job ID prevents confusion about which role a note or follow-up belongs to.

Note the interview date, local time, time zone, meeting platform, and backup contact

Confirm the time zone explicitly — especially for remote roles where the recruiter and you are in different regions. Save the meeting link the night before and test that it opens correctly. Write down the recruiter's direct email and phone number. For video interviews, a technical failure in the first minute is not disqualifying if you contact them immediately and reconnect within two to three minutes with a brief, calm apology.

Look up each interviewer on LinkedIn and note their title, tenure, and career history

How long someone has been at the company shapes their perspective significantly. A person who joined six months ago has fresh outside-in observations about the culture; someone who has been there eight years has deep institutional knowledge but may have normalized things that would surprise a newcomer. Their previous employers suggest the frameworks they carry: a hiring manager who came from a large enterprise thinks differently about process than one who came from a five-person startup. Note anything genuinely interesting that you might reference naturally — not as a forced name-drop, but as real context for your questions.

Confirm the interview structure: number of rounds, panel vs. 1:1, and any technical or case component

If the recruiter has not specified the format, email and ask before the day. Specific questions worth asking: How long is each session? Will there be a technical screen, take-home exercise, or case study? Who will I be speaking with, and what are their roles? Preparation is proportional to format — a 30-minute recruiter screen needs 20 minutes of prep; a four-hour panel with a case component needs an evening. Showing up to what you expected to be a brief screen and finding it is a 90-minute panel with four people is an avoidable and expensive surprise.

Describe what the company does and how it makes money — written out in your own words

Write this out rather than reading it back from their website. The exercise of paraphrasing forces genuine comprehension of the business model rather than memorized taglines. Interviewers notice the difference between a candidate who says 'I know you're in fintech' and one who says 'You sell a subscription workflow tool to compliance teams at mid-market financial services companies — your revenue model seems to depend on seat-based expansion within accounts.' The latter demonstrates real understanding, and it's the basis for every specific question you'll ask about strategy.

Read the company's About, Careers, and Blog pages and note the language they use to describe themselves

The words a company chooses to describe itself — the values it emphasizes publicly, the stories it features on its careers page, the problems it says it exists to solve — reflect internal priorities and cultural signals. When you mirror that vocabulary naturally in the interview, you demonstrate cultural awareness rather than just job-fit. Avoid sounding scripted; the goal is to absorb the language well enough that it comes out organically, not to quote it back to them.

Search the company name in Google News for the past 3–6 months and note relevant recent developments

For public companies, also look at the most recent earnings call transcript or investor letter — these are unusually candid about where the business is under pressure and what it is prioritizing. For private companies, look for funding announcements, notable executive hires, product launches, and press coverage. A reference to something specific and recent — 'I saw the announcement about your expansion into the EU market; I was curious how that is changing the product localization priorities' — signals current, genuine preparation rather than five minutes on their homepage the morning of.

Identify the company's two or three main competitors and how this company differentiates

You do not need a complete competitive analysis. You need enough to speak intelligently if the topic comes up — and it often does, particularly with senior interviewers who want to see business awareness. Look at review sites (G2 or Capterra for software; industry publications otherwise), read a few competitive comparison articles, and note what customers say they choose this company for. Understanding the competitive narrative also helps you frame your own experience: if you have worked on problems adjacent to a competitor, that context is worth naming.

Write your three most specific and genuine reasons for interest in this company — not generic ones

Before the interview, ask yourself honestly: if this company's offer were 10% lower than a comparable role elsewhere, would you still prefer it? The reasons that answer yes are your real reasons. These are also the ones that will land as authentic in the room because they require specific knowledge of the company that a generic answer cannot demonstrate. 'The particular problem you're solving for independent financial advisors — I came from that industry and watched them struggle with exactly this' is the kind of answer that makes interviewers remember you the next morning.

#10

Write out your 60-second 'Tell me about yourself' answer — then practice saying it aloud three times

Structure: (1) your current or most recent role and its scale or context in one sentence, (2) one or two career highlights that directly apply to this role, (3) why you are looking and why this specific opportunity. Keep it under 90 seconds. The reason to say it aloud — not just read it — is that answers that look polished in writing often sound either memorized or choppy when spoken. The goal is confident and natural: close enough to prepared that you do not stumble, far enough from scripted that it sounds like a conversation. End with an invitation to dialogue — 'I would love to hear more about where the team is headed with X' — so it opens rather than closes.

#11

Write your authentic answer to 'Why are you interested in this role and this company?'

The worst answers reference brand recognition, vague growth opportunities, or the role's alignment with your skills — all of which you could say about any comparable role. The best answers reference something specific: a product challenge the company is uniquely positioned to solve, a particular aspect of the team structure you find compelling, something you learned in your research about the company's direction that excites you. These answers are also more useful for your own decision-making: if you cannot find a specific, genuine reason to want this role over a similar one, that is worth examining before you get an offer.

#12

Distill your career trajectory into one sentence — the through-line that explains why this role is the logical next step

Interviewers often try to construct your narrative themselves from your résumé, and they frequently get it wrong or miss the thread you see. If you give them the framing directly — 'My career has moved from individual contributor technical work toward increasingly cross-functional product leadership, and this role is the natural next expression of that' — you shape how they interpret everything else you say. Write this sentence before the interview and deploy it naturally when the opportunity arises, typically early in the first substantive conversation.

#13

Story 1: Write a significant achievement you're proud of, with quantified results

Situation: the context — the company stage, team size, or scope of the problem. Task: your specific responsibility, not the team's. Action: what you personally did — be concrete and credit the team where credit is due, but your interviewer is evaluating you. Result: what changed, expressed in numbers where possible (revenue impact, time saved, error rate reduced, team growth). If you do not have a clean number, use a relative comparison: 'the fastest onboarding the team had seen' or 'reduced from three weeks to four days.' Practice the answer aloud — written STAR stories often sound like bullet-point recitations when spoken unpracticed.

#14

Story 2: Write a challenge, setback, or failure — what happened, what you learned, and what changed

This question is primarily an assessment of self-awareness and intellectual honesty, not a catalog of your worst moments. Interviewers are specifically listening for: do you take ownership without excessive self-criticism, do you demonstrate genuine and specific learning (not just 'I learned to communicate better'), and is there evidence of changed behavior? A real failure with honest reflection outperforms a 'challenge that turned out fine' story every time. Choose something where the stakes were real, your role was meaningful, and the lesson was specific enough to be credible.

#15

Story 3: Write a time you worked effectively in a difficult collaboration or navigated a team conflict

Difficult collaborations are among the most common interview topics because interpersonal friction at work is universal, and how someone handles it reveals a great deal about maturity and EQ. Strong stories: a disagreement with a colleague where you eventually reached alignment (describe how), a cross-functional project where goals were misaligned (describe how you bridged them), or a situation where you had to deliver critical feedback to a peer. The key is to describe your specific actions — not 'we figured it out' but 'I initiated a direct conversation where I acknowledged their concern first, then proposed a reframe that addressed both our constraints.'

#16

Story 4: Write a time you led something, influenced without authority, or drove a project forward

This applies even if you have never had direct reports. Spearheading a process improvement that required convincing reluctant colleagues, championing a new approach when the team's default was to do things the familiar way, taking ownership of a problem that had fallen through organizational cracks — these all demonstrate leadership in the sense interviewers mean it. The distinguishing feature of strong answers: describe specifically how you motivated or aligned others, not just what you decided to do.

#17

Story 5: Write a time you adapted to significant change, ambiguity, or shifting requirements

This story has become increasingly common because companies explicitly cite adaptability as a top hiring criterion, particularly in fast-growing environments. Strong examples: a project where the scope changed mid-execution and you had to reprioritize without losing momentum, an organizational restructuring that changed your reporting or mandate, or a market shift that required rethinking assumptions you had built work around. The interviewer is evaluating composure under uncertainty — the answer should show how you assessed the new situation clearly before acting, not just that you survived the change.

#18

Map the job description's key requirements to a prepared story for each major competency

Go through the job description systematically and highlight every requirement that implies a type of experience: 'proven ability to manage cross-functional projects,' 'experience with enterprise client relationships,' 'track record in high-growth environments.' For each major requirement, identify which of your five STAR stories covers it — or prepare a new one. Interviewers design their behavioral questions directly from the job description. This exercise means you are preparing specifically for the questions most likely to be asked, not just rehearsing answers to generic prompts.

#19

Ask what success looks like in this role in the first 90 days and in the first year

This is consistently one of the highest-value questions in any interview. The answer tells you the actual gap they are trying to fill — which may differ from what the job description emphasizes — reveals whether the company has clear expectations or is still figuring them out, and gives you an opportunity to directly address any gap between their expectations and your background while you are still in the room. It also demonstrates that you are thinking about delivering results, not just receiving an offer.

#20

Ask about the biggest challenge the team has faced recently and how it was approached

This question yields real information about the working environment that no careers page will show you. Follow up if the answer is vague: 'What made that particularly difficult?' A team that describes their challenges honestly and with specificity usually handles problems well. A team that gives an evasive or entirely positive answer — 'Oh, we have just been growing so fast' — may be glossing over something worth investigating before you accept an offer. The quality of the answer is itself data about the culture.

#21

Prepare one question specific to this interviewer's background or experience at the company

Based on your LinkedIn research, identify something genuinely interesting about this person's history that connects to the role or company — not flattery, actual curiosity. Examples: 'You came from a much larger organization — how has the pace here compared?' or 'You have been here through what looks like a significant inflection point — what has changed most about how the team operates?' These questions produce candid, personal answers, because they require the person to reflect rather than recite prepared company messaging.

#22

Ask how people typically grow from this role and what career paths you have seen

This signals that you think about development and trajectory, not just the immediate job. It also gives you real data about the company's actual track record of promoting internally versus filling senior roles from outside. A company that can name specific people who grew from this type of role is one that has demonstrably done it. 'Our best performers have typically moved into product leadership or general management' is a more useful answer than 'we have lots of growth opportunities here.'

#23

Before the interview ends, ask: 'Is there anything about my background that gives you any hesitation?'

This question feels uncomfortable to ask, which is exactly why it matters. It gives the interviewer explicit permission to voice a concern — about a gap in experience, an unusual career move, a qualification they are uncertain about — that might otherwise remain unspoken and become a silent reason not to proceed. A concern you can address in the room is one you can potentially resolve. A concern that leaves with the interviewer without your input becomes something the hiring committee discusses without you there to address it.

#24

Confirm the next steps and expected timeline before the interview ends

Specifically: when should you expect to hear back, from whom, and via what method? Having a concrete timeline lets you calibrate your follow-up appropriately — if they said 'end of next week' and Friday passes quietly, a brief professional email is appropriate and expected. If you do not ask, you may follow up too early (signaling impatience) or wait too long (signaling fading interest). Either misstep is avoidable with one direct question before you leave.

#25

For video interviews: run a full tech check at least 30 minutes before — camera position, audio, lighting, background, and internet connection

Camera: position it at eye level by stacking books under your laptop if needed — the default laptop-on-desk angle creates an unflattering upward view and makes you appear to be looking down throughout the interview. Audio: test with headphones or a dedicated microphone rather than laptop speakers, which introduce echo and background noise. Lighting: a window or lamp positioned in front of you (not behind you) makes a meaningful difference to how you appear on screen. Background: a clean, uncluttered wall or bookshelf reads as professional; a virtual background often looks artificial and flickers with movement. Internet: if your WiFi is unreliable, connect via ethernet cable for the call. Close all browser tabs and applications that might generate notification sounds.

#26

Print two copies of your résumé, and bring portfolio or work samples if relevant to the role

One printed copy is your reference; one is available for the interviewer in case they do not have it pulled up. For design, writing, data, or product roles: bring a printed or pre-loaded portfolio on your device — but ask before opening your laptop: 'Would it be useful to walk through a few examples directly?' This demonstrates initiative and makes the interview more concrete than description alone. For phone or video interviews, have your résumé open on a second screen or printed beside you — reference it naturally if needed, but do not read from it audibly.

#27

Arrive 10 minutes early in person or log in 5 minutes early for video — and use that window actively

For in-person: arrive at the building 10 to 15 minutes before and spend five of those minutes in a nearby lobby or café reviewing your prepared questions and career trajectory sentence. Arriving directly to reception a full 15 minutes early creates administrative awkwardness — 10 minutes is the right amount. For video: log in five minutes before the scheduled time, use the waiting room to review your questions one final time, and close everything on your screen except the video platform. Reviewing your notes in the five minutes immediately before the interview materially improves recall during the conversation — treat it as a deliberate warmup, not idle waiting.

#28

Write down key topics discussed, moments that went well, and anything to address in follow-up — within 30 minutes

Memory degrades quickly after high-stakes events. The specific examples you used, the concerns the interviewer raised, the topics that generated genuine energy or visible engagement in the conversation — these details blur within a few hours and become nearly inaccessible by the following day. Your notes from the first round become your preparation material for the second round, and a specific thank-you email depends on having accurate references to the conversation you just finished.

#29

Send a personalized thank-you email to each interviewer within 24 hours, with a specific reference to your conversation

Write a separate email to each interviewer referencing something different — not the same note sent to multiple people. The reference should come from the conversation itself: a topic you discussed in depth, a challenge they described, a follow-up thought you had after leaving. The email demonstrates that you were genuinely engaged, extends the positive impression from the interview, and gives you one more touchpoint before the hiring decision. Keep it to three to five sentences. A note that arrives more than 36 hours after the interview loses its impact significantly.

#30

Record the expected next-steps date and set a calendar reminder for one business day after it

Once you have a timeline from the interview (covered in the Questions section), add a reminder for one business day after that date. If that date passes without contact, a brief three-sentence email — you are following up on your conversation from a specific date, you remain genuinely interested, and you are happy to provide any additional information — is professional and fully expected. Waiting silently for two weeks past the stated timeline does not signal patience; it signals that the role may have stopped being a priority for you, which is rarely the impression you want to leave.

#31

🔍 What interviewers are actually scoring — before you answer the first question

Every interviewer maintains a running mental scorecard that starts before the formal interview begins. How you greet the receptionist, whether you log in early or scramble in late, how you handle the first thirty seconds of small talk — all of this shapes a first impression that researchers call cognitively sticky. Studies on interview decision-making consistently show that evaluators form an initial impression within the first 90 seconds and then spend much of the remaining conversation confirming or defending it, rather than genuinely re-evaluating. Knowing this is not an invitation to perform — it is a reason to be genuinely ready from the moment you arrive or connect, not from the moment the first formal question is asked.

✅ Signals that read as high competence

Specific, research-backed questions referencing recent company news or announcements
A natural pause before answering — reads as thoughtfulness, not hesitation
A follow-up question that builds directly on something the interviewer just said
Referencing the interviewer's own background or experience in a genuine question

⚠️ Patterns that quietly cost candidates

Interrupting the interviewer mid-sentence, even with enthusiasm
Ending answers without checking whether you actually answered the question asked
Speaking negatively about a previous employer, even briefly and even if warranted
Asking questions whose answers appear prominently on the company website

📋 What the interviewer's job changes at each stage of the process

Most candidates prepare the same way for every round. But the evaluation criteria shift meaningfully at each stage, and calibrating your preparation to the specific round gives you a structural advantage that few candidates use.

Phone screen or recruiter call

The recruiter is screening for baseline fit: are you qualified, are you realistic about compensation, and can you articulate your background clearly? Your goal here is clarity and genuine enthusiasm, not depth. Have your résumé in front of you, keep answers to 60–90 seconds maximum, and ask one well-informed question about the role or team that demonstrates you read the job description carefully.

First round with the hiring manager

This is where your narrative is evaluated most critically. The hiring manager wants to understand who you are professionally, why you are a plausible fit for this specific role, and whether they would enjoy working with you day to day. Your career through-line, your behavioral stories, and your questions about the role and team all carry their greatest weight in this conversation.

Panel or cross-functional interviews

Each panelist represents a stakeholder group you would work with. The engineer is assessing whether you understand technical constraints and tradeoffs. The designer is checking whether you respect craft and process. The sales lead wants to know whether you understand the customer and commercial reality. Adapt your language to each person's frame of reference — technical vocabulary with engineers, customer-outcome language with commercial stakeholders, and process language with operations. This is not inconsistency; it is communication intelligence.

Final round

By this stage, the committee generally believes you can do the job. The remaining question is usually fit: will this person thrive here, will they grow, and will they represent the team well both internally and externally? This is also the appropriate time for salary discussions to begin if the company has not already initiated them — earlier rounds are rarely the right context.

💡 Three ways to recover when your mind goes blank mid-answer

It happens in nearly every high-stakes interview — a question lands and the mental filing cabinet comes up empty. The worst response is to start talking before you have a real answer, which produces fragmented, repetitive sentences that visibly erode the impression you have built. These three techniques work:

Buy legitimate time. "That's a really interesting framing — let me think for a moment about the best example." Interviewers respect a candidate who pauses to think far more than one who rushes to fill silence. Five seconds of quiet is fine. Ten seconds is fine. The pause itself signals that you are taking the question seriously.

Acknowledge and redirect honestly. "I don't have a perfect example of exactly that situation — the closest thing I've encountered was..." followed by your best adjacent story. Partial honesty combined with a relevant example reads far better than a visibly forced or invented story. Most interviewers will appreciate the candor.

Pivot to a thoughtful hypothetical. For experience you genuinely do not yet have: "I haven't managed a team through that specific situation, but based on how I approached [a related challenge], my instinct would be to..." This only works if what follows is substantive and specific, not generic. A candid acknowledgment of a gap paired with genuinely thoughtful reasoning is a strong answer.

📖 The question that changed the final interview

Priya was in the final round for a senior engineering role. Near the end of her conversation with the VP of Engineering, she asked: "What's something about working here that surprised you most — something you couldn't have known from the outside?" The VP paused, then gave a candid, specific answer about the company's genuine appetite for technical risk and how much autonomy individual engineers held over architecture decisions. It opened a 15-minute conversation that the VP later described to the recruiting team as the most substantive final interview he'd conducted in two years. The question worked not because it was clever, but because it invited honesty — and honesty is what you need to make a real decision about whether to accept an offer.

🧮 Rate the company while they rate you

After each interview round, score these on 1–5 and track the total:

__ / 5Did the interviewers seem energized by the work itself?
__ / 5Were my questions answered directly, or deflected?
__ / 5Does the actual role scope match what was described?
__ / 5Would I respect and genuinely learn from these people?
__ / 5Did the culture feel like an environment where I'd do good work?

A total below 15 out of 25, consistently across rounds, is worth examining carefully before accepting an offer — regardless of compensation.

🔧 The video interview works against you — here's what closes the gap

Video interviews systematically disadvantage candidates compared to in-person conversations. Natural rapport-building cues — shared physical space, eye contact, room energy — are compressed or absent. Research also shows that interviewers experience more cognitive fatigue on video calls, which means they form their impressions from shorter and narrower windows of information. Two specific adjustments that help significantly:

Look at the camera lens, not the interviewer's face

When you watch the interviewer's face on your screen, your eyes appear to the interviewer as looking slightly downward — at their chest or hands. Looking directly at your camera lens creates the illusion of sustained direct eye contact from their perspective. It feels deeply unnatural to do, and that is exactly why most candidates never make the adjustment. Five minutes of practice before the call makes it second nature.

Speak at roughly 85% of your normal pace

Audio compression on video platforms adds a slight perceptual delay and makes rapid speech noticeably harder to process. Candidates who speak at their natural in-person pace often come across as rushed, dense, or difficult to follow on video. A deliberate 10–15% slowdown improves perceived clarity and authority — and it gives you more space to think between sentences, which itself reads as confidence rather than hesitation.

Master This Checklist Quickly

Every important button and option for this pre-made checklist, shown in a glance-friendly format.

Start Here

1
Click any item row to mark it complete.
2
Use the note row under each item for quick notes.
3
Use the tool row for undo, redo, reset, and check all.
4
Use Save Progress when you want to continue later.

Checklist Row Tools

UndoRedoResetCheck allCollapse/Expand sectionsShow/Hide detailsInline notes

Top Action Buttons

Open all sharing and export options in one menu.

Email DraftContinue on another devicePrint or Save as PDFPlain Text (.txt)Word (.docx)Excel (.xlsx)

Add & Ask

Open one menu for apps and AI guidance.

NotionTodoist CSVChatGPTClaude

Copy and customize

Create a new editable checklist pre-filled with your chosen content.

Save Progress

Adds this checklist to My Checklists and keeps your progress in this browser.

Most Natural Usage

Track over time

Check items -> Add notes where needed -> Save Progress

Send or export

Open Share -> Choose format -> Continue

Make your own version

Copy and customize -> Open create page -> Edit freely