Billy Bunn — software engineer.
I build software for products people use every day.
At Nike, my work sits behind privacy and consent systems used by millions of people. Before that, I worked closer to startup scale, building consumer web, mobile, and backend services. I like remote teams that learn quickly, use new tools carefully, and still expect good judgment after the first version ships.
Ship useful software without losing the thread.
I am usually most useful where product needs, backend systems, and release pressure meet: turning a rough ask into a service contract, a path to production, and enough evidence for the next person to trust the work.
- 01 Clarify the work. I like clearing up the data model, service boundary, failure cases, and the reason the thing needs to exist.
- 02 Ship with a rollback path. 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.