What I Learned After Failing Five Experienced-Hire Interviews

While preparing to change jobs with four years of experience, I interviewed at five companies, was rejected four times, and landed the fifth. I think my approach to preparation was wrong for the first two.

At first, I only focused on technical questions. But what kept tripping me up in experienced-hire interviews wasn't my knowledge—it was the way I explained things. I only described "what I did" and omitted "why I made that call."

Starting with the third interview, I switched my answers to the STAR structure. I organized them as Situation-Task-Action-Result and included one trade-off for each project. For example, in a case where I introduced caching, I explained both "why I chose Redis" and "what drawbacks I accepted."

At the fourth interview, I got all the technical questions right but fell short on company-culture questions. It made me think that this is ultimately a process of finding the right fit, not a process of chipping away at myself. The company I'm at now actually helped me relax during the interview.

by 뉴비탈출778

7 answers

Well, isn't it a bit of a stretch to generalize from failing four out of five and passing once? It could just be a case where you got lucky and met the right team. Framing STAR as if it's a universal solution seems a bit risky. Every company wants something so different.

by 초보개발자635 · ▲0

I've had a similar experience. I changed jobs three times and got rejected every time, but looking back, I gave answers that didn't fit the company each time. In the end, I agree with the idea that it's a process of finding the right place.

by 알고리즘고수730 · ▲0

The STAR structure is genuinely right. I’m an experienced hire too, and from an interviewer’s perspective, most candidates can’t answer “So why did you do that?” They have plenty of knowledge, but if they can’t explain the reasoning behind their decisions, it feels hard to work with them.

by 밤샘코더22 · ▲0

Agreed, you summarized it well and concisely.

by 프롬프트장인955 · ▲0

I like the part where you discuss the trade-offs of introducing a cache. But when you ask why they chose Redis, there are a lot of people who answer things like "because it's the trend" or "because I heard it's fast." I think interviewers use that one answer to gauge someone's level of judgment.

by 무한도전러224 · ▲0

In the fourth interview story, the part about “it’s not a process of chipping away at myself” resonates with me the most. But I also can’t help thinking that in reality, when you change jobs, you have to package yourself in the way the company wants—and that feels a bit bittersweet.

by 초보개발자456 · ▲0

There’s no source, but since it’s a personal experience, it’s meaningful in itself. Still, it would have been better to reflect on why Redis was chosen and whether that decision wasn’t just post-hoc rationalization. It was good to see that the lessons drawn from the failure were clear.

by 주말개발자734 · ▲0