Secure Microsoft and Federal cloud architecture, from the whiteboard to production.

The architect who also writes the SOW and stays for delivery.

I am drawn to the difficult middle of enterprise technology: the hybrid identity that half works, the certificate authority nobody documented, the tenant migration with a hard cutover date and no room to slip. My job is to make those systems clear, secure, and boring in the best possible sense of the word.

I move comfortably between a boardroom and a PowerShell prompt. I can sit with an executive to scope risk, budget, and outcomes, then write the statement of work, draw the architecture, and stand up the build alongside the engineering team. Most architects are strong on one side of that line. I have made a career out of covering both.

That work has spanned Enterprise, Federal, Financial, and Non-Profit/Not-For-Profit environments, and a large part of it is teaching: turning a deep technical decision into plain language for an executive, and raising the engineers and associate architects who deliver alongside me.

What I care about most is leaving environments better than I found them: standardized runbooks that survive turnover, engineers who level up because I took the time to teach, and clients who trust the next recommendation because the last one held under pressure. I would rather be the person who delivered exactly what was scoped than the one who oversold and apologized.

The habits started early. I earned Eagle Scout after a thirteen-year run in Scouting, where my project organized twenty-five volunteers to plant fifty bald cypress trees for a City of Lakeland community park. The instinct is the same one I bring to architecture: plan it properly, bring people with you, and leave something that outlasts your involvement.