I've met ten-year developers who still think like juniors, and two-year developers who already think like seniors. So after a decade in this field, here's my honest take on the senior vs junior engineer difference: it has almost nothing to do with how long you've been writing code. It's about the question you ask before you write any.

Two questions

The junior question is "How do I code this?"

The senior question is "Should we build this at all?"

I'm not romanticizing seniors here — I asked the wrong one for years. Every problem looked like a coding problem, so the solution was always more code. New feature? Write it. Weird edge case? Handle it. Someone mentions a shiny framework in standup? Perfect excuse to rewrite something that already worked. I thought that was engineering. It was mostly motion.

The senior mindset starts one step earlier, before a single line gets written. What's the actual problem? What's the simplest thing that solves it? What breaks when this runs a thousand times a second instead of once? Juniors solve coding problems. Seniors solve business problems that happen to involve code.

The two-weeks-vs-two-hours story

Here's the moment it clicked for me, and it stung enough that I still remember it.

A feature request came in: users wanted to export their data. Past me — honestly — would have spent two weeks on this. A proper export system. Custom formats. A queue for background processing. Progress bars. Retry logic. The whole cathedral. I'd have been proud of it, too.

A senior engineer on my team asked one question instead: "What format do they actually want?"

The answer was Excel. That's it. People wanted to open the data in Excel.

She added a CSV download button. Two hours. Same outcome — arguably a better one, because there was nothing left to maintain. My beautiful two-week plan went quietly into the trash, and I sat there feeling slightly ridiculous.

That's the whole lesson. Same result, ten times simpler, and the difference wasn't skill with a keyboard. It was one question asked at the right moment.

It keeps happening

Once you see the pattern, you see it everywhere.

  • A junior spends a week writing a custom monitoring solution. A senior asks, "Did you check whether Azure Monitor already does this?" — and it does, out of the box.
  • A junior reports "the build failed." A senior reports "the build failed because of X, here's the fix, and here's how we stop it happening again."
  • A junior wants to add another service. A senior wants to understand why the last one is slow before hiding the problem behind a second one.

Same errors. Same tickets. Completely different responses. You become senior the moment you stop solving tickets and start solving the systems that generate the tickets.

How the shift actually happens

Nobody flips a switch. But if I had to compress it into things you can practice starting tomorrow:

  • Ask "why" before "how." Before you design the solution, make sure you understand the problem. Half the time, the request people make isn't the thing they actually need.
  • Choose simple over clever. Clever code is the code you'll be debugging half-asleep on a Sunday. The person who has to fix it is almost always future you, six months later, with no memory of why it was written that way. Write for that person.
  • Check what already exists. Your cloud provider, your framework, your standard library — someone probably solved this already. The best code is the code you never write.
  • Optimize for the team, not for looking smart in review. Nobody remembers the elegant one-liner. Everybody remembers the outage it caused.

So which one are you?

None of this is about years on a résumé. It's about which question comes out of your mouth first when a task lands on your desk — "how" or "why."

I still catch myself reaching for the two-week version. The difference now is that I hear that senior's question in my head before I open the editor: what do they actually want? Usually the answer is smaller, simpler, and already sitting in the standard library.

If you're early in your career, you don't need ten more years. You need to start asking the second question today. And if you've been doing this a while and you're still asking only the first one — that's the honest gap worth closing.

Which question do you ask first?