Funny how we spend years learning to code, but no one really teaches us how to handle an interview. I've had a lot of people reach out for advice recently, from juniors to experienced engineers, and the pattern is always the same: they're worried about being put on the spot.
The fear of getting hit with a trick question or not knowing an answer is real. But having been on both sides of the table, as an interviewee and as the one doing the hiring for my company, Blueblood, I've learned that a successful interview isn't about having a perfect score.
It's a structured conversation, and you can be the one to guide it. I've put together my playbook for how to prepare, stay in control, and actually nail it.
The Game Plan
Do Your Homework (No, Really)
Prepare Your "Cheat Sheet"
Talk About the Money
It's Your Conversation
Step 1: Do Your Homework (No, Really)
The single biggest mistake developers make is shotgun-blasting applications and then scrambling to figure out what a company does five minutes before the call (if at all). The goal of research is to determine if you are genuinely excited about the opportunity and to distinguish yourself from the hundreds of other applicants.
Your research should start the moment you decide to apply. Here's your checklist:
1. The Official Website (The Source of Truth): This is your first stop.
- Values/Mission Page: Do their values resonate with you?
- Products Page: What are they building? Do you find it interesting?
- Blog/News Section: What are their recent announcements or technical challenges?
2. LinkedIn & Glassdoor (The Unfiltered View):
- Company Profiles: Get a feel for their size, recent posts, and company culture.
- Reviews & Salary Data: Read employee reviews and check for self-reported salary ranges for similar roles.
3. The Final Google Search (The Catch-All):
- Search for news articles, press releases, or any other public information that might have slipped through the cracks.
The outcome of this phase should be a simple document of raw notes. This document is your material for the next step.
Step 2: Prepare Your "Cheat Sheet"
Your research document is a messy brain dump of raw information. You don't want to be frantically scrolling through that during the call. The goal of this step is to condense that research into a clean, one-page "cheat sheet" that you can glance at to keep you focused and confident.
This shouldn't be treated as a script. It's a set of talking points organized into a few essential sections.
1. Your Tailored Introduction (The 30-Second Pitch)
The first question is often "Tell me about yourself." This isn't an invitation to read your resume out loud. They already have it. It's your chance to deliver a concise, powerful pitch that proves you're the right person for this specific job.
A good way to structure it is in 3-4 sentences:
- Who you are: "I'm a fullstack engineer specializing in..."
- Technical Alignment: "...with experience in React and TypeScript, which I saw was a key requirement for this role."
- Value Alignment: "...I was really drawn to your company's mission to [mention something from your research], and I'm looking for a role where I can build products that have a real impact."
2. "Why I'm a Good Fit" (Your Talking Points)
Here's a helpful way to organize your thoughts. Try a simple two-column list. On the left, list the top 3-4 requirements from the job description. On the right, map one of your projects or skills directly to that requirement.
| Company Needs | My Experience |
|---|---|
| Experience with React | Built a full admin dashboard with React, TypeScript, and Zustand. |
| AI/ML Interest | Developed a multi-tenant AI chatbot on the Cloudflare stack. |
| Cares about UX/Design | My portfolio and projects use a clean, modern design system (shadcn/ui). |
This helps you have specific, evidence-backed answers ready when they ask about your skills.
3. Salary & Logistics (The Practicalities)
It's always a good idea to have your numbers ready. It shows you're a professional who knows their worth:
-
Their Range:
£60,000 - £100,000(from your research) -
My Desired Range:
£80,000 - £90,000 -
My Walk-Away Number:
£75,000 - Question for them: "What is the envisioned salary range for this position?"
Remember, this is a normal part of the process. It's not greedy to talk about money; it's why you're there.
4. "My Questions for Them" (Show Your Interest)
Always have questions prepared. It shows you're engaged and genuinely interested, and it's your best chance to find out if the company is the right fit for you.
Here are a few good starting points and what they help you achieve:
-
"What are the biggest technical challenges the team is currently facing?"
- Why you're asking this: It shows you're a problem-solver, not a ticket-closer. You're already thinking about how you can provide value.
- What it helps you learn: It gives you a real preview of the job's day-to-day challenges and helps you decide if they're problems you'd be excited to work on.
-
"Could you tell me more about the day-to-day responsibilities of this role?"
- Why you're asking this: This signals that you're thinking practically about how you would fit into the team and its workflow.
- What it helps you learn: It cuts through the job description jargon. You'll find out if the job is mostly new features, bug fixes, or maintenance, and what the team's agile process is really like.
-
"What does the typical onboarding process look like for a new engineer?"
- Why you're asking this: This is a very smart question for a junior. It shows you're serious about getting up to speed and contributing effectively.
- What it helps you learn: The answer reveals how much a company invests in its new hires. A good answer will mention mentorship, documentation, and a structured plan for your first few weeks. A vague answer can be a red flag.
With a one-page cheat sheet like this, you'll walk into the interview feeling prepared, confident, and ready to guide the conversation.
Step 3: Talk About the Money
Sooner or later, the salary question will come up. Don't treat it like a taboo. This is a professional conversation about your livelihood, and companies expect it. Getting shy or closed off shows a lack of confidence.
Your research from Step 1 is your anchor here. Here’s how to handle it:
If the job post included a range: A great response is, "The range you posted aligns with my research and my expectations for the role."
If the post did not include a range: The best move is to let them provide the first number. You can ask confidently and politely: "I'm still learning about the full scope of the role, so I'd be interested to hear what the envisioned salary range for this position is."
If you must give a number first: Don't give a single number. Based on your research of similar roles, provide a confident range. For example: "Based on my research for similar roles in this market, I'm targeting a range of $X to $Y."
Remember, this is an initial check to make sure you're in the same ballpark. As long as your number is reasonable and based on research, it won't disqualify you. The final offer comes later.
Final Thoughts: It's Your Conversation
At the end of the day, remember this: an interview isn't a test you pass or fail. It's a two-way conversation to determine if there is a mutual fit. They are evaluating you, but you are also evaluating them.
This playbook isn't a script to memorize; it's about giving you the structure to walk in prepared and confident. Don't just hope you know the right answers. Be ready to show your value and to lead the conversation.
Be curious, be confident, and be yourself. The right opportunity will recognize your value. Good luck!
Top comments (0)