Pipeline run
4afaa014-842c-4908-a6ec-fc860ddc44d7
Client output enrichment
v2 Skill cluster · Nature of work · AI index · Tech stack maturity · Evidence · KRA descriptionvocab breakdown (legacy)
Signals
Post-classification
Captured for admin review
You will be the technical lead responsible for: • Implementing Insightly CRM pipelines, custom fields, automations, and API integrations • Designing and building a scalable middleware/API layer • Wor…
1 POST /skills/extract-from-jd
2 POST /skills/extract-details
3 POST /skills/final-role-output
Fullstack Developer
CASE Aslug: full-stack-engineer · id: 15 · source: db
Exact alias hit on full-stack-engineer (1.0) — no other alias at this confidence; skill_top full-stack-engineer 0.46 does not contradict
Resolution:
in_db
— role exists in library; skill↔dim and role↔dim links saved when applicable.
Job description
About Us: We are a dynamic and rapidly expanding residential solar installation business based in California, USA. Our mission is to make clean energy accessible to homeowners and accelerate the adoption of solar power throughout the United States. After bootstrapping our early growth, we are investing in the systems that will take us through our next stage. We're looking for a versatile, Lead full-stack developer(MERN) to help build and optimize the platforms that drive our business. This is an opportunity to join at the foundational stage of a multi-year transformation. Role Overview: You will be the technical lead responsible for: • Implementing Insightly CRM pipelines, custom fields, automations, and API integrations • Designing and building a scalable middleware/API layer • Working with operational heads to convert business processes into robust system workflows • Acting as the glue between CRM, web app, and external partner systems (dialers, financing providers, proposal management and scheduling tools, etc.) You will be an experienced, senior, hands-on engineer with architectural autonomy and significant influence over Lytegen's technology direction. This is a greenfield opportunity to help define the architecture, build core integrations, and ship real tools used daily by hundreds of internal and external users and would be ideal for an engineer who enjoys solving end-to-end business workflow problems, not just writing code. Key Responsibilities: CRM (Insightly) Implementation • Configure Insightly objects, pipelines, automations, and permissions • Build custom fields and structured workflows for leads, proposals, NTP, projects, permitting & installations • Set up and manage Insightly webhooks and API integrations • Optimize CRM usability for setters, schedulers, closers, and project teams Middleware / Integration Layer • Design system integrations between Insightly and external tools • Build REST APIs, background workers, webhooks, and syncing logic • Implement authentication, API rate-limit handling, and robust error logging • Set up a clean, maintainable architecture (Server less preferred) Collaboration + Product • Translate complex business workflows into technical designs • Participate in solution design workshops with US/UK stakeholders • Handle documentation, schema design, API contracts, and release planning • Assess technical feasibility, effort, and impact before implementation Skillset • Strong proficiency in full stack development (NOSQL, React or Next.js, Lambda) • Solid understanding of REST APIs, authentication, and integration patterns • Experience working with CRMs (Insightly preferred, Salesforce/HubSpot acceptable) • Strong debugging, performance optimization, and architectural skills • Cloud experience (AWS preferred) • Ability to understand sales workflows, operations processes, and multi-stage pipelines • Strong communication—clear documentation, structured thinking, and internal stakeholder coordination • Ability to convert ambiguous requirements into structured system designs Experience • 4 - 8 years of full-stack engineering experience • Must have delivered at least one end-to-end CRM or workflow automation project • Must have built API-driven backend services • Bonus: Experience in solar, field service, fintech, or operations-heavy businesses • Bonus: Experience with Insightly specifically (otherwise willingness to upskill quickly) Why Join Us? • Opportunity to make a significant impact in a rapidly growing company • A chance to design and own a mission-critical system from ground zero in a collaborative and supportive work environment. • Chance to work on cutting-edge greenfield projects and contribute to a sustainable future • Opportunity to grow your skills, advance your career, design and build a mission-critical system from ground zero
Skills from this JD
Each row merges API 1 extraction, API 2 library match / v3 orchestration (dimensions + locked dims), and API 3 persistence tags.
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
- CRM Platforms
- Sub-category
- general
- Skill nature
- PLATFORM
- 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
- STABLE
- Typical lifespan
- EVERGREEN
- Version strategy
- UNVERSIONED
Aliases — catalog
- API (CANONICAL)
Context tags (catalog)
Stored enrichment (catalog DB)
- Category
- Concept
- Sub-category
- Application Programming Interface
- Confidence
- 0.93
- Version strategy
- NOT_APPLICABLE
Maturity reasoning: APIs are a core requirement in most software engineering JDs and underpin common integrations across cloud, mobile, and web stacks; major vendors like AWS, Stripe, and Google Cloud center products on API-first usage.
Skill profile (library / DB)
- Skill nature
- CONCEPT
- Volatility
- STABLE
- Typical lifespan
- EVERGREEN
- Category id
- 2
- Sub-category id
- 1174
- Extractable
- True
- Also category
- False
Dimensions (API 2 worklist)
-
API Integration and Data Fetching Catalog dimension db id 127
Library dimension (catalog)
Roles linked in library: Angular Frontend Developer, Frontend Developer, Fullstack Developer, React Frontend Developer, Svelte Frontend Developer, Vue Frontend Developer, Web Developer
API 3 link attempts (this skill)
| Dimension | Skill↔dim | Role↔dim | Outcome |
|---|---|---|---|
|
API Integration and Data Fetching
api-integration-and-data-fetching
|
✓ | ✓ | Existing dimension (library) · Role↔dimension saved |
Aliases — catalog
- REST (CANONICAL) primary
Context tags (catalog)
Stored enrichment (catalog DB)
- Category
- Concept
- Sub-category
- Api Architecture Style
- Year introduced
- 2000
- Confidence
- 0.88
- Version strategy
- NOT_APPLICABLE
Maturity reasoning: REST is a default API architecture in many job descriptions and is widely supported by major vendors/frameworks; OpenAPI and RESTful endpoints remain standard in hiring pipelines.
Skill profile (library / DB)
- Skill nature
- CONCEPT
- Volatility
- STABLE
- Typical lifespan
- EVERGREEN
- Category id
- 2
- Sub-category id
- 2122
- Extractable
- True
- Also category
- False
Dimensions (API 2 worklist)
-
API Design and Contracts Catalog dimension db id 3
Library dimension (catalog)
Roles linked in library: Backend Developer, Fullstack Developer
-
API Interface and Contract Design Catalog dimension db id 289
Library dimension (catalog)
Roles linked in library: .NET Backend Developer, Go Backend Developer, Kotlin Backend Developer, Node.js Backend Developer, PHP Backend Developer, Python Backend Developer, Ruby Backend Developer, Scala Backend Developer
-
Integration Protocols & Standards Catalog dimension db id 271
Library dimension (catalog)
Roles linked in library: Pega Developer
-
Standards & Protocols Compliance Catalog dimension db id 452
Library dimension (catalog)
Roles linked in library: Sitecore Dev
API 3 link attempts (this skill)
| Dimension | Skill↔dim | Role↔dim | Outcome |
|---|---|---|---|
|
API Design and Contracts
api-design-and-contracts
|
✓ | ✓ | Existing dimension (library) · Role↔dimension saved |
|
API Interface and Contract Design
api-interface-and-contract-design
|
✓ | — | Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role) |
|
Integration Protocols & Standards
integration-protocols-standards
|
✓ | — | Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role) |
|
Standards & Protocols Compliance
standards-protocols-compliance
|
✓ | — | Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role) |
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
- React (CANONICAL) primary
- React 0.13 (VERSION)
- React 0.14 (VERSION)
- React 15 (VERSION)
- React 15.x (VERSION)
- React 16 (VERSION)
- React 16.x (VERSION)
- React 17 (VERSION)
- React 17.x (VERSION)
- React 18 (VERSION)
- React 18.x (VERSION)
- React 19 (VERSION)
- React v15 (VERSION)
- React v16 (VERSION)
- React v17 (VERSION)
- React v18 (VERSION)
- React v19 (VERSION)
- ReactJS 18 (VERSION)
- react 15 (VERSION)
- react 16 (VERSION)
- react 17 (VERSION)
- react 18 (VERSION)
- react 19 (VERSION)
- react15 (VERSION)
- react16 (VERSION)
- react17 (VERSION)
- react18 (VERSION)
- react19 (VERSION)
- reactjs 18 (VERSION)
Context tags (catalog)
Stored enrichment (catalog DB)
- Category
- Framework
- Sub-category
- Frontend Framework
- Vendor
- Meta
- License
- mit
- Year introduced
- 2013
- Confidence
- 0.98
- Version strategy
- SEPARATE_ENTITY
- Version tag
- 18
Maturity reasoning: React appears in high-volume frontend job postings across startups and enterprises and remains a default hiring-pipeline skill, with strong GitHub/npm usage and ecosystem activity.
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)
-
Application Frameworks & Libraries Catalog dimension db id 451
Library dimension (catalog)
Roles linked in library: Sitecore Dev
-
Frontend Frameworks and Libraries Catalog dimension db id 434
Library dimension (catalog)
Roles linked in library: Shopify Dev
-
JavaScript for WordPress Catalog dimension db id 329
Library dimension (catalog)
Roles linked in library: WordPress Dev
-
React Component Architecture Catalog dimension db id 302
Library dimension (catalog)
Roles linked in library: React Frontend Developer
-
UI Frameworks and Rendering Catalog dimension db id 115
Library dimension (catalog)
Roles linked in library: Frontend Developer, Fullstack Developer, Hybrid Mobile Developer, Ionic Developer, Web Developer
API 3 link attempts (this skill)
| Dimension | Skill↔dim | Role↔dim | Outcome |
|---|---|---|---|
|
Application Frameworks & Libraries
application-frameworks-libraries
|
✓ | — | Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role) |
|
Frontend Frameworks and Libraries
frontend-frameworks-and-libraries
|
✓ | — | Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role) |
|
JavaScript for WordPress
javascript-for-wordpress
|
✓ | — | Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role) |
|
React Component Architecture
react-component-architecture
|
✓ | — | Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role) |
|
UI Frameworks and Rendering
ui-frameworks-and-rendering
|
✓ | ✓ | Existing dimension (library) · Role↔dimension saved |
Aliases — catalog
- Next.js (CANONICAL) primary
- Next 10 (VERSION)
- Next 11 (VERSION)
- Next 12 (VERSION)
- Next 13 (VERSION)
- Next 14 (VERSION)
- Next 15 (VERSION)
- Next 2 (VERSION)
- Next 3 (VERSION)
- Next 4 (VERSION)
- Next 5 (VERSION)
- Next 6 (VERSION)
- Next 7 (VERSION)
- Next 8 (VERSION)
- Next 9 (VERSION)
- Next.js 1 (VERSION)
- Next.js 10 (VERSION)
- Next.js 11 (VERSION)
- Next.js 12 (VERSION)
- Next.js 13 (VERSION)
- Next.js 14 (VERSION)
- Next.js 15 (VERSION)
- Next.js 2 (VERSION)
- Next.js 3 (VERSION)
- Next.js 4 (VERSION)
- Next.js 5 (VERSION)
- Next.js 6 (VERSION)
- Next.js 7 (VERSION)
- Next.js 8 (VERSION)
- Next.js 9 (VERSION)
- next (VERSION)
- next.js (VERSION)
- next.js 14 (VERSION)
- nextjs (VERSION)
- nextjs 14 (VERSION)
Context tags (catalog)
Stored enrichment (catalog DB)
- Category
- Framework
- Sub-category
- Web Framework
- Vendor
- Vercel
- License
- mit
- Year introduced
- 2016
- Confidence
- 0.98
- Version strategy
- NOT_APPLICABLE
Maturity reasoning: Next.js appears in many frontend/full-stack job descriptions and is a common React meta-framework for production apps; Vercel’s ecosystem and strong GitHub adoption signal broad market demand.
Skill profile (library / DB)
- Skill nature
- FRAMEWORK
- Volatility
- STABLE
- Typical lifespan
- EVERGREEN
- Category id
- 5
- Sub-category id
- 35
- Extractable
- True
- Also category
- False
Dimensions (API 2 worklist)
-
Frontend Frameworks and Libraries Catalog dimension db id 434
Library dimension (catalog)
Roles linked in library: Shopify Dev
-
Meta-Frameworks & SSR Catalog dimension db id 130
Library dimension (catalog)
Roles linked in library: Frontend Developer, Web Developer
-
UI Frameworks and Rendering Catalog dimension db id 115
Library dimension (catalog)
Roles linked in library: Frontend Developer, Fullstack Developer, Hybrid Mobile Developer, Ionic Developer, Web Developer
API 3 link attempts (this skill)
| Dimension | Skill↔dim | Role↔dim | Outcome |
|---|---|---|---|
|
Frontend Frameworks and Libraries
frontend-frameworks-and-libraries
|
✓ | — | Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role) |
|
Meta-Frameworks & SSR
meta-frameworks-ssr
|
✓ | — | Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role) |
|
UI Frameworks and Rendering
ui-frameworks-and-rendering
|
✓ | ✓ | Existing dimension (library) · Role↔dimension saved |
Aliases — catalog
- AWS Lambda (CANONICAL) primary
Context tags (catalog)
Stored enrichment (catalog DB)
- Category
- Service
- Sub-category
- Serverless Function Service
- Vendor
- Amazon Web Services
- License
- other_open
- Year introduced
- 2014
- Confidence
- 0.98
- Version strategy
- NOT_APPLICABLE
Maturity reasoning: Broadly listed in cloud/backend JDs and AWS’s serverless docs/marketplace; it’s a standard hiring-pipeline skill for event-driven apps and APIs.
Skill profile (library / DB)
- Skill nature
- CLOUD_SERVICE
- Volatility
- STABLE
- Typical lifespan
- EVERGREEN
- Category id
- 11
- Sub-category id
- 1704
- Extractable
- True
- Also category
- False
Dimensions (API 2 worklist)
-
Cloud Platforms Catalog dimension db id 20
Library dimension (catalog)
Roles linked in library: .NET Backend Developer, Backend Developer, Cyber Security Engineer, Data Engineer, DevOps Engineer, Fullstack Developer, Go Backend Developer, Java Backend Developer, Kotlin Backend Developer, ML Engineer, MLOps Engineer, Node.js Backend Developer, Python Backend Developer, Scala Backend Developer
-
Cloud Platforms & Hosting Providers Catalog dimension db id 278
Library dimension (catalog)
Roles linked in library: .NET Backend Developer, Kotlin Backend Developer, Scala Backend Developer, Web Developer
-
Cloud Platforms & Managed Services Catalog dimension db id 221
Library dimension (catalog)
Roles linked in library: Fullstack Developer, Go Backend Developer, Node.js Backend Developer
-
Cloud Platforms & Services Catalog dimension db id 296
Library dimension (catalog)
Roles linked in library: Python Backend Developer
API 3 link attempts (this skill)
| Dimension | Skill↔dim | Role↔dim | Outcome |
|---|---|---|---|
|
Cloud Platforms
cloud-platforms
|
✓ | ✓ | Existing dimension (library) · Role↔dimension saved |
|
Cloud Platforms & Hosting Providers
cloud-platforms-hosting-providers
|
✓ | — | Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role) |
|
Cloud Platforms & Managed Services
cloud-platforms-managed-services
|
✓ | ✓ | Existing dimension (library) · Role↔dimension saved |
|
Cloud Platforms & Services
cloud-platforms-services
|
✓ | — | Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role) |
Aliases — catalog
- NoSQL (CANONICAL)
Context tags (catalog)
Stored enrichment (catalog DB)
- Category
- Concept
- Sub-category
- Database Paradigm
- Confidence
- 0.93
- Version strategy
- NOT_APPLICABLE
Maturity reasoning: NoSQL is broadly listed in job descriptions across backend/data roles, with MongoDB, DynamoDB, and Cassandra appearing as common market signals; it remains a hiring-pipeline staple rather than a niche or sunset tech.
Skill profile (library / DB)
- Skill nature
- CONCEPT
- Volatility
- STABLE
- Typical lifespan
- EVERGREEN
- Category id
- 2
- Sub-category id
- 1019
- Extractable
- True
- Also category
- False
Dimensions (API 2 worklist)
-
NoSQL Databases Catalog dimension db id 19
Library dimension (catalog)
Roles linked in library: Backend Developer
API 3 link attempts (this skill)
| Dimension | Skill↔dim | Role↔dim | Outcome |
|---|---|---|---|
|
NoSQL Databases
nosql-databases
|
✓ | — | Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role) |
Aliases — catalog
- Authentication (CANONICAL)
Context tags (catalog)
Stored enrichment (catalog DB)
- Category
- Concept
- Sub-category
- Authentication
- Confidence
- 0.96
- Version strategy
- NOT_APPLICABLE
Maturity reasoning: Authentication is a core requirement in most software JDs and security roles; it appears broadly across job postings and vendor docs for OAuth/OIDC, SSO, and MFA rather than as a niche specialty.
Skill profile (library / DB)
- Skill nature
- CONCEPT
- Volatility
- STABLE
- Typical lifespan
- EVERGREEN
- Category id
- 2
- Sub-category id
- 1211
- Extractable
- True
- Also category
- False
Dimensions (API 2 worklist)
-
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
API 3 link attempts (this skill)
| Dimension | Skill↔dim | Role↔dim | Outcome |
|---|---|---|---|
|
Authentication and Session Handling
authentication-and-session-handling
|
✓ | ✓ | Existing dimension (library) · Role↔dimension saved |
Aliases — catalog
- rate limiting (CANONICAL) primary
Context tags (catalog)
Stored enrichment (catalog DB)
- Category
- Concept
- Sub-category
- Traffic Throttling
- Confidence
- 0.88
- Version strategy
- NOT_APPLICABLE
Maturity reasoning: Common in API/backend JDs and cloud docs; vendors like AWS API Gateway, NGINX, and Kong all ship built-in rate-limiting features, showing broad hiring-market demand.
Skill profile (library / DB)
- Skill nature
- CONCEPT
- Volatility
- STABLE
- Typical lifespan
- EVERGREEN
- Category id
- 2
- Sub-category id
- 2522
- Extractable
- True
- Also category
- False
Dimensions (API 2 worklist)
-
Backend Security Hardening Catalog dimension db id 16
Library dimension (catalog)
Roles linked in library: .NET Backend Developer, Backend Developer, Java Backend Developer, Kotlin Backend Developer, Node.js Backend Developer, PHP Backend Developer, Python Backend Developer, Ruby Backend Developer, Scala Backend Developer
API 3 link attempts (this skill)
| Dimension | Skill↔dim | Role↔dim | Outcome |
|---|---|---|---|
|
Backend Security Hardening
backend-security-hardening
|
✓ | — | 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
- CRM Platforms
- Sub-category
- general
- Skill nature
- PLATFORM
- 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
- CRM Platforms
- Sub-category
- general
- Skill nature
- PLATFORM
- Volatility
- MEDIUM
- Typical lifespan
- MULTI_YEAR
- Version strategy
- UNVERSIONED
Aliases — catalog
- Serverless Framework (CANONICAL) primary
Context tags (catalog)
Stored enrichment (catalog DB)
- Category
- Framework
- Sub-category
- Infrastructure As Code Framework
- Vendor
- Serverless, Inc.
- License
- mit
- Year introduced
- 2015
- Confidence
- 0.95
- Version strategy
- NOT_APPLICABLE
Maturity reasoning: Commonly listed in cloud/IaC job descriptions for AWS Lambda deployments; strong GitHub usage and vendor ecosystem support indicate broad adoption, though often alongside newer tools like SST/CDK.
Skill profile (library / DB)
- Skill nature
- FRAMEWORK
- Volatility
- STABLE
- Typical lifespan
- EVERGREEN
- Category id
- 5
- Sub-category id
- 145
- Extractable
- True
- Also category
- False
Dimensions (API 2 worklist)
-
Infrastructure as Code Catalog dimension db id 132
Library dimension (catalog)
Roles linked in library: Cloud Architect, DevOps Engineer
API 3 link attempts (this skill)
| Dimension | Skill↔dim | Role↔dim | Outcome |
|---|---|---|---|
|
Infrastructure as Code
infrastructure-as-code
|
— | — |
Skipped — no persistable v3 meta for new skill
skill_not_in_db_v3_proposed
|
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 |
|---|---|---|---|---|---|---|
| API | in_db |
API Integration and Data Fetching
api-integration-and-data-fetching
|
✓ | ✓ | Existing dimension (library) · Role↔dimension saved | |
| REST | in_db |
API Design and Contracts
api-design-and-contracts
|
✓ | ✓ | Existing dimension (library) · Role↔dimension saved | |
| REST | in_db |
API Interface and Contract Design
api-interface-and-contract-design
|
✓ | — | Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role) | |
| REST | in_db |
Integration Protocols & Standards
integration-protocols-standards
|
✓ | — | Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role) | |
| REST | in_db |
Standards & Protocols Compliance
standards-protocols-compliance
|
✓ | — | Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role) | |
| 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) | |
| React | in_db |
Application Frameworks & Libraries
application-frameworks-libraries
|
✓ | — | Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role) | |
| React | in_db |
Frontend Frameworks and Libraries
frontend-frameworks-and-libraries
|
✓ | — | Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role) | |
| React | in_db |
JavaScript for WordPress
javascript-for-wordpress
|
✓ | — | Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role) | |
| React | in_db |
React Component Architecture
react-component-architecture
|
✓ | — | Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role) | |
| React | in_db |
UI Frameworks and Rendering
ui-frameworks-and-rendering
|
✓ | ✓ | Existing dimension (library) · Role↔dimension saved | |
| Next.js | in_db |
Frontend Frameworks and Libraries
frontend-frameworks-and-libraries
|
✓ | — | Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role) | |
| Next.js | in_db |
Meta-Frameworks & SSR
meta-frameworks-ssr
|
✓ | — | Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role) | |
| Next.js | in_db |
UI Frameworks and Rendering
ui-frameworks-and-rendering
|
✓ | ✓ | Existing dimension (library) · Role↔dimension saved | |
| AWS Lambda | in_db |
Cloud Platforms
cloud-platforms
|
✓ | ✓ | Existing dimension (library) · Role↔dimension saved | |
| AWS Lambda | in_db |
Cloud Platforms & Hosting Providers
cloud-platforms-hosting-providers
|
✓ | — | Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role) | |
| AWS Lambda | in_db |
Cloud Platforms & Managed Services
cloud-platforms-managed-services
|
✓ | ✓ | Existing dimension (library) · Role↔dimension saved | |
| AWS Lambda | in_db |
Cloud Platforms & Services
cloud-platforms-services
|
✓ | — | Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role) | |
| NoSQL | in_db |
NoSQL Databases
nosql-databases
|
✓ | — | Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role) | |
| Authentication | in_db |
Authentication and Session Handling
authentication-and-session-handling
|
✓ | ✓ | Existing dimension (library) · Role↔dimension saved | |
| Rate Limiting | in_db |
Backend Security Hardening
backend-security-hardening
|
✓ | — | Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role) | |
| Serverless | new |
Infrastructure as Code
infrastructure-as-code
|
— | — | Skipped — no persistable v3 meta for new skill | skill_not_in_db_v3_proposed |
Library artifacts (this run)
| Kind | Detail | DB id |
|---|---|---|
| canonical_skill_proposed | MERN | type=Web Frameworks subtype=general nature=TOOL lifespan=MULTI_YEAR | |
| canonical_skill_proposed | Insightly | type=CRM Platforms subtype=general nature=PLATFORM lifespan=MULTI_YEAR | |
| canonical_skill_proposed | CRM | type=Concepts subtype=general nature=CONCEPT lifespan=EVERGREEN | |
| canonical_skill_proposed | Background Workers | type=Concepts subtype=general nature=CONCEPT lifespan=MULTI_YEAR | |
| canonical_skill_proposed | Salesforce | type=CRM Platforms subtype=general nature=PLATFORM lifespan=MULTI_YEAR | |
| canonical_skill_proposed | HubSpot | type=CRM Platforms subtype=general nature=PLATFORM lifespan=MULTI_YEAR | |
| dimension_skill_link_proposed | Serverless ↔ Infrastructure as Code |
nano JD Parser — gpt-4.1-nano click to toggle
Show raw JSON
{
"JD_type": "pass",
"about_company": {
"source_marker": {
"first_5_words": "We are a dynamic and",
"last_5_words": "through our next stage."
},
"text": "We are a dynamic and rapidly expanding residential solar installation business based in California, USA. Our mission is to make clean energy accessible to homeowners and accelerate the adoption of solar power throughout the United States. After bootstrapping our early growth, we are investing in the systems that will take us through our next stage.",
"word_count": 64
},
"certifications": [],
"company_name": "Lytegen",
"ctc": null,
"domain": {
"primary": {
"aliases": [
"Solar",
"Clean Energy"
],
"domain": "Energy \u0026 Utilities"
},
"secondary": null
},
"education": [],
"experience": {
"max": 8,
"min": 4,
"raw": "4 - 8 years of full-stack engineering experience"
},
"job_locations": [],
"role": "Lead full-stack developer(MERN)",
"role_aliases": [
"Full Stack Developer",
"Lead Developer",
"MERN Developer"
],
"role_archetype": "Engineering",
"roles_and_responsibilities": [
{
"bullet_count": 4,
"heading": "Role Overview",
"heading_was_present": true,
"source_marker": {
"first_5_words": "You will be the technical",
"last_5_words": "not just writing code."
},
"text": "You will be the technical lead responsible for:\n\n\u2022 Implementing Insightly CRM pipelines, custom fields, automations, and API integrations\n\u2022 Designing and building a scalable middleware/API layer\n\u2022 Working with operational heads to convert business processes into robust system workflows\n\u2022 Acting as the glue between CRM, web app, and external partner systems (dialers, financing providers, proposal management and scheduling tools, etc.)\n\nYou will be an experienced, senior, hands-on engineer with architectural autonomy and significant influence over Lytegen\u0027s technology direction. This is a greenfield opportunity to help define the architecture, build core integrations, and ship real tools used daily by hundreds of internal and external users and would be ideal for an engineer who enjoys solving end-to-end business workflow problems, not just writing code.",
"word_count": 139
},
{
"bullet_count": 16,
"heading": "Key Responsibilities",
"heading_was_present": true,
"source_marker": {
"first_5_words": "CRM (Insightly) Implementation\n\n\u2022 Configure",
"last_5_words": "effort, and impact before implementation"
},
"text": "CRM (Insightly) Implementation\n\n\u2022 Configure Insightly objects, pipelines, automations, and permissions\n\u2022 Build custom fields and structured workflows for leads, proposals, NTP, projects, permitting \u0026 installations\n\u2022 Set up and manage Insightly webhooks and API integrations\n\u2022 Optimize CRM usability for setters, schedulers, closers, and project teams\n\nMiddleware / Integration Layer\n\n\u2022 Design system integrations between Insightly and external tools\n\u2022 Build REST APIs, background workers, webhooks, and syncing logic\n\u2022 Implement authentication, API rate-limit handling, and robust error logging\n\u2022 Set up a clean, maintainable architecture (Server less preferred)\n\nCollaboration + Product\n\n\u2022 Translate complex business workflows into technical designs\n\u2022 Participate in solution design workshops with US/UK stakeholders\n\u2022 Handle documentation, schema design, API contracts, and release planning\n\u2022 Assess technical feasibility, effort, and impact before implementation",
"word_count": 218
},
{
"bullet_count": 8,
"heading": "Skillset",
"heading_was_present": true,
"source_marker": {
"first_5_words": "\u2022 Strong proficiency in full",
"last_5_words": "structured system designs"
},
"text": "\u2022 Strong proficiency in full stack development (NOSQL, React or Next.js, Lambda)\n\u2022 Solid understanding of REST APIs, authentication, and integration patterns\n\u2022 Experience working with CRMs (Insightly preferred, Salesforce/HubSpot acceptable)\n\u2022 Strong debugging, performance optimization, and architectural skills\n\u2022 Cloud experience (AWS preferred)\n\u2022 Ability to understand sales workflows, operations processes, and multi-stage pipelines\n\u2022 Strong communication\u2014clear documentation, structured thinking, and internal stakeholder coordination\n\u2022 Ability to convert ambiguous requirements into structured system designs",
"word_count": 88
},
{
"bullet_count": 5,
"heading": "Experience",
"heading_was_present": true,
"source_marker": {
"first_5_words": "\u2022 4 - 8 years of full-stack",
"last_5_words": "upskill quickly"
},
"text": "\u2022 4 - 8 years of full-stack engineering experience\n\u2022 Must have delivered at least one end-to-end CRM or workflow automation project\n\u2022 Must have built API-driven backend services\n\u2022 Bonus: Experience in solar, field service, fintech, or operations-heavy businesses\n\u2022 Bonus: Experience with Insightly specifically (otherwise willingness to upskill quickly)",
"word_count": 49
}
],
"urls": []
}
API 1 — extract-from-jd click to toggle
{
"final_skills": [
{
"is_primary": true,
"skill_name": "MERN"
},
{
"is_primary": true,
"skill_name": "Insightly"
},
{
"is_primary": true,
"skill_name": "CRM"
},
{
"is_primary": true,
"skill_name": "API"
},
{
"is_primary": true,
"skill_name": "REST"
},
{
"is_primary": true,
"skill_name": "Webhooks"
},
{
"is_primary": true,
"skill_name": "React"
},
{
"is_primary": true,
"skill_name": "Next.js"
},
{
"is_primary": true,
"skill_name": "AWS Lambda"
},
{
"is_primary": true,
"skill_name": "NoSQL"
},
{
"is_primary": true,
"skill_name": "Authentication"
},
{
"is_primary": true,
"skill_name": "Rate Limiting"
},
{
"is_primary": true,
"skill_name": "Background Workers"
},
{
"is_primary": false,
"skill_name": "Salesforce"
},
{
"is_primary": false,
"skill_name": "HubSpot"
},
{
"is_primary": false,
"skill_name": "Serverless"
}
],
"jd_role": {
"display_name": "Lead full-stack developer(MERN)",
"rationale": null,
"role_aliases": [
"Full Stack Developer",
"Lead Developer",
"MERN Developer"
],
"role_archetype": "Engineering",
"slug": ""
},
"nano_parsed": {
"JD_type": "pass",
"about_company": {
"source_marker": {
"first_5_words": "We are a dynamic and",
"last_5_words": "through our next stage."
},
"text": "We are a dynamic and rapidly expanding residential solar installation business based in California, USA. Our mission is to make clean energy accessible to homeowners and accelerate the adoption of solar power throughout the United States. After bootstrapping our early growth, we are investing in the systems that will take us through our next stage.",
"word_count": 64
},
"certifications": [],
"company_name": "Lytegen",
"ctc": null,
"domain": {
"primary": {
"aliases": [
"Solar",
"Clean Energy"
],
"domain": "Energy \u0026 Utilities"
},
"secondary": null
},
"education": [],
"experience": {
"max": 8,
"min": 4,
"raw": "4 - 8 years of full-stack engineering experience"
},
"job_locations": [],
"role": "Lead full-stack developer(MERN)",
"role_aliases": [
"Full Stack Developer",
"Lead Developer",
"MERN Developer"
],
"role_archetype": "Engineering",
"roles_and_responsibilities": [
{
"bullet_count": 4,
"heading": "Role Overview",
"heading_was_present": true,
"source_marker": {
"first_5_words": "You will be the technical",
"last_5_words": "not just writing code."
},
"text": "You will be the technical lead responsible for:\n\n\u2022 Implementing Insightly CRM pipelines, custom fields, automations, and API integrations\n\u2022 Designing and building a scalable middleware/API layer\n\u2022 Working with operational heads to convert business processes into robust system workflows\n\u2022 Acting as the glue between CRM, web app, and external partner systems (dialers, financing providers, proposal management and scheduling tools, etc.)\n\nYou will be an experienced, senior, hands-on engineer with architectural autonomy and significant influence over Lytegen\u0027s technology direction. This is a greenfield opportunity to help define the architecture, build core integrations, and ship real tools used daily by hundreds of internal and external users and would be ideal for an engineer who enjoys solving end-to-end business workflow problems, not just writing code.",
"word_count": 139
},
{
"bullet_count": 16,
"heading": "Key Responsibilities",
"heading_was_present": true,
"source_marker": {
"first_5_words": "CRM (Insightly) Implementation\n\n\u2022 Configure",
"last_5_words": "effort, and impact before implementation"
},
"text": "CRM (Insightly) Implementation\n\n\u2022 Configure Insightly objects, pipelines, automations, and permissions\n\u2022 Build custom fields and structured workflows for leads, proposals, NTP, projects, permitting \u0026 installations\n\u2022 Set up and manage Insightly webhooks and API integrations\n\u2022 Optimize CRM usability for setters, schedulers, closers, and project teams\n\nMiddleware / Integration Layer\n\n\u2022 Design system integrations between Insightly and external tools\n\u2022 Build REST APIs, background workers, webhooks, and syncing logic\n\u2022 Implement authentication, API rate-limit handling, and robust error logging\n\u2022 Set up a clean, maintainable architecture (Server less preferred)\n\nCollaboration + Product\n\n\u2022 Translate complex business workflows into technical designs\n\u2022 Participate in solution design workshops with US/UK stakeholders\n\u2022 Handle documentation, schema design, API contracts, and release planning\n\u2022 Assess technical feasibility, effort, and impact before implementation",
"word_count": 218
},
{
"bullet_count": 8,
"heading": "Skillset",
"heading_was_present": true,
"source_marker": {
"first_5_words": "\u2022 Strong proficiency in full",
"last_5_words": "structured system designs"
},
"text": "\u2022 Strong proficiency in full stack development (NOSQL, React or Next.js, Lambda)\n\u2022 Solid understanding of REST APIs, authentication, and integration patterns\n\u2022 Experience working with CRMs (Insightly preferred, Salesforce/HubSpot acceptable)\n\u2022 Strong debugging, performance optimization, and architectural skills\n\u2022 Cloud experience (AWS preferred)\n\u2022 Ability to understand sales workflows, operations processes, and multi-stage pipelines\n\u2022 Strong communication\u2014clear documentation, structured thinking, and internal stakeholder coordination\n\u2022 Ability to convert ambiguous requirements into structured system designs",
"word_count": 88
},
{
"bullet_count": 5,
"heading": "Experience",
"heading_was_present": true,
"source_marker": {
"first_5_words": "\u2022 4 - 8 years of full-stack",
"last_5_words": "upskill quickly"
},
"text": "\u2022 4 - 8 years of full-stack engineering experience\n\u2022 Must have delivered at least one end-to-end CRM or workflow automation project\n\u2022 Must have built API-driven backend services\n\u2022 Bonus: Experience in solar, field service, fintech, or operations-heavy businesses\n\u2022 Bonus: Experience with Insightly specifically (otherwise willingness to upskill quickly)",
"word_count": 49
}
],
"urls": []
},
"rejected": false,
"rejection_reason": null,
"run_id": "4afaa014-842c-4908-a6ec-fc860ddc44d7",
"stage3_signals": {
"alias_found": true,
"alias_match_roles": [
{
"display_name": "Fullstack Developer",
"kra_matches": null,
"matched_count": null,
"matched_skills": null,
"role_id": 15,
"score": 1.0,
"slug": "full-stack-engineer",
"total_count": null
}
],
"kra_match_roles": [
{
"display_name": "Pega Developer",
"kra_matches": [
{
"kra_text": "Requirements analysis and process translation",
"sentence": "Translate complex business workflows into technical designs",
"similarity": 0.5701
},
{
"kra_text": "external system integration implementation",
"sentence": "Design system integrations between Insightly and external tools",
"similarity": 0.5541
},
{
"kra_text": "Requirements analysis and process translation",
"sentence": "Ability to convert ambiguous requirements into structured system designs",
"similarity": 0.552
}
],
"matched_count": null,
"matched_skills": null,
"role_id": 24,
"score": 0.5587,
"slug": "pega-developer",
"total_count": null
},
{
"display_name": "Backend Developer",
"kra_matches": [
{
"kra_text": "Implements request validation, structured error handling, and input sanitization across backend services to ensure predictable and secure API behavior.",
"sentence": "Implement authentication, API rate-limit handling, and robust error logging",
"similarity": 0.583
},
{
"kra_text": "Designs and maintains RESTful and GraphQL API interfaces with proper authentication, versioning, rate limiting, and documentation for frontend and third-party consumers.",
"sentence": "Build REST APIs, background workers, webhooks, and syncing logic",
"similarity": 0.5467
},
{
"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": "Designing and building a scalable middleware/API layer",
"similarity": 0.539
}
],
"matched_count": null,
"matched_skills": null,
"role_id": 1,
"score": 0.5562,
"slug": "backend-engineer",
"total_count": null
},
{
"display_name": "Flutter Developer",
"kra_matches": [
{
"kra_text": "translate product and design requirements",
"sentence": "Translate complex business workflows into technical designs",
"similarity": 0.5873
},
{
"kra_text": "integrate external APIs and data sources",
"sentence": "Design system integrations between Insightly and external tools",
"similarity": 0.5667
},
{
"kra_text": "translate product and design requirements",
"sentence": "Ability to convert ambiguous requirements into structured system designs",
"similarity": 0.5144
}
],
"matched_count": null,
"matched_skills": null,
"role_id": 74,
"score": 0.5561,
"slug": "flutter-developer",
"total_count": null
},
{
"display_name": "Python Backend Developer",
"kra_matches": [
{
"kra_text": "Support background jobs and async workflows",
"sentence": "Build REST APIs, background workers, webhooks, and syncing logic",
"similarity": 0.582
},
{
"kra_text": "Build service and external integrations",
"sentence": "Design system integrations between Insightly and external tools",
"similarity": 0.5737
},
{
"kra_text": "Design backend endpoints and request handling",
"sentence": "Designing and building a scalable middleware/API layer",
"similarity": 0.5069
}
],
"matched_count": null,
"matched_skills": null,
"role_id": 80,
"score": 0.5542,
"slug": "python-backend-developer",
"total_count": null
},
{
"display_name": "Node.js Backend Developer",
"kra_matches": [
{
"kra_text": "external system integration",
"sentence": "Design system integrations between Insightly and external tools",
"similarity": 0.5566
},
{
"kra_text": "API design and request handling",
"sentence": "Implement authentication, API rate-limit handling, and robust error logging",
"similarity": 0.5414
},
{
"kra_text": "API design and request handling",
"sentence": "Designing and building a scalable middleware/API layer",
"similarity": 0.5308
}
],
"matched_count": null,
"matched_skills": null,
"role_id": 82,
"score": 0.5429,
"slug": "node-backend-developer",
"total_count": null
}
],
"skill_match_roles": [
{
"display_name": "Fullstack Developer",
"kra_matches": null,
"matched_count": 6,
"matched_skills": [
"API",
"AWS Lambda",
"Authentication",
"Next.js",
"REST",
"React"
],
"role_id": 15,
"score": 0.4615,
"slug": "full-stack-engineer",
"total_count": 13
},
{
"display_name": "Web Developer",
"kra_matches": null,
"matched_count": 5,
"matched_skills": [
"API",
"AWS Lambda",
"Authentication",
"Next.js",
"React"
],
"role_id": 25,
"score": 0.3846,
"slug": "web-developer",
"total_count": 13
},
{
"display_name": "Backend Developer",
"kra_matches": null,
"matched_count": 5,
"matched_skills": [
"AWS Lambda",
"NoSQL",
"REST",
"rate limiting",
"webhooks"
],
"role_id": 1,
"score": 0.3846,
"slug": "backend-engineer",
"total_count": 13
},
{
"display_name": "Frontend Developer",
"kra_matches": null,
"matched_count": 4,
"matched_skills": [
"API",
"Authentication",
"Next.js",
"React"
],
"role_id": 7,
"score": 0.3077,
"slug": "frontend-engineer",
"total_count": 13
},
{
"display_name": "Python Backend Developer",
"kra_matches": null,
"matched_count": 4,
"matched_skills": [
"AWS Lambda",
"REST",
"rate limiting",
"webhooks"
],
"role_id": 80,
"score": 0.3077,
"slug": "python-backend-developer",
"total_count": 13
}
]
},
"stage4_decision": {
"alias_collision_detected": false,
"case": "A",
"chosen_role": {
"display_name": "Fullstack Developer",
"kra_matches": null,
"matched_count": null,
"matched_skills": null,
"role_id": 15,
"score": 1.0,
"slug": "full-stack-engineer",
"total_count": null
},
"confidence": 1.0,
"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": "Exact alias hit on full-stack-engineer (1.0) \u2014 no other alias at this confidence; skill_top full-stack-engineer 0.46 does not contradict",
"sub_role": null
},
"stage5_updates": {
"centroid_n_after": 81,
"centroid_updated": true,
"collision_log_id": null,
"new_kra_attached": {
"best_kra_similarity": 0.0,
"queue_id": 239,
"r_and_r_preview": "You will be the technical lead responsible for:\n\n\u2022 Implementing Insightly CRM pipelines, custom fields, automations, and API integrations\n\u2022 Designing and building a scalable middleware/API layer\n\u2022 Wor",
"role_display_name": "Fullstack Developer",
"role_slug": "full-stack-engineer",
"status": "pending"
},
"new_skills_attached": [
{
"is_primary": true,
"queue_id": 5154,
"role_display_name": "Fullstack Developer",
"role_slug": "full-stack-engineer",
"skill_name": "MERN",
"status": "pending"
},
{
"is_primary": true,
"queue_id": 5155,
"role_display_name": "Fullstack Developer",
"role_slug": "full-stack-engineer",
"skill_name": "Insightly",
"status": "pending"
},
{
"is_primary": true,
"queue_id": 5156,
"role_display_name": "Fullstack Developer",
"role_slug": "full-stack-engineer",
"skill_name": "CRM",
"status": "pending"
},
{
"is_primary": true,
"queue_id": 5157,
"role_display_name": "Fullstack Developer",
"role_slug": "full-stack-engineer",
"skill_name": "Background Workers",
"status": "pending"
},
{
"is_primary": false,
"queue_id": 5158,
"role_display_name": "Fullstack Developer",
"role_slug": "full-stack-engineer",
"skill_name": "Salesforce",
"status": "pending"
},
{
"is_primary": false,
"queue_id": 5159,
"role_display_name": "Fullstack Developer",
"role_slug": "full-stack-engineer",
"skill_name": "HubSpot",
"status": "pending"
},
{
"is_primary": false,
"queue_id": 5160,
"role_display_name": "Fullstack Developer",
"role_slug": "full-stack-engineer",
"skill_name": "Serverless",
"status": "pending"
}
],
"queue_entry_id": null,
"v3_pipeline_triggered": false,
"v3_role_slug": null,
"v3_run_id": null
}
}
API 2 — extract-details
{
"alias_matches": [
{
"alias_persist_skipped_reason": "alias_text already exists for this canonical skill",
"alias_persisted": false,
"existing_alias_id": 2514,
"existing_alias_text": "API",
"input_term": "API",
"matched_canonical": {
"category_id": 2,
"display_name": "API",
"id": 1568,
"is_also_category": false,
"is_extractable": true,
"skill_nature": "CONCEPT",
"slug": "api",
"sub_category_id": 1174,
"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": 1047,
"existing_alias_text": "React",
"input_term": "React",
"matched_canonical": {
"category_id": 5,
"display_name": "React",
"id": 610,
"is_also_category": false,
"is_extractable": true,
"skill_nature": "FRAMEWORK",
"slug": "react",
"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": 2117,
"existing_alias_text": "next.js",
"input_term": "Next.js",
"matched_canonical": {
"category_id": 5,
"display_name": "Next.js",
"id": 705,
"is_also_category": false,
"is_extractable": true,
"skill_nature": "FRAMEWORK",
"slug": "next-js",
"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": 3563,
"existing_alias_text": "AWS Lambda",
"input_term": "AWS Lambda",
"matched_canonical": {
"category_id": 11,
"display_name": "AWS Lambda",
"id": 2295,
"is_also_category": false,
"is_extractable": true,
"skill_nature": "CLOUD_SERVICE",
"slug": "aws-lambda",
"sub_category_id": 1704,
"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": 1989,
"existing_alias_text": "NoSQL",
"input_term": "NoSQL",
"matched_canonical": {
"category_id": 2,
"display_name": "NoSQL",
"id": 1346,
"is_also_category": false,
"is_extractable": true,
"skill_nature": "CONCEPT",
"slug": "nosql",
"sub_category_id": 1019,
"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": 2560,
"existing_alias_text": "Authentication",
"input_term": "Authentication",
"matched_canonical": {
"category_id": 2,
"display_name": "Authentication",
"id": 1608,
"is_also_category": false,
"is_extractable": true,
"skill_nature": "CONCEPT",
"slug": "authentication",
"sub_category_id": 1211,
"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": 3647,
"existing_alias_text": "rate limiting",
"input_term": "Rate Limiting",
"matched_canonical": {
"category_id": 2,
"display_name": "rate limiting",
"id": 2357,
"is_also_category": false,
"is_extractable": true,
"skill_nature": "CONCEPT",
"slug": "rate-limiting",
"sub_category_id": 2522,
"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": 1345,
"existing_alias_text": "Serverless Framework",
"input_term": "Serverless",
"matched_canonical": {
"category_id": 5,
"display_name": "Serverless Framework",
"id": 800,
"is_also_category": false,
"is_extractable": true,
"skill_nature": "FRAMEWORK",
"slug": "serverless-framework",
"sub_category_id": 145,
"typical_lifespan": "EVERGREEN",
"volatility": "STABLE"
},
"matched_via": "embedding_alias"
}
],
"candidate_roles": [
{
"display_name": "Angular Frontend Developer",
"id": 90,
"rationale": null,
"role_archetype": "Engineering",
"slug": "angular-frontend-developer",
"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": "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"
},
{
"display_name": "Web Developer",
"id": 25,
"rationale": null,
"role_archetype": null,
"slug": "web-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": ".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"
},
{
"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": "Java Backend Developer",
"id": 79,
"rationale": null,
"role_archetype": "Engineering",
"slug": "java-backend-developer",
"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": "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": "Cyber Security Engineer",
"id": 5,
"rationale": null,
"role_archetype": null,
"slug": "cybersecurity-engineer",
"source": "db"
},
{
"display_name": "Data Engineer",
"id": 2,
"rationale": null,
"role_archetype": null,
"slug": "data-engineer",
"source": "db"
},
{
"display_name": "DevOps Engineer",
"id": 10,
"rationale": null,
"role_archetype": null,
"slug": "devops-engineer",
"source": "db"
},
{
"display_name": "ML Engineer",
"id": 3,
"rationale": null,
"role_archetype": null,
"slug": "ml-engineer",
"source": "db"
},
{
"display_name": "MLOps Engineer",
"id": 16,
"rationale": null,
"role_archetype": null,
"slug": "ml-ops-engineer",
"source": "db"
},
{
"display_name": "Android Developer",
"id": 4,
"rationale": null,
"role_archetype": null,
"slug": "android-engineer",
"source": "db"
},
{
"display_name": "Native Mobile Developer",
"id": 75,
"rationale": null,
"role_archetype": "Engineering",
"slug": "native-mobile-developer",
"source": "db"
},
{
"display_name": "iOS Developer",
"id": 6,
"rationale": null,
"role_archetype": null,
"slug": "ios-engineer",
"source": "db"
},
{
"display_name": "Cloud Architect",
"id": 9,
"rationale": null,
"role_archetype": null,
"slug": "cloud-architect",
"source": "db"
}
],
"chosen_role": {
"display_name": "Fullstack Developer",
"id": 15,
"rationale": "Exact alias hit on full-stack-engineer (1.0) \u2014 no other alias at this confidence; skill_top full-stack-engineer 0.46 does not contradict",
"role_archetype": null,
"slug": "full-stack-engineer",
"source": "db"
},
"dimensions": [
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "API Integration and Data Fetching",
"id": 127,
"rationale": "Client-side integration with backend endpoints and third-party services, including request shaping, response handling, and synchronization with UI state. This is central to frontend work because most screens depend on remote data.",
"slug": "api-integration-and-data-fetching",
"source": "db"
},
"input_skill": "API",
"llm_role": null,
"roles_from_db": [
{
"display_name": "Angular Frontend Developer",
"id": 90,
"rationale": null,
"role_archetype": "Engineering",
"slug": "angular-frontend-developer",
"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": "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"
},
{
"display_name": "Web Developer",
"id": 25,
"rationale": null,
"role_archetype": null,
"slug": "web-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": "Application Frameworks \u0026 Libraries",
"id": 451,
"rationale": "Covers the primary software frameworks and libraries often used alongside Sitecore for building and enhancing site experiences.",
"slug": "application-frameworks-libraries",
"source": "db"
},
"input_skill": "React",
"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": "Frontend Frameworks and Libraries",
"id": 434,
"rationale": "Utilizing modern JavaScript frameworks and Shopify libraries to build dynamic and interactive storefronts.",
"slug": "frontend-frameworks-and-libraries",
"source": "db"
},
"input_skill": "React",
"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": "JavaScript for WordPress",
"id": 329,
"rationale": "Client-side scripting used to enhance WordPress themes, blocks, and admin/editor interactions. This includes modern JavaScript patterns as they apply to WordPress-specific behavior rather than standalone frontend applications.",
"slug": "javascript-for-wordpress",
"source": "db"
},
"input_skill": "React",
"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 Component Architecture",
"id": 302,
"rationale": "Building reusable React components, composing props and children, and managing rendering behavior across feature screens. This is the primary framework cluster for a React frontend developer.",
"slug": "react-component-architecture",
"source": "db"
},
"input_skill": "React",
"llm_role": null,
"roles_from_db": [
{
"display_name": "React Frontend Developer",
"id": 89,
"rationale": null,
"role_archetype": "Engineering",
"slug": "react-frontend-developer",
"source": "db"
}
]
},
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "UI Frameworks and Rendering",
"id": 115,
"rationale": "Component frameworks and rendering models used to build browser screens, reusable UI, and interactive client flows. This is a core cluster because frontend engineers spend much of their time composing and updating view hierarchies.",
"slug": "ui-frameworks-and-rendering",
"source": "db"
},
"input_skill": "React",
"llm_role": null,
"roles_from_db": [
{
"display_name": "Frontend Developer",
"id": 7,
"rationale": null,
"role_archetype": null,
"slug": "frontend-engineer",
"source": "db"
},
{
"display_name": "Fullstack Developer",
"id": 15,
"rationale": null,
"role_archetype": null,
"slug": "full-stack-engineer",
"source": "db"
},
{
"display_name": "Hybrid Mobile Developer",
"id": 11,
"rationale": null,
"role_archetype": null,
"slug": "hybrid-mobile-developer",
"source": "db"
},
{
"display_name": "Ionic Developer",
"id": 434,
"rationale": null,
"role_archetype": null,
"slug": "ionic-developer",
"source": "db"
},
{
"display_name": "Web Developer",
"id": 25,
"rationale": null,
"role_archetype": null,
"slug": "web-developer",
"source": "db"
}
]
},
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Frontend Frameworks and Libraries",
"id": 434,
"rationale": "Utilizing modern JavaScript frameworks and Shopify libraries to build dynamic and interactive storefronts.",
"slug": "frontend-frameworks-and-libraries",
"source": "db"
},
"input_skill": "Next.js",
"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": "Meta-Frameworks \u0026 SSR",
"id": 130,
"rationale": "Frameworks that build on UI libraries to provide routing, server-side rendering, and static site generation.",
"slug": "meta-frameworks-ssr",
"source": "db"
},
"input_skill": "Next.js",
"llm_role": null,
"roles_from_db": [
{
"display_name": "Frontend Developer",
"id": 7,
"rationale": null,
"role_archetype": null,
"slug": "frontend-engineer",
"source": "db"
},
{
"display_name": "Web Developer",
"id": 25,
"rationale": null,
"role_archetype": null,
"slug": "web-developer",
"source": "db"
}
]
},
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "UI Frameworks and Rendering",
"id": 115,
"rationale": "Component frameworks and rendering models used to build browser screens, reusable UI, and interactive client flows. This is a core cluster because frontend engineers spend much of their time composing and updating view hierarchies.",
"slug": "ui-frameworks-and-rendering",
"source": "db"
},
"input_skill": "Next.js",
"llm_role": null,
"roles_from_db": [
{
"display_name": "Frontend Developer",
"id": 7,
"rationale": null,
"role_archetype": null,
"slug": "frontend-engineer",
"source": "db"
},
{
"display_name": "Fullstack Developer",
"id": 15,
"rationale": null,
"role_archetype": null,
"slug": "full-stack-engineer",
"source": "db"
},
{
"display_name": "Hybrid Mobile Developer",
"id": 11,
"rationale": null,
"role_archetype": null,
"slug": "hybrid-mobile-developer",
"source": "db"
},
{
"display_name": "Ionic Developer",
"id": 434,
"rationale": null,
"role_archetype": null,
"slug": "ionic-developer",
"source": "db"
},
{
"display_name": "Web Developer",
"id": 25,
"rationale": null,
"role_archetype": null,
"slug": "web-developer",
"source": "db"
}
]
},
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Cloud Platforms",
"id": 20,
"rationale": "Underlying cloud providers that host the managed services or infrastructure used by the role, such as AWS, Azure, and GCP.",
"slug": "cloud-platforms",
"source": "db"
},
"input_skill": "AWS Lambda",
"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": "Cyber Security Engineer",
"id": 5,
"rationale": null,
"role_archetype": null,
"slug": "cybersecurity-engineer",
"source": "db"
},
{
"display_name": "Data Engineer",
"id": 2,
"rationale": null,
"role_archetype": null,
"slug": "data-engineer",
"source": "db"
},
{
"display_name": "DevOps Engineer",
"id": 10,
"rationale": null,
"role_archetype": null,
"slug": "devops-engineer",
"source": "db"
},
{
"display_name": "Fullstack Developer",
"id": 15,
"rationale": null,
"role_archetype": null,
"slug": "full-stack-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": "Kotlin Backend Developer",
"id": 84,
"rationale": null,
"role_archetype": "Engineering",
"slug": "kotlin-server-backend-developer",
"source": "db"
},
{
"display_name": "ML Engineer",
"id": 3,
"rationale": null,
"role_archetype": null,
"slug": "ml-engineer",
"source": "db"
},
{
"display_name": "MLOps Engineer",
"id": 16,
"rationale": null,
"role_archetype": null,
"slug": "ml-ops-engineer",
"source": "db"
},
{
"display_name": "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": "Scala Backend Developer",
"id": 87,
"rationale": null,
"role_archetype": "Engineering",
"slug": "scala-backend-developer",
"source": "db"
}
]
},
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Cloud Platforms \u0026 Hosting Providers",
"id": 278,
"rationale": "Familiarity with vendor-specific hosting and backend services for deploying and scaling web applications.",
"slug": "cloud-platforms-hosting-providers",
"source": "db"
},
"input_skill": "AWS Lambda",
"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": "Kotlin Backend Developer",
"id": 84,
"rationale": null,
"role_archetype": "Engineering",
"slug": "kotlin-server-backend-developer",
"source": "db"
},
{
"display_name": "Scala Backend Developer",
"id": 87,
"rationale": null,
"role_archetype": "Engineering",
"slug": "scala-backend-developer",
"source": "db"
},
{
"display_name": "Web Developer",
"id": 25,
"rationale": null,
"role_archetype": null,
"slug": "web-developer",
"source": "db"
}
]
},
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Cloud Platforms \u0026 Managed Services",
"id": 221,
"rationale": "Operates and integrates vendor-specific cloud compute, storage, and hosting services.",
"slug": "cloud-platforms-managed-services",
"source": "db"
},
"input_skill": "AWS Lambda",
"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": "Go Backend Developer",
"id": 81,
"rationale": null,
"role_archetype": "Engineering",
"slug": "go-backend-developer",
"source": "db"
},
{
"display_name": "Node.js Backend Developer",
"id": 82,
"rationale": null,
"role_archetype": "Engineering",
"slug": "node-backend-developer",
"source": "db"
}
]
},
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Cloud Platforms \u0026 Services",
"id": 296,
"rationale": "Deploying, configuring, and managing Python backends on major cloud and PaaS offerings.",
"slug": "cloud-platforms-services",
"source": "db"
},
"input_skill": "AWS Lambda",
"llm_role": null,
"roles_from_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": "NoSQL Databases",
"id": 19,
"rationale": "Models and manages data using non-relational database systems.",
"slug": "nosql-databases",
"source": "db"
},
"input_skill": "NoSQL",
"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"
}
]
},
{
"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": "Authentication",
"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 Security Hardening",
"id": 16,
"rationale": "Security practices specific to server-side application code and service exposure. Focuses on protecting backend endpoints, secrets, and data handling from common application-layer threats.",
"slug": "backend-security-hardening",
"source": "db"
},
"input_skill": "Rate Limiting",
"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": "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": "Infrastructure as Code",
"id": 132,
"rationale": "Declarative provisioning and environment definition tools used to codify cloud infrastructure, repeatable environments, and platform standards. Cloud Architects use these to express reference architectures and guardrails.",
"slug": "infrastructure-as-code",
"source": "db"
},
"input_skill": "Serverless",
"llm_role": null,
"roles_from_db": [
{
"display_name": "Cloud Architect",
"id": 9,
"rationale": null,
"role_archetype": null,
"slug": "cloud-architect",
"source": "db"
},
{
"display_name": "DevOps Engineer",
"id": 10,
"rationale": null,
"role_archetype": null,
"slug": "devops-engineer",
"source": "db"
}
]
}
],
"input_final_skills": [
"MERN",
"Insightly",
"CRM",
"API",
"REST",
"Webhooks",
"React",
"Next.js",
"AWS Lambda",
"NoSQL",
"Authentication",
"Rate Limiting",
"Background Workers",
"Salesforce",
"HubSpot",
"Serverless"
],
"input_llm_skills": [
"MERN",
"Insightly",
"CRM",
"API",
"REST",
"Webhooks",
"React",
"Next.js",
"AWS Lambda",
"NoSQL",
"Authentication",
"Rate Limiting",
"Background Workers",
"Salesforce",
"HubSpot",
"Serverless"
],
"new_aliases_persisted": 0,
"run_id": "4afaa014-842c-4908-a6ec-fc860ddc44d7",
"skills_detail": [
{
"aliases_in_db": [],
"canonical": null,
"dimensions": [],
"input_skill": "MERN",
"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": "mern",
"split_log": [],
"typed": null,
"warnings": []
},
"source_tag": "llm",
"was_in_llm_skills": true
},
{
"aliases_in_db": [],
"canonical": null,
"dimensions": [],
"input_skill": "Insightly",
"matched_via": null,
"new_alias_persisted": false,
"new_alias_text": null,
"new_skill_meta": {
"derived": {
"category": "CRM Platforms",
"skill_nature": "PLATFORM",
"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": "insightly",
"split_log": [],
"typed": null,
"warnings": []
},
"source_tag": "llm",
"was_in_llm_skills": true
},
{
"aliases_in_db": [],
"canonical": null,
"dimensions": [],
"input_skill": "CRM",
"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": "crm",
"split_log": [],
"typed": null,
"warnings": []
},
"source_tag": "llm",
"was_in_llm_skills": true
},
{
"aliases_in_db": [
{
"alias_text": "API",
"alias_type": "CANONICAL",
"id": 2514,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
}
],
"canonical": {
"category_id": 2,
"display_name": "API",
"id": 1568,
"is_also_category": false,
"is_extractable": true,
"skill_nature": "CONCEPT",
"slug": "api",
"sub_category_id": 1174,
"typical_lifespan": "EVERGREEN",
"volatility": "STABLE"
},
"dimensions": [
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "API Integration and Data Fetching",
"id": 127,
"rationale": "Client-side integration with backend endpoints and third-party services, including request shaping, response handling, and synchronization with UI state. This is central to frontend work because most screens depend on remote data.",
"slug": "api-integration-and-data-fetching",
"source": "db"
},
"input_skill": "API",
"llm_role": null,
"roles_from_db": [
{
"display_name": "Angular Frontend Developer",
"id": 90,
"rationale": null,
"role_archetype": "Engineering",
"slug": "angular-frontend-developer",
"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": "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"
},
{
"display_name": "Web Developer",
"id": 25,
"rationale": null,
"role_archetype": null,
"slug": "web-developer",
"source": "db"
}
]
}
],
"input_skill": "API",
"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": [
{
"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": "React",
"alias_type": "CANONICAL",
"id": 1047,
"is_primary": true,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "React 0.13",
"alias_type": "VERSION",
"id": 1052,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "React 0.14",
"alias_type": "VERSION",
"id": 1053,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "React 15",
"alias_type": "VERSION",
"id": 1048,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "React 15.x",
"alias_type": "VERSION",
"id": 1054,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "React 16",
"alias_type": "VERSION",
"id": 1049,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "React 16.x",
"alias_type": "VERSION",
"id": 1055,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "React 17",
"alias_type": "VERSION",
"id": 1050,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "React 17.x",
"alias_type": "VERSION",
"id": 1056,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "React 18",
"alias_type": "VERSION",
"id": 1051,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "React 18.x",
"alias_type": "VERSION",
"id": 1057,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "React 19",
"alias_type": "VERSION",
"id": 2068,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "React v15",
"alias_type": "VERSION",
"id": 3185,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "React v16",
"alias_type": "VERSION",
"id": 3186,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "React v17",
"alias_type": "VERSION",
"id": 3187,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "React v18",
"alias_type": "VERSION",
"id": 3188,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "ReactJS 18",
"alias_type": "VERSION",
"id": 2074,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "react 15",
"alias_type": "VERSION",
"id": 2069,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "react 16",
"alias_type": "VERSION",
"id": 2070,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "react 17",
"alias_type": "VERSION",
"id": 2071,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "react 18",
"alias_type": "VERSION",
"id": 2072,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "react 19",
"alias_type": "VERSION",
"id": 2073,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "react15",
"alias_type": "VERSION",
"id": 3177,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "react16",
"alias_type": "VERSION",
"id": 3178,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "react17",
"alias_type": "VERSION",
"id": 3179,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "react18",
"alias_type": "VERSION",
"id": 3180,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "reactjs 18",
"alias_type": "VERSION",
"id": 2075,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
}
],
"canonical": {
"category_id": 5,
"display_name": "React",
"id": 610,
"is_also_category": false,
"is_extractable": true,
"skill_nature": "FRAMEWORK",
"slug": "react",
"sub_category_id": 1072,
"typical_lifespan": "EVERGREEN",
"volatility": "STABLE"
},
"dimensions": [
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Application Frameworks \u0026 Libraries",
"id": 451,
"rationale": "Covers the primary software frameworks and libraries often used alongside Sitecore for building and enhancing site experiences.",
"slug": "application-frameworks-libraries",
"source": "db"
},
"input_skill": "React",
"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": "Frontend Frameworks and Libraries",
"id": 434,
"rationale": "Utilizing modern JavaScript frameworks and Shopify libraries to build dynamic and interactive storefronts.",
"slug": "frontend-frameworks-and-libraries",
"source": "db"
},
"input_skill": "React",
"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": "JavaScript for WordPress",
"id": 329,
"rationale": "Client-side scripting used to enhance WordPress themes, blocks, and admin/editor interactions. This includes modern JavaScript patterns as they apply to WordPress-specific behavior rather than standalone frontend applications.",
"slug": "javascript-for-wordpress",
"source": "db"
},
"input_skill": "React",
"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 Component Architecture",
"id": 302,
"rationale": "Building reusable React components, composing props and children, and managing rendering behavior across feature screens. This is the primary framework cluster for a React frontend developer.",
"slug": "react-component-architecture",
"source": "db"
},
"input_skill": "React",
"llm_role": null,
"roles_from_db": [
{
"display_name": "React Frontend Developer",
"id": 89,
"rationale": null,
"role_archetype": "Engineering",
"slug": "react-frontend-developer",
"source": "db"
}
]
},
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "UI Frameworks and Rendering",
"id": 115,
"rationale": "Component frameworks and rendering models used to build browser screens, reusable UI, and interactive client flows. This is a core cluster because frontend engineers spend much of their time composing and updating view hierarchies.",
"slug": "ui-frameworks-and-rendering",
"source": "db"
},
"input_skill": "React",
"llm_role": null,
"roles_from_db": [
{
"display_name": "Frontend Developer",
"id": 7,
"rationale": null,
"role_archetype": null,
"slug": "frontend-engineer",
"source": "db"
},
{
"display_name": "Fullstack Developer",
"id": 15,
"rationale": null,
"role_archetype": null,
"slug": "full-stack-engineer",
"source": "db"
},
{
"display_name": "Hybrid Mobile Developer",
"id": 11,
"rationale": null,
"role_archetype": null,
"slug": "hybrid-mobile-developer",
"source": "db"
},
{
"display_name": "Ionic Developer",
"id": 434,
"rationale": null,
"role_archetype": null,
"slug": "ionic-developer",
"source": "db"
},
{
"display_name": "Web Developer",
"id": 25,
"rationale": null,
"role_archetype": null,
"slug": "web-developer",
"source": "db"
}
]
}
],
"input_skill": "React",
"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": "Next.js",
"alias_type": "CANONICAL",
"id": 1210,
"is_primary": true,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "Next 10",
"alias_type": "VERSION",
"id": 1219,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "Next 11",
"alias_type": "VERSION",
"id": 1220,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "Next 12",
"alias_type": "VERSION",
"id": 1221,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "Next 13",
"alias_type": "VERSION",
"id": 1222,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "Next 14",
"alias_type": "VERSION",
"id": 1223,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "Next 15",
"alias_type": "VERSION",
"id": 1224,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "Next 2",
"alias_type": "VERSION",
"id": 1211,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "Next 3",
"alias_type": "VERSION",
"id": 1212,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "Next 4",
"alias_type": "VERSION",
"id": 1213,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "Next 5",
"alias_type": "VERSION",
"id": 1214,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "Next 6",
"alias_type": "VERSION",
"id": 1215,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "Next 7",
"alias_type": "VERSION",
"id": 1216,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "Next 8",
"alias_type": "VERSION",
"id": 1217,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "Next 9",
"alias_type": "VERSION",
"id": 1218,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "Next.js 1",
"alias_type": "VERSION",
"id": 1225,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "Next.js 10",
"alias_type": "VERSION",
"id": 1234,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "Next.js 11",
"alias_type": "VERSION",
"id": 1235,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "Next.js 12",
"alias_type": "VERSION",
"id": 1236,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "Next.js 13",
"alias_type": "VERSION",
"id": 1237,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "Next.js 14",
"alias_type": "VERSION",
"id": 1238,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "Next.js 15",
"alias_type": "VERSION",
"id": 1239,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "Next.js 2",
"alias_type": "VERSION",
"id": 1226,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "Next.js 3",
"alias_type": "VERSION",
"id": 1227,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "Next.js 4",
"alias_type": "VERSION",
"id": 1228,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "Next.js 5",
"alias_type": "VERSION",
"id": 1229,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "Next.js 6",
"alias_type": "VERSION",
"id": 1230,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "Next.js 7",
"alias_type": "VERSION",
"id": 1231,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "Next.js 8",
"alias_type": "VERSION",
"id": 1232,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "Next.js 9",
"alias_type": "VERSION",
"id": 1233,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "next",
"alias_type": "VERSION",
"id": 2115,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "next.js",
"alias_type": "VERSION",
"id": 2117,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "next.js 14",
"alias_type": "VERSION",
"id": 2120,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "nextjs",
"alias_type": "VERSION",
"id": 2116,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "nextjs 14",
"alias_type": "VERSION",
"id": 2118,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
}
],
"canonical": {
"category_id": 5,
"display_name": "Next.js",
"id": 705,
"is_also_category": false,
"is_extractable": true,
"skill_nature": "FRAMEWORK",
"slug": "next-js",
"sub_category_id": 35,
"typical_lifespan": "EVERGREEN",
"volatility": "STABLE"
},
"dimensions": [
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Frontend Frameworks and Libraries",
"id": 434,
"rationale": "Utilizing modern JavaScript frameworks and Shopify libraries to build dynamic and interactive storefronts.",
"slug": "frontend-frameworks-and-libraries",
"source": "db"
},
"input_skill": "Next.js",
"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": "Meta-Frameworks \u0026 SSR",
"id": 130,
"rationale": "Frameworks that build on UI libraries to provide routing, server-side rendering, and static site generation.",
"slug": "meta-frameworks-ssr",
"source": "db"
},
"input_skill": "Next.js",
"llm_role": null,
"roles_from_db": [
{
"display_name": "Frontend Developer",
"id": 7,
"rationale": null,
"role_archetype": null,
"slug": "frontend-engineer",
"source": "db"
},
{
"display_name": "Web Developer",
"id": 25,
"rationale": null,
"role_archetype": null,
"slug": "web-developer",
"source": "db"
}
]
},
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "UI Frameworks and Rendering",
"id": 115,
"rationale": "Component frameworks and rendering models used to build browser screens, reusable UI, and interactive client flows. This is a core cluster because frontend engineers spend much of their time composing and updating view hierarchies.",
"slug": "ui-frameworks-and-rendering",
"source": "db"
},
"input_skill": "Next.js",
"llm_role": null,
"roles_from_db": [
{
"display_name": "Frontend Developer",
"id": 7,
"rationale": null,
"role_archetype": null,
"slug": "frontend-engineer",
"source": "db"
},
{
"display_name": "Fullstack Developer",
"id": 15,
"rationale": null,
"role_archetype": null,
"slug": "full-stack-engineer",
"source": "db"
},
{
"display_name": "Hybrid Mobile Developer",
"id": 11,
"rationale": null,
"role_archetype": null,
"slug": "hybrid-mobile-developer",
"source": "db"
},
{
"display_name": "Ionic Developer",
"id": 434,
"rationale": null,
"role_archetype": null,
"slug": "ionic-developer",
"source": "db"
},
{
"display_name": "Web Developer",
"id": 25,
"rationale": null,
"role_archetype": null,
"slug": "web-developer",
"source": "db"
}
]
}
],
"input_skill": "Next.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": "AWS Lambda",
"alias_type": "CANONICAL",
"id": 3563,
"is_primary": true,
"match_strategy": "CASE_INSENSITIVE"
}
],
"canonical": {
"category_id": 11,
"display_name": "AWS Lambda",
"id": 2295,
"is_also_category": false,
"is_extractable": true,
"skill_nature": "CLOUD_SERVICE",
"slug": "aws-lambda",
"sub_category_id": 1704,
"typical_lifespan": "EVERGREEN",
"volatility": "STABLE"
},
"dimensions": [
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Cloud Platforms",
"id": 20,
"rationale": "Underlying cloud providers that host the managed services or infrastructure used by the role, such as AWS, Azure, and GCP.",
"slug": "cloud-platforms",
"source": "db"
},
"input_skill": "AWS Lambda",
"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": "Cyber Security Engineer",
"id": 5,
"rationale": null,
"role_archetype": null,
"slug": "cybersecurity-engineer",
"source": "db"
},
{
"display_name": "Data Engineer",
"id": 2,
"rationale": null,
"role_archetype": null,
"slug": "data-engineer",
"source": "db"
},
{
"display_name": "DevOps Engineer",
"id": 10,
"rationale": null,
"role_archetype": null,
"slug": "devops-engineer",
"source": "db"
},
{
"display_name": "Fullstack Developer",
"id": 15,
"rationale": null,
"role_archetype": null,
"slug": "full-stack-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": "Kotlin Backend Developer",
"id": 84,
"rationale": null,
"role_archetype": "Engineering",
"slug": "kotlin-server-backend-developer",
"source": "db"
},
{
"display_name": "ML Engineer",
"id": 3,
"rationale": null,
"role_archetype": null,
"slug": "ml-engineer",
"source": "db"
},
{
"display_name": "MLOps Engineer",
"id": 16,
"rationale": null,
"role_archetype": null,
"slug": "ml-ops-engineer",
"source": "db"
},
{
"display_name": "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": "Scala Backend Developer",
"id": 87,
"rationale": null,
"role_archetype": "Engineering",
"slug": "scala-backend-developer",
"source": "db"
}
]
},
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Cloud Platforms \u0026 Hosting Providers",
"id": 278,
"rationale": "Familiarity with vendor-specific hosting and backend services for deploying and scaling web applications.",
"slug": "cloud-platforms-hosting-providers",
"source": "db"
},
"input_skill": "AWS Lambda",
"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": "Kotlin Backend Developer",
"id": 84,
"rationale": null,
"role_archetype": "Engineering",
"slug": "kotlin-server-backend-developer",
"source": "db"
},
{
"display_name": "Scala Backend Developer",
"id": 87,
"rationale": null,
"role_archetype": "Engineering",
"slug": "scala-backend-developer",
"source": "db"
},
{
"display_name": "Web Developer",
"id": 25,
"rationale": null,
"role_archetype": null,
"slug": "web-developer",
"source": "db"
}
]
},
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Cloud Platforms \u0026 Managed Services",
"id": 221,
"rationale": "Operates and integrates vendor-specific cloud compute, storage, and hosting services.",
"slug": "cloud-platforms-managed-services",
"source": "db"
},
"input_skill": "AWS Lambda",
"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": "Go Backend Developer",
"id": 81,
"rationale": null,
"role_archetype": "Engineering",
"slug": "go-backend-developer",
"source": "db"
},
{
"display_name": "Node.js Backend Developer",
"id": 82,
"rationale": null,
"role_archetype": "Engineering",
"slug": "node-backend-developer",
"source": "db"
}
]
},
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Cloud Platforms \u0026 Services",
"id": 296,
"rationale": "Deploying, configuring, and managing Python backends on major cloud and PaaS offerings.",
"slug": "cloud-platforms-services",
"source": "db"
},
"input_skill": "AWS Lambda",
"llm_role": null,
"roles_from_db": [
{
"display_name": "Python Backend Developer",
"id": 80,
"rationale": null,
"role_archetype": "Engineering",
"slug": "python-backend-developer",
"source": "db"
}
]
}
],
"input_skill": "AWS Lambda",
"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": "NoSQL",
"alias_type": "CANONICAL",
"id": 1989,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
}
],
"canonical": {
"category_id": 2,
"display_name": "NoSQL",
"id": 1346,
"is_also_category": false,
"is_extractable": true,
"skill_nature": "CONCEPT",
"slug": "nosql",
"sub_category_id": 1019,
"typical_lifespan": "EVERGREEN",
"volatility": "STABLE"
},
"dimensions": [
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "NoSQL Databases",
"id": 19,
"rationale": "Models and manages data using non-relational database systems.",
"slug": "nosql-databases",
"source": "db"
},
"input_skill": "NoSQL",
"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"
}
]
}
],
"input_skill": "NoSQL",
"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": "Authentication",
"alias_type": "CANONICAL",
"id": 2560,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
}
],
"canonical": {
"category_id": 2,
"display_name": "Authentication",
"id": 1608,
"is_also_category": false,
"is_extractable": true,
"skill_nature": "CONCEPT",
"slug": "authentication",
"sub_category_id": 1211,
"typical_lifespan": "EVERGREEN",
"volatility": "STABLE"
},
"dimensions": [
{
"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": "Authentication",
"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"
}
]
}
],
"input_skill": "Authentication",
"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": "rate limiting",
"alias_type": "CANONICAL",
"id": 3647,
"is_primary": true,
"match_strategy": "CASE_INSENSITIVE"
}
],
"canonical": {
"category_id": 2,
"display_name": "rate limiting",
"id": 2357,
"is_also_category": false,
"is_extractable": true,
"skill_nature": "CONCEPT",
"slug": "rate-limiting",
"sub_category_id": 2522,
"typical_lifespan": "EVERGREEN",
"volatility": "STABLE"
},
"dimensions": [
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Backend Security Hardening",
"id": 16,
"rationale": "Security practices specific to server-side application code and service exposure. Focuses on protecting backend endpoints, secrets, and data handling from common application-layer threats.",
"slug": "backend-security-hardening",
"source": "db"
},
"input_skill": "Rate Limiting",
"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": "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"
}
]
}
],
"input_skill": "Rate Limiting",
"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": "Background Workers",
"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": "background-workers",
"split_log": [],
"typed": null,
"warnings": []
},
"source_tag": "llm",
"was_in_llm_skills": true
},
{
"aliases_in_db": [],
"canonical": null,
"dimensions": [],
"input_skill": "Salesforce",
"matched_via": null,
"new_alias_persisted": false,
"new_alias_text": null,
"new_skill_meta": {
"derived": {
"category": "CRM Platforms",
"skill_nature": "PLATFORM",
"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": "salesforce",
"split_log": [],
"typed": null,
"warnings": []
},
"source_tag": "llm",
"was_in_llm_skills": true
},
{
"aliases_in_db": [],
"canonical": null,
"dimensions": [],
"input_skill": "HubSpot",
"matched_via": null,
"new_alias_persisted": false,
"new_alias_text": null,
"new_skill_meta": {
"derived": {
"category": "CRM Platforms",
"skill_nature": "PLATFORM",
"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": "hubspot",
"split_log": [],
"typed": null,
"warnings": []
},
"source_tag": "llm",
"was_in_llm_skills": true
},
{
"aliases_in_db": [
{
"alias_text": "Serverless Framework",
"alias_type": "CANONICAL",
"id": 1345,
"is_primary": true,
"match_strategy": "CASE_INSENSITIVE"
}
],
"canonical": {
"category_id": 5,
"display_name": "Serverless Framework",
"id": 800,
"is_also_category": false,
"is_extractable": true,
"skill_nature": "FRAMEWORK",
"slug": "serverless-framework",
"sub_category_id": 145,
"typical_lifespan": "EVERGREEN",
"volatility": "STABLE"
},
"dimensions": [
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Infrastructure as Code",
"id": 132,
"rationale": "Declarative provisioning and environment definition tools used to codify cloud infrastructure, repeatable environments, and platform standards. Cloud Architects use these to express reference architectures and guardrails.",
"slug": "infrastructure-as-code",
"source": "db"
},
"input_skill": "Serverless",
"llm_role": null,
"roles_from_db": [
{
"display_name": "Cloud Architect",
"id": 9,
"rationale": null,
"role_archetype": null,
"slug": "cloud-architect",
"source": "db"
},
{
"display_name": "DevOps Engineer",
"id": 10,
"rationale": null,
"role_archetype": null,
"slug": "devops-engineer",
"source": "db"
}
]
}
],
"input_skill": "Serverless",
"matched_via": "embedding_alias",
"new_alias_persisted": false,
"new_alias_text": null,
"new_skill_meta": null,
"source_tag": "db",
"was_in_llm_skills": true
}
],
"unmatched_skills": [
"MERN",
"Insightly",
"CRM",
"Background Workers",
"Salesforce",
"HubSpot"
]
}
API 3 — final-role-output
{
"chosen_role": {
"display_name": "Fullstack Developer",
"id": 15,
"rationale": "Exact alias hit on full-stack-engineer (1.0) \u2014 no other alias at this confidence; skill_top full-stack-engineer 0.46 does not contradict",
"role_archetype": null,
"slug": "full-stack-engineer",
"source": "db"
},
"chosen_role_resolution": "in_db",
"final_input_skills": [
{
"skill": "MERN",
"tag": "new"
},
{
"skill": "Insightly",
"tag": "new"
},
{
"skill": "CRM",
"tag": "new"
},
{
"skill": "API",
"tag": "in_db"
},
{
"skill": "REST",
"tag": "in_db"
},
{
"skill": "Webhooks",
"tag": "in_db"
},
{
"skill": "React",
"tag": "in_db"
},
{
"skill": "Next.js",
"tag": "in_db"
},
{
"skill": "AWS Lambda",
"tag": "in_db"
},
{
"skill": "NoSQL",
"tag": "in_db"
},
{
"skill": "Authentication",
"tag": "in_db"
},
{
"skill": "Rate Limiting",
"tag": "in_db"
},
{
"skill": "Background Workers",
"tag": "new"
},
{
"skill": "Salesforce",
"tag": "new"
},
{
"skill": "HubSpot",
"tag": "new"
},
{
"skill": "Serverless",
"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": 15,
"dimension": {
"difficulty_hint": "well_known",
"display_name": "API Integration and Data Fetching",
"id": 127,
"rationale": "Client-side integration with backend endpoints and third-party services, including request shaping, response handling, and synchronization with UI state. This is central to frontend work because most screens depend on remote data.",
"slug": "api-integration-and-data-fetching",
"source": "db"
},
"dimension_id": 127,
"input_skill": "API",
"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": "Angular Frontend Developer",
"id": 90,
"rationale": null,
"role_archetype": "Engineering",
"slug": "angular-frontend-developer",
"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": "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"
},
{
"display_name": "Web Developer",
"id": 25,
"rationale": null,
"role_archetype": null,
"slug": "web-developer",
"source": "db"
}
],
"skill_dimension_saved": true,
"skill_id": 1568,
"skill_tag": "in_db",
"skipped_reason": null
},
{
"chosen_role_id": 15,
"dimension": {
"difficulty_hint": "well_known",
"display_name": "API Design and Contracts",
"id": 3,
"rationale": "Designing request/response shapes and the rules that govern client-server interaction. This cluster is coherent because full stack engineers often own the contract between UI behavior and backend implementation.",
"slug": "api-design-and-contracts",
"source": "db"
},
"dimension_id": 3,
"input_skill": "REST",
"llm_role": null,
"matched_chosen_role": true,
"outcome_line": "Existing dimension (library) \u00b7 Role\u2194dimension saved",
"role_dimension_saved": true,
"roles_from_db": [
{
"display_name": "Backend Developer",
"id": 1,
"rationale": null,
"role_archetype": "A Backend Engineer designs, builds, and maintains the server-side logic and data handling that power applications and services. They focus on implementing reliable business functionality, integrating with other systems, and ensuring the backend is scalable, maintainable, and observable.",
"slug": "backend-engineer",
"source": "db"
},
{
"display_name": "Fullstack Developer",
"id": 15,
"rationale": null,
"role_archetype": null,
"slug": "full-stack-engineer",
"source": "db"
}
],
"skill_dimension_saved": true,
"skill_id": 11,
"skill_tag": "in_db",
"skipped_reason": null
},
{
"chosen_role_id": 15,
"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": 15,
"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": 15,
"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": 15,
"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": 15,
"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": 15,
"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": 15,
"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": 15,
"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": 15,
"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": 15,
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Application Frameworks \u0026 Libraries",
"id": 451,
"rationale": "Covers the primary software frameworks and libraries often used alongside Sitecore for building and enhancing site experiences.",
"slug": "application-frameworks-libraries",
"source": "db"
},
"dimension_id": 451,
"input_skill": "React",
"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": 610,
"skill_tag": "in_db",
"skipped_reason": null
},
{
"chosen_role_id": 15,
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Frontend Frameworks and Libraries",
"id": 434,
"rationale": "Utilizing modern JavaScript frameworks and Shopify libraries to build dynamic and interactive storefronts.",
"slug": "frontend-frameworks-and-libraries",
"source": "db"
},
"dimension_id": 434,
"input_skill": "React",
"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": 610,
"skill_tag": "in_db",
"skipped_reason": null
},
{
"chosen_role_id": 15,
"dimension": {
"difficulty_hint": "well_known",
"display_name": "JavaScript for WordPress",
"id": 329,
"rationale": "Client-side scripting used to enhance WordPress themes, blocks, and admin/editor interactions. This includes modern JavaScript patterns as they apply to WordPress-specific behavior rather than standalone frontend applications.",
"slug": "javascript-for-wordpress",
"source": "db"
},
"dimension_id": 329,
"input_skill": "React",
"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": 610,
"skill_tag": "in_db",
"skipped_reason": null
},
{
"chosen_role_id": 15,
"dimension": {
"difficulty_hint": "well_known",
"display_name": "React Component Architecture",
"id": 302,
"rationale": "Building reusable React components, composing props and children, and managing rendering behavior across feature screens. This is the primary framework cluster for a React frontend developer.",
"slug": "react-component-architecture",
"source": "db"
},
"dimension_id": 302,
"input_skill": "React",
"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"
}
],
"skill_dimension_saved": true,
"skill_id": 610,
"skill_tag": "in_db",
"skipped_reason": null
},
{
"chosen_role_id": 15,
"dimension": {
"difficulty_hint": "well_known",
"display_name": "UI Frameworks and Rendering",
"id": 115,
"rationale": "Component frameworks and rendering models used to build browser screens, reusable UI, and interactive client flows. This is a core cluster because frontend engineers spend much of their time composing and updating view hierarchies.",
"slug": "ui-frameworks-and-rendering",
"source": "db"
},
"dimension_id": 115,
"input_skill": "React",
"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": "Frontend Developer",
"id": 7,
"rationale": null,
"role_archetype": null,
"slug": "frontend-engineer",
"source": "db"
},
{
"display_name": "Fullstack Developer",
"id": 15,
"rationale": null,
"role_archetype": null,
"slug": "full-stack-engineer",
"source": "db"
},
{
"display_name": "Hybrid Mobile Developer",
"id": 11,
"rationale": null,
"role_archetype": null,
"slug": "hybrid-mobile-developer",
"source": "db"
},
{
"display_name": "Ionic Developer",
"id": 434,
"rationale": null,
"role_archetype": null,
"slug": "ionic-developer",
"source": "db"
},
{
"display_name": "Web Developer",
"id": 25,
"rationale": null,
"role_archetype": null,
"slug": "web-developer",
"source": "db"
}
],
"skill_dimension_saved": true,
"skill_id": 610,
"skill_tag": "in_db",
"skipped_reason": null
},
{
"chosen_role_id": 15,
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Frontend Frameworks and Libraries",
"id": 434,
"rationale": "Utilizing modern JavaScript frameworks and Shopify libraries to build dynamic and interactive storefronts.",
"slug": "frontend-frameworks-and-libraries",
"source": "db"
},
"dimension_id": 434,
"input_skill": "Next.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": "Shopify Dev",
"id": 230,
"rationale": null,
"role_archetype": "Engineering",
"slug": "shopify-dev",
"source": "db"
}
],
"skill_dimension_saved": true,
"skill_id": 705,
"skill_tag": "in_db",
"skipped_reason": null
},
{
"chosen_role_id": 15,
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Meta-Frameworks \u0026 SSR",
"id": 130,
"rationale": "Frameworks that build on UI libraries to provide routing, server-side rendering, and static site generation.",
"slug": "meta-frameworks-ssr",
"source": "db"
},
"dimension_id": 130,
"input_skill": "Next.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": "Frontend Developer",
"id": 7,
"rationale": null,
"role_archetype": null,
"slug": "frontend-engineer",
"source": "db"
},
{
"display_name": "Web Developer",
"id": 25,
"rationale": null,
"role_archetype": null,
"slug": "web-developer",
"source": "db"
}
],
"skill_dimension_saved": true,
"skill_id": 705,
"skill_tag": "in_db",
"skipped_reason": null
},
{
"chosen_role_id": 15,
"dimension": {
"difficulty_hint": "well_known",
"display_name": "UI Frameworks and Rendering",
"id": 115,
"rationale": "Component frameworks and rendering models used to build browser screens, reusable UI, and interactive client flows. This is a core cluster because frontend engineers spend much of their time composing and updating view hierarchies.",
"slug": "ui-frameworks-and-rendering",
"source": "db"
},
"dimension_id": 115,
"input_skill": "Next.js",
"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": "Frontend Developer",
"id": 7,
"rationale": null,
"role_archetype": null,
"slug": "frontend-engineer",
"source": "db"
},
{
"display_name": "Fullstack Developer",
"id": 15,
"rationale": null,
"role_archetype": null,
"slug": "full-stack-engineer",
"source": "db"
},
{
"display_name": "Hybrid Mobile Developer",
"id": 11,
"rationale": null,
"role_archetype": null,
"slug": "hybrid-mobile-developer",
"source": "db"
},
{
"display_name": "Ionic Developer",
"id": 434,
"rationale": null,
"role_archetype": null,
"slug": "ionic-developer",
"source": "db"
},
{
"display_name": "Web Developer",
"id": 25,
"rationale": null,
"role_archetype": null,
"slug": "web-developer",
"source": "db"
}
],
"skill_dimension_saved": true,
"skill_id": 705,
"skill_tag": "in_db",
"skipped_reason": null
},
{
"chosen_role_id": 15,
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Cloud Platforms",
"id": 20,
"rationale": "Underlying cloud providers that host the managed services or infrastructure used by the role, such as AWS, Azure, and GCP.",
"slug": "cloud-platforms",
"source": "db"
},
"dimension_id": 20,
"input_skill": "AWS Lambda",
"llm_role": null,
"matched_chosen_role": true,
"outcome_line": "Existing dimension (library) \u00b7 Role\u2194dimension saved",
"role_dimension_saved": true,
"roles_from_db": [
{
"display_name": ".NET Backend Developer",
"id": 83,
"rationale": null,
"role_archetype": "Engineering",
"slug": "dotnet-backend-developer",
"source": "db"
},
{
"display_name": "Backend Developer",
"id": 1,
"rationale": null,
"role_archetype": "A Backend Engineer designs, builds, and maintains the server-side logic and data handling that power applications and services. They focus on implementing reliable business functionality, integrating with other systems, and ensuring the backend is scalable, maintainable, and observable.",
"slug": "backend-engineer",
"source": "db"
},
{
"display_name": "Cyber Security Engineer",
"id": 5,
"rationale": null,
"role_archetype": null,
"slug": "cybersecurity-engineer",
"source": "db"
},
{
"display_name": "Data Engineer",
"id": 2,
"rationale": null,
"role_archetype": null,
"slug": "data-engineer",
"source": "db"
},
{
"display_name": "DevOps Engineer",
"id": 10,
"rationale": null,
"role_archetype": null,
"slug": "devops-engineer",
"source": "db"
},
{
"display_name": "Fullstack Developer",
"id": 15,
"rationale": null,
"role_archetype": null,
"slug": "full-stack-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": "Kotlin Backend Developer",
"id": 84,
"rationale": null,
"role_archetype": "Engineering",
"slug": "kotlin-server-backend-developer",
"source": "db"
},
{
"display_name": "ML Engineer",
"id": 3,
"rationale": null,
"role_archetype": null,
"slug": "ml-engineer",
"source": "db"
},
{
"display_name": "MLOps Engineer",
"id": 16,
"rationale": null,
"role_archetype": null,
"slug": "ml-ops-engineer",
"source": "db"
},
{
"display_name": "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": "Scala Backend Developer",
"id": 87,
"rationale": null,
"role_archetype": "Engineering",
"slug": "scala-backend-developer",
"source": "db"
}
],
"skill_dimension_saved": true,
"skill_id": 2295,
"skill_tag": "in_db",
"skipped_reason": null
},
{
"chosen_role_id": 15,
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Cloud Platforms \u0026 Hosting Providers",
"id": 278,
"rationale": "Familiarity with vendor-specific hosting and backend services for deploying and scaling web applications.",
"slug": "cloud-platforms-hosting-providers",
"source": "db"
},
"dimension_id": 278,
"input_skill": "AWS Lambda",
"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": "Kotlin Backend Developer",
"id": 84,
"rationale": null,
"role_archetype": "Engineering",
"slug": "kotlin-server-backend-developer",
"source": "db"
},
{
"display_name": "Scala Backend Developer",
"id": 87,
"rationale": null,
"role_archetype": "Engineering",
"slug": "scala-backend-developer",
"source": "db"
},
{
"display_name": "Web Developer",
"id": 25,
"rationale": null,
"role_archetype": null,
"slug": "web-developer",
"source": "db"
}
],
"skill_dimension_saved": true,
"skill_id": 2295,
"skill_tag": "in_db",
"skipped_reason": null
},
{
"chosen_role_id": 15,
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Cloud Platforms \u0026 Managed Services",
"id": 221,
"rationale": "Operates and integrates vendor-specific cloud compute, storage, and hosting services.",
"slug": "cloud-platforms-managed-services",
"source": "db"
},
"dimension_id": 221,
"input_skill": "AWS Lambda",
"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": "Fullstack Developer",
"id": 15,
"rationale": null,
"role_archetype": null,
"slug": "full-stack-engineer",
"source": "db"
},
{
"display_name": "Go Backend Developer",
"id": 81,
"rationale": null,
"role_archetype": "Engineering",
"slug": "go-backend-developer",
"source": "db"
},
{
"display_name": "Node.js Backend Developer",
"id": 82,
"rationale": null,
"role_archetype": "Engineering",
"slug": "node-backend-developer",
"source": "db"
}
],
"skill_dimension_saved": true,
"skill_id": 2295,
"skill_tag": "in_db",
"skipped_reason": null
},
{
"chosen_role_id": 15,
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Cloud Platforms \u0026 Services",
"id": 296,
"rationale": "Deploying, configuring, and managing Python backends on major cloud and PaaS offerings.",
"slug": "cloud-platforms-services",
"source": "db"
},
"dimension_id": 296,
"input_skill": "AWS Lambda",
"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": "Python Backend Developer",
"id": 80,
"rationale": null,
"role_archetype": "Engineering",
"slug": "python-backend-developer",
"source": "db"
}
],
"skill_dimension_saved": true,
"skill_id": 2295,
"skill_tag": "in_db",
"skipped_reason": null
},
{
"chosen_role_id": 15,
"dimension": {
"difficulty_hint": "well_known",
"display_name": "NoSQL Databases",
"id": 19,
"rationale": "Models and manages data using non-relational database systems.",
"slug": "nosql-databases",
"source": "db"
},
"dimension_id": 19,
"input_skill": "NoSQL",
"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"
}
],
"skill_dimension_saved": true,
"skill_id": 1346,
"skill_tag": "in_db",
"skipped_reason": null
},
{
"chosen_role_id": 15,
"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": "Authentication",
"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": 1608,
"skill_tag": "in_db",
"skipped_reason": null
},
{
"chosen_role_id": 15,
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Backend Security Hardening",
"id": 16,
"rationale": "Security practices specific to server-side application code and service exposure. Focuses on protecting backend endpoints, secrets, and data handling from common application-layer threats.",
"slug": "backend-security-hardening",
"source": "db"
},
"dimension_id": 16,
"input_skill": "Rate Limiting",
"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": "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": 2357,
"skill_tag": "in_db",
"skipped_reason": null
},
{
"chosen_role_id": 15,
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Infrastructure as Code",
"id": 132,
"rationale": "Declarative provisioning and environment definition tools used to codify cloud infrastructure, repeatable environments, and platform standards. Cloud Architects use these to express reference architectures and guardrails.",
"slug": "infrastructure-as-code",
"source": "db"
},
"dimension_id": 132,
"input_skill": "Serverless",
"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": "Cloud Architect",
"id": 9,
"rationale": null,
"role_archetype": null,
"slug": "cloud-architect",
"source": "db"
},
{
"display_name": "DevOps Engineer",
"id": 10,
"rationale": null,
"role_archetype": null,
"slug": "devops-engineer",
"source": "db"
}
],
"skill_dimension_saved": false,
"skill_id": null,
"skill_tag": "new",
"skipped_reason": "skill_not_in_db_v3_proposed"
}
],
"new_skills_created": 0,
"role_dimension_saved": 0,
"skill_dimension_saved": 0,
"skipped": 1
},
"planner_output": null,
"run_id": "4afaa014-842c-4908-a6ec-fc860ddc44d7"
}
LLM Calls
Every model call made for this run, in pipeline order. Click a card to see the model's response.