Overview
Softwow was where I grew up as an engineer. Over five and a half years I went from Frontend Developer to Frontend Tech Lead to Technical Lead — watching the same company from three different altitudes, across many client projects.
Challenge
The hard part of moving into leadership isn’t the title; it’s changing what your job actually is. As an IC, success is the features you ship. As a lead, shipping more code stops being the point — the job becomes making sure the project succeeds technically, and that the team gets faster, without dropping your own hands-on edge.
Architecture
Each promotion came from fixing the system, not just the tickets. I started building client frontends from scratch. As I took ownership of standards, reusable components, and delivery quality, I was promoted to Frontend Tech Lead — and the work shifted: analyzing requirements, proposing architecture, choosing technologies, distributing work, unblocking developers, reviewing code, and mentoring juniors. As Technical Lead I led distributed engineering teams across concurrent projects.
Implementation
The changes that compounded:
- CI/CD adoption across client projects — deployments went out about 30% more often.
- Engineering standards, reusable components, and systematic code review to raise delivery consistency and quality.
- Mentoring — handing smaller projects to juniors and guiding them through the hard parts rather than doing it for them.
Throughout, I stayed hands-on. The bigger projects included management systems and AI chatbots.
Lessons
Leadership, I learned, is making the project succeed technically — not writing the most code. Architecture, technology choices, unblocking people, and review matter as much as implementation. The multiplier is systems and people, not heroics.
What I’d improve
I’ve never carried formal people-management — hiring, performance reviews, compensation. That’s my growth edge, and something I’m genuinely interested in; the technical-leadership-while-hands-on shape is where I do my best work today.