Lead by teaching
I transfer judgment through pairing, reviews, and living docs so the team gets faster as it grows, not slower.
Shoapeng Lee
Engineering Leader specializing in Commerce Platforms
I build scalable commerce systems and engineering teams that can ship without heroics.
- 9+ years of full-stack engineering
- Led teams of up to 10 engineers
- Shopify Plus + AWS commerce platforms
- Terraform, serverless, and full SDLC delivery
My Path
I have spent 8+ years building software and leading the people who ship it. Today I lead engineering at Sunrise Integration: architecture decisions, mentoring developers, and keeping delivery predictable for complex commerce and integration work.
The through-line is leadership by teaching. Weekly sharing, pairing, and reviews matter as much as Terraform modules or POS flows. Companies grow when more people can make good decisions without waiting on one hero.
Earlier specialty commerce work shaped that view: POS capture, associate portals, webhook platforms, cron fleets, and back-office order tools only stay calm when the team shares the map. Before that I shipped React Native and AWS-backed mobile experiences, and managed engineering for education technology including real-time classroom systems.
What I care about most is teams and systems that stay understandable: clear ownership, infrastructure you can review, and releases that do not surprise anyone at 2 a.m.
Where I Excel
Leadership, teaching, and the platform craft that makes teams faster over time
Technical Leadership
I lead cross-functional teams of up to 10 through full delivery: SRS and architecture docs, mentoring, Agile cadence, and hands-on guidance that helps teams ship 1-2 weeks ahead when it counts.
Teaching That Scales Companies
Weekly sharing, pairing, and reviews that transfer judgment. I measure leadership by how many teammates can ship without me in the critical path.
Full-Stack Product Engineering
End-to-end delivery with Node.js, TypeScript, React, and Remix. I turn requirements into production systems that teams can own and extend.
Cloud Architecture & IaC
AWS platforms built as code with Terraform: networks, containers, serverless, CI/CD, and multi-environment parity that stays reviewable.
Reliable Deployments
Release paths that reduce risk: pipelines, blue-green cutovers, health checks, and clear rollback stories for apps that cannot afford downtime.
Commerce Platforms
Shopify and Shopify Plus ecosystems, admin apps, POS specialty workflows, associate portals, webhook platforms, and event-driven backends that keep operations aligned.
How I Lead and Build
Teaching habits, modular design, and documentation that keeps teams aligned
Modular by default
I structure code and infrastructure into reusable units, services, modules, and contracts, so new features plug in without rewriting the core.
Boundaries that hold
Handlers stay thin; repositories, mappers, and domain services own the rules. That keeps Lambdas, APIs, and apps testable and easy to reason about.
Document the why
ERDs, infrastructure diagrams, and SRS writing keep stakeholders aligned and give engineers a map before the first PR.
Cloud, Deployments & Delivery
On AWS I design platforms as code with Terraform, using shared modules for networks, containers, serverless functions, and pipelines so environments stay in parity and changes are reviewable. I have wired Terraform Cloud flows for stage and production, and built event-driven backends with Lambda, queues, and EventBridge when the problem calls for isolation and scale.
For application releases I favor paths that reduce risk: health-checked blue-green cutovers, CI/CD that owns the ritual, and rollback stories that are practiced, not improvised.
Underneath the tools is the same OOP instinct: thin handlers, strong domain boundaries, and refactors that make the next feature cheaper than the last.