Why Do Interviews Keep Ending the Same Way? A Five Whys Story

Posted by

–

A DevOps engineer with solid skills applies to a dozen roles in a season and gets as far as the second interview every time. Each rejection email is polite and vague. Each time the engineer concludes that the market is tough, brushes off the disappointment and sends another batch of applications. By the fourth round the pattern is plain, but the explanation has not changed. This story, composed from situations that careers writers see often, is about the day the engineer stopped accepting “the market is tough” and began asking why, five times over, with a pen in hand.

The comfortable answer that explained nothing

“The market is tough” is true for most people at most times, which is exactly why it explains so little. If it were the whole story, results would be random, and instead they were oddly consistent: first interviews went well, second interviews stalled. A consistent outcome calls for a consistent cause, and consistent causes live in habits, not in the economy.

So the engineer wrote a different first sentence: “I reach the second round and then stop.” A pattern with a place in it can be investigated.

Why one: what happens in the second round?

The second interview was usually a conversation with a hiring manager and a senior engineer, built around the candidate’s past projects. Looking back at notes, the engineer saw that these conversations kept circling back to tools: which pipeline, which container platform, which cloud. Answers were accurate and short. The interviewers’ follow-up questions tended to drift toward other candidates’ stories.

Why two: why did the answers stay short?

When asked about a project, the engineer described what was built, not why. Outcomes, trade-offs and surprises were missing. In an interview, that makes a person sound like an operator of tools instead of someone who solves problems.

Why three: why did the stories lack outcomes?

Because the engineer had never written them down. The portfolio page and the resume listed technologies, and the engineer had assumed the interviewers would ask for the rest. Preparing for interviews meant revising commands, not rehearsing narratives.

Why four: why did the portfolio list only tools?

The template for the portfolio page had been copied from a popular example, and that example had a long “skills” section with logos but no section for problems solved. The engineer had filled in the boxes that existed.

Why five: why was the template never questioned?

Nobody had asked for it to be. Friends and former colleagues praised the clean look. Praise for design is easy to give and does not tell you whether the content answers the question a hiring manager has, which is “what would this person do for us?”

Five answers deep, the cause turned out to be a borrowed template and the habit of preparing for questions about tools. That was fixable in a weekend. It also had nothing to do with talent or the economy.

The changes that followed

  • The portfolio gained a “problem, action, result” format for each project, with one honest line about what went wrong along the way.
  • Interview preparation shifted from reciting commands to telling three short project stories aloud.
  • The resume lost its list of logos and gained two lines of results per role, each written in plain terms.
  • A one-page note recorded the chain, so the same loop could be spotted next time something stalled.

The second-round results did not turn around overnight, and the engineer was careful not to claim a single cause for every rejection. But the conversations changed: interviewers started asking about decisions, and the engineer had decisions to talk about.

Checking the story against reality

A chain that flatters you should make you suspicious. The engineer tested the finding by asking a former colleague to read the old portfolio cold and say, in one sentence, what kind of work the owner wanted to do next. The colleague’s answer was “something with containers”, which confirmed the problem: nothing on the page described a kind of problem, only a set of tools. That small outside check is worth far more than another hour of private reflection. It also costs almost nothing: five minutes of a friend’s attention and a willingness to hear an unflattering reading. Ask for the answer in writing so you can compare it with what you intended to say, and thank the reader whatever the verdict turns out to be.

Pitfalls to avoid while you try this

  • Do not turn every rejection into a lesson about yourself. Some roles are filled internally, and some close for budget reasons.
  • Do not stop at “I need more certifications”. Ask what the hiring manager would see differently if you had one.
  • Do not rewrite everything at once. Change one element, such as the project format, and watch what moves.
  • Do not invent results. Stories with honest numbers or honest uncertainty hold up under follow-up questions far better than polished ones.

What a skills example might look like

A strong portfolio entry might describe cleaning up a container image so builds became faster and less error-prone, name the trade-off that was accepted and say what was learned. Two of our pieces cover the technical side of that kind of entry: a walkthrough of keeping container images tidy and consistent for a whole engineering group and a list of frequent beginner slips with Docker and how to dodge them. Either can become the seed of a project story if you add the why.

A small detour about layout

Career pages benefit from the same signposting you see on large directories. A medical-tourism style orthopaedic listing site, with its hospital, doctor, blog and forum menus plus search, shows how a visitor can jump to what matters in a click. For a portfolio, the equivalent is putting the problem and result at the top of every project instead of burying them below a wall of logos.

Try it on your own search

If your applications stall at the same point, write that point as a sentence. Gather what you can observe: interview notes, feedback emails, your own portfolio as a stranger would read it. Ask why and answer from the evidence, and keep going until you reach something you control: a document, a habit, a template. Make one change, give it a month and look at what happens at the stage where you used to stall.

Careers rarely turn on a single insight, but they often turn on a single repeated question that someone finally had the patience to ask. Asking why five times will not guarantee an offer. It will, however, make sure that when an offer does not come, you learn something you can use.

0 0 votes
Article Rating
Subscribe
Notify of
guest
0 Comments
Oldest
Newest Most Voted
0
Would love your thoughts, please comment.x
()
x