Pipeline run
f73c3a4e-a52b-4f6b-8494-14e9972d52d2
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
• Build and maintain microservices using .NET Core, C#, and ASP.NET Core • Design and implement REST APIs (OpenAPI) • Develop event-driven solutions with Kafka and CDC pipelines • Work with PostgreSQL…
1 POST /skills/extract-from-jd
2 POST /skills/extract-details
3 POST /skills/final-role-output
Backend Engineer
CASE Bslug: backend-engineer · id: 1 · source: db
The primary skills align closely with the responsibilities of a Backend Engineer.
Resolution:
in_db
— role exists in library; skill↔dim and role↔dim links saved when applicable.
Job description
What you'll do • Build and maintain microservices using .NET Core, C#, and ASP.NET Core • Design and implement REST APIs (OpenAPI) • Develop event-driven solutions with Kafka and CDC pipelines • Work with PostgreSQL (schema design, performance tuning) • Contribute to backend architecture and technical improvements • Collaborate with cross-functional teams and support production systems • Leverage AI-assisted development for coding, testing, and documentation What you bring • Extensive backend development experience • Strong .NET Core / C# experience • Solid API design and database expertise (PostgreSQL, EF Core) • Experience with Kafka or event-driven architectures • Familiarity with Docker/Kubernetes (cloud + edge) • Experience using AI coding tools (e.g., GitHub Copilot) • Strong documentation and remote collaboration skills
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
- ASP.NET Core (CANONICAL) primary
- asp.net core (VERSION)
- asp.net core 8 (VERSION)
- asp.net core/.net 8 (VERSION)
- aspnetcore (VERSION)
- aspnetcore 8 (VERSION)
- net 8 (VERSION)
- net8 (VERSION)
Context tags (catalog)
Stored enrichment (catalog DB)
- Category
- Framework
- Sub-category
- Web Framework
- Vendor
- Microsoft
- License
- apache_2
- Year introduced
- 2016
- Confidence
- 0.99
- Version strategy
- SEPARATE_ENTITY
- Version tag
- 8
Maturity reasoning: Broadly adopted in enterprise web JDs and Microsoft positions it as the successor to ASP.NET for new .NET apps; strong GitHub and NuGet ecosystem activity supports continued demand.
Skill profile (library / DB)
- Skill nature
- FRAMEWORK
- Volatility
- STABLE
- Typical lifespan
- EVERGREEN
- Category id
- 5
- Sub-category id
- 35
- Extractable
- True
- Also category
- False
Dimensions (API 2 worklist)
-
Web Application Frameworks Catalog dimension db id 2
Library dimension (catalog)
Roles linked in library: Backend Engineer, Full Stack Engineer
API 3 link attempts (this skill)
| Dimension | Skill↔dim | Role↔dim | Outcome |
|---|---|---|---|
|
Web Application Frameworks
web-application-frameworks
|
— | — |
Skipped — no persistable v3 meta for new skill
skill_not_in_db_v3_proposed
|
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)
-
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 Engineer, Full Stack Engineer
-
Programming Languages for ML Systems Catalog dimension db id 39
Library dimension (catalog)
Roles linked in library: ML Engineer, ML Ops 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)
-
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 |
|---|---|---|---|
|
Cross-Platform App Languages
cross-platform-app-languages
|
✓ | — | Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role) |
|
Programming Languages
programming-languages
|
✓ | ✓ | Existing dimension (library) · Role↔dimension saved |
|
Programming Languages for ML Systems
programming-languages-for-ml-systems
|
✓ | — | Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role) |
|
Programming Languages for XR
programming-languages-for-xr
|
✓ | — | Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role) |
|
React Frontend Development
d_init_01
|
✓ | — | Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role) |
|
Video Codec Languages and DSLs
video-codec-languages-and-dsls
|
✓ | — | Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role) |
Aliases — catalog
- ASP.NET Core (CANONICAL) primary
- asp.net core (VERSION)
- asp.net core 8 (VERSION)
- asp.net core/.net 8 (VERSION)
- aspnetcore (VERSION)
- aspnetcore 8 (VERSION)
- net 8 (VERSION)
- net8 (VERSION)
Context tags (catalog)
Stored enrichment (catalog DB)
- Category
- Framework
- Sub-category
- Web Framework
- Vendor
- Microsoft
- License
- apache_2
- Year introduced
- 2016
- Confidence
- 0.99
- Version strategy
- SEPARATE_ENTITY
- Version tag
- 8
Maturity reasoning: Broadly adopted in enterprise web JDs and Microsoft positions it as the successor to ASP.NET for new .NET apps; strong GitHub and NuGet ecosystem activity supports continued demand.
Skill profile (library / DB)
- Skill nature
- FRAMEWORK
- Volatility
- STABLE
- Typical lifespan
- EVERGREEN
- Category id
- 5
- Sub-category id
- 35
- Extractable
- True
- Also category
- False
Dimensions (API 2 worklist)
-
Web Application Frameworks Catalog dimension db id 2
Library dimension (catalog)
Roles linked in library: Backend Engineer, Full Stack Engineer
API 3 link attempts (this skill)
| Dimension | Skill↔dim | Role↔dim | Outcome |
|---|---|---|---|
|
Web Application Frameworks
web-application-frameworks
|
✓ | ✓ | Existing dimension (library) · Role↔dimension saved |
Aliases — catalog
- REST (CANONICAL) primary
Context tags (catalog)
Stored enrichment (catalog DB)
- Category
- Concept
- Sub-category
- Api Architecture Style
- Year introduced
- 2000
- Confidence
- 0.88
- Version strategy
- NOT_APPLICABLE
Maturity reasoning: REST is a default API architecture in many job descriptions and is widely supported by major vendors/frameworks; OpenAPI and RESTful endpoints remain standard in hiring pipelines.
Skill profile (library / DB)
- Skill nature
- PROTOCOL
- Volatility
- STABLE
- Typical lifespan
- EVERGREEN
- Category id
- 10
- Sub-category id
- 48
- Extractable
- True
- Also category
- False
Dimensions (API 2 worklist)
-
API Design and Contracts Catalog dimension db id 3
Library dimension (catalog)
Roles linked in library: Backend Engineer, Full Stack Engineer
API 3 link attempts (this skill)
| Dimension | Skill↔dim | Role↔dim | Outcome |
|---|---|---|---|
|
API Design and Contracts
api-design-and-contracts
|
✓ | ✓ | Existing dimension (library) · Role↔dimension saved |
Aliases — catalog
- OpenAPI (CANONICAL) primary
Context tags (catalog)
Stored enrichment (catalog DB)
- Category
- Standard
- Sub-category
- Api Specification Standard
- Vendor
- OpenAPI Initiative
- License
- apache_2
- Year introduced
- 2016
- Confidence
- 0.95
- Version strategy
- NOT_APPLICABLE
Maturity reasoning: OpenAPI is widely listed in API/backend job descriptions and is the de facto standard for REST API contracts, with strong vendor support from Swagger/Redoc and broad tooling adoption across CI, docs, and codegen.
Skill profile (library / DB)
- Skill nature
- STANDARD
- Volatility
- STABLE
- Typical lifespan
- EVERGREEN
- Category id
- 12
- Sub-category id
- 1098
- Extractable
- True
- Also category
- False
Dimensions (API 2 worklist)
-
API Design and Contracts Catalog dimension db id 3
Library dimension (catalog)
Roles linked in library: Backend Engineer, Full Stack Engineer
API 3 link attempts (this skill)
| Dimension | Skill↔dim | Role↔dim | Outcome |
|---|---|---|---|
|
API Design and Contracts
api-design-and-contracts
|
✓ | ✓ | Existing dimension (library) · Role↔dimension saved |
Aliases — catalog
- Kafka (CANONICAL) primary
Context tags (catalog)
Stored enrichment (catalog DB)
- Category
- Datastore
- Sub-category
- Event Stream Store
- Vendor
- Confluent
- License
- apache_2
- Year introduced
- 2011
- Confidence
- 0.90
- Version strategy
- NOT_APPLICABLE
Maturity reasoning: Kafka appears in many production JDs for event streaming and data pipelines, and remains a standard platform in cloud/vendor offerings (e.g., Confluent, AWS MSK), indicating broad hiring demand.
Skill profile (library / DB)
- Skill nature
- PLATFORM
- Volatility
- STABLE
- Typical lifespan
- EVERGREEN
- Category id
- 9
- Sub-category id
- 47
- Extractable
- True
- Also category
- False
Dimensions (API 2 worklist)
-
Messaging and Event Streaming Catalog dimension db id 8
Library dimension (catalog)
Roles linked in library: Backend Engineer, Data Engineer
API 3 link attempts (this skill)
| Dimension | Skill↔dim | Role↔dim | Outcome |
|---|---|---|---|
|
Messaging and Event Streaming
messaging-and-event-streaming
|
✓ | ✓ | Existing dimension (library) · Role↔dimension saved |
Aliases — catalog
- Change data capture (CANONICAL) primary
Context tags (catalog)
Stored enrichment (catalog DB)
- Category
- Methodology
- Sub-category
- Data Capture Methodology
- Confidence
- 0.95
- Version strategy
- NOT_APPLICABLE
Maturity reasoning: CDC is broadly adopted in data engineering; it appears in many JDs for Kafka/Debezium/ETL roles and is a standard pattern for near-real-time replication and sync.
Skill profile (library / DB)
- Skill nature
- METHODOLOGY
- Volatility
- STABLE
- Typical lifespan
- EVERGREEN
- Category id
- 8
- Sub-category id
- 102
- Extractable
- True
- Also category
- False
Dimensions (API 2 worklist)
-
Batch Ingestion and Replication Catalog dimension db id 29
Library dimension (catalog)
Roles linked in library: Data Engineer
API 3 link attempts (this skill)
| Dimension | Skill↔dim | Role↔dim | Outcome |
|---|---|---|---|
|
Batch Ingestion and Replication
batch-ingestion-and-replication
|
✓ | — | Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role) |
Aliases — catalog
- PostgreSQL (CANONICAL) primary
- PG 13 (VERSION)
- PG 14 (VERSION)
- PG 15 (VERSION)
- PG 16 (VERSION)
- PostgreSQL 13 (VERSION)
- PostgreSQL 14 (VERSION)
- PostgreSQL 15 (VERSION)
- PostgreSQL 16 (VERSION)
- Postgres 13 (VERSION)
- Postgres 14 (VERSION)
- Postgres 15 (VERSION)
- Postgres 16 (VERSION)
- pg10 (VERSION)
- pg11 (VERSION)
- pg12 (VERSION)
- pg13 (VERSION)
- pg14 (VERSION)
- pg15 (VERSION)
- pg16 (VERSION)
- postgres (VERSION)
- postgresql 10 (VERSION)
- postgresql 11 (VERSION)
- postgresql 12 (VERSION)
- postgresql 13 (VERSION)
- postgresql 14 (VERSION)
- postgresql 15 (VERSION)
- postgresql 16 (VERSION)
- postgresql-16 (VERSION)
- postgresql10 (VERSION)
- postgresql11 (VERSION)
- postgresql12 (VERSION)
- postgresql13 (VERSION)
- postgresql14 (VERSION)
- postgresql15 (VERSION)
- postgresql16 (VERSION)
Context tags (catalog)
Stored enrichment (catalog DB)
- Category
- Datastore
- Sub-category
- Relational Database
- Vendor
- PostgreSQL Global Development Group
- License
- other_open
- Year introduced
- 1996
- Confidence
- 0.99
- Version strategy
- NOT_APPLICABLE
Maturity reasoning: PostgreSQL appears in a large share of backend/data engineering job postings and is a default managed option across AWS RDS, GCP Cloud SQL, and Azure Database, indicating broad hiring-pipeline adoption.
Skill profile (library / DB)
- Skill nature
- TOOL
- Volatility
- STABLE
- Typical lifespan
- EVERGREEN
- Category id
- 3
- Sub-category id
- 29
- Extractable
- True
- Also category
- False
Dimensions (API 2 worklist)
-
Relational Data Modeling Catalog dimension db id 216
Library dimension (catalog)
Roles linked in library: Full Stack Engineer
-
Relational Database Design Catalog dimension db id 4
Library dimension (catalog)
Roles linked in library: Backend Engineer
API 3 link attempts (this skill)
| Dimension | Skill↔dim | Role↔dim | Outcome |
|---|---|---|---|
|
Relational Data Modeling
relational-data-modeling
|
✓ | — | Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role) |
|
Relational Database Design
relational-database-design
|
✓ | ✓ | Existing dimension (library) · Role↔dimension saved |
Aliases — catalog
- Entity Framework (CANONICAL) primary
- .NET Core EF (VERSION)
- .NET Framework EF (VERSION)
- EF (VERSION)
- EF Core (VERSION)
- EF6 (VERSION)
- EFCore (VERSION)
- Entity Framework 6 (VERSION)
- Entity Framework Core (VERSION)
- EntityFramework6 (VERSION)
Context tags (catalog)
Stored enrichment (catalog DB)
- Category
- Framework
- Sub-category
- Orm Framework
- Vendor
- Microsoft
- License
- mit
- Year introduced
- 2008
- Confidence
- 0.92
- Version strategy
- SEPARATE_ENTITY
- Version tag
- 6
Maturity reasoning: Entity Framework appears frequently in .NET job descriptions and Microsoft actively maintains EF Core, indicating broad hiring demand rather than a sunset or niche tool.
Skill profile (library / DB)
- Skill nature
- FRAMEWORK
- Volatility
- STABLE
- Typical lifespan
- EVERGREEN
- Category id
- 5
- Sub-category id
- 1073
- Extractable
- True
- Also category
- False
Dimensions (API 2 worklist)
-
ORMs and Data Access Layers Catalog dimension db id 5
Library dimension (catalog)
Roles linked in library: Backend Engineer, Full Stack Engineer
API 3 link attempts (this skill)
| Dimension | Skill↔dim | Role↔dim | Outcome |
|---|---|---|---|
|
ORMs and Data Access Layers
orms-and-data-access-layers
|
✓ | ✓ | Existing dimension (library) · Role↔dimension saved |
Aliases — catalog
- Docker (CANONICAL) primary
Context tags (catalog)
Stored enrichment (catalog DB)
- Category
- Tool
- Sub-category
- Containerization Tool
- Vendor
- Docker, Inc.
- License
- apache_2
- Year introduced
- 2013
- Confidence
- 0.98
- Version strategy
- NOT_APPLICABLE
Maturity reasoning: Docker is a hiring-pipeline staple: it appears in many DevOps, backend, and platform JDs, and remains a standard containerization tool alongside Kubernetes in production stacks.
Skill profile (library / DB)
- Skill nature
- TOOL
- Volatility
- STABLE
- Typical lifespan
- EVERGREEN
- Category id
- 13
- Sub-category id
- 654
- Extractable
- True
- Also category
- False
Dimensions (API 2 worklist)
-
Containerization and Image Builds Catalog dimension db id 152
Library dimension (catalog)
Roles linked in library: DevOps Engineer
-
Deployment and Runtime Configuration Catalog dimension db id 13
Library dimension (catalog)
Roles linked in library: Backend Engineer
API 3 link attempts (this skill)
| Dimension | Skill↔dim | Role↔dim | Outcome |
|---|---|---|---|
|
Containerization and Image Builds
containerization-and-image-builds
|
✓ | — | Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role) |
|
Deployment and Runtime Configuration
deployment-and-runtime-configuration
|
✓ | ✓ | Existing dimension (library) · Role↔dimension saved |
Aliases — catalog
- Kubernetes (CANONICAL) primary
- Kubernetes 1.0+ (VERSION)
- Kubernetes 1.x (VERSION)
- Kubernetes v1 (VERSION)
- k8s (VERSION)
- kubernetes 1.x (VERSION)
- kubernetes latest (VERSION)
Context tags (catalog)
Stored enrichment (catalog DB)
- Category
- Platform
- Sub-category
- Container Orchestration Platform
- Vendor
- Cloud Native Computing Foundation
- License
- apache_2
- Year introduced
- 2014
- Confidence
- 0.90
- Version strategy
- SEPARATE_ENTITY
- Version tag
- 1.30
Maturity reasoning: Broadly adopted in cloud-native stacks; Kubernetes appears in a large share of DevOps/SRE job descriptions and is the default orchestration platform across major cloud vendors.
Skill profile (library / DB)
- Skill nature
- PLATFORM
- Volatility
- STABLE
- Typical lifespan
- EVERGREEN
- Category id
- 9
- Sub-category id
- 557
- Extractable
- True
- Also category
- False
Dimensions (API 2 worklist)
-
Container Orchestration Platforms Catalog dimension db id 134
Library dimension (catalog)
Roles linked in library: Cloud Architect, DevOps Engineer
-
Kubernetes for ML Workloads Catalog dimension db id 47
Library dimension (catalog)
Roles linked in library: ML Engineer, ML Ops Engineer
API 3 link attempts (this skill)
| Dimension | Skill↔dim | Role↔dim | Outcome |
|---|---|---|---|
|
Container Orchestration Platforms
container-orchestration-platforms
|
✓ | — | Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role) |
|
Kubernetes for ML Workloads
kubernetes-for-ml-workloads
|
✓ | — | Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role) |
Skill enrichment (orchestrator / LLM)
No Stage 7 enrichment blob on this skill (orchestrator skipped enrichment).
- Category
- Development Tools
- Sub-category
- general
- Skill nature
- TOOL
- Volatility
- MEDIUM
- Typical lifespan
- MULTI_YEAR
- Version strategy
- UNVERSIONED
All API 3 persistence rows
Same grid as the skill-extractor “Persistence items” table: one row per (skill × dimension) work item.
| Skill | Tag | Dimension | Skill↔dim | Role↔dim | Outcome | Notes |
|---|---|---|---|---|---|---|
| .NET Core | new |
Web Application Frameworks
web-application-frameworks
|
— | — | Skipped — no persistable v3 meta for new skill | skill_not_in_db_v3_proposed |
| C# | in_db |
Cross-Platform App Languages
cross-platform-app-languages
|
✓ | — | Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role) | |
| C# | in_db |
Programming Languages
programming-languages
|
✓ | ✓ | Existing dimension (library) · Role↔dimension saved | |
| C# | in_db |
Programming Languages for ML Systems
programming-languages-for-ml-systems
|
✓ | — | Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role) | |
| C# | in_db |
Programming Languages for XR
programming-languages-for-xr
|
✓ | — | Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role) | |
| C# | in_db |
React Frontend Development
d_init_01
|
✓ | — | Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role) | |
| C# | in_db |
Video Codec Languages and DSLs
video-codec-languages-and-dsls
|
✓ | — | Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role) | |
| ASP.NET Core | in_db |
Web Application Frameworks
web-application-frameworks
|
✓ | ✓ | Existing dimension (library) · Role↔dimension saved | |
| REST | in_db |
API Design and Contracts
api-design-and-contracts
|
✓ | ✓ | Existing dimension (library) · Role↔dimension saved | |
| OpenAPI | in_db |
API Design and Contracts
api-design-and-contracts
|
✓ | ✓ | Existing dimension (library) · Role↔dimension saved | |
| Kafka | in_db |
Messaging and Event Streaming
messaging-and-event-streaming
|
✓ | ✓ | Existing dimension (library) · Role↔dimension saved | |
| Change Data Capture | in_db |
Batch Ingestion and Replication
batch-ingestion-and-replication
|
✓ | — | Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role) | |
| PostgreSQL | in_db |
Relational Data Modeling
relational-data-modeling
|
✓ | — | Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role) | |
| PostgreSQL | in_db |
Relational Database Design
relational-database-design
|
✓ | ✓ | Existing dimension (library) · Role↔dimension saved | |
| EF Core | in_db |
ORMs and Data Access Layers
orms-and-data-access-layers
|
✓ | ✓ | Existing dimension (library) · Role↔dimension saved | |
| Docker | in_db |
Containerization and Image Builds
containerization-and-image-builds
|
✓ | — | Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role) | |
| Docker | in_db |
Deployment and Runtime Configuration
deployment-and-runtime-configuration
|
✓ | ✓ | Existing dimension (library) · Role↔dimension saved | |
| Kubernetes | in_db |
Container Orchestration Platforms
container-orchestration-platforms
|
✓ | — | Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role) | |
| Kubernetes | in_db |
Kubernetes for ML Workloads
kubernetes-for-ml-workloads
|
✓ | — | Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role) |
Library artifacts (this run)
| Kind | Detail | DB id |
|---|---|---|
| canonical_skill_proposed | GitHub Copilot | type=Development Tools subtype=general nature=TOOL lifespan=MULTI_YEAR | |
| dimension_skill_link_proposed | .NET Core ↔ Web Application Frameworks | |
| role_dimension_link_proposed | Backend Engineer ↔ Web Application Frameworks |
nano JD Parser — gpt-4.1-nano click to toggle
Show raw JSON
{
"JD_type": "pass",
"about_company": null,
"certifications": [],
"company_name": null,
"ctc": null,
"domain": {
"primary": {
"aliases": [],
"domain": "Other"
},
"secondary": null
},
"education": [],
"experience": null,
"job_locations": [],
"role": null,
"role_aliases": [],
"role_archetype": "Engineering",
"roles_and_responsibilities": [
{
"bullet_count": 7,
"heading": "What you\u0027ll do",
"heading_was_present": true,
"source_marker": {
"first_5_words": "\u2022 Build and maintain microservices",
"last_5_words": "coding, testing, and documentation"
},
"text": "\u2022 Build and maintain microservices using .NET Core, C#, and ASP.NET Core\n\u2022 Design and implement REST APIs (OpenAPI)\n\u2022 Develop event-driven solutions with Kafka and CDC pipelines\n\u2022 Work with PostgreSQL (schema design, performance tuning)\n\u2022 Contribute to backend architecture and technical improvements\n\u2022 Collaborate with cross-functional teams and support production systems\n\u2022 Leverage AI-assisted development for coding, testing, and documentation",
"word_count": 66
},
{
"bullet_count": 7,
"heading": "What you bring",
"heading_was_present": true,
"source_marker": {
"first_5_words": "\u2022 Extensive backend development experience",
"last_5_words": "documentation and remote collaboration skills"
},
"text": "\u2022 Extensive backend development experience\n\u2022 Strong .NET Core / C# experience\n\u2022 Solid API design and database expertise (PostgreSQL, EF Core)\n\u2022 Experience with Kafka or event-driven architectures\n\u2022 Familiarity with Docker/Kubernetes (cloud + edge)\n\u2022 Experience using AI coding tools (e.g., GitHub Copilot)\n\u2022 Strong documentation and remote collaboration skills",
"word_count": 66
}
],
"urls": []
}
API 1 — extract-from-jd click to toggle
{
"final_skills": [
{
"is_primary": true,
"skill_name": ".NET Core"
},
{
"is_primary": true,
"skill_name": "C#"
},
{
"is_primary": true,
"skill_name": "ASP.NET Core"
},
{
"is_primary": true,
"skill_name": "REST"
},
{
"is_primary": true,
"skill_name": "OpenAPI"
},
{
"is_primary": true,
"skill_name": "Kafka"
},
{
"is_primary": true,
"skill_name": "Change Data Capture"
},
{
"is_primary": true,
"skill_name": "PostgreSQL"
},
{
"is_primary": true,
"skill_name": "EF Core"
},
{
"is_primary": false,
"skill_name": "Docker"
},
{
"is_primary": false,
"skill_name": "Kubernetes"
},
{
"is_primary": false,
"skill_name": "GitHub Copilot"
}
],
"jd_role": null,
"nano_parsed": {
"JD_type": "pass",
"about_company": null,
"certifications": [],
"company_name": null,
"ctc": null,
"domain": {
"primary": {
"aliases": [],
"domain": "Other"
},
"secondary": null
},
"education": [],
"experience": null,
"job_locations": [],
"role": null,
"role_aliases": [],
"role_archetype": "Engineering",
"roles_and_responsibilities": [
{
"bullet_count": 7,
"heading": "What you\u0027ll do",
"heading_was_present": true,
"source_marker": {
"first_5_words": "\u2022 Build and maintain microservices",
"last_5_words": "coding, testing, and documentation"
},
"text": "\u2022 Build and maintain microservices using .NET Core, C#, and ASP.NET Core\n\u2022 Design and implement REST APIs (OpenAPI)\n\u2022 Develop event-driven solutions with Kafka and CDC pipelines\n\u2022 Work with PostgreSQL (schema design, performance tuning)\n\u2022 Contribute to backend architecture and technical improvements\n\u2022 Collaborate with cross-functional teams and support production systems\n\u2022 Leverage AI-assisted development for coding, testing, and documentation",
"word_count": 66
},
{
"bullet_count": 7,
"heading": "What you bring",
"heading_was_present": true,
"source_marker": {
"first_5_words": "\u2022 Extensive backend development experience",
"last_5_words": "documentation and remote collaboration skills"
},
"text": "\u2022 Extensive backend development experience\n\u2022 Strong .NET Core / C# experience\n\u2022 Solid API design and database expertise (PostgreSQL, EF Core)\n\u2022 Experience with Kafka or event-driven architectures\n\u2022 Familiarity with Docker/Kubernetes (cloud + edge)\n\u2022 Experience using AI coding tools (e.g., GitHub Copilot)\n\u2022 Strong documentation and remote collaboration skills",
"word_count": 66
}
],
"urls": []
},
"rejected": false,
"rejection_reason": null,
"run_id": "f73c3a4e-a52b-4f6b-8494-14e9972d52d2",
"stage3_signals": {
"alias_found": false,
"alias_match_roles": [],
"kra_match_roles": [
{
"display_name": "DevOps Engineer",
"matched_count": null,
"role_id": 10,
"score": 0.3993,
"slug": "devops-engineer",
"total_count": null
},
{
"display_name": "Frontend Engineer",
"matched_count": null,
"role_id": 7,
"score": 0.3938,
"slug": "frontend-engineer",
"total_count": null
},
{
"display_name": "Hybrid Mobile Developer",
"matched_count": null,
"role_id": 11,
"score": 0.3882,
"slug": "hybrid-mobile-developer",
"total_count": null
},
{
"display_name": "Android Engineer",
"matched_count": null,
"role_id": 4,
"score": 0.3774,
"slug": "android-engineer",
"total_count": null
},
{
"display_name": "Data Engineer",
"matched_count": null,
"role_id": 2,
"score": 0.3603,
"slug": "data-engineer",
"total_count": null
}
],
"skill_match_roles": [
{
"display_name": "Backend Engineer",
"matched_count": 8,
"role_id": 1,
"score": 0.6667,
"slug": "backend-engineer",
"total_count": 12
},
{
"display_name": "Full Stack Engineer",
"matched_count": 6,
"role_id": 15,
"score": 0.5,
"slug": "full-stack-engineer",
"total_count": 12
},
{
"display_name": "ML Engineer",
"matched_count": 2,
"role_id": 3,
"score": 0.1667,
"slug": "ml-engineer",
"total_count": 12
},
{
"display_name": "DevOps Engineer",
"matched_count": 2,
"role_id": 10,
"score": 0.1667,
"slug": "devops-engineer",
"total_count": 12
},
{
"display_name": "Data Engineer",
"matched_count": 2,
"role_id": 2,
"score": 0.1667,
"slug": "data-engineer",
"total_count": 12
}
]
},
"stage4_decision": {
"alias_collision_detected": false,
"case": "B",
"chosen_role": {
"display_name": "Backend Engineer",
"matched_count": null,
"role_id": 1,
"score": 0.6667,
"slug": "backend-engineer",
"total_count": null
},
"confidence": 0.6667,
"is_new_role": false,
"llm2_fired": false,
"llm2_reasoning": null,
"new_role_display_name": null,
"new_role_slug": null,
"queued": false,
"reasoning": "Stage 1 title \u0027\u0027 is unmapped (designation?); KRA inconclusive (0.40). Skill profile points at backend-engineer (0.67) - generalize."
},
"stage5_updates": {
"centroid_n_after": 34,
"centroid_updated": true,
"collision_log_id": null,
"new_kra_attached": {
"best_kra_similarity": 0.0,
"queue_id": 63,
"r_and_r_preview": "\u2022 Build and maintain microservices using .NET Core, C#, and ASP.NET Core\n\u2022 Design and implement REST APIs (OpenAPI)\n\u2022 Develop event-driven solutions with Kafka and CDC pipelines\n\u2022 Work with PostgreSQL",
"role_display_name": "Backend Engineer",
"role_slug": "backend-engineer",
"status": "pending"
},
"new_skills_attached": [
{
"is_primary": true,
"queue_id": 1661,
"role_display_name": "Backend Engineer",
"role_slug": "backend-engineer",
"skill_name": ".NET Core",
"status": "pending"
},
{
"is_primary": false,
"queue_id": 1662,
"role_display_name": "Backend Engineer",
"role_slug": "backend-engineer",
"skill_name": "GitHub Copilot",
"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": "TODO: REMOVE AFTER TESTING \u2014 alias DB write disabled",
"alias_persisted": false,
"existing_alias_id": 80,
"existing_alias_text": "ASP.NET Core",
"input_term": ".NET Core",
"matched_canonical": {
"category_id": 5,
"display_name": "ASP.NET Core",
"id": 7,
"is_also_category": false,
"is_extractable": true,
"skill_nature": "FRAMEWORK",
"slug": "asp-net-core",
"sub_category_id": 35,
"typical_lifespan": "EVERGREEN",
"volatility": "STABLE"
},
"matched_via": "embedding_alias"
},
{
"alias_persist_skipped_reason": "alias_text already exists for this canonical skill",
"alias_persisted": false,
"existing_alias_id": 52,
"existing_alias_text": "C#",
"input_term": "C#",
"matched_canonical": {
"category_id": 6,
"display_name": "C",
"id": 4,
"is_also_category": false,
"is_extractable": true,
"skill_nature": "LANGUAGE",
"slug": "c",
"sub_category_id": 96,
"typical_lifespan": "EVERGREEN",
"volatility": "STABLE"
},
"matched_via": "alias"
},
{
"alias_persist_skipped_reason": "alias_text already exists for this canonical skill",
"alias_persisted": false,
"existing_alias_id": 80,
"existing_alias_text": "ASP.NET Core",
"input_term": "ASP.NET Core",
"matched_canonical": {
"category_id": 5,
"display_name": "ASP.NET Core",
"id": 7,
"is_also_category": false,
"is_extractable": true,
"skill_nature": "FRAMEWORK",
"slug": "asp-net-core",
"sub_category_id": 35,
"typical_lifespan": "EVERGREEN",
"volatility": "STABLE"
},
"matched_via": "alias"
},
{
"alias_persist_skipped_reason": "alias_text already exists for this canonical skill",
"alias_persisted": false,
"existing_alias_id": 106,
"existing_alias_text": "REST",
"input_term": "REST",
"matched_canonical": {
"category_id": 10,
"display_name": "REST",
"id": 11,
"is_also_category": false,
"is_extractable": true,
"skill_nature": "PROTOCOL",
"slug": "rest",
"sub_category_id": 48,
"typical_lifespan": "EVERGREEN",
"volatility": "STABLE"
},
"matched_via": "alias"
},
{
"alias_persist_skipped_reason": "alias_text already exists for this canonical skill",
"alias_persisted": false,
"existing_alias_id": 109,
"existing_alias_text": "OpenAPI",
"input_term": "OpenAPI",
"matched_canonical": {
"category_id": 12,
"display_name": "OpenAPI",
"id": 14,
"is_also_category": false,
"is_extractable": true,
"skill_nature": "STANDARD",
"slug": "openapi",
"sub_category_id": 1098,
"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": 173,
"existing_alias_text": "Kafka",
"input_term": "Kafka",
"matched_canonical": {
"category_id": 9,
"display_name": "Kafka",
"id": 36,
"is_also_category": false,
"is_extractable": true,
"skill_nature": "PLATFORM",
"slug": "kafka",
"sub_category_id": 47,
"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": 344,
"existing_alias_text": "Change data capture",
"input_term": "Change Data Capture",
"matched_canonical": {
"category_id": 8,
"display_name": "Change data capture",
"id": 140,
"is_also_category": false,
"is_extractable": true,
"skill_nature": "METHODOLOGY",
"slug": "change-data-capture",
"sub_category_id": 102,
"typical_lifespan": "EVERGREEN",
"volatility": "STABLE"
},
"matched_via": "alias"
},
{
"alias_persist_skipped_reason": "alias_text already exists for this canonical skill",
"alias_persisted": false,
"existing_alias_id": 121,
"existing_alias_text": "PostgreSQL",
"input_term": "PostgreSQL",
"matched_canonical": {
"category_id": 3,
"display_name": "PostgreSQL",
"id": 16,
"is_also_category": false,
"is_extractable": true,
"skill_nature": "TOOL",
"slug": "postgresql",
"sub_category_id": 29,
"typical_lifespan": "EVERGREEN",
"volatility": "STABLE"
},
"matched_via": "alias"
},
{
"alias_persist_skipped_reason": "alias_text already exists for this canonical skill",
"alias_persisted": false,
"existing_alias_id": 152,
"existing_alias_text": "EF Core",
"input_term": "EF Core",
"matched_canonical": {
"category_id": 5,
"display_name": "Entity Framework",
"id": 22,
"is_also_category": false,
"is_extractable": true,
"skill_nature": "FRAMEWORK",
"slug": "entity-framework",
"sub_category_id": 1073,
"typical_lifespan": "EVERGREEN",
"volatility": "STABLE"
},
"matched_via": "alias"
},
{
"alias_persist_skipped_reason": "alias_text already exists for this canonical skill",
"alias_persisted": false,
"existing_alias_id": 198,
"existing_alias_text": "Docker",
"input_term": "Docker",
"matched_canonical": {
"category_id": 13,
"display_name": "Docker",
"id": 61,
"is_also_category": false,
"is_extractable": true,
"skill_nature": "TOOL",
"slug": "docker",
"sub_category_id": 654,
"typical_lifespan": "EVERGREEN",
"volatility": "STABLE"
},
"matched_via": "alias"
},
{
"alias_persist_skipped_reason": "alias_text already exists for this canonical skill",
"alias_persisted": false,
"existing_alias_id": 1267,
"existing_alias_text": "Kubernetes",
"input_term": "Kubernetes",
"matched_canonical": {
"category_id": 9,
"display_name": "Kubernetes",
"id": 726,
"is_also_category": false,
"is_extractable": true,
"skill_nature": "PLATFORM",
"slug": "kubernetes",
"sub_category_id": 557,
"typical_lifespan": "EVERGREEN",
"volatility": "STABLE"
},
"matched_via": "alias"
}
],
"candidate_roles": [
{
"display_name": "Backend Engineer",
"id": 1,
"rationale": null,
"role_archetype": "A Backend Engineer designs, builds, and maintains the server-side logic and data handling that power applications and services. They focus on implementing reliable business functionality, integrating with other systems, and ensuring the backend is scalable, maintainable, and observable.",
"slug": "backend-engineer",
"source": "db"
},
{
"display_name": "Full Stack Engineer",
"id": 15,
"rationale": null,
"role_archetype": null,
"slug": "full-stack-engineer",
"source": "db"
},
{
"display_name": "Hybrid Mobile Developer",
"id": 11,
"rationale": null,
"role_archetype": null,
"slug": "hybrid-mobile-developer",
"source": "db"
},
{
"display_name": "ML Engineer",
"id": 3,
"rationale": null,
"role_archetype": null,
"slug": "ml-engineer",
"source": "db"
},
{
"display_name": "ML Ops 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": "Video Codec Engineer",
"id": 22,
"rationale": null,
"role_archetype": null,
"slug": "video-codec-engineer",
"source": "db"
},
{
"display_name": "Data Engineer",
"id": 2,
"rationale": null,
"role_archetype": null,
"slug": "data-engineer",
"source": "db"
},
{
"display_name": "DevOps Engineer",
"id": 10,
"rationale": null,
"role_archetype": null,
"slug": "devops-engineer",
"source": "db"
},
{
"display_name": "Cloud Architect",
"id": 9,
"rationale": null,
"role_archetype": null,
"slug": "cloud-architect",
"source": "db"
}
],
"chosen_role": {
"display_name": "Backend Engineer",
"id": 1,
"rationale": "The primary skills align closely with the responsibilities of a Backend Engineer.",
"role_archetype": "A Backend Engineer designs, builds, and maintains the server-side logic and data handling that power applications and services. They focus on implementing reliable business functionality, integrating with other systems, and ensuring the backend is scalable, maintainable, and observable.",
"slug": "backend-engineer",
"source": "db"
},
"dimensions": [
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Web Application Frameworks",
"id": 2,
"rationale": "Server frameworks and runtimes used to build HTTP services, controllers, middleware, and request pipelines. These frameworks shape how backend endpoints are structured and delivered.",
"slug": "web-application-frameworks",
"source": "db"
},
"input_skill": ".NET Core",
"llm_role": null,
"roles_from_db": [
{
"display_name": "Backend Engineer",
"id": 1,
"rationale": null,
"role_archetype": "A Backend Engineer designs, builds, and maintains the server-side logic and data handling that power applications and services. They focus on implementing reliable business functionality, integrating with other systems, and ensuring the backend is scalable, maintainable, and observable.",
"slug": "backend-engineer",
"source": "db"
},
{
"display_name": "Full Stack Engineer",
"id": 15,
"rationale": null,
"role_archetype": null,
"slug": "full-stack-engineer",
"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 Engineer",
"id": 1,
"rationale": null,
"role_archetype": "A Backend Engineer designs, builds, and maintains the server-side logic and data handling that power applications and services. They focus on implementing reliable business functionality, integrating with other systems, and ensuring the backend is scalable, maintainable, and observable.",
"slug": "backend-engineer",
"source": "db"
},
{
"display_name": "Full Stack Engineer",
"id": 15,
"rationale": null,
"role_archetype": null,
"slug": "full-stack-engineer",
"source": "db"
}
]
},
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Programming Languages for ML Systems",
"id": 39,
"rationale": "Languages used to build training code, inference services, evaluation jobs, and ML glue code. This is the primary implementation surface for ML engineers across experimentation and productionization.",
"slug": "programming-languages-for-ml-systems",
"source": "db"
},
"input_skill": "C#",
"llm_role": null,
"roles_from_db": [
{
"display_name": "ML Engineer",
"id": 3,
"rationale": null,
"role_archetype": null,
"slug": "ml-engineer",
"source": "db"
},
{
"display_name": "ML Ops 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": "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": "Web Application Frameworks",
"id": 2,
"rationale": "Server frameworks and runtimes used to build HTTP services, controllers, middleware, and request pipelines. These frameworks shape how backend endpoints are structured and delivered.",
"slug": "web-application-frameworks",
"source": "db"
},
"input_skill": "ASP.NET Core",
"llm_role": null,
"roles_from_db": [
{
"display_name": "Backend Engineer",
"id": 1,
"rationale": null,
"role_archetype": "A Backend Engineer designs, builds, and maintains the server-side logic and data handling that power applications and services. They focus on implementing reliable business functionality, integrating with other systems, and ensuring the backend is scalable, maintainable, and observable.",
"slug": "backend-engineer",
"source": "db"
},
{
"display_name": "Full Stack Engineer",
"id": 15,
"rationale": null,
"role_archetype": null,
"slug": "full-stack-engineer",
"source": "db"
}
]
},
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "API Design and Contracts",
"id": 3,
"rationale": "Designing request/response shapes and the rules that govern client-server interaction. This cluster is coherent because full stack engineers often own the contract between UI behavior and backend implementation.",
"slug": "api-design-and-contracts",
"source": "db"
},
"input_skill": "REST",
"llm_role": null,
"roles_from_db": [
{
"display_name": "Backend Engineer",
"id": 1,
"rationale": null,
"role_archetype": "A Backend Engineer designs, builds, and maintains the server-side logic and data handling that power applications and services. They focus on implementing reliable business functionality, integrating with other systems, and ensuring the backend is scalable, maintainable, and observable.",
"slug": "backend-engineer",
"source": "db"
},
{
"display_name": "Full Stack Engineer",
"id": 15,
"rationale": null,
"role_archetype": null,
"slug": "full-stack-engineer",
"source": "db"
}
]
},
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "API Design and Contracts",
"id": 3,
"rationale": "Designing request/response shapes and the rules that govern client-server interaction. This cluster is coherent because full stack engineers often own the contract between UI behavior and backend implementation.",
"slug": "api-design-and-contracts",
"source": "db"
},
"input_skill": "OpenAPI",
"llm_role": null,
"roles_from_db": [
{
"display_name": "Backend Engineer",
"id": 1,
"rationale": null,
"role_archetype": "A Backend Engineer designs, builds, and maintains the server-side logic and data handling that power applications and services. They focus on implementing reliable business functionality, integrating with other systems, and ensuring the backend is scalable, maintainable, and observable.",
"slug": "backend-engineer",
"source": "db"
},
{
"display_name": "Full Stack Engineer",
"id": 15,
"rationale": null,
"role_archetype": null,
"slug": "full-stack-engineer",
"source": "db"
}
]
},
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Messaging and Event Streaming",
"id": 8,
"rationale": "Transport-layer systems used to move events and decouple producers from consumers. Data engineers use these systems to ingest, buffer, and distribute event data before downstream processing.",
"slug": "messaging-and-event-streaming",
"source": "db"
},
"input_skill": "Kafka",
"llm_role": null,
"roles_from_db": [
{
"display_name": "Backend Engineer",
"id": 1,
"rationale": null,
"role_archetype": "A Backend Engineer designs, builds, and maintains the server-side logic and data handling that power applications and services. They focus on implementing reliable business functionality, integrating with other systems, and ensuring the backend is scalable, maintainable, and observable.",
"slug": "backend-engineer",
"source": "db"
},
{
"display_name": "Data Engineer",
"id": 2,
"rationale": null,
"role_archetype": null,
"slug": "data-engineer",
"source": "db"
}
]
},
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Batch Ingestion and Replication",
"id": 29,
"rationale": "Moving data from source systems into landing zones or warehouses on batch schedules. Covers file ingestion, CDC-style replication, incremental loads, and source-to-target synchronization.",
"slug": "batch-ingestion-and-replication",
"source": "db"
},
"input_skill": "Change Data Capture",
"llm_role": null,
"roles_from_db": [
{
"display_name": "Data Engineer",
"id": 2,
"rationale": null,
"role_archetype": null,
"slug": "data-engineer",
"source": "db"
}
]
},
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Relational Data Modeling",
"id": 216,
"rationale": "Schema design and query-aware persistence for product features. Full stack engineers use this to shape tables, relationships, migrations, and transactional behavior that support application flows.",
"slug": "relational-data-modeling",
"source": "db"
},
"input_skill": "PostgreSQL",
"llm_role": null,
"roles_from_db": [
{
"display_name": "Full Stack Engineer",
"id": 15,
"rationale": null,
"role_archetype": null,
"slug": "full-stack-engineer",
"source": "db"
}
]
},
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Relational Database Design",
"id": 4,
"rationale": "Modeling and operating relational persistence for backend services. Includes schema design, normalization, indexing, transactions, and query tuning for operational data stores.",
"slug": "relational-database-design",
"source": "db"
},
"input_skill": "PostgreSQL",
"llm_role": null,
"roles_from_db": [
{
"display_name": "Backend Engineer",
"id": 1,
"rationale": null,
"role_archetype": "A Backend Engineer designs, builds, and maintains the server-side logic and data handling that power applications and services. They focus on implementing reliable business functionality, integrating with other systems, and ensuring the backend is scalable, maintainable, and observable.",
"slug": "backend-engineer",
"source": "db"
}
]
},
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "ORMs and Data Access Layers",
"id": 5,
"rationale": "Libraries and patterns used to map application objects to persistent storage and encapsulate database access. This cluster covers repository patterns, query builders, and persistence abstractions.",
"slug": "orms-and-data-access-layers",
"source": "db"
},
"input_skill": "EF Core",
"llm_role": null,
"roles_from_db": [
{
"display_name": "Backend Engineer",
"id": 1,
"rationale": null,
"role_archetype": "A Backend Engineer designs, builds, and maintains the server-side logic and data handling that power applications and services. They focus on implementing reliable business functionality, integrating with other systems, and ensuring the backend is scalable, maintainable, and observable.",
"slug": "backend-engineer",
"source": "db"
},
{
"display_name": "Full Stack Engineer",
"id": 15,
"rationale": null,
"role_archetype": null,
"slug": "full-stack-engineer",
"source": "db"
}
]
},
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Containerization and Image Builds",
"id": 152,
"rationale": "Container image creation, tagging, hardening, and registry workflows used to package services for deployment. This is coherent because DevOps often owns the build-to-image path that feeds runtime environments.",
"slug": "containerization-and-image-builds",
"source": "db"
},
"input_skill": "Docker",
"llm_role": null,
"roles_from_db": [
{
"display_name": "DevOps Engineer",
"id": 10,
"rationale": null,
"role_archetype": null,
"slug": "devops-engineer",
"source": "db"
}
]
},
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Deployment and Runtime Configuration",
"id": 13,
"rationale": "Configuration and release artifacts that control how backend services run in environments. Includes environment variables, manifests, feature flags, and release-safe configuration management.",
"slug": "deployment-and-runtime-configuration",
"source": "db"
},
"input_skill": "Docker",
"llm_role": null,
"roles_from_db": [
{
"display_name": "Backend Engineer",
"id": 1,
"rationale": null,
"role_archetype": "A Backend Engineer designs, builds, and maintains the server-side logic and data handling that power applications and services. They focus on implementing reliable business functionality, integrating with other systems, and ensuring the backend is scalable, maintainable, and observable.",
"slug": "backend-engineer",
"source": "db"
}
]
},
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Container Orchestration Platforms",
"id": 134,
"rationale": "Platforms that schedule and manage containerized workloads across clusters and environments. Cloud Architects need these to define workload placement standards, cluster boundaries, and platform capabilities.",
"slug": "container-orchestration-platforms",
"source": "db"
},
"input_skill": "Kubernetes",
"llm_role": null,
"roles_from_db": [
{
"display_name": "Cloud Architect",
"id": 9,
"rationale": null,
"role_archetype": null,
"slug": "cloud-architect",
"source": "db"
},
{
"display_name": "DevOps Engineer",
"id": 10,
"rationale": null,
"role_archetype": null,
"slug": "devops-engineer",
"source": "db"
}
]
},
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Kubernetes for ML Workloads",
"id": 47,
"rationale": "Kubernetes-native components used to schedule, accelerate, and isolate ML training and serving workloads. This includes GPU enablement and ML-specific controllers rather than generic cluster administration.",
"slug": "kubernetes-for-ml-workloads",
"source": "db"
},
"input_skill": "Kubernetes",
"llm_role": null,
"roles_from_db": [
{
"display_name": "ML Engineer",
"id": 3,
"rationale": null,
"role_archetype": null,
"slug": "ml-engineer",
"source": "db"
},
{
"display_name": "ML Ops Engineer",
"id": 16,
"rationale": null,
"role_archetype": null,
"slug": "ml-ops-engineer",
"source": "db"
}
]
}
],
"input_final_skills": [
".NET Core",
"C#",
"ASP.NET Core",
"REST",
"OpenAPI",
"Kafka",
"Change Data Capture",
"PostgreSQL",
"EF Core",
"Docker",
"Kubernetes",
"GitHub Copilot"
],
"input_llm_skills": [
".NET Core",
"C#",
"ASP.NET Core",
"REST",
"OpenAPI",
"Kafka",
"Change Data Capture",
"PostgreSQL",
"EF Core",
"Docker",
"Kubernetes",
"GitHub Copilot"
],
"new_aliases_persisted": 0,
"run_id": "f73c3a4e-a52b-4f6b-8494-14e9972d52d2",
"skills_detail": [
{
"aliases_in_db": [
{
"alias_text": "ASP.NET Core",
"alias_type": "CANONICAL",
"id": 80,
"is_primary": true,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "asp.net core",
"alias_type": "VERSION",
"id": 2298,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "asp.net core 8",
"alias_type": "VERSION",
"id": 2300,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "asp.net core/.net 8",
"alias_type": "VERSION",
"id": 2301,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "aspnetcore 8",
"alias_type": "VERSION",
"id": 2299,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "net 8",
"alias_type": "VERSION",
"id": 2297,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "net8",
"alias_type": "VERSION",
"id": 2296,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
}
],
"canonical": {
"category_id": 5,
"display_name": "ASP.NET Core",
"id": 7,
"is_also_category": false,
"is_extractable": true,
"skill_nature": "FRAMEWORK",
"slug": "asp-net-core",
"sub_category_id": 35,
"typical_lifespan": "EVERGREEN",
"volatility": "STABLE"
},
"dimensions": [
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Web Application Frameworks",
"id": 2,
"rationale": "Server frameworks and runtimes used to build HTTP services, controllers, middleware, and request pipelines. These frameworks shape how backend endpoints are structured and delivered.",
"slug": "web-application-frameworks",
"source": "db"
},
"input_skill": ".NET Core",
"llm_role": null,
"roles_from_db": [
{
"display_name": "Backend Engineer",
"id": 1,
"rationale": null,
"role_archetype": "A Backend Engineer designs, builds, and maintains the server-side logic and data handling that power applications and services. They focus on implementing reliable business functionality, integrating with other systems, and ensuring the backend is scalable, maintainable, and observable.",
"slug": "backend-engineer",
"source": "db"
},
{
"display_name": "Full Stack Engineer",
"id": 15,
"rationale": null,
"role_archetype": null,
"slug": "full-stack-engineer",
"source": "db"
}
]
}
],
"input_skill": ".NET Core",
"matched_via": "embedding_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": "C",
"alias_type": "CANONICAL",
"id": 1609,
"is_primary": true,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "C#",
"alias_type": "CANONICAL",
"id": 52,
"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": "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": "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": "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 Engineer",
"id": 1,
"rationale": null,
"role_archetype": "A Backend Engineer designs, builds, and maintains the server-side logic and data handling that power applications and services. They focus on implementing reliable business functionality, integrating with other systems, and ensuring the backend is scalable, maintainable, and observable.",
"slug": "backend-engineer",
"source": "db"
},
{
"display_name": "Full Stack Engineer",
"id": 15,
"rationale": null,
"role_archetype": null,
"slug": "full-stack-engineer",
"source": "db"
}
]
},
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Programming Languages for ML Systems",
"id": 39,
"rationale": "Languages used to build training code, inference services, evaluation jobs, and ML glue code. This is the primary implementation surface for ML engineers across experimentation and productionization.",
"slug": "programming-languages-for-ml-systems",
"source": "db"
},
"input_skill": "C#",
"llm_role": null,
"roles_from_db": [
{
"display_name": "ML Engineer",
"id": 3,
"rationale": null,
"role_archetype": null,
"slug": "ml-engineer",
"source": "db"
},
{
"display_name": "ML Ops 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": "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": "ASP.NET Core",
"alias_type": "CANONICAL",
"id": 80,
"is_primary": true,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "asp.net core",
"alias_type": "VERSION",
"id": 2298,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "asp.net core 8",
"alias_type": "VERSION",
"id": 2300,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "asp.net core/.net 8",
"alias_type": "VERSION",
"id": 2301,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "aspnetcore 8",
"alias_type": "VERSION",
"id": 2299,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "net 8",
"alias_type": "VERSION",
"id": 2297,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "net8",
"alias_type": "VERSION",
"id": 2296,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
}
],
"canonical": {
"category_id": 5,
"display_name": "ASP.NET Core",
"id": 7,
"is_also_category": false,
"is_extractable": true,
"skill_nature": "FRAMEWORK",
"slug": "asp-net-core",
"sub_category_id": 35,
"typical_lifespan": "EVERGREEN",
"volatility": "STABLE"
},
"dimensions": [
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Web Application Frameworks",
"id": 2,
"rationale": "Server frameworks and runtimes used to build HTTP services, controllers, middleware, and request pipelines. These frameworks shape how backend endpoints are structured and delivered.",
"slug": "web-application-frameworks",
"source": "db"
},
"input_skill": "ASP.NET Core",
"llm_role": null,
"roles_from_db": [
{
"display_name": "Backend Engineer",
"id": 1,
"rationale": null,
"role_archetype": "A Backend Engineer designs, builds, and maintains the server-side logic and data handling that power applications and services. They focus on implementing reliable business functionality, integrating with other systems, and ensuring the backend is scalable, maintainable, and observable.",
"slug": "backend-engineer",
"source": "db"
},
{
"display_name": "Full Stack Engineer",
"id": 15,
"rationale": null,
"role_archetype": null,
"slug": "full-stack-engineer",
"source": "db"
}
]
}
],
"input_skill": "ASP.NET Core",
"matched_via": "alias",
"new_alias_persisted": false,
"new_alias_text": null,
"new_skill_meta": null,
"source_tag": "db",
"was_in_llm_skills": true
},
{
"aliases_in_db": [
{
"alias_text": "REST",
"alias_type": "CANONICAL",
"id": 106,
"is_primary": true,
"match_strategy": "CASE_INSENSITIVE"
}
],
"canonical": {
"category_id": 10,
"display_name": "REST",
"id": 11,
"is_also_category": false,
"is_extractable": true,
"skill_nature": "PROTOCOL",
"slug": "rest",
"sub_category_id": 48,
"typical_lifespan": "EVERGREEN",
"volatility": "STABLE"
},
"dimensions": [
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "API Design and Contracts",
"id": 3,
"rationale": "Designing 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 Engineer",
"id": 1,
"rationale": null,
"role_archetype": "A Backend Engineer designs, builds, and maintains the server-side logic and data handling that power applications and services. They focus on implementing reliable business functionality, integrating with other systems, and ensuring the backend is scalable, maintainable, and observable.",
"slug": "backend-engineer",
"source": "db"
},
{
"display_name": "Full Stack Engineer",
"id": 15,
"rationale": null,
"role_archetype": null,
"slug": "full-stack-engineer",
"source": "db"
}
]
}
],
"input_skill": "REST",
"matched_via": "alias",
"new_alias_persisted": false,
"new_alias_text": null,
"new_skill_meta": null,
"source_tag": "db",
"was_in_llm_skills": true
},
{
"aliases_in_db": [
{
"alias_text": "OpenAPI",
"alias_type": "CANONICAL",
"id": 109,
"is_primary": true,
"match_strategy": "CASE_INSENSITIVE"
}
],
"canonical": {
"category_id": 12,
"display_name": "OpenAPI",
"id": 14,
"is_also_category": false,
"is_extractable": true,
"skill_nature": "STANDARD",
"slug": "openapi",
"sub_category_id": 1098,
"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": "OpenAPI",
"llm_role": null,
"roles_from_db": [
{
"display_name": "Backend Engineer",
"id": 1,
"rationale": null,
"role_archetype": "A Backend Engineer designs, builds, and maintains the server-side logic and data handling that power applications and services. They focus on implementing reliable business functionality, integrating with other systems, and ensuring the backend is scalable, maintainable, and observable.",
"slug": "backend-engineer",
"source": "db"
},
{
"display_name": "Full Stack Engineer",
"id": 15,
"rationale": null,
"role_archetype": null,
"slug": "full-stack-engineer",
"source": "db"
}
]
}
],
"input_skill": "OpenAPI",
"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": "Kafka",
"alias_type": "CANONICAL",
"id": 173,
"is_primary": true,
"match_strategy": "CASE_INSENSITIVE"
}
],
"canonical": {
"category_id": 9,
"display_name": "Kafka",
"id": 36,
"is_also_category": false,
"is_extractable": true,
"skill_nature": "PLATFORM",
"slug": "kafka",
"sub_category_id": 47,
"typical_lifespan": "EVERGREEN",
"volatility": "STABLE"
},
"dimensions": [
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Messaging and Event Streaming",
"id": 8,
"rationale": "Transport-layer systems used to move events and decouple producers from consumers. Data engineers use these systems to ingest, buffer, and distribute event data before downstream processing.",
"slug": "messaging-and-event-streaming",
"source": "db"
},
"input_skill": "Kafka",
"llm_role": null,
"roles_from_db": [
{
"display_name": "Backend Engineer",
"id": 1,
"rationale": null,
"role_archetype": "A Backend Engineer designs, builds, and maintains the server-side logic and data handling that power applications and services. They focus on implementing reliable business functionality, integrating with other systems, and ensuring the backend is scalable, maintainable, and observable.",
"slug": "backend-engineer",
"source": "db"
},
{
"display_name": "Data Engineer",
"id": 2,
"rationale": null,
"role_archetype": null,
"slug": "data-engineer",
"source": "db"
}
]
}
],
"input_skill": "Kafka",
"matched_via": "alias",
"new_alias_persisted": false,
"new_alias_text": null,
"new_skill_meta": null,
"source_tag": "db",
"was_in_llm_skills": true
},
{
"aliases_in_db": [
{
"alias_text": "Change data capture",
"alias_type": "CANONICAL",
"id": 344,
"is_primary": true,
"match_strategy": "CASE_INSENSITIVE"
}
],
"canonical": {
"category_id": 8,
"display_name": "Change data capture",
"id": 140,
"is_also_category": false,
"is_extractable": true,
"skill_nature": "METHODOLOGY",
"slug": "change-data-capture",
"sub_category_id": 102,
"typical_lifespan": "EVERGREEN",
"volatility": "STABLE"
},
"dimensions": [
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Batch Ingestion and Replication",
"id": 29,
"rationale": "Moving data from source systems into landing zones or warehouses on batch schedules. Covers file ingestion, CDC-style replication, incremental loads, and source-to-target synchronization.",
"slug": "batch-ingestion-and-replication",
"source": "db"
},
"input_skill": "Change Data Capture",
"llm_role": null,
"roles_from_db": [
{
"display_name": "Data Engineer",
"id": 2,
"rationale": null,
"role_archetype": null,
"slug": "data-engineer",
"source": "db"
}
]
}
],
"input_skill": "Change Data Capture",
"matched_via": "alias",
"new_alias_persisted": false,
"new_alias_text": null,
"new_skill_meta": null,
"source_tag": "db",
"was_in_llm_skills": true
},
{
"aliases_in_db": [
{
"alias_text": "PostgreSQL",
"alias_type": "CANONICAL",
"id": 121,
"is_primary": true,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "PG 13",
"alias_type": "VERSION",
"id": 122,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "PG 14",
"alias_type": "VERSION",
"id": 123,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "PG 15",
"alias_type": "VERSION",
"id": 124,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "PG 16",
"alias_type": "VERSION",
"id": 125,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "PostgreSQL 13",
"alias_type": "VERSION",
"id": 130,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "PostgreSQL 14",
"alias_type": "VERSION",
"id": 131,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "PostgreSQL 15",
"alias_type": "VERSION",
"id": 132,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "PostgreSQL 16",
"alias_type": "VERSION",
"id": 133,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "Postgres 13",
"alias_type": "VERSION",
"id": 126,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "Postgres 14",
"alias_type": "VERSION",
"id": 127,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "Postgres 15",
"alias_type": "VERSION",
"id": 128,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "Postgres 16",
"alias_type": "VERSION",
"id": 129,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
}
],
"canonical": {
"category_id": 3,
"display_name": "PostgreSQL",
"id": 16,
"is_also_category": false,
"is_extractable": true,
"skill_nature": "TOOL",
"slug": "postgresql",
"sub_category_id": 29,
"typical_lifespan": "EVERGREEN",
"volatility": "STABLE"
},
"dimensions": [
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Relational Data Modeling",
"id": 216,
"rationale": "Schema design and query-aware persistence for product features. Full stack engineers use this to shape tables, relationships, migrations, and transactional behavior that support application flows.",
"slug": "relational-data-modeling",
"source": "db"
},
"input_skill": "PostgreSQL",
"llm_role": null,
"roles_from_db": [
{
"display_name": "Full Stack Engineer",
"id": 15,
"rationale": null,
"role_archetype": null,
"slug": "full-stack-engineer",
"source": "db"
}
]
},
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Relational Database Design",
"id": 4,
"rationale": "Modeling and operating relational persistence for backend services. Includes schema design, normalization, indexing, transactions, and query tuning for operational data stores.",
"slug": "relational-database-design",
"source": "db"
},
"input_skill": "PostgreSQL",
"llm_role": null,
"roles_from_db": [
{
"display_name": "Backend Engineer",
"id": 1,
"rationale": null,
"role_archetype": "A Backend Engineer designs, builds, and maintains the server-side logic and data handling that power applications and services. They focus on implementing reliable business functionality, integrating with other systems, and ensuring the backend is scalable, maintainable, and observable.",
"slug": "backend-engineer",
"source": "db"
}
]
}
],
"input_skill": "PostgreSQL",
"matched_via": "alias",
"new_alias_persisted": false,
"new_alias_text": null,
"new_skill_meta": null,
"source_tag": "db",
"was_in_llm_skills": true
},
{
"aliases_in_db": [
{
"alias_text": "Entity Framework",
"alias_type": "CANONICAL",
"id": 150,
"is_primary": true,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": ".NET Core EF",
"alias_type": "VERSION",
"id": 153,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": ".NET Framework EF",
"alias_type": "VERSION",
"id": 154,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "EF",
"alias_type": "VERSION",
"id": 2317,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "EF Core",
"alias_type": "VERSION",
"id": 152,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "EF6",
"alias_type": "VERSION",
"id": 151,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "EFCore",
"alias_type": "VERSION",
"id": 2319,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "Entity Framework 6",
"alias_type": "VERSION",
"id": 155,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "Entity Framework Core",
"alias_type": "VERSION",
"id": 2323,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "EntityFramework6",
"alias_type": "VERSION",
"id": 2321,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
}
],
"canonical": {
"category_id": 5,
"display_name": "Entity Framework",
"id": 22,
"is_also_category": false,
"is_extractable": true,
"skill_nature": "FRAMEWORK",
"slug": "entity-framework",
"sub_category_id": 1073,
"typical_lifespan": "EVERGREEN",
"volatility": "STABLE"
},
"dimensions": [
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "ORMs and Data Access Layers",
"id": 5,
"rationale": "Libraries and patterns used to map application objects to persistent storage and encapsulate database access. This cluster covers repository patterns, query builders, and persistence abstractions.",
"slug": "orms-and-data-access-layers",
"source": "db"
},
"input_skill": "EF Core",
"llm_role": null,
"roles_from_db": [
{
"display_name": "Backend Engineer",
"id": 1,
"rationale": null,
"role_archetype": "A Backend Engineer designs, builds, and maintains the server-side logic and data handling that power applications and services. They focus on implementing reliable business functionality, integrating with other systems, and ensuring the backend is scalable, maintainable, and observable.",
"slug": "backend-engineer",
"source": "db"
},
{
"display_name": "Full Stack Engineer",
"id": 15,
"rationale": null,
"role_archetype": null,
"slug": "full-stack-engineer",
"source": "db"
}
]
}
],
"input_skill": "EF Core",
"matched_via": "alias",
"new_alias_persisted": false,
"new_alias_text": null,
"new_skill_meta": null,
"source_tag": "db",
"was_in_llm_skills": true
},
{
"aliases_in_db": [
{
"alias_text": "Docker",
"alias_type": "CANONICAL",
"id": 198,
"is_primary": true,
"match_strategy": "CASE_INSENSITIVE"
}
],
"canonical": {
"category_id": 13,
"display_name": "Docker",
"id": 61,
"is_also_category": false,
"is_extractable": true,
"skill_nature": "TOOL",
"slug": "docker",
"sub_category_id": 654,
"typical_lifespan": "EVERGREEN",
"volatility": "STABLE"
},
"dimensions": [
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Containerization and Image Builds",
"id": 152,
"rationale": "Container image creation, tagging, hardening, and registry workflows used to package services for deployment. This is coherent because DevOps often owns the build-to-image path that feeds runtime environments.",
"slug": "containerization-and-image-builds",
"source": "db"
},
"input_skill": "Docker",
"llm_role": null,
"roles_from_db": [
{
"display_name": "DevOps Engineer",
"id": 10,
"rationale": null,
"role_archetype": null,
"slug": "devops-engineer",
"source": "db"
}
]
},
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Deployment and Runtime Configuration",
"id": 13,
"rationale": "Configuration and release artifacts that control how backend services run in environments. Includes environment variables, manifests, feature flags, and release-safe configuration management.",
"slug": "deployment-and-runtime-configuration",
"source": "db"
},
"input_skill": "Docker",
"llm_role": null,
"roles_from_db": [
{
"display_name": "Backend Engineer",
"id": 1,
"rationale": null,
"role_archetype": "A Backend Engineer designs, builds, and maintains the server-side logic and data handling that power applications and services. They focus on implementing reliable business functionality, integrating with other systems, and ensuring the backend is scalable, maintainable, and observable.",
"slug": "backend-engineer",
"source": "db"
}
]
}
],
"input_skill": "Docker",
"matched_via": "alias",
"new_alias_persisted": false,
"new_alias_text": null,
"new_skill_meta": null,
"source_tag": "db",
"was_in_llm_skills": true
},
{
"aliases_in_db": [
{
"alias_text": "Kubernetes",
"alias_type": "CANONICAL",
"id": 1267,
"is_primary": true,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "Kubernetes 1.0+",
"alias_type": "VERSION",
"id": 1271,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "Kubernetes 1.x",
"alias_type": "VERSION",
"id": 1270,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "Kubernetes v1",
"alias_type": "VERSION",
"id": 1269,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "k8s",
"alias_type": "VERSION",
"id": 1268,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "kubernetes 1.x",
"alias_type": "VERSION",
"id": 1400,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "kubernetes latest",
"alias_type": "VERSION",
"id": 1401,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
}
],
"canonical": {
"category_id": 9,
"display_name": "Kubernetes",
"id": 726,
"is_also_category": false,
"is_extractable": true,
"skill_nature": "PLATFORM",
"slug": "kubernetes",
"sub_category_id": 557,
"typical_lifespan": "EVERGREEN",
"volatility": "STABLE"
},
"dimensions": [
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Container Orchestration Platforms",
"id": 134,
"rationale": "Platforms that schedule and manage containerized workloads across clusters and environments. Cloud Architects need these to define workload placement standards, cluster boundaries, and platform capabilities.",
"slug": "container-orchestration-platforms",
"source": "db"
},
"input_skill": "Kubernetes",
"llm_role": null,
"roles_from_db": [
{
"display_name": "Cloud Architect",
"id": 9,
"rationale": null,
"role_archetype": null,
"slug": "cloud-architect",
"source": "db"
},
{
"display_name": "DevOps Engineer",
"id": 10,
"rationale": null,
"role_archetype": null,
"slug": "devops-engineer",
"source": "db"
}
]
},
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Kubernetes for ML Workloads",
"id": 47,
"rationale": "Kubernetes-native components used to schedule, accelerate, and isolate ML training and serving workloads. This includes GPU enablement and ML-specific controllers rather than generic cluster administration.",
"slug": "kubernetes-for-ml-workloads",
"source": "db"
},
"input_skill": "Kubernetes",
"llm_role": null,
"roles_from_db": [
{
"display_name": "ML Engineer",
"id": 3,
"rationale": null,
"role_archetype": null,
"slug": "ml-engineer",
"source": "db"
},
{
"display_name": "ML Ops Engineer",
"id": 16,
"rationale": null,
"role_archetype": null,
"slug": "ml-ops-engineer",
"source": "db"
}
]
}
],
"input_skill": "Kubernetes",
"matched_via": "alias",
"new_alias_persisted": false,
"new_alias_text": null,
"new_skill_meta": null,
"source_tag": "db",
"was_in_llm_skills": true
},
{
"aliases_in_db": [],
"canonical": null,
"dimensions": [],
"input_skill": "GitHub Copilot",
"matched_via": null,
"new_alias_persisted": false,
"new_alias_text": null,
"new_skill_meta": {
"derived": {
"category": "Development Tools",
"skill_nature": "TOOL",
"sub_category": "general",
"typical_lifespan": "MULTI_YEAR",
"version_strategy": "UNVERSIONED",
"volatility": "MEDIUM"
},
"enrichment": null,
"keep_log": [],
"locked_dimensions": [],
"merge_log": [],
"placed": null,
"relationships": null,
"skill_id": "github-copilot",
"split_log": [],
"typed": null,
"warnings": []
},
"source_tag": "llm",
"was_in_llm_skills": true
}
],
"unmatched_skills": [
"GitHub Copilot"
]
}
API 3 — final-role-output
{
"chosen_role": {
"display_name": "Backend Engineer",
"id": 1,
"rationale": "The primary skills align closely with the responsibilities of a Backend Engineer.",
"role_archetype": "A Backend Engineer designs, builds, and maintains the server-side logic and data handling that power applications and services. They focus on implementing reliable business functionality, integrating with other systems, and ensuring the backend is scalable, maintainable, and observable.",
"slug": "backend-engineer",
"source": "db"
},
"chosen_role_resolution": "in_db",
"final_input_skills": [
{
"skill": ".NET Core",
"tag": "in_db"
},
{
"skill": "C#",
"tag": "in_db"
},
{
"skill": "ASP.NET Core",
"tag": "in_db"
},
{
"skill": "REST",
"tag": "in_db"
},
{
"skill": "OpenAPI",
"tag": "in_db"
},
{
"skill": "Kafka",
"tag": "in_db"
},
{
"skill": "Change Data Capture",
"tag": "in_db"
},
{
"skill": "PostgreSQL",
"tag": "in_db"
},
{
"skill": "EF Core",
"tag": "in_db"
},
{
"skill": "Docker",
"tag": "in_db"
},
{
"skill": "Kubernetes",
"tag": "in_db"
},
{
"skill": "GitHub Copilot",
"tag": "new"
}
],
"llm_cost_api1_usd": null,
"llm_cost_api2_usd": null,
"llm_cost_api3_usd": null,
"llm_cost_total_usd": null,
"persistence": {
"items": [
{
"chosen_role_id": 1,
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Web Application Frameworks",
"id": 2,
"rationale": "Server frameworks and runtimes used to build HTTP services, controllers, middleware, and request pipelines. These frameworks shape how backend endpoints are structured and delivered.",
"slug": "web-application-frameworks",
"source": "db"
},
"dimension_id": 2,
"input_skill": ".NET Core",
"llm_role": null,
"matched_chosen_role": true,
"outcome_line": "Skipped \u2014 no persistable v3 meta for new skill",
"role_dimension_saved": false,
"roles_from_db": [
{
"display_name": "Backend Engineer",
"id": 1,
"rationale": null,
"role_archetype": "A Backend Engineer designs, builds, and maintains the server-side logic and data handling that power applications and services. They focus on implementing reliable business functionality, integrating with other systems, and ensuring the backend is scalable, maintainable, and observable.",
"slug": "backend-engineer",
"source": "db"
},
{
"display_name": "Full Stack Engineer",
"id": 15,
"rationale": null,
"role_archetype": null,
"slug": "full-stack-engineer",
"source": "db"
}
],
"skill_dimension_saved": false,
"skill_id": null,
"skill_tag": "new",
"skipped_reason": "skill_not_in_db_v3_proposed"
},
{
"chosen_role_id": 1,
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Cross-Platform App Languages",
"id": 167,
"rationale": "Languages used to implement shared mobile features across iOS and Android from a common codebase. This is the primary coding surface for hybrid app logic, UI behavior, and platform-specific branching.",
"slug": "cross-platform-app-languages",
"source": "db"
},
"dimension_id": 167,
"input_skill": "C#",
"llm_role": null,
"matched_chosen_role": false,
"outcome_line": "Existing dimension (library) \u00b7 Role\u2194dimension skipped (dimension not under chosen role)",
"role_dimension_saved": false,
"roles_from_db": [
{
"display_name": "Hybrid Mobile Developer",
"id": 11,
"rationale": null,
"role_archetype": null,
"slug": "hybrid-mobile-developer",
"source": "db"
}
],
"skill_dimension_saved": true,
"skill_id": 4,
"skill_tag": "in_db",
"skipped_reason": null
},
{
"chosen_role_id": 1,
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Programming Languages",
"id": 1,
"rationale": "Primary implementation languages used to build client and server feature code. Full stack engineers need enough fluency to move across layers and implement product behavior end to end.",
"slug": "programming-languages",
"source": "db"
},
"dimension_id": 1,
"input_skill": "C#",
"llm_role": null,
"matched_chosen_role": true,
"outcome_line": "Existing dimension (library) \u00b7 Role\u2194dimension saved",
"role_dimension_saved": true,
"roles_from_db": [
{
"display_name": "Backend Engineer",
"id": 1,
"rationale": null,
"role_archetype": "A Backend Engineer designs, builds, and maintains the server-side logic and data handling that power applications and services. They focus on implementing reliable business functionality, integrating with other systems, and ensuring the backend is scalable, maintainable, and observable.",
"slug": "backend-engineer",
"source": "db"
},
{
"display_name": "Full Stack Engineer",
"id": 15,
"rationale": null,
"role_archetype": null,
"slug": "full-stack-engineer",
"source": "db"
}
],
"skill_dimension_saved": true,
"skill_id": 4,
"skill_tag": "in_db",
"skipped_reason": null
},
{
"chosen_role_id": 1,
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Programming Languages for ML Systems",
"id": 39,
"rationale": "Languages used to build training code, inference services, evaluation jobs, and ML glue code. This is the primary implementation surface for ML engineers across experimentation and productionization.",
"slug": "programming-languages-for-ml-systems",
"source": "db"
},
"dimension_id": 39,
"input_skill": "C#",
"llm_role": null,
"matched_chosen_role": false,
"outcome_line": "Existing dimension (library) \u00b7 Role\u2194dimension skipped (dimension not under chosen role)",
"role_dimension_saved": false,
"roles_from_db": [
{
"display_name": "ML Engineer",
"id": 3,
"rationale": null,
"role_archetype": null,
"slug": "ml-engineer",
"source": "db"
},
{
"display_name": "ML Ops Engineer",
"id": 16,
"rationale": null,
"role_archetype": null,
"slug": "ml-ops-engineer",
"source": "db"
}
],
"skill_dimension_saved": true,
"skill_id": 4,
"skill_tag": "in_db",
"skipped_reason": null
},
{
"chosen_role_id": 1,
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Programming Languages for XR",
"id": 97,
"rationale": "Primary implementation languages used to build immersive client features, interaction logic, and device-specific runtime behavior. This is the core coding surface for AR/VR experiences.",
"slug": "programming-languages-for-xr",
"source": "db"
},
"dimension_id": 97,
"input_skill": "C#",
"llm_role": null,
"matched_chosen_role": false,
"outcome_line": "Existing dimension (library) \u00b7 Role\u2194dimension skipped (dimension not under chosen role)",
"role_dimension_saved": false,
"roles_from_db": [
{
"display_name": "AR/VR Engineer",
"id": 8,
"rationale": null,
"role_archetype": null,
"slug": "ar-vr-engineer",
"source": "db"
}
],
"skill_dimension_saved": true,
"skill_id": 4,
"skill_tag": "in_db",
"skipped_reason": null
},
{
"chosen_role_id": 1,
"dimension": {
"difficulty_hint": "well_known",
"display_name": "React Frontend Development",
"id": 96,
"rationale": "Building interactive web user interfaces with React.js, including component composition, state management, hooks, and rendering patterns. React.js belongs here because it is a core library for client-side UI development in modern web applications.",
"slug": "d_init_01",
"source": "db"
},
"dimension_id": 96,
"input_skill": "C#",
"llm_role": null,
"matched_chosen_role": false,
"outcome_line": "Existing dimension (library) \u00b7 Role\u2194dimension skipped (dimension not under chosen role)",
"role_dimension_saved": false,
"roles_from_db": [],
"skill_dimension_saved": true,
"skill_id": 4,
"skill_tag": "in_db",
"skipped_reason": null
},
{
"chosen_role_id": 1,
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Video Codec Languages and DSLs",
"id": 225,
"rationale": "Implementation languages and codec-specific description languages used to build compression, decoding, and transform logic. This is the primary coding surface for codec behavior and bitstream manipulation.",
"slug": "video-codec-languages-and-dsls",
"source": "db"
},
"dimension_id": 225,
"input_skill": "C#",
"llm_role": null,
"matched_chosen_role": false,
"outcome_line": "Existing dimension (library) \u00b7 Role\u2194dimension skipped (dimension not under chosen role)",
"role_dimension_saved": false,
"roles_from_db": [
{
"display_name": "Video Codec Engineer",
"id": 22,
"rationale": null,
"role_archetype": null,
"slug": "video-codec-engineer",
"source": "db"
}
],
"skill_dimension_saved": true,
"skill_id": 4,
"skill_tag": "in_db",
"skipped_reason": null
},
{
"chosen_role_id": 1,
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Web Application Frameworks",
"id": 2,
"rationale": "Server frameworks and runtimes used to build HTTP services, controllers, middleware, and request pipelines. These frameworks shape how backend endpoints are structured and delivered.",
"slug": "web-application-frameworks",
"source": "db"
},
"dimension_id": 2,
"input_skill": "ASP.NET Core",
"llm_role": null,
"matched_chosen_role": true,
"outcome_line": "Existing dimension (library) \u00b7 Role\u2194dimension saved",
"role_dimension_saved": true,
"roles_from_db": [
{
"display_name": "Backend Engineer",
"id": 1,
"rationale": null,
"role_archetype": "A Backend Engineer designs, builds, and maintains the server-side logic and data handling that power applications and services. They focus on implementing reliable business functionality, integrating with other systems, and ensuring the backend is scalable, maintainable, and observable.",
"slug": "backend-engineer",
"source": "db"
},
{
"display_name": "Full Stack Engineer",
"id": 15,
"rationale": null,
"role_archetype": null,
"slug": "full-stack-engineer",
"source": "db"
}
],
"skill_dimension_saved": true,
"skill_id": 7,
"skill_tag": "in_db",
"skipped_reason": null
},
{
"chosen_role_id": 1,
"dimension": {
"difficulty_hint": "well_known",
"display_name": "API Design and Contracts",
"id": 3,
"rationale": "Designing request/response shapes and the rules that govern client-server interaction. This cluster is coherent because full stack engineers often own the contract between UI behavior and backend implementation.",
"slug": "api-design-and-contracts",
"source": "db"
},
"dimension_id": 3,
"input_skill": "REST",
"llm_role": null,
"matched_chosen_role": true,
"outcome_line": "Existing dimension (library) \u00b7 Role\u2194dimension saved",
"role_dimension_saved": true,
"roles_from_db": [
{
"display_name": "Backend Engineer",
"id": 1,
"rationale": null,
"role_archetype": "A Backend Engineer designs, builds, and maintains the server-side logic and data handling that power applications and services. They focus on implementing reliable business functionality, integrating with other systems, and ensuring the backend is scalable, maintainable, and observable.",
"slug": "backend-engineer",
"source": "db"
},
{
"display_name": "Full Stack Engineer",
"id": 15,
"rationale": null,
"role_archetype": null,
"slug": "full-stack-engineer",
"source": "db"
}
],
"skill_dimension_saved": true,
"skill_id": 11,
"skill_tag": "in_db",
"skipped_reason": null
},
{
"chosen_role_id": 1,
"dimension": {
"difficulty_hint": "well_known",
"display_name": "API 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": "OpenAPI",
"llm_role": null,
"matched_chosen_role": true,
"outcome_line": "Existing dimension (library) \u00b7 Role\u2194dimension saved",
"role_dimension_saved": true,
"roles_from_db": [
{
"display_name": "Backend Engineer",
"id": 1,
"rationale": null,
"role_archetype": "A Backend Engineer designs, builds, and maintains the server-side logic and data handling that power applications and services. They focus on implementing reliable business functionality, integrating with other systems, and ensuring the backend is scalable, maintainable, and observable.",
"slug": "backend-engineer",
"source": "db"
},
{
"display_name": "Full Stack Engineer",
"id": 15,
"rationale": null,
"role_archetype": null,
"slug": "full-stack-engineer",
"source": "db"
}
],
"skill_dimension_saved": true,
"skill_id": 14,
"skill_tag": "in_db",
"skipped_reason": null
},
{
"chosen_role_id": 1,
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Messaging and Event Streaming",
"id": 8,
"rationale": "Transport-layer systems used to move events and decouple producers from consumers. Data engineers use these systems to ingest, buffer, and distribute event data before downstream processing.",
"slug": "messaging-and-event-streaming",
"source": "db"
},
"dimension_id": 8,
"input_skill": "Kafka",
"llm_role": null,
"matched_chosen_role": true,
"outcome_line": "Existing dimension (library) \u00b7 Role\u2194dimension saved",
"role_dimension_saved": true,
"roles_from_db": [
{
"display_name": "Backend Engineer",
"id": 1,
"rationale": null,
"role_archetype": "A Backend Engineer designs, builds, and maintains the server-side logic and data handling that power applications and services. They focus on implementing reliable business functionality, integrating with other systems, and ensuring the backend is scalable, maintainable, and observable.",
"slug": "backend-engineer",
"source": "db"
},
{
"display_name": "Data Engineer",
"id": 2,
"rationale": null,
"role_archetype": null,
"slug": "data-engineer",
"source": "db"
}
],
"skill_dimension_saved": true,
"skill_id": 36,
"skill_tag": "in_db",
"skipped_reason": null
},
{
"chosen_role_id": 1,
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Batch Ingestion and Replication",
"id": 29,
"rationale": "Moving data from source systems into landing zones or warehouses on batch schedules. Covers file ingestion, CDC-style replication, incremental loads, and source-to-target synchronization.",
"slug": "batch-ingestion-and-replication",
"source": "db"
},
"dimension_id": 29,
"input_skill": "Change Data Capture",
"llm_role": null,
"matched_chosen_role": false,
"outcome_line": "Existing dimension (library) \u00b7 Role\u2194dimension skipped (dimension not under chosen role)",
"role_dimension_saved": false,
"roles_from_db": [
{
"display_name": "Data Engineer",
"id": 2,
"rationale": null,
"role_archetype": null,
"slug": "data-engineer",
"source": "db"
}
],
"skill_dimension_saved": true,
"skill_id": 140,
"skill_tag": "in_db",
"skipped_reason": null
},
{
"chosen_role_id": 1,
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Relational Data Modeling",
"id": 216,
"rationale": "Schema design and query-aware persistence for product features. Full stack engineers use this to shape tables, relationships, migrations, and transactional behavior that support application flows.",
"slug": "relational-data-modeling",
"source": "db"
},
"dimension_id": 216,
"input_skill": "PostgreSQL",
"llm_role": null,
"matched_chosen_role": false,
"outcome_line": "Existing dimension (library) \u00b7 Role\u2194dimension skipped (dimension not under chosen role)",
"role_dimension_saved": false,
"roles_from_db": [
{
"display_name": "Full Stack Engineer",
"id": 15,
"rationale": null,
"role_archetype": null,
"slug": "full-stack-engineer",
"source": "db"
}
],
"skill_dimension_saved": true,
"skill_id": 16,
"skill_tag": "in_db",
"skipped_reason": null
},
{
"chosen_role_id": 1,
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Relational Database Design",
"id": 4,
"rationale": "Modeling and operating relational persistence for backend services. Includes schema design, normalization, indexing, transactions, and query tuning for operational data stores.",
"slug": "relational-database-design",
"source": "db"
},
"dimension_id": 4,
"input_skill": "PostgreSQL",
"llm_role": null,
"matched_chosen_role": true,
"outcome_line": "Existing dimension (library) \u00b7 Role\u2194dimension saved",
"role_dimension_saved": true,
"roles_from_db": [
{
"display_name": "Backend Engineer",
"id": 1,
"rationale": null,
"role_archetype": "A Backend Engineer designs, builds, and maintains the server-side logic and data handling that power applications and services. They focus on implementing reliable business functionality, integrating with other systems, and ensuring the backend is scalable, maintainable, and observable.",
"slug": "backend-engineer",
"source": "db"
}
],
"skill_dimension_saved": true,
"skill_id": 16,
"skill_tag": "in_db",
"skipped_reason": null
},
{
"chosen_role_id": 1,
"dimension": {
"difficulty_hint": "well_known",
"display_name": "ORMs and Data Access Layers",
"id": 5,
"rationale": "Libraries and patterns used to map application objects to persistent storage and encapsulate database access. This cluster covers repository patterns, query builders, and persistence abstractions.",
"slug": "orms-and-data-access-layers",
"source": "db"
},
"dimension_id": 5,
"input_skill": "EF Core",
"llm_role": null,
"matched_chosen_role": true,
"outcome_line": "Existing dimension (library) \u00b7 Role\u2194dimension saved",
"role_dimension_saved": true,
"roles_from_db": [
{
"display_name": "Backend Engineer",
"id": 1,
"rationale": null,
"role_archetype": "A Backend Engineer designs, builds, and maintains the server-side logic and data handling that power applications and services. They focus on implementing reliable business functionality, integrating with other systems, and ensuring the backend is scalable, maintainable, and observable.",
"slug": "backend-engineer",
"source": "db"
},
{
"display_name": "Full Stack Engineer",
"id": 15,
"rationale": null,
"role_archetype": null,
"slug": "full-stack-engineer",
"source": "db"
}
],
"skill_dimension_saved": true,
"skill_id": 22,
"skill_tag": "in_db",
"skipped_reason": null
},
{
"chosen_role_id": 1,
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Containerization and Image Builds",
"id": 152,
"rationale": "Container image creation, tagging, hardening, and registry workflows used to package services for deployment. This is coherent because DevOps often owns the build-to-image path that feeds runtime environments.",
"slug": "containerization-and-image-builds",
"source": "db"
},
"dimension_id": 152,
"input_skill": "Docker",
"llm_role": null,
"matched_chosen_role": false,
"outcome_line": "Existing dimension (library) \u00b7 Role\u2194dimension skipped (dimension not under chosen role)",
"role_dimension_saved": false,
"roles_from_db": [
{
"display_name": "DevOps Engineer",
"id": 10,
"rationale": null,
"role_archetype": null,
"slug": "devops-engineer",
"source": "db"
}
],
"skill_dimension_saved": true,
"skill_id": 61,
"skill_tag": "in_db",
"skipped_reason": null
},
{
"chosen_role_id": 1,
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Deployment and Runtime Configuration",
"id": 13,
"rationale": "Configuration and release artifacts that control how backend services run in environments. Includes environment variables, manifests, feature flags, and release-safe configuration management.",
"slug": "deployment-and-runtime-configuration",
"source": "db"
},
"dimension_id": 13,
"input_skill": "Docker",
"llm_role": null,
"matched_chosen_role": true,
"outcome_line": "Existing dimension (library) \u00b7 Role\u2194dimension saved",
"role_dimension_saved": true,
"roles_from_db": [
{
"display_name": "Backend Engineer",
"id": 1,
"rationale": null,
"role_archetype": "A Backend Engineer designs, builds, and maintains the server-side logic and data handling that power applications and services. They focus on implementing reliable business functionality, integrating with other systems, and ensuring the backend is scalable, maintainable, and observable.",
"slug": "backend-engineer",
"source": "db"
}
],
"skill_dimension_saved": true,
"skill_id": 61,
"skill_tag": "in_db",
"skipped_reason": null
},
{
"chosen_role_id": 1,
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Container Orchestration Platforms",
"id": 134,
"rationale": "Platforms that schedule and manage containerized workloads across clusters and environments. Cloud Architects need these to define workload placement standards, cluster boundaries, and platform capabilities.",
"slug": "container-orchestration-platforms",
"source": "db"
},
"dimension_id": 134,
"input_skill": "Kubernetes",
"llm_role": null,
"matched_chosen_role": false,
"outcome_line": "Existing dimension (library) \u00b7 Role\u2194dimension skipped (dimension not under chosen role)",
"role_dimension_saved": false,
"roles_from_db": [
{
"display_name": "Cloud Architect",
"id": 9,
"rationale": null,
"role_archetype": null,
"slug": "cloud-architect",
"source": "db"
},
{
"display_name": "DevOps Engineer",
"id": 10,
"rationale": null,
"role_archetype": null,
"slug": "devops-engineer",
"source": "db"
}
],
"skill_dimension_saved": true,
"skill_id": 726,
"skill_tag": "in_db",
"skipped_reason": null
},
{
"chosen_role_id": 1,
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Kubernetes for ML Workloads",
"id": 47,
"rationale": "Kubernetes-native components used to schedule, accelerate, and isolate ML training and serving workloads. This includes GPU enablement and ML-specific controllers rather than generic cluster administration.",
"slug": "kubernetes-for-ml-workloads",
"source": "db"
},
"dimension_id": 47,
"input_skill": "Kubernetes",
"llm_role": null,
"matched_chosen_role": false,
"outcome_line": "Existing dimension (library) \u00b7 Role\u2194dimension skipped (dimension not under chosen role)",
"role_dimension_saved": false,
"roles_from_db": [
{
"display_name": "ML Engineer",
"id": 3,
"rationale": null,
"role_archetype": null,
"slug": "ml-engineer",
"source": "db"
},
{
"display_name": "ML Ops Engineer",
"id": 16,
"rationale": null,
"role_archetype": null,
"slug": "ml-ops-engineer",
"source": "db"
}
],
"skill_dimension_saved": true,
"skill_id": 726,
"skill_tag": "in_db",
"skipped_reason": null
}
],
"new_skills_created": 0,
"role_dimension_saved": 0,
"skill_dimension_saved": 0,
"skipped": 1
},
"planner_output": null,
"run_id": "f73c3a4e-a52b-4f6b-8494-14e9972d52d2"
}
LLM Calls
Every model call made for this run, in pipeline order. Click a card to see the model's response.