Pipeline run
1bd1614e-7b8d-49eb-8e9c-c2d64821a365
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
• Write well-designed, testable, efficient code by using best software development practices • Follows company IT processes and IT procedures for managing code using company standard tools and process…
1 POST /skills/extract-from-jd
2 POST /skills/extract-details
3 POST /skills/final-role-output
Desktop Application Developer
domain · Software Engineering CASE DOMAINslug: desktop-application-developer · id: 29 · source: db
Domain=Software Engineering; The JD centers on C# .NET desktop/UI development with WPF, MVVM, UI controls, and Git, which best matches a desktop application developer rather than backend or web roles.
Matched skills
Matched dimensions
Matched KRAs
Resolution:
in_db
— role exists in library; skill↔dim and role↔dim links saved when applicable.
Job description
Desired Skills: C#, WPF, ASP.NET Experience range: At least 3-5 years We are looking for a Microsoft C# .NET Developer who has the following expertise • • Top-notch programming skills and in-depth knowledge of C# • • Experience with WPF and design patterns like MVVM • • Good experience with Rest API's, Dependency Injection • • Solid understanding of object-oriented programming • • Experience developing user interfaces and customizing UI controls/components • • Familiarity with Agile software development methodologies • • Advanced knowledge of using Git source control system • • Ability to write clean, readable, maintainable code • • Advanced troubleshooting skills • • Possess excellent written and verbal communication skills (English) Job Responsibilities: • Write well-designed, testable, efficient code by using best software development practices • Follows company IT processes and IT procedures for managing code using company standard tools and processes • Collaborate with others in the design, development, and implementation of client solutions With us you can expect: • A modern, team-oriented working environment in an economically stable and globally active medium-sized company • A long-term, challenging working environment with global exposure. • Performance-related and competitive remuneration, • For more details, please refer www.gessmann.com If you would like to work in an open-minded and creative team, please send us your profile with all relevant documents and time required to join at E mail id gopalshastry@gessmann.com
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, 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 skipped (dimension not under chosen role) |
|
Programming Languages for ML Systems
programming-languages-for-ml-systems
|
✓ | — | Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role) |
|
Programming Languages for 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) |
Aliases — catalog
- .NET (CANONICAL) primary
- .NET 5 (VERSION)
- .NET 6 (VERSION)
- .NET 7 (VERSION)
- .NET 8 (VERSION)
- .NET Core (VERSION)
Context tags (catalog)
Stored enrichment (catalog DB)
- Category
- Runtime
- Sub-category
- Runtime Platform
- Vendor
- Microsoft
- License
- mit
- Year introduced
- 2002
- Confidence
- 0.90
- Version strategy
- SEPARATE_ENTITY
- Version tag
- .NET (modern, i.e., .NET 6+)
Maturity reasoning: .NET appears in large volumes of job postings across enterprise, cloud, and backend roles, and Microsoft continues active releases and LTS support, indicating broad hiring-pipeline adoption.
Skill profile (library / DB)
- Skill nature
- RUNTIME
- Volatility
- STABLE
- Typical lifespan
- EVERGREEN
- Category id
- 67
- Sub-category id
- 2564
- 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
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) |
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
- MVVM (CANONICAL) primary
Context tags (catalog)
Stored enrichment (catalog DB)
- Category
- Architecture
- Sub-category
- Presentation Architecture
- Confidence
- 0.95
- Version strategy
- NOT_APPLICABLE
Maturity reasoning: MVVM is widely used in mobile and desktop JDs, especially Android, WPF, and SwiftUI ecosystems; it remains a common hiring keyword rather than a sunset pattern.
Skill profile (library / DB)
- Skill nature
- PATTERN
- Volatility
- STABLE
- Typical lifespan
- EVERGREEN
- Category id
- 1
- Sub-category id
- 662
- Extractable
- True
- Also category
- False
Dimensions (API 2 worklist)
-
App Architecture and Dependency Injection Catalog dimension db id 94
Library dimension (catalog)
Roles linked in library: Android Developer, iOS 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
API 3 link attempts (this skill)
| Dimension | Skill↔dim | Role↔dim | Outcome |
|---|---|---|---|
|
App Architecture and Dependency Injection
app-architecture-and-dependency-injection
|
✓ | — | 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) |
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, 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: Engineering Manager, 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 skipped (dimension not under chosen role) |
|
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) |
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, 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 skipped (dimension not under chosen role) |
Skill enrichment (orchestrator / LLM)
No Stage 7 enrichment blob on this skill (orchestrator skipped enrichment).
- Category
- Programming Concepts
- Sub-category
- general
- Skill nature
- CONCEPT
- Volatility
- STABLE
- Typical lifespan
- EVERGREEN
- Version strategy
- UNVERSIONED
Aliases — catalog
- Agile (CANONICAL) primary
Context tags (catalog)
Stored enrichment (catalog DB)
- Category
- Methodology
- Sub-category
- Agile
- Confidence
- 0.99
- Version strategy
- NOT_APPLICABLE
Maturity reasoning: Agile appears in a large share of software job descriptions and is a standard hiring-pipeline requirement; Scrum/Kanban are commonly listed alongside it, showing broad market adoption.
Skill profile (library / DB)
- Skill nature
- METHODOLOGY
- Volatility
- STABLE
- Typical lifespan
- EVERGREEN
- Category id
- 8
- Sub-category id
- 3594
- Extractable
- True
- Also category
- False
Dimensions (API 2 worklist)
-
React Frontend Development Catalog dimension db id 96
Library dimension (catalog)
-
Software Concepts, Patterns & Practices Catalog dimension db id 478
Library dimension (catalog)
Roles linked in library: Engineering Manager
API 3 link attempts (this skill)
| Dimension | Skill↔dim | Role↔dim | Outcome |
|---|---|---|---|
|
React Frontend Development
d_init_01
|
✓ | — | Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role) |
|
Software Concepts, Patterns & Practices
software-concepts-patterns-practices
|
✓ | — | Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role) |
Aliases — catalog
- Git (CANONICAL)
Context tags (catalog)
Stored enrichment (catalog DB)
- Category
- Tool
- Sub-category
- Version Control Tool
- Vendor
- Linus Torvalds
- License
- gpl_v2
- Year introduced
- 2005
- Confidence
- 0.99
- Version strategy
- NOT_APPLICABLE
Maturity reasoning: Git is a hiring-pipeline staple: it appears in the vast majority of software engineering job descriptions and is the default VCS on GitHub/GitLab/Bitbucket.
Skill profile (library / DB)
- Skill nature
- TOOL
- Volatility
- STABLE
- Typical lifespan
- EVERGREEN
- Category id
- 13
- Sub-category id
- 730
- Extractable
- True
- Also category
- False
Dimensions (API 2 worklist)
-
React Frontend Development Catalog dimension db id 96
Library dimension (catalog)
API 3 link attempts (this skill)
| Dimension | Skill↔dim | Role↔dim | Outcome |
|---|---|---|---|
|
React Frontend Development
d_init_01
|
✓ | — | Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role) |
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 skipped (dimension not under chosen role) | |
| 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) | |
| .NET | in_db |
C# and .NET Languages
c-and-net-languages
|
✓ | — | Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role) | |
| MVVM | in_db |
App Architecture and Dependency Injection
app-architecture-and-dependency-injection
|
✓ | — | Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role) | |
| MVVM | in_db |
Mobile Architecture and Code Organization
mobile-architecture-and-code-organization
|
✓ | — | Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role) | |
| MVVM | 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 skipped (dimension not under chosen role) | |
| 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) | |
| 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 skipped (dimension not under chosen role) | |
| Agile | in_db |
React Frontend Development
d_init_01
|
✓ | — | Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role) | |
| Agile | in_db |
Software Concepts, Patterns & Practices
software-concepts-patterns-practices
|
✓ | — | Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role) | |
| Git | in_db |
React Frontend Development
d_init_01
|
✓ | — | Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role) |
Library artifacts (this run)
| Kind | Detail | DB id |
|---|---|---|
| canonical_skill_proposed | WPF | type=Web Frameworks subtype=general nature=TOOL lifespan=MULTI_YEAR | |
| canonical_skill_proposed | Object-Oriented Programming | type=Programming Concepts subtype=general nature=CONCEPT lifespan=EVERGREEN |
nano JD Parser — gpt-4.1-nano click to toggle
Show raw JSON
{
"JD_type": "pass",
"about_company": null,
"certifications": [],
"company_name": "Gessmann",
"ctc": null,
"domain": {
"primary": {
"aliases": [],
"domain": "Other"
},
"secondary": null
},
"education": [],
"experience": {
"max": 5,
"min": 3,
"raw": "At least 3-5 years"
},
"job_locations": [],
"role": "Microsoft C# .NET Developer",
"role_aliases": [
"C# Developer",
".NET Developer",
"Software Developer"
],
"role_archetype": "Engineering",
"roles_and_responsibilities": [
{
"bullet_count": 3,
"heading": "Job Responsibilities",
"heading_was_present": true,
"source_marker": {
"first_5_words": "\u2022 Write well-designed, testable,",
"last_5_words": "design, development, and implementation"
},
"text": "\u2022 Write well-designed, testable, efficient code by using best software development practices\n\u2022 Follows company IT processes and IT procedures for managing code using company standard tools and processes\n\u2022 Collaborate with others in the design, development, and implementation of client solutions",
"word_count": 36
},
{
"bullet_count": 10,
"heading": "Desired Skills",
"heading_was_present": true,
"source_marker": {
"first_5_words": "\u2022 Top-notch programming skills and",
"last_5_words": "written and verbal communication skills"
},
"text": "\u2022 Top-notch programming skills and in-depth knowledge of C#\n\u2022 Experience with WPF and design patterns like MVVM\n\u2022 Good experience with Rest API\u0027s, Dependency Injection\n\u2022 Solid understanding of object-oriented programming\n\u2022 Experience developing user interfaces and customizing UI controls/components\n\u2022 Familiarity with Agile software development methodologies\n\u2022 Advanced knowledge of using Git source control system\n\u2022 Ability to write clean, readable, maintainable code\n\u2022 Advanced troubleshooting skills\n\u2022 Possess excellent written and verbal communication skills (English)",
"word_count": 92
}
],
"urls": [
{
"type": "website",
"url": "www.gessmann.com"
}
]
}
API 1 — extract-from-jd click to toggle
{
"final_skills": [
{
"is_primary": true,
"skill_name": "C#"
},
{
"is_primary": true,
"skill_name": ".NET"
},
{
"is_primary": true,
"skill_name": "WPF"
},
{
"is_primary": true,
"skill_name": "MVVM"
},
{
"is_primary": true,
"skill_name": "REST"
},
{
"is_primary": true,
"skill_name": "Dependency Injection"
},
{
"is_primary": true,
"skill_name": "Object-Oriented Programming"
},
{
"is_primary": true,
"skill_name": "Agile"
},
{
"is_primary": true,
"skill_name": "Git"
}
],
"jd_role": {
"display_name": "Microsoft C# .NET Developer",
"rationale": null,
"role_aliases": [
"C# Developer",
".NET Developer",
"Software Developer"
],
"role_archetype": "Engineering",
"slug": ""
},
"nano_parsed": {
"JD_type": "pass",
"about_company": null,
"certifications": [],
"company_name": "Gessmann",
"ctc": null,
"domain": {
"primary": {
"aliases": [],
"domain": "Other"
},
"secondary": null
},
"education": [],
"experience": {
"max": 5,
"min": 3,
"raw": "At least 3-5 years"
},
"job_locations": [],
"role": "Microsoft C# .NET Developer",
"role_aliases": [
"C# Developer",
".NET Developer",
"Software Developer"
],
"role_archetype": "Engineering",
"roles_and_responsibilities": [
{
"bullet_count": 3,
"heading": "Job Responsibilities",
"heading_was_present": true,
"source_marker": {
"first_5_words": "\u2022 Write well-designed, testable,",
"last_5_words": "design, development, and implementation"
},
"text": "\u2022 Write well-designed, testable, efficient code by using best software development practices\n\u2022 Follows company IT processes and IT procedures for managing code using company standard tools and processes\n\u2022 Collaborate with others in the design, development, and implementation of client solutions",
"word_count": 36
},
{
"bullet_count": 10,
"heading": "Desired Skills",
"heading_was_present": true,
"source_marker": {
"first_5_words": "\u2022 Top-notch programming skills and",
"last_5_words": "written and verbal communication skills"
},
"text": "\u2022 Top-notch programming skills and in-depth knowledge of C#\n\u2022 Experience with WPF and design patterns like MVVM\n\u2022 Good experience with Rest API\u0027s, Dependency Injection\n\u2022 Solid understanding of object-oriented programming\n\u2022 Experience developing user interfaces and customizing UI controls/components\n\u2022 Familiarity with Agile software development methodologies\n\u2022 Advanced knowledge of using Git source control system\n\u2022 Ability to write clean, readable, maintainable code\n\u2022 Advanced troubleshooting skills\n\u2022 Possess excellent written and verbal communication skills (English)",
"word_count": 92
}
],
"urls": [
{
"type": "website",
"url": "www.gessmann.com"
}
]
},
"rejected": false,
"rejection_reason": null,
"run_id": "1bd1614e-7b8d-49eb-8e9c-c2d64821a365",
"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": "Flutter Developer",
"kra_matches": [
{
"kra_text": "collaborate with design, product, and backend teams",
"sentence": "Collaborate with others in the design, development, and implementation of client solutions",
"similarity": 0.7174
},
{
"kra_text": "Implement user-facing screens and flows",
"sentence": "Experience developing user interfaces and customizing UI controls/components",
"similarity": 0.5942
},
{
"kra_text": "structure reusable application code",
"sentence": "Ability to write clean, readable, maintainable code",
"similarity": 0.4514
}
],
"matched_count": null,
"matched_skills": null,
"role_id": 74,
"score": 0.5877,
"slug": "flutter-developer",
"total_count": null
},
{
"display_name": "React Native Developer",
"kra_matches": [
{
"kra_text": "maintain code quality",
"sentence": "Ability to write clean, readable, maintainable code",
"similarity": 0.6616
},
{
"kra_text": "maintain code quality",
"sentence": "Write well-designed, testable, efficient code by using best software development practices",
"similarity": 0.6192
},
{
"kra_text": "maintain code quality",
"sentence": "Follows company IT processes and IT procedures for managing code using company standard tools and processes",
"similarity": 0.4648
}
],
"matched_count": null,
"matched_skills": null,
"role_id": 73,
"score": 0.5818,
"slug": "react-native-developer",
"total_count": null
},
{
"display_name": "Angular Frontend Developer",
"kra_matches": [
{
"kra_text": "collaboration with design and QA",
"sentence": "Collaborate with others in the design, development, and implementation of client solutions",
"similarity": 0.6023
},
{
"kra_text": "code review and refactoring",
"sentence": "Write well-designed, testable, efficient code by using best software development practices",
"similarity": 0.5394
},
{
"kra_text": "code review and refactoring",
"sentence": "Ability to write clean, readable, maintainable code",
"similarity": 0.5386
}
],
"matched_count": null,
"matched_skills": null,
"role_id": 90,
"score": 0.5601,
"slug": "angular-frontend-developer",
"total_count": null
},
{
"display_name": "Node.js Backend Developer",
"kra_matches": [
{
"kra_text": "code review and refactoring",
"sentence": "Write well-designed, testable, efficient code by using best software development practices",
"similarity": 0.5394
},
{
"kra_text": "code review and refactoring",
"sentence": "Ability to write clean, readable, maintainable code",
"similarity": 0.5387
},
{
"kra_text": "API design and request handling",
"sentence": "Good experience with Rest API\u0027s, Dependency Injection",
"similarity": 0.4669
}
],
"matched_count": null,
"matched_skills": null,
"role_id": 82,
"score": 0.515,
"slug": "node-backend-developer",
"total_count": null
},
{
"display_name": ".NET Backend Developer",
"kra_matches": [
{
"kra_text": "backend code refactoring and maintenance",
"sentence": "Ability to write clean, readable, maintainable code",
"similarity": 0.5389
},
{
"kra_text": "service-level technical collaboration",
"sentence": "Collaborate with others in the design, development, and implementation of client solutions",
"similarity": 0.4983
},
{
"kra_text": "backend code refactoring and maintenance",
"sentence": "Write well-designed, testable, efficient code by using best software development practices",
"similarity": 0.4965
}
],
"matched_count": null,
"matched_skills": null,
"role_id": 83,
"score": 0.5112,
"slug": "dotnet-backend-developer",
"total_count": null
}
],
"skill_match_roles": [
{
"display_name": ".NET Backend Developer",
"kra_matches": null,
"matched_count": 4,
"matched_skills": [
".NET",
"C#",
"REST",
"dependency injection"
],
"role_id": 83,
"score": 0.4444,
"slug": "dotnet-backend-developer",
"total_count": 9
},
{
"display_name": "Fullstack Developer",
"kra_matches": null,
"matched_count": 3,
"matched_skills": [
"C#",
"REST",
"dependency injection"
],
"role_id": 15,
"score": 0.3333,
"slug": "full-stack-engineer",
"total_count": 9
},
{
"display_name": "Fullstack Developer",
"kra_matches": null,
"matched_count": 3,
"matched_skills": [
"C#",
"REST",
"dependency injection"
],
"role_id": 435,
"score": 0.3333,
"slug": "fullstack-developer",
"total_count": 9
},
{
"display_name": "Backend Developer",
"kra_matches": null,
"matched_count": 3,
"matched_skills": [
"C#",
"REST",
"dependency injection"
],
"role_id": 1,
"score": 0.3333,
"slug": "backend-engineer",
"total_count": 9
},
{
"display_name": "Hybrid Mobile Developer",
"kra_matches": null,
"matched_count": 3,
"matched_skills": [
"C#",
"MVVM",
"dependency injection"
],
"role_id": 11,
"score": 0.3333,
"slug": "hybrid-mobile-developer",
"total_count": 9
}
]
},
"stage4_decision": {
"alias_collision_detected": false,
"case": "DOMAIN",
"chosen_role": {
"display_name": "Desktop Application Developer",
"kra_matches": null,
"matched_count": null,
"matched_skills": null,
"role_id": 29,
"score": 0.88,
"slug": "desktop-application-developer",
"total_count": null
},
"confidence": 0.88,
"is_new_role": false,
"llm2_fired": false,
"llm2_reasoning": null,
"matched_dimensions": [
"Desktop Application Development",
"UI Development",
"Software Design and Code Quality",
"API Integration",
"Source Control and Engineering Processes",
"Agile Collaboration",
"Troubleshooting"
],
"matched_kras": [
"Write well-designed, testable, efficient code",
"Follow company IT processes and procedures",
"Collaborate in design, development, and implementation",
"Develop user interfaces and customize UI controls/components",
"Write clean, readable, maintainable code",
"Advance troubleshooting skills"
],
"matched_skills": [
"C#",
".NET",
"WPF",
"MVVM",
"Rest API\u0027s",
"Dependency Injection",
"object-oriented programming",
"Agile software development methodologies",
"Git",
"troubleshooting",
"UI controls/components"
],
"new_role_display_name": null,
"new_role_slug": null,
"queued": false,
"reasoning": "Domain=Software Engineering; The JD centers on C# .NET desktop/UI development with WPF, MVVM, UI controls, and Git, which best matches a desktop application developer rather than backend or web roles.",
"sub_role": null
},
"stage5_updates": {
"centroid_n_after": 5,
"centroid_updated": true,
"collision_log_id": null,
"new_kra_attached": {
"best_kra_similarity": 0.0,
"queue_id": 1408,
"r_and_r_preview": "\u2022 Write well-designed, testable, efficient code by using best software development practices\n\u2022 Follows company IT processes and IT procedures for managing code using company standard tools and process",
"role_display_name": "Desktop Application Developer",
"role_slug": "desktop-application-developer",
"status": "pending"
},
"new_skills_attached": [
{
"is_primary": true,
"queue_id": 19145,
"role_display_name": "Desktop Application Developer",
"role_slug": "desktop-application-developer",
"skill_name": "WPF",
"status": "pending"
},
{
"is_primary": true,
"queue_id": 19146,
"role_display_name": "Desktop Application Developer",
"role_slug": "desktop-application-developer",
"skill_name": "Object-Oriented Programming",
"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": 4766,
"existing_alias_text": ".NET",
"input_term": ".NET",
"matched_canonical": {
"category_id": 67,
"display_name": ".NET",
"id": 3237,
"is_also_category": false,
"is_extractable": true,
"skill_nature": "RUNTIME",
"slug": "net",
"sub_category_id": 2564,
"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": 830,
"existing_alias_text": "MVVM",
"input_term": "MVVM",
"matched_canonical": {
"category_id": 1,
"display_name": "MVVM",
"id": 504,
"is_also_category": false,
"is_extractable": true,
"skill_nature": "PATTERN",
"slug": "mvvm",
"sub_category_id": 662,
"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": 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": 868,
"existing_alias_text": "Agile",
"input_term": "Agile",
"matched_canonical": {
"category_id": 8,
"display_name": "Agile",
"id": 520,
"is_also_category": false,
"is_extractable": true,
"skill_nature": "METHODOLOGY",
"slug": "agile",
"sub_category_id": 3594,
"typical_lifespan": "EVERGREEN",
"volatility": "STABLE"
},
"matched_via": "alias"
},
{
"alias_persist_skipped_reason": "alias_text already exists for this canonical skill",
"alias_persisted": false,
"existing_alias_id": 1613,
"existing_alias_text": "Git",
"input_term": "Git",
"matched_canonical": {
"category_id": 13,
"display_name": "Git",
"id": 1002,
"is_also_category": false,
"is_extractable": true,
"skill_nature": "TOOL",
"slug": "git",
"sub_category_id": 730,
"typical_lifespan": "EVERGREEN",
"volatility": "STABLE"
},
"matched_via": "alias"
}
],
"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": "Fullstack Developer",
"id": 435,
"rationale": null,
"role_archetype": "Engineering",
"slug": "fullstack-developer",
"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": "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": "React Native Developer",
"id": 73,
"rationale": null,
"role_archetype": "Engineering",
"slug": "react-native-developer",
"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": "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"
},
{
"display_name": "Pega Developer",
"id": 24,
"rationale": null,
"role_archetype": null,
"slug": "pega-developer",
"source": "db"
},
{
"display_name": "Engineering Manager",
"id": 121,
"rationale": null,
"role_archetype": null,
"slug": "engineering-manager",
"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": "Magento Dev",
"id": 231,
"rationale": null,
"role_archetype": "Engineering",
"slug": "magento-dev",
"source": "db"
},
{
"display_name": "Java Backend Developer",
"id": 79,
"rationale": null,
"role_archetype": "Engineering",
"slug": "java-backend-developer",
"source": "db"
}
],
"chosen_role": {
"display_name": "Desktop Application Developer",
"id": 29,
"rationale": "Domain=Software Engineering; The JD centers on C# .NET desktop/UI development with WPF, MVVM, UI controls, and Git, which best matches a desktop application developer rather than backend or web roles.",
"role_archetype": null,
"slug": "desktop-application-developer",
"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"
},
{
"display_name": "Fullstack Developer",
"id": 435,
"rationale": null,
"role_archetype": "Engineering",
"slug": "fullstack-developer",
"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": "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": ".NET",
"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": "MVVM",
"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": "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": "MVVM",
"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": "MVVM",
"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": 435,
"rationale": null,
"role_archetype": "Engineering",
"slug": "fullstack-developer",
"source": "db"
},
{
"display_name": "Fullstack Developer",
"id": 15,
"rationale": null,
"role_archetype": null,
"slug": "full-stack-engineer",
"source": "db"
}
]
},
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "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, Protocols \u0026 Compliance",
"id": 452,
"rationale": "Ensure teams adhere to industry standards, security protocols, and regulatory compliance requirements.",
"slug": "standards-protocols-compliance",
"source": "db"
},
"input_skill": "REST",
"llm_role": null,
"roles_from_db": [
{
"display_name": "Engineering Manager",
"id": 121,
"rationale": null,
"role_archetype": null,
"slug": "engineering-manager",
"source": "db"
},
{
"display_name": "Sitecore Dev",
"id": 233,
"rationale": null,
"role_archetype": "Engineering",
"slug": "sitecore-dev",
"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"
},
{
"display_name": "Fullstack Developer",
"id": 435,
"rationale": null,
"role_archetype": "Engineering",
"slug": "fullstack-developer",
"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": "React Frontend Development",
"id": 96,
"rationale": "Building interactive web user interfaces with React.js, including component composition, state management, hooks, and rendering patterns. React.js belongs here because it is a core library for client-side UI development in modern web applications.",
"slug": "d_init_01",
"source": "db"
},
"input_skill": "Agile",
"llm_role": null,
"roles_from_db": []
},
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Software Concepts, Patterns \u0026 Practices",
"id": 478,
"rationale": "Champion foundational software design patterns, development methodologies, and engineering best practices.",
"slug": "software-concepts-patterns-practices",
"source": "db"
},
"input_skill": "Agile",
"llm_role": null,
"roles_from_db": [
{
"display_name": "Engineering Manager",
"id": 121,
"rationale": null,
"role_archetype": null,
"slug": "engineering-manager",
"source": "db"
}
]
},
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "React Frontend Development",
"id": 96,
"rationale": "Building interactive web user interfaces with React.js, including component composition, state management, hooks, and rendering patterns. React.js belongs here because it is a core library for client-side UI development in modern web applications.",
"slug": "d_init_01",
"source": "db"
},
"input_skill": "Git",
"llm_role": null,
"roles_from_db": []
}
],
"input_final_skills": [
"C#",
".NET",
"WPF",
"MVVM",
"REST",
"Dependency Injection",
"Object-Oriented Programming",
"Agile",
"Git"
],
"input_llm_skills": [
"C#",
".NET",
"WPF",
"MVVM",
"REST",
"Dependency Injection",
"Object-Oriented Programming",
"Agile",
"Git"
],
"new_aliases_persisted": 0,
"run_id": "1bd1614e-7b8d-49eb-8e9c-c2d64821a365",
"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"
},
{
"display_name": "Fullstack Developer",
"id": 435,
"rationale": null,
"role_archetype": "Engineering",
"slug": "fullstack-developer",
"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": [
{
"alias_text": ".NET",
"alias_type": "CANONICAL",
"id": 4766,
"is_primary": true,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": ".NET 5",
"alias_type": "VERSION",
"id": 4767,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": ".NET 6",
"alias_type": "VERSION",
"id": 4768,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": ".NET 7",
"alias_type": "VERSION",
"id": 4769,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": ".NET 8",
"alias_type": "VERSION",
"id": 4770,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": ".NET Core",
"alias_type": "VERSION",
"id": 4771,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
}
],
"canonical": {
"category_id": 67,
"display_name": ".NET",
"id": 3237,
"is_also_category": false,
"is_extractable": true,
"skill_nature": "RUNTIME",
"slug": "net",
"sub_category_id": 2564,
"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": ".NET",
"llm_role": null,
"roles_from_db": [
{
"display_name": ".NET Backend Developer",
"id": 83,
"rationale": null,
"role_archetype": "Engineering",
"slug": "dotnet-backend-developer",
"source": "db"
}
]
}
],
"input_skill": ".NET",
"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": "WPF",
"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": "wpf",
"split_log": [],
"typed": null,
"warnings": []
},
"source_tag": "llm",
"was_in_llm_skills": true
},
{
"aliases_in_db": [
{
"alias_text": "MVVM",
"alias_type": "CANONICAL",
"id": 830,
"is_primary": true,
"match_strategy": "CASE_INSENSITIVE"
}
],
"canonical": {
"category_id": 1,
"display_name": "MVVM",
"id": 504,
"is_also_category": false,
"is_extractable": true,
"skill_nature": "PATTERN",
"slug": "mvvm",
"sub_category_id": 662,
"typical_lifespan": "EVERGREEN",
"volatility": "STABLE"
},
"dimensions": [
{
"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": "MVVM",
"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": "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": "MVVM",
"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": "MVVM",
"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": "MVVM",
"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": 435,
"rationale": null,
"role_archetype": "Engineering",
"slug": "fullstack-developer",
"source": "db"
},
{
"display_name": "Fullstack Developer",
"id": 15,
"rationale": null,
"role_archetype": null,
"slug": "full-stack-engineer",
"source": "db"
}
]
},
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "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, Protocols \u0026 Compliance",
"id": 452,
"rationale": "Ensure teams adhere to industry standards, security protocols, and regulatory compliance requirements.",
"slug": "standards-protocols-compliance",
"source": "db"
},
"input_skill": "REST",
"llm_role": null,
"roles_from_db": [
{
"display_name": "Engineering Manager",
"id": 121,
"rationale": null,
"role_archetype": null,
"slug": "engineering-manager",
"source": "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": [
{
"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"
},
{
"display_name": "Fullstack Developer",
"id": 435,
"rationale": null,
"role_archetype": "Engineering",
"slug": "fullstack-developer",
"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": [],
"canonical": null,
"dimensions": [],
"input_skill": "Object-Oriented Programming",
"matched_via": null,
"new_alias_persisted": false,
"new_alias_text": null,
"new_skill_meta": {
"derived": {
"category": "Programming Concepts",
"skill_nature": "CONCEPT",
"sub_category": "general",
"typical_lifespan": "EVERGREEN",
"version_strategy": "UNVERSIONED",
"volatility": "STABLE"
},
"enrichment": null,
"keep_log": [],
"locked_dimensions": [],
"merge_log": [],
"placed": null,
"relationships": null,
"skill_id": "object-oriented-programming",
"split_log": [],
"typed": null,
"warnings": []
},
"source_tag": "llm",
"was_in_llm_skills": true
},
{
"aliases_in_db": [
{
"alias_text": "Agile",
"alias_type": "CANONICAL",
"id": 868,
"is_primary": true,
"match_strategy": "CASE_INSENSITIVE"
}
],
"canonical": {
"category_id": 8,
"display_name": "Agile",
"id": 520,
"is_also_category": false,
"is_extractable": true,
"skill_nature": "METHODOLOGY",
"slug": "agile",
"sub_category_id": 3594,
"typical_lifespan": "EVERGREEN",
"volatility": "STABLE"
},
"dimensions": [
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "React Frontend Development",
"id": 96,
"rationale": "Building interactive web user interfaces with React.js, including component composition, state management, hooks, and rendering patterns. React.js belongs here because it is a core library for client-side UI development in modern web applications.",
"slug": "d_init_01",
"source": "db"
},
"input_skill": "Agile",
"llm_role": null,
"roles_from_db": []
},
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Software Concepts, Patterns \u0026 Practices",
"id": 478,
"rationale": "Champion foundational software design patterns, development methodologies, and engineering best practices.",
"slug": "software-concepts-patterns-practices",
"source": "db"
},
"input_skill": "Agile",
"llm_role": null,
"roles_from_db": [
{
"display_name": "Engineering Manager",
"id": 121,
"rationale": null,
"role_archetype": null,
"slug": "engineering-manager",
"source": "db"
}
]
}
],
"input_skill": "Agile",
"matched_via": "alias",
"new_alias_persisted": false,
"new_alias_text": null,
"new_skill_meta": null,
"source_tag": "db",
"was_in_llm_skills": true
},
{
"aliases_in_db": [
{
"alias_text": "Git",
"alias_type": "CANONICAL",
"id": 1613,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
}
],
"canonical": {
"category_id": 13,
"display_name": "Git",
"id": 1002,
"is_also_category": false,
"is_extractable": true,
"skill_nature": "TOOL",
"slug": "git",
"sub_category_id": 730,
"typical_lifespan": "EVERGREEN",
"volatility": "STABLE"
},
"dimensions": [
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "React Frontend Development",
"id": 96,
"rationale": "Building interactive web user interfaces with React.js, including component composition, state management, hooks, and rendering patterns. React.js belongs here because it is a core library for client-side UI development in modern web applications.",
"slug": "d_init_01",
"source": "db"
},
"input_skill": "Git",
"llm_role": null,
"roles_from_db": []
}
],
"input_skill": "Git",
"matched_via": "alias",
"new_alias_persisted": false,
"new_alias_text": null,
"new_skill_meta": null,
"source_tag": "db",
"was_in_llm_skills": true
}
],
"unmatched_skills": [
"WPF",
"Object-Oriented Programming"
]
}
API 3 — final-role-output
{
"chosen_role": {
"display_name": "Desktop Application Developer",
"id": 29,
"rationale": "Domain=Software Engineering; The JD centers on C# .NET desktop/UI development with WPF, MVVM, UI controls, and Git, which best matches a desktop application developer rather than backend or web roles.",
"role_archetype": null,
"slug": "desktop-application-developer",
"source": "db"
},
"chosen_role_resolution": "in_db",
"final_input_skills": [
{
"skill": "C#",
"tag": "in_db"
},
{
"skill": ".NET",
"tag": "in_db"
},
{
"skill": "WPF",
"tag": "new"
},
{
"skill": "MVVM",
"tag": "in_db"
},
{
"skill": "REST",
"tag": "in_db"
},
{
"skill": "Dependency Injection",
"tag": "in_db"
},
{
"skill": "Object-Oriented Programming",
"tag": "new"
},
{
"skill": "Agile",
"tag": "in_db"
},
{
"skill": "Git",
"tag": "in_db"
}
],
"llm_cost_api1_usd": null,
"llm_cost_api2_usd": null,
"llm_cost_api3_usd": null,
"llm_cost_total_usd": null,
"persistence": {
"items": [
{
"chosen_role_id": 29,
"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": 29,
"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": 29,
"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": false,
"outcome_line": "Existing dimension (library) \u00b7 Role\u2194dimension skipped (dimension not under chosen role)",
"role_dimension_saved": false,
"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": "Fullstack Developer",
"id": 435,
"rationale": null,
"role_archetype": "Engineering",
"slug": "fullstack-developer",
"source": "db"
}
],
"skill_dimension_saved": true,
"skill_id": 4,
"skill_tag": "in_db",
"skipped_reason": null
},
{
"chosen_role_id": 29,
"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": 29,
"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": 29,
"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": 29,
"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": 29,
"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": 29,
"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": ".NET",
"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": 3237,
"skill_tag": "in_db",
"skipped_reason": null
},
{
"chosen_role_id": 29,
"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": "MVVM",
"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": 504,
"skill_tag": "in_db",
"skipped_reason": null
},
{
"chosen_role_id": 29,
"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": "MVVM",
"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": 504,
"skill_tag": "in_db",
"skipped_reason": null
},
{
"chosen_role_id": 29,
"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": "MVVM",
"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": 504,
"skill_tag": "in_db",
"skipped_reason": null
},
{
"chosen_role_id": 29,
"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": false,
"outcome_line": "Existing dimension (library) \u00b7 Role\u2194dimension skipped (dimension not under chosen role)",
"role_dimension_saved": false,
"roles_from_db": [
{
"display_name": "Backend Developer",
"id": 1,
"rationale": null,
"role_archetype": "A Backend Engineer designs, builds, and maintains the server-side logic and data handling that power applications and services. They focus on implementing reliable business functionality, integrating with other systems, and ensuring the backend is scalable, maintainable, and observable.",
"slug": "backend-engineer",
"source": "db"
},
{
"display_name": "Fullstack Developer",
"id": 435,
"rationale": null,
"role_archetype": "Engineering",
"slug": "fullstack-developer",
"source": "db"
},
{
"display_name": "Fullstack Developer",
"id": 15,
"rationale": null,
"role_archetype": null,
"slug": "full-stack-engineer",
"source": "db"
}
],
"skill_dimension_saved": true,
"skill_id": 11,
"skill_tag": "in_db",
"skipped_reason": null
},
{
"chosen_role_id": 29,
"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": 29,
"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": 29,
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Standards, Protocols \u0026 Compliance",
"id": 452,
"rationale": "Ensure teams adhere to industry standards, security protocols, and regulatory compliance requirements.",
"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": "Engineering Manager",
"id": 121,
"rationale": null,
"role_archetype": null,
"slug": "engineering-manager",
"source": "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": 29,
"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": 29,
"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": 29,
"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": 29,
"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"
},
{
"display_name": "Fullstack Developer",
"id": 435,
"rationale": null,
"role_archetype": "Engineering",
"slug": "fullstack-developer",
"source": "db"
}
],
"skill_dimension_saved": true,
"skill_id": 88,
"skill_tag": "in_db",
"skipped_reason": null
},
{
"chosen_role_id": 29,
"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": 29,
"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": 29,
"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": 29,
"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": 29,
"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": 29,
"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": 29,
"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": false,
"outcome_line": "Existing dimension (library) \u00b7 Role\u2194dimension skipped (dimension not under chosen role)",
"role_dimension_saved": false,
"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": 29,
"dimension": {
"difficulty_hint": "well_known",
"display_name": "React Frontend Development",
"id": 96,
"rationale": "Building interactive web user interfaces with React.js, including component composition, state management, hooks, and rendering patterns. React.js belongs here because it is a core library for client-side UI development in modern web applications.",
"slug": "d_init_01",
"source": "db"
},
"dimension_id": 96,
"input_skill": "Agile",
"llm_role": null,
"matched_chosen_role": false,
"outcome_line": "Existing dimension (library) \u00b7 Role\u2194dimension skipped (dimension not under chosen role)",
"role_dimension_saved": false,
"roles_from_db": [],
"skill_dimension_saved": true,
"skill_id": 520,
"skill_tag": "in_db",
"skipped_reason": null
},
{
"chosen_role_id": 29,
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Software Concepts, Patterns \u0026 Practices",
"id": 478,
"rationale": "Champion foundational software design patterns, development methodologies, and engineering best practices.",
"slug": "software-concepts-patterns-practices",
"source": "db"
},
"dimension_id": 478,
"input_skill": "Agile",
"llm_role": null,
"matched_chosen_role": false,
"outcome_line": "Existing dimension (library) \u00b7 Role\u2194dimension skipped (dimension not under chosen role)",
"role_dimension_saved": false,
"roles_from_db": [
{
"display_name": "Engineering Manager",
"id": 121,
"rationale": null,
"role_archetype": null,
"slug": "engineering-manager",
"source": "db"
}
],
"skill_dimension_saved": true,
"skill_id": 520,
"skill_tag": "in_db",
"skipped_reason": null
},
{
"chosen_role_id": 29,
"dimension": {
"difficulty_hint": "well_known",
"display_name": "React Frontend Development",
"id": 96,
"rationale": "Building interactive web user interfaces with React.js, including component composition, state management, hooks, and rendering patterns. React.js belongs here because it is a core library for client-side UI development in modern web applications.",
"slug": "d_init_01",
"source": "db"
},
"dimension_id": 96,
"input_skill": "Git",
"llm_role": null,
"matched_chosen_role": false,
"outcome_line": "Existing dimension (library) \u00b7 Role\u2194dimension skipped (dimension not under chosen role)",
"role_dimension_saved": false,
"roles_from_db": [],
"skill_dimension_saved": true,
"skill_id": 1002,
"skill_tag": "in_db",
"skipped_reason": null
}
],
"new_skills_created": 0,
"role_dimension_saved": 0,
"skill_dimension_saved": 0,
"skipped": 0
},
"planner_output": null,
"run_id": "1bd1614e-7b8d-49eb-8e9c-c2d64821a365"
}