Engineering Leadership

Business Goal

The organization needed credible product increments on aggressive timelines across web and mobile while keeping regressions manageable. Leadership wanted velocity without burning out contributors — which meant better scoping dialogue, tighter review expectations, and enough structure that juniors could onboard without heroics.

Problem Statement

Ship fast, don't break. Two web platforms and a mobile app, all serving thousands of daily active users, had to keep moving — without regressions reaching production. Delivery was reactive, spikes were undocumented, knowledge lived in chats, and there was no consolidated design language across the surfaces a single user touched.

Solution

I standardized the team on a modern toolchain so the boring parts stayed boring: Next.js on Vercel for the web platforms (preview deploys per PR), Expo for the cross-platform mobile app shipping to both iOS and Android, Notion as the single source of truth for specs and engineering docs, and Linear for project management with explicit cycle scopes. On top of that, I rebuilt the deployment and testing flow with GitHub Actions — typed CI, preview environments, and required checks before merge — so "ship fast" stopped meaning "ship broken".

Achievement

• Team lead of 5 engineers — hands-on technical lead and primary interface between engineering, product, and design.
• Developed and maintained 2 web platforms and 1 cross-platform mobile app (iOS + Android via Expo), all serving thousands of daily active users.
• Created the project's first consolidated, comprehensive design system — unified tokens, components, and patterns across web and mobile so the product looked and behaved like one product.
• Improved deployment and testing workflow with GitHub Actions — preview deploys, typed CI checks, and required green checks before merge, which let the team move quickly without breaking production.
• Standardized tooling across the team — Next.js + Vercel, Expo, Notion docs, Linear PM — so onboarding got predictable and meetings stopped relitigating choices.