Product engineer and technical advisor. I help early teams ship the first version of hard things.
I have spent a decade building products at the seam between infrastructure and interface — payments, developer tools, and the internal systems teams actually live in. I care about the version that ships, and the second version that fixes what the first one got wrong.
Now I work with a small number of founding teams at a time: setting technical direction, writing the load-bearing code, and leaving behind a team that can keep going without me.
A metering and billing service that ingests millions of events an hour and reconciles them into invoices teams can actually trust. Led architecture and the first year of delivery.
Internal tooling that turned a two-day manual release process into a 20-minute pipeline, with staged rollout and automatic rollback on crash-rate regressions.
An open-source CLI for capturing structured research notes from the terminal and syncing them to any Markdown vault.
A set of libraries for double-entry bookkeeping and idempotent financial workflows, extracted from three separate client engagements.
Embedded with founding teams to set technical direction and build the first production release. Two to three engagements a year.
Owned the billing and identity platforms used by every product team. Grew the platform group from four engineers to eleven.
Built data pipelines and internal analytics tools for a research group.
“Maya joined for three months and left us with a system we understood and could extend. That is much rarer than it sounds.”
“The clearest technical thinker we have worked with. She made the hard calls early so we did not have to relearn them the expensive way.”
Have a project in mind? maya@example.com
