I Read 40 Founder Biographies. My MBTI Type Made 37 of Them Useless.

The prompt-based system to find the founders whose brains are actually wired like yours.

10 min read

I love reading. Useful stuff, mostly. Founder biographies, specifically.

Yesterday at the beach (35 degrees in Arcachon, yes I'm aware), I asked myself what I actually take away from these books. Concretely. And the honest answer was: almost nothing.

Not because the books are bad. Because I was reading brains wired differently from mine. An INTJ who reads Branson walks away thinking extroversion is a prerequisite for building something. An INTP who reads Jobs collects quotes and changes nothing about their workflow. The cognitive mismatch turns lessons into entertainment. You admire, you don't absorb.

What if I picked my reading differently.

TLDR: I spent weeks reading founder biographies and came out with highlighted quotes, not changed decisions. The reason I finally figured out is simpler than I expected, and it completely changes which books you should open first.

Office worker overwhelmed by towering stack of rejected biography books with MBTI labels, while organized hero nearby holds just three books with a robotic lobster climbing the pile.
37 founder bios later, my personality type still can't predict success.

Reading the Wrong Founder Wastes Your Time

A thread from @OneJKMolina circulating on X put into words something I had been feeling without naming it: the founders worth reading are the ones who share your cognitive wiring, not the ones who are famous. Sounds obvious. Was not obvious to me after 40 books.

The mechanism is worth spelling out, because once you see it you can't unsee it. Every founder makes hundreds of decisions under uncertainty. The ones that end up in biographies are the high-stakes ones, the kind where there was no obvious right answer and someone picked one anyway. What makes those decisions replicable is not their content. It's the cognitive pattern underneath.

A founder who builds a complete mental model first and then commits very hard operates in a completely different mode from one who runs 6 fast experiments and bets on whatever feels most alive. Both can produce real outcomes. But if you're wired for the first pattern, reading 300 pages about the second one doesn't transfer anything. You build admiration for a style you're not built for. You take notes. You think you've learned something. You've watched a foreign film and assumed that following the plot was the same as speaking the language.

(Quick note on the MBTI skepticism I can already hear: valid. It doesn't hold up well under psychometric scrutiny. As a rough filter for a reading list, though, I think it's good enough. Close enough to point you toward the right cognitive neighborhood, even if the exact type is debatable.)

I have a stack of about 30 unread books on my desk right now. Most were bought because they appeared in some founder reading list tweet. Phil Libin's list. Sam Altman's list. Some hedge fund person whose name I already forgot. None of them sorted by anything cognitive. A random walk through other people's reading preferences, which is the default for most of us and probably explains why the self-help section keeps growing while average outcomes don't.

My kids wanted a paddleboard lesson while we were at the beach. I watched the instructor explain balance to my son for about 20 minutes, patient as anything, and my son couldn't get it. Then another kid who'd been surfing for 2 years got in the water and showed him. Same words, different body. My son stood up on the 2nd try. I have no point to make here. Just keep thinking about it.

Research in organizational psychology backs the core idea. Alignment between cognitive style and working patterns predicts long-term performance more reliably than industry context alone. The same logic applies to how you absorb a founder's story. When the decision-making pattern is mismatched, the biography is inspiring and not usable.

Take the Bill Gates reading method. Think Week, annotated books, a serious volume of reading per year. A genuinely interesting system. Built for a specific cognitive profile, one that synthesizes across very different domains, holds contradictions in suspension for a long time, and builds comprehensive models before committing to anything. If you're not wired that way, learning the Gates method is like learning a chess grandmaster's intuition by memorizing their past games. You follow the moves. The intuition doesn't transfer.

Stop Googling. Run This Prompt Instead.

Type "best books for founders" into any search engine. The results are the same everywhere: Zero to One, The Hard Thing About Hard Things, Shoe Dog. All solid. All built for or about specific cognitive profiles that may not be yours.

Here's the prompt I run in Claude instead:

I am a [MBTI TYPE] building [type of product / at stage / in domain]. I tend to
get stuck on [specific recurring problem: shipping / prioritizing / delegating /
staying motivated]. Suggest 5 founders or builders, including at least one
underrated name, whose documented experience directly addresses this pattern.
For each, specify the best primary source to read (book, interview, essay, or
talk) and the specific chapter or segment most relevant to my problem.

What makes this different from a search is the intersection of 3 variables: your cognitive type, your specific friction point, and the requirement for a precise source rather than just a title. That last constraint matters most. It forces the model past the bestseller list into territory that's actually relevant to the problem you're stuck on.

For an INTP dealing with "I over-engineer and never ship," the output looks something like this:

Jason Fried (Basecamp). Commonly associated with INTP patterns by the builder community. Primary source: Rework, chapters "Enough" and "Start at the Epicenter." Directly addresses the loop of over-building before shipping.

Pieter Levels (levels.io). No book. His essay "How I Build My Minimum Viable Products" is probably the most honest documented account of an INTP who broke the over-engineering habit. He never appears on a default list. The prompt surfaces him only when you require an underrated name explicitly.

Joel Spolsky. Joel on Software, specifically "Painless Software Schedules." Not glamorous. Written by someone who spent years thinking about the gap between "done in my head" and "actually shipped."

Amy Hoy. Less known than the others. Her "stacking the bricks" framework, documented in detail on stackingthebricks.com, is built specifically for builders who overthink the product before selling anything. Rarely appears in any founder recommendation list.

Justin Jackson (Transistor.fm). His podcast "Build Your SaaS," especially episodes from the first 2 years of building Transistor, is more useful than most books for this exact pattern. He narrates the over-engineering impulse in real time, not in retrospect.

Compare that to a standard search. The lists don't overlap.

If you want to apply what you learn from those founders to actually shipping a first real product, Vibe Coding, For Real is the method I built for builders at exactly that stage. Free on Kindle Unlimited.

The same logic of structured inputs over vibing your questions is what I eventually turned into a structured prompt contracts approach after enough rounds of getting generic output from Claude by asking generic things.

4 Cognitive Profiles, 4 Different Reading Lists

TITLE "4 Builder Profiles, 4 Reading Strategies" + subtitle "Match your cognitive wiring to the right founder". Metaphor: a workshop with 4 distinct workbenches, each set up with different tools and work-in-progress. Style: Franco-Belgian ligne claire comic, thick black outlines, flat color fills, slight grain texture on walls. Palette: mustard #F4C430, brick red #C0392B, slate blue #2C3E50, cream #FFF8E7, black #111111. Content: top-left workbench labeled "LONG-GAME ARCHITECT / INTJ-ISTJ" with blueprints rolled out and a ruler; top-right "ABSTRACT MAPPER / INTP-INFJ" with index cards spread across the surface; bottom-left "PROLIFIC EXECUTOR / ENTP-ENTJ" with a half-built prototype and scattered tools; bottom-right "HUMAN BUILDER / ENFP-ENFJ" with sticky notes and user persona sketches pinned to the wall. Highlight: each bench label in a mustard-colored tag, founder name examples appear as small polaroid-style sketches pinned above each station. Footer: copyright rentierdigital.xyz. NOT flat corporate vector, NOT management consulting quadrant grid, NOT minimalist tech startup aesthetic.
Four Builder Profiles and Their Reading Strategies

MBTI has 16 types. The tech builder community maps reasonably well onto 4 clusters. Think of these as cognitive neighborhoods, not personality diagnoses. The founder typings below are what the community commonly associates with each profile, via aggregators like Personality Database. Not official. Not confirmed. Close enough to be useful. And if a profile doesn't resonate, try the adjacent type before deciding the whole thing is useless.

The long-game architect (INTJ / ISTJ)

Picture a builder who writes the database schema before the first feature is scoped. Who has opinions about folder structure before there's any code in the folder. Who feels genuinely uncomfortable pressing deploy without a plan for the 3 failure modes that could happen next week.

The documented recurring problem for this profile, across hundreds of indie hacker threads: the architecture is never quite ready enough. The system gets refined. The ship date moves. Zuckerberg and Thiel are commonly typed in this cluster.

What to look for in their biographies is not the vision. Everyone in a founder bio has vision. Look for the stop decision: at what point did they decide the system was good enough to ship. The chapter where planning ends and committing begins. That specific moment is the transferable lesson. The rest is biography.

Prompt: "I tend to over-architect before shipping. Suggest 3 builders commonly associated with INTJ or ISTJ patterns who documented how they broke this loop."

The abstract mapper (INTP / INFJ)

The honest version of what this profile looks like from the inside: you're not stuck. You have too many good ideas and picking one feels like killing the others. The exploration-to-commitment gap has nothing to do with motivation. It's a selection problem, and those are 2 very different diagnoses that lead to completely different reading lists. Gates is commonly typed in this cluster.

Most content written for this profile focuses on the wrong side. It tells you how to generate better ideas. You don't need that. What to look for in the right biography is how a founder with this wiring decided which idea to actually pursue, then stayed committed long enough to ship it. The chapter you're looking for is usually not the famous one. It's the one where the options narrowed, not where the vision expanded.

Prompt: "I generate ideas faster than I ship. Suggest 3 builders associated with INTP or INFJ patterns who specifically addressed the selection and commitment problem."

The prolific executor (ENTP / ENTJ)

Start with the result: this profile ships things. Real things, frequently. The problem arrives around week 4 of any given project, when the hard part isn't interesting anymore and something new has become very interesting. Jobs and Andreessen are commonly typed in this cluster.

Reading their biographies as an executor yourself is useful for exactly 1 reason. Not the energy (you have that). Not the vision (you have that too). The only thing worth extracting is the constraint architecture. What did they put in place to force completion instead of perpetual iteration. What personal rules, external commitments, or structural decisions made finishing more probable than starting something else.

The same instinct explains why this profile naturally gravitates toward lightweight CLI pipelines over heavier framework abstractions: direct-line tools for direct-line thinkers.

Prompt: "I start many projects and struggle to finish them. Suggest 3 builders associated with ENTP or ENTJ patterns who documented how they solved their own follow-through problem."

The human builder (ENFP / ENFJ)

The product is good. Users love it. The roadmap is 3 times longer than it should be because saying no to a feature request from someone who clearly needs it feels like a moral failure. Chesky at Airbnb is commonly typed in this cluster.

The before-and-after to look for in the right biography: the moment this type of founder learned to hold the line on product focus without losing the user-closeness that made the product worth using in the first place. That's a very specific skill, and most founder bios don't even name it explicitly. It's buried in the chapter about a painful pivot, or a product decision that made early users angry for a quarter and loyal for a decade.

The general "learn to say no" lesson misses it entirely. You're not looking for permission to say no. You're looking for the framework that made saying no feel like protecting the product rather than abandoning the user.

Prompt: "I struggle to say no to user requests and lose product focus. Suggest 3 builders associated with ENFP or ENFJ patterns who documented how they held focus without losing their product's soul."

Find Your Type in 5 Minutes

16personalities.com. Free. Takes about 12 minutes.

1 thing most people get wrong: answer based on how you actually behave, not how you want to behave or how you perform on a good week. The test reflects your idealized self if you let it. Most people score more extroverted and more organized than they really are, because those patterns feel more productive when you're filling out a self-assessment.

There's a specific tell: if every answer feels comfortable and obvious, you're probably describing your aspirational self, not your operating self. Answer what's true under normal conditions, not best-case conditions.

If you land on the border between 2 types and can't decide, run this in Claude:

Ask me 10 targeted questions to distinguish between [TYPE A] and [TYPE B].
Focus on decision-making patterns and energy management, not abstract preferences.

Around question 5 or 6, you'll typically know. The 2 types usually diverge sharply on 1 or 2 specific scenarios, and your reaction is hard to fake, even to yourself.

Then plug your type and your specific blocker into the prompt, and run it. The goal isn't a perfect typing. It's enough directional signal to stop reading founder biographies selected by algorithm and start reading ones selected by cognitive proximity. You might surface 1 name from the output you'd never have found otherwise. That's already more than 37 biographies gave me at the beach.

Maybe I'm wrong that the type matters as much as I'm saying it does. But the pattern is consistent enough across my own reading list that it stopped feeling like a coincidence: the books where I changed something afterward were almost always books where the founder's decision-making style felt familiar. Not aspirational. Familiar.


Most people who read founder biographies are looking for inspiration. They find it. Monday arrives and they build exactly like before, same blockers.

Watching someone else navigate their decisions doesn't give you theirs. It gives you admiration for theirs.

Find a founder wired like you. Read how they bugged out. Not how they won. Your beach days will never be the same. 😎

Sources

  • @OneJKMolina thread on X: x.com/OneJKMolina. The post that sparked this.
  • "MBTI Types in Technology Careers: Who Thrives Where," ordinaryintrovert.com (April 2026)
  • Founder typings: personality-database.com
  • Free MBTI test: 16personalities.com
  • "What's the best finance career for your personality type?" Wall Street Oasis, YouTube
  • "How Bill Gates reads books," Quartz, YouTube

This post may contain affiliate links. If you click them, I might earn a small commission. Costs you nothing, and helps me keep shipping quality articles every day for your reading pleasure.


Most founder advice doesn't stick because you're reading brains wired differently from yours. The demo-vs-product checklist in the welcome kit shows you the same filter: match your cognitive pattern to the framework, not the hype.

→ Get the welcome kit