A few years ago, getting into software engineering felt more straightforward. Learn how to code, pick up a framework or two — React, Node, maybe some AWS — and you were set. Junior and intermediate roles were plentiful. Demand was high. The industry felt open.
That’s not the case anymore.
The market has changed. And it’s not just affecting those trying to break in — it’s impacting everyone, across the board.
This past year, I’ve watched layoff after layoff hit every part of the stack: frontend, backend, DevOps. Titles like “Junior JavaScript Developer” or “React Engineer” no longer carry the same weight. And from what I’ve seen, it’s not because people can’t write good code. It’s because the role of a software engineer has shifted. Being a “React expert” or a “DevOps specialist” isn’t enough — not when companies are rethinking who they really need on their teams.
What organizations want today is different. They’re looking for engineers who can contribute beyond just writing code. People who understand the bigger picture — product goals, customer needs, technical tradeoffs. Engineers who can pick the right tools for the job, even if that means stepping outside their comfort zone or choosing something outside their preferred stack.
Sometimes that means JavaScript isn’t the answer. Sometimes the best solution is no-code, or a drag-and-drop builder. Other times, it’s a custom C++ integration or a hybrid approach. The point is: organizations want engineers who think like partners, not just implementers.
That’s how I’ve approached my own career from the start. I’ve always positioned myself as a business partner with a technical mindset. I try to stay informed about the entire landscape — from website builders and automation tools to highly performant, low-level systems — because I want to bring value beyond the code I write.
Of course, I’m not an expert in everything. I choose the areas worth diving into more deeply based on the needs of the teams I work with. The goal isn’t to know it all — it’s to know enough to make the right call when it matters.
That’s what I believe today’s market rewards: not just writing code, but understanding when, how, and why to write it — and when not to.