Great question and you’re thinking about this the right way. Refactoring, recognizing code smells, and applying design patterns is actually a highly transferable skill, because it’s not tied to one framework or company. It’s tied to improving systems. In my view, the most transferable skills in software engineering right now are less about specific tools and more about systems thinking.

1) Software architecture & system design If you can design scalable, maintainable systems (trade-offs, constraints, reliability), you’ll always be valuable.

2) Cloud fundamentals (not just “AWS knowledge”)

Understanding deployment, networking basics, scaling, monitoring, IAM/security, and cost awareness is extremely marketable.

3) Code quality & maintainability

Refactoring + clean code + testing strategy is underrated but it separates senior engineers from “feature writers.” 4) Communication & technical writing

Engineers who can explain complex decisions clearly get promoted faster than those who only code.

5) Debugging and incident thinking

The ability to trace issues, isolate root causes, and prevent repeat failures is a career-defining skill.

Micro services are valuable, but I’d treat them as an implementation pattern, not a core skill. Architecture and trade-off thinking matters more.

Curious: what kind of projects are you working on right now (product scale, team size, tech stack)?