Dave Beazer.
Contract software engineer.
What do you want to know?
Suggested prompts
That's the lot. If anything resonated, drop me a line.
What kind of work do you do?
I build things on the web. End-to-end — frontend, API, infrastructure when it matters. Recent work has spanned organisation-wide platforms that cross multiple teams and departments, design systems that other teams build on every day, and media tooling for capturing, organising, and exploring photo and video at scale. The thread: complex domains made simple to use.
Frontend → API → Infra
Are you available?
For interesting work, typically Q3 2026 onwards — one engagement at a time, no agencies in between. If you're wondering whether your project counts as interesting, the test is: would I tell a friend what I'm working on? If yes, get in touch.
Show me something you've built.
I can't pin down a single screenshot — the work is rarely public. A platform that runs across every part of a single organisation. A design system that other teams build on every day. A photo-and-video tool for capturing and exploring large media archives. They look different. They needed someone who could pick up the domain, the stack, and the constraints, and own it end to end.
What do you care about?
Code that works. Interfaces that feel right on the worst phone, the worst connection. Picking the boring tool when boring is correct — and the right tool when it isn't. Not over-engineering. Teams that ship.
Why hire a contractor?
You don't always need to. If you've got the bandwidth, the domain knowledge, and the time to onboard a permanent hire, hire permanent. A contractor is for when you have a real piece of work, a real deadline, and you want someone who can land in week one and ship in week two. That's the whole pitch.
What are you working with?
Lately: turning over how good interfaces age. Three years out, are they still legible? Five years out, is the code still kind to its maintainer? It's the question that decides whether a stack choice was the right one.
Day to day: Angular and TypeScript on the front, NestJS and Postgres on the back. I try a new editor every couple of years and end up back in VS Code with too many keybindings.
- Angular
- TypeScript
- NestJS
- Postgres
- Prisma
- Azure
- AWS
- Git