How to Prepare for a Job Interview: A Complete Guide

Why Preparation Is the Biggest Variable in Interview Performance

Interviews feel high-stakes and unpredictable, but they are far more predictable than most people realise. The same questions come up repeatedly. The same patterns of success appear across industries. The candidates who perform best are almost always the ones who prepared most systematically — not necessarily the most naturally talented or experienced.

Research by Stanford psychologist Carol Dweck shows that people who attribute performance to preparation rather than innate ability consistently perform better in high-pressure situations. Treating an interview as something you practice and prepare for — rather than something you either "have" or do not — is itself a performance advantage.

Step 1: Research the Company Thoroughly (48–72 Hours Before)

Superficial company knowledge is easy to detect and immediately signals low interest. Deep research sets you apart and enables much more specific, compelling answers.

What to research:

• Business model: How does the company make money? Who are its customers? What is its competitive position?
• Recent news: Product launches, fundraising, acquisitions, leadership changes, press coverage in the past 6–12 months.
• The team: LinkedIn profiles of your interviewers. Look at their background, tenure, and what they post about.
• The product: If possible, use it. Sign up for a trial, read user reviews on G2 or Trustpilot, explore the documentation.
• The company's stated values and strategy: Annual reports, investor presentations, the CEO's interviews or written pieces, the company blog.
• The role itself: Re-read the job description carefully and map every requirement to something specific in your experience.

Step 2: Prepare Your Stories Using the STAR Method

Most interview questions — even ones that seem hypothetical — are best answered with a specific example from your experience. The STAR method gives you a reliable structure for telling these stories concisely and compellingly.

• Situation: Set the context briefly. What was happening? What was the environment?
• Task: What was your specific responsibility? What were you trying to achieve?
• Action: What did you specifically do? Focus on your individual contribution, not "we."
• Result: What was the outcome? Quantify it wherever possible (%, £, time saved, users impacted).

Prepare 8–10 STAR stories from your recent experience that cover a range of themes: a challenge you overcame, a time you led something, a time you failed and what you learned, a time you worked cross-functionally, a time you had a conflict and resolved it, and your biggest professional achievement. These stories can be adapted to answer almost any behavioural question.

Step 3: Prepare for the Most Common Interview Questions

"Tell me about yourself"

This is not an invitation for your life story. Prepare a 90-second professional narrative that covers your background, your most relevant recent experience, and why you are interested in this specific role. End with what you are looking for next and why this company fits.

"Why do you want to work here?"

Generic answers ("great culture," "exciting company") fall flat. Reference something specific: a product decision you admire, a strategic direction they are pursuing, a piece of content a leader published, or a problem they are solving that you care about.

"What is your greatest weakness?"

Avoid fake weaknesses ("I work too hard"). Choose a genuine development area, explain what you have done to address it, and show progress. Interviewers are assessing self-awareness and growth mindset — not whether you are perfect.

Example: "I used to struggle with delegating — I would hold on to tasks longer than I should because it felt faster to do them myself. Over the past year, I deliberately started by delegating smaller tasks, building trust incrementally, and then moved to delegating entire project phases. My team's output has improved, and I have more time for the strategic work I should be focused on."

"Where do you see yourself in 5 years?"

You do not need a precise plan. You do need to show ambition, alignment with the role's growth path, and commitment to this type of work rather than signalling you see it as a stepping stone.

"Why are you leaving your current role?"

Always frame this positively — toward something rather than away from something. Never criticise your current employer. Focus on what you are seeking: more scope, a different industry, technical growth, or alignment with your values.

Salary questions

Know your target range before the interview. Research market rates on LinkedIn Salary, Glassdoor, and Levels.fyi (for tech). When asked, provide a range with your target at the lower end of what you would be happy with. If pressed early, it is acceptable to say: "I would prefer to discuss compensation once we have both confirmed this is a strong mutual fit."

Step 4: Prepare Questions to Ask the Interviewer

Asking strong questions is not just polite — it signals strategic thinking and genuine interest. Prepare 5–7 questions so you have plenty after some are answered during the interview.

Strong question categories:

• Role-specific: "What does success look like in the first 90 days for this role?" / "What are the biggest challenges the team is currently working through?"
• Team dynamics: "How does this team make decisions?" / "How does collaboration typically work between this team and Product / Engineering / Sales?"
• Company strategy: "Where do you see the product evolving over the next 12–18 months?" / "What does the competitive landscape look like from inside the company?"
• Interviewer-specific: "What has kept you at this company?" / "What do you wish you had known before joining?"
• Process: "What does the rest of the interview process look like from here?"

Avoid questions about salary, benefits, or time off in early-stage interviews. These can signal that you are more interested in the package than the role.

Step 5: Logistics and Practical Preparation

For in-person interviews

• Confirm the exact location and do a dry run if possible to check timing
• Arrive 10 minutes early — no earlier, as it creates awkwardness for the reception team
• Bring printed copies of your resume (2–3), a notepad, and a pen
• Dress one level above the company's typical standard — when in doubt, err formal

For video interviews

• Test your camera, microphone, and internet connection the day before
• Use a neutral background or a professional virtual background — avoid busy or distracting spaces
• Look at the camera, not the screen, when speaking — this is the equivalent of eye contact
• Close all notifications and unnecessary browser tabs
• Have water and your notes visible but off-screen

Technical Interview Preparation (Engineering Roles)

Technical interviews for engineering roles typically span several areas. Prepare for each separately:

• Coding challenges (LeetCode-style): Practice on LeetCode, HackerRank, or Codewars. Focus on the most common patterns: arrays and strings, hashmaps, two pointers, sliding window, trees and graphs, dynamic programming. Aim to solve easy problems in under 10 minutes and medium problems in under 25 minutes. Verbalise your thought process — interviewers evaluate reasoning as much as the final solution.
• Language-specific questions: Know the internals of your primary language — garbage collection, concurrency model, memory management, standard library idioms. These are standard for any role where the JD names a specific language.
• Framework and tooling questions: If the role requires React, Kubernetes, Django, or any specific technology, prepare for questions about its architecture, lifecycle, and common failure modes. Reading the official documentation once before the interview is usually sufficient to answer 80% of these questions.
• Debugging exercises: Some interviews present buggy code and ask you to find the issue. Practice code reading — walk through unfamiliar code explaining what each part does before trying to find the bug.

System Design Interviews

System design interviews are common for mid-to-senior engineering roles. You will be given an open-ended problem ("design a URL shortener" or "design Twitter's feed") and evaluated on your ability to think through trade-offs, ask the right clarifying questions, and produce a scalable architecture.

The framework for system design interviews:

1. Clarify requirements before designing. Ask about scale (how many users? read/write ratio?), consistency requirements, latency targets, and budget constraints. This demonstrates structured thinking and prevents wasted time designing the wrong thing.
2. Start with a simple design, then scale it. Begin with the simplest architecture that satisfies the requirements. Then identify bottlenecks and propose solutions. Starting with a complex distributed system before establishing the simple baseline is a red flag for interviewers.
3. Think out loud. System design interviews evaluate your reasoning process. Narrate your decisions: "I'm using a relational database here because the data is highly structured, but I'd consider switching to a document store if the schema becomes more variable."
4. Know the common components. Be comfortable discussing: load balancers, CDNs, caches (Redis, Memcached), message queues (Kafka, SQS), databases (SQL vs. NoSQL, sharding, replication), and API design (REST vs. GraphQL vs. gRPC).

Step 6: After the Interview — Following Up

Send a thank-you email within 24 hours of each interview. Keep it brief — 3–4 sentences. Reference something specific from the conversation, reiterate your interest, and confirm your availability for next steps.

Example:

Hi Sarah — thank you for your time today. The conversation about how the team approaches quarterly planning gave me a much clearer picture of the role, and it reinforced my enthusiasm for the position. I look forward to hearing about next steps. Please let me know if there is anything else I can share.

If you do not hear back within the timeline they gave you, a single polite follow-up email is appropriate. After two follow-ups with no response, move on.

Salary Negotiation: The Complete Playbook

Most candidates undervalue themselves in salary negotiations because they accept the first number offered. The research is clear: negotiating respectfully and professionally rarely costs you the offer, and frequently improves the package.

• Research before the interview. Use LinkedIn Salary, Glassdoor, Levels.fyi (tech), Payscale, and conversations with peers to understand the market rate for this role in this location and at this company size. Know your floor (the lowest you would accept) and your anchor (the number you will name first).
• Let them make the first offer when possible. If they ask for your expectations early, it is reasonable to say: "I would like to hear your range for this role first to make sure we are aligned." This is not evasion — it is legitimate negotiation practice.
• Counter above your target. If they offer £80K and your target is £85K, counter at £88–90K. You are very unlikely to get exactly your counter number — you will meet somewhere in the middle.
• Negotiate the full package. If base salary is fixed, negotiate on signing bonus, stock grants, annual review timing, remote work flexibility, professional development budget, or extra annual leave. Companies often have more flexibility on these dimensions than on base pay.
• Never accept on the spot for a verbal offer. It is always acceptable to say: "Thank you so much — I would like to take 24–48 hours to review the full offer before responding. Can I get back to you by [specific date]?"

What to Do After a Rejection

Rejections are a standard part of the job search process, even for highly qualified candidates. How you handle them determines how quickly you recover and improve.

• Ask for feedback. Reply to the rejection email within 24 hours: "Thank you for letting me know. I really valued the conversations. If it would be possible to share any feedback on where I could improve, I would genuinely appreciate it." Many recruiters will not respond, but some will — and the feedback can be invaluable.
• Review what you can improve. If you reached the final round but did not get an offer, the issue is likely in your interview technique rather than your resume or ATS score. Record yourself answering mock questions and watch it back. The gap between how you think you sound and how you actually sound is often significant.
• Keep the relationship open. A rejection today does not mean rejection forever. A company that nearly hired you is more likely to hire you when a new role opens than a stranger who applies cold. Connect with your interviewers on LinkedIn with a brief, gracious message.
• Do not take it personally. Most rejections are not about you being unqualified — they are about fit, timing, internal candidates, or budget changes that have nothing to do with your ability. The candidate who got the role was not necessarily better than you; they were the right fit for this specific role at this specific moment.

How to Handle Nerves

Some anxiety before an interview is normal and even helpful — it sharpens focus. But excessive nerves impair performance. Several evidence-based strategies help:

• Reframe anxiety as excitement: The physiological state is identical. Telling yourself "I am excited" rather than "I am nervous" measurably improves performance in high-stakes situations, according to research by Alison Wood Brooks at Harvard Business School.
• Prepare more, not less: Most interview anxiety comes from fear of being caught unprepared. The more thoroughly you have prepared your stories and researched the company, the less there is to fear.
• Practice out loud: Reading answers in your head is not the same as saying them. Practice your STAR stories and your "tell me about yourself" answer out loud until they feel natural.
• Pause before answering: It is completely acceptable to take 2–3 seconds before answering a question. Silence does not signal confusion — it signals thoughtfulness.

Frequently Asked Questions

How many days before an interview should I start preparing?

Ideally 3–5 days for a first-round interview, 5–7 days for final rounds. Research, STAR story preparation, and question preparation each take a few hours. Leaving it to the night before means you are memorising rather than internalising — which shows.

Should I memorise my answers?

Memorise the structure and key points of your STAR stories — not the exact words. Memorised answers sound scripted, which undermines trust. Know your stories cold so you can tell them naturally and adapt them to different question framings.

What if I do not know the answer to a technical question?

Say so honestly and explain how you would find out: "I haven't worked with X specifically, but the approach I would take is..." or "That's outside my direct experience — what I can tell you is how I've solved related problems." Honesty paired with problem-solving orientation is far better than an incorrect confident answer.

Is it normal to have multiple rounds?

Yes, increasingly so. Enterprise companies and fast-growing startups commonly run 4–6 interview rounds: recruiter screen → hiring manager → technical assessment → panel → values/culture interview → sometimes a final executive call. Ask early in the process what the full interview loop looks like so you can plan your preparation accordingly.