Which Tech Role Fits You?

The question behind the question

Search “which tech role fits me” and you'll mostly find bootcamp quizzes. They ask six questions and — surprise — the answer is always a job their course happens to teach. That's lead generation, not an answer.

The honest version of the question is bigger than a job title. A technology wave — AI now, crypto before it, whatever comes next — is an ecosystem that needs a fixed set of functions filled: someone builds the technology, someone commercializes it, someone explains it, someone connects the people, someone funds it, someone negotiates its relationship with existing power. Those functions resolve into 23 recurring roles — and they recur so reliably across cycles (Linux, Bitcoin, Ethereum, AI) that you can study them like a map.

A job is something an employer defines. A role is a position in that ecosystem — and several of the 23 aren't jobs at all. Which is exactly why the bootcamp quizzes can't see them: there's no course to sell for “build a small product you own” or “become the person who curates the noise.”

The mistake: picking by identity instead of fit

Ask a developer which role fits them and the answer is usually “developer” — not because it fits, but because it's who they already are. The coder defaults to Developer even when their real edge is explaining (that's an Educator), or spotting what should be built (Product Manager), or shipping small products they own (Micro-Founder).

A blunt heuristic cuts through most of it: who decides what gets built next quarter?If it's you, you're a Product Manager. If you're convincing others to let it happen at all, you're a Bridge Builder. If you can fire the team, you're a Founder. The mismatch is expensive because roles demand very different pain tolerance, capital, time horizons, and skills — and you usually only find out mid-cycle, when switching costs the most.

What “fit” actually means

Fit is not “what are you good at.” Skills are the most learnable part of the equation. The parts that don't bend are behavioral:

• What energizes you— the work you'd do on a free Saturday, not the work you tolerate for a salary.
• What pain you can absorb— every role has a specific negative: rejection, obscurity, income gaps, killed projects. You don't escape pain by choosing well; you choose which pain.
• Your dispositions — niche vs. mass, autonomy vs. scale, solo depth vs. room energy.
• What you've actually done — track record and current skills, weighted least, because they change fastest.

On top of fit sits a fifth force that has nothing to do with you: timing. The same role pays completely differently depending on where the cycle stands — entering a hype-phase role at the peak means competing with a thousand people who started the same week. (Where the AI cycle stands right now is tracked on our hype-cycle page.)

The map: 23 roles in 7 categories

The full role descriptions live on the roles page— here's the territory at a glance:

Three questions that narrow it fast

1. What did a great Saturday look like, lately?Something you built finally worked → builder cluster. Someone finally understood a thing because of you → knowledge producer. Three people you introduced started something → network cluster. You spotted a mispricing → capital & markets.
2. Which bad day can you live with?Code that breaks at 2 a.m.? Publishing to twelve likes for a year? A deal dying after six months of work? Every role's downside is different — the one you can shrug off points at your role.
3. What do people already come to you for?Not what you'd like to be asked — what you actually get asked. Fixing the thing, explaining the thing, deciding the thing, or knowing who to call: four different roles.

Common mismatches (and what they cost)

• The developer whose edge is explaining. Stays heads-down in code while their real leverage — making complex things legible — goes unused. The cycle rewards them least of all their options.
• The organizer who never converts. Builds community and reputation for years — the classic build-up role — but never turns the accumulated social capital into an operator, founder, or investor position before the cycle turns.
• The functional expert who joined for the paycheck.“I work in the AI industry” is a job; “I have a position in the AI ecosystem” is a role. The first is replaceable and goes first in the bust.

FAQ