Pipeline run
14665224-3376-48b7-92b4-7aed97ed2be8
Client output enrichment
v2 Skill cluster · Nature of work · AI index · Tech stack maturity · Evidence · KRA descriptionvocab breakdown (legacy)
Signals
Post-classification
Captured for admin review
1 POST /skills/extract-from-jd
2 POST /skills/extract-details
3 POST /skills/final-role-output
Backend Developer
→Java Backend Developer
sub-role · 0.99 domain · Software Engineering CASE DOMAINslug: backend-engineer · id: 1 · source: db · sub-role slug: java-backend-developer
Domain=Software Engineering → sub-role java-backend-developer; The JD is centered on Java microservices, REST APIs, CI/CD, Docker/Kubernetes, and backend integration work, which best matches Backend Developer.
Matched skills
Matched dimensions
Matched KRAs
Resolution:
in_db
— role exists in library; skill↔dim and role↔dim links saved when applicable.
Job description
We are currently looking for a remote Senior Java Software Engineer with 3+ years of experience working with Java8+ to join our team. The customer is one of the world’s leading broadband, communication and converged video companies, with operations in six European countries. Responsibilities Develop MicroservicesParticipate in planning and management of the development processActively communicate with the stakeholdersContribute to continuous delivery and integration pipeline infrastructureImplement technical decisions with little supervisionWrite unit and some integration tests Requirements 3+ years of experience working with Java8+Background in SDLC, including coding standards, code reviews, source control management (Git), Agile development, build processes, testing and operationsUnderstanding of Microservice architectures, RESTful API designKnowledge of Docker containers and container orchestration systems like Kubernetes or Amazon EKSExperience with Java DI and IoC frameworks: Dropwizard, Spring or othersGood communication and problem-solving skillsEnglish B2 or higher Nice to have Kafka knowledgeExperience with legacy system integration and phased application integration Technologies MicroservicesDropwizardJettyJerseyNetflix HystrixZipkinPostgreSQLPrometheusDockerKubernetesKibanaGrafanaGitApache MavenApache KafkaContinuous Delivery approachBDD approach We offer Insurance Coverage Paid Leaves – including maternity, bereavement, paternity, and special COVID-19 leaves. Financial assistance for medical crisis Retiral Benefits – VPF and NPS Customized Mindfulness and Wellness programs EPAM Hobby ClubsHybrid Work Model Soft loans to set up workspace at home Stable workload Relocation opportunities with ‘EPAM without Borders’ programCertification trainings for technical and soft skills Access to unlimited LinkedIn Learning platform Access to internal learning programs set up by world class trainers Community networking and idea creation platforms Mentorship programs Self-driven career progression tool This is a remote position and we welcome applications from anywhere in India We accept CVs only in English. Please note that even though you are applying for this position, you may be offered other projects to join within EPAM Anywhere. Once you apply, you'll receive a confirmation email with a link to EPAM Anywhere platform. Sign up with this link to automate your prescreening, be able to monitor your application statuses, and enjoy a faster job application process. EPAM Anywhere — an online remote jobs platform for IT professionals. EPAM Anywhere allows technical specialists to quickly and easily find projects that match their knowledge and experience while working remotely with Forbes Global 2000 clients, building a successful IT career, and earning competitive rewards. EPAM Anywhere provides additional perks, including a flexible schedule, professional development opportunities, and access to a community of experts. The program offers open positions in 15+ countries—with plans to expand in the future. As of today, the platform is used by thousands of IT specialists across more than 165 cities around the world. Join EPAM Anywhere today at anywhere.epam.com. EPAM Anywhere is a part of EPAM Systems, Inc. Since 1993, EPAM Systems, Inc. (NYSE: EPAM) has leveraged its software engineering expertise to become a leading global product development, digital platform engineering, and top digital and product design agency. EPAM’s global teams serve customers in more than 35 countries across North America, Europe, Asia, and Australia.
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
- Java (CANONICAL) primary
- JDK (VERSION)
- JDK 10 (VERSION)
- JDK 11 (VERSION)
- JDK 12 (VERSION)
- JDK 13 (VERSION)
- JDK 14 (VERSION)
- JDK 15 (VERSION)
- JDK 16 (VERSION)
- JDK 17 (VERSION)
- JDK 18 (VERSION)
- JDK 19 (VERSION)
- JDK 20 (VERSION)
- JDK 21 (VERSION)
- JDK 5 (VERSION)
- JDK 6 (VERSION)
- JDK 7 (VERSION)
- JDK 8 (VERSION)
- JDK 9 (VERSION)
- Java 1.0 (VERSION)
- Java 1.1 (VERSION)
- Java 1.2 (VERSION)
- Java 1.3 (VERSION)
- Java 1.4 (VERSION)
- Java 1.5 (VERSION)
- Java 1.6 (VERSION)
- Java 1.7 (VERSION)
- Java 1.8 (VERSION)
- Java 10 (VERSION)
- Java 11 (VERSION)
- Java 12 (VERSION)
- Java 13 (VERSION)
- Java 14 (VERSION)
- Java 15 (VERSION)
- Java 16 (VERSION)
- Java 17 (VERSION)
- Java 18 (VERSION)
- Java 19 (VERSION)
- Java 20 (VERSION)
- Java 21 (VERSION)
- Java 5 (VERSION)
- Java 6 (VERSION)
- Java 7 (VERSION)
- Java 8 (VERSION)
- Java 9 (VERSION)
- Java11 (VERSION)
- Java17 (VERSION)
- Java21 (VERSION)
- Java8 (VERSION)
- OpenJDK 11 (VERSION)
- OpenJDK 17 (VERSION)
- OpenJDK 21 (VERSION)
- OpenJDK 8 (VERSION)
- java 11 (VERSION)
- java 17 (VERSION)
- java 21 (VERSION)
- java 4 (VERSION)
- java 5 (VERSION)
- java 6 (VERSION)
- java 7 (VERSION)
- java 8 (VERSION)
- java lts (VERSION)
- java-11 (VERSION)
- java-17 (VERSION)
- java-21 (VERSION)
- java-4 (VERSION)
- java-5 (VERSION)
- java-6 (VERSION)
- java-7 (VERSION)
- java-8 (VERSION)
- java11 (VERSION)
- java17 (VERSION)
- java21 (VERSION)
- java4 (VERSION)
- java5 (VERSION)
- java6 (VERSION)
- java7 (VERSION)
- java8 (VERSION)
- jdk 11 (VERSION)
- jdk 17 (VERSION)
- jdk 21 (VERSION)
- jdk 4 (VERSION)
- jdk 5 (VERSION)
- jdk 6 (VERSION)
- jdk 7 (VERSION)
- jdk 8 (VERSION)
- jdk11 (VERSION)
- jdk17 (VERSION)
- jdk21 (VERSION)
- jdk4 (VERSION)
- jdk5 (VERSION)
- jdk6 (VERSION)
- jdk7 (VERSION)
- jdk8 (VERSION)
- jvm21 (VERSION)
Context tags (catalog)
Stored enrichment (catalog DB)
- Category
- Language
- Sub-category
- Programming Language
- Vendor
- Oracle
- License
- other_open
- Year introduced
- 1995
- Confidence
- 0.99
- Version strategy
- SEPARATE_ENTITY
- Version tag
- 21
Maturity reasoning: Java is a hiring-pipeline staple with very high JD volume across enterprise backend, Android, and cloud roles; it remains widely supported by major vendors and frameworks like Spring.
Skill profile (library / DB)
- Skill nature
- LANGUAGE
- Volatility
- STABLE
- Typical lifespan
- EVERGREEN
- Category id
- 6
- Sub-category id
- 96
- Extractable
- True
- Also category
- False
Dimensions (API 2 worklist)
-
Java Language and JVM Catalog dimension db id 279
Library dimension (catalog)
Roles linked in library: Java Backend Developer, Kotlin Backend Developer, Scala Backend Developer
-
Kotlin and Java Catalog dimension db id 161
Library dimension (catalog)
Roles linked in library: Android Developer
-
Native Mobile Languages Catalog dimension db id 274
Library dimension (catalog)
Roles linked in library: Native Mobile Developer
-
Pega Programming Languages & DSLs Catalog dimension db id 267
Library dimension (catalog)
Roles linked in library: Pega Developer
-
Programming Languages Catalog dimension db id 1
Library dimension (catalog)
Roles linked in library: Backend Developer, Fullstack Developer, Fullstack Developer
-
Programming Languages for Data Work Catalog dimension db id 21
Library dimension (catalog)
Roles linked in library: Data Engineer
API 3 link attempts (this skill)
| Dimension | Skill↔dim | Role↔dim | Outcome |
|---|---|---|---|
|
Java Language and JVM
java-language-and-jvm
|
✓ | — | Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role) |
|
Kotlin and Java
kotlin-and-java
|
✓ | — | Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role) |
|
Native Mobile Languages
native-mobile-languages
|
✓ | — | Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role) |
|
Pega Programming Languages & DSLs
pega-programming-languages-dsls
|
✓ | — | Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role) |
|
Programming Languages
programming-languages
|
✓ | ✓ | 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) |
Aliases — catalog
- microservices (CANONICAL) primary
Context tags (catalog)
Stored enrichment (catalog DB)
- Category
- Architecture
- Sub-category
- Distributed System Architecture
- Confidence
- 0.99
- Version strategy
- NOT_APPLICABLE
Maturity reasoning: Microservices is a common architecture in job descriptions across backend/cloud roles, and major vendors like AWS, Google Cloud, and Kubernetes ecosystems provide first-class support and reference patterns.
Skill profile (library / DB)
- Skill nature
- PATTERN
- Volatility
- STABLE
- Typical lifespan
- EVERGREEN
- Category id
- 1
- Sub-category id
- 1
- Extractable
- True
- Also category
- False
Dimensions (API 2 worklist)
-
Microservices and Distributed Systems Catalog dimension db id 9
Library dimension (catalog)
Roles linked in library: Backend Developer, Node.js Backend Developer, Scala Backend Developer
API 3 link attempts (this skill)
| Dimension | Skill↔dim | Role↔dim | Outcome |
|---|---|---|---|
|
Microservices and Distributed Systems
microservices-and-distributed-systems
|
✓ | ✓ | Existing dimension (library) · Role↔dimension saved |
Aliases — catalog
- Git (CANONICAL)
Context tags (catalog)
Stored enrichment (catalog DB)
- Category
- Tool
- Sub-category
- Version Control Tool
- Vendor
- Linus Torvalds
- License
- gpl_v2
- Year introduced
- 2005
- Confidence
- 0.99
- Version strategy
- NOT_APPLICABLE
Maturity reasoning: Git is a hiring-pipeline staple: it appears in the vast majority of software engineering job descriptions and is the default VCS on GitHub/GitLab/Bitbucket.
Skill profile (library / DB)
- Skill nature
- TOOL
- Volatility
- STABLE
- Typical lifespan
- EVERGREEN
- Category id
- 13
- Sub-category id
- 730
- Extractable
- True
- Also category
- False
Dimensions (API 2 worklist)
-
React Frontend Development Catalog dimension db id 96
Library dimension (catalog)
API 3 link attempts (this skill)
| Dimension | Skill↔dim | Role↔dim | Outcome |
|---|---|---|---|
|
React Frontend Development
d_init_01
|
✓ | — | Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role) |
Aliases — catalog
- Agile (CANONICAL) primary
Context tags (catalog)
Stored enrichment (catalog DB)
- Category
- Methodology
- Sub-category
- Agile
- Confidence
- 0.99
- Version strategy
- NOT_APPLICABLE
Maturity reasoning: Agile appears in a large share of software job descriptions and is a standard hiring-pipeline requirement; Scrum/Kanban are commonly listed alongside it, showing broad market adoption.
Skill profile (library / DB)
- Skill nature
- METHODOLOGY
- Volatility
- STABLE
- Typical lifespan
- EVERGREEN
- Category id
- 8
- Sub-category id
- 367
- Extractable
- True
- Also category
- False
Dimensions (API 2 worklist)
-
React Frontend Development Catalog dimension db id 96
Library dimension (catalog)
API 3 link attempts (this skill)
| Dimension | Skill↔dim | Role↔dim | Outcome |
|---|---|---|---|
|
React Frontend Development
d_init_01
|
✓ | — | Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role) |
Aliases — catalog
- Docker (CANONICAL) primary
Context tags (catalog)
Stored enrichment (catalog DB)
- Category
- Tool
- Sub-category
- Containerization Tool
- Vendor
- Docker, Inc.
- License
- apache_2
- Year introduced
- 2013
- Confidence
- 0.98
- Version strategy
- NOT_APPLICABLE
Maturity reasoning: Docker is a hiring-pipeline staple: it appears in many DevOps, backend, and platform JDs, and remains a standard containerization tool alongside Kubernetes in production stacks.
Skill profile (library / DB)
- Skill nature
- TOOL
- Volatility
- STABLE
- Typical lifespan
- EVERGREEN
- Category id
- 13
- Sub-category id
- 63
- Extractable
- True
- Also category
- False
Dimensions (API 2 worklist)
-
Containerization and Image Builds Catalog dimension db id 152
Library dimension (catalog)
Roles linked in library: DevOps Engineer
-
Deployment and Cloud Platforms Catalog dimension db id 418
Library dimension (catalog)
Roles linked in library: Ruby Backend Developer
-
Deployment and Runtime Configuration Catalog dimension db id 13
Library dimension (catalog)
Roles linked in library: .NET Backend Developer, Backend Developer, Go Backend Developer, PHP Backend Developer
API 3 link attempts (this skill)
| Dimension | Skill↔dim | Role↔dim | Outcome |
|---|---|---|---|
|
Containerization and Image Builds
containerization-and-image-builds
|
✓ | — | Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role) |
|
Deployment and Cloud Platforms
deployment-and-cloud-platforms
|
✓ | — | Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role) |
|
Deployment and Runtime Configuration
deployment-and-runtime-configuration
|
✓ | ✓ | Existing dimension (library) · Role↔dimension saved |
Aliases — catalog
- Kubernetes (CANONICAL) primary
- Kubernetes 1.0+ (VERSION)
- Kubernetes 1.x (VERSION)
- Kubernetes v1 (VERSION)
- k8s (VERSION)
- kubernetes 1.x (VERSION)
- kubernetes latest (VERSION)
Context tags (catalog)
Stored enrichment (catalog DB)
- Category
- Platform
- Sub-category
- Container Orchestration Platform
- Vendor
- Cloud Native Computing Foundation
- License
- apache_2
- Year introduced
- 2014
- Confidence
- 0.90
- Version strategy
- SEPARATE_ENTITY
- Version tag
- 1.30
Maturity reasoning: Broadly adopted in cloud-native stacks; Kubernetes appears in a large share of DevOps/SRE job descriptions and is the default orchestration platform across major cloud vendors.
Skill profile (library / DB)
- Skill nature
- PLATFORM
- Volatility
- STABLE
- Typical lifespan
- EVERGREEN
- Category id
- 9
- Sub-category id
- 557
- Extractable
- True
- Also category
- False
Dimensions (API 2 worklist)
-
Container Orchestration Platforms Catalog dimension db id 134
Library dimension (catalog)
Roles linked in library: Cloud Architect, DevOps Engineer
-
Kubernetes for ML Workloads Catalog dimension db id 47
Library dimension (catalog)
Roles linked in library: ML Engineer, MLOps Engineer
API 3 link attempts (this skill)
| Dimension | Skill↔dim | Role↔dim | Outcome |
|---|---|---|---|
|
Container Orchestration Platforms
container-orchestration-platforms
|
✓ | — | Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role) |
|
Kubernetes for ML Workloads
kubernetes-for-ml-workloads
|
✓ | — | Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role) |
Aliases — catalog
- Spring (CANONICAL)
- Spring 4 (VERSION)
- Spring 4.x (VERSION)
- Spring 5 (VERSION)
- Spring 5.x (VERSION)
- Spring 6 (VERSION)
- Spring 6.x (VERSION)
- Spring Framework 4 (VERSION)
- Spring Framework 5 (VERSION)
- Spring Framework 6 (VERSION)
Context tags (catalog)
Stored enrichment (catalog DB)
- Category
- Framework
- Sub-category
- Java Application Framework
- Vendor
- Pivotal Software
- License
- apache_2
- Year introduced
- 2003
- Confidence
- 0.98
- Version strategy
- SEPARATE_ENTITY
- Version tag
- 6
Maturity reasoning: Spring is a hiring-pipeline staple in Java backend JDs across major job boards, and Spring Boot is the default framework in many enterprise and cloud-native stacks.
Skill profile (library / DB)
- Skill nature
- FRAMEWORK
- Volatility
- STABLE
- Typical lifespan
- EVERGREEN
- Category id
- 5
- Sub-category id
- 1228
- Extractable
- True
- Also category
- False
Dimensions (API 2 worklist)
-
Web Application Frameworks Catalog dimension db id 2
Library dimension (catalog)
Roles linked in library: Backend Developer, Fullstack Developer, Fullstack Developer, Java Backend Developer, Node.js Backend Developer, PHP Backend Developer, Python Backend Developer
API 3 link attempts (this skill)
| Dimension | Skill↔dim | Role↔dim | Outcome |
|---|---|---|---|
|
Web Application Frameworks
web-application-frameworks
|
✓ | ✓ | Existing dimension (library) · Role↔dimension saved |
Skill enrichment (orchestrator / LLM)
No Stage 7 enrichment blob on this skill (orchestrator skipped enrichment).
- Category
- Web Frameworks
- Sub-category
- general
- Skill nature
- TOOL
- Volatility
- MEDIUM
- Typical lifespan
- MULTI_YEAR
- Version strategy
- UNVERSIONED
Skill enrichment (orchestrator / LLM)
No Stage 7 enrichment blob on this skill (orchestrator skipped enrichment).
- Category
- Web Frameworks
- Sub-category
- general
- Skill nature
- TOOL
- Volatility
- MEDIUM
- Typical lifespan
- MULTI_YEAR
- Version strategy
- UNVERSIONED
Skill enrichment (orchestrator / LLM)
No Stage 7 enrichment blob on this skill (orchestrator skipped enrichment).
- Category
- Web Frameworks
- Sub-category
- general
- Skill nature
- TOOL
- Volatility
- MEDIUM
- Typical lifespan
- MULTI_YEAR
- Version strategy
- UNVERSIONED
Skill enrichment (orchestrator / LLM)
No Stage 7 enrichment blob on this skill (orchestrator skipped enrichment).
- Category
- Microservices
- Sub-category
- general
- Skill nature
- TOOL
- Volatility
- MEDIUM
- Typical lifespan
- MULTI_YEAR
- Version strategy
- UNVERSIONED
Skill enrichment (orchestrator / LLM)
No Stage 7 enrichment blob on this skill (orchestrator skipped enrichment).
- Category
- Monitoring Tools
- Sub-category
- general
- Skill nature
- TOOL
- Volatility
- MEDIUM
- Typical lifespan
- MULTI_YEAR
- Version strategy
- UNVERSIONED
Aliases — catalog
- PostgreSQL (CANONICAL) primary
- PG 13 (VERSION)
- PG 14 (VERSION)
- PG 15 (VERSION)
- PG 16 (VERSION)
- PostgreSQL 13 (VERSION)
- PostgreSQL 14 (VERSION)
- PostgreSQL 15 (VERSION)
- PostgreSQL 16 (VERSION)
- Postgres 13 (VERSION)
- Postgres 14 (VERSION)
- Postgres 15 (VERSION)
- Postgres 16 (VERSION)
- pg10 (VERSION)
- pg11 (VERSION)
- pg12 (VERSION)
- pg13 (VERSION)
- pg14 (VERSION)
- pg15 (VERSION)
- pg16 (VERSION)
- postgres (VERSION)
- postgresql 10 (VERSION)
- postgresql 11 (VERSION)
- postgresql 12 (VERSION)
- postgresql 13 (VERSION)
- postgresql 14 (VERSION)
- postgresql 15 (VERSION)
- postgresql 16 (VERSION)
- postgresql-16 (VERSION)
- postgresql10 (VERSION)
- postgresql11 (VERSION)
- postgresql12 (VERSION)
- postgresql13 (VERSION)
- postgresql14 (VERSION)
- postgresql15 (VERSION)
- postgresql16 (VERSION)
Context tags (catalog)
Stored enrichment (catalog DB)
- Category
- Datastore
- Sub-category
- Relational Database
- Vendor
- PostgreSQL Global Development Group
- License
- other_open
- Year introduced
- 1996
- Confidence
- 0.99
- Version strategy
- NOT_APPLICABLE
Maturity reasoning: PostgreSQL appears in a large share of backend/data engineering job postings and is a default managed option across AWS RDS, GCP Cloud SQL, and Azure Database, indicating broad hiring-pipeline adoption.
Skill profile (library / DB)
- Skill nature
- TOOL
- Volatility
- STABLE
- Typical lifespan
- EVERGREEN
- Category id
- 3
- Sub-category id
- 29
- Extractable
- True
- Also category
- False
Dimensions (API 2 worklist)
-
Relational Data Modeling Catalog dimension db id 216
Library dimension (catalog)
Roles linked in library: Fullstack Developer, Fullstack Developer, PHP Backend Developer
-
Relational Database Design Catalog dimension db id 4
Library dimension (catalog)
Roles linked in library: .NET Backend Developer, Backend Developer, Kotlin Backend Developer, Node.js Backend Developer, Python Backend Developer, Ruby Backend Developer, Scala Backend Developer
-
Relational Database Usage Catalog dimension db id 371
Library dimension (catalog)
Roles linked in library: Go Backend Developer
API 3 link attempts (this skill)
| Dimension | Skill↔dim | Role↔dim | Outcome |
|---|---|---|---|
|
Relational Data Modeling
relational-data-modeling
|
✓ | — | Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role) |
|
Relational Database Design
relational-database-design
|
✓ | ✓ | Existing dimension (library) · Role↔dimension saved |
|
Relational Database Usage
relational-database-usage
|
✓ | — | Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role) |
Aliases — catalog
- Prometheus (CANONICAL) primary
Context tags (catalog)
Stored enrichment (catalog DB)
- Category
- Platform
- Sub-category
- Monitoring Platform
- Vendor
- Cloud Native Computing Foundation
- License
- apache_2
- Year introduced
- 2012
- Confidence
- 0.62
- Version strategy
- NOT_APPLICABLE
Maturity reasoning: Prometheus is widely listed in DevOps/SRE job descriptions and is a standard CNCF monitoring stack component, often paired with Grafana for production observability.
Skill profile (library / DB)
- Skill nature
- PLATFORM
- Volatility
- STABLE
- Typical lifespan
- EVERGREEN
- Category id
- 9
- Sub-category id
- 2837
- Extractable
- True
- Also category
- False
Dimensions (API 2 worklist)
-
Backend Observability, Logging, and Diagnostics Catalog dimension db id 388
Library dimension (catalog)
Roles linked in library: Kotlin Backend Developer, Scala Backend Developer
-
Observability and Incident Response Catalog dimension db id 10
Library dimension (catalog)
Roles linked in library: .NET Backend Developer, Backend Developer, Node.js Backend Developer, PHP Backend Developer
-
Observability and Incident Triage Catalog dimension db id 155
Library dimension (catalog)
Roles linked in library: DevOps Engineer
-
Observability and Operations Catalog dimension db id 143
Library dimension (catalog)
Roles linked in library: Cloud Architect
API 3 link attempts (this skill)
| Dimension | Skill↔dim | Role↔dim | Outcome |
|---|---|---|---|
|
Backend Observability, Logging, and Diagnostics
backend-observability-logging-and-diagnostics
|
✓ | — | Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role) |
|
Observability and Incident Response
observability-and-incident-response
|
✓ | ✓ | Existing dimension (library) · Role↔dimension saved |
|
Observability and Incident Triage
observability-and-incident-triage
|
✓ | — | Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role) |
|
Observability and Operations
observability-and-operations
|
✓ | — | Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role) |
Skill enrichment (orchestrator / LLM)
No Stage 7 enrichment blob on this skill (orchestrator skipped enrichment).
- Category
- Monitoring Tools
- Sub-category
- general
- Skill nature
- TOOL
- Volatility
- MEDIUM
- Typical lifespan
- MULTI_YEAR
- Version strategy
- UNVERSIONED
Aliases — catalog
- Grafana (CANONICAL) primary
Context tags (catalog)
Stored enrichment (catalog DB)
- Category
- Platform
- Sub-category
- Observability Platform
- Vendor
- Grafana Labs
- License
- apache_2
- Year introduced
- 2014
- Confidence
- 0.90
- Version strategy
- NOT_APPLICABLE
Maturity reasoning: Grafana appears in many DevOps/SRE job descriptions and is a standard observability dashboarding tool alongside Prometheus and Loki; strong GitHub/community adoption and broad vendor integrations signal mainstream use.
Skill profile (library / DB)
- Skill nature
- PLATFORM
- Volatility
- STABLE
- Typical lifespan
- EVERGREEN
- Category id
- 9
- Sub-category id
- 176
- Extractable
- True
- Also category
- False
Dimensions (API 2 worklist)
-
Backend Observability, Logging, and Diagnostics Catalog dimension db id 388
Library dimension (catalog)
Roles linked in library: Kotlin Backend Developer, Scala Backend Developer
-
Observability and Incident Response Catalog dimension db id 10
Library dimension (catalog)
Roles linked in library: .NET Backend Developer, Backend Developer, Node.js Backend Developer, PHP Backend Developer
-
Observability and Incident Triage Catalog dimension db id 155
Library dimension (catalog)
Roles linked in library: DevOps Engineer
-
Observability and Operations Catalog dimension db id 143
Library dimension (catalog)
Roles linked in library: Cloud Architect
API 3 link attempts (this skill)
| Dimension | Skill↔dim | Role↔dim | Outcome |
|---|---|---|---|
|
Backend Observability, Logging, and Diagnostics
backend-observability-logging-and-diagnostics
|
✓ | — | Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role) |
|
Observability and Incident Response
observability-and-incident-response
|
✓ | ✓ | Existing dimension (library) · Role↔dimension saved |
|
Observability and Incident Triage
observability-and-incident-triage
|
✓ | — | Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role) |
|
Observability and Operations
observability-and-operations
|
✓ | — | Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role) |
Skill enrichment (orchestrator / LLM)
No Stage 7 enrichment blob on this skill (orchestrator skipped enrichment).
- Category
- Build Tools
- Sub-category
- general
- Skill nature
- TOOL
- Volatility
- MEDIUM
- Typical lifespan
- MULTI_YEAR
- Version strategy
- UNVERSIONED
Aliases — catalog
- Apache Kafka (CANONICAL) primary
Context tags (catalog)
Stored enrichment (catalog DB)
- Category
- Tool
- Sub-category
- Event Streaming Tool
- Vendor
- Apache Software Foundation
- License
- apache_2
- Year introduced
- 2011
- Confidence
- 0.90
- Version strategy
- NOT_APPLICABLE
Maturity reasoning: Apache Kafka is broadly adopted in production and appears frequently in job descriptions for event streaming, data pipelines, and microservices; it remains a common hiring-pipeline staple across backend and platform roles.
Skill profile (library / DB)
- Skill nature
- TOOL
- Volatility
- STABLE
- Typical lifespan
- EVERGREEN
- Category id
- 13
- Sub-category id
- 128
- Extractable
- True
- Also category
- False
Dimensions (API 2 worklist)
-
Messaging and Event Streaming Catalog dimension db id 8
Library dimension (catalog)
Roles linked in library: Backend Developer, Data 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 |
Skill enrichment (orchestrator / LLM)
No Stage 7 enrichment blob on this skill (orchestrator skipped enrichment).
- Category
- DevOps Tools
- Sub-category
- general
- Skill nature
- PRACTICE
- Volatility
- MEDIUM
- Typical lifespan
- MULTI_YEAR
- Version strategy
- UNVERSIONED
Skill enrichment (orchestrator / LLM)
No Stage 7 enrichment blob on this skill (orchestrator skipped enrichment).
- Category
- Software Development Practices
- Sub-category
- general
- Skill nature
- PRACTICE
- Volatility
- MEDIUM
- Typical lifespan
- MULTI_YEAR
- Version strategy
- UNVERSIONED
Aliases — catalog
- REST (CANONICAL) primary
Context tags (catalog)
Stored enrichment (catalog DB)
- Category
- Concept
- Sub-category
- Api Architecture Style
- Year introduced
- 2000
- Confidence
- 0.88
- Version strategy
- NOT_APPLICABLE
Maturity reasoning: REST is a default API architecture in many job descriptions and is widely supported by major vendors/frameworks; OpenAPI and RESTful endpoints remain standard in hiring pipelines.
Skill profile (library / DB)
- Skill nature
- CONCEPT
- Volatility
- STABLE
- Typical lifespan
- EVERGREEN
- Category id
- 2
- Sub-category id
- 2122
- Extractable
- True
- Also category
- False
Dimensions (API 2 worklist)
-
API Design and Contracts Catalog dimension db id 3
Library dimension (catalog)
Roles linked in library: Backend Developer, Fullstack Developer
-
API Interface and Contract Design Catalog dimension db id 289
Library dimension (catalog)
Roles linked in library: .NET Backend Developer, Go Backend Developer, Kotlin Backend Developer, Node.js Backend Developer, PHP Backend Developer, Python Backend Developer, Ruby Backend Developer, Scala Backend Developer
-
Integration Protocols & Standards Catalog dimension db id 271
Library dimension (catalog)
Roles linked in library: Pega Developer
-
Standards & Protocols Compliance Catalog dimension db id 452
Library dimension (catalog)
Roles linked in library: Sitecore Dev
API 3 link attempts (this skill)
| Dimension | Skill↔dim | Role↔dim | Outcome |
|---|---|---|---|
|
API Design and Contracts
api-design-and-contracts
|
✓ | ✓ | Existing dimension (library) · Role↔dimension saved |
|
API Interface and Contract Design
api-interface-and-contract-design
|
✓ | — | Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role) |
|
Integration Protocols & Standards
integration-protocols-standards
|
✓ | — | Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role) |
|
Standards & Protocols Compliance
standards-protocols-compliance
|
✓ | — | 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 |
|---|---|---|---|---|---|---|
| Java | in_db |
Java Language and JVM
java-language-and-jvm
|
✓ | — | Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role) | |
| Java | in_db |
Kotlin and Java
kotlin-and-java
|
✓ | — | Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role) | |
| Java | in_db |
Native Mobile Languages
native-mobile-languages
|
✓ | — | Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role) | |
| Java | in_db |
Pega Programming Languages & DSLs
pega-programming-languages-dsls
|
✓ | — | Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role) | |
| Java | in_db |
Programming Languages
programming-languages
|
✓ | ✓ | 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) | |
| Microservices | in_db |
Microservices and Distributed Systems
microservices-and-distributed-systems
|
✓ | ✓ | Existing dimension (library) · Role↔dimension saved | |
| Git | in_db |
React Frontend Development
d_init_01
|
✓ | — | Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role) | |
| Agile | in_db |
React Frontend Development
d_init_01
|
✓ | — | Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role) | |
| Docker | in_db |
Containerization and Image Builds
containerization-and-image-builds
|
✓ | — | Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role) | |
| Docker | in_db |
Deployment and Cloud Platforms
deployment-and-cloud-platforms
|
✓ | — | Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role) | |
| Docker | in_db |
Deployment and Runtime Configuration
deployment-and-runtime-configuration
|
✓ | ✓ | Existing dimension (library) · Role↔dimension saved | |
| Kubernetes | in_db |
Container Orchestration Platforms
container-orchestration-platforms
|
✓ | — | Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role) | |
| Kubernetes | in_db |
Kubernetes for ML Workloads
kubernetes-for-ml-workloads
|
✓ | — | Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role) | |
| Spring | in_db |
Web Application Frameworks
web-application-frameworks
|
✓ | ✓ | Existing dimension (library) · Role↔dimension saved | |
| PostgreSQL | in_db |
Relational Data Modeling
relational-data-modeling
|
✓ | — | Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role) | |
| PostgreSQL | in_db |
Relational Database Design
relational-database-design
|
✓ | ✓ | Existing dimension (library) · Role↔dimension saved | |
| PostgreSQL | in_db |
Relational Database Usage
relational-database-usage
|
✓ | — | Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role) | |
| Prometheus | in_db |
Backend Observability, Logging, and Diagnostics
backend-observability-logging-and-diagnostics
|
✓ | — | Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role) | |
| Prometheus | in_db |
Observability and Incident Response
observability-and-incident-response
|
✓ | ✓ | Existing dimension (library) · Role↔dimension saved | |
| Prometheus | in_db |
Observability and Incident Triage
observability-and-incident-triage
|
✓ | — | Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role) | |
| Prometheus | in_db |
Observability and Operations
observability-and-operations
|
✓ | — | Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role) | |
| Grafana | in_db |
Backend Observability, Logging, and Diagnostics
backend-observability-logging-and-diagnostics
|
✓ | — | Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role) | |
| Grafana | in_db |
Observability and Incident Response
observability-and-incident-response
|
✓ | ✓ | Existing dimension (library) · Role↔dimension saved | |
| Grafana | in_db |
Observability and Incident Triage
observability-and-incident-triage
|
✓ | — | Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role) | |
| Grafana | in_db |
Observability and Operations
observability-and-operations
|
✓ | — | Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role) | |
| Apache Kafka | in_db |
Messaging and Event Streaming
messaging-and-event-streaming
|
✓ | ✓ | Existing dimension (library) · Role↔dimension saved | |
| REST | in_db |
API Design and Contracts
api-design-and-contracts
|
✓ | ✓ | Existing dimension (library) · Role↔dimension saved | |
| REST | in_db |
API Interface and Contract Design
api-interface-and-contract-design
|
✓ | — | Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role) | |
| REST | in_db |
Integration Protocols & Standards
integration-protocols-standards
|
✓ | — | Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role) | |
| REST | in_db |
Standards & Protocols Compliance
standards-protocols-compliance
|
✓ | — | Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role) |
Library artifacts (this run)
| Kind | Detail | DB id |
|---|---|---|
| canonical_skill_proposed | Dropwizard | type=Web Frameworks subtype=general nature=TOOL lifespan=MULTI_YEAR | |
| canonical_skill_proposed | Jetty | type=Web Frameworks subtype=general nature=TOOL lifespan=MULTI_YEAR | |
| canonical_skill_proposed | Jersey | type=Web Frameworks subtype=general nature=TOOL lifespan=MULTI_YEAR | |
| canonical_skill_proposed | Netflix Hystrix | type=Microservices subtype=general nature=TOOL lifespan=MULTI_YEAR | |
| canonical_skill_proposed | Zipkin | type=Monitoring Tools subtype=general nature=TOOL lifespan=MULTI_YEAR | |
| canonical_skill_proposed | Kibana | type=Monitoring Tools subtype=general nature=TOOL lifespan=MULTI_YEAR | |
| canonical_skill_proposed | Apache Maven | type=Build Tools subtype=general nature=TOOL lifespan=MULTI_YEAR | |
| canonical_skill_proposed | Continuous Delivery | type=DevOps Tools subtype=general nature=PRACTICE lifespan=MULTI_YEAR | |
| canonical_skill_proposed | BDD | type=Software Development Practices subtype=general nature=PRACTICE lifespan=MULTI_YEAR |
nano JD Parser — gpt-4.1-nano click to toggle
Show raw JSON
{
"JD_type": "pass",
"about_company": {
"source_marker": {
"first_5_words": "EPAM Anywhere is a part",
"last_5_words": "North America, Europe, Asia, and Australia."
},
"text": "EPAM Anywhere is a part of EPAM Systems, Inc. Since 1993, EPAM Systems, Inc. (NYSE: EPAM) has leveraged its software engineering expertise to become a leading global product development, digital platform engineering, and top digital and product design agency. EPAM\u2019s global teams serve customers in more than 35 countries across North America, Europe, Asia, and Australia.",
"word_count": 64
},
"certifications": [],
"company_name": "EPAM Systems, Inc.",
"ctc": null,
"domain": {
"primary": {
"aliases": [
"ITES",
"BPO",
"Tech Consulting"
],
"domain": "IT Services \u0026 Consulting"
},
"secondary": null
},
"education": [],
"experience": {
"max": null,
"min": 3,
"raw": "3+ years of experience working with Java8+"
},
"job_locations": [
{
"aliases": [],
"city": null,
"country": "India",
"state": null,
"work_mode": "remote"
}
],
"role": "Senior Java Software Engineer",
"role_aliases": [
"Java Developer",
"Java Engineer",
"Software Engineer"
],
"role_archetype": "Engineering",
"roles_and_responsibilities": [
{
"bullet_count": 6,
"heading": "Responsibilities",
"heading_was_present": true,
"source_marker": {
"first_5_words": "Develop MicroservicesParticipate in planning",
"last_5_words": "unit and some integration tests"
},
"text": "Develop Microservices\nParticipate in planning and management of the development process\nActively communicate with the stakeholders\nContribute to continuous delivery and integration pipeline infrastructure\nImplement technical decisions with little supervision\nWrite unit and some integration tests",
"word_count": 36
},
{
"bullet_count": 7,
"heading": "Requirements",
"heading_was_present": true,
"source_marker": {
"first_5_words": "3+ years of experience working",
"last_5_words": "or higher"
},
"text": "3+ years of experience working with Java8+\nBackground in SDLC, including coding standards, code reviews, source control management (Git), Agile development, build processes, testing and operations\nUnderstanding of Microservice architectures, RESTful API design\nKnowledge of Docker containers and container orchestration systems like Kubernetes or Amazon EKS\nExperience with Java DI and IoC frameworks: Dropwizard, Spring or others\nGood communication and problem-solving skills\nEnglish B2 or higher",
"word_count": 66
},
{
"bullet_count": 2,
"heading": "Nice to have",
"heading_was_present": true,
"source_marker": {
"first_5_words": "Kafka knowledgeExperience with legacy",
"last_5_words": "and phased application integration"
},
"text": "Kafka knowledge\nExperience with legacy system integration and phased application integration",
"word_count": 14
},
{
"bullet_count": 15,
"heading": "Technologies",
"heading_was_present": true,
"source_marker": {
"first_5_words": "MicroservicesDropwizardJettyJerseyNetflix",
"last_5_words": "approach"
},
"text": "Microservices\nDropwizard\nJetty\nJersey\nNetflix Hystrix\nZipkin\nPostgreSQL\nPrometheus\nDocker\nKubernetes\nKibana\nGrafana\nGit\nApache Maven\nApache Kafka\nContinuous Delivery approach\nBDD approach",
"word_count": 16
}
],
"urls": [
{
"type": "website",
"url": "https://anywhere.epam.com"
}
]
}
API 1 — extract-from-jd click to toggle
{
"final_skills": [
{
"is_primary": true,
"skill_name": "Java"
},
{
"is_primary": true,
"skill_name": "Microservices"
},
{
"is_primary": true,
"skill_name": "Git"
},
{
"is_primary": true,
"skill_name": "Agile"
},
{
"is_primary": true,
"skill_name": "Docker"
},
{
"is_primary": true,
"skill_name": "Kubernetes"
},
{
"is_primary": false,
"skill_name": "Spring"
},
{
"is_primary": false,
"skill_name": "Dropwizard"
},
{
"is_primary": false,
"skill_name": "Jetty"
},
{
"is_primary": false,
"skill_name": "Jersey"
},
{
"is_primary": false,
"skill_name": "Netflix Hystrix"
},
{
"is_primary": false,
"skill_name": "Zipkin"
},
{
"is_primary": false,
"skill_name": "PostgreSQL"
},
{
"is_primary": false,
"skill_name": "Prometheus"
},
{
"is_primary": false,
"skill_name": "Kibana"
},
{
"is_primary": false,
"skill_name": "Grafana"
},
{
"is_primary": false,
"skill_name": "Apache Maven"
},
{
"is_primary": false,
"skill_name": "Apache Kafka"
},
{
"is_primary": false,
"skill_name": "Continuous Delivery"
},
{
"is_primary": false,
"skill_name": "BDD"
},
{
"is_primary": true,
"skill_name": "REST"
}
],
"jd_role": {
"display_name": "Senior Java Software Engineer",
"rationale": null,
"role_aliases": [
"Java Developer",
"Java Engineer",
"Software Engineer"
],
"role_archetype": "Engineering",
"slug": ""
},
"nano_parsed": {
"JD_type": "pass",
"about_company": {
"source_marker": {
"first_5_words": "EPAM Anywhere is a part",
"last_5_words": "North America, Europe, Asia, and Australia."
},
"text": "EPAM Anywhere is a part of EPAM Systems, Inc. Since 1993, EPAM Systems, Inc. (NYSE: EPAM) has leveraged its software engineering expertise to become a leading global product development, digital platform engineering, and top digital and product design agency. EPAM\u2019s global teams serve customers in more than 35 countries across North America, Europe, Asia, and Australia.",
"word_count": 64
},
"certifications": [],
"company_name": "EPAM Systems, Inc.",
"ctc": null,
"domain": {
"primary": {
"aliases": [
"ITES",
"BPO",
"Tech Consulting"
],
"domain": "IT Services \u0026 Consulting"
},
"secondary": null
},
"education": [],
"experience": {
"max": null,
"min": 3,
"raw": "3+ years of experience working with Java8+"
},
"job_locations": [
{
"aliases": [],
"city": null,
"country": "India",
"state": null,
"work_mode": "remote"
}
],
"role": "Senior Java Software Engineer",
"role_aliases": [
"Java Developer",
"Java Engineer",
"Software Engineer"
],
"role_archetype": "Engineering",
"roles_and_responsibilities": [
{
"bullet_count": 6,
"heading": "Responsibilities",
"heading_was_present": true,
"source_marker": {
"first_5_words": "Develop MicroservicesParticipate in planning",
"last_5_words": "unit and some integration tests"
},
"text": "Develop Microservices\nParticipate in planning and management of the development process\nActively communicate with the stakeholders\nContribute to continuous delivery and integration pipeline infrastructure\nImplement technical decisions with little supervision\nWrite unit and some integration tests",
"word_count": 36
},
{
"bullet_count": 7,
"heading": "Requirements",
"heading_was_present": true,
"source_marker": {
"first_5_words": "3+ years of experience working",
"last_5_words": "or higher"
},
"text": "3+ years of experience working with Java8+\nBackground in SDLC, including coding standards, code reviews, source control management (Git), Agile development, build processes, testing and operations\nUnderstanding of Microservice architectures, RESTful API design\nKnowledge of Docker containers and container orchestration systems like Kubernetes or Amazon EKS\nExperience with Java DI and IoC frameworks: Dropwizard, Spring or others\nGood communication and problem-solving skills\nEnglish B2 or higher",
"word_count": 66
},
{
"bullet_count": 2,
"heading": "Nice to have",
"heading_was_present": true,
"source_marker": {
"first_5_words": "Kafka knowledgeExperience with legacy",
"last_5_words": "and phased application integration"
},
"text": "Kafka knowledge\nExperience with legacy system integration and phased application integration",
"word_count": 14
},
{
"bullet_count": 15,
"heading": "Technologies",
"heading_was_present": true,
"source_marker": {
"first_5_words": "MicroservicesDropwizardJettyJerseyNetflix",
"last_5_words": "approach"
},
"text": "Microservices\nDropwizard\nJetty\nJersey\nNetflix Hystrix\nZipkin\nPostgreSQL\nPrometheus\nDocker\nKubernetes\nKibana\nGrafana\nGit\nApache Maven\nApache Kafka\nContinuous Delivery approach\nBDD approach",
"word_count": 16
}
],
"urls": [
{
"type": "website",
"url": "https://anywhere.epam.com"
}
]
},
"rejected": false,
"rejection_reason": null,
"run_id": "14665224-3376-48b7-92b4-7aed97ed2be8",
"stage3_signals": {
"alias_found": true,
"alias_match_roles": [
{
"display_name": "Backend Developer",
"kra_matches": null,
"matched_count": null,
"matched_skills": null,
"role_id": 1,
"score": 1.0,
"slug": "backend-engineer",
"total_count": null
},
{
"display_name": "Java Backend Developer",
"kra_matches": null,
"matched_count": null,
"matched_skills": null,
"role_id": 79,
"score": 1.0,
"slug": "java-backend-developer",
"total_count": null
}
],
"kra_match_roles": [
{
"display_name": "DevOps Engineer",
"kra_matches": [
{
"kra_text": "Monitors CI/CD pipeline reliability, identifies bottlenecks in delivery workflows, and improves deployment frequency, lead time, and failure recovery rate.",
"sentence": "Contribute to continuous delivery and integration pipeline infrastructure",
"similarity": 0.6245
},
{
"kra_text": "Collaborates with development teams to improve build processes, reduce deployment friction, containerize applications, and adopt DevOps best practices.",
"sentence": "Background in SDLC, including coding standards, code reviews, source control management (Git), Agile development, build processes, testing and operations",
"similarity": 0.5239
},
{
"kra_text": "Collaborates with development teams to improve build processes, reduce deployment friction, containerize applications, and adopt DevOps best practices.",
"sentence": "Participate in planning and management of the development process",
"similarity": 0.5021
}
],
"matched_count": null,
"matched_skills": null,
"role_id": 10,
"score": 0.5502,
"slug": "devops-engineer",
"total_count": null
},
{
"display_name": "Fullstack Developer",
"kra_matches": [
{
"kra_text": "Delivers features through CI/CD pipelines using automated tests, staged rollouts, feature flags, and incremental deployments.",
"sentence": "Contribute to continuous delivery and integration pipeline infrastructure",
"similarity": 0.5999
},
{
"kra_text": "Works closely with product managers and UX designers to translate requirements and wireframes into working software features through iterative development.",
"sentence": "Participate in planning and management of the development process",
"similarity": 0.5124
},
{
"kra_text": "Delivers features through CI/CD pipelines using automated tests, staged rollouts, feature flags, and incremental deployments.",
"sentence": "Background in SDLC, including coding standards, code reviews, source control management (Git), Agile development, build processes, testing and operations",
"similarity": 0.4534
}
],
"matched_count": null,
"matched_skills": null,
"role_id": 15,
"score": 0.5219,
"slug": "full-stack-engineer",
"total_count": null
},
{
"display_name": "Backend Developer",
"kra_matches": [
{
"kra_text": "Configures Docker containers, deployment descriptors, environment variables, and CI/CD pipeline stages for backend service releases.",
"sentence": "Contribute to continuous delivery and integration pipeline infrastructure",
"similarity": 0.5319
},
{
"kra_text": "Designs and maintains RESTful and GraphQL API interfaces with proper authentication, versioning, rate limiting, and documentation for frontend and third-party consumers.",
"sentence": "Understanding of Microservice architectures, RESTful API design",
"similarity": 0.5195
},
{
"kra_text": "Configures Docker containers, deployment descriptors, environment variables, and CI/CD pipeline stages for backend service releases.",
"sentence": "Background in SDLC, including coding standards, code reviews, source control management (Git), Agile development, build processes, testing and operations",
"similarity": 0.4695
}
],
"matched_count": null,
"matched_skills": null,
"role_id": 1,
"score": 0.507,
"slug": "backend-engineer",
"total_count": null
},
{
"display_name": "Node.js Backend Developer",
"kra_matches": [
{
"kra_text": "API design and request handling",
"sentence": "Understanding of Microservice architectures, RESTful API design",
"similarity": 0.5061
},
{
"kra_text": "code review and refactoring",
"sentence": "Background in SDLC, including coding standards, code reviews, source control management (Git), Agile development, build processes, testing and operations",
"similarity": 0.4417
},
{
"kra_text": "automated backend checks",
"sentence": "Contribute to continuous delivery and integration pipeline infrastructure",
"similarity": 0.4057
}
],
"matched_count": null,
"matched_skills": null,
"role_id": 82,
"score": 0.4512,
"slug": "node-backend-developer",
"total_count": null
},
{
"display_name": "Flutter Developer",
"kra_matches": [
{
"kra_text": "collaborate with design, product, and backend teams",
"sentence": "Participate in planning and management of the development process",
"similarity": 0.5132
},
{
"kra_text": "integrate external APIs and data sources",
"sentence": "Contribute to continuous delivery and integration pipeline infrastructure",
"similarity": 0.4395
},
{
"kra_text": "collaborate with design, product, and backend teams",
"sentence": "Background in SDLC, including coding standards, code reviews, source control management (Git), Agile development, build processes, testing and operations",
"similarity": 0.3977
}
],
"matched_count": null,
"matched_skills": null,
"role_id": 74,
"score": 0.4501,
"slug": "flutter-developer",
"total_count": null
}
],
"skill_match_roles": [
{
"display_name": "Backend Developer",
"kra_matches": null,
"matched_count": 4,
"matched_skills": [
"Docker",
"Java",
"REST",
"microservices"
],
"role_id": 1,
"score": 0.5714,
"slug": "backend-engineer",
"total_count": 7
},
{
"display_name": "Scala Backend Developer",
"kra_matches": null,
"matched_count": 3,
"matched_skills": [
"Java",
"REST",
"microservices"
],
"role_id": 87,
"score": 0.4286,
"slug": "scala-backend-developer",
"total_count": 7
},
{
"display_name": "Fullstack Developer",
"kra_matches": null,
"matched_count": 2,
"matched_skills": [
"Java",
"REST"
],
"role_id": 15,
"score": 0.2857,
"slug": "full-stack-engineer",
"total_count": 7
},
{
"display_name": "Pega Developer",
"kra_matches": null,
"matched_count": 2,
"matched_skills": [
"Java",
"REST"
],
"role_id": 24,
"score": 0.2857,
"slug": "pega-developer",
"total_count": 7
},
{
"display_name": "DevOps Engineer",
"kra_matches": null,
"matched_count": 2,
"matched_skills": [
"Docker",
"Kubernetes"
],
"role_id": 10,
"score": 0.2857,
"slug": "devops-engineer",
"total_count": 7
}
]
},
"stage4_decision": {
"alias_collision_detected": false,
"case": "DOMAIN",
"chosen_role": {
"display_name": "Backend Developer",
"kra_matches": null,
"matched_count": null,
"matched_skills": null,
"role_id": 1,
"score": 0.98,
"slug": "backend-engineer",
"total_count": null
},
"confidence": 0.98,
"is_new_role": false,
"llm2_fired": false,
"llm2_reasoning": null,
"matched_dimensions": [
"Backend Microservices Development",
"RESTful API Design",
"Continuous Integration and Delivery",
"Containerized Deployment",
"Legacy System Integration",
"Agile SDLC Collaboration",
"Testing and Quality Engineering"
],
"matched_kras": [
"Develop Microservices",
"Participate in planning and management of the development process",
"Actively communicate with the stakeholders",
"Contribute to continuous delivery and integration pipeline infrastructure",
"Implement technical decisions with little supervision",
"Write unit and some integration tests",
"Experience with legacy system integration and phased application integration"
],
"matched_skills": [
"Java8+",
"Microservices",
"Dropwizard",
"Jetty",
"Jersey",
"Netflix Hystrix",
"Zipkin",
"PostgreSQL",
"Prometheus",
"Docker",
"Kubernetes",
"Amazon EKS",
"Git",
"Apache Maven",
"Apache Kafka"
],
"new_role_display_name": null,
"new_role_slug": null,
"queued": false,
"reasoning": "Domain=Software Engineering \u2192 sub-role java-backend-developer; The JD is centered on Java microservices, REST APIs, CI/CD, Docker/Kubernetes, and backend integration work, which best matches Backend Developer.",
"sub_role": {
"confidence": 0.99,
"display_name": "Java Backend Developer",
"reasoning": "The JD is explicitly centered on Java 8+, Spring/Dropwizard, Maven, and Java microservice backend work, so Java Backend Developer is the clear match.",
"role_id": 79,
"slug": "java-backend-developer"
}
},
"stage5_updates": {
"centroid_n_after": 658,
"centroid_updated": true,
"collision_log_id": null,
"new_kra_attached": null,
"new_skills_attached": [
{
"is_primary": false,
"queue_id": 10810,
"role_display_name": "Backend Developer",
"role_slug": "backend-engineer",
"skill_name": "Dropwizard",
"status": "pending"
},
{
"is_primary": false,
"queue_id": 10811,
"role_display_name": "Backend Developer",
"role_slug": "backend-engineer",
"skill_name": "Jetty",
"status": "pending"
},
{
"is_primary": false,
"queue_id": 10812,
"role_display_name": "Backend Developer",
"role_slug": "backend-engineer",
"skill_name": "Jersey",
"status": "pending"
},
{
"is_primary": false,
"queue_id": 10813,
"role_display_name": "Backend Developer",
"role_slug": "backend-engineer",
"skill_name": "Netflix Hystrix",
"status": "pending"
},
{
"is_primary": false,
"queue_id": 10814,
"role_display_name": "Backend Developer",
"role_slug": "backend-engineer",
"skill_name": "Zipkin",
"status": "pending"
},
{
"is_primary": false,
"queue_id": 10815,
"role_display_name": "Backend Developer",
"role_slug": "backend-engineer",
"skill_name": "Kibana",
"status": "pending"
},
{
"is_primary": false,
"queue_id": 10816,
"role_display_name": "Backend Developer",
"role_slug": "backend-engineer",
"skill_name": "Apache Maven",
"status": "pending"
},
{
"is_primary": false,
"queue_id": 10817,
"role_display_name": "Backend Developer",
"role_slug": "backend-engineer",
"skill_name": "Continuous Delivery",
"status": "pending"
},
{
"is_primary": false,
"queue_id": 10818,
"role_display_name": "Backend Developer",
"role_slug": "backend-engineer",
"skill_name": "BDD",
"status": "pending"
}
],
"queue_entry_id": null,
"v3_pipeline_triggered": false,
"v3_role_slug": null,
"v3_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": 1,
"existing_alias_text": "Java",
"input_term": "Java",
"matched_canonical": {
"category_id": 6,
"display_name": "Java",
"id": 1,
"is_also_category": false,
"is_extractable": true,
"skill_nature": "LANGUAGE",
"slug": "java",
"sub_category_id": 96,
"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": 178,
"existing_alias_text": "microservices",
"input_term": "Microservices",
"matched_canonical": {
"category_id": 1,
"display_name": "microservices",
"id": 41,
"is_also_category": false,
"is_extractable": true,
"skill_nature": "PATTERN",
"slug": "microservices",
"sub_category_id": 1,
"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": 1613,
"existing_alias_text": "Git",
"input_term": "Git",
"matched_canonical": {
"category_id": 13,
"display_name": "Git",
"id": 1002,
"is_also_category": false,
"is_extractable": true,
"skill_nature": "TOOL",
"slug": "git",
"sub_category_id": 730,
"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": 868,
"existing_alias_text": "Agile",
"input_term": "Agile",
"matched_canonical": {
"category_id": 8,
"display_name": "Agile",
"id": 520,
"is_also_category": false,
"is_extractable": true,
"skill_nature": "METHODOLOGY",
"slug": "agile",
"sub_category_id": 367,
"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": 198,
"existing_alias_text": "Docker",
"input_term": "Docker",
"matched_canonical": {
"category_id": 13,
"display_name": "Docker",
"id": 61,
"is_also_category": false,
"is_extractable": true,
"skill_nature": "TOOL",
"slug": "docker",
"sub_category_id": 63,
"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": 1267,
"existing_alias_text": "Kubernetes",
"input_term": "Kubernetes",
"matched_canonical": {
"category_id": 9,
"display_name": "Kubernetes",
"id": 726,
"is_also_category": false,
"is_extractable": true,
"skill_nature": "PLATFORM",
"slug": "kubernetes",
"sub_category_id": 557,
"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": 2585,
"existing_alias_text": "Spring",
"input_term": "Spring",
"matched_canonical": {
"category_id": 5,
"display_name": "Spring",
"id": 1630,
"is_also_category": false,
"is_extractable": true,
"skill_nature": "FRAMEWORK",
"slug": "spring",
"sub_category_id": 1228,
"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": 121,
"existing_alias_text": "PostgreSQL",
"input_term": "PostgreSQL",
"matched_canonical": {
"category_id": 3,
"display_name": "PostgreSQL",
"id": 16,
"is_also_category": false,
"is_extractable": true,
"skill_nature": "TOOL",
"slug": "postgresql",
"sub_category_id": 29,
"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": 183,
"existing_alias_text": "Prometheus",
"input_term": "Prometheus",
"matched_canonical": {
"category_id": 9,
"display_name": "Prometheus",
"id": 46,
"is_also_category": false,
"is_extractable": true,
"skill_nature": "PLATFORM",
"slug": "prometheus",
"sub_category_id": 2837,
"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": 184,
"existing_alias_text": "Grafana",
"input_term": "Grafana",
"matched_canonical": {
"category_id": 9,
"display_name": "Grafana",
"id": 47,
"is_also_category": false,
"is_extractable": true,
"skill_nature": "PLATFORM",
"slug": "grafana",
"sub_category_id": 176,
"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": "Apache Kafka",
"input_term": "Apache Kafka",
"matched_canonical": {
"category_id": 13,
"display_name": "Apache Kafka",
"id": 145,
"is_also_category": false,
"is_extractable": true,
"skill_nature": "TOOL",
"slug": "apache-kafka",
"sub_category_id": 128,
"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": 106,
"existing_alias_text": "REST",
"input_term": "REST",
"matched_canonical": {
"category_id": 2,
"display_name": "REST",
"id": 11,
"is_also_category": false,
"is_extractable": true,
"skill_nature": "CONCEPT",
"slug": "rest",
"sub_category_id": 2122,
"typical_lifespan": "EVERGREEN",
"volatility": "STABLE"
},
"matched_via": "alias"
}
],
"candidate_roles": [
{
"display_name": "Java Backend Developer",
"id": 79,
"rationale": null,
"role_archetype": "Engineering",
"slug": "java-backend-developer",
"source": "db"
},
{
"display_name": "Kotlin Backend Developer",
"id": 84,
"rationale": null,
"role_archetype": "Engineering",
"slug": "kotlin-server-backend-developer",
"source": "db"
},
{
"display_name": "Scala Backend Developer",
"id": 87,
"rationale": null,
"role_archetype": "Engineering",
"slug": "scala-backend-developer",
"source": "db"
},
{
"display_name": "Android Developer",
"id": 4,
"rationale": null,
"role_archetype": null,
"slug": "android-engineer",
"source": "db"
},
{
"display_name": "Native Mobile Developer",
"id": 75,
"rationale": null,
"role_archetype": "Engineering",
"slug": "native-mobile-developer",
"source": "db"
},
{
"display_name": "Pega Developer",
"id": 24,
"rationale": null,
"role_archetype": null,
"slug": "pega-developer",
"source": "db"
},
{
"display_name": "Backend Developer",
"id": 1,
"rationale": null,
"role_archetype": "A Backend Engineer designs, builds, and maintains the server-side logic and data handling that power applications and services. They focus on implementing reliable business functionality, integrating with other systems, and ensuring the backend is scalable, maintainable, and observable.",
"slug": "backend-engineer",
"source": "db"
},
{
"display_name": "Fullstack Developer",
"id": 435,
"rationale": null,
"role_archetype": "Engineering",
"slug": "fullstack-developer",
"source": "db"
},
{
"display_name": "Fullstack Developer",
"id": 15,
"rationale": null,
"role_archetype": null,
"slug": "full-stack-engineer",
"source": "db"
},
{
"display_name": "Data Engineer",
"id": 2,
"rationale": null,
"role_archetype": null,
"slug": "data-engineer",
"source": "db"
},
{
"display_name": "Node.js Backend Developer",
"id": 82,
"rationale": null,
"role_archetype": "Engineering",
"slug": "node-backend-developer",
"source": "db"
},
{
"display_name": "DevOps Engineer",
"id": 10,
"rationale": null,
"role_archetype": null,
"slug": "devops-engineer",
"source": "db"
},
{
"display_name": "Ruby Backend Developer",
"id": 85,
"rationale": null,
"role_archetype": "Engineering",
"slug": "ruby-backend-developer",
"source": "db"
},
{
"display_name": ".NET Backend Developer",
"id": 83,
"rationale": null,
"role_archetype": "Engineering",
"slug": "dotnet-backend-developer",
"source": "db"
},
{
"display_name": "Go Backend Developer",
"id": 81,
"rationale": null,
"role_archetype": "Engineering",
"slug": "go-backend-developer",
"source": "db"
},
{
"display_name": "PHP Backend Developer",
"id": 86,
"rationale": null,
"role_archetype": "Engineering",
"slug": "php-backend-developer",
"source": "db"
},
{
"display_name": "Cloud Architect",
"id": 9,
"rationale": null,
"role_archetype": null,
"slug": "cloud-architect",
"source": "db"
},
{
"display_name": "ML Engineer",
"id": 3,
"rationale": null,
"role_archetype": null,
"slug": "ml-engineer",
"source": "db"
},
{
"display_name": "MLOps Engineer",
"id": 16,
"rationale": null,
"role_archetype": null,
"slug": "ml-ops-engineer",
"source": "db"
},
{
"display_name": "Python Backend Developer",
"id": 80,
"rationale": null,
"role_archetype": "Engineering",
"slug": "python-backend-developer",
"source": "db"
},
{
"display_name": "Sitecore Dev",
"id": 233,
"rationale": null,
"role_archetype": "Engineering",
"slug": "sitecore-dev",
"source": "db"
}
],
"chosen_role": {
"display_name": "Backend Developer",
"id": 1,
"rationale": "Domain=Software Engineering \u2192 sub-role java-backend-developer; The JD is centered on Java microservices, REST APIs, CI/CD, Docker/Kubernetes, and backend integration work, which best matches Backend Developer.",
"role_archetype": "A Backend Engineer designs, builds, and maintains the server-side logic and data handling that power applications and services. They focus on implementing reliable business functionality, integrating with other systems, and ensuring the backend is scalable, maintainable, and observable.",
"slug": "backend-engineer",
"source": "db"
},
"dimensions": [
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Java Language and JVM",
"id": 279,
"rationale": "Core Java implementation skills used to build backend service logic, utilities, and internal abstractions. This is the primary coding surface for the role and includes language features plus JVM behavior that affect correctness and maintainability.",
"slug": "java-language-and-jvm",
"source": "db"
},
"input_skill": "Java",
"llm_role": null,
"roles_from_db": [
{
"display_name": "Java Backend Developer",
"id": 79,
"rationale": null,
"role_archetype": "Engineering",
"slug": "java-backend-developer",
"source": "db"
},
{
"display_name": "Kotlin Backend Developer",
"id": 84,
"rationale": null,
"role_archetype": "Engineering",
"slug": "kotlin-server-backend-developer",
"source": "db"
},
{
"display_name": "Scala Backend Developer",
"id": 87,
"rationale": null,
"role_archetype": "Engineering",
"slug": "scala-backend-developer",
"source": "db"
}
]
},
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Kotlin and Java",
"id": 161,
"rationale": "Primary implementation languages for Android app features, platform integration, and client-side business logic. Android engineers use these languages to build screens, state flows, service adapters, and device-aware behavior.",
"slug": "kotlin-and-java",
"source": "db"
},
"input_skill": "Java",
"llm_role": null,
"roles_from_db": [
{
"display_name": "Android Developer",
"id": 4,
"rationale": null,
"role_archetype": null,
"slug": "android-engineer",
"source": "db"
}
]
},
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Native Mobile Languages",
"id": 274,
"rationale": "Primary implementation languages used to build platform-specific app features, UI logic, and device integrations. This is the core coding surface for native mobile work on one platform.",
"slug": "native-mobile-languages",
"source": "db"
},
"input_skill": "Java",
"llm_role": null,
"roles_from_db": [
{
"display_name": "Native Mobile Developer",
"id": 75,
"rationale": null,
"role_archetype": "Engineering",
"slug": "native-mobile-developer",
"source": "db"
}
]
},
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Pega Programming Languages \u0026 DSLs",
"id": 267,
"rationale": "Programming languages and domain-specific languages used in Pega development.",
"slug": "pega-programming-languages-dsls",
"source": "db"
},
"input_skill": "Java",
"llm_role": null,
"roles_from_db": [
{
"display_name": "Pega Developer",
"id": 24,
"rationale": null,
"role_archetype": null,
"slug": "pega-developer",
"source": "db"
}
]
},
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Programming Languages",
"id": 1,
"rationale": "Primary implementation languages used to build client and server feature code. Full stack engineers need enough fluency to move across layers and implement product behavior end to end.",
"slug": "programming-languages",
"source": "db"
},
"input_skill": "Java",
"llm_role": null,
"roles_from_db": [
{
"display_name": "Backend Developer",
"id": 1,
"rationale": null,
"role_archetype": "A Backend Engineer designs, builds, and maintains the server-side logic and data handling that power applications and services. They focus on implementing reliable business functionality, integrating with other systems, and ensuring the backend is scalable, maintainable, and observable.",
"slug": "backend-engineer",
"source": "db"
},
{
"display_name": "Fullstack Developer",
"id": 435,
"rationale": null,
"role_archetype": "Engineering",
"slug": "fullstack-developer",
"source": "db"
},
{
"display_name": "Fullstack Developer",
"id": 15,
"rationale": null,
"role_archetype": null,
"slug": "full-stack-engineer",
"source": "db"
}
]
},
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Programming Languages for Data Work",
"id": 21,
"rationale": "Languages used to implement data pipelines, transformations, and operational glue. This is the primary coding surface for building ingestion, enrichment, and automation logic in data engineering.",
"slug": "programming-languages-for-data-work",
"source": "db"
},
"input_skill": "Java",
"llm_role": null,
"roles_from_db": [
{
"display_name": "Data Engineer",
"id": 2,
"rationale": null,
"role_archetype": null,
"slug": "data-engineer",
"source": "db"
}
]
},
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Microservices and Distributed Systems",
"id": 9,
"rationale": "Architectural patterns for decomposed backend systems and the operational concerns they introduce. Covers service boundaries, consistency tradeoffs, retries, circuit breakers, and distributed coordination.",
"slug": "microservices-and-distributed-systems",
"source": "db"
},
"input_skill": "Microservices",
"llm_role": null,
"roles_from_db": [
{
"display_name": "Backend Developer",
"id": 1,
"rationale": null,
"role_archetype": "A Backend Engineer designs, builds, and maintains the server-side logic and data handling that power applications and services. They focus on implementing reliable business functionality, integrating with other systems, and ensuring the backend is scalable, maintainable, and observable.",
"slug": "backend-engineer",
"source": "db"
},
{
"display_name": "Node.js Backend Developer",
"id": 82,
"rationale": null,
"role_archetype": "Engineering",
"slug": "node-backend-developer",
"source": "db"
},
{
"display_name": "Scala Backend Developer",
"id": 87,
"rationale": null,
"role_archetype": "Engineering",
"slug": "scala-backend-developer",
"source": "db"
}
]
},
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "React Frontend Development",
"id": 96,
"rationale": "Building interactive web user interfaces with React.js, including component composition, state management, hooks, and rendering patterns. React.js belongs here because it is a core library for client-side UI development in modern web applications.",
"slug": "d_init_01",
"source": "db"
},
"input_skill": "Git",
"llm_role": null,
"roles_from_db": []
},
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "React Frontend Development",
"id": 96,
"rationale": "Building interactive web user interfaces with React.js, including component composition, state management, hooks, and rendering patterns. React.js belongs here because it is a core library for client-side UI development in modern web applications.",
"slug": "d_init_01",
"source": "db"
},
"input_skill": "Agile",
"llm_role": null,
"roles_from_db": []
},
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Containerization and Image Builds",
"id": 152,
"rationale": "Container image creation, tagging, hardening, and registry workflows used to package services for deployment. This is coherent because DevOps often owns the build-to-image path that feeds runtime environments.",
"slug": "containerization-and-image-builds",
"source": "db"
},
"input_skill": "Docker",
"llm_role": null,
"roles_from_db": [
{
"display_name": "DevOps Engineer",
"id": 10,
"rationale": null,
"role_archetype": null,
"slug": "devops-engineer",
"source": "db"
}
]
},
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Deployment and Cloud Platforms",
"id": 418,
"rationale": "Platform-as-a-Service and container environments for deploying Ruby applications.",
"slug": "deployment-and-cloud-platforms",
"source": "db"
},
"input_skill": "Docker",
"llm_role": null,
"roles_from_db": [
{
"display_name": "Ruby Backend Developer",
"id": 85,
"rationale": null,
"role_archetype": "Engineering",
"slug": "ruby-backend-developer",
"source": "db"
}
]
},
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Deployment and Runtime Configuration",
"id": 13,
"rationale": "Configuration and release artifacts that control how backend services run in environments. Includes environment variables, manifests, feature flags, and release-safe configuration management.",
"slug": "deployment-and-runtime-configuration",
"source": "db"
},
"input_skill": "Docker",
"llm_role": null,
"roles_from_db": [
{
"display_name": ".NET Backend Developer",
"id": 83,
"rationale": null,
"role_archetype": "Engineering",
"slug": "dotnet-backend-developer",
"source": "db"
},
{
"display_name": "Backend Developer",
"id": 1,
"rationale": null,
"role_archetype": "A Backend Engineer designs, builds, and maintains the server-side logic and data handling that power applications and services. They focus on implementing reliable business functionality, integrating with other systems, and ensuring the backend is scalable, maintainable, and observable.",
"slug": "backend-engineer",
"source": "db"
},
{
"display_name": "Go Backend Developer",
"id": 81,
"rationale": null,
"role_archetype": "Engineering",
"slug": "go-backend-developer",
"source": "db"
},
{
"display_name": "PHP Backend Developer",
"id": 86,
"rationale": null,
"role_archetype": "Engineering",
"slug": "php-backend-developer",
"source": "db"
}
]
},
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Container Orchestration Platforms",
"id": 134,
"rationale": "Platforms that schedule and manage containerized workloads across clusters and environments. Cloud Architects need these to define workload placement standards, cluster boundaries, and platform capabilities.",
"slug": "container-orchestration-platforms",
"source": "db"
},
"input_skill": "Kubernetes",
"llm_role": null,
"roles_from_db": [
{
"display_name": "Cloud Architect",
"id": 9,
"rationale": null,
"role_archetype": null,
"slug": "cloud-architect",
"source": "db"
},
{
"display_name": "DevOps Engineer",
"id": 10,
"rationale": null,
"role_archetype": null,
"slug": "devops-engineer",
"source": "db"
}
]
},
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Kubernetes for ML Workloads",
"id": 47,
"rationale": "Kubernetes-native components used to schedule, accelerate, and isolate ML training and serving workloads. This includes GPU enablement and ML-specific controllers rather than generic cluster administration.",
"slug": "kubernetes-for-ml-workloads",
"source": "db"
},
"input_skill": "Kubernetes",
"llm_role": null,
"roles_from_db": [
{
"display_name": "ML Engineer",
"id": 3,
"rationale": null,
"role_archetype": null,
"slug": "ml-engineer",
"source": "db"
},
{
"display_name": "MLOps Engineer",
"id": 16,
"rationale": null,
"role_archetype": null,
"slug": "ml-ops-engineer",
"source": "db"
}
]
},
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Web Application Frameworks",
"id": 2,
"rationale": "Server frameworks and runtimes used to build HTTP services, controllers, middleware, and request pipelines. These frameworks shape how backend endpoints are structured and delivered.",
"slug": "web-application-frameworks",
"source": "db"
},
"input_skill": "Spring",
"llm_role": null,
"roles_from_db": [
{
"display_name": "Backend Developer",
"id": 1,
"rationale": null,
"role_archetype": "A Backend Engineer designs, builds, and maintains the server-side logic and data handling that power applications and services. They focus on implementing reliable business functionality, integrating with other systems, and ensuring the backend is scalable, maintainable, and observable.",
"slug": "backend-engineer",
"source": "db"
},
{
"display_name": "Fullstack Developer",
"id": 435,
"rationale": null,
"role_archetype": "Engineering",
"slug": "fullstack-developer",
"source": "db"
},
{
"display_name": "Fullstack Developer",
"id": 15,
"rationale": null,
"role_archetype": null,
"slug": "full-stack-engineer",
"source": "db"
},
{
"display_name": "Java Backend Developer",
"id": 79,
"rationale": null,
"role_archetype": "Engineering",
"slug": "java-backend-developer",
"source": "db"
},
{
"display_name": "Node.js Backend Developer",
"id": 82,
"rationale": null,
"role_archetype": "Engineering",
"slug": "node-backend-developer",
"source": "db"
},
{
"display_name": "PHP Backend Developer",
"id": 86,
"rationale": null,
"role_archetype": "Engineering",
"slug": "php-backend-developer",
"source": "db"
},
{
"display_name": "Python Backend Developer",
"id": 80,
"rationale": null,
"role_archetype": "Engineering",
"slug": "python-backend-developer",
"source": "db"
}
]
},
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Relational Data Modeling",
"id": 216,
"rationale": "Modeling and tuning relational persistence for backend features. PHP backend developers need this to shape schemas, indexes, transactions, and query-aware data structures that support application behavior.",
"slug": "relational-data-modeling",
"source": "db"
},
"input_skill": "PostgreSQL",
"llm_role": null,
"roles_from_db": [
{
"display_name": "Fullstack Developer",
"id": 15,
"rationale": null,
"role_archetype": null,
"slug": "full-stack-engineer",
"source": "db"
},
{
"display_name": "Fullstack Developer",
"id": 435,
"rationale": null,
"role_archetype": "Engineering",
"slug": "fullstack-developer",
"source": "db"
},
{
"display_name": "PHP Backend Developer",
"id": 86,
"rationale": null,
"role_archetype": "Engineering",
"slug": "php-backend-developer",
"source": "db"
}
]
},
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Relational Database Design",
"id": 4,
"rationale": "Modeling and operating relational persistence for backend services. Includes schema design, normalization, indexing, transactions, and query tuning for operational data stores.",
"slug": "relational-database-design",
"source": "db"
},
"input_skill": "PostgreSQL",
"llm_role": null,
"roles_from_db": [
{
"display_name": ".NET Backend Developer",
"id": 83,
"rationale": null,
"role_archetype": "Engineering",
"slug": "dotnet-backend-developer",
"source": "db"
},
{
"display_name": "Backend Developer",
"id": 1,
"rationale": null,
"role_archetype": "A Backend Engineer designs, builds, and maintains the server-side logic and data handling that power applications and services. They focus on implementing reliable business functionality, integrating with other systems, and ensuring the backend is scalable, maintainable, and observable.",
"slug": "backend-engineer",
"source": "db"
},
{
"display_name": "Kotlin Backend Developer",
"id": 84,
"rationale": null,
"role_archetype": "Engineering",
"slug": "kotlin-server-backend-developer",
"source": "db"
},
{
"display_name": "Node.js Backend Developer",
"id": 82,
"rationale": null,
"role_archetype": "Engineering",
"slug": "node-backend-developer",
"source": "db"
},
{
"display_name": "Python Backend Developer",
"id": 80,
"rationale": null,
"role_archetype": "Engineering",
"slug": "python-backend-developer",
"source": "db"
},
{
"display_name": "Ruby Backend Developer",
"id": 85,
"rationale": null,
"role_archetype": "Engineering",
"slug": "ruby-backend-developer",
"source": "db"
},
{
"display_name": "Scala Backend Developer",
"id": 87,
"rationale": null,
"role_archetype": "Engineering",
"slug": "scala-backend-developer",
"source": "db"
}
]
},
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Relational Database Usage",
"id": 371,
"rationale": "Working effectively with operational relational databases from Go backend services. This includes schema-aware querying, indexing awareness, transactions, and understanding how service code interacts with PostgreSQL or similar systems.",
"slug": "relational-database-usage",
"source": "db"
},
"input_skill": "PostgreSQL",
"llm_role": null,
"roles_from_db": [
{
"display_name": "Go Backend Developer",
"id": 81,
"rationale": null,
"role_archetype": "Engineering",
"slug": "go-backend-developer",
"source": "db"
}
]
},
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Backend Observability, Logging, and Diagnostics",
"id": 388,
"rationale": "Instrumentation and troubleshooting practices used to understand and improve backend service behavior in production and lower environments. This includes logs, metrics, traces, alerting, dashboards, structured logging, distributed tracing, health checks, and root-cause analysis using ecosystem-specific tools such as SLF4J, Logback, Micrometer, OpenTelemetry, Prometheus, Grafana, ILogger, Serilog, and Application Insights.",
"slug": "backend-observability-logging-and-diagnostics",
"source": "db"
},
"input_skill": "Prometheus",
"llm_role": null,
"roles_from_db": [
{
"display_name": "Kotlin Backend Developer",
"id": 84,
"rationale": null,
"role_archetype": "Engineering",
"slug": "kotlin-server-backend-developer",
"source": "db"
},
{
"display_name": "Scala Backend Developer",
"id": 87,
"rationale": null,
"role_archetype": "Engineering",
"slug": "scala-backend-developer",
"source": "db"
}
]
},
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Observability and Incident Response",
"id": 10,
"rationale": "Instrumentation and production troubleshooting practices used to keep backend services reliable. Includes logs, metrics, traces, alerting, dashboards, and incident diagnosis.",
"slug": "observability-and-incident-response",
"source": "db"
},
"input_skill": "Prometheus",
"llm_role": null,
"roles_from_db": [
{
"display_name": ".NET Backend Developer",
"id": 83,
"rationale": null,
"role_archetype": "Engineering",
"slug": "dotnet-backend-developer",
"source": "db"
},
{
"display_name": "Backend Developer",
"id": 1,
"rationale": null,
"role_archetype": "A Backend Engineer designs, builds, and maintains the server-side logic and data handling that power applications and services. They focus on implementing reliable business functionality, integrating with other systems, and ensuring the backend is scalable, maintainable, and observable.",
"slug": "backend-engineer",
"source": "db"
},
{
"display_name": "Node.js Backend Developer",
"id": 82,
"rationale": null,
"role_archetype": "Engineering",
"slug": "node-backend-developer",
"source": "db"
},
{
"display_name": "PHP Backend Developer",
"id": 86,
"rationale": null,
"role_archetype": "Engineering",
"slug": "php-backend-developer",
"source": "db"
}
]
},
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Observability and Incident Triage",
"id": 155,
"rationale": "Telemetry, alerting, and troubleshooting practices used to diagnose failed builds, broken deployments, and unhealthy release environments. This is a coherent cluster because delivery reliability depends on quickly identifying where the workflow failed.",
"slug": "observability-and-incident-triage",
"source": "db"
},
"input_skill": "Prometheus",
"llm_role": null,
"roles_from_db": [
{
"display_name": "DevOps Engineer",
"id": 10,
"rationale": null,
"role_archetype": null,
"slug": "devops-engineer",
"source": "db"
}
]
},
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Observability and Operations",
"id": 143,
"rationale": "Monitoring, logging, tracing, and operational readiness patterns used to keep cloud platforms supportable. Cloud Architects use this to define what telemetry and operational controls workloads must expose.",
"slug": "observability-and-operations",
"source": "db"
},
"input_skill": "Prometheus",
"llm_role": null,
"roles_from_db": [
{
"display_name": "Cloud Architect",
"id": 9,
"rationale": null,
"role_archetype": null,
"slug": "cloud-architect",
"source": "db"
}
]
},
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Backend Observability, Logging, and Diagnostics",
"id": 388,
"rationale": "Instrumentation and troubleshooting practices used to understand and improve backend service behavior in production and lower environments. This includes logs, metrics, traces, alerting, dashboards, structured logging, distributed tracing, health checks, and root-cause analysis using ecosystem-specific tools such as SLF4J, Logback, Micrometer, OpenTelemetry, Prometheus, Grafana, ILogger, Serilog, and Application Insights.",
"slug": "backend-observability-logging-and-diagnostics",
"source": "db"
},
"input_skill": "Grafana",
"llm_role": null,
"roles_from_db": [
{
"display_name": "Kotlin Backend Developer",
"id": 84,
"rationale": null,
"role_archetype": "Engineering",
"slug": "kotlin-server-backend-developer",
"source": "db"
},
{
"display_name": "Scala Backend Developer",
"id": 87,
"rationale": null,
"role_archetype": "Engineering",
"slug": "scala-backend-developer",
"source": "db"
}
]
},
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Observability and Incident Response",
"id": 10,
"rationale": "Instrumentation and production troubleshooting practices used to keep backend services reliable. Includes logs, metrics, traces, alerting, dashboards, and incident diagnosis.",
"slug": "observability-and-incident-response",
"source": "db"
},
"input_skill": "Grafana",
"llm_role": null,
"roles_from_db": [
{
"display_name": ".NET Backend Developer",
"id": 83,
"rationale": null,
"role_archetype": "Engineering",
"slug": "dotnet-backend-developer",
"source": "db"
},
{
"display_name": "Backend Developer",
"id": 1,
"rationale": null,
"role_archetype": "A Backend Engineer designs, builds, and maintains the server-side logic and data handling that power applications and services. They focus on implementing reliable business functionality, integrating with other systems, and ensuring the backend is scalable, maintainable, and observable.",
"slug": "backend-engineer",
"source": "db"
},
{
"display_name": "Node.js Backend Developer",
"id": 82,
"rationale": null,
"role_archetype": "Engineering",
"slug": "node-backend-developer",
"source": "db"
},
{
"display_name": "PHP Backend Developer",
"id": 86,
"rationale": null,
"role_archetype": "Engineering",
"slug": "php-backend-developer",
"source": "db"
}
]
},
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Observability and Incident Triage",
"id": 155,
"rationale": "Telemetry, alerting, and troubleshooting practices used to diagnose failed builds, broken deployments, and unhealthy release environments. This is a coherent cluster because delivery reliability depends on quickly identifying where the workflow failed.",
"slug": "observability-and-incident-triage",
"source": "db"
},
"input_skill": "Grafana",
"llm_role": null,
"roles_from_db": [
{
"display_name": "DevOps Engineer",
"id": 10,
"rationale": null,
"role_archetype": null,
"slug": "devops-engineer",
"source": "db"
}
]
},
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Observability and Operations",
"id": 143,
"rationale": "Monitoring, logging, tracing, and operational readiness patterns used to keep cloud platforms supportable. Cloud Architects use this to define what telemetry and operational controls workloads must expose.",
"slug": "observability-and-operations",
"source": "db"
},
"input_skill": "Grafana",
"llm_role": null,
"roles_from_db": [
{
"display_name": "Cloud Architect",
"id": 9,
"rationale": null,
"role_archetype": null,
"slug": "cloud-architect",
"source": "db"
}
]
},
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Messaging and Event Streaming",
"id": 8,
"rationale": "Transport-layer systems used to move events and decouple producers from consumers. Data engineers use these systems to ingest, buffer, and distribute event data before downstream processing.",
"slug": "messaging-and-event-streaming",
"source": "db"
},
"input_skill": "Apache Kafka",
"llm_role": null,
"roles_from_db": [
{
"display_name": "Backend Developer",
"id": 1,
"rationale": null,
"role_archetype": "A Backend Engineer designs, builds, and maintains the server-side logic and data handling that power applications and services. They focus on implementing reliable business functionality, integrating with other systems, and ensuring the backend is scalable, maintainable, and observable.",
"slug": "backend-engineer",
"source": "db"
},
{
"display_name": "Data Engineer",
"id": 2,
"rationale": null,
"role_archetype": null,
"slug": "data-engineer",
"source": "db"
}
]
},
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "API Design and Contracts",
"id": 3,
"rationale": "Designing request/response shapes and the rules that govern client-server interaction. This cluster is coherent because full stack engineers often own the contract between UI behavior and backend implementation.",
"slug": "api-design-and-contracts",
"source": "db"
},
"input_skill": "REST",
"llm_role": null,
"roles_from_db": [
{
"display_name": "Backend Developer",
"id": 1,
"rationale": null,
"role_archetype": "A Backend Engineer designs, builds, and maintains the server-side logic and data handling that power applications and services. They focus on implementing reliable business functionality, integrating with other systems, and ensuring the backend is scalable, maintainable, and observable.",
"slug": "backend-engineer",
"source": "db"
},
{
"display_name": "Fullstack Developer",
"id": 15,
"rationale": null,
"role_archetype": null,
"slug": "full-stack-engineer",
"source": "db"
}
]
},
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "API Interface and Contract Design",
"id": 289,
"rationale": "Designing backend service interfaces and contracts that other systems consume, including endpoint and operation shape, request/response payloads, schema and validation, pagination, filtering, idempotency, versioning, status codes, and backward compatibility across REST, GraphQL, gRPC, and OpenAPI-based APIs.",
"slug": "api-interface-and-contract-design",
"source": "db"
},
"input_skill": "REST",
"llm_role": null,
"roles_from_db": [
{
"display_name": ".NET Backend Developer",
"id": 83,
"rationale": null,
"role_archetype": "Engineering",
"slug": "dotnet-backend-developer",
"source": "db"
},
{
"display_name": "Go Backend Developer",
"id": 81,
"rationale": null,
"role_archetype": "Engineering",
"slug": "go-backend-developer",
"source": "db"
},
{
"display_name": "Kotlin Backend Developer",
"id": 84,
"rationale": null,
"role_archetype": "Engineering",
"slug": "kotlin-server-backend-developer",
"source": "db"
},
{
"display_name": "Node.js Backend Developer",
"id": 82,
"rationale": null,
"role_archetype": "Engineering",
"slug": "node-backend-developer",
"source": "db"
},
{
"display_name": "PHP Backend Developer",
"id": 86,
"rationale": null,
"role_archetype": "Engineering",
"slug": "php-backend-developer",
"source": "db"
},
{
"display_name": "Python Backend Developer",
"id": 80,
"rationale": null,
"role_archetype": "Engineering",
"slug": "python-backend-developer",
"source": "db"
},
{
"display_name": "Ruby Backend Developer",
"id": 85,
"rationale": null,
"role_archetype": "Engineering",
"slug": "ruby-backend-developer",
"source": "db"
},
{
"display_name": "Scala Backend Developer",
"id": 87,
"rationale": null,
"role_archetype": "Engineering",
"slug": "scala-backend-developer",
"source": "db"
}
]
},
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Integration Protocols \u0026 Standards",
"id": 271,
"rationale": "Standards and protocols for integrating Pega applications.",
"slug": "integration-protocols-standards",
"source": "db"
},
"input_skill": "REST",
"llm_role": null,
"roles_from_db": [
{
"display_name": "Pega Developer",
"id": 24,
"rationale": null,
"role_archetype": null,
"slug": "pega-developer",
"source": "db"
}
]
},
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Standards \u0026 Protocols Compliance",
"id": 452,
"rationale": "Encompasses key web and data standards, protocols, and compliance requirements relevant to Sitecore implementations.",
"slug": "standards-protocols-compliance",
"source": "db"
},
"input_skill": "REST",
"llm_role": null,
"roles_from_db": [
{
"display_name": "Sitecore Dev",
"id": 233,
"rationale": null,
"role_archetype": "Engineering",
"slug": "sitecore-dev",
"source": "db"
}
]
}
],
"input_final_skills": [
"Java",
"Microservices",
"Git",
"Agile",
"Docker",
"Kubernetes",
"Spring",
"Dropwizard",
"Jetty",
"Jersey",
"Netflix Hystrix",
"Zipkin",
"PostgreSQL",
"Prometheus",
"Kibana",
"Grafana",
"Apache Maven",
"Apache Kafka",
"Continuous Delivery",
"BDD",
"REST"
],
"input_llm_skills": [
"Java",
"Microservices",
"Git",
"Agile",
"Docker",
"Kubernetes",
"Spring",
"Dropwizard",
"Jetty",
"Jersey",
"Netflix Hystrix",
"Zipkin",
"PostgreSQL",
"Prometheus",
"Kibana",
"Grafana",
"Apache Maven",
"Apache Kafka",
"Continuous Delivery",
"BDD",
"REST"
],
"new_aliases_persisted": 0,
"run_id": "14665224-3376-48b7-92b4-7aed97ed2be8",
"skills_detail": [
{
"aliases_in_db": [
{
"alias_text": "Java",
"alias_type": "CANONICAL",
"id": 1,
"is_primary": true,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "JDK",
"alias_type": "VERSION",
"id": 2968,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "JDK 10",
"alias_type": "VERSION",
"id": 2194,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "JDK 11",
"alias_type": "VERSION",
"id": 4,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "JDK 12",
"alias_type": "VERSION",
"id": 2196,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "JDK 13",
"alias_type": "VERSION",
"id": 2197,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "JDK 14",
"alias_type": "VERSION",
"id": 2198,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "JDK 15",
"alias_type": "VERSION",
"id": 2199,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "JDK 16",
"alias_type": "VERSION",
"id": 2200,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "JDK 17",
"alias_type": "VERSION",
"id": 5,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "JDK 18",
"alias_type": "VERSION",
"id": 2202,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "JDK 19",
"alias_type": "VERSION",
"id": 2203,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "JDK 20",
"alias_type": "VERSION",
"id": 2204,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "JDK 21",
"alias_type": "VERSION",
"id": 6,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "JDK 5",
"alias_type": "VERSION",
"id": 2189,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "JDK 6",
"alias_type": "VERSION",
"id": 2190,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "JDK 7",
"alias_type": "VERSION",
"id": 2191,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "JDK 8",
"alias_type": "VERSION",
"id": 3,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "JDK 9",
"alias_type": "VERSION",
"id": 2193,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "Java 1.0",
"alias_type": "VERSION",
"id": 11,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "Java 1.1",
"alias_type": "VERSION",
"id": 12,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "Java 1.2",
"alias_type": "VERSION",
"id": 13,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "Java 1.3",
"alias_type": "VERSION",
"id": 14,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "Java 1.4",
"alias_type": "VERSION",
"id": 15,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "Java 1.5",
"alias_type": "VERSION",
"id": 16,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "Java 1.6",
"alias_type": "VERSION",
"id": 17,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "Java 1.7",
"alias_type": "VERSION",
"id": 18,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "Java 1.8",
"alias_type": "VERSION",
"id": 19,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "Java 10",
"alias_type": "VERSION",
"id": 2211,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "Java 11",
"alias_type": "VERSION",
"id": 8,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "Java 12",
"alias_type": "VERSION",
"id": 2213,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "Java 13",
"alias_type": "VERSION",
"id": 2214,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "Java 14",
"alias_type": "VERSION",
"id": 2215,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "Java 15",
"alias_type": "VERSION",
"id": 2216,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "Java 16",
"alias_type": "VERSION",
"id": 2217,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "Java 17",
"alias_type": "VERSION",
"id": 9,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "Java 18",
"alias_type": "VERSION",
"id": 2219,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "Java 19",
"alias_type": "VERSION",
"id": 2220,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "Java 20",
"alias_type": "VERSION",
"id": 2221,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "Java 21",
"alias_type": "VERSION",
"id": 10,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "Java 5",
"alias_type": "VERSION",
"id": 288,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "Java 6",
"alias_type": "VERSION",
"id": 289,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "Java 7",
"alias_type": "VERSION",
"id": 290,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "Java 8",
"alias_type": "VERSION",
"id": 7,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "Java 9",
"alias_type": "VERSION",
"id": 2210,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "Java11",
"alias_type": "VERSION",
"id": 2976,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "Java17",
"alias_type": "VERSION",
"id": 2977,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "Java21",
"alias_type": "VERSION",
"id": 2978,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "Java8",
"alias_type": "VERSION",
"id": 2971,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "OpenJDK 11",
"alias_type": "VERSION",
"id": 21,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "OpenJDK 17",
"alias_type": "VERSION",
"id": 22,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "OpenJDK 21",
"alias_type": "VERSION",
"id": 23,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "OpenJDK 8",
"alias_type": "VERSION",
"id": 20,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "java 11",
"alias_type": "VERSION",
"id": 1512,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "java 17",
"alias_type": "VERSION",
"id": 1513,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "java 21",
"alias_type": "VERSION",
"id": 1514,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "java 4",
"alias_type": "VERSION",
"id": 1496,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "java 5",
"alias_type": "VERSION",
"id": 1497,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "java 6",
"alias_type": "VERSION",
"id": 1498,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "java 7",
"alias_type": "VERSION",
"id": 1499,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "java 8",
"alias_type": "VERSION",
"id": 1500,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "java lts",
"alias_type": "VERSION",
"id": 3122,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "java-11",
"alias_type": "VERSION",
"id": 1515,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "java-17",
"alias_type": "VERSION",
"id": 1516,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "java-21",
"alias_type": "VERSION",
"id": 1517,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "java-4",
"alias_type": "VERSION",
"id": 1501,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "java-5",
"alias_type": "VERSION",
"id": 1502,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "java-6",
"alias_type": "VERSION",
"id": 1503,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "java-7",
"alias_type": "VERSION",
"id": 1504,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "java-8",
"alias_type": "VERSION",
"id": 1505,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "java11",
"alias_type": "VERSION",
"id": 1506,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "java17",
"alias_type": "VERSION",
"id": 1507,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "java21",
"alias_type": "VERSION",
"id": 1508,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "java4",
"alias_type": "VERSION",
"id": 1482,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "java5",
"alias_type": "VERSION",
"id": 1483,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "java6",
"alias_type": "VERSION",
"id": 1484,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "java7",
"alias_type": "VERSION",
"id": 1485,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "java8",
"alias_type": "VERSION",
"id": 1486,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "jdk 11",
"alias_type": "VERSION",
"id": 1509,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "jdk 17",
"alias_type": "VERSION",
"id": 1510,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "jdk 21",
"alias_type": "VERSION",
"id": 1511,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "jdk 4",
"alias_type": "VERSION",
"id": 1487,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "jdk 5",
"alias_type": "VERSION",
"id": 1488,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "jdk 6",
"alias_type": "VERSION",
"id": 1489,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "jdk 7",
"alias_type": "VERSION",
"id": 1490,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "jdk 8",
"alias_type": "VERSION",
"id": 1491,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "jdk11",
"alias_type": "VERSION",
"id": 1492,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "jdk17",
"alias_type": "VERSION",
"id": 1493,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "jdk21",
"alias_type": "VERSION",
"id": 1494,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "jdk4",
"alias_type": "VERSION",
"id": 1477,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "jdk5",
"alias_type": "VERSION",
"id": 1478,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "jdk6",
"alias_type": "VERSION",
"id": 1479,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "jdk7",
"alias_type": "VERSION",
"id": 1480,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "jdk8",
"alias_type": "VERSION",
"id": 1481,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "jvm21",
"alias_type": "VERSION",
"id": 1495,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
}
],
"canonical": {
"category_id": 6,
"display_name": "Java",
"id": 1,
"is_also_category": false,
"is_extractable": true,
"skill_nature": "LANGUAGE",
"slug": "java",
"sub_category_id": 96,
"typical_lifespan": "EVERGREEN",
"volatility": "STABLE"
},
"dimensions": [
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Java Language and JVM",
"id": 279,
"rationale": "Core Java implementation skills used to build backend service logic, utilities, and internal abstractions. This is the primary coding surface for the role and includes language features plus JVM behavior that affect correctness and maintainability.",
"slug": "java-language-and-jvm",
"source": "db"
},
"input_skill": "Java",
"llm_role": null,
"roles_from_db": [
{
"display_name": "Java Backend Developer",
"id": 79,
"rationale": null,
"role_archetype": "Engineering",
"slug": "java-backend-developer",
"source": "db"
},
{
"display_name": "Kotlin Backend Developer",
"id": 84,
"rationale": null,
"role_archetype": "Engineering",
"slug": "kotlin-server-backend-developer",
"source": "db"
},
{
"display_name": "Scala Backend Developer",
"id": 87,
"rationale": null,
"role_archetype": "Engineering",
"slug": "scala-backend-developer",
"source": "db"
}
]
},
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Kotlin and Java",
"id": 161,
"rationale": "Primary implementation languages for Android app features, platform integration, and client-side business logic. Android engineers use these languages to build screens, state flows, service adapters, and device-aware behavior.",
"slug": "kotlin-and-java",
"source": "db"
},
"input_skill": "Java",
"llm_role": null,
"roles_from_db": [
{
"display_name": "Android Developer",
"id": 4,
"rationale": null,
"role_archetype": null,
"slug": "android-engineer",
"source": "db"
}
]
},
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Native Mobile Languages",
"id": 274,
"rationale": "Primary implementation languages used to build platform-specific app features, UI logic, and device integrations. This is the core coding surface for native mobile work on one platform.",
"slug": "native-mobile-languages",
"source": "db"
},
"input_skill": "Java",
"llm_role": null,
"roles_from_db": [
{
"display_name": "Native Mobile Developer",
"id": 75,
"rationale": null,
"role_archetype": "Engineering",
"slug": "native-mobile-developer",
"source": "db"
}
]
},
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Pega Programming Languages \u0026 DSLs",
"id": 267,
"rationale": "Programming languages and domain-specific languages used in Pega development.",
"slug": "pega-programming-languages-dsls",
"source": "db"
},
"input_skill": "Java",
"llm_role": null,
"roles_from_db": [
{
"display_name": "Pega Developer",
"id": 24,
"rationale": null,
"role_archetype": null,
"slug": "pega-developer",
"source": "db"
}
]
},
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Programming Languages",
"id": 1,
"rationale": "Primary implementation languages used to build client and server feature code. Full stack engineers need enough fluency to move across layers and implement product behavior end to end.",
"slug": "programming-languages",
"source": "db"
},
"input_skill": "Java",
"llm_role": null,
"roles_from_db": [
{
"display_name": "Backend Developer",
"id": 1,
"rationale": null,
"role_archetype": "A Backend Engineer designs, builds, and maintains the server-side logic and data handling that power applications and services. They focus on implementing reliable business functionality, integrating with other systems, and ensuring the backend is scalable, maintainable, and observable.",
"slug": "backend-engineer",
"source": "db"
},
{
"display_name": "Fullstack Developer",
"id": 435,
"rationale": null,
"role_archetype": "Engineering",
"slug": "fullstack-developer",
"source": "db"
},
{
"display_name": "Fullstack Developer",
"id": 15,
"rationale": null,
"role_archetype": null,
"slug": "full-stack-engineer",
"source": "db"
}
]
},
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Programming Languages for Data Work",
"id": 21,
"rationale": "Languages used to implement data pipelines, transformations, and operational glue. This is the primary coding surface for building ingestion, enrichment, and automation logic in data engineering.",
"slug": "programming-languages-for-data-work",
"source": "db"
},
"input_skill": "Java",
"llm_role": null,
"roles_from_db": [
{
"display_name": "Data Engineer",
"id": 2,
"rationale": null,
"role_archetype": null,
"slug": "data-engineer",
"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": "microservices",
"alias_type": "CANONICAL",
"id": 178,
"is_primary": true,
"match_strategy": "CASE_INSENSITIVE"
}
],
"canonical": {
"category_id": 1,
"display_name": "microservices",
"id": 41,
"is_also_category": false,
"is_extractable": true,
"skill_nature": "PATTERN",
"slug": "microservices",
"sub_category_id": 1,
"typical_lifespan": "EVERGREEN",
"volatility": "STABLE"
},
"dimensions": [
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Microservices and Distributed Systems",
"id": 9,
"rationale": "Architectural patterns for decomposed backend systems and the operational concerns they introduce. Covers service boundaries, consistency tradeoffs, retries, circuit breakers, and distributed coordination.",
"slug": "microservices-and-distributed-systems",
"source": "db"
},
"input_skill": "Microservices",
"llm_role": null,
"roles_from_db": [
{
"display_name": "Backend Developer",
"id": 1,
"rationale": null,
"role_archetype": "A Backend Engineer designs, builds, and maintains the server-side logic and data handling that power applications and services. They focus on implementing reliable business functionality, integrating with other systems, and ensuring the backend is scalable, maintainable, and observable.",
"slug": "backend-engineer",
"source": "db"
},
{
"display_name": "Node.js Backend Developer",
"id": 82,
"rationale": null,
"role_archetype": "Engineering",
"slug": "node-backend-developer",
"source": "db"
},
{
"display_name": "Scala Backend Developer",
"id": 87,
"rationale": null,
"role_archetype": "Engineering",
"slug": "scala-backend-developer",
"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": [
{
"alias_text": "Git",
"alias_type": "CANONICAL",
"id": 1613,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
}
],
"canonical": {
"category_id": 13,
"display_name": "Git",
"id": 1002,
"is_also_category": false,
"is_extractable": true,
"skill_nature": "TOOL",
"slug": "git",
"sub_category_id": 730,
"typical_lifespan": "EVERGREEN",
"volatility": "STABLE"
},
"dimensions": [
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "React Frontend Development",
"id": 96,
"rationale": "Building interactive web user interfaces with React.js, including component composition, state management, hooks, and rendering patterns. React.js belongs here because it is a core library for client-side UI development in modern web applications.",
"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": "Agile",
"alias_type": "CANONICAL",
"id": 868,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
}
],
"canonical": {
"category_id": 8,
"display_name": "Agile",
"id": 520,
"is_also_category": false,
"is_extractable": true,
"skill_nature": "METHODOLOGY",
"slug": "agile",
"sub_category_id": 367,
"typical_lifespan": "EVERGREEN",
"volatility": "STABLE"
},
"dimensions": [
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "React Frontend Development",
"id": 96,
"rationale": "Building interactive web user interfaces with React.js, including component composition, state management, hooks, and rendering patterns. React.js belongs here because it is a core library for client-side UI development in modern web applications.",
"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": "Docker",
"alias_type": "CANONICAL",
"id": 198,
"is_primary": true,
"match_strategy": "CASE_INSENSITIVE"
}
],
"canonical": {
"category_id": 13,
"display_name": "Docker",
"id": 61,
"is_also_category": false,
"is_extractable": true,
"skill_nature": "TOOL",
"slug": "docker",
"sub_category_id": 63,
"typical_lifespan": "EVERGREEN",
"volatility": "STABLE"
},
"dimensions": [
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Containerization and Image Builds",
"id": 152,
"rationale": "Container image creation, tagging, hardening, and registry workflows used to package services for deployment. This is coherent because DevOps often owns the build-to-image path that feeds runtime environments.",
"slug": "containerization-and-image-builds",
"source": "db"
},
"input_skill": "Docker",
"llm_role": null,
"roles_from_db": [
{
"display_name": "DevOps Engineer",
"id": 10,
"rationale": null,
"role_archetype": null,
"slug": "devops-engineer",
"source": "db"
}
]
},
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Deployment and Cloud Platforms",
"id": 418,
"rationale": "Platform-as-a-Service and container environments for deploying Ruby applications.",
"slug": "deployment-and-cloud-platforms",
"source": "db"
},
"input_skill": "Docker",
"llm_role": null,
"roles_from_db": [
{
"display_name": "Ruby Backend Developer",
"id": 85,
"rationale": null,
"role_archetype": "Engineering",
"slug": "ruby-backend-developer",
"source": "db"
}
]
},
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Deployment and Runtime Configuration",
"id": 13,
"rationale": "Configuration and release artifacts that control how backend services run in environments. Includes environment variables, manifests, feature flags, and release-safe configuration management.",
"slug": "deployment-and-runtime-configuration",
"source": "db"
},
"input_skill": "Docker",
"llm_role": null,
"roles_from_db": [
{
"display_name": ".NET Backend Developer",
"id": 83,
"rationale": null,
"role_archetype": "Engineering",
"slug": "dotnet-backend-developer",
"source": "db"
},
{
"display_name": "Backend Developer",
"id": 1,
"rationale": null,
"role_archetype": "A Backend Engineer designs, builds, and maintains the server-side logic and data handling that power applications and services. They focus on implementing reliable business functionality, integrating with other systems, and ensuring the backend is scalable, maintainable, and observable.",
"slug": "backend-engineer",
"source": "db"
},
{
"display_name": "Go Backend Developer",
"id": 81,
"rationale": null,
"role_archetype": "Engineering",
"slug": "go-backend-developer",
"source": "db"
},
{
"display_name": "PHP Backend Developer",
"id": 86,
"rationale": null,
"role_archetype": "Engineering",
"slug": "php-backend-developer",
"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": 1267,
"is_primary": true,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "Kubernetes 1.0+",
"alias_type": "VERSION",
"id": 1271,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "Kubernetes 1.x",
"alias_type": "VERSION",
"id": 1270,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "Kubernetes v1",
"alias_type": "VERSION",
"id": 1269,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "k8s",
"alias_type": "VERSION",
"id": 1268,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "kubernetes 1.x",
"alias_type": "VERSION",
"id": 1400,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "kubernetes latest",
"alias_type": "VERSION",
"id": 1401,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
}
],
"canonical": {
"category_id": 9,
"display_name": "Kubernetes",
"id": 726,
"is_also_category": false,
"is_extractable": true,
"skill_nature": "PLATFORM",
"slug": "kubernetes",
"sub_category_id": 557,
"typical_lifespan": "EVERGREEN",
"volatility": "STABLE"
},
"dimensions": [
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Container Orchestration Platforms",
"id": 134,
"rationale": "Platforms that schedule and manage containerized workloads across clusters and environments. Cloud Architects need these to define workload placement standards, cluster boundaries, and platform capabilities.",
"slug": "container-orchestration-platforms",
"source": "db"
},
"input_skill": "Kubernetes",
"llm_role": null,
"roles_from_db": [
{
"display_name": "Cloud Architect",
"id": 9,
"rationale": null,
"role_archetype": null,
"slug": "cloud-architect",
"source": "db"
},
{
"display_name": "DevOps Engineer",
"id": 10,
"rationale": null,
"role_archetype": null,
"slug": "devops-engineer",
"source": "db"
}
]
},
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Kubernetes for ML Workloads",
"id": 47,
"rationale": "Kubernetes-native components used to schedule, accelerate, and isolate ML training and serving workloads. This includes GPU enablement and ML-specific controllers rather than generic cluster administration.",
"slug": "kubernetes-for-ml-workloads",
"source": "db"
},
"input_skill": "Kubernetes",
"llm_role": null,
"roles_from_db": [
{
"display_name": "ML Engineer",
"id": 3,
"rationale": null,
"role_archetype": null,
"slug": "ml-engineer",
"source": "db"
},
{
"display_name": "MLOps Engineer",
"id": 16,
"rationale": null,
"role_archetype": null,
"slug": "ml-ops-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": "Spring",
"alias_type": "CANONICAL",
"id": 2585,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "Spring 4",
"alias_type": "VERSION",
"id": 2593,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "Spring 4.x",
"alias_type": "VERSION",
"id": 2594,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "Spring 5",
"alias_type": "VERSION",
"id": 2590,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "Spring 5.x",
"alias_type": "VERSION",
"id": 2591,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "Spring 6",
"alias_type": "VERSION",
"id": 2587,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "Spring 6.x",
"alias_type": "VERSION",
"id": 2588,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "Spring Framework 4",
"alias_type": "VERSION",
"id": 2592,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "Spring Framework 5",
"alias_type": "VERSION",
"id": 2589,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "Spring Framework 6",
"alias_type": "VERSION",
"id": 2586,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
}
],
"canonical": {
"category_id": 5,
"display_name": "Spring",
"id": 1630,
"is_also_category": false,
"is_extractable": true,
"skill_nature": "FRAMEWORK",
"slug": "spring",
"sub_category_id": 1228,
"typical_lifespan": "EVERGREEN",
"volatility": "STABLE"
},
"dimensions": [
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Web Application Frameworks",
"id": 2,
"rationale": "Server frameworks and runtimes used to build HTTP services, controllers, middleware, and request pipelines. These frameworks shape how backend endpoints are structured and delivered.",
"slug": "web-application-frameworks",
"source": "db"
},
"input_skill": "Spring",
"llm_role": null,
"roles_from_db": [
{
"display_name": "Backend Developer",
"id": 1,
"rationale": null,
"role_archetype": "A Backend Engineer designs, builds, and maintains the server-side logic and data handling that power applications and services. They focus on implementing reliable business functionality, integrating with other systems, and ensuring the backend is scalable, maintainable, and observable.",
"slug": "backend-engineer",
"source": "db"
},
{
"display_name": "Fullstack Developer",
"id": 435,
"rationale": null,
"role_archetype": "Engineering",
"slug": "fullstack-developer",
"source": "db"
},
{
"display_name": "Fullstack Developer",
"id": 15,
"rationale": null,
"role_archetype": null,
"slug": "full-stack-engineer",
"source": "db"
},
{
"display_name": "Java Backend Developer",
"id": 79,
"rationale": null,
"role_archetype": "Engineering",
"slug": "java-backend-developer",
"source": "db"
},
{
"display_name": "Node.js Backend Developer",
"id": 82,
"rationale": null,
"role_archetype": "Engineering",
"slug": "node-backend-developer",
"source": "db"
},
{
"display_name": "PHP Backend Developer",
"id": 86,
"rationale": null,
"role_archetype": "Engineering",
"slug": "php-backend-developer",
"source": "db"
},
{
"display_name": "Python Backend Developer",
"id": 80,
"rationale": null,
"role_archetype": "Engineering",
"slug": "python-backend-developer",
"source": "db"
}
]
}
],
"input_skill": "Spring",
"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": [],
"input_skill": "Dropwizard",
"matched_via": null,
"new_alias_persisted": false,
"new_alias_text": null,
"new_skill_meta": {
"derived": {
"category": "Web Frameworks",
"skill_nature": "TOOL",
"sub_category": "general",
"typical_lifespan": "MULTI_YEAR",
"version_strategy": "UNVERSIONED",
"volatility": "MEDIUM"
},
"enrichment": null,
"keep_log": [],
"locked_dimensions": [],
"merge_log": [],
"placed": null,
"relationships": null,
"skill_id": "dropwizard",
"split_log": [],
"typed": null,
"warnings": []
},
"source_tag": "llm",
"was_in_llm_skills": true
},
{
"aliases_in_db": [],
"canonical": null,
"dimensions": [],
"input_skill": "Jetty",
"matched_via": null,
"new_alias_persisted": false,
"new_alias_text": null,
"new_skill_meta": {
"derived": {
"category": "Web Frameworks",
"skill_nature": "TOOL",
"sub_category": "general",
"typical_lifespan": "MULTI_YEAR",
"version_strategy": "UNVERSIONED",
"volatility": "MEDIUM"
},
"enrichment": null,
"keep_log": [],
"locked_dimensions": [],
"merge_log": [],
"placed": null,
"relationships": null,
"skill_id": "jetty",
"split_log": [],
"typed": null,
"warnings": []
},
"source_tag": "llm",
"was_in_llm_skills": true
},
{
"aliases_in_db": [],
"canonical": null,
"dimensions": [],
"input_skill": "Jersey",
"matched_via": null,
"new_alias_persisted": false,
"new_alias_text": null,
"new_skill_meta": {
"derived": {
"category": "Web Frameworks",
"skill_nature": "TOOL",
"sub_category": "general",
"typical_lifespan": "MULTI_YEAR",
"version_strategy": "UNVERSIONED",
"volatility": "MEDIUM"
},
"enrichment": null,
"keep_log": [],
"locked_dimensions": [],
"merge_log": [],
"placed": null,
"relationships": null,
"skill_id": "jersey",
"split_log": [],
"typed": null,
"warnings": []
},
"source_tag": "llm",
"was_in_llm_skills": true
},
{
"aliases_in_db": [],
"canonical": null,
"dimensions": [],
"input_skill": "Netflix Hystrix",
"matched_via": null,
"new_alias_persisted": false,
"new_alias_text": null,
"new_skill_meta": {
"derived": {
"category": "Microservices",
"skill_nature": "TOOL",
"sub_category": "general",
"typical_lifespan": "MULTI_YEAR",
"version_strategy": "UNVERSIONED",
"volatility": "MEDIUM"
},
"enrichment": null,
"keep_log": [],
"locked_dimensions": [],
"merge_log": [],
"placed": null,
"relationships": null,
"skill_id": "netflix-hystrix",
"split_log": [],
"typed": null,
"warnings": []
},
"source_tag": "llm",
"was_in_llm_skills": true
},
{
"aliases_in_db": [],
"canonical": null,
"dimensions": [],
"input_skill": "Zipkin",
"matched_via": null,
"new_alias_persisted": false,
"new_alias_text": null,
"new_skill_meta": {
"derived": {
"category": "Monitoring Tools",
"skill_nature": "TOOL",
"sub_category": "general",
"typical_lifespan": "MULTI_YEAR",
"version_strategy": "UNVERSIONED",
"volatility": "MEDIUM"
},
"enrichment": null,
"keep_log": [],
"locked_dimensions": [],
"merge_log": [],
"placed": null,
"relationships": null,
"skill_id": "zipkin",
"split_log": [],
"typed": null,
"warnings": []
},
"source_tag": "llm",
"was_in_llm_skills": true
},
{
"aliases_in_db": [
{
"alias_text": "PostgreSQL",
"alias_type": "CANONICAL",
"id": 121,
"is_primary": true,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "PG 13",
"alias_type": "VERSION",
"id": 122,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "PG 14",
"alias_type": "VERSION",
"id": 123,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "PG 15",
"alias_type": "VERSION",
"id": 124,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "PG 16",
"alias_type": "VERSION",
"id": 125,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "PostgreSQL 13",
"alias_type": "VERSION",
"id": 130,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "PostgreSQL 14",
"alias_type": "VERSION",
"id": 131,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "PostgreSQL 15",
"alias_type": "VERSION",
"id": 132,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "PostgreSQL 16",
"alias_type": "VERSION",
"id": 133,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "Postgres 13",
"alias_type": "VERSION",
"id": 126,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "Postgres 14",
"alias_type": "VERSION",
"id": 127,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "Postgres 15",
"alias_type": "VERSION",
"id": 128,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "Postgres 16",
"alias_type": "VERSION",
"id": 129,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "pg10",
"alias_type": "VERSION",
"id": 4714,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "pg11",
"alias_type": "VERSION",
"id": 4715,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "pg12",
"alias_type": "VERSION",
"id": 4716,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "pg13",
"alias_type": "VERSION",
"id": 4717,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "pg14",
"alias_type": "VERSION",
"id": 4718,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "pg15",
"alias_type": "VERSION",
"id": 4719,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "pg16",
"alias_type": "VERSION",
"id": 4720,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "postgres",
"alias_type": "VERSION",
"id": 4721,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "postgresql 10",
"alias_type": "VERSION",
"id": 4729,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "postgresql 11",
"alias_type": "VERSION",
"id": 4730,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "postgresql 12",
"alias_type": "VERSION",
"id": 4731,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "postgresql 13",
"alias_type": "VERSION",
"id": 4732,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "postgresql 14",
"alias_type": "VERSION",
"id": 4733,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "postgresql 15",
"alias_type": "VERSION",
"id": 4734,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "postgresql 16",
"alias_type": "VERSION",
"id": 4735,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "postgresql-16",
"alias_type": "VERSION",
"id": 4736,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "postgresql10",
"alias_type": "VERSION",
"id": 4722,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "postgresql11",
"alias_type": "VERSION",
"id": 4723,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "postgresql12",
"alias_type": "VERSION",
"id": 4724,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "postgresql13",
"alias_type": "VERSION",
"id": 4725,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "postgresql14",
"alias_type": "VERSION",
"id": 4726,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "postgresql15",
"alias_type": "VERSION",
"id": 4727,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "postgresql16",
"alias_type": "VERSION",
"id": 4728,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
}
],
"canonical": {
"category_id": 3,
"display_name": "PostgreSQL",
"id": 16,
"is_also_category": false,
"is_extractable": true,
"skill_nature": "TOOL",
"slug": "postgresql",
"sub_category_id": 29,
"typical_lifespan": "EVERGREEN",
"volatility": "STABLE"
},
"dimensions": [
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Relational Data Modeling",
"id": 216,
"rationale": "Modeling and tuning relational persistence for backend features. PHP backend developers need this to shape schemas, indexes, transactions, and query-aware data structures that support application behavior.",
"slug": "relational-data-modeling",
"source": "db"
},
"input_skill": "PostgreSQL",
"llm_role": null,
"roles_from_db": [
{
"display_name": "Fullstack Developer",
"id": 15,
"rationale": null,
"role_archetype": null,
"slug": "full-stack-engineer",
"source": "db"
},
{
"display_name": "Fullstack Developer",
"id": 435,
"rationale": null,
"role_archetype": "Engineering",
"slug": "fullstack-developer",
"source": "db"
},
{
"display_name": "PHP Backend Developer",
"id": 86,
"rationale": null,
"role_archetype": "Engineering",
"slug": "php-backend-developer",
"source": "db"
}
]
},
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Relational Database Design",
"id": 4,
"rationale": "Modeling and operating relational persistence for backend services. Includes schema design, normalization, indexing, transactions, and query tuning for operational data stores.",
"slug": "relational-database-design",
"source": "db"
},
"input_skill": "PostgreSQL",
"llm_role": null,
"roles_from_db": [
{
"display_name": ".NET Backend Developer",
"id": 83,
"rationale": null,
"role_archetype": "Engineering",
"slug": "dotnet-backend-developer",
"source": "db"
},
{
"display_name": "Backend Developer",
"id": 1,
"rationale": null,
"role_archetype": "A Backend Engineer designs, builds, and maintains the server-side logic and data handling that power applications and services. They focus on implementing reliable business functionality, integrating with other systems, and ensuring the backend is scalable, maintainable, and observable.",
"slug": "backend-engineer",
"source": "db"
},
{
"display_name": "Kotlin Backend Developer",
"id": 84,
"rationale": null,
"role_archetype": "Engineering",
"slug": "kotlin-server-backend-developer",
"source": "db"
},
{
"display_name": "Node.js Backend Developer",
"id": 82,
"rationale": null,
"role_archetype": "Engineering",
"slug": "node-backend-developer",
"source": "db"
},
{
"display_name": "Python Backend Developer",
"id": 80,
"rationale": null,
"role_archetype": "Engineering",
"slug": "python-backend-developer",
"source": "db"
},
{
"display_name": "Ruby Backend Developer",
"id": 85,
"rationale": null,
"role_archetype": "Engineering",
"slug": "ruby-backend-developer",
"source": "db"
},
{
"display_name": "Scala Backend Developer",
"id": 87,
"rationale": null,
"role_archetype": "Engineering",
"slug": "scala-backend-developer",
"source": "db"
}
]
},
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Relational Database Usage",
"id": 371,
"rationale": "Working effectively with operational relational databases from Go backend services. This includes schema-aware querying, indexing awareness, transactions, and understanding how service code interacts with PostgreSQL or similar systems.",
"slug": "relational-database-usage",
"source": "db"
},
"input_skill": "PostgreSQL",
"llm_role": null,
"roles_from_db": [
{
"display_name": "Go Backend Developer",
"id": 81,
"rationale": null,
"role_archetype": "Engineering",
"slug": "go-backend-developer",
"source": "db"
}
]
}
],
"input_skill": "PostgreSQL",
"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": 183,
"is_primary": true,
"match_strategy": "CASE_INSENSITIVE"
}
],
"canonical": {
"category_id": 9,
"display_name": "Prometheus",
"id": 46,
"is_also_category": false,
"is_extractable": true,
"skill_nature": "PLATFORM",
"slug": "prometheus",
"sub_category_id": 2837,
"typical_lifespan": "EVERGREEN",
"volatility": "STABLE"
},
"dimensions": [
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Backend Observability, Logging, and Diagnostics",
"id": 388,
"rationale": "Instrumentation and troubleshooting practices used to understand and improve backend service behavior in production and lower environments. This includes logs, metrics, traces, alerting, dashboards, structured logging, distributed tracing, health checks, and root-cause analysis using ecosystem-specific tools such as SLF4J, Logback, Micrometer, OpenTelemetry, Prometheus, Grafana, ILogger, Serilog, and Application Insights.",
"slug": "backend-observability-logging-and-diagnostics",
"source": "db"
},
"input_skill": "Prometheus",
"llm_role": null,
"roles_from_db": [
{
"display_name": "Kotlin Backend Developer",
"id": 84,
"rationale": null,
"role_archetype": "Engineering",
"slug": "kotlin-server-backend-developer",
"source": "db"
},
{
"display_name": "Scala Backend Developer",
"id": 87,
"rationale": null,
"role_archetype": "Engineering",
"slug": "scala-backend-developer",
"source": "db"
}
]
},
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Observability and Incident Response",
"id": 10,
"rationale": "Instrumentation and production troubleshooting practices used to keep backend services reliable. Includes logs, metrics, traces, alerting, dashboards, and incident diagnosis.",
"slug": "observability-and-incident-response",
"source": "db"
},
"input_skill": "Prometheus",
"llm_role": null,
"roles_from_db": [
{
"display_name": ".NET Backend Developer",
"id": 83,
"rationale": null,
"role_archetype": "Engineering",
"slug": "dotnet-backend-developer",
"source": "db"
},
{
"display_name": "Backend Developer",
"id": 1,
"rationale": null,
"role_archetype": "A Backend Engineer designs, builds, and maintains the server-side logic and data handling that power applications and services. They focus on implementing reliable business functionality, integrating with other systems, and ensuring the backend is scalable, maintainable, and observable.",
"slug": "backend-engineer",
"source": "db"
},
{
"display_name": "Node.js Backend Developer",
"id": 82,
"rationale": null,
"role_archetype": "Engineering",
"slug": "node-backend-developer",
"source": "db"
},
{
"display_name": "PHP Backend Developer",
"id": 86,
"rationale": null,
"role_archetype": "Engineering",
"slug": "php-backend-developer",
"source": "db"
}
]
},
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Observability and Incident Triage",
"id": 155,
"rationale": "Telemetry, alerting, and troubleshooting practices used to diagnose failed builds, broken deployments, and unhealthy release environments. This is a coherent cluster because delivery reliability depends on quickly identifying where the workflow failed.",
"slug": "observability-and-incident-triage",
"source": "db"
},
"input_skill": "Prometheus",
"llm_role": null,
"roles_from_db": [
{
"display_name": "DevOps Engineer",
"id": 10,
"rationale": null,
"role_archetype": null,
"slug": "devops-engineer",
"source": "db"
}
]
},
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Observability and Operations",
"id": 143,
"rationale": "Monitoring, logging, tracing, and operational readiness patterns used to keep cloud platforms supportable. Cloud Architects use this to define what telemetry and operational controls workloads must expose.",
"slug": "observability-and-operations",
"source": "db"
},
"input_skill": "Prometheus",
"llm_role": null,
"roles_from_db": [
{
"display_name": "Cloud Architect",
"id": 9,
"rationale": null,
"role_archetype": null,
"slug": "cloud-architect",
"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": [],
"canonical": null,
"dimensions": [],
"input_skill": "Kibana",
"matched_via": null,
"new_alias_persisted": false,
"new_alias_text": null,
"new_skill_meta": {
"derived": {
"category": "Monitoring Tools",
"skill_nature": "TOOL",
"sub_category": "general",
"typical_lifespan": "MULTI_YEAR",
"version_strategy": "UNVERSIONED",
"volatility": "MEDIUM"
},
"enrichment": null,
"keep_log": [],
"locked_dimensions": [],
"merge_log": [],
"placed": null,
"relationships": null,
"skill_id": "kibana",
"split_log": [],
"typed": null,
"warnings": []
},
"source_tag": "llm",
"was_in_llm_skills": true
},
{
"aliases_in_db": [
{
"alias_text": "Grafana",
"alias_type": "CANONICAL",
"id": 184,
"is_primary": true,
"match_strategy": "CASE_INSENSITIVE"
}
],
"canonical": {
"category_id": 9,
"display_name": "Grafana",
"id": 47,
"is_also_category": false,
"is_extractable": true,
"skill_nature": "PLATFORM",
"slug": "grafana",
"sub_category_id": 176,
"typical_lifespan": "EVERGREEN",
"volatility": "STABLE"
},
"dimensions": [
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Backend Observability, Logging, and Diagnostics",
"id": 388,
"rationale": "Instrumentation and troubleshooting practices used to understand and improve backend service behavior in production and lower environments. This includes logs, metrics, traces, alerting, dashboards, structured logging, distributed tracing, health checks, and root-cause analysis using ecosystem-specific tools such as SLF4J, Logback, Micrometer, OpenTelemetry, Prometheus, Grafana, ILogger, Serilog, and Application Insights.",
"slug": "backend-observability-logging-and-diagnostics",
"source": "db"
},
"input_skill": "Grafana",
"llm_role": null,
"roles_from_db": [
{
"display_name": "Kotlin Backend Developer",
"id": 84,
"rationale": null,
"role_archetype": "Engineering",
"slug": "kotlin-server-backend-developer",
"source": "db"
},
{
"display_name": "Scala Backend Developer",
"id": 87,
"rationale": null,
"role_archetype": "Engineering",
"slug": "scala-backend-developer",
"source": "db"
}
]
},
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Observability and Incident Response",
"id": 10,
"rationale": "Instrumentation and production troubleshooting practices used to keep backend services reliable. Includes logs, metrics, traces, alerting, dashboards, and incident diagnosis.",
"slug": "observability-and-incident-response",
"source": "db"
},
"input_skill": "Grafana",
"llm_role": null,
"roles_from_db": [
{
"display_name": ".NET Backend Developer",
"id": 83,
"rationale": null,
"role_archetype": "Engineering",
"slug": "dotnet-backend-developer",
"source": "db"
},
{
"display_name": "Backend Developer",
"id": 1,
"rationale": null,
"role_archetype": "A Backend Engineer designs, builds, and maintains the server-side logic and data handling that power applications and services. They focus on implementing reliable business functionality, integrating with other systems, and ensuring the backend is scalable, maintainable, and observable.",
"slug": "backend-engineer",
"source": "db"
},
{
"display_name": "Node.js Backend Developer",
"id": 82,
"rationale": null,
"role_archetype": "Engineering",
"slug": "node-backend-developer",
"source": "db"
},
{
"display_name": "PHP Backend Developer",
"id": 86,
"rationale": null,
"role_archetype": "Engineering",
"slug": "php-backend-developer",
"source": "db"
}
]
},
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Observability and Incident Triage",
"id": 155,
"rationale": "Telemetry, alerting, and troubleshooting practices used to diagnose failed builds, broken deployments, and unhealthy release environments. This is a coherent cluster because delivery reliability depends on quickly identifying where the workflow failed.",
"slug": "observability-and-incident-triage",
"source": "db"
},
"input_skill": "Grafana",
"llm_role": null,
"roles_from_db": [
{
"display_name": "DevOps Engineer",
"id": 10,
"rationale": null,
"role_archetype": null,
"slug": "devops-engineer",
"source": "db"
}
]
},
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Observability and Operations",
"id": 143,
"rationale": "Monitoring, logging, tracing, and operational readiness patterns used to keep cloud platforms supportable. Cloud Architects use this to define what telemetry and operational controls workloads must expose.",
"slug": "observability-and-operations",
"source": "db"
},
"input_skill": "Grafana",
"llm_role": null,
"roles_from_db": [
{
"display_name": "Cloud Architect",
"id": 9,
"rationale": null,
"role_archetype": null,
"slug": "cloud-architect",
"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": [],
"canonical": null,
"dimensions": [],
"input_skill": "Apache Maven",
"matched_via": null,
"new_alias_persisted": false,
"new_alias_text": null,
"new_skill_meta": {
"derived": {
"category": "Build Tools",
"skill_nature": "TOOL",
"sub_category": "general",
"typical_lifespan": "MULTI_YEAR",
"version_strategy": "UNVERSIONED",
"volatility": "MEDIUM"
},
"enrichment": null,
"keep_log": [],
"locked_dimensions": [],
"merge_log": [],
"placed": null,
"relationships": null,
"skill_id": "apache-maven",
"split_log": [],
"typed": null,
"warnings": []
},
"source_tag": "llm",
"was_in_llm_skills": true
},
{
"aliases_in_db": [
{
"alias_text": "Apache Kafka",
"alias_type": "CANONICAL",
"id": 349,
"is_primary": true,
"match_strategy": "CASE_INSENSITIVE"
}
],
"canonical": {
"category_id": 13,
"display_name": "Apache Kafka",
"id": 145,
"is_also_category": false,
"is_extractable": true,
"skill_nature": "TOOL",
"slug": "apache-kafka",
"sub_category_id": 128,
"typical_lifespan": "EVERGREEN",
"volatility": "STABLE"
},
"dimensions": [
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Messaging and Event Streaming",
"id": 8,
"rationale": "Transport-layer systems used to move events and decouple producers from consumers. Data engineers use these systems to ingest, buffer, and distribute event data before downstream processing.",
"slug": "messaging-and-event-streaming",
"source": "db"
},
"input_skill": "Apache Kafka",
"llm_role": null,
"roles_from_db": [
{
"display_name": "Backend Developer",
"id": 1,
"rationale": null,
"role_archetype": "A Backend Engineer designs, builds, and maintains the server-side logic and data handling that power applications and services. They focus on implementing reliable business functionality, integrating with other systems, and ensuring the backend is scalable, maintainable, and observable.",
"slug": "backend-engineer",
"source": "db"
},
{
"display_name": "Data Engineer",
"id": 2,
"rationale": null,
"role_archetype": null,
"slug": "data-engineer",
"source": "db"
}
]
}
],
"input_skill": "Apache 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": [],
"canonical": null,
"dimensions": [],
"input_skill": "Continuous Delivery",
"matched_via": null,
"new_alias_persisted": false,
"new_alias_text": null,
"new_skill_meta": {
"derived": {
"category": "DevOps Tools",
"skill_nature": "PRACTICE",
"sub_category": "general",
"typical_lifespan": "MULTI_YEAR",
"version_strategy": "UNVERSIONED",
"volatility": "MEDIUM"
},
"enrichment": null,
"keep_log": [],
"locked_dimensions": [],
"merge_log": [],
"placed": null,
"relationships": null,
"skill_id": "continuous-delivery",
"split_log": [],
"typed": null,
"warnings": []
},
"source_tag": "llm",
"was_in_llm_skills": true
},
{
"aliases_in_db": [],
"canonical": null,
"dimensions": [],
"input_skill": "BDD",
"matched_via": null,
"new_alias_persisted": false,
"new_alias_text": null,
"new_skill_meta": {
"derived": {
"category": "Software Development Practices",
"skill_nature": "PRACTICE",
"sub_category": "general",
"typical_lifespan": "MULTI_YEAR",
"version_strategy": "UNVERSIONED",
"volatility": "MEDIUM"
},
"enrichment": null,
"keep_log": [],
"locked_dimensions": [],
"merge_log": [],
"placed": null,
"relationships": null,
"skill_id": "bdd",
"split_log": [],
"typed": null,
"warnings": []
},
"source_tag": "llm",
"was_in_llm_skills": true
},
{
"aliases_in_db": [
{
"alias_text": "REST",
"alias_type": "CANONICAL",
"id": 106,
"is_primary": true,
"match_strategy": "CASE_INSENSITIVE"
}
],
"canonical": {
"category_id": 2,
"display_name": "REST",
"id": 11,
"is_also_category": false,
"is_extractable": true,
"skill_nature": "CONCEPT",
"slug": "rest",
"sub_category_id": 2122,
"typical_lifespan": "EVERGREEN",
"volatility": "STABLE"
},
"dimensions": [
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "API Design and Contracts",
"id": 3,
"rationale": "Designing request/response shapes and the rules that govern client-server interaction. This cluster is coherent because full stack engineers often own the contract between UI behavior and backend implementation.",
"slug": "api-design-and-contracts",
"source": "db"
},
"input_skill": "REST",
"llm_role": null,
"roles_from_db": [
{
"display_name": "Backend Developer",
"id": 1,
"rationale": null,
"role_archetype": "A Backend Engineer designs, builds, and maintains the server-side logic and data handling that power applications and services. They focus on implementing reliable business functionality, integrating with other systems, and ensuring the backend is scalable, maintainable, and observable.",
"slug": "backend-engineer",
"source": "db"
},
{
"display_name": "Fullstack Developer",
"id": 15,
"rationale": null,
"role_archetype": null,
"slug": "full-stack-engineer",
"source": "db"
}
]
},
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "API Interface and Contract Design",
"id": 289,
"rationale": "Designing backend service interfaces and contracts that other systems consume, including endpoint and operation shape, request/response payloads, schema and validation, pagination, filtering, idempotency, versioning, status codes, and backward compatibility across REST, GraphQL, gRPC, and OpenAPI-based APIs.",
"slug": "api-interface-and-contract-design",
"source": "db"
},
"input_skill": "REST",
"llm_role": null,
"roles_from_db": [
{
"display_name": ".NET Backend Developer",
"id": 83,
"rationale": null,
"role_archetype": "Engineering",
"slug": "dotnet-backend-developer",
"source": "db"
},
{
"display_name": "Go Backend Developer",
"id": 81,
"rationale": null,
"role_archetype": "Engineering",
"slug": "go-backend-developer",
"source": "db"
},
{
"display_name": "Kotlin Backend Developer",
"id": 84,
"rationale": null,
"role_archetype": "Engineering",
"slug": "kotlin-server-backend-developer",
"source": "db"
},
{
"display_name": "Node.js Backend Developer",
"id": 82,
"rationale": null,
"role_archetype": "Engineering",
"slug": "node-backend-developer",
"source": "db"
},
{
"display_name": "PHP Backend Developer",
"id": 86,
"rationale": null,
"role_archetype": "Engineering",
"slug": "php-backend-developer",
"source": "db"
},
{
"display_name": "Python Backend Developer",
"id": 80,
"rationale": null,
"role_archetype": "Engineering",
"slug": "python-backend-developer",
"source": "db"
},
{
"display_name": "Ruby Backend Developer",
"id": 85,
"rationale": null,
"role_archetype": "Engineering",
"slug": "ruby-backend-developer",
"source": "db"
},
{
"display_name": "Scala Backend Developer",
"id": 87,
"rationale": null,
"role_archetype": "Engineering",
"slug": "scala-backend-developer",
"source": "db"
}
]
},
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Integration Protocols \u0026 Standards",
"id": 271,
"rationale": "Standards and protocols for integrating Pega applications.",
"slug": "integration-protocols-standards",
"source": "db"
},
"input_skill": "REST",
"llm_role": null,
"roles_from_db": [
{
"display_name": "Pega Developer",
"id": 24,
"rationale": null,
"role_archetype": null,
"slug": "pega-developer",
"source": "db"
}
]
},
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Standards \u0026 Protocols Compliance",
"id": 452,
"rationale": "Encompasses key web and data standards, protocols, and compliance requirements relevant to Sitecore implementations.",
"slug": "standards-protocols-compliance",
"source": "db"
},
"input_skill": "REST",
"llm_role": null,
"roles_from_db": [
{
"display_name": "Sitecore Dev",
"id": 233,
"rationale": null,
"role_archetype": "Engineering",
"slug": "sitecore-dev",
"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
}
],
"unmatched_skills": [
"Dropwizard",
"Jetty",
"Jersey",
"Netflix Hystrix",
"Zipkin",
"Kibana",
"Apache Maven",
"Continuous Delivery",
"BDD"
]
}
API 3 — final-role-output
{
"chosen_role": {
"display_name": "Backend Developer",
"id": 1,
"rationale": "Domain=Software Engineering \u2192 sub-role java-backend-developer; The JD is centered on Java microservices, REST APIs, CI/CD, Docker/Kubernetes, and backend integration work, which best matches Backend Developer.",
"role_archetype": "A Backend Engineer designs, builds, and maintains the server-side logic and data handling that power applications and services. They focus on implementing reliable business functionality, integrating with other systems, and ensuring the backend is scalable, maintainable, and observable.",
"slug": "backend-engineer",
"source": "db"
},
"chosen_role_resolution": "in_db",
"final_input_skills": [
{
"skill": "Java",
"tag": "in_db"
},
{
"skill": "Microservices",
"tag": "in_db"
},
{
"skill": "Git",
"tag": "in_db"
},
{
"skill": "Agile",
"tag": "in_db"
},
{
"skill": "Docker",
"tag": "in_db"
},
{
"skill": "Kubernetes",
"tag": "in_db"
},
{
"skill": "Spring",
"tag": "in_db"
},
{
"skill": "Dropwizard",
"tag": "new"
},
{
"skill": "Jetty",
"tag": "new"
},
{
"skill": "Jersey",
"tag": "new"
},
{
"skill": "Netflix Hystrix",
"tag": "new"
},
{
"skill": "Zipkin",
"tag": "new"
},
{
"skill": "PostgreSQL",
"tag": "in_db"
},
{
"skill": "Prometheus",
"tag": "in_db"
},
{
"skill": "Kibana",
"tag": "new"
},
{
"skill": "Grafana",
"tag": "in_db"
},
{
"skill": "Apache Maven",
"tag": "new"
},
{
"skill": "Apache Kafka",
"tag": "in_db"
},
{
"skill": "Continuous Delivery",
"tag": "new"
},
{
"skill": "BDD",
"tag": "new"
},
{
"skill": "REST",
"tag": "in_db"
}
],
"llm_cost_api1_usd": null,
"llm_cost_api2_usd": null,
"llm_cost_api3_usd": null,
"llm_cost_total_usd": null,
"persistence": {
"items": [
{
"chosen_role_id": 1,
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Java Language and JVM",
"id": 279,
"rationale": "Core Java implementation skills used to build backend service logic, utilities, and internal abstractions. This is the primary coding surface for the role and includes language features plus JVM behavior that affect correctness and maintainability.",
"slug": "java-language-and-jvm",
"source": "db"
},
"dimension_id": 279,
"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": "Java Backend Developer",
"id": 79,
"rationale": null,
"role_archetype": "Engineering",
"slug": "java-backend-developer",
"source": "db"
},
{
"display_name": "Kotlin Backend Developer",
"id": 84,
"rationale": null,
"role_archetype": "Engineering",
"slug": "kotlin-server-backend-developer",
"source": "db"
},
{
"display_name": "Scala Backend Developer",
"id": 87,
"rationale": null,
"role_archetype": "Engineering",
"slug": "scala-backend-developer",
"source": "db"
}
],
"skill_dimension_saved": true,
"skill_id": 1,
"skill_tag": "in_db",
"skipped_reason": null
},
{
"chosen_role_id": 1,
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Kotlin and Java",
"id": 161,
"rationale": "Primary implementation languages for Android app features, platform integration, and client-side business logic. Android engineers use these languages to build screens, state flows, service adapters, and device-aware behavior.",
"slug": "kotlin-and-java",
"source": "db"
},
"dimension_id": 161,
"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": "Android Developer",
"id": 4,
"rationale": null,
"role_archetype": null,
"slug": "android-engineer",
"source": "db"
}
],
"skill_dimension_saved": true,
"skill_id": 1,
"skill_tag": "in_db",
"skipped_reason": null
},
{
"chosen_role_id": 1,
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Native Mobile Languages",
"id": 274,
"rationale": "Primary implementation languages used to build platform-specific app features, UI logic, and device integrations. This is the core coding surface for native mobile work on one platform.",
"slug": "native-mobile-languages",
"source": "db"
},
"dimension_id": 274,
"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": "Native Mobile Developer",
"id": 75,
"rationale": null,
"role_archetype": "Engineering",
"slug": "native-mobile-developer",
"source": "db"
}
],
"skill_dimension_saved": true,
"skill_id": 1,
"skill_tag": "in_db",
"skipped_reason": null
},
{
"chosen_role_id": 1,
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Pega Programming Languages \u0026 DSLs",
"id": 267,
"rationale": "Programming languages and domain-specific languages used in Pega development.",
"slug": "pega-programming-languages-dsls",
"source": "db"
},
"dimension_id": 267,
"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": "Pega Developer",
"id": 24,
"rationale": null,
"role_archetype": null,
"slug": "pega-developer",
"source": "db"
}
],
"skill_dimension_saved": true,
"skill_id": 1,
"skill_tag": "in_db",
"skipped_reason": null
},
{
"chosen_role_id": 1,
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Programming Languages",
"id": 1,
"rationale": "Primary implementation languages used to build client and server feature code. Full stack engineers need enough fluency to move across layers and implement product behavior end to end.",
"slug": "programming-languages",
"source": "db"
},
"dimension_id": 1,
"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 Developer",
"id": 1,
"rationale": null,
"role_archetype": "A Backend Engineer designs, builds, and maintains the server-side logic and data handling that power applications and services. They focus on implementing reliable business functionality, integrating with other systems, and ensuring the backend is scalable, maintainable, and observable.",
"slug": "backend-engineer",
"source": "db"
},
{
"display_name": "Fullstack Developer",
"id": 435,
"rationale": null,
"role_archetype": "Engineering",
"slug": "fullstack-developer",
"source": "db"
},
{
"display_name": "Fullstack Developer",
"id": 15,
"rationale": null,
"role_archetype": null,
"slug": "full-stack-engineer",
"source": "db"
}
],
"skill_dimension_saved": true,
"skill_id": 1,
"skill_tag": "in_db",
"skipped_reason": null
},
{
"chosen_role_id": 1,
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Programming Languages for Data Work",
"id": 21,
"rationale": "Languages used to implement data pipelines, transformations, and operational glue. This is the primary coding surface for building ingestion, enrichment, and automation logic in data engineering.",
"slug": "programming-languages-for-data-work",
"source": "db"
},
"dimension_id": 21,
"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": 2,
"rationale": null,
"role_archetype": null,
"slug": "data-engineer",
"source": "db"
}
],
"skill_dimension_saved": true,
"skill_id": 1,
"skill_tag": "in_db",
"skipped_reason": null
},
{
"chosen_role_id": 1,
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Microservices and Distributed Systems",
"id": 9,
"rationale": "Architectural patterns for decomposed backend systems and the operational concerns they introduce. Covers service boundaries, consistency tradeoffs, retries, circuit breakers, and distributed coordination.",
"slug": "microservices-and-distributed-systems",
"source": "db"
},
"dimension_id": 9,
"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 Developer",
"id": 1,
"rationale": null,
"role_archetype": "A Backend Engineer designs, builds, and maintains the server-side logic and data handling that power applications and services. They focus on implementing reliable business functionality, integrating with other systems, and ensuring the backend is scalable, maintainable, and observable.",
"slug": "backend-engineer",
"source": "db"
},
{
"display_name": "Node.js Backend Developer",
"id": 82,
"rationale": null,
"role_archetype": "Engineering",
"slug": "node-backend-developer",
"source": "db"
},
{
"display_name": "Scala Backend Developer",
"id": 87,
"rationale": null,
"role_archetype": "Engineering",
"slug": "scala-backend-developer",
"source": "db"
}
],
"skill_dimension_saved": true,
"skill_id": 41,
"skill_tag": "in_db",
"skipped_reason": null
},
{
"chosen_role_id": 1,
"dimension": {
"difficulty_hint": "well_known",
"display_name": "React Frontend Development",
"id": 96,
"rationale": "Building interactive web user interfaces with React.js, including component composition, state management, hooks, and rendering patterns. React.js belongs here because it is a core library for client-side UI development in modern web applications.",
"slug": "d_init_01",
"source": "db"
},
"dimension_id": 96,
"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": 1002,
"skill_tag": "in_db",
"skipped_reason": null
},
{
"chosen_role_id": 1,
"dimension": {
"difficulty_hint": "well_known",
"display_name": "React Frontend Development",
"id": 96,
"rationale": "Building interactive web user interfaces with React.js, including component composition, state management, hooks, and rendering patterns. React.js belongs here because it is a core library for client-side UI development in modern web applications.",
"slug": "d_init_01",
"source": "db"
},
"dimension_id": 96,
"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": 520,
"skill_tag": "in_db",
"skipped_reason": null
},
{
"chosen_role_id": 1,
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Containerization and Image Builds",
"id": 152,
"rationale": "Container image creation, tagging, hardening, and registry workflows used to package services for deployment. This is coherent because DevOps often owns the build-to-image path that feeds runtime environments.",
"slug": "containerization-and-image-builds",
"source": "db"
},
"dimension_id": 152,
"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": 10,
"rationale": null,
"role_archetype": null,
"slug": "devops-engineer",
"source": "db"
}
],
"skill_dimension_saved": true,
"skill_id": 61,
"skill_tag": "in_db",
"skipped_reason": null
},
{
"chosen_role_id": 1,
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Deployment and Cloud Platforms",
"id": 418,
"rationale": "Platform-as-a-Service and container environments for deploying Ruby applications.",
"slug": "deployment-and-cloud-platforms",
"source": "db"
},
"dimension_id": 418,
"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": "Ruby Backend Developer",
"id": 85,
"rationale": null,
"role_archetype": "Engineering",
"slug": "ruby-backend-developer",
"source": "db"
}
],
"skill_dimension_saved": true,
"skill_id": 61,
"skill_tag": "in_db",
"skipped_reason": null
},
{
"chosen_role_id": 1,
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Deployment and Runtime Configuration",
"id": 13,
"rationale": "Configuration and release artifacts that control how backend services run in environments. Includes environment variables, manifests, feature flags, and release-safe configuration management.",
"slug": "deployment-and-runtime-configuration",
"source": "db"
},
"dimension_id": 13,
"input_skill": "Docker",
"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": ".NET Backend Developer",
"id": 83,
"rationale": null,
"role_archetype": "Engineering",
"slug": "dotnet-backend-developer",
"source": "db"
},
{
"display_name": "Backend Developer",
"id": 1,
"rationale": null,
"role_archetype": "A Backend Engineer designs, builds, and maintains the server-side logic and data handling that power applications and services. They focus on implementing reliable business functionality, integrating with other systems, and ensuring the backend is scalable, maintainable, and observable.",
"slug": "backend-engineer",
"source": "db"
},
{
"display_name": "Go Backend Developer",
"id": 81,
"rationale": null,
"role_archetype": "Engineering",
"slug": "go-backend-developer",
"source": "db"
},
{
"display_name": "PHP Backend Developer",
"id": 86,
"rationale": null,
"role_archetype": "Engineering",
"slug": "php-backend-developer",
"source": "db"
}
],
"skill_dimension_saved": true,
"skill_id": 61,
"skill_tag": "in_db",
"skipped_reason": null
},
{
"chosen_role_id": 1,
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Container Orchestration Platforms",
"id": 134,
"rationale": "Platforms that schedule and manage containerized workloads across clusters and environments. Cloud Architects need these to define workload placement standards, cluster boundaries, and platform capabilities.",
"slug": "container-orchestration-platforms",
"source": "db"
},
"dimension_id": 134,
"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 Architect",
"id": 9,
"rationale": null,
"role_archetype": null,
"slug": "cloud-architect",
"source": "db"
},
{
"display_name": "DevOps Engineer",
"id": 10,
"rationale": null,
"role_archetype": null,
"slug": "devops-engineer",
"source": "db"
}
],
"skill_dimension_saved": true,
"skill_id": 726,
"skill_tag": "in_db",
"skipped_reason": null
},
{
"chosen_role_id": 1,
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Kubernetes for ML Workloads",
"id": 47,
"rationale": "Kubernetes-native components used to schedule, accelerate, and isolate ML training and serving workloads. This includes GPU enablement and ML-specific controllers rather than generic cluster administration.",
"slug": "kubernetes-for-ml-workloads",
"source": "db"
},
"dimension_id": 47,
"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": "ML Engineer",
"id": 3,
"rationale": null,
"role_archetype": null,
"slug": "ml-engineer",
"source": "db"
},
{
"display_name": "MLOps Engineer",
"id": 16,
"rationale": null,
"role_archetype": null,
"slug": "ml-ops-engineer",
"source": "db"
}
],
"skill_dimension_saved": true,
"skill_id": 726,
"skill_tag": "in_db",
"skipped_reason": null
},
{
"chosen_role_id": 1,
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Web Application Frameworks",
"id": 2,
"rationale": "Server frameworks and runtimes used to build HTTP services, controllers, middleware, and request pipelines. These frameworks shape how backend endpoints are structured and delivered.",
"slug": "web-application-frameworks",
"source": "db"
},
"dimension_id": 2,
"input_skill": "Spring",
"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 Developer",
"id": 1,
"rationale": null,
"role_archetype": "A Backend Engineer designs, builds, and maintains the server-side logic and data handling that power applications and services. They focus on implementing reliable business functionality, integrating with other systems, and ensuring the backend is scalable, maintainable, and observable.",
"slug": "backend-engineer",
"source": "db"
},
{
"display_name": "Fullstack Developer",
"id": 435,
"rationale": null,
"role_archetype": "Engineering",
"slug": "fullstack-developer",
"source": "db"
},
{
"display_name": "Fullstack Developer",
"id": 15,
"rationale": null,
"role_archetype": null,
"slug": "full-stack-engineer",
"source": "db"
},
{
"display_name": "Java Backend Developer",
"id": 79,
"rationale": null,
"role_archetype": "Engineering",
"slug": "java-backend-developer",
"source": "db"
},
{
"display_name": "Node.js Backend Developer",
"id": 82,
"rationale": null,
"role_archetype": "Engineering",
"slug": "node-backend-developer",
"source": "db"
},
{
"display_name": "PHP Backend Developer",
"id": 86,
"rationale": null,
"role_archetype": "Engineering",
"slug": "php-backend-developer",
"source": "db"
},
{
"display_name": "Python Backend Developer",
"id": 80,
"rationale": null,
"role_archetype": "Engineering",
"slug": "python-backend-developer",
"source": "db"
}
],
"skill_dimension_saved": true,
"skill_id": 1630,
"skill_tag": "in_db",
"skipped_reason": null
},
{
"chosen_role_id": 1,
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Relational Data Modeling",
"id": 216,
"rationale": "Modeling and tuning relational persistence for backend features. PHP backend developers need this to shape schemas, indexes, transactions, and query-aware data structures that support application behavior.",
"slug": "relational-data-modeling",
"source": "db"
},
"dimension_id": 216,
"input_skill": "PostgreSQL",
"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": "Fullstack Developer",
"id": 15,
"rationale": null,
"role_archetype": null,
"slug": "full-stack-engineer",
"source": "db"
},
{
"display_name": "Fullstack Developer",
"id": 435,
"rationale": null,
"role_archetype": "Engineering",
"slug": "fullstack-developer",
"source": "db"
},
{
"display_name": "PHP Backend Developer",
"id": 86,
"rationale": null,
"role_archetype": "Engineering",
"slug": "php-backend-developer",
"source": "db"
}
],
"skill_dimension_saved": true,
"skill_id": 16,
"skill_tag": "in_db",
"skipped_reason": null
},
{
"chosen_role_id": 1,
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Relational Database Design",
"id": 4,
"rationale": "Modeling and operating relational persistence for backend services. Includes schema design, normalization, indexing, transactions, and query tuning for operational data stores.",
"slug": "relational-database-design",
"source": "db"
},
"dimension_id": 4,
"input_skill": "PostgreSQL",
"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": ".NET Backend Developer",
"id": 83,
"rationale": null,
"role_archetype": "Engineering",
"slug": "dotnet-backend-developer",
"source": "db"
},
{
"display_name": "Backend Developer",
"id": 1,
"rationale": null,
"role_archetype": "A Backend Engineer designs, builds, and maintains the server-side logic and data handling that power applications and services. They focus on implementing reliable business functionality, integrating with other systems, and ensuring the backend is scalable, maintainable, and observable.",
"slug": "backend-engineer",
"source": "db"
},
{
"display_name": "Kotlin Backend Developer",
"id": 84,
"rationale": null,
"role_archetype": "Engineering",
"slug": "kotlin-server-backend-developer",
"source": "db"
},
{
"display_name": "Node.js Backend Developer",
"id": 82,
"rationale": null,
"role_archetype": "Engineering",
"slug": "node-backend-developer",
"source": "db"
},
{
"display_name": "Python Backend Developer",
"id": 80,
"rationale": null,
"role_archetype": "Engineering",
"slug": "python-backend-developer",
"source": "db"
},
{
"display_name": "Ruby Backend Developer",
"id": 85,
"rationale": null,
"role_archetype": "Engineering",
"slug": "ruby-backend-developer",
"source": "db"
},
{
"display_name": "Scala Backend Developer",
"id": 87,
"rationale": null,
"role_archetype": "Engineering",
"slug": "scala-backend-developer",
"source": "db"
}
],
"skill_dimension_saved": true,
"skill_id": 16,
"skill_tag": "in_db",
"skipped_reason": null
},
{
"chosen_role_id": 1,
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Relational Database Usage",
"id": 371,
"rationale": "Working effectively with operational relational databases from Go backend services. This includes schema-aware querying, indexing awareness, transactions, and understanding how service code interacts with PostgreSQL or similar systems.",
"slug": "relational-database-usage",
"source": "db"
},
"dimension_id": 371,
"input_skill": "PostgreSQL",
"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": "Go Backend Developer",
"id": 81,
"rationale": null,
"role_archetype": "Engineering",
"slug": "go-backend-developer",
"source": "db"
}
],
"skill_dimension_saved": true,
"skill_id": 16,
"skill_tag": "in_db",
"skipped_reason": null
},
{
"chosen_role_id": 1,
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Backend Observability, Logging, and Diagnostics",
"id": 388,
"rationale": "Instrumentation and troubleshooting practices used to understand and improve backend service behavior in production and lower environments. This includes logs, metrics, traces, alerting, dashboards, structured logging, distributed tracing, health checks, and root-cause analysis using ecosystem-specific tools such as SLF4J, Logback, Micrometer, OpenTelemetry, Prometheus, Grafana, ILogger, Serilog, and Application Insights.",
"slug": "backend-observability-logging-and-diagnostics",
"source": "db"
},
"dimension_id": 388,
"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": "Kotlin Backend Developer",
"id": 84,
"rationale": null,
"role_archetype": "Engineering",
"slug": "kotlin-server-backend-developer",
"source": "db"
},
{
"display_name": "Scala Backend Developer",
"id": 87,
"rationale": null,
"role_archetype": "Engineering",
"slug": "scala-backend-developer",
"source": "db"
}
],
"skill_dimension_saved": true,
"skill_id": 46,
"skill_tag": "in_db",
"skipped_reason": null
},
{
"chosen_role_id": 1,
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Observability and Incident Response",
"id": 10,
"rationale": "Instrumentation and production troubleshooting practices used to keep backend services reliable. Includes logs, metrics, traces, alerting, dashboards, and incident diagnosis.",
"slug": "observability-and-incident-response",
"source": "db"
},
"dimension_id": 10,
"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": ".NET Backend Developer",
"id": 83,
"rationale": null,
"role_archetype": "Engineering",
"slug": "dotnet-backend-developer",
"source": "db"
},
{
"display_name": "Backend Developer",
"id": 1,
"rationale": null,
"role_archetype": "A Backend Engineer designs, builds, and maintains the server-side logic and data handling that power applications and services. They focus on implementing reliable business functionality, integrating with other systems, and ensuring the backend is scalable, maintainable, and observable.",
"slug": "backend-engineer",
"source": "db"
},
{
"display_name": "Node.js Backend Developer",
"id": 82,
"rationale": null,
"role_archetype": "Engineering",
"slug": "node-backend-developer",
"source": "db"
},
{
"display_name": "PHP Backend Developer",
"id": 86,
"rationale": null,
"role_archetype": "Engineering",
"slug": "php-backend-developer",
"source": "db"
}
],
"skill_dimension_saved": true,
"skill_id": 46,
"skill_tag": "in_db",
"skipped_reason": null
},
{
"chosen_role_id": 1,
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Observability and Incident Triage",
"id": 155,
"rationale": "Telemetry, alerting, and troubleshooting practices used to diagnose failed builds, broken deployments, and unhealthy release environments. This is a coherent cluster because delivery reliability depends on quickly identifying where the workflow failed.",
"slug": "observability-and-incident-triage",
"source": "db"
},
"dimension_id": 155,
"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": 10,
"rationale": null,
"role_archetype": null,
"slug": "devops-engineer",
"source": "db"
}
],
"skill_dimension_saved": true,
"skill_id": 46,
"skill_tag": "in_db",
"skipped_reason": null
},
{
"chosen_role_id": 1,
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Observability and Operations",
"id": 143,
"rationale": "Monitoring, logging, tracing, and operational readiness patterns used to keep cloud platforms supportable. Cloud Architects use this to define what telemetry and operational controls workloads must expose.",
"slug": "observability-and-operations",
"source": "db"
},
"dimension_id": 143,
"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": "Cloud Architect",
"id": 9,
"rationale": null,
"role_archetype": null,
"slug": "cloud-architect",
"source": "db"
}
],
"skill_dimension_saved": true,
"skill_id": 46,
"skill_tag": "in_db",
"skipped_reason": null
},
{
"chosen_role_id": 1,
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Backend Observability, Logging, and Diagnostics",
"id": 388,
"rationale": "Instrumentation and troubleshooting practices used to understand and improve backend service behavior in production and lower environments. This includes logs, metrics, traces, alerting, dashboards, structured logging, distributed tracing, health checks, and root-cause analysis using ecosystem-specific tools such as SLF4J, Logback, Micrometer, OpenTelemetry, Prometheus, Grafana, ILogger, Serilog, and Application Insights.",
"slug": "backend-observability-logging-and-diagnostics",
"source": "db"
},
"dimension_id": 388,
"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": "Kotlin Backend Developer",
"id": 84,
"rationale": null,
"role_archetype": "Engineering",
"slug": "kotlin-server-backend-developer",
"source": "db"
},
{
"display_name": "Scala Backend Developer",
"id": 87,
"rationale": null,
"role_archetype": "Engineering",
"slug": "scala-backend-developer",
"source": "db"
}
],
"skill_dimension_saved": true,
"skill_id": 47,
"skill_tag": "in_db",
"skipped_reason": null
},
{
"chosen_role_id": 1,
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Observability and Incident Response",
"id": 10,
"rationale": "Instrumentation and production troubleshooting practices used to keep backend services reliable. Includes logs, metrics, traces, alerting, dashboards, and incident diagnosis.",
"slug": "observability-and-incident-response",
"source": "db"
},
"dimension_id": 10,
"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": ".NET Backend Developer",
"id": 83,
"rationale": null,
"role_archetype": "Engineering",
"slug": "dotnet-backend-developer",
"source": "db"
},
{
"display_name": "Backend Developer",
"id": 1,
"rationale": null,
"role_archetype": "A Backend Engineer designs, builds, and maintains the server-side logic and data handling that power applications and services. They focus on implementing reliable business functionality, integrating with other systems, and ensuring the backend is scalable, maintainable, and observable.",
"slug": "backend-engineer",
"source": "db"
},
{
"display_name": "Node.js Backend Developer",
"id": 82,
"rationale": null,
"role_archetype": "Engineering",
"slug": "node-backend-developer",
"source": "db"
},
{
"display_name": "PHP Backend Developer",
"id": 86,
"rationale": null,
"role_archetype": "Engineering",
"slug": "php-backend-developer",
"source": "db"
}
],
"skill_dimension_saved": true,
"skill_id": 47,
"skill_tag": "in_db",
"skipped_reason": null
},
{
"chosen_role_id": 1,
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Observability and Incident Triage",
"id": 155,
"rationale": "Telemetry, alerting, and troubleshooting practices used to diagnose failed builds, broken deployments, and unhealthy release environments. This is a coherent cluster because delivery reliability depends on quickly identifying where the workflow failed.",
"slug": "observability-and-incident-triage",
"source": "db"
},
"dimension_id": 155,
"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": 10,
"rationale": null,
"role_archetype": null,
"slug": "devops-engineer",
"source": "db"
}
],
"skill_dimension_saved": true,
"skill_id": 47,
"skill_tag": "in_db",
"skipped_reason": null
},
{
"chosen_role_id": 1,
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Observability and Operations",
"id": 143,
"rationale": "Monitoring, logging, tracing, and operational readiness patterns used to keep cloud platforms supportable. Cloud Architects use this to define what telemetry and operational controls workloads must expose.",
"slug": "observability-and-operations",
"source": "db"
},
"dimension_id": 143,
"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": "Cloud Architect",
"id": 9,
"rationale": null,
"role_archetype": null,
"slug": "cloud-architect",
"source": "db"
}
],
"skill_dimension_saved": true,
"skill_id": 47,
"skill_tag": "in_db",
"skipped_reason": null
},
{
"chosen_role_id": 1,
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Messaging and Event Streaming",
"id": 8,
"rationale": "Transport-layer systems used to move events and decouple producers from consumers. Data engineers use these systems to ingest, buffer, and distribute event data before downstream processing.",
"slug": "messaging-and-event-streaming",
"source": "db"
},
"dimension_id": 8,
"input_skill": "Apache 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 Developer",
"id": 1,
"rationale": null,
"role_archetype": "A Backend Engineer designs, builds, and maintains the server-side logic and data handling that power applications and services. They focus on implementing reliable business functionality, integrating with other systems, and ensuring the backend is scalable, maintainable, and observable.",
"slug": "backend-engineer",
"source": "db"
},
{
"display_name": "Data Engineer",
"id": 2,
"rationale": null,
"role_archetype": null,
"slug": "data-engineer",
"source": "db"
}
],
"skill_dimension_saved": true,
"skill_id": 145,
"skill_tag": "in_db",
"skipped_reason": null
},
{
"chosen_role_id": 1,
"dimension": {
"difficulty_hint": "well_known",
"display_name": "API Design and Contracts",
"id": 3,
"rationale": "Designing request/response shapes and the rules that govern client-server interaction. This cluster is coherent because full stack engineers often own the contract between UI behavior and backend implementation.",
"slug": "api-design-and-contracts",
"source": "db"
},
"dimension_id": 3,
"input_skill": "REST",
"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 Developer",
"id": 1,
"rationale": null,
"role_archetype": "A Backend Engineer designs, builds, and maintains the server-side logic and data handling that power applications and services. They focus on implementing reliable business functionality, integrating with other systems, and ensuring the backend is scalable, maintainable, and observable.",
"slug": "backend-engineer",
"source": "db"
},
{
"display_name": "Fullstack Developer",
"id": 15,
"rationale": null,
"role_archetype": null,
"slug": "full-stack-engineer",
"source": "db"
}
],
"skill_dimension_saved": true,
"skill_id": 11,
"skill_tag": "in_db",
"skipped_reason": null
},
{
"chosen_role_id": 1,
"dimension": {
"difficulty_hint": "well_known",
"display_name": "API Interface and Contract Design",
"id": 289,
"rationale": "Designing backend service interfaces and contracts that other systems consume, including endpoint and operation shape, request/response payloads, schema and validation, pagination, filtering, idempotency, versioning, status codes, and backward compatibility across REST, GraphQL, gRPC, and OpenAPI-based APIs.",
"slug": "api-interface-and-contract-design",
"source": "db"
},
"dimension_id": 289,
"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": ".NET Backend Developer",
"id": 83,
"rationale": null,
"role_archetype": "Engineering",
"slug": "dotnet-backend-developer",
"source": "db"
},
{
"display_name": "Go Backend Developer",
"id": 81,
"rationale": null,
"role_archetype": "Engineering",
"slug": "go-backend-developer",
"source": "db"
},
{
"display_name": "Kotlin Backend Developer",
"id": 84,
"rationale": null,
"role_archetype": "Engineering",
"slug": "kotlin-server-backend-developer",
"source": "db"
},
{
"display_name": "Node.js Backend Developer",
"id": 82,
"rationale": null,
"role_archetype": "Engineering",
"slug": "node-backend-developer",
"source": "db"
},
{
"display_name": "PHP Backend Developer",
"id": 86,
"rationale": null,
"role_archetype": "Engineering",
"slug": "php-backend-developer",
"source": "db"
},
{
"display_name": "Python Backend Developer",
"id": 80,
"rationale": null,
"role_archetype": "Engineering",
"slug": "python-backend-developer",
"source": "db"
},
{
"display_name": "Ruby Backend Developer",
"id": 85,
"rationale": null,
"role_archetype": "Engineering",
"slug": "ruby-backend-developer",
"source": "db"
},
{
"display_name": "Scala Backend Developer",
"id": 87,
"rationale": null,
"role_archetype": "Engineering",
"slug": "scala-backend-developer",
"source": "db"
}
],
"skill_dimension_saved": true,
"skill_id": 11,
"skill_tag": "in_db",
"skipped_reason": null
},
{
"chosen_role_id": 1,
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Integration Protocols \u0026 Standards",
"id": 271,
"rationale": "Standards and protocols for integrating Pega applications.",
"slug": "integration-protocols-standards",
"source": "db"
},
"dimension_id": 271,
"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": "Pega Developer",
"id": 24,
"rationale": null,
"role_archetype": null,
"slug": "pega-developer",
"source": "db"
}
],
"skill_dimension_saved": true,
"skill_id": 11,
"skill_tag": "in_db",
"skipped_reason": null
},
{
"chosen_role_id": 1,
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Standards \u0026 Protocols Compliance",
"id": 452,
"rationale": "Encompasses key web and data standards, protocols, and compliance requirements relevant to Sitecore implementations.",
"slug": "standards-protocols-compliance",
"source": "db"
},
"dimension_id": 452,
"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": "Sitecore Dev",
"id": 233,
"rationale": null,
"role_archetype": "Engineering",
"slug": "sitecore-dev",
"source": "db"
}
],
"skill_dimension_saved": true,
"skill_id": 11,
"skill_tag": "in_db",
"skipped_reason": null
}
],
"new_skills_created": 0,
"role_dimension_saved": 0,
"skill_dimension_saved": 0,
"skipped": 0
},
"planner_output": null,
"run_id": "14665224-3376-48b7-92b4-7aed97ed2be8"
}
LLM Calls
Every model call made for this run, in pipeline order. Click a card to see the model's response.