Builder
Next.js frontends, NestJS and FastAPI services, a Python RAG pipeline, Helm charts. I wrote 97% of the old frontend and 70% of the new one.
Product engineer · BHyve
Product engineer and team lead at BHyve, a knowledge platform for enterprise teams. In five years I've gone from intern to owning the AI answer engine, a large share of the platform it runs on, and most of our releases. I measure before I change anything, and I write down what I find.
Impact
Each one links to the story behind it.
Case studies
Our platform was built for thousands of users and was serving 30 to 100 a day. I went through it service by service and cut what it reserved, while keeping live answers fast.
Jun – Oct 2026 · 5 monthsI own the engine behind BHyve's AI answers, which searches a company's knowledge base and connected tools like SharePoint, Gmail and Outlook. This is how I made it cheaper per question, measurably more accurate, and configurable per customer without a fork.
Jun – Oct 2026 · 4 monthsOur AI search ran inside Postgres, which scanned every chunk a user could see on every question. I moved it, in stages and without downtime, onto a dedicated vector store that keeps the same speed as the data grows and runs inside a customer's own cloud.
Jun 2025 – Sep 2026AI answers are only as good as the text we pull out of documents. I benchmarked the extraction engines, built a fusion pipeline that beats our old one on tables and headings, and turned it into three tiers each customer can pick by speed and cost.
Sep 2025 – Oct 2026Enterprise customers buy security first. When a penetration test came back with 15 findings, I closed 13 of them the day after the test window ended. When a critical Next.js flaw was being used against our production website, I patched it while the attempts were still coming in.
May – Sep 2026One library change used to rebuild six apps. I redesigned how the monorepo builds and ships: merge to deploy, tag to release, and a CI that only builds what changed.
Apr – Oct 2026On a five-person team, leading means reviewing, unblocking and deciding what's next. I also built the tooling that lets each of us ship like a bigger team: AI agents with shared rules, and a loop from customer tickets straight to the board.
Jul 2025 – Oct 2026 · 15 monthsBHyve v1 was one frontend talking to twelve separate backend repos, each with its own chart and deploy. I started the new web app and became the largest contributor to Platform v2: one Nx monorepo with 14 apps, 24 shared libraries and one release process.
Nov 2024 – Feb 2026Before Platform v2, I was effectively the only frontend engineer: the product, the marketing websites and everything customers clicked on. 671 of the 693 commits to the main app in that period were mine.
The last two years
My commits each month across 27 repositories. Highlighted months open the case study that started there.
2,451 in total
How I work
Next.js frontends, NestJS and FastAPI services, a Python RAG pipeline, Helm charts. I wrote 97% of the old frontend and 70% of the new one.
I treat the cloud bill as a product metric. Shared AI compute, right-sized services, night-only workers and 85–92% smaller images, each measured before and after.
One of four code owners on a five-person team. I've merged 146 pull requests into the platform and cut 59% of our production releases.
I wrote the BHyve AI v4 roadmap, and closed the loop from customers to the board: support tickets become Trello cards, and replies flow back.
I decide with data. A blind test on 935 real queries picked our embedding model. An A/B kept a caching trick switched off because it pushed give-ups from 50% to 84%.
Career