Pipeline run
39d79165-fae2-4b74-8eb1-d9ee388fdb2b
Client output enrichment
v2 Skill cluster · Nature of work · AI index · Tech stack maturity · Evidence · KRA descriptionvocab breakdown (legacy)
1 POST /skills/extract-from-jd
2 POST /skills/extract-details
3 POST /skills/final-role-output
Backend Engineer
slug: backend-engineer · id: 1 · source: db
The primary skills required for this role align closely with the responsibilities typical of a Backend Engineer.
Resolution:
in_db
— role exists in library; skill↔dim and role↔dim links saved when applicable.
Job description
Job Title: Full Stack Developer Experience: 7+ Years Location: Bangalore Employment Type: Full Time Job Summary We are looking for a skilled and passionate Full Stack Developer to join our growing technology team. The ideal candidate should have hands-on experience in building scalable web applications using .NET Core and React.js, along with strong database and cloud deployment expertise. You will work closely with cross-functional teams to design, develop, and deliver high-quality applications in an Agile environment. Key Responsibilities • Develop and maintain scalable web applications using Python, .NET Core (ASP.NET Core), and React.js • Collaborate with UI/UX designers, product managers, and development teams to build new features and enhance existing applications • Design, optimize, and manage relational and NoSQL databases such as SQL Server, PostgreSQL, MongoDB, and Cosmos DB • Write clean, maintainable, secure, and high-performance code following best development practices • Develop and integrate RESTful APIs and third-party services • Conduct code reviews and implement unit/integration testing to ensure application quality • Troubleshoot, debug, and resolve issues across frontend and backend systems • Handle deployment and hosting activities on Azure App Services and IIS Servers • Participate in Agile ceremonies including sprint planning, stand-ups, and retrospectives • Stay updated with emerging technologies and recommend improvements to applications and processes Required Skills & Qualifications • Bachelors degree in Computer Science, Information Technology, or related field • 2+ years of experience in web application development • Strong hands-on experience with: • React.js • .NET Core / ASP.NET Core • JavaScript, HTML, CSS • Python • Experience in developing and consuming REST APIs • Strong database knowledge with SQL Server/PostgreSQL and/or MongoDB/Cosmos DB • Hands-on experience with Microsoft Azure Cloud Services • Experience with Git or other version control systems • Familiarity with CI/CD tools such as Jenkins or GitLab CI/CD • Strong debugging, analytical, and problem-solving abilities • Excellent communication and collaboration skills Preferred Skills • Exposure to microservices architecture • Experience with containerization tools like Docker/Kubernetes • Knowledge of cloud-native application development • Understanding of DevOps and deployment automation practices
Skills from this JD
Each row merges API 1 extraction, API 2 library match / v3 orchestration (dimensions + locked dims), and API 3 persistence tags.
Aliases — catalog
- Python (CANONICAL) primary
- Python 2 (VERSION)
- Python 2.x (VERSION)
- Python 3 (VERSION)
- Python 3.10 (VERSION)
- Python 3.11 (VERSION)
- Python 3.12 (VERSION)
- Python 3.x (VERSION)
- py (VERSION)
- py2 (VERSION)
- py3 (VERSION)
- python 3 (VERSION)
- python 3.x (VERSION)
- python2 (VERSION)
- python3 (VERSION)
- python3.x (VERSION)
Context tags (catalog)
Stored enrichment (catalog DB)
- Category
- Language
- Sub-category
- Programming Language
- Vendor
- PSF
- License
- mit
- Year introduced
- 1991
- Confidence
- 0.99
- Version strategy
- SEPARATE_ENTITY
- Version tag
- 3
Maturity reasoning: Python appears in a very high volume of job descriptions across data, backend, automation, and ML roles, and remains a default hiring-pipeline language on major job boards and tech stacks.
Skill profile (library / DB)
- Skill nature
- LANGUAGE
- Volatility
- STABLE
- Typical lifespan
- EVERGREEN
- Category id
- 6
- Sub-category id
- 96
- Extractable
- True
- Also category
- False
Dimensions (API 2 worklist)
-
Programming Languages Catalog dimension db id 1
Library dimension (catalog)
Roles linked in library: Backend Engineer
-
Programming Languages and Scripting Catalog dimension db id 59
Library dimension (catalog)
Roles linked in library: Cybersecurity Engineer
-
Programming Languages for Data Work Catalog dimension db id 21
Library dimension (catalog)
Roles linked in library: Data Engineer
-
Programming Languages for ML Systems Catalog dimension db id 39
Library dimension (catalog)
Roles linked in library: ML Engineer
API 3 link attempts (this skill)
| Dimension | Skill↔dim | Role↔dim | Outcome |
|---|---|---|---|
|
Programming Languages
programming-languages
|
✓ | ✓ | Existing dimension (library) · Role↔dimension saved |
|
Programming Languages and Scripting
programming-languages-and-scripting
|
✓ | — | Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role) |
|
Programming Languages for Data Work
programming-languages-for-data-work
|
✓ | — | Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role) |
|
Programming Languages for ML Systems
programming-languages-for-ml-systems
|
✓ | — | Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role) |
Aliases — catalog
- ASP.NET Core (CANONICAL) primary
- asp.net core (VERSION)
- asp.net core 8 (VERSION)
- asp.net core/.net 8 (VERSION)
- aspnetcore (VERSION)
- aspnetcore 8 (VERSION)
- net 8 (VERSION)
- net8 (VERSION)
Context tags (catalog)
Stored enrichment (catalog DB)
- Category
- Framework
- Sub-category
- Web Framework
- Vendor
- Microsoft
- License
- apache_2
- Year introduced
- 2016
- Confidence
- 0.99
- Version strategy
- SEPARATE_ENTITY
- Version tag
- 8
Maturity reasoning: Broadly adopted in enterprise web JDs and Microsoft positions it as the successor to ASP.NET for new .NET apps; strong GitHub and NuGet ecosystem activity supports continued demand.
Skill profile (library / DB)
- Skill nature
- FRAMEWORK
- Volatility
- STABLE
- Typical lifespan
- EVERGREEN
- Category id
- 5
- Sub-category id
- 35
- Extractable
- True
- Also category
- False
Dimensions (API 2 worklist)
-
Web Application Frameworks Catalog dimension db id 2
Library dimension (catalog)
Roles linked in library: Backend Engineer
API 3 link attempts (this skill)
| Dimension | Skill↔dim | Role↔dim | Outcome |
|---|---|---|---|
|
Web Application Frameworks
web-application-frameworks
|
✓ | ✓ | Existing dimension (library) · Role↔dimension saved |
Skill enrichment (orchestrator / LLM)
React.js is a hiring-pipeline staple with very high JD volume across frontend roles and broad ecosystem adoption; it remains one of the most commonly requested UI frameworks on job boards and in GitHub usage trends.
Meta ·mit ·since 2013 (0.99)
React.js is a well-known, specific frontend framework name and is unlikely to be confused with another catalog skill in typical job descriptions.
Versioned 18
{
"React 0.1": "0.1",
"React 0.10": "0.10",
"React 0.11": "0.11",
"React 0.12": "0.12",
"React 0.13": "0.13",
"React 0.14": "0.14",
"React 0.2": "0.2",
"React 0.3": "0.3",
"React 0.4": "0.4",
"React 0.5": "0.5",
"React 0.6": "0.6",
"React 0.7": "0.7",
"React 0.8": "0.8",
"React 0.9": "0.9",
"React 15": "15",
"React 16": "16",
"React 17": "17",
"React 18": "18",
"React.js 15": "15",
"React.js 16": "16",
"React.js 17": "17",
"React.js 18": "18"
}
Framework ·frontend_ui_framework confidence 0.98
React.js is a framework because users build applications inside it and it drives the UI structure by calling application code, matching the Tool vs Framework rule.
- Category
- Framework
- Sub-category
- frontend_ui_framework
- Skill nature
- FRAMEWORK
- Volatility
- STABLE
- Typical lifespan
- EVERGREEN
- Version strategy
- SEPARATE_ENTITY
Dimensions (API 2 worklist)
-
React Frontend Development Proposed / LLM
Proposed / LLM dimension (no DB id yet)
Locked dimensions (v3 placement)
-
React Frontend Development
Pipeline tentative id
Building interactive web user interfaces with React.js, including component composition, state management, hooks, and rendering patterns. React.js belongs here because it is a core library for client-side UI development in modern web applications.
API 3 link attempts (this skill)
| Dimension | Skill↔dim | Role↔dim | Outcome |
|---|---|---|---|
|
React Frontend Development
d_init_01
|
✓ | — | New skill saved · New dimension saved (reconciliation separate) · Role↔dimension skipped (dimension not under chosen role) |
Aliases — catalog
- SQL Server (CANONICAL) primary
- SQL Server 2000 (VERSION)
- SQL Server 2005 (VERSION)
- SQL Server 2008 (VERSION)
- SQL Server 2012 (VERSION)
- SQL Server 2014 (VERSION)
- SQL Server 2016 (VERSION)
- SQL Server 2017 (VERSION)
- SQL Server 2019 (VERSION)
- SQL Server 2022 (VERSION)
- SQL Server 6.5 (VERSION)
- SQL Server 7.0 (VERSION)
Context tags (catalog)
Stored enrichment (catalog DB)
- Category
- Datastore
- Sub-category
- Relational Database
- Vendor
- Microsoft
- License
- proprietary
- Year introduced
- 1989
- Confidence
- 0.99
- Version strategy
- NOT_APPLICABLE
Maturity reasoning: SQL Server appears in many enterprise job descriptions and remains a major Microsoft-supported RDBMS with active Azure SQL/SQL Server demand; it is a common hiring-pipeline staple, not a sunset technology.
Skill profile (library / DB)
- Skill nature
- TOOL
- Volatility
- STABLE
- Typical lifespan
- EVERGREEN
- Category id
- 3
- Sub-category id
- 29
- Extractable
- True
- Also category
- False
Dimensions (API 2 worklist)
-
Relational Database Design Catalog dimension db id 4
Library dimension (catalog)
Roles linked in library: Backend Engineer
API 3 link attempts (this skill)
| Dimension | Skill↔dim | Role↔dim | Outcome |
|---|---|---|---|
|
Relational Database Design
relational-database-design
|
✓ | ✓ | Existing dimension (library) · Role↔dimension saved |
Aliases — catalog
- PostgreSQL (CANONICAL) primary
- PG 13 (VERSION)
- PG 14 (VERSION)
- PG 15 (VERSION)
- PG 16 (VERSION)
- PostgreSQL 13 (VERSION)
- PostgreSQL 14 (VERSION)
- PostgreSQL 15 (VERSION)
- PostgreSQL 16 (VERSION)
- Postgres 13 (VERSION)
- Postgres 14 (VERSION)
- Postgres 15 (VERSION)
- Postgres 16 (VERSION)
- pg10 (VERSION)
- pg11 (VERSION)
- pg12 (VERSION)
- pg13 (VERSION)
- pg14 (VERSION)
- pg15 (VERSION)
- pg16 (VERSION)
- postgres (VERSION)
- postgresql 10 (VERSION)
- postgresql 11 (VERSION)
- postgresql 12 (VERSION)
- postgresql 13 (VERSION)
- postgresql 14 (VERSION)
- postgresql 15 (VERSION)
- postgresql 16 (VERSION)
- postgresql-16 (VERSION)
- postgresql10 (VERSION)
- postgresql11 (VERSION)
- postgresql12 (VERSION)
- postgresql13 (VERSION)
- postgresql14 (VERSION)
- postgresql15 (VERSION)
- postgresql16 (VERSION)
Context tags (catalog)
Stored enrichment (catalog DB)
- Category
- Datastore
- Sub-category
- Relational Database
- Vendor
- PostgreSQL Global Development Group
- License
- other_open
- Year introduced
- 1996
- Confidence
- 0.99
- Version strategy
- NOT_APPLICABLE
Maturity reasoning: PostgreSQL appears in a large share of backend/data engineering job postings and is a default managed option across AWS RDS, GCP Cloud SQL, and Azure Database, indicating broad hiring-pipeline adoption.
Skill profile (library / DB)
- Skill nature
- TOOL
- Volatility
- STABLE
- Typical lifespan
- EVERGREEN
- Category id
- 3
- Sub-category id
- 29
- Extractable
- True
- Also category
- False
Dimensions (API 2 worklist)
-
Relational Database Design Catalog dimension db id 4
Library dimension (catalog)
Roles linked in library: Backend Engineer
API 3 link attempts (this skill)
| Dimension | Skill↔dim | Role↔dim | Outcome |
|---|---|---|---|
|
Relational Database Design
relational-database-design
|
✓ | ✓ | Existing dimension (library) · Role↔dimension saved |
Aliases — catalog
- MongoDB (CANONICAL) primary
- MongoDB 2.0 (VERSION)
- MongoDB 2.2 (VERSION)
- MongoDB 2.4 (VERSION)
- MongoDB 2.6 (VERSION)
- MongoDB 3.0 (VERSION)
- MongoDB 3.2 (VERSION)
- MongoDB 3.4 (VERSION)
- MongoDB 3.6 (VERSION)
- MongoDB 4 (VERSION)
- MongoDB 4.0 (VERSION)
- MongoDB 4.2 (VERSION)
- MongoDB 4.4 (VERSION)
- MongoDB 5 (VERSION)
- MongoDB 5.0 (VERSION)
- MongoDB 6 (VERSION)
- MongoDB 6.0 (VERSION)
- MongoDB 7 (VERSION)
- MongoDB 7.0 (VERSION)
- MongoDB 8 (VERSION)
- MongoDB 8.0 (VERSION)
Context tags (catalog)
Stored enrichment (catalog DB)
- Category
- Datastore
- Sub-category
- Document Database
- Vendor
- MongoDB, Inc.
- License
- other_open
- Year introduced
- 2009
- Confidence
- 0.99
- Version strategy
- SEPARATE_ENTITY
- Version tag
- 8.0
Maturity reasoning: MongoDB appears in many job descriptions across backend/data roles and is a standard document database in modern stacks; strong GitHub/community activity and broad cloud vendor support indicate mainstream adoption.
Skill profile (library / DB)
- Skill nature
- TOOL
- Volatility
- STABLE
- Typical lifespan
- EVERGREEN
- Category id
- 3
- Sub-category id
- 27
- Extractable
- True
- Also category
- False
Dimensions (API 2 worklist)
-
NoSQL Databases Catalog dimension db id 19
Library dimension (catalog)
Roles linked in library: Backend Engineer
API 3 link attempts (this skill)
| Dimension | Skill↔dim | Role↔dim | Outcome |
|---|---|---|---|
|
NoSQL Databases
nosql-databases
|
✓ | ✓ | Existing dimension (library) · Role↔dimension saved |
Skill enrichment (orchestrator / LLM)
Frequently appears in Azure/cloud data engineer JDs and Microsoft positions; strong vendor support and active docs indicate broad adoption rather than niche use.
Microsoft ·proprietary ·since 2010 (0.98)
Cosmos DB is a specific Azure database service name and is usually unambiguous in JDs; it is not commonly mistaken for another catalog skill.
Not versioned
Service ·managed_nosql_database_service confidence 0.97
By the Service vs Platform rule, Cosmos DB is a specific managed capability inside Azure rather than a standalone hosted environment, so it is a Service.
- Category
- Service
- Sub-category
- managed_nosql_database_service
- Skill nature
- CLOUD_SERVICE
- Volatility
- STABLE
- Typical lifespan
- EVERGREEN
- Version strategy
- NOT_APPLICABLE
Dimensions (API 2 worklist)
-
NoSQL Databases Catalog dimension db id 19
Library dimension (catalog)
Roles linked in library: Backend Engineer
-
NoSQL Databases Catalog dimension db id 19
Library dimension (catalog)
Roles linked in library: Backend Engineer
Locked dimensions (v3 placement)
-
NoSQL Databases
Reuses catalog slug
Non-relational database systems used for flexible schema storage, horizontal scaling, and low-latency application access. Cosmos DB fits here because it is a managed NoSQL database service with document, key-value, and other non-relational access patterns.
-
NoSQL Databases
Reuses catalog slug
Models and manages data using non-relational database systems.
API 3 link attempts (this skill)
| Dimension | Skill↔dim | Role↔dim | Outcome |
|---|---|---|---|
|
NoSQL Databases
nosql-databases
|
✓ | ✓ | New skill saved · Existing dimension (library) · Role↔dimension saved |
Aliases — catalog
- REST (CANONICAL) primary
Context tags (catalog)
Stored enrichment (catalog DB)
- Category
- Concept
- Sub-category
- Api Architecture Style
- Year introduced
- 2000
- Confidence
- 0.88
- Version strategy
- NOT_APPLICABLE
Maturity reasoning: REST is a default API architecture in many job descriptions and is widely supported by major vendors/frameworks; OpenAPI and RESTful endpoints remain standard in hiring pipelines.
Skill profile (library / DB)
- Skill nature
- PROTOCOL
- Volatility
- STABLE
- Typical lifespan
- EVERGREEN
- Category id
- 10
- Sub-category id
- 48
- Extractable
- True
- Also category
- False
Dimensions (API 2 worklist)
-
API Design and Contracts Catalog dimension db id 3
Library dimension (catalog)
Roles linked in library: Backend Engineer
API 3 link attempts (this skill)
| Dimension | Skill↔dim | Role↔dim | Outcome |
|---|---|---|---|
|
API Design and Contracts
api-design-and-contracts
|
✓ | ✓ | Existing dimension (library) · Role↔dimension saved |
Skill enrichment (orchestrator / LLM)
Code review is a standard hiring-pipeline requirement in engineering JDs and is built into major platforms like GitHub/GitLab pull-request workflows, indicating broad adoption.
(0.99)
“Code Review” is a fairly specific engineering practice and is unlikely to be mistaken for a different catalog skill in typical job descriptions.
Not versioned
SoftSkill ·code_review confidence 0.96
Code Review is fundamentally a collaborative interpersonal practice for giving and receiving feedback, so under the Concept vs Methodology rule it fits SoftSkill rather than a technical tool or framework.
- Category
- SoftSkill
- Sub-category
- code_review
- Skill nature
- PRACTICE
- Volatility
- STABLE
- Typical lifespan
- EVERGREEN
- Version strategy
- NOT_APPLICABLE
Dimensions (API 2 worklist)
-
Code Review Practices Proposed / LLM
Proposed / LLM dimension (no DB id yet)
Locked dimensions (v3 placement)
-
Code Review Practices
Pipeline tentative id
Reviewing code changes for correctness, maintainability, security, and alignment with team standards. This skill belongs here because it is a core collaborative engineering practice rather than a language, framework, or platform skill.
API 3 link attempts (this skill)
| Dimension | Skill↔dim | Role↔dim | Outcome |
|---|---|---|---|
|
Code Review Practices
d_init_01
|
✓ | — | New skill saved · Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role) |
Skill enrichment (orchestrator / LLM)
Unit testing is a standard hiring requirement across software JDs and appears in mainstream frameworks/docs; GitHub and Stack Overflow usage remain consistently high, with no successor replacing it.
(0.99)
"Unit Testing" is a standard, specific testing methodology and is unlikely to be confused with a different catalog skill in typical job descriptions.
Not versioned
Methodology ·testing_methodology confidence 0.98
By the Concept vs Methodology rule, unit testing is a way of working for verifying code behavior during development, not a knowledge unit or software artifact.
- Category
- Methodology
- Sub-category
- testing_methodology
- Skill nature
- METHODOLOGY
- Volatility
- STABLE
- Typical lifespan
- EVERGREEN
- Version strategy
- NOT_APPLICABLE
Dimensions (API 2 worklist)
-
Unit Testing Practices Proposed / LLM
Proposed / LLM dimension (no DB id yet)
Locked dimensions (v3 placement)
-
Unit Testing Practices
Pipeline tentative id
Techniques for writing isolated, repeatable tests that verify individual functions, classes, and modules. This skill belongs here because unit testing is the core practice of validating small code units before integration or end-to-end testing.
API 3 link attempts (this skill)
| Dimension | Skill↔dim | Role↔dim | Outcome |
|---|---|---|---|
|
Unit Testing Practices
d_init_01
|
✓ | — | New skill saved · Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role) |
Aliases — catalog
- Integration testing (CANONICAL) primary
- integration testing (CANONICAL)
Context tags (catalog)
Stored enrichment (catalog DB)
- Category
- Methodology
- Sub-category
- Testing Methodology
- Confidence
- 0.97
- Version strategy
- NOT_APPLICABLE
Maturity reasoning: Integration testing is a standard QA skill in job descriptions across backend, frontend, and DevOps roles; it’s commonly paired with CI/CD and tools like Jest, Cypress, and Testcontainers.
Skill profile (library / DB)
- Skill nature
- METHODOLOGY
- Volatility
- STABLE
- Typical lifespan
- EVERGREEN
- Category id
- 8
- Sub-category id
- 44
- Extractable
- True
- Also category
- False
Dimensions (API 2 worklist)
-
Testing and Quality Assurance Catalog dimension db id 12
Library dimension (catalog)
Roles linked in library: Backend Engineer
API 3 link attempts (this skill)
| Dimension | Skill↔dim | Role↔dim | Outcome |
|---|---|---|---|
|
Testing and Quality Assurance
testing-and-quality-assurance
|
✓ | ✓ | Existing dimension (library) · Role↔dimension saved |
Skill enrichment (orchestrator / LLM)
Broadly listed in cloud/platform job descriptions and Microsoft’s core PaaS offering for web apps; strong Azure ecosystem adoption keeps it a common hiring-pipeline skill.
Microsoft ·proprietary ·since 2015 (0.98)
Azure App Service is a specific Azure hosting product with a clear name; in typical JDs it is unlikely to be mistaken for a different catalog skill.
Not versioned
Service ·application_hosting_service confidence 0.97
By the Platform vs Service rule, Azure App Service is a specific managed capability inside the Azure platform rather than a standalone user-run tool.
- Category
- Service
- Sub-category
- application_hosting_service
- Skill nature
- CLOUD_SERVICE
- Volatility
- STABLE
- Typical lifespan
- EVERGREEN
- Version strategy
- NOT_APPLICABLE
Dimensions (API 2 worklist)
-
Cloud Platforms Catalog dimension db id 20
Library dimension (catalog)
Roles linked in library: Backend Engineer, Cybersecurity Engineer, Data Engineer, ML Engineer
Locked dimensions (v3 placement)
-
Cloud Platform Services
Reuses catalog slug
Core services and managed offerings within major cloud provider ecosystems. Azure App Service belongs here because it is a first-party Azure hosting service used to deploy and run web applications.
API 3 link attempts (this skill)
| Dimension | Skill↔dim | Role↔dim | Outcome |
|---|---|---|---|
|
Cloud Platforms
cloud-platforms
|
✓ | ✓ | New skill saved · Existing dimension (library) · Role↔dimension saved |
Skill enrichment (orchestrator / LLM)
IIS remains a common Windows web server in enterprise JDs and Microsoft still ships/supports it in Windows Server; it’s widely used alongside ASP.NET hosting rather than being sunset.
Microsoft ·proprietary ·since 1995 (0.99)
IIS is a well-known, specific Microsoft web server acronym in JDs; it is unlikely to be reasonably confused with another catalog skill in typical hiring context.
Not versioned
Tool ·web_server_tool confidence 0.93
IIS is software you run and operate as a server on your own infrastructure, so by the Tool vs Platform rule it is a Tool rather than a hosted platform or service.
- Category
- Tool
- Sub-category
- web_server_tool
- Skill nature
- TOOL
- Volatility
- STABLE
- Typical lifespan
- EVERGREEN
- Version strategy
- NOT_APPLICABLE
Dimensions (API 2 worklist)
-
Web Server Administration Proposed / LLM
Proposed / LLM dimension (no DB id yet)
Locked dimensions (v3 placement)
-
Web Server Administration
Pipeline tentative id
Administration and configuration of web server software used to host and route web applications. IIS belongs here because it is a Microsoft web server platform used to publish sites, manage bindings, and control request handling.
API 3 link attempts (this skill)
| Dimension | Skill↔dim | Role↔dim | Outcome |
|---|---|---|---|
|
Web Server Administration
d_init_01
|
✓ | — | New skill saved · Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role) |
Skill enrichment (orchestrator / LLM)
Agile is a hiring-pipeline staple: job postings across software roles routinely list Agile/Scrum experience, and major employers and vendors still train/certify around it.
(0.99)
In JDs, "Agile" usually clearly refers to the software development methodology; it is not commonly mistaken for a different catalog skill.
Not versioned
Methodology ·agile_methodology confidence 0.99
Agile is a way of working and organizing delivery, so by the Concept vs Methodology rule it is a Methodology rather than a Concept or Architecture.
- Category
- Methodology
- Sub-category
- agile_methodology
- Skill nature
- METHODOLOGY
- Volatility
- STABLE
- Typical lifespan
- EVERGREEN
- Version strategy
- NOT_APPLICABLE
Dimensions (API 2 worklist)
-
Agile Delivery Practices Proposed / LLM
Proposed / LLM dimension (no DB id yet)
Locked dimensions (v3 placement)
-
Agile Delivery Practices
Pipeline tentative id
Agile delivery practices cover iterative planning, cross-functional collaboration, and adaptive execution used to ship software in short cycles. Agile fits here because it describes the team operating model and delivery cadence rather than a specific technical tool or framework.
API 3 link attempts (this skill)
| Dimension | Skill↔dim | Role↔dim | Outcome |
|---|---|---|---|
|
Agile Delivery Practices
d_init_01
|
✓ | — | New skill saved · Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role) |
All API 3 persistence rows
Same grid as the skill-extractor “Persistence items” table: one row per (skill × dimension) work item.
| Skill | Tag | Dimension | Skill↔dim | Role↔dim | Outcome | Notes |
|---|---|---|---|---|---|---|
| Python | in_db |
Programming Languages
programming-languages
|
✓ | ✓ | Existing dimension (library) · Role↔dimension saved | |
| Python | in_db |
Programming Languages and Scripting
programming-languages-and-scripting
|
✓ | — | Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role) | |
| Python | in_db |
Programming Languages for Data Work
programming-languages-for-data-work
|
✓ | — | Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role) | |
| Python | in_db |
Programming Languages for ML Systems
programming-languages-for-ml-systems
|
✓ | — | Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role) | |
| ASP.NET Core | in_db |
Web Application Frameworks
web-application-frameworks
|
✓ | ✓ | Existing dimension (library) · Role↔dimension saved | |
| SQL Server | in_db |
Relational Database Design
relational-database-design
|
✓ | ✓ | Existing dimension (library) · Role↔dimension saved | |
| PostgreSQL | in_db |
Relational Database Design
relational-database-design
|
✓ | ✓ | Existing dimension (library) · Role↔dimension saved | |
| MongoDB | in_db |
NoSQL Databases
nosql-databases
|
✓ | ✓ | Existing dimension (library) · Role↔dimension saved | |
| REST | in_db |
API Design and Contracts
api-design-and-contracts
|
✓ | ✓ | Existing dimension (library) · Role↔dimension saved | |
| Integration Testing | in_db |
Testing and Quality Assurance
testing-and-quality-assurance
|
✓ | ✓ | Existing dimension (library) · Role↔dimension saved | |
| React.js | in_db |
React Frontend Development
d_init_01
|
✓ | — | New skill saved · New dimension saved (reconciliation separate) · Role↔dimension skipped (dimension not under chosen role) | |
| Cosmos DB | in_db |
NoSQL Databases
nosql-databases
|
✓ | ✓ | New skill saved · Existing dimension (library) · Role↔dimension saved | |
| Code Review | in_db |
Code Review Practices
d_init_01
|
✓ | — | New skill saved · Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role) | |
| Unit Testing | in_db |
Unit Testing Practices
d_init_01
|
✓ | — | New skill saved · Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role) | |
| Azure App Service | in_db |
Cloud Platforms
cloud-platforms
|
✓ | ✓ | New skill saved · Existing dimension (library) · Role↔dimension saved | |
| IIS | in_db |
Web Server Administration
d_init_01
|
✓ | — | New skill saved · Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role) | |
| Agile | in_db |
Agile Delivery Practices
d_init_01
|
✓ | — | New skill saved · Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role) |
Library artifacts (this run)
| Kind | Detail | DB id |
|---|---|---|
| canonical_skill_added | React.js | 514 |
| canonical_skill_added | Cosmos DB | 515 |
| canonical_skill_added | Code Review | 516 |
| canonical_skill_added | Unit Testing | 517 |
| canonical_skill_added | Azure App Service | 518 |
| canonical_skill_added | IIS | 519 |
| canonical_skill_added | Agile | 520 |
| dimension_created | React Frontend Development | 96 |
| dimension_skill_link | React.js ↔ React Frontend Development | 96 |
| dimension_skill_link | Cosmos DB ↔ NoSQL Databases | 19 |
| dimension_skill_link | Code Review ↔ Code Review Practices | 96 |
| dimension_skill_link | Unit Testing ↔ Unit Testing Practices | 96 |
| dimension_skill_link | Azure App Service ↔ Cloud Platforms | 20 |
| dimension_skill_link | IIS ↔ Web Server Administration | 96 |
| dimension_skill_link | Agile ↔ Agile Delivery Practices | 96 |
nano JD Parser — gpt-4.1-nano click to toggle
Show raw JSON
{
"JD_type": "pass",
"about_company": null,
"certifications": [],
"company_name": null,
"ctc": null,
"domain": {
"primary": {
"aliases": [
"ITES",
"BPO"
],
"domain": "IT Services \u0026 Consulting"
},
"secondary": null
},
"education": [
{
"level": "Bachelor\u0027s",
"qualification": "BTECH/BE - Computer Science / Information Technology (or related)",
"raw": "Bachelors degree in Computer Science, Information Technology, or related field",
"requirement": "required"
}
],
"experience": {
"max": null,
"min": 7,
"raw": "7+ Years"
},
"job_locations": [
{
"aliases": [
"Bengaluru"
],
"city": "Bangalore",
"country": "India",
"state": null,
"work_mode": null
}
],
"role": "Full Stack Developer",
"role_archetype": "Engineering",
"roles_and_responsibilities": [
{
"bullet_count": 10,
"heading": "Key Responsibilities",
"heading_was_present": true,
"source_marker": {
"first_5_words": "\u2022 Develop and maintain scalable",
"last_5_words": "and recommend improvements to applications"
},
"text": "\u2022 Develop and maintain scalable web applications using Python, .NET Core (ASP.NET Core), and React.js\n\u2022 Collaborate with UI/UX designers, product managers, and development teams to build new features and enhance existing applications\n\u2022 Design, optimize, and manage relational and NoSQL databases such as SQL Server, PostgreSQL, MongoDB, and Cosmos DB\n\u2022 Write clean, maintainable, secure, and high-performance code following best development practices\n\u2022 Develop and integrate RESTful APIs and third-party services\n\u2022 Conduct code reviews and implement unit/integration testing to ensure application quality\n\u2022 Troubleshoot, debug, and resolve issues across frontend and backend systems\n\u2022 Handle deployment and hosting activities on Azure App Services and IIS Servers\n\u2022 Participate in Agile ceremonies including sprint planning, stand-ups, and retrospectives\n\u2022 Stay updated with emerging technologies and recommend improvements to applications and processes",
"word_count": 134
}
],
"urls": []
}
API 1 — extract-from-jd click to toggle
{
"final_skills": [
{
"is_primary": true,
"skill_name": "Python"
},
{
"is_primary": true,
"skill_name": "ASP.NET Core"
},
{
"is_primary": true,
"skill_name": "React.js"
},
{
"is_primary": true,
"skill_name": "SQL Server"
},
{
"is_primary": true,
"skill_name": "PostgreSQL"
},
{
"is_primary": true,
"skill_name": "MongoDB"
},
{
"is_primary": true,
"skill_name": "Cosmos DB"
},
{
"is_primary": true,
"skill_name": "REST"
},
{
"is_primary": true,
"skill_name": "Code Review"
},
{
"is_primary": true,
"skill_name": "Unit Testing"
},
{
"is_primary": true,
"skill_name": "Integration Testing"
},
{
"is_primary": true,
"skill_name": "Azure App Service"
},
{
"is_primary": true,
"skill_name": "IIS"
},
{
"is_primary": true,
"skill_name": "Agile"
}
],
"jd_role": {
"display_name": "Full Stack Developer",
"rationale": null,
"role_archetype": "Engineering",
"slug": ""
},
"nano_parsed": {
"JD_type": "pass",
"about_company": null,
"certifications": [],
"company_name": null,
"ctc": null,
"domain": {
"primary": {
"aliases": [
"ITES",
"BPO"
],
"domain": "IT Services \u0026 Consulting"
},
"secondary": null
},
"education": [
{
"level": "Bachelor\u0027s",
"qualification": "BTECH/BE - Computer Science / Information Technology (or related)",
"raw": "Bachelors degree in Computer Science, Information Technology, or related field",
"requirement": "required"
}
],
"experience": {
"max": null,
"min": 7,
"raw": "7+ Years"
},
"job_locations": [
{
"aliases": [
"Bengaluru"
],
"city": "Bangalore",
"country": "India",
"state": null,
"work_mode": null
}
],
"role": "Full Stack Developer",
"role_archetype": "Engineering",
"roles_and_responsibilities": [
{
"bullet_count": 10,
"heading": "Key Responsibilities",
"heading_was_present": true,
"source_marker": {
"first_5_words": "\u2022 Develop and maintain scalable",
"last_5_words": "and recommend improvements to applications"
},
"text": "\u2022 Develop and maintain scalable web applications using Python, .NET Core (ASP.NET Core), and React.js\n\u2022 Collaborate with UI/UX designers, product managers, and development teams to build new features and enhance existing applications\n\u2022 Design, optimize, and manage relational and NoSQL databases such as SQL Server, PostgreSQL, MongoDB, and Cosmos DB\n\u2022 Write clean, maintainable, secure, and high-performance code following best development practices\n\u2022 Develop and integrate RESTful APIs and third-party services\n\u2022 Conduct code reviews and implement unit/integration testing to ensure application quality\n\u2022 Troubleshoot, debug, and resolve issues across frontend and backend systems\n\u2022 Handle deployment and hosting activities on Azure App Services and IIS Servers\n\u2022 Participate in Agile ceremonies including sprint planning, stand-ups, and retrospectives\n\u2022 Stay updated with emerging technologies and recommend improvements to applications and processes",
"word_count": 134
}
],
"urls": []
},
"run_id": null
}
API 2 — extract-details
{
"alias_matches": [
{
"alias_persist_skipped_reason": "alias_text already exists for this canonical skill",
"alias_persisted": false,
"existing_alias_id": 67,
"existing_alias_text": "Python",
"input_term": "Python",
"matched_canonical": {
"category_id": 6,
"display_name": "Python",
"id": 5,
"is_also_category": false,
"is_extractable": true,
"skill_nature": "LANGUAGE",
"slug": "python",
"sub_category_id": 96,
"typical_lifespan": "EVERGREEN",
"volatility": "STABLE"
},
"matched_via": "alias"
},
{
"alias_persist_skipped_reason": "alias_text already exists for this canonical skill",
"alias_persisted": false,
"existing_alias_id": 80,
"existing_alias_text": "ASP.NET Core",
"input_term": "ASP.NET Core",
"matched_canonical": {
"category_id": 5,
"display_name": "ASP.NET Core",
"id": 7,
"is_also_category": false,
"is_extractable": true,
"skill_nature": "FRAMEWORK",
"slug": "asp-net-core",
"sub_category_id": 35,
"typical_lifespan": "EVERGREEN",
"volatility": "STABLE"
},
"matched_via": "alias"
},
{
"alias_persist_skipped_reason": "alias_text already exists for this canonical skill",
"alias_persisted": false,
"existing_alias_id": 135,
"existing_alias_text": "SQL Server",
"input_term": "SQL Server",
"matched_canonical": {
"category_id": 3,
"display_name": "SQL Server",
"id": 18,
"is_also_category": false,
"is_extractable": true,
"skill_nature": "TOOL",
"slug": "sql-server",
"sub_category_id": 29,
"typical_lifespan": "EVERGREEN",
"volatility": "STABLE"
},
"matched_via": "alias"
},
{
"alias_persist_skipped_reason": "alias_text already exists for this canonical skill",
"alias_persisted": false,
"existing_alias_id": 121,
"existing_alias_text": "PostgreSQL",
"input_term": "PostgreSQL",
"matched_canonical": {
"category_id": 3,
"display_name": "PostgreSQL",
"id": 16,
"is_also_category": false,
"is_extractable": true,
"skill_nature": "TOOL",
"slug": "postgresql",
"sub_category_id": 29,
"typical_lifespan": "EVERGREEN",
"volatility": "STABLE"
},
"matched_via": "alias"
},
{
"alias_persist_skipped_reason": "alias_text already exists for this canonical skill",
"alias_persisted": false,
"existing_alias_id": 232,
"existing_alias_text": "MongoDB",
"input_term": "MongoDB",
"matched_canonical": {
"category_id": 3,
"display_name": "MongoDB",
"id": 91,
"is_also_category": false,
"is_extractable": true,
"skill_nature": "TOOL",
"slug": "mongodb",
"sub_category_id": 27,
"typical_lifespan": "EVERGREEN",
"volatility": "STABLE"
},
"matched_via": "alias"
},
{
"alias_persist_skipped_reason": "alias_text already exists for this canonical skill",
"alias_persisted": false,
"existing_alias_id": 106,
"existing_alias_text": "REST",
"input_term": "REST",
"matched_canonical": {
"category_id": 10,
"display_name": "REST",
"id": 11,
"is_also_category": false,
"is_extractable": true,
"skill_nature": "PROTOCOL",
"slug": "rest",
"sub_category_id": 48,
"typical_lifespan": "EVERGREEN",
"volatility": "STABLE"
},
"matched_via": "alias"
},
{
"alias_persist_skipped_reason": "alias_text already exists for this canonical skill",
"alias_persisted": false,
"existing_alias_id": 193,
"existing_alias_text": "integration testing",
"input_term": "Integration Testing",
"matched_canonical": {
"category_id": 8,
"display_name": "integration testing",
"id": 56,
"is_also_category": false,
"is_extractable": true,
"skill_nature": "METHODOLOGY",
"slug": "integration-testing",
"sub_category_id": 44,
"typical_lifespan": "EVERGREEN",
"volatility": "STABLE"
},
"matched_via": "alias"
}
],
"candidate_roles": [
{
"display_name": "Backend Engineer",
"id": 1,
"rationale": null,
"role_archetype": "A Backend Engineer designs, builds, and maintains the server-side logic and data handling that power applications and services. They focus on implementing reliable business functionality, integrating with other systems, and ensuring the backend is scalable, maintainable, and observable.",
"slug": "backend-engineer",
"source": "db"
},
{
"display_name": "Cybersecurity Engineer",
"id": 5,
"rationale": null,
"role_archetype": null,
"slug": "cybersecurity-engineer",
"source": "db"
},
{
"display_name": "Data Engineer",
"id": 2,
"rationale": null,
"role_archetype": null,
"slug": "data-engineer",
"source": "db"
},
{
"display_name": "ML Engineer",
"id": 3,
"rationale": null,
"role_archetype": null,
"slug": "ml-engineer",
"source": "db"
}
],
"chosen_role": {
"display_name": "Backend Engineer",
"id": 1,
"rationale": "The primary skills required for this role align closely with the responsibilities typical of a Backend Engineer.",
"role_archetype": "A Backend Engineer designs, builds, and maintains the server-side logic and data handling that power applications and services. They focus on implementing reliable business functionality, integrating with other systems, and ensuring the backend is scalable, maintainable, and observable.",
"slug": "backend-engineer",
"source": "db"
},
"dimensions": [
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Programming Languages",
"id": 1,
"rationale": "Core server-side languages used to implement backend business logic, integrations, and service internals. This is the primary coding surface for the role across application layers.",
"slug": "programming-languages",
"source": "db"
},
"input_skill": "Python",
"llm_role": null,
"roles_from_db": [
{
"display_name": "Backend Engineer",
"id": 1,
"rationale": null,
"role_archetype": "A Backend Engineer designs, builds, and maintains the server-side logic and data handling that power applications and services. They focus on implementing reliable business functionality, integrating with other systems, and ensuring the backend is scalable, maintainable, and observable.",
"slug": "backend-engineer",
"source": "db"
}
]
},
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Programming Languages and Scripting",
"id": 59,
"rationale": "Languages used to write security automation, analysis scripts, detection logic, and remediation helpers. This is the primary implementation surface for a cybersecurity engineer across tooling and response workflows.",
"slug": "programming-languages-and-scripting",
"source": "db"
},
"input_skill": "Python",
"llm_role": null,
"roles_from_db": [
{
"display_name": "Cybersecurity Engineer",
"id": 5,
"rationale": null,
"role_archetype": null,
"slug": "cybersecurity-engineer",
"source": "db"
}
]
},
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Programming Languages for Data Work",
"id": 21,
"rationale": "Languages used to implement data pipelines, transformations, and operational glue. This is the primary coding surface for building ingestion, enrichment, and automation logic in data engineering.",
"slug": "programming-languages-for-data-work",
"source": "db"
},
"input_skill": "Python",
"llm_role": null,
"roles_from_db": [
{
"display_name": "Data Engineer",
"id": 2,
"rationale": null,
"role_archetype": null,
"slug": "data-engineer",
"source": "db"
}
]
},
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Programming Languages for ML Systems",
"id": 39,
"rationale": "Languages used to build training code, inference services, evaluation jobs, and ML glue code. This is the primary implementation surface for ML engineers across experimentation and productionization.",
"slug": "programming-languages-for-ml-systems",
"source": "db"
},
"input_skill": "Python",
"llm_role": null,
"roles_from_db": [
{
"display_name": "ML Engineer",
"id": 3,
"rationale": null,
"role_archetype": null,
"slug": "ml-engineer",
"source": "db"
}
]
},
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Web Application Frameworks",
"id": 2,
"rationale": "Server frameworks and runtimes used to build HTTP services, controllers, middleware, and request pipelines. These frameworks shape how backend endpoints are structured and delivered.",
"slug": "web-application-frameworks",
"source": "db"
},
"input_skill": "ASP.NET Core",
"llm_role": null,
"roles_from_db": [
{
"display_name": "Backend Engineer",
"id": 1,
"rationale": null,
"role_archetype": "A Backend Engineer designs, builds, and maintains the server-side logic and data handling that power applications and services. They focus on implementing reliable business functionality, integrating with other systems, and ensuring the backend is scalable, maintainable, and observable.",
"slug": "backend-engineer",
"source": "db"
}
]
},
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Relational Database Design",
"id": 4,
"rationale": "Modeling and operating relational persistence for backend services. Includes schema design, normalization, indexing, transactions, and query tuning for operational data stores.",
"slug": "relational-database-design",
"source": "db"
},
"input_skill": "SQL Server",
"llm_role": null,
"roles_from_db": [
{
"display_name": "Backend Engineer",
"id": 1,
"rationale": null,
"role_archetype": "A Backend Engineer designs, builds, and maintains the server-side logic and data handling that power applications and services. They focus on implementing reliable business functionality, integrating with other systems, and ensuring the backend is scalable, maintainable, and observable.",
"slug": "backend-engineer",
"source": "db"
}
]
},
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Relational Database Design",
"id": 4,
"rationale": "Modeling and operating relational persistence for backend services. Includes schema design, normalization, indexing, transactions, and query tuning for operational data stores.",
"slug": "relational-database-design",
"source": "db"
},
"input_skill": "PostgreSQL",
"llm_role": null,
"roles_from_db": [
{
"display_name": "Backend Engineer",
"id": 1,
"rationale": null,
"role_archetype": "A Backend Engineer designs, builds, and maintains the server-side logic and data handling that power applications and services. They focus on implementing reliable business functionality, integrating with other systems, and ensuring the backend is scalable, maintainable, and observable.",
"slug": "backend-engineer",
"source": "db"
}
]
},
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "NoSQL Databases",
"id": 19,
"rationale": "Models and manages data using non-relational database systems.",
"slug": "nosql-databases",
"source": "db"
},
"input_skill": "MongoDB",
"llm_role": null,
"roles_from_db": [
{
"display_name": "Backend Engineer",
"id": 1,
"rationale": null,
"role_archetype": "A Backend Engineer designs, builds, and maintains the server-side logic and data handling that power applications and services. They focus on implementing reliable business functionality, integrating with other systems, and ensuring the backend is scalable, maintainable, and observable.",
"slug": "backend-engineer",
"source": "db"
}
]
},
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "API Design and Contracts",
"id": 3,
"rationale": "Designing and maintaining service interfaces that other systems consume. Covers endpoint shape, payload modeling, versioning, pagination, idempotency, and compatibility rules.",
"slug": "api-design-and-contracts",
"source": "db"
},
"input_skill": "REST",
"llm_role": null,
"roles_from_db": [
{
"display_name": "Backend Engineer",
"id": 1,
"rationale": null,
"role_archetype": "A Backend Engineer designs, builds, and maintains the server-side logic and data handling that power applications and services. They focus on implementing reliable business functionality, integrating with other systems, and ensuring the backend is scalable, maintainable, and observable.",
"slug": "backend-engineer",
"source": "db"
}
]
},
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Testing and Quality Assurance",
"id": 12,
"rationale": "Backend-specific test strategies used to validate service behavior and integration points. Covers automated test layers, contract checks, fixtures, and regression prevention.",
"slug": "testing-and-quality-assurance",
"source": "db"
},
"input_skill": "Integration Testing",
"llm_role": null,
"roles_from_db": [
{
"display_name": "Backend Engineer",
"id": 1,
"rationale": null,
"role_archetype": "A Backend Engineer designs, builds, and maintains the server-side logic and data handling that power applications and services. They focus on implementing reliable business functionality, integrating with other systems, and ensuring the backend is scalable, maintainable, and observable.",
"slug": "backend-engineer",
"source": "db"
}
]
},
{
"dimension": {
"difficulty_hint": null,
"display_name": "React Frontend Development",
"id": null,
"rationale": "Building interactive web user interfaces with React.js, including component composition, state management, hooks, and rendering patterns. React.js belongs here because it is a core library for client-side UI development in modern web applications.",
"slug": "d_init_01",
"source": "llm"
},
"input_skill": "React.js",
"llm_role": null,
"roles_from_db": []
},
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "NoSQL Databases",
"id": 19,
"rationale": "Models and manages data using non-relational database systems.",
"slug": "nosql-databases",
"source": "db"
},
"input_skill": "Cosmos DB",
"llm_role": null,
"roles_from_db": [
{
"display_name": "Backend Engineer",
"id": 1,
"rationale": null,
"role_archetype": "A Backend Engineer designs, builds, and maintains the server-side logic and data handling that power applications and services. They focus on implementing reliable business functionality, integrating with other systems, and ensuring the backend is scalable, maintainable, and observable.",
"slug": "backend-engineer",
"source": "db"
}
]
},
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "NoSQL Databases",
"id": 19,
"rationale": "Models and manages data using non-relational database systems.",
"slug": "nosql-databases",
"source": "db"
},
"input_skill": "Cosmos DB",
"llm_role": null,
"roles_from_db": [
{
"display_name": "Backend Engineer",
"id": 1,
"rationale": null,
"role_archetype": "A Backend Engineer designs, builds, and maintains the server-side logic and data handling that power applications and services. They focus on implementing reliable business functionality, integrating with other systems, and ensuring the backend is scalable, maintainable, and observable.",
"slug": "backend-engineer",
"source": "db"
}
]
},
{
"dimension": {
"difficulty_hint": null,
"display_name": "Code Review Practices",
"id": null,
"rationale": "Reviewing code changes for correctness, maintainability, security, and alignment with team standards. This skill belongs here because it is a core collaborative engineering practice rather than a language, framework, or platform skill.",
"slug": "d_init_01",
"source": "llm"
},
"input_skill": "Code Review",
"llm_role": null,
"roles_from_db": []
},
{
"dimension": {
"difficulty_hint": null,
"display_name": "Unit Testing Practices",
"id": null,
"rationale": "Techniques for writing isolated, repeatable tests that verify individual functions, classes, and modules. This skill belongs here because unit testing is the core practice of validating small code units before integration or end-to-end testing.",
"slug": "d_init_01",
"source": "llm"
},
"input_skill": "Unit Testing",
"llm_role": null,
"roles_from_db": []
},
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Cloud Platforms",
"id": 20,
"rationale": "Proficiency in major cloud service provider platforms and their core services.",
"slug": "cloud-platforms",
"source": "db"
},
"input_skill": "Azure App Service",
"llm_role": null,
"roles_from_db": [
{
"display_name": "Backend Engineer",
"id": 1,
"rationale": null,
"role_archetype": "A Backend Engineer designs, builds, and maintains the server-side logic and data handling that power applications and services. They focus on implementing reliable business functionality, integrating with other systems, and ensuring the backend is scalable, maintainable, and observable.",
"slug": "backend-engineer",
"source": "db"
},
{
"display_name": "Cybersecurity Engineer",
"id": 5,
"rationale": null,
"role_archetype": null,
"slug": "cybersecurity-engineer",
"source": "db"
},
{
"display_name": "Data Engineer",
"id": 2,
"rationale": null,
"role_archetype": null,
"slug": "data-engineer",
"source": "db"
},
{
"display_name": "ML Engineer",
"id": 3,
"rationale": null,
"role_archetype": null,
"slug": "ml-engineer",
"source": "db"
}
]
},
{
"dimension": {
"difficulty_hint": null,
"display_name": "Web Server Administration",
"id": null,
"rationale": "Administration and configuration of web server software used to host and route web applications. IIS belongs here because it is a Microsoft web server platform used to publish sites, manage bindings, and control request handling.",
"slug": "d_init_01",
"source": "llm"
},
"input_skill": "IIS",
"llm_role": null,
"roles_from_db": []
},
{
"dimension": {
"difficulty_hint": null,
"display_name": "Agile Delivery Practices",
"id": null,
"rationale": "Agile delivery practices cover iterative planning, cross-functional collaboration, and adaptive execution used to ship software in short cycles. Agile fits here because it describes the team operating model and delivery cadence rather than a specific technical tool or framework.",
"slug": "d_init_01",
"source": "llm"
},
"input_skill": "Agile",
"llm_role": null,
"roles_from_db": []
}
],
"input_final_skills": [
"Python",
"ASP.NET Core",
"React.js",
"SQL Server",
"PostgreSQL",
"MongoDB",
"Cosmos DB",
"REST",
"Code Review",
"Unit Testing",
"Integration Testing",
"Azure App Service",
"IIS",
"Agile"
],
"input_llm_skills": [
"Python",
"ASP.NET Core",
"React.js",
"SQL Server",
"PostgreSQL",
"MongoDB",
"Cosmos DB",
"REST",
"Code Review",
"Unit Testing",
"Integration Testing",
"Azure App Service",
"IIS",
"Agile"
],
"new_aliases_persisted": 0,
"run_id": "39d79165-fae2-4b74-8eb1-d9ee388fdb2b",
"skills_detail": [
{
"aliases_in_db": [
{
"alias_text": "Python",
"alias_type": "CANONICAL",
"id": 67,
"is_primary": true,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "Python 2",
"alias_type": "VERSION",
"id": 72,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "Python 2.x",
"alias_type": "VERSION",
"id": 74,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "Python 3",
"alias_type": "VERSION",
"id": 73,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "Python 3.10",
"alias_type": "VERSION",
"id": 76,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "Python 3.11",
"alias_type": "VERSION",
"id": 77,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "Python 3.12",
"alias_type": "VERSION",
"id": 78,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "Python 3.x",
"alias_type": "VERSION",
"id": 75,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "py2",
"alias_type": "VERSION",
"id": 68,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "py3",
"alias_type": "VERSION",
"id": 69,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "python2",
"alias_type": "VERSION",
"id": 70,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "python3",
"alias_type": "VERSION",
"id": 71,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
}
],
"canonical": {
"category_id": 6,
"display_name": "Python",
"id": 5,
"is_also_category": false,
"is_extractable": true,
"skill_nature": "LANGUAGE",
"slug": "python",
"sub_category_id": 96,
"typical_lifespan": "EVERGREEN",
"volatility": "STABLE"
},
"dimensions": [
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Programming Languages",
"id": 1,
"rationale": "Core server-side languages used to implement backend business logic, integrations, and service internals. This is the primary coding surface for the role across application layers.",
"slug": "programming-languages",
"source": "db"
},
"input_skill": "Python",
"llm_role": null,
"roles_from_db": [
{
"display_name": "Backend Engineer",
"id": 1,
"rationale": null,
"role_archetype": "A Backend Engineer designs, builds, and maintains the server-side logic and data handling that power applications and services. They focus on implementing reliable business functionality, integrating with other systems, and ensuring the backend is scalable, maintainable, and observable.",
"slug": "backend-engineer",
"source": "db"
}
]
},
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Programming Languages and Scripting",
"id": 59,
"rationale": "Languages used to write security automation, analysis scripts, detection logic, and remediation helpers. This is the primary implementation surface for a cybersecurity engineer across tooling and response workflows.",
"slug": "programming-languages-and-scripting",
"source": "db"
},
"input_skill": "Python",
"llm_role": null,
"roles_from_db": [
{
"display_name": "Cybersecurity Engineer",
"id": 5,
"rationale": null,
"role_archetype": null,
"slug": "cybersecurity-engineer",
"source": "db"
}
]
},
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Programming Languages for Data Work",
"id": 21,
"rationale": "Languages used to implement data pipelines, transformations, and operational glue. This is the primary coding surface for building ingestion, enrichment, and automation logic in data engineering.",
"slug": "programming-languages-for-data-work",
"source": "db"
},
"input_skill": "Python",
"llm_role": null,
"roles_from_db": [
{
"display_name": "Data Engineer",
"id": 2,
"rationale": null,
"role_archetype": null,
"slug": "data-engineer",
"source": "db"
}
]
},
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Programming Languages for ML Systems",
"id": 39,
"rationale": "Languages used to build training code, inference services, evaluation jobs, and ML glue code. This is the primary implementation surface for ML engineers across experimentation and productionization.",
"slug": "programming-languages-for-ml-systems",
"source": "db"
},
"input_skill": "Python",
"llm_role": null,
"roles_from_db": [
{
"display_name": "ML Engineer",
"id": 3,
"rationale": null,
"role_archetype": null,
"slug": "ml-engineer",
"source": "db"
}
]
}
],
"input_skill": "Python",
"matched_via": "alias",
"new_alias_persisted": false,
"new_alias_text": null,
"new_skill_meta": null,
"source_tag": "db",
"was_in_llm_skills": true
},
{
"aliases_in_db": [
{
"alias_text": "ASP.NET Core",
"alias_type": "CANONICAL",
"id": 80,
"is_primary": true,
"match_strategy": "CASE_INSENSITIVE"
}
],
"canonical": {
"category_id": 5,
"display_name": "ASP.NET Core",
"id": 7,
"is_also_category": false,
"is_extractable": true,
"skill_nature": "FRAMEWORK",
"slug": "asp-net-core",
"sub_category_id": 35,
"typical_lifespan": "EVERGREEN",
"volatility": "STABLE"
},
"dimensions": [
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Web Application Frameworks",
"id": 2,
"rationale": "Server frameworks and runtimes used to build HTTP services, controllers, middleware, and request pipelines. These frameworks shape how backend endpoints are structured and delivered.",
"slug": "web-application-frameworks",
"source": "db"
},
"input_skill": "ASP.NET Core",
"llm_role": null,
"roles_from_db": [
{
"display_name": "Backend Engineer",
"id": 1,
"rationale": null,
"role_archetype": "A Backend Engineer designs, builds, and maintains the server-side logic and data handling that power applications and services. They focus on implementing reliable business functionality, integrating with other systems, and ensuring the backend is scalable, maintainable, and observable.",
"slug": "backend-engineer",
"source": "db"
}
]
}
],
"input_skill": "ASP.NET Core",
"matched_via": "alias",
"new_alias_persisted": false,
"new_alias_text": null,
"new_skill_meta": null,
"source_tag": "db",
"was_in_llm_skills": true
},
{
"aliases_in_db": [],
"canonical": null,
"dimensions": [
{
"dimension": {
"difficulty_hint": null,
"display_name": "React Frontend Development",
"id": null,
"rationale": "Building interactive web user interfaces with React.js, including component composition, state management, hooks, and rendering patterns. React.js belongs here because it is a core library for client-side UI development in modern web applications.",
"slug": "d_init_01",
"source": "llm"
},
"input_skill": "React.js",
"llm_role": null,
"roles_from_db": []
}
],
"input_skill": "React.js",
"matched_via": null,
"new_alias_persisted": false,
"new_alias_text": null,
"new_skill_meta": {
"derived": {
"category": "Framework",
"skill_nature": "FRAMEWORK",
"sub_category": "frontend_ui_framework",
"typical_lifespan": "EVERGREEN",
"version_strategy": "SEPARATE_ENTITY",
"volatility": "STABLE"
},
"enrichment": {
"ambiguity": {
"ambiguity_flag": false,
"confused_with": [],
"reasoning": "React.js is a well-known, specific frontend framework name and is unlikely to be confused with another catalog skill in typical job descriptions."
},
"context_keywords": {
"context_keywords": [
"JSX",
"hooks",
"Redux",
"Next.js",
"TypeScript",
"virtual DOM",
"component lifecycle",
"state management",
"React Router",
"props",
"useEffect",
"useState",
"Material UI",
"Tailwind CSS",
"SSR"
]
},
"maturity": {
"confidence": 0.99,
"maturity": "well_known",
"reasoning": "React.js is a hiring-pipeline staple with very high JD volume across frontend roles and broad ecosystem adoption; it remains one of the most commonly requested UI frameworks on job boards and in GitHub usage trends."
},
"skill_id": "react-js",
"vendor_license": {
"confidence": 0.99,
"license": "mit",
"vendor": "Meta",
"year_introduced": 2013
},
"versioning": {
"current_version": "18",
"version_aliases": {
"React 0.1": "0.1",
"React 0.10": "0.10",
"React 0.11": "0.11",
"React 0.12": "0.12",
"React 0.13": "0.13",
"React 0.14": "0.14",
"React 0.2": "0.2",
"React 0.3": "0.3",
"React 0.4": "0.4",
"React 0.5": "0.5",
"React 0.6": "0.6",
"React 0.7": "0.7",
"React 0.8": "0.8",
"React 0.9": "0.9",
"React 15": "15",
"React 16": "16",
"React 17": "17",
"React 18": "18",
"React.js 15": "15",
"React.js 16": "16",
"React.js 17": "17",
"React.js 18": "18"
},
"versioned": true
}
},
"keep_log": [],
"locked_dimensions": [
{
"description": "Building interactive web user interfaces with React.js, including component composition, state management, hooks, and rendering patterns. React.js belongs here because it is a core library for client-side UI development in modern web applications.",
"exemplar_skills": [
"React.js",
"JSX",
"React Hooks",
"React Components",
"React Context",
"Component State Management"
],
"in_scope": "React.js, JSX, components, props, state, hooks, context, lifecycle patterns, conditional rendering, lists and keys, forms, client-side UI composition",
"name": "React Frontend Development",
"out_of_scope": "Backend API design, server-side rendering frameworks, mobile app UI frameworks, CSS-only styling systems, state management libraries as standalone architecture concerns",
"overlap_flags": [
{
"reason": "React development uses JavaScript or TypeScript, but the dimension is about the UI framework rather than the language itself.",
"with_dim_id": "programming-languages-and-scripting",
"with_dim_name": null,
"with_role": "Cybersecurity Engineer"
}
],
"tentative_id": "d_init_01"
}
],
"merge_log": [],
"placed": {
"name": "React.js",
"placement_confidence": 0.92,
"primary_dimension": "d_init_01",
"reasoning": "Deterministic JD placement: locked_dimensions has 1 dimension(s) from skill-driven dimension generation after reconciliation; primary_dimension is the first locked dim.",
"secondary_dimensions": [],
"skill_id": "react-js"
},
"relationships": {
"child_skills": [],
"parent_skills": [],
"related_to": [
"swiftui",
"uikit",
"mvvm",
"asp-net-core",
"github-actions",
"java",
"scala",
"rest-apis",
"schema-contracts",
"dynamic-type"
],
"requires": [],
"skill_id": "react-js",
"suppress_on_match": []
},
"skill_id": "react-js",
"split_log": [],
"typed": {
"alternatives_considered": [],
"confidence": 0.98,
"name": "React.js",
"reasoning": "React.js is a framework because users build applications inside it and it drives the UI structure by calling application code, matching the Tool vs Framework rule.",
"skill_id": "react-js",
"subtype": "frontend_ui_framework",
"type": "Framework"
},
"warnings": []
},
"source_tag": "llm",
"was_in_llm_skills": true
},
{
"aliases_in_db": [
{
"alias_text": "SQL Server",
"alias_type": "CANONICAL",
"id": 135,
"is_primary": true,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "SQL Server 2000",
"alias_type": "VERSION",
"id": 138,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "SQL Server 2005",
"alias_type": "VERSION",
"id": 139,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "SQL Server 2008",
"alias_type": "VERSION",
"id": 140,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "SQL Server 2012",
"alias_type": "VERSION",
"id": 141,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "SQL Server 2014",
"alias_type": "VERSION",
"id": 142,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "SQL Server 2016",
"alias_type": "VERSION",
"id": 143,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "SQL Server 2017",
"alias_type": "VERSION",
"id": 144,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "SQL Server 2019",
"alias_type": "VERSION",
"id": 145,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "SQL Server 2022",
"alias_type": "VERSION",
"id": 146,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "SQL Server 6.5",
"alias_type": "VERSION",
"id": 136,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "SQL Server 7.0",
"alias_type": "VERSION",
"id": 137,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
}
],
"canonical": {
"category_id": 3,
"display_name": "SQL Server",
"id": 18,
"is_also_category": false,
"is_extractable": true,
"skill_nature": "TOOL",
"slug": "sql-server",
"sub_category_id": 29,
"typical_lifespan": "EVERGREEN",
"volatility": "STABLE"
},
"dimensions": [
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Relational Database Design",
"id": 4,
"rationale": "Modeling and operating relational persistence for backend services. Includes schema design, normalization, indexing, transactions, and query tuning for operational data stores.",
"slug": "relational-database-design",
"source": "db"
},
"input_skill": "SQL Server",
"llm_role": null,
"roles_from_db": [
{
"display_name": "Backend Engineer",
"id": 1,
"rationale": null,
"role_archetype": "A Backend Engineer designs, builds, and maintains the server-side logic and data handling that power applications and services. They focus on implementing reliable business functionality, integrating with other systems, and ensuring the backend is scalable, maintainable, and observable.",
"slug": "backend-engineer",
"source": "db"
}
]
}
],
"input_skill": "SQL Server",
"matched_via": "alias",
"new_alias_persisted": false,
"new_alias_text": null,
"new_skill_meta": null,
"source_tag": "db",
"was_in_llm_skills": true
},
{
"aliases_in_db": [
{
"alias_text": "PostgreSQL",
"alias_type": "CANONICAL",
"id": 121,
"is_primary": true,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "PG 13",
"alias_type": "VERSION",
"id": 122,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "PG 14",
"alias_type": "VERSION",
"id": 123,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "PG 15",
"alias_type": "VERSION",
"id": 124,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "PG 16",
"alias_type": "VERSION",
"id": 125,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "PostgreSQL 13",
"alias_type": "VERSION",
"id": 130,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "PostgreSQL 14",
"alias_type": "VERSION",
"id": 131,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "PostgreSQL 15",
"alias_type": "VERSION",
"id": 132,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "PostgreSQL 16",
"alias_type": "VERSION",
"id": 133,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "Postgres 13",
"alias_type": "VERSION",
"id": 126,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "Postgres 14",
"alias_type": "VERSION",
"id": 127,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "Postgres 15",
"alias_type": "VERSION",
"id": 128,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "Postgres 16",
"alias_type": "VERSION",
"id": 129,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
}
],
"canonical": {
"category_id": 3,
"display_name": "PostgreSQL",
"id": 16,
"is_also_category": false,
"is_extractable": true,
"skill_nature": "TOOL",
"slug": "postgresql",
"sub_category_id": 29,
"typical_lifespan": "EVERGREEN",
"volatility": "STABLE"
},
"dimensions": [
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Relational Database Design",
"id": 4,
"rationale": "Modeling and operating relational persistence for backend services. Includes schema design, normalization, indexing, transactions, and query tuning for operational data stores.",
"slug": "relational-database-design",
"source": "db"
},
"input_skill": "PostgreSQL",
"llm_role": null,
"roles_from_db": [
{
"display_name": "Backend Engineer",
"id": 1,
"rationale": null,
"role_archetype": "A Backend Engineer designs, builds, and maintains the server-side logic and data handling that power applications and services. They focus on implementing reliable business functionality, integrating with other systems, and ensuring the backend is scalable, maintainable, and observable.",
"slug": "backend-engineer",
"source": "db"
}
]
}
],
"input_skill": "PostgreSQL",
"matched_via": "alias",
"new_alias_persisted": false,
"new_alias_text": null,
"new_skill_meta": null,
"source_tag": "db",
"was_in_llm_skills": true
},
{
"aliases_in_db": [
{
"alias_text": "MongoDB",
"alias_type": "CANONICAL",
"id": 232,
"is_primary": true,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "MongoDB 2.0",
"alias_type": "VERSION",
"id": 238,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "MongoDB 2.2",
"alias_type": "VERSION",
"id": 239,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "MongoDB 2.4",
"alias_type": "VERSION",
"id": 240,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "MongoDB 2.6",
"alias_type": "VERSION",
"id": 241,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "MongoDB 3.0",
"alias_type": "VERSION",
"id": 242,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "MongoDB 3.2",
"alias_type": "VERSION",
"id": 243,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "MongoDB 3.4",
"alias_type": "VERSION",
"id": 244,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "MongoDB 3.6",
"alias_type": "VERSION",
"id": 245,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "MongoDB 4",
"alias_type": "VERSION",
"id": 233,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "MongoDB 4.0",
"alias_type": "VERSION",
"id": 246,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "MongoDB 4.2",
"alias_type": "VERSION",
"id": 247,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "MongoDB 4.4",
"alias_type": "VERSION",
"id": 248,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "MongoDB 5",
"alias_type": "VERSION",
"id": 234,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "MongoDB 5.0",
"alias_type": "VERSION",
"id": 249,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "MongoDB 6",
"alias_type": "VERSION",
"id": 235,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "MongoDB 6.0",
"alias_type": "VERSION",
"id": 250,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "MongoDB 7",
"alias_type": "VERSION",
"id": 236,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "MongoDB 7.0",
"alias_type": "VERSION",
"id": 251,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "MongoDB 8",
"alias_type": "VERSION",
"id": 237,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "MongoDB 8.0",
"alias_type": "VERSION",
"id": 252,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
}
],
"canonical": {
"category_id": 3,
"display_name": "MongoDB",
"id": 91,
"is_also_category": false,
"is_extractable": true,
"skill_nature": "TOOL",
"slug": "mongodb",
"sub_category_id": 27,
"typical_lifespan": "EVERGREEN",
"volatility": "STABLE"
},
"dimensions": [
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "NoSQL Databases",
"id": 19,
"rationale": "Models and manages data using non-relational database systems.",
"slug": "nosql-databases",
"source": "db"
},
"input_skill": "MongoDB",
"llm_role": null,
"roles_from_db": [
{
"display_name": "Backend Engineer",
"id": 1,
"rationale": null,
"role_archetype": "A Backend Engineer designs, builds, and maintains the server-side logic and data handling that power applications and services. They focus on implementing reliable business functionality, integrating with other systems, and ensuring the backend is scalable, maintainable, and observable.",
"slug": "backend-engineer",
"source": "db"
}
]
}
],
"input_skill": "MongoDB",
"matched_via": "alias",
"new_alias_persisted": false,
"new_alias_text": null,
"new_skill_meta": null,
"source_tag": "db",
"was_in_llm_skills": true
},
{
"aliases_in_db": [],
"canonical": null,
"dimensions": [
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "NoSQL Databases",
"id": 19,
"rationale": "Models and manages data using non-relational database systems.",
"slug": "nosql-databases",
"source": "db"
},
"input_skill": "Cosmos DB",
"llm_role": null,
"roles_from_db": [
{
"display_name": "Backend Engineer",
"id": 1,
"rationale": null,
"role_archetype": "A Backend Engineer designs, builds, and maintains the server-side logic and data handling that power applications and services. They focus on implementing reliable business functionality, integrating with other systems, and ensuring the backend is scalable, maintainable, and observable.",
"slug": "backend-engineer",
"source": "db"
}
]
},
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "NoSQL Databases",
"id": 19,
"rationale": "Models and manages data using non-relational database systems.",
"slug": "nosql-databases",
"source": "db"
},
"input_skill": "Cosmos DB",
"llm_role": null,
"roles_from_db": [
{
"display_name": "Backend Engineer",
"id": 1,
"rationale": null,
"role_archetype": "A Backend Engineer designs, builds, and maintains the server-side logic and data handling that power applications and services. They focus on implementing reliable business functionality, integrating with other systems, and ensuring the backend is scalable, maintainable, and observable.",
"slug": "backend-engineer",
"source": "db"
}
]
}
],
"input_skill": "Cosmos DB",
"matched_via": null,
"new_alias_persisted": false,
"new_alias_text": null,
"new_skill_meta": {
"derived": {
"category": "Service",
"skill_nature": "CLOUD_SERVICE",
"sub_category": "managed_nosql_database_service",
"typical_lifespan": "EVERGREEN",
"version_strategy": "NOT_APPLICABLE",
"volatility": "STABLE"
},
"enrichment": {
"ambiguity": {
"ambiguity_flag": false,
"confused_with": [],
"reasoning": "Cosmos DB is a specific Azure database service name and is usually unambiguous in JDs; it is not commonly mistaken for another catalog skill."
},
"context_keywords": {
"context_keywords": [
"Azure",
"NoSQL",
"MongoDB API",
"Core (SQL) API",
"Gremlin API",
"Cassandra API",
"Table API",
"partition key",
"throughput",
"RU/s",
"change feed",
"global distribution",
"multi-region writes",
"consistency levels",
"TTL"
]
},
"maturity": {
"confidence": 0.86,
"maturity": "well_known",
"reasoning": "Frequently appears in Azure/cloud data engineer JDs and Microsoft positions; strong vendor support and active docs indicate broad adoption rather than niche use."
},
"skill_id": "cosmos-db",
"vendor_license": {
"confidence": 0.98,
"license": "proprietary",
"vendor": "Microsoft",
"year_introduced": 2010
},
"versioning": {
"current_version": null,
"version_aliases": {},
"versioned": false
}
},
"keep_log": [
{
"a_dim_id": "nosql-databases",
"a_name": "NoSQL Databases",
"a_role": "__skill_focal__",
"b_dim_id": "nosql-databases",
"b_name": "NoSQL Databases",
"b_role": "Backend Engineer",
"pair_kind": "cross_role",
"reasoning": "career-track: no, because Dim A is a concrete NoSQL database specialization with skills like Cosmos DB, document modeling, partition key design, and consistency tuning, while Dim B is only a generic backend label for using non-relational databases. A senior expert in A would not automatically be a senior backend engineer in B; the clusters differ in specificity and daily work.",
"similarity": 0.7084509837241068
}
],
"locked_dimensions": [
{
"description": "Non-relational database systems used for flexible schema storage, horizontal scaling, and low-latency application access. Cosmos DB fits here because it is a managed NoSQL database service with document, key-value, and other non-relational access patterns.",
"exemplar_skills": [
"Cosmos DB",
"NoSQL database design",
"Document database modeling",
"Partition key design",
"Consistency level tuning",
"Indexing strategies for NoSQL"
],
"in_scope": "Cosmos DB, document databases, key-value stores, wide-column stores, graph databases, schema-less data models, partitioning, replication, consistency models, indexing, query APIs",
"name": "NoSQL Databases",
"out_of_scope": "Relational SQL databases, data warehouse modeling, ETL pipelines, message brokers, and object storage; those belong to database, analytics, streaming, or storage dimensions.",
"overlap_flags": [
{
"reason": "Cosmos DB is an Azure-managed service, so cloud platform knowledge can overlap with service provisioning and operations.",
"with_dim_id": "cloud-platforms",
"with_dim_name": null,
"with_role": "Backend Engineer, Cybersecurity Engineer, Data Engineer, ML Engineer"
}
],
"tentative_id": "nosql-databases"
},
{
"description": "Models and manages data using non-relational database systems.",
"exemplar_skills": [
"NoSQL Databases"
],
"in_scope": "Skills, tools, and practices that belong under NoSQL Databases for the target role, including items implied by the dimension rationale.",
"name": "NoSQL Databases",
"out_of_scope": "Adjacent clusters explicitly not owned by NoSQL Databases, including unrelated platforms, roles, and skill families per library policy.",
"overlap_flags": [],
"tentative_id": "nosql-databases"
}
],
"merge_log": [],
"placed": {
"name": "Cosmos DB",
"placement_confidence": 0.92,
"primary_dimension": "nosql-databases",
"reasoning": "Deterministic JD placement: locked_dimensions has 2 dimension(s) from skill-driven dimension generation after reconciliation; primary_dimension is the first locked dim.",
"secondary_dimensions": [],
"skill_id": "cosmos-db"
},
"relationships": {
"child_skills": [],
"parent_skills": [
"azure"
],
"related_to": [
"amazon-dynamodb",
"ksqldb",
"amazon-redshift",
"apache-pulsar",
"azure-synapse-analytics",
"sqlite",
"sql-server",
"bigquery",
"amazon-s3",
"amazon-sqs"
],
"requires": [],
"skill_id": "cosmos-db",
"suppress_on_match": []
},
"skill_id": "cosmos-db",
"split_log": [],
"typed": {
"alternatives_considered": [],
"confidence": 0.97,
"name": "Cosmos DB",
"reasoning": "By the Service vs Platform rule, Cosmos DB is a specific managed capability inside Azure rather than a standalone hosted environment, so it is a Service.",
"skill_id": "cosmos-db",
"subtype": "managed_nosql_database_service",
"type": "Service"
},
"warnings": [
"stage3_post_filter_dropped_catalog_only_locked_dims:41-\u003e2"
]
},
"source_tag": "llm",
"was_in_llm_skills": true
},
{
"aliases_in_db": [
{
"alias_text": "REST",
"alias_type": "CANONICAL",
"id": 106,
"is_primary": true,
"match_strategy": "CASE_INSENSITIVE"
}
],
"canonical": {
"category_id": 10,
"display_name": "REST",
"id": 11,
"is_also_category": false,
"is_extractable": true,
"skill_nature": "PROTOCOL",
"slug": "rest",
"sub_category_id": 48,
"typical_lifespan": "EVERGREEN",
"volatility": "STABLE"
},
"dimensions": [
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "API Design and Contracts",
"id": 3,
"rationale": "Designing and maintaining service interfaces that other systems consume. Covers endpoint shape, payload modeling, versioning, pagination, idempotency, and compatibility rules.",
"slug": "api-design-and-contracts",
"source": "db"
},
"input_skill": "REST",
"llm_role": null,
"roles_from_db": [
{
"display_name": "Backend Engineer",
"id": 1,
"rationale": null,
"role_archetype": "A Backend Engineer designs, builds, and maintains the server-side logic and data handling that power applications and services. They focus on implementing reliable business functionality, integrating with other systems, and ensuring the backend is scalable, maintainable, and observable.",
"slug": "backend-engineer",
"source": "db"
}
]
}
],
"input_skill": "REST",
"matched_via": "alias",
"new_alias_persisted": false,
"new_alias_text": null,
"new_skill_meta": null,
"source_tag": "db",
"was_in_llm_skills": true
},
{
"aliases_in_db": [],
"canonical": null,
"dimensions": [
{
"dimension": {
"difficulty_hint": null,
"display_name": "Code Review Practices",
"id": null,
"rationale": "Reviewing code changes for correctness, maintainability, security, and alignment with team standards. This skill belongs here because it is a core collaborative engineering practice rather than a language, framework, or platform skill.",
"slug": "d_init_01",
"source": "llm"
},
"input_skill": "Code Review",
"llm_role": null,
"roles_from_db": []
}
],
"input_skill": "Code Review",
"matched_via": null,
"new_alias_persisted": false,
"new_alias_text": null,
"new_skill_meta": {
"derived": {
"category": "SoftSkill",
"skill_nature": "PRACTICE",
"sub_category": "code_review",
"typical_lifespan": "EVERGREEN",
"version_strategy": "NOT_APPLICABLE",
"volatility": "STABLE"
},
"enrichment": {
"ambiguity": {
"ambiguity_flag": false,
"confused_with": [],
"reasoning": "\u201cCode Review\u201d is a fairly specific engineering practice and is unlikely to be mistaken for a different catalog skill in typical job descriptions."
},
"context_keywords": {
"context_keywords": [
"pull request",
"merge request",
"diff",
"inline comments",
"approval workflow",
"GitHub",
"GitLab",
"Bitbucket",
"branch protection",
"code quality",
"linting",
"static analysis",
"PR review",
"review checklist",
"pair programming"
]
},
"maturity": {
"confidence": 0.96,
"maturity": "well_known",
"reasoning": "Code review is a standard hiring-pipeline requirement in engineering JDs and is built into major platforms like GitHub/GitLab pull-request workflows, indicating broad adoption."
},
"skill_id": "code-review",
"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": "Reviewing code changes for correctness, maintainability, security, and alignment with team standards. This skill belongs here because it is a core collaborative engineering practice rather than a language, framework, or platform skill.",
"exemplar_skills": [
"Code Review",
"Pull Request Review",
"Merge Request Review",
"Reviewing Diffs",
"Providing Review Feedback",
"Assessing Test Coverage",
"Identifying Code Smells"
],
"in_scope": "Code Review, pull request review, merge request review, reviewing diffs, approving changes, requesting revisions, identifying bugs, maintainability checks, style and consistency checks, test coverage review, design feedback, knowledge sharing",
"name": "Code Review Practices",
"out_of_scope": "Writing application code, automated unit testing, static analysis tooling, release management, incident response, architecture design ownership, security scanning tools",
"overlap_flags": [
{
"reason": "Code review often includes security findings, but that dimension owns broader security design and hardening practices.",
"with_dim_id": "security-architecture-and-hardening",
"with_dim_name": null,
"with_role": "Cybersecurity Engineer"
},
{
"reason": "Reviews may evaluate architecture and dependency structure, but that dimension owns the architectural patterns themselves.",
"with_dim_id": "app-architecture-and-dependency-injection",
"with_dim_name": null,
"with_role": "Ios engineer"
}
],
"tentative_id": "d_init_01"
}
],
"merge_log": [],
"placed": {
"name": "Code Review",
"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": "code-review"
},
"relationships": {
"child_skills": [],
"parent_skills": [],
"related_to": [
"security-review",
"post-incident-review",
"app-store-review",
"code-signing",
"gitlab-ci",
"github-actions",
"owasp-top-10",
"csrf",
"mvc",
"xcode"
],
"requires": [],
"skill_id": "code-review",
"suppress_on_match": []
},
"skill_id": "code-review",
"split_log": [],
"typed": {
"alternatives_considered": [],
"confidence": 0.96,
"name": "Code Review",
"reasoning": "Code Review is fundamentally a collaborative interpersonal practice for giving and receiving feedback, so under the Concept vs Methodology rule it fits SoftSkill rather than a technical tool or framework.",
"skill_id": "code-review",
"subtype": "code_review",
"type": "SoftSkill"
},
"warnings": []
},
"source_tag": "llm",
"was_in_llm_skills": true
},
{
"aliases_in_db": [],
"canonical": null,
"dimensions": [
{
"dimension": {
"difficulty_hint": null,
"display_name": "Unit Testing Practices",
"id": null,
"rationale": "Techniques for writing isolated, repeatable tests that verify individual functions, classes, and modules. This skill belongs here because unit testing is the core practice of validating small code units before integration or end-to-end testing.",
"slug": "d_init_01",
"source": "llm"
},
"input_skill": "Unit Testing",
"llm_role": null,
"roles_from_db": []
}
],
"input_skill": "Unit Testing",
"matched_via": null,
"new_alias_persisted": false,
"new_alias_text": null,
"new_skill_meta": {
"derived": {
"category": "Methodology",
"skill_nature": "METHODOLOGY",
"sub_category": "testing_methodology",
"typical_lifespan": "EVERGREEN",
"version_strategy": "NOT_APPLICABLE",
"volatility": "STABLE"
},
"enrichment": {
"ambiguity": {
"ambiguity_flag": false,
"confused_with": [],
"reasoning": "\"Unit Testing\" is a standard, specific testing methodology and is unlikely to be confused with a different catalog skill in typical job descriptions."
},
"context_keywords": {
"context_keywords": [
"test cases",
"assertions",
"mocking",
"stubs",
"fixtures",
"test doubles",
"regression",
"code coverage",
"TDD",
"JUnit",
"pytest",
"NUnit",
"xUnit",
"test runner",
"arrange-act-assert"
]
},
"maturity": {
"confidence": 0.98,
"maturity": "well_known",
"reasoning": "Unit testing is a standard hiring requirement across software JDs and appears in mainstream frameworks/docs; GitHub and Stack Overflow usage remain consistently high, with no successor replacing it."
},
"skill_id": "unit-testing",
"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": "Techniques for writing isolated, repeatable tests that verify individual functions, classes, and modules. This skill belongs here because unit testing is the core practice of validating small code units before integration or end-to-end testing.",
"exemplar_skills": [
"Unit Testing",
"Test-Driven Development",
"Mockito",
"pytest",
"Jest",
"JUnit",
"NUnit"
],
"in_scope": "Unit Testing, test cases, assertions, mocks, stubs, fixtures, test doubles, test isolation, Arrange-Act-Assert, TDD, JUnit, NUnit, pytest, Jest, Mocha",
"name": "Unit Testing Practices",
"out_of_scope": "Integration testing, end-to-end testing, UI automation, performance testing, and load testing, which validate larger system behavior or runtime characteristics rather than isolated code units.",
"overlap_flags": [
{
"reason": "Unit tests are written in a programming language, but the dimension is about testing practice rather than language syntax.",
"with_dim_id": "programming-languages-and-scripting",
"with_dim_name": null,
"with_role": "Cybersecurity Engineer"
},
{
"reason": "Dependency injection and modular architecture improve testability, but they are broader design concerns rather than the testing practice itself.",
"with_dim_id": "app-architecture-and-dependency-injection",
"with_dim_name": null,
"with_role": "Ios engineer"
}
],
"tentative_id": "d_init_01"
}
],
"merge_log": [],
"placed": {
"name": "Unit Testing",
"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": "unit-testing"
},
"relationships": {
"child_skills": [],
"parent_skills": [],
"related_to": [
"dbt-tests",
"azure-pipelines",
"gitlab-ci",
"github-actions",
"testflight",
"secure-baselines",
"dependency-injection",
"repository-pattern",
"rest-apis",
"mvc"
],
"requires": [],
"skill_id": "unit-testing",
"suppress_on_match": []
},
"skill_id": "unit-testing",
"split_log": [],
"typed": {
"alternatives_considered": [],
"confidence": 0.98,
"name": "Unit Testing",
"reasoning": "By the Concept vs Methodology rule, unit testing is a way of working for verifying code behavior during development, not a knowledge unit or software artifact.",
"skill_id": "unit-testing",
"subtype": "testing_methodology",
"type": "Methodology"
},
"warnings": []
},
"source_tag": "llm",
"was_in_llm_skills": true
},
{
"aliases_in_db": [
{
"alias_text": "integration testing",
"alias_type": "CANONICAL",
"id": 193,
"is_primary": true,
"match_strategy": "CASE_INSENSITIVE"
}
],
"canonical": {
"category_id": 8,
"display_name": "integration testing",
"id": 56,
"is_also_category": false,
"is_extractable": true,
"skill_nature": "METHODOLOGY",
"slug": "integration-testing",
"sub_category_id": 44,
"typical_lifespan": "EVERGREEN",
"volatility": "STABLE"
},
"dimensions": [
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Testing and Quality Assurance",
"id": 12,
"rationale": "Backend-specific test strategies used to validate service behavior and integration points. Covers automated test layers, contract checks, fixtures, and regression prevention.",
"slug": "testing-and-quality-assurance",
"source": "db"
},
"input_skill": "Integration Testing",
"llm_role": null,
"roles_from_db": [
{
"display_name": "Backend Engineer",
"id": 1,
"rationale": null,
"role_archetype": "A Backend Engineer designs, builds, and maintains the server-side logic and data handling that power applications and services. They focus on implementing reliable business functionality, integrating with other systems, and ensuring the backend is scalable, maintainable, and observable.",
"slug": "backend-engineer",
"source": "db"
}
]
}
],
"input_skill": "Integration Testing",
"matched_via": "alias",
"new_alias_persisted": false,
"new_alias_text": null,
"new_skill_meta": null,
"source_tag": "db",
"was_in_llm_skills": true
},
{
"aliases_in_db": [],
"canonical": null,
"dimensions": [
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Cloud Platforms",
"id": 20,
"rationale": "Proficiency in major cloud service provider platforms and their core services.",
"slug": "cloud-platforms",
"source": "db"
},
"input_skill": "Azure App Service",
"llm_role": null,
"roles_from_db": [
{
"display_name": "Backend Engineer",
"id": 1,
"rationale": null,
"role_archetype": "A Backend Engineer designs, builds, and maintains the server-side logic and data handling that power applications and services. They focus on implementing reliable business functionality, integrating with other systems, and ensuring the backend is scalable, maintainable, and observable.",
"slug": "backend-engineer",
"source": "db"
},
{
"display_name": "Cybersecurity Engineer",
"id": 5,
"rationale": null,
"role_archetype": null,
"slug": "cybersecurity-engineer",
"source": "db"
},
{
"display_name": "Data Engineer",
"id": 2,
"rationale": null,
"role_archetype": null,
"slug": "data-engineer",
"source": "db"
},
{
"display_name": "ML Engineer",
"id": 3,
"rationale": null,
"role_archetype": null,
"slug": "ml-engineer",
"source": "db"
}
]
}
],
"input_skill": "Azure App Service",
"matched_via": null,
"new_alias_persisted": false,
"new_alias_text": null,
"new_skill_meta": {
"derived": {
"category": "Service",
"skill_nature": "CLOUD_SERVICE",
"sub_category": "application_hosting_service",
"typical_lifespan": "EVERGREEN",
"version_strategy": "NOT_APPLICABLE",
"volatility": "STABLE"
},
"enrichment": {
"ambiguity": {
"ambiguity_flag": false,
"confused_with": [],
"reasoning": "Azure App Service is a specific Azure hosting product with a clear name; in typical JDs it is unlikely to be mistaken for a different catalog skill."
},
"context_keywords": {
"context_keywords": [
"App Service Plan",
"deployment slots",
"custom domain",
"TLS/SSL",
"Kudu",
"Web App",
"Linux App Service",
"Windows App Service",
"Azure Functions",
"Azure DevOps",
"CI/CD",
"slot swap",
"managed identity",
"Application Insights",
"autoscale"
]
},
"maturity": {
"confidence": 0.93,
"maturity": "well_known",
"reasoning": "Broadly listed in cloud/platform job descriptions and Microsoft\u2019s core PaaS offering for web apps; strong Azure ecosystem adoption keeps it a common hiring-pipeline skill."
},
"skill_id": "azure-app-service",
"vendor_license": {
"confidence": 0.98,
"license": "proprietary",
"vendor": "Microsoft",
"year_introduced": 2015
},
"versioning": {
"current_version": null,
"version_aliases": {},
"versioned": false
}
},
"keep_log": [],
"locked_dimensions": [
{
"description": "Core services and managed offerings within major cloud provider ecosystems. Azure App Service belongs here because it is a first-party Azure hosting service used to deploy and run web applications.",
"exemplar_skills": [
"Azure App Service",
"Azure Web Apps",
"Azure App Service plans",
"Azure deployment slots",
"Azure autoscale",
"Azure Portal"
],
"in_scope": "Azure App Service, Azure compute and hosting services, Azure Portal service management, Azure resource groups, Azure App Service plans, Azure Web Apps, deployment slots, autoscale, managed certificates",
"name": "Cloud Platform Services",
"out_of_scope": "Kubernetes cluster administration, container image build pipelines, application code frameworks, database schema design, identity product configuration",
"overlap_flags": [
{
"reason": "Application structure and code organization may be relevant to apps hosted on Azure App Service, but the hosting platform itself is the primary skill.",
"with_dim_id": "app-architecture-and-dependency-injection",
"with_dim_name": null,
"with_role": "Ios engineer"
}
],
"tentative_id": "cloud-platforms"
}
],
"merge_log": [],
"placed": {
"name": "Azure App Service",
"placement_confidence": 0.92,
"primary_dimension": "cloud-platforms",
"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": "azure-app-service"
},
"relationships": {
"child_skills": [],
"parent_skills": [
"azure"
],
"related_to": [
"azure-ad",
"azure-defender-for-cloud",
"azure-resource-manager",
"azure-pipelines",
"azure-ml",
"azure-synapse-analytics",
"aws-cloudformation",
"ibm-cloud",
"aws",
"google-cloud-platform"
],
"requires": [],
"skill_id": "azure-app-service",
"suppress_on_match": []
},
"skill_id": "azure-app-service",
"split_log": [],
"typed": {
"alternatives_considered": [],
"confidence": 0.97,
"name": "Azure App Service",
"reasoning": "By the Platform vs Service rule, Azure App Service is a specific managed capability inside the Azure platform rather than a standalone user-run tool.",
"skill_id": "azure-app-service",
"subtype": "application_hosting_service",
"type": "Service"
},
"warnings": []
},
"source_tag": "llm",
"was_in_llm_skills": true
},
{
"aliases_in_db": [],
"canonical": null,
"dimensions": [
{
"dimension": {
"difficulty_hint": null,
"display_name": "Web Server Administration",
"id": null,
"rationale": "Administration and configuration of web server software used to host and route web applications. IIS belongs here because it is a Microsoft web server platform used to publish sites, manage bindings, and control request handling.",
"slug": "d_init_01",
"source": "llm"
},
"input_skill": "IIS",
"llm_role": null,
"roles_from_db": []
}
],
"input_skill": "IIS",
"matched_via": null,
"new_alias_persisted": false,
"new_alias_text": null,
"new_skill_meta": {
"derived": {
"category": "Tool",
"skill_nature": "TOOL",
"sub_category": "web_server_tool",
"typical_lifespan": "EVERGREEN",
"version_strategy": "NOT_APPLICABLE",
"volatility": "STABLE"
},
"enrichment": {
"ambiguity": {
"ambiguity_flag": false,
"confused_with": [],
"reasoning": "IIS is a well-known, specific Microsoft web server acronym in JDs; it is unlikely to be reasonably confused with another catalog skill in typical hiring context."
},
"context_keywords": {
"context_keywords": [
"ASP.NET",
"Windows Server",
"Application Pool",
"Web.config",
"HTTP.sys",
"ARR",
"URL Rewrite",
"SSL/TLS",
"bindings",
"virtual directory",
"reverse proxy",
"Windows Authentication",
"FTP Publishing",
"PowerShell",
"Event Viewer"
]
},
"maturity": {
"confidence": 0.86,
"maturity": "well_known",
"reasoning": "IIS remains a common Windows web server in enterprise JDs and Microsoft still ships/supports it in Windows Server; it\u2019s widely used alongside ASP.NET hosting rather than being sunset."
},
"skill_id": "iis",
"vendor_license": {
"confidence": 0.99,
"license": "proprietary",
"vendor": "Microsoft",
"year_introduced": 1995
},
"versioning": {
"current_version": null,
"version_aliases": {},
"versioned": false
}
},
"keep_log": [],
"locked_dimensions": [
{
"description": "Administration and configuration of web server software used to host and route web applications. IIS belongs here because it is a Microsoft web server platform used to publish sites, manage bindings, and control request handling.",
"exemplar_skills": [
"IIS",
"Microsoft IIS",
"application pools",
"site bindings",
"request filtering",
"SSL/TLS configuration"
],
"in_scope": "IIS, Microsoft IIS, website hosting, application pools, site bindings, virtual directories, request filtering, SSL/TLS configuration, reverse proxy setup, Windows web server administration",
"name": "Web Server Administration",
"out_of_scope": "Application code frameworks, frontend UI development, database administration, cloud provider services, container orchestration",
"overlap_flags": [
{
"reason": "IIS is often deployed on cloud VMs, but the skill itself is web server administration rather than cloud platform management.",
"with_dim_id": "cloud-platforms",
"with_dim_name": null,
"with_role": "Backend Engineer, Cybersecurity Engineer, Data Engineer, ML Engineer"
}
],
"tentative_id": "d_init_01"
}
],
"merge_log": [],
"placed": {
"name": "IIS",
"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": "iis"
},
"relationships": {
"child_skills": [],
"parent_skills": [],
"related_to": [
"asp-net-core",
"mvc",
"sql-server",
"openid-connect",
"microsoft-entra-id",
"azure-ad",
"ibm-cloud",
"torchserve",
"kserve",
"misp"
],
"requires": [],
"skill_id": "iis",
"suppress_on_match": []
},
"skill_id": "iis",
"split_log": [],
"typed": {
"alternatives_considered": [],
"confidence": 0.93,
"name": "IIS",
"reasoning": "IIS is software you run and operate as a server on your own infrastructure, so by the Tool vs Platform rule it is a Tool rather than a hosted platform or service.",
"skill_id": "iis",
"subtype": "web_server_tool",
"type": "Tool"
},
"warnings": []
},
"source_tag": "llm",
"was_in_llm_skills": true
},
{
"aliases_in_db": [],
"canonical": null,
"dimensions": [
{
"dimension": {
"difficulty_hint": null,
"display_name": "Agile Delivery Practices",
"id": null,
"rationale": "Agile delivery practices cover iterative planning, cross-functional collaboration, and adaptive execution used to ship software in short cycles. Agile fits here because it describes the team operating model and delivery cadence rather than a specific technical tool or framework.",
"slug": "d_init_01",
"source": "llm"
},
"input_skill": "Agile",
"llm_role": null,
"roles_from_db": []
}
],
"input_skill": "Agile",
"matched_via": null,
"new_alias_persisted": false,
"new_alias_text": null,
"new_skill_meta": {
"derived": {
"category": "Methodology",
"skill_nature": "METHODOLOGY",
"sub_category": "agile_methodology",
"typical_lifespan": "EVERGREEN",
"version_strategy": "NOT_APPLICABLE",
"volatility": "STABLE"
},
"enrichment": {
"ambiguity": {
"ambiguity_flag": false,
"confused_with": [],
"reasoning": "In JDs, \"Agile\" usually clearly refers to the software development methodology; it is not commonly mistaken for a different catalog skill."
},
"context_keywords": {
"context_keywords": [
"Scrum",
"Kanban",
"sprint planning",
"daily standup",
"backlog grooming",
"retrospective",
"user stories",
"product backlog",
"velocity",
"burndown chart",
"epics",
"story points",
"SAFe",
"iteration planning",
"continuous improvement"
]
},
"maturity": {
"confidence": 0.96,
"maturity": "well_known",
"reasoning": "Agile is a hiring-pipeline staple: job postings across software roles routinely list Agile/Scrum experience, and major employers and vendors still train/certify around it."
},
"skill_id": "agile",
"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": "Agile delivery practices cover iterative planning, cross-functional collaboration, and adaptive execution used to ship software in short cycles. Agile fits here because it describes the team operating model and delivery cadence rather than a specific technical tool or framework.",
"exemplar_skills": [
"Agile",
"Scrum",
"Kanban",
"Sprint Planning",
"Retrospectives",
"Backlog Grooming",
"User Stories"
],
"in_scope": "Agile, Scrum, Kanban, sprint planning, daily standups, retrospectives, backlog grooming, user stories, iterative delivery, cross-functional teamwork",
"name": "Agile Delivery Practices",
"out_of_scope": "Waterfall project management, detailed requirements governance, release automation, and engineering architecture decisions, which belong to separate delivery, process, or technical dimensions",
"overlap_flags": [
{
"reason": "Agile delivery often coordinates releases, but this dimension is about the team process rather than deployment mechanics.",
"with_dim_id": "deployment-rollouts-and-release-control",
"with_dim_name": null,
"with_role": "ML Engineer"
}
],
"tentative_id": "d_init_01"
}
],
"merge_log": [],
"placed": {
"name": "Agile",
"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": "agile"
},
"relationships": {
"child_skills": [],
"parent_skills": [],
"related_to": [
"mvc",
"mitre-att-ck",
"stride",
"azure-pipelines",
"github-actions",
"argo-workflows",
"fastlane"
],
"requires": [],
"skill_id": "agile",
"suppress_on_match": []
},
"skill_id": "agile",
"split_log": [],
"typed": {
"alternatives_considered": [],
"confidence": 0.99,
"name": "Agile",
"reasoning": "Agile is a way of working and organizing delivery, so by the Concept vs Methodology rule it is a Methodology rather than a Concept or Architecture.",
"skill_id": "agile",
"subtype": "agile_methodology",
"type": "Methodology"
},
"warnings": []
},
"source_tag": "llm",
"was_in_llm_skills": true
}
],
"unmatched_skills": [
"React.js",
"Cosmos DB",
"Code Review",
"Unit Testing",
"Azure App Service",
"IIS",
"Agile"
]
}
API 3 — final-role-output
{
"chosen_role": {
"display_name": "Backend Engineer",
"id": 1,
"rationale": "The primary skills required for this role align closely with the responsibilities typical of a Backend Engineer.",
"role_archetype": "A Backend Engineer designs, builds, and maintains the server-side logic and data handling that power applications and services. They focus on implementing reliable business functionality, integrating with other systems, and ensuring the backend is scalable, maintainable, and observable.",
"slug": "backend-engineer",
"source": "db"
},
"chosen_role_resolution": "in_db",
"final_input_skills": [
{
"skill": "Python",
"tag": "in_db"
},
{
"skill": "ASP.NET Core",
"tag": "in_db"
},
{
"skill": "React.js",
"tag": "new"
},
{
"skill": "SQL Server",
"tag": "in_db"
},
{
"skill": "PostgreSQL",
"tag": "in_db"
},
{
"skill": "MongoDB",
"tag": "in_db"
},
{
"skill": "Cosmos DB",
"tag": "new"
},
{
"skill": "REST",
"tag": "in_db"
},
{
"skill": "Code Review",
"tag": "new"
},
{
"skill": "Unit Testing",
"tag": "new"
},
{
"skill": "Integration Testing",
"tag": "in_db"
},
{
"skill": "Azure App Service",
"tag": "new"
},
{
"skill": "IIS",
"tag": "new"
},
{
"skill": "Agile",
"tag": "new"
}
],
"persistence": {
"items": [
{
"chosen_role_id": 1,
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Programming Languages",
"id": 1,
"rationale": "Core server-side languages used to implement backend business logic, integrations, and service internals. This is the primary coding surface for the role across application layers.",
"slug": "programming-languages",
"source": "db"
},
"dimension_id": 1,
"input_skill": "Python",
"llm_role": null,
"matched_chosen_role": true,
"outcome_line": "Existing dimension (library) \u00b7 Role\u2194dimension saved",
"role_dimension_saved": true,
"roles_from_db": [
{
"display_name": "Backend Engineer",
"id": 1,
"rationale": null,
"role_archetype": "A Backend Engineer designs, builds, and maintains the server-side logic and data handling that power applications and services. They focus on implementing reliable business functionality, integrating with other systems, and ensuring the backend is scalable, maintainable, and observable.",
"slug": "backend-engineer",
"source": "db"
}
],
"skill_dimension_saved": true,
"skill_id": 5,
"skill_tag": "in_db",
"skipped_reason": null
},
{
"chosen_role_id": 1,
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Programming Languages and Scripting",
"id": 59,
"rationale": "Languages used to write security automation, analysis scripts, detection logic, and remediation helpers. This is the primary implementation surface for a cybersecurity engineer across tooling and response workflows.",
"slug": "programming-languages-and-scripting",
"source": "db"
},
"dimension_id": 59,
"input_skill": "Python",
"llm_role": null,
"matched_chosen_role": false,
"outcome_line": "Existing dimension (library) \u00b7 Role\u2194dimension skipped (dimension not under chosen role)",
"role_dimension_saved": false,
"roles_from_db": [
{
"display_name": "Cybersecurity Engineer",
"id": 5,
"rationale": null,
"role_archetype": null,
"slug": "cybersecurity-engineer",
"source": "db"
}
],
"skill_dimension_saved": true,
"skill_id": 5,
"skill_tag": "in_db",
"skipped_reason": null
},
{
"chosen_role_id": 1,
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Programming Languages for Data Work",
"id": 21,
"rationale": "Languages used to implement data pipelines, transformations, and operational glue. This is the primary coding surface for building ingestion, enrichment, and automation logic in data engineering.",
"slug": "programming-languages-for-data-work",
"source": "db"
},
"dimension_id": 21,
"input_skill": "Python",
"llm_role": null,
"matched_chosen_role": false,
"outcome_line": "Existing dimension (library) \u00b7 Role\u2194dimension skipped (dimension not under chosen role)",
"role_dimension_saved": false,
"roles_from_db": [
{
"display_name": "Data Engineer",
"id": 2,
"rationale": null,
"role_archetype": null,
"slug": "data-engineer",
"source": "db"
}
],
"skill_dimension_saved": true,
"skill_id": 5,
"skill_tag": "in_db",
"skipped_reason": null
},
{
"chosen_role_id": 1,
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Programming Languages for ML Systems",
"id": 39,
"rationale": "Languages used to build training code, inference services, evaluation jobs, and ML glue code. This is the primary implementation surface for ML engineers across experimentation and productionization.",
"slug": "programming-languages-for-ml-systems",
"source": "db"
},
"dimension_id": 39,
"input_skill": "Python",
"llm_role": null,
"matched_chosen_role": false,
"outcome_line": "Existing dimension (library) \u00b7 Role\u2194dimension skipped (dimension not under chosen role)",
"role_dimension_saved": false,
"roles_from_db": [
{
"display_name": "ML Engineer",
"id": 3,
"rationale": null,
"role_archetype": null,
"slug": "ml-engineer",
"source": "db"
}
],
"skill_dimension_saved": true,
"skill_id": 5,
"skill_tag": "in_db",
"skipped_reason": null
},
{
"chosen_role_id": 1,
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Web Application Frameworks",
"id": 2,
"rationale": "Server frameworks and runtimes used to build HTTP services, controllers, middleware, and request pipelines. These frameworks shape how backend endpoints are structured and delivered.",
"slug": "web-application-frameworks",
"source": "db"
},
"dimension_id": 2,
"input_skill": "ASP.NET Core",
"llm_role": null,
"matched_chosen_role": true,
"outcome_line": "Existing dimension (library) \u00b7 Role\u2194dimension saved",
"role_dimension_saved": true,
"roles_from_db": [
{
"display_name": "Backend Engineer",
"id": 1,
"rationale": null,
"role_archetype": "A Backend Engineer designs, builds, and maintains the server-side logic and data handling that power applications and services. They focus on implementing reliable business functionality, integrating with other systems, and ensuring the backend is scalable, maintainable, and observable.",
"slug": "backend-engineer",
"source": "db"
}
],
"skill_dimension_saved": true,
"skill_id": 7,
"skill_tag": "in_db",
"skipped_reason": null
},
{
"chosen_role_id": 1,
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Relational Database Design",
"id": 4,
"rationale": "Modeling and operating relational persistence for backend services. Includes schema design, normalization, indexing, transactions, and query tuning for operational data stores.",
"slug": "relational-database-design",
"source": "db"
},
"dimension_id": 4,
"input_skill": "SQL Server",
"llm_role": null,
"matched_chosen_role": true,
"outcome_line": "Existing dimension (library) \u00b7 Role\u2194dimension saved",
"role_dimension_saved": true,
"roles_from_db": [
{
"display_name": "Backend Engineer",
"id": 1,
"rationale": null,
"role_archetype": "A Backend Engineer designs, builds, and maintains the server-side logic and data handling that power applications and services. They focus on implementing reliable business functionality, integrating with other systems, and ensuring the backend is scalable, maintainable, and observable.",
"slug": "backend-engineer",
"source": "db"
}
],
"skill_dimension_saved": true,
"skill_id": 18,
"skill_tag": "in_db",
"skipped_reason": null
},
{
"chosen_role_id": 1,
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Relational Database Design",
"id": 4,
"rationale": "Modeling and operating relational persistence for backend services. Includes schema design, normalization, indexing, transactions, and query tuning for operational data stores.",
"slug": "relational-database-design",
"source": "db"
},
"dimension_id": 4,
"input_skill": "PostgreSQL",
"llm_role": null,
"matched_chosen_role": true,
"outcome_line": "Existing dimension (library) \u00b7 Role\u2194dimension saved",
"role_dimension_saved": true,
"roles_from_db": [
{
"display_name": "Backend Engineer",
"id": 1,
"rationale": null,
"role_archetype": "A Backend Engineer designs, builds, and maintains the server-side logic and data handling that power applications and services. They focus on implementing reliable business functionality, integrating with other systems, and ensuring the backend is scalable, maintainable, and observable.",
"slug": "backend-engineer",
"source": "db"
}
],
"skill_dimension_saved": true,
"skill_id": 16,
"skill_tag": "in_db",
"skipped_reason": null
},
{
"chosen_role_id": 1,
"dimension": {
"difficulty_hint": "well_known",
"display_name": "NoSQL Databases",
"id": 19,
"rationale": "Models and manages data using non-relational database systems.",
"slug": "nosql-databases",
"source": "db"
},
"dimension_id": 19,
"input_skill": "MongoDB",
"llm_role": null,
"matched_chosen_role": true,
"outcome_line": "Existing dimension (library) \u00b7 Role\u2194dimension saved",
"role_dimension_saved": true,
"roles_from_db": [
{
"display_name": "Backend Engineer",
"id": 1,
"rationale": null,
"role_archetype": "A Backend Engineer designs, builds, and maintains the server-side logic and data handling that power applications and services. They focus on implementing reliable business functionality, integrating with other systems, and ensuring the backend is scalable, maintainable, and observable.",
"slug": "backend-engineer",
"source": "db"
}
],
"skill_dimension_saved": true,
"skill_id": 91,
"skill_tag": "in_db",
"skipped_reason": null
},
{
"chosen_role_id": 1,
"dimension": {
"difficulty_hint": "well_known",
"display_name": "API Design and Contracts",
"id": 3,
"rationale": "Designing and maintaining service interfaces that other systems consume. Covers endpoint shape, payload modeling, versioning, pagination, idempotency, and compatibility rules.",
"slug": "api-design-and-contracts",
"source": "db"
},
"dimension_id": 3,
"input_skill": "REST",
"llm_role": null,
"matched_chosen_role": true,
"outcome_line": "Existing dimension (library) \u00b7 Role\u2194dimension saved",
"role_dimension_saved": true,
"roles_from_db": [
{
"display_name": "Backend Engineer",
"id": 1,
"rationale": null,
"role_archetype": "A Backend Engineer designs, builds, and maintains the server-side logic and data handling that power applications and services. They focus on implementing reliable business functionality, integrating with other systems, and ensuring the backend is scalable, maintainable, and observable.",
"slug": "backend-engineer",
"source": "db"
}
],
"skill_dimension_saved": true,
"skill_id": 11,
"skill_tag": "in_db",
"skipped_reason": null
},
{
"chosen_role_id": 1,
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Testing and Quality Assurance",
"id": 12,
"rationale": "Backend-specific test strategies used to validate service behavior and integration points. Covers automated test layers, contract checks, fixtures, and regression prevention.",
"slug": "testing-and-quality-assurance",
"source": "db"
},
"dimension_id": 12,
"input_skill": "Integration Testing",
"llm_role": null,
"matched_chosen_role": true,
"outcome_line": "Existing dimension (library) \u00b7 Role\u2194dimension saved",
"role_dimension_saved": true,
"roles_from_db": [
{
"display_name": "Backend Engineer",
"id": 1,
"rationale": null,
"role_archetype": "A Backend Engineer designs, builds, and maintains the server-side logic and data handling that power applications and services. They focus on implementing reliable business functionality, integrating with other systems, and ensuring the backend is scalable, maintainable, and observable.",
"slug": "backend-engineer",
"source": "db"
}
],
"skill_dimension_saved": true,
"skill_id": 56,
"skill_tag": "in_db",
"skipped_reason": null
},
{
"chosen_role_id": 1,
"dimension": {
"difficulty_hint": null,
"display_name": "React Frontend Development",
"id": null,
"rationale": "Building interactive web user interfaces with React.js, including component composition, state management, hooks, and rendering patterns. React.js belongs here because it is a core library for client-side UI development in modern web applications.",
"slug": "d_init_01",
"source": "llm"
},
"dimension_id": 96,
"input_skill": "React.js",
"llm_role": null,
"matched_chosen_role": false,
"outcome_line": "New skill saved \u00b7 New dimension saved (reconciliation separate) \u00b7 Role\u2194dimension skipped (dimension not under chosen role)",
"role_dimension_saved": false,
"roles_from_db": [],
"skill_dimension_saved": true,
"skill_id": 514,
"skill_tag": "in_db",
"skipped_reason": null
},
{
"chosen_role_id": 1,
"dimension": {
"difficulty_hint": "well_known",
"display_name": "NoSQL Databases",
"id": 19,
"rationale": "Models and manages data using non-relational database systems.",
"slug": "nosql-databases",
"source": "db"
},
"dimension_id": 19,
"input_skill": "Cosmos DB",
"llm_role": null,
"matched_chosen_role": true,
"outcome_line": "New skill saved \u00b7 Existing dimension (library) \u00b7 Role\u2194dimension saved",
"role_dimension_saved": true,
"roles_from_db": [
{
"display_name": "Backend Engineer",
"id": 1,
"rationale": null,
"role_archetype": "A Backend Engineer designs, builds, and maintains the server-side logic and data handling that power applications and services. They focus on implementing reliable business functionality, integrating with other systems, and ensuring the backend is scalable, maintainable, and observable.",
"slug": "backend-engineer",
"source": "db"
}
],
"skill_dimension_saved": true,
"skill_id": 515,
"skill_tag": "in_db",
"skipped_reason": null
},
{
"chosen_role_id": 1,
"dimension": {
"difficulty_hint": null,
"display_name": "Code Review Practices",
"id": null,
"rationale": "Reviewing code changes for correctness, maintainability, security, and alignment with team standards. This skill belongs here because it is a core collaborative engineering practice rather than a language, framework, or platform skill.",
"slug": "d_init_01",
"source": "llm"
},
"dimension_id": 96,
"input_skill": "Code Review",
"llm_role": null,
"matched_chosen_role": false,
"outcome_line": "New skill saved \u00b7 Existing dimension (library) \u00b7 Role\u2194dimension skipped (dimension not under chosen role)",
"role_dimension_saved": false,
"roles_from_db": [],
"skill_dimension_saved": true,
"skill_id": 516,
"skill_tag": "in_db",
"skipped_reason": null
},
{
"chosen_role_id": 1,
"dimension": {
"difficulty_hint": null,
"display_name": "Unit Testing Practices",
"id": null,
"rationale": "Techniques for writing isolated, repeatable tests that verify individual functions, classes, and modules. This skill belongs here because unit testing is the core practice of validating small code units before integration or end-to-end testing.",
"slug": "d_init_01",
"source": "llm"
},
"dimension_id": 96,
"input_skill": "Unit Testing",
"llm_role": null,
"matched_chosen_role": false,
"outcome_line": "New skill saved \u00b7 Existing dimension (library) \u00b7 Role\u2194dimension skipped (dimension not under chosen role)",
"role_dimension_saved": false,
"roles_from_db": [],
"skill_dimension_saved": true,
"skill_id": 517,
"skill_tag": "in_db",
"skipped_reason": null
},
{
"chosen_role_id": 1,
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Cloud Platforms",
"id": 20,
"rationale": "Proficiency in major cloud service provider platforms and their core services.",
"slug": "cloud-platforms",
"source": "db"
},
"dimension_id": 20,
"input_skill": "Azure App Service",
"llm_role": null,
"matched_chosen_role": true,
"outcome_line": "New skill saved \u00b7 Existing dimension (library) \u00b7 Role\u2194dimension saved",
"role_dimension_saved": true,
"roles_from_db": [
{
"display_name": "Backend Engineer",
"id": 1,
"rationale": null,
"role_archetype": "A Backend Engineer designs, builds, and maintains the server-side logic and data handling that power applications and services. They focus on implementing reliable business functionality, integrating with other systems, and ensuring the backend is scalable, maintainable, and observable.",
"slug": "backend-engineer",
"source": "db"
},
{
"display_name": "Cybersecurity Engineer",
"id": 5,
"rationale": null,
"role_archetype": null,
"slug": "cybersecurity-engineer",
"source": "db"
},
{
"display_name": "Data Engineer",
"id": 2,
"rationale": null,
"role_archetype": null,
"slug": "data-engineer",
"source": "db"
},
{
"display_name": "ML Engineer",
"id": 3,
"rationale": null,
"role_archetype": null,
"slug": "ml-engineer",
"source": "db"
}
],
"skill_dimension_saved": true,
"skill_id": 518,
"skill_tag": "in_db",
"skipped_reason": null
},
{
"chosen_role_id": 1,
"dimension": {
"difficulty_hint": null,
"display_name": "Web Server Administration",
"id": null,
"rationale": "Administration and configuration of web server software used to host and route web applications. IIS belongs here because it is a Microsoft web server platform used to publish sites, manage bindings, and control request handling.",
"slug": "d_init_01",
"source": "llm"
},
"dimension_id": 96,
"input_skill": "IIS",
"llm_role": null,
"matched_chosen_role": false,
"outcome_line": "New skill saved \u00b7 Existing dimension (library) \u00b7 Role\u2194dimension skipped (dimension not under chosen role)",
"role_dimension_saved": false,
"roles_from_db": [],
"skill_dimension_saved": true,
"skill_id": 519,
"skill_tag": "in_db",
"skipped_reason": null
},
{
"chosen_role_id": 1,
"dimension": {
"difficulty_hint": null,
"display_name": "Agile Delivery Practices",
"id": null,
"rationale": "Agile delivery practices cover iterative planning, cross-functional collaboration, and adaptive execution used to ship software in short cycles. Agile fits here because it describes the team operating model and delivery cadence rather than a specific technical tool or framework.",
"slug": "d_init_01",
"source": "llm"
},
"dimension_id": 96,
"input_skill": "Agile",
"llm_role": null,
"matched_chosen_role": false,
"outcome_line": "New skill saved \u00b7 Existing dimension (library) \u00b7 Role\u2194dimension skipped (dimension not under chosen role)",
"role_dimension_saved": false,
"roles_from_db": [],
"skill_dimension_saved": true,
"skill_id": 520,
"skill_tag": "in_db",
"skipped_reason": null
}
],
"new_skills_created": 7,
"role_dimension_saved": 0,
"skill_dimension_saved": 7,
"skipped": 0
},
"planner_output": null,
"run_id": "39d79165-fae2-4b74-8eb1-d9ee388fdb2b"
}
LLM Calls
Every model call made for this run, in pipeline order. Click a card to see the model's response.