The Five Layers
A career that looks like a zigzag can actually be the same move, repeated.
A genomics company: engagement engine underneath the heritage story
A fintech platform: settlement infrastructure underneath the democratization story.
A cybersecurity company: network fabric underneath the security story.
A work management platform: coordination graph underneath the task management story.
My own company: semiotic architecture underneath the self-knowledge story.
Five companies. One move: find the layer nobody built, build it.
The domain changes. The move doesn't.
My career reads as a zigzag. Genomics, fintech, cybersecurity, work management, identity measurement. Five domains in eight years, plus 18 months of solo founding. Every recruiter's database query bounces off this profile. It doesn't fit a lane.
The conventional read: restless. Can't commit. Domain-hopper.
I used to believe that read. I used to apologize for it in interviews. “I know it looks scattered, but...” and then I’d try to smooth the line, make it look intentional, narrate a through-line that felt like it belonged on a resume instead of a corkboard.
Then I stopped apologizing and started looking at what I’d actually done.
The layer underneath
At the genomics company, the surface product was a heritage story. DNA kits. Family trees. The thing you buy your parents for Christmas. I built an MVP that turned raw genetic data into something a person could look at and feel something. People don’t just want their data. They want their data to mean something.
I wasn't building the heritage story. I was building the engagement engine underneath it.
At the fintech platform, the surface product was democratized trading. The app everyone downloaded in 2021. I worked on the tax infrastructure, the part nobody talks about at parties. Millions of users, right before IPO. Every edge case has a regulatory body watching.
I wasn't building the trading story. I was building the settlement infrastructure underneath it.
At the cybersecurity company, the surface product was network protection. CDN. DDoS mitigation. I was brought in for a category that didn’t exist yet: monitoring what users actually experienced, not just what servers reported. I defined the product, built the business case, shipped it across multiple programming languages and engineering teams. Concept to product-market fit in one quarter.
I wasn't building the security story. I was building the observability fabric underneath it.
At the work management platform, the surface product was task tracking. The tool your team argues about in Slack. The company was shifting from product-led growth to enterprise, but nobody had named the enterprise persona. I found the gap. Built a segmentation framework from scratch. Identified a persona that nobody had articulated. Drove the decision that redirected the team's roadmap.
I wasn't building the task management story. I was building the coordination graph underneath it.
The pattern + progression
SURFACE ·············································· DEEP
Engagement Settlement Observability
layer layer layer
(product) (infrastructure) (meta-infra)
· · ·
You can see it You can't see The tool that
in the app. it, but you'd watches the
notice if infrastructure.
it broke.
Coordination Semiotic
layer layer
(org intel) (identity infra)
· ·
The system The substrate
underneath underneath
the system the person
people use. operating all
the others.Each time: arrive in a new domain. Spend weeks listening, asking questions, exploring the product. Identify the layer that makes the surface work — the one nobody built, the one nobody named, the one that's invisible until someone points at it.
Build it. Ship it. Watch the surface above it work better. Then the domain changes and the move happens again.
The layers get deeper each time. Not bigger. Deeper.
Genomics: engagement layer — product surface. You can see it in the app.
Fintech: settlement layer — infrastructure. You can't see it, but you'd notice if it broke.
Cybersecurity: observability layer — meta-infrastructure. The tool that watches the infrastructure.
Work management: coordination layer — organizational intelligence. The system underneath the system that people use.
Identity: semiotic layer — identity infrastructure. The substrate underneath the person operating all the other systems.
Each one is further from the visible surface and closer to the thing that actually determines whether everything above it works.
The fifth play
The fifth play. The surface is inner life — coherence, self-knowledge, the states you can feel but can't name. The layer underneath is a semiotic architecture for identity measurement. Twelve bounded AI agents that disagree by design. A correction loop where the user teaching the system IS the product. A coherence model that tracks seven factors over time and shows you your trajectory, not your score.
The non-obvious finding: people come back to measure, not to talk. Structured daily measurement retains at twice the rate of open-ended AI conversation. The model is commodity. The context architecture is the moat.
But here’s the thing I only saw after mapping the pattern across all five: the product I’m building IS the layer I keep finding. At every company, I found the invisible infrastructure that makes the surface work. Here, the invisible infrastructure is the self.
A founder I met recently said it simply: Your startup is a derivative of who you are. If that’s true, then a career that looks like a zigzag is the same derivative, computed five times. The output changes. The function doesn’t.
The hiring manager sees a zigzag. The database query returns "senior PM, AI, multiple domains, short tenures." The conventional career coaching says: pick a lane.
But the lane was always the same. The lane is underneath. The lane is the thing nobody built until someone walked in, looked around, asked the right questions, and said: there's a layer missing here.
That's what a career looks like when you stop narrating it as a zigzag and start reading it as a pattern.