Customer-Facing Solutions Engineering · Cloud Infrastructure
I help people understand complex technical problems, identify what truly matters, and make decisions they can act on. My background spans a wide range of technologies and industries, from hardware and programming to building and troubleshooting systems. More recently, I’ve expanded into cloud infrastructure, DevOps, and automation, bringing the same practical, people-focused approach to increasingly complex systems.
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
I build software and infrastructure as code with care for the people who will maintain, extend, or repair it next. I aim to make what I build clear and dependable, so it can keep serving people no matter who works on it.
Two decades of client-facing technical work, before joining a software company
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.
Making technical change understandable to the people who need to act on it
I naturally look for ways to make complex technical choices clear to both the people building the system and the people responsible for its business impact. Whether the subject is software, infrastructure, or operations, I care that people can understand what’s changing, why it matters, and what they need to decide.
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.
I'm a translator. Most of my work happens between people who need the same picture and don't have it yet: engineers and the business, a customer and the team building for them.
I pay attention to what people show me as much as what they ask for, and help them sort out what they want from what they need. When things get chaotic, I'm usually the one making sense of it, calming the room and keeping the problem from growing.
I also bring ideas. A problem rarely gets solved with the same thinking that created it, so I go looking for a different angle. When a team needs something new, or a fresh take on something it already has, I add to the thinking and back the people doing it. I think of it as nitrous to the fuel: the engine is already running, I help it go.
Most recently, three years as a senior cloud and DevOps engineer building and running production AWS environments for enterprise software. Before that, approximately two decades of client-facing technical work across many different industries, and earlier still, UI development for regulatory compliance, webmastering, and multi-server email administration.
The technology changed constantly. The job did not: work out what actually matters in a system somebody else built, look after the customer, 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.