# Role skills explorer

> Explore the skills described in HELM’s role guides, the experience they build on and questions to discuss with your team.

Source: https://helmframework.com/roles/competency-map
Updated: 2026-11-18
License: https://creativecommons.org/licenses/by/4.0/

Role skills

Choose a role to explore its skills, the experience they build on and areas to practice. The groupings describe the guide’s content.

[HELM 1.0.1](https://helmframework.com/changelog) · Updated 2026-11-18

The percentages describe the skills listed in each guide. They do not measure a person’s ability, readiness, or skill gap.

## 

Role guide Software Engineer Frontend Engineer · Backend Engineer · Full-Stack Engineer

HELM responsibilities Product Engineer

Build, review and maintain software with AI agents

3 Build on experience

3 Additional skills

5 Discuss in context

Skills linked to prior experience Other skills in this guide

50% of listed skills 50% of listed skills

[Read the role guide](https://helmframework.com/roles/software-engineer)

Build on experience

### Experience you can build on

These entries connect familiar experience with tasks in AI-assisted work. Use the examples to discuss what you know and what needs practice.

Related experience Programming language and framework experience

Application Cross-layer code review

Understand how a change affects frontend, backend and infrastructure. Involve the right expertise when a part needs closer review.

Related experience Problem-solving and algorithm skills

Application Architectural judgment

Recognize when a change conflicts with the architecture or creates security, reliability or maintenance problems.

Related experience REST API and database experience

Application System thinking

Trace how a change affects dependencies, interfaces and behavior in use.

Additional skills

### Other skills to discuss

These skills may also help with the work. The guide does not assign them to a previous skill or assume they are new to you.

PRACTICE Context engineering

Give agents relevant context, clear constraints and examples of the result you need.

PRACTICE Quality evaluation at volume

Keep review thorough as output increases. Prioritize meaningful checks and keep the workload manageable.

PRACTICE Product awareness

Check whether the change solves the user’s problem as well as meeting technical requirements.

Discuss in context

### Signals that need more context

These signals alone do not show how someone approaches the work. Discuss relevant examples, decisions and learning alongside them.

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

Syntax recall without examples of applying or checking that knowledge

Specialist knowledge without evidence of working across relevant boundaries

## 

Role guide Staff / Principal Engineer Staff Engineer · Principal Engineer · Solutions Architect

HELM responsibilities AI Architect

Set technical direction and clear boundaries for agent-assisted work

4 Build on experience

2 Additional skills

5 Discuss in context

Skills linked to prior experience Other skills in this guide

67% of listed skills 33% of listed skills

[Read the role guide](https://helmframework.com/roles/staff-engineer)

Build on experience

### Experience you can build on

These entries connect familiar experience with tasks in AI-assisted work. Use the examples to discuss what you know and what needs practice.

Related experience Deep distributed systems expertise

Application System design mastery

Design the interfaces, data flow and operating limits for systems that include agents.

Related experience Designing and shipping systems at scale

Application Failure mode thinking

Plan for incorrect outputs, repeated actions, stale instructions and unclear ownership, including how to detect and recover from failures.

Related experience Track record of mentorship

Application Technical communication

Explain architecture decisions through clear task boundaries, diagrams and instructions.

Related experience Leading complex technical initiatives

Application Cross-domain judgment

Assess output quality and design risk across domains (backend, data, security, UX) when agents span them.

Additional skills

### Other skills to discuss

These skills may also help with the work. The guide does not assign them to a previous skill or assume they are new to you.

PRACTICE Orchestration pattern expertise

Choose a workflow or agent pattern that fits the task, and explain why simpler options are insufficient.

PRACTICE Cost-performance reasoning

Compare model and routing choices using task quality, response time and cost.

Discuss in context

### Signals that need more context

These signals alone do not show how someone approaches the work. Discuss relevant examples, decisions and learning alongside them.

Code volume without evidence of the decisions and results behind it

Language or framework expertise without examples of wider system judgment

Expectation that you personally implement every subsystem you design

Individual achievements without evidence of collaboration or knowledge sharing

LeetCode-style algorithm screens disconnected from system and agentic design

## 

Role guide Engineering Manager Engineering Manager · Development Manager · Team Lead

HELM responsibilities Engineering Manager

Support team learning and review the results of agent-assisted work

3 Build on experience

3 Additional skills

5 Discuss in context

Skills linked to prior experience Other skills in this guide

50% of listed skills 50% of listed skills

[Read the role guide](https://helmframework.com/roles/engineering-manager)

Build on experience

### Experience you can build on

These entries connect familiar experience with tasks in AI-assisted work. Use the examples to discuss what you know and what needs practice.

Related experience Velocity tracking and capacity planning

Application Outcome-based measurement

Choose measures that help explain user outcomes, quality and effort, and check what a change in a measure means.

Related experience Managing engineering teams (5+ years)

Application Organizational design

Review responsibilities and handoffs, and try a team arrangement when there is evidence it could help.

Related experience Stakeholder communication

Application Coaching for judgment

Help engineers explain their reviews, recognize limits and practice difficult decisions.

Additional skills

### Other skills to discuss

These skills may also help with the work. The guide does not assign them to a previous skill or assume they are new to you.

PRACTICE Adoption management

Understand how the team uses agents, identify obstacles and agree useful learning or workflow changes.

PRACTICE Change leadership

Listen to concerns, explain the proposed change and involve people in deciding how to try it.

PRACTICE Agentic workflow fluency

Use Plan-Execute-Verify-Ship-Learn to find where work gets stuck and agree an improvement with the team.

Discuss in context

### Signals that need more context

These signals alone do not show how someone approaches the work. Discuss relevant examples, decisions and learning alongside them.

Meeting facilitation without examples of helping a team make decisions

Project-management tool expertise without evidence of leadership in practice

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

## 

Role guide SRE / DevOps Engineer Site Reliability Engineer · DevOps Engineer · Infrastructure Engineer

HELM responsibilities AI Reliability Engineer

Monitor agent behavior, cost and recovery alongside service reliability

2 Build on experience

4 Additional skills

5 Discuss in context

Skills linked to prior experience Other skills in this guide

33% of listed skills 67% of listed skills

[Read the role guide](https://helmframework.com/roles/sre-devops-engineer)

Build on experience

### Experience you can build on

These entries connect familiar experience with tasks in AI-assisted work. Use the examples to discuss what you know and what needs practice.

Related experience SLA/SLO definition (availability and latency)

Application Observability design

Monitor the quality and behavior of agent workflows as well as service availability.

Related experience Incident response and blameless postmortems

Application Incident response for AI systems

Adapting detection, communication, and postmortem practice when the trigger is an agent workflow rather than a failed deploy.

Additional skills

### Other skills to discuss

These skills may also help with the work. The guide does not assign them to a previous skill or assume they are new to you.

PRACTICE Agent failure mode expertise

Recognize incorrect outputs, repeated actions and scope errors that ordinary health checks may miss.

PRACTICE Cost engineering

Attribute costs to workflows, set useful budget alerts and compare savings with any effect on quality.

PRACTICE Guardrail implementation

Translating policy into automated enforcement, from secret scanning and PII detection to safety classification and dependency rules.

PRACTICE Governance enforcement

Check access, ownership records and budgets during operation. Coordinate with the people who maintain the shared infrastructure.

Discuss in context

### Signals that need more context

These signals alone do not show how someone approaches the work. Discuss relevant examples, decisions and learning alongside them.

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

## 

Role guide QA Engineer / SDET QA Engineer · SDET · QA Lead · Test Engineer

HELM responsibilities QA Engineer + Evaluation Lead

Check agent output and the product people use

3 Build on experience

3 Additional skills

5 Discuss in context

Skills linked to prior experience Other skills in this guide

50% of listed skills 50% of listed skills

[Read the role guide](https://helmframework.com/roles/qa-engineer)

Build on experience

### Experience you can build on

These entries connect familiar experience with tasks in AI-assisted work. Use the examples to discuss what you know and what needs practice.

Related experience Test plans and test cases

Application Product judgment

Assessing experience quality beyond functional pass/fail.

Related experience Automation frameworks (Selenium, Cypress, Jest)

Application Automation at scale

Build useful automated checks and plan the human review effort they leave.

Related experience Bug tracking and regression discipline

Application Cross-functional communication

Turning quality signals into concrete, prioritized feedback for engineering and product.

Additional skills

### Other skills to discuss

These skills may also help with the work. The guide does not assign them to a previous skill or assume they are new to you.

PRACTICE Evaluation design

Choose meaningful examples and criteria for judging outputs that may have more than one acceptable answer.

PRACTICE Drift detection

Notice changes in quality over time, including problems individual test runs can miss.

PRACTICE Statistical thinking

Understand the limits of a sample and explain what the available evidence supports.

Discuss in context

### Signals that need more context

These signals alone do not show how someone approaches the work. Discuss relevant examples, decisions and learning alongside them.

Test execution counts without examples of choosing and investigating meaningful checks

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

Release checks without involvement in planning and reviewing the work

## 

Role guide Platform / Infrastructure Engineer Platform Engineer · Infrastructure Engineer · DevOps Engineer

HELM responsibilities Platform Engineer

Provide dependable shared tools for agent-assisted work

3 Build on experience

3 Additional skills

5 Discuss in context

Skills linked to prior experience Other skills in this guide

50% of listed skills 50% of listed skills

[Read the role guide](https://helmframework.com/roles/platform-engineer)

Build on experience

### Experience you can build on

These entries connect familiar experience with tasks in AI-assisted work. Use the examples to discuss what you know and what needs practice.

Related experience Monitoring and alerting for clusters and services

Application Cost optimization

Token-level cost tracking, routing for economic efficiency, and caching strategies tuned to generative workloads.

Related experience Developer tooling and inner-loop optimization

Application Platform thinking

Understand what teams need from shared tools, make those tools usable and respond to feedback.

Related experience Kubernetes, cloud, and IaC at scale

Application Scale engineering

Plan shared capacity, ownership and operating support as more teams use agent workflows.

Additional skills

### Other skills to discuss

These skills may also help with the work. The guide does not assign them to a previous skill or assume they are new to you.

PRACTICE AI infrastructure

Model hosting, inference optimization, GPU management, and the workload patterns that distinguish LLM serving from stateless web tiers.

PRACTICE Governance engineering

Registry, access control, and audit systems for autonomous operations, not only for human users and service accounts.

PRACTICE Security at the agent layer

Secure connectivity between agents and production systems, secret lifecycle, and explicit boundaries when machines act with elevated scope.

Discuss in context

### Signals that need more context

These signals alone do not show how someone approaches the work. Discuss relevant examples, decisions and learning alongside them.

Hosting experience without discussion of the workloads this role will support

Build success without evidence about behavior, reliability or cost in use

Tool expertise without examples of supporting the teams who use it

Cost savings without checking the effect on quality and reliability

Design assumptions that do not fit long-running or stateful agent tasks

## 

Role guide Product Manager Product Manager · Product Owner · Business Analyst

HELM responsibilities Product Manager

Make goals clear and help your team build what users need

4 Build on experience

2 Additional skills

5 Discuss in context

Skills linked to prior experience Other skills in this guide

67% of listed skills 33% of listed skills

[Read the role guide](https://helmframework.com/roles/product-manager)

Build on experience

### Experience you can build on

These entries connect familiar experience with tasks in AI-assisted work. Use the examples to discuss what you know and what needs practice.

Related experience Writing detailed PRDs and user stories

Application Precision requirements writing

Write requirements with enough context and examples for someone to implement and review them.

Related experience Product strategy and roadmap ownership

Application Product judgment at speed

Review priorities and quality when several agent-assisted changes are ready at once.

Related experience Backlog prioritization by business value

Application Outcome orientation

Review user outcomes alongside delivery measures and explain what each measure can tell the team.

Related experience Managing stakeholder expectations

Application Data-informed iteration

Use the Learn phase to improve requirement templates and criteria based on what actually shipped and how users responded.

Additional skills

### Other skills to discuss

These skills may also help with the work. The guide does not assign them to a previous skill or assume they are new to you.

PRACTICE Agent capability awareness

Know what agents do well and where human judgment must intervene, and shape requirements accordingly.

PRACTICE Constraint-based thinking

Explain the requirements and limits a solution must respect, and specify steps where the task needs them.

Discuss in context

### Signals that need more context

These signals alone do not show how someone approaches the work. Discuss relevant examples, decisions and learning alongside them.

Document volume without evidence that the requirements helped the team

Planning-tool expertise without examples of product decisions

Status reporting without evidence of resolving questions or disagreements

Backlog activity without an explanation of priorities and outcomes

"Experience with Agile/Scrum" as a differentiating qualification on its own

## 

Role guide Product Designer UX Designer · UI Designer · Product Designer · Interaction Designer

HELM responsibilities Product Designer

Design clear experiences and review agent-generated interfaces

4 Build on experience

2 Additional skills

5 Discuss in context

Skills linked to prior experience Other skills in this guide

67% of listed skills 33% of listed skills

[Read the role guide](https://helmframework.com/roles/product-designer)

Build on experience

### Experience you can build on

These entries connect familiar experience with tasks in AI-assisted work. Use the examples to discuss what you know and what needs practice.

Related experience Design system familiarity

Application Design system architecture

Maintain reusable components, design values, states and examples at the detail implementation needs.

Related experience UX/UI experience (3-5 years)

Application UX judgment at volume

Review generated interfaces for task flow, timing, spacing, visual hierarchy and tone.

Related experience Implicit accessibility awareness

Application Accessibility engineering

Design for accessibility and combine automated checks with keyboard, assistive-technology and user testing where needed.

Related experience Research and usability testing

Application Cross-functional collaboration

Agree requirements and constraints with engineering and product, using examples to resolve ambiguity.

Additional skills

### Other skills to discuss

These skills may also help with the work. The guide does not assign them to a previous skill or assume they are new to you.

PRACTICE Design governance

Set clear review standards, check generated work and use findings to improve the design system.

PRACTICE Machine-readable specification

Expressing design intent in structured forms (token JSON, component APIs, interaction specs) agents can execute against.

Discuss in context

### Signals that need more context

These signals alone do not show how someone approaches the work. Discuss relevant examples, decisions and learning alongside them.

Pixel-perfect production speed as the main proxy for ability

Portfolios judged primarily on screen count

Design-tool fluency without examples of the decisions behind the work

Expectation that one designer personally produces every screen in a feature

Visual trends without evidence of usability, consistency or user needs
