Hey.

Three teams, fourteen engineers, across merchant experience, analytics, and storefront. My job: keep them shipping, keep the technical direction honest, and look further ahead than the next quarter.

• Brought agentic coding into all three teams at a pace that let it stick — shared patterns over mandates. The design-to-merge loop tightened week over week.
• Noticed work piling up in code review and ran a cross-team effort to unstick it.
• Put together a new team and roadmap for merchant analytics — it started as a gap in the product; merchants now treat it as a given.
• Worked with each team to take real ownership of observability — their own dashboards, alerts, and on-call health, not a central team's problem.

One team, seven engineers, creating the Rewards and Retention platform. Co-owned product roadmap for the team and spent much of the year mentoring newer engineering managers.

• With the team, shipped referrals, opened cancellation-prevention flows through new public APIs, and rolled out per-channel marketing consent for GDPR/CCPA.
• Mentored five first-time engineering managers across the org, and ran ~120 interview loops as hiring manager for engineering roles.
• Designed and ran an engineering-collaboration interview stage for the product manager hiring pipeline, used with about 15 PM candidates.
• Coached an engineer on my own team into the team-lead role — which made for a clean handoff when I moved up to Director.
• Untangled phone-number uniqueness across a billion-plus legacy customer records — rolled out without breaking anything, via bi-directional sync between old and new systems.

Seven engineers building the Rewards and Retention platform. I co-owned the roadmap and executed on it while steering the team's shift from API-only to fullstack.

• We launched the rewards product in 2023 — a scrappy first version that still issued $21M in rewards in its first year.
• Added credits so merchants could use rewards for retention, and issuance kept climbing — $28.9M in 2024, $108.5M in 2025, on track for ~$140M in 2026. Merchants now run whole loyalty programs through it.
• The team grew from API-only work to owning features end to end — everyone cross-trained across backend and frontend.
• Piloted a 6-week delivery rhythm with the team; the rest of the company later adopted it.

Early engineer at a YC observability startup. Event-driven monitoring in Go — and a generalist on whatever else needed doing.

• Worked alongside the founding engineers, using Go and protobuf, on the event-driven monitoring primitives that anchored the platform.
• Pitched in outside my lane too: a frontend redesign, the billing platform.
• Contributed to Plumber, the team's open-source event-routing CLI.

Hired as the team's billing subject-matter expert, on a small team spanning growth, onboarding, and billing, in an Elixir and event-sourcing codebase.

• Built the billing platform in Elixir and migrated the old one onto it, then refactored the onboarding and approval flow it powered.
• Built the company's first enterprise account platform, with two-way Salesforce sync.
• The billing go-to for the first native iOS app and the paid-membership launch.
• Like the rest of the team, on-call for the platform through the MrBeast, Barack Obama, and McDonald's launches.