The product's actual stage — early, growth, or mature — is, per Shreyas Doshi, the single most important fit factor when hiring a product leader. A candidate's resume pedigree (e.g. having scaled a mature product) does not guarantee fit for a different stage.
Founders often over-delegate everything to a newly hired head of product on the assumption that this is simply "what good managers do." The new hire — frequently coming from a mature company — imports operational assumptions calibrated to that stage: OKR systems, review cadences, staffing norms. Those assumptions are mismatched when applied to an earlier-stage product, where the actual need is different (e.g. more hands-on craft, less process).
Stage need and leader archetype are meant to be matched deliberately, not left to whatever a search firm's pedigree filter surfaces: see Product Leadership Archetypes: Operator, Craftsperson, Visionary for the three leader types, and Diagnostics for Reading a Candidate's Product-Leadership Archetype for how to detect the mismatch during hiring rather than after. This stage-mismatch is a major contributor to the failure rate in Head-of-Product Hiring Failure Base Rate.
A brand-name resume built at a mature, scaling product is not a safe default hire — it can be a liability if that leader is placed at a product's inflection point without deliberate planning for the mismatch. Years spent at mature-stage companies leave a leader with unconscious operational defaults — goal systems, review-meeting cadence, staffing norms — calibrated to a mature product's needs. Those defaults clash with what an earlier-stage product actually needs, independent of the leader's raw skill or seniority, which is why matching Product Leadership Archetypes: Operator, Craftsperson, Visionary to stage matters more than resume prestige.
Gibson Biddle's career-hacking framing sorts product leaders into three types by the company stage they thrive in: Starters (0-to-1, pre-product-market-fit), Builders (scaling a working product/market fit into a repeatable engine), and Super-Scalers (running product at massive, already-scaled organizations). The typology is a self-assessment tool for a leader picking their next role — the fit failure mode is a Starter joining a Super-Scaler expecting the same degrees of freedom, or a Super-Scaler joining a pre-PMF startup and over-processizing it before there's anything to scale. Compare to Product Leadership Archetypes: Operator, Craftsperson, Visionary (Operator/Craftsperson/Visionary), which sorts leaders by working style rather than by company stage.
For a Craftsperson specifically, the ideal target is a product or feature that has just hit product-market fit and is entering a high-growth phase — that's the stage where craftsperson skills (polish, refinement, quality) create the most value. Landing this window on demand isn't always possible; sometimes the only available role is a mismatch on paper. See Showcase Strengths in a Non-Ideal Role to Get Noticed for how that gap can still resolve favorably.
Doshi's heuristic for which archetype belongs at which stage: Visionaries fit zero-to-one/explore work, where creativity, big-picture thinking, and user empathy differentiate. Craftspersons fit the stage right after a product has hit product-market fit and enters high growth, where hands-on execution craft is most valuable. Operators fit neither zero-to-one nor early-growth work well — see Operator/Zero-to-One Mismatch — their strengths (process artifacts: OKRs, wikis, exec updates) apply best once a product is mature and running at scale. The point isn't to chase whichever stage is fashionable among PMs (0-to-1 work carries prestige) but to match the stage to your actual archetype.