Pipeline run
60479782-ae35-4185-9f9d-e76a25bd3b96
Pipeline LLM cost (USD)
API 1: $0.0107
API 2: $0.0003
API 3: $0.0000
Total: $0.0110
Client output enrichment
v2 Skill cluster · Nature of work · AI index · Tech stack maturity · Evidence · KRA description
role baseline loaded
sources · ai_index: jd · nature_of_work: jd · tech_stack_maturity: jd
Nature of work
· Responsive UI component development
Build and maintain accessible React/TypeScript web components, shape their design/architecture with product teams, and test, release, and fix production issues to deliver polished user experiences.
""Actively participate in the design and architecture of our web components, and tools""
Tech stack maturity
Mainstream Modern
The stack centers on React and TypeScript with REST and gRPC, which are widely used current technologies but not specifically cloud-native or legacy.
AI index (0 = no AI use, 5 = totally AI-dependent · v2.1)
0.00 / 5
· Title match
· Has AI skill
· AI skill (primary)
· AI skill (secondary)
· On AI team
· Builds AI products
vocab breakdown (legacy)
Assistants (×1):
—
Frameworks (×2):
—
Models / concepts (×3):
—
Evidence — skills matched in JD (12)
TypeScript
React
Agile
Test-driven development
REST
gRPC
XML Schema
JSON Schema
version control
build process
testing
code release
Skill cluster (6 dimension groups, role-scoped)
API Standards and Protocols
gRPC
Data Serialization Standards & Protocols
JSON Schema
Integration Protocols & Standards
REST
JavaScript and TypeScript
TypeScript
UI Frameworks and Rendering
React
Cross-cutting / unaligned
Agile
Test-driven development
XML Schema
version control
build process
testing
code release
Show KRA description ↓
• Write accessible code that is easy to maintain and test.
• Actively participate in the design and architecture of our web components, and tools
• Work with Project Management and other product teams to elicit design requirements
• Work as part of a passionate, agile development team to deliver engaging user experiences
• Fix production issues and maintain the code as needed
Basic qualifications
• 5- 8 years development experience
• Experience working with TypeScript and the React framework
• Experience building reusable front-end components
• Experience with front-end testing libraries
Preferred qualifications
• Experience delivering a SaaS product
• Be open minded, forward thinking, and passionate about great software
• Experience with the entire software development lifecycle, including version control, build process, testing, and code release
• Experience with data modeling or schema languages, such as XML Schema or JSON Schema.
• Agile and Test-driven development methodologies
• Experience building/consuming RESTful or gRPC web-services
• Strong communication skills, particularly in an asynchronous environment
Signals
Skill
full-stack-engineer
0.67
Alias
frontend-engineer
1.00
KRA
flutter-developer
0.60
Post-classification
Centroidupdated · n=98
Alias collision log—
New-role queue—
New skills captured6
New KRA captured—
Captured for admin review
Test-driven development
primary
↔
Frontend Developer
pending
XML Schema
↔
Frontend Developer
pending
version control
↔
Frontend Developer
pending
build process
↔
Frontend Developer
pending
testing
↔
Frontend Developer
pending
code release
↔
Frontend Developer
pending
Status:
completed
Created: 2026-05-27T13:58:32.640556Z
Updated: 2026-05-27T14:00:03.820833Z
API 3 duration: 40811 ms
Flow
Current 3-step pipeline
1 POST /skills/extract-from-jd
2 POST /skills/extract-details
3 POST /skills/final-role-output
Role
Chosen role & resolution
Frontend Developer
→React Frontend Developer
sub-role · 0.99 domain · Software Engineering CASE DOMAINslug: frontend-engineer · id: 7 · source: db · sub-role slug: react-frontend-developer
Domain=Software Engineering → sub-role react-frontend-developer; The JD is clearly for a React/TypeScript frontend role focused on reusable web components, testing, and user experience delivery.
Matched skills
TypeScriptReactfront-end testing librariesreusable front-end componentsweb componentsXML SchemaJSON SchemaRESTfulgRPCversion controlbuild processtestingcode releaseAgileTest-driven development
Matched dimensions
Frontend component architectureAccessible UI developmentUser experience deliveryFrontend testing and maintainabilityAgile product developmentSoftware development lifecycle
Matched KRAs
Write accessible code that is easy to maintain and testParticipate in the design and architecture of web componentsElicit design requirements with Project Management and product teamsDeliver engaging user experiencesFix production issues and maintain the code
Resolution:
in_db
— role exists in library; skill↔dim and role↔dim links saved when applicable.
0
New skills
0
Skill↔dim saved
0
Role↔dim saved
0
Skipped
Job description
As a Frontend software development engineer on a DocuSign team you will be responsible for building foundational web-components and web-based tools for our next-generation agreement platform. Your solutions will be used by multiple DocuSign product teams, partners and customers. The successful candidate will have a strong product engineering background and proficiency in front-end React development with TypeScript. You’ll enjoy entrepreneurial environments where you can solve difficult problems using current technologies and tools. You’ll collaborate well with other team members when brainstorming, designing, and implementing new solutions. You will help the team succeed by thinking about ways to improve processes, suggest ways to make the team more effective, and model engineering best practices. As a member of the Platform engineering group, you will work closely with product managers, developers, and platform engineers to ensure high quality and timely product releases. You are a hands-on technical person who will be responsible for issues related to product features, performance, speed, scale, security and accessibility.This position is an individual contributor role reporting to the Director of Engineering and is designated Hybrid. Responsibilities • Write accessible code that is easy to maintain and test. • Actively participate in the design and architecture of our web components, and tools • Work with Project Management and other product teams to elicit design requirements • Work as part of a passionate, agile development team to deliver engaging user experiences • Fix production issues and maintain the code as needed What you will bring Basic qualifications • 5- 8 years development experience • Experience working with TypeScript and the React framework • Experience building reusable front-end components • Experience with front-end testing libraries Preferred qualifications • Experience delivering a SaaS product • Be open minded, forward thinking, and passionate about great software • Experience with the entire software development lifecycle, including version control, build process, testing, and code release • Experience with data modeling or schema languages, such as XML Schema or JSON Schema. • Agile and Test-driven development methodologies • Experience building/consuming RESTful or gRPC web-services • Strong communication skills, particularly in an asynchronous environment
Skills from this JD
Each row merges API 1 extraction, API 2 library match / v3 orchestration (dimensions + locked dims), and API 3 persistence tags.
TypeScript
Primary
Library skill
API 3: existing canonical (in_db)
Existing skill (matched library)
Canonical: TypeScript
id=524
· typescript
Aliases — catalog
- TypeScript (CANONICAL) primary
- TypeScript 5 (VERSION)
- TypeScript 5.x (VERSION)
- ts (VERSION)
- ts5 (VERSION)
- typescript 5 (VERSION)
- typescript 5.x (VERSION)
- typescript5 (VERSION)
Context tags (catalog)
Angular
Async/Await
Decorator
Deno
ESLint
Generics
GraphQL
Interfaces
JavaScript
Jest
NestJS
Next.js
Node.js
Promise
React
Redux
RxJS
TypeORM
Vite
Vue
Vue.js
Webpack
async/await
decorators
generics
interfaces
module resolution
npm
strict mode
tsconfig
type annotations
type guards
type inference
type safety
yarn
Stored enrichment (catalog DB)
- Category
- Language
- Sub-category
- Programming Language
- Vendor
- Microsoft
- License
- apache_2
- Year introduced
- 2012
- Confidence
- 0.99
- Version strategy
- NOT_APPLICABLE
Maturity reasoning: TypeScript is a hiring-pipeline staple: it appears in a large share of modern web/frontend and Node.js job descriptions, and major frameworks like Angular and Next.js recommend it by default.
Skill profile (library / DB)
- Skill nature
- LANGUAGE
- Volatility
- STABLE
- Typical lifespan
- EVERGREEN
- Category id
- 6
- Sub-category id
- 96
- Extractable
- True
- Also category
- False
Dimensions (API 2 worklist)
-
Cross-Platform App Languages Catalog dimension db id 167
Library dimension (catalog)
Roles linked in library: Hybrid Mobile Developer
-
JavaScript and TypeScript Catalog dimension db id 114
Library dimension (catalog)
Roles linked in library: Angular Frontend Developer, Frontend Developer, Ionic Developer, Node.js Backend Developer, React Frontend Developer, React Native Developer, Svelte Frontend Developer, Vue Frontend Developer, Web Developer
-
Programming Languages Catalog dimension db id 1
Library dimension (catalog)
Roles linked in library: Backend Developer, Fullstack Developer
-
Programming Languages for XR Catalog dimension db id 97
Library dimension (catalog)
Roles linked in library: AR/VR Engineer
-
Sitecore Development Languages Catalog dimension db id 438
Library dimension (catalog)
Roles linked in library: Sitecore Dev
API 3 link attempts (this skill)
| Dimension | Skill↔dim | Role↔dim | Outcome |
|---|---|---|---|
|
Cross-Platform App Languages
cross-platform-app-languages
|
✓ | — | Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role) |
|
JavaScript and TypeScript
javascript-and-typescript
|
✓ | ✓ | Existing dimension (library) · Role↔dimension saved |
|
Programming Languages
programming-languages
|
✓ | — | Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role) |
|
Programming Languages for XR
programming-languages-for-xr
|
✓ | — | Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role) |
|
Sitecore Development Languages
sitecore-development-languages
|
✓ | — | Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role) |
React
Primary
Library skill
API 3: existing canonical (in_db)
Existing skill (matched library)
Canonical: React
id=610
· react
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)
Babel
Class Components
Component Lifecycle
Context API
Functional Components
Higher-Order Components
Hooks
JSX
Next.js
PropTypes
Props
React Native
React Router
Redux
SSR
State Management
Styled Components
Testing Library
TypeScript
Virtual DOM
Webpack
component lifecycle
context API
frontend
hooks
props
state management
useEffect
useState
virtual DOM
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 |
Agile
Primary
Library skill
API 3: existing canonical (in_db)
Existing skill (matched library)
Canonical: Agile
id=520
· agile
Aliases — catalog
- Agile (CANONICAL) primary
Context tags (catalog)
Kanban
SAFe
Scrum
backlog
backlog grooming
burndown
burndown chart
continuous delivery
continuous improvement
cross-functional
daily standup
epics
incremental development
iteration
iteration planning
lean
product backlog
product owner
retrospective
sprint
sprint planning
stand-up
story points
user stories
velocity
Stored enrichment (catalog DB)
- Category
- Methodology
- Sub-category
- Agile
- Confidence
- 0.99
- Version strategy
- NOT_APPLICABLE
Maturity reasoning: Agile appears in a large share of software job descriptions and is a standard hiring-pipeline requirement; Scrum/Kanban are commonly listed alongside it, showing broad market adoption.
Skill profile (library / DB)
- Skill nature
- METHODOLOGY
- Volatility
- STABLE
- Typical lifespan
- EVERGREEN
- Category id
- 8
- Sub-category id
- 367
- Extractable
- True
- Also category
- False
Dimensions (API 2 worklist)
-
React Frontend Development Catalog dimension db id 96
Library dimension (catalog)
API 3 link attempts (this skill)
| Dimension | Skill↔dim | Role↔dim | Outcome |
|---|---|---|---|
|
React Frontend Development
d_init_01
|
✓ | — | Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role) |
Test-driven development
Primary
New / orchestrated
API 3: new canonical path (new)
New / unmatched skill (orchestrated in API 2)
Skill enrichment (orchestrator / LLM)
No Stage 7 enrichment blob on this skill (orchestrator skipped enrichment).
Derived legacy fields
- Category
- Soft Skills
- Sub-category
- general
- Skill nature
- PRACTICE
- Volatility
- MEDIUM
- Typical lifespan
- MULTI_YEAR
- Version strategy
- UNVERSIONED
REST
Primary
Library skill
API 3: existing canonical (in_db)
Existing skill (matched library)
Canonical: REST
id=11
· rest
Aliases — catalog
- REST (CANONICAL) primary
Context tags (catalog)
API
API design
API versioning
CRUD
DELETE
GET
HATEOAS
HTTP
JSON
OAuth
OAuth2
OpenAPI
POST
PUT
Postman
RESTful
Swagger
URI
Webhooks
XML
authentication
client-server
content negotiation
endpoint
endpoints
middleware
resource
resource-oriented
serialization
stateless
status codes
versioning
web services
Stored enrichment (catalog DB)
- Category
- Concept
- Sub-category
- Api Architecture Style
- Year introduced
- 2000
- Confidence
- 0.88
- Version strategy
- NOT_APPLICABLE
Maturity reasoning: REST is a default API architecture in many job descriptions and is widely supported by major vendors/frameworks; OpenAPI and RESTful endpoints remain standard in hiring pipelines.
Skill profile (library / DB)
- Skill nature
- CONCEPT
- Volatility
- STABLE
- Typical lifespan
- EVERGREEN
- Category id
- 2
- Sub-category id
- 2122
- Extractable
- True
- Also category
- False
Dimensions (API 2 worklist)
-
API Design and Contracts Catalog dimension db id 3
Library dimension (catalog)
Roles linked in library: Backend Developer, Fullstack Developer
-
API Interface and Contract Design Catalog dimension db id 289
Library dimension (catalog)
Roles linked in library: .NET Backend Developer, Go Backend Developer, Kotlin Backend Developer, Node.js Backend Developer, PHP Backend Developer, Python Backend Developer, Ruby Backend Developer, Scala Backend Developer
-
Integration Protocols & Standards Catalog dimension db id 271
Library dimension (catalog)
Roles linked in library: Pega Developer
-
Standards & Protocols Compliance Catalog dimension db id 452
Library dimension (catalog)
Roles linked in library: Sitecore Dev
API 3 link attempts (this skill)
| Dimension | Skill↔dim | Role↔dim | Outcome |
|---|---|---|---|
|
API Design and Contracts
api-design-and-contracts
|
✓ | — | Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role) |
|
API Interface and Contract Design
api-interface-and-contract-design
|
✓ | — | Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role) |
|
Integration Protocols & Standards
integration-protocols-standards
|
✓ | — | Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role) |
|
Standards & Protocols Compliance
standards-protocols-compliance
|
✓ | — | Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role) |
gRPC
Primary
Library skill
API 3: existing canonical (in_db)
Existing skill (matched library)
Canonical: gRPC
id=13
· grpc
Aliases — catalog
- gRPC (CANONICAL) primary
Context tags (catalog)
API
HTTP/2
IDL
Protocol Buffers
asynchronous
authentication
bidirectional streaming
caching
cancellation
circuit breaker
client library
client-server
client-side load balancing
code generation
deadline
deadline propagation
deadlines
gRPC Gateway
gRPC-Web
inter-service communication
interceptors
interoperability
load balancing
mTLS
metadata
microservices
middleware
protobuf
reflection
server streaming
service definition
service discovery
service mesh
stub generation
unary RPC
Stored enrichment (catalog DB)
- Category
- Protocol
- Sub-category
- Rpc Protocol
- Vendor
- License
- apache_2
- Year introduced
- 2015
- Confidence
- 0.98
- Version strategy
- NOT_APPLICABLE
Maturity reasoning: gRPC appears frequently in backend/microservices job descriptions and is widely supported by major vendors (Google, Cloud providers, Envoy), indicating broad adoption rather than niche use.
Skill profile (library / DB)
- Skill nature
- PROTOCOL
- Volatility
- STABLE
- Typical lifespan
- EVERGREEN
- Category id
- 10
- Sub-category id
- 52
- 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
-
API Standards and Protocols Catalog dimension db id 318
Library dimension (catalog)
Roles linked in library: Flutter Developer
-
Mobile Protocols & Standards Catalog dimension db id 277
Library dimension (catalog)
Roles linked in library: Native Mobile Developer
API 3 link attempts (this skill)
| Dimension | Skill↔dim | Role↔dim | Outcome |
|---|---|---|---|
|
API Design and Contracts
api-design-and-contracts
|
✓ | — | Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role) |
|
API Interface and Contract Design
api-interface-and-contract-design
|
✓ | — | Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role) |
|
API Standards and Protocols
api-standards-and-protocols
|
✓ | — | Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role) |
|
Mobile Protocols & Standards
mobile-protocols-standards
|
✓ | — | Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role) |
XML Schema
Secondary
New / orchestrated
API 3: new canonical path (new)
New / unmatched skill (orchestrated in API 2)
Skill enrichment (orchestrator / LLM)
No Stage 7 enrichment blob on this skill (orchestrator skipped enrichment).
Derived legacy fields
- Category
- Markup Languages
- Sub-category
- general
- Skill nature
- LANGUAGE
- Volatility
- MEDIUM
- Typical lifespan
- MULTI_YEAR
- Version strategy
- UNVERSIONED
JSON Schema
Secondary
Library skill
API 3: existing canonical (in_db)
Existing skill (matched library)
Canonical: JSON schema
id=15
· json-schema
Aliases — catalog
- JSON schema (CANONICAL) primary
- 2019-09 (VERSION)
- 2020-12 (VERSION)
- JSON Schema (CANONICAL)
- JSON Schema 2019-09 (VERSION)
- JSON Schema 2020-12 (VERSION)
- JSON Schema Draft 4 (VERSION)
- JSON Schema Draft 6 (VERSION)
- JSON Schema Draft 7 (VERSION)
- draft-04 (VERSION)
- draft-06 (VERSION)
- draft-07 (VERSION)
Context tags (catalog)
$ref
$schema
AJV
JSON Pointer
JSON-LD
OpenAPI
OpenAPI Specification
Swagger
UI validation
YAML
allOf
anyOf
data interchange
data modeling
data validation
definitions
draft-07
draft-2020-12
enum
format validation
hyper-schema
oneOf
properties
required
schema design
schema documentation
schema evolution
schema generation
schema reference
schema repository
schema validation
type definitions
type validation
validation
Stored enrichment (catalog DB)
- Category
- Standard
- Sub-category
- Schema Specification Standard
- Vendor
- IETF
- License
- other_open
- Year introduced
- 2013
- Confidence
- 0.96
- Version strategy
- NOT_APPLICABLE
Maturity reasoning: JSON Schema appears in many API, validation, and OpenAPI-related job descriptions and is supported by major vendors/libraries (e.g., Ajv, OpenAPI tooling), indicating broad market adoption.
Skill profile (library / DB)
- Skill nature
- STANDARD
- Volatility
- STABLE
- Typical lifespan
- EVERGREEN
- Category id
- 12
- Sub-category id
- 1789
- 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
-
Data Serialization Standards & Protocols Catalog dimension db id 37
Library dimension (catalog)
Roles linked in library: Data Engineer
API 3 link attempts (this skill)
| Dimension | Skill↔dim | Role↔dim | Outcome |
|---|---|---|---|
|
API Design and Contracts
api-design-and-contracts
|
✓ | — | Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role) |
|
API Interface and Contract Design
api-interface-and-contract-design
|
✓ | — | Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role) |
|
Data Serialization Standards & Protocols
data-serialization-standards-protocols
|
✓ | — | Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role) |
version control
Secondary
New / orchestrated
API 3: new canonical path (new)
New / unmatched skill (orchestrated in API 2)
Skill enrichment (orchestrator / LLM)
No Stage 7 enrichment blob on this skill (orchestrator skipped enrichment).
Derived legacy fields
- Category
- DevOps Tools
- Sub-category
- general
- Skill nature
- PRACTICE
- Volatility
- MEDIUM
- Typical lifespan
- MULTI_YEAR
- Version strategy
- UNVERSIONED
build process
Secondary
New / orchestrated
API 3: new canonical path (new)
New / unmatched skill (orchestrated in API 2)
Skill enrichment (orchestrator / LLM)
No Stage 7 enrichment blob on this skill (orchestrator skipped enrichment).
Derived legacy fields
- Category
- DevOps Tools
- Sub-category
- general
- Skill nature
- PRACTICE
- Volatility
- MEDIUM
- Typical lifespan
- MULTI_YEAR
- Version strategy
- UNVERSIONED
testing
Secondary
New / orchestrated
API 3: new canonical path (new)
New / unmatched skill (orchestrated in API 2)
Skill enrichment (orchestrator / LLM)
No Stage 7 enrichment blob on this skill (orchestrator skipped enrichment).
Derived legacy fields
- Category
- Testing Tools
- Sub-category
- general
- Skill nature
- PRACTICE
- Volatility
- MEDIUM
- Typical lifespan
- MULTI_YEAR
- Version strategy
- UNVERSIONED
code release
Secondary
New / orchestrated
API 3: new canonical path (new)
New / unmatched skill (orchestrated in API 2)
Skill enrichment (orchestrator / LLM)
No Stage 7 enrichment blob on this skill (orchestrator skipped enrichment).
Derived legacy fields
- Category
- DevOps Tools
- Sub-category
- general
- Skill nature
- PRACTICE
- Volatility
- MEDIUM
- Typical lifespan
- MULTI_YEAR
- Version strategy
- UNVERSIONED
All API 3 persistence rows
Same grid as the skill-extractor “Persistence items” table: one row per (skill × dimension) work item.
| Skill | Tag | Dimension | Skill↔dim | Role↔dim | Outcome | Notes |
|---|---|---|---|---|---|---|
| TypeScript | in_db |
Cross-Platform App Languages
cross-platform-app-languages
|
✓ | — | Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role) | |
| TypeScript | in_db |
JavaScript and TypeScript
javascript-and-typescript
|
✓ | ✓ | Existing dimension (library) · Role↔dimension saved | |
| TypeScript | in_db |
Programming Languages
programming-languages
|
✓ | — | Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role) | |
| TypeScript | in_db |
Programming Languages for XR
programming-languages-for-xr
|
✓ | — | Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role) | |
| TypeScript | in_db |
Sitecore Development Languages
sitecore-development-languages
|
✓ | — | 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 | |
| Agile | in_db |
React Frontend Development
d_init_01
|
✓ | — | Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role) | |
| REST | in_db |
API Design and Contracts
api-design-and-contracts
|
✓ | — | Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role) | |
| REST | in_db |
API Interface and Contract Design
api-interface-and-contract-design
|
✓ | — | Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role) | |
| REST | in_db |
Integration Protocols & Standards
integration-protocols-standards
|
✓ | — | Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role) | |
| REST | in_db |
Standards & Protocols Compliance
standards-protocols-compliance
|
✓ | — | Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role) | |
| gRPC | in_db |
API Design and Contracts
api-design-and-contracts
|
✓ | — | Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role) | |
| gRPC | in_db |
API Interface and Contract Design
api-interface-and-contract-design
|
✓ | — | Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role) | |
| gRPC | in_db |
API Standards and Protocols
api-standards-and-protocols
|
✓ | — | Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role) | |
| gRPC | in_db |
Mobile Protocols & Standards
mobile-protocols-standards
|
✓ | — | Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role) | |
| JSON Schema | in_db |
API Design and Contracts
api-design-and-contracts
|
✓ | — | Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role) | |
| JSON Schema | in_db |
API Interface and Contract Design
api-interface-and-contract-design
|
✓ | — | Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role) | |
| JSON Schema | in_db |
Data Serialization Standards & Protocols
data-serialization-standards-protocols
|
✓ | — | Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role) |
Library artifacts (this run)
| Kind | Detail | DB id |
|---|---|---|
| canonical_skill_proposed | Test-driven development | type=Soft Skills subtype=general nature=PRACTICE lifespan=MULTI_YEAR | |
| canonical_skill_proposed | XML Schema | type=Markup Languages subtype=general nature=LANGUAGE lifespan=MULTI_YEAR | |
| canonical_skill_proposed | version control | type=DevOps Tools subtype=general nature=PRACTICE lifespan=MULTI_YEAR | |
| canonical_skill_proposed | build process | type=DevOps Tools subtype=general nature=PRACTICE lifespan=MULTI_YEAR | |
| canonical_skill_proposed | testing | type=Testing Tools subtype=general nature=PRACTICE lifespan=MULTI_YEAR | |
| canonical_skill_proposed | code release | type=DevOps Tools subtype=general nature=PRACTICE lifespan=MULTI_YEAR |
nano JD Parser — gpt-4.1-nano click to toggle
RoleFrontend Software Development Engineer
CompanyDocuSign
Experience5-8 years development experience
DomainSoftware & SaaS Products
Location
—
(hybrid)
JD type
pass
Show raw JSON
{
"JD_type": "pass",
"about_company": null,
"certifications": [],
"company_name": "DocuSign",
"ctc": null,
"domain": {
"primary": {
"aliases": [
"SaaS",
"Software Products"
],
"domain": "Software \u0026 SaaS Products"
},
"secondary": null
},
"education": [],
"experience": {
"max": 8,
"min": 5,
"raw": "5-8 years development experience"
},
"job_locations": [
{
"aliases": [],
"city": null,
"country": null,
"state": null,
"work_mode": "hybrid"
}
],
"role": "Frontend Software Development Engineer",
"role_aliases": [
"Frontend Engineer",
"Frontend Developer",
"Software Engineer"
],
"role_archetype": "Engineering",
"roles_and_responsibilities": [
{
"bullet_count": 5,
"heading": "Responsibilities",
"heading_was_present": true,
"source_marker": {
"first_5_words": "\u2022 Write accessible code that",
"last_5_words": "and maintain the code as needed"
},
"text": "\u2022 Write accessible code that is easy to maintain and test.\n\u2022 Actively participate in the design and architecture of our web components, and tools\n\u2022 Work with Project Management and other product teams to elicit design requirements\n\u2022 Work as part of a passionate, agile development team to deliver engaging user experiences\n\u2022 Fix production issues and maintain the code as needed",
"word_count": 47
},
{
"bullet_count": 12,
"heading": "What you will bring",
"heading_was_present": true,
"source_marker": {
"first_5_words": "Basic qualifications\n\u2022 5- 8 years",
"last_5_words": "in an asynchronous environment"
},
"text": "Basic qualifications\n\u2022 5- 8 years development experience\n\u2022 Experience working with TypeScript and the React framework\n\u2022 Experience building reusable front-end components\n\u2022 Experience with front-end testing libraries\n\nPreferred qualifications\n\u2022 Experience delivering a SaaS product\n\u2022 Be open minded, forward thinking, and passionate about great software\n\u2022 Experience with the entire software development lifecycle, including version control, build process, testing, and code release\n\u2022 Experience with data modeling or schema languages, such as XML Schema or JSON Schema.\n\u2022 Agile and Test-driven development methodologies\n\u2022 Experience building/consuming RESTful or gRPC web-services\n\u2022 Strong communication skills, particularly in an asynchronous environment",
"word_count": 134
}
],
"urls": []
}
API 1 — extract-from-jd click to toggle
{
"final_skills": [
{
"is_primary": true,
"skill_name": "TypeScript"
},
{
"is_primary": true,
"skill_name": "React"
},
{
"is_primary": true,
"skill_name": "Agile"
},
{
"is_primary": true,
"skill_name": "Test-driven development"
},
{
"is_primary": true,
"skill_name": "REST"
},
{
"is_primary": true,
"skill_name": "gRPC"
},
{
"is_primary": false,
"skill_name": "XML Schema"
},
{
"is_primary": false,
"skill_name": "JSON Schema"
},
{
"is_primary": false,
"skill_name": "version control"
},
{
"is_primary": false,
"skill_name": "build process"
},
{
"is_primary": false,
"skill_name": "testing"
},
{
"is_primary": false,
"skill_name": "code release"
}
],
"jd_role": {
"display_name": "Frontend Software Development Engineer",
"rationale": null,
"role_aliases": [
"Frontend Engineer",
"Frontend Developer",
"Software Engineer"
],
"role_archetype": "Engineering",
"slug": ""
},
"nano_parsed": {
"JD_type": "pass",
"about_company": null,
"certifications": [],
"company_name": "DocuSign",
"ctc": null,
"domain": {
"primary": {
"aliases": [
"SaaS",
"Software Products"
],
"domain": "Software \u0026 SaaS Products"
},
"secondary": null
},
"education": [],
"experience": {
"max": 8,
"min": 5,
"raw": "5-8 years development experience"
},
"job_locations": [
{
"aliases": [],
"city": null,
"country": null,
"state": null,
"work_mode": "hybrid"
}
],
"role": "Frontend Software Development Engineer",
"role_aliases": [
"Frontend Engineer",
"Frontend Developer",
"Software Engineer"
],
"role_archetype": "Engineering",
"roles_and_responsibilities": [
{
"bullet_count": 5,
"heading": "Responsibilities",
"heading_was_present": true,
"source_marker": {
"first_5_words": "\u2022 Write accessible code that",
"last_5_words": "and maintain the code as needed"
},
"text": "\u2022 Write accessible code that is easy to maintain and test.\n\u2022 Actively participate in the design and architecture of our web components, and tools\n\u2022 Work with Project Management and other product teams to elicit design requirements\n\u2022 Work as part of a passionate, agile development team to deliver engaging user experiences\n\u2022 Fix production issues and maintain the code as needed",
"word_count": 47
},
{
"bullet_count": 12,
"heading": "What you will bring",
"heading_was_present": true,
"source_marker": {
"first_5_words": "Basic qualifications\n\u2022 5- 8 years",
"last_5_words": "in an asynchronous environment"
},
"text": "Basic qualifications\n\u2022 5- 8 years development experience\n\u2022 Experience working with TypeScript and the React framework\n\u2022 Experience building reusable front-end components\n\u2022 Experience with front-end testing libraries\n\nPreferred qualifications\n\u2022 Experience delivering a SaaS product\n\u2022 Be open minded, forward thinking, and passionate about great software\n\u2022 Experience with the entire software development lifecycle, including version control, build process, testing, and code release\n\u2022 Experience with data modeling or schema languages, such as XML Schema or JSON Schema.\n\u2022 Agile and Test-driven development methodologies\n\u2022 Experience building/consuming RESTful or gRPC web-services\n\u2022 Strong communication skills, particularly in an asynchronous environment",
"word_count": 134
}
],
"urls": []
},
"rejected": false,
"rejection_reason": null,
"run_id": "60479782-ae35-4185-9f9d-e76a25bd3b96",
"stage3_signals": {
"alias_found": true,
"alias_match_roles": [
{
"display_name": "Frontend Developer",
"kra_matches": null,
"matched_count": null,
"matched_skills": null,
"role_id": 7,
"score": 1.0,
"slug": "frontend-engineer",
"total_count": null
},
{
"display_name": "Web Developer",
"kra_matches": null,
"matched_count": null,
"matched_skills": null,
"role_id": 25,
"score": 1.0,
"slug": "web-developer",
"total_count": null
}
],
"kra_match_roles": [
{
"display_name": "Flutter Developer",
"kra_matches": [
{
"kra_text": "collaborate with design, product, and backend teams",
"sentence": "Work with Project Management and other product teams to elicit design requirements",
"similarity": 0.6261
},
{
"kra_text": "collaborate with design, product, and backend teams",
"sentence": "Actively participate in the design and architecture of our web components, and tools",
"similarity": 0.5897
},
{
"kra_text": "structure reusable application code",
"sentence": "Experience building reusable front-end components",
"similarity": 0.5721
}
],
"matched_count": null,
"matched_skills": null,
"role_id": 74,
"score": 0.596,
"slug": "flutter-developer",
"total_count": null
},
{
"display_name": "Fullstack Developer",
"kra_matches": [
{
"kra_text": "Works closely with product managers and UX designers to translate requirements and wireframes into working software features through iterative development.",
"sentence": "Work with Project Management and other product teams to elicit design requirements",
"similarity": 0.6503
},
{
"kra_text": "Works closely with product managers and UX designers to translate requirements and wireframes into working software features through iterative development.",
"sentence": "Work as part of a passionate, agile development team to deliver engaging user experiences",
"similarity": 0.568
},
{
"kra_text": "Builds and integrates client-side React or Vue components with server-side Node.js or Django APIs, managing bidirectional data flow across frontend and backend layers.",
"sentence": "Experience building reusable front-end components",
"similarity": 0.5629
}
],
"matched_count": null,
"matched_skills": null,
"role_id": 15,
"score": 0.5937,
"slug": "full-stack-engineer",
"total_count": null
},
{
"display_name": "Frontend Developer",
"kra_matches": [
{
"kra_text": "Builds responsive user interfaces and interactive web components using React, Vue, or Angular with TypeScript, HTML5, and modern CSS for browser-based applications.",
"sentence": "Experience working with TypeScript and the React framework",
"similarity": 0.6177
},
{
"kra_text": "Supports production releases by diagnosing cross-browser compatibility issues, investigating UI regressions, and resolving frontend performance degradation.",
"sentence": "Fix production issues and maintain the code as needed",
"similarity": 0.5831
},
{
"kra_text": "Builds responsive user interfaces and interactive web components using React, Vue, or Angular with TypeScript, HTML5, and modern CSS for browser-based applications.",
"sentence": "Experience building reusable front-end components",
"similarity": 0.5641
}
],
"matched_count": null,
"matched_skills": null,
"role_id": 7,
"score": 0.5883,
"slug": "frontend-engineer",
"total_count": null
},
{
"display_name": "React Frontend Developer",
"kra_matches": [
{
"kra_text": "compose reusable interface components",
"sentence": "Experience building reusable front-end components",
"similarity": 0.6422
},
{
"kra_text": "translate product and design requirements",
"sentence": "Work with Project Management and other product teams to elicit design requirements",
"similarity": 0.5946
},
{
"kra_text": "Implement user-facing screens and interactions",
"sentence": "Work as part of a passionate, agile development team to deliver engaging user experiences",
"similarity": 0.4576
}
],
"matched_count": null,
"matched_skills": null,
"role_id": 89,
"score": 0.5648,
"slug": "react-frontend-developer",
"total_count": null
},
{
"display_name": "React Native Developer",
"kra_matches": [
{
"kra_text": "maintain code quality",
"sentence": "Fix production issues and maintain the code as needed",
"similarity": 0.6351
},
{
"kra_text": "maintain code quality",
"sentence": "Write accessible code that is easy to maintain and test.",
"similarity": 0.6342
},
{
"kra_text": "integrate backend APIs",
"sentence": "Experience building/consuming RESTful or gRPC web-services",
"similarity": 0.4146
}
],
"matched_count": null,
"matched_skills": null,
"role_id": 73,
"score": 0.5613,
"slug": "react-native-developer",
"total_count": null
}
],
"skill_match_roles": [
{
"display_name": "Fullstack Developer",
"kra_matches": null,
"matched_count": 4,
"matched_skills": [
"REST",
"React",
"TypeScript",
"gRPC"
],
"role_id": 15,
"score": 0.6667,
"slug": "full-stack-engineer",
"total_count": 6
},
{
"display_name": "Sitecore Dev",
"kra_matches": null,
"matched_count": 3,
"matched_skills": [
"REST",
"React",
"TypeScript"
],
"role_id": 233,
"score": 0.5,
"slug": "sitecore-dev",
"total_count": 6
},
{
"display_name": "Backend Developer",
"kra_matches": null,
"matched_count": 3,
"matched_skills": [
"REST",
"TypeScript",
"gRPC"
],
"role_id": 1,
"score": 0.5,
"slug": "backend-engineer",
"total_count": 6
},
{
"display_name": "Node.js Backend Developer",
"kra_matches": null,
"matched_count": 3,
"matched_skills": [
"REST",
"TypeScript",
"gRPC"
],
"role_id": 82,
"score": 0.5,
"slug": "node-backend-developer",
"total_count": 6
},
{
"display_name": "Frontend Developer",
"kra_matches": null,
"matched_count": 2,
"matched_skills": [
"React",
"TypeScript"
],
"role_id": 7,
"score": 0.3333,
"slug": "frontend-engineer",
"total_count": 6
}
]
},
"stage4_decision": {
"alias_collision_detected": false,
"case": "DOMAIN",
"chosen_role": {
"display_name": "Frontend Developer",
"kra_matches": null,
"matched_count": null,
"matched_skills": null,
"role_id": 7,
"score": 0.98,
"slug": "frontend-engineer",
"total_count": null
},
"confidence": 0.98,
"is_new_role": false,
"llm2_fired": false,
"llm2_reasoning": null,
"matched_dimensions": [
"Frontend component architecture",
"Accessible UI development",
"User experience delivery",
"Frontend testing and maintainability",
"Agile product development",
"Software development lifecycle"
],
"matched_kras": [
"Write accessible code that is easy to maintain and test",
"Participate in the design and architecture of web components",
"Elicit design requirements with Project Management and product teams",
"Deliver engaging user experiences",
"Fix production issues and maintain the code"
],
"matched_skills": [
"TypeScript",
"React",
"front-end testing libraries",
"reusable front-end components",
"web components",
"XML Schema",
"JSON Schema",
"RESTful",
"gRPC",
"version control",
"build process",
"testing",
"code release",
"Agile",
"Test-driven development"
],
"new_role_display_name": null,
"new_role_slug": null,
"queued": false,
"reasoning": "Domain=Software Engineering \u2192 sub-role react-frontend-developer; The JD is clearly for a React/TypeScript frontend role focused on reusable web components, testing, and user experience delivery.",
"sub_role": {
"confidence": 0.99,
"display_name": "React Frontend Developer",
"reasoning": "The JD explicitly requires TypeScript and the React framework and focuses on reusable front-end components and testing, which strongly matches React over the other frameworks.",
"role_id": 89,
"slug": "react-frontend-developer"
}
},
"stage5_updates": {
"centroid_n_after": 98,
"centroid_updated": true,
"collision_log_id": null,
"new_kra_attached": null,
"new_skills_attached": [
{
"is_primary": true,
"queue_id": 6111,
"role_display_name": "Frontend Developer",
"role_slug": "frontend-engineer",
"skill_name": "Test-driven development",
"status": "pending"
},
{
"is_primary": false,
"queue_id": 6113,
"role_display_name": "Frontend Developer",
"role_slug": "frontend-engineer",
"skill_name": "XML Schema",
"status": "pending"
},
{
"is_primary": false,
"queue_id": 6115,
"role_display_name": "Frontend Developer",
"role_slug": "frontend-engineer",
"skill_name": "version control",
"status": "pending"
},
{
"is_primary": false,
"queue_id": 6117,
"role_display_name": "Frontend Developer",
"role_slug": "frontend-engineer",
"skill_name": "build process",
"status": "pending"
},
{
"is_primary": false,
"queue_id": 6119,
"role_display_name": "Frontend Developer",
"role_slug": "frontend-engineer",
"skill_name": "testing",
"status": "pending"
},
{
"is_primary": false,
"queue_id": 6121,
"role_display_name": "Frontend Developer",
"role_slug": "frontend-engineer",
"skill_name": "code release",
"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": 914,
"existing_alias_text": "TypeScript",
"input_term": "TypeScript",
"matched_canonical": {
"category_id": 6,
"display_name": "TypeScript",
"id": 524,
"is_also_category": false,
"is_extractable": true,
"skill_nature": "LANGUAGE",
"slug": "typescript",
"sub_category_id": 96,
"typical_lifespan": "EVERGREEN",
"volatility": "STABLE"
},
"matched_via": "alias"
},
{
"alias_persist_skipped_reason": "alias_text already exists for this canonical skill",
"alias_persisted": false,
"existing_alias_id": 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": 868,
"existing_alias_text": "Agile",
"input_term": "Agile",
"matched_canonical": {
"category_id": 8,
"display_name": "Agile",
"id": 520,
"is_also_category": false,
"is_extractable": true,
"skill_nature": "METHODOLOGY",
"slug": "agile",
"sub_category_id": 367,
"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": 108,
"existing_alias_text": "gRPC",
"input_term": "gRPC",
"matched_canonical": {
"category_id": 10,
"display_name": "gRPC",
"id": 13,
"is_also_category": false,
"is_extractable": true,
"skill_nature": "PROTOCOL",
"slug": "grpc",
"sub_category_id": 52,
"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": 110,
"existing_alias_text": "JSON Schema",
"input_term": "JSON Schema",
"matched_canonical": {
"category_id": 12,
"display_name": "JSON schema",
"id": 15,
"is_also_category": false,
"is_extractable": true,
"skill_nature": "STANDARD",
"slug": "json-schema",
"sub_category_id": 1789,
"typical_lifespan": "EVERGREEN",
"volatility": "STABLE"
},
"matched_via": "alias"
}
],
"candidate_roles": [
{
"display_name": "Hybrid Mobile Developer",
"id": 11,
"rationale": null,
"role_archetype": null,
"slug": "hybrid-mobile-developer",
"source": "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": "Ionic Developer",
"id": 434,
"rationale": null,
"role_archetype": null,
"slug": "ionic-developer",
"source": "db"
},
{
"display_name": "Node.js Backend Developer",
"id": 82,
"rationale": null,
"role_archetype": "Engineering",
"slug": "node-backend-developer",
"source": "db"
},
{
"display_name": "React Frontend Developer",
"id": 89,
"rationale": null,
"role_archetype": "Engineering",
"slug": "react-frontend-developer",
"source": "db"
},
{
"display_name": "React Native Developer",
"id": 73,
"rationale": null,
"role_archetype": "Engineering",
"slug": "react-native-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": "Fullstack Developer",
"id": 15,
"rationale": null,
"role_archetype": null,
"slug": "full-stack-engineer",
"source": "db"
},
{
"display_name": "AR/VR Engineer",
"id": 8,
"rationale": null,
"role_archetype": null,
"slug": "ar-vr-engineer",
"source": "db"
},
{
"display_name": "Sitecore Dev",
"id": 233,
"rationale": null,
"role_archetype": "Engineering",
"slug": "sitecore-dev",
"source": "db"
},
{
"display_name": "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": ".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": "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": "Flutter Developer",
"id": 74,
"rationale": null,
"role_archetype": "Engineering",
"slug": "flutter-developer",
"source": "db"
},
{
"display_name": "Native Mobile Developer",
"id": 75,
"rationale": null,
"role_archetype": "Engineering",
"slug": "native-mobile-developer",
"source": "db"
},
{
"display_name": "Data Engineer",
"id": 2,
"rationale": null,
"role_archetype": null,
"slug": "data-engineer",
"source": "db"
}
],
"chosen_role": {
"display_name": "Frontend Developer",
"id": 7,
"rationale": "Domain=Software Engineering \u2192 sub-role react-frontend-developer; The JD is clearly for a React/TypeScript frontend role focused on reusable web components, testing, and user experience delivery.",
"role_archetype": null,
"slug": "frontend-engineer",
"source": "db"
},
"dimensions": [
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Cross-Platform App Languages",
"id": 167,
"rationale": "Languages used to implement shared mobile features across iOS and Android from a common codebase. This is the primary coding surface for hybrid app logic, UI behavior, and platform-specific branching.",
"slug": "cross-platform-app-languages",
"source": "db"
},
"input_skill": "TypeScript",
"llm_role": null,
"roles_from_db": [
{
"display_name": "Hybrid Mobile Developer",
"id": 11,
"rationale": null,
"role_archetype": null,
"slug": "hybrid-mobile-developer",
"source": "db"
}
]
},
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "JavaScript and TypeScript",
"id": 114,
"rationale": "Primary implementation languages for browser client code, UI logic, and shared frontend utilities. These languages are the main coding surface for building interactive web experiences in this role.",
"slug": "javascript-and-typescript",
"source": "db"
},
"input_skill": "TypeScript",
"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": "Ionic Developer",
"id": 434,
"rationale": null,
"role_archetype": null,
"slug": "ionic-developer",
"source": "db"
},
{
"display_name": "Node.js Backend Developer",
"id": 82,
"rationale": null,
"role_archetype": "Engineering",
"slug": "node-backend-developer",
"source": "db"
},
{
"display_name": "React Frontend Developer",
"id": 89,
"rationale": null,
"role_archetype": "Engineering",
"slug": "react-frontend-developer",
"source": "db"
},
{
"display_name": "React Native Developer",
"id": 73,
"rationale": null,
"role_archetype": "Engineering",
"slug": "react-native-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": "Programming Languages",
"id": 1,
"rationale": "Primary implementation languages used to build client and server feature code. Full stack engineers need enough fluency to move across layers and implement product behavior end to end.",
"slug": "programming-languages",
"source": "db"
},
"input_skill": "TypeScript",
"llm_role": null,
"roles_from_db": [
{
"display_name": "Backend Developer",
"id": 1,
"rationale": null,
"role_archetype": "A Backend Engineer designs, builds, and maintains the server-side logic and data handling that power applications and services. They focus on implementing reliable business functionality, integrating with other systems, and ensuring the backend is scalable, maintainable, and observable.",
"slug": "backend-engineer",
"source": "db"
},
{
"display_name": "Fullstack Developer",
"id": 15,
"rationale": null,
"role_archetype": null,
"slug": "full-stack-engineer",
"source": "db"
}
]
},
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Programming Languages for XR",
"id": 97,
"rationale": "Primary implementation languages used to build immersive client features, interaction logic, and device-specific runtime behavior. This is the core coding surface for AR/VR experiences.",
"slug": "programming-languages-for-xr",
"source": "db"
},
"input_skill": "TypeScript",
"llm_role": null,
"roles_from_db": [
{
"display_name": "AR/VR Engineer",
"id": 8,
"rationale": null,
"role_archetype": null,
"slug": "ar-vr-engineer",
"source": "db"
}
]
},
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Sitecore Development Languages",
"id": 438,
"rationale": "Core implementation languages and markup used to build Sitecore customizations, rendering logic, and site behavior. This is the primary authoring surface for Sitecore-specific code and templates.",
"slug": "sitecore-development-languages",
"source": "db"
},
"input_skill": "TypeScript",
"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": "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": "React Frontend Development",
"id": 96,
"rationale": "Building interactive web user interfaces with React.js, including component composition, state management, hooks, and rendering patterns. React.js belongs here because it is a core library for client-side UI development in modern web applications.",
"slug": "d_init_01",
"source": "db"
},
"input_skill": "Agile",
"llm_role": null,
"roles_from_db": []
},
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "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": "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": "gRPC",
"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": "gRPC",
"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": "API Standards and Protocols",
"id": 318,
"rationale": "Applies and implements key communication protocols, data formats, and security standards for Flutter client-server integration.",
"slug": "api-standards-and-protocols",
"source": "db"
},
"input_skill": "gRPC",
"llm_role": null,
"roles_from_db": [
{
"display_name": "Flutter Developer",
"id": 74,
"rationale": null,
"role_archetype": "Engineering",
"slug": "flutter-developer",
"source": "db"
}
]
},
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Mobile Protocols \u0026 Standards",
"id": 277,
"rationale": "Mastery of core networking and security protocols and compliance standards for native mobile apps.",
"slug": "mobile-protocols-standards",
"source": "db"
},
"input_skill": "gRPC",
"llm_role": null,
"roles_from_db": [
{
"display_name": "Native Mobile Developer",
"id": 75,
"rationale": null,
"role_archetype": "Engineering",
"slug": "native-mobile-developer",
"source": "db"
}
]
},
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "API Design and Contracts",
"id": 3,
"rationale": "Designing request/response shapes and the rules that govern client-server interaction. This cluster is coherent because full stack engineers often own the contract between UI behavior and backend implementation.",
"slug": "api-design-and-contracts",
"source": "db"
},
"input_skill": "JSON Schema",
"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": "JSON Schema",
"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": "Data Serialization Standards \u0026 Protocols",
"id": 37,
"rationale": "Covers the key industry standards and protocols for serializing, storing, and transmitting structured data in engineering pipelines.",
"slug": "data-serialization-standards-protocols",
"source": "db"
},
"input_skill": "JSON Schema",
"llm_role": null,
"roles_from_db": [
{
"display_name": "Data Engineer",
"id": 2,
"rationale": null,
"role_archetype": null,
"slug": "data-engineer",
"source": "db"
}
]
}
],
"input_final_skills": [
"TypeScript",
"React",
"Agile",
"Test-driven development",
"REST",
"gRPC",
"XML Schema",
"JSON Schema",
"version control",
"build process",
"testing",
"code release"
],
"input_llm_skills": [
"TypeScript",
"React",
"Agile",
"Test-driven development",
"REST",
"gRPC",
"XML Schema",
"JSON Schema",
"version control",
"build process",
"testing",
"code release"
],
"new_aliases_persisted": 0,
"run_id": "60479782-ae35-4185-9f9d-e76a25bd3b96",
"skills_detail": [
{
"aliases_in_db": [
{
"alias_text": "TypeScript",
"alias_type": "CANONICAL",
"id": 914,
"is_primary": true,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "TypeScript 5",
"alias_type": "VERSION",
"id": 3157,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "TypeScript 5.x",
"alias_type": "VERSION",
"id": 3159,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "ts",
"alias_type": "VERSION",
"id": 1647,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "ts5",
"alias_type": "VERSION",
"id": 1648,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "typescript 5",
"alias_type": "VERSION",
"id": 1649,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "typescript 5.x",
"alias_type": "VERSION",
"id": 1650,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "typescript5",
"alias_type": "VERSION",
"id": 2179,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
}
],
"canonical": {
"category_id": 6,
"display_name": "TypeScript",
"id": 524,
"is_also_category": false,
"is_extractable": true,
"skill_nature": "LANGUAGE",
"slug": "typescript",
"sub_category_id": 96,
"typical_lifespan": "EVERGREEN",
"volatility": "STABLE"
},
"dimensions": [
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Cross-Platform App Languages",
"id": 167,
"rationale": "Languages used to implement shared mobile features across iOS and Android from a common codebase. This is the primary coding surface for hybrid app logic, UI behavior, and platform-specific branching.",
"slug": "cross-platform-app-languages",
"source": "db"
},
"input_skill": "TypeScript",
"llm_role": null,
"roles_from_db": [
{
"display_name": "Hybrid Mobile Developer",
"id": 11,
"rationale": null,
"role_archetype": null,
"slug": "hybrid-mobile-developer",
"source": "db"
}
]
},
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "JavaScript and TypeScript",
"id": 114,
"rationale": "Primary implementation languages for browser client code, UI logic, and shared frontend utilities. These languages are the main coding surface for building interactive web experiences in this role.",
"slug": "javascript-and-typescript",
"source": "db"
},
"input_skill": "TypeScript",
"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": "Ionic Developer",
"id": 434,
"rationale": null,
"role_archetype": null,
"slug": "ionic-developer",
"source": "db"
},
{
"display_name": "Node.js Backend Developer",
"id": 82,
"rationale": null,
"role_archetype": "Engineering",
"slug": "node-backend-developer",
"source": "db"
},
{
"display_name": "React Frontend Developer",
"id": 89,
"rationale": null,
"role_archetype": "Engineering",
"slug": "react-frontend-developer",
"source": "db"
},
{
"display_name": "React Native Developer",
"id": 73,
"rationale": null,
"role_archetype": "Engineering",
"slug": "react-native-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": "Programming Languages",
"id": 1,
"rationale": "Primary implementation languages used to build client and server feature code. Full stack engineers need enough fluency to move across layers and implement product behavior end to end.",
"slug": "programming-languages",
"source": "db"
},
"input_skill": "TypeScript",
"llm_role": null,
"roles_from_db": [
{
"display_name": "Backend Developer",
"id": 1,
"rationale": null,
"role_archetype": "A Backend Engineer designs, builds, and maintains the server-side logic and data handling that power applications and services. They focus on implementing reliable business functionality, integrating with other systems, and ensuring the backend is scalable, maintainable, and observable.",
"slug": "backend-engineer",
"source": "db"
},
{
"display_name": "Fullstack Developer",
"id": 15,
"rationale": null,
"role_archetype": null,
"slug": "full-stack-engineer",
"source": "db"
}
]
},
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Programming Languages for XR",
"id": 97,
"rationale": "Primary implementation languages used to build immersive client features, interaction logic, and device-specific runtime behavior. This is the core coding surface for AR/VR experiences.",
"slug": "programming-languages-for-xr",
"source": "db"
},
"input_skill": "TypeScript",
"llm_role": null,
"roles_from_db": [
{
"display_name": "AR/VR Engineer",
"id": 8,
"rationale": null,
"role_archetype": null,
"slug": "ar-vr-engineer",
"source": "db"
}
]
},
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Sitecore Development Languages",
"id": 438,
"rationale": "Core implementation languages and markup used to build Sitecore customizations, rendering logic, and site behavior. This is the primary authoring surface for Sitecore-specific code and templates.",
"slug": "sitecore-development-languages",
"source": "db"
},
"input_skill": "TypeScript",
"llm_role": null,
"roles_from_db": [
{
"display_name": "Sitecore Dev",
"id": 233,
"rationale": null,
"role_archetype": "Engineering",
"slug": "sitecore-dev",
"source": "db"
}
]
}
],
"input_skill": "TypeScript",
"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": "Agile",
"alias_type": "CANONICAL",
"id": 868,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
}
],
"canonical": {
"category_id": 8,
"display_name": "Agile",
"id": 520,
"is_also_category": false,
"is_extractable": true,
"skill_nature": "METHODOLOGY",
"slug": "agile",
"sub_category_id": 367,
"typical_lifespan": "EVERGREEN",
"volatility": "STABLE"
},
"dimensions": [
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "React Frontend Development",
"id": 96,
"rationale": "Building interactive web user interfaces with React.js, including component composition, state management, hooks, and rendering patterns. React.js belongs here because it is a core library for client-side UI development in modern web applications.",
"slug": "d_init_01",
"source": "db"
},
"input_skill": "Agile",
"llm_role": null,
"roles_from_db": []
}
],
"input_skill": "Agile",
"matched_via": "alias",
"new_alias_persisted": false,
"new_alias_text": null,
"new_skill_meta": null,
"source_tag": "db",
"was_in_llm_skills": true
},
{
"aliases_in_db": [],
"canonical": null,
"dimensions": [],
"input_skill": "Test-driven development",
"matched_via": null,
"new_alias_persisted": false,
"new_alias_text": null,
"new_skill_meta": {
"derived": {
"category": "Soft Skills",
"skill_nature": "PRACTICE",
"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": "test-driven-development",
"split_log": [],
"typed": null,
"warnings": []
},
"source_tag": "llm",
"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": "gRPC",
"alias_type": "CANONICAL",
"id": 108,
"is_primary": true,
"match_strategy": "CASE_INSENSITIVE"
}
],
"canonical": {
"category_id": 10,
"display_name": "gRPC",
"id": 13,
"is_also_category": false,
"is_extractable": true,
"skill_nature": "PROTOCOL",
"slug": "grpc",
"sub_category_id": 52,
"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": "gRPC",
"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": "gRPC",
"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": "API Standards and Protocols",
"id": 318,
"rationale": "Applies and implements key communication protocols, data formats, and security standards for Flutter client-server integration.",
"slug": "api-standards-and-protocols",
"source": "db"
},
"input_skill": "gRPC",
"llm_role": null,
"roles_from_db": [
{
"display_name": "Flutter Developer",
"id": 74,
"rationale": null,
"role_archetype": "Engineering",
"slug": "flutter-developer",
"source": "db"
}
]
},
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Mobile Protocols \u0026 Standards",
"id": 277,
"rationale": "Mastery of core networking and security protocols and compliance standards for native mobile apps.",
"slug": "mobile-protocols-standards",
"source": "db"
},
"input_skill": "gRPC",
"llm_role": null,
"roles_from_db": [
{
"display_name": "Native Mobile Developer",
"id": 75,
"rationale": null,
"role_archetype": "Engineering",
"slug": "native-mobile-developer",
"source": "db"
}
]
}
],
"input_skill": "gRPC",
"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": "XML Schema",
"matched_via": null,
"new_alias_persisted": false,
"new_alias_text": null,
"new_skill_meta": {
"derived": {
"category": "Markup Languages",
"skill_nature": "LANGUAGE",
"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": "xml-schema",
"split_log": [],
"typed": null,
"warnings": []
},
"source_tag": "llm",
"was_in_llm_skills": true
},
{
"aliases_in_db": [
{
"alias_text": "JSON schema",
"alias_type": "CANONICAL",
"id": 3584,
"is_primary": true,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "2019-09",
"alias_type": "VERSION",
"id": 111,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "2020-12",
"alias_type": "VERSION",
"id": 112,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "JSON Schema",
"alias_type": "CANONICAL",
"id": 110,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "JSON Schema 2019-09",
"alias_type": "VERSION",
"id": 116,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "JSON Schema 2020-12",
"alias_type": "VERSION",
"id": 117,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "JSON Schema Draft 4",
"alias_type": "VERSION",
"id": 118,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "JSON Schema Draft 6",
"alias_type": "VERSION",
"id": 119,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "JSON Schema Draft 7",
"alias_type": "VERSION",
"id": 120,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "draft-04",
"alias_type": "VERSION",
"id": 113,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "draft-06",
"alias_type": "VERSION",
"id": 114,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "draft-07",
"alias_type": "VERSION",
"id": 115,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
}
],
"canonical": {
"category_id": 12,
"display_name": "JSON schema",
"id": 15,
"is_also_category": false,
"is_extractable": true,
"skill_nature": "STANDARD",
"slug": "json-schema",
"sub_category_id": 1789,
"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": "JSON Schema",
"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": "JSON Schema",
"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": "Data Serialization Standards \u0026 Protocols",
"id": 37,
"rationale": "Covers the key industry standards and protocols for serializing, storing, and transmitting structured data in engineering pipelines.",
"slug": "data-serialization-standards-protocols",
"source": "db"
},
"input_skill": "JSON Schema",
"llm_role": null,
"roles_from_db": [
{
"display_name": "Data Engineer",
"id": 2,
"rationale": null,
"role_archetype": null,
"slug": "data-engineer",
"source": "db"
}
]
}
],
"input_skill": "JSON Schema",
"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": "version control",
"matched_via": null,
"new_alias_persisted": false,
"new_alias_text": null,
"new_skill_meta": {
"derived": {
"category": "DevOps Tools",
"skill_nature": "PRACTICE",
"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": "version-control",
"split_log": [],
"typed": null,
"warnings": []
},
"source_tag": "llm",
"was_in_llm_skills": true
},
{
"aliases_in_db": [],
"canonical": null,
"dimensions": [],
"input_skill": "build process",
"matched_via": null,
"new_alias_persisted": false,
"new_alias_text": null,
"new_skill_meta": {
"derived": {
"category": "DevOps Tools",
"skill_nature": "PRACTICE",
"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": "build-process",
"split_log": [],
"typed": null,
"warnings": []
},
"source_tag": "llm",
"was_in_llm_skills": true
},
{
"aliases_in_db": [],
"canonical": null,
"dimensions": [],
"input_skill": "testing",
"matched_via": null,
"new_alias_persisted": false,
"new_alias_text": null,
"new_skill_meta": {
"derived": {
"category": "Testing Tools",
"skill_nature": "PRACTICE",
"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": "testing",
"split_log": [],
"typed": null,
"warnings": []
},
"source_tag": "llm",
"was_in_llm_skills": true
},
{
"aliases_in_db": [],
"canonical": null,
"dimensions": [],
"input_skill": "code release",
"matched_via": null,
"new_alias_persisted": false,
"new_alias_text": null,
"new_skill_meta": {
"derived": {
"category": "DevOps Tools",
"skill_nature": "PRACTICE",
"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": "code-release",
"split_log": [],
"typed": null,
"warnings": []
},
"source_tag": "llm",
"was_in_llm_skills": true
}
],
"unmatched_skills": [
"Test-driven development",
"XML Schema",
"version control",
"build process",
"testing",
"code release"
]
}
API 3 — final-role-output
{
"chosen_role": {
"display_name": "Frontend Developer",
"id": 7,
"rationale": "Domain=Software Engineering \u2192 sub-role react-frontend-developer; The JD is clearly for a React/TypeScript frontend role focused on reusable web components, testing, and user experience delivery.",
"role_archetype": null,
"slug": "frontend-engineer",
"source": "db"
},
"chosen_role_resolution": "in_db",
"final_input_skills": [
{
"skill": "TypeScript",
"tag": "in_db"
},
{
"skill": "React",
"tag": "in_db"
},
{
"skill": "Agile",
"tag": "in_db"
},
{
"skill": "Test-driven development",
"tag": "new"
},
{
"skill": "REST",
"tag": "in_db"
},
{
"skill": "gRPC",
"tag": "in_db"
},
{
"skill": "XML Schema",
"tag": "new"
},
{
"skill": "JSON Schema",
"tag": "in_db"
},
{
"skill": "version control",
"tag": "new"
},
{
"skill": "build process",
"tag": "new"
},
{
"skill": "testing",
"tag": "new"
},
{
"skill": "code release",
"tag": "new"
}
],
"llm_cost_api1_usd": null,
"llm_cost_api2_usd": null,
"llm_cost_api3_usd": null,
"llm_cost_total_usd": null,
"persistence": {
"items": [
{
"chosen_role_id": 7,
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Cross-Platform App Languages",
"id": 167,
"rationale": "Languages used to implement shared mobile features across iOS and Android from a common codebase. This is the primary coding surface for hybrid app logic, UI behavior, and platform-specific branching.",
"slug": "cross-platform-app-languages",
"source": "db"
},
"dimension_id": 167,
"input_skill": "TypeScript",
"llm_role": null,
"matched_chosen_role": false,
"outcome_line": "Existing dimension (library) \u00b7 Role\u2194dimension skipped (dimension not under chosen role)",
"role_dimension_saved": false,
"roles_from_db": [
{
"display_name": "Hybrid Mobile Developer",
"id": 11,
"rationale": null,
"role_archetype": null,
"slug": "hybrid-mobile-developer",
"source": "db"
}
],
"skill_dimension_saved": true,
"skill_id": 524,
"skill_tag": "in_db",
"skipped_reason": null
},
{
"chosen_role_id": 7,
"dimension": {
"difficulty_hint": "well_known",
"display_name": "JavaScript and TypeScript",
"id": 114,
"rationale": "Primary implementation languages for browser client code, UI logic, and shared frontend utilities. These languages are the main coding surface for building interactive web experiences in this role.",
"slug": "javascript-and-typescript",
"source": "db"
},
"dimension_id": 114,
"input_skill": "TypeScript",
"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": "Ionic Developer",
"id": 434,
"rationale": null,
"role_archetype": null,
"slug": "ionic-developer",
"source": "db"
},
{
"display_name": "Node.js Backend Developer",
"id": 82,
"rationale": null,
"role_archetype": "Engineering",
"slug": "node-backend-developer",
"source": "db"
},
{
"display_name": "React Frontend Developer",
"id": 89,
"rationale": null,
"role_archetype": "Engineering",
"slug": "react-frontend-developer",
"source": "db"
},
{
"display_name": "React Native Developer",
"id": 73,
"rationale": null,
"role_archetype": "Engineering",
"slug": "react-native-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": 524,
"skill_tag": "in_db",
"skipped_reason": null
},
{
"chosen_role_id": 7,
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Programming Languages",
"id": 1,
"rationale": "Primary implementation languages used to build client and server feature code. Full stack engineers need enough fluency to move across layers and implement product behavior end to end.",
"slug": "programming-languages",
"source": "db"
},
"dimension_id": 1,
"input_skill": "TypeScript",
"llm_role": null,
"matched_chosen_role": false,
"outcome_line": "Existing dimension (library) \u00b7 Role\u2194dimension skipped (dimension not under chosen role)",
"role_dimension_saved": false,
"roles_from_db": [
{
"display_name": "Backend Developer",
"id": 1,
"rationale": null,
"role_archetype": "A Backend Engineer designs, builds, and maintains the server-side logic and data handling that power applications and services. They focus on implementing reliable business functionality, integrating with other systems, and ensuring the backend is scalable, maintainable, and observable.",
"slug": "backend-engineer",
"source": "db"
},
{
"display_name": "Fullstack Developer",
"id": 15,
"rationale": null,
"role_archetype": null,
"slug": "full-stack-engineer",
"source": "db"
}
],
"skill_dimension_saved": true,
"skill_id": 524,
"skill_tag": "in_db",
"skipped_reason": null
},
{
"chosen_role_id": 7,
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Programming Languages for XR",
"id": 97,
"rationale": "Primary implementation languages used to build immersive client features, interaction logic, and device-specific runtime behavior. This is the core coding surface for AR/VR experiences.",
"slug": "programming-languages-for-xr",
"source": "db"
},
"dimension_id": 97,
"input_skill": "TypeScript",
"llm_role": null,
"matched_chosen_role": false,
"outcome_line": "Existing dimension (library) \u00b7 Role\u2194dimension skipped (dimension not under chosen role)",
"role_dimension_saved": false,
"roles_from_db": [
{
"display_name": "AR/VR Engineer",
"id": 8,
"rationale": null,
"role_archetype": null,
"slug": "ar-vr-engineer",
"source": "db"
}
],
"skill_dimension_saved": true,
"skill_id": 524,
"skill_tag": "in_db",
"skipped_reason": null
},
{
"chosen_role_id": 7,
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Sitecore Development Languages",
"id": 438,
"rationale": "Core implementation languages and markup used to build Sitecore customizations, rendering logic, and site behavior. This is the primary authoring surface for Sitecore-specific code and templates.",
"slug": "sitecore-development-languages",
"source": "db"
},
"dimension_id": 438,
"input_skill": "TypeScript",
"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": 524,
"skill_tag": "in_db",
"skipped_reason": null
},
{
"chosen_role_id": 7,
"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": 7,
"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": 7,
"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": 7,
"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": 7,
"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": 7,
"dimension": {
"difficulty_hint": "well_known",
"display_name": "React Frontend Development",
"id": 96,
"rationale": "Building interactive web user interfaces with React.js, including component composition, state management, hooks, and rendering patterns. React.js belongs here because it is a core library for client-side UI development in modern web applications.",
"slug": "d_init_01",
"source": "db"
},
"dimension_id": 96,
"input_skill": "Agile",
"llm_role": null,
"matched_chosen_role": false,
"outcome_line": "Existing dimension (library) \u00b7 Role\u2194dimension skipped (dimension not under chosen role)",
"role_dimension_saved": false,
"roles_from_db": [],
"skill_dimension_saved": true,
"skill_id": 520,
"skill_tag": "in_db",
"skipped_reason": null
},
{
"chosen_role_id": 7,
"dimension": {
"difficulty_hint": "well_known",
"display_name": "API Design and Contracts",
"id": 3,
"rationale": "Designing request/response shapes and the rules that govern client-server interaction. This cluster is coherent because full stack engineers often own the contract between UI behavior and backend implementation.",
"slug": "api-design-and-contracts",
"source": "db"
},
"dimension_id": 3,
"input_skill": "REST",
"llm_role": null,
"matched_chosen_role": false,
"outcome_line": "Existing dimension (library) \u00b7 Role\u2194dimension skipped (dimension not under chosen role)",
"role_dimension_saved": false,
"roles_from_db": [
{
"display_name": "Backend Developer",
"id": 1,
"rationale": null,
"role_archetype": "A Backend Engineer designs, builds, and maintains the server-side logic and data handling that power applications and services. They focus on implementing reliable business functionality, integrating with other systems, and ensuring the backend is scalable, maintainable, and observable.",
"slug": "backend-engineer",
"source": "db"
},
{
"display_name": "Fullstack Developer",
"id": 15,
"rationale": null,
"role_archetype": null,
"slug": "full-stack-engineer",
"source": "db"
}
],
"skill_dimension_saved": true,
"skill_id": 11,
"skill_tag": "in_db",
"skipped_reason": null
},
{
"chosen_role_id": 7,
"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": 7,
"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": 7,
"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": 7,
"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": "gRPC",
"llm_role": null,
"matched_chosen_role": false,
"outcome_line": "Existing dimension (library) \u00b7 Role\u2194dimension skipped (dimension not under chosen role)",
"role_dimension_saved": false,
"roles_from_db": [
{
"display_name": "Backend Developer",
"id": 1,
"rationale": null,
"role_archetype": "A Backend Engineer designs, builds, and maintains the server-side logic and data handling that power applications and services. They focus on implementing reliable business functionality, integrating with other systems, and ensuring the backend is scalable, maintainable, and observable.",
"slug": "backend-engineer",
"source": "db"
},
{
"display_name": "Fullstack Developer",
"id": 15,
"rationale": null,
"role_archetype": null,
"slug": "full-stack-engineer",
"source": "db"
}
],
"skill_dimension_saved": true,
"skill_id": 13,
"skill_tag": "in_db",
"skipped_reason": null
},
{
"chosen_role_id": 7,
"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": "gRPC",
"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": 13,
"skill_tag": "in_db",
"skipped_reason": null
},
{
"chosen_role_id": 7,
"dimension": {
"difficulty_hint": "well_known",
"display_name": "API Standards and Protocols",
"id": 318,
"rationale": "Applies and implements key communication protocols, data formats, and security standards for Flutter client-server integration.",
"slug": "api-standards-and-protocols",
"source": "db"
},
"dimension_id": 318,
"input_skill": "gRPC",
"llm_role": null,
"matched_chosen_role": false,
"outcome_line": "Existing dimension (library) \u00b7 Role\u2194dimension skipped (dimension not under chosen role)",
"role_dimension_saved": false,
"roles_from_db": [
{
"display_name": "Flutter Developer",
"id": 74,
"rationale": null,
"role_archetype": "Engineering",
"slug": "flutter-developer",
"source": "db"
}
],
"skill_dimension_saved": true,
"skill_id": 13,
"skill_tag": "in_db",
"skipped_reason": null
},
{
"chosen_role_id": 7,
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Mobile Protocols \u0026 Standards",
"id": 277,
"rationale": "Mastery of core networking and security protocols and compliance standards for native mobile apps.",
"slug": "mobile-protocols-standards",
"source": "db"
},
"dimension_id": 277,
"input_skill": "gRPC",
"llm_role": null,
"matched_chosen_role": false,
"outcome_line": "Existing dimension (library) \u00b7 Role\u2194dimension skipped (dimension not under chosen role)",
"role_dimension_saved": false,
"roles_from_db": [
{
"display_name": "Native Mobile Developer",
"id": 75,
"rationale": null,
"role_archetype": "Engineering",
"slug": "native-mobile-developer",
"source": "db"
}
],
"skill_dimension_saved": true,
"skill_id": 13,
"skill_tag": "in_db",
"skipped_reason": null
},
{
"chosen_role_id": 7,
"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": "JSON Schema",
"llm_role": null,
"matched_chosen_role": false,
"outcome_line": "Existing dimension (library) \u00b7 Role\u2194dimension skipped (dimension not under chosen role)",
"role_dimension_saved": false,
"roles_from_db": [
{
"display_name": "Backend Developer",
"id": 1,
"rationale": null,
"role_archetype": "A Backend Engineer designs, builds, and maintains the server-side logic and data handling that power applications and services. They focus on implementing reliable business functionality, integrating with other systems, and ensuring the backend is scalable, maintainable, and observable.",
"slug": "backend-engineer",
"source": "db"
},
{
"display_name": "Fullstack Developer",
"id": 15,
"rationale": null,
"role_archetype": null,
"slug": "full-stack-engineer",
"source": "db"
}
],
"skill_dimension_saved": true,
"skill_id": 15,
"skill_tag": "in_db",
"skipped_reason": null
},
{
"chosen_role_id": 7,
"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": "JSON Schema",
"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": 15,
"skill_tag": "in_db",
"skipped_reason": null
},
{
"chosen_role_id": 7,
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Data Serialization Standards \u0026 Protocols",
"id": 37,
"rationale": "Covers the key industry standards and protocols for serializing, storing, and transmitting structured data in engineering pipelines.",
"slug": "data-serialization-standards-protocols",
"source": "db"
},
"dimension_id": 37,
"input_skill": "JSON Schema",
"llm_role": null,
"matched_chosen_role": false,
"outcome_line": "Existing dimension (library) \u00b7 Role\u2194dimension skipped (dimension not under chosen role)",
"role_dimension_saved": false,
"roles_from_db": [
{
"display_name": "Data Engineer",
"id": 2,
"rationale": null,
"role_archetype": null,
"slug": "data-engineer",
"source": "db"
}
],
"skill_dimension_saved": true,
"skill_id": 15,
"skill_tag": "in_db",
"skipped_reason": null
}
],
"new_skills_created": 0,
"role_dimension_saved": 0,
"skill_dimension_saved": 0,
"skipped": 0
},
"planner_output": null,
"run_id": "60479782-ae35-4185-9f9d-e76a25bd3b96"
}
LLM Calls
Every model call made for this run, in pipeline order. Click a card to see the model's response.
Loading…