Pipeline run
8077639b-c7cb-4ba7-998c-e936e0f7c4d4
Client output enrichment
v2 Skill cluster · Nature of work · AI index · Tech stack maturity · Evidence · KRA descriptionvocab breakdown (legacy)
1 POST /skills/extract-from-jd
2 POST /skills/extract-details
3 POST /skills/final-role-output
Backend Engineer
slug: backend-engineer · id: 14 · source: db
The primary skills indicate a strong emphasis on backend development, which aligns with the role of a Backend Engineer.
Resolution:
in_db
— role exists in library; skill↔dim and role↔dim links saved when applicable.
Job description
ackend Engineer — Job Description Job Title: Backend Engineer Experience: 2–5 Years Location: Remote / Hybrid / Onsite About the Role We are looking for a Backend Engineer to build scalable, secure, and high-performance backend systems. You will work closely with frontend developers, product managers, and DevOps teams to design APIs, manage databases, and improve system reliability. Key Responsibilities Design and develop RESTful APIs and backend services Build scalable microservices and server-side applications Optimize application performance and database queries Implement authentication, authorization, and security best practices Integrate third-party APIs and cloud services Write clean, maintainable, and testable code Collaborate with frontend and DevOps teams for deployment and integration Monitor applications, debug issues, and improve system stability Participate in code reviews and technical discussions Required Skills Strong proficiency in Node.js / Java / Python / Go Experience with Express.js, Spring Boot, FastAPI, or similar frameworks Good understanding of REST APIs and microservices architecture Experience with databases such as PostgreSQL, MySQL, or MongoDB Knowledge of Redis, Kafka, or RabbitMQ is a plus Familiarity with Docker and Kubernetes Understanding of Git and CI/CD pipelines Knowledge of AWS, Azure, or GCP cloud platforms Strong problem-solving and debugging skills Preferred Qualifications Experience with scalable distributed systems Understanding of caching and performance optimization Familiarity with monitoring tools like Prometheus or Grafana Exposure to Agile/Scrum methodologies Nice to Have Experience with GraphQL Knowledge of event-driven architecture Open-source contributions or personal backend projects
Skills from this JD
Each row merges API 1 extraction, API 2 library match / v3 orchestration (dimensions + locked dims), and API 3 persistence tags.
Aliases — catalog
- DStreams (VERSION)
- Spark 2.x (VERSION)
- Spark 3.x (VERSION)
- Spark Streaming (VERSION)
- Spark Structured Streaming (VERSION)
- Structured Streaming (VERSION)
Context tags (catalog)
Stored enrichment (catalog DB)
- Category
- Framework
- Sub-category
- Stream Processing Framework
- Vendor
- Apache Software Foundation
- License
- apache_2
- Year introduced
- 2013
- Confidence
- 0.90
- Version strategy
- SEPARATE_ENTITY
- Version tag
- Structured Streaming (Spark 2.0+)
Maturity reasoning: JD volume is far lower than Structured Streaming; most Spark streaming roles now specify Structured Streaming or Kafka/Flink, and Spark docs position Spark Streaming as the older API.
Skill profile (library / DB)
- Skill nature
- PROTOCOL
- Volatility
- STABLE
- Typical lifespan
- EVERGREEN
- Category id
- 8
- Sub-category id
- 67
- Extractable
- True
- Also category
- False
Dimensions (API 2 worklist)
-
API Integration and Data Fetching Catalog dimension db id 9
Library dimension (catalog)
Roles linked in library: Frontend Engineer, Full Stack Developer
API 3 link attempts (this skill)
| Dimension | Skill↔dim | Role↔dim | Outcome |
|---|---|---|---|
|
API Integration and Data Fetching
api-integration-and-data-fetching
|
✓ | — | Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role) |
Aliases — catalog
- hooks composition (CANONICAL) primary
Context tags (catalog)
Stored enrichment (catalog DB)
- Category
- Concept
- Sub-category
- Hooks Composition
- Confidence
- 0.92
- Version strategy
- NOT_APPLICABLE
Maturity reasoning: React job postings commonly require hooks and custom hook composition; the pattern is standard in modern React codebases and docs, with broad ecosystem adoption rather than a niche tool.
Skill profile (library / DB)
- Skill nature
- RUNTIME
- Volatility
- STABLE
- Typical lifespan
- EVERGREEN
- Category id
- 271
- Sub-category id
- 2120
- Extractable
- True
- Also category
- False
Dimensions (API 2 worklist)
-
Programming Languages for Backend Systems Catalog dimension db id 140
Library dimension (catalog)
Roles linked in library: Backend Engineer
API 3 link attempts (this skill)
| Dimension | Skill↔dim | Role↔dim | Outcome |
|---|---|---|---|
|
Programming Languages for Backend Systems
programming-languages-for-backend-systems
|
✓ | ✓ | Existing dimension (library) · Role↔dimension saved |
Aliases — catalog
- sqlmap (CANONICAL) primary
Context tags (catalog)
Stored enrichment (catalog DB)
- Category
- Tool
- Sub-category
- Sql Injection Testing Tool
- Vendor
- sqlmap project
- License
- gpl_v2
- Year introduced
- 2006
- Confidence
- 0.98
- Version strategy
- NOT_APPLICABLE
Maturity reasoning: sqlmap appears in pentest/security JDs far less than mainstream dev tools; GitHub shows steady but specialized use, and it’s a focused SQL injection testing utility rather than a general-purpose platform.
Skill profile (library / DB)
- Skill nature
- LANGUAGE
- Volatility
- STABLE
- Typical lifespan
- EVERGREEN
- Category id
- 5
- Sub-category id
- 54
- Extractable
- True
- Also category
- False
Dimensions (API 2 worklist)
-
Programming Languages for AI Workflows Catalog dimension db id 261
Library dimension (catalog)
Roles linked in library: AI Engineer
-
Programming Languages for Backend Systems Catalog dimension db id 140
Library dimension (catalog)
Roles linked in library: Backend Engineer
-
Programming Languages for Data Work Catalog dimension db id 67
Library dimension (catalog)
Roles linked in library: Data Engineer
-
Programming Languages for ML Systems Catalog dimension db id 113
Library dimension (catalog)
Roles linked in library: Machine Learning Engineer
-
Programming Languages for Test Automation Catalog dimension db id 193
Library dimension (catalog)
Roles linked in library: Automation Tester
API 3 link attempts (this skill)
| Dimension | Skill↔dim | Role↔dim | Outcome |
|---|---|---|---|
|
Programming Languages for AI Workflows
programming-languages-for-ai-workflows
|
✓ | — | Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role) |
|
Programming Languages for Backend Systems
programming-languages-for-backend-systems
|
✓ | ✓ | Existing dimension (library) · Role↔dimension saved |
|
Programming Languages for Data Work
programming-languages-for-data-work
|
✓ | — | Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role) |
|
Programming Languages for ML Systems
programming-languages-for-ml-systems
|
✓ | — | Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role) |
|
Programming Languages for Test Automation
programming-languages-for-test-automation
|
✓ | — | Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role) |
Aliases — catalog
- Cobalt Strike (CANONICAL) primary
Context tags (catalog)
Stored enrichment (catalog DB)
- Category
- Tool
- Sub-category
- Adversary Simulation Tool
- Vendor
- Fortra
- License
- proprietary
- Year introduced
- 2012
- Confidence
- 0.98
- Version strategy
- NOT_APPLICABLE
Maturity reasoning: Appears in a limited set of red-team/pentest JDs and security vendor training, but far below mainstream devops tools; market signal is specialized adversary-simulation usage rather than broad hiring demand.
Skill profile (library / DB)
- Skill nature
- LANGUAGE
- Volatility
- STABLE
- Typical lifespan
- EVERGREEN
- Category id
- 5
- Sub-category id
- 54
- Extractable
- True
- Also category
- False
Dimensions (API 2 worklist)
-
Analytical Programming Languages Catalog dimension db id 82
Library dimension (catalog)
Roles linked in library: Data Analyst, Data Scientist
-
Automation Scripting and CLI Catalog dimension db id 48
Library dimension (catalog)
Roles linked in library: Azure Cloud Engineer, Cloud Engineer
-
Automation and Scripting for Operations Catalog dimension db id 361
Library dimension (catalog)
Roles linked in library: Virtualization Engineer
-
Network Automation and Scripting Catalog dimension db id 285
Library dimension (catalog)
Roles linked in library: Network Engineer
-
Programming Languages for AI Workflows Catalog dimension db id 261
Library dimension (catalog)
Roles linked in library: AI Engineer
-
Programming Languages for Backend Systems Catalog dimension db id 140
Library dimension (catalog)
Roles linked in library: Backend Engineer
-
Programming Languages for Data Work Catalog dimension db id 67
Library dimension (catalog)
Roles linked in library: Data Engineer
-
Programming Languages for ML Systems Catalog dimension db id 113
Library dimension (catalog)
Roles linked in library: Machine Learning Engineer
-
Programming Languages for Security Work Catalog dimension db id 328
Library dimension (catalog)
Roles linked in library: Cybersecurity Engineer
-
Programming Languages for Test Automation Catalog dimension db id 193
Library dimension (catalog)
Roles linked in library: Automation Tester
-
Security Automation and Scripting Catalog dimension db id 258
Library dimension (catalog)
Roles linked in library: Cybersecurity Engineer
API 3 link attempts (this skill)
| Dimension | Skill↔dim | Role↔dim | Outcome |
|---|---|---|---|
|
Analytical Programming Languages
analytical-programming-languages
|
✓ | — | Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role) |
|
Automation Scripting and CLI
automation-scripting-and-cli
|
✓ | — | Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role) |
|
Automation and Scripting for Operations
automation-and-scripting-for-operations
|
✓ | — | Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role) |
|
Network Automation and Scripting
network-automation-and-scripting
|
✓ | — | Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role) |
|
Programming Languages for AI Workflows
programming-languages-for-ai-workflows
|
✓ | — | Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role) |
|
Programming Languages for Backend Systems
programming-languages-for-backend-systems
|
✓ | ✓ | Existing dimension (library) · Role↔dimension saved |
|
Programming Languages for Data Work
programming-languages-for-data-work
|
✓ | — | Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role) |
|
Programming Languages for ML Systems
programming-languages-for-ml-systems
|
✓ | — | Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role) |
|
Programming Languages for Security Work
programming-languages-for-security-work
|
✓ | — | Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role) |
|
Programming Languages for Test Automation
programming-languages-for-test-automation
|
✓ | — | Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role) |
|
Security Automation and Scripting
security-automation-and-scripting
|
✓ | — | Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role) |
Aliases — catalog
- field-level errors (CANONICAL) primary
Context tags (catalog)
Stored enrichment (catalog DB)
- Category
- Concept
- Sub-category
- Form Error Handling Concept
- Confidence
- 0.90
- Version strategy
- NOT_APPLICABLE
Maturity reasoning: Common form UX pattern in web/mobile JDs and design-system docs; widely supported by libraries like React Hook Form, Formik, and Angular forms for per-field validation feedback.
Skill profile (library / DB)
- Skill nature
- LANGUAGE
- Volatility
- STABLE
- Typical lifespan
- EVERGREEN
- Category id
- 5
- Sub-category id
- 54
- Extractable
- True
- Also category
- False
Dimensions (API 2 worklist)
-
Programming Languages for Backend Systems Catalog dimension db id 140
Library dimension (catalog)
Roles linked in library: Backend Engineer
-
Programming Languages for ML Systems Catalog dimension db id 113
Library dimension (catalog)
Roles linked in library: Machine Learning Engineer
-
Programming Languages for Security Work Catalog dimension db id 328
Library dimension (catalog)
Roles linked in library: Cybersecurity Engineer
API 3 link attempts (this skill)
| Dimension | Skill↔dim | Role↔dim | Outcome |
|---|---|---|---|
|
Programming Languages for Backend Systems
programming-languages-for-backend-systems
|
✓ | ✓ | Existing dimension (library) · Role↔dimension saved |
|
Programming Languages for ML Systems
programming-languages-for-ml-systems
|
✓ | — | Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role) |
|
Programming Languages for Security Work
programming-languages-for-security-work
|
✓ | — | Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role) |
Skill enrichment (orchestrator / LLM)
Express.js appears in many Node.js web backend job postings and remains a standard default in hiring pipelines, despite newer frameworks like Fastify/NestJS gaining share.
Express.js ·mit ·since 2010 (0.99)
Express.js is a well-known Node.js web framework with a distinctive name; in typical JDs it is unlikely to be confused with another catalog skill.
Not versioned
Framework ·web_framework confidence 0.98
Express.js is a structured codebase that applications are built inside and it calls user code, so by the Tool vs Framework rule it is a Framework.
- Category
- Framework
- Sub-category
- web_framework
- Skill nature
- FRAMEWORK
- Volatility
- STABLE
- Typical lifespan
- EVERGREEN
- Version strategy
- NOT_APPLICABLE
Dimensions (API 2 worklist)
-
Version Control Systems Catalog dimension db id 365
Library dimension (catalog)
Locked dimensions (v3 placement)
-
Node.js Web Frameworks
Pipeline tentative id
Frameworks and conventions for building server-side web applications and APIs on Node.js. Express.js belongs here because it is a core backend HTTP framework used to define routes, middleware, request handling, and service endpoints.
API 3 link attempts (this skill)
| Dimension | Skill↔dim | Role↔dim | Outcome |
|---|---|---|---|
|
Version Control Systems
d_init_01
|
✓ | — | New skill saved · Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role) |
Aliases — catalog
- pagination (CANONICAL) primary
- Pagination (CANONICAL)
Context tags (catalog)
Stored enrichment (catalog DB)
- Category
- Concept
- Sub-category
- Api Pagination
- Confidence
- 0.70
- Version strategy
- NOT_APPLICABLE
Maturity reasoning: Common API design requirement in job descriptions for REST/GraphQL backends; widely implemented via page/limit or cursor patterns across major platforms and SDKs.
Skill profile (library / DB)
- Skill nature
- FRAMEWORK
- Volatility
- STABLE
- Typical lifespan
- EVERGREEN
- Category id
- 4
- Sub-category id
- 708
- Extractable
- True
- Also category
- False
Dimensions (API 2 worklist)
-
Inference Service Frameworks Catalog dimension db id 114
Library dimension (catalog)
Roles linked in library: Machine Learning Engineer
-
Web Service Frameworks Catalog dimension db id 141
Library dimension (catalog)
Roles linked in library: Backend Engineer
API 3 link attempts (this skill)
| Dimension | Skill↔dim | Role↔dim | Outcome |
|---|---|---|---|
|
Inference Service Frameworks
inference-service-frameworks
|
✓ | — | Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role) |
|
Web Service Frameworks
web-service-frameworks
|
✓ | ✓ | Existing dimension (library) · Role↔dimension saved |
Aliases — catalog
- GraphQL clients (CANONICAL) primary
Context tags (catalog)
Stored enrichment (catalog DB)
- Category
- Library
- Sub-category
- Graphql Client Library
- Vendor
- Apollo GraphQL
- License
- mit
- Year introduced
- 2015
- Confidence
- 0.90
- Version strategy
- NOT_APPLICABLE
Maturity reasoning: GraphQL clients are widely listed in frontend/backend JDs alongside Apollo/Relay, and major vendors maintain active docs and tooling; market demand is broad rather than niche.
Skill profile (library / DB)
- Skill nature
- FRAMEWORK
- Volatility
- STABLE
- Typical lifespan
- EVERGREEN
- Category id
- 4
- Sub-category id
- 52
- Extractable
- True
- Also category
- False
Dimensions (API 2 worklist)
-
Inference Service Frameworks Catalog dimension db id 114
Library dimension (catalog)
Roles linked in library: Machine Learning Engineer
-
Web Service Frameworks Catalog dimension db id 141
Library dimension (catalog)
Roles linked in library: Backend Engineer
API 3 link attempts (this skill)
| Dimension | Skill↔dim | Role↔dim | Outcome |
|---|---|---|---|
|
Inference Service Frameworks
inference-service-frameworks
|
✓ | — | Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role) |
|
Web Service Frameworks
web-service-frameworks
|
✓ | ✓ | Existing dimension (library) · Role↔dimension saved |
Aliases — from this run (catalog unavailable)
- Microservices (CANONICAL) primary
Skill profile (library / DB)
- Skill nature
- PATTERN
- Volatility
- STABLE
- Typical lifespan
- EVERGREEN
- Category id
- 1
- Sub-category id
- 663
- Extractable
- True
- Also category
- False
Dimensions (API 2 worklist)
-
Service Architecture and Integration Catalog dimension db id 148
Library dimension (catalog)
Roles linked in library: Backend Engineer
API 3 link attempts (this skill)
| Dimension | Skill↔dim | Role↔dim | Outcome |
|---|---|---|---|
|
Service Architecture and Integration
service-architecture-and-integration
|
✓ | ✓ | Existing dimension (library) · Role↔dimension saved |
Skill enrichment (orchestrator / LLM)
PostgreSQL appears in a large share of backend and data-engineering job descriptions and is a standard managed offering across AWS, GCP, and Azure, indicating broad market adoption.
PostgreSQL Global Development Group ·other_open ·since 1996 (0.97)
PostgreSQL is a specific, well-known relational database name with little overlap in typical JDs beyond generic database mentions; it is unlikely to be confused with another catalog skill.
Versioned 16
{
"PostgreSQL 10": "10",
"PostgreSQL 11": "11",
"PostgreSQL 12": "12",
"PostgreSQL 13": "13",
"PostgreSQL 14": "14",
"PostgreSQL 15": "15",
"PostgreSQL 16": "16",
"PostgreSQL 9.5": "9.5",
"PostgreSQL 9.6": "9.6",
"Postgres 10": "10",
"Postgres 11": "11",
"Postgres 12": "12",
"Postgres 13": "13",
"Postgres 14": "14",
"Postgres 15": "15",
"Postgres 16": "16",
"Postgres 9.5": "9.5",
"Postgres 9.6": "9.6"
}
Datastore ·relational_database confidence 0.99
By the Datastore vs Format rule, PostgreSQL persists data as a primary database system, so it is fundamentally a Datastore.
- Category
- Datastore
- Sub-category
- relational_database
- Skill nature
- TOOL
- Volatility
- STABLE
- Typical lifespan
- EVERGREEN
- Version strategy
- SEPARATE_ENTITY
Dimensions (API 2 worklist)
-
Version Control Systems Catalog dimension db id 365
Library dimension (catalog)
Locked dimensions (v3 placement)
-
PostgreSQL Database Administration
Pipeline tentative id
Covers operating PostgreSQL as a production relational database, including schema management, backups, restores, replication, monitoring, and routine DBA tasks. PostgreSQL belongs here because it is a specific database platform rather than a generic SQL skill.
API 3 link attempts (this skill)
| Dimension | Skill↔dim | Role↔dim | Outcome |
|---|---|---|---|
|
Version Control Systems
d_init_01
|
✓ | — | New skill saved · Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role) |
Skill enrichment (orchestrator / LLM)
MySQL appears in high-volume job postings across backend/data roles and remains a default managed option on AWS RDS, GCP Cloud SQL, and Azure Database for MySQL, indicating broad market adoption.
Oracle Corporation ·gpl_v2 ·since 1995 (0.98)
MySQL is a specific, well-known relational database name in job descriptions and is usually not confused with other catalog skills.
Not versioned
Datastore ·relational_database confidence 0.99
MySQL is fundamentally a system that persists and queries data, so by the Datastore vs Format rule it is a Datastore.
- Category
- Datastore
- Sub-category
- relational_database
- Skill nature
- TOOL
- Volatility
- STABLE
- Typical lifespan
- EVERGREEN
- Version strategy
- NOT_APPLICABLE
Dimensions (API 2 worklist)
-
MySQL Operational Monitoring, Logging, and Diagnostics Catalog dimension db id 166
Library dimension (catalog)
Roles linked in library: MySQL DBA
-
Data Access and Query Optimization Catalog dimension db id 74
Library dimension (catalog)
Roles linked in library: Data Engineer
-
Data Access and Query Optimization Catalog dimension db id 74
Library dimension (catalog)
Roles linked in library: Data Engineer
Locked dimensions (v3 placement)
-
MySQL Operational Monitoring, Logging, and Diagnostics
Pipeline tentative id
Covers monitoring MySQL production health and using MySQL-native logs, status data, and diagnostic views to detect, investigate, and explain incidents or performance anomalies. Includes routine health checks, alerting, replication and availability monitoring, resource and connection monitoring, incident triage, and use of error logs, slow query logs, general logs, SHOW PROCESSLIST, performance_schema, information_schema, status variables, and diagnostic queries to understand behavior and support
-
Data Access and Query Optimization
Reuses catalog slug
Covers how data is accessed efficiently through indexes, query plans, partitioning, and access-path tuning. MySQL belongs here because working effectively with it often requires understanding and improving query performance.
-
Data Access and Query Optimization
Reuses catalog slug
Techniques for making analytical data fast and reliable to query. This includes partitioning, clustering, indexing choices, file layout, and access-path tuning for downstream consumers.
API 3 link attempts (this skill)
| Dimension | Skill↔dim | Role↔dim | Outcome |
|---|---|---|---|
|
MySQL Operational Monitoring, Logging, and Diagnostics
mysql-operational-monitoring-logging-and-diagnostics
|
✓ | — | New skill saved · Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role) |
|
Data Access and Query Optimization
data-access-and-query-optimization
|
✓ | — | New skill saved · Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role) |
|
MySQL Operational Monitoring, Logging, and Diagnostics
d_merge_01
|
✓ | — | New skill saved · Existing dimension (reconciliation merge) · Role↔dimension skipped (dimension not under chosen role) |
Aliases — catalog
- STIX/TAXII (CANONICAL) primary
Context tags (catalog)
Stored enrichment (catalog DB)
- Category
- Standard
- Sub-category
- Threat Intelligence Exchange Standard
- Vendor
- OASIS
- License
- other_open
- Year introduced
- 2012
- Confidence
- 0.90
- Version strategy
- NOT_APPLICABLE
Maturity reasoning: STIX/TAXII appears in threat-intel and SOC job postings, but JD volume is far below mainstream standards; it’s mainly used in specialized CTI platforms and vendor integrations rather than general software roles.
Skill profile (library / DB)
- Skill nature
- TOOL
- Volatility
- STABLE
- Typical lifespan
- EVERGREEN
- Category id
- 12
- Sub-category id
- 360
- Extractable
- True
- Also category
- False
Dimensions (API 2 worklist)
-
NoSQL and Cache Stores Catalog dimension db id 145
Library dimension (catalog)
Roles linked in library: Backend Engineer
-
NoSQL and Data Lake Storage Catalog dimension db id 73
Library dimension (catalog)
Roles linked in library: Data Engineer
API 3 link attempts (this skill)
| Dimension | Skill↔dim | Role↔dim | Outcome |
|---|---|---|---|
|
NoSQL and Cache Stores
nosql-and-cache-stores
|
✓ | ✓ | Existing dimension (library) · Role↔dimension saved |
|
NoSQL and Data Lake Storage
nosql-and-data-lake-storage
|
✓ | — | Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role) |
Aliases — catalog
- idempotent configuration (CANONICAL) primary
Context tags (catalog)
Stored enrichment (catalog DB)
- Category
- Concept
- Sub-category
- Configuration Concept
- Confidence
- 0.86
- Version strategy
- NOT_APPLICABLE
Maturity reasoning: Common DevOps/SRE requirement in JDs for Ansible, Terraform, and Kubernetes: "idempotent" appears frequently in automation and IaC roles, reflecting broad market adoption.
Skill profile (library / DB)
- Skill nature
- TOOL
- Volatility
- STABLE
- Typical lifespan
- EVERGREEN
- Category id
- 12
- Sub-category id
- 701
- Extractable
- True
- Also category
- False
Dimensions (API 2 worklist)
-
NoSQL and Cache Stores Catalog dimension db id 145
Library dimension (catalog)
Roles linked in library: Backend Engineer
API 3 link attempts (this skill)
| Dimension | Skill↔dim | Role↔dim | Outcome |
|---|---|---|---|
|
NoSQL and Cache Stores
nosql-and-cache-stores
|
✓ | ✓ | Existing dimension (library) · Role↔dimension saved |
Aliases — catalog
- image scanning (CANONICAL) primary
Context tags (catalog)
Stored enrichment (catalog DB)
- Category
- Tool
- Sub-category
- Security Scanning Tool
- Vendor
- Aqua Security
- License
- apache_2
- Year introduced
- 2015
- Confidence
- 0.80
- Version strategy
- NOT_APPLICABLE
Maturity reasoning: Image scanning is widely listed in DevSecOps JDs and CI/CD security stacks; vendors like Trivy, Snyk, and Prisma Cloud have made container/image scanning a standard market requirement.
Skill profile (library / DB)
- Skill nature
- TOOL
- Volatility
- STABLE
- Typical lifespan
- EVERGREEN
- Category id
- 12
- Sub-category id
- 700
- Extractable
- True
- Also category
- False
Dimensions (API 2 worklist)
-
Messaging and Event Streaming Catalog dimension db id 146
Library dimension (catalog)
Roles linked in library: Backend Engineer
API 3 link attempts (this skill)
| Dimension | Skill↔dim | Role↔dim | Outcome |
|---|---|---|---|
|
Messaging and Event Streaming
messaging-and-event-streaming
|
✓ | ✓ | Existing dimension (library) · Role↔dimension saved |
Aliases — from this run (catalog unavailable)
- RabbitMQ (CANONICAL) primary
Skill profile (library / DB)
- Skill nature
- TOOL
- Volatility
- STABLE
- Typical lifespan
- EVERGREEN
- Category id
- 11
- Sub-category id
- 743
- Extractable
- True
- Also category
- False
Dimensions (API 2 worklist)
-
Messaging and Event Streaming Catalog dimension db id 146
Library dimension (catalog)
Roles linked in library: Backend Engineer
API 3 link attempts (this skill)
| Dimension | Skill↔dim | Role↔dim | Outcome |
|---|---|---|---|
|
Messaging and Event Streaming
messaging-and-event-streaming
|
✓ | ✓ | Existing dimension (library) · Role↔dimension saved |
Aliases — catalog
- Metabase (CANONICAL) primary
Context tags (catalog)
Stored enrichment (catalog DB)
- Category
- Tool
- Sub-category
- Bi Analytics Tool
- Vendor
- Metabase, Inc.
- License
- apache_2
- Year introduced
- 2014
- Confidence
- 0.90
- Version strategy
- NOT_APPLICABLE
Maturity reasoning: Metabase appears in many BI/analytics job postings and is growing in GitHub usage, but it is still far less universal than Tableau/Power BI in enterprise JDs.
Skill profile (library / DB)
- Skill nature
- TOOL
- Volatility
- STABLE
- Typical lifespan
- EVERGREEN
- Category id
- 11
- Sub-category id
- 170
- Extractable
- True
- Also category
- False
Dimensions (API 2 worklist)
-
Containerization and Image Delivery Catalog dimension db id 24
Library dimension (catalog)
Roles linked in library: DevOps Engineer
-
Model Serving Deployment and Runtime Packaging Catalog dimension db id 52
Library dimension (catalog)
Roles linked in library: MLOps Engineer, Machine Learning Engineer
API 3 link attempts (this skill)
| Dimension | Skill↔dim | Role↔dim | Outcome |
|---|---|---|---|
|
Containerization and Image Delivery
containerization-and-image-delivery
|
✓ | — | Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role) |
|
Model Serving Deployment and Runtime Packaging
model-serving-deployment-and-runtime-packaging
|
✓ | — | Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role) |
Aliases — catalog
- Column-level security (CANONICAL) primary
Context tags (catalog)
Stored enrichment (catalog DB)
- Category
- Concept
- Sub-category
- Access Control Concept
- Confidence
- 0.90
- Version strategy
- NOT_APPLICABLE
Maturity reasoning: Appears in cloud/data platform JDs and vendor docs for Snowflake, BigQuery, and PostgreSQL RLS/column masking, but is not yet a universal hiring staple like core IAM or RBAC.
Skill profile (library / DB)
- Skill nature
- PLATFORM
- Volatility
- STABLE
- Typical lifespan
- EVERGREEN
- Category id
- 13
- Sub-category id
- 1524
- Extractable
- True
- Also category
- False
Dimensions (API 2 worklist)
-
Orchestration Platforms Catalog dimension db id 25
Library dimension (catalog)
Roles linked in library: Cloud Engineer, DevOps Engineer
API 3 link attempts (this skill)
| Dimension | Skill↔dim | Role↔dim | Outcome |
|---|---|---|---|
|
Orchestration Platforms
orchestration-platforms
|
✓ | — | Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role) |
Aliases — from this run (catalog unavailable)
- Git (CANONICAL)
Skill profile (library / DB)
- Skill nature
- TOOL
- Volatility
- STABLE
- Typical lifespan
- EVERGREEN
- Category id
- 11
- Sub-category id
- 2101
- Extractable
- True
- Also category
- False
Dimensions (API 2 worklist)
-
Version Control Systems Catalog dimension db id 365
Library dimension (catalog)
API 3 link attempts (this skill)
| Dimension | Skill↔dim | Role↔dim | Outcome |
|---|---|---|---|
|
Version Control Systems
d_init_01
|
✓ | — | Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role) |
Aliases — from this run (catalog unavailable)
- CI/CD (CANONICAL)
Skill profile (library / DB)
- Skill nature
- METHODOLOGY
- Volatility
- STABLE
- Typical lifespan
- EVERGREEN
- Category id
- 7
- Sub-category id
- 2102
- Extractable
- True
- Also category
- False
Dimensions (API 2 worklist)
-
Version Control Systems Catalog dimension db id 365
Library dimension (catalog)
API 3 link attempts (this skill)
| Dimension | Skill↔dim | Role↔dim | Outcome |
|---|---|---|---|
|
Version Control Systems
d_init_01
|
✓ | — | Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role) |
Aliases — catalog
- Compaction (CANONICAL) primary
Context tags (catalog)
Stored enrichment (catalog DB)
- Category
- Concept
- Sub-category
- Storage Maintenance Concept
- Confidence
- 0.74
- Version strategy
- NOT_APPLICABLE
Maturity reasoning: Compaction is a standard storage-maintenance concept in widely used systems like LSM databases and Kafka; it appears in many JDs for Cassandra, RocksDB, and Kafka ops roles, indicating broad market demand.
Skill profile (library / DB)
- Skill nature
- PLATFORM
- Volatility
- STABLE
- Typical lifespan
- EVERGREEN
- Category id
- 13
- Sub-category id
- 161
- Extractable
- True
- Also category
- False
Dimensions (API 2 worklist)
-
Cloud Platform Operations Catalog dimension db id 26
Library dimension (catalog)
Roles linked in library: DevOps Engineer
-
Cloud Security Platforms Catalog dimension db id 332
Library dimension (catalog)
Roles linked in library: Cybersecurity Engineer
API 3 link attempts (this skill)
| Dimension | Skill↔dim | Role↔dim | Outcome |
|---|---|---|---|
|
Cloud Platform Operations
cloud-platform-operations
|
✓ | — | Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role) |
|
Cloud Security Platforms
cloud-security-platforms
|
✓ | — | Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role) |
Aliases — catalog
- Compute right-sizing (CANONICAL) primary
Context tags (catalog)
Stored enrichment (catalog DB)
- Category
- Methodology
- Sub-category
- Capacity Planning Methodology
- Confidence
- 0.78
- Version strategy
- NOT_APPLICABLE
Maturity reasoning: Common cloud/capacity-planning practice; widely referenced in AWS/Azure/GCP cost-optimization docs and frequently appears in FinOps and SRE job descriptions focused on reducing overprovisioning.
Skill profile (library / DB)
- Skill nature
- PLATFORM
- Volatility
- STABLE
- Typical lifespan
- EVERGREEN
- Category id
- 13
- Sub-category id
- 161
- Extractable
- True
- Also category
- False
Dimensions (API 2 worklist)
-
Cloud Platform Operations Catalog dimension db id 26
Library dimension (catalog)
Roles linked in library: DevOps Engineer
-
Cloud Security Platforms Catalog dimension db id 332
Library dimension (catalog)
Roles linked in library: Cybersecurity Engineer
API 3 link attempts (this skill)
| Dimension | Skill↔dim | Role↔dim | Outcome |
|---|---|---|---|
|
Cloud Platform Operations
cloud-platform-operations
|
✓ | — | Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role) |
|
Cloud Security Platforms
cloud-security-platforms
|
✓ | — | Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role) |
Aliases — catalog
- ASGI (CANONICAL) primary
Context tags (catalog)
Stored enrichment (catalog DB)
- Category
- Protocol
- Sub-category
- Web Application Protocol
- Vendor
- Django Software Foundation
- License
- bsd
- Year introduced
- 2016
- Confidence
- 0.95
- Version strategy
- NOT_APPLICABLE
Maturity reasoning: ASGI appears in many Python web JDs for async frameworks like FastAPI/Starlette, but WSGI remains the broader default in legacy stacks; market signal shows growing adoption rather than universal demand.
Skill profile (library / DB)
- Skill nature
- PLATFORM
- Volatility
- STABLE
- Typical lifespan
- EVERGREEN
- Category id
- 13
- Sub-category id
- 161
- Extractable
- True
- Also category
- False
Dimensions (API 2 worklist)
-
Cloud Security Platforms Catalog dimension db id 332
Library dimension (catalog)
Roles linked in library: Cybersecurity Engineer
API 3 link attempts (this skill)
| Dimension | Skill↔dim | Role↔dim | Outcome |
|---|---|---|---|
|
Cloud Security Platforms
cloud-security-platforms
|
✓ | — | Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role) |
Aliases — catalog
- Replay processing (CANONICAL) primary
Context tags (catalog)
Stored enrichment (catalog DB)
- Category
- Methodology
- Sub-category
- Data Reprocessing Methodology
- Confidence
- 0.77
- Version strategy
- NOT_APPLICABLE
Maturity reasoning: Replay processing appears in specialized data/streaming and event-sourcing JDs, but far less often than core ETL or batch processing; market demand is concentrated in a narrow set of platforms and teams.
Skill profile (library / DB)
- Skill nature
- PLATFORM
- Volatility
- STABLE
- Typical lifespan
- EVERGREEN
- Category id
- 13
- Sub-category id
- 729
- Extractable
- True
- Also category
- False
Dimensions (API 2 worklist)
-
Observability and Alerting Catalog dimension db id 27
Library dimension (catalog)
Roles linked in library: DevOps Engineer
-
Observability and Diagnostics Catalog dimension db id 151
Library dimension (catalog)
Roles linked in library: Backend Engineer
API 3 link attempts (this skill)
| Dimension | Skill↔dim | Role↔dim | Outcome |
|---|---|---|---|
|
Observability and Alerting
observability-and-alerting
|
✓ | — | Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role) |
|
Observability and Diagnostics
observability-and-diagnostics
|
✓ | ✓ | Existing dimension (library) · Role↔dimension saved |
Aliases — catalog
- Recovery runbooks (CANONICAL) primary
Context tags (catalog)
Stored enrichment (catalog DB)
- Category
- Methodology
- Sub-category
- Operational Runbook Methodology
- Confidence
- 0.93
- Version strategy
- NOT_APPLICABLE
Maturity reasoning: Common SRE/ops requirement: many job descriptions for DevOps/SRE/Platform roles explicitly ask for incident response and recovery runbooks, and major vendors like AWS/Azure document runbooks as standard operational practice.
Skill profile (library / DB)
- Skill nature
- TOOL
- Volatility
- STABLE
- Typical lifespan
- EVERGREEN
- Category id
- 11
- Sub-category id
- 331
- Extractable
- True
- Also category
- False
Dimensions (API 2 worklist)
-
Observability and Alerting Catalog dimension db id 27
Library dimension (catalog)
Roles linked in library: DevOps Engineer
-
Observability and Diagnostics Catalog dimension db id 151
Library dimension (catalog)
Roles linked in library: Backend Engineer
API 3 link attempts (this skill)
| Dimension | Skill↔dim | Role↔dim | Outcome |
|---|---|---|---|
|
Observability and Alerting
observability-and-alerting
|
✓ | — | Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role) |
|
Observability and Diagnostics
observability-and-diagnostics
|
✓ | ✓ | Existing dimension (library) · Role↔dimension saved |
Aliases — from this run (catalog unavailable)
- Agile (CANONICAL)
Skill profile (library / DB)
- Skill nature
- METHODOLOGY
- Volatility
- STABLE
- Typical lifespan
- EVERGREEN
- Category id
- 7
- Sub-category id
- 2124
- Extractable
- True
- Also category
- False
Dimensions (API 2 worklist)
-
Project Delivery and Coordination Catalog dimension db id 366
Library dimension (catalog)
-
Version Control Systems Catalog dimension db id 365
Library dimension (catalog)
API 3 link attempts (this skill)
| Dimension | Skill↔dim | Role↔dim | Outcome |
|---|---|---|---|
|
Project Delivery and Coordination
d_init_02
|
✓ | — | Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role) |
|
Version Control Systems
d_init_01
|
✓ | — | Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role) |
Aliases — from this run (catalog unavailable)
- Scrum (CANONICAL)
Skill profile (library / DB)
- Skill nature
- METHODOLOGY
- Volatility
- STABLE
- Typical lifespan
- EVERGREEN
- Category id
- 7
- Sub-category id
- 2125
- Extractable
- True
- Also category
- False
Dimensions (API 2 worklist)
-
Version Control Systems Catalog dimension db id 365
Library dimension (catalog)
API 3 link attempts (this skill)
| Dimension | Skill↔dim | Role↔dim | Outcome |
|---|---|---|---|
|
Version Control Systems
d_init_01
|
✓ | — | Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role) |
Aliases — catalog
- structured logging (CANONICAL) primary
- Structured logging (CANONICAL)
Context tags (catalog)
Stored enrichment (catalog DB)
- Category
- Concept
- Sub-category
- Structured Logging
- Confidence
- 0.91
- Version strategy
- NOT_APPLICABLE
Maturity reasoning: Commonly required in JDs for observability/SRE roles and supported by major stacks (e.g., JSON logs in ELK, Datadog, OpenTelemetry); market demand is broad rather than niche.
Skill profile (library / DB)
- Skill nature
- PROTOCOL
- Volatility
- STABLE
- Typical lifespan
- EVERGREEN
- Category id
- 8
- Sub-category id
- 651
- Extractable
- True
- Also category
- False
Dimensions (API 2 worklist)
-
API Integration and Data Fetching Catalog dimension db id 9
Library dimension (catalog)
Roles linked in library: Frontend Engineer, Full Stack Developer
-
API Integration and Serialization Catalog dimension db id 128
Library dimension (catalog)
Roles linked in library: iOS Engineer
API 3 link attempts (this skill)
| Dimension | Skill↔dim | Role↔dim | Outcome |
|---|---|---|---|
|
API Integration and Data Fetching
api-integration-and-data-fetching
|
✓ | — | Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role) |
|
API Integration and Serialization
api-integration-and-serialization
|
✓ | — | Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role) |
Aliases — catalog
- pre-production signoff (CANONICAL) primary
Context tags (catalog)
Stored enrichment (catalog DB)
- Category
- SoftSkill
- Sub-category
- Approval Coordination
- Confidence
- 0.78
- Version strategy
- NOT_APPLICABLE
Maturity reasoning: Common release-gate requirement in JDs for QA/release managers and DevOps; often listed as UAT/production approval or go-live signoff in enterprise hiring pipelines.
Skill profile (library / DB)
- Skill nature
- PATTERN
- Volatility
- STABLE
- Typical lifespan
- EVERGREEN
- Category id
- 1
- Sub-category id
- 911
- Extractable
- True
- Also category
- False
Dimensions (API 2 worklist)
-
Cloud Service Integration Patterns Catalog dimension db id 188
Library dimension (catalog)
Roles linked in library: Cloud Architect
API 3 link attempts (this skill)
| Dimension | Skill↔dim | Role↔dim | Outcome |
|---|---|---|---|
|
Cloud Service Integration Patterns
cloud-service-integration-patterns
|
✓ | — | Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role) |
All API 3 persistence rows
Same grid as the skill-extractor “Persistence items” table: one row per (skill × dimension) work item.
| Skill | Tag | Dimension | Skill↔dim | Role↔dim | Outcome | Notes |
|---|---|---|---|---|---|---|
| REST | in_db |
API Integration and Data Fetching
api-integration-and-data-fetching
|
✓ | — | Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role) | |
| Node.js | in_db |
Programming Languages for Backend Systems
programming-languages-for-backend-systems
|
✓ | ✓ | Existing dimension (library) · Role↔dimension saved | |
| Java | in_db |
Programming Languages for AI Workflows
programming-languages-for-ai-workflows
|
✓ | — | Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role) | |
| Java | in_db |
Programming Languages for Backend Systems
programming-languages-for-backend-systems
|
✓ | ✓ | Existing dimension (library) · Role↔dimension saved | |
| Java | in_db |
Programming Languages for Data Work
programming-languages-for-data-work
|
✓ | — | Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role) | |
| Java | in_db |
Programming Languages for ML Systems
programming-languages-for-ml-systems
|
✓ | — | Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role) | |
| Java | in_db |
Programming Languages for Test Automation
programming-languages-for-test-automation
|
✓ | — | Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role) | |
| Python | in_db |
Analytical Programming Languages
analytical-programming-languages
|
✓ | — | Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role) | |
| Python | in_db |
Automation Scripting and CLI
automation-scripting-and-cli
|
✓ | — | Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role) | |
| Python | in_db |
Automation and Scripting for Operations
automation-and-scripting-for-operations
|
✓ | — | Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role) | |
| Python | in_db |
Network Automation and Scripting
network-automation-and-scripting
|
✓ | — | Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role) | |
| Python | in_db |
Programming Languages for AI Workflows
programming-languages-for-ai-workflows
|
✓ | — | Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role) | |
| Python | in_db |
Programming Languages for Backend Systems
programming-languages-for-backend-systems
|
✓ | ✓ | Existing dimension (library) · Role↔dimension saved | |
| Python | in_db |
Programming Languages for Data Work
programming-languages-for-data-work
|
✓ | — | Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role) | |
| Python | in_db |
Programming Languages for ML Systems
programming-languages-for-ml-systems
|
✓ | — | Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role) | |
| Python | in_db |
Programming Languages for Security Work
programming-languages-for-security-work
|
✓ | — | Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role) | |
| Python | in_db |
Programming Languages for Test Automation
programming-languages-for-test-automation
|
✓ | — | Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role) | |
| Python | in_db |
Security Automation and Scripting
security-automation-and-scripting
|
✓ | — | Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role) | |
| Go | in_db |
Programming Languages for Backend Systems
programming-languages-for-backend-systems
|
✓ | ✓ | Existing dimension (library) · Role↔dimension saved | |
| Go | in_db |
Programming Languages for ML Systems
programming-languages-for-ml-systems
|
✓ | — | Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role) | |
| Go | in_db |
Programming Languages for Security Work
programming-languages-for-security-work
|
✓ | — | Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role) | |
| Spring Boot | in_db |
Inference Service Frameworks
inference-service-frameworks
|
✓ | — | Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role) | |
| Spring Boot | in_db |
Web Service Frameworks
web-service-frameworks
|
✓ | ✓ | Existing dimension (library) · Role↔dimension saved | |
| FastAPI | in_db |
Inference Service Frameworks
inference-service-frameworks
|
✓ | — | Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role) | |
| FastAPI | in_db |
Web Service Frameworks
web-service-frameworks
|
✓ | ✓ | Existing dimension (library) · Role↔dimension saved | |
| Microservices | in_db |
Service Architecture and Integration
service-architecture-and-integration
|
✓ | ✓ | Existing dimension (library) · Role↔dimension saved | |
| MongoDB | in_db |
NoSQL and Cache Stores
nosql-and-cache-stores
|
✓ | ✓ | Existing dimension (library) · Role↔dimension saved | |
| MongoDB | in_db |
NoSQL and Data Lake Storage
nosql-and-data-lake-storage
|
✓ | — | Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role) | |
| Redis | in_db |
NoSQL and Cache Stores
nosql-and-cache-stores
|
✓ | ✓ | Existing dimension (library) · Role↔dimension saved | |
| Kafka | in_db |
Messaging and Event Streaming
messaging-and-event-streaming
|
✓ | ✓ | Existing dimension (library) · Role↔dimension saved | |
| RabbitMQ | in_db |
Messaging and Event Streaming
messaging-and-event-streaming
|
✓ | ✓ | Existing dimension (library) · Role↔dimension saved | |
| Docker | in_db |
Containerization and Image Delivery
containerization-and-image-delivery
|
✓ | — | Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role) | |
| Docker | in_db |
Model Serving Deployment and Runtime Packaging
model-serving-deployment-and-runtime-packaging
|
✓ | — | Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role) | |
| Kubernetes | in_db |
Orchestration Platforms
orchestration-platforms
|
✓ | — | Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role) | |
| Git | in_db |
Version Control Systems
d_init_01
|
✓ | — | Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role) | |
| CI/CD | in_db |
Version Control Systems
d_init_01
|
✓ | — | Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role) | |
| AWS | in_db |
Cloud Platform Operations
cloud-platform-operations
|
✓ | — | Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role) | |
| AWS | in_db |
Cloud Security Platforms
cloud-security-platforms
|
✓ | — | Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role) | |
| Azure | in_db |
Cloud Platform Operations
cloud-platform-operations
|
✓ | — | Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role) | |
| Azure | in_db |
Cloud Security Platforms
cloud-security-platforms
|
✓ | — | Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role) | |
| GCP | in_db |
Cloud Security Platforms
cloud-security-platforms
|
✓ | — | Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role) | |
| Prometheus | in_db |
Observability and Alerting
observability-and-alerting
|
✓ | — | Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role) | |
| Prometheus | in_db |
Observability and Diagnostics
observability-and-diagnostics
|
✓ | ✓ | Existing dimension (library) · Role↔dimension saved | |
| Grafana | in_db |
Observability and Alerting
observability-and-alerting
|
✓ | — | Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role) | |
| Grafana | in_db |
Observability and Diagnostics
observability-and-diagnostics
|
✓ | ✓ | Existing dimension (library) · Role↔dimension saved | |
| Agile | in_db |
Project Delivery and Coordination
d_init_02
|
✓ | — | Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role) | |
| Agile | in_db |
Version Control Systems
d_init_01
|
✓ | — | Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role) | |
| Scrum | in_db |
Version Control Systems
d_init_01
|
✓ | — | Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role) | |
| GraphQL | in_db |
API Integration and Data Fetching
api-integration-and-data-fetching
|
✓ | — | Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role) | |
| GraphQL | in_db |
API Integration and Serialization
api-integration-and-serialization
|
✓ | — | Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role) | |
| Event-Driven Architecture | in_db |
Cloud Service Integration Patterns
cloud-service-integration-patterns
|
✓ | — | Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role) | |
| Express.js | in_db |
Version Control Systems
d_init_01
|
✓ | — | New skill saved · Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role) | |
| PostgreSQL | in_db |
Version Control Systems
d_init_01
|
✓ | — | New skill saved · Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role) | |
| MySQL | in_db |
MySQL Operational Monitoring, Logging, and Diagnostics
mysql-operational-monitoring-logging-and-diagnostics
|
✓ | — | New skill saved · Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role) | |
| MySQL | in_db |
Data Access and Query Optimization
data-access-and-query-optimization
|
✓ | — | New skill saved · Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role) | |
| MySQL | in_db |
MySQL Operational Monitoring, Logging, and Diagnostics
d_merge_01
|
✓ | — | New skill saved · Existing dimension (reconciliation merge) · Role↔dimension skipped (dimension not under chosen role) |
Library artifacts (this run)
| Kind | Detail | DB id |
|---|---|---|
| canonical_skill_added | Express.js | 2668 |
| canonical_skill_added | PostgreSQL | 2669 |
| canonical_skill_added | MySQL | 2670 |
| library_enrichment_backfilled | Scrum | 2605 |
| dimension_skill_link | Express.js ↔ Version Control Systems | 365 |
| dimension_skill_link | PostgreSQL ↔ Version Control Systems | 365 |
| dimension_skill_link | MySQL ↔ MySQL Operational Monitoring, Logging, and Diagnostics | 166 |
| dimension_skill_link | MySQL ↔ Data Access and Query Optimization | 74 |
nano JD Parser — gpt-4.1-nano click to toggle
Show raw JSON
{
"JD_type": "pass",
"about_company": null,
"certifications": [],
"company_name": null,
"ctc": null,
"domain": {
"primary": {
"aliases": [
"Enterprise Software",
"B2B Software"
],
"domain": "Software \u0026 SaaS Products"
},
"secondary": null
},
"education": [],
"experience": {
"max": 5,
"min": 2,
"raw": "2\u20135 Years"
},
"job_locations": [
{
"aliases": [],
"city": null,
"country": null,
"state": null,
"work_mode": "remote"
},
{
"aliases": [],
"city": null,
"country": null,
"state": null,
"work_mode": "hybrid"
},
{
"aliases": [],
"city": null,
"country": null,
"state": null,
"work_mode": "onsite"
}
],
"role": "Backend Engineer",
"role_archetype": "Engineering",
"roles_and_responsibilities": [
{
"bullet_count": 9,
"heading": "Key Responsibilities",
"heading_was_present": true,
"source_marker": {
"first_5_words": "Design and develop RESTful APIs",
"last_5_words": "and technical discussions"
},
"text": "Design and develop RESTful APIs and backend services\nBuild scalable microservices and server-side applications\nOptimize application performance and database queries\nImplement authentication, authorization, and security best practices\nIntegrate third-party APIs and cloud services\nWrite clean, maintainable, and testable code\nCollaborate with frontend and DevOps teams for deployment and integration\nMonitor applications, debug issues, and improve system stability\nParticipate in code reviews and technical discussions",
"word_count": 86
},
{
"bullet_count": 9,
"heading": "Required Skills",
"heading_was_present": true,
"source_marker": {
"first_5_words": "Strong proficiency in Node.js /",
"last_5_words": "skills"
},
"text": "Strong proficiency in Node.js / Java / Python / Go\nExperience with Express.js, Spring Boot, FastAPI, or similar frameworks\nGood understanding of REST APIs and microservices architecture\nExperience with databases such as PostgreSQL, MySQL, or MongoDB\nKnowledge of Redis, Kafka, or RabbitMQ is a plus\nFamiliarity with Docker and Kubernetes\nUnderstanding of Git and CI/CD pipelines\nKnowledge of AWS, Azure, or GCP cloud platforms\nStrong problem-solving and debugging skills",
"word_count": 94
},
{
"bullet_count": 4,
"heading": "Preferred Qualifications",
"heading_was_present": true,
"source_marker": {
"first_5_words": "Experience with scalable distributed",
"last_5_words": "methodologies"
},
"text": "Experience with scalable distributed systems\nUnderstanding of caching and performance optimization\nFamiliarity with monitoring tools like Prometheus or Grafana\nExposure to Agile/Scrum methodologies",
"word_count": 36
},
{
"bullet_count": 3,
"heading": "Nice to Have",
"heading_was_present": true,
"source_marker": {
"first_5_words": "Experience with GraphQL",
"last_5_words": "projects"
},
"text": "Experience with GraphQL\nKnowledge of event-driven architecture\nOpen-source contributions or personal backend projects",
"word_count": 17
}
],
"urls": []
}
API 1 — extract-from-jd click to toggle
{
"final_skills": [
{
"is_primary": true,
"skill_name": "REST"
},
{
"is_primary": true,
"skill_name": "Node.js"
},
{
"is_primary": true,
"skill_name": "Java"
},
{
"is_primary": true,
"skill_name": "Python"
},
{
"is_primary": true,
"skill_name": "Go"
},
{
"is_primary": true,
"skill_name": "Express.js"
},
{
"is_primary": true,
"skill_name": "Spring Boot"
},
{
"is_primary": true,
"skill_name": "FastAPI"
},
{
"is_primary": true,
"skill_name": "Microservices"
},
{
"is_primary": true,
"skill_name": "PostgreSQL"
},
{
"is_primary": true,
"skill_name": "MySQL"
},
{
"is_primary": true,
"skill_name": "MongoDB"
},
{
"is_primary": false,
"skill_name": "Redis"
},
{
"is_primary": false,
"skill_name": "Kafka"
},
{
"is_primary": false,
"skill_name": "RabbitMQ"
},
{
"is_primary": true,
"skill_name": "Docker"
},
{
"is_primary": true,
"skill_name": "Kubernetes"
},
{
"is_primary": true,
"skill_name": "Git"
},
{
"is_primary": true,
"skill_name": "CI/CD"
},
{
"is_primary": true,
"skill_name": "AWS"
},
{
"is_primary": true,
"skill_name": "Azure"
},
{
"is_primary": true,
"skill_name": "GCP"
},
{
"is_primary": false,
"skill_name": "Prometheus"
},
{
"is_primary": false,
"skill_name": "Grafana"
},
{
"is_primary": false,
"skill_name": "Agile"
},
{
"is_primary": false,
"skill_name": "Scrum"
},
{
"is_primary": false,
"skill_name": "GraphQL"
},
{
"is_primary": false,
"skill_name": "Event-Driven Architecture"
}
],
"jd_role": {
"display_name": "Backend Engineer",
"rationale": null,
"role_archetype": "Engineering",
"slug": ""
},
"nano_parsed": {
"JD_type": "pass",
"about_company": null,
"certifications": [],
"company_name": null,
"ctc": null,
"domain": {
"primary": {
"aliases": [
"Enterprise Software",
"B2B Software"
],
"domain": "Software \u0026 SaaS Products"
},
"secondary": null
},
"education": [],
"experience": {
"max": 5,
"min": 2,
"raw": "2\u20135 Years"
},
"job_locations": [
{
"aliases": [],
"city": null,
"country": null,
"state": null,
"work_mode": "remote"
},
{
"aliases": [],
"city": null,
"country": null,
"state": null,
"work_mode": "hybrid"
},
{
"aliases": [],
"city": null,
"country": null,
"state": null,
"work_mode": "onsite"
}
],
"role": "Backend Engineer",
"role_archetype": "Engineering",
"roles_and_responsibilities": [
{
"bullet_count": 9,
"heading": "Key Responsibilities",
"heading_was_present": true,
"source_marker": {
"first_5_words": "Design and develop RESTful APIs",
"last_5_words": "and technical discussions"
},
"text": "Design and develop RESTful APIs and backend services\nBuild scalable microservices and server-side applications\nOptimize application performance and database queries\nImplement authentication, authorization, and security best practices\nIntegrate third-party APIs and cloud services\nWrite clean, maintainable, and testable code\nCollaborate with frontend and DevOps teams for deployment and integration\nMonitor applications, debug issues, and improve system stability\nParticipate in code reviews and technical discussions",
"word_count": 86
},
{
"bullet_count": 9,
"heading": "Required Skills",
"heading_was_present": true,
"source_marker": {
"first_5_words": "Strong proficiency in Node.js /",
"last_5_words": "skills"
},
"text": "Strong proficiency in Node.js / Java / Python / Go\nExperience with Express.js, Spring Boot, FastAPI, or similar frameworks\nGood understanding of REST APIs and microservices architecture\nExperience with databases such as PostgreSQL, MySQL, or MongoDB\nKnowledge of Redis, Kafka, or RabbitMQ is a plus\nFamiliarity with Docker and Kubernetes\nUnderstanding of Git and CI/CD pipelines\nKnowledge of AWS, Azure, or GCP cloud platforms\nStrong problem-solving and debugging skills",
"word_count": 94
},
{
"bullet_count": 4,
"heading": "Preferred Qualifications",
"heading_was_present": true,
"source_marker": {
"first_5_words": "Experience with scalable distributed",
"last_5_words": "methodologies"
},
"text": "Experience with scalable distributed systems\nUnderstanding of caching and performance optimization\nFamiliarity with monitoring tools like Prometheus or Grafana\nExposure to Agile/Scrum methodologies",
"word_count": 36
},
{
"bullet_count": 3,
"heading": "Nice to Have",
"heading_was_present": true,
"source_marker": {
"first_5_words": "Experience with GraphQL",
"last_5_words": "projects"
},
"text": "Experience with GraphQL\nKnowledge of event-driven architecture\nOpen-source contributions or personal backend projects",
"word_count": 17
}
],
"urls": []
},
"run_id": null
}
API 2 — extract-details
{
"alias_matches": [
{
"alias_persist_skipped_reason": "alias_text already exists for this canonical skill",
"alias_persisted": false,
"existing_alias_id": 266,
"existing_alias_text": "REST",
"input_term": "REST",
"matched_canonical": {
"category_id": 8,
"display_name": "REST",
"id": 121,
"is_also_category": false,
"is_extractable": true,
"skill_nature": "PROTOCOL",
"slug": "rest",
"sub_category_id": 67,
"typical_lifespan": "EVERGREEN",
"volatility": "STABLE"
},
"matched_via": "alias"
},
{
"alias_persist_skipped_reason": "alias_text already exists for this canonical skill",
"alias_persisted": false,
"existing_alias_id": 3396,
"existing_alias_text": "Node.js",
"input_term": "Node.js",
"matched_canonical": {
"category_id": 271,
"display_name": "Node.js",
"id": 2599,
"is_also_category": false,
"is_extractable": true,
"skill_nature": "RUNTIME",
"slug": "node-js",
"sub_category_id": 2120,
"typical_lifespan": "EVERGREEN",
"volatility": "STABLE"
},
"matched_via": "alias"
},
{
"alias_persist_skipped_reason": "alias_text already exists for this canonical skill",
"alias_persisted": false,
"existing_alias_id": 616,
"existing_alias_text": "Java",
"input_term": "Java",
"matched_canonical": {
"category_id": 5,
"display_name": "Java",
"id": 395,
"is_also_category": false,
"is_extractable": true,
"skill_nature": "LANGUAGE",
"slug": "java",
"sub_category_id": 54,
"typical_lifespan": "EVERGREEN",
"volatility": "STABLE"
},
"matched_via": "alias"
},
{
"alias_persist_skipped_reason": "alias_text already exists for this canonical skill",
"alias_persisted": false,
"existing_alias_id": 608,
"existing_alias_text": "Python",
"input_term": "Python",
"matched_canonical": {
"category_id": 5,
"display_name": "Python",
"id": 393,
"is_also_category": false,
"is_extractable": true,
"skill_nature": "LANGUAGE",
"slug": "python",
"sub_category_id": 54,
"typical_lifespan": "EVERGREEN",
"volatility": "STABLE"
},
"matched_via": "alias"
},
{
"alias_persist_skipped_reason": "alias_text already exists for this canonical skill",
"alias_persisted": false,
"existing_alias_id": 1012,
"existing_alias_text": "Go",
"input_term": "Go",
"matched_canonical": {
"category_id": 5,
"display_name": "Go",
"id": 679,
"is_also_category": false,
"is_extractable": true,
"skill_nature": "LANGUAGE",
"slug": "go",
"sub_category_id": 54,
"typical_lifespan": "EVERGREEN",
"volatility": "STABLE"
},
"matched_via": "alias"
},
{
"alias_persist_skipped_reason": "alias_text already exists for this canonical skill",
"alias_persisted": false,
"existing_alias_id": 1024,
"existing_alias_text": "Spring Boot",
"input_term": "Spring Boot",
"matched_canonical": {
"category_id": 4,
"display_name": "Spring Boot",
"id": 684,
"is_also_category": false,
"is_extractable": true,
"skill_nature": "FRAMEWORK",
"slug": "spring-boot",
"sub_category_id": 708,
"typical_lifespan": "EVERGREEN",
"volatility": "STABLE"
},
"matched_via": "alias"
},
{
"alias_persist_skipped_reason": "alias_text already exists for this canonical skill",
"alias_persisted": false,
"existing_alias_id": 1022,
"existing_alias_text": "FastAPI",
"input_term": "FastAPI",
"matched_canonical": {
"category_id": 4,
"display_name": "FastAPI",
"id": 682,
"is_also_category": false,
"is_extractable": true,
"skill_nature": "FRAMEWORK",
"slug": "fastapi",
"sub_category_id": 52,
"typical_lifespan": "EVERGREEN",
"volatility": "STABLE"
},
"matched_via": "alias"
},
{
"alias_persist_skipped_reason": "alias_text already exists for this canonical skill",
"alias_persisted": false,
"existing_alias_id": 1307,
"existing_alias_text": "Microservices",
"input_term": "Microservices",
"matched_canonical": {
"category_id": 1,
"display_name": "Microservices",
"id": 864,
"is_also_category": false,
"is_extractable": true,
"skill_nature": "PATTERN",
"slug": "microservices",
"sub_category_id": 663,
"typical_lifespan": "EVERGREEN",
"volatility": "STABLE"
},
"matched_via": "alias"
},
{
"alias_persist_skipped_reason": "alias_text already exists for this canonical skill",
"alias_persisted": false,
"existing_alias_id": 684,
"existing_alias_text": "MongoDB",
"input_term": "MongoDB",
"matched_canonical": {
"category_id": 12,
"display_name": "MongoDB",
"id": 432,
"is_also_category": false,
"is_extractable": true,
"skill_nature": "TOOL",
"slug": "mongodb",
"sub_category_id": 360,
"typical_lifespan": "EVERGREEN",
"volatility": "STABLE"
},
"matched_via": "alias"
},
{
"alias_persist_skipped_reason": "alias_text already exists for this canonical skill",
"alias_persisted": false,
"existing_alias_id": 1278,
"existing_alias_text": "Redis",
"input_term": "Redis",
"matched_canonical": {
"category_id": 12,
"display_name": "Redis",
"id": 846,
"is_also_category": false,
"is_extractable": true,
"skill_nature": "TOOL",
"slug": "redis",
"sub_category_id": 701,
"typical_lifespan": "EVERGREEN",
"volatility": "STABLE"
},
"matched_via": "alias"
},
{
"alias_persist_skipped_reason": "alias_text already exists for this canonical skill",
"alias_persisted": false,
"existing_alias_id": 1284,
"existing_alias_text": "Kafka",
"input_term": "Kafka",
"matched_canonical": {
"category_id": 12,
"display_name": "Kafka",
"id": 852,
"is_also_category": false,
"is_extractable": true,
"skill_nature": "TOOL",
"slug": "kafka",
"sub_category_id": 700,
"typical_lifespan": "EVERGREEN",
"volatility": "STABLE"
},
"matched_via": "alias"
},
{
"alias_persist_skipped_reason": "alias_text already exists for this canonical skill",
"alias_persisted": false,
"existing_alias_id": 1296,
"existing_alias_text": "RabbitMQ",
"input_term": "RabbitMQ",
"matched_canonical": {
"category_id": 11,
"display_name": "RabbitMQ",
"id": 853,
"is_also_category": false,
"is_extractable": true,
"skill_nature": "TOOL",
"slug": "rabbitmq",
"sub_category_id": 743,
"typical_lifespan": "EVERGREEN",
"volatility": "STABLE"
},
"matched_via": "alias"
},
{
"alias_persist_skipped_reason": "alias_text already exists for this canonical skill",
"alias_persisted": false,
"existing_alias_id": 299,
"existing_alias_text": "Docker",
"input_term": "Docker",
"matched_canonical": {
"category_id": 11,
"display_name": "Docker",
"id": 153,
"is_also_category": false,
"is_extractable": true,
"skill_nature": "TOOL",
"slug": "docker",
"sub_category_id": 170,
"typical_lifespan": "EVERGREEN",
"volatility": "STABLE"
},
"matched_via": "alias"
},
{
"alias_persist_skipped_reason": "alias_text already exists for this canonical skill",
"alias_persisted": false,
"existing_alias_id": 304,
"existing_alias_text": "Kubernetes",
"input_term": "Kubernetes",
"matched_canonical": {
"category_id": 13,
"display_name": "Kubernetes",
"id": 158,
"is_also_category": false,
"is_extractable": true,
"skill_nature": "PLATFORM",
"slug": "kubernetes",
"sub_category_id": 1524,
"typical_lifespan": "EVERGREEN",
"volatility": "STABLE"
},
"matched_via": "alias"
},
{
"alias_persist_skipped_reason": "alias_text already exists for this canonical skill",
"alias_persisted": false,
"existing_alias_id": 3375,
"existing_alias_text": "Git",
"input_term": "Git",
"matched_canonical": {
"category_id": 11,
"display_name": "Git",
"id": 2578,
"is_also_category": false,
"is_extractable": true,
"skill_nature": "TOOL",
"slug": "git",
"sub_category_id": 2101,
"typical_lifespan": "EVERGREEN",
"volatility": "STABLE"
},
"matched_via": "alias"
},
{
"alias_persist_skipped_reason": "alias_text already exists for this canonical skill",
"alias_persisted": false,
"existing_alias_id": 3376,
"existing_alias_text": "CI/CD",
"input_term": "CI/CD",
"matched_canonical": {
"category_id": 7,
"display_name": "CI/CD",
"id": 2579,
"is_also_category": false,
"is_extractable": true,
"skill_nature": "METHODOLOGY",
"slug": "ci-cd",
"sub_category_id": 2102,
"typical_lifespan": "EVERGREEN",
"volatility": "STABLE"
},
"matched_via": "alias"
},
{
"alias_persist_skipped_reason": "alias_text already exists for this canonical skill",
"alias_persisted": false,
"existing_alias_id": 348,
"existing_alias_text": "AWS",
"input_term": "AWS",
"matched_canonical": {
"category_id": 13,
"display_name": "AWS",
"id": 163,
"is_also_category": false,
"is_extractable": true,
"skill_nature": "PLATFORM",
"slug": "aws",
"sub_category_id": 161,
"typical_lifespan": "EVERGREEN",
"volatility": "STABLE"
},
"matched_via": "alias"
},
{
"alias_persist_skipped_reason": "alias_text already exists for this canonical skill",
"alias_persisted": false,
"existing_alias_id": 349,
"existing_alias_text": "Azure",
"input_term": "Azure",
"matched_canonical": {
"category_id": 13,
"display_name": "Azure",
"id": 164,
"is_also_category": false,
"is_extractable": true,
"skill_nature": "PLATFORM",
"slug": "azure",
"sub_category_id": 161,
"typical_lifespan": "EVERGREEN",
"volatility": "STABLE"
},
"matched_via": "alias"
},
{
"alias_persist_skipped_reason": "alias_text already exists for this canonical skill",
"alias_persisted": false,
"existing_alias_id": 3043,
"existing_alias_text": "GCP",
"input_term": "GCP",
"matched_canonical": {
"category_id": 13,
"display_name": "GCP",
"id": 2304,
"is_also_category": false,
"is_extractable": true,
"skill_nature": "PLATFORM",
"slug": "gcp",
"sub_category_id": 161,
"typical_lifespan": "EVERGREEN",
"volatility": "STABLE"
},
"matched_via": "alias"
},
{
"alias_persist_skipped_reason": "alias_text already exists for this canonical skill",
"alias_persisted": false,
"existing_alias_id": 353,
"existing_alias_text": "Prometheus",
"input_term": "Prometheus",
"matched_canonical": {
"category_id": 13,
"display_name": "Prometheus",
"id": 168,
"is_also_category": false,
"is_extractable": true,
"skill_nature": "PLATFORM",
"slug": "prometheus",
"sub_category_id": 729,
"typical_lifespan": "EVERGREEN",
"volatility": "STABLE"
},
"matched_via": "alias"
},
{
"alias_persist_skipped_reason": "alias_text already exists for this canonical skill",
"alias_persisted": false,
"existing_alias_id": 354,
"existing_alias_text": "Grafana",
"input_term": "Grafana",
"matched_canonical": {
"category_id": 11,
"display_name": "Grafana",
"id": 169,
"is_also_category": false,
"is_extractable": true,
"skill_nature": "TOOL",
"slug": "grafana",
"sub_category_id": 331,
"typical_lifespan": "EVERGREEN",
"volatility": "STABLE"
},
"matched_via": "alias"
},
{
"alias_persist_skipped_reason": "alias_text already exists for this canonical skill",
"alias_persisted": false,
"existing_alias_id": 3401,
"existing_alias_text": "Agile",
"input_term": "Agile",
"matched_canonical": {
"category_id": 7,
"display_name": "Agile",
"id": 2604,
"is_also_category": false,
"is_extractable": true,
"skill_nature": "METHODOLOGY",
"slug": "agile",
"sub_category_id": 2124,
"typical_lifespan": "EVERGREEN",
"volatility": "STABLE"
},
"matched_via": "alias"
},
{
"alias_persist_skipped_reason": "alias_text already exists for this canonical skill",
"alias_persisted": false,
"existing_alias_id": 3402,
"existing_alias_text": "Scrum",
"input_term": "Scrum",
"matched_canonical": {
"category_id": 7,
"display_name": "Scrum",
"id": 2605,
"is_also_category": false,
"is_extractable": true,
"skill_nature": "METHODOLOGY",
"slug": "scrum",
"sub_category_id": 2125,
"typical_lifespan": "EVERGREEN",
"volatility": "STABLE"
},
"matched_via": "alias"
},
{
"alias_persist_skipped_reason": "alias_text already exists for this canonical skill",
"alias_persisted": false,
"existing_alias_id": 175,
"existing_alias_text": "GraphQL",
"input_term": "GraphQL",
"matched_canonical": {
"category_id": 8,
"display_name": "GraphQL",
"id": 50,
"is_also_category": false,
"is_extractable": true,
"skill_nature": "PROTOCOL",
"slug": "graphql",
"sub_category_id": 651,
"typical_lifespan": "EVERGREEN",
"volatility": "STABLE"
},
"matched_via": "alias"
},
{
"alias_persist_skipped_reason": "alias_text already exists for this canonical skill",
"alias_persisted": false,
"existing_alias_id": 1630,
"existing_alias_text": "Event-driven architecture",
"input_term": "Event-Driven Architecture",
"matched_canonical": {
"category_id": 1,
"display_name": "Event-driven architecture",
"id": 1156,
"is_also_category": false,
"is_extractable": true,
"skill_nature": "PATTERN",
"slug": "event-driven-architecture",
"sub_category_id": 911,
"typical_lifespan": "EVERGREEN",
"volatility": "STABLE"
},
"matched_via": "alias"
}
],
"candidate_roles": [
{
"display_name": "Frontend Engineer",
"id": 3,
"rationale": null,
"role_archetype": "Frontend Engineers design and build the user-facing parts of applications, translating product and design requirements into interactive experiences. They focus on how the application looks, behaves, and responds in the browser, ensuring usability, accessibility, and consistency across the interface.",
"slug": "frontend-engineer",
"source": "db"
},
{
"display_name": "Full Stack Developer",
"id": 2,
"rationale": null,
"role_archetype": null,
"slug": "full-stack-developer",
"source": "db"
},
{
"display_name": "Backend Engineer",
"id": 14,
"rationale": null,
"role_archetype": null,
"slug": "backend-engineer",
"source": "db"
},
{
"display_name": "AI Engineer",
"id": 12,
"rationale": null,
"role_archetype": null,
"slug": "ai-engineer",
"source": "db"
},
{
"display_name": "Data Engineer",
"id": 6,
"rationale": null,
"role_archetype": null,
"slug": "data-engineer",
"source": "db"
},
{
"display_name": "Machine Learning Engineer",
"id": 10,
"rationale": null,
"role_archetype": null,
"slug": "machine-learning-engineer",
"source": "db"
},
{
"display_name": "Automation Tester",
"id": 16,
"rationale": null,
"role_archetype": null,
"slug": "automation-tester",
"source": "db"
},
{
"display_name": "Data Analyst",
"id": 20,
"rationale": null,
"role_archetype": null,
"slug": "data-analyst",
"source": "db"
},
{
"display_name": "Data Scientist",
"id": 7,
"rationale": null,
"role_archetype": null,
"slug": "data-scientist",
"source": "db"
},
{
"display_name": "Azure Cloud Engineer",
"id": 4,
"rationale": null,
"role_archetype": null,
"slug": "azure-cloud-engineer",
"source": "db"
},
{
"display_name": "Cloud Engineer",
"id": 18,
"rationale": null,
"role_archetype": null,
"slug": "cloud-engineer",
"source": "db"
},
{
"display_name": "Virtualization Engineer",
"id": 26,
"rationale": null,
"role_archetype": null,
"slug": "virtualization-engineer",
"source": "db"
},
{
"display_name": "Network Engineer",
"id": 21,
"rationale": null,
"role_archetype": null,
"slug": "network-engineer",
"source": "db"
},
{
"display_name": "Cybersecurity Engineer",
"id": 9,
"rationale": null,
"role_archetype": null,
"slug": "cybersecurity-engineer",
"source": "db"
},
{
"display_name": "DevOps Engineer",
"id": 1,
"rationale": null,
"role_archetype": "A DevOps Engineer enables reliable, repeatable delivery of software by designing and operating the processes that connect development and production. They focus on improving deployment flow, operational stability, and collaboration between teams through automation, standardization, and monitoring of delivery and runtime practices.",
"slug": "devops-engineer",
"source": "db"
},
{
"display_name": "MLOps Engineer",
"id": 5,
"rationale": null,
"role_archetype": null,
"slug": "mlops-engineer",
"source": "db"
},
{
"display_name": "iOS Engineer",
"id": 13,
"rationale": null,
"role_archetype": null,
"slug": "ios-engineer",
"source": "db"
},
{
"display_name": "Cloud Architect",
"id": 11,
"rationale": null,
"role_archetype": null,
"slug": "cloud-architect",
"source": "db"
},
{
"display_name": "MySQL DBA",
"id": 23,
"rationale": null,
"role_archetype": null,
"slug": "mysql-dba",
"source": "db"
}
],
"chosen_role": {
"display_name": "Backend Engineer",
"id": 14,
"rationale": "The primary skills indicate a strong emphasis on backend development, which aligns with the role of a Backend Engineer.",
"role_archetype": null,
"slug": "backend-engineer",
"source": "db"
},
"dimensions": [
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "API Integration and Data Fetching",
"id": 9,
"rationale": "Connecting frontend applications to backend services and third-party endpoints. This covers request orchestration, error handling, pagination, and shaping remote data for UI consumption.",
"slug": "api-integration-and-data-fetching",
"source": "db"
},
"input_skill": "REST",
"llm_role": null,
"roles_from_db": [
{
"display_name": "Frontend Engineer",
"id": 3,
"rationale": null,
"role_archetype": "Frontend Engineers design and build the user-facing parts of applications, translating product and design requirements into interactive experiences. They focus on how the application looks, behaves, and responds in the browser, ensuring usability, accessibility, and consistency across the interface.",
"slug": "frontend-engineer",
"source": "db"
},
{
"display_name": "Full Stack Developer",
"id": 2,
"rationale": null,
"role_archetype": null,
"slug": "full-stack-developer",
"source": "db"
}
]
},
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Programming Languages for Backend Systems",
"id": 140,
"rationale": "Languages used to implement server-side business logic, request handlers, workers, and service integrations. This is the core coding surface for backend feature delivery and maintenance.",
"slug": "programming-languages-for-backend-systems",
"source": "db"
},
"input_skill": "Node.js",
"llm_role": null,
"roles_from_db": [
{
"display_name": "Backend Engineer",
"id": 14,
"rationale": null,
"role_archetype": null,
"slug": "backend-engineer",
"source": "db"
}
]
},
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Programming Languages for AI Workflows",
"id": 261,
"rationale": "Languages used to implement AI feature logic, orchestration, and response handling inside product code. This is the core coding surface for turning prompts and model calls into reliable application behavior.",
"slug": "programming-languages-for-ai-workflows",
"source": "db"
},
"input_skill": "Java",
"llm_role": null,
"roles_from_db": [
{
"display_name": "AI Engineer",
"id": 12,
"rationale": null,
"role_archetype": null,
"slug": "ai-engineer",
"source": "db"
}
]
},
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Programming Languages for Backend Systems",
"id": 140,
"rationale": "Languages used to implement server-side business logic, request handlers, workers, and service integrations. This is the core coding surface for backend feature delivery and maintenance.",
"slug": "programming-languages-for-backend-systems",
"source": "db"
},
"input_skill": "Java",
"llm_role": null,
"roles_from_db": [
{
"display_name": "Backend Engineer",
"id": 14,
"rationale": null,
"role_archetype": null,
"slug": "backend-engineer",
"source": "db"
}
]
},
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Programming Languages for Data Work",
"id": 67,
"rationale": "Languages used to implement data pipelines, transformations, and operational utilities. This is the code layer for expressing extraction, parsing, validation, and orchestration logic in data engineering workflows.",
"slug": "programming-languages-for-data-work",
"source": "db"
},
"input_skill": "Java",
"llm_role": null,
"roles_from_db": [
{
"display_name": "Data Engineer",
"id": 6,
"rationale": null,
"role_archetype": null,
"slug": "data-engineer",
"source": "db"
}
]
},
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Programming Languages for ML Systems",
"id": 113,
"rationale": "Languages used to implement model integration code, inference services, and feature-processing logic. This is the core coding surface for turning trained models into product-facing software components.",
"slug": "programming-languages-for-ml-systems",
"source": "db"
},
"input_skill": "Java",
"llm_role": null,
"roles_from_db": [
{
"display_name": "Machine Learning Engineer",
"id": 10,
"rationale": null,
"role_archetype": null,
"slug": "machine-learning-engineer",
"source": "db"
}
]
},
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Programming Languages for Test Automation",
"id": 193,
"rationale": "Languages used to implement automated checks, helper utilities, and test harness code. This is the core coding surface for turning test ideas into maintainable automation.",
"slug": "programming-languages-for-test-automation",
"source": "db"
},
"input_skill": "Java",
"llm_role": null,
"roles_from_db": [
{
"display_name": "Automation Tester",
"id": 16,
"rationale": null,
"role_archetype": null,
"slug": "automation-tester",
"source": "db"
}
]
},
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Analytical Programming Languages",
"id": 82,
"rationale": "Languages used to clean, transform, analyze, and prototype models in notebooks and scripts. This is the core coding surface for expressing statistical logic and data manipulation in a reproducible way.",
"slug": "analytical-programming-languages",
"source": "db"
},
"input_skill": "Python",
"llm_role": null,
"roles_from_db": [
{
"display_name": "Data Analyst",
"id": 20,
"rationale": null,
"role_archetype": null,
"slug": "data-analyst",
"source": "db"
},
{
"display_name": "Data Scientist",
"id": 7,
"rationale": null,
"role_archetype": null,
"slug": "data-scientist",
"source": "db"
}
]
},
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Automation Scripting and CLI",
"id": 48,
"rationale": "Uses scripts and command-line tooling to execute repeatable Azure operations and reduce manual work. This is a practical cluster because the role frequently automates provisioning, checks, and remediation tasks.",
"slug": "automation-scripting-and-cli",
"source": "db"
},
"input_skill": "Python",
"llm_role": null,
"roles_from_db": [
{
"display_name": "Azure Cloud Engineer",
"id": 4,
"rationale": null,
"role_archetype": null,
"slug": "azure-cloud-engineer",
"source": "db"
},
{
"display_name": "Cloud Engineer",
"id": 18,
"rationale": null,
"role_archetype": null,
"slug": "cloud-engineer",
"source": "db"
}
]
},
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Automation and Scripting for Operations",
"id": 361,
"rationale": "Scripts and lightweight automation used to execute repetitive virtualization tasks and enforce operational consistency. This is the practical glue that reduces manual host and VM administration.",
"slug": "automation-and-scripting-for-operations",
"source": "db"
},
"input_skill": "Python",
"llm_role": null,
"roles_from_db": [
{
"display_name": "Virtualization Engineer",
"id": 26,
"rationale": null,
"role_archetype": null,
"slug": "virtualization-engineer",
"source": "db"
}
]
},
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Network Automation and Scripting",
"id": 285,
"rationale": "Covers scripts and automation used to configure, validate, and audit network devices and services. This cluster is coherent because repeatable network operations increasingly depend on programmatic changes and checks.",
"slug": "network-automation-and-scripting",
"source": "db"
},
"input_skill": "Python",
"llm_role": null,
"roles_from_db": [
{
"display_name": "Network Engineer",
"id": 21,
"rationale": null,
"role_archetype": null,
"slug": "network-engineer",
"source": "db"
}
]
},
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Programming Languages for AI Workflows",
"id": 261,
"rationale": "Languages used to implement AI feature logic, orchestration, and response handling inside product code. This is the core coding surface for turning prompts and model calls into reliable application behavior.",
"slug": "programming-languages-for-ai-workflows",
"source": "db"
},
"input_skill": "Python",
"llm_role": null,
"roles_from_db": [
{
"display_name": "AI Engineer",
"id": 12,
"rationale": null,
"role_archetype": null,
"slug": "ai-engineer",
"source": "db"
}
]
},
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Programming Languages for Backend Systems",
"id": 140,
"rationale": "Languages used to implement server-side business logic, request handlers, workers, and service integrations. This is the core coding surface for backend feature delivery and maintenance.",
"slug": "programming-languages-for-backend-systems",
"source": "db"
},
"input_skill": "Python",
"llm_role": null,
"roles_from_db": [
{
"display_name": "Backend Engineer",
"id": 14,
"rationale": null,
"role_archetype": null,
"slug": "backend-engineer",
"source": "db"
}
]
},
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Programming Languages for Data Work",
"id": 67,
"rationale": "Languages used to implement data pipelines, transformations, and operational utilities. This is the code layer for expressing extraction, parsing, validation, and orchestration logic in data engineering workflows.",
"slug": "programming-languages-for-data-work",
"source": "db"
},
"input_skill": "Python",
"llm_role": null,
"roles_from_db": [
{
"display_name": "Data Engineer",
"id": 6,
"rationale": null,
"role_archetype": null,
"slug": "data-engineer",
"source": "db"
}
]
},
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Programming Languages for ML Systems",
"id": 113,
"rationale": "Languages used to implement model integration code, inference services, and feature-processing logic. This is the core coding surface for turning trained models into product-facing software components.",
"slug": "programming-languages-for-ml-systems",
"source": "db"
},
"input_skill": "Python",
"llm_role": null,
"roles_from_db": [
{
"display_name": "Machine Learning Engineer",
"id": 10,
"rationale": null,
"role_archetype": null,
"slug": "machine-learning-engineer",
"source": "db"
}
]
},
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Programming Languages for Security Work",
"id": 328,
"rationale": "Languages used to automate security tasks, write detection logic, and build analysis or remediation tooling. This is the core coding surface for a cybersecurity engineer across scripts, queries, and small utilities.",
"slug": "programming-languages-for-security-work",
"source": "db"
},
"input_skill": "Python",
"llm_role": null,
"roles_from_db": [
{
"display_name": "Cybersecurity Engineer",
"id": 9,
"rationale": null,
"role_archetype": null,
"slug": "cybersecurity-engineer",
"source": "db"
}
]
},
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Programming Languages for Test Automation",
"id": 193,
"rationale": "Languages used to implement automated checks, helper utilities, and test harness code. This is the core coding surface for turning test ideas into maintainable automation.",
"slug": "programming-languages-for-test-automation",
"source": "db"
},
"input_skill": "Python",
"llm_role": null,
"roles_from_db": [
{
"display_name": "Automation Tester",
"id": 16,
"rationale": null,
"role_archetype": null,
"slug": "automation-tester",
"source": "db"
}
]
},
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Security Automation and Scripting",
"id": 258,
"rationale": "Automating repeatable security checks, enrichment, and remediation workflows. This cluster is coherent because the role often needs lightweight automation to scale analysis and response.",
"slug": "security-automation-and-scripting",
"source": "db"
},
"input_skill": "Python",
"llm_role": null,
"roles_from_db": [
{
"display_name": "Cybersecurity Engineer",
"id": 9,
"rationale": null,
"role_archetype": null,
"slug": "cybersecurity-engineer",
"source": "db"
}
]
},
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Programming Languages for Backend Systems",
"id": 140,
"rationale": "Languages used to implement server-side business logic, request handlers, workers, and service integrations. This is the core coding surface for backend feature delivery and maintenance.",
"slug": "programming-languages-for-backend-systems",
"source": "db"
},
"input_skill": "Go",
"llm_role": null,
"roles_from_db": [
{
"display_name": "Backend Engineer",
"id": 14,
"rationale": null,
"role_archetype": null,
"slug": "backend-engineer",
"source": "db"
}
]
},
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Programming Languages for ML Systems",
"id": 113,
"rationale": "Languages used to implement model integration code, inference services, and feature-processing logic. This is the core coding surface for turning trained models into product-facing software components.",
"slug": "programming-languages-for-ml-systems",
"source": "db"
},
"input_skill": "Go",
"llm_role": null,
"roles_from_db": [
{
"display_name": "Machine Learning Engineer",
"id": 10,
"rationale": null,
"role_archetype": null,
"slug": "machine-learning-engineer",
"source": "db"
}
]
},
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Programming Languages for Security Work",
"id": 328,
"rationale": "Languages used to automate security tasks, write detection logic, and build analysis or remediation tooling. This is the core coding surface for a cybersecurity engineer across scripts, queries, and small utilities.",
"slug": "programming-languages-for-security-work",
"source": "db"
},
"input_skill": "Go",
"llm_role": null,
"roles_from_db": [
{
"display_name": "Cybersecurity Engineer",
"id": 9,
"rationale": null,
"role_archetype": null,
"slug": "cybersecurity-engineer",
"source": "db"
}
]
},
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Inference Service Frameworks",
"id": 114,
"rationale": "Web and service frameworks used to expose model predictions through APIs and application endpoints. This cluster is coherent because MLEs often implement the runtime surface where requests enter and predictions leave the system.",
"slug": "inference-service-frameworks",
"source": "db"
},
"input_skill": "Spring Boot",
"llm_role": null,
"roles_from_db": [
{
"display_name": "Machine Learning Engineer",
"id": 10,
"rationale": null,
"role_archetype": null,
"slug": "machine-learning-engineer",
"source": "db"
}
]
},
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Web Service Frameworks",
"id": 141,
"rationale": "Server frameworks used to build HTTP APIs, route requests, validate inputs, and structure backend application code. This cluster is coherent because it defines how backend services expose behavior to clients and other services.",
"slug": "web-service-frameworks",
"source": "db"
},
"input_skill": "Spring Boot",
"llm_role": null,
"roles_from_db": [
{
"display_name": "Backend Engineer",
"id": 14,
"rationale": null,
"role_archetype": null,
"slug": "backend-engineer",
"source": "db"
}
]
},
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Inference Service Frameworks",
"id": 114,
"rationale": "Web and service frameworks used to expose model predictions through APIs and application endpoints. This cluster is coherent because MLEs often implement the runtime surface where requests enter and predictions leave the system.",
"slug": "inference-service-frameworks",
"source": "db"
},
"input_skill": "FastAPI",
"llm_role": null,
"roles_from_db": [
{
"display_name": "Machine Learning Engineer",
"id": 10,
"rationale": null,
"role_archetype": null,
"slug": "machine-learning-engineer",
"source": "db"
}
]
},
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Web Service Frameworks",
"id": 141,
"rationale": "Server frameworks used to build HTTP APIs, route requests, validate inputs, and structure backend application code. This cluster is coherent because it defines how backend services expose behavior to clients and other services.",
"slug": "web-service-frameworks",
"source": "db"
},
"input_skill": "FastAPI",
"llm_role": null,
"roles_from_db": [
{
"display_name": "Backend Engineer",
"id": 14,
"rationale": null,
"role_archetype": null,
"slug": "backend-engineer",
"source": "db"
}
]
},
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Service Architecture and Integration",
"id": 148,
"rationale": "Patterns for structuring backend systems as services and coordinating calls across internal and external dependencies. This includes how services are decomposed, connected, and evolved safely.",
"slug": "service-architecture-and-integration",
"source": "db"
},
"input_skill": "Microservices",
"llm_role": null,
"roles_from_db": [
{
"display_name": "Backend Engineer",
"id": 14,
"rationale": null,
"role_archetype": null,
"slug": "backend-engineer",
"source": "db"
}
]
},
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "NoSQL and Cache Stores",
"id": 145,
"rationale": "Non-relational databases and in-memory stores used for low-latency access, flexible schemas, and specialized persistence patterns. This cluster is coherent because backend services often combine these stores with relational systems.",
"slug": "nosql-and-cache-stores",
"source": "db"
},
"input_skill": "MongoDB",
"llm_role": null,
"roles_from_db": [
{
"display_name": "Backend Engineer",
"id": 14,
"rationale": null,
"role_archetype": null,
"slug": "backend-engineer",
"source": "db"
}
]
},
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "NoSQL and Data Lake Storage",
"id": 73,
"rationale": "Non-relational stores and lake storage used for semi-structured, large-scale, or raw data retention. This cluster is coherent because many pipelines land and serve data outside classic relational warehouses.",
"slug": "nosql-and-data-lake-storage",
"source": "db"
},
"input_skill": "MongoDB",
"llm_role": null,
"roles_from_db": [
{
"display_name": "Data Engineer",
"id": 6,
"rationale": null,
"role_archetype": null,
"slug": "data-engineer",
"source": "db"
}
]
},
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "NoSQL and Cache Stores",
"id": 145,
"rationale": "Non-relational databases and in-memory stores used for low-latency access, flexible schemas, and specialized persistence patterns. This cluster is coherent because backend services often combine these stores with relational systems.",
"slug": "nosql-and-cache-stores",
"source": "db"
},
"input_skill": "Redis",
"llm_role": null,
"roles_from_db": [
{
"display_name": "Backend Engineer",
"id": 14,
"rationale": null,
"role_archetype": null,
"slug": "backend-engineer",
"source": "db"
}
]
},
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Messaging and Event Streaming",
"id": 146,
"rationale": "Asynchronous communication patterns and systems for decoupled service interaction and background processing. This is a coherent backend cluster because many server-side workflows depend on queues, topics, and event streams.",
"slug": "messaging-and-event-streaming",
"source": "db"
},
"input_skill": "Kafka",
"llm_role": null,
"roles_from_db": [
{
"display_name": "Backend Engineer",
"id": 14,
"rationale": null,
"role_archetype": null,
"slug": "backend-engineer",
"source": "db"
}
]
},
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Messaging and Event Streaming",
"id": 146,
"rationale": "Asynchronous communication patterns and systems for decoupled service interaction and background processing. This is a coherent backend cluster because many server-side workflows depend on queues, topics, and event streams.",
"slug": "messaging-and-event-streaming",
"source": "db"
},
"input_skill": "RabbitMQ",
"llm_role": null,
"roles_from_db": [
{
"display_name": "Backend Engineer",
"id": 14,
"rationale": null,
"role_archetype": null,
"slug": "backend-engineer",
"source": "db"
}
]
},
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Containerization and Image Delivery",
"id": 24,
"rationale": "Builds, packages, and ships application and support workloads as container images. This cluster covers the artifact format and the mechanics of producing deployable images.",
"slug": "containerization-and-image-delivery",
"source": "db"
},
"input_skill": "Docker",
"llm_role": null,
"roles_from_db": [
{
"display_name": "DevOps Engineer",
"id": 1,
"rationale": null,
"role_archetype": "A DevOps Engineer enables reliable, repeatable delivery of software by designing and operating the processes that connect development and production. They focus on improving deployment flow, operational stability, and collaboration between teams through automation, standardization, and monitoring of delivery and runtime practices.",
"slug": "devops-engineer",
"source": "db"
}
]
},
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Model Serving Deployment and Runtime Packaging",
"id": 52,
"rationale": "Operational deployment of trained models into online, batch, or streaming serving environments, including packaging models and model servers into containers or managed inference runtimes, coordinating rollout, and handing off to inference systems. Covers serving frameworks and platforms such as TensorFlow Serving, TorchServe, Triton Inference Server, BentoML, KServe, and Seldon Core, plus container/runtime concerns like Docker images, GPU-enabled containers, base image selection, container entrypoints, runtime dependencies, and image scanning for model services.",
"slug": "model-serving-deployment-and-runtime-packaging",
"source": "db"
},
"input_skill": "Docker",
"llm_role": null,
"roles_from_db": [
{
"display_name": "MLOps Engineer",
"id": 5,
"rationale": null,
"role_archetype": null,
"slug": "mlops-engineer",
"source": "db"
},
{
"display_name": "Machine Learning Engineer",
"id": 10,
"rationale": null,
"role_archetype": null,
"slug": "machine-learning-engineer",
"source": "db"
}
]
},
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Orchestration Platforms",
"id": 25,
"rationale": "Operates the platforms that schedule and run containerized workloads and related deployment primitives. This is separate from image delivery because it concerns runtime placement and service rollout behavior.",
"slug": "orchestration-platforms",
"source": "db"
},
"input_skill": "Kubernetes",
"llm_role": null,
"roles_from_db": [
{
"display_name": "Cloud Engineer",
"id": 18,
"rationale": null,
"role_archetype": null,
"slug": "cloud-engineer",
"source": "db"
},
{
"display_name": "DevOps Engineer",
"id": 1,
"rationale": null,
"role_archetype": "A DevOps Engineer enables reliable, repeatable delivery of software by designing and operating the processes that connect development and production. They focus on improving deployment flow, operational stability, and collaboration between teams through automation, standardization, and monitoring of delivery and runtime practices.",
"slug": "devops-engineer",
"source": "db"
}
]
},
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Version Control Systems",
"id": 365,
"rationale": "Tools and workflows for tracking source changes, branching, merging, and collaborating on code history. Git belongs here because it is the canonical distributed version control system used to manage revisions and coordinate team development.",
"slug": "d_init_01",
"source": "db"
},
"input_skill": "Git",
"llm_role": null,
"roles_from_db": []
},
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Version Control Systems",
"id": 365,
"rationale": "Tools and workflows for tracking source changes, branching, merging, and collaborating on code history. Git belongs here because it is the canonical distributed version control system used to manage revisions and coordinate team development.",
"slug": "d_init_01",
"source": "db"
},
"input_skill": "CI/CD",
"llm_role": null,
"roles_from_db": []
},
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Cloud Platform Operations",
"id": 26,
"rationale": "Uses cloud provider services to support delivery and runtime environments. The focus is on consumer-level operation of cloud services rather than deep cloud architecture ownership.",
"slug": "cloud-platform-operations",
"source": "db"
},
"input_skill": "AWS",
"llm_role": null,
"roles_from_db": [
{
"display_name": "DevOps Engineer",
"id": 1,
"rationale": null,
"role_archetype": "A DevOps Engineer enables reliable, repeatable delivery of software by designing and operating the processes that connect development and production. They focus on improving deployment flow, operational stability, and collaboration between teams through automation, standardization, and monitoring of delivery and runtime practices.",
"slug": "devops-engineer",
"source": "db"
}
]
},
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Cloud Security Platforms",
"id": 332,
"rationale": "Cloud-native security products used to assess posture, detect misconfigurations, and monitor workloads across AWS, Azure, and GCP. This is a distinct product family because the role often works across multiple CNAPP/CSPM/CWPP offerings and cloud-native detectors.",
"slug": "cloud-security-platforms",
"source": "db"
},
"input_skill": "AWS",
"llm_role": null,
"roles_from_db": [
{
"display_name": "Cybersecurity Engineer",
"id": 9,
"rationale": null,
"role_archetype": null,
"slug": "cybersecurity-engineer",
"source": "db"
}
]
},
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Cloud Platform Operations",
"id": 26,
"rationale": "Uses cloud provider services to support delivery and runtime environments. The focus is on consumer-level operation of cloud services rather than deep cloud architecture ownership.",
"slug": "cloud-platform-operations",
"source": "db"
},
"input_skill": "Azure",
"llm_role": null,
"roles_from_db": [
{
"display_name": "DevOps Engineer",
"id": 1,
"rationale": null,
"role_archetype": "A DevOps Engineer enables reliable, repeatable delivery of software by designing and operating the processes that connect development and production. They focus on improving deployment flow, operational stability, and collaboration between teams through automation, standardization, and monitoring of delivery and runtime practices.",
"slug": "devops-engineer",
"source": "db"
}
]
},
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Cloud Security Platforms",
"id": 332,
"rationale": "Cloud-native security products used to assess posture, detect misconfigurations, and monitor workloads across AWS, Azure, and GCP. This is a distinct product family because the role often works across multiple CNAPP/CSPM/CWPP offerings and cloud-native detectors.",
"slug": "cloud-security-platforms",
"source": "db"
},
"input_skill": "Azure",
"llm_role": null,
"roles_from_db": [
{
"display_name": "Cybersecurity Engineer",
"id": 9,
"rationale": null,
"role_archetype": null,
"slug": "cybersecurity-engineer",
"source": "db"
}
]
},
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Cloud Security Platforms",
"id": 332,
"rationale": "Cloud-native security products used to assess posture, detect misconfigurations, and monitor workloads across AWS, Azure, and GCP. This is a distinct product family because the role often works across multiple CNAPP/CSPM/CWPP offerings and cloud-native detectors.",
"slug": "cloud-security-platforms",
"source": "db"
},
"input_skill": "GCP",
"llm_role": null,
"roles_from_db": [
{
"display_name": "Cybersecurity Engineer",
"id": 9,
"rationale": null,
"role_archetype": null,
"slug": "cybersecurity-engineer",
"source": "db"
}
]
},
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Observability and Alerting",
"id": 27,
"rationale": "Builds feedback loops for system health through metrics, logs, traces, dashboards, and alerts. This cluster is coherent because it turns runtime behavior into actionable operational signals.",
"slug": "observability-and-alerting",
"source": "db"
},
"input_skill": "Prometheus",
"llm_role": null,
"roles_from_db": [
{
"display_name": "DevOps Engineer",
"id": 1,
"rationale": null,
"role_archetype": "A DevOps Engineer enables reliable, repeatable delivery of software by designing and operating the processes that connect development and production. They focus on improving deployment flow, operational stability, and collaboration between teams through automation, standardization, and monitoring of delivery and runtime practices.",
"slug": "devops-engineer",
"source": "db"
}
]
},
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Observability and Diagnostics",
"id": 151,
"rationale": "Logging, metrics, tracing, dashboards, and debugging practices used to understand backend behavior in production. This cluster is coherent because backend engineers must detect failures, performance issues, and unexpected behavior.",
"slug": "observability-and-diagnostics",
"source": "db"
},
"input_skill": "Prometheus",
"llm_role": null,
"roles_from_db": [
{
"display_name": "Backend Engineer",
"id": 14,
"rationale": null,
"role_archetype": null,
"slug": "backend-engineer",
"source": "db"
}
]
},
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Observability and Alerting",
"id": 27,
"rationale": "Builds feedback loops for system health through metrics, logs, traces, dashboards, and alerts. This cluster is coherent because it turns runtime behavior into actionable operational signals.",
"slug": "observability-and-alerting",
"source": "db"
},
"input_skill": "Grafana",
"llm_role": null,
"roles_from_db": [
{
"display_name": "DevOps Engineer",
"id": 1,
"rationale": null,
"role_archetype": "A DevOps Engineer enables reliable, repeatable delivery of software by designing and operating the processes that connect development and production. They focus on improving deployment flow, operational stability, and collaboration between teams through automation, standardization, and monitoring of delivery and runtime practices.",
"slug": "devops-engineer",
"source": "db"
}
]
},
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Observability and Diagnostics",
"id": 151,
"rationale": "Logging, metrics, tracing, dashboards, and debugging practices used to understand backend behavior in production. This cluster is coherent because backend engineers must detect failures, performance issues, and unexpected behavior.",
"slug": "observability-and-diagnostics",
"source": "db"
},
"input_skill": "Grafana",
"llm_role": null,
"roles_from_db": [
{
"display_name": "Backend Engineer",
"id": 14,
"rationale": null,
"role_archetype": null,
"slug": "backend-engineer",
"source": "db"
}
]
},
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Project Delivery and Coordination",
"id": 366,
"rationale": "Coordination practices for organizing work, tracking progress, and aligning stakeholders across a delivery effort. Agile fits here when used as a team execution framework for managing scope, cadence, and collaboration.",
"slug": "d_init_02",
"source": "db"
},
"input_skill": "Agile",
"llm_role": null,
"roles_from_db": []
},
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Version Control Systems",
"id": 365,
"rationale": "Tools and workflows for tracking source changes, branching, merging, and collaborating on code history. Git belongs here because it is the canonical distributed version control system used to manage revisions and coordinate team development.",
"slug": "d_init_01",
"source": "db"
},
"input_skill": "Agile",
"llm_role": null,
"roles_from_db": []
},
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Version Control Systems",
"id": 365,
"rationale": "Tools and workflows for tracking source changes, branching, merging, and collaborating on code history. Git belongs here because it is the canonical distributed version control system used to manage revisions and coordinate team development.",
"slug": "d_init_01",
"source": "db"
},
"input_skill": "Scrum",
"llm_role": null,
"roles_from_db": []
},
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "API Integration and Data Fetching",
"id": 9,
"rationale": "Connecting frontend applications to backend services and third-party endpoints. This covers request orchestration, error handling, pagination, and shaping remote data for UI consumption.",
"slug": "api-integration-and-data-fetching",
"source": "db"
},
"input_skill": "GraphQL",
"llm_role": null,
"roles_from_db": [
{
"display_name": "Frontend Engineer",
"id": 3,
"rationale": null,
"role_archetype": "Frontend Engineers design and build the user-facing parts of applications, translating product and design requirements into interactive experiences. They focus on how the application looks, behaves, and responds in the browser, ensuring usability, accessibility, and consistency across the interface.",
"slug": "frontend-engineer",
"source": "db"
},
{
"display_name": "Full Stack Developer",
"id": 2,
"rationale": null,
"role_archetype": null,
"slug": "full-stack-developer",
"source": "db"
}
]
},
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "API Integration and Serialization",
"id": 128,
"rationale": "Client-side integration with backend services, including request handling, response parsing, and contract alignment. This cluster is coherent because iOS features frequently depend on stable data exchange with server APIs.",
"slug": "api-integration-and-serialization",
"source": "db"
},
"input_skill": "GraphQL",
"llm_role": null,
"roles_from_db": [
{
"display_name": "iOS Engineer",
"id": 13,
"rationale": null,
"role_archetype": null,
"slug": "ios-engineer",
"source": "db"
}
]
},
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Cloud Service Integration Patterns",
"id": 188,
"rationale": "Covers how cloud services and workloads connect through APIs, events, shared services, and integration boundaries. This cluster is coherent because architects must define interaction patterns that preserve decoupling, security, and operability.",
"slug": "cloud-service-integration-patterns",
"source": "db"
},
"input_skill": "Event-Driven Architecture",
"llm_role": null,
"roles_from_db": [
{
"display_name": "Cloud Architect",
"id": 11,
"rationale": null,
"role_archetype": null,
"slug": "cloud-architect",
"source": "db"
}
]
},
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Version Control Systems",
"id": 365,
"rationale": "Tools and workflows for tracking source changes, branching, merging, and collaborating on code history. Git belongs here because it is the canonical distributed version control system used to manage revisions and coordinate team development.",
"slug": "d_init_01",
"source": "db"
},
"input_skill": "Express.js",
"llm_role": null,
"roles_from_db": []
},
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Version Control Systems",
"id": 365,
"rationale": "Tools and workflows for tracking source changes, branching, merging, and collaborating on code history. Git belongs here because it is the canonical distributed version control system used to manage revisions and coordinate team development.",
"slug": "d_init_01",
"source": "db"
},
"input_skill": "PostgreSQL",
"llm_role": null,
"roles_from_db": []
},
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "MySQL Operational Monitoring, Logging, and Diagnostics",
"id": 166,
"rationale": "Covers the DBA practice of monitoring MySQL production health and using MySQL-native logs and diagnostic views to detect, investigate, and explain incidents or performance anomalies. Includes routine health checks, alerting, replication and availability monitoring, resource and connection monitoring, and use of error logs, slow query logs, SHOW PROCESSLIST, performance_schema, status variables, and diagnostic queries to understand behavior and support recovery decisions.",
"slug": "mysql-operational-monitoring-logging-and-diagnostics",
"source": "db"
},
"input_skill": "MySQL",
"llm_role": null,
"roles_from_db": [
{
"display_name": "MySQL DBA",
"id": 23,
"rationale": null,
"role_archetype": null,
"slug": "mysql-dba",
"source": "db"
}
]
},
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Data Access and Query Optimization",
"id": 74,
"rationale": "Techniques for making analytical data fast and reliable to query. This includes partitioning, clustering, indexing choices, file layout, and access-path tuning for downstream consumers.",
"slug": "data-access-and-query-optimization",
"source": "db"
},
"input_skill": "MySQL",
"llm_role": null,
"roles_from_db": [
{
"display_name": "Data Engineer",
"id": 6,
"rationale": null,
"role_archetype": null,
"slug": "data-engineer",
"source": "db"
}
]
},
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Data Access and Query Optimization",
"id": 74,
"rationale": "Techniques for making analytical data fast and reliable to query. This includes partitioning, clustering, indexing choices, file layout, and access-path tuning for downstream consumers.",
"slug": "data-access-and-query-optimization",
"source": "db"
},
"input_skill": "MySQL",
"llm_role": null,
"roles_from_db": [
{
"display_name": "Data Engineer",
"id": 6,
"rationale": null,
"role_archetype": null,
"slug": "data-engineer",
"source": "db"
}
]
}
],
"input_final_skills": [
"REST",
"Node.js",
"Java",
"Python",
"Go",
"Express.js",
"Spring Boot",
"FastAPI",
"Microservices",
"PostgreSQL",
"MySQL",
"MongoDB",
"Redis",
"Kafka",
"RabbitMQ",
"Docker",
"Kubernetes",
"Git",
"CI/CD",
"AWS",
"Azure",
"GCP",
"Prometheus",
"Grafana",
"Agile",
"Scrum",
"GraphQL",
"Event-Driven Architecture"
],
"input_llm_skills": [
"REST",
"Node.js",
"Java",
"Python",
"Go",
"Express.js",
"Spring Boot",
"FastAPI",
"Microservices",
"PostgreSQL",
"MySQL",
"MongoDB",
"Redis",
"Kafka",
"RabbitMQ",
"Docker",
"Kubernetes",
"Git",
"CI/CD",
"AWS",
"Azure",
"GCP",
"Prometheus",
"Grafana",
"Agile",
"Scrum",
"GraphQL",
"Event-Driven Architecture"
],
"new_aliases_persisted": 0,
"run_id": "8077639b-c7cb-4ba7-998c-e936e0f7c4d4",
"skills_detail": [
{
"aliases_in_db": [
{
"alias_text": "REST",
"alias_type": "CANONICAL",
"id": 266,
"is_primary": true,
"match_strategy": "CASE_INSENSITIVE"
}
],
"canonical": {
"category_id": 8,
"display_name": "REST",
"id": 121,
"is_also_category": false,
"is_extractable": true,
"skill_nature": "PROTOCOL",
"slug": "rest",
"sub_category_id": 67,
"typical_lifespan": "EVERGREEN",
"volatility": "STABLE"
},
"dimensions": [
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "API Integration and Data Fetching",
"id": 9,
"rationale": "Connecting frontend applications to backend services and third-party endpoints. This covers request orchestration, error handling, pagination, and shaping remote data for UI consumption.",
"slug": "api-integration-and-data-fetching",
"source": "db"
},
"input_skill": "REST",
"llm_role": null,
"roles_from_db": [
{
"display_name": "Frontend Engineer",
"id": 3,
"rationale": null,
"role_archetype": "Frontend Engineers design and build the user-facing parts of applications, translating product and design requirements into interactive experiences. They focus on how the application looks, behaves, and responds in the browser, ensuring usability, accessibility, and consistency across the interface.",
"slug": "frontend-engineer",
"source": "db"
},
{
"display_name": "Full Stack Developer",
"id": 2,
"rationale": null,
"role_archetype": null,
"slug": "full-stack-developer",
"source": "db"
}
]
}
],
"input_skill": "REST",
"matched_via": "alias",
"new_alias_persisted": false,
"new_alias_text": null,
"new_skill_meta": null,
"source_tag": "db",
"was_in_llm_skills": true
},
{
"aliases_in_db": [
{
"alias_text": "Node 18",
"alias_type": "VERSION",
"id": 3458,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "Node 20",
"alias_type": "VERSION",
"id": 3456,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "Node 22",
"alias_type": "VERSION",
"id": 3453,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "Node.js",
"alias_type": "CANONICAL",
"id": 3396,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "Node.js 18",
"alias_type": "VERSION",
"id": 3459,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "Node.js 20",
"alias_type": "VERSION",
"id": 3457,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "Node.js 22",
"alias_type": "VERSION",
"id": 3454,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "Node.js 22 LTS",
"alias_type": "VERSION",
"id": 3455,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "node",
"alias_type": "VERSION",
"id": 3451,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "nodejs",
"alias_type": "VERSION",
"id": 3452,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
}
],
"canonical": {
"category_id": 271,
"display_name": "Node.js",
"id": 2599,
"is_also_category": false,
"is_extractable": true,
"skill_nature": "RUNTIME",
"slug": "node-js",
"sub_category_id": 2120,
"typical_lifespan": "EVERGREEN",
"volatility": "STABLE"
},
"dimensions": [
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Programming Languages for Backend Systems",
"id": 140,
"rationale": "Languages used to implement server-side business logic, request handlers, workers, and service integrations. This is the core coding surface for backend feature delivery and maintenance.",
"slug": "programming-languages-for-backend-systems",
"source": "db"
},
"input_skill": "Node.js",
"llm_role": null,
"roles_from_db": [
{
"display_name": "Backend Engineer",
"id": 14,
"rationale": null,
"role_archetype": null,
"slug": "backend-engineer",
"source": "db"
}
]
}
],
"input_skill": "Node.js",
"matched_via": "alias",
"new_alias_persisted": false,
"new_alias_text": null,
"new_skill_meta": null,
"source_tag": "db",
"was_in_llm_skills": true
},
{
"aliases_in_db": [
{
"alias_text": "Java",
"alias_type": "CANONICAL",
"id": 616,
"is_primary": true,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "JDK 11",
"alias_type": "VERSION",
"id": 1186,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "JDK 17",
"alias_type": "VERSION",
"id": 1187,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "JDK 21",
"alias_type": "VERSION",
"id": 1188,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "JDK 8",
"alias_type": "VERSION",
"id": 1185,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "Java 1.0",
"alias_type": "VERSION",
"id": 1002,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "Java 1.1",
"alias_type": "VERSION",
"id": 1003,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "Java 1.2",
"alias_type": "VERSION",
"id": 1004,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "Java 1.3",
"alias_type": "VERSION",
"id": 1005,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "Java 1.4",
"alias_type": "VERSION",
"id": 1006,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "Java 1.5",
"alias_type": "VERSION",
"id": 1007,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "Java 1.6",
"alias_type": "VERSION",
"id": 1008,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "Java 1.7",
"alias_type": "VERSION",
"id": 625,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "Java 1.8",
"alias_type": "VERSION",
"id": 626,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "Java 11",
"alias_type": "VERSION",
"id": 622,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "Java 11+",
"alias_type": "VERSION",
"id": 1194,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "Java 17",
"alias_type": "VERSION",
"id": 623,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "Java 17+",
"alias_type": "VERSION",
"id": 1195,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "Java 21",
"alias_type": "VERSION",
"id": 624,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "Java 21+",
"alias_type": "VERSION",
"id": 1196,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "Java 5",
"alias_type": "VERSION",
"id": 618,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "Java 6",
"alias_type": "VERSION",
"id": 619,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "Java 7",
"alias_type": "VERSION",
"id": 620,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "Java 8",
"alias_type": "VERSION",
"id": 621,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "Java 8+",
"alias_type": "VERSION",
"id": 1001,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "Java SE 11",
"alias_type": "VERSION",
"id": 1198,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "Java SE 17",
"alias_type": "VERSION",
"id": 1199,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "Java SE 21",
"alias_type": "VERSION",
"id": 1011,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "Java SE 8",
"alias_type": "VERSION",
"id": 1197,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
}
],
"canonical": {
"category_id": 5,
"display_name": "Java",
"id": 395,
"is_also_category": false,
"is_extractable": true,
"skill_nature": "LANGUAGE",
"slug": "java",
"sub_category_id": 54,
"typical_lifespan": "EVERGREEN",
"volatility": "STABLE"
},
"dimensions": [
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Programming Languages for AI Workflows",
"id": 261,
"rationale": "Languages used to implement AI feature logic, orchestration, and response handling inside product code. This is the core coding surface for turning prompts and model calls into reliable application behavior.",
"slug": "programming-languages-for-ai-workflows",
"source": "db"
},
"input_skill": "Java",
"llm_role": null,
"roles_from_db": [
{
"display_name": "AI Engineer",
"id": 12,
"rationale": null,
"role_archetype": null,
"slug": "ai-engineer",
"source": "db"
}
]
},
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Programming Languages for Backend Systems",
"id": 140,
"rationale": "Languages used to implement server-side business logic, request handlers, workers, and service integrations. This is the core coding surface for backend feature delivery and maintenance.",
"slug": "programming-languages-for-backend-systems",
"source": "db"
},
"input_skill": "Java",
"llm_role": null,
"roles_from_db": [
{
"display_name": "Backend Engineer",
"id": 14,
"rationale": null,
"role_archetype": null,
"slug": "backend-engineer",
"source": "db"
}
]
},
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Programming Languages for Data Work",
"id": 67,
"rationale": "Languages used to implement data pipelines, transformations, and operational utilities. This is the code layer for expressing extraction, parsing, validation, and orchestration logic in data engineering workflows.",
"slug": "programming-languages-for-data-work",
"source": "db"
},
"input_skill": "Java",
"llm_role": null,
"roles_from_db": [
{
"display_name": "Data Engineer",
"id": 6,
"rationale": null,
"role_archetype": null,
"slug": "data-engineer",
"source": "db"
}
]
},
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Programming Languages for ML Systems",
"id": 113,
"rationale": "Languages used to implement model integration code, inference services, and feature-processing logic. This is the core coding surface for turning trained models into product-facing software components.",
"slug": "programming-languages-for-ml-systems",
"source": "db"
},
"input_skill": "Java",
"llm_role": null,
"roles_from_db": [
{
"display_name": "Machine Learning Engineer",
"id": 10,
"rationale": null,
"role_archetype": null,
"slug": "machine-learning-engineer",
"source": "db"
}
]
},
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Programming Languages for Test Automation",
"id": 193,
"rationale": "Languages used to implement automated checks, helper utilities, and test harness code. This is the core coding surface for turning test ideas into maintainable automation.",
"slug": "programming-languages-for-test-automation",
"source": "db"
},
"input_skill": "Java",
"llm_role": null,
"roles_from_db": [
{
"display_name": "Automation Tester",
"id": 16,
"rationale": null,
"role_archetype": null,
"slug": "automation-tester",
"source": "db"
}
]
}
],
"input_skill": "Java",
"matched_via": "alias",
"new_alias_persisted": false,
"new_alias_text": null,
"new_skill_meta": null,
"source_tag": "db",
"was_in_llm_skills": true
},
{
"aliases_in_db": [
{
"alias_text": "Python",
"alias_type": "CANONICAL",
"id": 608,
"is_primary": true,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "Python 2",
"alias_type": "VERSION",
"id": 611,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "Python 2.x",
"alias_type": "VERSION",
"id": 613,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "Python 3",
"alias_type": "VERSION",
"id": 612,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "Python 3.10",
"alias_type": "VERSION",
"id": 2330,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "Python 3.11",
"alias_type": "VERSION",
"id": 2331,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "Python 3.12",
"alias_type": "VERSION",
"id": 2332,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "Python 3.x",
"alias_type": "VERSION",
"id": 614,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "py2",
"alias_type": "VERSION",
"id": 609,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "py3",
"alias_type": "VERSION",
"id": 610,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "python 2",
"alias_type": "VERSION",
"id": 2152,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "python 2.x",
"alias_type": "VERSION",
"id": 2154,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "python 3",
"alias_type": "VERSION",
"id": 990,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "python 3.10",
"alias_type": "VERSION",
"id": 992,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "python 3.11",
"alias_type": "VERSION",
"id": 993,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "python 3.12",
"alias_type": "VERSION",
"id": 994,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "python 3.x",
"alias_type": "VERSION",
"id": 991,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "python2",
"alias_type": "VERSION",
"id": 2150,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "python3",
"alias_type": "VERSION",
"id": 989,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
}
],
"canonical": {
"category_id": 5,
"display_name": "Python",
"id": 393,
"is_also_category": false,
"is_extractable": true,
"skill_nature": "LANGUAGE",
"slug": "python",
"sub_category_id": 54,
"typical_lifespan": "EVERGREEN",
"volatility": "STABLE"
},
"dimensions": [
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Analytical Programming Languages",
"id": 82,
"rationale": "Languages used to clean, transform, analyze, and prototype models in notebooks and scripts. This is the core coding surface for expressing statistical logic and data manipulation in a reproducible way.",
"slug": "analytical-programming-languages",
"source": "db"
},
"input_skill": "Python",
"llm_role": null,
"roles_from_db": [
{
"display_name": "Data Analyst",
"id": 20,
"rationale": null,
"role_archetype": null,
"slug": "data-analyst",
"source": "db"
},
{
"display_name": "Data Scientist",
"id": 7,
"rationale": null,
"role_archetype": null,
"slug": "data-scientist",
"source": "db"
}
]
},
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Automation Scripting and CLI",
"id": 48,
"rationale": "Uses scripts and command-line tooling to execute repeatable Azure operations and reduce manual work. This is a practical cluster because the role frequently automates provisioning, checks, and remediation tasks.",
"slug": "automation-scripting-and-cli",
"source": "db"
},
"input_skill": "Python",
"llm_role": null,
"roles_from_db": [
{
"display_name": "Azure Cloud Engineer",
"id": 4,
"rationale": null,
"role_archetype": null,
"slug": "azure-cloud-engineer",
"source": "db"
},
{
"display_name": "Cloud Engineer",
"id": 18,
"rationale": null,
"role_archetype": null,
"slug": "cloud-engineer",
"source": "db"
}
]
},
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Automation and Scripting for Operations",
"id": 361,
"rationale": "Scripts and lightweight automation used to execute repetitive virtualization tasks and enforce operational consistency. This is the practical glue that reduces manual host and VM administration.",
"slug": "automation-and-scripting-for-operations",
"source": "db"
},
"input_skill": "Python",
"llm_role": null,
"roles_from_db": [
{
"display_name": "Virtualization Engineer",
"id": 26,
"rationale": null,
"role_archetype": null,
"slug": "virtualization-engineer",
"source": "db"
}
]
},
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Network Automation and Scripting",
"id": 285,
"rationale": "Covers scripts and automation used to configure, validate, and audit network devices and services. This cluster is coherent because repeatable network operations increasingly depend on programmatic changes and checks.",
"slug": "network-automation-and-scripting",
"source": "db"
},
"input_skill": "Python",
"llm_role": null,
"roles_from_db": [
{
"display_name": "Network Engineer",
"id": 21,
"rationale": null,
"role_archetype": null,
"slug": "network-engineer",
"source": "db"
}
]
},
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Programming Languages for AI Workflows",
"id": 261,
"rationale": "Languages used to implement AI feature logic, orchestration, and response handling inside product code. This is the core coding surface for turning prompts and model calls into reliable application behavior.",
"slug": "programming-languages-for-ai-workflows",
"source": "db"
},
"input_skill": "Python",
"llm_role": null,
"roles_from_db": [
{
"display_name": "AI Engineer",
"id": 12,
"rationale": null,
"role_archetype": null,
"slug": "ai-engineer",
"source": "db"
}
]
},
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Programming Languages for Backend Systems",
"id": 140,
"rationale": "Languages used to implement server-side business logic, request handlers, workers, and service integrations. This is the core coding surface for backend feature delivery and maintenance.",
"slug": "programming-languages-for-backend-systems",
"source": "db"
},
"input_skill": "Python",
"llm_role": null,
"roles_from_db": [
{
"display_name": "Backend Engineer",
"id": 14,
"rationale": null,
"role_archetype": null,
"slug": "backend-engineer",
"source": "db"
}
]
},
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Programming Languages for Data Work",
"id": 67,
"rationale": "Languages used to implement data pipelines, transformations, and operational utilities. This is the code layer for expressing extraction, parsing, validation, and orchestration logic in data engineering workflows.",
"slug": "programming-languages-for-data-work",
"source": "db"
},
"input_skill": "Python",
"llm_role": null,
"roles_from_db": [
{
"display_name": "Data Engineer",
"id": 6,
"rationale": null,
"role_archetype": null,
"slug": "data-engineer",
"source": "db"
}
]
},
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Programming Languages for ML Systems",
"id": 113,
"rationale": "Languages used to implement model integration code, inference services, and feature-processing logic. This is the core coding surface for turning trained models into product-facing software components.",
"slug": "programming-languages-for-ml-systems",
"source": "db"
},
"input_skill": "Python",
"llm_role": null,
"roles_from_db": [
{
"display_name": "Machine Learning Engineer",
"id": 10,
"rationale": null,
"role_archetype": null,
"slug": "machine-learning-engineer",
"source": "db"
}
]
},
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Programming Languages for Security Work",
"id": 328,
"rationale": "Languages used to automate security tasks, write detection logic, and build analysis or remediation tooling. This is the core coding surface for a cybersecurity engineer across scripts, queries, and small utilities.",
"slug": "programming-languages-for-security-work",
"source": "db"
},
"input_skill": "Python",
"llm_role": null,
"roles_from_db": [
{
"display_name": "Cybersecurity Engineer",
"id": 9,
"rationale": null,
"role_archetype": null,
"slug": "cybersecurity-engineer",
"source": "db"
}
]
},
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Programming Languages for Test Automation",
"id": 193,
"rationale": "Languages used to implement automated checks, helper utilities, and test harness code. This is the core coding surface for turning test ideas into maintainable automation.",
"slug": "programming-languages-for-test-automation",
"source": "db"
},
"input_skill": "Python",
"llm_role": null,
"roles_from_db": [
{
"display_name": "Automation Tester",
"id": 16,
"rationale": null,
"role_archetype": null,
"slug": "automation-tester",
"source": "db"
}
]
},
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Security Automation and Scripting",
"id": 258,
"rationale": "Automating repeatable security checks, enrichment, and remediation workflows. This cluster is coherent because the role often needs lightweight automation to scale analysis and response.",
"slug": "security-automation-and-scripting",
"source": "db"
},
"input_skill": "Python",
"llm_role": null,
"roles_from_db": [
{
"display_name": "Cybersecurity Engineer",
"id": 9,
"rationale": null,
"role_archetype": null,
"slug": "cybersecurity-engineer",
"source": "db"
}
]
}
],
"input_skill": "Python",
"matched_via": "alias",
"new_alias_persisted": false,
"new_alias_text": null,
"new_skill_meta": null,
"source_tag": "db",
"was_in_llm_skills": true
},
{
"aliases_in_db": [
{
"alias_text": "Go",
"alias_type": "CANONICAL",
"id": 1012,
"is_primary": true,
"match_strategy": "CASE_INSENSITIVE"
}
],
"canonical": {
"category_id": 5,
"display_name": "Go",
"id": 679,
"is_also_category": false,
"is_extractable": true,
"skill_nature": "LANGUAGE",
"slug": "go",
"sub_category_id": 54,
"typical_lifespan": "EVERGREEN",
"volatility": "STABLE"
},
"dimensions": [
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Programming Languages for Backend Systems",
"id": 140,
"rationale": "Languages used to implement server-side business logic, request handlers, workers, and service integrations. This is the core coding surface for backend feature delivery and maintenance.",
"slug": "programming-languages-for-backend-systems",
"source": "db"
},
"input_skill": "Go",
"llm_role": null,
"roles_from_db": [
{
"display_name": "Backend Engineer",
"id": 14,
"rationale": null,
"role_archetype": null,
"slug": "backend-engineer",
"source": "db"
}
]
},
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Programming Languages for ML Systems",
"id": 113,
"rationale": "Languages used to implement model integration code, inference services, and feature-processing logic. This is the core coding surface for turning trained models into product-facing software components.",
"slug": "programming-languages-for-ml-systems",
"source": "db"
},
"input_skill": "Go",
"llm_role": null,
"roles_from_db": [
{
"display_name": "Machine Learning Engineer",
"id": 10,
"rationale": null,
"role_archetype": null,
"slug": "machine-learning-engineer",
"source": "db"
}
]
},
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Programming Languages for Security Work",
"id": 328,
"rationale": "Languages used to automate security tasks, write detection logic, and build analysis or remediation tooling. This is the core coding surface for a cybersecurity engineer across scripts, queries, and small utilities.",
"slug": "programming-languages-for-security-work",
"source": "db"
},
"input_skill": "Go",
"llm_role": null,
"roles_from_db": [
{
"display_name": "Cybersecurity Engineer",
"id": 9,
"rationale": null,
"role_archetype": null,
"slug": "cybersecurity-engineer",
"source": "db"
}
]
}
],
"input_skill": "Go",
"matched_via": "alias",
"new_alias_persisted": false,
"new_alias_text": null,
"new_skill_meta": null,
"source_tag": "db",
"was_in_llm_skills": true
},
{
"aliases_in_db": [],
"canonical": null,
"dimensions": [
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Version Control Systems",
"id": 365,
"rationale": "Tools and workflows for tracking source changes, branching, merging, and collaborating on code history. Git belongs here because it is the canonical distributed version control system used to manage revisions and coordinate team development.",
"slug": "d_init_01",
"source": "db"
},
"input_skill": "Express.js",
"llm_role": null,
"roles_from_db": []
}
],
"input_skill": "Express.js",
"matched_via": null,
"new_alias_persisted": false,
"new_alias_text": null,
"new_skill_meta": {
"derived": {
"category": "Framework",
"skill_nature": "FRAMEWORK",
"sub_category": "web_framework",
"typical_lifespan": "EVERGREEN",
"version_strategy": "NOT_APPLICABLE",
"volatility": "STABLE"
},
"enrichment": {
"ambiguity": {
"ambiguity_flag": false,
"confused_with": [],
"reasoning": "Express.js is a well-known Node.js web framework with a distinctive name; in typical JDs it is unlikely to be confused with another catalog skill."
},
"context_keywords": {
"context_keywords": [
"Node.js",
"REST API",
"middleware",
"routing",
"Express Router",
"Mongoose",
"JWT",
"CORS",
"body-parser",
"cookie-parser",
"EJS",
"Pug",
"Swagger",
"Sequelize",
"TypeScript"
]
},
"maturity": {
"confidence": 0.95,
"maturity": "well_known",
"reasoning": "Express.js appears in many Node.js web backend job postings and remains a standard default in hiring pipelines, despite newer frameworks like Fastify/NestJS gaining share."
},
"skill_id": "express-js",
"vendor_license": {
"confidence": 0.99,
"license": "mit",
"vendor": "Express.js",
"year_introduced": 2010
},
"versioning": {
"current_version": null,
"version_aliases": {},
"versioned": false
}
},
"keep_log": [],
"locked_dimensions": [
{
"description": "Frameworks and conventions for building server-side web applications and APIs on Node.js. Express.js belongs here because it is a core backend HTTP framework used to define routes, middleware, request handling, and service endpoints.",
"exemplar_skills": [
"Express.js",
"Node.js",
"Express routing",
"Express middleware",
"REST API development",
"HTTP request handling"
],
"in_scope": "Express.js, routing, middleware, request/response handling, REST API endpoints, error handling in Node.js apps, Express routers, Express app configuration, server-side web application structure",
"name": "Node.js Web Frameworks",
"out_of_scope": "Client-side UI frameworks and rendering, database query tuning, authentication protocol design, message brokers and event streaming, infrastructure provisioning and deployment tooling",
"overlap_flags": [
{
"reason": "Both involve HTTP APIs, but this dimension covers building the server-side API surface rather than consuming APIs from a client.",
"with_dim_id": "api-integration-and-data-fetching",
"with_dim_name": null,
"with_role": "Frontend Engineer, Full Stack Developer"
},
{
"reason": "Express apps often implement auth middleware and sessions, but identity and session security are a separate concern.",
"with_dim_id": "authentication-and-session-security",
"with_dim_name": null,
"with_role": "Cybersecurity Engineer"
}
],
"tentative_id": "d_init_01"
}
],
"merge_log": [],
"placed": {
"name": "Express.js",
"placement_confidence": 0.92,
"primary_dimension": "d_init_01",
"reasoning": "Deterministic JD placement: locked_dimensions has 1 dimension(s) from skill-driven dimension generation after reconciliation; primary_dimension is the first locked dim.",
"secondary_dimensions": [],
"skill_id": "express-js"
},
"relationships": {
"child_skills": [],
"parent_skills": [
"node-js",
"javascript"
],
"related_to": [
"rest-apis",
"aws-lambda",
"amazon-api-gateway",
"web3-js",
"ethers-js",
"solana-web3-js",
"react-native",
"truffle",
"metamask",
"elasticsearch"
],
"requires": [],
"skill_id": "express-js",
"suppress_on_match": []
},
"skill_id": "express-js",
"split_log": [],
"typed": {
"alternatives_considered": [],
"confidence": 0.98,
"name": "Express.js",
"reasoning": "Express.js is a structured codebase that applications are built inside and it calls user code, so by the Tool vs Framework rule it is a Framework.",
"skill_id": "express-js",
"subtype": "web_framework",
"type": "Framework"
},
"warnings": []
},
"source_tag": "llm",
"was_in_llm_skills": true
},
{
"aliases_in_db": [
{
"alias_text": "Spring Boot",
"alias_type": "CANONICAL",
"id": 1024,
"is_primary": true,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "Spring Boot 1",
"alias_type": "VERSION",
"id": 1025,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "Spring Boot 1.x",
"alias_type": "VERSION",
"id": 1028,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "Spring Boot 2",
"alias_type": "VERSION",
"id": 1026,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "Spring Boot 2.x",
"alias_type": "VERSION",
"id": 1029,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "Spring Boot 3",
"alias_type": "VERSION",
"id": 1027,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "Spring Boot 3.x",
"alias_type": "VERSION",
"id": 1030,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
}
],
"canonical": {
"category_id": 4,
"display_name": "Spring Boot",
"id": 684,
"is_also_category": false,
"is_extractable": true,
"skill_nature": "FRAMEWORK",
"slug": "spring-boot",
"sub_category_id": 708,
"typical_lifespan": "EVERGREEN",
"volatility": "STABLE"
},
"dimensions": [
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Inference Service Frameworks",
"id": 114,
"rationale": "Web and service frameworks used to expose model predictions through APIs and application endpoints. This cluster is coherent because MLEs often implement the runtime surface where requests enter and predictions leave the system.",
"slug": "inference-service-frameworks",
"source": "db"
},
"input_skill": "Spring Boot",
"llm_role": null,
"roles_from_db": [
{
"display_name": "Machine Learning Engineer",
"id": 10,
"rationale": null,
"role_archetype": null,
"slug": "machine-learning-engineer",
"source": "db"
}
]
},
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Web Service Frameworks",
"id": 141,
"rationale": "Server frameworks used to build HTTP APIs, route requests, validate inputs, and structure backend application code. This cluster is coherent because it defines how backend services expose behavior to clients and other services.",
"slug": "web-service-frameworks",
"source": "db"
},
"input_skill": "Spring Boot",
"llm_role": null,
"roles_from_db": [
{
"display_name": "Backend Engineer",
"id": 14,
"rationale": null,
"role_archetype": null,
"slug": "backend-engineer",
"source": "db"
}
]
}
],
"input_skill": "Spring Boot",
"matched_via": "alias",
"new_alias_persisted": false,
"new_alias_text": null,
"new_skill_meta": null,
"source_tag": "db",
"was_in_llm_skills": true
},
{
"aliases_in_db": [
{
"alias_text": "FastAPI",
"alias_type": "CANONICAL",
"id": 1022,
"is_primary": true,
"match_strategy": "CASE_INSENSITIVE"
}
],
"canonical": {
"category_id": 4,
"display_name": "FastAPI",
"id": 682,
"is_also_category": false,
"is_extractable": true,
"skill_nature": "FRAMEWORK",
"slug": "fastapi",
"sub_category_id": 52,
"typical_lifespan": "EVERGREEN",
"volatility": "STABLE"
},
"dimensions": [
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Inference Service Frameworks",
"id": 114,
"rationale": "Web and service frameworks used to expose model predictions through APIs and application endpoints. This cluster is coherent because MLEs often implement the runtime surface where requests enter and predictions leave the system.",
"slug": "inference-service-frameworks",
"source": "db"
},
"input_skill": "FastAPI",
"llm_role": null,
"roles_from_db": [
{
"display_name": "Machine Learning Engineer",
"id": 10,
"rationale": null,
"role_archetype": null,
"slug": "machine-learning-engineer",
"source": "db"
}
]
},
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Web Service Frameworks",
"id": 141,
"rationale": "Server frameworks used to build HTTP APIs, route requests, validate inputs, and structure backend application code. This cluster is coherent because it defines how backend services expose behavior to clients and other services.",
"slug": "web-service-frameworks",
"source": "db"
},
"input_skill": "FastAPI",
"llm_role": null,
"roles_from_db": [
{
"display_name": "Backend Engineer",
"id": 14,
"rationale": null,
"role_archetype": null,
"slug": "backend-engineer",
"source": "db"
}
]
}
],
"input_skill": "FastAPI",
"matched_via": "alias",
"new_alias_persisted": false,
"new_alias_text": null,
"new_skill_meta": null,
"source_tag": "db",
"was_in_llm_skills": true
},
{
"aliases_in_db": [
{
"alias_text": "Microservices",
"alias_type": "CANONICAL",
"id": 1307,
"is_primary": true,
"match_strategy": "CASE_INSENSITIVE"
}
],
"canonical": {
"category_id": 1,
"display_name": "Microservices",
"id": 864,
"is_also_category": false,
"is_extractable": true,
"skill_nature": "PATTERN",
"slug": "microservices",
"sub_category_id": 663,
"typical_lifespan": "EVERGREEN",
"volatility": "STABLE"
},
"dimensions": [
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Service Architecture and Integration",
"id": 148,
"rationale": "Patterns for structuring backend systems as services and coordinating calls across internal and external dependencies. This includes how services are decomposed, connected, and evolved safely.",
"slug": "service-architecture-and-integration",
"source": "db"
},
"input_skill": "Microservices",
"llm_role": null,
"roles_from_db": [
{
"display_name": "Backend Engineer",
"id": 14,
"rationale": null,
"role_archetype": null,
"slug": "backend-engineer",
"source": "db"
}
]
}
],
"input_skill": "Microservices",
"matched_via": "alias",
"new_alias_persisted": false,
"new_alias_text": null,
"new_skill_meta": null,
"source_tag": "db",
"was_in_llm_skills": true
},
{
"aliases_in_db": [],
"canonical": null,
"dimensions": [
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Version Control Systems",
"id": 365,
"rationale": "Tools and workflows for tracking source changes, branching, merging, and collaborating on code history. Git belongs here because it is the canonical distributed version control system used to manage revisions and coordinate team development.",
"slug": "d_init_01",
"source": "db"
},
"input_skill": "PostgreSQL",
"llm_role": null,
"roles_from_db": []
}
],
"input_skill": "PostgreSQL",
"matched_via": null,
"new_alias_persisted": false,
"new_alias_text": null,
"new_skill_meta": {
"derived": {
"category": "Datastore",
"skill_nature": "TOOL",
"sub_category": "relational_database",
"typical_lifespan": "EVERGREEN",
"version_strategy": "SEPARATE_ENTITY",
"volatility": "STABLE"
},
"enrichment": {
"ambiguity": {
"ambiguity_flag": false,
"confused_with": [],
"reasoning": "PostgreSQL is a specific, well-known relational database name with little overlap in typical JDs beyond generic database mentions; it is unlikely to be confused with another catalog skill."
},
"context_keywords": {
"context_keywords": [
"SQL",
"schema",
"indexes",
"query optimization",
"replication",
"partitioning",
"transactions",
"ACID",
"stored procedures",
"triggers",
"views",
"JSONB",
"PostGIS",
"pgAdmin",
"connection pooling"
]
},
"maturity": {
"confidence": 0.99,
"maturity": "well_known",
"reasoning": "PostgreSQL appears in a large share of backend and data-engineering job descriptions and is a standard managed offering across AWS, GCP, and Azure, indicating broad market adoption."
},
"skill_id": "postgresql",
"vendor_license": {
"confidence": 0.97,
"license": "other_open",
"vendor": "PostgreSQL Global Development Group",
"year_introduced": 1996
},
"versioning": {
"current_version": "16",
"version_aliases": {
"PostgreSQL 10": "10",
"PostgreSQL 11": "11",
"PostgreSQL 12": "12",
"PostgreSQL 13": "13",
"PostgreSQL 14": "14",
"PostgreSQL 15": "15",
"PostgreSQL 16": "16",
"PostgreSQL 9.5": "9.5",
"PostgreSQL 9.6": "9.6",
"Postgres 10": "10",
"Postgres 11": "11",
"Postgres 12": "12",
"Postgres 13": "13",
"Postgres 14": "14",
"Postgres 15": "15",
"Postgres 16": "16",
"Postgres 9.5": "9.5",
"Postgres 9.6": "9.6"
},
"versioned": true
}
},
"keep_log": [],
"locked_dimensions": [
{
"description": "Covers operating PostgreSQL as a production relational database, including schema management, backups, restores, replication, monitoring, and routine DBA tasks. PostgreSQL belongs here because it is a specific database platform rather than a generic SQL skill.",
"exemplar_skills": [
"PostgreSQL",
"PostgreSQL administration",
"PostgreSQL backups",
"PostgreSQL replication",
"VACUUM",
"pg_dump",
"pg_restore",
"PostgreSQL monitoring"
],
"in_scope": "PostgreSQL, PostgreSQL administration, backups and restores, replication and failover, user and role management, schema and table maintenance, vacuum and analyze, connection pooling, extensions, basic query troubleshooting",
"name": "PostgreSQL Database Administration",
"out_of_scope": "General SQL query writing, data modeling for application features, MySQL-specific administration, data warehouse tuning, application ORM usage",
"overlap_flags": [
{
"reason": "Both cover DBA automation, but this dimension is PostgreSQL-specific while the catalog item is MySQL-specific.",
"with_dim_id": "mysql-automation-and-scripting",
"with_dim_name": null,
"with_role": "MySQL DBA"
},
{
"reason": "Operational monitoring and diagnostics overlap at the DBA layer, but this dimension is for PostgreSQL rather than MySQL.",
"with_dim_id": "mysql-operational-monitoring-logging-and-diagnostics",
"with_dim_name": null,
"with_role": "MySQL DBA"
},
{
"reason": "PostgreSQL performance work can overlap with query optimization, but that catalog dimension is broader and analytics-oriented.",
"with_dim_id": "data-access-and-query-optimization",
"with_dim_name": null,
"with_role": "Data Engineer"
}
],
"tentative_id": "d_init_01"
}
],
"merge_log": [],
"placed": {
"name": "PostgreSQL",
"placement_confidence": 0.92,
"primary_dimension": "d_init_01",
"reasoning": "Deterministic JD placement: locked_dimensions has 1 dimension(s) from skill-driven dimension generation after reconciliation; primary_dimension is the first locked dim.",
"secondary_dimensions": [],
"skill_id": "postgresql"
},
"relationships": {
"child_skills": [],
"parent_skills": [],
"related_to": [
"nosql",
"elasticsearch",
"amazon-athena",
"opensearch",
"microsoft-azure",
"aws-data-pipeline",
"linux",
"git",
"node-js",
"bash"
],
"requires": [
"sql"
],
"skill_id": "postgresql",
"suppress_on_match": []
},
"skill_id": "postgresql",
"split_log": [],
"typed": {
"alternatives_considered": [],
"confidence": 0.99,
"name": "PostgreSQL",
"reasoning": "By the Datastore vs Format rule, PostgreSQL persists data as a primary database system, so it is fundamentally a Datastore.",
"skill_id": "postgresql",
"subtype": "relational_database",
"type": "Datastore"
},
"warnings": []
},
"source_tag": "llm",
"was_in_llm_skills": true
},
{
"aliases_in_db": [],
"canonical": null,
"dimensions": [
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "MySQL Operational Monitoring, Logging, and Diagnostics",
"id": 166,
"rationale": "Covers the DBA practice of monitoring MySQL production health and using MySQL-native logs and diagnostic views to detect, investigate, and explain incidents or performance anomalies. Includes routine health checks, alerting, replication and availability monitoring, resource and connection monitoring, and use of error logs, slow query logs, SHOW PROCESSLIST, performance_schema, status variables, and diagnostic queries to understand behavior and support recovery decisions.",
"slug": "mysql-operational-monitoring-logging-and-diagnostics",
"source": "db"
},
"input_skill": "MySQL",
"llm_role": null,
"roles_from_db": [
{
"display_name": "MySQL DBA",
"id": 23,
"rationale": null,
"role_archetype": null,
"slug": "mysql-dba",
"source": "db"
}
]
},
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Data Access and Query Optimization",
"id": 74,
"rationale": "Techniques for making analytical data fast and reliable to query. This includes partitioning, clustering, indexing choices, file layout, and access-path tuning for downstream consumers.",
"slug": "data-access-and-query-optimization",
"source": "db"
},
"input_skill": "MySQL",
"llm_role": null,
"roles_from_db": [
{
"display_name": "Data Engineer",
"id": 6,
"rationale": null,
"role_archetype": null,
"slug": "data-engineer",
"source": "db"
}
]
},
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Data Access and Query Optimization",
"id": 74,
"rationale": "Techniques for making analytical data fast and reliable to query. This includes partitioning, clustering, indexing choices, file layout, and access-path tuning for downstream consumers.",
"slug": "data-access-and-query-optimization",
"source": "db"
},
"input_skill": "MySQL",
"llm_role": null,
"roles_from_db": [
{
"display_name": "Data Engineer",
"id": 6,
"rationale": null,
"role_archetype": null,
"slug": "data-engineer",
"source": "db"
}
]
}
],
"input_skill": "MySQL",
"matched_via": null,
"new_alias_persisted": false,
"new_alias_text": null,
"new_skill_meta": {
"derived": {
"category": "Datastore",
"skill_nature": "TOOL",
"sub_category": "relational_database",
"typical_lifespan": "EVERGREEN",
"version_strategy": "NOT_APPLICABLE",
"volatility": "STABLE"
},
"enrichment": {
"ambiguity": {
"ambiguity_flag": false,
"confused_with": [],
"reasoning": "MySQL is a specific, well-known relational database name in job descriptions and is usually not confused with other catalog skills."
},
"context_keywords": {
"context_keywords": [
"InnoDB",
"SQL",
"stored procedures",
"triggers",
"replication",
"sharding",
"indexing",
"query optimization",
"transactions",
"ACID",
"foreign keys",
"views",
"backup and restore",
"high availability",
"MariaDB"
]
},
"maturity": {
"confidence": 0.98,
"maturity": "well_known",
"reasoning": "MySQL appears in high-volume job postings across backend/data roles and remains a default managed option on AWS RDS, GCP Cloud SQL, and Azure Database for MySQL, indicating broad market adoption."
},
"skill_id": "mysql",
"vendor_license": {
"confidence": 0.98,
"license": "gpl_v2",
"vendor": "Oracle Corporation",
"year_introduced": 1995
},
"versioning": {
"current_version": null,
"version_aliases": {},
"versioned": false
}
},
"keep_log": [
{
"a_dim_id": "data-access-and-query-optimization",
"a_name": "Data Access and Query Optimization",
"a_role": "__skill_focal__",
"b_dim_id": "data-access-and-query-optimization",
"b_name": "Data Access and Query Optimization",
"b_role": "Data Engineer",
"pair_kind": "cross_role",
"reasoning": "Both share query-performance language, but A is MySQL/database-engine tuning (EXPLAIN, join optimization, buffer pool-aware tuning, SQL troubleshooting), while B is analytical data layout for downstream consumers (partitioning, clustering, file layout). The exemplar skills point to different work: A\u2019s MySQL and execution plan analysis vs B\u2019s warehouse/lakehouse storage design. Same words, different clusters.",
"similarity": 0.730054045199034
}
],
"locked_dimensions": [
{
"description": "Covers monitoring MySQL production health and using MySQL-native logs, status data, and diagnostic views to detect, investigate, and explain incidents or performance anomalies. Includes routine health checks, alerting, replication and availability monitoring, resource and connection monitoring, incident triage, and use of error logs, slow query logs, general logs, SHOW PROCESSLIST, performance_schema, information_schema, status variables, and diagnostic queries to understand behavior and support recovery decisions.",
"exemplar_skills": [
"MySQL Operational Monitoring, Logging, and Diagnostics"
],
"in_scope": "Skills, tools, and practices that belong under MySQL Operational Monitoring, Logging, and Diagnostics for the target role, including items implied by the dimension rationale.",
"name": "MySQL Operational Monitoring, Logging, and Diagnostics",
"out_of_scope": "Adjacent clusters explicitly not owned by MySQL Operational Monitoring, Logging, and Diagnostics, including unrelated platforms, roles, and skill families per library policy.",
"overlap_flags": [],
"tentative_id": "d_merge_01"
},
{
"description": "Covers how data is accessed efficiently through indexes, query plans, partitioning, and access-path tuning. MySQL belongs here because working effectively with it often requires understanding and improving query performance.",
"exemplar_skills": [
"MySQL",
"EXPLAIN",
"index tuning",
"query optimization",
"join optimization",
"partitioning",
"covering indexes",
"execution plan analysis"
],
"in_scope": "MySQL, indexes, EXPLAIN plans, query rewriting, join optimization, partitioning, covering indexes, cardinality, access-path analysis, buffer pool-aware tuning, SQL performance troubleshooting",
"name": "Data Access and Query Optimization",
"out_of_scope": "Backup/restore operations, replication setup, server monitoring, user authentication, application framework integration",
"overlap_flags": [
{
"reason": "Performance investigation often starts from logs and runtime metrics, which are owned by the operational diagnostics dimension.",
"with_dim_id": "mysql-operational-monitoring-logging-and-diagnostics",
"with_dim_name": null,
"with_role": "MySQL DBA"
}
],
"tentative_id": "data-access-and-query-optimization"
},
{
"description": "Techniques for making analytical data fast and reliable to query. This includes partitioning, clustering, indexing choices, file layout, and access-path tuning for downstream consumers.",
"exemplar_skills": [
"Data Access and Query Optimization"
],
"in_scope": "Skills, tools, and practices that belong under Data Access and Query Optimization for the target role, including items implied by the dimension rationale.",
"name": "Data Access and Query Optimization",
"out_of_scope": "Adjacent clusters explicitly not owned by Data Access and Query Optimization, including unrelated platforms, roles, and skill families per library policy.",
"overlap_flags": [],
"tentative_id": "data-access-and-query-optimization"
}
],
"merge_log": [
{
"a_dim_id": "mysql-operational-monitoring-logging-and-diagnostics",
"a_name": "MySQL Operational Monitoring and Diagnostics",
"a_role": "__skill_focal__",
"b_dim_id": "mysql-operational-monitoring-logging-and-diagnostics",
"b_name": "MySQL Operational Monitoring, Logging, and Diagnostics",
"b_role": "MySQL DBA",
"into": "d_merge_01",
"into_name": "MySQL Operational Monitoring, Logging, and Diagnostics",
"merged_from": [
"mysql-operational-monitoring-logging-and-diagnostics",
"mysql-operational-monitoring-logging-and-diagnostics"
],
"pair_kind": "cross_role",
"reasoning": "Both dims cover the same MySQL ops/DBA observability cluster: monitoring production health, reading MySQL logs, and using diagnostic views to explain incidents. Dim A cites MySQL error logs, slow query log, performance_schema, SHOW PROCESSLIST, replication lag checks, and deadlock investigation. Dim B repeats those same skills and adds routine health checks, alerting, status variables, and diagnostic queries. The overlap is substantive, not just lexical, so they should be unified.",
"similarity": 0.8926553133256224
}
],
"placed": {
"name": "MySQL",
"placement_confidence": 0.92,
"primary_dimension": "d_merge_01",
"reasoning": "Deterministic JD placement: locked_dimensions has 3 dimension(s) from skill-driven dimension generation after reconciliation; primary_dimension is the first locked dim.",
"secondary_dimensions": [
"data-access-and-query-optimization"
],
"skill_id": "mysql"
},
"relationships": {
"child_skills": [],
"parent_skills": [],
"related_to": [
"nosql",
"amazon-athena",
"elasticsearch",
"minio",
"aws",
"microsoft-azure",
"aws-lambda",
"linux",
"git",
"containers"
],
"requires": [
"sql"
],
"skill_id": "mysql",
"suppress_on_match": []
},
"skill_id": "mysql",
"split_log": [],
"typed": {
"alternatives_considered": [],
"confidence": 0.99,
"name": "MySQL",
"reasoning": "MySQL is fundamentally a system that persists and queries data, so by the Datastore vs Format rule it is a Datastore.",
"skill_id": "mysql",
"subtype": "relational_database",
"type": "Datastore"
},
"warnings": [
"stage3_post_filter_dropped_catalog_only_locked_dims:41-\u003e3"
]
},
"source_tag": "llm",
"was_in_llm_skills": true
},
{
"aliases_in_db": [
{
"alias_text": "MongoDB",
"alias_type": "CANONICAL",
"id": 684,
"is_primary": true,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "MongoDB 3",
"alias_type": "VERSION",
"id": 685,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "MongoDB 3.x",
"alias_type": "VERSION",
"id": 691,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "MongoDB 4",
"alias_type": "VERSION",
"id": 686,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "MongoDB 4.x",
"alias_type": "VERSION",
"id": 692,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "MongoDB 5",
"alias_type": "VERSION",
"id": 687,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "MongoDB 5.x",
"alias_type": "VERSION",
"id": 693,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "MongoDB 6",
"alias_type": "VERSION",
"id": 688,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "MongoDB 6.x",
"alias_type": "VERSION",
"id": 694,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "MongoDB 7",
"alias_type": "VERSION",
"id": 689,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "MongoDB 7.x",
"alias_type": "VERSION",
"id": 695,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "MongoDB 8",
"alias_type": "VERSION",
"id": 690,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "MongoDB 8.x",
"alias_type": "VERSION",
"id": 696,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
}
],
"canonical": {
"category_id": 12,
"display_name": "MongoDB",
"id": 432,
"is_also_category": false,
"is_extractable": true,
"skill_nature": "TOOL",
"slug": "mongodb",
"sub_category_id": 360,
"typical_lifespan": "EVERGREEN",
"volatility": "STABLE"
},
"dimensions": [
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "NoSQL and Cache Stores",
"id": 145,
"rationale": "Non-relational databases and in-memory stores used for low-latency access, flexible schemas, and specialized persistence patterns. This cluster is coherent because backend services often combine these stores with relational systems.",
"slug": "nosql-and-cache-stores",
"source": "db"
},
"input_skill": "MongoDB",
"llm_role": null,
"roles_from_db": [
{
"display_name": "Backend Engineer",
"id": 14,
"rationale": null,
"role_archetype": null,
"slug": "backend-engineer",
"source": "db"
}
]
},
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "NoSQL and Data Lake Storage",
"id": 73,
"rationale": "Non-relational stores and lake storage used for semi-structured, large-scale, or raw data retention. This cluster is coherent because many pipelines land and serve data outside classic relational warehouses.",
"slug": "nosql-and-data-lake-storage",
"source": "db"
},
"input_skill": "MongoDB",
"llm_role": null,
"roles_from_db": [
{
"display_name": "Data Engineer",
"id": 6,
"rationale": null,
"role_archetype": null,
"slug": "data-engineer",
"source": "db"
}
]
}
],
"input_skill": "MongoDB",
"matched_via": "alias",
"new_alias_persisted": false,
"new_alias_text": null,
"new_skill_meta": null,
"source_tag": "db",
"was_in_llm_skills": true
},
{
"aliases_in_db": [
{
"alias_text": "Redis",
"alias_type": "CANONICAL",
"id": 1278,
"is_primary": true,
"match_strategy": "CASE_INSENSITIVE"
}
],
"canonical": {
"category_id": 12,
"display_name": "Redis",
"id": 846,
"is_also_category": false,
"is_extractable": true,
"skill_nature": "TOOL",
"slug": "redis",
"sub_category_id": 701,
"typical_lifespan": "EVERGREEN",
"volatility": "STABLE"
},
"dimensions": [
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "NoSQL and Cache Stores",
"id": 145,
"rationale": "Non-relational databases and in-memory stores used for low-latency access, flexible schemas, and specialized persistence patterns. This cluster is coherent because backend services often combine these stores with relational systems.",
"slug": "nosql-and-cache-stores",
"source": "db"
},
"input_skill": "Redis",
"llm_role": null,
"roles_from_db": [
{
"display_name": "Backend Engineer",
"id": 14,
"rationale": null,
"role_archetype": null,
"slug": "backend-engineer",
"source": "db"
}
]
}
],
"input_skill": "Redis",
"matched_via": "alias",
"new_alias_persisted": false,
"new_alias_text": null,
"new_skill_meta": null,
"source_tag": "db",
"was_in_llm_skills": true
},
{
"aliases_in_db": [
{
"alias_text": "Apache Kafka",
"alias_type": "VERSION",
"id": 1295,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "Kafka",
"alias_type": "VERSION",
"id": 1284,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "Kafka 3",
"alias_type": "VERSION",
"id": 1286,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "Kafka 3.0",
"alias_type": "VERSION",
"id": 1287,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "Kafka 3.1",
"alias_type": "VERSION",
"id": 1288,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "Kafka 3.2",
"alias_type": "VERSION",
"id": 1289,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "Kafka 3.3",
"alias_type": "VERSION",
"id": 1290,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "Kafka 3.4",
"alias_type": "VERSION",
"id": 1291,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "Kafka 3.5",
"alias_type": "VERSION",
"id": 1292,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "Kafka 3.6",
"alias_type": "VERSION",
"id": 1293,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "Kafka 3.x",
"alias_type": "VERSION",
"id": 1294,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
}
],
"canonical": {
"category_id": 12,
"display_name": "Kafka",
"id": 852,
"is_also_category": false,
"is_extractable": true,
"skill_nature": "TOOL",
"slug": "kafka",
"sub_category_id": 700,
"typical_lifespan": "EVERGREEN",
"volatility": "STABLE"
},
"dimensions": [
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Messaging and Event Streaming",
"id": 146,
"rationale": "Asynchronous communication patterns and systems for decoupled service interaction and background processing. This is a coherent backend cluster because many server-side workflows depend on queues, topics, and event streams.",
"slug": "messaging-and-event-streaming",
"source": "db"
},
"input_skill": "Kafka",
"llm_role": null,
"roles_from_db": [
{
"display_name": "Backend Engineer",
"id": 14,
"rationale": null,
"role_archetype": null,
"slug": "backend-engineer",
"source": "db"
}
]
}
],
"input_skill": "Kafka",
"matched_via": "alias",
"new_alias_persisted": false,
"new_alias_text": null,
"new_skill_meta": null,
"source_tag": "db",
"was_in_llm_skills": true
},
{
"aliases_in_db": [
{
"alias_text": "RabbitMQ",
"alias_type": "CANONICAL",
"id": 1296,
"is_primary": true,
"match_strategy": "CASE_INSENSITIVE"
}
],
"canonical": {
"category_id": 11,
"display_name": "RabbitMQ",
"id": 853,
"is_also_category": false,
"is_extractable": true,
"skill_nature": "TOOL",
"slug": "rabbitmq",
"sub_category_id": 743,
"typical_lifespan": "EVERGREEN",
"volatility": "STABLE"
},
"dimensions": [
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Messaging and Event Streaming",
"id": 146,
"rationale": "Asynchronous communication patterns and systems for decoupled service interaction and background processing. This is a coherent backend cluster because many server-side workflows depend on queues, topics, and event streams.",
"slug": "messaging-and-event-streaming",
"source": "db"
},
"input_skill": "RabbitMQ",
"llm_role": null,
"roles_from_db": [
{
"display_name": "Backend Engineer",
"id": 14,
"rationale": null,
"role_archetype": null,
"slug": "backend-engineer",
"source": "db"
}
]
}
],
"input_skill": "RabbitMQ",
"matched_via": "alias",
"new_alias_persisted": false,
"new_alias_text": null,
"new_skill_meta": null,
"source_tag": "db",
"was_in_llm_skills": true
},
{
"aliases_in_db": [
{
"alias_text": "Docker",
"alias_type": "CANONICAL",
"id": 299,
"is_primary": true,
"match_strategy": "CASE_INSENSITIVE"
}
],
"canonical": {
"category_id": 11,
"display_name": "Docker",
"id": 153,
"is_also_category": false,
"is_extractable": true,
"skill_nature": "TOOL",
"slug": "docker",
"sub_category_id": 170,
"typical_lifespan": "EVERGREEN",
"volatility": "STABLE"
},
"dimensions": [
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Containerization and Image Delivery",
"id": 24,
"rationale": "Builds, packages, and ships application and support workloads as container images. This cluster covers the artifact format and the mechanics of producing deployable images.",
"slug": "containerization-and-image-delivery",
"source": "db"
},
"input_skill": "Docker",
"llm_role": null,
"roles_from_db": [
{
"display_name": "DevOps Engineer",
"id": 1,
"rationale": null,
"role_archetype": "A DevOps Engineer enables reliable, repeatable delivery of software by designing and operating the processes that connect development and production. They focus on improving deployment flow, operational stability, and collaboration between teams through automation, standardization, and monitoring of delivery and runtime practices.",
"slug": "devops-engineer",
"source": "db"
}
]
},
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Model Serving Deployment and Runtime Packaging",
"id": 52,
"rationale": "Operational deployment of trained models into online, batch, or streaming serving environments, including packaging models and model servers into containers or managed inference runtimes, coordinating rollout, and handing off to inference systems. Covers serving frameworks and platforms such as TensorFlow Serving, TorchServe, Triton Inference Server, BentoML, KServe, and Seldon Core, plus container/runtime concerns like Docker images, GPU-enabled containers, base image selection, container entrypoints, runtime dependencies, and image scanning for model services.",
"slug": "model-serving-deployment-and-runtime-packaging",
"source": "db"
},
"input_skill": "Docker",
"llm_role": null,
"roles_from_db": [
{
"display_name": "MLOps Engineer",
"id": 5,
"rationale": null,
"role_archetype": null,
"slug": "mlops-engineer",
"source": "db"
},
{
"display_name": "Machine Learning Engineer",
"id": 10,
"rationale": null,
"role_archetype": null,
"slug": "machine-learning-engineer",
"source": "db"
}
]
}
],
"input_skill": "Docker",
"matched_via": "alias",
"new_alias_persisted": false,
"new_alias_text": null,
"new_skill_meta": null,
"source_tag": "db",
"was_in_llm_skills": true
},
{
"aliases_in_db": [
{
"alias_text": "Kubernetes",
"alias_type": "CANONICAL",
"id": 304,
"is_primary": true,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "Kubernetes 1.0",
"alias_type": "VERSION",
"id": 307,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "Kubernetes 1.0+",
"alias_type": "VERSION",
"id": 2366,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "Kubernetes 1.1",
"alias_type": "VERSION",
"id": 308,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "Kubernetes 1.10",
"alias_type": "VERSION",
"id": 318,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "Kubernetes 1.11",
"alias_type": "VERSION",
"id": 319,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "Kubernetes 1.12",
"alias_type": "VERSION",
"id": 320,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "Kubernetes 1.13",
"alias_type": "VERSION",
"id": 321,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "Kubernetes 1.14",
"alias_type": "VERSION",
"id": 322,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "Kubernetes 1.15",
"alias_type": "VERSION",
"id": 323,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "Kubernetes 1.16",
"alias_type": "VERSION",
"id": 324,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "Kubernetes 1.17",
"alias_type": "VERSION",
"id": 325,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "Kubernetes 1.18",
"alias_type": "VERSION",
"id": 326,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "Kubernetes 1.19",
"alias_type": "VERSION",
"id": 327,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "Kubernetes 1.2",
"alias_type": "VERSION",
"id": 309,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "Kubernetes 1.20",
"alias_type": "VERSION",
"id": 328,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "Kubernetes 1.21",
"alias_type": "VERSION",
"id": 329,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "Kubernetes 1.22",
"alias_type": "VERSION",
"id": 330,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "Kubernetes 1.23",
"alias_type": "VERSION",
"id": 331,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "Kubernetes 1.24",
"alias_type": "VERSION",
"id": 332,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "Kubernetes 1.25",
"alias_type": "VERSION",
"id": 333,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "Kubernetes 1.26",
"alias_type": "VERSION",
"id": 334,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "Kubernetes 1.27",
"alias_type": "VERSION",
"id": 335,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "Kubernetes 1.28",
"alias_type": "VERSION",
"id": 336,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "Kubernetes 1.29",
"alias_type": "VERSION",
"id": 337,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "Kubernetes 1.3",
"alias_type": "VERSION",
"id": 310,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "Kubernetes 1.30",
"alias_type": "VERSION",
"id": 338,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "Kubernetes 1.4",
"alias_type": "VERSION",
"id": 311,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "Kubernetes 1.5",
"alias_type": "VERSION",
"id": 312,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "Kubernetes 1.6",
"alias_type": "VERSION",
"id": 313,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "Kubernetes 1.7",
"alias_type": "VERSION",
"id": 314,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "Kubernetes 1.8",
"alias_type": "VERSION",
"id": 315,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "Kubernetes 1.9",
"alias_type": "VERSION",
"id": 316,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "Kubernetes 1.x",
"alias_type": "VERSION",
"id": 317,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "Kubernetes v1",
"alias_type": "VERSION",
"id": 306,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "k8s",
"alias_type": "VERSION",
"id": 305,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
}
],
"canonical": {
"category_id": 13,
"display_name": "Kubernetes",
"id": 158,
"is_also_category": false,
"is_extractable": true,
"skill_nature": "PLATFORM",
"slug": "kubernetes",
"sub_category_id": 1524,
"typical_lifespan": "EVERGREEN",
"volatility": "STABLE"
},
"dimensions": [
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Orchestration Platforms",
"id": 25,
"rationale": "Operates the platforms that schedule and run containerized workloads and related deployment primitives. This is separate from image delivery because it concerns runtime placement and service rollout behavior.",
"slug": "orchestration-platforms",
"source": "db"
},
"input_skill": "Kubernetes",
"llm_role": null,
"roles_from_db": [
{
"display_name": "Cloud Engineer",
"id": 18,
"rationale": null,
"role_archetype": null,
"slug": "cloud-engineer",
"source": "db"
},
{
"display_name": "DevOps Engineer",
"id": 1,
"rationale": null,
"role_archetype": "A DevOps Engineer enables reliable, repeatable delivery of software by designing and operating the processes that connect development and production. They focus on improving deployment flow, operational stability, and collaboration between teams through automation, standardization, and monitoring of delivery and runtime practices.",
"slug": "devops-engineer",
"source": "db"
}
]
}
],
"input_skill": "Kubernetes",
"matched_via": "alias",
"new_alias_persisted": false,
"new_alias_text": null,
"new_skill_meta": null,
"source_tag": "db",
"was_in_llm_skills": true
},
{
"aliases_in_db": [
{
"alias_text": "Git",
"alias_type": "CANONICAL",
"id": 3375,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
}
],
"canonical": {
"category_id": 11,
"display_name": "Git",
"id": 2578,
"is_also_category": false,
"is_extractable": true,
"skill_nature": "TOOL",
"slug": "git",
"sub_category_id": 2101,
"typical_lifespan": "EVERGREEN",
"volatility": "STABLE"
},
"dimensions": [
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Version Control Systems",
"id": 365,
"rationale": "Tools and workflows for tracking source changes, branching, merging, and collaborating on code history. Git belongs here because it is the canonical distributed version control system used to manage revisions and coordinate team development.",
"slug": "d_init_01",
"source": "db"
},
"input_skill": "Git",
"llm_role": null,
"roles_from_db": []
}
],
"input_skill": "Git",
"matched_via": "alias",
"new_alias_persisted": false,
"new_alias_text": null,
"new_skill_meta": null,
"source_tag": "db",
"was_in_llm_skills": true
},
{
"aliases_in_db": [
{
"alias_text": "CI/CD",
"alias_type": "CANONICAL",
"id": 3376,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
}
],
"canonical": {
"category_id": 7,
"display_name": "CI/CD",
"id": 2579,
"is_also_category": false,
"is_extractable": true,
"skill_nature": "METHODOLOGY",
"slug": "ci-cd",
"sub_category_id": 2102,
"typical_lifespan": "EVERGREEN",
"volatility": "STABLE"
},
"dimensions": [
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Version Control Systems",
"id": 365,
"rationale": "Tools and workflows for tracking source changes, branching, merging, and collaborating on code history. Git belongs here because it is the canonical distributed version control system used to manage revisions and coordinate team development.",
"slug": "d_init_01",
"source": "db"
},
"input_skill": "CI/CD",
"llm_role": null,
"roles_from_db": []
}
],
"input_skill": "CI/CD",
"matched_via": "alias",
"new_alias_persisted": false,
"new_alias_text": null,
"new_skill_meta": null,
"source_tag": "db",
"was_in_llm_skills": true
},
{
"aliases_in_db": [
{
"alias_text": "AWS",
"alias_type": "CANONICAL",
"id": 348,
"is_primary": true,
"match_strategy": "CASE_INSENSITIVE"
}
],
"canonical": {
"category_id": 13,
"display_name": "AWS",
"id": 163,
"is_also_category": false,
"is_extractable": true,
"skill_nature": "PLATFORM",
"slug": "aws",
"sub_category_id": 161,
"typical_lifespan": "EVERGREEN",
"volatility": "STABLE"
},
"dimensions": [
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Cloud Platform Operations",
"id": 26,
"rationale": "Uses cloud provider services to support delivery and runtime environments. The focus is on consumer-level operation of cloud services rather than deep cloud architecture ownership.",
"slug": "cloud-platform-operations",
"source": "db"
},
"input_skill": "AWS",
"llm_role": null,
"roles_from_db": [
{
"display_name": "DevOps Engineer",
"id": 1,
"rationale": null,
"role_archetype": "A DevOps Engineer enables reliable, repeatable delivery of software by designing and operating the processes that connect development and production. They focus on improving deployment flow, operational stability, and collaboration between teams through automation, standardization, and monitoring of delivery and runtime practices.",
"slug": "devops-engineer",
"source": "db"
}
]
},
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Cloud Security Platforms",
"id": 332,
"rationale": "Cloud-native security products used to assess posture, detect misconfigurations, and monitor workloads across AWS, Azure, and GCP. This is a distinct product family because the role often works across multiple CNAPP/CSPM/CWPP offerings and cloud-native detectors.",
"slug": "cloud-security-platforms",
"source": "db"
},
"input_skill": "AWS",
"llm_role": null,
"roles_from_db": [
{
"display_name": "Cybersecurity Engineer",
"id": 9,
"rationale": null,
"role_archetype": null,
"slug": "cybersecurity-engineer",
"source": "db"
}
]
}
],
"input_skill": "AWS",
"matched_via": "alias",
"new_alias_persisted": false,
"new_alias_text": null,
"new_skill_meta": null,
"source_tag": "db",
"was_in_llm_skills": true
},
{
"aliases_in_db": [
{
"alias_text": "Azure",
"alias_type": "CANONICAL",
"id": 349,
"is_primary": true,
"match_strategy": "CASE_INSENSITIVE"
}
],
"canonical": {
"category_id": 13,
"display_name": "Azure",
"id": 164,
"is_also_category": false,
"is_extractable": true,
"skill_nature": "PLATFORM",
"slug": "azure",
"sub_category_id": 161,
"typical_lifespan": "EVERGREEN",
"volatility": "STABLE"
},
"dimensions": [
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Cloud Platform Operations",
"id": 26,
"rationale": "Uses cloud provider services to support delivery and runtime environments. The focus is on consumer-level operation of cloud services rather than deep cloud architecture ownership.",
"slug": "cloud-platform-operations",
"source": "db"
},
"input_skill": "Azure",
"llm_role": null,
"roles_from_db": [
{
"display_name": "DevOps Engineer",
"id": 1,
"rationale": null,
"role_archetype": "A DevOps Engineer enables reliable, repeatable delivery of software by designing and operating the processes that connect development and production. They focus on improving deployment flow, operational stability, and collaboration between teams through automation, standardization, and monitoring of delivery and runtime practices.",
"slug": "devops-engineer",
"source": "db"
}
]
},
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Cloud Security Platforms",
"id": 332,
"rationale": "Cloud-native security products used to assess posture, detect misconfigurations, and monitor workloads across AWS, Azure, and GCP. This is a distinct product family because the role often works across multiple CNAPP/CSPM/CWPP offerings and cloud-native detectors.",
"slug": "cloud-security-platforms",
"source": "db"
},
"input_skill": "Azure",
"llm_role": null,
"roles_from_db": [
{
"display_name": "Cybersecurity Engineer",
"id": 9,
"rationale": null,
"role_archetype": null,
"slug": "cybersecurity-engineer",
"source": "db"
}
]
}
],
"input_skill": "Azure",
"matched_via": "alias",
"new_alias_persisted": false,
"new_alias_text": null,
"new_skill_meta": null,
"source_tag": "db",
"was_in_llm_skills": true
},
{
"aliases_in_db": [
{
"alias_text": "GCP",
"alias_type": "CANONICAL",
"id": 3043,
"is_primary": true,
"match_strategy": "CASE_INSENSITIVE"
}
],
"canonical": {
"category_id": 13,
"display_name": "GCP",
"id": 2304,
"is_also_category": false,
"is_extractable": true,
"skill_nature": "PLATFORM",
"slug": "gcp",
"sub_category_id": 161,
"typical_lifespan": "EVERGREEN",
"volatility": "STABLE"
},
"dimensions": [
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Cloud Security Platforms",
"id": 332,
"rationale": "Cloud-native security products used to assess posture, detect misconfigurations, and monitor workloads across AWS, Azure, and GCP. This is a distinct product family because the role often works across multiple CNAPP/CSPM/CWPP offerings and cloud-native detectors.",
"slug": "cloud-security-platforms",
"source": "db"
},
"input_skill": "GCP",
"llm_role": null,
"roles_from_db": [
{
"display_name": "Cybersecurity Engineer",
"id": 9,
"rationale": null,
"role_archetype": null,
"slug": "cybersecurity-engineer",
"source": "db"
}
]
}
],
"input_skill": "GCP",
"matched_via": "alias",
"new_alias_persisted": false,
"new_alias_text": null,
"new_skill_meta": null,
"source_tag": "db",
"was_in_llm_skills": true
},
{
"aliases_in_db": [
{
"alias_text": "Prometheus",
"alias_type": "CANONICAL",
"id": 353,
"is_primary": true,
"match_strategy": "CASE_INSENSITIVE"
}
],
"canonical": {
"category_id": 13,
"display_name": "Prometheus",
"id": 168,
"is_also_category": false,
"is_extractable": true,
"skill_nature": "PLATFORM",
"slug": "prometheus",
"sub_category_id": 729,
"typical_lifespan": "EVERGREEN",
"volatility": "STABLE"
},
"dimensions": [
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Observability and Alerting",
"id": 27,
"rationale": "Builds feedback loops for system health through metrics, logs, traces, dashboards, and alerts. This cluster is coherent because it turns runtime behavior into actionable operational signals.",
"slug": "observability-and-alerting",
"source": "db"
},
"input_skill": "Prometheus",
"llm_role": null,
"roles_from_db": [
{
"display_name": "DevOps Engineer",
"id": 1,
"rationale": null,
"role_archetype": "A DevOps Engineer enables reliable, repeatable delivery of software by designing and operating the processes that connect development and production. They focus on improving deployment flow, operational stability, and collaboration between teams through automation, standardization, and monitoring of delivery and runtime practices.",
"slug": "devops-engineer",
"source": "db"
}
]
},
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Observability and Diagnostics",
"id": 151,
"rationale": "Logging, metrics, tracing, dashboards, and debugging practices used to understand backend behavior in production. This cluster is coherent because backend engineers must detect failures, performance issues, and unexpected behavior.",
"slug": "observability-and-diagnostics",
"source": "db"
},
"input_skill": "Prometheus",
"llm_role": null,
"roles_from_db": [
{
"display_name": "Backend Engineer",
"id": 14,
"rationale": null,
"role_archetype": null,
"slug": "backend-engineer",
"source": "db"
}
]
}
],
"input_skill": "Prometheus",
"matched_via": "alias",
"new_alias_persisted": false,
"new_alias_text": null,
"new_skill_meta": null,
"source_tag": "db",
"was_in_llm_skills": true
},
{
"aliases_in_db": [
{
"alias_text": "Grafana",
"alias_type": "CANONICAL",
"id": 354,
"is_primary": true,
"match_strategy": "CASE_INSENSITIVE"
}
],
"canonical": {
"category_id": 11,
"display_name": "Grafana",
"id": 169,
"is_also_category": false,
"is_extractable": true,
"skill_nature": "TOOL",
"slug": "grafana",
"sub_category_id": 331,
"typical_lifespan": "EVERGREEN",
"volatility": "STABLE"
},
"dimensions": [
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Observability and Alerting",
"id": 27,
"rationale": "Builds feedback loops for system health through metrics, logs, traces, dashboards, and alerts. This cluster is coherent because it turns runtime behavior into actionable operational signals.",
"slug": "observability-and-alerting",
"source": "db"
},
"input_skill": "Grafana",
"llm_role": null,
"roles_from_db": [
{
"display_name": "DevOps Engineer",
"id": 1,
"rationale": null,
"role_archetype": "A DevOps Engineer enables reliable, repeatable delivery of software by designing and operating the processes that connect development and production. They focus on improving deployment flow, operational stability, and collaboration between teams through automation, standardization, and monitoring of delivery and runtime practices.",
"slug": "devops-engineer",
"source": "db"
}
]
},
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Observability and Diagnostics",
"id": 151,
"rationale": "Logging, metrics, tracing, dashboards, and debugging practices used to understand backend behavior in production. This cluster is coherent because backend engineers must detect failures, performance issues, and unexpected behavior.",
"slug": "observability-and-diagnostics",
"source": "db"
},
"input_skill": "Grafana",
"llm_role": null,
"roles_from_db": [
{
"display_name": "Backend Engineer",
"id": 14,
"rationale": null,
"role_archetype": null,
"slug": "backend-engineer",
"source": "db"
}
]
}
],
"input_skill": "Grafana",
"matched_via": "alias",
"new_alias_persisted": false,
"new_alias_text": null,
"new_skill_meta": null,
"source_tag": "db",
"was_in_llm_skills": true
},
{
"aliases_in_db": [
{
"alias_text": "Agile",
"alias_type": "CANONICAL",
"id": 3401,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
}
],
"canonical": {
"category_id": 7,
"display_name": "Agile",
"id": 2604,
"is_also_category": false,
"is_extractable": true,
"skill_nature": "METHODOLOGY",
"slug": "agile",
"sub_category_id": 2124,
"typical_lifespan": "EVERGREEN",
"volatility": "STABLE"
},
"dimensions": [
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Project Delivery and Coordination",
"id": 366,
"rationale": "Coordination practices for organizing work, tracking progress, and aligning stakeholders across a delivery effort. Agile fits here when used as a team execution framework for managing scope, cadence, and collaboration.",
"slug": "d_init_02",
"source": "db"
},
"input_skill": "Agile",
"llm_role": null,
"roles_from_db": []
},
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Version Control Systems",
"id": 365,
"rationale": "Tools and workflows for tracking source changes, branching, merging, and collaborating on code history. Git belongs here because it is the canonical distributed version control system used to manage revisions and coordinate team development.",
"slug": "d_init_01",
"source": "db"
},
"input_skill": "Agile",
"llm_role": null,
"roles_from_db": []
}
],
"input_skill": "Agile",
"matched_via": "alias",
"new_alias_persisted": false,
"new_alias_text": null,
"new_skill_meta": null,
"source_tag": "db",
"was_in_llm_skills": true
},
{
"aliases_in_db": [
{
"alias_text": "Scrum",
"alias_type": "CANONICAL",
"id": 3402,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
}
],
"canonical": {
"category_id": 7,
"display_name": "Scrum",
"id": 2605,
"is_also_category": false,
"is_extractable": true,
"skill_nature": "METHODOLOGY",
"slug": "scrum",
"sub_category_id": 2125,
"typical_lifespan": "EVERGREEN",
"volatility": "STABLE"
},
"dimensions": [
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Version Control Systems",
"id": 365,
"rationale": "Tools and workflows for tracking source changes, branching, merging, and collaborating on code history. Git belongs here because it is the canonical distributed version control system used to manage revisions and coordinate team development.",
"slug": "d_init_01",
"source": "db"
},
"input_skill": "Scrum",
"llm_role": null,
"roles_from_db": []
}
],
"input_skill": "Scrum",
"matched_via": "alias",
"new_alias_persisted": false,
"new_alias_text": null,
"new_skill_meta": null,
"source_tag": "db",
"was_in_llm_skills": true
},
{
"aliases_in_db": [
{
"alias_text": "GraphQL",
"alias_type": "CANONICAL",
"id": 175,
"is_primary": true,
"match_strategy": "CASE_INSENSITIVE"
}
],
"canonical": {
"category_id": 8,
"display_name": "GraphQL",
"id": 50,
"is_also_category": false,
"is_extractable": true,
"skill_nature": "PROTOCOL",
"slug": "graphql",
"sub_category_id": 651,
"typical_lifespan": "EVERGREEN",
"volatility": "STABLE"
},
"dimensions": [
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "API Integration and Data Fetching",
"id": 9,
"rationale": "Connecting frontend applications to backend services and third-party endpoints. This covers request orchestration, error handling, pagination, and shaping remote data for UI consumption.",
"slug": "api-integration-and-data-fetching",
"source": "db"
},
"input_skill": "GraphQL",
"llm_role": null,
"roles_from_db": [
{
"display_name": "Frontend Engineer",
"id": 3,
"rationale": null,
"role_archetype": "Frontend Engineers design and build the user-facing parts of applications, translating product and design requirements into interactive experiences. They focus on how the application looks, behaves, and responds in the browser, ensuring usability, accessibility, and consistency across the interface.",
"slug": "frontend-engineer",
"source": "db"
},
{
"display_name": "Full Stack Developer",
"id": 2,
"rationale": null,
"role_archetype": null,
"slug": "full-stack-developer",
"source": "db"
}
]
},
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "API Integration and Serialization",
"id": 128,
"rationale": "Client-side integration with backend services, including request handling, response parsing, and contract alignment. This cluster is coherent because iOS features frequently depend on stable data exchange with server APIs.",
"slug": "api-integration-and-serialization",
"source": "db"
},
"input_skill": "GraphQL",
"llm_role": null,
"roles_from_db": [
{
"display_name": "iOS Engineer",
"id": 13,
"rationale": null,
"role_archetype": null,
"slug": "ios-engineer",
"source": "db"
}
]
}
],
"input_skill": "GraphQL",
"matched_via": "alias",
"new_alias_persisted": false,
"new_alias_text": null,
"new_skill_meta": null,
"source_tag": "db",
"was_in_llm_skills": true
},
{
"aliases_in_db": [
{
"alias_text": "Event-driven architecture",
"alias_type": "CANONICAL",
"id": 1630,
"is_primary": true,
"match_strategy": "CASE_INSENSITIVE"
}
],
"canonical": {
"category_id": 1,
"display_name": "Event-driven architecture",
"id": 1156,
"is_also_category": false,
"is_extractable": true,
"skill_nature": "PATTERN",
"slug": "event-driven-architecture",
"sub_category_id": 911,
"typical_lifespan": "EVERGREEN",
"volatility": "STABLE"
},
"dimensions": [
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Cloud Service Integration Patterns",
"id": 188,
"rationale": "Covers how cloud services and workloads connect through APIs, events, shared services, and integration boundaries. This cluster is coherent because architects must define interaction patterns that preserve decoupling, security, and operability.",
"slug": "cloud-service-integration-patterns",
"source": "db"
},
"input_skill": "Event-Driven Architecture",
"llm_role": null,
"roles_from_db": [
{
"display_name": "Cloud Architect",
"id": 11,
"rationale": null,
"role_archetype": null,
"slug": "cloud-architect",
"source": "db"
}
]
}
],
"input_skill": "Event-Driven Architecture",
"matched_via": "alias",
"new_alias_persisted": false,
"new_alias_text": null,
"new_skill_meta": null,
"source_tag": "db",
"was_in_llm_skills": true
}
],
"unmatched_skills": [
"Express.js",
"PostgreSQL",
"MySQL"
]
}
API 3 — final-role-output
{
"chosen_role": {
"display_name": "Backend Engineer",
"id": 14,
"rationale": "The primary skills indicate a strong emphasis on backend development, which aligns with the role of a Backend Engineer.",
"role_archetype": null,
"slug": "backend-engineer",
"source": "db"
},
"chosen_role_resolution": "in_db",
"final_input_skills": [
{
"skill": "REST",
"tag": "in_db"
},
{
"skill": "Node.js",
"tag": "in_db"
},
{
"skill": "Java",
"tag": "in_db"
},
{
"skill": "Python",
"tag": "in_db"
},
{
"skill": "Go",
"tag": "in_db"
},
{
"skill": "Express.js",
"tag": "new"
},
{
"skill": "Spring Boot",
"tag": "in_db"
},
{
"skill": "FastAPI",
"tag": "in_db"
},
{
"skill": "Microservices",
"tag": "in_db"
},
{
"skill": "PostgreSQL",
"tag": "new"
},
{
"skill": "MySQL",
"tag": "new"
},
{
"skill": "MongoDB",
"tag": "in_db"
},
{
"skill": "Redis",
"tag": "in_db"
},
{
"skill": "Kafka",
"tag": "in_db"
},
{
"skill": "RabbitMQ",
"tag": "in_db"
},
{
"skill": "Docker",
"tag": "in_db"
},
{
"skill": "Kubernetes",
"tag": "in_db"
},
{
"skill": "Git",
"tag": "in_db"
},
{
"skill": "CI/CD",
"tag": "in_db"
},
{
"skill": "AWS",
"tag": "in_db"
},
{
"skill": "Azure",
"tag": "in_db"
},
{
"skill": "GCP",
"tag": "in_db"
},
{
"skill": "Prometheus",
"tag": "in_db"
},
{
"skill": "Grafana",
"tag": "in_db"
},
{
"skill": "Agile",
"tag": "in_db"
},
{
"skill": "Scrum",
"tag": "in_db"
},
{
"skill": "GraphQL",
"tag": "in_db"
},
{
"skill": "Event-Driven Architecture",
"tag": "in_db"
}
],
"persistence": {
"items": [
{
"chosen_role_id": 14,
"dimension": {
"difficulty_hint": "well_known",
"display_name": "API Integration and Data Fetching",
"id": 9,
"rationale": "Connecting frontend applications to backend services and third-party endpoints. This covers request orchestration, error handling, pagination, and shaping remote data for UI consumption.",
"slug": "api-integration-and-data-fetching",
"source": "db"
},
"dimension_id": 9,
"input_skill": "REST",
"llm_role": null,
"matched_chosen_role": false,
"outcome_line": "Existing dimension (library) \u00b7 Role\u2194dimension skipped (dimension not under chosen role)",
"role_dimension_saved": false,
"roles_from_db": [
{
"display_name": "Frontend Engineer",
"id": 3,
"rationale": null,
"role_archetype": "Frontend Engineers design and build the user-facing parts of applications, translating product and design requirements into interactive experiences. They focus on how the application looks, behaves, and responds in the browser, ensuring usability, accessibility, and consistency across the interface.",
"slug": "frontend-engineer",
"source": "db"
},
{
"display_name": "Full Stack Developer",
"id": 2,
"rationale": null,
"role_archetype": null,
"slug": "full-stack-developer",
"source": "db"
}
],
"skill_dimension_saved": true,
"skill_id": 121,
"skill_tag": "in_db",
"skipped_reason": null
},
{
"chosen_role_id": 14,
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Programming Languages for Backend Systems",
"id": 140,
"rationale": "Languages used to implement server-side business logic, request handlers, workers, and service integrations. This is the core coding surface for backend feature delivery and maintenance.",
"slug": "programming-languages-for-backend-systems",
"source": "db"
},
"dimension_id": 140,
"input_skill": "Node.js",
"llm_role": null,
"matched_chosen_role": true,
"outcome_line": "Existing dimension (library) \u00b7 Role\u2194dimension saved",
"role_dimension_saved": true,
"roles_from_db": [
{
"display_name": "Backend Engineer",
"id": 14,
"rationale": null,
"role_archetype": null,
"slug": "backend-engineer",
"source": "db"
}
],
"skill_dimension_saved": true,
"skill_id": 2599,
"skill_tag": "in_db",
"skipped_reason": null
},
{
"chosen_role_id": 14,
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Programming Languages for AI Workflows",
"id": 261,
"rationale": "Languages used to implement AI feature logic, orchestration, and response handling inside product code. This is the core coding surface for turning prompts and model calls into reliable application behavior.",
"slug": "programming-languages-for-ai-workflows",
"source": "db"
},
"dimension_id": 261,
"input_skill": "Java",
"llm_role": null,
"matched_chosen_role": false,
"outcome_line": "Existing dimension (library) \u00b7 Role\u2194dimension skipped (dimension not under chosen role)",
"role_dimension_saved": false,
"roles_from_db": [
{
"display_name": "AI Engineer",
"id": 12,
"rationale": null,
"role_archetype": null,
"slug": "ai-engineer",
"source": "db"
}
],
"skill_dimension_saved": true,
"skill_id": 395,
"skill_tag": "in_db",
"skipped_reason": null
},
{
"chosen_role_id": 14,
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Programming Languages for Backend Systems",
"id": 140,
"rationale": "Languages used to implement server-side business logic, request handlers, workers, and service integrations. This is the core coding surface for backend feature delivery and maintenance.",
"slug": "programming-languages-for-backend-systems",
"source": "db"
},
"dimension_id": 140,
"input_skill": "Java",
"llm_role": null,
"matched_chosen_role": true,
"outcome_line": "Existing dimension (library) \u00b7 Role\u2194dimension saved",
"role_dimension_saved": true,
"roles_from_db": [
{
"display_name": "Backend Engineer",
"id": 14,
"rationale": null,
"role_archetype": null,
"slug": "backend-engineer",
"source": "db"
}
],
"skill_dimension_saved": true,
"skill_id": 395,
"skill_tag": "in_db",
"skipped_reason": null
},
{
"chosen_role_id": 14,
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Programming Languages for Data Work",
"id": 67,
"rationale": "Languages used to implement data pipelines, transformations, and operational utilities. This is the code layer for expressing extraction, parsing, validation, and orchestration logic in data engineering workflows.",
"slug": "programming-languages-for-data-work",
"source": "db"
},
"dimension_id": 67,
"input_skill": "Java",
"llm_role": null,
"matched_chosen_role": false,
"outcome_line": "Existing dimension (library) \u00b7 Role\u2194dimension skipped (dimension not under chosen role)",
"role_dimension_saved": false,
"roles_from_db": [
{
"display_name": "Data Engineer",
"id": 6,
"rationale": null,
"role_archetype": null,
"slug": "data-engineer",
"source": "db"
}
],
"skill_dimension_saved": true,
"skill_id": 395,
"skill_tag": "in_db",
"skipped_reason": null
},
{
"chosen_role_id": 14,
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Programming Languages for ML Systems",
"id": 113,
"rationale": "Languages used to implement model integration code, inference services, and feature-processing logic. This is the core coding surface for turning trained models into product-facing software components.",
"slug": "programming-languages-for-ml-systems",
"source": "db"
},
"dimension_id": 113,
"input_skill": "Java",
"llm_role": null,
"matched_chosen_role": false,
"outcome_line": "Existing dimension (library) \u00b7 Role\u2194dimension skipped (dimension not under chosen role)",
"role_dimension_saved": false,
"roles_from_db": [
{
"display_name": "Machine Learning Engineer",
"id": 10,
"rationale": null,
"role_archetype": null,
"slug": "machine-learning-engineer",
"source": "db"
}
],
"skill_dimension_saved": true,
"skill_id": 395,
"skill_tag": "in_db",
"skipped_reason": null
},
{
"chosen_role_id": 14,
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Programming Languages for Test Automation",
"id": 193,
"rationale": "Languages used to implement automated checks, helper utilities, and test harness code. This is the core coding surface for turning test ideas into maintainable automation.",
"slug": "programming-languages-for-test-automation",
"source": "db"
},
"dimension_id": 193,
"input_skill": "Java",
"llm_role": null,
"matched_chosen_role": false,
"outcome_line": "Existing dimension (library) \u00b7 Role\u2194dimension skipped (dimension not under chosen role)",
"role_dimension_saved": false,
"roles_from_db": [
{
"display_name": "Automation Tester",
"id": 16,
"rationale": null,
"role_archetype": null,
"slug": "automation-tester",
"source": "db"
}
],
"skill_dimension_saved": true,
"skill_id": 395,
"skill_tag": "in_db",
"skipped_reason": null
},
{
"chosen_role_id": 14,
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Analytical Programming Languages",
"id": 82,
"rationale": "Languages used to clean, transform, analyze, and prototype models in notebooks and scripts. This is the core coding surface for expressing statistical logic and data manipulation in a reproducible way.",
"slug": "analytical-programming-languages",
"source": "db"
},
"dimension_id": 82,
"input_skill": "Python",
"llm_role": null,
"matched_chosen_role": false,
"outcome_line": "Existing dimension (library) \u00b7 Role\u2194dimension skipped (dimension not under chosen role)",
"role_dimension_saved": false,
"roles_from_db": [
{
"display_name": "Data Analyst",
"id": 20,
"rationale": null,
"role_archetype": null,
"slug": "data-analyst",
"source": "db"
},
{
"display_name": "Data Scientist",
"id": 7,
"rationale": null,
"role_archetype": null,
"slug": "data-scientist",
"source": "db"
}
],
"skill_dimension_saved": true,
"skill_id": 393,
"skill_tag": "in_db",
"skipped_reason": null
},
{
"chosen_role_id": 14,
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Automation Scripting and CLI",
"id": 48,
"rationale": "Uses scripts and command-line tooling to execute repeatable Azure operations and reduce manual work. This is a practical cluster because the role frequently automates provisioning, checks, and remediation tasks.",
"slug": "automation-scripting-and-cli",
"source": "db"
},
"dimension_id": 48,
"input_skill": "Python",
"llm_role": null,
"matched_chosen_role": false,
"outcome_line": "Existing dimension (library) \u00b7 Role\u2194dimension skipped (dimension not under chosen role)",
"role_dimension_saved": false,
"roles_from_db": [
{
"display_name": "Azure Cloud Engineer",
"id": 4,
"rationale": null,
"role_archetype": null,
"slug": "azure-cloud-engineer",
"source": "db"
},
{
"display_name": "Cloud Engineer",
"id": 18,
"rationale": null,
"role_archetype": null,
"slug": "cloud-engineer",
"source": "db"
}
],
"skill_dimension_saved": true,
"skill_id": 393,
"skill_tag": "in_db",
"skipped_reason": null
},
{
"chosen_role_id": 14,
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Automation and Scripting for Operations",
"id": 361,
"rationale": "Scripts and lightweight automation used to execute repetitive virtualization tasks and enforce operational consistency. This is the practical glue that reduces manual host and VM administration.",
"slug": "automation-and-scripting-for-operations",
"source": "db"
},
"dimension_id": 361,
"input_skill": "Python",
"llm_role": null,
"matched_chosen_role": false,
"outcome_line": "Existing dimension (library) \u00b7 Role\u2194dimension skipped (dimension not under chosen role)",
"role_dimension_saved": false,
"roles_from_db": [
{
"display_name": "Virtualization Engineer",
"id": 26,
"rationale": null,
"role_archetype": null,
"slug": "virtualization-engineer",
"source": "db"
}
],
"skill_dimension_saved": true,
"skill_id": 393,
"skill_tag": "in_db",
"skipped_reason": null
},
{
"chosen_role_id": 14,
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Network Automation and Scripting",
"id": 285,
"rationale": "Covers scripts and automation used to configure, validate, and audit network devices and services. This cluster is coherent because repeatable network operations increasingly depend on programmatic changes and checks.",
"slug": "network-automation-and-scripting",
"source": "db"
},
"dimension_id": 285,
"input_skill": "Python",
"llm_role": null,
"matched_chosen_role": false,
"outcome_line": "Existing dimension (library) \u00b7 Role\u2194dimension skipped (dimension not under chosen role)",
"role_dimension_saved": false,
"roles_from_db": [
{
"display_name": "Network Engineer",
"id": 21,
"rationale": null,
"role_archetype": null,
"slug": "network-engineer",
"source": "db"
}
],
"skill_dimension_saved": true,
"skill_id": 393,
"skill_tag": "in_db",
"skipped_reason": null
},
{
"chosen_role_id": 14,
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Programming Languages for AI Workflows",
"id": 261,
"rationale": "Languages used to implement AI feature logic, orchestration, and response handling inside product code. This is the core coding surface for turning prompts and model calls into reliable application behavior.",
"slug": "programming-languages-for-ai-workflows",
"source": "db"
},
"dimension_id": 261,
"input_skill": "Python",
"llm_role": null,
"matched_chosen_role": false,
"outcome_line": "Existing dimension (library) \u00b7 Role\u2194dimension skipped (dimension not under chosen role)",
"role_dimension_saved": false,
"roles_from_db": [
{
"display_name": "AI Engineer",
"id": 12,
"rationale": null,
"role_archetype": null,
"slug": "ai-engineer",
"source": "db"
}
],
"skill_dimension_saved": true,
"skill_id": 393,
"skill_tag": "in_db",
"skipped_reason": null
},
{
"chosen_role_id": 14,
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Programming Languages for Backend Systems",
"id": 140,
"rationale": "Languages used to implement server-side business logic, request handlers, workers, and service integrations. This is the core coding surface for backend feature delivery and maintenance.",
"slug": "programming-languages-for-backend-systems",
"source": "db"
},
"dimension_id": 140,
"input_skill": "Python",
"llm_role": null,
"matched_chosen_role": true,
"outcome_line": "Existing dimension (library) \u00b7 Role\u2194dimension saved",
"role_dimension_saved": true,
"roles_from_db": [
{
"display_name": "Backend Engineer",
"id": 14,
"rationale": null,
"role_archetype": null,
"slug": "backend-engineer",
"source": "db"
}
],
"skill_dimension_saved": true,
"skill_id": 393,
"skill_tag": "in_db",
"skipped_reason": null
},
{
"chosen_role_id": 14,
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Programming Languages for Data Work",
"id": 67,
"rationale": "Languages used to implement data pipelines, transformations, and operational utilities. This is the code layer for expressing extraction, parsing, validation, and orchestration logic in data engineering workflows.",
"slug": "programming-languages-for-data-work",
"source": "db"
},
"dimension_id": 67,
"input_skill": "Python",
"llm_role": null,
"matched_chosen_role": false,
"outcome_line": "Existing dimension (library) \u00b7 Role\u2194dimension skipped (dimension not under chosen role)",
"role_dimension_saved": false,
"roles_from_db": [
{
"display_name": "Data Engineer",
"id": 6,
"rationale": null,
"role_archetype": null,
"slug": "data-engineer",
"source": "db"
}
],
"skill_dimension_saved": true,
"skill_id": 393,
"skill_tag": "in_db",
"skipped_reason": null
},
{
"chosen_role_id": 14,
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Programming Languages for ML Systems",
"id": 113,
"rationale": "Languages used to implement model integration code, inference services, and feature-processing logic. This is the core coding surface for turning trained models into product-facing software components.",
"slug": "programming-languages-for-ml-systems",
"source": "db"
},
"dimension_id": 113,
"input_skill": "Python",
"llm_role": null,
"matched_chosen_role": false,
"outcome_line": "Existing dimension (library) \u00b7 Role\u2194dimension skipped (dimension not under chosen role)",
"role_dimension_saved": false,
"roles_from_db": [
{
"display_name": "Machine Learning Engineer",
"id": 10,
"rationale": null,
"role_archetype": null,
"slug": "machine-learning-engineer",
"source": "db"
}
],
"skill_dimension_saved": true,
"skill_id": 393,
"skill_tag": "in_db",
"skipped_reason": null
},
{
"chosen_role_id": 14,
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Programming Languages for Security Work",
"id": 328,
"rationale": "Languages used to automate security tasks, write detection logic, and build analysis or remediation tooling. This is the core coding surface for a cybersecurity engineer across scripts, queries, and small utilities.",
"slug": "programming-languages-for-security-work",
"source": "db"
},
"dimension_id": 328,
"input_skill": "Python",
"llm_role": null,
"matched_chosen_role": false,
"outcome_line": "Existing dimension (library) \u00b7 Role\u2194dimension skipped (dimension not under chosen role)",
"role_dimension_saved": false,
"roles_from_db": [
{
"display_name": "Cybersecurity Engineer",
"id": 9,
"rationale": null,
"role_archetype": null,
"slug": "cybersecurity-engineer",
"source": "db"
}
],
"skill_dimension_saved": true,
"skill_id": 393,
"skill_tag": "in_db",
"skipped_reason": null
},
{
"chosen_role_id": 14,
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Programming Languages for Test Automation",
"id": 193,
"rationale": "Languages used to implement automated checks, helper utilities, and test harness code. This is the core coding surface for turning test ideas into maintainable automation.",
"slug": "programming-languages-for-test-automation",
"source": "db"
},
"dimension_id": 193,
"input_skill": "Python",
"llm_role": null,
"matched_chosen_role": false,
"outcome_line": "Existing dimension (library) \u00b7 Role\u2194dimension skipped (dimension not under chosen role)",
"role_dimension_saved": false,
"roles_from_db": [
{
"display_name": "Automation Tester",
"id": 16,
"rationale": null,
"role_archetype": null,
"slug": "automation-tester",
"source": "db"
}
],
"skill_dimension_saved": true,
"skill_id": 393,
"skill_tag": "in_db",
"skipped_reason": null
},
{
"chosen_role_id": 14,
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Security Automation and Scripting",
"id": 258,
"rationale": "Automating repeatable security checks, enrichment, and remediation workflows. This cluster is coherent because the role often needs lightweight automation to scale analysis and response.",
"slug": "security-automation-and-scripting",
"source": "db"
},
"dimension_id": 258,
"input_skill": "Python",
"llm_role": null,
"matched_chosen_role": false,
"outcome_line": "Existing dimension (library) \u00b7 Role\u2194dimension skipped (dimension not under chosen role)",
"role_dimension_saved": false,
"roles_from_db": [
{
"display_name": "Cybersecurity Engineer",
"id": 9,
"rationale": null,
"role_archetype": null,
"slug": "cybersecurity-engineer",
"source": "db"
}
],
"skill_dimension_saved": true,
"skill_id": 393,
"skill_tag": "in_db",
"skipped_reason": null
},
{
"chosen_role_id": 14,
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Programming Languages for Backend Systems",
"id": 140,
"rationale": "Languages used to implement server-side business logic, request handlers, workers, and service integrations. This is the core coding surface for backend feature delivery and maintenance.",
"slug": "programming-languages-for-backend-systems",
"source": "db"
},
"dimension_id": 140,
"input_skill": "Go",
"llm_role": null,
"matched_chosen_role": true,
"outcome_line": "Existing dimension (library) \u00b7 Role\u2194dimension saved",
"role_dimension_saved": true,
"roles_from_db": [
{
"display_name": "Backend Engineer",
"id": 14,
"rationale": null,
"role_archetype": null,
"slug": "backend-engineer",
"source": "db"
}
],
"skill_dimension_saved": true,
"skill_id": 679,
"skill_tag": "in_db",
"skipped_reason": null
},
{
"chosen_role_id": 14,
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Programming Languages for ML Systems",
"id": 113,
"rationale": "Languages used to implement model integration code, inference services, and feature-processing logic. This is the core coding surface for turning trained models into product-facing software components.",
"slug": "programming-languages-for-ml-systems",
"source": "db"
},
"dimension_id": 113,
"input_skill": "Go",
"llm_role": null,
"matched_chosen_role": false,
"outcome_line": "Existing dimension (library) \u00b7 Role\u2194dimension skipped (dimension not under chosen role)",
"role_dimension_saved": false,
"roles_from_db": [
{
"display_name": "Machine Learning Engineer",
"id": 10,
"rationale": null,
"role_archetype": null,
"slug": "machine-learning-engineer",
"source": "db"
}
],
"skill_dimension_saved": true,
"skill_id": 679,
"skill_tag": "in_db",
"skipped_reason": null
},
{
"chosen_role_id": 14,
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Programming Languages for Security Work",
"id": 328,
"rationale": "Languages used to automate security tasks, write detection logic, and build analysis or remediation tooling. This is the core coding surface for a cybersecurity engineer across scripts, queries, and small utilities.",
"slug": "programming-languages-for-security-work",
"source": "db"
},
"dimension_id": 328,
"input_skill": "Go",
"llm_role": null,
"matched_chosen_role": false,
"outcome_line": "Existing dimension (library) \u00b7 Role\u2194dimension skipped (dimension not under chosen role)",
"role_dimension_saved": false,
"roles_from_db": [
{
"display_name": "Cybersecurity Engineer",
"id": 9,
"rationale": null,
"role_archetype": null,
"slug": "cybersecurity-engineer",
"source": "db"
}
],
"skill_dimension_saved": true,
"skill_id": 679,
"skill_tag": "in_db",
"skipped_reason": null
},
{
"chosen_role_id": 14,
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Inference Service Frameworks",
"id": 114,
"rationale": "Web and service frameworks used to expose model predictions through APIs and application endpoints. This cluster is coherent because MLEs often implement the runtime surface where requests enter and predictions leave the system.",
"slug": "inference-service-frameworks",
"source": "db"
},
"dimension_id": 114,
"input_skill": "Spring Boot",
"llm_role": null,
"matched_chosen_role": false,
"outcome_line": "Existing dimension (library) \u00b7 Role\u2194dimension skipped (dimension not under chosen role)",
"role_dimension_saved": false,
"roles_from_db": [
{
"display_name": "Machine Learning Engineer",
"id": 10,
"rationale": null,
"role_archetype": null,
"slug": "machine-learning-engineer",
"source": "db"
}
],
"skill_dimension_saved": true,
"skill_id": 684,
"skill_tag": "in_db",
"skipped_reason": null
},
{
"chosen_role_id": 14,
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Web Service Frameworks",
"id": 141,
"rationale": "Server frameworks used to build HTTP APIs, route requests, validate inputs, and structure backend application code. This cluster is coherent because it defines how backend services expose behavior to clients and other services.",
"slug": "web-service-frameworks",
"source": "db"
},
"dimension_id": 141,
"input_skill": "Spring Boot",
"llm_role": null,
"matched_chosen_role": true,
"outcome_line": "Existing dimension (library) \u00b7 Role\u2194dimension saved",
"role_dimension_saved": true,
"roles_from_db": [
{
"display_name": "Backend Engineer",
"id": 14,
"rationale": null,
"role_archetype": null,
"slug": "backend-engineer",
"source": "db"
}
],
"skill_dimension_saved": true,
"skill_id": 684,
"skill_tag": "in_db",
"skipped_reason": null
},
{
"chosen_role_id": 14,
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Inference Service Frameworks",
"id": 114,
"rationale": "Web and service frameworks used to expose model predictions through APIs and application endpoints. This cluster is coherent because MLEs often implement the runtime surface where requests enter and predictions leave the system.",
"slug": "inference-service-frameworks",
"source": "db"
},
"dimension_id": 114,
"input_skill": "FastAPI",
"llm_role": null,
"matched_chosen_role": false,
"outcome_line": "Existing dimension (library) \u00b7 Role\u2194dimension skipped (dimension not under chosen role)",
"role_dimension_saved": false,
"roles_from_db": [
{
"display_name": "Machine Learning Engineer",
"id": 10,
"rationale": null,
"role_archetype": null,
"slug": "machine-learning-engineer",
"source": "db"
}
],
"skill_dimension_saved": true,
"skill_id": 682,
"skill_tag": "in_db",
"skipped_reason": null
},
{
"chosen_role_id": 14,
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Web Service Frameworks",
"id": 141,
"rationale": "Server frameworks used to build HTTP APIs, route requests, validate inputs, and structure backend application code. This cluster is coherent because it defines how backend services expose behavior to clients and other services.",
"slug": "web-service-frameworks",
"source": "db"
},
"dimension_id": 141,
"input_skill": "FastAPI",
"llm_role": null,
"matched_chosen_role": true,
"outcome_line": "Existing dimension (library) \u00b7 Role\u2194dimension saved",
"role_dimension_saved": true,
"roles_from_db": [
{
"display_name": "Backend Engineer",
"id": 14,
"rationale": null,
"role_archetype": null,
"slug": "backend-engineer",
"source": "db"
}
],
"skill_dimension_saved": true,
"skill_id": 682,
"skill_tag": "in_db",
"skipped_reason": null
},
{
"chosen_role_id": 14,
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Service Architecture and Integration",
"id": 148,
"rationale": "Patterns for structuring backend systems as services and coordinating calls across internal and external dependencies. This includes how services are decomposed, connected, and evolved safely.",
"slug": "service-architecture-and-integration",
"source": "db"
},
"dimension_id": 148,
"input_skill": "Microservices",
"llm_role": null,
"matched_chosen_role": true,
"outcome_line": "Existing dimension (library) \u00b7 Role\u2194dimension saved",
"role_dimension_saved": true,
"roles_from_db": [
{
"display_name": "Backend Engineer",
"id": 14,
"rationale": null,
"role_archetype": null,
"slug": "backend-engineer",
"source": "db"
}
],
"skill_dimension_saved": true,
"skill_id": 864,
"skill_tag": "in_db",
"skipped_reason": null
},
{
"chosen_role_id": 14,
"dimension": {
"difficulty_hint": "well_known",
"display_name": "NoSQL and Cache Stores",
"id": 145,
"rationale": "Non-relational databases and in-memory stores used for low-latency access, flexible schemas, and specialized persistence patterns. This cluster is coherent because backend services often combine these stores with relational systems.",
"slug": "nosql-and-cache-stores",
"source": "db"
},
"dimension_id": 145,
"input_skill": "MongoDB",
"llm_role": null,
"matched_chosen_role": true,
"outcome_line": "Existing dimension (library) \u00b7 Role\u2194dimension saved",
"role_dimension_saved": true,
"roles_from_db": [
{
"display_name": "Backend Engineer",
"id": 14,
"rationale": null,
"role_archetype": null,
"slug": "backend-engineer",
"source": "db"
}
],
"skill_dimension_saved": true,
"skill_id": 432,
"skill_tag": "in_db",
"skipped_reason": null
},
{
"chosen_role_id": 14,
"dimension": {
"difficulty_hint": "well_known",
"display_name": "NoSQL and Data Lake Storage",
"id": 73,
"rationale": "Non-relational stores and lake storage used for semi-structured, large-scale, or raw data retention. This cluster is coherent because many pipelines land and serve data outside classic relational warehouses.",
"slug": "nosql-and-data-lake-storage",
"source": "db"
},
"dimension_id": 73,
"input_skill": "MongoDB",
"llm_role": null,
"matched_chosen_role": false,
"outcome_line": "Existing dimension (library) \u00b7 Role\u2194dimension skipped (dimension not under chosen role)",
"role_dimension_saved": false,
"roles_from_db": [
{
"display_name": "Data Engineer",
"id": 6,
"rationale": null,
"role_archetype": null,
"slug": "data-engineer",
"source": "db"
}
],
"skill_dimension_saved": true,
"skill_id": 432,
"skill_tag": "in_db",
"skipped_reason": null
},
{
"chosen_role_id": 14,
"dimension": {
"difficulty_hint": "well_known",
"display_name": "NoSQL and Cache Stores",
"id": 145,
"rationale": "Non-relational databases and in-memory stores used for low-latency access, flexible schemas, and specialized persistence patterns. This cluster is coherent because backend services often combine these stores with relational systems.",
"slug": "nosql-and-cache-stores",
"source": "db"
},
"dimension_id": 145,
"input_skill": "Redis",
"llm_role": null,
"matched_chosen_role": true,
"outcome_line": "Existing dimension (library) \u00b7 Role\u2194dimension saved",
"role_dimension_saved": true,
"roles_from_db": [
{
"display_name": "Backend Engineer",
"id": 14,
"rationale": null,
"role_archetype": null,
"slug": "backend-engineer",
"source": "db"
}
],
"skill_dimension_saved": true,
"skill_id": 846,
"skill_tag": "in_db",
"skipped_reason": null
},
{
"chosen_role_id": 14,
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Messaging and Event Streaming",
"id": 146,
"rationale": "Asynchronous communication patterns and systems for decoupled service interaction and background processing. This is a coherent backend cluster because many server-side workflows depend on queues, topics, and event streams.",
"slug": "messaging-and-event-streaming",
"source": "db"
},
"dimension_id": 146,
"input_skill": "Kafka",
"llm_role": null,
"matched_chosen_role": true,
"outcome_line": "Existing dimension (library) \u00b7 Role\u2194dimension saved",
"role_dimension_saved": true,
"roles_from_db": [
{
"display_name": "Backend Engineer",
"id": 14,
"rationale": null,
"role_archetype": null,
"slug": "backend-engineer",
"source": "db"
}
],
"skill_dimension_saved": true,
"skill_id": 852,
"skill_tag": "in_db",
"skipped_reason": null
},
{
"chosen_role_id": 14,
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Messaging and Event Streaming",
"id": 146,
"rationale": "Asynchronous communication patterns and systems for decoupled service interaction and background processing. This is a coherent backend cluster because many server-side workflows depend on queues, topics, and event streams.",
"slug": "messaging-and-event-streaming",
"source": "db"
},
"dimension_id": 146,
"input_skill": "RabbitMQ",
"llm_role": null,
"matched_chosen_role": true,
"outcome_line": "Existing dimension (library) \u00b7 Role\u2194dimension saved",
"role_dimension_saved": true,
"roles_from_db": [
{
"display_name": "Backend Engineer",
"id": 14,
"rationale": null,
"role_archetype": null,
"slug": "backend-engineer",
"source": "db"
}
],
"skill_dimension_saved": true,
"skill_id": 853,
"skill_tag": "in_db",
"skipped_reason": null
},
{
"chosen_role_id": 14,
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Containerization and Image Delivery",
"id": 24,
"rationale": "Builds, packages, and ships application and support workloads as container images. This cluster covers the artifact format and the mechanics of producing deployable images.",
"slug": "containerization-and-image-delivery",
"source": "db"
},
"dimension_id": 24,
"input_skill": "Docker",
"llm_role": null,
"matched_chosen_role": false,
"outcome_line": "Existing dimension (library) \u00b7 Role\u2194dimension skipped (dimension not under chosen role)",
"role_dimension_saved": false,
"roles_from_db": [
{
"display_name": "DevOps Engineer",
"id": 1,
"rationale": null,
"role_archetype": "A DevOps Engineer enables reliable, repeatable delivery of software by designing and operating the processes that connect development and production. They focus on improving deployment flow, operational stability, and collaboration between teams through automation, standardization, and monitoring of delivery and runtime practices.",
"slug": "devops-engineer",
"source": "db"
}
],
"skill_dimension_saved": true,
"skill_id": 153,
"skill_tag": "in_db",
"skipped_reason": null
},
{
"chosen_role_id": 14,
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Model Serving Deployment and Runtime Packaging",
"id": 52,
"rationale": "Operational deployment of trained models into online, batch, or streaming serving environments, including packaging models and model servers into containers or managed inference runtimes, coordinating rollout, and handing off to inference systems. Covers serving frameworks and platforms such as TensorFlow Serving, TorchServe, Triton Inference Server, BentoML, KServe, and Seldon Core, plus container/runtime concerns like Docker images, GPU-enabled containers, base image selection, container entrypoints, runtime dependencies, and image scanning for model services.",
"slug": "model-serving-deployment-and-runtime-packaging",
"source": "db"
},
"dimension_id": 52,
"input_skill": "Docker",
"llm_role": null,
"matched_chosen_role": false,
"outcome_line": "Existing dimension (library) \u00b7 Role\u2194dimension skipped (dimension not under chosen role)",
"role_dimension_saved": false,
"roles_from_db": [
{
"display_name": "MLOps Engineer",
"id": 5,
"rationale": null,
"role_archetype": null,
"slug": "mlops-engineer",
"source": "db"
},
{
"display_name": "Machine Learning Engineer",
"id": 10,
"rationale": null,
"role_archetype": null,
"slug": "machine-learning-engineer",
"source": "db"
}
],
"skill_dimension_saved": true,
"skill_id": 153,
"skill_tag": "in_db",
"skipped_reason": null
},
{
"chosen_role_id": 14,
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Orchestration Platforms",
"id": 25,
"rationale": "Operates the platforms that schedule and run containerized workloads and related deployment primitives. This is separate from image delivery because it concerns runtime placement and service rollout behavior.",
"slug": "orchestration-platforms",
"source": "db"
},
"dimension_id": 25,
"input_skill": "Kubernetes",
"llm_role": null,
"matched_chosen_role": false,
"outcome_line": "Existing dimension (library) \u00b7 Role\u2194dimension skipped (dimension not under chosen role)",
"role_dimension_saved": false,
"roles_from_db": [
{
"display_name": "Cloud Engineer",
"id": 18,
"rationale": null,
"role_archetype": null,
"slug": "cloud-engineer",
"source": "db"
},
{
"display_name": "DevOps Engineer",
"id": 1,
"rationale": null,
"role_archetype": "A DevOps Engineer enables reliable, repeatable delivery of software by designing and operating the processes that connect development and production. They focus on improving deployment flow, operational stability, and collaboration between teams through automation, standardization, and monitoring of delivery and runtime practices.",
"slug": "devops-engineer",
"source": "db"
}
],
"skill_dimension_saved": true,
"skill_id": 158,
"skill_tag": "in_db",
"skipped_reason": null
},
{
"chosen_role_id": 14,
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Version Control Systems",
"id": 365,
"rationale": "Tools and workflows for tracking source changes, branching, merging, and collaborating on code history. Git belongs here because it is the canonical distributed version control system used to manage revisions and coordinate team development.",
"slug": "d_init_01",
"source": "db"
},
"dimension_id": 365,
"input_skill": "Git",
"llm_role": null,
"matched_chosen_role": false,
"outcome_line": "Existing dimension (library) \u00b7 Role\u2194dimension skipped (dimension not under chosen role)",
"role_dimension_saved": false,
"roles_from_db": [],
"skill_dimension_saved": true,
"skill_id": 2578,
"skill_tag": "in_db",
"skipped_reason": null
},
{
"chosen_role_id": 14,
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Version Control Systems",
"id": 365,
"rationale": "Tools and workflows for tracking source changes, branching, merging, and collaborating on code history. Git belongs here because it is the canonical distributed version control system used to manage revisions and coordinate team development.",
"slug": "d_init_01",
"source": "db"
},
"dimension_id": 365,
"input_skill": "CI/CD",
"llm_role": null,
"matched_chosen_role": false,
"outcome_line": "Existing dimension (library) \u00b7 Role\u2194dimension skipped (dimension not under chosen role)",
"role_dimension_saved": false,
"roles_from_db": [],
"skill_dimension_saved": true,
"skill_id": 2579,
"skill_tag": "in_db",
"skipped_reason": null
},
{
"chosen_role_id": 14,
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Cloud Platform Operations",
"id": 26,
"rationale": "Uses cloud provider services to support delivery and runtime environments. The focus is on consumer-level operation of cloud services rather than deep cloud architecture ownership.",
"slug": "cloud-platform-operations",
"source": "db"
},
"dimension_id": 26,
"input_skill": "AWS",
"llm_role": null,
"matched_chosen_role": false,
"outcome_line": "Existing dimension (library) \u00b7 Role\u2194dimension skipped (dimension not under chosen role)",
"role_dimension_saved": false,
"roles_from_db": [
{
"display_name": "DevOps Engineer",
"id": 1,
"rationale": null,
"role_archetype": "A DevOps Engineer enables reliable, repeatable delivery of software by designing and operating the processes that connect development and production. They focus on improving deployment flow, operational stability, and collaboration between teams through automation, standardization, and monitoring of delivery and runtime practices.",
"slug": "devops-engineer",
"source": "db"
}
],
"skill_dimension_saved": true,
"skill_id": 163,
"skill_tag": "in_db",
"skipped_reason": null
},
{
"chosen_role_id": 14,
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Cloud Security Platforms",
"id": 332,
"rationale": "Cloud-native security products used to assess posture, detect misconfigurations, and monitor workloads across AWS, Azure, and GCP. This is a distinct product family because the role often works across multiple CNAPP/CSPM/CWPP offerings and cloud-native detectors.",
"slug": "cloud-security-platforms",
"source": "db"
},
"dimension_id": 332,
"input_skill": "AWS",
"llm_role": null,
"matched_chosen_role": false,
"outcome_line": "Existing dimension (library) \u00b7 Role\u2194dimension skipped (dimension not under chosen role)",
"role_dimension_saved": false,
"roles_from_db": [
{
"display_name": "Cybersecurity Engineer",
"id": 9,
"rationale": null,
"role_archetype": null,
"slug": "cybersecurity-engineer",
"source": "db"
}
],
"skill_dimension_saved": true,
"skill_id": 163,
"skill_tag": "in_db",
"skipped_reason": null
},
{
"chosen_role_id": 14,
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Cloud Platform Operations",
"id": 26,
"rationale": "Uses cloud provider services to support delivery and runtime environments. The focus is on consumer-level operation of cloud services rather than deep cloud architecture ownership.",
"slug": "cloud-platform-operations",
"source": "db"
},
"dimension_id": 26,
"input_skill": "Azure",
"llm_role": null,
"matched_chosen_role": false,
"outcome_line": "Existing dimension (library) \u00b7 Role\u2194dimension skipped (dimension not under chosen role)",
"role_dimension_saved": false,
"roles_from_db": [
{
"display_name": "DevOps Engineer",
"id": 1,
"rationale": null,
"role_archetype": "A DevOps Engineer enables reliable, repeatable delivery of software by designing and operating the processes that connect development and production. They focus on improving deployment flow, operational stability, and collaboration between teams through automation, standardization, and monitoring of delivery and runtime practices.",
"slug": "devops-engineer",
"source": "db"
}
],
"skill_dimension_saved": true,
"skill_id": 164,
"skill_tag": "in_db",
"skipped_reason": null
},
{
"chosen_role_id": 14,
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Cloud Security Platforms",
"id": 332,
"rationale": "Cloud-native security products used to assess posture, detect misconfigurations, and monitor workloads across AWS, Azure, and GCP. This is a distinct product family because the role often works across multiple CNAPP/CSPM/CWPP offerings and cloud-native detectors.",
"slug": "cloud-security-platforms",
"source": "db"
},
"dimension_id": 332,
"input_skill": "Azure",
"llm_role": null,
"matched_chosen_role": false,
"outcome_line": "Existing dimension (library) \u00b7 Role\u2194dimension skipped (dimension not under chosen role)",
"role_dimension_saved": false,
"roles_from_db": [
{
"display_name": "Cybersecurity Engineer",
"id": 9,
"rationale": null,
"role_archetype": null,
"slug": "cybersecurity-engineer",
"source": "db"
}
],
"skill_dimension_saved": true,
"skill_id": 164,
"skill_tag": "in_db",
"skipped_reason": null
},
{
"chosen_role_id": 14,
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Cloud Security Platforms",
"id": 332,
"rationale": "Cloud-native security products used to assess posture, detect misconfigurations, and monitor workloads across AWS, Azure, and GCP. This is a distinct product family because the role often works across multiple CNAPP/CSPM/CWPP offerings and cloud-native detectors.",
"slug": "cloud-security-platforms",
"source": "db"
},
"dimension_id": 332,
"input_skill": "GCP",
"llm_role": null,
"matched_chosen_role": false,
"outcome_line": "Existing dimension (library) \u00b7 Role\u2194dimension skipped (dimension not under chosen role)",
"role_dimension_saved": false,
"roles_from_db": [
{
"display_name": "Cybersecurity Engineer",
"id": 9,
"rationale": null,
"role_archetype": null,
"slug": "cybersecurity-engineer",
"source": "db"
}
],
"skill_dimension_saved": true,
"skill_id": 2304,
"skill_tag": "in_db",
"skipped_reason": null
},
{
"chosen_role_id": 14,
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Observability and Alerting",
"id": 27,
"rationale": "Builds feedback loops for system health through metrics, logs, traces, dashboards, and alerts. This cluster is coherent because it turns runtime behavior into actionable operational signals.",
"slug": "observability-and-alerting",
"source": "db"
},
"dimension_id": 27,
"input_skill": "Prometheus",
"llm_role": null,
"matched_chosen_role": false,
"outcome_line": "Existing dimension (library) \u00b7 Role\u2194dimension skipped (dimension not under chosen role)",
"role_dimension_saved": false,
"roles_from_db": [
{
"display_name": "DevOps Engineer",
"id": 1,
"rationale": null,
"role_archetype": "A DevOps Engineer enables reliable, repeatable delivery of software by designing and operating the processes that connect development and production. They focus on improving deployment flow, operational stability, and collaboration between teams through automation, standardization, and monitoring of delivery and runtime practices.",
"slug": "devops-engineer",
"source": "db"
}
],
"skill_dimension_saved": true,
"skill_id": 168,
"skill_tag": "in_db",
"skipped_reason": null
},
{
"chosen_role_id": 14,
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Observability and Diagnostics",
"id": 151,
"rationale": "Logging, metrics, tracing, dashboards, and debugging practices used to understand backend behavior in production. This cluster is coherent because backend engineers must detect failures, performance issues, and unexpected behavior.",
"slug": "observability-and-diagnostics",
"source": "db"
},
"dimension_id": 151,
"input_skill": "Prometheus",
"llm_role": null,
"matched_chosen_role": true,
"outcome_line": "Existing dimension (library) \u00b7 Role\u2194dimension saved",
"role_dimension_saved": true,
"roles_from_db": [
{
"display_name": "Backend Engineer",
"id": 14,
"rationale": null,
"role_archetype": null,
"slug": "backend-engineer",
"source": "db"
}
],
"skill_dimension_saved": true,
"skill_id": 168,
"skill_tag": "in_db",
"skipped_reason": null
},
{
"chosen_role_id": 14,
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Observability and Alerting",
"id": 27,
"rationale": "Builds feedback loops for system health through metrics, logs, traces, dashboards, and alerts. This cluster is coherent because it turns runtime behavior into actionable operational signals.",
"slug": "observability-and-alerting",
"source": "db"
},
"dimension_id": 27,
"input_skill": "Grafana",
"llm_role": null,
"matched_chosen_role": false,
"outcome_line": "Existing dimension (library) \u00b7 Role\u2194dimension skipped (dimension not under chosen role)",
"role_dimension_saved": false,
"roles_from_db": [
{
"display_name": "DevOps Engineer",
"id": 1,
"rationale": null,
"role_archetype": "A DevOps Engineer enables reliable, repeatable delivery of software by designing and operating the processes that connect development and production. They focus on improving deployment flow, operational stability, and collaboration between teams through automation, standardization, and monitoring of delivery and runtime practices.",
"slug": "devops-engineer",
"source": "db"
}
],
"skill_dimension_saved": true,
"skill_id": 169,
"skill_tag": "in_db",
"skipped_reason": null
},
{
"chosen_role_id": 14,
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Observability and Diagnostics",
"id": 151,
"rationale": "Logging, metrics, tracing, dashboards, and debugging practices used to understand backend behavior in production. This cluster is coherent because backend engineers must detect failures, performance issues, and unexpected behavior.",
"slug": "observability-and-diagnostics",
"source": "db"
},
"dimension_id": 151,
"input_skill": "Grafana",
"llm_role": null,
"matched_chosen_role": true,
"outcome_line": "Existing dimension (library) \u00b7 Role\u2194dimension saved",
"role_dimension_saved": true,
"roles_from_db": [
{
"display_name": "Backend Engineer",
"id": 14,
"rationale": null,
"role_archetype": null,
"slug": "backend-engineer",
"source": "db"
}
],
"skill_dimension_saved": true,
"skill_id": 169,
"skill_tag": "in_db",
"skipped_reason": null
},
{
"chosen_role_id": 14,
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Project Delivery and Coordination",
"id": 366,
"rationale": "Coordination practices for organizing work, tracking progress, and aligning stakeholders across a delivery effort. Agile fits here when used as a team execution framework for managing scope, cadence, and collaboration.",
"slug": "d_init_02",
"source": "db"
},
"dimension_id": 366,
"input_skill": "Agile",
"llm_role": null,
"matched_chosen_role": false,
"outcome_line": "Existing dimension (library) \u00b7 Role\u2194dimension skipped (dimension not under chosen role)",
"role_dimension_saved": false,
"roles_from_db": [],
"skill_dimension_saved": true,
"skill_id": 2604,
"skill_tag": "in_db",
"skipped_reason": null
},
{
"chosen_role_id": 14,
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Version Control Systems",
"id": 365,
"rationale": "Tools and workflows for tracking source changes, branching, merging, and collaborating on code history. Git belongs here because it is the canonical distributed version control system used to manage revisions and coordinate team development.",
"slug": "d_init_01",
"source": "db"
},
"dimension_id": 365,
"input_skill": "Agile",
"llm_role": null,
"matched_chosen_role": false,
"outcome_line": "Existing dimension (library) \u00b7 Role\u2194dimension skipped (dimension not under chosen role)",
"role_dimension_saved": false,
"roles_from_db": [],
"skill_dimension_saved": true,
"skill_id": 2604,
"skill_tag": "in_db",
"skipped_reason": null
},
{
"chosen_role_id": 14,
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Version Control Systems",
"id": 365,
"rationale": "Tools and workflows for tracking source changes, branching, merging, and collaborating on code history. Git belongs here because it is the canonical distributed version control system used to manage revisions and coordinate team development.",
"slug": "d_init_01",
"source": "db"
},
"dimension_id": 365,
"input_skill": "Scrum",
"llm_role": null,
"matched_chosen_role": false,
"outcome_line": "Existing dimension (library) \u00b7 Role\u2194dimension skipped (dimension not under chosen role)",
"role_dimension_saved": false,
"roles_from_db": [],
"skill_dimension_saved": true,
"skill_id": 2605,
"skill_tag": "in_db",
"skipped_reason": null
},
{
"chosen_role_id": 14,
"dimension": {
"difficulty_hint": "well_known",
"display_name": "API Integration and Data Fetching",
"id": 9,
"rationale": "Connecting frontend applications to backend services and third-party endpoints. This covers request orchestration, error handling, pagination, and shaping remote data for UI consumption.",
"slug": "api-integration-and-data-fetching",
"source": "db"
},
"dimension_id": 9,
"input_skill": "GraphQL",
"llm_role": null,
"matched_chosen_role": false,
"outcome_line": "Existing dimension (library) \u00b7 Role\u2194dimension skipped (dimension not under chosen role)",
"role_dimension_saved": false,
"roles_from_db": [
{
"display_name": "Frontend Engineer",
"id": 3,
"rationale": null,
"role_archetype": "Frontend Engineers design and build the user-facing parts of applications, translating product and design requirements into interactive experiences. They focus on how the application looks, behaves, and responds in the browser, ensuring usability, accessibility, and consistency across the interface.",
"slug": "frontend-engineer",
"source": "db"
},
{
"display_name": "Full Stack Developer",
"id": 2,
"rationale": null,
"role_archetype": null,
"slug": "full-stack-developer",
"source": "db"
}
],
"skill_dimension_saved": true,
"skill_id": 50,
"skill_tag": "in_db",
"skipped_reason": null
},
{
"chosen_role_id": 14,
"dimension": {
"difficulty_hint": "well_known",
"display_name": "API Integration and Serialization",
"id": 128,
"rationale": "Client-side integration with backend services, including request handling, response parsing, and contract alignment. This cluster is coherent because iOS features frequently depend on stable data exchange with server APIs.",
"slug": "api-integration-and-serialization",
"source": "db"
},
"dimension_id": 128,
"input_skill": "GraphQL",
"llm_role": null,
"matched_chosen_role": false,
"outcome_line": "Existing dimension (library) \u00b7 Role\u2194dimension skipped (dimension not under chosen role)",
"role_dimension_saved": false,
"roles_from_db": [
{
"display_name": "iOS Engineer",
"id": 13,
"rationale": null,
"role_archetype": null,
"slug": "ios-engineer",
"source": "db"
}
],
"skill_dimension_saved": true,
"skill_id": 50,
"skill_tag": "in_db",
"skipped_reason": null
},
{
"chosen_role_id": 14,
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Cloud Service Integration Patterns",
"id": 188,
"rationale": "Covers how cloud services and workloads connect through APIs, events, shared services, and integration boundaries. This cluster is coherent because architects must define interaction patterns that preserve decoupling, security, and operability.",
"slug": "cloud-service-integration-patterns",
"source": "db"
},
"dimension_id": 188,
"input_skill": "Event-Driven Architecture",
"llm_role": null,
"matched_chosen_role": false,
"outcome_line": "Existing dimension (library) \u00b7 Role\u2194dimension skipped (dimension not under chosen role)",
"role_dimension_saved": false,
"roles_from_db": [
{
"display_name": "Cloud Architect",
"id": 11,
"rationale": null,
"role_archetype": null,
"slug": "cloud-architect",
"source": "db"
}
],
"skill_dimension_saved": true,
"skill_id": 1156,
"skill_tag": "in_db",
"skipped_reason": null
},
{
"chosen_role_id": 14,
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Version Control Systems",
"id": 365,
"rationale": "Tools and workflows for tracking source changes, branching, merging, and collaborating on code history. Git belongs here because it is the canonical distributed version control system used to manage revisions and coordinate team development.",
"slug": "d_init_01",
"source": "db"
},
"dimension_id": 365,
"input_skill": "Express.js",
"llm_role": null,
"matched_chosen_role": false,
"outcome_line": "New skill saved \u00b7 Existing dimension (library) \u00b7 Role\u2194dimension skipped (dimension not under chosen role)",
"role_dimension_saved": false,
"roles_from_db": [],
"skill_dimension_saved": true,
"skill_id": 2668,
"skill_tag": "in_db",
"skipped_reason": null
},
{
"chosen_role_id": 14,
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Version Control Systems",
"id": 365,
"rationale": "Tools and workflows for tracking source changes, branching, merging, and collaborating on code history. Git belongs here because it is the canonical distributed version control system used to manage revisions and coordinate team development.",
"slug": "d_init_01",
"source": "db"
},
"dimension_id": 365,
"input_skill": "PostgreSQL",
"llm_role": null,
"matched_chosen_role": false,
"outcome_line": "New skill saved \u00b7 Existing dimension (library) \u00b7 Role\u2194dimension skipped (dimension not under chosen role)",
"role_dimension_saved": false,
"roles_from_db": [],
"skill_dimension_saved": true,
"skill_id": 2669,
"skill_tag": "in_db",
"skipped_reason": null
},
{
"chosen_role_id": 14,
"dimension": {
"difficulty_hint": "well_known",
"display_name": "MySQL Operational Monitoring, Logging, and Diagnostics",
"id": 166,
"rationale": "Covers the DBA practice of monitoring MySQL production health and using MySQL-native logs and diagnostic views to detect, investigate, and explain incidents or performance anomalies. Includes routine health checks, alerting, replication and availability monitoring, resource and connection monitoring, and use of error logs, slow query logs, SHOW PROCESSLIST, performance_schema, status variables, and diagnostic queries to understand behavior and support recovery decisions.",
"slug": "mysql-operational-monitoring-logging-and-diagnostics",
"source": "db"
},
"dimension_id": 166,
"input_skill": "MySQL",
"llm_role": null,
"matched_chosen_role": false,
"outcome_line": "New skill saved \u00b7 Existing dimension (library) \u00b7 Role\u2194dimension skipped (dimension not under chosen role)",
"role_dimension_saved": false,
"roles_from_db": [
{
"display_name": "MySQL DBA",
"id": 23,
"rationale": null,
"role_archetype": null,
"slug": "mysql-dba",
"source": "db"
}
],
"skill_dimension_saved": true,
"skill_id": 2670,
"skill_tag": "in_db",
"skipped_reason": null
},
{
"chosen_role_id": 14,
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Data Access and Query Optimization",
"id": 74,
"rationale": "Techniques for making analytical data fast and reliable to query. This includes partitioning, clustering, indexing choices, file layout, and access-path tuning for downstream consumers.",
"slug": "data-access-and-query-optimization",
"source": "db"
},
"dimension_id": 74,
"input_skill": "MySQL",
"llm_role": null,
"matched_chosen_role": false,
"outcome_line": "New skill saved \u00b7 Existing dimension (library) \u00b7 Role\u2194dimension skipped (dimension not under chosen role)",
"role_dimension_saved": false,
"roles_from_db": [
{
"display_name": "Data Engineer",
"id": 6,
"rationale": null,
"role_archetype": null,
"slug": "data-engineer",
"source": "db"
}
],
"skill_dimension_saved": true,
"skill_id": 2670,
"skill_tag": "in_db",
"skipped_reason": null
},
{
"chosen_role_id": 14,
"dimension": {
"difficulty_hint": "well_known",
"display_name": "MySQL Operational Monitoring, Logging, and Diagnostics",
"id": null,
"rationale": "Covers monitoring MySQL production health and using MySQL-native logs, status data, and diagnostic views to detect, investigate, and explain incidents or performance anomalies. Includes routine health checks, alerting, replication and availability monitoring, resource and connection monitoring, incident triage, and use of error logs, slow query logs, general logs, SHOW PROCESSLIST, performance_schema, information_schema, status variables, and diagnostic queries to understand behavior and support recovery decisions.",
"slug": "d_merge_01",
"source": "llm"
},
"dimension_id": 166,
"input_skill": "MySQL",
"llm_role": null,
"matched_chosen_role": false,
"outcome_line": "New skill saved \u00b7 Existing dimension (reconciliation merge) \u00b7 Role\u2194dimension skipped (dimension not under chosen role)",
"role_dimension_saved": false,
"roles_from_db": [],
"skill_dimension_saved": true,
"skill_id": 2670,
"skill_tag": "in_db",
"skipped_reason": null
}
],
"new_skills_created": 3,
"role_dimension_saved": 0,
"skill_dimension_saved": 4,
"skipped": 0
},
"planner_output": null,
"run_id": "8077639b-c7cb-4ba7-998c-e936e0f7c4d4"
}
LLM Calls
Every model call made for this run, in pipeline order. Click a card to see the model's response.