Setting your direction
What you’ll learn:
- Define what you want from your next role
- Separate genuine priorities from nice-to-haves
- Connect your strengths to the right company stage
- Build a clear story around your next move
Seven modules walking you through every stage of the technical interview process, practical knowledge built from thousands of hours of real candidate coaching.
Start learning
From understanding the process to meeting the founder, a complete guide to engineering interviews.
A strong interview starts before the first conversation. Get clear on the work you want to do, the environment where you thrive and what your next move needs to give you.
Think about the projects that gave you energy. Was it solving an unfamiliar problem, shipping quickly or improving a complex system? Use those patterns to describe the work you want more of, rather than starting with a job title.
Write down what matters to you: ownership, mentorship, flexibility, compensation or impact. Decide which are essential and which you can trade. A short, honest list makes it easier to compare opportunities.
An early-stage team may offer breadth and ambiguity; a larger organisation may provide deeper specialisation and established support. Neither is inherently better. Ask where your strengths and learning goals fit today.
Explain what you have learned so far, what you want to build next and why this opportunity connects the two. Keep the story specific and grounded in real experience.
Most engineers read job specs at face value, but they're rarely written by the people who'll actually interview you. This module helps you understand what companies are really looking for at different stages, so you can make better decisions about where to apply and what to expect.
Most engineers read job specs at face value, but they're rarely written by the people who'll actually interview you. This module helps you understand what companies are really looking for at different stages, so you can make better decisions about where to apply and what to expect.
A Google interview and a Series A startup interview look fundamentally different. Big tech tends to focus on algorithmic thinking and operating at scale. Startups care more about velocity, ownership, and breadth. Product companies often prioritise user empathy. Understanding these differences helps you know what to expect and where your strengths align best.
Going beyond the ‘About Us’ page makes a real difference. A useful approach: check Crunchbase for funding history, read the founders' blog posts, look at their tech blog and open-source contributions, and understand their competitive landscape. Even 30 minutes of focused research gives you a much clearer picture of what a company actually does and whether it's a good fit.
Interview processes have their own rhythm. Understanding typical timelines, knowing when to ask about next steps, and being aware of how multiple processes can run in parallel gives you a clearer picture of what's happening behind the scenes. It also helps you make better decisions about your own time.
Your experience is more than a list of technologies. Show how you think, the decisions you made and the difference your work created.
Prepare a few projects that show different strengths: delivery, collaboration, problem solving and learning. For each, note the problem, the constraints, your contribution and the outcome.
Describe what the team achieved and which decisions you personally owned. Be precise about your scope without taking credit for someone else's work.
A strong example shows why you chose an approach, which alternatives you considered and what you would change now. The reasoning is often more valuable than the technology itself.
Start with a concise version of the story. Let the interviewer choose where to go deeper rather than delivering every detail at once.
Technical interviews are a conversation about how you solve problems. Build a calm, repeatable approach that makes your reasoning visible.
Restate the task and ask about inputs, constraints and expected behaviour. A few careful questions can prevent you from solving the wrong problem.
Outline a straightforward solution before optimising. Explain its limitations, then improve it where the problem actually requires it.
Share your reasoning, not every passing thought. If you are uncertain, explain what you know and how you would test the next idea.
Walk through a typical example, a boundary case and an invalid input. Explain the time and space trade-offs and identify what you would improve with more time.
Good system design is about choosing sensible trade-offs, not drawing the most complicated architecture. Start with the user need and build from there.
Agree on the main user journeys, traffic expectations and essential quality requirements. Make assumptions explicit so the interviewer can help you refine them.
Show the main services, data flow and storage choices. Explain how a request travels through the system before exploring individual parts in depth.
Consider what happens when a dependency is slow or unavailable. Talk through monitoring, retries, recovery and the operational cost of your choices.
When a requirement changes, explain which part of the design needs to change and why. Avoid adding complexity without a clear benefit.
Interviews are a two-way decision. Use conversations with future colleagues to understand how the team works and whether you can do your best work there.
Instead of asking whether the team collaborates well, ask how a recent cross-team project worked. Specific stories reveal more than broad statements.
Ask how engineers receive feedback and how decisions are challenged. Understand what support looks like when someone is learning or a project is struggling.
Use real examples to explain your communication style and how you handle disagreement. Be honest about what helps you perform well.
Write down what you heard while it is fresh. Separate evidence from impressions and follow up on anything important that remains unclear.
The final stage brings the bigger picture into focus. Understand the company's direction, the expectations of your role and the full offer before deciding.
Ask what the company needs to prove next and where the biggest challenges sit. Connect those priorities to the work you would own.
Discuss the first few months, the support available and how your contribution will be evaluated. Clear expectations help both sides make a better decision.
Consider salary, benefits, working arrangements and equity terms together. Ask for unclear terms in writing; equity carries risk and should not be treated as guaranteed compensation.
Return to your priorities and the evidence you collected throughout the process. Ask any final questions, agree on a realistic decision date and communicate your choice clearly.
Put your prep into practice.
Join our engineering community events to network, discuss and learn from
others going through the same process.