Pipeline run
08be24ac-5284-4a44-91f7-18094da63273
Client output enrichment
v2 Skill cluster · Nature of work · AI index · Tech stack maturity · Evidence · KRA descriptionvocab breakdown (legacy)
Signals
1 POST /skills/extract-from-jd
2 POST /skills/extract-details
3 POST /skills/final-role-output
Web Developer
CASE Aslug: web-developer · id: 25 · source: db
Multi-alias tie (4 roles at 1.0) resolved by TIER_B_TITLE: Web Developer
Resolution:
in_db
— role exists in library; skill↔dim and role↔dim links saved when applicable.
Job description
We are looking for a skilled Junior Laravel Developer to join our team. The ideal candidate should have strong experience in PHP, Laravel framework, MySQL, and API development. You will be responsible for designing, developing, and maintaining scalable web applications. Experience 1 to 2 Years Key Responsibilities • Develop, maintain, and optimize RESTful APIs in Laravel. • Implement webhook integrations for seamless third-party communication. • Integrate WebRTC for real-time video and audio communication. • Work on chat and video integration within Laravel applications. • Troubleshoot and resolve backend issues effectively. • Strong Laravel expertise (latest versions) • Experience with API development and authentication (OAuth, JWT) • Understanding of MySQL, Redis, and caching mechanisms. • Familiarity with socket.io or Pusher for real-time chat • Install and configure laravel-seo package for comprehensive SEO management in Laravel applications, including robots tag, title tag (with suffix), meta tags (author, description, image), OpenGraph (Facebook, LinkedIn), Twitter tags, structured data (Article & Breadcrumbs), and favicon support. • Preferred if any frontend technology known such react js or vue js Requirements • Proven experience minimum 1y+ • Strong Laravel expertise (latest versions). • Experience with API development and authentication (OAuth, JWT). • Familiarity with WebRTC, socket.io, or Pusher. • Basic knowledge of React.js or Vue.js (preferred). • Experience with SEO management using laravel-seo Perks & Benefits:: • Permanent job role • 5 days in a week • Fixed day shift • On time salary • Good career growth Please note that, candidate's preferred location is in an around West Bengal. Apply For A Job Choose Job Role*—Please choose an option—Business AnalystBusiness Development ManagerContent WriterFUll Stack Developer - Node & LaravelHybrid Mobile App DeveloperLaravel DeveloperManual TesterMERN Stack DeveloperNode js developerOnline BidderProject CoordinatorReact Native DeveloperSEO/Digital Marketing ExecutiveShopify DeveloperTechnical Project ManagerUI/UX DesignerWordPress Developer Upload your resume *
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
- Laravel (CANONICAL) primary
- Laravel 10 (VERSION)
- Laravel 11 (VERSION)
- Laravel 4 (VERSION)
- Laravel 5 (VERSION)
- Laravel 6 (VERSION)
- Laravel 7 (VERSION)
- Laravel 8 (VERSION)
- Laravel 9 (VERSION)
- laravel 10 (VERSION)
- laravel 11 (VERSION)
- laravel 4 (VERSION)
- laravel 5 (VERSION)
- laravel 6 (VERSION)
- laravel 7 (VERSION)
- laravel 8 (VERSION)
- laravel 9 (VERSION)
Context tags (catalog)
Stored enrichment (catalog DB)
- Category
- Framework
- Sub-category
- Web Framework
- Vendor
- Taylor Otwell
- License
- mit
- Year introduced
- 2011
- Confidence
- 0.99
- Version strategy
- SEPARATE_ENTITY
- Version tag
- 11
Maturity reasoning: Laravel appears in many web developer job postings and has strong GitHub activity; it remains a common PHP framework in hiring pipelines, not a niche or sunset technology.
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 Developer, Fullstack Developer, Fullstack Developer, Java Backend Developer, Node.js Backend Developer, PHP Backend Developer, Python Backend Developer
API 3 link attempts (this skill)
| Dimension | Skill↔dim | Role↔dim | Outcome |
|---|---|---|---|
|
Web Application Frameworks
web-application-frameworks
|
✓ | — | Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role) |
Aliases — catalog
- REST (CANONICAL) primary
Context tags (catalog)
Stored enrichment (catalog DB)
- Category
- Concept
- Sub-category
- Api Architecture Style
- Year introduced
- 2000
- Confidence
- 0.88
- Version strategy
- NOT_APPLICABLE
Maturity reasoning: REST is a default API architecture in many job descriptions and is widely supported by major vendors/frameworks; OpenAPI and RESTful endpoints remain standard in hiring pipelines.
Skill profile (library / DB)
- Skill nature
- CONCEPT
- Volatility
- STABLE
- Typical lifespan
- EVERGREEN
- Category id
- 2
- Sub-category id
- 2122
- Extractable
- True
- Also category
- False
Dimensions (API 2 worklist)
-
API Design and Contracts Catalog dimension db id 3
Library dimension (catalog)
Roles linked in library: Backend Developer, Fullstack Developer
-
API Interface and Contract Design Catalog dimension db id 289
Library dimension (catalog)
Roles linked in library: .NET Backend Developer, Go Backend Developer, Kotlin Backend Developer, Node.js Backend Developer, PHP Backend Developer, Python Backend Developer, Ruby Backend Developer, Scala Backend Developer
-
Integration Protocols & Standards Catalog dimension db id 271
Library dimension (catalog)
Roles linked in library: Pega Developer
-
Standards & Protocols Compliance Catalog dimension db id 452
Library dimension (catalog)
Roles linked in library: Sitecore Dev
API 3 link attempts (this skill)
| Dimension | Skill↔dim | Role↔dim | Outcome |
|---|---|---|---|
|
API Design and Contracts
api-design-and-contracts
|
✓ | — | Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role) |
|
API Interface and Contract Design
api-interface-and-contract-design
|
✓ | — | Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role) |
|
Integration Protocols & Standards
integration-protocols-standards
|
✓ | — | Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role) |
|
Standards & Protocols Compliance
standards-protocols-compliance
|
✓ | — | Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role) |
Skill enrichment (orchestrator / LLM)
No Stage 7 enrichment blob on this skill (orchestrator skipped enrichment).
- Category
- Concepts
- Sub-category
- general
- Skill nature
- CONCEPT
- Volatility
- STABLE
- Typical lifespan
- EVERGREEN
- Version strategy
- UNVERSIONED
Aliases — catalog
- webhooks (CANONICAL) primary
- Webhooks (CANONICAL)
Context tags (catalog)
Stored enrichment (catalog DB)
- Category
- Concept
- Sub-category
- Webhook
- Confidence
- 0.90
- Version strategy
- NOT_APPLICABLE
Maturity reasoning: Webhooks are a standard integration pattern and appear routinely in SaaS/API job descriptions; major vendors like Stripe, GitHub, and Shopify document webhook support as a core feature.
Skill profile (library / DB)
- Skill nature
- CONCEPT
- Volatility
- STABLE
- Typical lifespan
- EVERGREEN
- Category id
- 2
- Sub-category id
- 3531
- Extractable
- True
- Also category
- False
Dimensions (API 2 worklist)
-
External Integrations and Clients Catalog dimension db id 375
Library dimension (catalog)
Roles linked in library: Go Backend Developer
-
External System Integrations Catalog dimension db id 14
Library dimension (catalog)
Roles linked in library: .NET Backend Developer, Backend Developer, Drupal Dev, Java Backend Developer, Kotlin Backend Developer, Node.js Backend Developer, PHP Backend Developer, Python Backend Developer, Ruby Backend Developer, Scala Backend Developer
-
Magento Integration Adapters Catalog dimension db id 401
Library dimension (catalog)
Roles linked in library: Magento Dev
-
Shopify APIs and Webhooks Catalog dimension db id 427
Library dimension (catalog)
Roles linked in library: Shopify Dev
-
Sitecore Integration Patterns Catalog dimension db id 444
Library dimension (catalog)
Roles linked in library: Sitecore Dev
-
WordPress REST Integrations Catalog dimension db id 332
Library dimension (catalog)
Roles linked in library: WordPress Dev
API 3 link attempts (this skill)
| Dimension | Skill↔dim | Role↔dim | Outcome |
|---|---|---|---|
|
External Integrations and Clients
external-integrations-and-clients
|
✓ | — | Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role) |
|
External System Integrations
external-system-integrations
|
✓ | — | Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role) |
|
Magento Integration Adapters
magento-integration-adapters
|
✓ | — | Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role) |
|
Shopify APIs and Webhooks
shopify-apis-and-webhooks
|
✓ | — | Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role) |
|
Sitecore Integration Patterns
sitecore-integration-patterns
|
✓ | — | Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role) |
|
WordPress REST Integrations
wordpress-rest-integrations
|
✓ | — | Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role) |
Aliases — catalog
- WebRTC (CANONICAL)
Context tags (catalog)
Stored enrichment (catalog DB)
- Category
- Protocol
- Sub-category
- Real Time Communication Protocol
- Vendor
- License
- other_open
- Year introduced
- 2011
- Confidence
- 0.93
- Version strategy
- NOT_APPLICABLE
Maturity reasoning: WebRTC appears in many job descriptions for real-time video/audio apps and is a standard browser API; it’s broadly adopted rather than niche or sunsetted.
Skill profile (library / DB)
- Skill nature
- PROTOCOL
- Volatility
- STABLE
- Typical lifespan
- EVERGREEN
- Category id
- 10
- Sub-category id
- 500
- Extractable
- True
- Also category
- False
Dimensions (API 2 worklist)
-
React Frontend Development Catalog dimension db id 96
Library dimension (catalog)
API 3 link attempts (this skill)
| Dimension | Skill↔dim | Role↔dim | Outcome |
|---|---|---|---|
|
React Frontend Development
d_init_01
|
✓ | — | Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role) |
Aliases — catalog
- MySQL (CANONICAL) primary
Context tags (catalog)
Stored enrichment (catalog DB)
- Category
- Datastore
- Sub-category
- Relational Database
- Vendor
- Oracle Corporation
- License
- gpl_v2
- Year introduced
- 1995
- Confidence
- 0.99
- Version strategy
- NOT_APPLICABLE
Maturity reasoning: MySQL appears in a large share of backend/DB job descriptions and remains a standard managed offering across AWS RDS, Cloud SQL, and Azure Database, indicating broad hiring-pipeline demand.
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: Fullstack Developer, Fullstack Developer, PHP Backend Developer
-
Relational Database Design Catalog dimension db id 4
Library dimension (catalog)
Roles linked in library: .NET Backend Developer, Backend Developer, Kotlin Backend Developer, Node.js Backend Developer, Python Backend Developer, Ruby Backend Developer, Scala Backend Developer
-
Relational Database Usage Catalog dimension db id 371
Library dimension (catalog)
Roles linked in library: Go Backend Developer
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 skipped (dimension not under chosen role) |
|
Relational Database Usage
relational-database-usage
|
✓ | — | Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role) |
Aliases — catalog
- Redis (CANONICAL) primary
Context tags (catalog)
Stored enrichment (catalog DB)
- Category
- Datastore
- Sub-category
- Key Value Store
- Vendor
- Redis Labs
- License
- apache_2
- Year introduced
- 2009
- Confidence
- 0.95
- Version strategy
- NOT_APPLICABLE
Maturity reasoning: Redis appears in many job descriptions for caching, queues, and session storage, and is a standard datastore in modern backend stacks; vendor activity and broad ecosystem support indicate strong market demand.
Skill profile (library / DB)
- Skill nature
- TOOL
- Volatility
- STABLE
- Typical lifespan
- EVERGREEN
- Category id
- 3
- Sub-category id
- 28
- Extractable
- True
- Also category
- False
Dimensions (API 2 worklist)
-
Caching and State Management Catalog dimension db id 7
Library dimension (catalog)
Roles linked in library: .NET Backend Developer, Backend Developer, Kotlin Backend Developer, Node.js Backend Developer, PHP Backend Developer, Python Backend Developer, Ruby Backend Developer, Scala Backend Developer
-
Magento Caching and Performance Catalog dimension db id 404
Library dimension (catalog)
Roles linked in library: Magento Dev
API 3 link attempts (this skill)
| Dimension | Skill↔dim | Role↔dim | Outcome |
|---|---|---|---|
|
Caching and State Management
caching-and-state-management
|
✓ | — | Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role) |
|
Magento Caching and Performance
magento-caching-and-performance
|
✓ | — | Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role) |
Aliases — catalog
- response caching (CANONICAL) primary
Context tags (catalog)
Stored enrichment (catalog DB)
- Category
- Tool
- Sub-category
- Caching Tool
- Vendor
- Varnish Software
- License
- bsd
- Year introduced
- 2006
- Confidence
- 0.67
- Version strategy
- NOT_APPLICABLE
Maturity reasoning: Commonly requested in JDs for web/API performance via CDNs, reverse proxies, and app caches; vendor docs and cloud offerings (Cloudflare, Redis, Varnish) show broad production adoption.
Skill profile (library / DB)
- Skill nature
- TOOL
- Volatility
- STABLE
- Typical lifespan
- EVERGREEN
- Category id
- 13
- Sub-category id
- 1010
- Extractable
- True
- Also category
- False
Dimensions (API 2 worklist)
-
Latency and Cost Optimization Catalog dimension db id 205
Library dimension (catalog)
Roles linked in library: AI Engineer
API 3 link attempts (this skill)
| Dimension | Skill↔dim | Role↔dim | Outcome |
|---|---|---|---|
|
Latency and Cost Optimization
latency-and-cost-optimization
|
— | — |
Skipped — no persistable v3 meta for new skill
skill_not_in_db_v3_proposed
|
Skill enrichment (orchestrator / LLM)
No Stage 7 enrichment blob on this skill (orchestrator skipped enrichment).
- Category
- Web Frameworks
- Sub-category
- general
- Skill nature
- TOOL
- Volatility
- MEDIUM
- Typical lifespan
- MULTI_YEAR
- Version strategy
- UNVERSIONED
Skill enrichment (orchestrator / LLM)
No Stage 7 enrichment blob on this skill (orchestrator skipped enrichment).
- Category
- Web Frameworks
- Sub-category
- general
- Skill nature
- TOOL
- Volatility
- MEDIUM
- Typical lifespan
- MULTI_YEAR
- Version strategy
- UNVERSIONED
Aliases — catalog
- SEO (CANONICAL)
Context tags (catalog)
Stored enrichment (catalog DB)
- Category
- Domain
- Sub-category
- Search Engine Optimization
- Confidence
- 0.98
- Version strategy
- NOT_APPLICABLE
Maturity reasoning: SEO appears in large volumes of marketing, content, and growth job descriptions across industries; Google Search Central and major CMS vendors continue to publish active guidance, indicating broad ongoing demand.
Skill profile (library / DB)
- Skill nature
- CONCEPT
- Volatility
- STABLE
- Typical lifespan
- EVERGREEN
- Category id
- 37
- Sub-category id
- 1251
- Extractable
- True
- Also category
- False
Dimensions (API 2 worklist)
-
React Frontend Development Catalog dimension db id 96
Library dimension (catalog)
API 3 link attempts (this skill)
| Dimension | Skill↔dim | Role↔dim | Outcome |
|---|---|---|---|
|
React Frontend Development
d_init_01
|
✓ | — | Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role) |
Skill enrichment (orchestrator / LLM)
No Stage 7 enrichment blob on this skill (orchestrator skipped enrichment).
- Category
- Concepts
- Sub-category
- general
- Skill nature
- CONCEPT
- Volatility
- MEDIUM
- Typical lifespan
- MULTI_YEAR
- Version strategy
- UNVERSIONED
Skill enrichment (orchestrator / LLM)
No Stage 7 enrichment blob on this skill (orchestrator skipped enrichment).
- Category
- Concepts
- Sub-category
- general
- Skill nature
- CONCEPT
- Volatility
- MEDIUM
- Typical lifespan
- MULTI_YEAR
- Version strategy
- UNVERSIONED
Skill enrichment (orchestrator / LLM)
No Stage 7 enrichment blob on this skill (orchestrator skipped enrichment).
- Category
- Concepts
- Sub-category
- general
- Skill nature
- CONCEPT
- Volatility
- MEDIUM
- Typical lifespan
- MULTI_YEAR
- Version strategy
- UNVERSIONED
Aliases — catalog
- React 0.1 (VERSION)
- React 0.10 (VERSION)
- React 0.11 (VERSION)
- React 0.12 (VERSION)
- React 0.13 (VERSION)
- React 0.14 (VERSION)
- React 0.2 (VERSION)
- React 0.3 (VERSION)
- React 0.4 (VERSION)
- React 0.5 (VERSION)
- React 0.6 (VERSION)
- React 0.7 (VERSION)
- React 0.8 (VERSION)
- React 0.9 (VERSION)
- React 15 (VERSION)
- React 16 (VERSION)
- React 17 (VERSION)
- React 18 (VERSION)
- React.js (CANONICAL)
- React.js 15 (VERSION)
- React.js 16 (VERSION)
- React.js 17 (VERSION)
- React.js 18 (VERSION)
Context tags (catalog)
Stored enrichment (catalog DB)
- Category
- Framework
- Sub-category
- Frontend Ui Framework
- Vendor
- Meta
- License
- mit
- Year introduced
- 2013
- Confidence
- 0.98
- Version strategy
- SEPARATE_ENTITY
- Version tag
- 18
Maturity reasoning: React.js is a hiring-pipeline staple with very high JD volume across frontend roles and broad ecosystem adoption; it remains one of the most commonly requested UI frameworks on job boards and in GitHub usage trends.
Skill profile (library / DB)
- Skill nature
- FRAMEWORK
- Volatility
- STABLE
- Typical lifespan
- EVERGREEN
- Category id
- 5
- Sub-category id
- 363
- Extractable
- True
- Also category
- False
Dimensions (API 2 worklist)
-
React Frontend Development Catalog dimension db id 96
Library dimension (catalog)
API 3 link attempts (this skill)
| Dimension | Skill↔dim | Role↔dim | Outcome |
|---|---|---|---|
|
React Frontend Development
d_init_01
|
✓ | — | Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role) |
Aliases — catalog
- Vue.js (CANONICAL) primary
- vue (VERSION)
- vue 2 (VERSION)
- vue 2.x (VERSION)
- vue 3 (VERSION)
- vue 3.x (VERSION)
- vue.js 2 (VERSION)
- vue.js 3 (VERSION)
- vue.js2 (VERSION)
- vue.js@3 (VERSION)
- vue2 (VERSION)
- vue2.x (VERSION)
- vue3 (VERSION)
- vuejs 3 (VERSION)
- vuejs3 (VERSION)
Context tags (catalog)
Stored enrichment (catalog DB)
- Category
- Framework
- Sub-category
- Frontend Framework
- Vendor
- Evan You
- License
- mit
- Year introduced
- 2014
- Confidence
- 0.98
- Version strategy
- SEPARATE_ENTITY
- Version tag
- 3
Maturity reasoning: Vue.js appears in many frontend job postings and is a common alternative to React/Angular; its ecosystem and Vue 3 adoption show sustained market demand rather than niche use.
Skill profile (library / DB)
- Skill nature
- FRAMEWORK
- Volatility
- STABLE
- Typical lifespan
- EVERGREEN
- Category id
- 5
- Sub-category id
- 1072
- Extractable
- True
- Also category
- False
Dimensions (API 2 worklist)
-
Frameworks & Libraries Catalog dimension db id 360
Library dimension (catalog)
Roles linked in library: Drupal Dev
API 3 link attempts (this skill)
| Dimension | Skill↔dim | Role↔dim | Outcome |
|---|---|---|---|
|
Frameworks & Libraries
frameworks-libraries
|
✓ | — | Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role) |
Aliases — catalog
- OAuth (CANONICAL) primary
Context tags (catalog)
Stored enrichment (catalog DB)
- Category
- Protocol
- Sub-category
- Authorization Protocol
- Confidence
- 0.97
- Version strategy
- NOT_APPLICABLE
Maturity reasoning: OAuth is widely listed in job descriptions for API/auth work and is a standard authorization protocol across major vendors; OAuth 2.0/OIDC are common requirements in modern identity stacks.
Skill profile (library / DB)
- Skill nature
- PROTOCOL
- Volatility
- STABLE
- Typical lifespan
- EVERGREEN
- Category id
- 10
- Sub-category id
- 50
- Extractable
- True
- Also category
- False
Dimensions (API 2 worklist)
-
Shopify APIs and Webhooks Catalog dimension db id 427
Library dimension (catalog)
Roles linked in library: Shopify Dev
API 3 link attempts (this skill)
| Dimension | Skill↔dim | Role↔dim | Outcome |
|---|---|---|---|
|
Shopify APIs and Webhooks
shopify-apis-and-webhooks
|
✓ | — | Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role) |
Aliases — catalog
- JWT (CANONICAL) primary
Context tags (catalog)
Stored enrichment (catalog DB)
- Category
- Format
- Sub-category
- Token Format
- Vendor
- IETF
- License
- unknown
- Year introduced
- 2010
- Confidence
- 0.90
- Version strategy
- NOT_APPLICABLE
Maturity reasoning: JWT is widely listed in backend/auth job descriptions and is a standard token format in OAuth2/OIDC ecosystems; no vendor sunset or replacement has displaced it.
Skill profile (library / DB)
- Skill nature
- STANDARD
- Volatility
- STABLE
- Typical lifespan
- EVERGREEN
- Category id
- 4
- Sub-category id
- 33
- Extractable
- True
- Also category
- False
Dimensions (API 2 worklist)
-
Authentication and Authorization Catalog dimension db id 6
Library dimension (catalog)
Roles linked in library: .NET Backend Developer, Backend Developer, Go Backend Developer, Java Backend Developer, Node.js Backend Developer, PHP Backend Developer, Python Backend Developer
-
Authentication and Session Handling Catalog dimension db id 86
Library dimension (catalog)
Roles linked in library: Android Developer, Frontend Developer, Fullstack Developer, Hybrid Mobile Developer, Ionic Developer, Native Mobile Developer, Web Developer, iOS Developer
-
Backend Authentication and Authorization Catalog dimension db id 386
Library dimension (catalog)
Roles linked in library: Kotlin Backend Developer, Ruby Backend Developer, Scala Backend Developer
-
Frontend Authentication and Session Management Catalog dimension db id 300
Library dimension (catalog)
Roles linked in library: React Frontend Developer, Svelte Frontend Developer, Vue Frontend Developer
API 3 link attempts (this skill)
| Dimension | Skill↔dim | Role↔dim | Outcome |
|---|---|---|---|
|
Authentication and Authorization
authentication-and-authorization
|
✓ | — | Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role) |
|
Authentication and Session Handling
authentication-and-session-handling
|
✓ | ✓ | Existing dimension (library) · Role↔dimension saved |
|
Backend Authentication and Authorization
backend-authentication-and-authorization
|
✓ | — | Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role) |
|
Frontend Authentication and Session Management
frontend-authentication-and-session-management
|
✓ | — | Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role) |
All API 3 persistence rows
Same grid as the skill-extractor “Persistence items” table: one row per (skill × dimension) work item.
| Skill | Tag | Dimension | Skill↔dim | Role↔dim | Outcome | Notes |
|---|---|---|---|---|---|---|
| Laravel | in_db |
Web Application Frameworks
web-application-frameworks
|
✓ | — | Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role) | |
| REST | in_db |
API Design and Contracts
api-design-and-contracts
|
✓ | — | Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role) | |
| REST | in_db |
API Interface and Contract Design
api-interface-and-contract-design
|
✓ | — | Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role) | |
| REST | in_db |
Integration Protocols & Standards
integration-protocols-standards
|
✓ | — | Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role) | |
| REST | in_db |
Standards & Protocols Compliance
standards-protocols-compliance
|
✓ | — | Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role) | |
| Webhooks | in_db |
External Integrations and Clients
external-integrations-and-clients
|
✓ | — | Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role) | |
| Webhooks | in_db |
External System Integrations
external-system-integrations
|
✓ | — | Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role) | |
| Webhooks | in_db |
Magento Integration Adapters
magento-integration-adapters
|
✓ | — | Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role) | |
| Webhooks | in_db |
Shopify APIs and Webhooks
shopify-apis-and-webhooks
|
✓ | — | Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role) | |
| Webhooks | in_db |
Sitecore Integration Patterns
sitecore-integration-patterns
|
✓ | — | Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role) | |
| Webhooks | in_db |
WordPress REST Integrations
wordpress-rest-integrations
|
✓ | — | Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role) | |
| WebRTC | in_db |
React Frontend Development
d_init_01
|
✓ | — | Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role) | |
| MySQL | in_db |
Relational Data Modeling
relational-data-modeling
|
✓ | — | Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role) | |
| MySQL | in_db |
Relational Database Design
relational-database-design
|
✓ | — | Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role) | |
| MySQL | in_db |
Relational Database Usage
relational-database-usage
|
✓ | — | Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role) | |
| Redis | in_db |
Caching and State Management
caching-and-state-management
|
✓ | — | Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role) | |
| Redis | in_db |
Magento Caching and Performance
magento-caching-and-performance
|
✓ | — | Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role) | |
| Caching | new |
Latency and Cost Optimization
latency-and-cost-optimization
|
— | — | Skipped — no persistable v3 meta for new skill | skill_not_in_db_v3_proposed |
| SEO | in_db |
React Frontend Development
d_init_01
|
✓ | — | Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role) | |
| React.js | in_db |
React Frontend Development
d_init_01
|
✓ | — | Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role) | |
| Vue.js | in_db |
Frameworks & Libraries
frameworks-libraries
|
✓ | — | Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role) | |
| OAuth | in_db |
Shopify APIs and Webhooks
shopify-apis-and-webhooks
|
✓ | — | Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role) | |
| JWT | in_db |
Authentication and Authorization
authentication-and-authorization
|
✓ | — | Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role) | |
| JWT | in_db |
Authentication and Session Handling
authentication-and-session-handling
|
✓ | ✓ | Existing dimension (library) · Role↔dimension saved | |
| JWT | in_db |
Backend Authentication and Authorization
backend-authentication-and-authorization
|
✓ | — | Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role) | |
| JWT | in_db |
Frontend Authentication and Session Management
frontend-authentication-and-session-management
|
✓ | — | Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role) |
Library artifacts (this run)
| Kind | Detail | DB id |
|---|---|---|
| canonical_skill_proposed | API Development | type=Concepts subtype=general nature=CONCEPT lifespan=EVERGREEN | |
| canonical_skill_proposed | socket.io | type=Web Frameworks subtype=general nature=TOOL lifespan=MULTI_YEAR | |
| canonical_skill_proposed | Pusher | type=Web Frameworks subtype=general nature=TOOL lifespan=MULTI_YEAR | |
| canonical_skill_proposed | OpenGraph | type=Concepts subtype=general nature=CONCEPT lifespan=MULTI_YEAR | |
| canonical_skill_proposed | Twitter Cards | type=Concepts subtype=general nature=CONCEPT lifespan=MULTI_YEAR | |
| canonical_skill_proposed | Structured Data | type=Concepts subtype=general nature=CONCEPT lifespan=MULTI_YEAR | |
| dimension_skill_link_proposed | Caching ↔ Latency and Cost Optimization |
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": "Software \u0026 SaaS Products"
},
"secondary": null
},
"education": [],
"experience": {
"max": 2,
"min": 1,
"raw": "1 to 2 Years"
},
"job_locations": [
{
"aliases": [],
"city": null,
"country": "India",
"state": "West Bengal",
"work_mode": "null"
}
],
"role": "Junior Laravel Developer",
"role_aliases": [
"Laravel Developer",
"PHP Developer",
"Web Developer"
],
"role_archetype": "Engineering",
"roles_and_responsibilities": [
{
"bullet_count": 10,
"heading": "Key Responsibilities",
"heading_was_present": true,
"source_marker": {
"first_5_words": "\u2022 Develop, maintain, and optimize",
"last_5_words": "or frontend technology known such"
},
"text": "\u2022 Develop, maintain, and optimize RESTful APIs in Laravel.\n\u2022 Implement webhook integrations for seamless third-party communication.\n\u2022 Integrate WebRTC for real-time video and audio communication.\n\u2022 Work on chat and video integration within Laravel applications.\n\u2022 Troubleshoot and resolve backend issues effectively.\n\u2022 Strong Laravel expertise (latest versions)\n\u2022 Experience with API development and authentication (OAuth, JWT)\n\u2022 Understanding of MySQL, Redis, and caching mechanisms.\n\u2022 Familiarity with socket.io or Pusher for real-time chat\n\u2022 Install and configure laravel-seo package for comprehensive SEO management in Laravel applications, including robots tag, title tag (with suffix), meta tags (author, description, image), OpenGraph (Facebook, LinkedIn), Twitter tags, structured data (Article \u0026 Breadcrumbs), and favicon support.\n\u2022 Preferred if any frontend technology known such react js or vue js",
"word_count": 164
},
{
"bullet_count": 6,
"heading": "Requirements",
"heading_was_present": true,
"source_marker": {
"first_5_words": "\u2022 Proven experience minimum 1y+",
"last_5_words": "management using laravel-seo"
},
"text": "\u2022 Proven experience minimum 1y+\n\u2022 Strong Laravel expertise (latest versions).\n\u2022 Experience with API development and authentication (OAuth, JWT).\n\u2022 Familiarity with WebRTC, socket.io, or Pusher.\n\u2022 Basic knowledge of React.js or Vue.js (preferred).\n\u2022 Experience with SEO management using laravel-seo",
"word_count": 54
}
],
"urls": []
}
API 1 — extract-from-jd click to toggle
{
"final_skills": [
{
"is_primary": true,
"skill_name": "Laravel"
},
{
"is_primary": true,
"skill_name": "REST"
},
{
"is_primary": true,
"skill_name": "API Development"
},
{
"is_primary": true,
"skill_name": "Webhooks"
},
{
"is_primary": true,
"skill_name": "WebRTC"
},
{
"is_primary": true,
"skill_name": "MySQL"
},
{
"is_primary": true,
"skill_name": "Redis"
},
{
"is_primary": true,
"skill_name": "Caching"
},
{
"is_primary": false,
"skill_name": "socket.io"
},
{
"is_primary": false,
"skill_name": "Pusher"
},
{
"is_primary": false,
"skill_name": "SEO"
},
{
"is_primary": false,
"skill_name": "OpenGraph"
},
{
"is_primary": false,
"skill_name": "Twitter Cards"
},
{
"is_primary": false,
"skill_name": "Structured Data"
},
{
"is_primary": false,
"skill_name": "React.js"
},
{
"is_primary": false,
"skill_name": "Vue.js"
},
{
"is_primary": true,
"skill_name": "OAuth"
},
{
"is_primary": true,
"skill_name": "JWT"
}
],
"jd_role": {
"display_name": "Junior Laravel Developer",
"rationale": null,
"role_aliases": [
"Laravel Developer",
"PHP Developer",
"Web Developer"
],
"role_archetype": "Engineering",
"slug": ""
},
"nano_parsed": {
"JD_type": "pass",
"about_company": null,
"certifications": [],
"company_name": null,
"ctc": null,
"domain": {
"primary": {
"aliases": [],
"domain": "Software \u0026 SaaS Products"
},
"secondary": null
},
"education": [],
"experience": {
"max": 2,
"min": 1,
"raw": "1 to 2 Years"
},
"job_locations": [
{
"aliases": [],
"city": null,
"country": "India",
"state": "West Bengal",
"work_mode": "null"
}
],
"role": "Junior Laravel Developer",
"role_aliases": [
"Laravel Developer",
"PHP Developer",
"Web Developer"
],
"role_archetype": "Engineering",
"roles_and_responsibilities": [
{
"bullet_count": 10,
"heading": "Key Responsibilities",
"heading_was_present": true,
"source_marker": {
"first_5_words": "\u2022 Develop, maintain, and optimize",
"last_5_words": "or frontend technology known such"
},
"text": "\u2022 Develop, maintain, and optimize RESTful APIs in Laravel.\n\u2022 Implement webhook integrations for seamless third-party communication.\n\u2022 Integrate WebRTC for real-time video and audio communication.\n\u2022 Work on chat and video integration within Laravel applications.\n\u2022 Troubleshoot and resolve backend issues effectively.\n\u2022 Strong Laravel expertise (latest versions)\n\u2022 Experience with API development and authentication (OAuth, JWT)\n\u2022 Understanding of MySQL, Redis, and caching mechanisms.\n\u2022 Familiarity with socket.io or Pusher for real-time chat\n\u2022 Install and configure laravel-seo package for comprehensive SEO management in Laravel applications, including robots tag, title tag (with suffix), meta tags (author, description, image), OpenGraph (Facebook, LinkedIn), Twitter tags, structured data (Article \u0026 Breadcrumbs), and favicon support.\n\u2022 Preferred if any frontend technology known such react js or vue js",
"word_count": 164
},
{
"bullet_count": 6,
"heading": "Requirements",
"heading_was_present": true,
"source_marker": {
"first_5_words": "\u2022 Proven experience minimum 1y+",
"last_5_words": "management using laravel-seo"
},
"text": "\u2022 Proven experience minimum 1y+\n\u2022 Strong Laravel expertise (latest versions).\n\u2022 Experience with API development and authentication (OAuth, JWT).\n\u2022 Familiarity with WebRTC, socket.io, or Pusher.\n\u2022 Basic knowledge of React.js or Vue.js (preferred).\n\u2022 Experience with SEO management using laravel-seo",
"word_count": 54
}
],
"urls": []
},
"rejected": false,
"rejection_reason": null,
"run_id": "08be24ac-5284-4a44-91f7-18094da63273",
"stage3_signals": {
"alias_found": true,
"alias_match_roles": [
{
"display_name": "PHP Backend Developer",
"kra_matches": null,
"matched_count": null,
"matched_skills": null,
"role_id": 86,
"score": 1.0,
"slug": "php-backend-developer",
"total_count": null
},
{
"display_name": "Backend Developer",
"kra_matches": null,
"matched_count": null,
"matched_skills": null,
"role_id": 1,
"score": 1.0,
"slug": "backend-engineer",
"total_count": null
},
{
"display_name": "Frontend Developer",
"kra_matches": null,
"matched_count": null,
"matched_skills": null,
"role_id": 7,
"score": 1.0,
"slug": "frontend-engineer",
"total_count": null
},
{
"display_name": "Web Developer",
"kra_matches": null,
"matched_count": null,
"matched_skills": null,
"role_id": 25,
"score": 1.0,
"slug": "web-developer",
"total_count": null
}
],
"kra_match_roles": [
{
"display_name": "Backend Developer",
"kra_matches": [
{
"kra_text": "Identifies and resolves backend performance bottlenecks through query optimization, indexing strategies, connection pooling, and distributed caching with Redis.",
"sentence": "Understanding of MySQL, Redis, and caching mechanisms.",
"similarity": 0.6139
},
{
"kra_text": "Identifies and resolves backend performance bottlenecks through query optimization, indexing strategies, connection pooling, and distributed caching with Redis.",
"sentence": "Troubleshoot and resolve backend issues effectively.",
"similarity": 0.6016
},
{
"kra_text": "Designs and maintains RESTful and GraphQL API interfaces with proper authentication, versioning, rate limiting, and documentation for frontend and third-party consumers.",
"sentence": "Develop, maintain, and optimize RESTful APIs in Laravel.",
"similarity": 0.5591
}
],
"matched_count": null,
"matched_skills": null,
"role_id": 1,
"score": 0.5915,
"slug": "backend-engineer",
"total_count": null
},
{
"display_name": "Fullstack Developer",
"kra_matches": [
{
"kra_text": "Builds and integrates client-side React or Vue components with server-side Node.js or Django APIs, managing bidirectional data flow across frontend and backend layers.",
"sentence": "Preferred if any frontend technology known such react js or vue js",
"similarity": 0.6061
},
{
"kra_text": "Builds and integrates client-side React or Vue components with server-side Node.js or Django APIs, managing bidirectional data flow across frontend and backend layers.",
"sentence": "Basic knowledge of React.js or Vue.js (preferred).",
"similarity": 0.5691
},
{
"kra_text": "Debugs full-stack issues that span frontend rendering, API behavior, database queries, and infrastructure configuration to identify root causes.",
"sentence": "Troubleshoot and resolve backend issues effectively.",
"similarity": 0.5611
}
],
"matched_count": null,
"matched_skills": null,
"role_id": 15,
"score": 0.5788,
"slug": "full-stack-engineer",
"total_count": null
},
{
"display_name": "Frontend Developer",
"kra_matches": [
{
"kra_text": "Builds responsive user interfaces and interactive web components using React, Vue, or Angular with TypeScript, HTML5, and modern CSS for browser-based applications.",
"sentence": "Preferred if any frontend technology known such react js or vue js",
"similarity": 0.6108
},
{
"kra_text": "Builds responsive user interfaces and interactive web components using React, Vue, or Angular with TypeScript, HTML5, and modern CSS for browser-based applications.",
"sentence": "Basic knowledge of React.js or Vue.js (preferred).",
"similarity": 0.5735
},
{
"kra_text": "Supports production releases by diagnosing cross-browser compatibility issues, investigating UI regressions, and resolving frontend performance degradation.",
"sentence": "Troubleshoot and resolve backend issues effectively.",
"similarity": 0.502
}
],
"matched_count": null,
"matched_skills": null,
"role_id": 7,
"score": 0.5621,
"slug": "frontend-engineer",
"total_count": null
},
{
"display_name": "Python Backend Developer",
"kra_matches": [
{
"kra_text": "Troubleshoot server-side defects",
"sentence": "Troubleshoot and resolve backend issues effectively.",
"similarity": 0.5788
},
{
"kra_text": "Design backend endpoints and request handling",
"sentence": "Preferred if any frontend technology known such react js or vue js",
"similarity": 0.5094
},
{
"kra_text": "Design backend endpoints and request handling",
"sentence": "Develop, maintain, and optimize RESTful APIs in Laravel.",
"similarity": 0.4538
}
],
"matched_count": null,
"matched_skills": null,
"role_id": 80,
"score": 0.514,
"slug": "python-backend-developer",
"total_count": null
},
{
"display_name": "React Native Developer",
"kra_matches": [
{
"kra_text": "integrate backend APIs",
"sentence": "Troubleshoot and resolve backend issues effectively.",
"similarity": 0.5191
},
{
"kra_text": "integrate backend APIs",
"sentence": "Integrate WebRTC for real-time video and audio communication.",
"similarity": 0.4811
},
{
"kra_text": "integrate backend APIs",
"sentence": "Develop, maintain, and optimize RESTful APIs in Laravel.",
"similarity": 0.4722
}
],
"matched_count": null,
"matched_skills": null,
"role_id": 73,
"score": 0.4908,
"slug": "react-native-developer",
"total_count": null
}
],
"skill_match_roles": [
{
"display_name": "PHP Backend Developer",
"kra_matches": null,
"matched_count": 6,
"matched_skills": [
"JWT",
"Laravel",
"MySQL",
"REST",
"Redis",
"webhooks"
],
"role_id": 86,
"score": 0.6,
"slug": "php-backend-developer",
"total_count": 10
},
{
"display_name": "Python Backend Developer",
"kra_matches": null,
"matched_count": 6,
"matched_skills": [
"JWT",
"Laravel",
"MySQL",
"REST",
"Redis",
"webhooks"
],
"role_id": 80,
"score": 0.6,
"slug": "python-backend-developer",
"total_count": 10
},
{
"display_name": "Backend Developer",
"kra_matches": null,
"matched_count": 6,
"matched_skills": [
"JWT",
"Laravel",
"MySQL",
"REST",
"Redis",
"webhooks"
],
"role_id": 1,
"score": 0.6,
"slug": "backend-engineer",
"total_count": 10
},
{
"display_name": "Node.js Backend Developer",
"kra_matches": null,
"matched_count": 6,
"matched_skills": [
"JWT",
"Laravel",
"MySQL",
"REST",
"Redis",
"webhooks"
],
"role_id": 82,
"score": 0.6,
"slug": "node-backend-developer",
"total_count": 10
},
{
"display_name": ".NET Backend Developer",
"kra_matches": null,
"matched_count": 5,
"matched_skills": [
"JWT",
"MySQL",
"REST",
"Redis",
"webhooks"
],
"role_id": 83,
"score": 0.5,
"slug": "dotnet-backend-developer",
"total_count": 10
}
]
},
"stage4_decision": {
"alias_collision_detected": true,
"case": "A",
"chosen_role": {
"display_name": "Web Developer",
"kra_matches": null,
"matched_count": null,
"matched_skills": null,
"role_id": 25,
"score": 1.0,
"slug": "web-developer",
"total_count": null
},
"confidence": 0.95,
"is_new_role": false,
"llm2_fired": false,
"llm2_reasoning": null,
"matched_dimensions": [],
"matched_kras": [],
"matched_skills": [],
"new_role_display_name": null,
"new_role_slug": null,
"queued": false,
"reasoning": "Multi-alias tie (4 roles at 1.0) resolved by TIER_B_TITLE: Web Developer",
"sub_role": null
},
"stage5_updates": null
}
API 2 — extract-details
{
"alias_matches": [
{
"alias_persist_skipped_reason": "alias_text already exists for this canonical skill",
"alias_persisted": false,
"existing_alias_id": 5429,
"existing_alias_text": "Laravel",
"input_term": "Laravel",
"matched_canonical": {
"category_id": 5,
"display_name": "Laravel",
"id": 3798,
"is_also_category": false,
"is_extractable": true,
"skill_nature": "FRAMEWORK",
"slug": "laravel",
"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": 2,
"display_name": "REST",
"id": 11,
"is_also_category": false,
"is_extractable": true,
"skill_nature": "CONCEPT",
"slug": "rest",
"sub_category_id": 2122,
"typical_lifespan": "EVERGREEN",
"volatility": "STABLE"
},
"matched_via": "alias"
},
{
"alias_persist_skipped_reason": "alias_text already exists for this canonical skill",
"alias_persisted": false,
"existing_alias_id": 3507,
"existing_alias_text": "Webhooks",
"input_term": "Webhooks",
"matched_canonical": {
"category_id": 2,
"display_name": "webhooks",
"id": 2243,
"is_also_category": false,
"is_extractable": true,
"skill_nature": "CONCEPT",
"slug": "webhooks",
"sub_category_id": 3531,
"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": 2552,
"existing_alias_text": "WebRTC",
"input_term": "WebRTC",
"matched_canonical": {
"category_id": 10,
"display_name": "WebRTC",
"id": 1600,
"is_also_category": false,
"is_extractable": true,
"skill_nature": "PROTOCOL",
"slug": "webrtc",
"sub_category_id": 500,
"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": 134,
"existing_alias_text": "MySQL",
"input_term": "MySQL",
"matched_canonical": {
"category_id": 3,
"display_name": "MySQL",
"id": 17,
"is_also_category": false,
"is_extractable": true,
"skill_nature": "TOOL",
"slug": "mysql",
"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": 168,
"existing_alias_text": "Redis",
"input_term": "Redis",
"matched_canonical": {
"category_id": 3,
"display_name": "Redis",
"id": 31,
"is_also_category": false,
"is_extractable": true,
"skill_nature": "TOOL",
"slug": "redis",
"sub_category_id": 28,
"typical_lifespan": "EVERGREEN",
"volatility": "STABLE"
},
"matched_via": "alias"
},
{
"alias_persist_skipped_reason": "TODO: REMOVE AFTER TESTING \u2014 alias DB write disabled",
"alias_persisted": false,
"existing_alias_id": 1921,
"existing_alias_text": "response caching",
"input_term": "Caching",
"matched_canonical": {
"category_id": 13,
"display_name": "response caching",
"id": 1285,
"is_also_category": false,
"is_extractable": true,
"skill_nature": "TOOL",
"slug": "response-caching",
"sub_category_id": 1010,
"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": 2628,
"existing_alias_text": "SEO",
"input_term": "SEO",
"matched_canonical": {
"category_id": 37,
"display_name": "SEO",
"id": 1658,
"is_also_category": false,
"is_extractable": true,
"skill_nature": "CONCEPT",
"slug": "seo",
"sub_category_id": 1251,
"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": 840,
"existing_alias_text": "React.js",
"input_term": "React.js",
"matched_canonical": {
"category_id": 5,
"display_name": "React.js",
"id": 514,
"is_also_category": false,
"is_extractable": true,
"skill_nature": "FRAMEWORK",
"slug": "react-js",
"sub_category_id": 363,
"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": 4689,
"existing_alias_text": "Vue.js",
"input_term": "Vue.js",
"matched_canonical": {
"category_id": 5,
"display_name": "Vue.js",
"id": 3201,
"is_also_category": false,
"is_extractable": true,
"skill_nature": "FRAMEWORK",
"slug": "vue-js",
"sub_category_id": 1072,
"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": 5768,
"existing_alias_text": "OAuth",
"input_term": "OAuth",
"matched_canonical": {
"category_id": 10,
"display_name": "OAuth",
"id": 4066,
"is_also_category": false,
"is_extractable": true,
"skill_nature": "PROTOCOL",
"slug": "oauth",
"sub_category_id": 50,
"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": 165,
"existing_alias_text": "JWT",
"input_term": "JWT",
"matched_canonical": {
"category_id": 4,
"display_name": "JWT",
"id": 28,
"is_also_category": false,
"is_extractable": true,
"skill_nature": "STANDARD",
"slug": "jwt",
"sub_category_id": 33,
"typical_lifespan": "EVERGREEN",
"volatility": "STABLE"
},
"matched_via": "alias"
}
],
"candidate_roles": [
{
"display_name": "Backend Developer",
"id": 1,
"rationale": null,
"role_archetype": "A Backend Engineer designs, builds, and maintains the server-side logic and data handling that power applications and services. They focus on implementing reliable business functionality, integrating with other systems, and ensuring the backend is scalable, maintainable, and observable.",
"slug": "backend-engineer",
"source": "db"
},
{
"display_name": "Fullstack Developer",
"id": 15,
"rationale": null,
"role_archetype": null,
"slug": "full-stack-engineer",
"source": "db"
},
{
"display_name": "Fullstack Developer",
"id": 435,
"rationale": null,
"role_archetype": "Engineering",
"slug": "fullstack-developer",
"source": "db"
},
{
"display_name": "Java Backend Developer",
"id": 79,
"rationale": null,
"role_archetype": "Engineering",
"slug": "java-backend-developer",
"source": "db"
},
{
"display_name": "Node.js Backend Developer",
"id": 82,
"rationale": null,
"role_archetype": "Engineering",
"slug": "node-backend-developer",
"source": "db"
},
{
"display_name": "PHP Backend Developer",
"id": 86,
"rationale": null,
"role_archetype": "Engineering",
"slug": "php-backend-developer",
"source": "db"
},
{
"display_name": "Python Backend Developer",
"id": 80,
"rationale": null,
"role_archetype": "Engineering",
"slug": "python-backend-developer",
"source": "db"
},
{
"display_name": ".NET Backend Developer",
"id": 83,
"rationale": null,
"role_archetype": "Engineering",
"slug": "dotnet-backend-developer",
"source": "db"
},
{
"display_name": "Go Backend Developer",
"id": 81,
"rationale": null,
"role_archetype": "Engineering",
"slug": "go-backend-developer",
"source": "db"
},
{
"display_name": "Kotlin Backend Developer",
"id": 84,
"rationale": null,
"role_archetype": "Engineering",
"slug": "kotlin-server-backend-developer",
"source": "db"
},
{
"display_name": "Ruby Backend Developer",
"id": 85,
"rationale": null,
"role_archetype": "Engineering",
"slug": "ruby-backend-developer",
"source": "db"
},
{
"display_name": "Scala Backend Developer",
"id": 87,
"rationale": null,
"role_archetype": "Engineering",
"slug": "scala-backend-developer",
"source": "db"
},
{
"display_name": "Pega Developer",
"id": 24,
"rationale": null,
"role_archetype": null,
"slug": "pega-developer",
"source": "db"
},
{
"display_name": "Sitecore Dev",
"id": 233,
"rationale": null,
"role_archetype": "Engineering",
"slug": "sitecore-dev",
"source": "db"
},
{
"display_name": "Drupal Dev",
"id": 228,
"rationale": null,
"role_archetype": "Engineering",
"slug": "drupal-dev",
"source": "db"
},
{
"display_name": "Magento Dev",
"id": 231,
"rationale": null,
"role_archetype": "Engineering",
"slug": "magento-dev",
"source": "db"
},
{
"display_name": "Shopify Dev",
"id": 230,
"rationale": null,
"role_archetype": "Engineering",
"slug": "shopify-dev",
"source": "db"
},
{
"display_name": "WordPress Dev",
"id": 227,
"rationale": null,
"role_archetype": "Engineering",
"slug": "wordpress-dev",
"source": "db"
},
{
"display_name": "AI Engineer",
"id": 13,
"rationale": null,
"role_archetype": null,
"slug": "ai-engineer",
"source": "db"
},
{
"display_name": "Android Developer",
"id": 4,
"rationale": null,
"role_archetype": null,
"slug": "android-engineer",
"source": "db"
},
{
"display_name": "Frontend Developer",
"id": 7,
"rationale": null,
"role_archetype": null,
"slug": "frontend-engineer",
"source": "db"
},
{
"display_name": "Hybrid Mobile Developer",
"id": 11,
"rationale": null,
"role_archetype": null,
"slug": "hybrid-mobile-developer",
"source": "db"
},
{
"display_name": "Ionic Developer",
"id": 434,
"rationale": null,
"role_archetype": null,
"slug": "ionic-developer",
"source": "db"
},
{
"display_name": "Native Mobile Developer",
"id": 75,
"rationale": null,
"role_archetype": "Engineering",
"slug": "native-mobile-developer",
"source": "db"
},
{
"display_name": "Web Developer",
"id": 25,
"rationale": null,
"role_archetype": null,
"slug": "web-developer",
"source": "db"
},
{
"display_name": "iOS Developer",
"id": 6,
"rationale": null,
"role_archetype": null,
"slug": "ios-engineer",
"source": "db"
},
{
"display_name": "React Frontend Developer",
"id": 89,
"rationale": null,
"role_archetype": "Engineering",
"slug": "react-frontend-developer",
"source": "db"
},
{
"display_name": "Svelte Frontend Developer",
"id": 92,
"rationale": null,
"role_archetype": "Engineering",
"slug": "svelte-frontend-developer",
"source": "db"
},
{
"display_name": "Vue Frontend Developer",
"id": 91,
"rationale": null,
"role_archetype": "Engineering",
"slug": "vue-frontend-developer",
"source": "db"
}
],
"chosen_role": {
"display_name": "Web Developer",
"id": 25,
"rationale": "Multi-alias tie (4 roles at 1.0) resolved by TIER_B_TITLE: Web Developer",
"role_archetype": null,
"slug": "web-developer",
"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": "Laravel",
"llm_role": null,
"roles_from_db": [
{
"display_name": "Backend Developer",
"id": 1,
"rationale": null,
"role_archetype": "A Backend Engineer designs, builds, and maintains the server-side logic and data handling that power applications and services. They focus on implementing reliable business functionality, integrating with other systems, and ensuring the backend is scalable, maintainable, and observable.",
"slug": "backend-engineer",
"source": "db"
},
{
"display_name": "Fullstack Developer",
"id": 15,
"rationale": null,
"role_archetype": null,
"slug": "full-stack-engineer",
"source": "db"
},
{
"display_name": "Fullstack Developer",
"id": 435,
"rationale": null,
"role_archetype": "Engineering",
"slug": "fullstack-developer",
"source": "db"
},
{
"display_name": "Java Backend Developer",
"id": 79,
"rationale": null,
"role_archetype": "Engineering",
"slug": "java-backend-developer",
"source": "db"
},
{
"display_name": "Node.js Backend Developer",
"id": 82,
"rationale": null,
"role_archetype": "Engineering",
"slug": "node-backend-developer",
"source": "db"
},
{
"display_name": "PHP Backend Developer",
"id": 86,
"rationale": null,
"role_archetype": "Engineering",
"slug": "php-backend-developer",
"source": "db"
},
{
"display_name": "Python Backend Developer",
"id": 80,
"rationale": null,
"role_archetype": "Engineering",
"slug": "python-backend-developer",
"source": "db"
}
]
},
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "API Design and Contracts",
"id": 3,
"rationale": "Designing request/response shapes and the rules that govern client-server interaction. This cluster is coherent because full stack engineers often own the contract between UI behavior and backend implementation.",
"slug": "api-design-and-contracts",
"source": "db"
},
"input_skill": "REST",
"llm_role": null,
"roles_from_db": [
{
"display_name": "Backend Developer",
"id": 1,
"rationale": null,
"role_archetype": "A Backend Engineer designs, builds, and maintains the server-side logic and data handling that power applications and services. They focus on implementing reliable business functionality, integrating with other systems, and ensuring the backend is scalable, maintainable, and observable.",
"slug": "backend-engineer",
"source": "db"
},
{
"display_name": "Fullstack Developer",
"id": 15,
"rationale": null,
"role_archetype": null,
"slug": "full-stack-engineer",
"source": "db"
}
]
},
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "API Interface and Contract Design",
"id": 289,
"rationale": "Designing backend service interfaces and contracts that other systems consume, including endpoint and operation shape, request/response payloads, schema and validation, pagination, filtering, idempotency, versioning, status codes, and backward compatibility across REST, GraphQL, gRPC, and OpenAPI-based APIs.",
"slug": "api-interface-and-contract-design",
"source": "db"
},
"input_skill": "REST",
"llm_role": null,
"roles_from_db": [
{
"display_name": ".NET Backend Developer",
"id": 83,
"rationale": null,
"role_archetype": "Engineering",
"slug": "dotnet-backend-developer",
"source": "db"
},
{
"display_name": "Go Backend Developer",
"id": 81,
"rationale": null,
"role_archetype": "Engineering",
"slug": "go-backend-developer",
"source": "db"
},
{
"display_name": "Kotlin Backend Developer",
"id": 84,
"rationale": null,
"role_archetype": "Engineering",
"slug": "kotlin-server-backend-developer",
"source": "db"
},
{
"display_name": "Node.js Backend Developer",
"id": 82,
"rationale": null,
"role_archetype": "Engineering",
"slug": "node-backend-developer",
"source": "db"
},
{
"display_name": "PHP Backend Developer",
"id": 86,
"rationale": null,
"role_archetype": "Engineering",
"slug": "php-backend-developer",
"source": "db"
},
{
"display_name": "Python Backend Developer",
"id": 80,
"rationale": null,
"role_archetype": "Engineering",
"slug": "python-backend-developer",
"source": "db"
},
{
"display_name": "Ruby Backend Developer",
"id": 85,
"rationale": null,
"role_archetype": "Engineering",
"slug": "ruby-backend-developer",
"source": "db"
},
{
"display_name": "Scala Backend Developer",
"id": 87,
"rationale": null,
"role_archetype": "Engineering",
"slug": "scala-backend-developer",
"source": "db"
}
]
},
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Integration Protocols \u0026 Standards",
"id": 271,
"rationale": "Standards and protocols for integrating Pega applications.",
"slug": "integration-protocols-standards",
"source": "db"
},
"input_skill": "REST",
"llm_role": null,
"roles_from_db": [
{
"display_name": "Pega Developer",
"id": 24,
"rationale": null,
"role_archetype": null,
"slug": "pega-developer",
"source": "db"
}
]
},
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Standards \u0026 Protocols Compliance",
"id": 452,
"rationale": "Encompasses key web and data standards, protocols, and compliance requirements relevant to Sitecore implementations.",
"slug": "standards-protocols-compliance",
"source": "db"
},
"input_skill": "REST",
"llm_role": null,
"roles_from_db": [
{
"display_name": "Sitecore Dev",
"id": 233,
"rationale": null,
"role_archetype": "Engineering",
"slug": "sitecore-dev",
"source": "db"
}
]
},
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "External Integrations and Clients",
"id": 375,
"rationale": "Connecting Go backend services to third-party APIs and internal enterprise systems. This cluster is coherent because the role frequently builds outbound clients, handles retries, and maps external payloads into service workflows.",
"slug": "external-integrations-and-clients",
"source": "db"
},
"input_skill": "Webhooks",
"llm_role": null,
"roles_from_db": [
{
"display_name": "Go Backend Developer",
"id": 81,
"rationale": null,
"role_archetype": "Engineering",
"slug": "go-backend-developer",
"source": "db"
}
]
},
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "External System Integrations",
"id": 14,
"rationale": "Connecting backend services to third-party APIs and internal enterprise systems. This includes client libraries, webhooks, retries, data mapping, and integration failure handling.",
"slug": "external-system-integrations",
"source": "db"
},
"input_skill": "Webhooks",
"llm_role": null,
"roles_from_db": [
{
"display_name": ".NET Backend Developer",
"id": 83,
"rationale": null,
"role_archetype": "Engineering",
"slug": "dotnet-backend-developer",
"source": "db"
},
{
"display_name": "Backend Developer",
"id": 1,
"rationale": null,
"role_archetype": "A Backend Engineer designs, builds, and maintains the server-side logic and data handling that power applications and services. They focus on implementing reliable business functionality, integrating with other systems, and ensuring the backend is scalable, maintainable, and observable.",
"slug": "backend-engineer",
"source": "db"
},
{
"display_name": "Drupal Dev",
"id": 228,
"rationale": null,
"role_archetype": "Engineering",
"slug": "drupal-dev",
"source": "db"
},
{
"display_name": "Java Backend Developer",
"id": 79,
"rationale": null,
"role_archetype": "Engineering",
"slug": "java-backend-developer",
"source": "db"
},
{
"display_name": "Kotlin Backend Developer",
"id": 84,
"rationale": null,
"role_archetype": "Engineering",
"slug": "kotlin-server-backend-developer",
"source": "db"
},
{
"display_name": "Node.js Backend Developer",
"id": 82,
"rationale": null,
"role_archetype": "Engineering",
"slug": "node-backend-developer",
"source": "db"
},
{
"display_name": "PHP Backend Developer",
"id": 86,
"rationale": null,
"role_archetype": "Engineering",
"slug": "php-backend-developer",
"source": "db"
},
{
"display_name": "Python Backend Developer",
"id": 80,
"rationale": null,
"role_archetype": "Engineering",
"slug": "python-backend-developer",
"source": "db"
},
{
"display_name": "Ruby Backend Developer",
"id": 85,
"rationale": null,
"role_archetype": "Engineering",
"slug": "ruby-backend-developer",
"source": "db"
},
{
"display_name": "Scala Backend Developer",
"id": 87,
"rationale": null,
"role_archetype": "Engineering",
"slug": "scala-backend-developer",
"source": "db"
}
]
},
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Magento Integration Adapters",
"id": 401,
"rationale": "Connecting Magento to external commerce systems and services. This cluster covers API clients, webhooks, message-driven adapters, and data mapping needed to synchronize storefront behavior with surrounding platforms.",
"slug": "magento-integration-adapters",
"source": "db"
},
"input_skill": "Webhooks",
"llm_role": null,
"roles_from_db": [
{
"display_name": "Magento Dev",
"id": 231,
"rationale": null,
"role_archetype": "Engineering",
"slug": "magento-dev",
"source": "db"
}
]
},
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Shopify APIs and Webhooks",
"id": 427,
"rationale": "Integration work that connects storefronts and apps to external business systems through Shopify interfaces. This cluster is central because Shopify Dev often wires store behavior to inventory, ERP, CRM, and fulfillment systems.",
"slug": "shopify-apis-and-webhooks",
"source": "db"
},
"input_skill": "Webhooks",
"llm_role": null,
"roles_from_db": [
{
"display_name": "Shopify Dev",
"id": 230,
"rationale": null,
"role_archetype": "Engineering",
"slug": "shopify-dev",
"source": "db"
}
]
},
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Sitecore Integration Patterns",
"id": 444,
"rationale": "Connecting Sitecore to adjacent systems such as commerce, search, identity, analytics, and data services. This cluster covers the integration code and patterns needed to keep the site experience connected to enterprise systems.",
"slug": "sitecore-integration-patterns",
"source": "db"
},
"input_skill": "Webhooks",
"llm_role": null,
"roles_from_db": [
{
"display_name": "Sitecore Dev",
"id": 233,
"rationale": null,
"role_archetype": "Engineering",
"slug": "sitecore-dev",
"source": "db"
}
]
},
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "WordPress REST Integrations",
"id": 332,
"rationale": "Connecting WordPress sites to external services and internal systems through APIs and webhooks. This is a distinct cluster because WordPress developers frequently implement data exchange, sync, and integration behavior at the site layer.",
"slug": "wordpress-rest-integrations",
"source": "db"
},
"input_skill": "Webhooks",
"llm_role": null,
"roles_from_db": [
{
"display_name": "WordPress Dev",
"id": 227,
"rationale": null,
"role_archetype": "Engineering",
"slug": "wordpress-dev",
"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": "WebRTC",
"llm_role": null,
"roles_from_db": []
},
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Relational Data Modeling",
"id": 216,
"rationale": "Modeling and tuning relational persistence for backend features. PHP backend developers need this to shape schemas, indexes, transactions, and query-aware data structures that support application behavior.",
"slug": "relational-data-modeling",
"source": "db"
},
"input_skill": "MySQL",
"llm_role": null,
"roles_from_db": [
{
"display_name": "Fullstack Developer",
"id": 15,
"rationale": null,
"role_archetype": null,
"slug": "full-stack-engineer",
"source": "db"
},
{
"display_name": "Fullstack Developer",
"id": 435,
"rationale": null,
"role_archetype": "Engineering",
"slug": "fullstack-developer",
"source": "db"
},
{
"display_name": "PHP Backend Developer",
"id": 86,
"rationale": null,
"role_archetype": "Engineering",
"slug": "php-backend-developer",
"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": "MySQL",
"llm_role": null,
"roles_from_db": [
{
"display_name": ".NET Backend Developer",
"id": 83,
"rationale": null,
"role_archetype": "Engineering",
"slug": "dotnet-backend-developer",
"source": "db"
},
{
"display_name": "Backend Developer",
"id": 1,
"rationale": null,
"role_archetype": "A Backend Engineer designs, builds, and maintains the server-side logic and data handling that power applications and services. They focus on implementing reliable business functionality, integrating with other systems, and ensuring the backend is scalable, maintainable, and observable.",
"slug": "backend-engineer",
"source": "db"
},
{
"display_name": "Kotlin Backend Developer",
"id": 84,
"rationale": null,
"role_archetype": "Engineering",
"slug": "kotlin-server-backend-developer",
"source": "db"
},
{
"display_name": "Node.js Backend Developer",
"id": 82,
"rationale": null,
"role_archetype": "Engineering",
"slug": "node-backend-developer",
"source": "db"
},
{
"display_name": "Python Backend Developer",
"id": 80,
"rationale": null,
"role_archetype": "Engineering",
"slug": "python-backend-developer",
"source": "db"
},
{
"display_name": "Ruby Backend Developer",
"id": 85,
"rationale": null,
"role_archetype": "Engineering",
"slug": "ruby-backend-developer",
"source": "db"
},
{
"display_name": "Scala Backend Developer",
"id": 87,
"rationale": null,
"role_archetype": "Engineering",
"slug": "scala-backend-developer",
"source": "db"
}
]
},
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Relational Database Usage",
"id": 371,
"rationale": "Working effectively with operational relational databases from Go backend services. This includes schema-aware querying, indexing awareness, transactions, and understanding how service code interacts with PostgreSQL or similar systems.",
"slug": "relational-database-usage",
"source": "db"
},
"input_skill": "MySQL",
"llm_role": null,
"roles_from_db": [
{
"display_name": "Go Backend Developer",
"id": 81,
"rationale": null,
"role_archetype": "Engineering",
"slug": "go-backend-developer",
"source": "db"
}
]
},
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Caching and State Management",
"id": 7,
"rationale": "Techniques and systems for reducing latency and managing ephemeral backend state. Covers cache-aside patterns, distributed caches, session stores, and invalidation strategies.",
"slug": "caching-and-state-management",
"source": "db"
},
"input_skill": "Redis",
"llm_role": null,
"roles_from_db": [
{
"display_name": ".NET Backend Developer",
"id": 83,
"rationale": null,
"role_archetype": "Engineering",
"slug": "dotnet-backend-developer",
"source": "db"
},
{
"display_name": "Backend Developer",
"id": 1,
"rationale": null,
"role_archetype": "A Backend Engineer designs, builds, and maintains the server-side logic and data handling that power applications and services. They focus on implementing reliable business functionality, integrating with other systems, and ensuring the backend is scalable, maintainable, and observable.",
"slug": "backend-engineer",
"source": "db"
},
{
"display_name": "Kotlin Backend Developer",
"id": 84,
"rationale": null,
"role_archetype": "Engineering",
"slug": "kotlin-server-backend-developer",
"source": "db"
},
{
"display_name": "Node.js Backend Developer",
"id": 82,
"rationale": null,
"role_archetype": "Engineering",
"slug": "node-backend-developer",
"source": "db"
},
{
"display_name": "PHP Backend Developer",
"id": 86,
"rationale": null,
"role_archetype": "Engineering",
"slug": "php-backend-developer",
"source": "db"
},
{
"display_name": "Python Backend Developer",
"id": 80,
"rationale": null,
"role_archetype": "Engineering",
"slug": "python-backend-developer",
"source": "db"
},
{
"display_name": "Ruby Backend Developer",
"id": 85,
"rationale": null,
"role_archetype": "Engineering",
"slug": "ruby-backend-developer",
"source": "db"
},
{
"display_name": "Scala Backend Developer",
"id": 87,
"rationale": null,
"role_archetype": "Engineering",
"slug": "scala-backend-developer",
"source": "db"
}
]
},
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Magento Caching and Performance",
"id": 404,
"rationale": "Performance tuning specific to Magento storefronts and their rendering pipeline. This includes cache layers, page generation costs, and practical optimizations that preserve upgradeability while improving shopper experience.",
"slug": "magento-caching-and-performance",
"source": "db"
},
"input_skill": "Redis",
"llm_role": null,
"roles_from_db": [
{
"display_name": "Magento Dev",
"id": 231,
"rationale": null,
"role_archetype": "Engineering",
"slug": "magento-dev",
"source": "db"
}
]
},
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Latency and Cost Optimization",
"id": 205,
"rationale": "Techniques for making AI features fast and affordable enough for production use. This cluster is coherent because model choice, prompt length, caching, batching, and routing directly affect user experience and unit economics.",
"slug": "latency-and-cost-optimization",
"source": "db"
},
"input_skill": "Caching",
"llm_role": null,
"roles_from_db": [
{
"display_name": "AI Engineer",
"id": 13,
"rationale": null,
"role_archetype": null,
"slug": "ai-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": "SEO",
"llm_role": null,
"roles_from_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": "React.js",
"llm_role": null,
"roles_from_db": []
},
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Frameworks \u0026 Libraries",
"id": 360,
"rationale": "The PHP frameworks and JavaScript libraries commonly employed within Drupal projects for building features and integrations.",
"slug": "frameworks-libraries",
"source": "db"
},
"input_skill": "Vue.js",
"llm_role": null,
"roles_from_db": [
{
"display_name": "Drupal Dev",
"id": 228,
"rationale": null,
"role_archetype": "Engineering",
"slug": "drupal-dev",
"source": "db"
}
]
},
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Shopify APIs and Webhooks",
"id": 427,
"rationale": "Integration work that connects storefronts and apps to external business systems through Shopify interfaces. This cluster is central because Shopify Dev often wires store behavior to inventory, ERP, CRM, and fulfillment systems.",
"slug": "shopify-apis-and-webhooks",
"source": "db"
},
"input_skill": "OAuth",
"llm_role": null,
"roles_from_db": [
{
"display_name": "Shopify Dev",
"id": 230,
"rationale": null,
"role_archetype": "Engineering",
"slug": "shopify-dev",
"source": "db"
}
]
},
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Authentication and Authorization",
"id": 6,
"rationale": "Identity, session, and access-control mechanisms used to protect PHP backend resources. This includes login flows, token handling, role checks, permissions, and policy enforcement in server-side code.",
"slug": "authentication-and-authorization",
"source": "db"
},
"input_skill": "JWT",
"llm_role": null,
"roles_from_db": [
{
"display_name": ".NET Backend Developer",
"id": 83,
"rationale": null,
"role_archetype": "Engineering",
"slug": "dotnet-backend-developer",
"source": "db"
},
{
"display_name": "Backend Developer",
"id": 1,
"rationale": null,
"role_archetype": "A Backend Engineer designs, builds, and maintains the server-side logic and data handling that power applications and services. They focus on implementing reliable business functionality, integrating with other systems, and ensuring the backend is scalable, maintainable, and observable.",
"slug": "backend-engineer",
"source": "db"
},
{
"display_name": "Go Backend Developer",
"id": 81,
"rationale": null,
"role_archetype": "Engineering",
"slug": "go-backend-developer",
"source": "db"
},
{
"display_name": "Java Backend Developer",
"id": 79,
"rationale": null,
"role_archetype": "Engineering",
"slug": "java-backend-developer",
"source": "db"
},
{
"display_name": "Node.js Backend Developer",
"id": 82,
"rationale": null,
"role_archetype": "Engineering",
"slug": "node-backend-developer",
"source": "db"
},
{
"display_name": "PHP Backend Developer",
"id": 86,
"rationale": null,
"role_archetype": "Engineering",
"slug": "php-backend-developer",
"source": "db"
},
{
"display_name": "Python Backend Developer",
"id": 80,
"rationale": null,
"role_archetype": "Engineering",
"slug": "python-backend-developer",
"source": "db"
}
]
},
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Authentication and Session Handling",
"id": 86,
"rationale": "Client-side identity flows and secure session management used to sign users in and keep them authenticated. This includes token handling, login UX, and protecting secrets on device.",
"slug": "authentication-and-session-handling",
"source": "db"
},
"input_skill": "JWT",
"llm_role": null,
"roles_from_db": [
{
"display_name": "Android Developer",
"id": 4,
"rationale": null,
"role_archetype": null,
"slug": "android-engineer",
"source": "db"
},
{
"display_name": "Frontend Developer",
"id": 7,
"rationale": null,
"role_archetype": null,
"slug": "frontend-engineer",
"source": "db"
},
{
"display_name": "Fullstack Developer",
"id": 15,
"rationale": null,
"role_archetype": null,
"slug": "full-stack-engineer",
"source": "db"
},
{
"display_name": "Hybrid Mobile Developer",
"id": 11,
"rationale": null,
"role_archetype": null,
"slug": "hybrid-mobile-developer",
"source": "db"
},
{
"display_name": "Ionic Developer",
"id": 434,
"rationale": null,
"role_archetype": null,
"slug": "ionic-developer",
"source": "db"
},
{
"display_name": "Native Mobile Developer",
"id": 75,
"rationale": null,
"role_archetype": "Engineering",
"slug": "native-mobile-developer",
"source": "db"
},
{
"display_name": "Web Developer",
"id": 25,
"rationale": null,
"role_archetype": null,
"slug": "web-developer",
"source": "db"
},
{
"display_name": "iOS Developer",
"id": 6,
"rationale": null,
"role_archetype": null,
"slug": "ios-engineer",
"source": "db"
}
]
},
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Backend Authentication and Authorization",
"id": 386,
"rationale": "Identity and access control mechanisms used by backend services to authenticate users or clients and enforce permissions on protected resources. This includes token and session handling, OAuth 2.0 / OpenID Connect / SAML flows, JWT and access tokens, API keys, MFA, role- or claim-based authorization, RBAC/ABAC, scopes, policies, Spring Security, and authorization filters.",
"slug": "backend-authentication-and-authorization",
"source": "db"
},
"input_skill": "JWT",
"llm_role": null,
"roles_from_db": [
{
"display_name": "Kotlin Backend Developer",
"id": 84,
"rationale": null,
"role_archetype": "Engineering",
"slug": "kotlin-server-backend-developer",
"source": "db"
},
{
"display_name": "Ruby Backend Developer",
"id": 85,
"rationale": null,
"role_archetype": "Engineering",
"slug": "ruby-backend-developer",
"source": "db"
},
{
"display_name": "Scala Backend Developer",
"id": 87,
"rationale": null,
"role_archetype": "Engineering",
"slug": "scala-backend-developer",
"source": "db"
}
]
},
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Frontend Authentication and Session Management",
"id": 300,
"rationale": "Client-side authentication and session management for frontend applications, including sign-in flows, OAuth 2.0/OpenID Connect/SSO integration, JWT and refresh token handling, login forms, protected routes, session persistence, and session-expiry user experience. This covers the user-facing parts of identity workflows implemented in React or other frontend stacks, but excludes identity provider administration, backend authorization policy, secret storage on servers, and MFA device management.",
"slug": "frontend-authentication-and-session-management",
"source": "db"
},
"input_skill": "JWT",
"llm_role": null,
"roles_from_db": [
{
"display_name": "React Frontend Developer",
"id": 89,
"rationale": null,
"role_archetype": "Engineering",
"slug": "react-frontend-developer",
"source": "db"
},
{
"display_name": "Svelte Frontend Developer",
"id": 92,
"rationale": null,
"role_archetype": "Engineering",
"slug": "svelte-frontend-developer",
"source": "db"
},
{
"display_name": "Vue Frontend Developer",
"id": 91,
"rationale": null,
"role_archetype": "Engineering",
"slug": "vue-frontend-developer",
"source": "db"
}
]
}
],
"input_final_skills": [
"Laravel",
"REST",
"API Development",
"Webhooks",
"WebRTC",
"MySQL",
"Redis",
"Caching",
"socket.io",
"Pusher",
"SEO",
"OpenGraph",
"Twitter Cards",
"Structured Data",
"React.js",
"Vue.js",
"OAuth",
"JWT"
],
"input_llm_skills": [
"Laravel",
"REST",
"API Development",
"Webhooks",
"WebRTC",
"MySQL",
"Redis",
"Caching",
"socket.io",
"Pusher",
"SEO",
"OpenGraph",
"Twitter Cards",
"Structured Data",
"React.js",
"Vue.js",
"OAuth",
"JWT"
],
"new_aliases_persisted": 0,
"run_id": "08be24ac-5284-4a44-91f7-18094da63273",
"skills_detail": [
{
"aliases_in_db": [
{
"alias_text": "Laravel",
"alias_type": "CANONICAL",
"id": 5429,
"is_primary": true,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "Laravel 10",
"alias_type": "VERSION",
"id": 5442,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "Laravel 11",
"alias_type": "VERSION",
"id": 5443,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "Laravel 4",
"alias_type": "VERSION",
"id": 5430,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "Laravel 5",
"alias_type": "VERSION",
"id": 5431,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "Laravel 6",
"alias_type": "VERSION",
"id": 5432,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "Laravel 7",
"alias_type": "VERSION",
"id": 5433,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "Laravel 8",
"alias_type": "VERSION",
"id": 5434,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "Laravel 9",
"alias_type": "VERSION",
"id": 5435,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "laravel 10",
"alias_type": "VERSION",
"id": 5444,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "laravel 11",
"alias_type": "VERSION",
"id": 5445,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "laravel 4",
"alias_type": "VERSION",
"id": 5436,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "laravel 5",
"alias_type": "VERSION",
"id": 5437,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "laravel 6",
"alias_type": "VERSION",
"id": 5438,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "laravel 7",
"alias_type": "VERSION",
"id": 5439,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "laravel 8",
"alias_type": "VERSION",
"id": 5440,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "laravel 9",
"alias_type": "VERSION",
"id": 5441,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
}
],
"canonical": {
"category_id": 5,
"display_name": "Laravel",
"id": 3798,
"is_also_category": false,
"is_extractable": true,
"skill_nature": "FRAMEWORK",
"slug": "laravel",
"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": "Laravel",
"llm_role": null,
"roles_from_db": [
{
"display_name": "Backend Developer",
"id": 1,
"rationale": null,
"role_archetype": "A Backend Engineer designs, builds, and maintains the server-side logic and data handling that power applications and services. They focus on implementing reliable business functionality, integrating with other systems, and ensuring the backend is scalable, maintainable, and observable.",
"slug": "backend-engineer",
"source": "db"
},
{
"display_name": "Fullstack Developer",
"id": 15,
"rationale": null,
"role_archetype": null,
"slug": "full-stack-engineer",
"source": "db"
},
{
"display_name": "Fullstack Developer",
"id": 435,
"rationale": null,
"role_archetype": "Engineering",
"slug": "fullstack-developer",
"source": "db"
},
{
"display_name": "Java Backend Developer",
"id": 79,
"rationale": null,
"role_archetype": "Engineering",
"slug": "java-backend-developer",
"source": "db"
},
{
"display_name": "Node.js Backend Developer",
"id": 82,
"rationale": null,
"role_archetype": "Engineering",
"slug": "node-backend-developer",
"source": "db"
},
{
"display_name": "PHP Backend Developer",
"id": 86,
"rationale": null,
"role_archetype": "Engineering",
"slug": "php-backend-developer",
"source": "db"
},
{
"display_name": "Python Backend Developer",
"id": 80,
"rationale": null,
"role_archetype": "Engineering",
"slug": "python-backend-developer",
"source": "db"
}
]
}
],
"input_skill": "Laravel",
"matched_via": "alias",
"new_alias_persisted": false,
"new_alias_text": null,
"new_skill_meta": null,
"source_tag": "db",
"was_in_llm_skills": true
},
{
"aliases_in_db": [
{
"alias_text": "REST",
"alias_type": "CANONICAL",
"id": 106,
"is_primary": true,
"match_strategy": "CASE_INSENSITIVE"
}
],
"canonical": {
"category_id": 2,
"display_name": "REST",
"id": 11,
"is_also_category": false,
"is_extractable": true,
"skill_nature": "CONCEPT",
"slug": "rest",
"sub_category_id": 2122,
"typical_lifespan": "EVERGREEN",
"volatility": "STABLE"
},
"dimensions": [
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "API Design and Contracts",
"id": 3,
"rationale": "Designing request/response shapes and the rules that govern client-server interaction. This cluster is coherent because full stack engineers often own the contract between UI behavior and backend implementation.",
"slug": "api-design-and-contracts",
"source": "db"
},
"input_skill": "REST",
"llm_role": null,
"roles_from_db": [
{
"display_name": "Backend Developer",
"id": 1,
"rationale": null,
"role_archetype": "A Backend Engineer designs, builds, and maintains the server-side logic and data handling that power applications and services. They focus on implementing reliable business functionality, integrating with other systems, and ensuring the backend is scalable, maintainable, and observable.",
"slug": "backend-engineer",
"source": "db"
},
{
"display_name": "Fullstack Developer",
"id": 15,
"rationale": null,
"role_archetype": null,
"slug": "full-stack-engineer",
"source": "db"
}
]
},
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "API Interface and Contract Design",
"id": 289,
"rationale": "Designing backend service interfaces and contracts that other systems consume, including endpoint and operation shape, request/response payloads, schema and validation, pagination, filtering, idempotency, versioning, status codes, and backward compatibility across REST, GraphQL, gRPC, and OpenAPI-based APIs.",
"slug": "api-interface-and-contract-design",
"source": "db"
},
"input_skill": "REST",
"llm_role": null,
"roles_from_db": [
{
"display_name": ".NET Backend Developer",
"id": 83,
"rationale": null,
"role_archetype": "Engineering",
"slug": "dotnet-backend-developer",
"source": "db"
},
{
"display_name": "Go Backend Developer",
"id": 81,
"rationale": null,
"role_archetype": "Engineering",
"slug": "go-backend-developer",
"source": "db"
},
{
"display_name": "Kotlin Backend Developer",
"id": 84,
"rationale": null,
"role_archetype": "Engineering",
"slug": "kotlin-server-backend-developer",
"source": "db"
},
{
"display_name": "Node.js Backend Developer",
"id": 82,
"rationale": null,
"role_archetype": "Engineering",
"slug": "node-backend-developer",
"source": "db"
},
{
"display_name": "PHP Backend Developer",
"id": 86,
"rationale": null,
"role_archetype": "Engineering",
"slug": "php-backend-developer",
"source": "db"
},
{
"display_name": "Python Backend Developer",
"id": 80,
"rationale": null,
"role_archetype": "Engineering",
"slug": "python-backend-developer",
"source": "db"
},
{
"display_name": "Ruby Backend Developer",
"id": 85,
"rationale": null,
"role_archetype": "Engineering",
"slug": "ruby-backend-developer",
"source": "db"
},
{
"display_name": "Scala Backend Developer",
"id": 87,
"rationale": null,
"role_archetype": "Engineering",
"slug": "scala-backend-developer",
"source": "db"
}
]
},
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Integration Protocols \u0026 Standards",
"id": 271,
"rationale": "Standards and protocols for integrating Pega applications.",
"slug": "integration-protocols-standards",
"source": "db"
},
"input_skill": "REST",
"llm_role": null,
"roles_from_db": [
{
"display_name": "Pega Developer",
"id": 24,
"rationale": null,
"role_archetype": null,
"slug": "pega-developer",
"source": "db"
}
]
},
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Standards \u0026 Protocols Compliance",
"id": 452,
"rationale": "Encompasses key web and data standards, protocols, and compliance requirements relevant to Sitecore implementations.",
"slug": "standards-protocols-compliance",
"source": "db"
},
"input_skill": "REST",
"llm_role": null,
"roles_from_db": [
{
"display_name": "Sitecore Dev",
"id": 233,
"rationale": null,
"role_archetype": "Engineering",
"slug": "sitecore-dev",
"source": "db"
}
]
}
],
"input_skill": "REST",
"matched_via": "alias",
"new_alias_persisted": false,
"new_alias_text": null,
"new_skill_meta": null,
"source_tag": "db",
"was_in_llm_skills": true
},
{
"aliases_in_db": [],
"canonical": null,
"dimensions": [],
"input_skill": "API Development",
"matched_via": null,
"new_alias_persisted": false,
"new_alias_text": null,
"new_skill_meta": {
"derived": {
"category": "Concepts",
"skill_nature": "CONCEPT",
"sub_category": "general",
"typical_lifespan": "EVERGREEN",
"version_strategy": "UNVERSIONED",
"volatility": "STABLE"
},
"enrichment": null,
"keep_log": [],
"locked_dimensions": [],
"merge_log": [],
"placed": null,
"relationships": null,
"skill_id": "api-development",
"split_log": [],
"typed": null,
"warnings": []
},
"source_tag": "llm",
"was_in_llm_skills": true
},
{
"aliases_in_db": [
{
"alias_text": "webhooks",
"alias_type": "CANONICAL",
"id": 3645,
"is_primary": true,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "Webhooks",
"alias_type": "CANONICAL",
"id": 3507,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
}
],
"canonical": {
"category_id": 2,
"display_name": "webhooks",
"id": 2243,
"is_also_category": false,
"is_extractable": true,
"skill_nature": "CONCEPT",
"slug": "webhooks",
"sub_category_id": 3531,
"typical_lifespan": "EVERGREEN",
"volatility": "STABLE"
},
"dimensions": [
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "External Integrations and Clients",
"id": 375,
"rationale": "Connecting Go backend services to third-party APIs and internal enterprise systems. This cluster is coherent because the role frequently builds outbound clients, handles retries, and maps external payloads into service workflows.",
"slug": "external-integrations-and-clients",
"source": "db"
},
"input_skill": "Webhooks",
"llm_role": null,
"roles_from_db": [
{
"display_name": "Go Backend Developer",
"id": 81,
"rationale": null,
"role_archetype": "Engineering",
"slug": "go-backend-developer",
"source": "db"
}
]
},
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "External System Integrations",
"id": 14,
"rationale": "Connecting backend services to third-party APIs and internal enterprise systems. This includes client libraries, webhooks, retries, data mapping, and integration failure handling.",
"slug": "external-system-integrations",
"source": "db"
},
"input_skill": "Webhooks",
"llm_role": null,
"roles_from_db": [
{
"display_name": ".NET Backend Developer",
"id": 83,
"rationale": null,
"role_archetype": "Engineering",
"slug": "dotnet-backend-developer",
"source": "db"
},
{
"display_name": "Backend Developer",
"id": 1,
"rationale": null,
"role_archetype": "A Backend Engineer designs, builds, and maintains the server-side logic and data handling that power applications and services. They focus on implementing reliable business functionality, integrating with other systems, and ensuring the backend is scalable, maintainable, and observable.",
"slug": "backend-engineer",
"source": "db"
},
{
"display_name": "Drupal Dev",
"id": 228,
"rationale": null,
"role_archetype": "Engineering",
"slug": "drupal-dev",
"source": "db"
},
{
"display_name": "Java Backend Developer",
"id": 79,
"rationale": null,
"role_archetype": "Engineering",
"slug": "java-backend-developer",
"source": "db"
},
{
"display_name": "Kotlin Backend Developer",
"id": 84,
"rationale": null,
"role_archetype": "Engineering",
"slug": "kotlin-server-backend-developer",
"source": "db"
},
{
"display_name": "Node.js Backend Developer",
"id": 82,
"rationale": null,
"role_archetype": "Engineering",
"slug": "node-backend-developer",
"source": "db"
},
{
"display_name": "PHP Backend Developer",
"id": 86,
"rationale": null,
"role_archetype": "Engineering",
"slug": "php-backend-developer",
"source": "db"
},
{
"display_name": "Python Backend Developer",
"id": 80,
"rationale": null,
"role_archetype": "Engineering",
"slug": "python-backend-developer",
"source": "db"
},
{
"display_name": "Ruby Backend Developer",
"id": 85,
"rationale": null,
"role_archetype": "Engineering",
"slug": "ruby-backend-developer",
"source": "db"
},
{
"display_name": "Scala Backend Developer",
"id": 87,
"rationale": null,
"role_archetype": "Engineering",
"slug": "scala-backend-developer",
"source": "db"
}
]
},
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Magento Integration Adapters",
"id": 401,
"rationale": "Connecting Magento to external commerce systems and services. This cluster covers API clients, webhooks, message-driven adapters, and data mapping needed to synchronize storefront behavior with surrounding platforms.",
"slug": "magento-integration-adapters",
"source": "db"
},
"input_skill": "Webhooks",
"llm_role": null,
"roles_from_db": [
{
"display_name": "Magento Dev",
"id": 231,
"rationale": null,
"role_archetype": "Engineering",
"slug": "magento-dev",
"source": "db"
}
]
},
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Shopify APIs and Webhooks",
"id": 427,
"rationale": "Integration work that connects storefronts and apps to external business systems through Shopify interfaces. This cluster is central because Shopify Dev often wires store behavior to inventory, ERP, CRM, and fulfillment systems.",
"slug": "shopify-apis-and-webhooks",
"source": "db"
},
"input_skill": "Webhooks",
"llm_role": null,
"roles_from_db": [
{
"display_name": "Shopify Dev",
"id": 230,
"rationale": null,
"role_archetype": "Engineering",
"slug": "shopify-dev",
"source": "db"
}
]
},
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Sitecore Integration Patterns",
"id": 444,
"rationale": "Connecting Sitecore to adjacent systems such as commerce, search, identity, analytics, and data services. This cluster covers the integration code and patterns needed to keep the site experience connected to enterprise systems.",
"slug": "sitecore-integration-patterns",
"source": "db"
},
"input_skill": "Webhooks",
"llm_role": null,
"roles_from_db": [
{
"display_name": "Sitecore Dev",
"id": 233,
"rationale": null,
"role_archetype": "Engineering",
"slug": "sitecore-dev",
"source": "db"
}
]
},
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "WordPress REST Integrations",
"id": 332,
"rationale": "Connecting WordPress sites to external services and internal systems through APIs and webhooks. This is a distinct cluster because WordPress developers frequently implement data exchange, sync, and integration behavior at the site layer.",
"slug": "wordpress-rest-integrations",
"source": "db"
},
"input_skill": "Webhooks",
"llm_role": null,
"roles_from_db": [
{
"display_name": "WordPress Dev",
"id": 227,
"rationale": null,
"role_archetype": "Engineering",
"slug": "wordpress-dev",
"source": "db"
}
]
}
],
"input_skill": "Webhooks",
"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": "WebRTC",
"alias_type": "CANONICAL",
"id": 2552,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
}
],
"canonical": {
"category_id": 10,
"display_name": "WebRTC",
"id": 1600,
"is_also_category": false,
"is_extractable": true,
"skill_nature": "PROTOCOL",
"slug": "webrtc",
"sub_category_id": 500,
"typical_lifespan": "EVERGREEN",
"volatility": "STABLE"
},
"dimensions": [
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "React Frontend Development",
"id": 96,
"rationale": "Building interactive web user interfaces with React.js, including component composition, state management, hooks, and rendering patterns. React.js belongs here because it is a core library for client-side UI development in modern web applications.",
"slug": "d_init_01",
"source": "db"
},
"input_skill": "WebRTC",
"llm_role": null,
"roles_from_db": []
}
],
"input_skill": "WebRTC",
"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": "MySQL",
"alias_type": "CANONICAL",
"id": 134,
"is_primary": true,
"match_strategy": "CASE_INSENSITIVE"
}
],
"canonical": {
"category_id": 3,
"display_name": "MySQL",
"id": 17,
"is_also_category": false,
"is_extractable": true,
"skill_nature": "TOOL",
"slug": "mysql",
"sub_category_id": 29,
"typical_lifespan": "EVERGREEN",
"volatility": "STABLE"
},
"dimensions": [
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Relational Data Modeling",
"id": 216,
"rationale": "Modeling and tuning relational persistence for backend features. PHP backend developers need this to shape schemas, indexes, transactions, and query-aware data structures that support application behavior.",
"slug": "relational-data-modeling",
"source": "db"
},
"input_skill": "MySQL",
"llm_role": null,
"roles_from_db": [
{
"display_name": "Fullstack Developer",
"id": 15,
"rationale": null,
"role_archetype": null,
"slug": "full-stack-engineer",
"source": "db"
},
{
"display_name": "Fullstack Developer",
"id": 435,
"rationale": null,
"role_archetype": "Engineering",
"slug": "fullstack-developer",
"source": "db"
},
{
"display_name": "PHP Backend Developer",
"id": 86,
"rationale": null,
"role_archetype": "Engineering",
"slug": "php-backend-developer",
"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": "MySQL",
"llm_role": null,
"roles_from_db": [
{
"display_name": ".NET Backend Developer",
"id": 83,
"rationale": null,
"role_archetype": "Engineering",
"slug": "dotnet-backend-developer",
"source": "db"
},
{
"display_name": "Backend Developer",
"id": 1,
"rationale": null,
"role_archetype": "A Backend Engineer designs, builds, and maintains the server-side logic and data handling that power applications and services. They focus on implementing reliable business functionality, integrating with other systems, and ensuring the backend is scalable, maintainable, and observable.",
"slug": "backend-engineer",
"source": "db"
},
{
"display_name": "Kotlin Backend Developer",
"id": 84,
"rationale": null,
"role_archetype": "Engineering",
"slug": "kotlin-server-backend-developer",
"source": "db"
},
{
"display_name": "Node.js Backend Developer",
"id": 82,
"rationale": null,
"role_archetype": "Engineering",
"slug": "node-backend-developer",
"source": "db"
},
{
"display_name": "Python Backend Developer",
"id": 80,
"rationale": null,
"role_archetype": "Engineering",
"slug": "python-backend-developer",
"source": "db"
},
{
"display_name": "Ruby Backend Developer",
"id": 85,
"rationale": null,
"role_archetype": "Engineering",
"slug": "ruby-backend-developer",
"source": "db"
},
{
"display_name": "Scala Backend Developer",
"id": 87,
"rationale": null,
"role_archetype": "Engineering",
"slug": "scala-backend-developer",
"source": "db"
}
]
},
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Relational Database Usage",
"id": 371,
"rationale": "Working effectively with operational relational databases from Go backend services. This includes schema-aware querying, indexing awareness, transactions, and understanding how service code interacts with PostgreSQL or similar systems.",
"slug": "relational-database-usage",
"source": "db"
},
"input_skill": "MySQL",
"llm_role": null,
"roles_from_db": [
{
"display_name": "Go Backend Developer",
"id": 81,
"rationale": null,
"role_archetype": "Engineering",
"slug": "go-backend-developer",
"source": "db"
}
]
}
],
"input_skill": "MySQL",
"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": "Redis",
"alias_type": "CANONICAL",
"id": 168,
"is_primary": true,
"match_strategy": "CASE_INSENSITIVE"
}
],
"canonical": {
"category_id": 3,
"display_name": "Redis",
"id": 31,
"is_also_category": false,
"is_extractable": true,
"skill_nature": "TOOL",
"slug": "redis",
"sub_category_id": 28,
"typical_lifespan": "EVERGREEN",
"volatility": "STABLE"
},
"dimensions": [
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Caching and State Management",
"id": 7,
"rationale": "Techniques and systems for reducing latency and managing ephemeral backend state. Covers cache-aside patterns, distributed caches, session stores, and invalidation strategies.",
"slug": "caching-and-state-management",
"source": "db"
},
"input_skill": "Redis",
"llm_role": null,
"roles_from_db": [
{
"display_name": ".NET Backend Developer",
"id": 83,
"rationale": null,
"role_archetype": "Engineering",
"slug": "dotnet-backend-developer",
"source": "db"
},
{
"display_name": "Backend Developer",
"id": 1,
"rationale": null,
"role_archetype": "A Backend Engineer designs, builds, and maintains the server-side logic and data handling that power applications and services. They focus on implementing reliable business functionality, integrating with other systems, and ensuring the backend is scalable, maintainable, and observable.",
"slug": "backend-engineer",
"source": "db"
},
{
"display_name": "Kotlin Backend Developer",
"id": 84,
"rationale": null,
"role_archetype": "Engineering",
"slug": "kotlin-server-backend-developer",
"source": "db"
},
{
"display_name": "Node.js Backend Developer",
"id": 82,
"rationale": null,
"role_archetype": "Engineering",
"slug": "node-backend-developer",
"source": "db"
},
{
"display_name": "PHP Backend Developer",
"id": 86,
"rationale": null,
"role_archetype": "Engineering",
"slug": "php-backend-developer",
"source": "db"
},
{
"display_name": "Python Backend Developer",
"id": 80,
"rationale": null,
"role_archetype": "Engineering",
"slug": "python-backend-developer",
"source": "db"
},
{
"display_name": "Ruby Backend Developer",
"id": 85,
"rationale": null,
"role_archetype": "Engineering",
"slug": "ruby-backend-developer",
"source": "db"
},
{
"display_name": "Scala Backend Developer",
"id": 87,
"rationale": null,
"role_archetype": "Engineering",
"slug": "scala-backend-developer",
"source": "db"
}
]
},
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Magento Caching and Performance",
"id": 404,
"rationale": "Performance tuning specific to Magento storefronts and their rendering pipeline. This includes cache layers, page generation costs, and practical optimizations that preserve upgradeability while improving shopper experience.",
"slug": "magento-caching-and-performance",
"source": "db"
},
"input_skill": "Redis",
"llm_role": null,
"roles_from_db": [
{
"display_name": "Magento Dev",
"id": 231,
"rationale": null,
"role_archetype": "Engineering",
"slug": "magento-dev",
"source": "db"
}
]
}
],
"input_skill": "Redis",
"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": "response caching",
"alias_type": "CANONICAL",
"id": 1921,
"is_primary": true,
"match_strategy": "CASE_INSENSITIVE"
}
],
"canonical": {
"category_id": 13,
"display_name": "response caching",
"id": 1285,
"is_also_category": false,
"is_extractable": true,
"skill_nature": "TOOL",
"slug": "response-caching",
"sub_category_id": 1010,
"typical_lifespan": "EVERGREEN",
"volatility": "STABLE"
},
"dimensions": [
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Latency and Cost Optimization",
"id": 205,
"rationale": "Techniques for making AI features fast and affordable enough for production use. This cluster is coherent because model choice, prompt length, caching, batching, and routing directly affect user experience and unit economics.",
"slug": "latency-and-cost-optimization",
"source": "db"
},
"input_skill": "Caching",
"llm_role": null,
"roles_from_db": [
{
"display_name": "AI Engineer",
"id": 13,
"rationale": null,
"role_archetype": null,
"slug": "ai-engineer",
"source": "db"
}
]
}
],
"input_skill": "Caching",
"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": [],
"canonical": null,
"dimensions": [],
"input_skill": "socket.io",
"matched_via": null,
"new_alias_persisted": false,
"new_alias_text": null,
"new_skill_meta": {
"derived": {
"category": "Web Frameworks",
"skill_nature": "TOOL",
"sub_category": "general",
"typical_lifespan": "MULTI_YEAR",
"version_strategy": "UNVERSIONED",
"volatility": "MEDIUM"
},
"enrichment": null,
"keep_log": [],
"locked_dimensions": [],
"merge_log": [],
"placed": null,
"relationships": null,
"skill_id": "socket-io",
"split_log": [],
"typed": null,
"warnings": []
},
"source_tag": "llm",
"was_in_llm_skills": true
},
{
"aliases_in_db": [],
"canonical": null,
"dimensions": [],
"input_skill": "Pusher",
"matched_via": null,
"new_alias_persisted": false,
"new_alias_text": null,
"new_skill_meta": {
"derived": {
"category": "Web Frameworks",
"skill_nature": "TOOL",
"sub_category": "general",
"typical_lifespan": "MULTI_YEAR",
"version_strategy": "UNVERSIONED",
"volatility": "MEDIUM"
},
"enrichment": null,
"keep_log": [],
"locked_dimensions": [],
"merge_log": [],
"placed": null,
"relationships": null,
"skill_id": "pusher",
"split_log": [],
"typed": null,
"warnings": []
},
"source_tag": "llm",
"was_in_llm_skills": true
},
{
"aliases_in_db": [
{
"alias_text": "SEO",
"alias_type": "CANONICAL",
"id": 2628,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
}
],
"canonical": {
"category_id": 37,
"display_name": "SEO",
"id": 1658,
"is_also_category": false,
"is_extractable": true,
"skill_nature": "CONCEPT",
"slug": "seo",
"sub_category_id": 1251,
"typical_lifespan": "EVERGREEN",
"volatility": "STABLE"
},
"dimensions": [
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "React Frontend Development",
"id": 96,
"rationale": "Building interactive web user interfaces with React.js, including component composition, state management, hooks, and rendering patterns. React.js belongs here because it is a core library for client-side UI development in modern web applications.",
"slug": "d_init_01",
"source": "db"
},
"input_skill": "SEO",
"llm_role": null,
"roles_from_db": []
}
],
"input_skill": "SEO",
"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": "OpenGraph",
"matched_via": null,
"new_alias_persisted": false,
"new_alias_text": null,
"new_skill_meta": {
"derived": {
"category": "Concepts",
"skill_nature": "CONCEPT",
"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": "opengraph",
"split_log": [],
"typed": null,
"warnings": []
},
"source_tag": "llm",
"was_in_llm_skills": true
},
{
"aliases_in_db": [],
"canonical": null,
"dimensions": [],
"input_skill": "Twitter Cards",
"matched_via": null,
"new_alias_persisted": false,
"new_alias_text": null,
"new_skill_meta": {
"derived": {
"category": "Concepts",
"skill_nature": "CONCEPT",
"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": "twitter-cards",
"split_log": [],
"typed": null,
"warnings": []
},
"source_tag": "llm",
"was_in_llm_skills": true
},
{
"aliases_in_db": [],
"canonical": null,
"dimensions": [],
"input_skill": "Structured Data",
"matched_via": null,
"new_alias_persisted": false,
"new_alias_text": null,
"new_skill_meta": {
"derived": {
"category": "Concepts",
"skill_nature": "CONCEPT",
"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": "structured-data",
"split_log": [],
"typed": null,
"warnings": []
},
"source_tag": "llm",
"was_in_llm_skills": true
},
{
"aliases_in_db": [
{
"alias_text": "React 0.1",
"alias_type": "VERSION",
"id": 862,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "React 0.10",
"alias_type": "VERSION",
"id": 853,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "React 0.11",
"alias_type": "VERSION",
"id": 852,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "React 0.12",
"alias_type": "VERSION",
"id": 851,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "React 0.13",
"alias_type": "VERSION",
"id": 850,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "React 0.14",
"alias_type": "VERSION",
"id": 849,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "React 0.2",
"alias_type": "VERSION",
"id": 861,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "React 0.3",
"alias_type": "VERSION",
"id": 860,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "React 0.4",
"alias_type": "VERSION",
"id": 859,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "React 0.5",
"alias_type": "VERSION",
"id": 858,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "React 0.6",
"alias_type": "VERSION",
"id": 857,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "React 0.7",
"alias_type": "VERSION",
"id": 856,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "React 0.8",
"alias_type": "VERSION",
"id": 855,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "React 0.9",
"alias_type": "VERSION",
"id": 854,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "React 15",
"alias_type": "VERSION",
"id": 847,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "React 16",
"alias_type": "VERSION",
"id": 845,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "React 17",
"alias_type": "VERSION",
"id": 843,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "React 18",
"alias_type": "VERSION",
"id": 841,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "React.js",
"alias_type": "CANONICAL",
"id": 840,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "React.js 15",
"alias_type": "VERSION",
"id": 848,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "React.js 16",
"alias_type": "VERSION",
"id": 846,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "React.js 17",
"alias_type": "VERSION",
"id": 844,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "React.js 18",
"alias_type": "VERSION",
"id": 842,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
}
],
"canonical": {
"category_id": 5,
"display_name": "React.js",
"id": 514,
"is_also_category": false,
"is_extractable": true,
"skill_nature": "FRAMEWORK",
"slug": "react-js",
"sub_category_id": 363,
"typical_lifespan": "EVERGREEN",
"volatility": "STABLE"
},
"dimensions": [
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "React Frontend Development",
"id": 96,
"rationale": "Building interactive web user interfaces with React.js, including component composition, state management, hooks, and rendering patterns. React.js belongs here because it is a core library for client-side UI development in modern web applications.",
"slug": "d_init_01",
"source": "db"
},
"input_skill": "React.js",
"llm_role": null,
"roles_from_db": []
}
],
"input_skill": "React.js",
"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": "Vue.js",
"alias_type": "CANONICAL",
"id": 4689,
"is_primary": true,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "vue",
"alias_type": "VERSION",
"id": 4690,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "vue 2",
"alias_type": "VERSION",
"id": 4693,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "vue 2.x",
"alias_type": "VERSION",
"id": 4696,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "vue 3",
"alias_type": "VERSION",
"id": 4694,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "vue.js 2",
"alias_type": "VERSION",
"id": 4699,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "vue.js 3",
"alias_type": "VERSION",
"id": 4700,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "vue.js2",
"alias_type": "VERSION",
"id": 4697,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "vue2",
"alias_type": "VERSION",
"id": 4691,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "vue2.x",
"alias_type": "VERSION",
"id": 4695,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "vue3",
"alias_type": "VERSION",
"id": 4692,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "vuejs 3",
"alias_type": "VERSION",
"id": 4698,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
}
],
"canonical": {
"category_id": 5,
"display_name": "Vue.js",
"id": 3201,
"is_also_category": false,
"is_extractable": true,
"skill_nature": "FRAMEWORK",
"slug": "vue-js",
"sub_category_id": 1072,
"typical_lifespan": "EVERGREEN",
"volatility": "STABLE"
},
"dimensions": [
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Frameworks \u0026 Libraries",
"id": 360,
"rationale": "The PHP frameworks and JavaScript libraries commonly employed within Drupal projects for building features and integrations.",
"slug": "frameworks-libraries",
"source": "db"
},
"input_skill": "Vue.js",
"llm_role": null,
"roles_from_db": [
{
"display_name": "Drupal Dev",
"id": 228,
"rationale": null,
"role_archetype": "Engineering",
"slug": "drupal-dev",
"source": "db"
}
]
}
],
"input_skill": "Vue.js",
"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": "OAuth",
"alias_type": "CANONICAL",
"id": 5768,
"is_primary": true,
"match_strategy": "CASE_INSENSITIVE"
}
],
"canonical": {
"category_id": 10,
"display_name": "OAuth",
"id": 4066,
"is_also_category": false,
"is_extractable": true,
"skill_nature": "PROTOCOL",
"slug": "oauth",
"sub_category_id": 50,
"typical_lifespan": "EVERGREEN",
"volatility": "STABLE"
},
"dimensions": [
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Shopify APIs and Webhooks",
"id": 427,
"rationale": "Integration work that connects storefronts and apps to external business systems through Shopify interfaces. This cluster is central because Shopify Dev often wires store behavior to inventory, ERP, CRM, and fulfillment systems.",
"slug": "shopify-apis-and-webhooks",
"source": "db"
},
"input_skill": "OAuth",
"llm_role": null,
"roles_from_db": [
{
"display_name": "Shopify Dev",
"id": 230,
"rationale": null,
"role_archetype": "Engineering",
"slug": "shopify-dev",
"source": "db"
}
]
}
],
"input_skill": "OAuth",
"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": "JWT",
"alias_type": "CANONICAL",
"id": 165,
"is_primary": true,
"match_strategy": "CASE_INSENSITIVE"
}
],
"canonical": {
"category_id": 4,
"display_name": "JWT",
"id": 28,
"is_also_category": false,
"is_extractable": true,
"skill_nature": "STANDARD",
"slug": "jwt",
"sub_category_id": 33,
"typical_lifespan": "EVERGREEN",
"volatility": "STABLE"
},
"dimensions": [
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Authentication and Authorization",
"id": 6,
"rationale": "Identity, session, and access-control mechanisms used to protect PHP backend resources. This includes login flows, token handling, role checks, permissions, and policy enforcement in server-side code.",
"slug": "authentication-and-authorization",
"source": "db"
},
"input_skill": "JWT",
"llm_role": null,
"roles_from_db": [
{
"display_name": ".NET Backend Developer",
"id": 83,
"rationale": null,
"role_archetype": "Engineering",
"slug": "dotnet-backend-developer",
"source": "db"
},
{
"display_name": "Backend Developer",
"id": 1,
"rationale": null,
"role_archetype": "A Backend Engineer designs, builds, and maintains the server-side logic and data handling that power applications and services. They focus on implementing reliable business functionality, integrating with other systems, and ensuring the backend is scalable, maintainable, and observable.",
"slug": "backend-engineer",
"source": "db"
},
{
"display_name": "Go Backend Developer",
"id": 81,
"rationale": null,
"role_archetype": "Engineering",
"slug": "go-backend-developer",
"source": "db"
},
{
"display_name": "Java Backend Developer",
"id": 79,
"rationale": null,
"role_archetype": "Engineering",
"slug": "java-backend-developer",
"source": "db"
},
{
"display_name": "Node.js Backend Developer",
"id": 82,
"rationale": null,
"role_archetype": "Engineering",
"slug": "node-backend-developer",
"source": "db"
},
{
"display_name": "PHP Backend Developer",
"id": 86,
"rationale": null,
"role_archetype": "Engineering",
"slug": "php-backend-developer",
"source": "db"
},
{
"display_name": "Python Backend Developer",
"id": 80,
"rationale": null,
"role_archetype": "Engineering",
"slug": "python-backend-developer",
"source": "db"
}
]
},
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Authentication and Session Handling",
"id": 86,
"rationale": "Client-side identity flows and secure session management used to sign users in and keep them authenticated. This includes token handling, login UX, and protecting secrets on device.",
"slug": "authentication-and-session-handling",
"source": "db"
},
"input_skill": "JWT",
"llm_role": null,
"roles_from_db": [
{
"display_name": "Android Developer",
"id": 4,
"rationale": null,
"role_archetype": null,
"slug": "android-engineer",
"source": "db"
},
{
"display_name": "Frontend Developer",
"id": 7,
"rationale": null,
"role_archetype": null,
"slug": "frontend-engineer",
"source": "db"
},
{
"display_name": "Fullstack Developer",
"id": 15,
"rationale": null,
"role_archetype": null,
"slug": "full-stack-engineer",
"source": "db"
},
{
"display_name": "Hybrid Mobile Developer",
"id": 11,
"rationale": null,
"role_archetype": null,
"slug": "hybrid-mobile-developer",
"source": "db"
},
{
"display_name": "Ionic Developer",
"id": 434,
"rationale": null,
"role_archetype": null,
"slug": "ionic-developer",
"source": "db"
},
{
"display_name": "Native Mobile Developer",
"id": 75,
"rationale": null,
"role_archetype": "Engineering",
"slug": "native-mobile-developer",
"source": "db"
},
{
"display_name": "Web Developer",
"id": 25,
"rationale": null,
"role_archetype": null,
"slug": "web-developer",
"source": "db"
},
{
"display_name": "iOS Developer",
"id": 6,
"rationale": null,
"role_archetype": null,
"slug": "ios-engineer",
"source": "db"
}
]
},
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Backend Authentication and Authorization",
"id": 386,
"rationale": "Identity and access control mechanisms used by backend services to authenticate users or clients and enforce permissions on protected resources. This includes token and session handling, OAuth 2.0 / OpenID Connect / SAML flows, JWT and access tokens, API keys, MFA, role- or claim-based authorization, RBAC/ABAC, scopes, policies, Spring Security, and authorization filters.",
"slug": "backend-authentication-and-authorization",
"source": "db"
},
"input_skill": "JWT",
"llm_role": null,
"roles_from_db": [
{
"display_name": "Kotlin Backend Developer",
"id": 84,
"rationale": null,
"role_archetype": "Engineering",
"slug": "kotlin-server-backend-developer",
"source": "db"
},
{
"display_name": "Ruby Backend Developer",
"id": 85,
"rationale": null,
"role_archetype": "Engineering",
"slug": "ruby-backend-developer",
"source": "db"
},
{
"display_name": "Scala Backend Developer",
"id": 87,
"rationale": null,
"role_archetype": "Engineering",
"slug": "scala-backend-developer",
"source": "db"
}
]
},
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Frontend Authentication and Session Management",
"id": 300,
"rationale": "Client-side authentication and session management for frontend applications, including sign-in flows, OAuth 2.0/OpenID Connect/SSO integration, JWT and refresh token handling, login forms, protected routes, session persistence, and session-expiry user experience. This covers the user-facing parts of identity workflows implemented in React or other frontend stacks, but excludes identity provider administration, backend authorization policy, secret storage on servers, and MFA device management.",
"slug": "frontend-authentication-and-session-management",
"source": "db"
},
"input_skill": "JWT",
"llm_role": null,
"roles_from_db": [
{
"display_name": "React Frontend Developer",
"id": 89,
"rationale": null,
"role_archetype": "Engineering",
"slug": "react-frontend-developer",
"source": "db"
},
{
"display_name": "Svelte Frontend Developer",
"id": 92,
"rationale": null,
"role_archetype": "Engineering",
"slug": "svelte-frontend-developer",
"source": "db"
},
{
"display_name": "Vue Frontend Developer",
"id": 91,
"rationale": null,
"role_archetype": "Engineering",
"slug": "vue-frontend-developer",
"source": "db"
}
]
}
],
"input_skill": "JWT",
"matched_via": "alias",
"new_alias_persisted": false,
"new_alias_text": null,
"new_skill_meta": null,
"source_tag": "db",
"was_in_llm_skills": true
}
],
"unmatched_skills": [
"API Development",
"socket.io",
"Pusher",
"OpenGraph",
"Twitter Cards",
"Structured Data"
]
}
API 3 — final-role-output
{
"chosen_role": {
"display_name": "Web Developer",
"id": 25,
"rationale": "Multi-alias tie (4 roles at 1.0) resolved by TIER_B_TITLE: Web Developer",
"role_archetype": null,
"slug": "web-developer",
"source": "db"
},
"chosen_role_resolution": "in_db",
"final_input_skills": [
{
"skill": "Laravel",
"tag": "in_db"
},
{
"skill": "REST",
"tag": "in_db"
},
{
"skill": "API Development",
"tag": "new"
},
{
"skill": "Webhooks",
"tag": "in_db"
},
{
"skill": "WebRTC",
"tag": "in_db"
},
{
"skill": "MySQL",
"tag": "in_db"
},
{
"skill": "Redis",
"tag": "in_db"
},
{
"skill": "Caching",
"tag": "in_db"
},
{
"skill": "socket.io",
"tag": "new"
},
{
"skill": "Pusher",
"tag": "new"
},
{
"skill": "SEO",
"tag": "in_db"
},
{
"skill": "OpenGraph",
"tag": "new"
},
{
"skill": "Twitter Cards",
"tag": "new"
},
{
"skill": "Structured Data",
"tag": "new"
},
{
"skill": "React.js",
"tag": "in_db"
},
{
"skill": "Vue.js",
"tag": "in_db"
},
{
"skill": "OAuth",
"tag": "in_db"
},
{
"skill": "JWT",
"tag": "in_db"
}
],
"llm_cost_api1_usd": null,
"llm_cost_api2_usd": null,
"llm_cost_api3_usd": null,
"llm_cost_total_usd": null,
"persistence": {
"items": [
{
"chosen_role_id": 25,
"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": "Laravel",
"llm_role": null,
"matched_chosen_role": false,
"outcome_line": "Existing dimension (library) \u00b7 Role\u2194dimension skipped (dimension not under chosen role)",
"role_dimension_saved": false,
"roles_from_db": [
{
"display_name": "Backend Developer",
"id": 1,
"rationale": null,
"role_archetype": "A Backend Engineer designs, builds, and maintains the server-side logic and data handling that power applications and services. They focus on implementing reliable business functionality, integrating with other systems, and ensuring the backend is scalable, maintainable, and observable.",
"slug": "backend-engineer",
"source": "db"
},
{
"display_name": "Fullstack Developer",
"id": 15,
"rationale": null,
"role_archetype": null,
"slug": "full-stack-engineer",
"source": "db"
},
{
"display_name": "Fullstack Developer",
"id": 435,
"rationale": null,
"role_archetype": "Engineering",
"slug": "fullstack-developer",
"source": "db"
},
{
"display_name": "Java Backend Developer",
"id": 79,
"rationale": null,
"role_archetype": "Engineering",
"slug": "java-backend-developer",
"source": "db"
},
{
"display_name": "Node.js Backend Developer",
"id": 82,
"rationale": null,
"role_archetype": "Engineering",
"slug": "node-backend-developer",
"source": "db"
},
{
"display_name": "PHP Backend Developer",
"id": 86,
"rationale": null,
"role_archetype": "Engineering",
"slug": "php-backend-developer",
"source": "db"
},
{
"display_name": "Python Backend Developer",
"id": 80,
"rationale": null,
"role_archetype": "Engineering",
"slug": "python-backend-developer",
"source": "db"
}
],
"skill_dimension_saved": true,
"skill_id": 3798,
"skill_tag": "in_db",
"skipped_reason": null
},
{
"chosen_role_id": 25,
"dimension": {
"difficulty_hint": "well_known",
"display_name": "API Design and Contracts",
"id": 3,
"rationale": "Designing request/response shapes and the rules that govern client-server interaction. This cluster is coherent because full stack engineers often own the contract between UI behavior and backend implementation.",
"slug": "api-design-and-contracts",
"source": "db"
},
"dimension_id": 3,
"input_skill": "REST",
"llm_role": null,
"matched_chosen_role": false,
"outcome_line": "Existing dimension (library) \u00b7 Role\u2194dimension skipped (dimension not under chosen role)",
"role_dimension_saved": false,
"roles_from_db": [
{
"display_name": "Backend Developer",
"id": 1,
"rationale": null,
"role_archetype": "A Backend Engineer designs, builds, and maintains the server-side logic and data handling that power applications and services. They focus on implementing reliable business functionality, integrating with other systems, and ensuring the backend is scalable, maintainable, and observable.",
"slug": "backend-engineer",
"source": "db"
},
{
"display_name": "Fullstack Developer",
"id": 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": 25,
"dimension": {
"difficulty_hint": "well_known",
"display_name": "API Interface and Contract Design",
"id": 289,
"rationale": "Designing backend service interfaces and contracts that other systems consume, including endpoint and operation shape, request/response payloads, schema and validation, pagination, filtering, idempotency, versioning, status codes, and backward compatibility across REST, GraphQL, gRPC, and OpenAPI-based APIs.",
"slug": "api-interface-and-contract-design",
"source": "db"
},
"dimension_id": 289,
"input_skill": "REST",
"llm_role": null,
"matched_chosen_role": false,
"outcome_line": "Existing dimension (library) \u00b7 Role\u2194dimension skipped (dimension not under chosen role)",
"role_dimension_saved": false,
"roles_from_db": [
{
"display_name": ".NET Backend Developer",
"id": 83,
"rationale": null,
"role_archetype": "Engineering",
"slug": "dotnet-backend-developer",
"source": "db"
},
{
"display_name": "Go Backend Developer",
"id": 81,
"rationale": null,
"role_archetype": "Engineering",
"slug": "go-backend-developer",
"source": "db"
},
{
"display_name": "Kotlin Backend Developer",
"id": 84,
"rationale": null,
"role_archetype": "Engineering",
"slug": "kotlin-server-backend-developer",
"source": "db"
},
{
"display_name": "Node.js Backend Developer",
"id": 82,
"rationale": null,
"role_archetype": "Engineering",
"slug": "node-backend-developer",
"source": "db"
},
{
"display_name": "PHP Backend Developer",
"id": 86,
"rationale": null,
"role_archetype": "Engineering",
"slug": "php-backend-developer",
"source": "db"
},
{
"display_name": "Python Backend Developer",
"id": 80,
"rationale": null,
"role_archetype": "Engineering",
"slug": "python-backend-developer",
"source": "db"
},
{
"display_name": "Ruby Backend Developer",
"id": 85,
"rationale": null,
"role_archetype": "Engineering",
"slug": "ruby-backend-developer",
"source": "db"
},
{
"display_name": "Scala Backend Developer",
"id": 87,
"rationale": null,
"role_archetype": "Engineering",
"slug": "scala-backend-developer",
"source": "db"
}
],
"skill_dimension_saved": true,
"skill_id": 11,
"skill_tag": "in_db",
"skipped_reason": null
},
{
"chosen_role_id": 25,
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Integration Protocols \u0026 Standards",
"id": 271,
"rationale": "Standards and protocols for integrating Pega applications.",
"slug": "integration-protocols-standards",
"source": "db"
},
"dimension_id": 271,
"input_skill": "REST",
"llm_role": null,
"matched_chosen_role": false,
"outcome_line": "Existing dimension (library) \u00b7 Role\u2194dimension skipped (dimension not under chosen role)",
"role_dimension_saved": false,
"roles_from_db": [
{
"display_name": "Pega Developer",
"id": 24,
"rationale": null,
"role_archetype": null,
"slug": "pega-developer",
"source": "db"
}
],
"skill_dimension_saved": true,
"skill_id": 11,
"skill_tag": "in_db",
"skipped_reason": null
},
{
"chosen_role_id": 25,
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Standards \u0026 Protocols Compliance",
"id": 452,
"rationale": "Encompasses key web and data standards, protocols, and compliance requirements relevant to Sitecore implementations.",
"slug": "standards-protocols-compliance",
"source": "db"
},
"dimension_id": 452,
"input_skill": "REST",
"llm_role": null,
"matched_chosen_role": false,
"outcome_line": "Existing dimension (library) \u00b7 Role\u2194dimension skipped (dimension not under chosen role)",
"role_dimension_saved": false,
"roles_from_db": [
{
"display_name": "Sitecore Dev",
"id": 233,
"rationale": null,
"role_archetype": "Engineering",
"slug": "sitecore-dev",
"source": "db"
}
],
"skill_dimension_saved": true,
"skill_id": 11,
"skill_tag": "in_db",
"skipped_reason": null
},
{
"chosen_role_id": 25,
"dimension": {
"difficulty_hint": "well_known",
"display_name": "External Integrations and Clients",
"id": 375,
"rationale": "Connecting Go backend services to third-party APIs and internal enterprise systems. This cluster is coherent because the role frequently builds outbound clients, handles retries, and maps external payloads into service workflows.",
"slug": "external-integrations-and-clients",
"source": "db"
},
"dimension_id": 375,
"input_skill": "Webhooks",
"llm_role": null,
"matched_chosen_role": false,
"outcome_line": "Existing dimension (library) \u00b7 Role\u2194dimension skipped (dimension not under chosen role)",
"role_dimension_saved": false,
"roles_from_db": [
{
"display_name": "Go Backend Developer",
"id": 81,
"rationale": null,
"role_archetype": "Engineering",
"slug": "go-backend-developer",
"source": "db"
}
],
"skill_dimension_saved": true,
"skill_id": 2243,
"skill_tag": "in_db",
"skipped_reason": null
},
{
"chosen_role_id": 25,
"dimension": {
"difficulty_hint": "well_known",
"display_name": "External System Integrations",
"id": 14,
"rationale": "Connecting backend services to third-party APIs and internal enterprise systems. This includes client libraries, webhooks, retries, data mapping, and integration failure handling.",
"slug": "external-system-integrations",
"source": "db"
},
"dimension_id": 14,
"input_skill": "Webhooks",
"llm_role": null,
"matched_chosen_role": false,
"outcome_line": "Existing dimension (library) \u00b7 Role\u2194dimension skipped (dimension not under chosen role)",
"role_dimension_saved": false,
"roles_from_db": [
{
"display_name": ".NET Backend Developer",
"id": 83,
"rationale": null,
"role_archetype": "Engineering",
"slug": "dotnet-backend-developer",
"source": "db"
},
{
"display_name": "Backend Developer",
"id": 1,
"rationale": null,
"role_archetype": "A Backend Engineer designs, builds, and maintains the server-side logic and data handling that power applications and services. They focus on implementing reliable business functionality, integrating with other systems, and ensuring the backend is scalable, maintainable, and observable.",
"slug": "backend-engineer",
"source": "db"
},
{
"display_name": "Drupal Dev",
"id": 228,
"rationale": null,
"role_archetype": "Engineering",
"slug": "drupal-dev",
"source": "db"
},
{
"display_name": "Java Backend Developer",
"id": 79,
"rationale": null,
"role_archetype": "Engineering",
"slug": "java-backend-developer",
"source": "db"
},
{
"display_name": "Kotlin Backend Developer",
"id": 84,
"rationale": null,
"role_archetype": "Engineering",
"slug": "kotlin-server-backend-developer",
"source": "db"
},
{
"display_name": "Node.js Backend Developer",
"id": 82,
"rationale": null,
"role_archetype": "Engineering",
"slug": "node-backend-developer",
"source": "db"
},
{
"display_name": "PHP Backend Developer",
"id": 86,
"rationale": null,
"role_archetype": "Engineering",
"slug": "php-backend-developer",
"source": "db"
},
{
"display_name": "Python Backend Developer",
"id": 80,
"rationale": null,
"role_archetype": "Engineering",
"slug": "python-backend-developer",
"source": "db"
},
{
"display_name": "Ruby Backend Developer",
"id": 85,
"rationale": null,
"role_archetype": "Engineering",
"slug": "ruby-backend-developer",
"source": "db"
},
{
"display_name": "Scala Backend Developer",
"id": 87,
"rationale": null,
"role_archetype": "Engineering",
"slug": "scala-backend-developer",
"source": "db"
}
],
"skill_dimension_saved": true,
"skill_id": 2243,
"skill_tag": "in_db",
"skipped_reason": null
},
{
"chosen_role_id": 25,
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Magento Integration Adapters",
"id": 401,
"rationale": "Connecting Magento to external commerce systems and services. This cluster covers API clients, webhooks, message-driven adapters, and data mapping needed to synchronize storefront behavior with surrounding platforms.",
"slug": "magento-integration-adapters",
"source": "db"
},
"dimension_id": 401,
"input_skill": "Webhooks",
"llm_role": null,
"matched_chosen_role": false,
"outcome_line": "Existing dimension (library) \u00b7 Role\u2194dimension skipped (dimension not under chosen role)",
"role_dimension_saved": false,
"roles_from_db": [
{
"display_name": "Magento Dev",
"id": 231,
"rationale": null,
"role_archetype": "Engineering",
"slug": "magento-dev",
"source": "db"
}
],
"skill_dimension_saved": true,
"skill_id": 2243,
"skill_tag": "in_db",
"skipped_reason": null
},
{
"chosen_role_id": 25,
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Shopify APIs and Webhooks",
"id": 427,
"rationale": "Integration work that connects storefronts and apps to external business systems through Shopify interfaces. This cluster is central because Shopify Dev often wires store behavior to inventory, ERP, CRM, and fulfillment systems.",
"slug": "shopify-apis-and-webhooks",
"source": "db"
},
"dimension_id": 427,
"input_skill": "Webhooks",
"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": "Shopify Dev",
"id": 230,
"rationale": null,
"role_archetype": "Engineering",
"slug": "shopify-dev",
"source": "db"
}
],
"skill_dimension_saved": true,
"skill_id": 2243,
"skill_tag": "in_db",
"skipped_reason": null
},
{
"chosen_role_id": 25,
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Sitecore Integration Patterns",
"id": 444,
"rationale": "Connecting Sitecore to adjacent systems such as commerce, search, identity, analytics, and data services. This cluster covers the integration code and patterns needed to keep the site experience connected to enterprise systems.",
"slug": "sitecore-integration-patterns",
"source": "db"
},
"dimension_id": 444,
"input_skill": "Webhooks",
"llm_role": null,
"matched_chosen_role": false,
"outcome_line": "Existing dimension (library) \u00b7 Role\u2194dimension skipped (dimension not under chosen role)",
"role_dimension_saved": false,
"roles_from_db": [
{
"display_name": "Sitecore Dev",
"id": 233,
"rationale": null,
"role_archetype": "Engineering",
"slug": "sitecore-dev",
"source": "db"
}
],
"skill_dimension_saved": true,
"skill_id": 2243,
"skill_tag": "in_db",
"skipped_reason": null
},
{
"chosen_role_id": 25,
"dimension": {
"difficulty_hint": "well_known",
"display_name": "WordPress REST Integrations",
"id": 332,
"rationale": "Connecting WordPress sites to external services and internal systems through APIs and webhooks. This is a distinct cluster because WordPress developers frequently implement data exchange, sync, and integration behavior at the site layer.",
"slug": "wordpress-rest-integrations",
"source": "db"
},
"dimension_id": 332,
"input_skill": "Webhooks",
"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": "WordPress Dev",
"id": 227,
"rationale": null,
"role_archetype": "Engineering",
"slug": "wordpress-dev",
"source": "db"
}
],
"skill_dimension_saved": true,
"skill_id": 2243,
"skill_tag": "in_db",
"skipped_reason": null
},
{
"chosen_role_id": 25,
"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": "WebRTC",
"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": 1600,
"skill_tag": "in_db",
"skipped_reason": null
},
{
"chosen_role_id": 25,
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Relational Data Modeling",
"id": 216,
"rationale": "Modeling and tuning relational persistence for backend features. PHP backend developers need this to shape schemas, indexes, transactions, and query-aware data structures that support application behavior.",
"slug": "relational-data-modeling",
"source": "db"
},
"dimension_id": 216,
"input_skill": "MySQL",
"llm_role": null,
"matched_chosen_role": false,
"outcome_line": "Existing dimension (library) \u00b7 Role\u2194dimension skipped (dimension not under chosen role)",
"role_dimension_saved": false,
"roles_from_db": [
{
"display_name": "Fullstack Developer",
"id": 15,
"rationale": null,
"role_archetype": null,
"slug": "full-stack-engineer",
"source": "db"
},
{
"display_name": "Fullstack Developer",
"id": 435,
"rationale": null,
"role_archetype": "Engineering",
"slug": "fullstack-developer",
"source": "db"
},
{
"display_name": "PHP Backend Developer",
"id": 86,
"rationale": null,
"role_archetype": "Engineering",
"slug": "php-backend-developer",
"source": "db"
}
],
"skill_dimension_saved": true,
"skill_id": 17,
"skill_tag": "in_db",
"skipped_reason": null
},
{
"chosen_role_id": 25,
"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": "MySQL",
"llm_role": null,
"matched_chosen_role": false,
"outcome_line": "Existing dimension (library) \u00b7 Role\u2194dimension skipped (dimension not under chosen role)",
"role_dimension_saved": false,
"roles_from_db": [
{
"display_name": ".NET Backend Developer",
"id": 83,
"rationale": null,
"role_archetype": "Engineering",
"slug": "dotnet-backend-developer",
"source": "db"
},
{
"display_name": "Backend Developer",
"id": 1,
"rationale": null,
"role_archetype": "A Backend Engineer designs, builds, and maintains the server-side logic and data handling that power applications and services. They focus on implementing reliable business functionality, integrating with other systems, and ensuring the backend is scalable, maintainable, and observable.",
"slug": "backend-engineer",
"source": "db"
},
{
"display_name": "Kotlin Backend Developer",
"id": 84,
"rationale": null,
"role_archetype": "Engineering",
"slug": "kotlin-server-backend-developer",
"source": "db"
},
{
"display_name": "Node.js Backend Developer",
"id": 82,
"rationale": null,
"role_archetype": "Engineering",
"slug": "node-backend-developer",
"source": "db"
},
{
"display_name": "Python Backend Developer",
"id": 80,
"rationale": null,
"role_archetype": "Engineering",
"slug": "python-backend-developer",
"source": "db"
},
{
"display_name": "Ruby Backend Developer",
"id": 85,
"rationale": null,
"role_archetype": "Engineering",
"slug": "ruby-backend-developer",
"source": "db"
},
{
"display_name": "Scala Backend Developer",
"id": 87,
"rationale": null,
"role_archetype": "Engineering",
"slug": "scala-backend-developer",
"source": "db"
}
],
"skill_dimension_saved": true,
"skill_id": 17,
"skill_tag": "in_db",
"skipped_reason": null
},
{
"chosen_role_id": 25,
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Relational Database Usage",
"id": 371,
"rationale": "Working effectively with operational relational databases from Go backend services. This includes schema-aware querying, indexing awareness, transactions, and understanding how service code interacts with PostgreSQL or similar systems.",
"slug": "relational-database-usage",
"source": "db"
},
"dimension_id": 371,
"input_skill": "MySQL",
"llm_role": null,
"matched_chosen_role": false,
"outcome_line": "Existing dimension (library) \u00b7 Role\u2194dimension skipped (dimension not under chosen role)",
"role_dimension_saved": false,
"roles_from_db": [
{
"display_name": "Go Backend Developer",
"id": 81,
"rationale": null,
"role_archetype": "Engineering",
"slug": "go-backend-developer",
"source": "db"
}
],
"skill_dimension_saved": true,
"skill_id": 17,
"skill_tag": "in_db",
"skipped_reason": null
},
{
"chosen_role_id": 25,
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Caching and State Management",
"id": 7,
"rationale": "Techniques and systems for reducing latency and managing ephemeral backend state. Covers cache-aside patterns, distributed caches, session stores, and invalidation strategies.",
"slug": "caching-and-state-management",
"source": "db"
},
"dimension_id": 7,
"input_skill": "Redis",
"llm_role": null,
"matched_chosen_role": false,
"outcome_line": "Existing dimension (library) \u00b7 Role\u2194dimension skipped (dimension not under chosen role)",
"role_dimension_saved": false,
"roles_from_db": [
{
"display_name": ".NET Backend Developer",
"id": 83,
"rationale": null,
"role_archetype": "Engineering",
"slug": "dotnet-backend-developer",
"source": "db"
},
{
"display_name": "Backend Developer",
"id": 1,
"rationale": null,
"role_archetype": "A Backend Engineer designs, builds, and maintains the server-side logic and data handling that power applications and services. They focus on implementing reliable business functionality, integrating with other systems, and ensuring the backend is scalable, maintainable, and observable.",
"slug": "backend-engineer",
"source": "db"
},
{
"display_name": "Kotlin Backend Developer",
"id": 84,
"rationale": null,
"role_archetype": "Engineering",
"slug": "kotlin-server-backend-developer",
"source": "db"
},
{
"display_name": "Node.js Backend Developer",
"id": 82,
"rationale": null,
"role_archetype": "Engineering",
"slug": "node-backend-developer",
"source": "db"
},
{
"display_name": "PHP Backend Developer",
"id": 86,
"rationale": null,
"role_archetype": "Engineering",
"slug": "php-backend-developer",
"source": "db"
},
{
"display_name": "Python Backend Developer",
"id": 80,
"rationale": null,
"role_archetype": "Engineering",
"slug": "python-backend-developer",
"source": "db"
},
{
"display_name": "Ruby Backend Developer",
"id": 85,
"rationale": null,
"role_archetype": "Engineering",
"slug": "ruby-backend-developer",
"source": "db"
},
{
"display_name": "Scala Backend Developer",
"id": 87,
"rationale": null,
"role_archetype": "Engineering",
"slug": "scala-backend-developer",
"source": "db"
}
],
"skill_dimension_saved": true,
"skill_id": 31,
"skill_tag": "in_db",
"skipped_reason": null
},
{
"chosen_role_id": 25,
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Magento Caching and Performance",
"id": 404,
"rationale": "Performance tuning specific to Magento storefronts and their rendering pipeline. This includes cache layers, page generation costs, and practical optimizations that preserve upgradeability while improving shopper experience.",
"slug": "magento-caching-and-performance",
"source": "db"
},
"dimension_id": 404,
"input_skill": "Redis",
"llm_role": null,
"matched_chosen_role": false,
"outcome_line": "Existing dimension (library) \u00b7 Role\u2194dimension skipped (dimension not under chosen role)",
"role_dimension_saved": false,
"roles_from_db": [
{
"display_name": "Magento Dev",
"id": 231,
"rationale": null,
"role_archetype": "Engineering",
"slug": "magento-dev",
"source": "db"
}
],
"skill_dimension_saved": true,
"skill_id": 31,
"skill_tag": "in_db",
"skipped_reason": null
},
{
"chosen_role_id": 25,
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Latency and Cost Optimization",
"id": 205,
"rationale": "Techniques for making AI features fast and affordable enough for production use. This cluster is coherent because model choice, prompt length, caching, batching, and routing directly affect user experience and unit economics.",
"slug": "latency-and-cost-optimization",
"source": "db"
},
"dimension_id": 205,
"input_skill": "Caching",
"llm_role": null,
"matched_chosen_role": false,
"outcome_line": "Skipped \u2014 no persistable v3 meta for new skill",
"role_dimension_saved": false,
"roles_from_db": [
{
"display_name": "AI Engineer",
"id": 13,
"rationale": null,
"role_archetype": null,
"slug": "ai-engineer",
"source": "db"
}
],
"skill_dimension_saved": false,
"skill_id": null,
"skill_tag": "new",
"skipped_reason": "skill_not_in_db_v3_proposed"
},
{
"chosen_role_id": 25,
"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": "SEO",
"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": 1658,
"skill_tag": "in_db",
"skipped_reason": null
},
{
"chosen_role_id": 25,
"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": "React.js",
"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": 514,
"skill_tag": "in_db",
"skipped_reason": null
},
{
"chosen_role_id": 25,
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Frameworks \u0026 Libraries",
"id": 360,
"rationale": "The PHP frameworks and JavaScript libraries commonly employed within Drupal projects for building features and integrations.",
"slug": "frameworks-libraries",
"source": "db"
},
"dimension_id": 360,
"input_skill": "Vue.js",
"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": "Drupal Dev",
"id": 228,
"rationale": null,
"role_archetype": "Engineering",
"slug": "drupal-dev",
"source": "db"
}
],
"skill_dimension_saved": true,
"skill_id": 3201,
"skill_tag": "in_db",
"skipped_reason": null
},
{
"chosen_role_id": 25,
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Shopify APIs and Webhooks",
"id": 427,
"rationale": "Integration work that connects storefronts and apps to external business systems through Shopify interfaces. This cluster is central because Shopify Dev often wires store behavior to inventory, ERP, CRM, and fulfillment systems.",
"slug": "shopify-apis-and-webhooks",
"source": "db"
},
"dimension_id": 427,
"input_skill": "OAuth",
"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": "Shopify Dev",
"id": 230,
"rationale": null,
"role_archetype": "Engineering",
"slug": "shopify-dev",
"source": "db"
}
],
"skill_dimension_saved": true,
"skill_id": 4066,
"skill_tag": "in_db",
"skipped_reason": null
},
{
"chosen_role_id": 25,
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Authentication and Authorization",
"id": 6,
"rationale": "Identity, session, and access-control mechanisms used to protect PHP backend resources. This includes login flows, token handling, role checks, permissions, and policy enforcement in server-side code.",
"slug": "authentication-and-authorization",
"source": "db"
},
"dimension_id": 6,
"input_skill": "JWT",
"llm_role": null,
"matched_chosen_role": false,
"outcome_line": "Existing dimension (library) \u00b7 Role\u2194dimension skipped (dimension not under chosen role)",
"role_dimension_saved": false,
"roles_from_db": [
{
"display_name": ".NET Backend Developer",
"id": 83,
"rationale": null,
"role_archetype": "Engineering",
"slug": "dotnet-backend-developer",
"source": "db"
},
{
"display_name": "Backend Developer",
"id": 1,
"rationale": null,
"role_archetype": "A Backend Engineer designs, builds, and maintains the server-side logic and data handling that power applications and services. They focus on implementing reliable business functionality, integrating with other systems, and ensuring the backend is scalable, maintainable, and observable.",
"slug": "backend-engineer",
"source": "db"
},
{
"display_name": "Go Backend Developer",
"id": 81,
"rationale": null,
"role_archetype": "Engineering",
"slug": "go-backend-developer",
"source": "db"
},
{
"display_name": "Java Backend Developer",
"id": 79,
"rationale": null,
"role_archetype": "Engineering",
"slug": "java-backend-developer",
"source": "db"
},
{
"display_name": "Node.js Backend Developer",
"id": 82,
"rationale": null,
"role_archetype": "Engineering",
"slug": "node-backend-developer",
"source": "db"
},
{
"display_name": "PHP Backend Developer",
"id": 86,
"rationale": null,
"role_archetype": "Engineering",
"slug": "php-backend-developer",
"source": "db"
},
{
"display_name": "Python Backend Developer",
"id": 80,
"rationale": null,
"role_archetype": "Engineering",
"slug": "python-backend-developer",
"source": "db"
}
],
"skill_dimension_saved": true,
"skill_id": 28,
"skill_tag": "in_db",
"skipped_reason": null
},
{
"chosen_role_id": 25,
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Authentication and Session Handling",
"id": 86,
"rationale": "Client-side identity flows and secure session management used to sign users in and keep them authenticated. This includes token handling, login UX, and protecting secrets on device.",
"slug": "authentication-and-session-handling",
"source": "db"
},
"dimension_id": 86,
"input_skill": "JWT",
"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": "Android Developer",
"id": 4,
"rationale": null,
"role_archetype": null,
"slug": "android-engineer",
"source": "db"
},
{
"display_name": "Frontend Developer",
"id": 7,
"rationale": null,
"role_archetype": null,
"slug": "frontend-engineer",
"source": "db"
},
{
"display_name": "Fullstack Developer",
"id": 15,
"rationale": null,
"role_archetype": null,
"slug": "full-stack-engineer",
"source": "db"
},
{
"display_name": "Hybrid Mobile Developer",
"id": 11,
"rationale": null,
"role_archetype": null,
"slug": "hybrid-mobile-developer",
"source": "db"
},
{
"display_name": "Ionic Developer",
"id": 434,
"rationale": null,
"role_archetype": null,
"slug": "ionic-developer",
"source": "db"
},
{
"display_name": "Native Mobile Developer",
"id": 75,
"rationale": null,
"role_archetype": "Engineering",
"slug": "native-mobile-developer",
"source": "db"
},
{
"display_name": "Web Developer",
"id": 25,
"rationale": null,
"role_archetype": null,
"slug": "web-developer",
"source": "db"
},
{
"display_name": "iOS Developer",
"id": 6,
"rationale": null,
"role_archetype": null,
"slug": "ios-engineer",
"source": "db"
}
],
"skill_dimension_saved": true,
"skill_id": 28,
"skill_tag": "in_db",
"skipped_reason": null
},
{
"chosen_role_id": 25,
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Backend Authentication and Authorization",
"id": 386,
"rationale": "Identity and access control mechanisms used by backend services to authenticate users or clients and enforce permissions on protected resources. This includes token and session handling, OAuth 2.0 / OpenID Connect / SAML flows, JWT and access tokens, API keys, MFA, role- or claim-based authorization, RBAC/ABAC, scopes, policies, Spring Security, and authorization filters.",
"slug": "backend-authentication-and-authorization",
"source": "db"
},
"dimension_id": 386,
"input_skill": "JWT",
"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": "Kotlin Backend Developer",
"id": 84,
"rationale": null,
"role_archetype": "Engineering",
"slug": "kotlin-server-backend-developer",
"source": "db"
},
{
"display_name": "Ruby Backend Developer",
"id": 85,
"rationale": null,
"role_archetype": "Engineering",
"slug": "ruby-backend-developer",
"source": "db"
},
{
"display_name": "Scala Backend Developer",
"id": 87,
"rationale": null,
"role_archetype": "Engineering",
"slug": "scala-backend-developer",
"source": "db"
}
],
"skill_dimension_saved": true,
"skill_id": 28,
"skill_tag": "in_db",
"skipped_reason": null
},
{
"chosen_role_id": 25,
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Frontend Authentication and Session Management",
"id": 300,
"rationale": "Client-side authentication and session management for frontend applications, including sign-in flows, OAuth 2.0/OpenID Connect/SSO integration, JWT and refresh token handling, login forms, protected routes, session persistence, and session-expiry user experience. This covers the user-facing parts of identity workflows implemented in React or other frontend stacks, but excludes identity provider administration, backend authorization policy, secret storage on servers, and MFA device management.",
"slug": "frontend-authentication-and-session-management",
"source": "db"
},
"dimension_id": 300,
"input_skill": "JWT",
"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": "React Frontend Developer",
"id": 89,
"rationale": null,
"role_archetype": "Engineering",
"slug": "react-frontend-developer",
"source": "db"
},
{
"display_name": "Svelte Frontend Developer",
"id": 92,
"rationale": null,
"role_archetype": "Engineering",
"slug": "svelte-frontend-developer",
"source": "db"
},
{
"display_name": "Vue Frontend Developer",
"id": 91,
"rationale": null,
"role_archetype": "Engineering",
"slug": "vue-frontend-developer",
"source": "db"
}
],
"skill_dimension_saved": true,
"skill_id": 28,
"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": "08be24ac-5284-4a44-91f7-18094da63273"
}
LLM Calls
Every model call made for this run, in pipeline order. Click a card to see the model's response.