We live in a world that sees most things through a win/lose lens. If you don’t “win” the interview, then you must have lost. That’s the common belief.
But after years of interviewing, mentoring, and being interviewed myself, I’ve realised this thinking is completely wrong. Interviews aren’t win/lose. They’re about alignment.
If you don’t get the job, you’re not losing in the long term - you’ve avoided a mismatch. And if a company doesn’t hire you, they’re not losing either - they’ve avoided bringing in someone who doesn’t fully align with their goals.
The best way to frame it is Covey’s principle: win/win or no deal.
Think about it: what happens if you somehow “win” the job but there’s no real alignment?
In short, misalignment is a lose/lose disguised as a win.
Because we’ve been taught the win/lose model, many candidates approach interviews thinking: “My job is to impress the interviewer at all costs.”
But that’s backwards. The real goal is to find out whether there’s alignment between you and the company.
If the answer is no, then walking away is the right outcome. It’s not a loss. It’s clarity.
Early in my career, I joined a company because I “won” the interview. The offer was there, and I was proud of it. But within months, I realised their engineering culture was the opposite of mine. They moved slow and didn’t care about maintainability, testing, or accessibility. I cared deeply about those things.
On the other side, as an interviewer, I’ve seen strong candidates who were technically brilliant but didn’t show real interest in the product. Hiring them would have been easy. But long term, I knew it wouldn’t work, for them or for us. Saying no in those cases wasn’t rejection, it was protection.
Adopting the win/win or no deal mindset changed everything for me. It takes away the fear of rejection and replaces it with clarity.
As engineers, we know that forcing systems to work together when they don’t belong leads to brittle solutions. The same is true in our careers.
So next time you walk into an interview, remember: you’re not there to win or lose. You’re there to discover alignment. If it’s a win for both sides, brilliant. If not, it’s no deal - and that’s the best outcome you could ask for.
Wed, 11 June 2025
From Athlete to Engineer: Lessons I Carry Into Coding
I spent over 15 years as a professional hockey player before becoming a software engineer. The lessons I carried from the ice to the codebase continue to shape how I write code, work with teams, and grow my career.
Mon, 23 June 2025
Managing Time as a Senior Engineer: What Actually Works for Me
Senior engineers are constantly pulled in different directions. Here's how I manage my time to stay focused on high-impact work, support my team, and avoid drowning in distractions.
Thu, 17 April 2025
Why I Stopped Obsessing Over 100% Unit Test Coverage
Our CI pipelines required 100% coverage. Here's how it backfired and what I now focus on instead.
Subscribe to get updates on new blog posts, useful frontend tips and ideas you can apply in your own work.