I am a fractional engineering lead. I join teams when a product or technical system has become consequential—billing, revenue, scale, event flows, or a delivery problem the permanent team cannot safely absorb. I work inside the team for a defined period, from decisions through implementation, tests, deployment, and handoff. I am temporary leadership, not a replacement team or a promise that a rewrite will fix the business.
My work includes billing and revenue systems at New Relic and Netlify, customer-feedback systems at Apple, engineering leadership at Atlassian, products with founders at Scout Fuel, and performance work at Staffing Referrals. I maintain DSPy.rb, write about technical decisions in the blog, and explain the work in talks. These are selected examples, not a claim that every engagement has the same shape.
The constant across that work is team-building. At Apple, I helped the team move from fortnightly release meetings to smaller daily releases while the Rails system grew from 3 to 80 web instances and from 1 to 94 background workers. Across Apple, Atlassian, New Relic, Netlify, Staffing Referrals, Tray.io, and Finalis, I help teams learn technical and operating skills while the work ships. The handoff is part of the job: people should understand the decisions, extend the system, and face the next change with more range than they had when I arrived.
If your team is carrying a high-consequence change while it still has to ship, send me the situation: what the system does, what needs to change, and what the team cannot pause. I will say whether I can help. My public identity is also verifiable through GitHub, LinkedIn, and X.
Colophon
This site is built with Bridgetown.