Billy Bunn — software engineer.
I build software for systems people actually have to run.
At Nike, that means privacy and consent services: APIs, data migrations, deployment paths, monitoring, and internal tools. Before that I built consumer web and mobile services for Hestan. I'm open to remote roles where the work is practical, technical, and still needs judgment after the first version ships.
Make the work easier to change later.
I am usually most useful between a feature request and the system that has to run it: shaping the contract, building the path to production, writing down the tradeoffs, and making sure someone else can pick it up without starting over.
- 01 Understand the shape. I like clearing up the data model, service boundary, failure cases, and the reason the thing needs to exist.
- 02 Ship with a rollback story. The release plan, checks, alerts, and handoff are part of the work, not chores after the work.
- 03 Use tools without hiding judgment. Automation and AI help when they make the evidence easier to review.
The short version.
Privacy is where I have done a lot of recent work, but the broader fit is backend and platform engineering: reliable services, data migrations, internal tools, developer workflows, and systems that need to be both useful and explainable.
- Profile Current role, previous work, skills, and how to get the full resume.
- Selected work High-level examples from platform, migration, and privacy systems work.
- Notes Short pieces on software, tools, and the parts of systems people live with.
- Personal bits Tools, software, music, and what I use day to day.