Dear team,
I did not become a full-stack engineer by collecting a long list of technologies. The work kept asking me to understand one more part of the system.
Most recently, Tempo Labs asked me to own customer-facing features from technical design through deployment and support. Before that, Swerv asked me to lead across APIs, cloud systems, partner tooling, and a consumer mobile app.
The earlier work explains the instinct underneath that range: reliable interfaces at FoodNow and offline-first mobile at Timart. The products I build now keep extending it. Wherever a decision is blocking the outcome, I want to understand enough of the system to help it move.
Tempo Labs · Software Engineer · Oct 2024 — Mar 2026
Ownership moved beyond shipping.
At Tempo Labs, a YC S23 company, I shipped customer-facing products for 5+ startup clients. I worked directly with founders, designers, and product teams, owning features from technical design through deployment and support.
The work spanned React and Next.js web interfaces, React Native mobile work, and TanStack and TypeScript connected to Hono services, PostgreSQL, and Supabase. I built streamed AI experiences over SSE and a server-side provider abstraction, alongside Clerk and Supabase Auth flows and upload and content workflows whose states stayed aligned with backend processing and persisted data.
Read the Tempo Labs story ↗Swerv · Lead Software Engineer · Jun 2022 — Oct 2024
Leadership widened the frame.
At Swerv, I was one of two engineers responsible for an embedded-finance platform spanning payments, virtual accounts and cards, wallets, KYC, transaction history, and reconciliation. The work crossed Go and NestJS services, public APIs, partner tooling, cloud infrastructure, and the Flutter consumer app.
Those REST APIs served nearly 20 partner businesses. OAuth, partner webhooks, and Asynq and Redis jobs kept integrations moving reliably, while the mobile app reached approximately 100,000 combined iOS and Android downloads. Leadership became less about a title and more about owning how the whole system behaved.
Read the Swerv story ↗FoodNow + Timart · Frontend and mobile · 2021 — 2023
Reliability was the first product lesson.
At FoodNow, I built responsive ordering and real-time order status experiences with Next.js and Tailwind CSS, connecting reusable interface states to backend APIs. It taught me that a polished screen is only useful when it reflects what the system is actually doing.
Timart made that lesson harder and more valuable. I worked on an offline-first Flutter commerce app using local SQL storage and synchronization, GraphQL, Firebase Cloud Messaging, Analytics, and Crashlytics. At the time, the product served over 200 businesses. Weak networks, delayed sync, and recovery paths were part of the product—not edge cases.
Now · Open source and products
Between roles is still a building season.
Mosaic is my ongoing open-source app monetization platform: a shared protocol, local-first Studio, Go API, and native renderer and preview clients for Flutter, SwiftUI, and Jetpack Compose. It asks me to think across product, protocol, SDK, backend, and developer experience at once.
The same instinct runs through PGStream, s3ase, Dagryn, and b0: migration tooling, storage infrastructure, workflow orchestration, and an AI backend builder. Independent work keeps product judgment honest because there is no handoff point—if something is confusing, brittle, or unfinished, it is mine to notice.
Next · A high-ownership team
The next chapter should be shared.
I am looking for a team where engineers are trusted with context, product quality and code quality belong in the same conversation, and ownership does not stop when a pull request merges.
I can move between React, Next.js, TypeScript, Go, Flutter, PostgreSQL, Redis, and cloud delivery. The more important pattern is how I use that range: understand the real constraint, make trade-offs visible, and stay with the result after it ships. I am open to relocating for the right team.