Reading the Skill Trees of Six Roles: A Map of Capability

2026-10-19

This skill tree came out of a real piece of organizing work. The team has six roles: AD (application development), PM (project management), SRE (site reliability), BA (business analysis), QA (quality assurance), and OM (operations). Each role has its own table. Within each table, capabilities are split into dimensions and sub-skills, and every sub-skill is described across five levels, from Level 1 to Level 5.

1. How to Read the Five Levels

Level 1 usually means knowing about something, having heard of it, and needing guidance. Level 2 means being able to follow the steps but still needing supervision. Level 3 means completing routine work independently. Level 4 means handling complex problems and helping others. Level 5 means designing mechanisms at the organizational level and driving improvement across the team.

The levels are not job grades. They are a measuring stick. The same person can sit at different levels on different sub-skills. That is exactly the purpose of a skill tree: to help people see where they are strong and where they are weak.

2. AD: Application Development

AD covers five dimensions: foundational technical skills, Graphene system development work, delivery capability, team collaboration, and overall capability. Under foundational technical skills sit six sub-skills: common tools, Java fundamentals, framework mastery, middleware usage, database skills, and cloud service usage.

Take Git and Maven as an example. At Level 1, a person cannot perform version control on their own. At Level 2, they can clone, commit, and push, switch branches, and resolve simple conflicts. At Level 3, they understand branching models, use stash, and can roll back bad commits. At Level 4, they handle complex commit histories with rebase and cherry-pick. At Level 5, they design the team's branching strategy and release process.

The delivery dimension is about output. Process execution, delivery artifacts, and retrospective skills together determine whether a person's deliveries are reliable and traceable.

3. PM: Project Management

The PM table starts by requiring an understanding of the Graphene system itself: its architecture, its processing flows, and its baseline documents. Only after that comes insurance business capability. The delivery section puts particular weight on WBS progress, quality management, change management, release management, risk and issue management, and advancing infrastructure and security compliance.

One detail is worth noting. A PM's Level 5 is usually not about doing things better personally. It is about guiding others from a PMO perspective. For example, under architecture understanding, Level 5 requires raising network-related confirmation items early and bringing middleware EOL and version constraints into schedule and risk management.

4. SRE: Site Reliability

SRE's foundational technical skills span Linux, containers and Kubernetes, cloud platforms, middleware and databases, monitoring and alerting with observability, and automation with IaC. Each area moves from being able to read the system, all the way to designing governance frameworks for it.

Take monitoring as an example. At Level 1, a person cannot tell the roles of Prometheus, Grafana, and Alertmanager apart. At Level 3, they can judge metric anomalies independently and combine them with logs to locate causes. At Level 5, they build an SLO and SLI framework and use observability data to guide architectural evolution and cost budgeting.

5. BA: Business Analysis

The core of BA is insurance business capability. It breaks down into product understanding, business process understanding, and the ability to write and review BSD (business specification documents). Product understanding starts with knowing sums insured and premiums, and reaches the idea of a product factory where new products can be released quickly through configuration.

Business process understanding covers the full lifecycle of a policy: enrollment, policy changes, renewal, claims, maturity, and cancellation. At Level 3, a BA must handle reverse flows such as surrenders and refunds. At Level 4, they understand lifecycle management for long-term policies. At Level 5, they can design process architectures that support millions of policies.

6. QA: Quality Assurance

QA's test technical capability begins with test design, including the test design document (TMP) and test cases. It then moves to tooling and code skills, covering Jira, Postman, Magic, JMeter, and Python. The final stage is BUG analysis and localization.

The five levels of test design differ clearly. At Level 1, a person can only list visible scenarios. At Level 2, they apply techniques such as equivalence partitioning and boundary values. At Level 3, they build high-coverage test sets independently. At Level 4, they can review coverage blind spots. At Level 5, they establish an organization-wide test design system and scenario library.

7. OM: Operations

OM's foundational operations skills split into two sub-skills: operating infrastructure and middleware, and operating the application layer. At Level 1, one only needs to understand how cloud platforms, databases, caches, message queues, and load balancers relate to each other. At Level 3, one can tell whether a problem is a resource shortage or a downstream issue. At Level 5, one can identify chain reaction paths across systems.

OM also requires familiarity with Graphene's operations tools, such as BOOM, Kibana, Kafka Ops, and Nacos Ops. The expectation is to use them within daily investigation, iterative releases, and alert response, following the defined process.

8. Closing Thoughts

The most valuable part of a skill tree is not scoring people. It is showing them a path they can walk. The boundaries between the six roles also become clearer in this table: who is responsible for understanding the business, who guards quality, and who keeps the system stable. When everyone knows where they stand on the scale and which piece to strengthen next, collaboration finally has a shared language.