internal / QA — not linked from the main site
Persona previews
One synthetic persona per archetype, each built from that archetype's own target profile and run through the real assessment scoring pipeline (see docs/research/persona-suite-v1.md). Click a card to see the full dimension breakdown and every question/answer behind its score.
The Platonic Product Engineer
Generalist IC who ships features across the stack, wants moderate ownership and moderate ambiguity, and explicitly does not want to manage people or live in front of clients.
The Platform Builder
Builds the internal tooling and cloud infrastructure other engineers depend on; high systems-design orientation, genuine cloud/infra hands-on depth, low client-facing need.
The On-Call Owner
Lives for production reliability and incident response, high on-call appetite, SLO-driven, low interest in sales/teaching/public visibility.
The Pipeline Builder
Builds and operates data pipelines and warehouses feeding analytics/ML, real hands-on data-infrastructure depth, moderate systems-design scope, low client-facing need.
The Production ML Engineer
Ships production ML systems end-to-end (pipelines, APIs, monitoring), genuine hands-on ML experience, high ambiguity tolerance and outcome accountability, not a researcher.
The Mobile App Builder
Builds native or cross-platform mobile apps with real hands-on mobile-platform depth; otherwise a fairly standard IC profile, low client-facing and low management orientation.
The Firmware Engineer
Works at the hardware/software boundary with hard physical constraints as a daily reality (power, memory, real-time deadlines), low ambiguity tolerance, low client-facing need.
The Security Gatekeeper
Adversarial thinking is a default lens on every system, not an occasional checklist item; has actually sought out security-focused work, moderate-high on-call appetite.
The Technical Seller
Runs live discovery and POCs, genuinely energized by high-stakes client rooms, wants variable/commission-linked comp, low interest in deep hands-on-keyboard coding.
The Vendor-Side Architect
Deep single-product-stack technical advisor, comfortable with client/exec rooms, some variable comp appetite, moderate coding intensity — designs more than it ships.
The Consulting Architect
Multi-platform technical architect spanning bid work through delivery oversight across many concurrent client engagements, broad technical breadth over narrow depth, low people-management pull.
The Embedded Builder
Embeds long-term with one strategic account and personally ships production code into their environment — coding is 70-90% of the week, no sales quota, high travel/embed willingness.
The Ticket-Queue Debugger
Thrives on fast, interrupt-driven ticket resolution with crisp SLA targets; low ambiguity tolerance and low interest in open-ended architecture work, high debugging speed.
The Named-Account Owner
Owns a book of accounts on a scheduled cadence (QBRs, check-ins), wants one persistent long-term relationship over ticket-queue variety, genuinely enjoys teaching without wanting a public stage.
The Delivery Consultant
Billable, SOW-scoped hands-on implementation and integration work across many client engagements; high coding intensity but implementation-led, not design-led like an architect.
The Public-Stage Teacher
Genuinely wants the public stage — conference talks, content, community — not just 1:1 explaining; no sales quota, high ambiguity tolerance, low structured account ownership.
The People Manager
Wants to be judged entirely on team retention, morale, and growth rather than personal technical output; willing to give up hands-on coding almost entirely.
The Technical PM
Owns roadmap and architecture trade-off calls for a technical/infrastructure product; reads code and sits in ambiguity comfortably, but doesn't ship production code personally.