I have been inside the systems. I know what they cost.

There is a version of this page that lists certifications and keyword stacks. This is not that page.

I have spent twenty years inside some of the most demanding technology environments on earth: Amazon, Microsoft, three CTO roles, and a consulting firm I built from nothing. I have owned roadmaps across 100 engineers, 20 teams, and 66 countries, rebuilt platforms on fire, advised C-suites, and managed the kind of complexity that does not show up cleanly in a slide deck.

What I have learned in that time is not primarily technical. The technical part is table stakes. What I have actually learned is how organizations work, how they fail, and what it takes to build the frameworks that let them function at scale without the constant overhead of chaos.

I built and operated the delivery infrastructure that governed a $1.4B technology organization at Amazon. The only Principal TPM in a 3,000-person organization. The operating model I built governed a $70M engineering organization spanning 20 teams, 100+ engineers, 11 business domains, and 66 countries, while driving program strategy and delivery standards across the full enterprise. That operating model governed the delivery of $100M in annual automation savings. It did not exist before I built it.

My job was not to have all the answers. It was to build the operating system that let the people around me find them, move fast, and stay aligned while doing it.

I served as the virtual CTO and senior technology advisor to the largest for-profit healthcare company in the United States. I translated complex technology strategy into multi-year transformation roadmaps and drove them to execution, including the largest Healthcare Enterprise Agreement in Microsoft history, exceeding $268M.

I did not just sell technology. I owned the strategy, the relationships, and the outcomes at the C-suite level.

Anytime Telehealth

I walked into a telehealth platform cratering under load during COVID and scaled it to 5,000% growth in sixty days. The system was unstable, the technical debt was severe, and the infrastructure was not built for the demand it was facing.

Mike Ross Consulting

Fifteen years founding and operating technology consulting practices across healthcare, finance, government, and cloud-native platform delivery. Three times, I was the CTO. Three times, I also built the company.

These are not listed to impress. They are listed because the pattern across all of them is the same: organizations brought me in when the complexity had outgrown the current system. My job was to build a better one.

Beyond the work.

I also write and build frameworks under the name Ross Charles. The work at rosscharles.net sits at the intersection of trauma science, attachment theory, and twenty years of watching what sustained pressure does to the people operating inside demanding systems, including me.

The Identity Pattern Framework, which powers the yourpatternmap.com assessment, came out of that work. Leaders who encounter it tend to describe it as the most clarifying lens they have found, both for themselves and for the teams they lead.

I mention it here because the frameworks I build professionally and the frameworks I build personally come from the same instinct: that most of what we call dysfunction has a reason, and naming the reason is where real change starts.

Based in Nashville, TN. Available for fractional CTO engagements, consulting, advisory roles, and speaking. PE firms and portfolio companies welcome.