Was Framework/language fluency (5+ years with React, Python, etc.)
Now Cross-layer code review
Reading and challenging agent-generated changes across frontend, backend, and infrastructure without deferring whole layers to someone else.
Interactive Tool
Competency Evolution Explorer
See how each role's competencies transform in the AI era — what carries over, what's entirely new, and what's no longer relevant.
Traditional Role Software Engineer Frontend Engineer · Backend Engineer · Full-Stack Engineer AI-Era Role Product Engineer
From code producer to agent orchestrator and quality judge
3 Evolved
3 New Gaps
5 Sunset
Foundation you build on New areas to develop
50% existing foundation 50% new competencies
Evolved
Competencies that carry over — transformed
These build on your existing foundation. The core skill survives but the application, scope, and context change fundamentally.
Was Problem-solving and algorithm skills
Now Architectural judgment
Spotting when output violates established patterns, quietly accumulates tech debt, or introduces security and reliability risk.
Was REST API and database experience
Now System thinking
Tracing how a localized change propagates through dependencies, contracts, and operational behavior.
New Gaps
Entirely new competencies to develop
No traditional equivalent exists. These represent genuine skill gaps that require deliberate investment to close.
NEW Context engineering
Structuring prompts, rules files, and task plans so agents produce output that fits your standards on the first pass more often, and fails in predictable, recoverable ways when they do not.
NEW Quality evaluation at volume
Maintaining a high bar when reviewing code you did not write, without rubber-stamping or burning out on nitpicks.
NEW Product awareness
Asking whether the change solves the user's problem and meets the bar for shippable product, not only whether it compiles and passes tests.
Sunset
What we no longer screen for
These were reasonable signals in the pre-AI era. They are no longer reliable predictors of contribution in agent-augmented teams.
Whiteboard algorithm challenges disconnected from how the team actually ships
Arbitrary years-of-experience gates tied to specific framework versions
Raw speed of manual typing or line count as a proxy for seniority
Memorization of syntax or API surface area that documentation and agents retrieve instantly
Hyper-specialization in a single layer of the stack with no ability to reason across boundaries
Traditional Role Staff / Principal Engineer Staff Engineer · Principal Engineer · Solutions Architect AI-Era Role AI Architect
From the best individual coder to the architect of systems agents build within
4 Evolved
2 New Gaps
5 Sunset
Foundation you build on New areas to develop
67% existing foundation 33% new competencies
Evolved
Competencies that carry over — transformed
These build on your existing foundation. The core skill survives but the application, scope, and context change fundamentally.
Was Deep distributed systems expertise
Now System design mastery
Architect systems that treat AI agents as execution components inside explicit contracts, not as magic that replaces design.
Was Designing and shipping systems at scale
Now Failure mode thinking
Anticipate hallucination, scope drift, cost spirals, stale instructions, and ambiguous ownership; design detection and recovery into the architecture.
Was Track record of mentorship
Now Technical communication
Translate architecture into rules files, task boundaries, and instructions that both people and agents can execute without improvising structure.
Was Leading complex technical initiatives
Now Cross-domain judgment
Assess output quality and design risk across domains (backend, data, security, UX) when agents span them.
New Gaps
Entirely new competencies to develop
No traditional equivalent exists. These represent genuine skill gaps that require deliberate investment to close.
NEW Orchestration pattern expertise
Discriminate when workflows, single-agent loops, or multi-agent compositions fit the problem—aligned with established composition patterns for structuring reliable agentic systems.
NEW Cost-performance reasoning
Tie model and routing choices to measurable quality, latency, and spend—not to model hype.
Sunset
What we no longer screen for
These were reasonable signals in the pre-AI era. They are no longer reliable predictors of contribution in agent-augmented teams.
Personal code output volume or vanity metrics such as lines of code
Narrow supremacy in a single language or framework when agents cover breadth
Expectation that you personally implement every subsystem you design
"Hero" narratives where one person rescues a program through brute-force implementation
LeetCode-style algorithm screens disconnected from system and agentic design
Traditional Role Engineering Manager Engineering Manager · Development Manager · Team Lead AI-Era Role Engineering Manager
From tracking velocity to building capability and measuring what matters
3 Evolved
3 New Gaps
5 Sunset
Foundation you build on New areas to develop
50% existing foundation 50% new competencies
Evolved
Competencies that carry over — transformed
These build on your existing foundation. The core skill survives but the application, scope, and context change fundamentally.
Was Velocity tracking and capacity planning
Now Outcome-based measurement
Designing KPI frameworks that reward impact over activity, aligned with the HELM KPI Dashboard.
Was Managing engineering teams (5+ years)
Now Organizational design
Moving teams from functional silos to pods organized around outcomes and customer value.
Was Stakeholder communication
Now Coaching for judgment
Developing engineers who can evaluate and review at volume with consistent standards.
New Gaps
Entirely new competencies to develop
No traditional equivalent exists. These represent genuine skill gaps that require deliberate investment to close.
NEW Adoption management
Assessing where each person sits on the maturity model and building individual development plans that raise the team floor, not only the ceiling.
NEW Change leadership
Holding space for emotional and identity challenges as roles transform, without letting avoidance stall the whole organization.
NEW Agentic workflow fluency
Knowing the Plan-Execute-Verify-Ship-Learn loop well enough to see where it breaks in practice and fix the system, not blame individuals.
Sunset
What we no longer screen for
These were reasonable signals in the pre-AI era. They are no longer reliable predictors of contribution in agent-augmented teams.
Ability to "run a good standup" or optimize Scrum ceremonies as the core proof of management skill
Deep expertise in a specific project-management toolchain (e.g., Jira wizardry) as a proxy for leadership quality
Velocity tracking and capacity planning anchored in story points
Team growth framed primarily as headcount scaling
Performance management driven mainly by code output or merge volume
Traditional Role SRE / DevOps Engineer Site Reliability Engineer · DevOps Engineer · Infrastructure Engineer AI-Era Role AI Reliability Engineer
From monitoring infrastructure to monitoring the machines that monitor the machines
2 Evolved
4 New Gaps
5 Sunset
Foundation you build on New areas to develop
33% existing foundation 67% new competencies
Evolved
Competencies that carry over — transformed
These build on your existing foundation. The core skill survives but the application, scope, and context change fundamentally.
Was SLA/SLO definition (availability and latency)
Now Observability design
Building monitoring for non-deterministic operations where identical inputs do not guarantee identical outputs, and where "green" infra can mask behavioral failure.
Was Incident response and blameless postmortems
Now Incident response for AI systems
Adapting detection, communication, and postmortem practice when the trigger is an agent workflow rather than a failed deploy.
New Gaps
Entirely new competencies to develop
No traditional equivalent exists. These represent genuine skill gaps that require deliberate investment to close.
NEW Agent failure mode expertise
Understanding how agents fail differently from deterministic software: stochastic outputs, plausible mistakes, cost multiplication, and scope drift that bypasses conventional tests.
NEW Cost engineering
Token-level cost tracking, budget alerting, chargeback or showback discipline, and optimization for AI workloads without starving legitimate use.
NEW Guardrail implementation
Translating policy into automated enforcement, from secret scanning and PII detection to safety classification and dependency rules.
NEW Governance enforcement
Runtime monitoring and enforcement of governance policies (registry compliance, access boundaries, cost budgets) across agent operations. Distinct from the Platform Engineer who builds the governance infrastructure itself.
Sunset
What we no longer screen for
These were reasonable signals in the pre-AI era. They are no longer reliable predictors of contribution in agent-augmented teams.
Purely infrastructure-focused experience with no application-layer or data-flow awareness
Expertise limited to container orchestration and CI/CD pipelines without ownership of behavioral or economic SLOs
Incident response habits that assume deterministic failure modes and static blast-radius models
Cost management confined to compute, storage, and network with no fluency in token economics and agent run patterns
Monitoring strategies that stop at binary up/down checks and miss drift, abuse, and quality erosion
Traditional Role QA Engineer / SDET QA Engineer · SDET · QA Lead · Test Engineer AI-Era Role QA Engineer + Evaluation Lead
The role that splits in two — one judges the agent, the other judges the product
3 Evolved
3 New Gaps
5 Sunset
Foundation you build on New areas to develop
50% existing foundation 50% new competencies
Evolved
Competencies that carry over — transformed
These build on your existing foundation. The core skill survives but the application, scope, and context change fundamentally.
Was Test plans and test cases
Now Product judgment
Assessing experience quality beyond functional pass/fail.
Was Automation frameworks (Selenium, Cypress, Jest)
Now Automation at scale
Infrastructure that keeps up with high-volume agent output without drowning the team in manual review.
Was Bug tracking and regression discipline
Now Cross-functional communication
Turning quality signals into concrete, prioritized feedback for engineering and product.
New Gaps
Entirely new competencies to develop
No traditional equivalent exists. These represent genuine skill gaps that require deliberate investment to close.
NEW Evaluation design
Defining eval suites for non-deterministic or open-ended output — where "correct" is graded, not always unique.
NEW Drift detection
Spotting gradual degradation that no single PR or green build exposes.
NEW Statistical thinking
Setting thresholds, confidence, and sampling when binary gates mislead.
Sunset
What we no longer screen for
These were reasonable signals in the pre-AI era. They are no longer reliable predictors of contribution in agent-augmented teams.
Manual test execution as the primary value proposition
Depth in a single framework without judgment about what to automate and why
Quality defined only as absence of defects, ignoring intent and experience
Assumptions that all code is human-written, reviewed at human cadence, and stable between releases
QA as a final gate after development, disconnected from the continuous Build-Verify rhythm
Traditional Role Platform / Infrastructure Engineer Platform Engineer · Infrastructure Engineer · DevOps Engineer AI-Era Role Platform Engineer
From CI/CD pipelines to agent infrastructure and governance at scale
3 Evolved
3 New Gaps
5 Sunset
Foundation you build on New areas to develop
50% existing foundation 50% new competencies
Evolved
Competencies that carry over — transformed
These build on your existing foundation. The core skill survives but the application, scope, and context change fundamentally.
Was Monitoring and alerting for clusters and services
Now Cost optimization
Token-level cost tracking, routing for economic efficiency, and caching strategies tuned to generative workloads.
Was Developer tooling and inner-loop optimization
Now Platform thinking
Treating infrastructure as a product engineering teams adopt; designing agent execution experience with the same rigor once applied to builds and deploys.
Was Kubernetes, cloud, and IaC at scale
Now Scale engineering
Systems that survive fleet-level agent operations across many teams and repositories without collapsing into tribal knowledge and shadow endpoints.
New Gaps
Entirely new competencies to develop
No traditional equivalent exists. These represent genuine skill gaps that require deliberate investment to close.
NEW AI infrastructure
Model hosting, inference optimization, GPU management, and the workload patterns that distinguish LLM serving from stateless web tiers.
NEW Governance engineering
Registry, access control, and audit systems for autonomous operations, not only for human users and service accounts.
NEW Security at the agent layer
Secure connectivity between agents and production systems, secret lifecycle, and explicit boundaries when machines act with elevated scope.
Sunset
What we no longer screen for
These were reasonable signals in the pre-AI era. They are no longer reliable predictors of contribution in agent-augmented teams.
Infrastructure experience limited to traditional web application hosting
Platform work defined purely as "keeping the build green" without behavioral or economic SLOs
DevOps depth that never touches AI-specific infrastructure patterns
Cost management confined to cloud resource optimization with no literacy in token and inference economics
Designs that treat every workload as a stateless request
Traditional Role Product Manager Product Manager · Product Owner · Business Analyst AI-Era Role Product Manager
From directing execution to orchestrating intent through precision requirements
4 Evolved
2 New Gaps
5 Sunset
Foundation you build on New areas to develop
67% existing foundation 33% new competencies
Evolved
Competencies that carry over — transformed
These build on your existing foundation. The core skill survives but the application, scope, and context change fundamentally.
Was Writing detailed PRDs and user stories
Now Precision requirements writing
Craft acceptance criteria that are agent-executable—specific enough to act on, verifiable enough for human judgment.
Was Product strategy and roadmap ownership
Now Product judgment at speed
Decide quality and direction when agent output arrives far faster than traditional engineering cycles.
Was Backlog prioritization by business value
Now Outcome orientation
Anchor success in product metrics (adoption, satisfaction, retention), not only delivery metrics (stories closed, features shipped).
Was Managing stakeholder expectations
Now Data-informed iteration
Use the Learn phase to improve requirement templates and criteria based on what actually shipped and how users responded.
New Gaps
Entirely new competencies to develop
No traditional equivalent exists. These represent genuine skill gaps that require deliberate investment to close.
NEW Agent capability awareness
Know what agents do well and where human judgment must intervene, and shape requirements accordingly.
NEW Constraint-based thinking
Prefer boundaries—"never violate this," "always uphold that"—over brittle procedural scripts.
Sunset
What we no longer screen for
These were reasonable signals in the pre-AI era. They are no longer reliable predictors of contribution in agent-augmented teams.
PRD writing as the primary deliverable
Deep expertise in managing Jira boards and sprint ceremonies as core PM craft
Stakeholder management reduced to status updates and narrative control
Backlog grooming as a dominant use of PM time
"Experience with Agile/Scrum" as a differentiating qualification on its own
Traditional Role Product Designer UX Designer · UI Designer · Product Designer · Interaction Designer AI-Era Role Product Designer
From producing screens to governing the system agents generate from
4 Evolved
2 New Gaps
5 Sunset
Foundation you build on New areas to develop
67% existing foundation 33% new competencies
Evolved
Competencies that carry over — transformed
These build on your existing foundation. The core skill survives but the application, scope, and context change fundamentally.
Was Design system familiarity
Now Design system architecture
Building and maintaining systems precise enough for generation—tokens, components, patterns, and rules at implementation depth.
Was UX/UI experience (3-5 years)
Now UX judgment at volume
Quickly assessing many agent-generated interfaces while still sensing subtle failures—timing, spacing rhythm, visual weight, tone.
Was Implicit accessibility awareness
Now Accessibility engineering
Baking a11y requirements into the system so compliance is systematic, not heroic last-mile fixes.
Was Research and usability testing
Now Cross-functional collaboration
Working with engineering and product so requirements land as agent-executable constraints, not ambiguous intent.
New Gaps
Entirely new competencies to develop
No traditional equivalent exists. These represent genuine skill gaps that require deliberate investment to close.
NEW Design governance
Moving from primary production to quality control—reviewing, auditing, and correcting agent output at volume without losing standards.
NEW Machine-readable specification
Expressing design intent in structured forms (token JSON, component APIs, interaction specs) agents can execute against.
Sunset
What we no longer screen for
These were reasonable signals in the pre-AI era. They are no longer reliable predictors of contribution in agent-augmented teams.
Pixel-perfect production speed as the main proxy for ability
Portfolios judged primarily on screen count
Figma or Sketch fluency as a differentiator—tools are table stakes
Expectation that one designer personally produces every screen in a feature
Design excellence equated with trend-chasing rather than systemic thinking