I'm the engineer who spent 8 years at Google Cloud in the room with companies like Home Depot, Nokia, Sabre, and Panera while they made their hardest platform decisions. Now I bring that judgment to established operators whose revenue runs through software their team can't fix or replace. And I still open the code.
How I Got Here
I've been building technology for 28 years. Started writing code, grew into architecture, and eventually into the leadership roles where you're responsible for the decisions that compound, the ones that either accelerate your organization or quietly constrain it for years.
At Google Cloud, I spent 8 years working with enterprise engineering teams on their most complex challenges: cloud migrations at retail scale, platform rebuilds for telecom infrastructure, deployment tooling that had to work in the real world. I co-created products like Cloud Deploy by working directly with the customers who would use them, which taught me something consulting never could, what actually works when the pressure is on.
I founded Nebari because I kept meeting the same company: an established business, real revenue, and that revenue flowing through a system that's breaking, aging out, or beyond the people left to run it. Often the person who understood it just walked out the door. What those companies need is a CTO who can lead the function and also sit down in the codebase, and that combination is hard to hire and expensive to get full time.
What Makes This Different
Plenty of fractional CTOs will diagnose your situation and hand you a plan. The diagnosis is real, and then your team still can't execute it, because the team was the constraint in the first place. My engagements go further: I remediate the live system, lead the rebuild while the old system keeps earning, and when you need engineers under that leadership, I source and manage them myself.
Every engagement starts with an assessment grounded in your actual code, with every finding placed on the path your revenue takes through the system. I'll tell you what's working, what isn't, and what will hurt you in 18 months if you don't address it now. Then, if you want the fixing handled rather than just mapped, I'm in it with you.
How I Use AI
I use AI heavily in delivery because it lets a small senior team move at a pace that used to take a department. The KeyBank engagement, implementing AI-enhanced SDLC in a regulated financial services environment, shows what that looks like done responsibly. What you buy from me is working software, a stable system, and a technology function that runs. AI is how we get there fast.
Certifications
- Google Cloud Professional Cloud Architect
- AWS Solutions Architect
Community
I'm an active member of 7CTOs and CTOx peer networks, communities of technology leaders who share the reality of the job, not the LinkedIn version of it.
Let's Talk
If money is moving through a system you no longer trust, or the person who understood it just left, or someone is pitching you a rebuild you can't evaluate, I'd like to hear about it.