Senior software engineer, 17 years in. I design and run the APIs, integrations and event-driven systems that connect things never built to work together. Also a curious human.
In 2009, I was working on reporting systems. The lesson was simple: when software fails, someone's real day gets harder.
Then came my first integrations. Vehicle data. Business systems. External services. Suddenly, the interesting part wasn't just the code — it was what happened between things.
Seventeen years later, that's still the job. Across lending, payments, clinical research, wealth management, telecoms and energy, I design the systems in between, and stay responsible for them once they're running.
THE FULL STORY HAS TWELVE ROLES. EXPLORE THE CAREER TIMELINE ↗
I design how services that were never meant to know each other work together: the APIs, the events, the data contracts, and what happens when one of them fails. Then I own it in production.
Here's what happens behind the scenes when you place an order, and what happens when things go wrong. It's built the way I'd build one: separate bounded contexts, an aggregate that protects the business rules, events in an append-only store, a saga coordinating payment, and a separate read model for queries. Then break it and watch it recover.
SIMULATION ONLY. NO LIVE CUSTOMER DATA OR REAL API CALLS.
POST /orders// Press “place an order” to follow it across the system.
{ }Change one letter at a time to make a new word. Every valid word resets the 60-second clock. How long can you keep going?
Loading meaning…
Start the timer and stop it at exactly 5.00 seconds. Then try the real thing, where the clock can disappear.
You can learn a lot about someone from what they do when they're not working. Click around.
Some weekends are wonderful. Others make me question why I let eleven people I've never met determine my mood. And yet, here we are.
MORE ABOUT THIS SIDE OF ME ↗Server-side rules, real-time multiplayer and the engineering behind Word Duel.
READ THE NOTE ↗NOTE 02 · · 4 min readWhat happens to engineering teams when everyone solves problems with an assistant?
READ THE NOTE ↗NOTE 03 · · 2 min readLessons from upgrading mature systems without rewriting everything.
READ THE NOTE ↗After building systems across a lot of industries, my next chapter is at Transact, in financial services. New domain, same instincts.
I don't think the interesting part of a career is the list of technologies you've used. It's what you keep wanting to understand next.
SAY HELLO ↗