Technical note
Leading a frontend team of 5 in SaaS
Technical leadership patterns, CI/CD, and standardization I used over 3+ years on a production pharmaceutical product.
Beyond code review
Leading 5 frontend engineers on a B2B SaaS means defining standards that scale: folder conventions, state patterns, when to use composition vs. premature abstraction, and how to document decisions (lightweight ADRs in Notion or README).
Standardization without bureaucracy
We built an internal component library for critical purchase flows (cart, checkout, distributor comparison). It didn't replace all UI — it covered the 20% of components representing 80% of the bug surface.
CI/CD as culture
Jenkins + AWS aren't just tools: they're the team's quality contract. PRs with lint, tests, and preview environments reduced deploy fear. Predictable deployments let product trust frequent releases.
Mentoring and ownership
Rotating ownership by module (each dev leads a domain per sprint) distributed knowledge and reduced bus factor. Pair programming on complex integrations and biweekly architecture sessions kept alignment without extra daily meetings.
Takeaways
- Component library focused on critical flows, not cataloging everything
- CI/CD pipeline as quality gate, not obstacle
- Rotating ownership by business domain
- Mentoring on complex integrations, autonomy on standard features