I'm a Good Engineer but Terrible at Interviews. What I Did About It.
Prashant Mehta
April 15, 2026
I know my stuff. I've been doing backend development for nine years, mostly Go and Python, some Rust lately. I can architect distributed systems. I can debug things at 2am. I've shipped products that handle millions of requests. But put me in a behavioural interview and I fall apart. "Tell me about a time you handled conflict with a stakeholder." My brain goes blank. Not because I haven't done it. I have. But I can't package it into a neat story on the spot. I start rambling. I give too much technical context. The interviewer's eyes glaze over.
The Melbourne market specifically
I'm based in Melbourne and the tech scene here has this weird thing where even deeply technical roles want you to pass behavioural rounds. I get it in theory — culture fit matters. But when I'm applying for a principal engineer role and the third interview is "tell me about your leadership philosophy," it feels disconnected from the actual work. I lost two offers last year because of this. Technical rounds, fine. System design, fine. Behavioural round? Thanks but we've decided to go in a different direction.
What I tried
I'm not great at winging things so I prepared like it was a technical problem. I wrote down twelve stories from my career. Real ones. Conflict. Failure. Leading without authority. Tight deadlines. Each one in a basic structure — what happened, what I did, what the result was. Then I practiced saying them out loud. This felt incredibly stupid. I was sitting in my apartment talking to myself about a disagreement I had with a product manager in 2022. But it worked. When the question came up in my next interview, my brain had something to reach for instead of just panic.
The outcome
Got an offer from a company in Cremorne. Principal engineer. The behavioural round still wasn't my strongest — the interviewer could probably tell I was reciting prepared answers. But prepared answers are better than no answers. My advice to other engineers who hate this stuff: treat it like a system you need to learn. It's not natural talent. It's preparation. Write the stories down. Practice them. It feels dumb but it works.
Share Your Career Story
Have insights about salaries, interviews, or career moves in Asia? Join our community and share your experience.
Related Posts
I Bombed Three Interviews in a Row. Then I Changed One Thing.
I'm a project manager. Eight years experience, PMP certified, good track record. I was looking to move from construction into tech — same function, different industry. Seemed reasonable. The first three interviews were disasters. Not in...
The Interview Question That Made Me Realise I'd Been Out Too Long
I was in an interview for an operations role at a logistics company. Things were going fine. Standard questions about my experience, my approach to problem-solving, team management. All stuff I could handle. Then the interviewer asked: "What...
The Five Things That Make Me Reject a CV in Under Ten Seconds
I review about 50 CVs a day. Sometimes more. I don't read them in detail — not at first. I scan them. And there are a handful of things that make me move to the next one almost immediately. I'm not proud of how fast these...