Pipeline run
1a58e1db-36d7-4a29-b216-3d2e9f68b7e9
Client output enrichment
v2 Skill cluster · Nature of work · AI index · Tech stack maturity · Evidence · KRA description
role baseline loaded
sources · ai_index: jd · nature_of_work: no_kras · tech_stack_maturity: jd
Nature of work
no kras
Vague JD — no KRAs present to derive a specific nature of work.
Tech stack maturity
Mainstream Modern
AI index (0 = no AI use, 5 = totally AI-dependent · v2.1)
0.20 / 5
· Title match
✓ Has AI skill
· AI skill (primary)
· AI skill (secondary)
· On AI team
· Builds AI products
vocab breakdown (legacy)
Assistants (×1):
—
Frameworks (×2):
—
Models / concepts (×3):
agentic AI, agentic, AI, Artificial Intelligence
Evidence — skills matched in JD (0)
Skill cluster (0 dimension groups, role-scoped)
Status:
completed
Created: 2026-05-08T15:27:14.697233Z
Updated: 2026-05-08T15:28:57.113448Z
API 3 duration: 26 ms
Flow
Current 3-step pipeline
1 POST /skills/extract-from-jd
2 POST /skills/extract-details
3 POST /skills/final-role-output
Role
Chosen role & resolution
DevOps Engineer
slug: devops-engineer · id: 1 · source: db
Most dimensions map to DevOps Engineer, especially Kubernetes, Docker, Azure/AWS, deployment automation, and IaC.
0
New skills
0
Skill↔dim saved
0
Role↔dim saved
41
Skipped
Job description
Job Description Role Overview: We are seeking a seasoned Cloud Engineer to join our dynamic Technology research team. The ideal candidate will work collaboratively with the AI, Product and other teams to optimize building Devops cloud-based pipelines, enabling cloud infrastructure and services, ensuring the full benefits of standardized Cloud Tools are achieved across various teams of the vertical. This individual will play a crucial role in developing Infrastructure as a Code, AI models deployment pipelines, security ops, automating CI/CD pipelines, and streamlining cloud operations to improve efficiency, reduce costs, and enhance system availability, performance, and scalability. Responsibilities: Be an active member of the team to build, own cloud based platform, its services, Devops pipelines for AI Model deployment, development pipelines, and provisioning public Cloud Native platform infrastructure in AWS or Azure or GCP. Develop and maintain Infrastructure as a Code (IaC) scripts to deploy cloud resources through pipelines and automate application installs. Continually evolve deployment methods and processes to effectively deliver products across all environments. Will be responsible for building docker containerization pipelines for Nvidia Nemo/NIM models and services. Will be involved in Containerization and Containers orchestration using Kubernetes Good experience in setting up end to end CI/CD using AWS/Azure Devops (components such as web app, function app, logic app and APIM) Building feedback loops to transfer data from client end to optimization hub in WNS environment. Will be involved in integrating platform with other tools like Junit, Jmeter, Jira, Jenkins etc Will be involved in sandbox cloud VM creation and replication for multiple users where they can collaborate to dev AI/Agentic AI applications. Will be involved in scaling product deployment - Authentication, Authorization, Session management, rest APIs and code building to scale applications which can be used by 10K+ users. Should have experience with AI Model versioning, code versioning through SVN and Git repository configuration and management Collaborate with the senior members of the AI Software Engineering team, Product Manager, and Product team to continuously improve the processes for the implementation, operation, and maintenance of the platform Implement automation, monitoring, logging, alerting, and deployment solutions to improve buildAI Model deployment experience and developer productivity. Ensure that all cloud solutions follow internally defined security and compliance standards and controls. Also take care of Containers and Code security while deploying the product/solution in client environment. Being the Cloud Native advocate to challenge status quo and ensure leveraging the full capabilities of the Cloud Platform Skills: Possess one or more experience(AWS/Azure/GCP). Possess experience in containers development, Kubernetes, Devops tools, CI/CD pipeline development, Jenkins etc. Possess deep and broad knowledge and experience in general IT and public cloud, including Networking, Infrastructure, Security, Storage, Operating Systems (Linux/Windows). Experience with cloud infrastructure as code tooling.5. Proficiency in server OS, including Windows and/or Linux.6. Strong skills in Python and PowerShell/Bash scripting. Qualifications Bachelors or master’s in computer science, Artificial Intelligence, or a related field 7+ years of experience in Devops and Cloud Experience tool chaining (GitHub, Jira), building CICD Pipeline, deployment automation, and containerization (Kubernetes, Docker). Excellent problem solving, troubleshooting and analytical skill
history_view bundle (older API). Showing raw API payloads below.
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 |
|---|---|---|---|---|---|---|
| Kubernetes | in_db |
Orchestration Platforms
orchestration-platforms
|
— | — | — | TODO: REMOVE AFTER TESTING — api3_writes_enabled=False (writes disabled) |
| PowerShell | in_db |
Deployment Automation Scripts
deployment-automation-scripts
|
— | — | — | TODO: REMOVE AFTER TESTING — api3_writes_enabled=False (writes disabled) |
| JUnit | in_db |
Authentication Flows and Session Handling
authentication-flows-and-session-handling
|
— | — | — | TODO: REMOVE AFTER TESTING — api3_writes_enabled=False (writes disabled) |
| JUnit | in_db |
Test Frameworks and Runners
test-frameworks-and-runners
|
— | — | — | TODO: REMOVE AFTER TESTING — api3_writes_enabled=False (writes disabled) |
| JUnit | in_db |
Testing and Quality Assurance
testing-and-quality-assurance
|
— | — | — | TODO: REMOVE AFTER TESTING — api3_writes_enabled=False (writes disabled) |
| Docker | in_db |
Containerization and Image Delivery
containerization-and-image-delivery
|
— | — | — | TODO: REMOVE AFTER TESTING — api3_writes_enabled=False (writes disabled) |
| Docker | in_db |
Model Serving Deployment and Runtime Packaging
model-serving-deployment-and-runtime-packaging
|
— | — | — | TODO: REMOVE AFTER TESTING — api3_writes_enabled=False (writes disabled) |
| REST APIs | in_db |
API Integration and Data Fetching
api-integration-and-data-fetching
|
— | — | — | TODO: REMOVE AFTER TESTING — api3_writes_enabled=False (writes disabled) |
| REST APIs | in_db |
API Integration and Serialization
api-integration-and-serialization
|
— | — | — | TODO: REMOVE AFTER TESTING — api3_writes_enabled=False (writes disabled) |
| REST APIs | in_db |
Network Automation and Scripting
network-automation-and-scripting
|
— | — | — | TODO: REMOVE AFTER TESTING — api3_writes_enabled=False (writes disabled) |
| Jenkins | in_db |
Continuous Integration Test Integration
continuous-integration-test-integration
|
— | — | — | TODO: REMOVE AFTER TESTING — api3_writes_enabled=False (writes disabled) |
| Python | in_db |
Analytical Programming Languages
analytical-programming-languages
|
— | — | — | TODO: REMOVE AFTER TESTING — api3_writes_enabled=False (writes disabled) |
| Python | in_db |
Automation Scripting and CLI
automation-scripting-and-cli
|
— | — | — | TODO: REMOVE AFTER TESTING — api3_writes_enabled=False (writes disabled) |
| Python | in_db |
Network Automation and Scripting
network-automation-and-scripting
|
— | — | — | TODO: REMOVE AFTER TESTING — api3_writes_enabled=False (writes disabled) |
| Python | in_db |
Programming Languages for AI Workflows
programming-languages-for-ai-workflows
|
— | — | — | TODO: REMOVE AFTER TESTING — api3_writes_enabled=False (writes disabled) |
| Python | in_db |
Programming Languages for Backend Systems
programming-languages-for-backend-systems
|
— | — | — | TODO: REMOVE AFTER TESTING — api3_writes_enabled=False (writes disabled) |
| Python | in_db |
Programming Languages for Data Work
programming-languages-for-data-work
|
— | — | — | TODO: REMOVE AFTER TESTING — api3_writes_enabled=False (writes disabled) |
| Python | in_db |
Programming Languages for ML Systems
programming-languages-for-ml-systems
|
— | — | — | TODO: REMOVE AFTER TESTING — api3_writes_enabled=False (writes disabled) |
| Python | in_db |
Programming Languages for Test Automation
programming-languages-for-test-automation
|
— | — | — | TODO: REMOVE AFTER TESTING — api3_writes_enabled=False (writes disabled) |
| Python | in_db |
Security Automation and Scripting
security-automation-and-scripting
|
— | — | — | TODO: REMOVE AFTER TESTING — api3_writes_enabled=False (writes disabled) |
| Azure | in_db |
Cloud Platform Operations
cloud-platform-operations
|
— | — | — | TODO: REMOVE AFTER TESTING — api3_writes_enabled=False (writes disabled) |
| Bash scripting | in_db |
Deployment Automation Scripts
deployment-automation-scripts
|
— | — | — | TODO: REMOVE AFTER TESTING — api3_writes_enabled=False (writes disabled) |
| Bash scripting | in_db |
MySQL Automation and Scripting
mysql-automation-and-scripting
|
— | — | — | TODO: REMOVE AFTER TESTING — api3_writes_enabled=False (writes disabled) |
| AWS | in_db |
Cloud Platform Operations
cloud-platform-operations
|
— | — | — | TODO: REMOVE AFTER TESTING — api3_writes_enabled=False (writes disabled) |
| AI | new |
Artificial Intelligence
d_init_01
|
— | — | — | skill_not_in_db_v3_proposed |
| APIM | new |
API Management Platforms
d_init_01
|
— | — | — | skill_not_in_db_v3_proposed |
| Authentication | new |
Authentication
d_init_01
|
— | — | — | skill_not_in_db_v3_proposed |
| CD | new |
Continuous Delivery
d_init_01
|
— | — | — | skill_not_in_db_v3_proposed |
| CI | new |
Continuous Integration Practices
d_init_01
|
— | — | — | skill_not_in_db_v3_proposed |
| Cloud | new |
Cloud Platforms and Services
d_init_01
|
— | — | — | skill_not_in_db_v3_proposed |
| Containers | new |
Containerization
d_init_01
|
— | — | — | skill_not_in_db_v3_proposed |
| Devops | new |
Scaling and Resilience Engineering
scaling-and-resilience-engineering
|
— | — | — | skill_not_in_db_v3_proposed |
| IaC | new |
Infrastructure as Code
infrastructure-as-code
|
— | — | — | skill_not_in_db_v3_proposed |
| Infrastructure | new |
Infrastructure Provisioning
d_init_01
|
— | — | — | skill_not_in_db_v3_proposed |
| Linux.6 | new |
Linux System Administration
d_init_01
|
— | — | — | skill_not_in_db_v3_proposed |
| NIM | new |
NIM Inference Serving
d_init_01
|
— | — | — | skill_not_in_db_v3_proposed |
| Nemo | new |
Nemo Framework Usage
d_init_01
|
— | — | — | skill_not_in_db_v3_proposed |
| Networking | new |
Networking Fundamentals
d_init_01
|
— | — | — | skill_not_in_db_v3_proposed |
| OS | new |
Operating Systems Fundamentals
d_init_01
|
— | — | — | skill_not_in_db_v3_proposed |
| SVN | new |
Version Control Systems
d_init_01
|
— | — | — | skill_not_in_db_v3_proposed |
| Windows | new |
Windows Administration
d_init_01
|
— | — | — | skill_not_in_db_v3_proposed |
Library artifacts (this run)
| Kind | Detail | DB id |
|---|---|---|
| canonical_skill_proposed | AI | type=Concept subtype=artificial_intelligence nature=CONCEPT lifespan=EVERGREEN | |
| canonical_skill_proposed | APIM | type=Platform subtype=api_management_platform nature=PLATFORM lifespan=EVERGREEN | |
| canonical_skill_proposed | Authentication | type=Concept subtype=security_concept nature=CONCEPT lifespan=EVERGREEN | |
| canonical_skill_proposed | CD | type=Methodology subtype=continuous_delivery nature=METHODOLOGY lifespan=EVERGREEN | |
| canonical_skill_proposed | CI | type=Methodology subtype=continuous_integration_methodology nature=METHODOLOGY lifespan=EVERGREEN | |
| canonical_skill_proposed | CICD | type=Methodology subtype=continuous_integration_continuous_delivery nature=METHODOLOGY lifespan=EVERGREEN | |
| canonical_skill_proposed | Cloud | type=Domain subtype=cloud_computing nature=CONCEPT lifespan=EVERGREEN | |
| canonical_skill_proposed | Containers | type=Architecture subtype=containerization_architecture nature=PATTERN lifespan=EVERGREEN | |
| canonical_skill_proposed | Devops | type=Methodology subtype=devops_practices nature=METHODOLOGY lifespan=EVERGREEN | |
| canonical_skill_proposed | IaC | type=Methodology subtype=infrastructure_as_code nature=METHODOLOGY lifespan=EVERGREEN | |
| canonical_skill_proposed | Infrastructure | type=Domain subtype=infrastructure nature=CONCEPT lifespan=EVERGREEN | |
| canonical_skill_proposed | Linux.6 | type=Concept subtype=operating_system_concept nature=CONCEPT lifespan=EVERGREEN | |
| canonical_skill_proposed | NIM | type=Language subtype=programming_language nature=LANGUAGE lifespan=EVERGREEN | |
| canonical_skill_proposed | Nemo | type=Tool subtype=desktop_application nature=TOOL lifespan=EVERGREEN | |
| canonical_skill_proposed | Networking | type=Concept subtype=computer_networking nature=CONCEPT lifespan=EVERGREEN | |
| canonical_skill_proposed | OS | type=Concept subtype=operating_system nature=CONCEPT lifespan=EVERGREEN | |
| canonical_skill_proposed | Pipeline | type=Architecture subtype=data_pipeline_architecture nature=PATTERN lifespan=EVERGREEN | |
| canonical_skill_proposed | SVN | type=Tool subtype=version_control_tool nature=TOOL lifespan=EVERGREEN | |
| canonical_skill_proposed | Security | type=Domain subtype=security nature=CONCEPT lifespan=EVERGREEN | |
| canonical_skill_proposed | Storage | type=Domain subtype=data_storage nature=CONCEPT lifespan=EVERGREEN | |
| canonical_skill_proposed | Windows | type=Platform subtype=operating_system_platform nature=PLATFORM lifespan=EVERGREEN | |
| dimension_proposed | Artificial Intelligence | |
| dimension_skill_link_proposed | AI ↔ Artificial Intelligence | |
| dimension_proposed | API Management Platforms | |
| dimension_skill_link_proposed | APIM ↔ API Management Platforms | |
| dimension_proposed | Authentication | |
| dimension_skill_link_proposed | Authentication ↔ Authentication | |
| dimension_proposed | Continuous Delivery | |
| dimension_skill_link_proposed | CD ↔ Continuous Delivery | |
| dimension_proposed | Continuous Integration Practices | |
| dimension_skill_link_proposed | CI ↔ Continuous Integration Practices | |
| dimension_proposed | Cloud Platforms and Services | |
| dimension_skill_link_proposed | Cloud ↔ Cloud Platforms and Services | |
| dimension_proposed | Containerization | |
| dimension_skill_link_proposed | Containers ↔ Containerization | |
| dimension_skill_link_proposed | Devops ↔ Scaling and Resilience Engineering | |
| dimension_skill_link_proposed | IaC ↔ Infrastructure as Code | |
| role_dimension_link_proposed | DevOps Engineer ↔ Infrastructure as Code | |
| dimension_proposed | Infrastructure Provisioning | |
| dimension_skill_link_proposed | Infrastructure ↔ Infrastructure Provisioning | |
| dimension_proposed | Linux System Administration | |
| dimension_skill_link_proposed | Linux.6 ↔ Linux System Administration | |
| dimension_proposed | NIM Inference Serving | |
| dimension_skill_link_proposed | NIM ↔ NIM Inference Serving | |
| dimension_proposed | Nemo Framework Usage | |
| dimension_skill_link_proposed | Nemo ↔ Nemo Framework Usage | |
| dimension_proposed | Networking Fundamentals | |
| dimension_skill_link_proposed | Networking ↔ Networking Fundamentals | |
| dimension_proposed | Operating Systems Fundamentals | |
| dimension_skill_link_proposed | OS ↔ Operating Systems Fundamentals | |
| dimension_proposed | Version Control Systems | |
| dimension_skill_link_proposed | SVN ↔ Version Control Systems | |
| dimension_proposed | Windows Administration | |
| dimension_skill_link_proposed | Windows ↔ Windows Administration |
API 1 — extract-from-jd click to toggle
{
"filtered_unknown_words": [
"10K+",
"AI",
"APIM",
"APIs",
"Agentic",
"Artificial",
"Authentication",
"Bachelors",
"CD",
"CI",
"CICD",
"Cloud",
"Code",
"Containers",
"Description",
"Develop",
"Devops",
"Engineer",
"Engineering",
"Experience",
"IaC",
"Infrastructure",
"Intelligence",
"Job",
"Linux.6",
"Manager",
"Model",
"NIM",
"Native",
"Nemo",
"Networking",
"Nvidia",
"OS",
"Operating",
"Overview",
"Pipeline",
"Platform",
"Product",
"Proficiency",
"Qualifications",
"Responsibilities",
"Role",
"SVN",
"Security",
"Skills",
"Software",
"Storage",
"Systems",
"Technology",
"Tools",
"WNS",
"Windows",
"advocate",
"app",
"application",
"applications",
"availability",
"benefits",
"buildAI",
"building",
"candidate",
"capabilities",
"care",
"chaining",
"client",
"cloud",
"code",
"compliance",
"components",
"computer",
"configuration",
"containers",
"controls",
"costs",
"creation",
"data",
"deployment",
"dev",
"developer",
"development",
"efficiency",
"end",
"environment",
"environments",
"experience",
"experience(AWS",
"feedback",
"field",
"function",
"hub",
"implementation",
"individual",
"infrastructure",
"installs",
"knowledge",
"logic",
"loops",
"maintenance",
"master",
"member",
"members",
"methods",
"models",
"monitoring",
"operation",
"operations",
"ops",
"optimization",
"orchestration",
"performance",
"pipeline",
"pipelines",
"platform",
"problem",
"processes",
"product",
"productivity",
"products",
"quo",
"repository",
"research",
"resources",
"role",
"sandbox",
"science",
"scripts",
"security",
"server",
"services",
"skill",
"skills",
"solution",
"solutions",
"solving",
"standards",
"status",
"system",
"team",
"teams",
"tool",
"tooling.5",
"tools",
"users",
"versioning",
"web",
"years"
],
"final_non_skills": [
"10K+",
"Agentic",
"Artificial",
"Bachelors",
"Code",
"Description",
"Develop",
"Engineer",
"Engineering",
"Experience",
"Intelligence",
"Job",
"Manager",
"Model",
"Native",
"Nvidia",
"Operating",
"Overview",
"Platform",
"Product",
"Proficiency",
"Qualifications",
"Responsibilities",
"Role",
"Skills",
"Software",
"Systems",
"Technology",
"Tools",
"WNS",
"advocate",
"app",
"availability",
"benefits",
"buildAI",
"building",
"candidate",
"capabilities",
"care",
"chaining",
"client",
"compliance",
"components",
"computer",
"configuration",
"controls",
"costs",
"creation",
"data",
"dev",
"developer",
"efficiency",
"end",
"environment",
"environments",
"experience(AWS",
"feedback",
"field",
"function",
"hub",
"implementation",
"individual",
"installs",
"knowledge",
"logic",
"loops",
"maintenance",
"master",
"member",
"members",
"methods",
"models",
"operation",
"optimization",
"performance",
"problem",
"processes",
"productivity",
"products",
"quo",
"research",
"sandbox",
"science",
"server",
"skill",
"solution",
"solving",
"standards",
"status",
"system",
"team",
"teams",
"tooling.5",
"users",
"web",
"years"
],
"final_skills": [
"Kubernetes",
"PowerShell",
"JUnit",
"Docker",
"REST APIs",
"Jenkins",
"Python",
"Azure",
"Bash scripting",
"AWS",
"AI",
"APIM",
"Authentication",
"CD",
"CI",
"CICD",
"Cloud",
"Containers",
"Devops",
"IaC",
"Infrastructure",
"Linux.6",
"NIM",
"Nemo",
"Networking",
"OS",
"Pipeline",
"SVN",
"Security",
"Storage",
"Windows",
"application",
"applications",
"deployment",
"development",
"monitoring",
"operations",
"ops",
"orchestration",
"pipelines",
"repository",
"resources",
"scripts",
"services",
"solutions",
"tool",
"versioning"
],
"initial_skills": [
"Kubernetes",
"PowerShell",
"JUnit",
"Docker",
"REST APIs",
"Jenkins",
"Python",
"Azure",
"Bash scripting",
"AWS"
],
"jd_role_hint": {
"display_name": "Cloud Engineer",
"rationale": "The excerpt centers on cloud infrastructure, DevOps pipelines, CI/CD, IaC, and deployment automation.",
"role_archetype": "Cloud/DevOps infrastructure engineer focused on deployment pipelines, cloud operations, and platform automation.",
"slug": "cloud-engineer"
},
"llm_non_skills": [
"10K+",
"Agentic",
"Artificial",
"Bachelors",
"Code",
"Description",
"Develop",
"Engineer",
"Engineering",
"Experience",
"Intelligence",
"Job",
"Manager",
"Model",
"Native",
"Nvidia",
"Operating",
"Overview",
"Platform",
"Product",
"Proficiency",
"Qualifications",
"Responsibilities",
"Role",
"Skills",
"Software",
"Systems",
"Technology",
"Tools",
"WNS",
"advocate",
"app",
"availability",
"benefits",
"buildAI",
"building",
"candidate",
"capabilities",
"care",
"chaining",
"client",
"compliance",
"components",
"computer",
"configuration",
"controls",
"costs",
"creation",
"data",
"dev",
"developer",
"efficiency",
"end",
"environment",
"environments",
"experience(AWS",
"feedback",
"field",
"function",
"hub",
"implementation",
"individual",
"installs",
"knowledge",
"logic",
"loops",
"maintenance",
"master",
"member",
"members",
"methods",
"models",
"operation",
"optimization",
"performance",
"problem",
"processes",
"productivity",
"products",
"quo",
"research",
"sandbox",
"science",
"server",
"skill",
"solution",
"solving",
"standards",
"status",
"system",
"team",
"teams",
"tooling.5",
"users",
"web",
"years"
],
"llm_skills": [
"AI",
"APIM",
"Authentication",
"CD",
"CI",
"CICD",
"Cloud",
"Containers",
"Devops",
"IaC",
"Infrastructure",
"Linux.6",
"NIM",
"Nemo",
"Networking",
"OS",
"Pipeline",
"SVN",
"Security",
"Storage",
"Windows",
"application",
"applications",
"cloud",
"containers",
"deployment",
"development",
"infrastructure",
"monitoring",
"operations",
"ops",
"orchestration",
"pipeline",
"pipelines",
"repository",
"resources",
"scripts",
"security",
"services",
"solutions",
"tool",
"versioning"
],
"run_id": null,
"unknown_words": [
"10K+",
"AI",
"APIM",
"APIs",
"Agentic",
"Artificial",
"Authentication",
"Bachelors",
"CD",
"CI",
"CICD",
"Cloud",
"Code",
"Containers",
"Description",
"Develop",
"Devops",
"Engineer",
"Engineering",
"Experience",
"IaC",
"Infrastructure",
"Intelligence",
"Job",
"Linux.6",
"Manager",
"Model",
"NIM",
"Native",
"Nemo",
"Networking",
"Nvidia",
"OS",
"Operating",
"Overview",
"Pipeline",
"Platform",
"Product",
"Proficiency",
"Qualifications",
"Responsibilities",
"Role",
"SVN",
"Security",
"Skills",
"Software",
"Storage",
"Systems",
"Technology",
"Tools",
"WNS",
"Windows",
"advocate",
"app",
"application",
"applications",
"availability",
"benefits",
"buildAI",
"building",
"candidate",
"capabilities",
"care",
"chaining",
"client",
"cloud",
"code",
"compliance",
"components",
"computer",
"configuration",
"containers",
"controls",
"costs",
"creation",
"data",
"deployment",
"dev",
"developer",
"development",
"efficiency",
"end",
"environment",
"environments",
"experience",
"experience(AWS",
"feedback",
"field",
"function",
"hub",
"implementation",
"individual",
"infrastructure",
"installs",
"knowledge",
"logic",
"loops",
"maintenance",
"master",
"member",
"members",
"methods",
"models",
"monitoring",
"operation",
"operations",
"ops",
"optimization",
"orchestration",
"performance",
"pipeline",
"pipelines",
"platform",
"problem",
"processes",
"product",
"productivity",
"products",
"quo",
"repository",
"research",
"resources",
"role",
"sandbox",
"science",
"scripts",
"security",
"server",
"services",
"skill",
"skills",
"solution",
"solutions",
"solving",
"standards",
"status",
"system",
"team",
"teams",
"tool",
"tooling.5",
"tools",
"users",
"versioning",
"web",
"years"
]
}
API 2 — extract-details
{
"alias_matches": [],
"candidate_roles": [
{
"display_name": "Cloud Engineer",
"id": 18,
"rationale": null,
"role_archetype": null,
"slug": "cloud-engineer",
"source": "db"
},
{
"display_name": "DevOps Engineer",
"id": 1,
"rationale": null,
"role_archetype": "A DevOps Engineer enables reliable, repeatable delivery of software by designing and operating the processes that connect development and production. They focus on improving deployment flow, operational stability, and collaboration between teams through automation, standardization, and monitoring of delivery and runtime practices.",
"slug": "devops-engineer",
"source": "db"
},
{
"display_name": "Android Engineer",
"id": 15,
"rationale": null,
"role_archetype": null,
"slug": "android-engineer",
"source": "db"
},
{
"display_name": "Frontend Engineer",
"id": 3,
"rationale": null,
"role_archetype": "Frontend Engineers design and build the user-facing parts of applications, translating product and design requirements into interactive experiences. They focus on how the application looks, behaves, and responds in the browser, ensuring usability, accessibility, and consistency across the interface.",
"slug": "frontend-engineer",
"source": "db"
},
{
"display_name": "Full Stack Developer",
"id": 2,
"rationale": null,
"role_archetype": null,
"slug": "full-stack-developer",
"source": "db"
},
{
"display_name": "Automation Tester",
"id": 16,
"rationale": null,
"role_archetype": null,
"slug": "automation-tester",
"source": "db"
},
{
"display_name": "Backend Engineer",
"id": 14,
"rationale": null,
"role_archetype": null,
"slug": "backend-engineer",
"source": "db"
},
{
"display_name": "MLOps Engineer",
"id": 5,
"rationale": null,
"role_archetype": null,
"slug": "mlops-engineer",
"source": "db"
},
{
"display_name": "Machine Learning Engineer",
"id": 10,
"rationale": null,
"role_archetype": null,
"slug": "machine-learning-engineer",
"source": "db"
},
{
"display_name": "iOS Engineer",
"id": 13,
"rationale": null,
"role_archetype": null,
"slug": "ios-engineer",
"source": "db"
},
{
"display_name": "Network Engineer",
"id": 21,
"rationale": null,
"role_archetype": null,
"slug": "network-engineer",
"source": "db"
},
{
"display_name": "Data Analyst",
"id": 20,
"rationale": null,
"role_archetype": null,
"slug": "data-analyst",
"source": "db"
},
{
"display_name": "Data Scientist",
"id": 7,
"rationale": null,
"role_archetype": null,
"slug": "data-scientist",
"source": "db"
},
{
"display_name": "Azure Cloud Engineer",
"id": 4,
"rationale": null,
"role_archetype": null,
"slug": "azure-cloud-engineer",
"source": "db"
},
{
"display_name": "AI Engineer",
"id": 12,
"rationale": null,
"role_archetype": null,
"slug": "ai-engineer",
"source": "db"
},
{
"display_name": "Data Engineer",
"id": 6,
"rationale": null,
"role_archetype": null,
"slug": "data-engineer",
"source": "db"
},
{
"display_name": "Cybersecurity Engineer",
"id": 9,
"rationale": null,
"role_archetype": null,
"slug": "cybersecurity-engineer",
"source": "db"
},
{
"display_name": "MySQL DBA",
"id": 23,
"rationale": null,
"role_archetype": null,
"slug": "mysql-dba",
"source": "db"
}
],
"chosen_role": {
"display_name": "DevOps Engineer",
"id": 1,
"rationale": "Most dimensions map to DevOps Engineer, especially Kubernetes, Docker, Azure/AWS, deployment automation, and IaC.",
"role_archetype": "A DevOps Engineer enables reliable, repeatable delivery of software by designing and operating the processes that connect development and production. They focus on improving deployment flow, operational stability, and collaboration between teams through automation, standardization, and monitoring of delivery and runtime practices.",
"slug": "devops-engineer",
"source": "db"
},
"dimensions": [
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Orchestration Platforms",
"id": 25,
"rationale": "Operates the platforms that schedule and run containerized workloads and related deployment primitives. This is separate from image delivery because it concerns runtime placement and service rollout behavior.",
"slug": "orchestration-platforms",
"source": "db"
},
"input_skill": "Kubernetes",
"llm_role": null,
"roles_from_db": [
{
"display_name": "Cloud Engineer",
"id": 18,
"rationale": null,
"role_archetype": null,
"slug": "cloud-engineer",
"source": "db"
},
{
"display_name": "DevOps Engineer",
"id": 1,
"rationale": null,
"role_archetype": "A DevOps Engineer enables reliable, repeatable delivery of software by designing and operating the processes that connect development and production. They focus on improving deployment flow, operational stability, and collaboration between teams through automation, standardization, and monitoring of delivery and runtime practices.",
"slug": "devops-engineer",
"source": "db"
}
]
},
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Deployment Automation Scripts",
"id": 31,
"rationale": "Implements the scripts and command-line automation used to execute deployments and environment changes. This cluster covers the practical glue code that pipelines and operators rely on.",
"slug": "deployment-automation-scripts",
"source": "db"
},
"input_skill": "PowerShell",
"llm_role": null,
"roles_from_db": [
{
"display_name": "DevOps Engineer",
"id": 1,
"rationale": null,
"role_archetype": "A DevOps Engineer enables reliable, repeatable delivery of software by designing and operating the processes that connect development and production. They focus on improving deployment flow, operational stability, and collaboration between teams through automation, standardization, and monitoring of delivery and runtime practices.",
"slug": "devops-engineer",
"source": "db"
}
]
},
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Authentication Flows and Session Handling",
"id": 10,
"rationale": "Client-side implementation of sign-in, sign-out, session persistence, and protected navigation. This is separated from general API integration because auth flows have distinct UX and state concerns.",
"slug": "authentication-flows-and-session-handling",
"source": "db"
},
"input_skill": "JUnit",
"llm_role": null,
"roles_from_db": [
{
"display_name": "Android Engineer",
"id": 15,
"rationale": null,
"role_archetype": null,
"slug": "android-engineer",
"source": "db"
},
{
"display_name": "Frontend Engineer",
"id": 3,
"rationale": null,
"role_archetype": "Frontend Engineers design and build the user-facing parts of applications, translating product and design requirements into interactive experiences. They focus on how the application looks, behaves, and responds in the browser, ensuring usability, accessibility, and consistency across the interface.",
"slug": "frontend-engineer",
"source": "db"
},
{
"display_name": "Full Stack Developer",
"id": 2,
"rationale": null,
"role_archetype": null,
"slug": "full-stack-developer",
"source": "db"
}
]
},
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Test Frameworks and Runners",
"id": 194,
"rationale": "Frameworks and execution tools used to author, organize, and run automated tests. This cluster is coherent because it defines how test cases are structured, parameterized, and reported.",
"slug": "test-frameworks-and-runners",
"source": "db"
},
"input_skill": "JUnit",
"llm_role": null,
"roles_from_db": [
{
"display_name": "Automation Tester",
"id": 16,
"rationale": null,
"role_archetype": null,
"slug": "automation-tester",
"source": "db"
}
]
},
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Testing and Quality Assurance",
"id": 150,
"rationale": "Automated testing approaches used to verify backend behavior across units, integrations, contracts, and end-to-end flows. This cluster is coherent because backend engineers need confidence in request handling, data changes, and service interactions.",
"slug": "testing-and-quality-assurance",
"source": "db"
},
"input_skill": "JUnit",
"llm_role": null,
"roles_from_db": [
{
"display_name": "Backend Engineer",
"id": 14,
"rationale": null,
"role_archetype": null,
"slug": "backend-engineer",
"source": "db"
}
]
},
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Containerization and Image Delivery",
"id": 24,
"rationale": "Builds, packages, and ships application and support workloads as container images. This cluster covers the artifact format and the mechanics of producing deployable images.",
"slug": "containerization-and-image-delivery",
"source": "db"
},
"input_skill": "Docker",
"llm_role": null,
"roles_from_db": [
{
"display_name": "DevOps Engineer",
"id": 1,
"rationale": null,
"role_archetype": "A DevOps Engineer enables reliable, repeatable delivery of software by designing and operating the processes that connect development and production. They focus on improving deployment flow, operational stability, and collaboration between teams through automation, standardization, and monitoring of delivery and runtime practices.",
"slug": "devops-engineer",
"source": "db"
}
]
},
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Model Serving Deployment and Runtime Packaging",
"id": 52,
"rationale": "Operational deployment of trained models into online, batch, or streaming serving environments, including packaging models and model servers into containers or managed inference runtimes, coordinating rollout, and handing off to inference systems. Covers serving frameworks and platforms such as TensorFlow Serving, TorchServe, Triton Inference Server, BentoML, KServe, and Seldon Core, plus container/runtime concerns like Docker images, GPU-enabled containers, base image selection, container entrypoints, runtime dependencies, and image scanning for model services.",
"slug": "model-serving-deployment-and-runtime-packaging",
"source": "db"
},
"input_skill": "Docker",
"llm_role": null,
"roles_from_db": [
{
"display_name": "MLOps Engineer",
"id": 5,
"rationale": null,
"role_archetype": null,
"slug": "mlops-engineer",
"source": "db"
},
{
"display_name": "Machine Learning Engineer",
"id": 10,
"rationale": null,
"role_archetype": null,
"slug": "machine-learning-engineer",
"source": "db"
}
]
},
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "API Integration and Data Fetching",
"id": 9,
"rationale": "Connecting frontend applications to backend services and third-party endpoints. This covers request orchestration, error handling, pagination, and shaping remote data for UI consumption.",
"slug": "api-integration-and-data-fetching",
"source": "db"
},
"input_skill": "REST APIs",
"llm_role": null,
"roles_from_db": [
{
"display_name": "Frontend Engineer",
"id": 3,
"rationale": null,
"role_archetype": "Frontend Engineers design and build the user-facing parts of applications, translating product and design requirements into interactive experiences. They focus on how the application looks, behaves, and responds in the browser, ensuring usability, accessibility, and consistency across the interface.",
"slug": "frontend-engineer",
"source": "db"
},
{
"display_name": "Full Stack Developer",
"id": 2,
"rationale": null,
"role_archetype": null,
"slug": "full-stack-developer",
"source": "db"
}
]
},
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "API Integration and Serialization",
"id": 128,
"rationale": "Client-side integration with backend services, including request handling, response parsing, and contract alignment. This cluster is coherent because iOS features frequently depend on stable data exchange with server APIs.",
"slug": "api-integration-and-serialization",
"source": "db"
},
"input_skill": "REST APIs",
"llm_role": null,
"roles_from_db": [
{
"display_name": "iOS Engineer",
"id": 13,
"rationale": null,
"role_archetype": null,
"slug": "ios-engineer",
"source": "db"
}
]
},
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Network Automation and Scripting",
"id": 285,
"rationale": "Covers scripts and automation used to configure, validate, and audit network devices and services. This cluster is coherent because repeatable network operations increasingly depend on programmatic changes and checks.",
"slug": "network-automation-and-scripting",
"source": "db"
},
"input_skill": "REST APIs",
"llm_role": null,
"roles_from_db": [
{
"display_name": "Network Engineer",
"id": 21,
"rationale": null,
"role_archetype": null,
"slug": "network-engineer",
"source": "db"
}
]
},
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Continuous Integration Test Integration",
"id": 207,
"rationale": "Integrating automated checks into shared build and merge workflows so results are repeatable and visible. This cluster is coherent because automation testers commonly configure test execution triggers, artifacts, and reporting hooks.",
"slug": "continuous-integration-test-integration",
"source": "db"
},
"input_skill": "Jenkins",
"llm_role": null,
"roles_from_db": [
{
"display_name": "Automation Tester",
"id": 16,
"rationale": null,
"role_archetype": null,
"slug": "automation-tester",
"source": "db"
}
]
},
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Analytical Programming Languages",
"id": 82,
"rationale": "Languages used to clean, transform, analyze, and prototype models in notebooks and scripts. This is the core coding surface for expressing statistical logic and data manipulation in a reproducible way.",
"slug": "analytical-programming-languages",
"source": "db"
},
"input_skill": "Python",
"llm_role": null,
"roles_from_db": [
{
"display_name": "Data Analyst",
"id": 20,
"rationale": null,
"role_archetype": null,
"slug": "data-analyst",
"source": "db"
},
{
"display_name": "Data Scientist",
"id": 7,
"rationale": null,
"role_archetype": null,
"slug": "data-scientist",
"source": "db"
}
]
},
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Automation Scripting and CLI",
"id": 48,
"rationale": "Uses scripts and command-line tooling to execute repeatable Azure operations and reduce manual work. This is a practical cluster because the role frequently automates provisioning, checks, and remediation tasks.",
"slug": "automation-scripting-and-cli",
"source": "db"
},
"input_skill": "Python",
"llm_role": null,
"roles_from_db": [
{
"display_name": "Azure Cloud Engineer",
"id": 4,
"rationale": null,
"role_archetype": null,
"slug": "azure-cloud-engineer",
"source": "db"
},
{
"display_name": "Cloud Engineer",
"id": 18,
"rationale": null,
"role_archetype": null,
"slug": "cloud-engineer",
"source": "db"
}
]
},
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Network Automation and Scripting",
"id": 285,
"rationale": "Covers scripts and automation used to configure, validate, and audit network devices and services. This cluster is coherent because repeatable network operations increasingly depend on programmatic changes and checks.",
"slug": "network-automation-and-scripting",
"source": "db"
},
"input_skill": "Python",
"llm_role": null,
"roles_from_db": [
{
"display_name": "Network Engineer",
"id": 21,
"rationale": null,
"role_archetype": null,
"slug": "network-engineer",
"source": "db"
}
]
},
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Programming Languages for AI Workflows",
"id": 261,
"rationale": "Languages used to implement AI feature logic, orchestration, and response handling inside product code. This is the core coding surface for turning prompts and model calls into reliable application behavior.",
"slug": "programming-languages-for-ai-workflows",
"source": "db"
},
"input_skill": "Python",
"llm_role": null,
"roles_from_db": [
{
"display_name": "AI Engineer",
"id": 12,
"rationale": null,
"role_archetype": null,
"slug": "ai-engineer",
"source": "db"
}
]
},
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Programming Languages for Backend Systems",
"id": 140,
"rationale": "Languages used to implement server-side business logic, request handlers, workers, and service integrations. This is the core coding surface for backend feature delivery and maintenance.",
"slug": "programming-languages-for-backend-systems",
"source": "db"
},
"input_skill": "Python",
"llm_role": null,
"roles_from_db": [
{
"display_name": "Backend Engineer",
"id": 14,
"rationale": null,
"role_archetype": null,
"slug": "backend-engineer",
"source": "db"
}
]
},
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Programming Languages for Data Work",
"id": 67,
"rationale": "Languages used to implement data pipelines, transformations, and operational utilities. This is the code layer for expressing extraction, parsing, validation, and orchestration logic in data engineering workflows.",
"slug": "programming-languages-for-data-work",
"source": "db"
},
"input_skill": "Python",
"llm_role": null,
"roles_from_db": [
{
"display_name": "Data Engineer",
"id": 6,
"rationale": null,
"role_archetype": null,
"slug": "data-engineer",
"source": "db"
}
]
},
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Programming Languages for ML Systems",
"id": 113,
"rationale": "Languages used to implement model integration code, inference services, and feature-processing logic. This is the core coding surface for turning trained models into product-facing software components.",
"slug": "programming-languages-for-ml-systems",
"source": "db"
},
"input_skill": "Python",
"llm_role": null,
"roles_from_db": [
{
"display_name": "Machine Learning Engineer",
"id": 10,
"rationale": null,
"role_archetype": null,
"slug": "machine-learning-engineer",
"source": "db"
}
]
},
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Programming Languages for Test Automation",
"id": 193,
"rationale": "Languages used to implement automated checks, helper utilities, and test harness code. This is the core coding surface for turning test ideas into maintainable automation.",
"slug": "programming-languages-for-test-automation",
"source": "db"
},
"input_skill": "Python",
"llm_role": null,
"roles_from_db": [
{
"display_name": "Automation Tester",
"id": 16,
"rationale": null,
"role_archetype": null,
"slug": "automation-tester",
"source": "db"
}
]
},
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Security Automation and Scripting",
"id": 258,
"rationale": "Automating repeatable security checks, enrichment, and remediation workflows. This cluster is coherent because the role often needs lightweight automation to scale analysis and response.",
"slug": "security-automation-and-scripting",
"source": "db"
},
"input_skill": "Python",
"llm_role": null,
"roles_from_db": [
{
"display_name": "Cybersecurity Engineer",
"id": 9,
"rationale": null,
"role_archetype": null,
"slug": "cybersecurity-engineer",
"source": "db"
}
]
},
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Cloud Platform Operations",
"id": 26,
"rationale": "Uses cloud provider services to support delivery and runtime environments. The focus is on consumer-level operation of cloud services rather than deep cloud architecture ownership.",
"slug": "cloud-platform-operations",
"source": "db"
},
"input_skill": "Azure",
"llm_role": null,
"roles_from_db": [
{
"display_name": "DevOps Engineer",
"id": 1,
"rationale": null,
"role_archetype": "A DevOps Engineer enables reliable, repeatable delivery of software by designing and operating the processes that connect development and production. They focus on improving deployment flow, operational stability, and collaboration between teams through automation, standardization, and monitoring of delivery and runtime practices.",
"slug": "devops-engineer",
"source": "db"
}
]
},
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Deployment Automation Scripts",
"id": 31,
"rationale": "Implements the scripts and command-line automation used to execute deployments and environment changes. This cluster covers the practical glue code that pipelines and operators rely on.",
"slug": "deployment-automation-scripts",
"source": "db"
},
"input_skill": "Bash scripting",
"llm_role": null,
"roles_from_db": [
{
"display_name": "DevOps Engineer",
"id": 1,
"rationale": null,
"role_archetype": "A DevOps Engineer enables reliable, repeatable delivery of software by designing and operating the processes that connect development and production. They focus on improving deployment flow, operational stability, and collaboration between teams through automation, standardization, and monitoring of delivery and runtime practices.",
"slug": "devops-engineer",
"source": "db"
}
]
},
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "MySQL Automation and Scripting",
"id": 176,
"rationale": "Covers scripts and operational automation used to run repeatable DBA tasks. This cluster is coherent because production database administration depends on safe, repeatable execution of checks, maintenance, and change steps.",
"slug": "mysql-automation-and-scripting",
"source": "db"
},
"input_skill": "Bash scripting",
"llm_role": null,
"roles_from_db": [
{
"display_name": "MySQL DBA",
"id": 23,
"rationale": null,
"role_archetype": null,
"slug": "mysql-dba",
"source": "db"
}
]
},
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Cloud Platform Operations",
"id": 26,
"rationale": "Uses cloud provider services to support delivery and runtime environments. The focus is on consumer-level operation of cloud services rather than deep cloud architecture ownership.",
"slug": "cloud-platform-operations",
"source": "db"
},
"input_skill": "AWS",
"llm_role": null,
"roles_from_db": [
{
"display_name": "DevOps Engineer",
"id": 1,
"rationale": null,
"role_archetype": "A DevOps Engineer enables reliable, repeatable delivery of software by designing and operating the processes that connect development and production. They focus on improving deployment flow, operational stability, and collaboration between teams through automation, standardization, and monitoring of delivery and runtime practices.",
"slug": "devops-engineer",
"source": "db"
}
]
},
{
"dimension": {
"difficulty_hint": null,
"display_name": "Artificial Intelligence",
"id": null,
"rationale": "Covers the broad concept of AI systems and capabilities, including how intelligent behavior is applied in software and cloud solutions. The target skill belongs here because it is the umbrella term for AI-related work when no narrower sub-skill is specified.",
"slug": "d_init_01",
"source": "llm"
},
"input_skill": "AI",
"llm_role": null,
"roles_from_db": []
},
{
"dimension": {
"difficulty_hint": null,
"display_name": "API Management Platforms",
"id": null,
"rationale": "Covers managed API gateway and lifecycle capabilities such as publishing, routing, throttling, versioning, and policy enforcement. APIM belongs here because it is commonly used to expose, secure, and govern APIs in cloud environments.",
"slug": "d_init_01",
"source": "llm"
},
"input_skill": "APIM",
"llm_role": null,
"roles_from_db": []
},
{
"dimension": {
"difficulty_hint": null,
"display_name": "Authentication",
"id": null,
"rationale": "Mechanisms for verifying identity and establishing a trusted user or service session. This covers the core authentication concept itself, which is broader than any one client flow or platform-specific access setup.",
"slug": "d_init_01",
"source": "llm"
},
"input_skill": "Authentication",
"llm_role": null,
"roles_from_db": []
},
{
"dimension": {
"difficulty_hint": null,
"display_name": "Continuous Delivery",
"id": null,
"rationale": "Covers automating the path from a validated build to deployable releases across environments. CD belongs here because it is the standard engineering practice for reliably promoting changes through delivery pipelines.",
"slug": "d_init_01",
"source": "llm"
},
"input_skill": "CD",
"llm_role": null,
"roles_from_db": []
},
{
"dimension": {
"difficulty_hint": null,
"display_name": "Continuous Integration Practices",
"id": null,
"rationale": "Covers the automation that builds, tests, and validates code changes whenever they are merged or proposed. CI belongs here because it is the core delivery discipline for keeping changes integrated and verifiable in cloud and software engineering workflows.",
"slug": "d_init_01",
"source": "llm"
},
"input_skill": "CI",
"llm_role": null,
"roles_from_db": []
},
{
"dimension": {
"difficulty_hint": null,
"display_name": "Cloud Platforms and Services",
"id": null,
"rationale": "Covers core cloud computing concepts and the use of managed cloud services across major providers. This fits the target skill because \"Cloud\" is a broad umbrella for provisioning, operating, and integrating cloud-hosted infrastructure and services.",
"slug": "d_init_01",
"source": "llm"
},
"input_skill": "Cloud",
"llm_role": null,
"roles_from_db": []
},
{
"dimension": {
"difficulty_hint": null,
"display_name": "Containerization",
"id": null,
"rationale": "Covers packaging and running software in isolated containers, including the core concepts and tooling used to build, ship, and execute containerized applications. Containers belongs here when the skill refers to the container abstraction itself rather than orchestration or image delivery.",
"slug": "d_init_01",
"source": "llm"
},
"input_skill": "Containers",
"llm_role": null,
"roles_from_db": []
},
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Scaling and Resilience Engineering",
"id": 45,
"rationale": "Implements Azure-side patterns that improve availability, capacity, and fault tolerance. This is a coherent cluster because the role must keep environments ready for production load and failure scenarios.",
"slug": "scaling-and-resilience-engineering",
"source": "db"
},
"input_skill": "Devops",
"llm_role": null,
"roles_from_db": [
{
"display_name": "Azure Cloud Engineer",
"id": 4,
"rationale": null,
"role_archetype": null,
"slug": "azure-cloud-engineer",
"source": "db"
}
]
},
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Infrastructure as Code",
"id": 22,
"rationale": "Defines infrastructure and platform resources through versioned code so environments are repeatable and reviewable. This is a coherent cluster because it underpins environment consistency and change control.",
"slug": "infrastructure-as-code",
"source": "db"
},
"input_skill": "IaC",
"llm_role": null,
"roles_from_db": [
{
"display_name": "DevOps Engineer",
"id": 1,
"rationale": null,
"role_archetype": "A DevOps Engineer enables reliable, repeatable delivery of software by designing and operating the processes that connect development and production. They focus on improving deployment flow, operational stability, and collaboration between teams through automation, standardization, and monitoring of delivery and runtime practices.",
"slug": "devops-engineer",
"source": "db"
}
]
},
{
"dimension": {
"difficulty_hint": null,
"display_name": "Infrastructure Provisioning",
"id": null,
"rationale": "Covers the setup and management of compute, network, storage, and environment resources that applications depend on. The target skill belongs here when it refers to the underlying systems and runtime foundation rather than a specific cloud service or security control.",
"slug": "d_init_01",
"source": "llm"
},
"input_skill": "Infrastructure",
"llm_role": null,
"roles_from_db": []
},
{
"dimension": {
"difficulty_hint": null,
"display_name": "Linux System Administration",
"id": null,
"rationale": "Covers day-to-day administration of Linux hosts used in cloud and infrastructure environments. This skill belongs here because Linux.6 most likely refers to operating, configuring, and troubleshooting Linux systems rather than application code.",
"slug": "d_init_01",
"source": "llm"
},
"input_skill": "Linux.6",
"llm_role": null,
"roles_from_db": []
},
{
"dimension": {
"difficulty_hint": null,
"display_name": "NIM Inference Serving",
"id": null,
"rationale": "Covers NVIDIA Inference Microservices used to package, deploy, and operate model inference services. NIM belongs here because it is a runtime layer for exposing AI models as production-ready services.",
"slug": "d_init_01",
"source": "llm"
},
"input_skill": "NIM",
"llm_role": null,
"roles_from_db": []
},
{
"dimension": {
"difficulty_hint": null,
"display_name": "Nemo Framework Usage",
"id": null,
"rationale": "Covers working with the Nemo framework itself: its APIs, project structure, and how it is used to build or run AI-related workflows. This fits the target skill because \u0027Nemo\u0027 most likely refers to the framework rather than a generic concept.",
"slug": "d_init_01",
"source": "llm"
},
"input_skill": "Nemo",
"llm_role": null,
"roles_from_db": []
},
{
"dimension": {
"difficulty_hint": null,
"display_name": "Networking Fundamentals",
"id": null,
"rationale": "Core concepts and practices for designing, configuring, and troubleshooting network connectivity in cloud and enterprise environments. This fits Networking because it covers the base layer of how systems communicate over IP networks.",
"slug": "d_init_01",
"source": "llm"
},
"input_skill": "Networking",
"llm_role": null,
"roles_from_db": []
},
{
"dimension": {
"difficulty_hint": null,
"display_name": "Operating Systems Fundamentals",
"id": null,
"rationale": "Core knowledge of operating system concepts, components, and behavior across desktop, server, and cloud-hosted environments. This fits OS because the skill refers to the underlying platform layer that manages processes, memory, files, and device interactions.",
"slug": "d_init_01",
"source": "llm"
},
"input_skill": "OS",
"llm_role": null,
"roles_from_db": []
},
{
"dimension": {
"difficulty_hint": null,
"display_name": "Version Control Systems",
"id": null,
"rationale": "Covers source code versioning workflows for tracking changes, branching, merging, and repository history. SVN belongs here because it is a version control system used to manage code and related artifacts.",
"slug": "d_init_01",
"source": "llm"
},
"input_skill": "SVN",
"llm_role": null,
"roles_from_db": []
},
{
"dimension": {
"difficulty_hint": null,
"display_name": "Windows Administration",
"id": null,
"rationale": "Covers administering Windows operating systems in server or workstation environments, including configuration, patching, troubleshooting, and core OS management. Windows belongs here because it refers to the platform itself rather than a specific application or cloud service.",
"slug": "d_init_01",
"source": "llm"
},
"input_skill": "Windows",
"llm_role": null,
"roles_from_db": []
}
],
"input_final_skills": [
"Kubernetes",
"PowerShell",
"JUnit",
"Docker",
"REST APIs",
"Jenkins",
"Python",
"Azure",
"Bash scripting",
"AWS",
"AI",
"APIM",
"Authentication",
"CD",
"CI",
"CICD",
"Cloud",
"Containers",
"Devops",
"IaC",
"Infrastructure",
"Linux.6",
"NIM",
"Nemo",
"Networking",
"OS",
"Pipeline",
"SVN",
"Security",
"Storage",
"Windows",
"application",
"applications",
"deployment",
"development",
"monitoring",
"operations",
"ops",
"orchestration",
"pipelines",
"repository",
"resources",
"scripts",
"services",
"solutions",
"tool",
"versioning"
],
"input_llm_skills": [
"AI",
"APIM",
"Authentication",
"CD",
"CI",
"CICD",
"Cloud",
"Containers",
"Devops",
"IaC",
"Infrastructure",
"Linux.6",
"NIM",
"Nemo",
"Networking",
"OS",
"Pipeline",
"SVN",
"Security",
"Storage",
"Windows",
"application",
"applications",
"deployment",
"development",
"monitoring",
"operations",
"ops",
"orchestration",
"pipelines",
"repository",
"resources",
"scripts",
"services",
"solutions",
"tool",
"versioning"
],
"new_aliases_persisted": 0,
"run_id": "1a58e1db-36d7-4a29-b216-3d2e9f68b7e9",
"skills_detail": [
{
"aliases_in_db": [
{
"alias_text": "Kubernetes",
"alias_type": "CANONICAL",
"id": 304,
"is_primary": true,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "Kubernetes 1.0",
"alias_type": "VERSION",
"id": 307,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "Kubernetes 1.0+",
"alias_type": "VERSION",
"id": 2366,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "Kubernetes 1.1",
"alias_type": "VERSION",
"id": 308,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "Kubernetes 1.10",
"alias_type": "VERSION",
"id": 318,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "Kubernetes 1.11",
"alias_type": "VERSION",
"id": 319,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "Kubernetes 1.12",
"alias_type": "VERSION",
"id": 320,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "Kubernetes 1.13",
"alias_type": "VERSION",
"id": 321,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "Kubernetes 1.14",
"alias_type": "VERSION",
"id": 322,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "Kubernetes 1.15",
"alias_type": "VERSION",
"id": 323,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "Kubernetes 1.16",
"alias_type": "VERSION",
"id": 324,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "Kubernetes 1.17",
"alias_type": "VERSION",
"id": 325,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "Kubernetes 1.18",
"alias_type": "VERSION",
"id": 326,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "Kubernetes 1.19",
"alias_type": "VERSION",
"id": 327,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "Kubernetes 1.2",
"alias_type": "VERSION",
"id": 309,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "Kubernetes 1.20",
"alias_type": "VERSION",
"id": 328,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "Kubernetes 1.21",
"alias_type": "VERSION",
"id": 329,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "Kubernetes 1.22",
"alias_type": "VERSION",
"id": 330,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "Kubernetes 1.23",
"alias_type": "VERSION",
"id": 331,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "Kubernetes 1.24",
"alias_type": "VERSION",
"id": 332,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "Kubernetes 1.25",
"alias_type": "VERSION",
"id": 333,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "Kubernetes 1.26",
"alias_type": "VERSION",
"id": 334,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "Kubernetes 1.27",
"alias_type": "VERSION",
"id": 335,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "Kubernetes 1.28",
"alias_type": "VERSION",
"id": 336,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "Kubernetes 1.29",
"alias_type": "VERSION",
"id": 337,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "Kubernetes 1.3",
"alias_type": "VERSION",
"id": 310,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "Kubernetes 1.30",
"alias_type": "VERSION",
"id": 338,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "Kubernetes 1.4",
"alias_type": "VERSION",
"id": 311,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "Kubernetes 1.5",
"alias_type": "VERSION",
"id": 312,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "Kubernetes 1.6",
"alias_type": "VERSION",
"id": 313,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "Kubernetes 1.7",
"alias_type": "VERSION",
"id": 314,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "Kubernetes 1.8",
"alias_type": "VERSION",
"id": 315,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "Kubernetes 1.9",
"alias_type": "VERSION",
"id": 316,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "Kubernetes 1.x",
"alias_type": "VERSION",
"id": 317,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "Kubernetes v1",
"alias_type": "VERSION",
"id": 306,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "k8s",
"alias_type": "VERSION",
"id": 305,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
}
],
"canonical": {
"category_id": 13,
"display_name": "Kubernetes",
"id": 158,
"is_also_category": false,
"is_extractable": true,
"skill_nature": "PLATFORM",
"slug": "kubernetes",
"sub_category_id": 1524,
"typical_lifespan": "EVERGREEN",
"volatility": "STABLE"
},
"dimensions": [
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Orchestration Platforms",
"id": 25,
"rationale": "Operates the platforms that schedule and run containerized workloads and related deployment primitives. This is separate from image delivery because it concerns runtime placement and service rollout behavior.",
"slug": "orchestration-platforms",
"source": "db"
},
"input_skill": "Kubernetes",
"llm_role": null,
"roles_from_db": [
{
"display_name": "Cloud Engineer",
"id": 18,
"rationale": null,
"role_archetype": null,
"slug": "cloud-engineer",
"source": "db"
},
{
"display_name": "DevOps Engineer",
"id": 1,
"rationale": null,
"role_archetype": "A DevOps Engineer enables reliable, repeatable delivery of software by designing and operating the processes that connect development and production. They focus on improving deployment flow, operational stability, and collaboration between teams through automation, standardization, and monitoring of delivery and runtime practices.",
"slug": "devops-engineer",
"source": "db"
}
]
}
],
"input_skill": "Kubernetes",
"matched_via": "alias",
"new_alias_persisted": false,
"new_alias_text": null,
"new_skill_meta": null,
"source_tag": "db",
"was_in_llm_skills": false
},
{
"aliases_in_db": [
{
"alias_text": "PowerShell scripting",
"alias_type": "CANONICAL",
"id": 374,
"is_primary": true,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "PowerShell 5.1",
"alias_type": "VERSION",
"id": 377,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "PowerShell 7.x",
"alias_type": "VERSION",
"id": 378,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "PowerShell Core",
"alias_type": "VERSION",
"id": 379,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "Windows PowerShell",
"alias_type": "VERSION",
"id": 380,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "powershell",
"alias_type": "VERSION",
"id": 376,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "pwsh",
"alias_type": "VERSION",
"id": 375,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
}
],
"canonical": {
"category_id": 5,
"display_name": "PowerShell scripting",
"id": 189,
"is_also_category": false,
"is_extractable": true,
"skill_nature": "LANGUAGE",
"slug": "powershell-scripting",
"sub_category_id": 146,
"typical_lifespan": "EVERGREEN",
"volatility": "STABLE"
},
"dimensions": [
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Deployment Automation Scripts",
"id": 31,
"rationale": "Implements the scripts and command-line automation used to execute deployments and environment changes. This cluster covers the practical glue code that pipelines and operators rely on.",
"slug": "deployment-automation-scripts",
"source": "db"
},
"input_skill": "PowerShell",
"llm_role": null,
"roles_from_db": [
{
"display_name": "DevOps Engineer",
"id": 1,
"rationale": null,
"role_archetype": "A DevOps Engineer enables reliable, repeatable delivery of software by designing and operating the processes that connect development and production. They focus on improving deployment flow, operational stability, and collaboration between teams through automation, standardization, and monitoring of delivery and runtime practices.",
"slug": "devops-engineer",
"source": "db"
}
]
}
],
"input_skill": "PowerShell",
"matched_via": "alias",
"new_alias_persisted": false,
"new_alias_text": null,
"new_skill_meta": null,
"source_tag": "db",
"was_in_llm_skills": false
},
{
"aliases_in_db": [
{
"alias_text": "JUnit",
"alias_type": "CANONICAL",
"id": 1325,
"is_primary": true,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "JUnit 3",
"alias_type": "VERSION",
"id": 1326,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "JUnit 4",
"alias_type": "VERSION",
"id": 1327,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "JUnit 5",
"alias_type": "VERSION",
"id": 1393,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "JUnit 5.x",
"alias_type": "VERSION",
"id": 1328,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "JUnit Jupiter",
"alias_type": "VERSION",
"id": 1329,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "JUnit Vintage",
"alias_type": "VERSION",
"id": 1395,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
}
],
"canonical": {
"category_id": 6,
"display_name": "JUnit",
"id": 882,
"is_also_category": false,
"is_extractable": true,
"skill_nature": "LIBRARY",
"slug": "junit",
"sub_category_id": 63,
"typical_lifespan": "EVERGREEN",
"volatility": "STABLE"
},
"dimensions": [
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Authentication Flows and Session Handling",
"id": 10,
"rationale": "Client-side implementation of sign-in, sign-out, session persistence, and protected navigation. This is separated from general API integration because auth flows have distinct UX and state concerns.",
"slug": "authentication-flows-and-session-handling",
"source": "db"
},
"input_skill": "JUnit",
"llm_role": null,
"roles_from_db": [
{
"display_name": "Android Engineer",
"id": 15,
"rationale": null,
"role_archetype": null,
"slug": "android-engineer",
"source": "db"
},
{
"display_name": "Frontend Engineer",
"id": 3,
"rationale": null,
"role_archetype": "Frontend Engineers design and build the user-facing parts of applications, translating product and design requirements into interactive experiences. They focus on how the application looks, behaves, and responds in the browser, ensuring usability, accessibility, and consistency across the interface.",
"slug": "frontend-engineer",
"source": "db"
},
{
"display_name": "Full Stack Developer",
"id": 2,
"rationale": null,
"role_archetype": null,
"slug": "full-stack-developer",
"source": "db"
}
]
},
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Test Frameworks and Runners",
"id": 194,
"rationale": "Frameworks and execution tools used to author, organize, and run automated tests. This cluster is coherent because it defines how test cases are structured, parameterized, and reported.",
"slug": "test-frameworks-and-runners",
"source": "db"
},
"input_skill": "JUnit",
"llm_role": null,
"roles_from_db": [
{
"display_name": "Automation Tester",
"id": 16,
"rationale": null,
"role_archetype": null,
"slug": "automation-tester",
"source": "db"
}
]
},
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Testing and Quality Assurance",
"id": 150,
"rationale": "Automated testing approaches used to verify backend behavior across units, integrations, contracts, and end-to-end flows. This cluster is coherent because backend engineers need confidence in request handling, data changes, and service interactions.",
"slug": "testing-and-quality-assurance",
"source": "db"
},
"input_skill": "JUnit",
"llm_role": null,
"roles_from_db": [
{
"display_name": "Backend Engineer",
"id": 14,
"rationale": null,
"role_archetype": null,
"slug": "backend-engineer",
"source": "db"
}
]
}
],
"input_skill": "JUnit",
"matched_via": "alias",
"new_alias_persisted": false,
"new_alias_text": null,
"new_skill_meta": null,
"source_tag": "db",
"was_in_llm_skills": false
},
{
"aliases_in_db": [
{
"alias_text": "Docker",
"alias_type": "CANONICAL",
"id": 299,
"is_primary": true,
"match_strategy": "CASE_INSENSITIVE"
}
],
"canonical": {
"category_id": 11,
"display_name": "Docker",
"id": 153,
"is_also_category": false,
"is_extractable": true,
"skill_nature": "TOOL",
"slug": "docker",
"sub_category_id": 170,
"typical_lifespan": "EVERGREEN",
"volatility": "STABLE"
},
"dimensions": [
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Containerization and Image Delivery",
"id": 24,
"rationale": "Builds, packages, and ships application and support workloads as container images. This cluster covers the artifact format and the mechanics of producing deployable images.",
"slug": "containerization-and-image-delivery",
"source": "db"
},
"input_skill": "Docker",
"llm_role": null,
"roles_from_db": [
{
"display_name": "DevOps Engineer",
"id": 1,
"rationale": null,
"role_archetype": "A DevOps Engineer enables reliable, repeatable delivery of software by designing and operating the processes that connect development and production. They focus on improving deployment flow, operational stability, and collaboration between teams through automation, standardization, and monitoring of delivery and runtime practices.",
"slug": "devops-engineer",
"source": "db"
}
]
},
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Model Serving Deployment and Runtime Packaging",
"id": 52,
"rationale": "Operational deployment of trained models into online, batch, or streaming serving environments, including packaging models and model servers into containers or managed inference runtimes, coordinating rollout, and handing off to inference systems. Covers serving frameworks and platforms such as TensorFlow Serving, TorchServe, Triton Inference Server, BentoML, KServe, and Seldon Core, plus container/runtime concerns like Docker images, GPU-enabled containers, base image selection, container entrypoints, runtime dependencies, and image scanning for model services.",
"slug": "model-serving-deployment-and-runtime-packaging",
"source": "db"
},
"input_skill": "Docker",
"llm_role": null,
"roles_from_db": [
{
"display_name": "MLOps Engineer",
"id": 5,
"rationale": null,
"role_archetype": null,
"slug": "mlops-engineer",
"source": "db"
},
{
"display_name": "Machine Learning Engineer",
"id": 10,
"rationale": null,
"role_archetype": null,
"slug": "machine-learning-engineer",
"source": "db"
}
]
}
],
"input_skill": "Docker",
"matched_via": "alias",
"new_alias_persisted": false,
"new_alias_text": null,
"new_skill_meta": null,
"source_tag": "db",
"was_in_llm_skills": false
},
{
"aliases_in_db": [
{
"alias_text": "REST APIs",
"alias_type": "CANONICAL",
"id": 174,
"is_primary": true,
"match_strategy": "CASE_INSENSITIVE"
}
],
"canonical": {
"category_id": 8,
"display_name": "REST APIs",
"id": 49,
"is_also_category": false,
"is_extractable": true,
"skill_nature": "PROTOCOL",
"slug": "rest-apis",
"sub_category_id": 67,
"typical_lifespan": "EVERGREEN",
"volatility": "STABLE"
},
"dimensions": [
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "API Integration and Data Fetching",
"id": 9,
"rationale": "Connecting frontend applications to backend services and third-party endpoints. This covers request orchestration, error handling, pagination, and shaping remote data for UI consumption.",
"slug": "api-integration-and-data-fetching",
"source": "db"
},
"input_skill": "REST APIs",
"llm_role": null,
"roles_from_db": [
{
"display_name": "Frontend Engineer",
"id": 3,
"rationale": null,
"role_archetype": "Frontend Engineers design and build the user-facing parts of applications, translating product and design requirements into interactive experiences. They focus on how the application looks, behaves, and responds in the browser, ensuring usability, accessibility, and consistency across the interface.",
"slug": "frontend-engineer",
"source": "db"
},
{
"display_name": "Full Stack Developer",
"id": 2,
"rationale": null,
"role_archetype": null,
"slug": "full-stack-developer",
"source": "db"
}
]
},
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "API Integration and Serialization",
"id": 128,
"rationale": "Client-side integration with backend services, including request handling, response parsing, and contract alignment. This cluster is coherent because iOS features frequently depend on stable data exchange with server APIs.",
"slug": "api-integration-and-serialization",
"source": "db"
},
"input_skill": "REST APIs",
"llm_role": null,
"roles_from_db": [
{
"display_name": "iOS Engineer",
"id": 13,
"rationale": null,
"role_archetype": null,
"slug": "ios-engineer",
"source": "db"
}
]
},
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Network Automation and Scripting",
"id": 285,
"rationale": "Covers scripts and automation used to configure, validate, and audit network devices and services. This cluster is coherent because repeatable network operations increasingly depend on programmatic changes and checks.",
"slug": "network-automation-and-scripting",
"source": "db"
},
"input_skill": "REST APIs",
"llm_role": null,
"roles_from_db": [
{
"display_name": "Network Engineer",
"id": 21,
"rationale": null,
"role_archetype": null,
"slug": "network-engineer",
"source": "db"
}
]
}
],
"input_skill": "REST APIs",
"matched_via": "alias",
"new_alias_persisted": false,
"new_alias_text": null,
"new_skill_meta": null,
"source_tag": "db",
"was_in_llm_skills": false
},
{
"aliases_in_db": [
{
"alias_text": "Jenkins",
"alias_type": "CANONICAL",
"id": 1799,
"is_primary": true,
"match_strategy": "CASE_INSENSITIVE"
}
],
"canonical": {
"category_id": 11,
"display_name": "Jenkins",
"id": 1249,
"is_also_category": false,
"is_extractable": true,
"skill_nature": "TOOL",
"slug": "jenkins",
"sub_category_id": 166,
"typical_lifespan": "EVERGREEN",
"volatility": "STABLE"
},
"dimensions": [
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Continuous Integration Test Integration",
"id": 207,
"rationale": "Integrating automated checks into shared build and merge workflows so results are repeatable and visible. This cluster is coherent because automation testers commonly configure test execution triggers, artifacts, and reporting hooks.",
"slug": "continuous-integration-test-integration",
"source": "db"
},
"input_skill": "Jenkins",
"llm_role": null,
"roles_from_db": [
{
"display_name": "Automation Tester",
"id": 16,
"rationale": null,
"role_archetype": null,
"slug": "automation-tester",
"source": "db"
}
]
}
],
"input_skill": "Jenkins",
"matched_via": "alias",
"new_alias_persisted": false,
"new_alias_text": null,
"new_skill_meta": null,
"source_tag": "db",
"was_in_llm_skills": false
},
{
"aliases_in_db": [
{
"alias_text": "Python",
"alias_type": "CANONICAL",
"id": 608,
"is_primary": true,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "Python 2",
"alias_type": "VERSION",
"id": 611,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "Python 2.x",
"alias_type": "VERSION",
"id": 613,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "Python 3",
"alias_type": "VERSION",
"id": 612,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "Python 3.10",
"alias_type": "VERSION",
"id": 2330,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "Python 3.11",
"alias_type": "VERSION",
"id": 2331,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "Python 3.12",
"alias_type": "VERSION",
"id": 2332,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "Python 3.x",
"alias_type": "VERSION",
"id": 614,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "py2",
"alias_type": "VERSION",
"id": 609,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "py3",
"alias_type": "VERSION",
"id": 610,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "python 2",
"alias_type": "VERSION",
"id": 2152,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "python 2.x",
"alias_type": "VERSION",
"id": 2154,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "python 3",
"alias_type": "VERSION",
"id": 990,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "python 3.10",
"alias_type": "VERSION",
"id": 992,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "python 3.11",
"alias_type": "VERSION",
"id": 993,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "python 3.12",
"alias_type": "VERSION",
"id": 994,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "python 3.x",
"alias_type": "VERSION",
"id": 991,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "python2",
"alias_type": "VERSION",
"id": 2150,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "python3",
"alias_type": "VERSION",
"id": 989,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
}
],
"canonical": {
"category_id": 5,
"display_name": "Python",
"id": 393,
"is_also_category": false,
"is_extractable": true,
"skill_nature": "LANGUAGE",
"slug": "python",
"sub_category_id": 54,
"typical_lifespan": "EVERGREEN",
"volatility": "STABLE"
},
"dimensions": [
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Analytical Programming Languages",
"id": 82,
"rationale": "Languages used to clean, transform, analyze, and prototype models in notebooks and scripts. This is the core coding surface for expressing statistical logic and data manipulation in a reproducible way.",
"slug": "analytical-programming-languages",
"source": "db"
},
"input_skill": "Python",
"llm_role": null,
"roles_from_db": [
{
"display_name": "Data Analyst",
"id": 20,
"rationale": null,
"role_archetype": null,
"slug": "data-analyst",
"source": "db"
},
{
"display_name": "Data Scientist",
"id": 7,
"rationale": null,
"role_archetype": null,
"slug": "data-scientist",
"source": "db"
}
]
},
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Automation Scripting and CLI",
"id": 48,
"rationale": "Uses scripts and command-line tooling to execute repeatable Azure operations and reduce manual work. This is a practical cluster because the role frequently automates provisioning, checks, and remediation tasks.",
"slug": "automation-scripting-and-cli",
"source": "db"
},
"input_skill": "Python",
"llm_role": null,
"roles_from_db": [
{
"display_name": "Azure Cloud Engineer",
"id": 4,
"rationale": null,
"role_archetype": null,
"slug": "azure-cloud-engineer",
"source": "db"
},
{
"display_name": "Cloud Engineer",
"id": 18,
"rationale": null,
"role_archetype": null,
"slug": "cloud-engineer",
"source": "db"
}
]
},
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Network Automation and Scripting",
"id": 285,
"rationale": "Covers scripts and automation used to configure, validate, and audit network devices and services. This cluster is coherent because repeatable network operations increasingly depend on programmatic changes and checks.",
"slug": "network-automation-and-scripting",
"source": "db"
},
"input_skill": "Python",
"llm_role": null,
"roles_from_db": [
{
"display_name": "Network Engineer",
"id": 21,
"rationale": null,
"role_archetype": null,
"slug": "network-engineer",
"source": "db"
}
]
},
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Programming Languages for AI Workflows",
"id": 261,
"rationale": "Languages used to implement AI feature logic, orchestration, and response handling inside product code. This is the core coding surface for turning prompts and model calls into reliable application behavior.",
"slug": "programming-languages-for-ai-workflows",
"source": "db"
},
"input_skill": "Python",
"llm_role": null,
"roles_from_db": [
{
"display_name": "AI Engineer",
"id": 12,
"rationale": null,
"role_archetype": null,
"slug": "ai-engineer",
"source": "db"
}
]
},
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Programming Languages for Backend Systems",
"id": 140,
"rationale": "Languages used to implement server-side business logic, request handlers, workers, and service integrations. This is the core coding surface for backend feature delivery and maintenance.",
"slug": "programming-languages-for-backend-systems",
"source": "db"
},
"input_skill": "Python",
"llm_role": null,
"roles_from_db": [
{
"display_name": "Backend Engineer",
"id": 14,
"rationale": null,
"role_archetype": null,
"slug": "backend-engineer",
"source": "db"
}
]
},
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Programming Languages for Data Work",
"id": 67,
"rationale": "Languages used to implement data pipelines, transformations, and operational utilities. This is the code layer for expressing extraction, parsing, validation, and orchestration logic in data engineering workflows.",
"slug": "programming-languages-for-data-work",
"source": "db"
},
"input_skill": "Python",
"llm_role": null,
"roles_from_db": [
{
"display_name": "Data Engineer",
"id": 6,
"rationale": null,
"role_archetype": null,
"slug": "data-engineer",
"source": "db"
}
]
},
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Programming Languages for ML Systems",
"id": 113,
"rationale": "Languages used to implement model integration code, inference services, and feature-processing logic. This is the core coding surface for turning trained models into product-facing software components.",
"slug": "programming-languages-for-ml-systems",
"source": "db"
},
"input_skill": "Python",
"llm_role": null,
"roles_from_db": [
{
"display_name": "Machine Learning Engineer",
"id": 10,
"rationale": null,
"role_archetype": null,
"slug": "machine-learning-engineer",
"source": "db"
}
]
},
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Programming Languages for Test Automation",
"id": 193,
"rationale": "Languages used to implement automated checks, helper utilities, and test harness code. This is the core coding surface for turning test ideas into maintainable automation.",
"slug": "programming-languages-for-test-automation",
"source": "db"
},
"input_skill": "Python",
"llm_role": null,
"roles_from_db": [
{
"display_name": "Automation Tester",
"id": 16,
"rationale": null,
"role_archetype": null,
"slug": "automation-tester",
"source": "db"
}
]
},
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Security Automation and Scripting",
"id": 258,
"rationale": "Automating repeatable security checks, enrichment, and remediation workflows. This cluster is coherent because the role often needs lightweight automation to scale analysis and response.",
"slug": "security-automation-and-scripting",
"source": "db"
},
"input_skill": "Python",
"llm_role": null,
"roles_from_db": [
{
"display_name": "Cybersecurity Engineer",
"id": 9,
"rationale": null,
"role_archetype": null,
"slug": "cybersecurity-engineer",
"source": "db"
}
]
}
],
"input_skill": "Python",
"matched_via": "alias",
"new_alias_persisted": false,
"new_alias_text": null,
"new_skill_meta": null,
"source_tag": "db",
"was_in_llm_skills": false
},
{
"aliases_in_db": [
{
"alias_text": "Azure",
"alias_type": "CANONICAL",
"id": 349,
"is_primary": true,
"match_strategy": "CASE_INSENSITIVE"
}
],
"canonical": {
"category_id": 13,
"display_name": "Azure",
"id": 164,
"is_also_category": false,
"is_extractable": true,
"skill_nature": "PLATFORM",
"slug": "azure",
"sub_category_id": 161,
"typical_lifespan": "EVERGREEN",
"volatility": "STABLE"
},
"dimensions": [
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Cloud Platform Operations",
"id": 26,
"rationale": "Uses cloud provider services to support delivery and runtime environments. The focus is on consumer-level operation of cloud services rather than deep cloud architecture ownership.",
"slug": "cloud-platform-operations",
"source": "db"
},
"input_skill": "Azure",
"llm_role": null,
"roles_from_db": [
{
"display_name": "DevOps Engineer",
"id": 1,
"rationale": null,
"role_archetype": "A DevOps Engineer enables reliable, repeatable delivery of software by designing and operating the processes that connect development and production. They focus on improving deployment flow, operational stability, and collaboration between teams through automation, standardization, and monitoring of delivery and runtime practices.",
"slug": "devops-engineer",
"source": "db"
}
]
}
],
"input_skill": "Azure",
"matched_via": "alias",
"new_alias_persisted": false,
"new_alias_text": null,
"new_skill_meta": null,
"source_tag": "db",
"was_in_llm_skills": false
},
{
"aliases_in_db": [
{
"alias_text": "Bash scripting",
"alias_type": "CANONICAL",
"id": 373,
"is_primary": true,
"match_strategy": "CASE_INSENSITIVE"
}
],
"canonical": {
"category_id": 5,
"display_name": "Bash scripting",
"id": 188,
"is_also_category": false,
"is_extractable": true,
"skill_nature": "LANGUAGE",
"slug": "bash-scripting",
"sub_category_id": 146,
"typical_lifespan": "EVERGREEN",
"volatility": "STABLE"
},
"dimensions": [
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Deployment Automation Scripts",
"id": 31,
"rationale": "Implements the scripts and command-line automation used to execute deployments and environment changes. This cluster covers the practical glue code that pipelines and operators rely on.",
"slug": "deployment-automation-scripts",
"source": "db"
},
"input_skill": "Bash scripting",
"llm_role": null,
"roles_from_db": [
{
"display_name": "DevOps Engineer",
"id": 1,
"rationale": null,
"role_archetype": "A DevOps Engineer enables reliable, repeatable delivery of software by designing and operating the processes that connect development and production. They focus on improving deployment flow, operational stability, and collaboration between teams through automation, standardization, and monitoring of delivery and runtime practices.",
"slug": "devops-engineer",
"source": "db"
}
]
},
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "MySQL Automation and Scripting",
"id": 176,
"rationale": "Covers scripts and operational automation used to run repeatable DBA tasks. This cluster is coherent because production database administration depends on safe, repeatable execution of checks, maintenance, and change steps.",
"slug": "mysql-automation-and-scripting",
"source": "db"
},
"input_skill": "Bash scripting",
"llm_role": null,
"roles_from_db": [
{
"display_name": "MySQL DBA",
"id": 23,
"rationale": null,
"role_archetype": null,
"slug": "mysql-dba",
"source": "db"
}
]
}
],
"input_skill": "Bash scripting",
"matched_via": "alias",
"new_alias_persisted": false,
"new_alias_text": null,
"new_skill_meta": null,
"source_tag": "db",
"was_in_llm_skills": false
},
{
"aliases_in_db": [
{
"alias_text": "AWS",
"alias_type": "CANONICAL",
"id": 348,
"is_primary": true,
"match_strategy": "CASE_INSENSITIVE"
}
],
"canonical": {
"category_id": 13,
"display_name": "AWS",
"id": 163,
"is_also_category": false,
"is_extractable": true,
"skill_nature": "PLATFORM",
"slug": "aws",
"sub_category_id": 161,
"typical_lifespan": "EVERGREEN",
"volatility": "STABLE"
},
"dimensions": [
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Cloud Platform Operations",
"id": 26,
"rationale": "Uses cloud provider services to support delivery and runtime environments. The focus is on consumer-level operation of cloud services rather than deep cloud architecture ownership.",
"slug": "cloud-platform-operations",
"source": "db"
},
"input_skill": "AWS",
"llm_role": null,
"roles_from_db": [
{
"display_name": "DevOps Engineer",
"id": 1,
"rationale": null,
"role_archetype": "A DevOps Engineer enables reliable, repeatable delivery of software by designing and operating the processes that connect development and production. They focus on improving deployment flow, operational stability, and collaboration between teams through automation, standardization, and monitoring of delivery and runtime practices.",
"slug": "devops-engineer",
"source": "db"
}
]
}
],
"input_skill": "AWS",
"matched_via": "alias",
"new_alias_persisted": false,
"new_alias_text": null,
"new_skill_meta": null,
"source_tag": "db",
"was_in_llm_skills": false
},
{
"aliases_in_db": [],
"canonical": null,
"dimensions": [
{
"dimension": {
"difficulty_hint": null,
"display_name": "Artificial Intelligence",
"id": null,
"rationale": "Covers the broad concept of AI systems and capabilities, including how intelligent behavior is applied in software and cloud solutions. The target skill belongs here because it is the umbrella term for AI-related work when no narrower sub-skill is specified.",
"slug": "d_init_01",
"source": "llm"
},
"input_skill": "AI",
"llm_role": null,
"roles_from_db": []
}
],
"input_skill": "AI",
"matched_via": null,
"new_alias_persisted": false,
"new_alias_text": null,
"new_skill_meta": {
"derived": {
"category": "Concept",
"skill_nature": "CONCEPT",
"sub_category": "artificial_intelligence",
"typical_lifespan": "EVERGREEN",
"version_strategy": "NOT_APPLICABLE",
"volatility": "STABLE"
},
"enrichment": {
"ambiguity": {
"ambiguity_flag": true,
"confused_with": [
"machine_learning",
"artificial_intelligence"
],
"reasoning": "\"AI\" is a common abbreviation that can mean artificial intelligence, but in JDs it may also be used loosely to refer to machine learning or related AI/ML work, so an extractor could confuse it with nearby catalog skills."
},
"context_keywords": {
"context_keywords": [
"machine learning",
"deep learning",
"neural networks",
"NLP",
"computer vision",
"reinforcement learning",
"model training",
"inference",
"feature engineering",
"transformers",
"LLM",
"MLOps",
"TensorFlow",
"PyTorch",
"prompt engineering"
]
},
"maturity": {
"confidence": 0.93,
"maturity": "well_known",
"reasoning": "AI appears in a large and growing share of job descriptions across software, data, and product roles, and major vendors (Microsoft, Google, AWS) have broad AI platform offerings, indicating mainstream adoption."
},
"skill_id": "ai",
"vendor_license": {
"confidence": 0.99,
"license": null,
"vendor": null,
"year_introduced": null
},
"versioning": {
"current_version": null,
"version_aliases": {},
"versioned": false
}
},
"keep_log": [],
"locked_dimensions": [
{
"description": "Covers the broad concept of AI systems and capabilities, including how intelligent behavior is applied in software and cloud solutions. The target skill belongs here because it is the umbrella term for AI-related work when no narrower sub-skill is specified.",
"exemplar_skills": [
"AI",
"machine learning",
"generative AI",
"inference",
"prompt engineering",
"AI applications"
],
"in_scope": "AI, machine learning, generative AI, inference, model usage, prompt-based features, AI-enabled applications, AI platform concepts",
"name": "Artificial Intelligence",
"out_of_scope": "Specific model training workflows, model serving deployment, service architecture patterns, fallback and guardrail handling, these belong to narrower AI operations or architecture dimensions",
"overlap_flags": [
{
"reason": "AI often overlaps with how AI capabilities are embedded into services and application flows.",
"with_dim_id": "ai-service-architecture-patterns",
"with_dim_name": null,
"with_role": "AI Engineer"
},
{
"reason": "AI can overlap with operational deployment of models, but that is a distinct runtime/serving concern.",
"with_dim_id": "model-serving-deployment-and-runtime-packaging",
"with_dim_name": null,
"with_role": "MLOps Engineer, Machine Learning Engineer"
},
{
"reason": "AI implementations often need safety and fallback logic, but that is a separate resilience dimension.",
"with_dim_id": "fallback-and-guardrail-handling",
"with_dim_name": null,
"with_role": "Machine Learning Engineer"
}
],
"tentative_id": "d_init_01"
}
],
"merge_log": [],
"placed": {
"name": "AI",
"placement_confidence": 0.92,
"primary_dimension": "d_init_01",
"reasoning": "Deterministic JD placement: locked_dimensions has 1 dimension(s) from skill-driven dimension generation after reconciliation; primary_dimension is the first locked dim.",
"secondary_dimensions": [],
"skill_id": "ai"
},
"relationships": {
"child_skills": [],
"parent_skills": [],
"related_to": [],
"requires": [],
"skill_id": "ai",
"suppress_on_match": []
},
"skill_id": "ai",
"split_log": [],
"typed": {
"alternatives_considered": [],
"confidence": 0.98,
"name": "AI",
"reasoning": "AI is fundamentally a named knowledge unit about intelligent systems, so by the Concept vs Methodology rule it is a Concept rather than a tool, platform, or architecture.",
"skill_id": "ai",
"subtype": "artificial_intelligence",
"type": "Concept"
},
"warnings": []
},
"source_tag": "llm",
"was_in_llm_skills": true
},
{
"aliases_in_db": [],
"canonical": null,
"dimensions": [
{
"dimension": {
"difficulty_hint": null,
"display_name": "API Management Platforms",
"id": null,
"rationale": "Covers managed API gateway and lifecycle capabilities such as publishing, routing, throttling, versioning, and policy enforcement. APIM belongs here because it is commonly used to expose, secure, and govern APIs in cloud environments.",
"slug": "d_init_01",
"source": "llm"
},
"input_skill": "APIM",
"llm_role": null,
"roles_from_db": []
}
],
"input_skill": "APIM",
"matched_via": null,
"new_alias_persisted": false,
"new_alias_text": null,
"new_skill_meta": {
"derived": {
"category": "Platform",
"skill_nature": "PLATFORM",
"sub_category": "api_management_platform",
"typical_lifespan": "EVERGREEN",
"version_strategy": "NOT_APPLICABLE",
"volatility": "STABLE"
},
"enrichment": {
"ambiguity": {
"ambiguity_flag": true,
"confused_with": [
"azure_api_management",
"api_management"
],
"reasoning": "APIM is commonly shorthand for Azure API Management, and in JDs it may be written as API management generally. A parser could confuse this platform-specific acronym with the broader API management skill."
},
"context_keywords": {
"context_keywords": [
"Azure API Management",
"gateway",
"policies",
"developer portal",
"subscriptions",
"products",
"rate limiting",
"throttling",
"OpenAPI",
"Swagger",
"JWT",
"OAuth 2.0",
"backend services",
"revision",
"versioning"
]
},
"maturity": {
"confidence": 0.84,
"maturity": "well_known",
"reasoning": "API management platforms (e.g., Azure API Management, Apigee, Kong) appear frequently in cloud/platform job descriptions and are standard in enterprise API programs; vendor docs and hiring demand show broad adoption."
},
"skill_id": "apim",
"vendor_license": {
"confidence": 0.93,
"license": "proprietary",
"vendor": "Microsoft",
"year_introduced": 2013
},
"versioning": {
"current_version": null,
"version_aliases": {},
"versioned": false
}
},
"keep_log": [],
"locked_dimensions": [
{
"description": "Covers managed API gateway and lifecycle capabilities such as publishing, routing, throttling, versioning, and policy enforcement. APIM belongs here because it is commonly used to expose, secure, and govern APIs in cloud environments.",
"exemplar_skills": [
"APIM",
"Azure API Management",
"API gateway configuration",
"API policy management",
"API versioning",
"developer portal setup",
"rate limiting",
"request transformation"
],
"in_scope": "APIM, Azure API Management, API gateway configuration, API publishing, routing policies, rate limiting, quotas, versioning, developer portals, subscription keys, request/response transformation",
"name": "API Management Platforms",
"out_of_scope": "Service decomposition and inter-service call design, which belong to service-architecture-and-integration; identity provider setup and user-role administration, which belong to identity-and-access-configuration; cloud perimeter controls, which belong to cloud-security-guardrails",
"overlap_flags": [
{
"reason": "API management often sits alongside service design, but this dimension focuses on gateway/runtime policy rather than how services are decomposed or integrated.",
"with_dim_id": "service-architecture-and-integration",
"with_dim_name": null,
"with_role": "Backend Engineer"
},
{
"reason": "APIM enforces security controls like auth and throttling, but broader cloud security architecture is owned by the guardrails dimension.",
"with_dim_id": "cloud-security-guardrails",
"with_dim_name": null,
"with_role": "Cloud Architect, Cloud Engineer, Cybersecurity Engineer"
}
],
"tentative_id": "d_init_01"
}
],
"merge_log": [],
"placed": {
"name": "APIM",
"placement_confidence": 0.92,
"primary_dimension": "d_init_01",
"reasoning": "Deterministic JD placement: locked_dimensions has 1 dimension(s) from skill-driven dimension generation after reconciliation; primary_dimension is the first locked dim.",
"secondary_dimensions": [],
"skill_id": "apim"
},
"relationships": {
"child_skills": [],
"parent_skills": [],
"related_to": [
"rest-apis",
"grpc",
"aws-iam",
"rbac",
"saml",
"portal-pages"
],
"requires": [],
"skill_id": "apim",
"suppress_on_match": []
},
"skill_id": "apim",
"split_log": [],
"typed": {
"alternatives_considered": [],
"confidence": 0.9,
"name": "APIM",
"reasoning": "By the Platform vs Tool rule, APIM is best treated as a hosted, multi-tenant API management environment with managed capabilities rather than a single user-run tool.",
"skill_id": "apim",
"subtype": "api_management_platform",
"type": "Platform"
},
"warnings": []
},
"source_tag": "llm",
"was_in_llm_skills": true
},
{
"aliases_in_db": [],
"canonical": null,
"dimensions": [
{
"dimension": {
"difficulty_hint": null,
"display_name": "Authentication",
"id": null,
"rationale": "Mechanisms for verifying identity and establishing a trusted user or service session. This covers the core authentication concept itself, which is broader than any one client flow or platform-specific access setup.",
"slug": "d_init_01",
"source": "llm"
},
"input_skill": "Authentication",
"llm_role": null,
"roles_from_db": []
}
],
"input_skill": "Authentication",
"matched_via": null,
"new_alias_persisted": false,
"new_alias_text": null,
"new_skill_meta": {
"derived": {
"category": "Concept",
"skill_nature": "CONCEPT",
"sub_category": "security_concept",
"typical_lifespan": "EVERGREEN",
"version_strategy": "NOT_APPLICABLE",
"volatility": "STABLE"
},
"enrichment": {
"ambiguity": {
"ambiguity_flag": false,
"confused_with": [],
"reasoning": "Authentication is a standard, well-scoped security concept in JDs and is unlikely to be mistaken for a different catalog skill."
},
"context_keywords": {
"context_keywords": [
"OAuth 2.0",
"OpenID Connect",
"SAML",
"JWT",
"SSO",
"MFA",
"2FA",
"identity provider",
"session management",
"token-based authentication",
"passwordless",
"federated identity",
"authorization",
"access control",
"refresh token"
]
},
"maturity": {
"confidence": 0.96,
"maturity": "well_known",
"reasoning": "Authentication is a core requirement in most software JDs and security roles; market demand is broad across web, mobile, cloud, and IAM stacks, with common listings for OAuth2/OIDC, SSO, and MFA."
},
"skill_id": "authentication",
"vendor_license": {
"confidence": 0.99,
"license": null,
"vendor": null,
"year_introduced": null
},
"versioning": {
"current_version": null,
"version_aliases": {},
"versioned": false
}
},
"keep_log": [
{
"a_dim_id": "d_init_01",
"a_name": "Authentication",
"a_role": "__skill_focal__",
"b_dim_id": "authentication-flows-and-session-handling",
"b_name": "Authentication Flows and Session Handling",
"b_role": "Android Engineer",
"pair_kind": "cross_role",
"reasoning": "Dim A is the general auth concept: verifying identity and establishing a trusted session, including password login, MFA challenge handling, SSO handoff, token refresh, and session persistence. Dim B is Android-specific client-side work: sign-in/sign-out flows, session persistence, and protected navigation, with emphasis on UX and state handling. The overlap on login/session terms is real, but A covers the underlying authentication mechanisms while B covers app-layer flow implementation, so they are distinct.",
"similarity": 0.6545647233260281
}
],
"locked_dimensions": [
{
"description": "Mechanisms for verifying identity and establishing a trusted user or service session. This covers the core authentication concept itself, which is broader than any one client flow or platform-specific access setup.",
"exemplar_skills": [
"Authentication",
"Sign-in flow implementation",
"Session management",
"Token refresh handling",
"Multi-factor authentication",
"Single sign-on integration"
],
"in_scope": "Authentication, sign-in, sign-out, login flows, session persistence, token refresh, password-based login, MFA challenge handling, SSO handoff",
"name": "Authentication",
"out_of_scope": "Authorization policy, role-based access control, cloud IAM, network perimeter controls, password hashing internals, identity provider administration",
"overlap_flags": [
{
"reason": "Client-side auth flows and session persistence are a close sub-area, but this dimension is the broader identity-verification concept.",
"with_dim_id": "authentication-flows-and-session-handling",
"with_dim_name": null,
"with_role": "Android Engineer, Frontend Engineer, Full Stack Developer"
},
{
"reason": "Authentication often depends on identity provider and access setup, but that catalog dimension owns platform-side configuration.",
"with_dim_id": "identity-and-access-configuration",
"with_dim_name": null,
"with_role": "ServiceNOW Developer"
},
{
"reason": "Authentication implementations in apps intersect with secure token handling, but broader browser security concerns belong there.",
"with_dim_id": "frontend-security-practices",
"with_dim_name": null,
"with_role": "Frontend Engineer, Full Stack Developer"
}
],
"tentative_id": "d_init_01"
}
],
"merge_log": [],
"placed": {
"name": "Authentication",
"placement_confidence": 0.92,
"primary_dimension": "d_init_01",
"reasoning": "Deterministic JD placement: locked_dimensions has 1 dimension(s) from skill-driven dimension generation after reconciliation; primary_dimension is the first locked dim.",
"secondary_dimensions": [],
"skill_id": "authentication"
},
"relationships": {
"child_skills": [],
"parent_skills": [],
"related_to": [
"jwt",
"oauth-2-0",
"saml",
"openid-connect",
"session-cookies",
"managed-identities",
"rbac",
"aws-iam",
"refresh-tokens"
],
"requires": [],
"skill_id": "authentication",
"suppress_on_match": []
},
"skill_id": "authentication",
"split_log": [],
"typed": {
"alternatives_considered": [],
"confidence": 0.96,
"name": "Authentication",
"reasoning": "Authentication is a named knowledge unit about verifying identity, so by the Concept vs Methodology rule it is a Concept rather than a tool, protocol, or standard.",
"skill_id": "authentication",
"subtype": "security_concept",
"type": "Concept"
},
"warnings": []
},
"source_tag": "llm",
"was_in_llm_skills": true
},
{
"aliases_in_db": [],
"canonical": null,
"dimensions": [
{
"dimension": {
"difficulty_hint": null,
"display_name": "Continuous Delivery",
"id": null,
"rationale": "Covers automating the path from a validated build to deployable releases across environments. CD belongs here because it is the standard engineering practice for reliably promoting changes through delivery pipelines.",
"slug": "d_init_01",
"source": "llm"
},
"input_skill": "CD",
"llm_role": null,
"roles_from_db": []
}
],
"input_skill": "CD",
"matched_via": null,
"new_alias_persisted": false,
"new_alias_text": null,
"new_skill_meta": {
"derived": {
"category": "Methodology",
"skill_nature": "METHODOLOGY",
"sub_category": "continuous_delivery",
"typical_lifespan": "EVERGREEN",
"version_strategy": "NOT_APPLICABLE",
"volatility": "STABLE"
},
"enrichment": {
"ambiguity": {
"ambiguity_flag": true,
"confused_with": [
"continuous_integration",
"circular_dependency"
],
"reasoning": "\"CD\" is a common abbreviation for continuous delivery, but in JDs it can also mean continuous deployment or be read as circular dependency. The acronym is short enough that extractors may confuse it with nearby catalog skills."
},
"context_keywords": {
"context_keywords": [
"CI/CD",
"deployment pipeline",
"release automation",
"blue-green deployment",
"canary release",
"rollback",
"feature flags",
"artifact repository",
"build pipeline",
"staging environment",
"production deployment",
"versioning",
"infrastructure as code",
"Jenkins",
"GitLab CI"
]
},
"maturity": {
"confidence": 0.92,
"maturity": "well_known",
"reasoning": "Continuous Delivery is a standard DevOps practice; it appears in many software engineering JDs and is reinforced by major cloud/vendor docs and platform tooling (e.g., GitHub Actions, GitLab CI, Azure DevOps) built around it."
},
"skill_id": "cd",
"vendor_license": {
"confidence": 0.99,
"license": null,
"vendor": null,
"year_introduced": null
},
"versioning": {
"current_version": null,
"version_aliases": {},
"versioned": false
}
},
"keep_log": [],
"locked_dimensions": [
{
"description": "Covers automating the path from a validated build to deployable releases across environments. CD belongs here because it is the standard engineering practice for reliably promoting changes through delivery pipelines.",
"exemplar_skills": [
"CD",
"continuous delivery",
"deployment automation",
"release promotion",
"deployment approvals",
"canary rollout",
"release orchestration"
],
"in_scope": "CD, continuous delivery pipelines, automated release promotion, deployment automation, release gates, canary rollout steps, environment promotion, deployment approvals, release orchestration",
"name": "Continuous Delivery",
"out_of_scope": "Continuous integration build/test execution, which belongs to build and execution tooling; runtime scaling and fault tolerance, which belong to resilience engineering; post-release monitoring, which belongs to observability",
"overlap_flags": [
{
"reason": "CD commonly starts from build artifacts, but the core skill is delivery automation rather than compiling or running tests.",
"with_dim_id": "build-and-execution-tooling",
"with_dim_name": null,
"with_role": "Automation Tester"
},
{
"reason": "Both involve moving software across environments, but this dimension is specifically the delivery pipeline and release mechanics.",
"with_dim_id": "environment-provisioning-and-promotion",
"with_dim_name": null,
"with_role": "DevOps Engineer"
}
],
"tentative_id": "d_init_01"
}
],
"merge_log": [],
"placed": {
"name": "CD",
"placement_confidence": 0.92,
"primary_dimension": "d_init_01",
"reasoning": "Deterministic JD placement: locked_dimensions has 1 dimension(s) from skill-driven dimension generation after reconciliation; primary_dimension is the first locked dim.",
"secondary_dimensions": [],
"skill_id": "cd"
},
"relationships": {
"child_skills": [],
"parent_skills": [],
"related_to": [
"contract-tests",
"scorecards",
"defect-retest"
],
"requires": [],
"skill_id": "cd",
"suppress_on_match": []
},
"skill_id": "cd",
"split_log": [],
"typed": {
"alternatives_considered": [],
"confidence": 0.93,
"name": "CD",
"reasoning": "CD here most naturally means Continuous Delivery, which is a way of working for releasing software, so by the Concept vs Methodology rule it is a Methodology.",
"skill_id": "cd",
"subtype": "continuous_delivery",
"type": "Methodology"
},
"warnings": []
},
"source_tag": "llm",
"was_in_llm_skills": true
},
{
"aliases_in_db": [],
"canonical": null,
"dimensions": [
{
"dimension": {
"difficulty_hint": null,
"display_name": "Continuous Integration Practices",
"id": null,
"rationale": "Covers the automation that builds, tests, and validates code changes whenever they are merged or proposed. CI belongs here because it is the core delivery discipline for keeping changes integrated and verifiable in cloud and software engineering workflows.",
"slug": "d_init_01",
"source": "llm"
},
"input_skill": "CI",
"llm_role": null,
"roles_from_db": []
}
],
"input_skill": "CI",
"matched_via": null,
"new_alias_persisted": false,
"new_alias_text": null,
"new_skill_meta": {
"derived": {
"category": "Methodology",
"skill_nature": "METHODOLOGY",
"sub_category": "continuous_integration_methodology",
"typical_lifespan": "EVERGREEN",
"version_strategy": "NOT_APPLICABLE",
"volatility": "STABLE"
},
"enrichment": {
"ambiguity": {
"ambiguity_flag": true,
"confused_with": [
"continuous_delivery",
"continuous_deployment"
],
"reasoning": "\"CI\" is a common abbreviation for continuous integration, but in JDs it can be conflated with closely related DevOps terms like continuous delivery/deployment, especially when shorthand is used loosely."
},
"context_keywords": {
"context_keywords": [
"Jenkins",
"GitHub Actions",
"GitLab CI",
"CircleCI",
"Travis CI",
"Azure DevOps",
"build pipeline",
"automated testing",
"unit tests",
"integration tests",
"artifact",
"pipeline as code",
"merge request",
"pull request",
"deployment"
]
},
"maturity": {
"confidence": 0.95,
"maturity": "well_known",
"reasoning": "CI is a standard hiring-pipeline requirement in many software JDs, and major platforms like GitHub Actions, GitLab CI, and Jenkins show broad ecosystem adoption."
},
"skill_id": "ci",
"vendor_license": {
"confidence": 0.99,
"license": null,
"vendor": null,
"year_introduced": null
},
"versioning": {
"current_version": null,
"version_aliases": {},
"versioned": false
}
},
"keep_log": [],
"locked_dimensions": [
{
"description": "Covers the automation that builds, tests, and validates code changes whenever they are merged or proposed. CI belongs here because it is the core delivery discipline for keeping changes integrated and verifiable in cloud and software engineering workflows.",
"exemplar_skills": [
"CI",
"continuous integration",
"build triggers",
"automated unit tests",
"merge validation",
"pipeline status checks"
],
"in_scope": "CI, continuous integration, build triggers, automated unit tests, integration checks, linting, static analysis, merge validation, pipeline status checks, pull request gating",
"name": "Continuous Integration Practices",
"out_of_scope": "Continuous delivery/release promotion, runtime deployment orchestration, environment provisioning, production monitoring, which are owned by deployment and operations dimensions",
"overlap_flags": [
{
"reason": "CI pipelines often use build tools and runners, but this dimension is about the integration practice rather than the tooling itself.",
"with_dim_id": "build-and-execution-tooling",
"with_dim_name": null,
"with_role": "Automation Tester"
},
{
"reason": "CI commonly executes automated tests, yet the test framework dimension owns the test implementation details.",
"with_dim_id": "testing-and-automation-frameworks",
"with_dim_name": null,
"with_role": "iOS Engineer"
}
],
"tentative_id": "d_init_01"
}
],
"merge_log": [],
"placed": {
"name": "CI",
"placement_confidence": 0.92,
"primary_dimension": "d_init_01",
"reasoning": "Deterministic JD placement: locked_dimensions has 1 dimension(s) from skill-driven dimension generation after reconciliation; primary_dimension is the first locked dim.",
"secondary_dimensions": [],
"skill_id": "ci"
},
"relationships": {
"child_skills": [],
"parent_skills": [],
"related_to": [
"junit",
"ec2",
"sqlite",
"r",
"acls",
"jwt",
"java",
"cspm",
"navcontroller",
"catalog-items",
"confidence-intervals",
"livedata",
"ssids",
"fc-zoning",
"c",
"javascript",
"openid-connect",
"confidence-thresholds",
"http",
"rbac"
],
"requires": [],
"skill_id": "ci",
"suppress_on_match": []
},
"skill_id": "ci",
"split_log": [],
"typed": {
"alternatives_considered": [],
"confidence": 0.91,
"name": "CI",
"reasoning": "CI is fundamentally a way of working for integrating changes frequently and validating them continuously, so it fits the Concept vs Methodology rule as a Methodology.",
"skill_id": "ci",
"subtype": "continuous_integration_methodology",
"type": "Methodology"
},
"warnings": []
},
"source_tag": "llm",
"was_in_llm_skills": true
},
{
"aliases_in_db": [],
"canonical": null,
"dimensions": [],
"input_skill": "CICD",
"matched_via": null,
"new_alias_persisted": false,
"new_alias_text": null,
"new_skill_meta": {
"derived": {
"category": "Methodology",
"skill_nature": "METHODOLOGY",
"sub_category": "continuous_integration_continuous_delivery",
"typical_lifespan": "EVERGREEN",
"version_strategy": "NOT_APPLICABLE",
"volatility": "STABLE"
},
"enrichment": {
"ambiguity": {
"ambiguity_flag": false,
"confused_with": [],
"reasoning": "CICD is a standard DevOps methodology acronym with a clear meaning in job descriptions; it is unlikely to be mistaken for a different catalog skill."
},
"context_keywords": {
"context_keywords": [
"Jenkins",
"GitHub Actions",
"GitLab CI",
"Azure DevOps",
"CircleCI",
"Travis CI",
"pipeline",
"build automation",
"deployment pipeline",
"artifact repository",
"unit tests",
"integration tests",
"rollback",
"blue-green deployment",
"canary release"
]
},
"maturity": {
"confidence": 0.97,
"maturity": "well_known",
"reasoning": "CI/CD appears in a large share of DevOps and platform engineering job descriptions and is a standard requirement in major cloud/vendor docs and tooling ecosystems."
},
"skill_id": "cicd",
"vendor_license": {
"confidence": 0.99,
"license": null,
"vendor": null,
"year_introduced": null
},
"versioning": {
"current_version": null,
"version_aliases": {},
"versioned": false
}
},
"keep_log": [],
"locked_dimensions": [],
"merge_log": [],
"placed": {
"name": "CICD",
"placement_confidence": 0.0,
"primary_dimension": "d_init_00",
"reasoning": "Stub placement: no locked_dimensions after Stage 2/3; downstream containment and enrichment use placeholders only.",
"secondary_dimensions": [],
"skill_id": "cicd"
},
"relationships": {
"child_skills": [],
"parent_skills": [],
"related_to": [
"runbooks",
"ansible",
"kubernetes",
"policy-as-code",
"health-checks",
"circuit-breakers",
"shutdown-sequencing",
"escalation-paths"
],
"requires": [],
"skill_id": "cicd",
"suppress_on_match": []
},
"skill_id": "cicd",
"split_log": [],
"typed": {
"alternatives_considered": [],
"confidence": 0.93,
"name": "CICD",
"reasoning": "By the Concept vs Methodology rule, CI/CD is primarily a way of working and delivery process rather than a single knowledge unit or software product.",
"skill_id": "cicd",
"subtype": "continuous_integration_continuous_delivery",
"type": "Methodology"
},
"warnings": [
"stage2_dim_gen_failed: ValidationError: 1 validation error for SkillDimensionList\ncandidate_dimensions.1.tentative_id\n String should match pattern \u0027^d_init_\\d{2,3}$\u0027 [type=string_pattern_mismatch, input_value=\u0027environment-provisioning-and-promotion\u0027, input_type=str]\n For further information visit https://errors.pydantic.dev/2.13/v/string_pattern_mismatch",
"placement_stub_no_locked_dimensions"
]
},
"source_tag": "llm",
"was_in_llm_skills": true
},
{
"aliases_in_db": [],
"canonical": null,
"dimensions": [
{
"dimension": {
"difficulty_hint": null,
"display_name": "Cloud Platforms and Services",
"id": null,
"rationale": "Covers core cloud computing concepts and the use of managed cloud services across major providers. This fits the target skill because \"Cloud\" is a broad umbrella for provisioning, operating, and integrating cloud-hosted infrastructure and services.",
"slug": "d_init_01",
"source": "llm"
},
"input_skill": "Cloud",
"llm_role": null,
"roles_from_db": []
}
],
"input_skill": "Cloud",
"matched_via": null,
"new_alias_persisted": false,
"new_alias_text": null,
"new_skill_meta": {
"derived": {
"category": "Domain",
"skill_nature": "CONCEPT",
"sub_category": "cloud_computing",
"typical_lifespan": "EVERGREEN",
"version_strategy": "NOT_APPLICABLE",
"volatility": "STABLE"
},
"enrichment": {
"ambiguity": {
"ambiguity_flag": false,
"confused_with": [],
"reasoning": "In JDs, \"cloud\" usually clearly denotes cloud computing as a domain. It\u2019s broad, but not typically confused with a different catalog skill name."
},
"context_keywords": {
"context_keywords": [
"AWS",
"Azure",
"Google Cloud",
"IaaS",
"PaaS",
"SaaS",
"Kubernetes",
"Docker",
"serverless",
"virtual machines",
"load balancer",
"auto-scaling",
"VPC",
"IAM",
"Terraform"
]
},
"maturity": {
"confidence": 0.98,
"maturity": "well_known",
"reasoning": "Cloud computing is a hiring-pipeline staple: AWS, Azure, and GCP appear in a large share of infrastructure and platform JDs, and major vendors continue expanding cloud certifications and services."
},
"skill_id": "cloud",
"vendor_license": {
"confidence": 0.99,
"license": null,
"vendor": null,
"year_introduced": null
},
"versioning": {
"current_version": null,
"version_aliases": {},
"versioned": false
}
},
"keep_log": [],
"locked_dimensions": [
{
"description": "Covers core cloud computing concepts and the use of managed cloud services across major providers. This fits the target skill because \"Cloud\" is a broad umbrella for provisioning, operating, and integrating cloud-hosted infrastructure and services.",
"exemplar_skills": [
"Cloud",
"AWS",
"Azure",
"Google Cloud Platform",
"cloud infrastructure",
"managed cloud services",
"serverless computing"
],
"in_scope": "Cloud, AWS, Azure, Google Cloud Platform, compute, storage, networking, managed databases, serverless services, IAM basics, cloud regions and availability zones",
"name": "Cloud Platforms and Services",
"out_of_scope": "Cloud security controls and hardening, covered by cloud-security-guardrails; cloud migration sequencing and target-state planning, covered by migration-and-modernization-planning; environment promotion workflows, covered by environment-provisioning-and-promotion",
"overlap_flags": [
{
"reason": "Cloud work often includes security configuration, but this dimension focuses on general platform usage rather than guardrails and hardening.",
"with_dim_id": "cloud-security-guardrails",
"with_dim_name": null,
"with_role": "Cloud Architect, Cloud Engineer, Cybersecurity Engineer"
},
{
"reason": "Cloud adoption can involve migration planning, but that is a distinct planning dimension rather than general cloud capability.",
"with_dim_id": "migration-and-modernization-planning",
"with_dim_name": null,
"with_role": "Cloud Architect"
},
{
"reason": "Provisioning cloud environments overlaps operationally, but this dimension is broader than lifecycle promotion workflows.",
"with_dim_id": "environment-provisioning-and-promotion",
"with_dim_name": null,
"with_role": "DevOps Engineer"
}
],
"tentative_id": "d_init_01"
}
],
"merge_log": [],
"placed": {
"name": "Cloud",
"placement_confidence": 0.92,
"primary_dimension": "d_init_01",
"reasoning": "Deterministic JD placement: locked_dimensions has 1 dimension(s) from skill-driven dimension generation after reconciliation; primary_dimension is the first locked dim.",
"secondary_dimensions": [],
"skill_id": "cloud"
},
"relationships": {
"child_skills": [],
"parent_skills": [],
"related_to": [
"cloud-run",
"cloud-reference-architecture",
"kubernetes",
"aws-s3",
"aws-cloudformation",
"azure-backup",
"azure-monitor",
"aws-organizations",
"aws-direct-connect",
"ec2",
"aws-vpc",
"google-cloud-iam",
"azure-virtual-machines",
"aws-migration-hub",
"aws-iam",
"azure-expressroute"
],
"requires": [],
"skill_id": "cloud",
"suppress_on_match": []
},
"skill_id": "cloud",
"split_log": [],
"typed": {
"alternatives_considered": [],
"confidence": 0.93,
"name": "Cloud",
"reasoning": "Cloud is best treated as a Domain because it names a broad technology/problem space rather than a specific product, runtime, or hosted platform under the given taxonomy.",
"skill_id": "cloud",
"subtype": "cloud_computing",
"type": "Domain"
},
"warnings": []
},
"source_tag": "llm",
"was_in_llm_skills": true
},
{
"aliases_in_db": [],
"canonical": null,
"dimensions": [
{
"dimension": {
"difficulty_hint": null,
"display_name": "Containerization",
"id": null,
"rationale": "Covers packaging and running software in isolated containers, including the core concepts and tooling used to build, ship, and execute containerized applications. Containers belongs here when the skill refers to the container abstraction itself rather than orchestration or image delivery.",
"slug": "d_init_01",
"source": "llm"
},
"input_skill": "Containers",
"llm_role": null,
"roles_from_db": []
}
],
"input_skill": "Containers",
"matched_via": null,
"new_alias_persisted": false,
"new_alias_text": null,
"new_skill_meta": {
"derived": {
"category": "Architecture",
"skill_nature": "PATTERN",
"sub_category": "containerization_architecture",
"typical_lifespan": "EVERGREEN",
"version_strategy": "NOT_APPLICABLE",
"volatility": "STABLE"
},
"enrichment": {
"ambiguity": {
"ambiguity_flag": true,
"confused_with": [
"docker",
"kubernetes",
"containerization"
],
"reasoning": "\u201cContainers\u201d is broad and can mean generic containerization architecture, but JDs often use it to refer to Docker or Kubernetes-related container platforms. A parser could reasonably map it to those adjacent skills."
},
"context_keywords": {
"context_keywords": [
"Docker",
"Kubernetes",
"Podman",
"containerd",
"CRI-O",
"Helm",
"Dockerfile",
"image registry",
"orchestration",
"namespaces",
"cgroups",
"OCI",
"microservices",
"CI/CD",
"ECS"
]
},
"maturity": {
"confidence": 0.98,
"maturity": "well_known",
"reasoning": "Containers are a hiring-pipeline staple: Docker/Kubernetes appear in a large share of cloud and DevOps job descriptions, and major vendors (AWS, Azure, GCP) offer first-class container services."
},
"skill_id": "containers",
"vendor_license": {
"confidence": 0.84,
"license": "apache_2",
"vendor": "Docker, Inc.",
"year_introduced": 2013
},
"versioning": {
"current_version": null,
"version_aliases": {},
"versioned": false
}
},
"keep_log": [],
"locked_dimensions": [
{
"description": "Covers packaging and running software in isolated containers, including the core concepts and tooling used to build, ship, and execute containerized applications. Containers belongs here when the skill refers to the container abstraction itself rather than orchestration or image delivery.",
"exemplar_skills": [
"Containers",
"Docker",
"Podman",
"container images",
"container runtime",
"container isolation",
"container lifecycle"
],
"in_scope": "Containers, Docker containers, container images, container runtimes, Docker, Podman, container isolation, container lifecycle, container networking basics, container storage basics",
"name": "Containerization",
"out_of_scope": "Kubernetes scheduling and cluster operations, Dockerfile build optimization, image registry administration, VM provisioning, cloud network security controls, application code running inside containers",
"overlap_flags": [
{
"reason": "Containerization often feeds into orchestration platforms, but this dimension owns the container abstraction itself rather than cluster scheduling and deployment control.",
"with_dim_id": "orchestration-platforms",
"with_dim_name": null,
"with_role": "Cloud Engineer, DevOps Engineer"
},
{
"reason": "Containers are used to create consistent environments, but this dimension focuses on the container technology rather than environment lifecycle management.",
"with_dim_id": "environment-provisioning-and-promotion",
"with_dim_name": null,
"with_role": "DevOps Engineer"
}
],
"tentative_id": "d_init_01"
}
],
"merge_log": [],
"placed": {
"name": "Containers",
"placement_confidence": 0.92,
"primary_dimension": "d_init_01",
"reasoning": "Deterministic JD placement: locked_dimensions has 1 dimension(s) from skill-driven dimension generation after reconciliation; primary_dimension is the first locked dim.",
"secondary_dimensions": [],
"skill_id": "containers"
},
"relationships": {
"child_skills": [
"kubernetes"
],
"parent_skills": [],
"related_to": [
"kubernetes",
"node-pools",
"capacity-planning"
],
"requires": [],
"skill_id": "containers",
"suppress_on_match": []
},
"skill_id": "containers",
"split_log": [],
"typed": {
"alternatives_considered": [
"Tool: ruled out \u2014 containers are not primarily software a user operates, but an architectural approach to deployment and isolation",
"Concept: ruled out \u2014 while containerization is a concept, the named skill here refers to the architectural pattern"
],
"confidence": 0.88,
"name": "Containers",
"reasoning": "Containers are fundamentally a system-shape pattern for packaging and isolating applications, so by the Architecture vs Concept rule they fit Architecture rather than Tool or Platform.",
"skill_id": "containers",
"subtype": "containerization_architecture",
"type": "Architecture"
},
"warnings": []
},
"source_tag": "llm",
"was_in_llm_skills": true
},
{
"aliases_in_db": [],
"canonical": null,
"dimensions": [
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Scaling and Resilience Engineering",
"id": 45,
"rationale": "Implements Azure-side patterns that improve availability, capacity, and fault tolerance. This is a coherent cluster because the role must keep environments ready for production load and failure scenarios.",
"slug": "scaling-and-resilience-engineering",
"source": "db"
},
"input_skill": "Devops",
"llm_role": null,
"roles_from_db": [
{
"display_name": "Azure Cloud Engineer",
"id": 4,
"rationale": null,
"role_archetype": null,
"slug": "azure-cloud-engineer",
"source": "db"
}
]
}
],
"input_skill": "Devops",
"matched_via": null,
"new_alias_persisted": false,
"new_alias_text": null,
"new_skill_meta": {
"derived": {
"category": "Methodology",
"skill_nature": "METHODOLOGY",
"sub_category": "devops_practices",
"typical_lifespan": "EVERGREEN",
"version_strategy": "NOT_APPLICABLE",
"volatility": "STABLE"
},
"enrichment": {
"ambiguity": {
"ambiguity_flag": false,
"confused_with": [],
"reasoning": "\u201cDevOps\u201d is a well-established methodology term with a specific meaning in JDs; it is unlikely to be reasonably confused with a different catalog skill."
},
"context_keywords": {
"context_keywords": [
"CI/CD",
"Jenkins",
"GitLab CI",
"GitHub Actions",
"Terraform",
"Ansible",
"Kubernetes",
"Docker",
"Helm",
"AWS",
"Azure",
"GCP",
"Infrastructure as Code",
"monitoring",
"observability"
]
},
"maturity": {
"confidence": 0.96,
"maturity": "well_known",
"reasoning": "DevOps is a standard hiring-pipeline keyword across SRE, platform, and cloud roles; LinkedIn/Indeed job postings routinely list it alongside CI/CD and Kubernetes, showing broad market adoption."
},
"skill_id": "devops",
"vendor_license": {
"confidence": 0.99,
"license": null,
"vendor": null,
"year_introduced": null
},
"versioning": {
"current_version": null,
"version_aliases": {},
"versioned": false
}
},
"keep_log": [
{
"a_dim_id": "d_init_02",
"a_name": "Scaling and Resilience Engineering",
"a_role": "__skill_focal__",
"b_dim_id": "scaling-and-resilience-engineering",
"b_name": "Scaling and Resilience Engineering",
"b_role": "Azure Cloud Engineer",
"pair_kind": "cross_role",
"reasoning": "Same label, but different role anchors. Dim A is DevOps/ops reliability: its description stresses operational practices, and exemplars like autoscaling, failover, capacity planning, rollback automation, and resilience testing are broad production-readiness skills. Dim B is Azure Cloud Engineer-specific, focused on Azure-side patterns for availability, capacity, and fault tolerance. The overlap is from shared reliability vocabulary, not identical skill clusters.",
"similarity": 0.7400200719489172
}
],
"locked_dimensions": [
{
"description": "Covers operational practices that keep cloud systems available, scalable, and fault-tolerant under load or failure. DevOps belongs here when it refers to reliability automation, capacity management, and production readiness.",
"exemplar_skills": [
"Devops",
"autoscaling",
"failover",
"capacity planning",
"rollback automation",
"resilience testing",
"high availability"
],
"in_scope": "Devops, autoscaling, failover, redundancy, capacity planning, incident recovery, resilience testing, deployment rollback, service health checks, availability engineering",
"name": "Scaling and Resilience Engineering",
"out_of_scope": "Security hardening, application feature coding, data pipeline monitoring, container scheduling specifics, backup media management",
"overlap_flags": [
{
"reason": "Orchestration platforms can implement scaling actions, but this dimension is about the reliability goals and operational patterns behind them.",
"with_dim_id": "orchestration-platforms",
"with_dim_name": null,
"with_role": "Cloud Engineer, DevOps Engineer"
},
{
"reason": "Recovery workflows can overlap with resilience work, but backups and restores are a distinct operational discipline.",
"with_dim_id": "backup-and-restore-operations",
"with_dim_name": null,
"with_role": "Storage Engineer"
}
],
"tentative_id": "d_init_02"
}
],
"merge_log": [
{
"a_dim_id": "d_init_01",
"a_name": "Environment Provisioning and Promotion",
"a_role": "__skill_focal__",
"b_dim_id": "environment-provisioning-and-promotion",
"b_name": "Environment Provisioning and Promotion",
"b_role": "DevOps Engineer",
"into": "d_merge_01",
"into_name": "Environment Provisioning, Parity, and Release Promotion",
"merged_from": [
"d_init_01",
"environment-provisioning-and-promotion"
],
"pair_kind": "cross_role",
"reasoning": "Both dims describe the same DevOps cluster: creating consistent dev/test/staging/prod environments and promoting releases through them. Dim A mentions \"environment provisioning,\" \"infrastructure as code,\" \"release promotion,\" and \"pipeline gating.\" Dim B says it \"creates and promotes consistent dev, test, staging, and production environments\" and emphasizes lifecycle parity. The substance is identical, not merely similar, so a single unified cluster is appropriate.",
"similarity": 0.8543330831234583
}
],
"placed": {
"name": "Devops",
"placement_confidence": 0.92,
"primary_dimension": "d_init_02",
"reasoning": "Deterministic JD placement: locked_dimensions has 1 dimension(s) from skill-driven dimension generation after reconciliation; primary_dimension is the first locked dim.",
"secondary_dimensions": [],
"skill_id": "devops"
},
"relationships": {
"child_skills": [],
"parent_skills": [],
"related_to": [
"kubernetes",
"ansible",
"policy-as-code",
"runbooks",
"dashboards",
"terraform",
"aws-cdk",
"aws-cloudformation",
"azure-monitor",
"aws-organizations",
"aws-migration-hub",
"cloud-run",
"azure-virtual-machines",
"failover"
],
"requires": [],
"skill_id": "devops",
"suppress_on_match": []
},
"skill_id": "devops",
"split_log": [],
"typed": {
"alternatives_considered": [],
"confidence": 0.88,
"name": "Devops",
"reasoning": "DevOps is fundamentally a way of working that combines development and operations practices, so by the Concept vs Methodology rule it fits Methodology rather than a tool or architecture.",
"skill_id": "devops",
"subtype": "devops_practices",
"type": "Methodology"
},
"warnings": []
},
"source_tag": "llm",
"was_in_llm_skills": true
},
{
"aliases_in_db": [],
"canonical": null,
"dimensions": [
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Infrastructure as Code",
"id": 22,
"rationale": "Defines infrastructure and platform resources through versioned code so environments are repeatable and reviewable. This is a coherent cluster because it underpins environment consistency and change control.",
"slug": "infrastructure-as-code",
"source": "db"
},
"input_skill": "IaC",
"llm_role": null,
"roles_from_db": [
{
"display_name": "DevOps Engineer",
"id": 1,
"rationale": null,
"role_archetype": "A DevOps Engineer enables reliable, repeatable delivery of software by designing and operating the processes that connect development and production. They focus on improving deployment flow, operational stability, and collaboration between teams through automation, standardization, and monitoring of delivery and runtime practices.",
"slug": "devops-engineer",
"source": "db"
}
]
}
],
"input_skill": "IaC",
"matched_via": null,
"new_alias_persisted": false,
"new_alias_text": null,
"new_skill_meta": {
"derived": {
"category": "Methodology",
"skill_nature": "METHODOLOGY",
"sub_category": "infrastructure_as_code",
"typical_lifespan": "EVERGREEN",
"version_strategy": "NOT_APPLICABLE",
"volatility": "STABLE"
},
"enrichment": {
"ambiguity": {
"ambiguity_flag": false,
"confused_with": [],
"reasoning": "IaC is a standard, widely used abbreviation for Infrastructure as Code and is usually clear in JD context; it is not commonly mistaken for another catalog skill."
},
"context_keywords": {
"context_keywords": [
"Terraform",
"CloudFormation",
"Pulumi",
"Ansible",
"Chef",
"Puppet",
"Bicep",
"ARM templates",
"CDK",
"GitOps",
"version control",
"CI/CD",
"provisioning",
"declarative",
"immutable infrastructure"
]
},
"maturity": {
"confidence": 0.96,
"maturity": "well_known",
"reasoning": "IaC is broadly listed in DevOps/cloud job descriptions and supported by major vendors (Terraform, CloudFormation, Pulumi), making it a hiring-pipeline staple rather than a niche practice."
},
"skill_id": "iac",
"vendor_license": {
"confidence": 0.99,
"license": null,
"vendor": null,
"year_introduced": null
},
"versioning": {
"current_version": null,
"version_aliases": {},
"versioned": false
}
},
"keep_log": [],
"locked_dimensions": [
{
"description": "Covers defining and managing cloud and platform infrastructure through declarative code and repeatable templates. IaC belongs here because the skill is specifically about codifying infrastructure setup, change control, and reproducible provisioning.",
"exemplar_skills": [
"IaC",
"Terraform",
"CloudFormation",
"Bicep",
"Pulumi",
"declarative provisioning",
"infrastructure modules",
"infrastructure drift detection"
],
"in_scope": "IaC, Terraform, CloudFormation, ARM templates, Bicep, Pulumi, declarative infrastructure, reusable modules, parameterized stacks, infrastructure drift detection",
"name": "Infrastructure as Code",
"out_of_scope": "Application source code, container image creation, workload scheduling, cloud security policy design, which are owned by other dimensions",
"overlap_flags": [
{
"reason": "IaC often implements security baselines and policy controls, so it can overlap with cloud security guardrail work.",
"with_dim_id": "cloud-security-guardrails",
"with_dim_name": null,
"with_role": "Cloud Architect, Cloud Engineer, Cybersecurity Engineer"
},
{
"reason": "IaC is commonly used to create and promote environments, which makes it adjacent to environment lifecycle management.",
"with_dim_id": "environment-provisioning-and-promotion",
"with_dim_name": null,
"with_role": "DevOps Engineer"
},
{
"reason": "Infrastructure code may encode autoscaling, redundancy, and failover settings that are also part of resilience engineering.",
"with_dim_id": "scaling-and-resilience-engineering",
"with_dim_name": null,
"with_role": "Azure Cloud Engineer"
}
],
"tentative_id": "d_init_01"
}
],
"merge_log": [],
"placed": {
"name": "IaC",
"placement_confidence": 0.92,
"primary_dimension": "d_init_01",
"reasoning": "Deterministic JD placement: locked_dimensions has 1 dimension(s) from skill-driven dimension generation after reconciliation; primary_dimension is the first locked dim.",
"secondary_dimensions": [],
"skill_id": "iac"
},
"relationships": {
"child_skills": [],
"parent_skills": [],
"related_to": [
"aws-cdk",
"clean-architecture",
"cspm"
],
"requires": [],
"skill_id": "iac",
"suppress_on_match": []
},
"skill_id": "iac",
"split_log": [],
"typed": {
"alternatives_considered": [],
"confidence": 0.88,
"name": "IaC",
"reasoning": "IaC is best treated as a way of working for provisioning and managing infrastructure through code, so under the Concept vs Methodology rule it fits Methodology rather than a tool or framework.",
"skill_id": "iac",
"subtype": "infrastructure_as_code",
"type": "Methodology"
},
"warnings": []
},
"source_tag": "llm",
"was_in_llm_skills": true
},
{
"aliases_in_db": [],
"canonical": null,
"dimensions": [
{
"dimension": {
"difficulty_hint": null,
"display_name": "Infrastructure Provisioning",
"id": null,
"rationale": "Covers the setup and management of compute, network, storage, and environment resources that applications depend on. The target skill belongs here when it refers to the underlying systems and runtime foundation rather than a specific cloud service or security control.",
"slug": "d_init_01",
"source": "llm"
},
"input_skill": "Infrastructure",
"llm_role": null,
"roles_from_db": []
}
],
"input_skill": "Infrastructure",
"matched_via": null,
"new_alias_persisted": false,
"new_alias_text": null,
"new_skill_meta": {
"derived": {
"category": "Domain",
"skill_nature": "CONCEPT",
"sub_category": "infrastructure",
"typical_lifespan": "EVERGREEN",
"version_strategy": "NOT_APPLICABLE",
"volatility": "STABLE"
},
"enrichment": {
"ambiguity": {
"ambiguity_flag": false,
"confused_with": [],
"reasoning": "\u201cInfrastructure\u201d is a broad domain term, but in JDs it usually refers to the general IT/cloud/platform area rather than a distinct alternate catalog skill with the same short name."
},
"context_keywords": {
"context_keywords": [
"Terraform",
"Ansible",
"Kubernetes",
"Docker",
"AWS",
"Azure",
"GCP",
"CI/CD",
"IaC",
"Helm",
"Linux",
"VPC",
"subnets",
"load balancer",
"autoscaling"
]
},
"maturity": {
"confidence": 0.96,
"maturity": "well_known",
"reasoning": "Infrastructure is a core hiring-pipeline domain across cloud/DevOps/SRE roles; job postings routinely list AWS, Kubernetes, Terraform, and CI/CD infrastructure work as standard requirements."
},
"skill_id": "infrastructure",
"vendor_license": {
"confidence": 0.99,
"license": null,
"vendor": null,
"year_introduced": null
},
"versioning": {
"current_version": null,
"version_aliases": {},
"versioned": false
}
},
"keep_log": [],
"locked_dimensions": [
{
"description": "Covers the setup and management of compute, network, storage, and environment resources that applications depend on. The target skill belongs here when it refers to the underlying systems and runtime foundation rather than a specific cloud service or security control.",
"exemplar_skills": [
"Infrastructure",
"infrastructure provisioning",
"cloud resource creation",
"environment setup",
"compute instances",
"networking and storage"
],
"in_scope": "Infrastructure, infrastructure provisioning, compute instances, networking, storage, environment setup, platform resources, cloud resource creation, base runtime foundation",
"name": "Infrastructure Provisioning",
"out_of_scope": "Cloud security policies and hardening, application deployment pipelines, service architecture, backup operations, monitoring-specific tooling",
"overlap_flags": [
{
"reason": "Environment promotion is closely related to infrastructure setup, but that catalog dimension is more specific to lifecycle movement across dev/test/stage/prod.",
"with_dim_id": "environment-provisioning-and-promotion",
"with_dim_name": null,
"with_role": "DevOps Engineer"
},
{
"reason": "Infrastructure provisioning often includes baseline security settings, but security guardrails are owned by the cloud security dimension.",
"with_dim_id": "cloud-security-guardrails",
"with_dim_name": null,
"with_role": "Cloud Architect, Cloud Engineer, Cybersecurity Engineer"
},
{
"reason": "Infrastructure can include capacity and fault-tolerance concerns, which overlap with resilience engineering when the focus is on availability.",
"with_dim_id": "scaling-and-resilience-engineering",
"with_dim_name": null,
"with_role": "Azure Cloud Engineer"
}
],
"tentative_id": "d_init_01"
}
],
"merge_log": [],
"placed": {
"name": "Infrastructure",
"placement_confidence": 0.92,
"primary_dimension": "d_init_01",
"reasoning": "Deterministic JD placement: locked_dimensions has 1 dimension(s) from skill-driven dimension generation after reconciliation; primary_dimension is the first locked dim.",
"secondary_dimensions": [],
"skill_id": "infrastructure"
},
"relationships": {
"child_skills": [],
"parent_skills": [],
"related_to": [
"capacity-planning",
"capacity-forecasting",
"thin-provisioning",
"terraform",
"pulumi",
"dependency-mapping",
"acls",
"expressroute",
"endpoint-hardening",
"feature-flags",
"policy-enforcement"
],
"requires": [],
"skill_id": "infrastructure",
"suppress_on_match": []
},
"skill_id": "infrastructure",
"split_log": [],
"typed": {
"alternatives_considered": [
"Concept: ruled out \u2014 too broad and industry-oriented rather than a single named knowledge unit",
"Architecture: ruled out \u2014 not a specific system-shape pattern like microservices or hexagonal architecture"
],
"confidence": 0.88,
"name": "Infrastructure",
"reasoning": "Infrastructure is best treated as a Domain because it names a broad technical problem-space/body of knowledge rather than a specific system shape, tool, or methodology.",
"skill_id": "infrastructure",
"subtype": "infrastructure",
"type": "Domain"
},
"warnings": []
},
"source_tag": "llm",
"was_in_llm_skills": true
},
{
"aliases_in_db": [],
"canonical": null,
"dimensions": [
{
"dimension": {
"difficulty_hint": null,
"display_name": "Linux System Administration",
"id": null,
"rationale": "Covers day-to-day administration of Linux hosts used in cloud and infrastructure environments. This skill belongs here because Linux.6 most likely refers to operating, configuring, and troubleshooting Linux systems rather than application code.",
"slug": "d_init_01",
"source": "llm"
},
"input_skill": "Linux.6",
"llm_role": null,
"roles_from_db": []
}
],
"input_skill": "Linux.6",
"matched_via": null,
"new_alias_persisted": false,
"new_alias_text": null,
"new_skill_meta": {
"derived": {
"category": "Concept",
"skill_nature": "CONCEPT",
"sub_category": "operating_system_concept",
"typical_lifespan": "EVERGREEN",
"version_strategy": "NOT_APPLICABLE",
"volatility": "STABLE"
},
"enrichment": {
"ambiguity": {
"ambiguity_flag": false,
"confused_with": [],
"reasoning": "Linux.6 is a versioned Linux OS concept; the dotted version makes it specific and unlikely to be confused with another catalog skill in a typical JD."
},
"context_keywords": {
"context_keywords": [
"systemd",
"kernel",
"bash",
"shell scripting",
"cron",
"iptables",
"SELinux",
"SSH",
"LVM",
"RAID",
"Docker",
"Kubernetes",
"package manager",
"init.d",
"sysctl"
]
},
"maturity": {
"confidence": 0.98,
"maturity": "well_known",
"reasoning": "Linux is a core OS skill in broad hiring pipelines; job postings routinely list Linux administration and shell usage across cloud, DevOps, and backend roles, and major vendors like AWS/GCP document Linux as the default server platform."
},
"skill_id": "linux-6",
"vendor_license": {
"confidence": 0.99,
"license": null,
"vendor": null,
"year_introduced": null
},
"versioning": {
"current_version": null,
"version_aliases": {},
"versioned": false
}
},
"keep_log": [],
"locked_dimensions": [
{
"description": "Covers day-to-day administration of Linux hosts used in cloud and infrastructure environments. This skill belongs here because Linux.6 most likely refers to operating, configuring, and troubleshooting Linux systems rather than application code.",
"exemplar_skills": [
"Linux.6",
"Linux administration",
"systemd",
"SSH",
"package management",
"process management",
"filesystem permissions"
],
"in_scope": "Linux.6, shell access, users and groups, permissions, systemd, package management, process management, filesystem layout, cron, SSH, log inspection, service troubleshooting, basic kernel and OS tuning",
"name": "Linux System Administration",
"out_of_scope": "Cloud IAM roles, Kubernetes cluster orchestration, network packet analysis, database administration, application deployment pipelines",
"overlap_flags": [
{
"reason": "Linux hardening and access controls often overlap with cloud baseline security, but this dimension focuses on host administration rather than security policy.",
"with_dim_id": "cloud-security-guardrails",
"with_dim_name": null,
"with_role": "Cloud Architect, Cloud Engineer, Cybersecurity Engineer"
},
{
"reason": "Provisioning Linux servers can be part of environment setup, but this dimension is about managing the OS after the host exists.",
"with_dim_id": "environment-provisioning-and-promotion",
"with_dim_name": null,
"with_role": "DevOps Engineer"
}
],
"tentative_id": "d_init_01"
}
],
"merge_log": [],
"placed": {
"name": "Linux.6",
"placement_confidence": 0.92,
"primary_dimension": "d_init_01",
"reasoning": "Deterministic JD placement: locked_dimensions has 1 dimension(s) from skill-driven dimension generation after reconciliation; primary_dimension is the first locked dim.",
"secondary_dimensions": [],
"skill_id": "linux-6"
},
"relationships": {
"child_skills": [],
"parent_skills": [],
"related_to": [
"bash",
"bash-scripting",
"powershell",
"ansible",
"kubernetes",
"gke",
"ec2",
"cloud-run",
"azure-virtual-machines"
],
"requires": [],
"skill_id": "linux-6",
"suppress_on_match": []
},
"skill_id": "linux-6",
"split_log": [],
"typed": {
"alternatives_considered": [],
"confidence": 0.88,
"name": "Linux.6",
"reasoning": "Linux.6 is best treated as a named knowledge unit about the Linux operating system rather than a specific software package or hosted environment, so it fits the Concept category.",
"skill_id": "linux-6",
"subtype": "operating_system_concept",
"type": "Concept"
},
"warnings": []
},
"source_tag": "llm",
"was_in_llm_skills": true
},
{
"aliases_in_db": [],
"canonical": null,
"dimensions": [
{
"dimension": {
"difficulty_hint": null,
"display_name": "NIM Inference Serving",
"id": null,
"rationale": "Covers NVIDIA Inference Microservices used to package, deploy, and operate model inference services. NIM belongs here because it is a runtime layer for exposing AI models as production-ready services.",
"slug": "d_init_01",
"source": "llm"
},
"input_skill": "NIM",
"llm_role": null,
"roles_from_db": []
}
],
"input_skill": "NIM",
"matched_via": null,
"new_alias_persisted": false,
"new_alias_text": null,
"new_skill_meta": {
"derived": {
"category": "Language",
"skill_nature": "LANGUAGE",
"sub_category": "programming_language",
"typical_lifespan": "EVERGREEN",
"version_strategy": "NOT_APPLICABLE",
"volatility": "STABLE"
},
"enrichment": {
"ambiguity": {
"ambiguity_flag": false,
"confused_with": [],
"reasoning": "Nim is a distinct programming language name; in typical JDs it is unlikely to be confused with another catalog skill."
},
"context_keywords": {
"context_keywords": [
"C",
"C++",
"systems programming",
"metaprogramming",
"macros",
"ARC",
"GC",
"FFI",
"cross-compilation",
"embedded",
"concurrency",
"async",
"compile-time",
"static typing",
"package manager"
]
},
"maturity": {
"confidence": 0.9,
"maturity": "niche",
"reasoning": "Nim appears in relatively few job postings compared with mainstream languages, and GitHub activity remains far below Python/Go/Rust; it has no major vendor-backed adoption wave."
},
"skill_id": "nim",
"vendor_license": {
"confidence": 0.96,
"license": "mit",
"vendor": "Nim Compiler Team",
"year_introduced": 2008
},
"versioning": {
"current_version": null,
"version_aliases": {},
"versioned": false
}
},
"keep_log": [],
"locked_dimensions": [
{
"description": "Covers NVIDIA Inference Microservices used to package, deploy, and operate model inference services. NIM belongs here because it is a runtime layer for exposing AI models as production-ready services.",
"exemplar_skills": [
"NIM",
"NVIDIA Inference Microservices",
"model serving",
"inference endpoint deployment",
"GPU inference runtime",
"serving containers"
],
"in_scope": "NIM, NVIDIA Inference Microservices, model serving, inference endpoints, GPU inference runtime, serving containers, runtime configuration, deployment artifacts",
"name": "NIM Inference Serving",
"out_of_scope": "Model training workflows, prompt engineering, offline batch analytics, general Kubernetes cluster operations, application frontend deployment",
"overlap_flags": [
{
"reason": "NIM services are frequently deployed and scaled on orchestration platforms such as Kubernetes.",
"with_dim_id": "orchestration-platforms",
"with_dim_name": null,
"with_role": "Cloud Engineer, DevOps Engineer"
},
{
"reason": "NIM is often one implementation choice within a broader AI service architecture.",
"with_dim_id": "ai-service-architecture-patterns",
"with_dim_name": null,
"with_role": "AI Engineer"
}
],
"tentative_id": "d_init_01"
}
],
"merge_log": [],
"placed": {
"name": "NIM",
"placement_confidence": 0.92,
"primary_dimension": "d_init_01",
"reasoning": "Deterministic JD placement: locked_dimensions has 1 dimension(s) from skill-driven dimension generation after reconciliation; primary_dimension is the first locked dim.",
"secondary_dimensions": [],
"skill_id": "nim"
},
"relationships": {
"child_skills": [],
"parent_skills": [],
"related_to": [],
"requires": [],
"skill_id": "nim",
"suppress_on_match": []
},
"skill_id": "nim",
"split_log": [],
"typed": {
"alternatives_considered": [],
"confidence": 0.99,
"name": "NIM",
"reasoning": "NIM is fundamentally a programming language, not a library or tool, because it is used to write software code directly.",
"skill_id": "nim",
"subtype": "programming_language",
"type": "Language"
},
"warnings": []
},
"source_tag": "llm",
"was_in_llm_skills": true
},
{
"aliases_in_db": [],
"canonical": null,
"dimensions": [
{
"dimension": {
"difficulty_hint": null,
"display_name": "Nemo Framework Usage",
"id": null,
"rationale": "Covers working with the Nemo framework itself: its APIs, project structure, and how it is used to build or run AI-related workflows. This fits the target skill because \u0027Nemo\u0027 most likely refers to the framework rather than a generic concept.",
"slug": "d_init_01",
"source": "llm"
},
"input_skill": "Nemo",
"llm_role": null,
"roles_from_db": []
}
],
"input_skill": "Nemo",
"matched_via": null,
"new_alias_persisted": false,
"new_alias_text": null,
"new_skill_meta": {
"derived": {
"category": "Tool",
"skill_nature": "TOOL",
"sub_category": "desktop_application",
"typical_lifespan": "EVERGREEN",
"version_strategy": "NOT_APPLICABLE",
"volatility": "STABLE"
},
"enrichment": {
"ambiguity": {
"ambiguity_flag": false,
"confused_with": [],
"reasoning": "\"Nemo\" is a specific desktop file manager name and is not a common overloaded JD term; typical job descriptions would not plausibly confuse it with another catalog skill."
},
"context_keywords": {
"context_keywords": [
"speech recognition",
"ASR",
"TTS",
"speech synthesis",
"transcription",
"audio processing",
"language model",
"decoder",
"beam search",
"CTC",
"RNN-T",
"Kaldi",
"PyTorch",
"Jupyter Notebook",
"NeMo toolkit"
]
},
"maturity": {
"confidence": 0.86,
"maturity": "niche",
"reasoning": "Nemo is a Linux desktop file manager with limited JD volume; market signals show it mainly in Cinnamon/Linux desktop roles, not broad generalist hiring."
},
"skill_id": "nemo",
"vendor_license": {
"confidence": 0.78,
"license": "proprietary",
"vendor": "NVIDIA",
"year_introduced": 2019
},
"versioning": {
"current_version": null,
"version_aliases": {},
"versioned": false
}
},
"keep_log": [],
"locked_dimensions": [
{
"description": "Covers working with the Nemo framework itself: its APIs, project structure, and how it is used to build or run AI-related workflows. This fits the target skill because \u0027Nemo\u0027 most likely refers to the framework rather than a generic concept.",
"exemplar_skills": [
"Nemo",
"Nemo APIs",
"Nemo configuration",
"Nemo workflow composition",
"Nemo runtime usage"
],
"in_scope": "Nemo, Nemo APIs, Nemo project setup, Nemo configuration, Nemo workflow composition, Nemo runtime usage, Nemo integration patterns",
"name": "Nemo Framework Usage",
"out_of_scope": "Model serving infrastructure, container orchestration, cloud security controls, general Python programming, streaming data processing",
"overlap_flags": [
{
"reason": "Nemo is typically used through code, so implementation details may overlap with AI workflow programming languages.",
"with_dim_id": "programming-languages-for-ai-workflows",
"with_dim_name": null,
"with_role": "AI Engineer"
},
{
"reason": "Using Nemo inside a product may intersect with broader AI service design and placement decisions.",
"with_dim_id": "ai-service-architecture-patterns",
"with_dim_name": null,
"with_role": "AI Engineer"
}
],
"tentative_id": "d_init_01"
}
],
"merge_log": [],
"placed": {
"name": "Nemo",
"placement_confidence": 0.92,
"primary_dimension": "d_init_01",
"reasoning": "Deterministic JD placement: locked_dimensions has 1 dimension(s) from skill-driven dimension generation after reconciliation; primary_dimension is the first locked dim.",
"secondary_dimensions": [],
"skill_id": "nemo"
},
"relationships": {
"child_skills": [],
"parent_skills": [],
"related_to": [],
"requires": [],
"skill_id": "nemo",
"suppress_on_match": []
},
"skill_id": "nemo",
"split_log": [],
"typed": {
"alternatives_considered": [
"Framework: ruled out \u2014 Nemo is not something you build applications inside.",
"Platform: ruled out \u2014 it is not a hosted multi-tenant environment with APIs.",
"Library: ruled out \u2014 it is not primarily a code package imported by application code."
],
"confidence": 0.78,
"name": "Nemo",
"reasoning": "By the Tool vs Platform rule, Nemo is best treated as software you run locally rather than a hosted multi-tenant environment, so it fits Tool.",
"skill_id": "nemo",
"subtype": "desktop_application",
"type": "Tool"
},
"warnings": []
},
"source_tag": "llm",
"was_in_llm_skills": true
},
{
"aliases_in_db": [],
"canonical": null,
"dimensions": [
{
"dimension": {
"difficulty_hint": null,
"display_name": "Networking Fundamentals",
"id": null,
"rationale": "Core concepts and practices for designing, configuring, and troubleshooting network connectivity in cloud and enterprise environments. This fits Networking because it covers the base layer of how systems communicate over IP networks.",
"slug": "d_init_01",
"source": "llm"
},
"input_skill": "Networking",
"llm_role": null,
"roles_from_db": []
}
],
"input_skill": "Networking",
"matched_via": null,
"new_alias_persisted": false,
"new_alias_text": null,
"new_skill_meta": {
"derived": {
"category": "Concept",
"skill_nature": "CONCEPT",
"sub_category": "computer_networking",
"typical_lifespan": "EVERGREEN",
"version_strategy": "NOT_APPLICABLE",
"volatility": "STABLE"
},
"enrichment": {
"ambiguity": {
"ambiguity_flag": true,
"confused_with": [
"network_security",
"network_administration",
"network_engineering"
],
"reasoning": "\u201cNetworking\u201d is broad in JDs and can mean computer networking, network administration/engineering, or network security. A reasonable extractor could confuse this concept with adjacent catalog skills."
},
"context_keywords": {
"context_keywords": [
"TCP/IP",
"DNS",
"DHCP",
"VLAN",
"subnetting",
"routing",
"switching",
"firewall",
"VPN",
"OSI model",
"LAN",
"WAN",
"BGP",
"NAT",
"load balancer"
]
},
"maturity": {
"confidence": 0.96,
"maturity": "well_known",
"reasoning": "Networking is a core requirement in many software, cloud, and SRE job descriptions, with frequent mentions of TCP/IP, DNS, HTTP, and VPCs across hiring pipelines."
},
"skill_id": "networking",
"vendor_license": {
"confidence": 0.99,
"license": null,
"vendor": null,
"year_introduced": null
},
"versioning": {
"current_version": null,
"version_aliases": {},
"versioned": false
}
},
"keep_log": [],
"locked_dimensions": [
{
"description": "Core concepts and practices for designing, configuring, and troubleshooting network connectivity in cloud and enterprise environments. This fits Networking because it covers the base layer of how systems communicate over IP networks.",
"exemplar_skills": [
"Networking",
"TCP/IP",
"DNS",
"Routing",
"Subnetting",
"NAT",
"VPNs",
"Load Balancers"
],
"in_scope": "Networking, TCP/IP, UDP, DNS, DHCP, routing, subnetting, VLANs, NAT, firewalls, load balancers, VPNs, network addressing, connectivity troubleshooting",
"name": "Networking Fundamentals",
"out_of_scope": "Packet capture and protocol forensics, deep inspection of packet traces, IDS/IPS tuning, network appliance administration, cloud security policy design",
"overlap_flags": [
{
"reason": "Networking often overlaps with protocol-level troubleshooting, but that catalog dimension is specifically about packet inspection and lower-level analysis.",
"with_dim_id": "network-protocols-and-packet-analysis",
"with_dim_name": null,
"with_role": "Network Engineer"
},
{
"reason": "Networking can include firewalls and perimeter devices, but that dimension owns operational configuration of dedicated security appliances.",
"with_dim_id": "network-security-appliances",
"with_dim_name": null,
"with_role": "Network Engineer"
}
],
"tentative_id": "d_init_01"
}
],
"merge_log": [
{
"a_dim_id": "d_init_02",
"a_name": "Network Security Appliances",
"a_role": "__skill_focal__",
"b_dim_id": "network-security-appliances",
"b_name": "Network Security Appliances",
"b_role": "Network Engineer",
"into": "d_merge_01",
"into_name": "Network Security Appliance Configuration",
"merged_from": [
"d_init_02",
"network-security-appliances"
],
"pair_kind": "cross_role",
"reasoning": "Dim A and Dim B describe the same operational cluster: configuring network security devices that enforce traffic policy. Both explicitly center on firewalls, proxies, IDS/IPS, WAFs, ACLs, packet filtering, and perimeter policy enforcement. Dim A says networking belongs here only when it involves these controls rather than general connectivity, and its exemplar skills are exactly those appliance/security controls. Dim B uses nearly the same framing, describing perimeter and internal security devices that enforce network policy and naming firewalls, proxies, and related edge controls. There is no meaningful skill distinction between them; the cosine similarity is high because they are effectively duplicate definitions, not because they are adjacent but separate.",
"similarity": 0.8562070154691553
}
],
"placed": {
"name": "Networking",
"placement_confidence": 0.92,
"primary_dimension": "d_init_01",
"reasoning": "Deterministic JD placement: locked_dimensions has 1 dimension(s) from skill-driven dimension generation after reconciliation; primary_dimension is the first locked dim.",
"secondary_dimensions": [],
"skill_id": "networking"
},
"relationships": {
"child_skills": [],
"parent_skills": [],
"related_to": [
"subnetting",
"http",
"replication",
"failover",
"security-groups",
"kubernetes"
],
"requires": [],
"skill_id": "networking",
"suppress_on_match": []
},
"skill_id": "networking",
"split_log": [],
"typed": {
"alternatives_considered": [],
"confidence": 0.93,
"name": "Networking",
"reasoning": "Networking is best treated as a Concept because it is a body of knowledge about how systems communicate, not a specific protocol, tool, or architecture.",
"skill_id": "networking",
"subtype": "computer_networking",
"type": "Concept"
},
"warnings": []
},
"source_tag": "llm",
"was_in_llm_skills": true
},
{
"aliases_in_db": [],
"canonical": null,
"dimensions": [
{
"dimension": {
"difficulty_hint": null,
"display_name": "Operating Systems Fundamentals",
"id": null,
"rationale": "Core knowledge of operating system concepts, components, and behavior across desktop, server, and cloud-hosted environments. This fits OS because the skill refers to the underlying platform layer that manages processes, memory, files, and device interactions.",
"slug": "d_init_01",
"source": "llm"
},
"input_skill": "OS",
"llm_role": null,
"roles_from_db": []
}
],
"input_skill": "OS",
"matched_via": null,
"new_alias_persisted": false,
"new_alias_text": null,
"new_skill_meta": {
"derived": {
"category": "Concept",
"skill_nature": "CONCEPT",
"sub_category": "operating_system",
"typical_lifespan": "EVERGREEN",
"version_strategy": "NOT_APPLICABLE",
"volatility": "STABLE"
},
"enrichment": {
"ambiguity": {
"ambiguity_flag": true,
"confused_with": [
"operating_system"
],
"reasoning": "\"OS\" is a common abbreviation for operating system, but in JDs it can also be read as other OS-related terms or product names. A reasonable extractor could confuse it with the broader operating_system skill entry."
},
"context_keywords": {
"context_keywords": [
"kernel",
"process scheduling",
"memory management",
"virtual memory",
"device drivers",
"file system",
"system calls",
"interrupts",
"multitasking",
"permissions",
"bootloader",
"shell",
"POSIX",
"Unix",
"Windows"
]
},
"maturity": {
"confidence": 0.96,
"maturity": "well_known",
"reasoning": "Operating systems are a core requirement in many JDs (Linux/Windows/macOS), and vendor support plus broad enterprise/cloud adoption keep OS knowledge a standard hiring signal."
},
"skill_id": "os",
"vendor_license": {
"confidence": 0.99,
"license": null,
"vendor": null,
"year_introduced": null
},
"versioning": {
"current_version": null,
"version_aliases": {},
"versioned": false
}
},
"keep_log": [],
"locked_dimensions": [
{
"description": "Core knowledge of operating system concepts, components, and behavior across desktop, server, and cloud-hosted environments. This fits OS because the skill refers to the underlying platform layer that manages processes, memory, files, and device interactions.",
"exemplar_skills": [
"OS",
"Operating systems",
"Linux",
"Windows Server",
"Unix",
"Process scheduling",
"Memory management",
"File systems"
],
"in_scope": "OS, operating system concepts, process scheduling, memory management, file systems, device drivers, system calls, kernel/user space, Linux, Windows Server, Unix, permissions, boot and startup behavior",
"name": "Operating Systems Fundamentals",
"out_of_scope": "Cloud resource provisioning, container orchestration, network appliance configuration, database administration, application-level lifecycle handling",
"overlap_flags": [
{
"reason": "OS tuning can affect availability and capacity, but that dimension focuses on Azure-side resilience patterns rather than the operating system itself.",
"with_dim_id": "scaling-and-resilience-engineering",
"with_dim_name": null,
"with_role": "Azure Cloud Engineer"
},
{
"reason": "OS hardening and patching can be part of security guardrails, but this dimension is about the base operating system platform rather than security policy.",
"with_dim_id": "cloud-security-guardrails",
"with_dim_name": null,
"with_role": "Cloud Architect, Cloud Engineer, Cybersecurity Engineer"
}
],
"tentative_id": "d_init_01"
}
],
"merge_log": [],
"placed": {
"name": "OS",
"placement_confidence": 0.92,
"primary_dimension": "d_init_01",
"reasoning": "Deterministic JD placement: locked_dimensions has 1 dimension(s) from skill-driven dimension generation after reconciliation; primary_dimension is the first locked dim.",
"secondary_dimensions": [],
"skill_id": "os"
},
"relationships": {
"child_skills": [],
"parent_skills": [],
"related_to": [],
"requires": [],
"skill_id": "os",
"suppress_on_match": []
},
"skill_id": "os",
"split_log": [],
"typed": {
"alternatives_considered": [
"Architecture: ruled out \u2014 OS is a system software category, not a system-shape pattern like microservices or hexagonal architecture.",
"Tool: ruled out \u2014 while an operating system is software you use, the term here refers to the concept/category itself rather than a specific user-operated tool."
],
"confidence": 0.88,
"name": "OS",
"reasoning": "OS is fundamentally a named knowledge unit about how computing systems are organized and managed, so it fits the Concept category rather than a Tool or Platform.",
"skill_id": "os",
"subtype": "operating_system",
"type": "Concept"
},
"warnings": []
},
"source_tag": "llm",
"was_in_llm_skills": true
},
{
"aliases_in_db": [],
"canonical": null,
"dimensions": [],
"input_skill": "Pipeline",
"matched_via": null,
"new_alias_persisted": false,
"new_alias_text": null,
"new_skill_meta": {
"derived": {
"category": "Architecture",
"skill_nature": "PATTERN",
"sub_category": "data_pipeline_architecture",
"typical_lifespan": "EVERGREEN",
"version_strategy": "NOT_APPLICABLE",
"volatility": "STABLE"
},
"enrichment": {
"ambiguity": {
"ambiguity_flag": true,
"confused_with": [
"ci_cd_pipeline",
"etl_pipeline",
"ml_pipeline"
],
"reasoning": "\u201cPipeline\u201d is overloaded in JDs and can mean CI/CD, ETL/data pipelines, or ML pipelines. A generic mention could plausibly refer to these other catalog skills."
},
"context_keywords": {
"context_keywords": [
"ETL",
"ELT",
"orchestration",
"Apache Airflow",
"Dagster",
"Prefect",
"Kafka",
"Spark",
"dbt",
"data ingestion",
"batch processing",
"stream processing",
"data warehouse",
"data lake",
"workflow DAG"
]
},
"maturity": {
"confidence": 0.86,
"maturity": "well_known",
"reasoning": "Data pipeline architecture is a common requirement in data/analytics JDs and cloud vendor docs; roles routinely ask for ETL/ELT, Airflow, Spark, and Kafka pipeline experience."
},
"skill_id": "pipeline",
"vendor_license": {
"confidence": 0.98,
"license": null,
"vendor": null,
"year_introduced": null
},
"versioning": {
"current_version": null,
"version_aliases": {},
"versioned": false
}
},
"keep_log": [],
"locked_dimensions": [],
"merge_log": [
{
"a_dim_id": "d_init_01",
"a_name": "Data Pipeline Observability",
"a_role": "__skill_focal__",
"b_dim_id": "data-pipeline-observability",
"b_name": "Data Pipeline Observability",
"b_role": "Data Engineer",
"into": "d_merge_01",
"into_name": "Data Pipeline Monitoring and Troubleshooting",
"merged_from": [
"d_init_01",
"data-pipeline-observability"
],
"pair_kind": "cross_role",
"reasoning": "Both dimensions describe the same operational data-pipeline monitoring cluster. Dim A defines it as visibility into pipeline health, freshness, throughput, failure alerts, lineage signals, SLA/SLO tracking, and retry diagnostics, with exemplars like pipeline monitoring, data freshness monitoring, job health dashboards, and pipeline alerting. Dim B uses the same name and nearly identical description, emphasizing monitoring and troubleshooting for pipeline health, freshness, and throughput, plus diagnostics to detect failures before consumers are impacted. There is no substantive distinction in scope, and the cross-role label appears to be a duplicate rather than a role-specific variant.",
"similarity": 0.8669698312612797
}
],
"placed": {
"name": "Pipeline",
"placement_confidence": 0.0,
"primary_dimension": "d_init_00",
"reasoning": "Stub placement: no locked_dimensions after Stage 2/3; downstream containment and enrichment use placeholders only.",
"secondary_dimensions": [],
"skill_id": "pipeline"
},
"relationships": {
"child_skills": [],
"parent_skills": [],
"related_to": [
"stateflow",
"navcontroller",
"portal-navigation",
"dependency-mapping",
"dispatchers",
"failover",
"shutdown-sequencing"
],
"requires": [],
"skill_id": "pipeline",
"suppress_on_match": []
},
"skill_id": "pipeline",
"split_log": [],
"typed": {
"alternatives_considered": [
"Concept: ruled out \u2014 while pipelines are a common idea, the term here more strongly denotes an architectural pattern.",
"Methodology: ruled out \u2014 it is not a way of working or process like Agile or TDD."
],
"confidence": 0.78,
"name": "Pipeline",
"reasoning": "By the Architecture vs Concept rule, \"Pipeline\" most fundamentally names a system-shape for moving data or work through stages rather than a tool or language.",
"skill_id": "pipeline",
"subtype": "data_pipeline_architecture",
"type": "Architecture"
},
"warnings": [
"placement_stub_no_locked_dimensions"
]
},
"source_tag": "llm",
"was_in_llm_skills": true
},
{
"aliases_in_db": [],
"canonical": null,
"dimensions": [
{
"dimension": {
"difficulty_hint": null,
"display_name": "Version Control Systems",
"id": null,
"rationale": "Covers source code versioning workflows for tracking changes, branching, merging, and repository history. SVN belongs here because it is a version control system used to manage code and related artifacts.",
"slug": "d_init_01",
"source": "llm"
},
"input_skill": "SVN",
"llm_role": null,
"roles_from_db": []
}
],
"input_skill": "SVN",
"matched_via": null,
"new_alias_persisted": false,
"new_alias_text": null,
"new_skill_meta": {
"derived": {
"category": "Tool",
"skill_nature": "TOOL",
"sub_category": "version_control_tool",
"typical_lifespan": "EVERGREEN",
"version_strategy": "NOT_APPLICABLE",
"volatility": "STABLE"
},
"enrichment": {
"ambiguity": {
"ambiguity_flag": false,
"confused_with": [],
"reasoning": "SVN is a well-known version control tool name and is usually unambiguous in job descriptions; typical JDs would not confuse it with another catalog skill."
},
"context_keywords": {
"context_keywords": [
"Subversion",
"trunk",
"branches",
"tags",
"checkout",
"commit",
"update",
"merge",
"revert",
"conflict",
"working copy",
"repository",
"svnadmin",
"svnserve",
"TortoiseSVN"
]
},
"maturity": {
"confidence": 0.93,
"maturity": "niche",
"reasoning": "SVN still appears in some legacy-maintenance JDs, but Git dominates hiring pipelines and new projects; most market demand has shifted to Git-based workflows and platforms like GitHub/GitLab."
},
"skill_id": "svn",
"vendor_license": {
"confidence": 0.98,
"license": "apache_2",
"vendor": "Apache Software Foundation",
"year_introduced": 2000
},
"versioning": {
"current_version": null,
"version_aliases": {},
"versioned": false
}
},
"keep_log": [],
"locked_dimensions": [
{
"description": "Covers source code versioning workflows for tracking changes, branching, merging, and repository history. SVN belongs here because it is a version control system used to manage code and related artifacts.",
"exemplar_skills": [
"SVN",
"Subversion",
"branching",
"merging",
"tagging",
"checkout",
"commit history",
"working copy management"
],
"in_scope": "SVN, Subversion, branching, merging, tagging, commits, checkouts, repository history, working copies, conflict resolution, trunk-based workflows",
"name": "Version Control Systems",
"out_of_scope": "GitHub Actions, CI/CD pipelines, artifact repositories, code review policy, build automation, release orchestration",
"overlap_flags": [
{
"reason": "Version control often feeds build workflows, but this dimension is specifically about repository management rather than build execution.",
"with_dim_id": "build-and-execution-tooling",
"with_dim_name": null,
"with_role": "Automation Tester"
}
],
"tentative_id": "d_init_01"
}
],
"merge_log": [],
"placed": {
"name": "SVN",
"placement_confidence": 0.92,
"primary_dimension": "d_init_01",
"reasoning": "Deterministic JD placement: locked_dimensions has 1 dimension(s) from skill-driven dimension generation after reconciliation; primary_dimension is the first locked dim.",
"secondary_dimensions": [],
"skill_id": "svn"
},
"relationships": {
"child_skills": [],
"parent_skills": [],
"related_to": [],
"requires": [],
"skill_id": "svn",
"suppress_on_match": []
},
"skill_id": "svn",
"split_log": [],
"typed": {
"alternatives_considered": [],
"confidence": 0.98,
"name": "SVN",
"reasoning": "SVN is software you run to manage source control locally or against a server, so by the Tool vs Framework rule it is a Tool rather than a framework or platform.",
"skill_id": "svn",
"subtype": "version_control_tool",
"type": "Tool"
},
"warnings": []
},
"source_tag": "llm",
"was_in_llm_skills": true
},
{
"aliases_in_db": [],
"canonical": null,
"dimensions": [],
"input_skill": "Security",
"matched_via": null,
"new_alias_persisted": false,
"new_alias_text": null,
"new_skill_meta": {
"derived": {
"category": "Domain",
"skill_nature": "CONCEPT",
"sub_category": "security",
"typical_lifespan": "EVERGREEN",
"version_strategy": "NOT_APPLICABLE",
"volatility": "STABLE"
},
"enrichment": {
"ambiguity": {
"ambiguity_flag": false,
"confused_with": [],
"reasoning": "\u201cSecurity\u201d is a broad domain term, but in JDs it usually denotes the cybersecurity/security function itself rather than a different catalog skill; it\u2019s not a short acronym or product name likely to collide."
},
"context_keywords": {
"context_keywords": [
"threat modeling",
"vulnerability assessment",
"penetration testing",
"SIEM",
"IDS/IPS",
"zero trust",
"IAM",
"encryption",
"incident response",
"risk management",
"CISSP",
"NIST",
"OWASP",
"SOC 2",
"firewall"
]
},
"maturity": {
"confidence": 0.96,
"maturity": "well_known",
"reasoning": "Security is a standard requirement in most engineering JDs and compliance-driven roles; OWASP, IAM, and cloud security appear broadly across postings, reflecting universal market demand."
},
"skill_id": "security",
"vendor_license": {
"confidence": 0.99,
"license": null,
"vendor": null,
"year_introduced": null
},
"versioning": {
"current_version": null,
"version_aliases": {},
"versioned": false
}
},
"keep_log": [],
"locked_dimensions": [],
"merge_log": [
{
"a_dim_id": "d_init_01",
"a_name": "Cloud Security Guardrails",
"a_role": "__skill_focal__",
"b_dim_id": "cloud-security-guardrails",
"b_name": "Cloud Security Guardrails",
"b_role": "Cloud Engineer",
"into": "d_merge_01",
"into_name": "Cloud Security Guardrails and Baseline Hardening",
"merged_from": [
"d_init_01",
"cloud-security-guardrails"
],
"pair_kind": "cross_role",
"reasoning": "Both dims describe the same cloud-security baseline control cluster. Dim A covers baseline security architecture and preventive controls, listing IAM guardrails, network segmentation, encryption, key management, policy-as-code, secure defaults, and logging/audit controls. Dim B says the same thing in slightly different words: baseline security architecture, preventive controls, and hardening standards for cloud environments. The cross-role wording differs, but the exemplar skills and scope are the same, so this is not a distinct cluster.",
"similarity": 0.8561680048454917
}
],
"placed": {
"name": "Security",
"placement_confidence": 0.0,
"primary_dimension": "d_init_00",
"reasoning": "Stub placement: no locked_dimensions after Stage 2/3; downstream containment and enrichment use placeholders only.",
"secondary_dimensions": [],
"skill_id": "security"
},
"relationships": {
"child_skills": [],
"parent_skills": [],
"related_to": [
"policy-enforcement",
"endpoint-hardening",
"jwt",
"saml",
"encryption-at-rest",
"rbac",
"acls",
"azure-rbac",
"certificate-pinning",
"security-groups"
],
"requires": [],
"skill_id": "security",
"suppress_on_match": []
},
"skill_id": "security",
"split_log": [],
"typed": {
"alternatives_considered": [],
"confidence": 0.96,
"name": "Security",
"reasoning": "Security is a vertical/problem-space body of knowledge rather than a tool, protocol, or methodology, so it fits the Domain type.",
"skill_id": "security",
"subtype": "security",
"type": "Domain"
},
"warnings": [
"placement_stub_no_locked_dimensions"
]
},
"source_tag": "llm",
"was_in_llm_skills": true
},
{
"aliases_in_db": [],
"canonical": null,
"dimensions": [],
"input_skill": "Storage",
"matched_via": null,
"new_alias_persisted": false,
"new_alias_text": null,
"new_skill_meta": {
"derived": {
"category": "Domain",
"skill_nature": "CONCEPT",
"sub_category": "data_storage",
"typical_lifespan": "EVERGREEN",
"version_strategy": "NOT_APPLICABLE",
"volatility": "STABLE"
},
"enrichment": {
"ambiguity": {
"ambiguity_flag": true,
"confused_with": [
"cloud_storage",
"database_storage",
"file_storage"
],
"reasoning": "\u201cStorage\u201d is very broad in JDs and can refer to cloud storage, database storage, or file storage rather than the generic domain skill."
},
"context_keywords": {
"context_keywords": [
"SAN",
"NAS",
"object storage",
"block storage",
"file storage",
"RAID",
"LUN",
"iSCSI",
"NFS",
"SMB",
"Ceph",
"GlusterFS",
"EBS",
"S3",
"snapshot"
]
},
"maturity": {
"confidence": 0.93,
"maturity": "well_known",
"reasoning": "Storage is a core infrastructure domain with high JD volume across cloud, backend, and DevOps roles; postings routinely ask for S3, EBS, SAN/NAS, and database storage design."
},
"skill_id": "storage",
"vendor_license": {
"confidence": 0.99,
"license": null,
"vendor": null,
"year_introduced": null
},
"versioning": {
"current_version": null,
"version_aliases": {},
"versioned": false
}
},
"keep_log": [],
"locked_dimensions": [],
"merge_log": [
{
"a_dim_id": "d_init_01",
"a_name": "Storage Hardware and Firmware",
"a_role": "__skill_focal__",
"b_dim_id": "storage-hardware-and-firmware",
"b_name": "Storage Hardware and Firmware",
"b_role": "Storage Engineer",
"into": "d_merge_01",
"into_name": "Physical Storage Hardware and Firmware",
"merged_from": [
"d_init_01",
"storage-hardware-and-firmware"
],
"pair_kind": "cross_role",
"reasoning": "Both dims target the same physical storage layer: disks, SSDs, controllers, shelves, and firmware. Dim A\u2019s scope includes RAID controllers, JBOD shelves, SAN arrays, firmware updates, drive health, and storage enclosures; Dim B repeats the same cluster with physical storage systems, controllers, disks, shelves, and firmware for reliability. A\u2019s exemplars (disk management, SSD firmware, RAID configuration, SAN array administration, storage shelf maintenance) all fit B as well. This is not a broad-area split; it is the same skill cluster with different wording.",
"similarity": 0.8962940133883299
}
],
"placed": {
"name": "Storage",
"placement_confidence": 0.0,
"primary_dimension": "d_init_00",
"reasoning": "Stub placement: no locked_dimensions after Stage 2/3; downstream containment and enrichment use placeholders only.",
"secondary_dimensions": [],
"skill_id": "storage"
},
"relationships": {
"child_skills": [],
"parent_skills": [],
"related_to": [
"sqlite",
"snapshot-retention",
"thin-provisioning",
"retention-policies",
"azure-backup",
"aws-s3",
"capacity-planning",
"capacity-forecasting",
"ebs-snapshots",
"encryption-at-rest"
],
"requires": [],
"skill_id": "storage",
"suppress_on_match": []
},
"skill_id": "storage",
"split_log": [],
"typed": {
"alternatives_considered": [],
"confidence": 0.88,
"name": "Storage",
"reasoning": "Storage is best treated as a Domain because it names a broad problem-space/body of knowledge rather than a specific system, language, or managed service.",
"skill_id": "storage",
"subtype": "data_storage",
"type": "Domain"
},
"warnings": [
"placement_stub_no_locked_dimensions"
]
},
"source_tag": "llm",
"was_in_llm_skills": true
},
{
"aliases_in_db": [],
"canonical": null,
"dimensions": [
{
"dimension": {
"difficulty_hint": null,
"display_name": "Windows Administration",
"id": null,
"rationale": "Covers administering Windows operating systems in server or workstation environments, including configuration, patching, troubleshooting, and core OS management. Windows belongs here because it refers to the platform itself rather than a specific application or cloud service.",
"slug": "d_init_01",
"source": "llm"
},
"input_skill": "Windows",
"llm_role": null,
"roles_from_db": []
}
],
"input_skill": "Windows",
"matched_via": null,
"new_alias_persisted": false,
"new_alias_text": null,
"new_skill_meta": {
"derived": {
"category": "Platform",
"skill_nature": "PLATFORM",
"sub_category": "operating_system_platform",
"typical_lifespan": "EVERGREEN",
"version_strategy": "SEPARATE_ENTITY",
"volatility": "STABLE"
},
"enrichment": {
"ambiguity": {
"ambiguity_flag": true,
"confused_with": [
"windows_server",
"windows_desktop"
],
"reasoning": "\"Windows\" in JDs can mean the desktop OS, Windows Server, or the broader Microsoft Windows platform. A reasonable extractor could confuse it with the server-specific or desktop-specific catalog skills."
},
"context_keywords": {
"context_keywords": [
"Active Directory",
"Group Policy",
"PowerShell",
"Registry",
"Event Viewer",
"IIS",
"Hyper-V",
"WSL",
"RDP",
"NTFS",
"Windows Server",
"PowerShell Remoting",
"SCCM",
"Intune",
"MMC"
]
},
"maturity": {
"confidence": 0.97,
"maturity": "well_known",
"reasoning": "Windows remains a broadly adopted enterprise OS and appears frequently in job descriptions for desktop support, sysadmin, and endpoint management roles; Microsoft continues active support and releases, indicating strong market demand."
},
"skill_id": "windows",
"vendor_license": {
"confidence": 0.99,
"license": "proprietary",
"vendor": "Microsoft",
"year_introduced": 1985
},
"versioning": {
"current_version": "Windows 11",
"version_aliases": {
"Win10": "Windows 10",
"Win11": "Windows 11",
"Windows 10": "Windows 10",
"Windows 11": "Windows 11",
"Windows 2000": "Windows 2000",
"Windows 7": "Windows 7",
"Windows 8": "Windows 8",
"Windows 8.1": "Windows 8.1",
"Windows NT": "Windows NT",
"Windows Vista": "Windows Vista",
"Windows XP": "Windows XP"
},
"versioned": true
}
},
"keep_log": [],
"locked_dimensions": [
{
"description": "Covers administering Windows operating systems in server or workstation environments, including configuration, patching, troubleshooting, and core OS management. Windows belongs here because it refers to the platform itself rather than a specific application or cloud service.",
"exemplar_skills": [
"Windows",
"Windows Server administration",
"Group Policy",
"PowerShell",
"Event Viewer",
"Remote Desktop",
"Registry editing"
],
"in_scope": "Windows, Windows Server, Windows client OS, system settings, patching, services, event logs, registry, Group Policy, PowerShell administration, local users and groups, Remote Desktop",
"name": "Windows Administration",
"out_of_scope": "Active Directory design, identity federation, cloud IAM, Linux administration, application deployment, endpoint security tooling, virtualization platforms",
"overlap_flags": [
{
"reason": "Windows hardening and baseline configuration can overlap with cloud security controls when Windows hosts run in cloud environments.",
"with_dim_id": "cloud-security-guardrails",
"with_dim_name": null,
"with_role": "Cloud Architect, Cloud Engineer, Cybersecurity Engineer"
},
{
"reason": "Windows machine setup may be part of environment provisioning, but this dimension owns the OS-level administration itself.",
"with_dim_id": "environment-provisioning-and-promotion",
"with_dim_name": null,
"with_role": "DevOps Engineer"
}
],
"tentative_id": "d_init_01"
}
],
"merge_log": [],
"placed": {
"name": "Windows",
"placement_confidence": 0.92,
"primary_dimension": "d_init_01",
"reasoning": "Deterministic JD placement: locked_dimensions has 1 dimension(s) from skill-driven dimension generation after reconciliation; primary_dimension is the first locked dim.",
"secondary_dimensions": [],
"skill_id": "windows"
},
"relationships": {
"child_skills": [],
"parent_skills": [],
"related_to": [
"azure-virtual-machines",
"powershell",
"bash"
],
"requires": [],
"skill_id": "windows",
"suppress_on_match": []
},
"skill_id": "windows",
"split_log": [],
"typed": {
"alternatives_considered": [
"Tool: ruled out \u2014 although Windows can be installed and operated locally, the dominant classification here is the operating environment/platform it provides.",
"Runtime: ruled out \u2014 Windows is not primarily an execution environment for code like the JVM or Node.js."
],
"confidence": 0.88,
"name": "Windows",
"reasoning": "By the Platform vs Tool rule, Windows is best treated as a hosted operating environment with APIs and managed services rather than software you merely run as a user.",
"skill_id": "windows",
"subtype": "operating_system_platform",
"type": "Platform"
},
"warnings": []
},
"source_tag": "llm",
"was_in_llm_skills": true
},
{
"aliases_in_db": [],
"canonical": null,
"dimensions": [],
"input_skill": "application",
"matched_via": null,
"new_alias_persisted": false,
"new_alias_text": null,
"new_skill_meta": null,
"source_tag": "llm",
"was_in_llm_skills": true
},
{
"aliases_in_db": [],
"canonical": null,
"dimensions": [],
"input_skill": "applications",
"matched_via": null,
"new_alias_persisted": false,
"new_alias_text": null,
"new_skill_meta": null,
"source_tag": "llm",
"was_in_llm_skills": true
},
{
"aliases_in_db": [],
"canonical": null,
"dimensions": [],
"input_skill": "deployment",
"matched_via": null,
"new_alias_persisted": false,
"new_alias_text": null,
"new_skill_meta": null,
"source_tag": "llm",
"was_in_llm_skills": true
},
{
"aliases_in_db": [],
"canonical": null,
"dimensions": [],
"input_skill": "development",
"matched_via": null,
"new_alias_persisted": false,
"new_alias_text": null,
"new_skill_meta": null,
"source_tag": "llm",
"was_in_llm_skills": true
},
{
"aliases_in_db": [],
"canonical": null,
"dimensions": [],
"input_skill": "monitoring",
"matched_via": null,
"new_alias_persisted": false,
"new_alias_text": null,
"new_skill_meta": null,
"source_tag": "llm",
"was_in_llm_skills": true
},
{
"aliases_in_db": [],
"canonical": null,
"dimensions": [],
"input_skill": "operations",
"matched_via": null,
"new_alias_persisted": false,
"new_alias_text": null,
"new_skill_meta": null,
"source_tag": "llm",
"was_in_llm_skills": true
},
{
"aliases_in_db": [],
"canonical": null,
"dimensions": [],
"input_skill": "ops",
"matched_via": null,
"new_alias_persisted": false,
"new_alias_text": null,
"new_skill_meta": null,
"source_tag": "llm",
"was_in_llm_skills": true
},
{
"aliases_in_db": [],
"canonical": null,
"dimensions": [],
"input_skill": "orchestration",
"matched_via": null,
"new_alias_persisted": false,
"new_alias_text": null,
"new_skill_meta": null,
"source_tag": "llm",
"was_in_llm_skills": true
},
{
"aliases_in_db": [],
"canonical": null,
"dimensions": [],
"input_skill": "pipelines",
"matched_via": null,
"new_alias_persisted": false,
"new_alias_text": null,
"new_skill_meta": null,
"source_tag": "llm",
"was_in_llm_skills": true
},
{
"aliases_in_db": [],
"canonical": null,
"dimensions": [],
"input_skill": "repository",
"matched_via": null,
"new_alias_persisted": false,
"new_alias_text": null,
"new_skill_meta": null,
"source_tag": "llm",
"was_in_llm_skills": true
},
{
"aliases_in_db": [],
"canonical": null,
"dimensions": [],
"input_skill": "resources",
"matched_via": null,
"new_alias_persisted": false,
"new_alias_text": null,
"new_skill_meta": null,
"source_tag": "llm",
"was_in_llm_skills": true
},
{
"aliases_in_db": [],
"canonical": null,
"dimensions": [],
"input_skill": "scripts",
"matched_via": null,
"new_alias_persisted": false,
"new_alias_text": null,
"new_skill_meta": null,
"source_tag": "llm",
"was_in_llm_skills": true
},
{
"aliases_in_db": [],
"canonical": null,
"dimensions": [],
"input_skill": "services",
"matched_via": null,
"new_alias_persisted": false,
"new_alias_text": null,
"new_skill_meta": null,
"source_tag": "llm",
"was_in_llm_skills": true
},
{
"aliases_in_db": [],
"canonical": null,
"dimensions": [],
"input_skill": "solutions",
"matched_via": null,
"new_alias_persisted": false,
"new_alias_text": null,
"new_skill_meta": null,
"source_tag": "llm",
"was_in_llm_skills": true
},
{
"aliases_in_db": [],
"canonical": null,
"dimensions": [],
"input_skill": "tool",
"matched_via": null,
"new_alias_persisted": false,
"new_alias_text": null,
"new_skill_meta": null,
"source_tag": "llm",
"was_in_llm_skills": true
},
{
"aliases_in_db": [],
"canonical": null,
"dimensions": [],
"input_skill": "versioning",
"matched_via": null,
"new_alias_persisted": false,
"new_alias_text": null,
"new_skill_meta": null,
"source_tag": "llm",
"was_in_llm_skills": true
}
],
"unmatched_skills": [
"AI",
"APIM",
"Authentication",
"CD",
"CI",
"CICD",
"Cloud",
"Containers",
"Devops",
"IaC",
"Infrastructure",
"Linux.6",
"NIM",
"Nemo",
"Networking",
"OS",
"Pipeline",
"SVN",
"Security",
"Storage",
"Windows"
]
}
API 3 — final-role-output
{
"chosen_role": {
"display_name": "DevOps Engineer",
"id": 1,
"rationale": "Most dimensions map to DevOps Engineer, especially Kubernetes, Docker, Azure/AWS, deployment automation, and IaC.",
"role_archetype": "A DevOps Engineer enables reliable, repeatable delivery of software by designing and operating the processes that connect development and production. They focus on improving deployment flow, operational stability, and collaboration between teams through automation, standardization, and monitoring of delivery and runtime practices.",
"slug": "devops-engineer",
"source": "db"
},
"final_input_skills": [
{
"skill": "Kubernetes",
"tag": "in_db"
},
{
"skill": "PowerShell",
"tag": "in_db"
},
{
"skill": "JUnit",
"tag": "in_db"
},
{
"skill": "Docker",
"tag": "in_db"
},
{
"skill": "REST APIs",
"tag": "in_db"
},
{
"skill": "Jenkins",
"tag": "in_db"
},
{
"skill": "Python",
"tag": "in_db"
},
{
"skill": "Azure",
"tag": "in_db"
},
{
"skill": "Bash scripting",
"tag": "in_db"
},
{
"skill": "AWS",
"tag": "in_db"
},
{
"skill": "AI",
"tag": "new"
},
{
"skill": "APIM",
"tag": "new"
},
{
"skill": "Authentication",
"tag": "new"
},
{
"skill": "CD",
"tag": "new"
},
{
"skill": "CI",
"tag": "new"
},
{
"skill": "CICD",
"tag": "new"
},
{
"skill": "Cloud",
"tag": "new"
},
{
"skill": "Containers",
"tag": "new"
},
{
"skill": "Devops",
"tag": "new"
},
{
"skill": "IaC",
"tag": "new"
},
{
"skill": "Infrastructure",
"tag": "new"
},
{
"skill": "Linux.6",
"tag": "new"
},
{
"skill": "NIM",
"tag": "new"
},
{
"skill": "Nemo",
"tag": "new"
},
{
"skill": "Networking",
"tag": "new"
},
{
"skill": "OS",
"tag": "new"
},
{
"skill": "Pipeline",
"tag": "new"
},
{
"skill": "SVN",
"tag": "new"
},
{
"skill": "Security",
"tag": "new"
},
{
"skill": "Storage",
"tag": "new"
},
{
"skill": "Windows",
"tag": "new"
},
{
"skill": "application",
"tag": "new"
},
{
"skill": "applications",
"tag": "new"
},
{
"skill": "deployment",
"tag": "new"
},
{
"skill": "development",
"tag": "new"
},
{
"skill": "monitoring",
"tag": "new"
},
{
"skill": "operations",
"tag": "new"
},
{
"skill": "ops",
"tag": "new"
},
{
"skill": "orchestration",
"tag": "new"
},
{
"skill": "pipelines",
"tag": "new"
},
{
"skill": "repository",
"tag": "new"
},
{
"skill": "resources",
"tag": "new"
},
{
"skill": "scripts",
"tag": "new"
},
{
"skill": "services",
"tag": "new"
},
{
"skill": "solutions",
"tag": "new"
},
{
"skill": "tool",
"tag": "new"
},
{
"skill": "versioning",
"tag": "new"
}
],
"persistence": {
"items": [
{
"chosen_role_id": 1,
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Orchestration Platforms",
"id": 25,
"rationale": "Operates the platforms that schedule and run containerized workloads and related deployment primitives. This is separate from image delivery because it concerns runtime placement and service rollout behavior.",
"slug": "orchestration-platforms",
"source": "db"
},
"dimension_id": 25,
"input_skill": "Kubernetes",
"llm_role": null,
"matched_chosen_role": true,
"role_dimension_saved": false,
"roles_from_db": [
{
"display_name": "Cloud Engineer",
"id": 18,
"rationale": null,
"role_archetype": null,
"slug": "cloud-engineer",
"source": "db"
},
{
"display_name": "DevOps Engineer",
"id": 1,
"rationale": null,
"role_archetype": "A DevOps Engineer enables reliable, repeatable delivery of software by designing and operating the processes that connect development and production. They focus on improving deployment flow, operational stability, and collaboration between teams through automation, standardization, and monitoring of delivery and runtime practices.",
"slug": "devops-engineer",
"source": "db"
}
],
"skill_dimension_saved": false,
"skill_id": 158,
"skill_tag": "in_db",
"skipped_reason": "TODO: REMOVE AFTER TESTING \u2014 api3_writes_enabled=False (writes disabled)"
},
{
"chosen_role_id": 1,
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Deployment Automation Scripts",
"id": 31,
"rationale": "Implements the scripts and command-line automation used to execute deployments and environment changes. This cluster covers the practical glue code that pipelines and operators rely on.",
"slug": "deployment-automation-scripts",
"source": "db"
},
"dimension_id": 31,
"input_skill": "PowerShell",
"llm_role": null,
"matched_chosen_role": true,
"role_dimension_saved": false,
"roles_from_db": [
{
"display_name": "DevOps Engineer",
"id": 1,
"rationale": null,
"role_archetype": "A DevOps Engineer enables reliable, repeatable delivery of software by designing and operating the processes that connect development and production. They focus on improving deployment flow, operational stability, and collaboration between teams through automation, standardization, and monitoring of delivery and runtime practices.",
"slug": "devops-engineer",
"source": "db"
}
],
"skill_dimension_saved": false,
"skill_id": 189,
"skill_tag": "in_db",
"skipped_reason": "TODO: REMOVE AFTER TESTING \u2014 api3_writes_enabled=False (writes disabled)"
},
{
"chosen_role_id": 1,
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Authentication Flows and Session Handling",
"id": 10,
"rationale": "Client-side implementation of sign-in, sign-out, session persistence, and protected navigation. This is separated from general API integration because auth flows have distinct UX and state concerns.",
"slug": "authentication-flows-and-session-handling",
"source": "db"
},
"dimension_id": 10,
"input_skill": "JUnit",
"llm_role": null,
"matched_chosen_role": false,
"role_dimension_saved": false,
"roles_from_db": [
{
"display_name": "Android Engineer",
"id": 15,
"rationale": null,
"role_archetype": null,
"slug": "android-engineer",
"source": "db"
},
{
"display_name": "Frontend Engineer",
"id": 3,
"rationale": null,
"role_archetype": "Frontend Engineers design and build the user-facing parts of applications, translating product and design requirements into interactive experiences. They focus on how the application looks, behaves, and responds in the browser, ensuring usability, accessibility, and consistency across the interface.",
"slug": "frontend-engineer",
"source": "db"
},
{
"display_name": "Full Stack Developer",
"id": 2,
"rationale": null,
"role_archetype": null,
"slug": "full-stack-developer",
"source": "db"
}
],
"skill_dimension_saved": false,
"skill_id": 882,
"skill_tag": "in_db",
"skipped_reason": "TODO: REMOVE AFTER TESTING \u2014 api3_writes_enabled=False (writes disabled)"
},
{
"chosen_role_id": 1,
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Test Frameworks and Runners",
"id": 194,
"rationale": "Frameworks and execution tools used to author, organize, and run automated tests. This cluster is coherent because it defines how test cases are structured, parameterized, and reported.",
"slug": "test-frameworks-and-runners",
"source": "db"
},
"dimension_id": 194,
"input_skill": "JUnit",
"llm_role": null,
"matched_chosen_role": false,
"role_dimension_saved": false,
"roles_from_db": [
{
"display_name": "Automation Tester",
"id": 16,
"rationale": null,
"role_archetype": null,
"slug": "automation-tester",
"source": "db"
}
],
"skill_dimension_saved": false,
"skill_id": 882,
"skill_tag": "in_db",
"skipped_reason": "TODO: REMOVE AFTER TESTING \u2014 api3_writes_enabled=False (writes disabled)"
},
{
"chosen_role_id": 1,
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Testing and Quality Assurance",
"id": 150,
"rationale": "Automated testing approaches used to verify backend behavior across units, integrations, contracts, and end-to-end flows. This cluster is coherent because backend engineers need confidence in request handling, data changes, and service interactions.",
"slug": "testing-and-quality-assurance",
"source": "db"
},
"dimension_id": 150,
"input_skill": "JUnit",
"llm_role": null,
"matched_chosen_role": false,
"role_dimension_saved": false,
"roles_from_db": [
{
"display_name": "Backend Engineer",
"id": 14,
"rationale": null,
"role_archetype": null,
"slug": "backend-engineer",
"source": "db"
}
],
"skill_dimension_saved": false,
"skill_id": 882,
"skill_tag": "in_db",
"skipped_reason": "TODO: REMOVE AFTER TESTING \u2014 api3_writes_enabled=False (writes disabled)"
},
{
"chosen_role_id": 1,
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Containerization and Image Delivery",
"id": 24,
"rationale": "Builds, packages, and ships application and support workloads as container images. This cluster covers the artifact format and the mechanics of producing deployable images.",
"slug": "containerization-and-image-delivery",
"source": "db"
},
"dimension_id": 24,
"input_skill": "Docker",
"llm_role": null,
"matched_chosen_role": true,
"role_dimension_saved": false,
"roles_from_db": [
{
"display_name": "DevOps Engineer",
"id": 1,
"rationale": null,
"role_archetype": "A DevOps Engineer enables reliable, repeatable delivery of software by designing and operating the processes that connect development and production. They focus on improving deployment flow, operational stability, and collaboration between teams through automation, standardization, and monitoring of delivery and runtime practices.",
"slug": "devops-engineer",
"source": "db"
}
],
"skill_dimension_saved": false,
"skill_id": 153,
"skill_tag": "in_db",
"skipped_reason": "TODO: REMOVE AFTER TESTING \u2014 api3_writes_enabled=False (writes disabled)"
},
{
"chosen_role_id": 1,
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Model Serving Deployment and Runtime Packaging",
"id": 52,
"rationale": "Operational deployment of trained models into online, batch, or streaming serving environments, including packaging models and model servers into containers or managed inference runtimes, coordinating rollout, and handing off to inference systems. Covers serving frameworks and platforms such as TensorFlow Serving, TorchServe, Triton Inference Server, BentoML, KServe, and Seldon Core, plus container/runtime concerns like Docker images, GPU-enabled containers, base image selection, container entrypoints, runtime dependencies, and image scanning for model services.",
"slug": "model-serving-deployment-and-runtime-packaging",
"source": "db"
},
"dimension_id": 52,
"input_skill": "Docker",
"llm_role": null,
"matched_chosen_role": false,
"role_dimension_saved": false,
"roles_from_db": [
{
"display_name": "MLOps Engineer",
"id": 5,
"rationale": null,
"role_archetype": null,
"slug": "mlops-engineer",
"source": "db"
},
{
"display_name": "Machine Learning Engineer",
"id": 10,
"rationale": null,
"role_archetype": null,
"slug": "machine-learning-engineer",
"source": "db"
}
],
"skill_dimension_saved": false,
"skill_id": 153,
"skill_tag": "in_db",
"skipped_reason": "TODO: REMOVE AFTER TESTING \u2014 api3_writes_enabled=False (writes disabled)"
},
{
"chosen_role_id": 1,
"dimension": {
"difficulty_hint": "well_known",
"display_name": "API Integration and Data Fetching",
"id": 9,
"rationale": "Connecting frontend applications to backend services and third-party endpoints. This covers request orchestration, error handling, pagination, and shaping remote data for UI consumption.",
"slug": "api-integration-and-data-fetching",
"source": "db"
},
"dimension_id": 9,
"input_skill": "REST APIs",
"llm_role": null,
"matched_chosen_role": false,
"role_dimension_saved": false,
"roles_from_db": [
{
"display_name": "Frontend Engineer",
"id": 3,
"rationale": null,
"role_archetype": "Frontend Engineers design and build the user-facing parts of applications, translating product and design requirements into interactive experiences. They focus on how the application looks, behaves, and responds in the browser, ensuring usability, accessibility, and consistency across the interface.",
"slug": "frontend-engineer",
"source": "db"
},
{
"display_name": "Full Stack Developer",
"id": 2,
"rationale": null,
"role_archetype": null,
"slug": "full-stack-developer",
"source": "db"
}
],
"skill_dimension_saved": false,
"skill_id": 49,
"skill_tag": "in_db",
"skipped_reason": "TODO: REMOVE AFTER TESTING \u2014 api3_writes_enabled=False (writes disabled)"
},
{
"chosen_role_id": 1,
"dimension": {
"difficulty_hint": "well_known",
"display_name": "API Integration and Serialization",
"id": 128,
"rationale": "Client-side integration with backend services, including request handling, response parsing, and contract alignment. This cluster is coherent because iOS features frequently depend on stable data exchange with server APIs.",
"slug": "api-integration-and-serialization",
"source": "db"
},
"dimension_id": 128,
"input_skill": "REST APIs",
"llm_role": null,
"matched_chosen_role": false,
"role_dimension_saved": false,
"roles_from_db": [
{
"display_name": "iOS Engineer",
"id": 13,
"rationale": null,
"role_archetype": null,
"slug": "ios-engineer",
"source": "db"
}
],
"skill_dimension_saved": false,
"skill_id": 49,
"skill_tag": "in_db",
"skipped_reason": "TODO: REMOVE AFTER TESTING \u2014 api3_writes_enabled=False (writes disabled)"
},
{
"chosen_role_id": 1,
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Network Automation and Scripting",
"id": 285,
"rationale": "Covers scripts and automation used to configure, validate, and audit network devices and services. This cluster is coherent because repeatable network operations increasingly depend on programmatic changes and checks.",
"slug": "network-automation-and-scripting",
"source": "db"
},
"dimension_id": 285,
"input_skill": "REST APIs",
"llm_role": null,
"matched_chosen_role": false,
"role_dimension_saved": false,
"roles_from_db": [
{
"display_name": "Network Engineer",
"id": 21,
"rationale": null,
"role_archetype": null,
"slug": "network-engineer",
"source": "db"
}
],
"skill_dimension_saved": false,
"skill_id": 49,
"skill_tag": "in_db",
"skipped_reason": "TODO: REMOVE AFTER TESTING \u2014 api3_writes_enabled=False (writes disabled)"
},
{
"chosen_role_id": 1,
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Continuous Integration Test Integration",
"id": 207,
"rationale": "Integrating automated checks into shared build and merge workflows so results are repeatable and visible. This cluster is coherent because automation testers commonly configure test execution triggers, artifacts, and reporting hooks.",
"slug": "continuous-integration-test-integration",
"source": "db"
},
"dimension_id": 207,
"input_skill": "Jenkins",
"llm_role": null,
"matched_chosen_role": false,
"role_dimension_saved": false,
"roles_from_db": [
{
"display_name": "Automation Tester",
"id": 16,
"rationale": null,
"role_archetype": null,
"slug": "automation-tester",
"source": "db"
}
],
"skill_dimension_saved": false,
"skill_id": 1249,
"skill_tag": "in_db",
"skipped_reason": "TODO: REMOVE AFTER TESTING \u2014 api3_writes_enabled=False (writes disabled)"
},
{
"chosen_role_id": 1,
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Analytical Programming Languages",
"id": 82,
"rationale": "Languages used to clean, transform, analyze, and prototype models in notebooks and scripts. This is the core coding surface for expressing statistical logic and data manipulation in a reproducible way.",
"slug": "analytical-programming-languages",
"source": "db"
},
"dimension_id": 82,
"input_skill": "Python",
"llm_role": null,
"matched_chosen_role": false,
"role_dimension_saved": false,
"roles_from_db": [
{
"display_name": "Data Analyst",
"id": 20,
"rationale": null,
"role_archetype": null,
"slug": "data-analyst",
"source": "db"
},
{
"display_name": "Data Scientist",
"id": 7,
"rationale": null,
"role_archetype": null,
"slug": "data-scientist",
"source": "db"
}
],
"skill_dimension_saved": false,
"skill_id": 393,
"skill_tag": "in_db",
"skipped_reason": "TODO: REMOVE AFTER TESTING \u2014 api3_writes_enabled=False (writes disabled)"
},
{
"chosen_role_id": 1,
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Automation Scripting and CLI",
"id": 48,
"rationale": "Uses scripts and command-line tooling to execute repeatable Azure operations and reduce manual work. This is a practical cluster because the role frequently automates provisioning, checks, and remediation tasks.",
"slug": "automation-scripting-and-cli",
"source": "db"
},
"dimension_id": 48,
"input_skill": "Python",
"llm_role": null,
"matched_chosen_role": false,
"role_dimension_saved": false,
"roles_from_db": [
{
"display_name": "Azure Cloud Engineer",
"id": 4,
"rationale": null,
"role_archetype": null,
"slug": "azure-cloud-engineer",
"source": "db"
},
{
"display_name": "Cloud Engineer",
"id": 18,
"rationale": null,
"role_archetype": null,
"slug": "cloud-engineer",
"source": "db"
}
],
"skill_dimension_saved": false,
"skill_id": 393,
"skill_tag": "in_db",
"skipped_reason": "TODO: REMOVE AFTER TESTING \u2014 api3_writes_enabled=False (writes disabled)"
},
{
"chosen_role_id": 1,
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Network Automation and Scripting",
"id": 285,
"rationale": "Covers scripts and automation used to configure, validate, and audit network devices and services. This cluster is coherent because repeatable network operations increasingly depend on programmatic changes and checks.",
"slug": "network-automation-and-scripting",
"source": "db"
},
"dimension_id": 285,
"input_skill": "Python",
"llm_role": null,
"matched_chosen_role": false,
"role_dimension_saved": false,
"roles_from_db": [
{
"display_name": "Network Engineer",
"id": 21,
"rationale": null,
"role_archetype": null,
"slug": "network-engineer",
"source": "db"
}
],
"skill_dimension_saved": false,
"skill_id": 393,
"skill_tag": "in_db",
"skipped_reason": "TODO: REMOVE AFTER TESTING \u2014 api3_writes_enabled=False (writes disabled)"
},
{
"chosen_role_id": 1,
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Programming Languages for AI Workflows",
"id": 261,
"rationale": "Languages used to implement AI feature logic, orchestration, and response handling inside product code. This is the core coding surface for turning prompts and model calls into reliable application behavior.",
"slug": "programming-languages-for-ai-workflows",
"source": "db"
},
"dimension_id": 261,
"input_skill": "Python",
"llm_role": null,
"matched_chosen_role": false,
"role_dimension_saved": false,
"roles_from_db": [
{
"display_name": "AI Engineer",
"id": 12,
"rationale": null,
"role_archetype": null,
"slug": "ai-engineer",
"source": "db"
}
],
"skill_dimension_saved": false,
"skill_id": 393,
"skill_tag": "in_db",
"skipped_reason": "TODO: REMOVE AFTER TESTING \u2014 api3_writes_enabled=False (writes disabled)"
},
{
"chosen_role_id": 1,
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Programming Languages for Backend Systems",
"id": 140,
"rationale": "Languages used to implement server-side business logic, request handlers, workers, and service integrations. This is the core coding surface for backend feature delivery and maintenance.",
"slug": "programming-languages-for-backend-systems",
"source": "db"
},
"dimension_id": 140,
"input_skill": "Python",
"llm_role": null,
"matched_chosen_role": false,
"role_dimension_saved": false,
"roles_from_db": [
{
"display_name": "Backend Engineer",
"id": 14,
"rationale": null,
"role_archetype": null,
"slug": "backend-engineer",
"source": "db"
}
],
"skill_dimension_saved": false,
"skill_id": 393,
"skill_tag": "in_db",
"skipped_reason": "TODO: REMOVE AFTER TESTING \u2014 api3_writes_enabled=False (writes disabled)"
},
{
"chosen_role_id": 1,
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Programming Languages for Data Work",
"id": 67,
"rationale": "Languages used to implement data pipelines, transformations, and operational utilities. This is the code layer for expressing extraction, parsing, validation, and orchestration logic in data engineering workflows.",
"slug": "programming-languages-for-data-work",
"source": "db"
},
"dimension_id": 67,
"input_skill": "Python",
"llm_role": null,
"matched_chosen_role": false,
"role_dimension_saved": false,
"roles_from_db": [
{
"display_name": "Data Engineer",
"id": 6,
"rationale": null,
"role_archetype": null,
"slug": "data-engineer",
"source": "db"
}
],
"skill_dimension_saved": false,
"skill_id": 393,
"skill_tag": "in_db",
"skipped_reason": "TODO: REMOVE AFTER TESTING \u2014 api3_writes_enabled=False (writes disabled)"
},
{
"chosen_role_id": 1,
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Programming Languages for ML Systems",
"id": 113,
"rationale": "Languages used to implement model integration code, inference services, and feature-processing logic. This is the core coding surface for turning trained models into product-facing software components.",
"slug": "programming-languages-for-ml-systems",
"source": "db"
},
"dimension_id": 113,
"input_skill": "Python",
"llm_role": null,
"matched_chosen_role": false,
"role_dimension_saved": false,
"roles_from_db": [
{
"display_name": "Machine Learning Engineer",
"id": 10,
"rationale": null,
"role_archetype": null,
"slug": "machine-learning-engineer",
"source": "db"
}
],
"skill_dimension_saved": false,
"skill_id": 393,
"skill_tag": "in_db",
"skipped_reason": "TODO: REMOVE AFTER TESTING \u2014 api3_writes_enabled=False (writes disabled)"
},
{
"chosen_role_id": 1,
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Programming Languages for Test Automation",
"id": 193,
"rationale": "Languages used to implement automated checks, helper utilities, and test harness code. This is the core coding surface for turning test ideas into maintainable automation.",
"slug": "programming-languages-for-test-automation",
"source": "db"
},
"dimension_id": 193,
"input_skill": "Python",
"llm_role": null,
"matched_chosen_role": false,
"role_dimension_saved": false,
"roles_from_db": [
{
"display_name": "Automation Tester",
"id": 16,
"rationale": null,
"role_archetype": null,
"slug": "automation-tester",
"source": "db"
}
],
"skill_dimension_saved": false,
"skill_id": 393,
"skill_tag": "in_db",
"skipped_reason": "TODO: REMOVE AFTER TESTING \u2014 api3_writes_enabled=False (writes disabled)"
},
{
"chosen_role_id": 1,
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Security Automation and Scripting",
"id": 258,
"rationale": "Automating repeatable security checks, enrichment, and remediation workflows. This cluster is coherent because the role often needs lightweight automation to scale analysis and response.",
"slug": "security-automation-and-scripting",
"source": "db"
},
"dimension_id": 258,
"input_skill": "Python",
"llm_role": null,
"matched_chosen_role": false,
"role_dimension_saved": false,
"roles_from_db": [
{
"display_name": "Cybersecurity Engineer",
"id": 9,
"rationale": null,
"role_archetype": null,
"slug": "cybersecurity-engineer",
"source": "db"
}
],
"skill_dimension_saved": false,
"skill_id": 393,
"skill_tag": "in_db",
"skipped_reason": "TODO: REMOVE AFTER TESTING \u2014 api3_writes_enabled=False (writes disabled)"
},
{
"chosen_role_id": 1,
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Cloud Platform Operations",
"id": 26,
"rationale": "Uses cloud provider services to support delivery and runtime environments. The focus is on consumer-level operation of cloud services rather than deep cloud architecture ownership.",
"slug": "cloud-platform-operations",
"source": "db"
},
"dimension_id": 26,
"input_skill": "Azure",
"llm_role": null,
"matched_chosen_role": true,
"role_dimension_saved": false,
"roles_from_db": [
{
"display_name": "DevOps Engineer",
"id": 1,
"rationale": null,
"role_archetype": "A DevOps Engineer enables reliable, repeatable delivery of software by designing and operating the processes that connect development and production. They focus on improving deployment flow, operational stability, and collaboration between teams through automation, standardization, and monitoring of delivery and runtime practices.",
"slug": "devops-engineer",
"source": "db"
}
],
"skill_dimension_saved": false,
"skill_id": 164,
"skill_tag": "in_db",
"skipped_reason": "TODO: REMOVE AFTER TESTING \u2014 api3_writes_enabled=False (writes disabled)"
},
{
"chosen_role_id": 1,
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Deployment Automation Scripts",
"id": 31,
"rationale": "Implements the scripts and command-line automation used to execute deployments and environment changes. This cluster covers the practical glue code that pipelines and operators rely on.",
"slug": "deployment-automation-scripts",
"source": "db"
},
"dimension_id": 31,
"input_skill": "Bash scripting",
"llm_role": null,
"matched_chosen_role": true,
"role_dimension_saved": false,
"roles_from_db": [
{
"display_name": "DevOps Engineer",
"id": 1,
"rationale": null,
"role_archetype": "A DevOps Engineer enables reliable, repeatable delivery of software by designing and operating the processes that connect development and production. They focus on improving deployment flow, operational stability, and collaboration between teams through automation, standardization, and monitoring of delivery and runtime practices.",
"slug": "devops-engineer",
"source": "db"
}
],
"skill_dimension_saved": false,
"skill_id": 188,
"skill_tag": "in_db",
"skipped_reason": "TODO: REMOVE AFTER TESTING \u2014 api3_writes_enabled=False (writes disabled)"
},
{
"chosen_role_id": 1,
"dimension": {
"difficulty_hint": "well_known",
"display_name": "MySQL Automation and Scripting",
"id": 176,
"rationale": "Covers scripts and operational automation used to run repeatable DBA tasks. This cluster is coherent because production database administration depends on safe, repeatable execution of checks, maintenance, and change steps.",
"slug": "mysql-automation-and-scripting",
"source": "db"
},
"dimension_id": 176,
"input_skill": "Bash scripting",
"llm_role": null,
"matched_chosen_role": false,
"role_dimension_saved": false,
"roles_from_db": [
{
"display_name": "MySQL DBA",
"id": 23,
"rationale": null,
"role_archetype": null,
"slug": "mysql-dba",
"source": "db"
}
],
"skill_dimension_saved": false,
"skill_id": 188,
"skill_tag": "in_db",
"skipped_reason": "TODO: REMOVE AFTER TESTING \u2014 api3_writes_enabled=False (writes disabled)"
},
{
"chosen_role_id": 1,
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Cloud Platform Operations",
"id": 26,
"rationale": "Uses cloud provider services to support delivery and runtime environments. The focus is on consumer-level operation of cloud services rather than deep cloud architecture ownership.",
"slug": "cloud-platform-operations",
"source": "db"
},
"dimension_id": 26,
"input_skill": "AWS",
"llm_role": null,
"matched_chosen_role": true,
"role_dimension_saved": false,
"roles_from_db": [
{
"display_name": "DevOps Engineer",
"id": 1,
"rationale": null,
"role_archetype": "A DevOps Engineer enables reliable, repeatable delivery of software by designing and operating the processes that connect development and production. They focus on improving deployment flow, operational stability, and collaboration between teams through automation, standardization, and monitoring of delivery and runtime practices.",
"slug": "devops-engineer",
"source": "db"
}
],
"skill_dimension_saved": false,
"skill_id": 163,
"skill_tag": "in_db",
"skipped_reason": "TODO: REMOVE AFTER TESTING \u2014 api3_writes_enabled=False (writes disabled)"
},
{
"chosen_role_id": 1,
"dimension": {
"difficulty_hint": null,
"display_name": "Artificial Intelligence",
"id": null,
"rationale": "Covers the broad concept of AI systems and capabilities, including how intelligent behavior is applied in software and cloud solutions. The target skill belongs here because it is the umbrella term for AI-related work when no narrower sub-skill is specified.",
"slug": "d_init_01",
"source": "llm"
},
"dimension_id": null,
"input_skill": "AI",
"llm_role": null,
"matched_chosen_role": false,
"role_dimension_saved": false,
"roles_from_db": [],
"skill_dimension_saved": false,
"skill_id": null,
"skill_tag": "new",
"skipped_reason": "skill_not_in_db_v3_proposed"
},
{
"chosen_role_id": 1,
"dimension": {
"difficulty_hint": null,
"display_name": "API Management Platforms",
"id": null,
"rationale": "Covers managed API gateway and lifecycle capabilities such as publishing, routing, throttling, versioning, and policy enforcement. APIM belongs here because it is commonly used to expose, secure, and govern APIs in cloud environments.",
"slug": "d_init_01",
"source": "llm"
},
"dimension_id": null,
"input_skill": "APIM",
"llm_role": null,
"matched_chosen_role": false,
"role_dimension_saved": false,
"roles_from_db": [],
"skill_dimension_saved": false,
"skill_id": null,
"skill_tag": "new",
"skipped_reason": "skill_not_in_db_v3_proposed"
},
{
"chosen_role_id": 1,
"dimension": {
"difficulty_hint": null,
"display_name": "Authentication",
"id": null,
"rationale": "Mechanisms for verifying identity and establishing a trusted user or service session. This covers the core authentication concept itself, which is broader than any one client flow or platform-specific access setup.",
"slug": "d_init_01",
"source": "llm"
},
"dimension_id": null,
"input_skill": "Authentication",
"llm_role": null,
"matched_chosen_role": false,
"role_dimension_saved": false,
"roles_from_db": [],
"skill_dimension_saved": false,
"skill_id": null,
"skill_tag": "new",
"skipped_reason": "skill_not_in_db_v3_proposed"
},
{
"chosen_role_id": 1,
"dimension": {
"difficulty_hint": null,
"display_name": "Continuous Delivery",
"id": null,
"rationale": "Covers automating the path from a validated build to deployable releases across environments. CD belongs here because it is the standard engineering practice for reliably promoting changes through delivery pipelines.",
"slug": "d_init_01",
"source": "llm"
},
"dimension_id": null,
"input_skill": "CD",
"llm_role": null,
"matched_chosen_role": false,
"role_dimension_saved": false,
"roles_from_db": [],
"skill_dimension_saved": false,
"skill_id": null,
"skill_tag": "new",
"skipped_reason": "skill_not_in_db_v3_proposed"
},
{
"chosen_role_id": 1,
"dimension": {
"difficulty_hint": null,
"display_name": "Continuous Integration Practices",
"id": null,
"rationale": "Covers the automation that builds, tests, and validates code changes whenever they are merged or proposed. CI belongs here because it is the core delivery discipline for keeping changes integrated and verifiable in cloud and software engineering workflows.",
"slug": "d_init_01",
"source": "llm"
},
"dimension_id": null,
"input_skill": "CI",
"llm_role": null,
"matched_chosen_role": false,
"role_dimension_saved": false,
"roles_from_db": [],
"skill_dimension_saved": false,
"skill_id": null,
"skill_tag": "new",
"skipped_reason": "skill_not_in_db_v3_proposed"
},
{
"chosen_role_id": 1,
"dimension": {
"difficulty_hint": null,
"display_name": "Cloud Platforms and Services",
"id": null,
"rationale": "Covers core cloud computing concepts and the use of managed cloud services across major providers. This fits the target skill because \"Cloud\" is a broad umbrella for provisioning, operating, and integrating cloud-hosted infrastructure and services.",
"slug": "d_init_01",
"source": "llm"
},
"dimension_id": null,
"input_skill": "Cloud",
"llm_role": null,
"matched_chosen_role": false,
"role_dimension_saved": false,
"roles_from_db": [],
"skill_dimension_saved": false,
"skill_id": null,
"skill_tag": "new",
"skipped_reason": "skill_not_in_db_v3_proposed"
},
{
"chosen_role_id": 1,
"dimension": {
"difficulty_hint": null,
"display_name": "Containerization",
"id": null,
"rationale": "Covers packaging and running software in isolated containers, including the core concepts and tooling used to build, ship, and execute containerized applications. Containers belongs here when the skill refers to the container abstraction itself rather than orchestration or image delivery.",
"slug": "d_init_01",
"source": "llm"
},
"dimension_id": null,
"input_skill": "Containers",
"llm_role": null,
"matched_chosen_role": false,
"role_dimension_saved": false,
"roles_from_db": [],
"skill_dimension_saved": false,
"skill_id": null,
"skill_tag": "new",
"skipped_reason": "skill_not_in_db_v3_proposed"
},
{
"chosen_role_id": 1,
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Scaling and Resilience Engineering",
"id": 45,
"rationale": "Implements Azure-side patterns that improve availability, capacity, and fault tolerance. This is a coherent cluster because the role must keep environments ready for production load and failure scenarios.",
"slug": "scaling-and-resilience-engineering",
"source": "db"
},
"dimension_id": 45,
"input_skill": "Devops",
"llm_role": null,
"matched_chosen_role": false,
"role_dimension_saved": false,
"roles_from_db": [
{
"display_name": "Azure Cloud Engineer",
"id": 4,
"rationale": null,
"role_archetype": null,
"slug": "azure-cloud-engineer",
"source": "db"
}
],
"skill_dimension_saved": false,
"skill_id": null,
"skill_tag": "new",
"skipped_reason": "skill_not_in_db_v3_proposed"
},
{
"chosen_role_id": 1,
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Infrastructure as Code",
"id": 22,
"rationale": "Defines infrastructure and platform resources through versioned code so environments are repeatable and reviewable. This is a coherent cluster because it underpins environment consistency and change control.",
"slug": "infrastructure-as-code",
"source": "db"
},
"dimension_id": 22,
"input_skill": "IaC",
"llm_role": null,
"matched_chosen_role": true,
"role_dimension_saved": false,
"roles_from_db": [
{
"display_name": "DevOps Engineer",
"id": 1,
"rationale": null,
"role_archetype": "A DevOps Engineer enables reliable, repeatable delivery of software by designing and operating the processes that connect development and production. They focus on improving deployment flow, operational stability, and collaboration between teams through automation, standardization, and monitoring of delivery and runtime practices.",
"slug": "devops-engineer",
"source": "db"
}
],
"skill_dimension_saved": false,
"skill_id": null,
"skill_tag": "new",
"skipped_reason": "skill_not_in_db_v3_proposed"
},
{
"chosen_role_id": 1,
"dimension": {
"difficulty_hint": null,
"display_name": "Infrastructure Provisioning",
"id": null,
"rationale": "Covers the setup and management of compute, network, storage, and environment resources that applications depend on. The target skill belongs here when it refers to the underlying systems and runtime foundation rather than a specific cloud service or security control.",
"slug": "d_init_01",
"source": "llm"
},
"dimension_id": null,
"input_skill": "Infrastructure",
"llm_role": null,
"matched_chosen_role": false,
"role_dimension_saved": false,
"roles_from_db": [],
"skill_dimension_saved": false,
"skill_id": null,
"skill_tag": "new",
"skipped_reason": "skill_not_in_db_v3_proposed"
},
{
"chosen_role_id": 1,
"dimension": {
"difficulty_hint": null,
"display_name": "Linux System Administration",
"id": null,
"rationale": "Covers day-to-day administration of Linux hosts used in cloud and infrastructure environments. This skill belongs here because Linux.6 most likely refers to operating, configuring, and troubleshooting Linux systems rather than application code.",
"slug": "d_init_01",
"source": "llm"
},
"dimension_id": null,
"input_skill": "Linux.6",
"llm_role": null,
"matched_chosen_role": false,
"role_dimension_saved": false,
"roles_from_db": [],
"skill_dimension_saved": false,
"skill_id": null,
"skill_tag": "new",
"skipped_reason": "skill_not_in_db_v3_proposed"
},
{
"chosen_role_id": 1,
"dimension": {
"difficulty_hint": null,
"display_name": "NIM Inference Serving",
"id": null,
"rationale": "Covers NVIDIA Inference Microservices used to package, deploy, and operate model inference services. NIM belongs here because it is a runtime layer for exposing AI models as production-ready services.",
"slug": "d_init_01",
"source": "llm"
},
"dimension_id": null,
"input_skill": "NIM",
"llm_role": null,
"matched_chosen_role": false,
"role_dimension_saved": false,
"roles_from_db": [],
"skill_dimension_saved": false,
"skill_id": null,
"skill_tag": "new",
"skipped_reason": "skill_not_in_db_v3_proposed"
},
{
"chosen_role_id": 1,
"dimension": {
"difficulty_hint": null,
"display_name": "Nemo Framework Usage",
"id": null,
"rationale": "Covers working with the Nemo framework itself: its APIs, project structure, and how it is used to build or run AI-related workflows. This fits the target skill because \u0027Nemo\u0027 most likely refers to the framework rather than a generic concept.",
"slug": "d_init_01",
"source": "llm"
},
"dimension_id": null,
"input_skill": "Nemo",
"llm_role": null,
"matched_chosen_role": false,
"role_dimension_saved": false,
"roles_from_db": [],
"skill_dimension_saved": false,
"skill_id": null,
"skill_tag": "new",
"skipped_reason": "skill_not_in_db_v3_proposed"
},
{
"chosen_role_id": 1,
"dimension": {
"difficulty_hint": null,
"display_name": "Networking Fundamentals",
"id": null,
"rationale": "Core concepts and practices for designing, configuring, and troubleshooting network connectivity in cloud and enterprise environments. This fits Networking because it covers the base layer of how systems communicate over IP networks.",
"slug": "d_init_01",
"source": "llm"
},
"dimension_id": null,
"input_skill": "Networking",
"llm_role": null,
"matched_chosen_role": false,
"role_dimension_saved": false,
"roles_from_db": [],
"skill_dimension_saved": false,
"skill_id": null,
"skill_tag": "new",
"skipped_reason": "skill_not_in_db_v3_proposed"
},
{
"chosen_role_id": 1,
"dimension": {
"difficulty_hint": null,
"display_name": "Operating Systems Fundamentals",
"id": null,
"rationale": "Core knowledge of operating system concepts, components, and behavior across desktop, server, and cloud-hosted environments. This fits OS because the skill refers to the underlying platform layer that manages processes, memory, files, and device interactions.",
"slug": "d_init_01",
"source": "llm"
},
"dimension_id": null,
"input_skill": "OS",
"llm_role": null,
"matched_chosen_role": false,
"role_dimension_saved": false,
"roles_from_db": [],
"skill_dimension_saved": false,
"skill_id": null,
"skill_tag": "new",
"skipped_reason": "skill_not_in_db_v3_proposed"
},
{
"chosen_role_id": 1,
"dimension": {
"difficulty_hint": null,
"display_name": "Version Control Systems",
"id": null,
"rationale": "Covers source code versioning workflows for tracking changes, branching, merging, and repository history. SVN belongs here because it is a version control system used to manage code and related artifacts.",
"slug": "d_init_01",
"source": "llm"
},
"dimension_id": null,
"input_skill": "SVN",
"llm_role": null,
"matched_chosen_role": false,
"role_dimension_saved": false,
"roles_from_db": [],
"skill_dimension_saved": false,
"skill_id": null,
"skill_tag": "new",
"skipped_reason": "skill_not_in_db_v3_proposed"
},
{
"chosen_role_id": 1,
"dimension": {
"difficulty_hint": null,
"display_name": "Windows Administration",
"id": null,
"rationale": "Covers administering Windows operating systems in server or workstation environments, including configuration, patching, troubleshooting, and core OS management. Windows belongs here because it refers to the platform itself rather than a specific application or cloud service.",
"slug": "d_init_01",
"source": "llm"
},
"dimension_id": null,
"input_skill": "Windows",
"llm_role": null,
"matched_chosen_role": false,
"role_dimension_saved": false,
"roles_from_db": [],
"skill_dimension_saved": false,
"skill_id": null,
"skill_tag": "new",
"skipped_reason": "skill_not_in_db_v3_proposed"
}
],
"new_skills_created": 0,
"role_dimension_saved": 0,
"skill_dimension_saved": 0,
"skipped": 41
},
"planner_output": null,
"run_id": "1a58e1db-36d7-4a29-b216-3d2e9f68b7e9"
}
LLM Calls
Every model call made for this run, in pipeline order. Click a card to see the model's response.
Loading…