Career planning is most often discussed at the level of “which technology should I learn?”. In reality, a software engineer’s career is shaped less by technology and more by impact area, problem type, and operational maturity.
In this post, I’ll share practical methods for building a 6–12 month career plan not like a “course list” but like a real-world skill portfolio.
1) Choose the goal as a problem type, not a role
Role names change; the problem type endures:
- product development
- platform/SRE
- security
- data
- system design
Pick which problem type you want to deepen in.
2) Skill portfolio: make T‑shape real
One “deep area” + several “supporting areas”:
- deep: domain and system design
- supporting: observability, security fundamentals, CI/CD, communication
3) 90/180 day plan: concrete output
90 days:
- 1 technical investment
- 1 operations investment
- 1 communication investment
180 days:
- 1 large project ownership
- 1 cross‑team impact
- 1 knowledge share
Conclusion
Career planning is not a one-time list; it’s a regularly measured system. Move forward with repeatable outputs that produce impact.