Pipeline run
b2f2b7dd-70e0-4efc-aa08-f3e38c9cf04f
Client output enrichment
v2 Skill cluster · Nature of work · AI index · Tech stack maturity · Evidence · KRA descriptionvocab breakdown (legacy)
Signals
Post-classification
Captured for admin review
1 POST /skills/extract-from-jd
2 POST /skills/extract-details
3 POST /skills/final-role-output
Backend Developer
→.NET Backend Developer
sub-role · 0.99 domain · Software Engineering CASE DOMAINslug: backend-engineer · id: 1 · source: db · sub-role slug: dotnet-backend-developer
Domain=Software Engineering → sub-role dotnet-backend-developer; The JD is centered on C#/.NET backend and application development with APIs, SQL Server, SignalR, and deployment tooling, which best matches Backend Developer.
Matched skills
Matched dimensions
Matched KRAs
Resolution:
in_db
— role exists in library; skill↔dim and role↔dim links saved when applicable.
Job description
Overview WELCOME TO SITA We're the team that keeps airports moving, airlines flying smoothly, and borders open. Our tech and communication innovations are the secret behind the success of the world's air travel industry. You'll find us at 95% of international hubs. We partner closely with over 2,500 transportation and government clients, each with their own unique needs and challenges. Our goal is to find fresh solutions and cutting-edge tech to make their operations run like clockwork. Want to be a part of something big? Are you ready to love your job? The adventure begins right here, with you, at SITA. About The Role & Team Designs develop maintains and supports functionality and features in modules within an application or system using existing and emerging technology platforms. What You Will Do You will have the opportunity to work on some, or all, of the following: • Design, develop, and maintain high-performance Windows and Web applications using C#, WinForms, ASP.NET Core, and MVC. • Build and integrate RESTful APIs using ASP.NET Web API. • Develop and optimize SQL Server databases, stored procedures, and queries. • Implement real-time communication features using SignalR. • Apply Dependency Injection and SOLID principles to ensure scalable and maintainable code. • Troubleshoot and resolve software defects and production issues. • Collaborate with cross-functional teams to define and implement project requirements Qualifications EXPERIENCE • This position requires a highly skilled and self-motivated Senior .NET Developer with extensive hands-on experience in C#, Windows Forms, ASP.NET Core, MVC, and Web API. • The ideal candidate should possess significant exposure to SQL Server, SignalR, Dependency Injection, and Azure DevOps pipelines, as well as experience in creating MSI packages for application deployment. • This role demands an individual who can operate autonomously and work collaboratively across teams. What We Offer We're all about diversity. We operate in 200 countries and speak 60 different languages and cultures. We're really proud of our inclusive environment. Our offices are comfortable and fun places to work, and we make sure you get to work from home too. Find out what it's like to join our team and take a step closer to your best life ever. 🏡 Flex Week: Work from home up to 2 days/week (depending on your team's needs) ⏰ Flex Day: Make your workday suit your life and plans. 🌎 Flex-Location: Take up to 30 days a year to work from any location in the world. 🌿 Employee Wellbeing: We have got you covered with our Employee Assistance Program (EAP), for you and your dependents 24/7, 365 days/year. We also offer Champion Health - a personalized platform that supports a range of wellbeing needs. 🚀 Professional Development: Level up your skills with our training platforms, including LinkedIn Learning! 🙌 Competitive Benefits: Competitive benefits that make sense with both your local market and employment status. SITA is an Equal Opportunity Employer. We value a diverse workforce. In support of our Employment Equity Program, we encourage women, aboriginal people, members of visible minorities, and/or persons with disabilities to apply and self-identify in the application process.
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
- C# (CANONICAL) primary
- C (CANONICAL)
- C# 1 (VERSION)
- C# 10 (VERSION)
- C# 11 (VERSION)
- C# 12 (VERSION)
- C# 13 (VERSION)
- C# 14 (VERSION)
- C# 2 (VERSION)
- C# 3 (VERSION)
- C# 4 (VERSION)
- C# 5 (VERSION)
- C# 6 (VERSION)
- C# 7 (VERSION)
- C# 8 (VERSION)
- C# 9 (VERSION)
- C# latest (VERSION)
- C#1 (VERSION)
- C#10 (VERSION)
- C#11 (VERSION)
- C#12 (VERSION)
- C#2 (VERSION)
- C#3 (VERSION)
- C#4 (VERSION)
- C#5 (VERSION)
- C#6 (VERSION)
- C#7 (VERSION)
- C#8 (VERSION)
- C#9 (VERSION)
- C++ (CANONICAL)
- C++03 (VERSION)
- C++11 (VERSION)
- C++14 (VERSION)
- C++17 (VERSION)
- C++20 (VERSION)
- C++23 (VERSION)
- C++26 (VERSION)
- C++98 (VERSION)
- c sharp (VERSION)
- c# (VERSION)
- cpp03 (VERSION)
- cpp11 (VERSION)
- cpp14 (VERSION)
- cpp17 (VERSION)
- cpp20 (VERSION)
- cpp23 (VERSION)
- cpp26 (VERSION)
- cpp98 (VERSION)
- csharp (VERSION)
- modern C++ (VERSION)
Context tags (catalog)
Stored enrichment (catalog DB)
- Category
- Language
- Sub-category
- Programming Language
- Vendor
- Microsoft
- License
- mit
- Year introduced
- 2000
- Confidence
- 0.99
- Version strategy
- SEPARATE_ENTITY
- Version tag
- latest
Maturity reasoning: C# is a mainstream hiring staple with high JD volume across .NET, Azure, and enterprise roles; Microsoft continues active platform investment in .NET, reinforcing broad adoption.
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)
-
C# and .NET Languages Catalog dimension db id 362
Library dimension (catalog)
Roles linked in library: .NET Backend Developer
-
Cross-Platform App Languages Catalog dimension db id 167
Library dimension (catalog)
Roles linked in library: Hybrid Mobile Developer
-
Programming Languages Catalog dimension db id 1
Library dimension (catalog)
Roles linked in library: Backend Developer, Fullstack Developer
-
Programming Languages for ML Systems Catalog dimension db id 39
Library dimension (catalog)
Roles linked in library: ML Engineer, MLOps Engineer
-
Programming Languages for XR Catalog dimension db id 97
Library dimension (catalog)
Roles linked in library: AR/VR Engineer
-
React Frontend Development Catalog dimension db id 96
Library dimension (catalog)
-
Sitecore Development Languages Catalog dimension db id 438
Library dimension (catalog)
Roles linked in library: Sitecore Dev
-
Video Codec Languages and DSLs Catalog dimension db id 225
Library dimension (catalog)
Roles linked in library: Video Codec Engineer
API 3 link attempts (this skill)
| Dimension | Skill↔dim | Role↔dim | Outcome |
|---|---|---|---|
|
C# and .NET Languages
c-and-net-languages
|
✓ | — | Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role) |
|
Cross-Platform App Languages
cross-platform-app-languages
|
✓ | — | Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role) |
|
Programming Languages
programming-languages
|
✓ | ✓ | Existing dimension (library) · Role↔dimension saved |
|
Programming Languages for ML Systems
programming-languages-for-ml-systems
|
✓ | — | Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role) |
|
Programming Languages for XR
programming-languages-for-xr
|
✓ | — | Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role) |
|
React Frontend Development
d_init_01
|
✓ | — | Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role) |
|
Sitecore Development Languages
sitecore-development-languages
|
✓ | — | Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role) |
|
Video Codec Languages and DSLs
video-codec-languages-and-dsls
|
✓ | — | Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role) |
Skill enrichment (orchestrator / LLM)
No Stage 7 enrichment blob on this skill (orchestrator skipped enrichment).
- Category
- Web Frameworks
- Sub-category
- general
- Skill nature
- TOOL
- Volatility
- MEDIUM
- Typical lifespan
- MULTI_YEAR
- Version strategy
- UNVERSIONED
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)
-
ASP.NET Core Web Frameworks Catalog dimension db id 363
Library dimension (catalog)
Roles linked in library: .NET Backend Developer
-
Web Application Frameworks Catalog dimension db id 2
Library dimension (catalog)
Roles linked in library: Backend Developer, Fullstack Developer, Java Backend Developer, Node.js Backend Developer, PHP Backend Developer, Python Backend Developer
API 3 link attempts (this skill)
| Dimension | Skill↔dim | Role↔dim | Outcome |
|---|---|---|---|
|
ASP.NET Core Web Frameworks
asp-net-core-web-frameworks
|
✓ | — | Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role) |
|
Web Application Frameworks
web-application-frameworks
|
✓ | ✓ | Existing dimension (library) · Role↔dimension saved |
Aliases — catalog
- MVC (CANONICAL) primary
Context tags (catalog)
Stored enrichment (catalog DB)
- Category
- Architecture
- Sub-category
- Model View Controller
- Year introduced
- 1979
- Confidence
- 0.93
- Version strategy
- NOT_APPLICABLE
Maturity reasoning: MVC remains a standard web/app architecture in many job descriptions and frameworks (e.g., ASP.NET MVC, Spring MVC, Rails), with no vendor sunset or replacement making it obsolete.
Skill profile (library / DB)
- Skill nature
- PATTERN
- Volatility
- STABLE
- Typical lifespan
- EVERGREEN
- Category id
- 1
- Sub-category id
- 2462
- Extractable
- True
- Also category
- False
Dimensions (API 2 worklist)
-
ASP.NET Core Web Frameworks Catalog dimension db id 363
Library dimension (catalog)
Roles linked in library: .NET Backend Developer
-
App Architecture and Dependency Injection Catalog dimension db id 94
Library dimension (catalog)
Roles linked in library: Android Developer, iOS Developer
-
Application Architecture and Code Organization Catalog dimension db id 220
Library dimension (catalog)
Roles linked in library: Fullstack Developer
-
Native Mobile App Architecture and Dependency Injection Catalog dimension db id 273
Library dimension (catalog)
Roles linked in library: Native Mobile Developer
API 3 link attempts (this skill)
| Dimension | Skill↔dim | Role↔dim | Outcome |
|---|---|---|---|
|
ASP.NET Core Web Frameworks
asp-net-core-web-frameworks
|
✓ | — | Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role) |
|
App Architecture and Dependency Injection
app-architecture-and-dependency-injection
|
✓ | — | Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role) |
|
Application Architecture and Code Organization
application-architecture-and-code-organization
|
✓ | — | Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role) |
|
Native Mobile App Architecture and Dependency Injection
native-mobile-app-architecture-and-dependency-injection
|
✓ | — | Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role) |
Aliases — catalog
- REST (CANONICAL) primary
Context tags (catalog)
Stored enrichment (catalog DB)
- Category
- Concept
- Sub-category
- Api Architecture Style
- Year introduced
- 2000
- Confidence
- 0.88
- Version strategy
- NOT_APPLICABLE
Maturity reasoning: REST is a default API architecture in many job descriptions and is widely supported by major vendors/frameworks; OpenAPI and RESTful endpoints remain standard in hiring pipelines.
Skill profile (library / DB)
- Skill nature
- CONCEPT
- Volatility
- STABLE
- Typical lifespan
- EVERGREEN
- Category id
- 2
- Sub-category id
- 2122
- Extractable
- True
- Also category
- False
Dimensions (API 2 worklist)
-
API Design and Contracts Catalog dimension db id 3
Library dimension (catalog)
Roles linked in library: Backend Developer, Fullstack Developer
-
API Interface and Contract Design Catalog dimension db id 289
Library dimension (catalog)
Roles linked in library: .NET Backend Developer, Go Backend Developer, Kotlin Backend Developer, Node.js Backend Developer, PHP Backend Developer, Python Backend Developer, Ruby Backend Developer, Scala Backend Developer
-
Integration Protocols & Standards Catalog dimension db id 271
Library dimension (catalog)
Roles linked in library: Pega Developer
-
Standards & Protocols Compliance Catalog dimension db id 452
Library dimension (catalog)
Roles linked in library: Sitecore Dev
API 3 link attempts (this skill)
| Dimension | Skill↔dim | Role↔dim | Outcome |
|---|---|---|---|
|
API Design and Contracts
api-design-and-contracts
|
✓ | ✓ | Existing dimension (library) · Role↔dimension saved |
|
API Interface and Contract Design
api-interface-and-contract-design
|
✓ | — | Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role) |
|
Integration Protocols & Standards
integration-protocols-standards
|
✓ | — | Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role) |
|
Standards & Protocols Compliance
standards-protocols-compliance
|
✓ | — | Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role) |
Skill enrichment (orchestrator / LLM)
No Stage 7 enrichment blob on this skill (orchestrator skipped enrichment).
- Category
- Web Frameworks
- Sub-category
- general
- Skill nature
- TOOL
- Volatility
- MEDIUM
- Typical lifespan
- MULTI_YEAR
- Version strategy
- UNVERSIONED
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: .NET Backend Developer, Backend Developer, Kotlin Backend Developer, Node.js Backend Developer, Python Backend Developer, Ruby Backend Developer, Scala Backend Developer
API 3 link attempts (this skill)
| Dimension | Skill↔dim | Role↔dim | Outcome |
|---|---|---|---|
|
Relational Database Design
relational-database-design
|
✓ | ✓ | Existing dimension (library) · Role↔dimension saved |
Skill enrichment (orchestrator / LLM)
No Stage 7 enrichment blob on this skill (orchestrator skipped enrichment).
- Category
- Web Frameworks
- Sub-category
- general
- Skill nature
- TOOL
- Volatility
- MEDIUM
- Typical lifespan
- MULTI_YEAR
- Version strategy
- UNVERSIONED
Aliases — catalog
- dependency injection (CANONICAL) primary
- Dependency Injection (CANONICAL)
- Dependency injection (CANONICAL)
Context tags (catalog)
Stored enrichment (catalog DB)
- Category
- Concept
- Sub-category
- Dependency Injection
- Confidence
- 0.95
- Version strategy
- NOT_APPLICABLE
Maturity reasoning: Common in JDs for Java/.NET/TypeScript roles and supported by major frameworks like Spring, ASP.NET Core, and Angular; it’s a standard architectural pattern rather than a niche tool.
Skill profile (library / DB)
- Skill nature
- CONCEPT
- Volatility
- STABLE
- Typical lifespan
- EVERGREEN
- Category id
- 2
- Sub-category id
- 2482
- Extractable
- True
- Also category
- False
Dimensions (API 2 worklist)
-
Angular Component Model and Templates Catalog dimension db id 303
Library dimension (catalog)
Roles linked in library: Angular Frontend Developer
-
App Architecture and Dependency Injection Catalog dimension db id 94
Library dimension (catalog)
Roles linked in library: Android Developer, iOS Developer
-
Application Architecture Patterns Catalog dimension db id 293
Library dimension (catalog)
Roles linked in library: .NET Backend Developer, Python Backend Developer
-
Application Architecture and Code Organization Catalog dimension db id 220
Library dimension (catalog)
Roles linked in library: Fullstack Developer
-
Backend Application Architecture and Code Organization Catalog dimension db id 366
Library dimension (catalog)
Roles linked in library: Go Backend Developer
-
Flutter App Architecture Catalog dimension db id 316
Library dimension (catalog)
Roles linked in library: Flutter Developer
-
Ionic App Architecture Catalog dimension db id 384
Library dimension (catalog)
Roles linked in library: Ionic Developer
-
Mobile Architecture and Code Organization Catalog dimension db id 170
Library dimension (catalog)
Roles linked in library: Hybrid Mobile Developer, React Native Developer
-
Native Mobile App Architecture and Dependency Injection Catalog dimension db id 273
Library dimension (catalog)
Roles linked in library: Native Mobile Developer
-
PHP and Magento Extension Points Catalog dimension db id 391
Library dimension (catalog)
Roles linked in library: Magento Dev
-
Service Architecture and Design Patterns Catalog dimension db id 18
Library dimension (catalog)
Roles linked in library: Backend Developer, Java Backend Developer, Kotlin Backend Developer, Node.js Backend Developer, PHP Backend Developer, Ruby Backend Developer, Scala Backend Developer
API 3 link attempts (this skill)
| Dimension | Skill↔dim | Role↔dim | Outcome |
|---|---|---|---|
|
Angular Component Model and Templates
angular-component-model-and-templates
|
✓ | — | Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role) |
|
App Architecture and Dependency Injection
app-architecture-and-dependency-injection
|
✓ | — | Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role) |
|
Application Architecture Patterns
application-architecture-patterns
|
✓ | — | Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role) |
|
Application Architecture and Code Organization
application-architecture-and-code-organization
|
✓ | — | Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role) |
|
Backend Application Architecture and Code Organization
backend-application-architecture-and-code-organization
|
✓ | — | Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role) |
|
Flutter App Architecture
flutter-app-architecture
|
✓ | — | Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role) |
|
Ionic App Architecture
ionic-app-architecture
|
✓ | — | Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role) |
|
Mobile Architecture and Code Organization
mobile-architecture-and-code-organization
|
✓ | — | Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role) |
|
Native Mobile App Architecture and Dependency Injection
native-mobile-app-architecture-and-dependency-injection
|
✓ | — | Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role) |
|
PHP and Magento Extension Points
php-and-magento-extension-points
|
✓ | — | Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role) |
|
Service Architecture and Design Patterns
service-architecture-and-design-patterns
|
✓ | ✓ | Existing dimension (library) · Role↔dimension saved |
Aliases — catalog
- SOLID (CANONICAL) primary
- Solid (CANONICAL)
Context tags (catalog)
Stored enrichment (catalog DB)
- Category
- Concept
- Sub-category
- Object Oriented Design Principles
- Vendor
- SolidJS
- License
- mit
- Year introduced
- 2018
- Confidence
- 0.95
- Version strategy
- NOT_APPLICABLE
Maturity reasoning: SOLID is a standard OOP design-principles topic in many software engineering JDs and interview loops; it’s widely taught and referenced in code reviews, though not a standalone tool.
Skill profile (library / DB)
- Skill nature
- CONCEPT
- Volatility
- STABLE
- Typical lifespan
- EVERGREEN
- Category id
- 2
- Sub-category id
- 2976
- Extractable
- True
- Also category
- False
Dimensions (API 2 worklist)
-
Application Architecture Patterns Catalog dimension db id 293
Library dimension (catalog)
Roles linked in library: .NET Backend Developer, Python Backend Developer
-
Service Architecture and Design Patterns Catalog dimension db id 18
Library dimension (catalog)
Roles linked in library: Backend Developer, Java Backend Developer, Kotlin Backend Developer, Node.js Backend Developer, PHP Backend Developer, Ruby Backend Developer, Scala Backend Developer
-
UI Frameworks and Rendering Catalog dimension db id 115
Library dimension (catalog)
Roles linked in library: Frontend Developer, Fullstack Developer, Hybrid Mobile Developer, Ionic Developer, Web Developer
API 3 link attempts (this skill)
| Dimension | Skill↔dim | Role↔dim | Outcome |
|---|---|---|---|
|
Application Architecture Patterns
application-architecture-patterns
|
✓ | — | Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role) |
|
Service Architecture and Design Patterns
service-architecture-and-design-patterns
|
✓ | ✓ | Existing dimension (library) · Role↔dimension saved |
|
UI Frameworks and Rendering
ui-frameworks-and-rendering
|
✓ | — | Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role) |
Skill enrichment (orchestrator / LLM)
No Stage 7 enrichment blob on this skill (orchestrator skipped enrichment).
- Category
- Web Frameworks
- Sub-category
- general
- Skill nature
- TOOL
- Volatility
- MEDIUM
- Typical lifespan
- MULTI_YEAR
- Version strategy
- UNVERSIONED
Aliases — catalog
- Azure DevOps (CANONICAL)
Context tags (catalog)
Stored enrichment (catalog DB)
- Category
- Platform
- Sub-category
- Devops Platform
- Vendor
- Microsoft
- License
- proprietary
- Year introduced
- 2018
- Confidence
- 0.93
- Version strategy
- NOT_APPLICABLE
Maturity reasoning: Azure DevOps appears in many enterprise job descriptions for CI/CD, boards, and repos, and Microsoft continues active product support and updates; it remains a common hiring-pipeline skill alongside GitHub Actions/Jenkins.
Skill profile (library / DB)
- Skill nature
- PLATFORM
- Volatility
- STABLE
- Typical lifespan
- EVERGREEN
- Category id
- 9
- Sub-category id
- 170
- Extractable
- True
- Also category
- False
Dimensions (API 2 worklist)
-
CI/CD Pipeline Platforms Catalog dimension db id 150
Library dimension (catalog)
Roles linked in library: DevOps Engineer
API 3 link attempts (this skill)
| Dimension | Skill↔dim | Role↔dim | Outcome |
|---|---|---|---|
|
CI/CD Pipeline Platforms
ci-cd-pipeline-platforms
|
✓ | — | Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role) |
Skill enrichment (orchestrator / LLM)
No Stage 7 enrichment blob on this skill (orchestrator skipped enrichment).
- Category
- Deployment Tools
- Sub-category
- general
- Skill nature
- TOOL
- Volatility
- MEDIUM
- Typical lifespan
- MULTI_YEAR
- Version strategy
- UNVERSIONED
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 |
|---|---|---|---|---|---|---|
| C# | in_db |
C# and .NET Languages
c-and-net-languages
|
✓ | — | Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role) | |
| C# | in_db |
Cross-Platform App Languages
cross-platform-app-languages
|
✓ | — | Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role) | |
| C# | in_db |
Programming Languages
programming-languages
|
✓ | ✓ | Existing dimension (library) · Role↔dimension saved | |
| C# | in_db |
Programming Languages for ML Systems
programming-languages-for-ml-systems
|
✓ | — | Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role) | |
| C# | in_db |
Programming Languages for XR
programming-languages-for-xr
|
✓ | — | Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role) | |
| C# | in_db |
React Frontend Development
d_init_01
|
✓ | — | Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role) | |
| C# | in_db |
Sitecore Development Languages
sitecore-development-languages
|
✓ | — | Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role) | |
| C# | in_db |
Video Codec Languages and DSLs
video-codec-languages-and-dsls
|
✓ | — | Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role) | |
| ASP.NET Core | in_db |
ASP.NET Core Web Frameworks
asp-net-core-web-frameworks
|
✓ | — | 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 | |
| MVC | in_db |
ASP.NET Core Web Frameworks
asp-net-core-web-frameworks
|
✓ | — | Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role) | |
| MVC | in_db |
App Architecture and Dependency Injection
app-architecture-and-dependency-injection
|
✓ | — | Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role) | |
| MVC | in_db |
Application Architecture and Code Organization
application-architecture-and-code-organization
|
✓ | — | Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role) | |
| MVC | in_db |
Native Mobile App Architecture and Dependency Injection
native-mobile-app-architecture-and-dependency-injection
|
✓ | — | Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role) | |
| REST | in_db |
API Design and Contracts
api-design-and-contracts
|
✓ | ✓ | Existing dimension (library) · Role↔dimension saved | |
| REST | in_db |
API Interface and Contract Design
api-interface-and-contract-design
|
✓ | — | Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role) | |
| REST | in_db |
Integration Protocols & Standards
integration-protocols-standards
|
✓ | — | Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role) | |
| REST | in_db |
Standards & Protocols Compliance
standards-protocols-compliance
|
✓ | — | Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role) | |
| SQL Server | in_db |
Relational Database Design
relational-database-design
|
✓ | ✓ | Existing dimension (library) · Role↔dimension saved | |
| Dependency Injection | in_db |
Angular Component Model and Templates
angular-component-model-and-templates
|
✓ | — | Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role) | |
| Dependency Injection | in_db |
App Architecture and Dependency Injection
app-architecture-and-dependency-injection
|
✓ | — | Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role) | |
| Dependency Injection | in_db |
Application Architecture Patterns
application-architecture-patterns
|
✓ | — | Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role) | |
| Dependency Injection | in_db |
Application Architecture and Code Organization
application-architecture-and-code-organization
|
✓ | — | Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role) | |
| Dependency Injection | in_db |
Backend Application Architecture and Code Organization
backend-application-architecture-and-code-organization
|
✓ | — | Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role) | |
| Dependency Injection | in_db |
Flutter App Architecture
flutter-app-architecture
|
✓ | — | Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role) | |
| Dependency Injection | in_db |
Ionic App Architecture
ionic-app-architecture
|
✓ | — | Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role) | |
| Dependency Injection | in_db |
Mobile Architecture and Code Organization
mobile-architecture-and-code-organization
|
✓ | — | Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role) | |
| Dependency Injection | in_db |
Native Mobile App Architecture and Dependency Injection
native-mobile-app-architecture-and-dependency-injection
|
✓ | — | Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role) | |
| Dependency Injection | in_db |
PHP and Magento Extension Points
php-and-magento-extension-points
|
✓ | — | Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role) | |
| Dependency Injection | in_db |
Service Architecture and Design Patterns
service-architecture-and-design-patterns
|
✓ | ✓ | Existing dimension (library) · Role↔dimension saved | |
| SOLID | in_db |
Application Architecture Patterns
application-architecture-patterns
|
✓ | — | Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role) | |
| SOLID | in_db |
Service Architecture and Design Patterns
service-architecture-and-design-patterns
|
✓ | ✓ | Existing dimension (library) · Role↔dimension saved | |
| SOLID | in_db |
UI Frameworks and Rendering
ui-frameworks-and-rendering
|
✓ | — | Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role) | |
| Azure DevOps | in_db |
CI/CD Pipeline Platforms
ci-cd-pipeline-platforms
|
✓ | — | Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role) |
Library artifacts (this run)
| Kind | Detail | DB id |
|---|---|---|
| canonical_skill_proposed | WinForms | type=Web Frameworks subtype=general nature=TOOL lifespan=MULTI_YEAR | |
| canonical_skill_proposed | ASP.NET Web API | type=Web Frameworks subtype=general nature=TOOL lifespan=MULTI_YEAR | |
| canonical_skill_proposed | SignalR | type=Web Frameworks subtype=general nature=TOOL lifespan=MULTI_YEAR | |
| canonical_skill_proposed | Windows Forms | type=Web Frameworks subtype=general nature=TOOL lifespan=MULTI_YEAR | |
| canonical_skill_proposed | MSI | type=Deployment Tools subtype=general nature=TOOL lifespan=MULTI_YEAR |
nano JD Parser — gpt-4.1-nano click to toggle
Show raw JSON
{
"JD_type": "pass",
"about_company": {
"source_marker": {
"first_5_words": "WELCOME TO SITA We\u0027re the",
"last_5_words": "you, at SITA."
},
"text": "WELCOME TO SITA\n\nWe\u0027re the team that keeps airports moving, airlines flying smoothly, and borders open. Our tech and communication innovations are the secret behind the success of the world\u0027s air travel industry.\n\nYou\u0027ll find us at 95% of international hubs. We partner closely with over 2,500 transportation and government clients, each with their own unique needs and challenges. Our goal is to find fresh solutions and cutting-edge tech to make their operations run like clockwork. Want to be a part of something big?\n\nAre you ready to love your job? The adventure begins right here, with you, at SITA.",
"word_count": 108
},
"certifications": [],
"company_name": "SITA",
"ctc": null,
"domain": {
"primary": {
"aliases": [
"ITES",
"BPO",
"Tech Consulting"
],
"domain": "IT Services \u0026 Consulting"
},
"secondary": null
},
"education": [],
"experience": {
"max": null,
"min": null,
"raw": "extensive hands-on experience in C#, Windows Forms, ASP.NET Core, MVC, and Web API"
},
"job_locations": [],
"role": "Senior .NET Developer",
"role_aliases": [
".NET Developer",
"Software Engineer",
"C# Developer"
],
"role_archetype": "Engineering",
"roles_and_responsibilities": [
{
"bullet_count": 7,
"heading": "What You Will Do",
"heading_was_present": true,
"source_marker": {
"first_5_words": "You will have the opportunity",
"last_5_words": "define and implement project requirements"
},
"text": "You will have the opportunity to work on some, or all, of the following:\n\n\u2022 Design, develop, and maintain high-performance Windows and Web applications using C#, WinForms, ASP.NET Core, and MVC.\n\u2022 Build and integrate RESTful APIs using ASP.NET Web API.\n\u2022 Develop and optimize SQL Server databases, stored procedures, and queries.\n\u2022 Implement real-time communication features using SignalR.\n\u2022 Apply Dependency Injection and SOLID principles to ensure scalable and maintainable code.\n\u2022 Troubleshoot and resolve software defects and production issues.\n\u2022 Collaborate with cross-functional teams to define and implement project requirements",
"word_count": 104
},
{
"bullet_count": 3,
"heading": "Qualifications",
"heading_was_present": true,
"source_marker": {
"first_5_words": "EXPERIENCE \u2022 This position requires",
"last_5_words": "autonomously and work collaboratively across teams."
},
"text": "EXPERIENCE\n\n\u2022 This position requires a highly skilled and self-motivated Senior .NET Developer with extensive hands-on experience in C#, Windows Forms, ASP.NET Core, MVC, and Web API. \n\u2022 The ideal candidate should possess significant exposure to SQL Server, SignalR, Dependency Injection, and Azure DevOps pipelines, as well as experience in creating MSI packages for application deployment. \n\u2022 This role demands an individual who can operate autonomously and work collaboratively across teams.",
"word_count": 83
}
],
"urls": []
}
API 1 — extract-from-jd click to toggle
{
"final_skills": [
{
"is_primary": true,
"skill_name": "C#"
},
{
"is_primary": true,
"skill_name": "WinForms"
},
{
"is_primary": true,
"skill_name": "ASP.NET Core"
},
{
"is_primary": true,
"skill_name": "MVC"
},
{
"is_primary": true,
"skill_name": "REST"
},
{
"is_primary": true,
"skill_name": "ASP.NET Web API"
},
{
"is_primary": true,
"skill_name": "SQL Server"
},
{
"is_primary": true,
"skill_name": "SignalR"
},
{
"is_primary": true,
"skill_name": "Dependency Injection"
},
{
"is_primary": true,
"skill_name": "SOLID"
},
{
"is_primary": true,
"skill_name": "Windows Forms"
},
{
"is_primary": false,
"skill_name": "Azure DevOps"
},
{
"is_primary": false,
"skill_name": "MSI"
}
],
"jd_role": {
"display_name": "Senior .NET Developer",
"rationale": null,
"role_aliases": [
".NET Developer",
"Software Engineer",
"C# Developer"
],
"role_archetype": "Engineering",
"slug": ""
},
"nano_parsed": {
"JD_type": "pass",
"about_company": {
"source_marker": {
"first_5_words": "WELCOME TO SITA We\u0027re the",
"last_5_words": "you, at SITA."
},
"text": "WELCOME TO SITA\n\nWe\u0027re the team that keeps airports moving, airlines flying smoothly, and borders open. Our tech and communication innovations are the secret behind the success of the world\u0027s air travel industry.\n\nYou\u0027ll find us at 95% of international hubs. We partner closely with over 2,500 transportation and government clients, each with their own unique needs and challenges. Our goal is to find fresh solutions and cutting-edge tech to make their operations run like clockwork. Want to be a part of something big?\n\nAre you ready to love your job? The adventure begins right here, with you, at SITA.",
"word_count": 108
},
"certifications": [],
"company_name": "SITA",
"ctc": null,
"domain": {
"primary": {
"aliases": [
"ITES",
"BPO",
"Tech Consulting"
],
"domain": "IT Services \u0026 Consulting"
},
"secondary": null
},
"education": [],
"experience": {
"max": null,
"min": null,
"raw": "extensive hands-on experience in C#, Windows Forms, ASP.NET Core, MVC, and Web API"
},
"job_locations": [],
"role": "Senior .NET Developer",
"role_aliases": [
".NET Developer",
"Software Engineer",
"C# Developer"
],
"role_archetype": "Engineering",
"roles_and_responsibilities": [
{
"bullet_count": 7,
"heading": "What You Will Do",
"heading_was_present": true,
"source_marker": {
"first_5_words": "You will have the opportunity",
"last_5_words": "define and implement project requirements"
},
"text": "You will have the opportunity to work on some, or all, of the following:\n\n\u2022 Design, develop, and maintain high-performance Windows and Web applications using C#, WinForms, ASP.NET Core, and MVC.\n\u2022 Build and integrate RESTful APIs using ASP.NET Web API.\n\u2022 Develop and optimize SQL Server databases, stored procedures, and queries.\n\u2022 Implement real-time communication features using SignalR.\n\u2022 Apply Dependency Injection and SOLID principles to ensure scalable and maintainable code.\n\u2022 Troubleshoot and resolve software defects and production issues.\n\u2022 Collaborate with cross-functional teams to define and implement project requirements",
"word_count": 104
},
{
"bullet_count": 3,
"heading": "Qualifications",
"heading_was_present": true,
"source_marker": {
"first_5_words": "EXPERIENCE \u2022 This position requires",
"last_5_words": "autonomously and work collaboratively across teams."
},
"text": "EXPERIENCE\n\n\u2022 This position requires a highly skilled and self-motivated Senior .NET Developer with extensive hands-on experience in C#, Windows Forms, ASP.NET Core, MVC, and Web API. \n\u2022 The ideal candidate should possess significant exposure to SQL Server, SignalR, Dependency Injection, and Azure DevOps pipelines, as well as experience in creating MSI packages for application deployment. \n\u2022 This role demands an individual who can operate autonomously and work collaboratively across teams.",
"word_count": 83
}
],
"urls": []
},
"rejected": false,
"rejection_reason": null,
"run_id": "b2f2b7dd-70e0-4efc-aa08-f3e38c9cf04f",
"stage3_signals": {
"alias_found": true,
"alias_match_roles": [
{
"display_name": ".NET Backend Developer",
"kra_matches": null,
"matched_count": null,
"matched_skills": null,
"role_id": 83,
"score": 1.0,
"slug": "dotnet-backend-developer",
"total_count": null
},
{
"display_name": "Backend Developer",
"kra_matches": null,
"matched_count": null,
"matched_skills": null,
"role_id": 1,
"score": 1.0,
"slug": "backend-engineer",
"total_count": null
}
],
"kra_match_roles": [
{
"display_name": "Backend Developer",
"kra_matches": [
{
"kra_text": "Investigates and resolves production incidents, API bugs, and service degradation through root cause analysis, hotfixes, and post-mortems.",
"sentence": "Troubleshoot and resolve software defects and production issues.",
"similarity": 0.6977
},
{
"kra_text": "Identifies and resolves backend performance bottlenecks through query optimization, indexing strategies, connection pooling, and distributed caching with Redis.",
"sentence": "Develop and optimize SQL Server databases, stored procedures, and queries.",
"similarity": 0.5148
},
{
"kra_text": "Designs and maintains RESTful and GraphQL API interfaces with proper authentication, versioning, rate limiting, and documentation for frontend and third-party consumers.",
"sentence": "Build and integrate RESTful APIs using ASP.NET Web API.",
"similarity": 0.4459
}
],
"matched_count": null,
"matched_skills": null,
"role_id": 1,
"score": 0.5528,
"slug": "backend-engineer",
"total_count": null
},
{
"display_name": "Fullstack Developer",
"kra_matches": [
{
"kra_text": "Designs and queries relational databases like PostgreSQL and document stores like MongoDB, writing migrations, indexes, and optimized queries.",
"sentence": "Develop and optimize SQL Server databases, stored procedures, and queries.",
"similarity": 0.5752
},
{
"kra_text": "Works closely with product managers and UX designers to translate requirements and wireframes into working software features through iterative development.",
"sentence": "Collaborate with cross-functional teams to define and implement project requirements",
"similarity": 0.545
},
{
"kra_text": "Debugs full-stack issues that span frontend rendering, API behavior, database queries, and infrastructure configuration to identify root causes.",
"sentence": "Troubleshoot and resolve software defects and production issues.",
"similarity": 0.4899
}
],
"matched_count": null,
"matched_skills": null,
"role_id": 15,
"score": 0.5367,
"slug": "full-stack-engineer",
"total_count": null
},
{
"display_name": "Flutter Developer",
"kra_matches": [
{
"kra_text": "collaborate with design, product, and backend teams",
"sentence": "Collaborate with cross-functional teams to define and implement project requirements",
"similarity": 0.6627
},
{
"kra_text": "collaborate with design, product, and backend teams",
"sentence": "This role demands an individual who can operate autonomously and work collaboratively across teams.",
"similarity": 0.4719
},
{
"kra_text": "structure reusable application code",
"sentence": "Apply Dependency Injection and SOLID principles to ensure scalable and maintainable code.",
"similarity": 0.46
}
],
"matched_count": null,
"matched_skills": null,
"role_id": 74,
"score": 0.5315,
"slug": "flutter-developer",
"total_count": null
},
{
"display_name": "Angular Frontend Developer",
"kra_matches": [
{
"kra_text": "defect diagnosis and fixes",
"sentence": "Troubleshoot and resolve software defects and production issues.",
"similarity": 0.5669
},
{
"kra_text": "collaboration with design and QA",
"sentence": "Collaborate with cross-functional teams to define and implement project requirements",
"similarity": 0.5498
},
{
"kra_text": "backend endpoint integration",
"sentence": "Build and integrate RESTful APIs using ASP.NET Web API.",
"similarity": 0.4699
}
],
"matched_count": null,
"matched_skills": null,
"role_id": 90,
"score": 0.5289,
"slug": "angular-frontend-developer",
"total_count": null
},
{
"display_name": "Frontend Developer",
"kra_matches": [
{
"kra_text": "Supports production releases by diagnosing cross-browser compatibility issues, investigating UI regressions, and resolving frontend performance degradation.",
"sentence": "Troubleshoot and resolve software defects and production issues.",
"similarity": 0.5789
},
{
"kra_text": "Collaborates with UX designers to refine interaction details, animations, responsive breakpoints, and micro-interaction behavior.",
"sentence": "Collaborate with cross-functional teams to define and implement project requirements",
"similarity": 0.5053
},
{
"kra_text": "Builds responsive user interfaces and interactive web components using React, Vue, or Angular with TypeScript, HTML5, and modern CSS for browser-based applications.",
"sentence": "Design, develop, and maintain high-performance Windows and Web applications using C#, WinForms, ASP.NET Core, and MVC.",
"similarity": 0.4958
}
],
"matched_count": null,
"matched_skills": null,
"role_id": 7,
"score": 0.5267,
"slug": "frontend-engineer",
"total_count": null
}
],
"skill_match_roles": [
{
"display_name": ".NET Backend Developer",
"kra_matches": null,
"matched_count": 8,
"matched_skills": [
".NET Core",
"ASP.NET Core",
"C#",
"MVC",
"REST",
"SOLID",
"SQL Server",
"dependency injection"
],
"role_id": 83,
"score": 0.7273,
"slug": "dotnet-backend-developer",
"total_count": 11
},
{
"display_name": "Fullstack Developer",
"kra_matches": null,
"matched_count": 6,
"matched_skills": [
"ASP.NET Core",
"C#",
"MVC",
"REST",
"SOLID",
"dependency injection"
],
"role_id": 15,
"score": 0.5455,
"slug": "full-stack-engineer",
"total_count": 11
},
{
"display_name": "Backend Developer",
"kra_matches": null,
"matched_count": 6,
"matched_skills": [
"ASP.NET Core",
"C#",
"REST",
"SOLID",
"SQL Server",
"dependency injection"
],
"role_id": 1,
"score": 0.5455,
"slug": "backend-engineer",
"total_count": 11
},
{
"display_name": "Node.js Backend Developer",
"kra_matches": null,
"matched_count": 5,
"matched_skills": [
"ASP.NET Core",
"REST",
"SOLID",
"SQL Server",
"dependency injection"
],
"role_id": 82,
"score": 0.4545,
"slug": "node-backend-developer",
"total_count": 11
},
{
"display_name": "Python Backend Developer",
"kra_matches": null,
"matched_count": 5,
"matched_skills": [
"ASP.NET Core",
"REST",
"SOLID",
"SQL Server",
"dependency injection"
],
"role_id": 80,
"score": 0.4545,
"slug": "python-backend-developer",
"total_count": 11
}
]
},
"stage4_decision": {
"alias_collision_detected": false,
"case": "DOMAIN",
"chosen_role": {
"display_name": "Backend Developer",
"kra_matches": null,
"matched_count": null,
"matched_skills": null,
"role_id": 1,
"score": 0.98,
"slug": "backend-engineer",
"total_count": null
},
"confidence": 0.98,
"is_new_role": false,
"llm2_fired": false,
"llm2_reasoning": null,
"matched_dimensions": [
"Backend .NET application development",
"API development and integration",
"Database design and optimization",
"Real-time communication features",
"Maintainable software architecture",
"Production issue troubleshooting",
"Cross-functional collaboration",
"Application deployment tooling"
],
"matched_kras": [
"Design, develop, and maintain high-performance Windows and Web applications",
"Build and integrate RESTful APIs",
"Develop and optimize SQL Server databases, stored procedures, and queries",
"Implement real-time communication features using SignalR",
"Apply Dependency Injection and SOLID principles",
"Troubleshoot and resolve software defects and production issues",
"Collaborate with cross-functional teams to define and implement project requirements"
],
"matched_skills": [
"C#",
"WinForms",
"ASP.NET Core",
"MVC",
"RESTful APIs",
"ASP.NET Web API",
"SQL Server",
"stored procedures",
"queries",
"SignalR",
"Dependency Injection",
"SOLID principles",
"Azure DevOps pipelines",
"MSI packages"
],
"new_role_display_name": null,
"new_role_slug": null,
"queued": false,
"reasoning": "Domain=Software Engineering \u2192 sub-role dotnet-backend-developer; The JD is centered on C#/.NET backend and application development with APIs, SQL Server, SignalR, and deployment tooling, which best matches Backend Developer.",
"sub_role": {
"confidence": 0.99,
"display_name": ".NET Backend Developer",
"reasoning": "The JD explicitly centers on C#, ASP.NET Core, MVC, Web API, SignalR, SQL Server, and Azure DevOps, which clearly maps to a .NET backend role.",
"role_id": 83,
"slug": "dotnet-backend-developer"
}
},
"stage5_updates": {
"centroid_n_after": 106,
"centroid_updated": true,
"collision_log_id": null,
"new_kra_attached": null,
"new_skills_attached": [
{
"is_primary": true,
"queue_id": 3978,
"role_display_name": "Backend Developer",
"role_slug": "backend-engineer",
"skill_name": "WinForms",
"status": "pending"
},
{
"is_primary": true,
"queue_id": 3979,
"role_display_name": "Backend Developer",
"role_slug": "backend-engineer",
"skill_name": "ASP.NET Web API",
"status": "pending"
},
{
"is_primary": true,
"queue_id": 3980,
"role_display_name": "Backend Developer",
"role_slug": "backend-engineer",
"skill_name": "SignalR",
"status": "pending"
},
{
"is_primary": true,
"queue_id": 3981,
"role_display_name": "Backend Developer",
"role_slug": "backend-engineer",
"skill_name": "Windows Forms",
"status": "pending"
},
{
"is_primary": false,
"queue_id": 3982,
"role_display_name": "Backend Developer",
"role_slug": "backend-engineer",
"skill_name": "MSI",
"status": "pending"
}
],
"queue_entry_id": null,
"v3_pipeline_triggered": false,
"v3_role_slug": null,
"v3_run_id": null
}
}
API 2 — extract-details
{
"alias_matches": [
{
"alias_persist_skipped_reason": "alias_text already exists for this canonical skill",
"alias_persisted": false,
"existing_alias_id": 52,
"existing_alias_text": "C#",
"input_term": "C#",
"matched_canonical": {
"category_id": 6,
"display_name": "C#",
"id": 4,
"is_also_category": false,
"is_extractable": true,
"skill_nature": "LANGUAGE",
"slug": "c",
"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": 831,
"existing_alias_text": "MVC",
"input_term": "MVC",
"matched_canonical": {
"category_id": 1,
"display_name": "MVC",
"id": 505,
"is_also_category": false,
"is_extractable": true,
"skill_nature": "PATTERN",
"slug": "mvc",
"sub_category_id": 2462,
"typical_lifespan": "EVERGREEN",
"volatility": "STABLE"
},
"matched_via": "alias"
},
{
"alias_persist_skipped_reason": "alias_text already exists for this canonical skill",
"alias_persisted": false,
"existing_alias_id": 106,
"existing_alias_text": "REST",
"input_term": "REST",
"matched_canonical": {
"category_id": 2,
"display_name": "REST",
"id": 11,
"is_also_category": false,
"is_extractable": true,
"skill_nature": "CONCEPT",
"slug": "rest",
"sub_category_id": 2122,
"typical_lifespan": "EVERGREEN",
"volatility": "STABLE"
},
"matched_via": "alias"
},
{
"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": 5279,
"existing_alias_text": "Dependency Injection",
"input_term": "Dependency Injection",
"matched_canonical": {
"category_id": 2,
"display_name": "dependency injection",
"id": 88,
"is_also_category": false,
"is_extractable": true,
"skill_nature": "CONCEPT",
"slug": "dependency-injection",
"sub_category_id": 2482,
"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": 1098,
"existing_alias_text": "Solid",
"input_term": "SOLID",
"matched_canonical": {
"category_id": 2,
"display_name": "SOLID",
"id": 614,
"is_also_category": false,
"is_extractable": true,
"skill_nature": "CONCEPT",
"slug": "solid",
"sub_category_id": 2976,
"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": 1850,
"existing_alias_text": "Azure DevOps",
"input_term": "Azure DevOps",
"matched_canonical": {
"category_id": 9,
"display_name": "Azure DevOps",
"id": 1214,
"is_also_category": false,
"is_extractable": true,
"skill_nature": "PLATFORM",
"slug": "azure-devops",
"sub_category_id": 170,
"typical_lifespan": "EVERGREEN",
"volatility": "STABLE"
},
"matched_via": "alias"
}
],
"candidate_roles": [
{
"display_name": ".NET Backend Developer",
"id": 83,
"rationale": null,
"role_archetype": "Engineering",
"slug": "dotnet-backend-developer",
"source": "db"
},
{
"display_name": "Hybrid Mobile Developer",
"id": 11,
"rationale": null,
"role_archetype": null,
"slug": "hybrid-mobile-developer",
"source": "db"
},
{
"display_name": "Backend Developer",
"id": 1,
"rationale": null,
"role_archetype": "A Backend Engineer designs, builds, and maintains the server-side logic and data handling that power applications and services. They focus on implementing reliable business functionality, integrating with other systems, and ensuring the backend is scalable, maintainable, and observable.",
"slug": "backend-engineer",
"source": "db"
},
{
"display_name": "Fullstack Developer",
"id": 15,
"rationale": null,
"role_archetype": null,
"slug": "full-stack-engineer",
"source": "db"
},
{
"display_name": "ML Engineer",
"id": 3,
"rationale": null,
"role_archetype": null,
"slug": "ml-engineer",
"source": "db"
},
{
"display_name": "MLOps Engineer",
"id": 16,
"rationale": null,
"role_archetype": null,
"slug": "ml-ops-engineer",
"source": "db"
},
{
"display_name": "AR/VR Engineer",
"id": 8,
"rationale": null,
"role_archetype": null,
"slug": "ar-vr-engineer",
"source": "db"
},
{
"display_name": "Sitecore Dev",
"id": 233,
"rationale": null,
"role_archetype": "Engineering",
"slug": "sitecore-dev",
"source": "db"
},
{
"display_name": "Video Codec Engineer",
"id": 22,
"rationale": null,
"role_archetype": null,
"slug": "video-codec-engineer",
"source": "db"
},
{
"display_name": "Java Backend Developer",
"id": 79,
"rationale": null,
"role_archetype": "Engineering",
"slug": "java-backend-developer",
"source": "db"
},
{
"display_name": "Node.js Backend Developer",
"id": 82,
"rationale": null,
"role_archetype": "Engineering",
"slug": "node-backend-developer",
"source": "db"
},
{
"display_name": "PHP Backend Developer",
"id": 86,
"rationale": null,
"role_archetype": "Engineering",
"slug": "php-backend-developer",
"source": "db"
},
{
"display_name": "Python Backend Developer",
"id": 80,
"rationale": null,
"role_archetype": "Engineering",
"slug": "python-backend-developer",
"source": "db"
},
{
"display_name": "Android Developer",
"id": 4,
"rationale": null,
"role_archetype": null,
"slug": "android-engineer",
"source": "db"
},
{
"display_name": "iOS Developer",
"id": 6,
"rationale": null,
"role_archetype": null,
"slug": "ios-engineer",
"source": "db"
},
{
"display_name": "Native Mobile Developer",
"id": 75,
"rationale": null,
"role_archetype": "Engineering",
"slug": "native-mobile-developer",
"source": "db"
},
{
"display_name": "Go Backend Developer",
"id": 81,
"rationale": null,
"role_archetype": "Engineering",
"slug": "go-backend-developer",
"source": "db"
},
{
"display_name": "Kotlin Backend Developer",
"id": 84,
"rationale": null,
"role_archetype": "Engineering",
"slug": "kotlin-server-backend-developer",
"source": "db"
},
{
"display_name": "Ruby Backend Developer",
"id": 85,
"rationale": null,
"role_archetype": "Engineering",
"slug": "ruby-backend-developer",
"source": "db"
},
{
"display_name": "Scala Backend Developer",
"id": 87,
"rationale": null,
"role_archetype": "Engineering",
"slug": "scala-backend-developer",
"source": "db"
},
{
"display_name": "Pega Developer",
"id": 24,
"rationale": null,
"role_archetype": null,
"slug": "pega-developer",
"source": "db"
},
{
"display_name": "Angular Frontend Developer",
"id": 90,
"rationale": null,
"role_archetype": "Engineering",
"slug": "angular-frontend-developer",
"source": "db"
},
{
"display_name": "Flutter Developer",
"id": 74,
"rationale": null,
"role_archetype": "Engineering",
"slug": "flutter-developer",
"source": "db"
},
{
"display_name": "Ionic Developer",
"id": 434,
"rationale": null,
"role_archetype": null,
"slug": "ionic-developer",
"source": "db"
},
{
"display_name": "React Native Developer",
"id": 73,
"rationale": null,
"role_archetype": "Engineering",
"slug": "react-native-developer",
"source": "db"
},
{
"display_name": "Magento Dev",
"id": 231,
"rationale": null,
"role_archetype": "Engineering",
"slug": "magento-dev",
"source": "db"
},
{
"display_name": "Frontend Developer",
"id": 7,
"rationale": null,
"role_archetype": null,
"slug": "frontend-engineer",
"source": "db"
},
{
"display_name": "Web Developer",
"id": 25,
"rationale": null,
"role_archetype": null,
"slug": "web-developer",
"source": "db"
},
{
"display_name": "DevOps Engineer",
"id": 10,
"rationale": null,
"role_archetype": null,
"slug": "devops-engineer",
"source": "db"
}
],
"chosen_role": {
"display_name": "Backend Developer",
"id": 1,
"rationale": "Domain=Software Engineering \u2192 sub-role dotnet-backend-developer; The JD is centered on C#/.NET backend and application development with APIs, SQL Server, SignalR, and deployment tooling, which best matches Backend Developer.",
"role_archetype": "A Backend Engineer designs, builds, and maintains the server-side logic and data handling that power applications and services. They focus on implementing reliable business functionality, integrating with other systems, and ensuring the backend is scalable, maintainable, and observable.",
"slug": "backend-engineer",
"source": "db"
},
"dimensions": [
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "C# and .NET Languages",
"id": 362,
"rationale": "Primary implementation languages and runtime features used to build backend service logic in the .NET ecosystem. This is the core coding surface for request handling, domain logic, and service internals.",
"slug": "c-and-net-languages",
"source": "db"
},
"input_skill": "C#",
"llm_role": null,
"roles_from_db": [
{
"display_name": ".NET Backend Developer",
"id": 83,
"rationale": null,
"role_archetype": "Engineering",
"slug": "dotnet-backend-developer",
"source": "db"
}
]
},
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Cross-Platform App Languages",
"id": 167,
"rationale": "Languages used to implement shared mobile features across iOS and Android from a common codebase. This is the primary coding surface for hybrid app logic, UI behavior, and platform-specific branching.",
"slug": "cross-platform-app-languages",
"source": "db"
},
"input_skill": "C#",
"llm_role": null,
"roles_from_db": [
{
"display_name": "Hybrid Mobile Developer",
"id": 11,
"rationale": null,
"role_archetype": null,
"slug": "hybrid-mobile-developer",
"source": "db"
}
]
},
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Programming Languages",
"id": 1,
"rationale": "Primary implementation languages used to build client and server feature code. Full stack engineers need enough fluency to move across layers and implement product behavior end to end.",
"slug": "programming-languages",
"source": "db"
},
"input_skill": "C#",
"llm_role": null,
"roles_from_db": [
{
"display_name": "Backend Developer",
"id": 1,
"rationale": null,
"role_archetype": "A Backend Engineer designs, builds, and maintains the server-side logic and data handling that power applications and services. They focus on implementing reliable business functionality, integrating with other systems, and ensuring the backend is scalable, maintainable, and observable.",
"slug": "backend-engineer",
"source": "db"
},
{
"display_name": "Fullstack Developer",
"id": 15,
"rationale": null,
"role_archetype": null,
"slug": "full-stack-engineer",
"source": "db"
}
]
},
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "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": "C#",
"llm_role": null,
"roles_from_db": [
{
"display_name": "ML Engineer",
"id": 3,
"rationale": null,
"role_archetype": null,
"slug": "ml-engineer",
"source": "db"
},
{
"display_name": "MLOps Engineer",
"id": 16,
"rationale": null,
"role_archetype": null,
"slug": "ml-ops-engineer",
"source": "db"
}
]
},
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Programming Languages for XR",
"id": 97,
"rationale": "Primary implementation languages used to build immersive client features, interaction logic, and device-specific runtime behavior. This is the core coding surface for AR/VR experiences.",
"slug": "programming-languages-for-xr",
"source": "db"
},
"input_skill": "C#",
"llm_role": null,
"roles_from_db": [
{
"display_name": "AR/VR Engineer",
"id": 8,
"rationale": null,
"role_archetype": null,
"slug": "ar-vr-engineer",
"source": "db"
}
]
},
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "React Frontend Development",
"id": 96,
"rationale": "Building interactive web user interfaces with React.js, including component composition, state management, hooks, and rendering patterns. React.js belongs here because it is a core library for client-side UI development in modern web applications.",
"slug": "d_init_01",
"source": "db"
},
"input_skill": "C#",
"llm_role": null,
"roles_from_db": []
},
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Sitecore Development Languages",
"id": 438,
"rationale": "Core implementation languages and markup used to build Sitecore customizations, rendering logic, and site behavior. This is the primary authoring surface for Sitecore-specific code and templates.",
"slug": "sitecore-development-languages",
"source": "db"
},
"input_skill": "C#",
"llm_role": null,
"roles_from_db": [
{
"display_name": "Sitecore Dev",
"id": 233,
"rationale": null,
"role_archetype": "Engineering",
"slug": "sitecore-dev",
"source": "db"
}
]
},
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Video Codec Languages and DSLs",
"id": 225,
"rationale": "Implementation languages and codec-specific description languages used to build compression, decoding, and transform logic. This is the primary coding surface for codec behavior and bitstream manipulation.",
"slug": "video-codec-languages-and-dsls",
"source": "db"
},
"input_skill": "C#",
"llm_role": null,
"roles_from_db": [
{
"display_name": "Video Codec Engineer",
"id": 22,
"rationale": null,
"role_archetype": null,
"slug": "video-codec-engineer",
"source": "db"
}
]
},
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "ASP.NET Core Web Frameworks",
"id": 363,
"rationale": "Server-side web frameworks and hosting models used to build HTTP APIs, middleware, filters, and request pipelines. This cluster is coherent because it defines how backend services receive, process, and return requests.",
"slug": "asp-net-core-web-frameworks",
"source": "db"
},
"input_skill": "ASP.NET Core",
"llm_role": null,
"roles_from_db": [
{
"display_name": ".NET Backend Developer",
"id": 83,
"rationale": null,
"role_archetype": "Engineering",
"slug": "dotnet-backend-developer",
"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 Developer",
"id": 1,
"rationale": null,
"role_archetype": "A Backend Engineer designs, builds, and maintains the server-side logic and data handling that power applications and services. They focus on implementing reliable business functionality, integrating with other systems, and ensuring the backend is scalable, maintainable, and observable.",
"slug": "backend-engineer",
"source": "db"
},
{
"display_name": "Fullstack Developer",
"id": 15,
"rationale": null,
"role_archetype": null,
"slug": "full-stack-engineer",
"source": "db"
},
{
"display_name": "Java Backend Developer",
"id": 79,
"rationale": null,
"role_archetype": "Engineering",
"slug": "java-backend-developer",
"source": "db"
},
{
"display_name": "Node.js Backend Developer",
"id": 82,
"rationale": null,
"role_archetype": "Engineering",
"slug": "node-backend-developer",
"source": "db"
},
{
"display_name": "PHP Backend Developer",
"id": 86,
"rationale": null,
"role_archetype": "Engineering",
"slug": "php-backend-developer",
"source": "db"
},
{
"display_name": "Python Backend Developer",
"id": 80,
"rationale": null,
"role_archetype": "Engineering",
"slug": "python-backend-developer",
"source": "db"
}
]
},
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "ASP.NET Core Web Frameworks",
"id": 363,
"rationale": "Server-side web frameworks and hosting models used to build HTTP APIs, middleware, filters, and request pipelines. This cluster is coherent because it defines how backend services receive, process, and return requests.",
"slug": "asp-net-core-web-frameworks",
"source": "db"
},
"input_skill": "MVC",
"llm_role": null,
"roles_from_db": [
{
"display_name": ".NET Backend Developer",
"id": 83,
"rationale": null,
"role_archetype": "Engineering",
"slug": "dotnet-backend-developer",
"source": "db"
}
]
},
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "App Architecture and Dependency Injection",
"id": 94,
"rationale": "Structural patterns used to organize iOS code into testable, maintainable feature modules and layers. iOS engineers use these patterns to separate UI, state, and service integration concerns.",
"slug": "app-architecture-and-dependency-injection",
"source": "db"
},
"input_skill": "MVC",
"llm_role": null,
"roles_from_db": [
{
"display_name": "Android Developer",
"id": 4,
"rationale": null,
"role_archetype": null,
"slug": "android-engineer",
"source": "db"
},
{
"display_name": "iOS Developer",
"id": 6,
"rationale": null,
"role_archetype": null,
"slug": "ios-engineer",
"source": "db"
}
]
},
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Application Architecture and Code Organization",
"id": 220,
"rationale": "Structural patterns for organizing product code into maintainable modules, layers, and feature boundaries. Full stack engineers need this to keep cross-layer feature work understandable as the product grows.",
"slug": "application-architecture-and-code-organization",
"source": "db"
},
"input_skill": "MVC",
"llm_role": null,
"roles_from_db": [
{
"display_name": "Fullstack Developer",
"id": 15,
"rationale": null,
"role_archetype": null,
"slug": "full-stack-engineer",
"source": "db"
}
]
},
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Native Mobile App Architecture and Dependency Injection",
"id": 273,
"rationale": "Structural patterns for organizing native mobile application code into maintainable, testable modules, layers, and feature boundaries. This includes app architecture patterns such as MVVM, MVC, MVI, VIPER, and Clean Architecture; dependency injection frameworks and patterns such as Hilt, Dagger, and Koin; and code organization techniques such as modularization, feature modules, repository pattern, and use-case layering to separate UI, state, data, and platform concerns across a growing codebase.",
"slug": "native-mobile-app-architecture-and-dependency-injection",
"source": "db"
},
"input_skill": "MVC",
"llm_role": null,
"roles_from_db": [
{
"display_name": "Native Mobile Developer",
"id": 75,
"rationale": null,
"role_archetype": "Engineering",
"slug": "native-mobile-developer",
"source": "db"
}
]
},
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "API Design and Contracts",
"id": 3,
"rationale": "Designing request/response shapes and the rules that govern client-server interaction. This cluster is coherent because full stack engineers often own the contract between UI behavior and backend implementation.",
"slug": "api-design-and-contracts",
"source": "db"
},
"input_skill": "REST",
"llm_role": null,
"roles_from_db": [
{
"display_name": "Backend Developer",
"id": 1,
"rationale": null,
"role_archetype": "A Backend Engineer designs, builds, and maintains the server-side logic and data handling that power applications and services. They focus on implementing reliable business functionality, integrating with other systems, and ensuring the backend is scalable, maintainable, and observable.",
"slug": "backend-engineer",
"source": "db"
},
{
"display_name": "Fullstack Developer",
"id": 15,
"rationale": null,
"role_archetype": null,
"slug": "full-stack-engineer",
"source": "db"
}
]
},
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "API Interface and Contract Design",
"id": 289,
"rationale": "Designing backend service interfaces and contracts that other systems consume, including endpoint and operation shape, request/response payloads, schema and validation, pagination, filtering, idempotency, versioning, status codes, and backward compatibility across REST, GraphQL, gRPC, and OpenAPI-based APIs.",
"slug": "api-interface-and-contract-design",
"source": "db"
},
"input_skill": "REST",
"llm_role": null,
"roles_from_db": [
{
"display_name": ".NET Backend Developer",
"id": 83,
"rationale": null,
"role_archetype": "Engineering",
"slug": "dotnet-backend-developer",
"source": "db"
},
{
"display_name": "Go Backend Developer",
"id": 81,
"rationale": null,
"role_archetype": "Engineering",
"slug": "go-backend-developer",
"source": "db"
},
{
"display_name": "Kotlin Backend Developer",
"id": 84,
"rationale": null,
"role_archetype": "Engineering",
"slug": "kotlin-server-backend-developer",
"source": "db"
},
{
"display_name": "Node.js Backend Developer",
"id": 82,
"rationale": null,
"role_archetype": "Engineering",
"slug": "node-backend-developer",
"source": "db"
},
{
"display_name": "PHP Backend Developer",
"id": 86,
"rationale": null,
"role_archetype": "Engineering",
"slug": "php-backend-developer",
"source": "db"
},
{
"display_name": "Python Backend Developer",
"id": 80,
"rationale": null,
"role_archetype": "Engineering",
"slug": "python-backend-developer",
"source": "db"
},
{
"display_name": "Ruby Backend Developer",
"id": 85,
"rationale": null,
"role_archetype": "Engineering",
"slug": "ruby-backend-developer",
"source": "db"
},
{
"display_name": "Scala Backend Developer",
"id": 87,
"rationale": null,
"role_archetype": "Engineering",
"slug": "scala-backend-developer",
"source": "db"
}
]
},
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Integration Protocols \u0026 Standards",
"id": 271,
"rationale": "Standards and protocols for integrating Pega applications.",
"slug": "integration-protocols-standards",
"source": "db"
},
"input_skill": "REST",
"llm_role": null,
"roles_from_db": [
{
"display_name": "Pega Developer",
"id": 24,
"rationale": null,
"role_archetype": null,
"slug": "pega-developer",
"source": "db"
}
]
},
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Standards \u0026 Protocols Compliance",
"id": 452,
"rationale": "Encompasses key web and data standards, protocols, and compliance requirements relevant to Sitecore implementations.",
"slug": "standards-protocols-compliance",
"source": "db"
},
"input_skill": "REST",
"llm_role": null,
"roles_from_db": [
{
"display_name": "Sitecore Dev",
"id": 233,
"rationale": null,
"role_archetype": "Engineering",
"slug": "sitecore-dev",
"source": "db"
}
]
},
{
"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": ".NET Backend Developer",
"id": 83,
"rationale": null,
"role_archetype": "Engineering",
"slug": "dotnet-backend-developer",
"source": "db"
},
{
"display_name": "Backend Developer",
"id": 1,
"rationale": null,
"role_archetype": "A Backend Engineer designs, builds, and maintains the server-side logic and data handling that power applications and services. They focus on implementing reliable business functionality, integrating with other systems, and ensuring the backend is scalable, maintainable, and observable.",
"slug": "backend-engineer",
"source": "db"
},
{
"display_name": "Kotlin Backend Developer",
"id": 84,
"rationale": null,
"role_archetype": "Engineering",
"slug": "kotlin-server-backend-developer",
"source": "db"
},
{
"display_name": "Node.js Backend Developer",
"id": 82,
"rationale": null,
"role_archetype": "Engineering",
"slug": "node-backend-developer",
"source": "db"
},
{
"display_name": "Python Backend Developer",
"id": 80,
"rationale": null,
"role_archetype": "Engineering",
"slug": "python-backend-developer",
"source": "db"
},
{
"display_name": "Ruby Backend Developer",
"id": 85,
"rationale": null,
"role_archetype": "Engineering",
"slug": "ruby-backend-developer",
"source": "db"
},
{
"display_name": "Scala Backend Developer",
"id": 87,
"rationale": null,
"role_archetype": "Engineering",
"slug": "scala-backend-developer",
"source": "db"
}
]
},
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Angular Component Model and Templates",
"id": 303,
"rationale": "Core Angular framework surface for building reusable UI, composing views, and wiring component behavior. This is the main application substrate for browser features in this role.",
"slug": "angular-component-model-and-templates",
"source": "db"
},
"input_skill": "Dependency Injection",
"llm_role": null,
"roles_from_db": [
{
"display_name": "Angular Frontend Developer",
"id": 90,
"rationale": null,
"role_archetype": "Engineering",
"slug": "angular-frontend-developer",
"source": "db"
}
]
},
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "App Architecture and Dependency Injection",
"id": 94,
"rationale": "Structural patterns used to organize iOS code into testable, maintainable feature modules and layers. iOS engineers use these patterns to separate UI, state, and service integration concerns.",
"slug": "app-architecture-and-dependency-injection",
"source": "db"
},
"input_skill": "Dependency Injection",
"llm_role": null,
"roles_from_db": [
{
"display_name": "Android Developer",
"id": 4,
"rationale": null,
"role_archetype": null,
"slug": "android-engineer",
"source": "db"
},
{
"display_name": "iOS Developer",
"id": 6,
"rationale": null,
"role_archetype": null,
"slug": "ios-engineer",
"source": "db"
}
]
},
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Application Architecture Patterns",
"id": 293,
"rationale": "Structural patterns for organizing Python backend code into maintainable modules, layers, and feature boundaries. This is a coherent cluster because senior backend developers are expected to refactor and shape service internals over time.",
"slug": "application-architecture-patterns",
"source": "db"
},
"input_skill": "Dependency Injection",
"llm_role": null,
"roles_from_db": [
{
"display_name": ".NET Backend Developer",
"id": 83,
"rationale": null,
"role_archetype": "Engineering",
"slug": "dotnet-backend-developer",
"source": "db"
},
{
"display_name": "Python Backend Developer",
"id": 80,
"rationale": null,
"role_archetype": "Engineering",
"slug": "python-backend-developer",
"source": "db"
}
]
},
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Application Architecture and Code Organization",
"id": 220,
"rationale": "Structural patterns for organizing product code into maintainable modules, layers, and feature boundaries. Full stack engineers need this to keep cross-layer feature work understandable as the product grows.",
"slug": "application-architecture-and-code-organization",
"source": "db"
},
"input_skill": "Dependency Injection",
"llm_role": null,
"roles_from_db": [
{
"display_name": "Fullstack Developer",
"id": 15,
"rationale": null,
"role_archetype": null,
"slug": "full-stack-engineer",
"source": "db"
}
]
},
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Backend Application Architecture and Code Organization",
"id": 366,
"rationale": "Structural patterns for organizing backend application code into maintainable modules, layers, and boundaries so services remain testable, modular, evolvable, and easy to refactor. This includes clean architecture, hexagonal architecture, layered architecture, dependency injection, service layers, package or module boundaries, modularization, domain-driven design, SOLID, CQRS, and mediator-style patterns. It excludes API endpoint syntax, database schema design, deployment topology, and frontend architecture.",
"slug": "backend-application-architecture-and-code-organization",
"source": "db"
},
"input_skill": "Dependency Injection",
"llm_role": null,
"roles_from_db": [
{
"display_name": "Go Backend Developer",
"id": 81,
"rationale": null,
"role_archetype": "Engineering",
"slug": "go-backend-developer",
"source": "db"
}
]
},
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Flutter App Architecture",
"id": 316,
"rationale": "Structural patterns used to organize Flutter code into maintainable modules, layers, and feature boundaries. Senior Flutter developers often own these patterns to keep shared app delivery scalable across teams and releases.",
"slug": "flutter-app-architecture",
"source": "db"
},
"input_skill": "Dependency Injection",
"llm_role": null,
"roles_from_db": [
{
"display_name": "Flutter Developer",
"id": 74,
"rationale": null,
"role_archetype": "Engineering",
"slug": "flutter-developer",
"source": "db"
}
]
},
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Ionic App Architecture",
"id": 384,
"rationale": "Structural patterns for organizing Ionic code into maintainable modules, layers, and feature boundaries. Senior Ionic developers often define these patterns to keep shared app behavior consistent across devices and releases.",
"slug": "ionic-app-architecture",
"source": "db"
},
"input_skill": "Dependency Injection",
"llm_role": null,
"roles_from_db": [
{
"display_name": "Ionic Developer",
"id": 434,
"rationale": null,
"role_archetype": null,
"slug": "ionic-developer",
"source": "db"
}
]
},
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Mobile Architecture and Code Organization",
"id": 170,
"rationale": "Structural patterns used to organize shared mobile code into maintainable modules, layers, and feature boundaries. Senior hybrid developers often own these patterns to keep cross-platform code testable and adaptable to platform exceptions.",
"slug": "mobile-architecture-and-code-organization",
"source": "db"
},
"input_skill": "Dependency Injection",
"llm_role": null,
"roles_from_db": [
{
"display_name": "Hybrid Mobile Developer",
"id": 11,
"rationale": null,
"role_archetype": null,
"slug": "hybrid-mobile-developer",
"source": "db"
},
{
"display_name": "React Native Developer",
"id": 73,
"rationale": null,
"role_archetype": "Engineering",
"slug": "react-native-developer",
"source": "db"
}
]
},
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Native Mobile App Architecture and Dependency Injection",
"id": 273,
"rationale": "Structural patterns for organizing native mobile application code into maintainable, testable modules, layers, and feature boundaries. This includes app architecture patterns such as MVVM, MVC, MVI, VIPER, and Clean Architecture; dependency injection frameworks and patterns such as Hilt, Dagger, and Koin; and code organization techniques such as modularization, feature modules, repository pattern, and use-case layering to separate UI, state, data, and platform concerns across a growing codebase.",
"slug": "native-mobile-app-architecture-and-dependency-injection",
"source": "db"
},
"input_skill": "Dependency Injection",
"llm_role": null,
"roles_from_db": [
{
"display_name": "Native Mobile Developer",
"id": 75,
"rationale": null,
"role_archetype": "Engineering",
"slug": "native-mobile-developer",
"source": "db"
}
]
},
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "PHP and Magento Extension Points",
"id": 391,
"rationale": "Core implementation surface for Magento customizations, including module code, event-driven hooks, and platform conventions. This is the primary language-and-framework cluster for building upgrade-safe storefront behavior.",
"slug": "php-and-magento-extension-points",
"source": "db"
},
"input_skill": "Dependency Injection",
"llm_role": null,
"roles_from_db": [
{
"display_name": "Magento Dev",
"id": 231,
"rationale": null,
"role_archetype": "Engineering",
"slug": "magento-dev",
"source": "db"
}
]
},
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Service Architecture and Design Patterns",
"id": 18,
"rationale": "Reusable backend design patterns used to structure service code and boundaries. Covers layering, dependency management, domain modeling, and maintainable service organization.",
"slug": "service-architecture-and-design-patterns",
"source": "db"
},
"input_skill": "Dependency Injection",
"llm_role": null,
"roles_from_db": [
{
"display_name": "Backend Developer",
"id": 1,
"rationale": null,
"role_archetype": "A Backend Engineer designs, builds, and maintains the server-side logic and data handling that power applications and services. They focus on implementing reliable business functionality, integrating with other systems, and ensuring the backend is scalable, maintainable, and observable.",
"slug": "backend-engineer",
"source": "db"
},
{
"display_name": "Java Backend Developer",
"id": 79,
"rationale": null,
"role_archetype": "Engineering",
"slug": "java-backend-developer",
"source": "db"
},
{
"display_name": "Kotlin Backend Developer",
"id": 84,
"rationale": null,
"role_archetype": "Engineering",
"slug": "kotlin-server-backend-developer",
"source": "db"
},
{
"display_name": "Node.js Backend Developer",
"id": 82,
"rationale": null,
"role_archetype": "Engineering",
"slug": "node-backend-developer",
"source": "db"
},
{
"display_name": "PHP Backend Developer",
"id": 86,
"rationale": null,
"role_archetype": "Engineering",
"slug": "php-backend-developer",
"source": "db"
},
{
"display_name": "Ruby Backend Developer",
"id": 85,
"rationale": null,
"role_archetype": "Engineering",
"slug": "ruby-backend-developer",
"source": "db"
},
{
"display_name": "Scala Backend Developer",
"id": 87,
"rationale": null,
"role_archetype": "Engineering",
"slug": "scala-backend-developer",
"source": "db"
}
]
},
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Application Architecture Patterns",
"id": 293,
"rationale": "Structural patterns for organizing Python backend code into maintainable modules, layers, and feature boundaries. This is a coherent cluster because senior backend developers are expected to refactor and shape service internals over time.",
"slug": "application-architecture-patterns",
"source": "db"
},
"input_skill": "SOLID",
"llm_role": null,
"roles_from_db": [
{
"display_name": ".NET Backend Developer",
"id": 83,
"rationale": null,
"role_archetype": "Engineering",
"slug": "dotnet-backend-developer",
"source": "db"
},
{
"display_name": "Python Backend Developer",
"id": 80,
"rationale": null,
"role_archetype": "Engineering",
"slug": "python-backend-developer",
"source": "db"
}
]
},
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Service Architecture and Design Patterns",
"id": 18,
"rationale": "Reusable backend design patterns used to structure service code and boundaries. Covers layering, dependency management, domain modeling, and maintainable service organization.",
"slug": "service-architecture-and-design-patterns",
"source": "db"
},
"input_skill": "SOLID",
"llm_role": null,
"roles_from_db": [
{
"display_name": "Backend Developer",
"id": 1,
"rationale": null,
"role_archetype": "A Backend Engineer designs, builds, and maintains the server-side logic and data handling that power applications and services. They focus on implementing reliable business functionality, integrating with other systems, and ensuring the backend is scalable, maintainable, and observable.",
"slug": "backend-engineer",
"source": "db"
},
{
"display_name": "Java Backend Developer",
"id": 79,
"rationale": null,
"role_archetype": "Engineering",
"slug": "java-backend-developer",
"source": "db"
},
{
"display_name": "Kotlin Backend Developer",
"id": 84,
"rationale": null,
"role_archetype": "Engineering",
"slug": "kotlin-server-backend-developer",
"source": "db"
},
{
"display_name": "Node.js Backend Developer",
"id": 82,
"rationale": null,
"role_archetype": "Engineering",
"slug": "node-backend-developer",
"source": "db"
},
{
"display_name": "PHP Backend Developer",
"id": 86,
"rationale": null,
"role_archetype": "Engineering",
"slug": "php-backend-developer",
"source": "db"
},
{
"display_name": "Ruby Backend Developer",
"id": 85,
"rationale": null,
"role_archetype": "Engineering",
"slug": "ruby-backend-developer",
"source": "db"
},
{
"display_name": "Scala Backend Developer",
"id": 87,
"rationale": null,
"role_archetype": "Engineering",
"slug": "scala-backend-developer",
"source": "db"
}
]
},
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "UI Frameworks and Rendering",
"id": 115,
"rationale": "Component frameworks and rendering models used to build browser screens, reusable UI, and interactive client flows. This is a core cluster because frontend engineers spend much of their time composing and updating view hierarchies.",
"slug": "ui-frameworks-and-rendering",
"source": "db"
},
"input_skill": "SOLID",
"llm_role": null,
"roles_from_db": [
{
"display_name": "Frontend Developer",
"id": 7,
"rationale": null,
"role_archetype": null,
"slug": "frontend-engineer",
"source": "db"
},
{
"display_name": "Fullstack Developer",
"id": 15,
"rationale": null,
"role_archetype": null,
"slug": "full-stack-engineer",
"source": "db"
},
{
"display_name": "Hybrid Mobile Developer",
"id": 11,
"rationale": null,
"role_archetype": null,
"slug": "hybrid-mobile-developer",
"source": "db"
},
{
"display_name": "Ionic Developer",
"id": 434,
"rationale": null,
"role_archetype": null,
"slug": "ionic-developer",
"source": "db"
},
{
"display_name": "Web Developer",
"id": 25,
"rationale": null,
"role_archetype": null,
"slug": "web-developer",
"source": "db"
}
]
},
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "CI/CD Pipeline Platforms",
"id": 150,
"rationale": "Systems used to define, run, and maintain automated build and deployment workflows. This cluster is coherent because the role owns delivery automation end to end, including pipeline reliability and promotion logic.",
"slug": "ci-cd-pipeline-platforms",
"source": "db"
},
"input_skill": "Azure DevOps",
"llm_role": null,
"roles_from_db": [
{
"display_name": "DevOps Engineer",
"id": 10,
"rationale": null,
"role_archetype": null,
"slug": "devops-engineer",
"source": "db"
}
]
}
],
"input_final_skills": [
"C#",
"WinForms",
"ASP.NET Core",
"MVC",
"REST",
"ASP.NET Web API",
"SQL Server",
"SignalR",
"Dependency Injection",
"SOLID",
"Windows Forms",
"Azure DevOps",
"MSI"
],
"input_llm_skills": [
"C#",
"WinForms",
"ASP.NET Core",
"MVC",
"REST",
"ASP.NET Web API",
"SQL Server",
"SignalR",
"Dependency Injection",
"SOLID",
"Windows Forms",
"Azure DevOps",
"MSI"
],
"new_aliases_persisted": 0,
"run_id": "b2f2b7dd-70e0-4efc-aa08-f3e38c9cf04f",
"skills_detail": [
{
"aliases_in_db": [
{
"alias_text": "C#",
"alias_type": "CANONICAL",
"id": 52,
"is_primary": true,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "C",
"alias_type": "CANONICAL",
"id": 1609,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "C# 1",
"alias_type": "VERSION",
"id": 53,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "C# 10",
"alias_type": "VERSION",
"id": 62,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "C# 11",
"alias_type": "VERSION",
"id": 63,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "C# 12",
"alias_type": "VERSION",
"id": 64,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "C# 13",
"alias_type": "VERSION",
"id": 65,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "C# 14",
"alias_type": "VERSION",
"id": 66,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "C# 2",
"alias_type": "VERSION",
"id": 54,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "C# 3",
"alias_type": "VERSION",
"id": 55,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "C# 4",
"alias_type": "VERSION",
"id": 56,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "C# 5",
"alias_type": "VERSION",
"id": 57,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "C# 6",
"alias_type": "VERSION",
"id": 58,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "C# 7",
"alias_type": "VERSION",
"id": 59,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "C# 8",
"alias_type": "VERSION",
"id": 60,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "C# 9",
"alias_type": "VERSION",
"id": 61,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "C# latest",
"alias_type": "VERSION",
"id": 1655,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "C#1",
"alias_type": "VERSION",
"id": 2228,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "C#10",
"alias_type": "VERSION",
"id": 2246,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "C#11",
"alias_type": "VERSION",
"id": 2247,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "C#12",
"alias_type": "VERSION",
"id": 2248,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "C#2",
"alias_type": "VERSION",
"id": 2229,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "C#3",
"alias_type": "VERSION",
"id": 2230,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "C#4",
"alias_type": "VERSION",
"id": 2231,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "C#5",
"alias_type": "VERSION",
"id": 2232,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "C#6",
"alias_type": "VERSION",
"id": 2233,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "C#7",
"alias_type": "VERSION",
"id": 2234,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "C#8",
"alias_type": "VERSION",
"id": 2235,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "C#9",
"alias_type": "VERSION",
"id": 2236,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "C++",
"alias_type": "CANONICAL",
"id": 418,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "C++03",
"alias_type": "VERSION",
"id": 420,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "C++11",
"alias_type": "VERSION",
"id": 421,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "C++14",
"alias_type": "VERSION",
"id": 422,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "C++17",
"alias_type": "VERSION",
"id": 423,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "C++20",
"alias_type": "VERSION",
"id": 424,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "C++23",
"alias_type": "VERSION",
"id": 425,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "C++26",
"alias_type": "VERSION",
"id": 426,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "C++98",
"alias_type": "VERSION",
"id": 427,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "c sharp",
"alias_type": "VERSION",
"id": 4765,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "c#",
"alias_type": "VERSION",
"id": 4763,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "cpp03",
"alias_type": "VERSION",
"id": 879,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "cpp11",
"alias_type": "VERSION",
"id": 880,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "cpp14",
"alias_type": "VERSION",
"id": 881,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "cpp17",
"alias_type": "VERSION",
"id": 882,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "cpp20",
"alias_type": "VERSION",
"id": 883,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "cpp23",
"alias_type": "VERSION",
"id": 884,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "cpp26",
"alias_type": "VERSION",
"id": 885,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "cpp98",
"alias_type": "VERSION",
"id": 886,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "csharp",
"alias_type": "VERSION",
"id": 4764,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "modern C++",
"alias_type": "VERSION",
"id": 428,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
}
],
"canonical": {
"category_id": 6,
"display_name": "C#",
"id": 4,
"is_also_category": false,
"is_extractable": true,
"skill_nature": "LANGUAGE",
"slug": "c",
"sub_category_id": 96,
"typical_lifespan": "EVERGREEN",
"volatility": "STABLE"
},
"dimensions": [
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "C# and .NET Languages",
"id": 362,
"rationale": "Primary implementation languages and runtime features used to build backend service logic in the .NET ecosystem. This is the core coding surface for request handling, domain logic, and service internals.",
"slug": "c-and-net-languages",
"source": "db"
},
"input_skill": "C#",
"llm_role": null,
"roles_from_db": [
{
"display_name": ".NET Backend Developer",
"id": 83,
"rationale": null,
"role_archetype": "Engineering",
"slug": "dotnet-backend-developer",
"source": "db"
}
]
},
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Cross-Platform App Languages",
"id": 167,
"rationale": "Languages used to implement shared mobile features across iOS and Android from a common codebase. This is the primary coding surface for hybrid app logic, UI behavior, and platform-specific branching.",
"slug": "cross-platform-app-languages",
"source": "db"
},
"input_skill": "C#",
"llm_role": null,
"roles_from_db": [
{
"display_name": "Hybrid Mobile Developer",
"id": 11,
"rationale": null,
"role_archetype": null,
"slug": "hybrid-mobile-developer",
"source": "db"
}
]
},
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Programming Languages",
"id": 1,
"rationale": "Primary implementation languages used to build client and server feature code. Full stack engineers need enough fluency to move across layers and implement product behavior end to end.",
"slug": "programming-languages",
"source": "db"
},
"input_skill": "C#",
"llm_role": null,
"roles_from_db": [
{
"display_name": "Backend Developer",
"id": 1,
"rationale": null,
"role_archetype": "A Backend Engineer designs, builds, and maintains the server-side logic and data handling that power applications and services. They focus on implementing reliable business functionality, integrating with other systems, and ensuring the backend is scalable, maintainable, and observable.",
"slug": "backend-engineer",
"source": "db"
},
{
"display_name": "Fullstack Developer",
"id": 15,
"rationale": null,
"role_archetype": null,
"slug": "full-stack-engineer",
"source": "db"
}
]
},
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "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": "C#",
"llm_role": null,
"roles_from_db": [
{
"display_name": "ML Engineer",
"id": 3,
"rationale": null,
"role_archetype": null,
"slug": "ml-engineer",
"source": "db"
},
{
"display_name": "MLOps Engineer",
"id": 16,
"rationale": null,
"role_archetype": null,
"slug": "ml-ops-engineer",
"source": "db"
}
]
},
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Programming Languages for XR",
"id": 97,
"rationale": "Primary implementation languages used to build immersive client features, interaction logic, and device-specific runtime behavior. This is the core coding surface for AR/VR experiences.",
"slug": "programming-languages-for-xr",
"source": "db"
},
"input_skill": "C#",
"llm_role": null,
"roles_from_db": [
{
"display_name": "AR/VR Engineer",
"id": 8,
"rationale": null,
"role_archetype": null,
"slug": "ar-vr-engineer",
"source": "db"
}
]
},
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "React Frontend Development",
"id": 96,
"rationale": "Building interactive web user interfaces with React.js, including component composition, state management, hooks, and rendering patterns. React.js belongs here because it is a core library for client-side UI development in modern web applications.",
"slug": "d_init_01",
"source": "db"
},
"input_skill": "C#",
"llm_role": null,
"roles_from_db": []
},
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Sitecore Development Languages",
"id": 438,
"rationale": "Core implementation languages and markup used to build Sitecore customizations, rendering logic, and site behavior. This is the primary authoring surface for Sitecore-specific code and templates.",
"slug": "sitecore-development-languages",
"source": "db"
},
"input_skill": "C#",
"llm_role": null,
"roles_from_db": [
{
"display_name": "Sitecore Dev",
"id": 233,
"rationale": null,
"role_archetype": "Engineering",
"slug": "sitecore-dev",
"source": "db"
}
]
},
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Video Codec Languages and DSLs",
"id": 225,
"rationale": "Implementation languages and codec-specific description languages used to build compression, decoding, and transform logic. This is the primary coding surface for codec behavior and bitstream manipulation.",
"slug": "video-codec-languages-and-dsls",
"source": "db"
},
"input_skill": "C#",
"llm_role": null,
"roles_from_db": [
{
"display_name": "Video Codec Engineer",
"id": 22,
"rationale": null,
"role_archetype": null,
"slug": "video-codec-engineer",
"source": "db"
}
]
}
],
"input_skill": "C#",
"matched_via": "alias",
"new_alias_persisted": false,
"new_alias_text": null,
"new_skill_meta": null,
"source_tag": "db",
"was_in_llm_skills": true
},
{
"aliases_in_db": [],
"canonical": null,
"dimensions": [],
"input_skill": "WinForms",
"matched_via": null,
"new_alias_persisted": false,
"new_alias_text": null,
"new_skill_meta": {
"derived": {
"category": "Web Frameworks",
"skill_nature": "TOOL",
"sub_category": "general",
"typical_lifespan": "MULTI_YEAR",
"version_strategy": "UNVERSIONED",
"volatility": "MEDIUM"
},
"enrichment": null,
"keep_log": [],
"locked_dimensions": [],
"merge_log": [],
"placed": null,
"relationships": null,
"skill_id": "winforms",
"split_log": [],
"typed": null,
"warnings": []
},
"source_tag": "llm",
"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"
},
{
"alias_text": "asp.net core",
"alias_type": "VERSION",
"id": 2298,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "asp.net core 8",
"alias_type": "VERSION",
"id": 2300,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "asp.net core/.net 8",
"alias_type": "VERSION",
"id": 2301,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "aspnetcore",
"alias_type": "VERSION",
"id": 4784,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "aspnetcore 8",
"alias_type": "VERSION",
"id": 2299,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "net 8",
"alias_type": "VERSION",
"id": 2297,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "net8",
"alias_type": "VERSION",
"id": 2296,
"is_primary": false,
"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": "ASP.NET Core Web Frameworks",
"id": 363,
"rationale": "Server-side web frameworks and hosting models used to build HTTP APIs, middleware, filters, and request pipelines. This cluster is coherent because it defines how backend services receive, process, and return requests.",
"slug": "asp-net-core-web-frameworks",
"source": "db"
},
"input_skill": "ASP.NET Core",
"llm_role": null,
"roles_from_db": [
{
"display_name": ".NET Backend Developer",
"id": 83,
"rationale": null,
"role_archetype": "Engineering",
"slug": "dotnet-backend-developer",
"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 Developer",
"id": 1,
"rationale": null,
"role_archetype": "A Backend Engineer designs, builds, and maintains the server-side logic and data handling that power applications and services. They focus on implementing reliable business functionality, integrating with other systems, and ensuring the backend is scalable, maintainable, and observable.",
"slug": "backend-engineer",
"source": "db"
},
{
"display_name": "Fullstack Developer",
"id": 15,
"rationale": null,
"role_archetype": null,
"slug": "full-stack-engineer",
"source": "db"
},
{
"display_name": "Java Backend Developer",
"id": 79,
"rationale": null,
"role_archetype": "Engineering",
"slug": "java-backend-developer",
"source": "db"
},
{
"display_name": "Node.js Backend Developer",
"id": 82,
"rationale": null,
"role_archetype": "Engineering",
"slug": "node-backend-developer",
"source": "db"
},
{
"display_name": "PHP Backend Developer",
"id": 86,
"rationale": null,
"role_archetype": "Engineering",
"slug": "php-backend-developer",
"source": "db"
},
{
"display_name": "Python Backend Developer",
"id": 80,
"rationale": null,
"role_archetype": "Engineering",
"slug": "python-backend-developer",
"source": "db"
}
]
}
],
"input_skill": "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": [
{
"alias_text": "MVC",
"alias_type": "CANONICAL",
"id": 831,
"is_primary": true,
"match_strategy": "CASE_INSENSITIVE"
}
],
"canonical": {
"category_id": 1,
"display_name": "MVC",
"id": 505,
"is_also_category": false,
"is_extractable": true,
"skill_nature": "PATTERN",
"slug": "mvc",
"sub_category_id": 2462,
"typical_lifespan": "EVERGREEN",
"volatility": "STABLE"
},
"dimensions": [
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "ASP.NET Core Web Frameworks",
"id": 363,
"rationale": "Server-side web frameworks and hosting models used to build HTTP APIs, middleware, filters, and request pipelines. This cluster is coherent because it defines how backend services receive, process, and return requests.",
"slug": "asp-net-core-web-frameworks",
"source": "db"
},
"input_skill": "MVC",
"llm_role": null,
"roles_from_db": [
{
"display_name": ".NET Backend Developer",
"id": 83,
"rationale": null,
"role_archetype": "Engineering",
"slug": "dotnet-backend-developer",
"source": "db"
}
]
},
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "App Architecture and Dependency Injection",
"id": 94,
"rationale": "Structural patterns used to organize iOS code into testable, maintainable feature modules and layers. iOS engineers use these patterns to separate UI, state, and service integration concerns.",
"slug": "app-architecture-and-dependency-injection",
"source": "db"
},
"input_skill": "MVC",
"llm_role": null,
"roles_from_db": [
{
"display_name": "Android Developer",
"id": 4,
"rationale": null,
"role_archetype": null,
"slug": "android-engineer",
"source": "db"
},
{
"display_name": "iOS Developer",
"id": 6,
"rationale": null,
"role_archetype": null,
"slug": "ios-engineer",
"source": "db"
}
]
},
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Application Architecture and Code Organization",
"id": 220,
"rationale": "Structural patterns for organizing product code into maintainable modules, layers, and feature boundaries. Full stack engineers need this to keep cross-layer feature work understandable as the product grows.",
"slug": "application-architecture-and-code-organization",
"source": "db"
},
"input_skill": "MVC",
"llm_role": null,
"roles_from_db": [
{
"display_name": "Fullstack Developer",
"id": 15,
"rationale": null,
"role_archetype": null,
"slug": "full-stack-engineer",
"source": "db"
}
]
},
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Native Mobile App Architecture and Dependency Injection",
"id": 273,
"rationale": "Structural patterns for organizing native mobile application code into maintainable, testable modules, layers, and feature boundaries. This includes app architecture patterns such as MVVM, MVC, MVI, VIPER, and Clean Architecture; dependency injection frameworks and patterns such as Hilt, Dagger, and Koin; and code organization techniques such as modularization, feature modules, repository pattern, and use-case layering to separate UI, state, data, and platform concerns across a growing codebase.",
"slug": "native-mobile-app-architecture-and-dependency-injection",
"source": "db"
},
"input_skill": "MVC",
"llm_role": null,
"roles_from_db": [
{
"display_name": "Native Mobile Developer",
"id": 75,
"rationale": null,
"role_archetype": "Engineering",
"slug": "native-mobile-developer",
"source": "db"
}
]
}
],
"input_skill": "MVC",
"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": "REST",
"alias_type": "CANONICAL",
"id": 106,
"is_primary": true,
"match_strategy": "CASE_INSENSITIVE"
}
],
"canonical": {
"category_id": 2,
"display_name": "REST",
"id": 11,
"is_also_category": false,
"is_extractable": true,
"skill_nature": "CONCEPT",
"slug": "rest",
"sub_category_id": 2122,
"typical_lifespan": "EVERGREEN",
"volatility": "STABLE"
},
"dimensions": [
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "API Design and Contracts",
"id": 3,
"rationale": "Designing request/response shapes and the rules that govern client-server interaction. This cluster is coherent because full stack engineers often own the contract between UI behavior and backend implementation.",
"slug": "api-design-and-contracts",
"source": "db"
},
"input_skill": "REST",
"llm_role": null,
"roles_from_db": [
{
"display_name": "Backend Developer",
"id": 1,
"rationale": null,
"role_archetype": "A Backend Engineer designs, builds, and maintains the server-side logic and data handling that power applications and services. They focus on implementing reliable business functionality, integrating with other systems, and ensuring the backend is scalable, maintainable, and observable.",
"slug": "backend-engineer",
"source": "db"
},
{
"display_name": "Fullstack Developer",
"id": 15,
"rationale": null,
"role_archetype": null,
"slug": "full-stack-engineer",
"source": "db"
}
]
},
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "API Interface and Contract Design",
"id": 289,
"rationale": "Designing backend service interfaces and contracts that other systems consume, including endpoint and operation shape, request/response payloads, schema and validation, pagination, filtering, idempotency, versioning, status codes, and backward compatibility across REST, GraphQL, gRPC, and OpenAPI-based APIs.",
"slug": "api-interface-and-contract-design",
"source": "db"
},
"input_skill": "REST",
"llm_role": null,
"roles_from_db": [
{
"display_name": ".NET Backend Developer",
"id": 83,
"rationale": null,
"role_archetype": "Engineering",
"slug": "dotnet-backend-developer",
"source": "db"
},
{
"display_name": "Go Backend Developer",
"id": 81,
"rationale": null,
"role_archetype": "Engineering",
"slug": "go-backend-developer",
"source": "db"
},
{
"display_name": "Kotlin Backend Developer",
"id": 84,
"rationale": null,
"role_archetype": "Engineering",
"slug": "kotlin-server-backend-developer",
"source": "db"
},
{
"display_name": "Node.js Backend Developer",
"id": 82,
"rationale": null,
"role_archetype": "Engineering",
"slug": "node-backend-developer",
"source": "db"
},
{
"display_name": "PHP Backend Developer",
"id": 86,
"rationale": null,
"role_archetype": "Engineering",
"slug": "php-backend-developer",
"source": "db"
},
{
"display_name": "Python Backend Developer",
"id": 80,
"rationale": null,
"role_archetype": "Engineering",
"slug": "python-backend-developer",
"source": "db"
},
{
"display_name": "Ruby Backend Developer",
"id": 85,
"rationale": null,
"role_archetype": "Engineering",
"slug": "ruby-backend-developer",
"source": "db"
},
{
"display_name": "Scala Backend Developer",
"id": 87,
"rationale": null,
"role_archetype": "Engineering",
"slug": "scala-backend-developer",
"source": "db"
}
]
},
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Integration Protocols \u0026 Standards",
"id": 271,
"rationale": "Standards and protocols for integrating Pega applications.",
"slug": "integration-protocols-standards",
"source": "db"
},
"input_skill": "REST",
"llm_role": null,
"roles_from_db": [
{
"display_name": "Pega Developer",
"id": 24,
"rationale": null,
"role_archetype": null,
"slug": "pega-developer",
"source": "db"
}
]
},
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Standards \u0026 Protocols Compliance",
"id": 452,
"rationale": "Encompasses key web and data standards, protocols, and compliance requirements relevant to Sitecore implementations.",
"slug": "standards-protocols-compliance",
"source": "db"
},
"input_skill": "REST",
"llm_role": null,
"roles_from_db": [
{
"display_name": "Sitecore Dev",
"id": 233,
"rationale": null,
"role_archetype": "Engineering",
"slug": "sitecore-dev",
"source": "db"
}
]
}
],
"input_skill": "REST",
"matched_via": "alias",
"new_alias_persisted": false,
"new_alias_text": null,
"new_skill_meta": null,
"source_tag": "db",
"was_in_llm_skills": true
},
{
"aliases_in_db": [],
"canonical": null,
"dimensions": [],
"input_skill": "ASP.NET Web API",
"matched_via": null,
"new_alias_persisted": false,
"new_alias_text": null,
"new_skill_meta": {
"derived": {
"category": "Web Frameworks",
"skill_nature": "TOOL",
"sub_category": "general",
"typical_lifespan": "MULTI_YEAR",
"version_strategy": "UNVERSIONED",
"volatility": "MEDIUM"
},
"enrichment": null,
"keep_log": [],
"locked_dimensions": [],
"merge_log": [],
"placed": null,
"relationships": null,
"skill_id": "asp-net-web-api",
"split_log": [],
"typed": null,
"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": ".NET Backend Developer",
"id": 83,
"rationale": null,
"role_archetype": "Engineering",
"slug": "dotnet-backend-developer",
"source": "db"
},
{
"display_name": "Backend Developer",
"id": 1,
"rationale": null,
"role_archetype": "A Backend Engineer designs, builds, and maintains the server-side logic and data handling that power applications and services. They focus on implementing reliable business functionality, integrating with other systems, and ensuring the backend is scalable, maintainable, and observable.",
"slug": "backend-engineer",
"source": "db"
},
{
"display_name": "Kotlin Backend Developer",
"id": 84,
"rationale": null,
"role_archetype": "Engineering",
"slug": "kotlin-server-backend-developer",
"source": "db"
},
{
"display_name": "Node.js Backend Developer",
"id": 82,
"rationale": null,
"role_archetype": "Engineering",
"slug": "node-backend-developer",
"source": "db"
},
{
"display_name": "Python Backend Developer",
"id": 80,
"rationale": null,
"role_archetype": "Engineering",
"slug": "python-backend-developer",
"source": "db"
},
{
"display_name": "Ruby Backend Developer",
"id": 85,
"rationale": null,
"role_archetype": "Engineering",
"slug": "ruby-backend-developer",
"source": "db"
},
{
"display_name": "Scala Backend Developer",
"id": 87,
"rationale": null,
"role_archetype": "Engineering",
"slug": "scala-backend-developer",
"source": "db"
}
]
}
],
"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": [],
"canonical": null,
"dimensions": [],
"input_skill": "SignalR",
"matched_via": null,
"new_alias_persisted": false,
"new_alias_text": null,
"new_skill_meta": {
"derived": {
"category": "Web Frameworks",
"skill_nature": "TOOL",
"sub_category": "general",
"typical_lifespan": "MULTI_YEAR",
"version_strategy": "UNVERSIONED",
"volatility": "MEDIUM"
},
"enrichment": null,
"keep_log": [],
"locked_dimensions": [],
"merge_log": [],
"placed": null,
"relationships": null,
"skill_id": "signalr",
"split_log": [],
"typed": null,
"warnings": []
},
"source_tag": "llm",
"was_in_llm_skills": true
},
{
"aliases_in_db": [
{
"alias_text": "dependency injection",
"alias_type": "CANONICAL",
"id": 229,
"is_primary": true,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "Dependency Injection",
"alias_type": "CANONICAL",
"id": 5279,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "Dependency injection",
"alias_type": "CANONICAL",
"id": 3524,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
}
],
"canonical": {
"category_id": 2,
"display_name": "dependency injection",
"id": 88,
"is_also_category": false,
"is_extractable": true,
"skill_nature": "CONCEPT",
"slug": "dependency-injection",
"sub_category_id": 2482,
"typical_lifespan": "EVERGREEN",
"volatility": "STABLE"
},
"dimensions": [
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Angular Component Model and Templates",
"id": 303,
"rationale": "Core Angular framework surface for building reusable UI, composing views, and wiring component behavior. This is the main application substrate for browser features in this role.",
"slug": "angular-component-model-and-templates",
"source": "db"
},
"input_skill": "Dependency Injection",
"llm_role": null,
"roles_from_db": [
{
"display_name": "Angular Frontend Developer",
"id": 90,
"rationale": null,
"role_archetype": "Engineering",
"slug": "angular-frontend-developer",
"source": "db"
}
]
},
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "App Architecture and Dependency Injection",
"id": 94,
"rationale": "Structural patterns used to organize iOS code into testable, maintainable feature modules and layers. iOS engineers use these patterns to separate UI, state, and service integration concerns.",
"slug": "app-architecture-and-dependency-injection",
"source": "db"
},
"input_skill": "Dependency Injection",
"llm_role": null,
"roles_from_db": [
{
"display_name": "Android Developer",
"id": 4,
"rationale": null,
"role_archetype": null,
"slug": "android-engineer",
"source": "db"
},
{
"display_name": "iOS Developer",
"id": 6,
"rationale": null,
"role_archetype": null,
"slug": "ios-engineer",
"source": "db"
}
]
},
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Application Architecture Patterns",
"id": 293,
"rationale": "Structural patterns for organizing Python backend code into maintainable modules, layers, and feature boundaries. This is a coherent cluster because senior backend developers are expected to refactor and shape service internals over time.",
"slug": "application-architecture-patterns",
"source": "db"
},
"input_skill": "Dependency Injection",
"llm_role": null,
"roles_from_db": [
{
"display_name": ".NET Backend Developer",
"id": 83,
"rationale": null,
"role_archetype": "Engineering",
"slug": "dotnet-backend-developer",
"source": "db"
},
{
"display_name": "Python Backend Developer",
"id": 80,
"rationale": null,
"role_archetype": "Engineering",
"slug": "python-backend-developer",
"source": "db"
}
]
},
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Application Architecture and Code Organization",
"id": 220,
"rationale": "Structural patterns for organizing product code into maintainable modules, layers, and feature boundaries. Full stack engineers need this to keep cross-layer feature work understandable as the product grows.",
"slug": "application-architecture-and-code-organization",
"source": "db"
},
"input_skill": "Dependency Injection",
"llm_role": null,
"roles_from_db": [
{
"display_name": "Fullstack Developer",
"id": 15,
"rationale": null,
"role_archetype": null,
"slug": "full-stack-engineer",
"source": "db"
}
]
},
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Backend Application Architecture and Code Organization",
"id": 366,
"rationale": "Structural patterns for organizing backend application code into maintainable modules, layers, and boundaries so services remain testable, modular, evolvable, and easy to refactor. This includes clean architecture, hexagonal architecture, layered architecture, dependency injection, service layers, package or module boundaries, modularization, domain-driven design, SOLID, CQRS, and mediator-style patterns. It excludes API endpoint syntax, database schema design, deployment topology, and frontend architecture.",
"slug": "backend-application-architecture-and-code-organization",
"source": "db"
},
"input_skill": "Dependency Injection",
"llm_role": null,
"roles_from_db": [
{
"display_name": "Go Backend Developer",
"id": 81,
"rationale": null,
"role_archetype": "Engineering",
"slug": "go-backend-developer",
"source": "db"
}
]
},
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Flutter App Architecture",
"id": 316,
"rationale": "Structural patterns used to organize Flutter code into maintainable modules, layers, and feature boundaries. Senior Flutter developers often own these patterns to keep shared app delivery scalable across teams and releases.",
"slug": "flutter-app-architecture",
"source": "db"
},
"input_skill": "Dependency Injection",
"llm_role": null,
"roles_from_db": [
{
"display_name": "Flutter Developer",
"id": 74,
"rationale": null,
"role_archetype": "Engineering",
"slug": "flutter-developer",
"source": "db"
}
]
},
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Ionic App Architecture",
"id": 384,
"rationale": "Structural patterns for organizing Ionic code into maintainable modules, layers, and feature boundaries. Senior Ionic developers often define these patterns to keep shared app behavior consistent across devices and releases.",
"slug": "ionic-app-architecture",
"source": "db"
},
"input_skill": "Dependency Injection",
"llm_role": null,
"roles_from_db": [
{
"display_name": "Ionic Developer",
"id": 434,
"rationale": null,
"role_archetype": null,
"slug": "ionic-developer",
"source": "db"
}
]
},
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Mobile Architecture and Code Organization",
"id": 170,
"rationale": "Structural patterns used to organize shared mobile code into maintainable modules, layers, and feature boundaries. Senior hybrid developers often own these patterns to keep cross-platform code testable and adaptable to platform exceptions.",
"slug": "mobile-architecture-and-code-organization",
"source": "db"
},
"input_skill": "Dependency Injection",
"llm_role": null,
"roles_from_db": [
{
"display_name": "Hybrid Mobile Developer",
"id": 11,
"rationale": null,
"role_archetype": null,
"slug": "hybrid-mobile-developer",
"source": "db"
},
{
"display_name": "React Native Developer",
"id": 73,
"rationale": null,
"role_archetype": "Engineering",
"slug": "react-native-developer",
"source": "db"
}
]
},
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Native Mobile App Architecture and Dependency Injection",
"id": 273,
"rationale": "Structural patterns for organizing native mobile application code into maintainable, testable modules, layers, and feature boundaries. This includes app architecture patterns such as MVVM, MVC, MVI, VIPER, and Clean Architecture; dependency injection frameworks and patterns such as Hilt, Dagger, and Koin; and code organization techniques such as modularization, feature modules, repository pattern, and use-case layering to separate UI, state, data, and platform concerns across a growing codebase.",
"slug": "native-mobile-app-architecture-and-dependency-injection",
"source": "db"
},
"input_skill": "Dependency Injection",
"llm_role": null,
"roles_from_db": [
{
"display_name": "Native Mobile Developer",
"id": 75,
"rationale": null,
"role_archetype": "Engineering",
"slug": "native-mobile-developer",
"source": "db"
}
]
},
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "PHP and Magento Extension Points",
"id": 391,
"rationale": "Core implementation surface for Magento customizations, including module code, event-driven hooks, and platform conventions. This is the primary language-and-framework cluster for building upgrade-safe storefront behavior.",
"slug": "php-and-magento-extension-points",
"source": "db"
},
"input_skill": "Dependency Injection",
"llm_role": null,
"roles_from_db": [
{
"display_name": "Magento Dev",
"id": 231,
"rationale": null,
"role_archetype": "Engineering",
"slug": "magento-dev",
"source": "db"
}
]
},
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Service Architecture and Design Patterns",
"id": 18,
"rationale": "Reusable backend design patterns used to structure service code and boundaries. Covers layering, dependency management, domain modeling, and maintainable service organization.",
"slug": "service-architecture-and-design-patterns",
"source": "db"
},
"input_skill": "Dependency Injection",
"llm_role": null,
"roles_from_db": [
{
"display_name": "Backend Developer",
"id": 1,
"rationale": null,
"role_archetype": "A Backend Engineer designs, builds, and maintains the server-side logic and data handling that power applications and services. They focus on implementing reliable business functionality, integrating with other systems, and ensuring the backend is scalable, maintainable, and observable.",
"slug": "backend-engineer",
"source": "db"
},
{
"display_name": "Java Backend Developer",
"id": 79,
"rationale": null,
"role_archetype": "Engineering",
"slug": "java-backend-developer",
"source": "db"
},
{
"display_name": "Kotlin Backend Developer",
"id": 84,
"rationale": null,
"role_archetype": "Engineering",
"slug": "kotlin-server-backend-developer",
"source": "db"
},
{
"display_name": "Node.js Backend Developer",
"id": 82,
"rationale": null,
"role_archetype": "Engineering",
"slug": "node-backend-developer",
"source": "db"
},
{
"display_name": "PHP Backend Developer",
"id": 86,
"rationale": null,
"role_archetype": "Engineering",
"slug": "php-backend-developer",
"source": "db"
},
{
"display_name": "Ruby Backend Developer",
"id": 85,
"rationale": null,
"role_archetype": "Engineering",
"slug": "ruby-backend-developer",
"source": "db"
},
{
"display_name": "Scala Backend Developer",
"id": 87,
"rationale": null,
"role_archetype": "Engineering",
"slug": "scala-backend-developer",
"source": "db"
}
]
}
],
"input_skill": "Dependency Injection",
"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": "SOLID",
"alias_type": "CANONICAL",
"id": 4820,
"is_primary": true,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "Solid",
"alias_type": "CANONICAL",
"id": 1098,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
}
],
"canonical": {
"category_id": 2,
"display_name": "SOLID",
"id": 614,
"is_also_category": false,
"is_extractable": true,
"skill_nature": "CONCEPT",
"slug": "solid",
"sub_category_id": 2976,
"typical_lifespan": "EVERGREEN",
"volatility": "STABLE"
},
"dimensions": [
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Application Architecture Patterns",
"id": 293,
"rationale": "Structural patterns for organizing Python backend code into maintainable modules, layers, and feature boundaries. This is a coherent cluster because senior backend developers are expected to refactor and shape service internals over time.",
"slug": "application-architecture-patterns",
"source": "db"
},
"input_skill": "SOLID",
"llm_role": null,
"roles_from_db": [
{
"display_name": ".NET Backend Developer",
"id": 83,
"rationale": null,
"role_archetype": "Engineering",
"slug": "dotnet-backend-developer",
"source": "db"
},
{
"display_name": "Python Backend Developer",
"id": 80,
"rationale": null,
"role_archetype": "Engineering",
"slug": "python-backend-developer",
"source": "db"
}
]
},
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Service Architecture and Design Patterns",
"id": 18,
"rationale": "Reusable backend design patterns used to structure service code and boundaries. Covers layering, dependency management, domain modeling, and maintainable service organization.",
"slug": "service-architecture-and-design-patterns",
"source": "db"
},
"input_skill": "SOLID",
"llm_role": null,
"roles_from_db": [
{
"display_name": "Backend Developer",
"id": 1,
"rationale": null,
"role_archetype": "A Backend Engineer designs, builds, and maintains the server-side logic and data handling that power applications and services. They focus on implementing reliable business functionality, integrating with other systems, and ensuring the backend is scalable, maintainable, and observable.",
"slug": "backend-engineer",
"source": "db"
},
{
"display_name": "Java Backend Developer",
"id": 79,
"rationale": null,
"role_archetype": "Engineering",
"slug": "java-backend-developer",
"source": "db"
},
{
"display_name": "Kotlin Backend Developer",
"id": 84,
"rationale": null,
"role_archetype": "Engineering",
"slug": "kotlin-server-backend-developer",
"source": "db"
},
{
"display_name": "Node.js Backend Developer",
"id": 82,
"rationale": null,
"role_archetype": "Engineering",
"slug": "node-backend-developer",
"source": "db"
},
{
"display_name": "PHP Backend Developer",
"id": 86,
"rationale": null,
"role_archetype": "Engineering",
"slug": "php-backend-developer",
"source": "db"
},
{
"display_name": "Ruby Backend Developer",
"id": 85,
"rationale": null,
"role_archetype": "Engineering",
"slug": "ruby-backend-developer",
"source": "db"
},
{
"display_name": "Scala Backend Developer",
"id": 87,
"rationale": null,
"role_archetype": "Engineering",
"slug": "scala-backend-developer",
"source": "db"
}
]
},
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "UI Frameworks and Rendering",
"id": 115,
"rationale": "Component frameworks and rendering models used to build browser screens, reusable UI, and interactive client flows. This is a core cluster because frontend engineers spend much of their time composing and updating view hierarchies.",
"slug": "ui-frameworks-and-rendering",
"source": "db"
},
"input_skill": "SOLID",
"llm_role": null,
"roles_from_db": [
{
"display_name": "Frontend Developer",
"id": 7,
"rationale": null,
"role_archetype": null,
"slug": "frontend-engineer",
"source": "db"
},
{
"display_name": "Fullstack Developer",
"id": 15,
"rationale": null,
"role_archetype": null,
"slug": "full-stack-engineer",
"source": "db"
},
{
"display_name": "Hybrid Mobile Developer",
"id": 11,
"rationale": null,
"role_archetype": null,
"slug": "hybrid-mobile-developer",
"source": "db"
},
{
"display_name": "Ionic Developer",
"id": 434,
"rationale": null,
"role_archetype": null,
"slug": "ionic-developer",
"source": "db"
},
{
"display_name": "Web Developer",
"id": 25,
"rationale": null,
"role_archetype": null,
"slug": "web-developer",
"source": "db"
}
]
}
],
"input_skill": "SOLID",
"matched_via": "alias",
"new_alias_persisted": false,
"new_alias_text": null,
"new_skill_meta": null,
"source_tag": "db",
"was_in_llm_skills": true
},
{
"aliases_in_db": [],
"canonical": null,
"dimensions": [],
"input_skill": "Windows Forms",
"matched_via": null,
"new_alias_persisted": false,
"new_alias_text": null,
"new_skill_meta": {
"derived": {
"category": "Web Frameworks",
"skill_nature": "TOOL",
"sub_category": "general",
"typical_lifespan": "MULTI_YEAR",
"version_strategy": "UNVERSIONED",
"volatility": "MEDIUM"
},
"enrichment": null,
"keep_log": [],
"locked_dimensions": [],
"merge_log": [],
"placed": null,
"relationships": null,
"skill_id": "windows-forms",
"split_log": [],
"typed": null,
"warnings": []
},
"source_tag": "llm",
"was_in_llm_skills": true
},
{
"aliases_in_db": [
{
"alias_text": "Azure DevOps",
"alias_type": "CANONICAL",
"id": 1850,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
}
],
"canonical": {
"category_id": 9,
"display_name": "Azure DevOps",
"id": 1214,
"is_also_category": false,
"is_extractable": true,
"skill_nature": "PLATFORM",
"slug": "azure-devops",
"sub_category_id": 170,
"typical_lifespan": "EVERGREEN",
"volatility": "STABLE"
},
"dimensions": [
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "CI/CD Pipeline Platforms",
"id": 150,
"rationale": "Systems used to define, run, and maintain automated build and deployment workflows. This cluster is coherent because the role owns delivery automation end to end, including pipeline reliability and promotion logic.",
"slug": "ci-cd-pipeline-platforms",
"source": "db"
},
"input_skill": "Azure DevOps",
"llm_role": null,
"roles_from_db": [
{
"display_name": "DevOps Engineer",
"id": 10,
"rationale": null,
"role_archetype": null,
"slug": "devops-engineer",
"source": "db"
}
]
}
],
"input_skill": "Azure DevOps",
"matched_via": "alias",
"new_alias_persisted": false,
"new_alias_text": null,
"new_skill_meta": null,
"source_tag": "db",
"was_in_llm_skills": true
},
{
"aliases_in_db": [],
"canonical": null,
"dimensions": [],
"input_skill": "MSI",
"matched_via": null,
"new_alias_persisted": false,
"new_alias_text": null,
"new_skill_meta": {
"derived": {
"category": "Deployment Tools",
"skill_nature": "TOOL",
"sub_category": "general",
"typical_lifespan": "MULTI_YEAR",
"version_strategy": "UNVERSIONED",
"volatility": "MEDIUM"
},
"enrichment": null,
"keep_log": [],
"locked_dimensions": [],
"merge_log": [],
"placed": null,
"relationships": null,
"skill_id": "msi",
"split_log": [],
"typed": null,
"warnings": []
},
"source_tag": "llm",
"was_in_llm_skills": true
}
],
"unmatched_skills": [
"WinForms",
"ASP.NET Web API",
"SignalR",
"Windows Forms",
"MSI"
]
}
API 3 — final-role-output
{
"chosen_role": {
"display_name": "Backend Developer",
"id": 1,
"rationale": "Domain=Software Engineering \u2192 sub-role dotnet-backend-developer; The JD is centered on C#/.NET backend and application development with APIs, SQL Server, SignalR, and deployment tooling, which best matches Backend Developer.",
"role_archetype": "A Backend Engineer designs, builds, and maintains the server-side logic and data handling that power applications and services. They focus on implementing reliable business functionality, integrating with other systems, and ensuring the backend is scalable, maintainable, and observable.",
"slug": "backend-engineer",
"source": "db"
},
"chosen_role_resolution": "in_db",
"final_input_skills": [
{
"skill": "C#",
"tag": "in_db"
},
{
"skill": "WinForms",
"tag": "new"
},
{
"skill": "ASP.NET Core",
"tag": "in_db"
},
{
"skill": "MVC",
"tag": "in_db"
},
{
"skill": "REST",
"tag": "in_db"
},
{
"skill": "ASP.NET Web API",
"tag": "new"
},
{
"skill": "SQL Server",
"tag": "in_db"
},
{
"skill": "SignalR",
"tag": "new"
},
{
"skill": "Dependency Injection",
"tag": "in_db"
},
{
"skill": "SOLID",
"tag": "in_db"
},
{
"skill": "Windows Forms",
"tag": "new"
},
{
"skill": "Azure DevOps",
"tag": "in_db"
},
{
"skill": "MSI",
"tag": "new"
}
],
"llm_cost_api1_usd": null,
"llm_cost_api2_usd": null,
"llm_cost_api3_usd": null,
"llm_cost_total_usd": null,
"persistence": {
"items": [
{
"chosen_role_id": 1,
"dimension": {
"difficulty_hint": "well_known",
"display_name": "C# and .NET Languages",
"id": 362,
"rationale": "Primary implementation languages and runtime features used to build backend service logic in the .NET ecosystem. This is the core coding surface for request handling, domain logic, and service internals.",
"slug": "c-and-net-languages",
"source": "db"
},
"dimension_id": 362,
"input_skill": "C#",
"llm_role": null,
"matched_chosen_role": false,
"outcome_line": "Existing dimension (library) \u00b7 Role\u2194dimension skipped (dimension not under chosen role)",
"role_dimension_saved": false,
"roles_from_db": [
{
"display_name": ".NET Backend Developer",
"id": 83,
"rationale": null,
"role_archetype": "Engineering",
"slug": "dotnet-backend-developer",
"source": "db"
}
],
"skill_dimension_saved": true,
"skill_id": 4,
"skill_tag": "in_db",
"skipped_reason": null
},
{
"chosen_role_id": 1,
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Cross-Platform App Languages",
"id": 167,
"rationale": "Languages used to implement shared mobile features across iOS and Android from a common codebase. This is the primary coding surface for hybrid app logic, UI behavior, and platform-specific branching.",
"slug": "cross-platform-app-languages",
"source": "db"
},
"dimension_id": 167,
"input_skill": "C#",
"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": "Hybrid Mobile Developer",
"id": 11,
"rationale": null,
"role_archetype": null,
"slug": "hybrid-mobile-developer",
"source": "db"
}
],
"skill_dimension_saved": true,
"skill_id": 4,
"skill_tag": "in_db",
"skipped_reason": null
},
{
"chosen_role_id": 1,
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Programming Languages",
"id": 1,
"rationale": "Primary implementation languages used to build client and server feature code. Full stack engineers need enough fluency to move across layers and implement product behavior end to end.",
"slug": "programming-languages",
"source": "db"
},
"dimension_id": 1,
"input_skill": "C#",
"llm_role": null,
"matched_chosen_role": true,
"outcome_line": "Existing dimension (library) \u00b7 Role\u2194dimension saved",
"role_dimension_saved": true,
"roles_from_db": [
{
"display_name": "Backend Developer",
"id": 1,
"rationale": null,
"role_archetype": "A Backend Engineer designs, builds, and maintains the server-side logic and data handling that power applications and services. They focus on implementing reliable business functionality, integrating with other systems, and ensuring the backend is scalable, maintainable, and observable.",
"slug": "backend-engineer",
"source": "db"
},
{
"display_name": "Fullstack Developer",
"id": 15,
"rationale": null,
"role_archetype": null,
"slug": "full-stack-engineer",
"source": "db"
}
],
"skill_dimension_saved": true,
"skill_id": 4,
"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": "C#",
"llm_role": null,
"matched_chosen_role": false,
"outcome_line": "Existing dimension (library) \u00b7 Role\u2194dimension skipped (dimension not under chosen role)",
"role_dimension_saved": false,
"roles_from_db": [
{
"display_name": "ML Engineer",
"id": 3,
"rationale": null,
"role_archetype": null,
"slug": "ml-engineer",
"source": "db"
},
{
"display_name": "MLOps Engineer",
"id": 16,
"rationale": null,
"role_archetype": null,
"slug": "ml-ops-engineer",
"source": "db"
}
],
"skill_dimension_saved": true,
"skill_id": 4,
"skill_tag": "in_db",
"skipped_reason": null
},
{
"chosen_role_id": 1,
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Programming Languages for XR",
"id": 97,
"rationale": "Primary implementation languages used to build immersive client features, interaction logic, and device-specific runtime behavior. This is the core coding surface for AR/VR experiences.",
"slug": "programming-languages-for-xr",
"source": "db"
},
"dimension_id": 97,
"input_skill": "C#",
"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": "AR/VR Engineer",
"id": 8,
"rationale": null,
"role_archetype": null,
"slug": "ar-vr-engineer",
"source": "db"
}
],
"skill_dimension_saved": true,
"skill_id": 4,
"skill_tag": "in_db",
"skipped_reason": null
},
{
"chosen_role_id": 1,
"dimension": {
"difficulty_hint": "well_known",
"display_name": "React Frontend Development",
"id": 96,
"rationale": "Building interactive web user interfaces with React.js, including component composition, state management, hooks, and rendering patterns. React.js belongs here because it is a core library for client-side UI development in modern web applications.",
"slug": "d_init_01",
"source": "db"
},
"dimension_id": 96,
"input_skill": "C#",
"llm_role": null,
"matched_chosen_role": false,
"outcome_line": "Existing dimension (library) \u00b7 Role\u2194dimension skipped (dimension not under chosen role)",
"role_dimension_saved": false,
"roles_from_db": [],
"skill_dimension_saved": true,
"skill_id": 4,
"skill_tag": "in_db",
"skipped_reason": null
},
{
"chosen_role_id": 1,
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Sitecore Development Languages",
"id": 438,
"rationale": "Core implementation languages and markup used to build Sitecore customizations, rendering logic, and site behavior. This is the primary authoring surface for Sitecore-specific code and templates.",
"slug": "sitecore-development-languages",
"source": "db"
},
"dimension_id": 438,
"input_skill": "C#",
"llm_role": null,
"matched_chosen_role": false,
"outcome_line": "Existing dimension (library) \u00b7 Role\u2194dimension skipped (dimension not under chosen role)",
"role_dimension_saved": false,
"roles_from_db": [
{
"display_name": "Sitecore Dev",
"id": 233,
"rationale": null,
"role_archetype": "Engineering",
"slug": "sitecore-dev",
"source": "db"
}
],
"skill_dimension_saved": true,
"skill_id": 4,
"skill_tag": "in_db",
"skipped_reason": null
},
{
"chosen_role_id": 1,
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Video Codec Languages and DSLs",
"id": 225,
"rationale": "Implementation languages and codec-specific description languages used to build compression, decoding, and transform logic. This is the primary coding surface for codec behavior and bitstream manipulation.",
"slug": "video-codec-languages-and-dsls",
"source": "db"
},
"dimension_id": 225,
"input_skill": "C#",
"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": "Video Codec Engineer",
"id": 22,
"rationale": null,
"role_archetype": null,
"slug": "video-codec-engineer",
"source": "db"
}
],
"skill_dimension_saved": true,
"skill_id": 4,
"skill_tag": "in_db",
"skipped_reason": null
},
{
"chosen_role_id": 1,
"dimension": {
"difficulty_hint": "well_known",
"display_name": "ASP.NET Core Web Frameworks",
"id": 363,
"rationale": "Server-side web frameworks and hosting models used to build HTTP APIs, middleware, filters, and request pipelines. This cluster is coherent because it defines how backend services receive, process, and return requests.",
"slug": "asp-net-core-web-frameworks",
"source": "db"
},
"dimension_id": 363,
"input_skill": "ASP.NET Core",
"llm_role": null,
"matched_chosen_role": false,
"outcome_line": "Existing dimension (library) \u00b7 Role\u2194dimension skipped (dimension not under chosen role)",
"role_dimension_saved": false,
"roles_from_db": [
{
"display_name": ".NET Backend Developer",
"id": 83,
"rationale": null,
"role_archetype": "Engineering",
"slug": "dotnet-backend-developer",
"source": "db"
}
],
"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": "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 Developer",
"id": 1,
"rationale": null,
"role_archetype": "A Backend Engineer designs, builds, and maintains the server-side logic and data handling that power applications and services. They focus on implementing reliable business functionality, integrating with other systems, and ensuring the backend is scalable, maintainable, and observable.",
"slug": "backend-engineer",
"source": "db"
},
{
"display_name": "Fullstack Developer",
"id": 15,
"rationale": null,
"role_archetype": null,
"slug": "full-stack-engineer",
"source": "db"
},
{
"display_name": "Java Backend Developer",
"id": 79,
"rationale": null,
"role_archetype": "Engineering",
"slug": "java-backend-developer",
"source": "db"
},
{
"display_name": "Node.js Backend Developer",
"id": 82,
"rationale": null,
"role_archetype": "Engineering",
"slug": "node-backend-developer",
"source": "db"
},
{
"display_name": "PHP Backend Developer",
"id": 86,
"rationale": null,
"role_archetype": "Engineering",
"slug": "php-backend-developer",
"source": "db"
},
{
"display_name": "Python Backend Developer",
"id": 80,
"rationale": null,
"role_archetype": "Engineering",
"slug": "python-backend-developer",
"source": "db"
}
],
"skill_dimension_saved": true,
"skill_id": 7,
"skill_tag": "in_db",
"skipped_reason": null
},
{
"chosen_role_id": 1,
"dimension": {
"difficulty_hint": "well_known",
"display_name": "ASP.NET Core Web Frameworks",
"id": 363,
"rationale": "Server-side web frameworks and hosting models used to build HTTP APIs, middleware, filters, and request pipelines. This cluster is coherent because it defines how backend services receive, process, and return requests.",
"slug": "asp-net-core-web-frameworks",
"source": "db"
},
"dimension_id": 363,
"input_skill": "MVC",
"llm_role": null,
"matched_chosen_role": false,
"outcome_line": "Existing dimension (library) \u00b7 Role\u2194dimension skipped (dimension not under chosen role)",
"role_dimension_saved": false,
"roles_from_db": [
{
"display_name": ".NET Backend Developer",
"id": 83,
"rationale": null,
"role_archetype": "Engineering",
"slug": "dotnet-backend-developer",
"source": "db"
}
],
"skill_dimension_saved": true,
"skill_id": 505,
"skill_tag": "in_db",
"skipped_reason": null
},
{
"chosen_role_id": 1,
"dimension": {
"difficulty_hint": "well_known",
"display_name": "App Architecture and Dependency Injection",
"id": 94,
"rationale": "Structural patterns used to organize iOS code into testable, maintainable feature modules and layers. iOS engineers use these patterns to separate UI, state, and service integration concerns.",
"slug": "app-architecture-and-dependency-injection",
"source": "db"
},
"dimension_id": 94,
"input_skill": "MVC",
"llm_role": null,
"matched_chosen_role": false,
"outcome_line": "Existing dimension (library) \u00b7 Role\u2194dimension skipped (dimension not under chosen role)",
"role_dimension_saved": false,
"roles_from_db": [
{
"display_name": "Android Developer",
"id": 4,
"rationale": null,
"role_archetype": null,
"slug": "android-engineer",
"source": "db"
},
{
"display_name": "iOS Developer",
"id": 6,
"rationale": null,
"role_archetype": null,
"slug": "ios-engineer",
"source": "db"
}
],
"skill_dimension_saved": true,
"skill_id": 505,
"skill_tag": "in_db",
"skipped_reason": null
},
{
"chosen_role_id": 1,
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Application Architecture and Code Organization",
"id": 220,
"rationale": "Structural patterns for organizing product code into maintainable modules, layers, and feature boundaries. Full stack engineers need this to keep cross-layer feature work understandable as the product grows.",
"slug": "application-architecture-and-code-organization",
"source": "db"
},
"dimension_id": 220,
"input_skill": "MVC",
"llm_role": null,
"matched_chosen_role": false,
"outcome_line": "Existing dimension (library) \u00b7 Role\u2194dimension skipped (dimension not under chosen role)",
"role_dimension_saved": false,
"roles_from_db": [
{
"display_name": "Fullstack Developer",
"id": 15,
"rationale": null,
"role_archetype": null,
"slug": "full-stack-engineer",
"source": "db"
}
],
"skill_dimension_saved": true,
"skill_id": 505,
"skill_tag": "in_db",
"skipped_reason": null
},
{
"chosen_role_id": 1,
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Native Mobile App Architecture and Dependency Injection",
"id": 273,
"rationale": "Structural patterns for organizing native mobile application code into maintainable, testable modules, layers, and feature boundaries. This includes app architecture patterns such as MVVM, MVC, MVI, VIPER, and Clean Architecture; dependency injection frameworks and patterns such as Hilt, Dagger, and Koin; and code organization techniques such as modularization, feature modules, repository pattern, and use-case layering to separate UI, state, data, and platform concerns across a growing codebase.",
"slug": "native-mobile-app-architecture-and-dependency-injection",
"source": "db"
},
"dimension_id": 273,
"input_skill": "MVC",
"llm_role": null,
"matched_chosen_role": false,
"outcome_line": "Existing dimension (library) \u00b7 Role\u2194dimension skipped (dimension not under chosen role)",
"role_dimension_saved": false,
"roles_from_db": [
{
"display_name": "Native Mobile Developer",
"id": 75,
"rationale": null,
"role_archetype": "Engineering",
"slug": "native-mobile-developer",
"source": "db"
}
],
"skill_dimension_saved": true,
"skill_id": 505,
"skill_tag": "in_db",
"skipped_reason": null
},
{
"chosen_role_id": 1,
"dimension": {
"difficulty_hint": "well_known",
"display_name": "API Design and Contracts",
"id": 3,
"rationale": "Designing request/response shapes and the rules that govern client-server interaction. This cluster is coherent because full stack engineers often own the contract between UI behavior and backend implementation.",
"slug": "api-design-and-contracts",
"source": "db"
},
"dimension_id": 3,
"input_skill": "REST",
"llm_role": null,
"matched_chosen_role": true,
"outcome_line": "Existing dimension (library) \u00b7 Role\u2194dimension saved",
"role_dimension_saved": true,
"roles_from_db": [
{
"display_name": "Backend Developer",
"id": 1,
"rationale": null,
"role_archetype": "A Backend Engineer designs, builds, and maintains the server-side logic and data handling that power applications and services. They focus on implementing reliable business functionality, integrating with other systems, and ensuring the backend is scalable, maintainable, and observable.",
"slug": "backend-engineer",
"source": "db"
},
{
"display_name": "Fullstack Developer",
"id": 15,
"rationale": null,
"role_archetype": null,
"slug": "full-stack-engineer",
"source": "db"
}
],
"skill_dimension_saved": true,
"skill_id": 11,
"skill_tag": "in_db",
"skipped_reason": null
},
{
"chosen_role_id": 1,
"dimension": {
"difficulty_hint": "well_known",
"display_name": "API Interface and Contract Design",
"id": 289,
"rationale": "Designing backend service interfaces and contracts that other systems consume, including endpoint and operation shape, request/response payloads, schema and validation, pagination, filtering, idempotency, versioning, status codes, and backward compatibility across REST, GraphQL, gRPC, and OpenAPI-based APIs.",
"slug": "api-interface-and-contract-design",
"source": "db"
},
"dimension_id": 289,
"input_skill": "REST",
"llm_role": null,
"matched_chosen_role": false,
"outcome_line": "Existing dimension (library) \u00b7 Role\u2194dimension skipped (dimension not under chosen role)",
"role_dimension_saved": false,
"roles_from_db": [
{
"display_name": ".NET Backend Developer",
"id": 83,
"rationale": null,
"role_archetype": "Engineering",
"slug": "dotnet-backend-developer",
"source": "db"
},
{
"display_name": "Go Backend Developer",
"id": 81,
"rationale": null,
"role_archetype": "Engineering",
"slug": "go-backend-developer",
"source": "db"
},
{
"display_name": "Kotlin Backend Developer",
"id": 84,
"rationale": null,
"role_archetype": "Engineering",
"slug": "kotlin-server-backend-developer",
"source": "db"
},
{
"display_name": "Node.js Backend Developer",
"id": 82,
"rationale": null,
"role_archetype": "Engineering",
"slug": "node-backend-developer",
"source": "db"
},
{
"display_name": "PHP Backend Developer",
"id": 86,
"rationale": null,
"role_archetype": "Engineering",
"slug": "php-backend-developer",
"source": "db"
},
{
"display_name": "Python Backend Developer",
"id": 80,
"rationale": null,
"role_archetype": "Engineering",
"slug": "python-backend-developer",
"source": "db"
},
{
"display_name": "Ruby Backend Developer",
"id": 85,
"rationale": null,
"role_archetype": "Engineering",
"slug": "ruby-backend-developer",
"source": "db"
},
{
"display_name": "Scala Backend Developer",
"id": 87,
"rationale": null,
"role_archetype": "Engineering",
"slug": "scala-backend-developer",
"source": "db"
}
],
"skill_dimension_saved": true,
"skill_id": 11,
"skill_tag": "in_db",
"skipped_reason": null
},
{
"chosen_role_id": 1,
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Integration Protocols \u0026 Standards",
"id": 271,
"rationale": "Standards and protocols for integrating Pega applications.",
"slug": "integration-protocols-standards",
"source": "db"
},
"dimension_id": 271,
"input_skill": "REST",
"llm_role": null,
"matched_chosen_role": false,
"outcome_line": "Existing dimension (library) \u00b7 Role\u2194dimension skipped (dimension not under chosen role)",
"role_dimension_saved": false,
"roles_from_db": [
{
"display_name": "Pega Developer",
"id": 24,
"rationale": null,
"role_archetype": null,
"slug": "pega-developer",
"source": "db"
}
],
"skill_dimension_saved": true,
"skill_id": 11,
"skill_tag": "in_db",
"skipped_reason": null
},
{
"chosen_role_id": 1,
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Standards \u0026 Protocols Compliance",
"id": 452,
"rationale": "Encompasses key web and data standards, protocols, and compliance requirements relevant to Sitecore implementations.",
"slug": "standards-protocols-compliance",
"source": "db"
},
"dimension_id": 452,
"input_skill": "REST",
"llm_role": null,
"matched_chosen_role": false,
"outcome_line": "Existing dimension (library) \u00b7 Role\u2194dimension skipped (dimension not under chosen role)",
"role_dimension_saved": false,
"roles_from_db": [
{
"display_name": "Sitecore Dev",
"id": 233,
"rationale": null,
"role_archetype": "Engineering",
"slug": "sitecore-dev",
"source": "db"
}
],
"skill_dimension_saved": true,
"skill_id": 11,
"skill_tag": "in_db",
"skipped_reason": null
},
{
"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": ".NET Backend Developer",
"id": 83,
"rationale": null,
"role_archetype": "Engineering",
"slug": "dotnet-backend-developer",
"source": "db"
},
{
"display_name": "Backend Developer",
"id": 1,
"rationale": null,
"role_archetype": "A Backend Engineer designs, builds, and maintains the server-side logic and data handling that power applications and services. They focus on implementing reliable business functionality, integrating with other systems, and ensuring the backend is scalable, maintainable, and observable.",
"slug": "backend-engineer",
"source": "db"
},
{
"display_name": "Kotlin Backend Developer",
"id": 84,
"rationale": null,
"role_archetype": "Engineering",
"slug": "kotlin-server-backend-developer",
"source": "db"
},
{
"display_name": "Node.js Backend Developer",
"id": 82,
"rationale": null,
"role_archetype": "Engineering",
"slug": "node-backend-developer",
"source": "db"
},
{
"display_name": "Python Backend Developer",
"id": 80,
"rationale": null,
"role_archetype": "Engineering",
"slug": "python-backend-developer",
"source": "db"
},
{
"display_name": "Ruby Backend Developer",
"id": 85,
"rationale": null,
"role_archetype": "Engineering",
"slug": "ruby-backend-developer",
"source": "db"
},
{
"display_name": "Scala Backend Developer",
"id": 87,
"rationale": null,
"role_archetype": "Engineering",
"slug": "scala-backend-developer",
"source": "db"
}
],
"skill_dimension_saved": true,
"skill_id": 18,
"skill_tag": "in_db",
"skipped_reason": null
},
{
"chosen_role_id": 1,
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Angular Component Model and Templates",
"id": 303,
"rationale": "Core Angular framework surface for building reusable UI, composing views, and wiring component behavior. This is the main application substrate for browser features in this role.",
"slug": "angular-component-model-and-templates",
"source": "db"
},
"dimension_id": 303,
"input_skill": "Dependency Injection",
"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": "Angular Frontend Developer",
"id": 90,
"rationale": null,
"role_archetype": "Engineering",
"slug": "angular-frontend-developer",
"source": "db"
}
],
"skill_dimension_saved": true,
"skill_id": 88,
"skill_tag": "in_db",
"skipped_reason": null
},
{
"chosen_role_id": 1,
"dimension": {
"difficulty_hint": "well_known",
"display_name": "App Architecture and Dependency Injection",
"id": 94,
"rationale": "Structural patterns used to organize iOS code into testable, maintainable feature modules and layers. iOS engineers use these patterns to separate UI, state, and service integration concerns.",
"slug": "app-architecture-and-dependency-injection",
"source": "db"
},
"dimension_id": 94,
"input_skill": "Dependency Injection",
"llm_role": null,
"matched_chosen_role": false,
"outcome_line": "Existing dimension (library) \u00b7 Role\u2194dimension skipped (dimension not under chosen role)",
"role_dimension_saved": false,
"roles_from_db": [
{
"display_name": "Android Developer",
"id": 4,
"rationale": null,
"role_archetype": null,
"slug": "android-engineer",
"source": "db"
},
{
"display_name": "iOS Developer",
"id": 6,
"rationale": null,
"role_archetype": null,
"slug": "ios-engineer",
"source": "db"
}
],
"skill_dimension_saved": true,
"skill_id": 88,
"skill_tag": "in_db",
"skipped_reason": null
},
{
"chosen_role_id": 1,
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Application Architecture Patterns",
"id": 293,
"rationale": "Structural patterns for organizing Python backend code into maintainable modules, layers, and feature boundaries. This is a coherent cluster because senior backend developers are expected to refactor and shape service internals over time.",
"slug": "application-architecture-patterns",
"source": "db"
},
"dimension_id": 293,
"input_skill": "Dependency Injection",
"llm_role": null,
"matched_chosen_role": false,
"outcome_line": "Existing dimension (library) \u00b7 Role\u2194dimension skipped (dimension not under chosen role)",
"role_dimension_saved": false,
"roles_from_db": [
{
"display_name": ".NET Backend Developer",
"id": 83,
"rationale": null,
"role_archetype": "Engineering",
"slug": "dotnet-backend-developer",
"source": "db"
},
{
"display_name": "Python Backend Developer",
"id": 80,
"rationale": null,
"role_archetype": "Engineering",
"slug": "python-backend-developer",
"source": "db"
}
],
"skill_dimension_saved": true,
"skill_id": 88,
"skill_tag": "in_db",
"skipped_reason": null
},
{
"chosen_role_id": 1,
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Application Architecture and Code Organization",
"id": 220,
"rationale": "Structural patterns for organizing product code into maintainable modules, layers, and feature boundaries. Full stack engineers need this to keep cross-layer feature work understandable as the product grows.",
"slug": "application-architecture-and-code-organization",
"source": "db"
},
"dimension_id": 220,
"input_skill": "Dependency Injection",
"llm_role": null,
"matched_chosen_role": false,
"outcome_line": "Existing dimension (library) \u00b7 Role\u2194dimension skipped (dimension not under chosen role)",
"role_dimension_saved": false,
"roles_from_db": [
{
"display_name": "Fullstack Developer",
"id": 15,
"rationale": null,
"role_archetype": null,
"slug": "full-stack-engineer",
"source": "db"
}
],
"skill_dimension_saved": true,
"skill_id": 88,
"skill_tag": "in_db",
"skipped_reason": null
},
{
"chosen_role_id": 1,
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Backend Application Architecture and Code Organization",
"id": 366,
"rationale": "Structural patterns for organizing backend application code into maintainable modules, layers, and boundaries so services remain testable, modular, evolvable, and easy to refactor. This includes clean architecture, hexagonal architecture, layered architecture, dependency injection, service layers, package or module boundaries, modularization, domain-driven design, SOLID, CQRS, and mediator-style patterns. It excludes API endpoint syntax, database schema design, deployment topology, and frontend architecture.",
"slug": "backend-application-architecture-and-code-organization",
"source": "db"
},
"dimension_id": 366,
"input_skill": "Dependency Injection",
"llm_role": null,
"matched_chosen_role": false,
"outcome_line": "Existing dimension (library) \u00b7 Role\u2194dimension skipped (dimension not under chosen role)",
"role_dimension_saved": false,
"roles_from_db": [
{
"display_name": "Go Backend Developer",
"id": 81,
"rationale": null,
"role_archetype": "Engineering",
"slug": "go-backend-developer",
"source": "db"
}
],
"skill_dimension_saved": true,
"skill_id": 88,
"skill_tag": "in_db",
"skipped_reason": null
},
{
"chosen_role_id": 1,
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Flutter App Architecture",
"id": 316,
"rationale": "Structural patterns used to organize Flutter code into maintainable modules, layers, and feature boundaries. Senior Flutter developers often own these patterns to keep shared app delivery scalable across teams and releases.",
"slug": "flutter-app-architecture",
"source": "db"
},
"dimension_id": 316,
"input_skill": "Dependency Injection",
"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": "Flutter Developer",
"id": 74,
"rationale": null,
"role_archetype": "Engineering",
"slug": "flutter-developer",
"source": "db"
}
],
"skill_dimension_saved": true,
"skill_id": 88,
"skill_tag": "in_db",
"skipped_reason": null
},
{
"chosen_role_id": 1,
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Ionic App Architecture",
"id": 384,
"rationale": "Structural patterns for organizing Ionic code into maintainable modules, layers, and feature boundaries. Senior Ionic developers often define these patterns to keep shared app behavior consistent across devices and releases.",
"slug": "ionic-app-architecture",
"source": "db"
},
"dimension_id": 384,
"input_skill": "Dependency Injection",
"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": "Ionic Developer",
"id": 434,
"rationale": null,
"role_archetype": null,
"slug": "ionic-developer",
"source": "db"
}
],
"skill_dimension_saved": true,
"skill_id": 88,
"skill_tag": "in_db",
"skipped_reason": null
},
{
"chosen_role_id": 1,
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Mobile Architecture and Code Organization",
"id": 170,
"rationale": "Structural patterns used to organize shared mobile code into maintainable modules, layers, and feature boundaries. Senior hybrid developers often own these patterns to keep cross-platform code testable and adaptable to platform exceptions.",
"slug": "mobile-architecture-and-code-organization",
"source": "db"
},
"dimension_id": 170,
"input_skill": "Dependency Injection",
"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": "Hybrid Mobile Developer",
"id": 11,
"rationale": null,
"role_archetype": null,
"slug": "hybrid-mobile-developer",
"source": "db"
},
{
"display_name": "React Native Developer",
"id": 73,
"rationale": null,
"role_archetype": "Engineering",
"slug": "react-native-developer",
"source": "db"
}
],
"skill_dimension_saved": true,
"skill_id": 88,
"skill_tag": "in_db",
"skipped_reason": null
},
{
"chosen_role_id": 1,
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Native Mobile App Architecture and Dependency Injection",
"id": 273,
"rationale": "Structural patterns for organizing native mobile application code into maintainable, testable modules, layers, and feature boundaries. This includes app architecture patterns such as MVVM, MVC, MVI, VIPER, and Clean Architecture; dependency injection frameworks and patterns such as Hilt, Dagger, and Koin; and code organization techniques such as modularization, feature modules, repository pattern, and use-case layering to separate UI, state, data, and platform concerns across a growing codebase.",
"slug": "native-mobile-app-architecture-and-dependency-injection",
"source": "db"
},
"dimension_id": 273,
"input_skill": "Dependency Injection",
"llm_role": null,
"matched_chosen_role": false,
"outcome_line": "Existing dimension (library) \u00b7 Role\u2194dimension skipped (dimension not under chosen role)",
"role_dimension_saved": false,
"roles_from_db": [
{
"display_name": "Native Mobile Developer",
"id": 75,
"rationale": null,
"role_archetype": "Engineering",
"slug": "native-mobile-developer",
"source": "db"
}
],
"skill_dimension_saved": true,
"skill_id": 88,
"skill_tag": "in_db",
"skipped_reason": null
},
{
"chosen_role_id": 1,
"dimension": {
"difficulty_hint": "well_known",
"display_name": "PHP and Magento Extension Points",
"id": 391,
"rationale": "Core implementation surface for Magento customizations, including module code, event-driven hooks, and platform conventions. This is the primary language-and-framework cluster for building upgrade-safe storefront behavior.",
"slug": "php-and-magento-extension-points",
"source": "db"
},
"dimension_id": 391,
"input_skill": "Dependency Injection",
"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": "Magento Dev",
"id": 231,
"rationale": null,
"role_archetype": "Engineering",
"slug": "magento-dev",
"source": "db"
}
],
"skill_dimension_saved": true,
"skill_id": 88,
"skill_tag": "in_db",
"skipped_reason": null
},
{
"chosen_role_id": 1,
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Service Architecture and Design Patterns",
"id": 18,
"rationale": "Reusable backend design patterns used to structure service code and boundaries. Covers layering, dependency management, domain modeling, and maintainable service organization.",
"slug": "service-architecture-and-design-patterns",
"source": "db"
},
"dimension_id": 18,
"input_skill": "Dependency Injection",
"llm_role": null,
"matched_chosen_role": true,
"outcome_line": "Existing dimension (library) \u00b7 Role\u2194dimension saved",
"role_dimension_saved": true,
"roles_from_db": [
{
"display_name": "Backend Developer",
"id": 1,
"rationale": null,
"role_archetype": "A Backend Engineer designs, builds, and maintains the server-side logic and data handling that power applications and services. They focus on implementing reliable business functionality, integrating with other systems, and ensuring the backend is scalable, maintainable, and observable.",
"slug": "backend-engineer",
"source": "db"
},
{
"display_name": "Java Backend Developer",
"id": 79,
"rationale": null,
"role_archetype": "Engineering",
"slug": "java-backend-developer",
"source": "db"
},
{
"display_name": "Kotlin Backend Developer",
"id": 84,
"rationale": null,
"role_archetype": "Engineering",
"slug": "kotlin-server-backend-developer",
"source": "db"
},
{
"display_name": "Node.js Backend Developer",
"id": 82,
"rationale": null,
"role_archetype": "Engineering",
"slug": "node-backend-developer",
"source": "db"
},
{
"display_name": "PHP Backend Developer",
"id": 86,
"rationale": null,
"role_archetype": "Engineering",
"slug": "php-backend-developer",
"source": "db"
},
{
"display_name": "Ruby Backend Developer",
"id": 85,
"rationale": null,
"role_archetype": "Engineering",
"slug": "ruby-backend-developer",
"source": "db"
},
{
"display_name": "Scala Backend Developer",
"id": 87,
"rationale": null,
"role_archetype": "Engineering",
"slug": "scala-backend-developer",
"source": "db"
}
],
"skill_dimension_saved": true,
"skill_id": 88,
"skill_tag": "in_db",
"skipped_reason": null
},
{
"chosen_role_id": 1,
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Application Architecture Patterns",
"id": 293,
"rationale": "Structural patterns for organizing Python backend code into maintainable modules, layers, and feature boundaries. This is a coherent cluster because senior backend developers are expected to refactor and shape service internals over time.",
"slug": "application-architecture-patterns",
"source": "db"
},
"dimension_id": 293,
"input_skill": "SOLID",
"llm_role": null,
"matched_chosen_role": false,
"outcome_line": "Existing dimension (library) \u00b7 Role\u2194dimension skipped (dimension not under chosen role)",
"role_dimension_saved": false,
"roles_from_db": [
{
"display_name": ".NET Backend Developer",
"id": 83,
"rationale": null,
"role_archetype": "Engineering",
"slug": "dotnet-backend-developer",
"source": "db"
},
{
"display_name": "Python Backend Developer",
"id": 80,
"rationale": null,
"role_archetype": "Engineering",
"slug": "python-backend-developer",
"source": "db"
}
],
"skill_dimension_saved": true,
"skill_id": 614,
"skill_tag": "in_db",
"skipped_reason": null
},
{
"chosen_role_id": 1,
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Service Architecture and Design Patterns",
"id": 18,
"rationale": "Reusable backend design patterns used to structure service code and boundaries. Covers layering, dependency management, domain modeling, and maintainable service organization.",
"slug": "service-architecture-and-design-patterns",
"source": "db"
},
"dimension_id": 18,
"input_skill": "SOLID",
"llm_role": null,
"matched_chosen_role": true,
"outcome_line": "Existing dimension (library) \u00b7 Role\u2194dimension saved",
"role_dimension_saved": true,
"roles_from_db": [
{
"display_name": "Backend Developer",
"id": 1,
"rationale": null,
"role_archetype": "A Backend Engineer designs, builds, and maintains the server-side logic and data handling that power applications and services. They focus on implementing reliable business functionality, integrating with other systems, and ensuring the backend is scalable, maintainable, and observable.",
"slug": "backend-engineer",
"source": "db"
},
{
"display_name": "Java Backend Developer",
"id": 79,
"rationale": null,
"role_archetype": "Engineering",
"slug": "java-backend-developer",
"source": "db"
},
{
"display_name": "Kotlin Backend Developer",
"id": 84,
"rationale": null,
"role_archetype": "Engineering",
"slug": "kotlin-server-backend-developer",
"source": "db"
},
{
"display_name": "Node.js Backend Developer",
"id": 82,
"rationale": null,
"role_archetype": "Engineering",
"slug": "node-backend-developer",
"source": "db"
},
{
"display_name": "PHP Backend Developer",
"id": 86,
"rationale": null,
"role_archetype": "Engineering",
"slug": "php-backend-developer",
"source": "db"
},
{
"display_name": "Ruby Backend Developer",
"id": 85,
"rationale": null,
"role_archetype": "Engineering",
"slug": "ruby-backend-developer",
"source": "db"
},
{
"display_name": "Scala Backend Developer",
"id": 87,
"rationale": null,
"role_archetype": "Engineering",
"slug": "scala-backend-developer",
"source": "db"
}
],
"skill_dimension_saved": true,
"skill_id": 614,
"skill_tag": "in_db",
"skipped_reason": null
},
{
"chosen_role_id": 1,
"dimension": {
"difficulty_hint": "well_known",
"display_name": "UI Frameworks and Rendering",
"id": 115,
"rationale": "Component frameworks and rendering models used to build browser screens, reusable UI, and interactive client flows. This is a core cluster because frontend engineers spend much of their time composing and updating view hierarchies.",
"slug": "ui-frameworks-and-rendering",
"source": "db"
},
"dimension_id": 115,
"input_skill": "SOLID",
"llm_role": null,
"matched_chosen_role": false,
"outcome_line": "Existing dimension (library) \u00b7 Role\u2194dimension skipped (dimension not under chosen role)",
"role_dimension_saved": false,
"roles_from_db": [
{
"display_name": "Frontend Developer",
"id": 7,
"rationale": null,
"role_archetype": null,
"slug": "frontend-engineer",
"source": "db"
},
{
"display_name": "Fullstack Developer",
"id": 15,
"rationale": null,
"role_archetype": null,
"slug": "full-stack-engineer",
"source": "db"
},
{
"display_name": "Hybrid Mobile Developer",
"id": 11,
"rationale": null,
"role_archetype": null,
"slug": "hybrid-mobile-developer",
"source": "db"
},
{
"display_name": "Ionic Developer",
"id": 434,
"rationale": null,
"role_archetype": null,
"slug": "ionic-developer",
"source": "db"
},
{
"display_name": "Web Developer",
"id": 25,
"rationale": null,
"role_archetype": null,
"slug": "web-developer",
"source": "db"
}
],
"skill_dimension_saved": true,
"skill_id": 614,
"skill_tag": "in_db",
"skipped_reason": null
},
{
"chosen_role_id": 1,
"dimension": {
"difficulty_hint": "well_known",
"display_name": "CI/CD Pipeline Platforms",
"id": 150,
"rationale": "Systems used to define, run, and maintain automated build and deployment workflows. This cluster is coherent because the role owns delivery automation end to end, including pipeline reliability and promotion logic.",
"slug": "ci-cd-pipeline-platforms",
"source": "db"
},
"dimension_id": 150,
"input_skill": "Azure DevOps",
"llm_role": null,
"matched_chosen_role": false,
"outcome_line": "Existing dimension (library) \u00b7 Role\u2194dimension skipped (dimension not under chosen role)",
"role_dimension_saved": false,
"roles_from_db": [
{
"display_name": "DevOps Engineer",
"id": 10,
"rationale": null,
"role_archetype": null,
"slug": "devops-engineer",
"source": "db"
}
],
"skill_dimension_saved": true,
"skill_id": 1214,
"skill_tag": "in_db",
"skipped_reason": null
}
],
"new_skills_created": 0,
"role_dimension_saved": 0,
"skill_dimension_saved": 0,
"skipped": 0
},
"planner_output": null,
"run_id": "b2f2b7dd-70e0-4efc-aa08-f3e38c9cf04f"
}
LLM Calls
Every model call made for this run, in pipeline order. Click a card to see the model's response.