Deyan Peev
I build entire products end to end
Product, platform and cloud, with AI as the multiplier. Over a decade of engineering - from financial systems and virtualisation infrastructure to an AI-native platform I now own from the data model down to the Terraform.
What I do
Cloud platform & infrastructure
Designing and owning a whole cloud footprint in Terraform - three environments reproducible from an empty project, plus the migration path onto them.
Full-stack product engineering
APIs, data models, operator admin, customer portals and mobile apps across a large TypeScript monorepo - and the design system the rest of the team builds against.
Production ownership
Networking, secrets, operator access, monitoring and alerting, keyless CI/CD, and a cost model that stays predictable as the platform grows.
AI as a multiplier
Agent-written changes that pass the type check and tests before anyone reviews them, Claude and Codex checking each other, and an MCP server our customers connect their own assistants to.
Technical team leadership
Leading engineering teams through delivery: sharing out the work, setting the technical direction, keeping product owners close, and stepping in on the blockers that would otherwise stall everyone.
Mentoring and knowledge transfer
Raising a team's bar through shared practices, code-quality standards and mentoring, and walking other engineering teams through a platform migration until they could run it themselves.
Experience
Jan 2026 - Present
Founding Engineer · 1club
An AI-native platform for gyms, studios and sports clubs. Product, cloud platform and delivery pipeline, end to end.
2023 - Jan 2026
Senior Platform Engineer · OfficeRnD
Moved the platform off EC2 onto serverless, pulled shared libraries out of the monolith, and built the monitoring and alerting behind them.
2021 - 2023
Co-Founder · DIV Motion
Leading discovery with CTOs and technology directors at small and mid-sized companies, then architecting and building what came out of it.
2017 - 2021
Software Engineer → Technical Team Lead · VMware (now Broadcom)
Automation and orchestration for enterprise virtualisation, ending as the lead on client migration planning and the tooling that automated it.
2015 - 2017
Software Consultant · Accedia
Financial and insurance systems - new features and API management, and later leading a small team and working directly with the client’s product owners.
How I work
Boring over clever
I'd rather spend our creativity on the product than on the stack. Proven tools and simple designs leave more energy for the people we're building for.
Boring over clever
Small steps over big launches
I like shipping in small pieces we can look at together and easily undo. Every step teaches us something, and it makes mistakes a lot less scary.
Small steps over big launches
Prototypes over presentations
When we're stuck on an idea, I like to build a rough version and try it. It's usually quicker than another meeting, and much more fun to talk about.
Prototypes over presentations
A clear no over a maybe
Saying yes to everything means doing nothing especially well. I try to be upfront about what we can't take on right now, and explain why.
A clear no over a maybe
Context over control
I try to share the why and the goal, then get out of the way. The people closest to the work usually find a better how than I would have.
Context over control
Trust first
I start from trust and assume everyone's doing their best. When something goes wrong, we look at what let it happen, not at who to blame.
Trust first
Boring over clever
I'd rather spend our creativity on the product than on the stack. Proven tools and simple designs leave more energy for the people we're building for.
Small steps over big launches
I like shipping in small pieces we can look at together and easily undo. Every step teaches us something, and it makes mistakes a lot less scary.
Prototypes over presentations
When we're stuck on an idea, I like to build a rough version and try it. It's usually quicker than another meeting, and much more fun to talk about.
A clear no over a maybe
Saying yes to everything means doing nothing especially well. I try to be upfront about what we can't take on right now, and explain why.
Context over control
I try to share the why and the goal, then get out of the way. The people closest to the work usually find a better how than I would have.
Trust first
I start from trust and assume everyone's doing their best. When something goes wrong, we look at what let it happen, not at who to blame.
Working on something interesting?
I am always happy to talk about systems, architecture, or a problem you are stuck on.
