SaaS and product systems
How I build SaaS products from interface to infrastructure
I build enterprise and early-stage SaaS products across React, TypeScript, Node.js, Python, APIs, data, authentication, permissions, and delivery.
I like being close to the whole product. The interface may be where I start, but I want to understand the permissions, data, APIs, failure states, and delivery decisions that shape what the user ultimately experiences.
How I think about this work
Good SaaS engineering is not a handoff between frontend and backend. Product behavior crosses the boundary continuously: what a user can see depends on permissions, what they can change depends on workflow state, and whether the experience feels trustworthy depends on latency, recovery, observability, and release discipline.
I am most useful where the interface is a major part of the product but end-to-end ownership is required. I can shape the interaction model, define service contracts, build the supporting systems, and leave the product easier for another engineer to extend.
Work I've done
Enterprise SaaS
Connecting accessible interfaces to distributed services
At ServiceNow, I worked across React and TypeScript product surfaces and Python, FastAPI, PostgreSQL, Redis, RabbitMQ, and role-based access systems. The work connected accessible editor behavior to permissions, transactions, asynchronous processing, caching, and reliable API contracts.
Outcome. The combined frontend and service work improved response times, reduced repeat queries, and lowered cross-team implementation effort for complex workflow features.
Independent product
Building Handoff for Linear from sign-in to issue creation
I created Handoff for Linear, a Figma plugin that turns selected FigJam notes and shapes into Linear issues. The product includes Google sign-in, Linear OAuth, persistent sessions, Supabase-backed link storage, FigJam backlinks, API integration, and product telemetry.
View Handoff for LinearDelivery systems
Reducing release cycles by 30% and documentation builds by 50%
Across enterprise and startup work, I have built CI/CD improvements, test automation, release workflows, instrumentation, performance monitoring, and debugging tools alongside product features.
Outcome. At ServiceNow, delivery improvements reduced release-cycle time by 30%; at BrowserStack, build automation cut documentation build time by 50%.
Let's talk