Tetrate
Making invisible infrastructure legible.
I joined Tetrate as a Content Engineer when the team was 30 people. My job was to turn highly complex networking concepts—service mesh, Istio, Envoy—into visual stories, games, and web interactions. I stayed until they crossed the 100-person mark, leaving with immense respect for what they build.
The Context
Here is something nobody warns you about when joining a hyper-growth infrastructure startup—the sheer velocity of the intellect in the room is both exhilarating and terrifying.
I joined Tetrate in a global remote capacity long before Covid made it the standard. We were building Tetrate Service Bridge (TSB) and Tetrate Service Enterprise (TSE), essentially the control planes for massive enterprise service meshes. If you aren't neck-deep in cloud-native architecture, that translates to: "We build the nervous system for enormous server farms."
The Work
My role was Content Engineering. Not marketing copy, but curriculum and technical translation. I produced videos, created PDF visualizers, and even prototyped web interactions and small games to help people understand what a packet does when it hits an Envoy proxy, and why multi-cluster topology matters.
If a technical concept cannot be explained with a physical metaphor, it isn't fully understood yet. So, I spent my days mapping complex access control policies (AuthN/AuthZ) and multi-tenant workspaces into visual narratives that engineers could actually digest without falling asleep at their keyboards.
The Departure
Eventually, the startup scaled past 100 employees, and the nature of the beast changed. To be brutally honest—and this is a reality we don't talk about enough in tech—I was fired.
The truth is, I simply wasn't contributing productively to the specific machinery the company needed at that scale. Sometimes a person and an organization grow in two entirely different directions. It stings, naturally, but it also provides a profound moment of clarity.
I left with an incredible respect for the engineers at Tetrate, the systems they continue to build, and the harsh but necessary lessons I learned about alignment, productivity, and finding where my own systems-thinking actually belongs.
The Core Lessons
Content Engineering
Explaining service mesh architecture isn't just about writing docs. It's about translating highly abstract infrastructure—Istio, Envoy—into mental models that actually stick. I made videos, games, and web interactions to bridge that gap.
Tetrate Service Bridge
A significant part of the work involved creating deep-dive visual content for Tetrate Service Bridge (TSB). From access control to multi-cluster topology, making the invisible visible.
The Pre-Covid Remote Era
Joined a globally distributed 30-person team before the pandemic made it cool. It was a masterclass in asynchronous communication, high-trust environments, and the sheer density of talent a startup can attract.
A Respectful Exit
I was let go as the company scaled past 100 people. I wasn't contributing productively to their evolving needs. It's a tough pill, but an invaluable lesson in alignment and owning your trajectory. Massive respect to the team.