The engineer you bring in when the system has to work.
The backend work that keeps products running: resilient queues, idempotent flows, and APIs that don't need babysitting at 2am.
1–2 engagements per quarter. EU and US morning overlap.
What I actually work with, day to day.
Not a stack sheet. The tools and terrain I'm fluent in — the ones that pay for themselves in the second sprint, not the tenth.
The engineering, translated into things you'd actually put on a roadmap.
Backend work only matters if it moves the business. Three of the ways it usually does.
-
Ship what you promised
Backends that go live on the date you told the customer, not on the day the ticket queue clears.
-
Sleep through the night
Systems designed for the failure modes, not just the happy path — because the pager is a business problem, not a lifestyle.
-
Scale without the rewrite
APIs and data flows shaped so next year's growth doesn't cost you next year's roadmap.
The still point
“I can do all things through Christ who strengthens me.”
Philippians 4:13The work has meaning because there are plans I did not draw. Jeremiah 29:11
Between systems, there are people.
I like the long table, the late conversation, the part where the good stuff comes out after the second coffee. Bring your team, or bring yourself.