Self-serve onboarding and a faster checkout
Self-serve onboarding, live for every new signup at Northwind. Activation rose 18%, and checkout load dropped from 4.1s to 1.3s.
+18% activation
Career changelog. Everything connected.
Calary is a product engineer with five years of shipping, written up as release notes. Zero breaking changes, a few merge conflicts, one very patient design system.

By the numbers
// git blame: 2020 to 2026, product engineering
// git log --oneline | wc -l
// co-authored-by: everyone who asked a question
Selected work
Self-serve onboarding, live for every new signup at Northwind. Activation rose 18%, and checkout load dropped from 4.1s to 1.3s.
+18% activation
A scheduling API that replaced 3 legacy endpoints at Lumen Health. Retry-safe writes brought failed bookings down 31%.
31% fewer failed bookings
The changelog
Every role is a release. Every release has a version, a changelog and one number that mattered.
My approach
Interviews and analytics first. Nothing gets scoped until the problem is written down.
Pick the one metric that matters, then cut scope until the work fits a single release.
Short written updates each week, so no decision reaches anyone for the first time in a meeting.
Prototypes in code early, so the design survives contact with a real browser.
Small merges behind flags, with a test suite that finishes in under two minutes.
Ship, watch the number, and write down whether it actually moved.
Skills
Installed, tested, occasionally upgraded.
// peerDependencies: coffee, curiosity
Reviews
Approved
“Calary cut our onboarding flow from 9 steps to 3 and drop-off fell 41% in one sprint. The migration plan came with a rollback plan, which is more than I can say for most of my roadmap.”
Approved
“Inherited a checkout test suite passing 37% of the time. Two weeks later it was at 99.2%, and nobody on the team has said "just rerun it" since. I read the diff twice and found nothing to block on.”
Approved
“Rebuilt our billing pipeline across 12 deploys with zero incidents. The docs were written before the code, which I did not know was allowed. Approving with zero nits, a first for this repo.”
Contact. Let’s ship something.
Open to full-time and contract roles. Reviews are fast, reverts are rare.
status: open_to_work