1334 questions
Could not save this preference. Your choice applies only to this page.
Stage profile · Individual contributor
Creates sustained professional value in a critical domain or across teams, scaling impact through reusable practices and collaboration without assuming company-wide governance or formal succession duties.
Read these as observable expectations across repeated work, not as a checklist for a single project. First distinguish whether the role expects the work, whether the person had a chance to demonstrate it, and whether the evidence supports the claim. Lack of opportunity or evidence is not itself a negative judgment. AI use is judged by verified outcomes, sound boundaries, and the quality of decisions; choosing not to use AI can be sound.
These lenses and the A–H capability map answer different questions. One experience may provide evidence across lenses, but do not count the same result multiple times.
Understand the people served and intended outcomes, make evidence-based trade-offs, and verify contribution. For platform, infrastructure, reliability, and safety work, cost, efficiency, risk reduction, and internal-user outcomes count; direct revenue ownership is not universal.
Apply relevant knowledge to diagnose, design, implement or review, validate quality, and make evolution decisions. The professional leaves required depend on the role.
Help others work effectively through communication, coordination, review, shared methods, coaching, or organizational mechanisms. IC influence is not measured by direct reports; managers also own formal people responsibilities.
Observe questioning, reasoning, learning transfer, judgment updates, relationship handling, and recovery in work. This is not a fixed personality or potential verdict; do not infer it from extroversion, fluent speech, or willingness to overwork.
Use this structure to understand a real example. Strong judgment can appear in a failed project; a successful result alone does not prove personal causation.
The labels beside capability references describe that capability’s role in this standard; they do not make the whole standard optional. Any role or scenario condition is stated separately.
Evidence to inspect: Roadmap connects business measures, capability investment, and long-term cost.
Evidence to inspect: Decision states opportunity cost, downside scenarios, and evidence thresholds for further investment.
Evidence to inspect: Review shares definitions and attribution limits, assigns actions, and changes resource choices.
Evidence to inspect: Long-term goals connect to near-term investment through an adjustable plan.
Applies when: Assess the AI portion only when the investment includes AI or AI is an alternative.
Evidence to inspect: Compares maintenance, migration, adoption, and alternatives.
Evidence to inspect: Multiple teams adopt the approach and track quality, cost, and evolution outcomes.
Applies when: AI evaluation applies only to AI systems or risks within the actual responsibility.
Evidence to inspect: Reusable baselines, production monitoring, and clear human-intervention/rollback conditions exist.
Evidence to inspect: Consumers repeat less work and incidents, change cost, or complexity decline.
Applies when: Include AI work when relevant to the opportunity or risk; when it is not relevant, explain the technical or product basis.
Evidence to inspect: The roadmap explains cross-team dependencies, migration sequence, and acceptance standards.
Evidence to inspect: Key metrics, entities, and rules have owners and change mechanisms.
Evidence to inspect: Multiple people can independently own critical areas.
Evidence to inspect: Collaboration cycles or dependency risk improve sustainably and multiple teams adopt the mechanism.
Evidence to inspect: Team capability plans support the domain roadmap and verify backup coverage.
Evidence to inspect: Adoption, resistance, and improvement are tracked over time.
Evidence to inspect: Across decisions, risk is calibrated and views update in time, not only explained after the fact.
Evidence to inspect: Partners share bad news early and engage in difficult trade-offs.
Evidence to inspect: Decision records preserve original assumptions and updates for later teams to reuse.
Evidence to inspect: High-pressure decisions record boundaries, alternatives, and accountable owners.
