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 platforms that run across whole organisations, design systems other teams build on, and tools for working with photo and video at scale. The thread: complex domains made simple to use.
Frontend → API → Infra
Are you available?
From Q3 2026. No middlemen. Get in touch.
What does a first week look like?
Trust gets built by the loop closing, not by the diagnosis. The goal in week one is to be useful fast — not to redesign everything from a position of confidence I haven't earned yet.
- Read the codebase. Don't touch it.
- Talk to the team — what's working, what hurts, what's about to break.
- Find one small thing and ship it by Friday.
From week two: ship things that actually matter.
What do you care about?
Software that doesn't get in the way of the people using it. Interfaces that feel right on a flaky phone with one bar of signal. Picking the boring tool when boring is correct, and recognising when it isn't. Teams that ship more than they polish.
Why hire a contractor?
Often you shouldn't. If you've got the bandwidth to bring someone permanent on properly, do that. A contractor makes sense when you have a real piece of work, a real deadline, and need someone who can land in week one and ship in week two. That's the only honest pitch.
What are you working with?
Lately: thinking about how the choices I make today will look in three years. Not "is this maintainable" — "is the paradigm still the right one for the problem".
Day to day though: Angular and TypeScript on the front, NestJS and Postgres on the back, Azure or AWS depending on the project. Picked because they get out of the way.
- Angular
- TypeScript
- NestJS
- Postgres
- Prisma
- Azure
- AWS
- Git