Pipeline run
de23a89f-0937-4d62-8c3d-a0e7a659ccb2
Client output enrichment
v2 Skill cluster · Nature of work · AI index · Tech stack maturity · Evidence · KRA descriptionNature of work
no kras
Vague JD — no KRAs present to derive a specific nature of work.
Tech stack maturity
Mainstream Modern
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 (0)
Skill cluster (0 dimension groups, role-scoped)
Status:
completed
Created: 2026-05-08T15:48:07.244426Z
Updated: 2026-05-08T15:49:41.799105Z
API 3 duration: 25 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
iOS Engineer
slug: ios-engineer · id: 13 · source: db
The map includes iOS and Native signals, and iOS Engineer is the only candidate directly tied to those dimensions while also fitting the API and state-management overlap.
0
New skills
0
Skill↔dim saved
0
Role↔dim saved
16
Skipped
Job description
t the job Strong experience in JavaScript (ES6), and extensive experience with HTML5 and CSS. Ability to turn wireframes & screen/user flows into pixel-perfect applications. Experience with Redux and source management tools like git. Experience with both iOS and Android deployment. Experience with integration with backend REST APIs. Excellent understanding of software design and object oriented programming principles. Experience on React-Native/React, Redux is a plus. Fluent with usage of instrumentation and debugging tools on respective platforms Have an excellent Foundation in Data Structures & Algorithms. Demonstrate ability to understand and improve complex business logic and user flow. Familiarity with the agile development process is a plus. Familiarity with CI/CD pipelines is a plus. A team player with an appetite to learn is highly valued. Bachelors Degree. Minimum 2 years experience of native iOS/Android consumer facing application. Excellent understanding of software design and object oriented programming principles. Experience on React-Native/React, Redux is a plus. Fluent with usage of instrumentation and debugging tools on respective platforms
history_view bundle (older API). Showing raw API payloads below.
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 |
|---|---|---|---|---|---|---|
| JavaScript | in_db |
Frontend Programming Languages
frontend-programming-languages
|
— | — | — | TODO: REMOVE AFTER TESTING — api3_writes_enabled=False (writes disabled) |
| JavaScript | in_db |
Programming Languages for AI Workflows
programming-languages-for-ai-workflows
|
— | — | — | TODO: REMOVE AFTER TESTING — api3_writes_enabled=False (writes disabled) |
| JavaScript | in_db |
Programming Languages for Test Automation
programming-languages-for-test-automation
|
— | — | — | TODO: REMOVE AFTER TESTING — api3_writes_enabled=False (writes disabled) |
| JavaScript | in_db |
ServiceNow Scripting and Logic
servicenow-scripting-and-logic
|
— | — | — | TODO: REMOVE AFTER TESTING — api3_writes_enabled=False (writes disabled) |
| CSS | in_db |
Responsive Layout and Styling
responsive-layout-and-styling
|
— | — | — | TODO: REMOVE AFTER TESTING — api3_writes_enabled=False (writes disabled) |
| Redux | in_db |
State Management and Client Data
state-management-and-client-data
|
— | — | — | TODO: REMOVE AFTER TESTING — api3_writes_enabled=False (writes disabled) |
| REST APIs | in_db |
API Integration and Data Fetching
api-integration-and-data-fetching
|
— | — | — | TODO: REMOVE AFTER TESTING — api3_writes_enabled=False (writes disabled) |
| REST APIs | in_db |
API Integration and Serialization
api-integration-and-serialization
|
— | — | — | TODO: REMOVE AFTER TESTING — api3_writes_enabled=False (writes disabled) |
| REST APIs | in_db |
Network Automation and Scripting
network-automation-and-scripting
|
— | — | — | TODO: REMOVE AFTER TESTING — api3_writes_enabled=False (writes disabled) |
| HTML | in_db |
Frontend Programming Languages
frontend-programming-languages
|
— | — | — | TODO: REMOVE AFTER TESTING — api3_writes_enabled=False (writes disabled) |
| React | in_db |
Component Frameworks and Rendering
component-frameworks-and-rendering
|
— | — | — | TODO: REMOVE AFTER TESTING — api3_writes_enabled=False (writes disabled) |
| APIs | new |
API Design and Contracting
api-design-and-contracting
|
— | — | — | skill_not_in_db_v3_proposed |
| CI | new |
Continuous Integration
d_init_01
|
— | — | — | skill_not_in_db_v3_proposed |
| Native | new |
Native Platform Development
d_init_01
|
— | — | — | skill_not_in_db_v3_proposed |
| Native | new |
Native Integration Interfaces
d_init_02
|
— | — | — | skill_not_in_db_v3_proposed |
| iOS | new |
iOS Application Development
d_init_01
|
— | — | — | skill_not_in_db_v3_proposed |
Library artifacts (this run)
| Kind | Detail | DB id |
|---|---|---|
| canonical_skill_proposed | APIs | type=Protocol subtype=application_programming_interfaces nature=PROTOCOL lifespan=EVERGREEN | |
| canonical_skill_proposed | CI | type=Methodology subtype=continuous_integration nature=METHODOLOGY lifespan=EVERGREEN | |
| canonical_skill_proposed | Native | type=Concept subtype=native_code nature=CONCEPT lifespan=EVERGREEN | |
| canonical_skill_proposed | iOS | type=Platform subtype=mobile_operating_platform nature=PLATFORM lifespan=EVERGREEN | |
| dimension_skill_link_proposed | APIs ↔ API Design and Contracting | |
| dimension_proposed | Continuous Integration | |
| dimension_skill_link_proposed | CI ↔ Continuous Integration | |
| dimension_proposed | Native Platform Development | |
| dimension_skill_link_proposed | Native ↔ Native Platform Development | |
| dimension_proposed | Native Integration Interfaces | |
| dimension_skill_link_proposed | Native ↔ Native Integration Interfaces | |
| dimension_proposed | iOS Application Development | |
| dimension_skill_link_proposed | iOS ↔ iOS Application Development |
API 1 — extract-from-jd click to toggle
{
"filtered_unknown_words": [
"APIs",
"Ability",
"Bachelors",
"CD",
"CI",
"Data",
"Degree",
"Experience",
"Familiarity",
"Minimum",
"Native",
"Structures",
"ability",
"appetite",
"application",
"applications",
"business",
"consumer",
"deployment",
"design",
"development",
"experience",
"facing",
"iOS",
"job",
"logic",
"management",
"object",
"pipelines",
"pixel",
"platforms",
"player",
"plus",
"principles",
"process",
"programming",
"screen",
"software",
"team",
"tools",
"understanding",
"usage",
"user",
"wireframes",
"years"
],
"final_non_skills": [
"Ability",
"Bachelors",
"CD",
"Data",
"Degree",
"Experience",
"Familiarity",
"Minimum",
"Structures",
"appetite",
"application",
"applications",
"business",
"consumer",
"deployment",
"design",
"development",
"facing",
"job",
"logic",
"management",
"object",
"pipelines",
"pixel",
"platforms",
"player",
"plus",
"principles",
"process",
"programming",
"screen",
"software",
"team",
"tools",
"understanding",
"usage",
"user",
"wireframes",
"years"
],
"final_skills": [
"JavaScript",
"CSS",
"Redux",
"REST APIs",
"HTML",
"React",
"APIs",
"CI",
"Native",
"iOS"
],
"initial_skills": [
"JavaScript",
"CSS",
"Redux",
"REST APIs",
"HTML",
"React"
],
"jd_role_hint": null,
"llm_non_skills": [
"Ability",
"Bachelors",
"CD",
"Data",
"Degree",
"Experience",
"Familiarity",
"Minimum",
"Structures",
"appetite",
"application",
"applications",
"business",
"consumer",
"deployment",
"design",
"development",
"facing",
"job",
"logic",
"management",
"object",
"pipelines",
"pixel",
"platforms",
"player",
"plus",
"principles",
"process",
"programming",
"screen",
"software",
"team",
"tools",
"understanding",
"usage",
"user",
"wireframes",
"years"
],
"llm_skills": [
"APIs",
"CI",
"Native",
"iOS"
],
"run_id": null,
"unknown_words": [
"APIs",
"Ability",
"Bachelors",
"CD",
"CI",
"Data",
"Degree",
"Experience",
"Familiarity",
"Minimum",
"Native",
"Structures",
"ability",
"appetite",
"application",
"applications",
"business",
"consumer",
"deployment",
"design",
"development",
"experience",
"facing",
"iOS",
"job",
"logic",
"management",
"object",
"pipelines",
"pixel",
"platforms",
"player",
"plus",
"principles",
"process",
"programming",
"screen",
"software",
"team",
"tools",
"understanding",
"usage",
"user",
"wireframes",
"years"
]
}
API 2 — extract-details
{
"alias_matches": [],
"candidate_roles": [
{
"display_name": "Frontend Engineer",
"id": 3,
"rationale": null,
"role_archetype": "Frontend Engineers design and build the user-facing parts of applications, translating product and design requirements into interactive experiences. They focus on how the application looks, behaves, and responds in the browser, ensuring usability, accessibility, and consistency across the interface.",
"slug": "frontend-engineer",
"source": "db"
},
{
"display_name": "Full Stack Developer",
"id": 2,
"rationale": null,
"role_archetype": null,
"slug": "full-stack-developer",
"source": "db"
},
{
"display_name": "AI Engineer",
"id": 12,
"rationale": null,
"role_archetype": null,
"slug": "ai-engineer",
"source": "db"
},
{
"display_name": "Automation Tester",
"id": 16,
"rationale": null,
"role_archetype": null,
"slug": "automation-tester",
"source": "db"
},
{
"display_name": "ServiceNOW Developer",
"id": 24,
"rationale": null,
"role_archetype": null,
"slug": "servicenow-developer",
"source": "db"
},
{
"display_name": "iOS Engineer",
"id": 13,
"rationale": null,
"role_archetype": null,
"slug": "ios-engineer",
"source": "db"
},
{
"display_name": "Network Engineer",
"id": 21,
"rationale": null,
"role_archetype": null,
"slug": "network-engineer",
"source": "db"
},
{
"display_name": "Backend Engineer",
"id": 14,
"rationale": null,
"role_archetype": null,
"slug": "backend-engineer",
"source": "db"
}
],
"chosen_role": {
"display_name": "iOS Engineer",
"id": 13,
"rationale": "The map includes iOS and Native signals, and iOS Engineer is the only candidate directly tied to those dimensions while also fitting the API and state-management overlap.",
"role_archetype": null,
"slug": "ios-engineer",
"source": "db"
},
"dimensions": [
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Frontend Programming Languages",
"id": 1,
"rationale": "Languages used to implement browser-side application logic, component behavior, and UI state. This is the core code layer for frontend features and interactive experiences.",
"slug": "frontend-programming-languages",
"source": "db"
},
"input_skill": "JavaScript",
"llm_role": null,
"roles_from_db": [
{
"display_name": "Frontend Engineer",
"id": 3,
"rationale": null,
"role_archetype": "Frontend Engineers design and build the user-facing parts of applications, translating product and design requirements into interactive experiences. They focus on how the application looks, behaves, and responds in the browser, ensuring usability, accessibility, and consistency across the interface.",
"slug": "frontend-engineer",
"source": "db"
},
{
"display_name": "Full Stack Developer",
"id": 2,
"rationale": null,
"role_archetype": null,
"slug": "full-stack-developer",
"source": "db"
}
]
},
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Programming Languages for AI Workflows",
"id": 261,
"rationale": "Languages used to implement AI feature logic, orchestration, and response handling inside product code. This is the core coding surface for turning prompts and model calls into reliable application behavior.",
"slug": "programming-languages-for-ai-workflows",
"source": "db"
},
"input_skill": "JavaScript",
"llm_role": null,
"roles_from_db": [
{
"display_name": "AI Engineer",
"id": 12,
"rationale": null,
"role_archetype": null,
"slug": "ai-engineer",
"source": "db"
}
]
},
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Programming Languages for Test Automation",
"id": 193,
"rationale": "Languages used to implement automated checks, helper utilities, and test harness code. This is the core coding surface for turning test ideas into maintainable automation.",
"slug": "programming-languages-for-test-automation",
"source": "db"
},
"input_skill": "JavaScript",
"llm_role": null,
"roles_from_db": [
{
"display_name": "Automation Tester",
"id": 16,
"rationale": null,
"role_archetype": null,
"slug": "automation-tester",
"source": "db"
}
]
},
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "ServiceNow Scripting and Logic",
"id": 210,
"rationale": "Server-side scripting used to implement workflow behavior, validations, and record logic on the ServiceNow platform. This is the core customization layer for translating requirements into executable platform behavior.",
"slug": "servicenow-scripting-and-logic",
"source": "db"
},
"input_skill": "JavaScript",
"llm_role": null,
"roles_from_db": [
{
"display_name": "ServiceNOW Developer",
"id": 24,
"rationale": null,
"role_archetype": null,
"slug": "servicenow-developer",
"source": "db"
}
]
},
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Responsive Layout and Styling",
"id": 5,
"rationale": "Techniques for translating designs into adaptive layouts and consistent visual presentation across devices. This includes layout systems, styling approaches, and breakpoint-driven behavior.",
"slug": "responsive-layout-and-styling",
"source": "db"
},
"input_skill": "CSS",
"llm_role": null,
"roles_from_db": [
{
"display_name": "Frontend Engineer",
"id": 3,
"rationale": null,
"role_archetype": "Frontend Engineers design and build the user-facing parts of applications, translating product and design requirements into interactive experiences. They focus on how the application looks, behaves, and responds in the browser, ensuring usability, accessibility, and consistency across the interface.",
"slug": "frontend-engineer",
"source": "db"
},
{
"display_name": "Full Stack Developer",
"id": 2,
"rationale": null,
"role_archetype": null,
"slug": "full-stack-developer",
"source": "db"
}
]
},
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "State Management and Client Data",
"id": 3,
"rationale": "Patterns and libraries for managing application state, server-synced data, and cache-aware UI updates. This is a coherent cluster because frontend behavior often depends on local, shared, and remote state coordination.",
"slug": "state-management-and-client-data",
"source": "db"
},
"input_skill": "Redux",
"llm_role": null,
"roles_from_db": [
{
"display_name": "Frontend Engineer",
"id": 3,
"rationale": null,
"role_archetype": "Frontend Engineers design and build the user-facing parts of applications, translating product and design requirements into interactive experiences. They focus on how the application looks, behaves, and responds in the browser, ensuring usability, accessibility, and consistency across the interface.",
"slug": "frontend-engineer",
"source": "db"
},
{
"display_name": "Full Stack Developer",
"id": 2,
"rationale": null,
"role_archetype": null,
"slug": "full-stack-developer",
"source": "db"
},
{
"display_name": "iOS Engineer",
"id": 13,
"rationale": null,
"role_archetype": null,
"slug": "ios-engineer",
"source": "db"
}
]
},
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "API Integration and Data Fetching",
"id": 9,
"rationale": "Connecting frontend applications to backend services and third-party endpoints. This covers request orchestration, error handling, pagination, and shaping remote data for UI consumption.",
"slug": "api-integration-and-data-fetching",
"source": "db"
},
"input_skill": "REST APIs",
"llm_role": null,
"roles_from_db": [
{
"display_name": "Frontend Engineer",
"id": 3,
"rationale": null,
"role_archetype": "Frontend Engineers design and build the user-facing parts of applications, translating product and design requirements into interactive experiences. They focus on how the application looks, behaves, and responds in the browser, ensuring usability, accessibility, and consistency across the interface.",
"slug": "frontend-engineer",
"source": "db"
},
{
"display_name": "Full Stack Developer",
"id": 2,
"rationale": null,
"role_archetype": null,
"slug": "full-stack-developer",
"source": "db"
}
]
},
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "API Integration and Serialization",
"id": 128,
"rationale": "Client-side integration with backend services, including request handling, response parsing, and contract alignment. This cluster is coherent because iOS features frequently depend on stable data exchange with server APIs.",
"slug": "api-integration-and-serialization",
"source": "db"
},
"input_skill": "REST APIs",
"llm_role": null,
"roles_from_db": [
{
"display_name": "iOS Engineer",
"id": 13,
"rationale": null,
"role_archetype": null,
"slug": "ios-engineer",
"source": "db"
}
]
},
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Network Automation and Scripting",
"id": 285,
"rationale": "Covers scripts and automation used to configure, validate, and audit network devices and services. This cluster is coherent because repeatable network operations increasingly depend on programmatic changes and checks.",
"slug": "network-automation-and-scripting",
"source": "db"
},
"input_skill": "REST APIs",
"llm_role": null,
"roles_from_db": [
{
"display_name": "Network Engineer",
"id": 21,
"rationale": null,
"role_archetype": null,
"slug": "network-engineer",
"source": "db"
}
]
},
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Frontend Programming Languages",
"id": 1,
"rationale": "Languages used to implement browser-side application logic, component behavior, and UI state. This is the core code layer for frontend features and interactive experiences.",
"slug": "frontend-programming-languages",
"source": "db"
},
"input_skill": "HTML",
"llm_role": null,
"roles_from_db": [
{
"display_name": "Frontend Engineer",
"id": 3,
"rationale": null,
"role_archetype": "Frontend Engineers design and build the user-facing parts of applications, translating product and design requirements into interactive experiences. They focus on how the application looks, behaves, and responds in the browser, ensuring usability, accessibility, and consistency across the interface.",
"slug": "frontend-engineer",
"source": "db"
},
{
"display_name": "Full Stack Developer",
"id": 2,
"rationale": null,
"role_archetype": null,
"slug": "full-stack-developer",
"source": "db"
}
]
},
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Component Frameworks and Rendering",
"id": 2,
"rationale": "Frameworks and rendering models used to build reusable UI components and page composition. This covers how frontend applications structure views, manage rendering, and organize feature code.",
"slug": "component-frameworks-and-rendering",
"source": "db"
},
"input_skill": "React",
"llm_role": null,
"roles_from_db": [
{
"display_name": "Frontend Engineer",
"id": 3,
"rationale": null,
"role_archetype": "Frontend Engineers design and build the user-facing parts of applications, translating product and design requirements into interactive experiences. They focus on how the application looks, behaves, and responds in the browser, ensuring usability, accessibility, and consistency across the interface.",
"slug": "frontend-engineer",
"source": "db"
},
{
"display_name": "Full Stack Developer",
"id": 2,
"rationale": null,
"role_archetype": null,
"slug": "full-stack-developer",
"source": "db"
}
]
},
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "API Design and Contracting",
"id": 142,
"rationale": "Designing stable service interfaces and request/response contracts for REST, GraphQL, and gRPC endpoints. This is central to backend work because it shapes how clients and downstream services interact with the system.",
"slug": "api-design-and-contracting",
"source": "db"
},
"input_skill": "APIs",
"llm_role": null,
"roles_from_db": [
{
"display_name": "Backend Engineer",
"id": 14,
"rationale": null,
"role_archetype": null,
"slug": "backend-engineer",
"source": "db"
}
]
},
{
"dimension": {
"difficulty_hint": null,
"display_name": "Continuous Integration",
"id": null,
"rationale": "Practices for automatically building, validating, and merging code changes through shared pipelines. This fits CI because the skill refers to the integration stage where commits are tested and verified before delivery.",
"slug": "d_init_01",
"source": "llm"
},
"input_skill": "CI",
"llm_role": null,
"roles_from_db": []
},
{
"dimension": {
"difficulty_hint": null,
"display_name": "Native Platform Development",
"id": null,
"rationale": "Covers building and integrating software using native platform SDKs and APIs rather than cross-platform abstractions. This fits the target skill because \"native\" commonly refers to platform-specific app development and native capabilities on iOS, Android, or desktop runtimes.",
"slug": "d_init_01",
"source": "llm"
},
"input_skill": "Native",
"llm_role": null,
"roles_from_db": []
},
{
"dimension": {
"difficulty_hint": null,
"display_name": "Native Integration Interfaces",
"id": null,
"rationale": "Covers using native interfaces exposed by a host platform to extend application behavior. This applies when \"native\" means calling into platform-native capabilities, modules, or bridges from higher-level application code.",
"slug": "d_init_02",
"source": "llm"
},
"input_skill": "Native",
"llm_role": null,
"roles_from_db": []
},
{
"dimension": {
"difficulty_hint": null,
"display_name": "iOS Application Development",
"id": null,
"rationale": "Building native applications for Apple\u0027s iPhone and iPad platforms using iOS frameworks and platform conventions. This dimension covers the core app development surface that the skill iOS refers to, including UI, device APIs, and app behavior on Apple mobile devices.",
"slug": "d_init_01",
"source": "llm"
},
"input_skill": "iOS",
"llm_role": null,
"roles_from_db": []
}
],
"input_final_skills": [
"JavaScript",
"CSS",
"Redux",
"REST APIs",
"HTML",
"React",
"APIs",
"CI",
"Native",
"iOS"
],
"input_llm_skills": [
"APIs",
"CI",
"Native",
"iOS"
],
"new_aliases_persisted": 0,
"run_id": "de23a89f-0937-4d62-8c3d-a0e7a659ccb2",
"skills_detail": [
{
"aliases_in_db": [
{
"alias_text": "JavaScript",
"alias_type": "CANONICAL",
"id": 1,
"is_primary": true,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "ES2015",
"alias_type": "VERSION",
"id": 3,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "ES2016",
"alias_type": "VERSION",
"id": 4,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "ES2017",
"alias_type": "VERSION",
"id": 5,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "ES2018",
"alias_type": "VERSION",
"id": 6,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "ES2019",
"alias_type": "VERSION",
"id": 7,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "ES2020",
"alias_type": "VERSION",
"id": 8,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "ES2021",
"alias_type": "VERSION",
"id": 9,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "ES2022",
"alias_type": "VERSION",
"id": 10,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "ES2023",
"alias_type": "VERSION",
"id": 11,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "ES2024",
"alias_type": "VERSION",
"id": 12,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "ES6",
"alias_type": "VERSION",
"id": 2,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "ESNext",
"alias_type": "VERSION",
"id": 13,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "JavaScript ES2015",
"alias_type": "VERSION",
"id": 1697,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "JavaScript ES2024",
"alias_type": "VERSION",
"id": 1698,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "JavaScript ES6",
"alias_type": "VERSION",
"id": 1696,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
}
],
"canonical": {
"category_id": 5,
"display_name": "JavaScript",
"id": 1,
"is_also_category": false,
"is_extractable": true,
"skill_nature": "LANGUAGE",
"slug": "javascript",
"sub_category_id": 54,
"typical_lifespan": "EVERGREEN",
"volatility": "STABLE"
},
"dimensions": [
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Frontend Programming Languages",
"id": 1,
"rationale": "Languages used to implement browser-side application logic, component behavior, and UI state. This is the core code layer for frontend features and interactive experiences.",
"slug": "frontend-programming-languages",
"source": "db"
},
"input_skill": "JavaScript",
"llm_role": null,
"roles_from_db": [
{
"display_name": "Frontend Engineer",
"id": 3,
"rationale": null,
"role_archetype": "Frontend Engineers design and build the user-facing parts of applications, translating product and design requirements into interactive experiences. They focus on how the application looks, behaves, and responds in the browser, ensuring usability, accessibility, and consistency across the interface.",
"slug": "frontend-engineer",
"source": "db"
},
{
"display_name": "Full Stack Developer",
"id": 2,
"rationale": null,
"role_archetype": null,
"slug": "full-stack-developer",
"source": "db"
}
]
},
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Programming Languages for AI Workflows",
"id": 261,
"rationale": "Languages used to implement AI feature logic, orchestration, and response handling inside product code. This is the core coding surface for turning prompts and model calls into reliable application behavior.",
"slug": "programming-languages-for-ai-workflows",
"source": "db"
},
"input_skill": "JavaScript",
"llm_role": null,
"roles_from_db": [
{
"display_name": "AI Engineer",
"id": 12,
"rationale": null,
"role_archetype": null,
"slug": "ai-engineer",
"source": "db"
}
]
},
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Programming Languages for Test Automation",
"id": 193,
"rationale": "Languages used to implement automated checks, helper utilities, and test harness code. This is the core coding surface for turning test ideas into maintainable automation.",
"slug": "programming-languages-for-test-automation",
"source": "db"
},
"input_skill": "JavaScript",
"llm_role": null,
"roles_from_db": [
{
"display_name": "Automation Tester",
"id": 16,
"rationale": null,
"role_archetype": null,
"slug": "automation-tester",
"source": "db"
}
]
},
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "ServiceNow Scripting and Logic",
"id": 210,
"rationale": "Server-side scripting used to implement workflow behavior, validations, and record logic on the ServiceNow platform. This is the core customization layer for translating requirements into executable platform behavior.",
"slug": "servicenow-scripting-and-logic",
"source": "db"
},
"input_skill": "JavaScript",
"llm_role": null,
"roles_from_db": [
{
"display_name": "ServiceNOW Developer",
"id": 24,
"rationale": null,
"role_archetype": null,
"slug": "servicenow-developer",
"source": "db"
}
]
}
],
"input_skill": "JavaScript",
"matched_via": "alias",
"new_alias_persisted": false,
"new_alias_text": null,
"new_skill_meta": null,
"source_tag": "db",
"was_in_llm_skills": false
},
{
"aliases_in_db": [
{
"alias_text": "CSS",
"alias_type": "CANONICAL",
"id": 37,
"is_primary": true,
"match_strategy": "CASE_INSENSITIVE"
}
],
"canonical": {
"category_id": 5,
"display_name": "CSS",
"id": 6,
"is_also_category": false,
"is_extractable": true,
"skill_nature": "LANGUAGE",
"slug": "css",
"sub_category_id": 56,
"typical_lifespan": "EVERGREEN",
"volatility": "STABLE"
},
"dimensions": [
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Responsive Layout and Styling",
"id": 5,
"rationale": "Techniques for translating designs into adaptive layouts and consistent visual presentation across devices. This includes layout systems, styling approaches, and breakpoint-driven behavior.",
"slug": "responsive-layout-and-styling",
"source": "db"
},
"input_skill": "CSS",
"llm_role": null,
"roles_from_db": [
{
"display_name": "Frontend Engineer",
"id": 3,
"rationale": null,
"role_archetype": "Frontend Engineers design and build the user-facing parts of applications, translating product and design requirements into interactive experiences. They focus on how the application looks, behaves, and responds in the browser, ensuring usability, accessibility, and consistency across the interface.",
"slug": "frontend-engineer",
"source": "db"
},
{
"display_name": "Full Stack Developer",
"id": 2,
"rationale": null,
"role_archetype": null,
"slug": "full-stack-developer",
"source": "db"
}
]
}
],
"input_skill": "CSS",
"matched_via": "alias",
"new_alias_persisted": false,
"new_alias_text": null,
"new_skill_meta": null,
"source_tag": "db",
"was_in_llm_skills": false
},
{
"aliases_in_db": [
{
"alias_text": "Redux",
"alias_type": "CANONICAL",
"id": 117,
"is_primary": true,
"match_strategy": "CASE_INSENSITIVE"
}
],
"canonical": {
"category_id": 6,
"display_name": "Redux",
"id": 13,
"is_also_category": false,
"is_extractable": true,
"skill_nature": "LIBRARY",
"slug": "redux",
"sub_category_id": 62,
"typical_lifespan": "EVERGREEN",
"volatility": "STABLE"
},
"dimensions": [
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "State Management and Client Data",
"id": 3,
"rationale": "Patterns and libraries for managing application state, server-synced data, and cache-aware UI updates. This is a coherent cluster because frontend behavior often depends on local, shared, and remote state coordination.",
"slug": "state-management-and-client-data",
"source": "db"
},
"input_skill": "Redux",
"llm_role": null,
"roles_from_db": [
{
"display_name": "Frontend Engineer",
"id": 3,
"rationale": null,
"role_archetype": "Frontend Engineers design and build the user-facing parts of applications, translating product and design requirements into interactive experiences. They focus on how the application looks, behaves, and responds in the browser, ensuring usability, accessibility, and consistency across the interface.",
"slug": "frontend-engineer",
"source": "db"
},
{
"display_name": "Full Stack Developer",
"id": 2,
"rationale": null,
"role_archetype": null,
"slug": "full-stack-developer",
"source": "db"
},
{
"display_name": "iOS Engineer",
"id": 13,
"rationale": null,
"role_archetype": null,
"slug": "ios-engineer",
"source": "db"
}
]
}
],
"input_skill": "Redux",
"matched_via": "alias",
"new_alias_persisted": false,
"new_alias_text": null,
"new_skill_meta": null,
"source_tag": "db",
"was_in_llm_skills": false
},
{
"aliases_in_db": [
{
"alias_text": "REST APIs",
"alias_type": "CANONICAL",
"id": 174,
"is_primary": true,
"match_strategy": "CASE_INSENSITIVE"
}
],
"canonical": {
"category_id": 8,
"display_name": "REST APIs",
"id": 49,
"is_also_category": false,
"is_extractable": true,
"skill_nature": "PROTOCOL",
"slug": "rest-apis",
"sub_category_id": 67,
"typical_lifespan": "EVERGREEN",
"volatility": "STABLE"
},
"dimensions": [
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "API Integration and Data Fetching",
"id": 9,
"rationale": "Connecting frontend applications to backend services and third-party endpoints. This covers request orchestration, error handling, pagination, and shaping remote data for UI consumption.",
"slug": "api-integration-and-data-fetching",
"source": "db"
},
"input_skill": "REST APIs",
"llm_role": null,
"roles_from_db": [
{
"display_name": "Frontend Engineer",
"id": 3,
"rationale": null,
"role_archetype": "Frontend Engineers design and build the user-facing parts of applications, translating product and design requirements into interactive experiences. They focus on how the application looks, behaves, and responds in the browser, ensuring usability, accessibility, and consistency across the interface.",
"slug": "frontend-engineer",
"source": "db"
},
{
"display_name": "Full Stack Developer",
"id": 2,
"rationale": null,
"role_archetype": null,
"slug": "full-stack-developer",
"source": "db"
}
]
},
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "API Integration and Serialization",
"id": 128,
"rationale": "Client-side integration with backend services, including request handling, response parsing, and contract alignment. This cluster is coherent because iOS features frequently depend on stable data exchange with server APIs.",
"slug": "api-integration-and-serialization",
"source": "db"
},
"input_skill": "REST APIs",
"llm_role": null,
"roles_from_db": [
{
"display_name": "iOS Engineer",
"id": 13,
"rationale": null,
"role_archetype": null,
"slug": "ios-engineer",
"source": "db"
}
]
},
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Network Automation and Scripting",
"id": 285,
"rationale": "Covers scripts and automation used to configure, validate, and audit network devices and services. This cluster is coherent because repeatable network operations increasingly depend on programmatic changes and checks.",
"slug": "network-automation-and-scripting",
"source": "db"
},
"input_skill": "REST APIs",
"llm_role": null,
"roles_from_db": [
{
"display_name": "Network Engineer",
"id": 21,
"rationale": null,
"role_archetype": null,
"slug": "network-engineer",
"source": "db"
}
]
}
],
"input_skill": "REST APIs",
"matched_via": "alias",
"new_alias_persisted": false,
"new_alias_text": null,
"new_skill_meta": null,
"source_tag": "db",
"was_in_llm_skills": false
},
{
"aliases_in_db": [
{
"alias_text": "HTML",
"alias_type": "CANONICAL",
"id": 29,
"is_primary": true,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "HTML 2.0",
"alias_type": "VERSION",
"id": 34,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "HTML 3.2",
"alias_type": "VERSION",
"id": 35,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "HTML 4",
"alias_type": "VERSION",
"id": 32,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "HTML 4.01",
"alias_type": "VERSION",
"id": 36,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "HTML 5",
"alias_type": "VERSION",
"id": 33,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "HTML4",
"alias_type": "VERSION",
"id": 30,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "HTML5",
"alias_type": "VERSION",
"id": 31,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
}
],
"canonical": {
"category_id": 5,
"display_name": "HTML",
"id": 5,
"is_also_category": false,
"is_extractable": true,
"skill_nature": "LANGUAGE",
"slug": "html",
"sub_category_id": 53,
"typical_lifespan": "EVERGREEN",
"volatility": "STABLE"
},
"dimensions": [
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Frontend Programming Languages",
"id": 1,
"rationale": "Languages used to implement browser-side application logic, component behavior, and UI state. This is the core code layer for frontend features and interactive experiences.",
"slug": "frontend-programming-languages",
"source": "db"
},
"input_skill": "HTML",
"llm_role": null,
"roles_from_db": [
{
"display_name": "Frontend Engineer",
"id": 3,
"rationale": null,
"role_archetype": "Frontend Engineers design and build the user-facing parts of applications, translating product and design requirements into interactive experiences. They focus on how the application looks, behaves, and responds in the browser, ensuring usability, accessibility, and consistency across the interface.",
"slug": "frontend-engineer",
"source": "db"
},
{
"display_name": "Full Stack Developer",
"id": 2,
"rationale": null,
"role_archetype": null,
"slug": "full-stack-developer",
"source": "db"
}
]
}
],
"input_skill": "HTML",
"matched_via": "alias",
"new_alias_persisted": false,
"new_alias_text": null,
"new_skill_meta": null,
"source_tag": "db",
"was_in_llm_skills": false
},
{
"aliases_in_db": [
{
"alias_text": "React",
"alias_type": "CANONICAL",
"id": 38,
"is_primary": true,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "React 0.1",
"alias_type": "VERSION",
"id": 242,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "React 0.10",
"alias_type": "VERSION",
"id": 251,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "React 0.11",
"alias_type": "VERSION",
"id": 252,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "React 0.12",
"alias_type": "VERSION",
"id": 253,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "React 0.13",
"alias_type": "VERSION",
"id": 43,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "React 0.14",
"alias_type": "VERSION",
"id": 44,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "React 0.2",
"alias_type": "VERSION",
"id": 243,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "React 0.3",
"alias_type": "VERSION",
"id": 244,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "React 0.4",
"alias_type": "VERSION",
"id": 245,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "React 0.5",
"alias_type": "VERSION",
"id": 246,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "React 0.6",
"alias_type": "VERSION",
"id": 247,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "React 0.7",
"alias_type": "VERSION",
"id": 248,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "React 0.8",
"alias_type": "VERSION",
"id": 249,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "React 0.9",
"alias_type": "VERSION",
"id": 250,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "React 15",
"alias_type": "VERSION",
"id": 39,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "React 15.x",
"alias_type": "VERSION",
"id": 45,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "React 16",
"alias_type": "VERSION",
"id": 40,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "React 16.x",
"alias_type": "VERSION",
"id": 46,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "React 17",
"alias_type": "VERSION",
"id": 41,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "React 17.x",
"alias_type": "VERSION",
"id": 47,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "React 18",
"alias_type": "VERSION",
"id": 42,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "React 18.x",
"alias_type": "VERSION",
"id": 48,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "React 19",
"alias_type": "VERSION",
"id": 241,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "React 19.x",
"alias_type": "VERSION",
"id": 254,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
}
],
"canonical": {
"category_id": 4,
"display_name": "React",
"id": 7,
"is_also_category": false,
"is_extractable": true,
"skill_nature": "FRAMEWORK",
"slug": "react",
"sub_category_id": 51,
"typical_lifespan": "EVERGREEN",
"volatility": "STABLE"
},
"dimensions": [
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Component Frameworks and Rendering",
"id": 2,
"rationale": "Frameworks and rendering models used to build reusable UI components and page composition. This covers how frontend applications structure views, manage rendering, and organize feature code.",
"slug": "component-frameworks-and-rendering",
"source": "db"
},
"input_skill": "React",
"llm_role": null,
"roles_from_db": [
{
"display_name": "Frontend Engineer",
"id": 3,
"rationale": null,
"role_archetype": "Frontend Engineers design and build the user-facing parts of applications, translating product and design requirements into interactive experiences. They focus on how the application looks, behaves, and responds in the browser, ensuring usability, accessibility, and consistency across the interface.",
"slug": "frontend-engineer",
"source": "db"
},
{
"display_name": "Full Stack Developer",
"id": 2,
"rationale": null,
"role_archetype": null,
"slug": "full-stack-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": false
},
{
"aliases_in_db": [],
"canonical": null,
"dimensions": [
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "API Design and Contracting",
"id": 142,
"rationale": "Designing stable service interfaces and request/response contracts for REST, GraphQL, and gRPC endpoints. This is central to backend work because it shapes how clients and downstream services interact with the system.",
"slug": "api-design-and-contracting",
"source": "db"
},
"input_skill": "APIs",
"llm_role": null,
"roles_from_db": [
{
"display_name": "Backend Engineer",
"id": 14,
"rationale": null,
"role_archetype": null,
"slug": "backend-engineer",
"source": "db"
}
]
}
],
"input_skill": "APIs",
"matched_via": null,
"new_alias_persisted": false,
"new_alias_text": null,
"new_skill_meta": {
"derived": {
"category": "Protocol",
"skill_nature": "PROTOCOL",
"sub_category": "application_programming_interfaces",
"typical_lifespan": "EVERGREEN",
"version_strategy": "NOT_APPLICABLE",
"volatility": "STABLE"
},
"enrichment": {
"ambiguity": {
"ambiguity_flag": false,
"confused_with": [],
"reasoning": "APIs is a standard, well-scoped term in JDs and usually refers to application programming interfaces; it is not typically confused with a different catalog skill."
},
"context_keywords": {
"context_keywords": [
"REST",
"GraphQL",
"OpenAPI",
"Swagger",
"JSON",
"OAuth 2.0",
"API gateway",
"webhooks",
"rate limiting",
"endpoint",
"SDK",
"microservices",
"gRPC",
"Postman",
"versioning"
]
},
"maturity": {
"confidence": 0.98,
"maturity": "well_known",
"reasoning": "APIs are a hiring-pipeline staple across backend, mobile, and platform JDs; REST/GraphQL/API design appears in large volumes of job postings and vendor docs, indicating broad adoption."
},
"skill_id": "apis",
"vendor_license": {
"confidence": 0.99,
"license": null,
"vendor": null,
"year_introduced": null
},
"versioning": {
"current_version": null,
"version_aliases": {},
"versioned": false
}
},
"keep_log": [],
"locked_dimensions": [
{
"description": "Defining API interfaces, payloads, and compatibility rules so systems can communicate reliably. This is the best fit for the skill APIs when the emphasis is on building or specifying the interface itself.",
"exemplar_skills": [
"APIs",
"REST API design",
"OpenAPI",
"Schema design",
"Versioning",
"Idempotency",
"Resource modeling"
],
"in_scope": "APIs, REST API design, endpoint naming, request and response schemas, resource modeling, versioning strategy, backward compatibility, pagination, idempotency, OpenAPI specifications",
"name": "API Design and Contracting",
"out_of_scope": "Automated API test execution, client-side session handling, low-level network protocols, database implementation details",
"overlap_flags": [
{
"reason": "API design is often validated by automated tests, but this dimension is about defining the contract rather than testing it.",
"with_dim_id": "api-and-service-test-automation",
"with_dim_name": null,
"with_role": "Automation Tester"
},
{
"reason": "API design is frequently part of broader service integration work, so the boundary can overlap with backend architecture.",
"with_dim_id": "service-architecture-and-integration",
"with_dim_name": null,
"with_role": "Backend Engineer"
}
],
"tentative_id": "d_init_01"
}
],
"merge_log": [],
"placed": {
"name": "APIs",
"placement_confidence": 0.92,
"primary_dimension": "d_init_01",
"reasoning": "Deterministic JD placement: locked_dimensions has 1 dimension(s) from skill-driven dimension generation after reconciliation; primary_dimension is the first locked dim.",
"secondary_dimensions": [],
"skill_id": "apis"
},
"relationships": {
"child_skills": [],
"parent_skills": [],
"related_to": [
"rest-apis",
"grpc",
"http",
"json",
"oauth-2-0",
"scripted-rest-api",
"outbound-rest-messages",
"mock-servers"
],
"requires": [],
"skill_id": "apis",
"suppress_on_match": []
},
"skill_id": "apis",
"split_log": [],
"typed": {
"alternatives_considered": [],
"confidence": 0.91,
"name": "APIs",
"reasoning": "APIs are best treated as a communication contract between systems, so under the Protocol rule they fit as the interface standard rather than a tool or platform.",
"skill_id": "apis",
"subtype": "application_programming_interfaces",
"type": "Protocol"
},
"warnings": []
},
"source_tag": "llm",
"was_in_llm_skills": true
},
{
"aliases_in_db": [],
"canonical": null,
"dimensions": [
{
"dimension": {
"difficulty_hint": null,
"display_name": "Continuous Integration",
"id": null,
"rationale": "Practices for automatically building, validating, and merging code changes through shared pipelines. This fits CI because the skill refers to the integration stage where commits are tested and verified before delivery.",
"slug": "d_init_01",
"source": "llm"
},
"input_skill": "CI",
"llm_role": null,
"roles_from_db": []
}
],
"input_skill": "CI",
"matched_via": null,
"new_alias_persisted": false,
"new_alias_text": null,
"new_skill_meta": {
"derived": {
"category": "Methodology",
"skill_nature": "METHODOLOGY",
"sub_category": "continuous_integration",
"typical_lifespan": "EVERGREEN",
"version_strategy": "NOT_APPLICABLE",
"volatility": "STABLE"
},
"enrichment": {
"ambiguity": {
"ambiguity_flag": true,
"confused_with": [
"continuous_improvement",
"ci_cd"
],
"reasoning": "\"CI\" is a common acronym for continuous integration, but in JDs it can also mean continuous improvement or be used as shorthand within CI/CD. A parser could reasonably confuse these."
},
"context_keywords": {
"context_keywords": [
"Jenkins",
"GitHub Actions",
"GitLab CI",
"CircleCI",
"Travis CI",
"build pipeline",
"automated testing",
"unit tests",
"integration tests",
"pipeline as code",
"artifact repository",
"merge request",
"pull request",
"build status",
"deployment pipeline"
]
},
"maturity": {
"confidence": 0.96,
"maturity": "well_known",
"reasoning": "CI is a standard hiring-pipeline requirement in DevOps/software JDs, with widespread support in GitHub Actions, GitLab CI, Jenkins, and Azure DevOps; market demand is broad rather than niche."
},
"skill_id": "ci",
"vendor_license": {
"confidence": 0.99,
"license": null,
"vendor": null,
"year_introduced": null
},
"versioning": {
"current_version": null,
"version_aliases": {},
"versioned": false
}
},
"keep_log": [],
"locked_dimensions": [
{
"description": "Practices for automatically building, validating, and merging code changes through shared pipelines. This fits CI because the skill refers to the integration stage where commits are tested and verified before delivery.",
"exemplar_skills": [
"CI",
"continuous integration",
"build verification",
"merge validation",
"pipeline status checks",
"commit-triggered testing"
],
"in_scope": "CI, continuous integration pipelines, automated build verification, merge validation, commit-triggered tests, linting in CI, unit test execution on push, pipeline status checks, pre-merge validation",
"name": "Continuous Integration",
"out_of_scope": "Continuous delivery to production, release orchestration, deployment approvals, runtime monitoring, which belong to deployment and operations dimensions",
"overlap_flags": [
{
"reason": "CI pipelines often use build tools and runners, but this dimension is about the integration workflow rather than the tooling itself.",
"with_dim_id": "build-and-execution-tooling",
"with_dim_name": null,
"with_role": "Automation Tester"
},
{
"reason": "CI commonly executes automated tests, but the test framework dimension owns the test design and implementation details.",
"with_dim_id": "testing-and-automation-frameworks",
"with_dim_name": null,
"with_role": "iOS Engineer"
}
],
"tentative_id": "d_init_01"
}
],
"merge_log": [],
"placed": {
"name": "CI",
"placement_confidence": 0.92,
"primary_dimension": "d_init_01",
"reasoning": "Deterministic JD placement: locked_dimensions has 1 dimension(s) from skill-driven dimension generation after reconciliation; primary_dimension is the first locked dim.",
"secondary_dimensions": [],
"skill_id": "ci"
},
"relationships": {
"child_skills": [],
"parent_skills": [],
"related_to": [
"junit",
"http",
"rbac",
"openid-connect"
],
"requires": [],
"skill_id": "ci",
"suppress_on_match": []
},
"skill_id": "ci",
"split_log": [],
"typed": {
"alternatives_considered": [],
"confidence": 0.93,
"name": "CI",
"reasoning": "CI is fundamentally a way of working for integrating changes frequently and validating them continuously, so by the Concept vs Methodology rule it is a Methodology.",
"skill_id": "ci",
"subtype": "continuous_integration",
"type": "Methodology"
},
"warnings": []
},
"source_tag": "llm",
"was_in_llm_skills": true
},
{
"aliases_in_db": [],
"canonical": null,
"dimensions": [
{
"dimension": {
"difficulty_hint": null,
"display_name": "Native Platform Development",
"id": null,
"rationale": "Covers building and integrating software using native platform SDKs and APIs rather than cross-platform abstractions. This fits the target skill because \"native\" commonly refers to platform-specific app development and native capabilities on iOS, Android, or desktop runtimes.",
"slug": "d_init_01",
"source": "llm"
},
"input_skill": "Native",
"llm_role": null,
"roles_from_db": []
},
{
"dimension": {
"difficulty_hint": null,
"display_name": "Native Integration Interfaces",
"id": null,
"rationale": "Covers using native interfaces exposed by a host platform to extend application behavior. This applies when \"native\" means calling into platform-native capabilities, modules, or bridges from higher-level application code.",
"slug": "d_init_02",
"source": "llm"
},
"input_skill": "Native",
"llm_role": null,
"roles_from_db": []
}
],
"input_skill": "Native",
"matched_via": null,
"new_alias_persisted": false,
"new_alias_text": null,
"new_skill_meta": {
"derived": {
"category": "Concept",
"skill_nature": "CONCEPT",
"sub_category": "native_code",
"typical_lifespan": "EVERGREEN",
"version_strategy": "NOT_APPLICABLE",
"volatility": "STABLE"
},
"enrichment": {
"ambiguity": {
"ambiguity_flag": true,
"confused_with": [
"native_app",
"native_advertising"
],
"reasoning": "\u201cNative\u201d is overloaded in JDs: it can mean native code/app development, native advertising, or native-language/localization contexts. A parser could reasonably confuse this concept with other catalog skills using the same term."
},
"context_keywords": {
"context_keywords": [
"JNI",
"Objective-C",
"Swift",
"Kotlin",
"C++",
"Android NDK",
"iOS",
"Xcode",
"Gradle",
"Cocoa Touch",
"UIKit",
"NDK",
"cross-platform",
"mobile app",
"interop"
]
},
"maturity": {
"confidence": 0.78,
"maturity": "well_known",
"reasoning": "\u201cNative\u201d appears broadly in JDs as native mobile/app development and native code interop; it\u2019s a common hiring keyword across iOS/Android and systems roles, with no sunset or replacement signal."
},
"skill_id": "native",
"vendor_license": {
"confidence": 0.99,
"license": null,
"vendor": null,
"year_introduced": null
},
"versioning": {
"current_version": null,
"version_aliases": {},
"versioned": false
}
},
"keep_log": [],
"locked_dimensions": [
{
"description": "Covers building and integrating software using native platform SDKs and APIs rather than cross-platform abstractions. This fits the target skill because \"native\" commonly refers to platform-specific app development and native capabilities on iOS, Android, or desktop runtimes.",
"exemplar_skills": [
"Native",
"native app development",
"iOS native development",
"Android native development",
"Swift",
"Kotlin",
"Objective-C",
"Java for Android",
"native SDK integration"
],
"in_scope": "Native app development, native SDK usage, platform-specific APIs, native UI components, Native, iOS native development, Android native development, Swift/Objective-C app code, Kotlin/Java Android code, platform bindings, device capabilities, native modules",
"name": "Native Platform Development",
"out_of_scope": "Cross-platform frameworks like React Native or Flutter, backend service development, cloud infrastructure, UI styling and layout, these belong to other dimensions such as frontend, mobile architecture, or service engineering",
"overlap_flags": [
{
"reason": "Native mobile work often includes lifecycle and background execution concerns, but that dimension owns the runtime-behavior specifics.",
"with_dim_id": "app-lifecycle-and-background-tasks",
"with_dim_name": null,
"with_role": "Android Engineer, iOS Engineer"
},
{
"reason": "Native platform development can be validated with platform-specific tests, but testing frameworks are a separate concern.",
"with_dim_id": "testing-and-automation-frameworks",
"with_dim_name": null,
"with_role": "iOS Engineer"
}
],
"tentative_id": "d_init_01"
},
{
"description": "Covers using native interfaces exposed by a host platform to extend application behavior. This applies when \"native\" means calling into platform-native capabilities, modules, or bridges from higher-level application code.",
"exemplar_skills": [
"Native",
"native modules",
"native bridges",
"JNI",
"Swift interoperability",
"Objective-C bridging",
"platform interop",
"native plugin APIs"
],
"in_scope": "Native bridges, native modules, platform interop, host-language extensions, native plugin APIs, device feature access, Native, JNI, Objective-C bridges, Swift interoperability, Android platform services",
"name": "Native Integration Interfaces",
"out_of_scope": "Pure application UI design, general backend APIs, cloud deployment, and cross-platform business logic; those belong to frontend, service, or mobile architecture dimensions",
"overlap_flags": [
{
"reason": "Integration interfaces can resemble service integration, but this dimension is specifically about platform-native extension points.",
"with_dim_id": "service-architecture-and-integration",
"with_dim_name": null,
"with_role": "Backend Engineer"
},
{
"reason": "If \u0027native\u0027 is used only as a language/runtime implementation detail, that would be a different coding dimension rather than platform interop.",
"with_dim_id": "programming-languages-for-ai-workflows",
"with_dim_name": null,
"with_role": "AI Engineer"
}
],
"tentative_id": "d_init_02"
}
],
"merge_log": [],
"placed": {
"name": "Native",
"placement_confidence": 0.92,
"primary_dimension": "d_init_01",
"reasoning": "Deterministic JD placement: locked_dimensions has 2 dimension(s) from skill-driven dimension generation after reconciliation; primary_dimension is the first locked dim.",
"secondary_dimensions": [
"d_init_02"
],
"skill_id": "native"
},
"relationships": {
"child_skills": [],
"parent_skills": [],
"related_to": [],
"requires": [],
"skill_id": "native",
"suppress_on_match": []
},
"skill_id": "native",
"split_log": [],
"typed": {
"alternatives_considered": [
"Architecture: ruled out \u2014 it is not a system-shape pattern.",
"Language: ruled out \u2014 \"Native\" is not a programming or markup language.",
"Tool: ruled out \u2014 it is not software you operate as a user."
],
"confidence": 0.67,
"name": "Native",
"reasoning": "By the Concept vs Methodology rule, \"Native\" is best treated as a knowledge unit describing code or binaries built for a target platform rather than a tool, framework, or runtime.",
"skill_id": "native",
"subtype": "native_code",
"type": "Concept"
},
"warnings": []
},
"source_tag": "llm",
"was_in_llm_skills": true
},
{
"aliases_in_db": [],
"canonical": null,
"dimensions": [
{
"dimension": {
"difficulty_hint": null,
"display_name": "iOS Application Development",
"id": null,
"rationale": "Building native applications for Apple\u0027s iPhone and iPad platforms using iOS frameworks and platform conventions. This dimension covers the core app development surface that the skill iOS refers to, including UI, device APIs, and app behavior on Apple mobile devices.",
"slug": "d_init_01",
"source": "llm"
},
"input_skill": "iOS",
"llm_role": null,
"roles_from_db": []
}
],
"input_skill": "iOS",
"matched_via": null,
"new_alias_persisted": false,
"new_alias_text": null,
"new_skill_meta": {
"derived": {
"category": "Platform",
"skill_nature": "PLATFORM",
"sub_category": "mobile_operating_platform",
"typical_lifespan": "EVERGREEN",
"version_strategy": "SEPARATE_ENTITY",
"volatility": "STABLE"
},
"enrichment": {
"ambiguity": {
"ambiguity_flag": false,
"confused_with": [],
"reasoning": "iOS is a well-known mobile operating platform and is usually unambiguous in JDs; it is unlikely to be confused with a different catalog skill."
},
"context_keywords": {
"context_keywords": [
"Swift",
"Objective-C",
"Xcode",
"UIKit",
"SwiftUI",
"Cocoa Touch",
"Core Data",
"Combine",
"TestFlight",
"App Store Connect",
"Instruments",
"Auto Layout",
"Carthage",
"CocoaPods",
"AVFoundation"
]
},
"maturity": {
"confidence": 0.98,
"maturity": "well_known",
"reasoning": "iOS is a mainstream mobile platform with high JD volume for Swift/iOS roles across consumer and enterprise apps; Apple continues active platform support and releases, indicating broad adoption rather than niche use."
},
"skill_id": "ios",
"vendor_license": {
"confidence": 0.99,
"license": "proprietary",
"vendor": "Apple",
"year_introduced": 2007
},
"versioning": {
"current_version": "iOS 18",
"version_aliases": {
"iOS 1.0": "iOS 1",
"iOS 1.x": "iOS 1",
"iOS 10.0": "iOS 10",
"iOS 10.x": "iOS 10",
"iOS 11.0": "iOS 11",
"iOS 11.x": "iOS 11",
"iOS 12.0": "iOS 12",
"iOS 12.x": "iOS 12",
"iOS 13.0": "iOS 13",
"iOS 13.x": "iOS 13",
"iOS 14.0": "iOS 14",
"iOS 14.x": "iOS 14",
"iOS 15.0": "iOS 15",
"iOS 15.x": "iOS 15",
"iOS 16.0": "iOS 16",
"iOS 16.x": "iOS 16",
"iOS 17.0": "iOS 17",
"iOS 17.x": "iOS 17",
"iOS 18.0": "iOS 18",
"iOS 18.x": "iOS 18",
"iOS 2.0": "iOS 2",
"iOS 2.x": "iOS 2",
"iOS 3.0": "iOS 3",
"iOS 3.x": "iOS 3",
"iOS 4.0": "iOS 4",
"iOS 4.x": "iOS 4",
"iOS 5.0": "iOS 5",
"iOS 5.x": "iOS 5",
"iOS 6.0": "iOS 6",
"iOS 6.x": "iOS 6",
"iOS 7.0": "iOS 7",
"iOS 7.x": "iOS 7",
"iOS 8.0": "iOS 8",
"iOS 8.x": "iOS 8",
"iOS 9.0": "iOS 9",
"iOS 9.x": "iOS 9"
},
"versioned": true
}
},
"keep_log": [],
"locked_dimensions": [
{
"description": "Building native applications for Apple\u0027s iPhone and iPad platforms using iOS frameworks and platform conventions. This dimension covers the core app development surface that the skill iOS refers to, including UI, device APIs, and app behavior on Apple mobile devices.",
"exemplar_skills": [
"iOS",
"Swift",
"Objective-C",
"UIKit",
"SwiftUI",
"Xcode"
],
"in_scope": "iOS, Swift, Objective-C, UIKit, SwiftUI, Xcode, iOS SDK, view controllers, app delegates, device permissions, Apple Human Interface Guidelines",
"name": "iOS Application Development",
"out_of_scope": "Android app development, backend API implementation, web frontend frameworks, macOS desktop apps, server-side Swift services",
"overlap_flags": [
{
"reason": "iOS apps often implement VoiceOver, Dynamic Type, and locale-aware behavior, but those concerns are a distinct accessibility/localization dimension.",
"with_dim_id": "accessibility-and-localization",
"with_dim_name": null,
"with_role": "Android Engineer, iOS Engineer"
},
{
"reason": "iOS development includes lifecycle and background execution APIs, but those behaviors are a narrower platform-specific subcluster.",
"with_dim_id": "app-lifecycle-and-background-tasks",
"with_dim_name": null,
"with_role": "Android Engineer, iOS Engineer"
},
{
"reason": "iOS work frequently uses XCTest and UI testing, but test automation is a separate dimension from app implementation.",
"with_dim_id": "testing-and-automation-frameworks",
"with_dim_name": null,
"with_role": "iOS Engineer"
}
],
"tentative_id": "d_init_01"
}
],
"merge_log": [],
"placed": {
"name": "iOS",
"placement_confidence": 0.92,
"primary_dimension": "d_init_01",
"reasoning": "Deterministic JD placement: locked_dimensions has 1 dimension(s) from skill-driven dimension generation after reconciliation; primary_dimension is the first locked dim.",
"secondary_dimensions": [],
"skill_id": "ios"
},
"relationships": {
"child_skills": [],
"parent_skills": [],
"related_to": [
"android-app-bundle",
"android"
],
"requires": [],
"skill_id": "ios",
"suppress_on_match": []
},
"skill_id": "ios",
"split_log": [],
"typed": {
"alternatives_considered": [],
"confidence": 0.88,
"name": "iOS",
"reasoning": "By the Platform vs Tool rule, iOS is a hosted mobile operating platform with APIs and managed system services rather than software you run locally.",
"skill_id": "ios",
"subtype": "mobile_operating_platform",
"type": "Platform"
},
"warnings": []
},
"source_tag": "llm",
"was_in_llm_skills": true
}
],
"unmatched_skills": [
"APIs",
"CI",
"Native",
"iOS"
]
}
API 3 — final-role-output
{
"chosen_role": {
"display_name": "iOS Engineer",
"id": 13,
"rationale": "The map includes iOS and Native signals, and iOS Engineer is the only candidate directly tied to those dimensions while also fitting the API and state-management overlap.",
"role_archetype": null,
"slug": "ios-engineer",
"source": "db"
},
"final_input_skills": [
{
"skill": "JavaScript",
"tag": "in_db"
},
{
"skill": "CSS",
"tag": "in_db"
},
{
"skill": "Redux",
"tag": "in_db"
},
{
"skill": "REST APIs",
"tag": "in_db"
},
{
"skill": "HTML",
"tag": "in_db"
},
{
"skill": "React",
"tag": "in_db"
},
{
"skill": "APIs",
"tag": "new"
},
{
"skill": "CI",
"tag": "new"
},
{
"skill": "Native",
"tag": "new"
},
{
"skill": "iOS",
"tag": "new"
}
],
"persistence": {
"items": [
{
"chosen_role_id": 13,
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Frontend Programming Languages",
"id": 1,
"rationale": "Languages used to implement browser-side application logic, component behavior, and UI state. This is the core code layer for frontend features and interactive experiences.",
"slug": "frontend-programming-languages",
"source": "db"
},
"dimension_id": 1,
"input_skill": "JavaScript",
"llm_role": null,
"matched_chosen_role": false,
"role_dimension_saved": false,
"roles_from_db": [
{
"display_name": "Frontend Engineer",
"id": 3,
"rationale": null,
"role_archetype": "Frontend Engineers design and build the user-facing parts of applications, translating product and design requirements into interactive experiences. They focus on how the application looks, behaves, and responds in the browser, ensuring usability, accessibility, and consistency across the interface.",
"slug": "frontend-engineer",
"source": "db"
},
{
"display_name": "Full Stack Developer",
"id": 2,
"rationale": null,
"role_archetype": null,
"slug": "full-stack-developer",
"source": "db"
}
],
"skill_dimension_saved": false,
"skill_id": 1,
"skill_tag": "in_db",
"skipped_reason": "TODO: REMOVE AFTER TESTING \u2014 api3_writes_enabled=False (writes disabled)"
},
{
"chosen_role_id": 13,
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Programming Languages for AI Workflows",
"id": 261,
"rationale": "Languages used to implement AI feature logic, orchestration, and response handling inside product code. This is the core coding surface for turning prompts and model calls into reliable application behavior.",
"slug": "programming-languages-for-ai-workflows",
"source": "db"
},
"dimension_id": 261,
"input_skill": "JavaScript",
"llm_role": null,
"matched_chosen_role": false,
"role_dimension_saved": false,
"roles_from_db": [
{
"display_name": "AI Engineer",
"id": 12,
"rationale": null,
"role_archetype": null,
"slug": "ai-engineer",
"source": "db"
}
],
"skill_dimension_saved": false,
"skill_id": 1,
"skill_tag": "in_db",
"skipped_reason": "TODO: REMOVE AFTER TESTING \u2014 api3_writes_enabled=False (writes disabled)"
},
{
"chosen_role_id": 13,
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Programming Languages for Test Automation",
"id": 193,
"rationale": "Languages used to implement automated checks, helper utilities, and test harness code. This is the core coding surface for turning test ideas into maintainable automation.",
"slug": "programming-languages-for-test-automation",
"source": "db"
},
"dimension_id": 193,
"input_skill": "JavaScript",
"llm_role": null,
"matched_chosen_role": false,
"role_dimension_saved": false,
"roles_from_db": [
{
"display_name": "Automation Tester",
"id": 16,
"rationale": null,
"role_archetype": null,
"slug": "automation-tester",
"source": "db"
}
],
"skill_dimension_saved": false,
"skill_id": 1,
"skill_tag": "in_db",
"skipped_reason": "TODO: REMOVE AFTER TESTING \u2014 api3_writes_enabled=False (writes disabled)"
},
{
"chosen_role_id": 13,
"dimension": {
"difficulty_hint": "well_known",
"display_name": "ServiceNow Scripting and Logic",
"id": 210,
"rationale": "Server-side scripting used to implement workflow behavior, validations, and record logic on the ServiceNow platform. This is the core customization layer for translating requirements into executable platform behavior.",
"slug": "servicenow-scripting-and-logic",
"source": "db"
},
"dimension_id": 210,
"input_skill": "JavaScript",
"llm_role": null,
"matched_chosen_role": false,
"role_dimension_saved": false,
"roles_from_db": [
{
"display_name": "ServiceNOW Developer",
"id": 24,
"rationale": null,
"role_archetype": null,
"slug": "servicenow-developer",
"source": "db"
}
],
"skill_dimension_saved": false,
"skill_id": 1,
"skill_tag": "in_db",
"skipped_reason": "TODO: REMOVE AFTER TESTING \u2014 api3_writes_enabled=False (writes disabled)"
},
{
"chosen_role_id": 13,
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Responsive Layout and Styling",
"id": 5,
"rationale": "Techniques for translating designs into adaptive layouts and consistent visual presentation across devices. This includes layout systems, styling approaches, and breakpoint-driven behavior.",
"slug": "responsive-layout-and-styling",
"source": "db"
},
"dimension_id": 5,
"input_skill": "CSS",
"llm_role": null,
"matched_chosen_role": false,
"role_dimension_saved": false,
"roles_from_db": [
{
"display_name": "Frontend Engineer",
"id": 3,
"rationale": null,
"role_archetype": "Frontend Engineers design and build the user-facing parts of applications, translating product and design requirements into interactive experiences. They focus on how the application looks, behaves, and responds in the browser, ensuring usability, accessibility, and consistency across the interface.",
"slug": "frontend-engineer",
"source": "db"
},
{
"display_name": "Full Stack Developer",
"id": 2,
"rationale": null,
"role_archetype": null,
"slug": "full-stack-developer",
"source": "db"
}
],
"skill_dimension_saved": false,
"skill_id": 6,
"skill_tag": "in_db",
"skipped_reason": "TODO: REMOVE AFTER TESTING \u2014 api3_writes_enabled=False (writes disabled)"
},
{
"chosen_role_id": 13,
"dimension": {
"difficulty_hint": "well_known",
"display_name": "State Management and Client Data",
"id": 3,
"rationale": "Patterns and libraries for managing application state, server-synced data, and cache-aware UI updates. This is a coherent cluster because frontend behavior often depends on local, shared, and remote state coordination.",
"slug": "state-management-and-client-data",
"source": "db"
},
"dimension_id": 3,
"input_skill": "Redux",
"llm_role": null,
"matched_chosen_role": true,
"role_dimension_saved": false,
"roles_from_db": [
{
"display_name": "Frontend Engineer",
"id": 3,
"rationale": null,
"role_archetype": "Frontend Engineers design and build the user-facing parts of applications, translating product and design requirements into interactive experiences. They focus on how the application looks, behaves, and responds in the browser, ensuring usability, accessibility, and consistency across the interface.",
"slug": "frontend-engineer",
"source": "db"
},
{
"display_name": "Full Stack Developer",
"id": 2,
"rationale": null,
"role_archetype": null,
"slug": "full-stack-developer",
"source": "db"
},
{
"display_name": "iOS Engineer",
"id": 13,
"rationale": null,
"role_archetype": null,
"slug": "ios-engineer",
"source": "db"
}
],
"skill_dimension_saved": false,
"skill_id": 13,
"skill_tag": "in_db",
"skipped_reason": "TODO: REMOVE AFTER TESTING \u2014 api3_writes_enabled=False (writes disabled)"
},
{
"chosen_role_id": 13,
"dimension": {
"difficulty_hint": "well_known",
"display_name": "API Integration and Data Fetching",
"id": 9,
"rationale": "Connecting frontend applications to backend services and third-party endpoints. This covers request orchestration, error handling, pagination, and shaping remote data for UI consumption.",
"slug": "api-integration-and-data-fetching",
"source": "db"
},
"dimension_id": 9,
"input_skill": "REST APIs",
"llm_role": null,
"matched_chosen_role": false,
"role_dimension_saved": false,
"roles_from_db": [
{
"display_name": "Frontend Engineer",
"id": 3,
"rationale": null,
"role_archetype": "Frontend Engineers design and build the user-facing parts of applications, translating product and design requirements into interactive experiences. They focus on how the application looks, behaves, and responds in the browser, ensuring usability, accessibility, and consistency across the interface.",
"slug": "frontend-engineer",
"source": "db"
},
{
"display_name": "Full Stack Developer",
"id": 2,
"rationale": null,
"role_archetype": null,
"slug": "full-stack-developer",
"source": "db"
}
],
"skill_dimension_saved": false,
"skill_id": 49,
"skill_tag": "in_db",
"skipped_reason": "TODO: REMOVE AFTER TESTING \u2014 api3_writes_enabled=False (writes disabled)"
},
{
"chosen_role_id": 13,
"dimension": {
"difficulty_hint": "well_known",
"display_name": "API Integration and Serialization",
"id": 128,
"rationale": "Client-side integration with backend services, including request handling, response parsing, and contract alignment. This cluster is coherent because iOS features frequently depend on stable data exchange with server APIs.",
"slug": "api-integration-and-serialization",
"source": "db"
},
"dimension_id": 128,
"input_skill": "REST APIs",
"llm_role": null,
"matched_chosen_role": true,
"role_dimension_saved": false,
"roles_from_db": [
{
"display_name": "iOS Engineer",
"id": 13,
"rationale": null,
"role_archetype": null,
"slug": "ios-engineer",
"source": "db"
}
],
"skill_dimension_saved": false,
"skill_id": 49,
"skill_tag": "in_db",
"skipped_reason": "TODO: REMOVE AFTER TESTING \u2014 api3_writes_enabled=False (writes disabled)"
},
{
"chosen_role_id": 13,
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Network Automation and Scripting",
"id": 285,
"rationale": "Covers scripts and automation used to configure, validate, and audit network devices and services. This cluster is coherent because repeatable network operations increasingly depend on programmatic changes and checks.",
"slug": "network-automation-and-scripting",
"source": "db"
},
"dimension_id": 285,
"input_skill": "REST APIs",
"llm_role": null,
"matched_chosen_role": false,
"role_dimension_saved": false,
"roles_from_db": [
{
"display_name": "Network Engineer",
"id": 21,
"rationale": null,
"role_archetype": null,
"slug": "network-engineer",
"source": "db"
}
],
"skill_dimension_saved": false,
"skill_id": 49,
"skill_tag": "in_db",
"skipped_reason": "TODO: REMOVE AFTER TESTING \u2014 api3_writes_enabled=False (writes disabled)"
},
{
"chosen_role_id": 13,
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Frontend Programming Languages",
"id": 1,
"rationale": "Languages used to implement browser-side application logic, component behavior, and UI state. This is the core code layer for frontend features and interactive experiences.",
"slug": "frontend-programming-languages",
"source": "db"
},
"dimension_id": 1,
"input_skill": "HTML",
"llm_role": null,
"matched_chosen_role": false,
"role_dimension_saved": false,
"roles_from_db": [
{
"display_name": "Frontend Engineer",
"id": 3,
"rationale": null,
"role_archetype": "Frontend Engineers design and build the user-facing parts of applications, translating product and design requirements into interactive experiences. They focus on how the application looks, behaves, and responds in the browser, ensuring usability, accessibility, and consistency across the interface.",
"slug": "frontend-engineer",
"source": "db"
},
{
"display_name": "Full Stack Developer",
"id": 2,
"rationale": null,
"role_archetype": null,
"slug": "full-stack-developer",
"source": "db"
}
],
"skill_dimension_saved": false,
"skill_id": 5,
"skill_tag": "in_db",
"skipped_reason": "TODO: REMOVE AFTER TESTING \u2014 api3_writes_enabled=False (writes disabled)"
},
{
"chosen_role_id": 13,
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Component Frameworks and Rendering",
"id": 2,
"rationale": "Frameworks and rendering models used to build reusable UI components and page composition. This covers how frontend applications structure views, manage rendering, and organize feature code.",
"slug": "component-frameworks-and-rendering",
"source": "db"
},
"dimension_id": 2,
"input_skill": "React",
"llm_role": null,
"matched_chosen_role": false,
"role_dimension_saved": false,
"roles_from_db": [
{
"display_name": "Frontend Engineer",
"id": 3,
"rationale": null,
"role_archetype": "Frontend Engineers design and build the user-facing parts of applications, translating product and design requirements into interactive experiences. They focus on how the application looks, behaves, and responds in the browser, ensuring usability, accessibility, and consistency across the interface.",
"slug": "frontend-engineer",
"source": "db"
},
{
"display_name": "Full Stack Developer",
"id": 2,
"rationale": null,
"role_archetype": null,
"slug": "full-stack-developer",
"source": "db"
}
],
"skill_dimension_saved": false,
"skill_id": 7,
"skill_tag": "in_db",
"skipped_reason": "TODO: REMOVE AFTER TESTING \u2014 api3_writes_enabled=False (writes disabled)"
},
{
"chosen_role_id": 13,
"dimension": {
"difficulty_hint": "well_known",
"display_name": "API Design and Contracting",
"id": 142,
"rationale": "Designing stable service interfaces and request/response contracts for REST, GraphQL, and gRPC endpoints. This is central to backend work because it shapes how clients and downstream services interact with the system.",
"slug": "api-design-and-contracting",
"source": "db"
},
"dimension_id": 142,
"input_skill": "APIs",
"llm_role": null,
"matched_chosen_role": false,
"role_dimension_saved": false,
"roles_from_db": [
{
"display_name": "Backend Engineer",
"id": 14,
"rationale": null,
"role_archetype": null,
"slug": "backend-engineer",
"source": "db"
}
],
"skill_dimension_saved": false,
"skill_id": null,
"skill_tag": "new",
"skipped_reason": "skill_not_in_db_v3_proposed"
},
{
"chosen_role_id": 13,
"dimension": {
"difficulty_hint": null,
"display_name": "Continuous Integration",
"id": null,
"rationale": "Practices for automatically building, validating, and merging code changes through shared pipelines. This fits CI because the skill refers to the integration stage where commits are tested and verified before delivery.",
"slug": "d_init_01",
"source": "llm"
},
"dimension_id": null,
"input_skill": "CI",
"llm_role": null,
"matched_chosen_role": false,
"role_dimension_saved": false,
"roles_from_db": [],
"skill_dimension_saved": false,
"skill_id": null,
"skill_tag": "new",
"skipped_reason": "skill_not_in_db_v3_proposed"
},
{
"chosen_role_id": 13,
"dimension": {
"difficulty_hint": null,
"display_name": "Native Platform Development",
"id": null,
"rationale": "Covers building and integrating software using native platform SDKs and APIs rather than cross-platform abstractions. This fits the target skill because \"native\" commonly refers to platform-specific app development and native capabilities on iOS, Android, or desktop runtimes.",
"slug": "d_init_01",
"source": "llm"
},
"dimension_id": null,
"input_skill": "Native",
"llm_role": null,
"matched_chosen_role": false,
"role_dimension_saved": false,
"roles_from_db": [],
"skill_dimension_saved": false,
"skill_id": null,
"skill_tag": "new",
"skipped_reason": "skill_not_in_db_v3_proposed"
},
{
"chosen_role_id": 13,
"dimension": {
"difficulty_hint": null,
"display_name": "Native Integration Interfaces",
"id": null,
"rationale": "Covers using native interfaces exposed by a host platform to extend application behavior. This applies when \"native\" means calling into platform-native capabilities, modules, or bridges from higher-level application code.",
"slug": "d_init_02",
"source": "llm"
},
"dimension_id": null,
"input_skill": "Native",
"llm_role": null,
"matched_chosen_role": false,
"role_dimension_saved": false,
"roles_from_db": [],
"skill_dimension_saved": false,
"skill_id": null,
"skill_tag": "new",
"skipped_reason": "skill_not_in_db_v3_proposed"
},
{
"chosen_role_id": 13,
"dimension": {
"difficulty_hint": null,
"display_name": "iOS Application Development",
"id": null,
"rationale": "Building native applications for Apple\u0027s iPhone and iPad platforms using iOS frameworks and platform conventions. This dimension covers the core app development surface that the skill iOS refers to, including UI, device APIs, and app behavior on Apple mobile devices.",
"slug": "d_init_01",
"source": "llm"
},
"dimension_id": null,
"input_skill": "iOS",
"llm_role": null,
"matched_chosen_role": false,
"role_dimension_saved": false,
"roles_from_db": [],
"skill_dimension_saved": false,
"skill_id": null,
"skill_tag": "new",
"skipped_reason": "skill_not_in_db_v3_proposed"
}
],
"new_skills_created": 0,
"role_dimension_saved": 0,
"skill_dimension_saved": 0,
"skipped": 16
},
"planner_output": null,
"run_id": "de23a89f-0937-4d62-8c3d-a0e7a659ccb2"
}
LLM Calls
Every model call made for this run, in pipeline order. Click a card to see the model's response.
Loading…