I Bombed Three Interviews in a Row. Then I Changed One Thing.
Darren Loh
April 24, 2026
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 obvious way. I didn't forget my name or spill coffee on anyone. I answered every question competently. I was polite. I wore a nice shirt. I just didn't get callbacks. Every single time, the recruiter would say "they've decided to go with someone who's a closer fit to the industry." Three times in a row.
The thing I changed
After the third rejection, I called the recruiter and properly pushed for feedback. Not the polished version — the real version. She hesitated and then said something that stuck with me. "You're answering their questions, but you're not connecting your experience to their world." She was right. I was talking about construction timelines and site coordination. They were hearing "this person doesn't understand our context." Even though the core skills are identical. So before my fourth interview — a PM role at a fintech in one-north — I spent an entire weekend reading their blog, their product docs, their Glassdoor reviews. I rewrote my examples. Same achievements, different framing. Instead of "I managed a 50-person site team to deliver a SGD 12M project on time," I said "I coordinated cross-functional delivery across distributed teams with hard external deadlines — similar to your sprint model but with less room for iteration." Same experience. Different language.
The result
Got the offer. Started three months ago. I'm not saying this is some revolutionary insight. But when you're mid-career and switching industries, the gap between what you've done and what they need is often just a translation problem. You have the skills. You just need to describe them in their vocabulary, not yours.
Share Your Career Story
Have insights about salaries, interviews, or career moves in Asia? Join our community and share your experience.
Related Posts
I'm a Good Engineer but Terrible at Interviews. What I Did About It.
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...
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...