AI-native qualifier

Find your future-role archetype.

This survey checks the required AI-first baseline for all roles, then scores how you naturally contribute across Prototyper, Builder, Sweeper, Grower, and Maintainer modes.

Required AI-first baseline

These are minimum requirements before archetype scoring is considered.

0/4

I use AI tools every working day to research, design, write, code, analyze, automate, or operate.I can show concrete examples of work I shipped or improved with AI in the loop.I am comfortable owning outcomes that cross traditional product, engineering, design, data, growth, or operations boundaries.I understand that AI-native work still requires taste, verification, security judgment, and human accountability.

01 · Prototyper

I regularly create multiple divergent concepts before choosing what deserves investment.

02 · Prototyper

I am comfortable discarding most explorations once the signal says they should not ship.

03 · Prototyper

I can turn ambiguous opportunities into believable demos, workflows, or proofs quickly.

04 · Builder

I can convert a promising prototype into a durable product, workflow, integration, or system.

05 · Builder

I care about implementation details enough to make the shipped version stable and useful.

06 · Builder

I can define clean handoffs between people, tools, data, automations, and approvals.

07 · Sweeper

I naturally remove clutter, consolidate duplicate logic, simplify UI, and reduce process drag.

08 · Sweeper

I am willing to unship, prune, or redesign work when the system is clearer without it.

09 · Sweeper

I notice performance, cost, accessibility, maintainability, and usability issues before they compound.

10 · Grower

I use customer or user signal to improve adoption, retention, conversion, or product-market fit.

11 · Grower

I can design practical experiments that clarify what a market, team, or workflow actually values.

12 · Grower

I can sharpen positioning, onboarding, activation, or usage loops after a product is already working.

13 · Maintainer

I take ownership of mature systems so they stay reliable, secure, observable, and efficient.

14 · Maintainer

I think about permissions, data quality, runbooks, monitoring, failure modes, and scale early.

15 · Maintainer

I can improve an existing system patiently without needing every project to be net-new.

Progress: 0/15 scored · AI baseline pending