Fractional Architect
Technical leadership without full-time overhead.
I partner with CTOs, engineering managers, and teams to connect strategy, architecture, and execution.
Core Expertise
01
Grounded Architecture & Connected Engineering
Bridging strategy, architecture, and code I help you build, or oil, the machine that builds your machine. I move comfortably between system design, teams, and code. I connect abstract principles or requirements with reality, for example, by linking decisions with verification criteria or turning a requirement into an executable specification.
02
Delivery & Developer Experience
Ship software more efficiently and more effectively. I help teams turn big, risky releases into a steady flow of changes. This can mean iterating development or QA/QC processes, tightening feedback loops with executable specifications, using AI to remove friction around engineering work or adjusting team structure and responsibilities so work can move without constant handoffs.
03
Technical Leadership Advisory
A thinking partner for technical leadership decisions. I work alongside CTOs and engineering leads as a sparring partner: architectural decision making, aligning technical direction with business strategy, and helping navigate team scaling challenges. Sometimes that's a second opinion, sometimes it's working through slow delivery challenges or preparing for a conversation about tech debt priorities.
04
Secure Software Development
Security and compliance built into how you develop. Drawing on experience in high-compliance environments, I help you design secure-by-default architectures and processes.
Work with me
If you think I might be a good fit for your team or product, send a short email. As conversation starter, tell me about where you are today and what you're trying to change. I will reply as soon as possible.
Related articles
-
What caught my attention in the book Vibe Coding by Gene Kim and Steve Yegge is the idea that, as LLMs and coding agents change how we build software, control loops—tests, reviews, and other signals that tell you whether a change behaves as expected—should be faster and more inte…
-
This post captures my current thinking on how LLMs are impacting software development, particularly around software quality and engineering discipline. My main observation: most of the best practices we've relied on for years are just as important—maybe even more so—in an LLM-ass…
-
If you've read some of my posts before or worked with me, you know I like using Architectural Decision Records (ADRs) for lots of reasons. To me the most important one is documenting the why of a decision. If you've worked with AI models before, you've probably asked them for opt…
-
Making architectural decisions is one thing, but have you ever wondered how to make them more effective? Adding a Verification section to Architecture Decision Records (ADRs) can make the difference. This simple addition bridges the gap between theory and practice, making decisio…
-
Teams adopt Architecture Decision Records (ADRs) to document decisions, avoid revisiting settled matters, onboard newcomers, adapt to changing circumstances, and sharpen their thinking. However, there are several other valuable benefits that often go unnoticed. A clear decision p…