Hi. I'm George.

My career started in telecommunications, specifically the infrastructure that made deregulation work. In the mid-1990s, the Telecommunications Act of 1996 required incumbent local exchange carriers to open their networks to competitors. This wasn't theoretical—it meant building the actual systems that enabled competitors to exchange data, route calls, and operate reliably inside regulatory frameworks. I engineered EDI test beds and interoperability frameworks that made this possible.

This work taught me something foundational: complex institutional systems don't fail because of lack of capability. They fail because disparate parties can't reliably exchange information and intent. That lesson never left me. It showed up in mobile banking. It showed up in institutional trust operations. It shows up right now in how organizations integrate AI tools into their workflows. Technology changes. The architecture principle—making disparate systems talk reliably—doesn't.

Around 2011–2012, I discovered the Android development community. I was working a day job building automated testing systems for an e-commerce solution provider, and I was bored. I attended Startup Weekend events—entrepreneurial hackathons that brought together people trying to build something real in a weekend—and found my people.

In 2012, I co-founded Rheti, a platform-as-a-service tool designed to let non-technical users build Android applications from their phones without deep coding knowledge. The idea was ambitious: move the friction of app development far enough left that anyone could do it. The engineering challenge was equally ambitious: figure out which development tools are essential for a novice user, then make them intuitive on a 4-inch mobile screen. We lost the battle (building a dev environment on a small mobile screen is genuinely hard), but I won something else: clarity on where mobile development was heading and why native development mattered.

I also built ParkingBrain, a commuter utility for BART stations in the San Francisco Bay Area, as a practical example of when platform-agnostic tools make sense versus when native development is necessary. This work led to recognition within the Android developer community—I won the Phandroid Developer Appreciation Contest in 2012, which earned me a ticket to Google I/O 2012, Google's annual developer conference. It wasn't a household name thing, but in the community I cared about, it meant something. I had been recognized as a top-tier innovator for architecting a pioneering "app-to-build-apps" platform.

In 2012, I moved from Miami Beach to Silicon Valley full-time to pursue Rheti. The startup didn't take off (everyone involved had outside commitments—school, other startups, day jobs—and you can't will a complex product into existence on weekends). But I had found my obsession: how do you move friction out of systems, and where does capability emerge?

In the era when major financial institutions were realizing that mobile wasn't a feature—it was the future—U.S. Bank was one of the first to move seriously. I joined as Mobile Development Manager, tasked with translating platform innovation into institutional mobile banking architecture. This wasn't about building the next slick app. It was about defining the systems that would govern how millions of people banked through their phones.

A 2010 American Banker article from the period captures what U.S. Bank was trying to accomplish: mobile P2P payments, mobile remote deposit capture (take a picture of a check, deposit it from your phone—revolutionary at the time), location-based coupon delivery, Micro-SD-based payments. These weren't toys. They were institutional commitments to moving core banking functionality to mobile.

My role was to lead the architecture that would make this reliable and scalable. I architected the infrastructure that defined the first era of native mobile finance at a major American bank. That meant thinking through security, throughput, user experience under constraints, and how to release features reliably at speed. This was institutional rigor meeting technical velocity—exactly the principle I'd learned in telecom.

The work taught me how to move large institutions. You don't change culture by declarations. You change it by shipping reliable systems that prove new ways of working are possible.

At JPMorgan Chase, I worked in the Online Banking Division as a Mobile Web Developer, building Business and Corporate banking solutions. This was serious institutional work—the kinds of systems that businesses rely on to move money and manage operations at scale. I didn't just write code. I solved genuinely tough problems that others couldn't crack. I was the person you called when the question was hard and the stakes were high.

I took on leadership roles beyond the typical developer track: Agile Lead, driving how teams shipped features reliably; Diversity Ambassador, because the work of building inclusive teams matters; and I was active in Toastmasters, because clarity in communication is non-negotiable when you're coordinating complex work.

I also dove deep into Data Ontologies—mapping the web of data fields and capabilities against the full scope of what the system could do. This is architectural thinking, not just coding. You have to understand the entire landscape of your data before you can build reliably on top of it.

Beyond the day-to-day work, I participated in Crypto Innovation discussions—JPMorgan was exploring where blockchain and cryptocurrency fit into institutional finance, and I was part of those early conversations. This connected my telecom interoperability roots to the decentralized systems I'd work on later.

I worked with Destination Reward, building test automation systems for companies that powered consumer-facing web experiences. Destination Reward's platform was the backbone for web experiences at major brands like Hertz and Coca-Cola—the kinds of platforms where a system failure costs serious money and erodes customer confidence.

My focus was eliminating testing bottlenecks. There was a multi-week manual testing task that was blocking releases and slowing down the entire engineering organization. I automated it. The same work that used to take weeks could now be done in hours. That's the velocity principle in action: identify the bottleneck, move predictable work into reliable systems, and move people to solve the hard problems nobody else can solve.

This engagement reinforced something I already knew: in any complex operation, the constraint is usually not capability. It's friction. Remove the friction, and capability emerges.

Over the last decade, I've worked in interim and fractional leadership roles focused on organizational transformation. This is where the architecture principle meets human systems. I work with teams to establish sustainable, predictable delivery cadences—meaning: how do we ship things reliably, how do we move fast without burning people out, and how do we know when something's working.

I facilitate cross-functional engineering teams, identify delivery bottlenecks (often institutional, not technical), and reengineering workflows around Agile principles. The goal is always the same: velocity by design. Remove what's not serving you. Automate what's predictable. Move people to the work only they can do.

I work with small and medium-sized businesses solving their most pressing workflow constraints. A few hours with me—a clarity session—and they have a clear path forward they can own and execute. I identify the bottleneck, eliminate the friction, and create velocity. These engagements often lead to deeper consulting relationships, but the initial clarity is what matters: helping business owners and leaders see what's possible and move from stuck to moving.

I lead the AI Collective chapter here in Playa del Carmen. AI Collective is a major global community focused on AI literacy, governance, and practical application. As Chapter Lead, I'm responsible for bringing significant speakers and thought leadership to our local community, building peer networks, and creating a hub where people can actually understand AI beyond the hype. This is serious community work—not side project, but leadership responsibility.

Last summer, I taught at AI Summer Camp, run by SAS Academy International in Playa del Carmen, working with students ages 12–17. This was a rewarding challenge in rigor—getting to work with bright young people who are growing up in an AI-first world. Decoding complexity and helping them understand the technology, not fear it. To see possibility, not complexity.

Most people assume tech anxiety is about not understanding the tools. It's not. It's about a loss of control when confronted with rapid change. I work with accomplished professionals who feel genuinely overwhelmed—and I restore their ability to move forward.

I also facilitate Vibe Coding sessions—practical AI automation workshops for expats and locals in the community. Hands-on, supportive, for people who want to learn without the overwhelm.