What Interviewing 100+ Engineers Taught Me (as a Leader & as an Engineer)

"Honesty, curiosity, and a genuine engineering mindset will always stand out — louder than any number of years, tools, or buzzwords."

Over the last few months, I have spoken to more than a hundred developers and QA engineers — across startups, product companies, and large organisations like Amazon and Walmart. Different tech stacks. Different journeys. Different motivations.

And yet, despite all that diversity, a few clear patterns kept repeating. Patterns that say a lot about where engineering talent is today — and where it is headed.

Five Patterns That Kept Repeating

From a hundred-plus conversations and countless problem-solving sessions

1️⃣

Talent today is far more intentional

Why: A few years ago, interviews felt exploratory — "let me try; if it works, I'll switch." Today candidates come deeply prepared, they know what they want, and they are serious about their next step almost regardless of where they currently are. The casual era is fading.

2️⃣

Passion for coding has zero correlation with years of experience

Why: I have seen 3-year developers write elegant, efficient logic and 10-year developers struggle with fundamentals. Some genuinely enjoy problem-solving; some rely entirely on memory or external aids.

Experience is a number. Mindset is the differentiator.

3️⃣

AI is entering the interview room — and it shows

Why: A surprising number of candidates say "I write prompts for coding." I appreciate the honesty, but the follow-up is always: do you have the prompt with you now? Using AI is not the issue. Not understanding what the AI produced is the real gap — one missing condition, one edge case, and the solution breaks.

AI accelerates strong engineers. It exposes unprepared ones.

4️⃣

Microservices, Kafka and quality gates — the reality check

Why: Some conversations are deeply energising: designing microservices, scaling for throughput, Kafka for parallelism, high availability, strong quality gates, deployment strategies that reduce blast radius. But that is not the majority. Many genuinely believe "Copilot wrote my tests, so quality is done" — and don't know what happens after code is merged: pipelines, rollbacks, metrics, observability, incident patterns.

Quality is not a file. Quality is a mindset.

5️⃣

Interview mindset shapes the outcome more than people realise

Why: Engineers who say "I'm not strong in this area" earn enormous credibility instantly. Honesty is a signal of maturity.

The Two Kinds of Candidates

One group almost always leaves a stronger impression

Two postures in the same interview

The Conversational Engineers

They discuss openly, think aloud, challenge assumptions, and ask clarifying questions. They treat the interview as a collaborative problem-solving session.

The Q&A Engineers

Short answers, defensive tone. Trying to convince instead of engaging. Treating it like an exam rather than a technical discussion.

The first group almost always leaves a stronger impression — even when they do not know everything.

What It Taught Me as an Engineer

Interviewing is a mirror

✓Three things I did not expect to learn

•

The same problem can be solved in beautiful, surprising ways:different logic structures, different breakdowns, different optimisations, different heuristics — some approaches were unique enough that I genuinely learned from them

•

System design conversations sharpen architectural intuition:new ways of building parallel processing pipelines, patterns for scaling reads and writes, approaches to high availability and fault tolerance, where quality gates fail in practice

•

Interviews create a two-way learning loop:engineering isn't rigid, good design isn't a template, problem-solving is deeply personal, and true expertise often hides behind simplicity

A Few Principles I Wish More Candidates Followed

Simple things, massive impact

Small habits that change everything

✓Be 5 minutes early
✓Treat it like a conversation, not an argument
✓If you need time to think, say so
✓If you don't know, say so
✓Don't join interviews "just to attend"
✓Respect your time and the interviewer's time

Conclusion

Interviewing hundreds of people doesn't just sharpen your eye for talent. It reshapes your belief in what great engineering looks like.

You don't just evaluate others — you evolve your own mental models.

Read original article on Medium