Solutions Engineering · Cloud · Technical Advisory
I help customers and technical teams turn ambiguous infrastructure constraints into decisions they can understand, trust, and act on.
Finding the constraint a customer actually has, which is usually not the one written in the requirements.
Laying out what each option costs later — in operational load, and in the freedom it removes from the next team.
Building the foundation so the next engineer extends it rather than routes around it.
Senior cloud & DevOps engineer, enterprise software
Built a parameterized infrastructure-as-code pattern (AWS CloudFormation) that multiple customer environments were instantiated from — a foundation later engineers extended rather than replaced. Alongside it, a multi-account production AWS estate: networking, compute, managed databases, containers, IAM, designed with recovery in mind.
Two decades of client-facing technical work, before moving in-house
Small businesses and professional offices, one unfamiliar environment after another — infrastructure, networks, web, support. Different industry every time, different constraints, same job: work out what actually matters here, then leave the owner able to run it. The customer-facing part was never a side of the work; it was the work.
Written for engineering and non-engineering decision-makers
Authored a business case that translated a technical modernization — trunk-based development and CI/CD — into a proposal non-engineers could evaluate and decide on. Earlier: UI development on regulatory compliance software, where the constraint was always what a non-specialist could be trusted to understand.
Ongoing, self-directed
I build and run my own AI tooling daily — agent workflows, retrieval, evaluation of whether the output is actually right. It has made me a careful reader of confident, well-formatted, wrong answers, which turns out to be the useful skill as these products reach customers.
Written August 2026
What I look for before choosing an architecture, which tradeoffs only show up after the first deployment, and why the handoff is a design constraint rather than a documentation task.
Senior, customer-facing technical work, remote. Discovery, technical presentation, weighing tradeoffs, and helping someone reach a decision they can stand behind.
Most recently, three years as a senior cloud and DevOps engineer building and running production AWS environments for enterprise software. Before that, roughly two decades of client-facing technical work across a lot of different industries, and earlier still, UI development on regulatory compliance software.
The technology changed constantly. The job did not: work out what actually matters in a system somebody else built, and leave the people who own it able to run it.
If you are hiring for a role like this, the best first step is a short message on LinkedIn.