Problem
Carbon compliance shifted from “annual report” to “daily operations.” Enterprises needed audit-ready supply chain data flows, not Excel collages.
Architecture
v1.0 modular monolith on Nest.js → v2.0 split into product lines. Supply chain integrates with two other product lines via explicit APIs.
My Role
- v1.0: founding backend engineer; promoted to Team Lead within a year
- v2.0: own the supply chain product line — milestone planning with the PO, sitemap and flow design, OpenAPI v3.0 specs, and cross-product-line integration
Impact
- v1.0 shipped to multiple enterprise clients
- v2.0 introduced Specification-Driven Development; velocity increased to the point that writing specs became the new bottleneck
Lessons
From writing code, to managing people writing code, to writing specs for AI to write code — each transition resets where my highest-value contribution lives.