Pipeline run
a057c8f6-e315-4a2a-b70a-371e8908bf02
Client output enrichment
v2 Skill cluster · Nature of work · AI index · Tech stack maturity · Evidence · KRA descriptionvocab breakdown (legacy)
Signals
1 POST /skills/extract-from-jd
2 POST /skills/extract-details
3 POST /skills/final-role-output
Native Mobile Developer
→iOS Developer
sub-role · 0.95 CASE Aslug: native-mobile-developer · id: 75 · source: db · sub-role slug: ios-engineer
Multi-alias tie (3 roles at 1.0) resolved by TIER_B_TITLE: iOS Developer
Resolution:
in_db
— role exists in library; skill↔dim and role↔dim links saved when applicable.
Job description
📍 Noida | 🧑💼 Full-Time | 🌍 IT Services | 💼 2–5 Years Experience Grepix Infotech Pvt Ltd is looking for an experienced iOS Developer to join our team in Noida. This is a full time, onsite role only. No remote work. Experience Minimum 2 years in iOS application development Location Noida only Work from office Key Skills Required • Strong experience in Swift • Good understanding of iOS frameworks and Apple guidelines • Hands on experience with Maps and location based features • Ability to implement complex business logic • Strong understanding of Data Structures • Excellent debugging and problem solving skills • Experience with REST API integration Good to Have • Experience in apps involving real time location tracking • App Store deployment experience What We Offer • Opportunity to work on scalable, real world applications • Growth oriented and collaborative work environment • Long term career opportunities 📩 Apply Now Send your CV to hr@grepixit.com Subject: Application – iOS Developer
Skills from this JD
Each row merges API 1 extraction, API 2 library match / v3 orchestration (dimensions + locked dims), and API 3 persistence tags.
Aliases — catalog
- iOS (CANONICAL)
Context tags (catalog)
Stored enrichment (catalog DB)
- Category
- Platform
- Sub-category
- Mobile Operating Platform
- Vendor
- Apple Inc.
- License
- proprietary
- Year introduced
- 2007
- Confidence
- 0.93
- Version strategy
- NOT_APPLICABLE
Maturity 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 profile (library / DB)
- Skill nature
- PLATFORM
- Volatility
- STABLE
- Typical lifespan
- EVERGREEN
- Category id
- 9
- Sub-category id
- 1200
- Extractable
- True
- Also category
- False
Dimensions (API 2 worklist)
-
React Frontend Development Catalog dimension db id 96
Library dimension (catalog)
API 3 link attempts (this skill)
| Dimension | Skill↔dim | Role↔dim | Outcome |
|---|---|---|---|
|
React Frontend Development
d_init_01
|
✓ | — | Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role) |
Aliases — catalog
- Swift (CANONICAL) primary
- Swift 2.0 (VERSION)
- Swift 2.x (VERSION)
- Swift 3.0 (VERSION)
- Swift 3.x (VERSION)
- Swift 4.0 (VERSION)
- Swift 4.x (VERSION)
- Swift 5.0 (VERSION)
- Swift 5.x (VERSION)
- Swift 6.0 (VERSION)
- Swift 6.x (VERSION)
Context tags (catalog)
Stored enrichment (catalog DB)
- Category
- Language
- Sub-category
- Programming Language
- Vendor
- Apple
- License
- apache_2
- Year introduced
- 2014
- Confidence
- 0.99
- Version strategy
- NOT_APPLICABLE
Maturity reasoning: Swift is broadly used for iOS/macOS hiring; job postings commonly list it alongside UIKit/SwiftUI, and Apple continues to invest in it as the primary language for new app development.
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)
-
Native Mobile Languages Catalog dimension db id 274
Library dimension (catalog)
Roles linked in library: Native Mobile Developer
-
Swift and Objective-C Catalog dimension db id 81
Library dimension (catalog)
Roles linked in library: iOS Developer
API 3 link attempts (this skill)
| Dimension | Skill↔dim | Role↔dim | Outcome |
|---|---|---|---|
|
Native Mobile Languages
native-mobile-languages
|
✓ | ✓ | Existing dimension (library) · Role↔dimension saved |
|
Swift and Objective-C
swift-and-objective-c
|
✓ | — | Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role) |
Aliases — catalog
- REST (CANONICAL) primary
Context tags (catalog)
Stored enrichment (catalog DB)
- Category
- Concept
- Sub-category
- Api Architecture Style
- Year introduced
- 2000
- Confidence
- 0.88
- Version strategy
- NOT_APPLICABLE
Maturity reasoning: REST is a default API architecture in many job descriptions and is widely supported by major vendors/frameworks; OpenAPI and RESTful endpoints remain standard in hiring pipelines.
Skill profile (library / DB)
- Skill nature
- CONCEPT
- Volatility
- STABLE
- Typical lifespan
- EVERGREEN
- Category id
- 2
- Sub-category id
- 2122
- Extractable
- True
- Also category
- False
Dimensions (API 2 worklist)
-
API Design and Contracts Catalog dimension db id 3
Library dimension (catalog)
Roles linked in library: Backend Developer, Fullstack Developer
-
API Interface and Contract Design Catalog dimension db id 289
Library dimension (catalog)
Roles linked in library: .NET Backend Developer, Go Backend Developer, Kotlin Backend Developer, Node.js Backend Developer, PHP Backend Developer, Python Backend Developer, Ruby Backend Developer, Scala Backend Developer
-
Integration Protocols & Standards Catalog dimension db id 271
Library dimension (catalog)
Roles linked in library: Pega Developer
-
Standards & Protocols Compliance Catalog dimension db id 452
Library dimension (catalog)
Roles linked in library: Sitecore Dev
API 3 link attempts (this skill)
| Dimension | Skill↔dim | Role↔dim | Outcome |
|---|---|---|---|
|
API Design and Contracts
api-design-and-contracts
|
✓ | — | Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role) |
|
API Interface and Contract Design
api-interface-and-contract-design
|
✓ | — | Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role) |
|
Integration Protocols & Standards
integration-protocols-standards
|
✓ | — | Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role) |
|
Standards & Protocols Compliance
standards-protocols-compliance
|
✓ | — | Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role) |
Skill enrichment (orchestrator / LLM)
No Stage 7 enrichment blob on this skill (orchestrator skipped enrichment).
- Category
- Other
- Sub-category
- general
- Skill nature
- TOOL
- Volatility
- MEDIUM
- Typical lifespan
- MULTI_YEAR
- Version strategy
- UNVERSIONED
Aliases — catalog
- location services (CANONICAL) primary
Context tags (catalog)
Stored enrichment (catalog DB)
- Category
- Service
- Sub-category
- Device Location Service
- Confidence
- 0.74
- Version strategy
- NOT_APPLICABLE
Maturity reasoning: Common in mobile/backend JDs for geofencing, maps, and delivery apps; major vendors like Google Maps Platform and Apple Core Location remain standard market signals.
Skill profile (library / DB)
- Skill nature
- CLOUD_SERVICE
- Volatility
- STABLE
- Typical lifespan
- EVERGREEN
- Category id
- 11
- Sub-category id
- 719
- Extractable
- True
- Also category
- False
Dimensions (API 2 worklist)
-
Device APIs and Hardware Features Catalog dimension db id 95
Library dimension (catalog)
Roles linked in library: Android Developer, Native Mobile Developer, iOS Developer
-
Device APIs and Hardware Integration Catalog dimension db id 171
Library dimension (catalog)
Roles linked in library: Hybrid Mobile Developer, React Native Developer
API 3 link attempts (this skill)
| Dimension | Skill↔dim | Role↔dim | Outcome |
|---|---|---|---|
|
Device APIs and Hardware Features
device-apis-and-hardware-features
|
✓ | ✓ | Existing dimension (library) · Role↔dimension saved |
|
Device APIs and Hardware Integration
device-apis-and-hardware-integration
|
✓ | — | Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role) |
Aliases — catalog
- Apple App Store (CANONICAL) primary
Context tags (catalog)
Stored enrichment (catalog DB)
- Category
- Platform
- Sub-category
- App Distribution Platform
- Vendor
- Apple Inc.
- License
- proprietary
- Year introduced
- 2008
- Confidence
- 0.98
- Version strategy
- NOT_APPLICABLE
Maturity reasoning: Broadly used app distribution platform; App Store review and release management appear in many iOS job descriptions and are a standard requirement for shipping Apple apps.
Skill profile (library / DB)
- Skill nature
- PLATFORM
- Volatility
- STABLE
- Typical lifespan
- EVERGREEN
- Category id
- 9
- Sub-category id
- 347
- Extractable
- True
- Also category
- False
Dimensions (API 2 worklist)
-
Mobile Vendor Platforms Catalog dimension db id 172
Library dimension (catalog)
Roles linked in library: Hybrid Mobile Developer
API 3 link attempts (this skill)
| Dimension | Skill↔dim | Role↔dim | Outcome |
|---|---|---|---|
|
Mobile Vendor Platforms
mobile-vendor-platforms
|
— | — |
Skipped — no persistable v3 meta for new skill
skill_not_in_db_v3_proposed
|
All API 3 persistence rows
Same grid as the skill-extractor “Persistence items” table: one row per (skill × dimension) work item.
| Skill | Tag | Dimension | Skill↔dim | Role↔dim | Outcome | Notes |
|---|---|---|---|---|---|---|
| iOS | in_db |
React Frontend Development
d_init_01
|
✓ | — | Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role) | |
| Swift | in_db |
Native Mobile Languages
native-mobile-languages
|
✓ | ✓ | Existing dimension (library) · Role↔dimension saved | |
| Swift | in_db |
Swift and Objective-C
swift-and-objective-c
|
✓ | — | 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) | |
| Location Services | in_db |
Device APIs and Hardware Features
device-apis-and-hardware-features
|
✓ | ✓ | Existing dimension (library) · Role↔dimension saved | |
| Location Services | in_db |
Device APIs and Hardware Integration
device-apis-and-hardware-integration
|
✓ | — | Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role) | |
| App Store | new |
Mobile Vendor Platforms
mobile-vendor-platforms
|
— | — | Skipped — no persistable v3 meta for new skill | skill_not_in_db_v3_proposed |
Library artifacts (this run)
| Kind | Detail | DB id |
|---|---|---|
| canonical_skill_proposed | Maps | type=Other subtype=general nature=TOOL lifespan=MULTI_YEAR | |
| dimension_skill_link_proposed | App Store ↔ Mobile Vendor Platforms |
nano JD Parser — gpt-4.1-nano click to toggle
Show raw JSON
{
"JD_type": "pass",
"about_company": null,
"certifications": [],
"company_name": "Grepix Infotech Pvt Ltd",
"ctc": null,
"domain": {
"primary": {
"aliases": [],
"domain": "IT Services"
},
"secondary": null
},
"education": [],
"experience": {
"max": 5,
"min": 2,
"raw": "2\u20135 Years Experience"
},
"job_locations": [
{
"aliases": [
"Noida"
],
"city": "Noida",
"country": "India",
"state": null,
"work_mode": "onsite"
}
],
"role": "iOS Developer",
"role_aliases": [
"iOS Engineer",
"Mobile Developer",
"iOS Application Developer"
],
"role_archetype": "Engineering",
"roles_and_responsibilities": [
{
"bullet_count": 0,
"heading": "Experience",
"heading_was_present": true,
"source_marker": {
"first_5_words": "Minimum 2 years in iOS",
"last_5_words": "application development"
},
"text": "Minimum 2 years in iOS application development",
"word_count": 9
},
{
"bullet_count": 7,
"heading": "Key Skills Required",
"heading_was_present": true,
"source_marker": {
"first_5_words": "\u2022 Strong experience in Swift",
"last_5_words": "with REST API integration"
},
"text": "\u2022 Strong experience in Swift\n\u2022 Good understanding of iOS frameworks and Apple guidelines\n\u2022 Hands on experience with Maps and location based features\n\u2022 Ability to implement complex business logic\n\u2022 Strong understanding of Data Structures\n\u2022 Excellent debugging and problem solving skills\n\u2022 Experience with REST API integration",
"word_count": 43
},
{
"bullet_count": 2,
"heading": "Good to Have",
"heading_was_present": true,
"source_marker": {
"first_5_words": "\u2022 Experience in apps involving",
"last_5_words": "deployment experience"
},
"text": "\u2022 Experience in apps involving real time location tracking\n\u2022 App Store deployment experience",
"word_count": 18
},
{
"bullet_count": 3,
"heading": "What We Offer",
"heading_was_present": true,
"source_marker": {
"first_5_words": "\u2022 Opportunity to work on",
"last_5_words": "long term career opportunities"
},
"text": "\u2022 Opportunity to work on scalable, real world applications\n\u2022 Growth oriented and collaborative work environment\n\u2022 Long term career opportunities",
"word_count": 22
}
],
"urls": [
{
"type": "other",
"url": "hr@grepixit.com"
}
]
}
API 1 — extract-from-jd click to toggle
{
"final_skills": [
{
"is_primary": true,
"skill_name": "iOS"
},
{
"is_primary": true,
"skill_name": "Swift"
},
{
"is_primary": true,
"skill_name": "REST"
},
{
"is_primary": false,
"skill_name": "Maps"
},
{
"is_primary": false,
"skill_name": "Location Services"
},
{
"is_primary": false,
"skill_name": "App Store"
}
],
"jd_role": {
"display_name": "iOS Developer",
"rationale": null,
"role_aliases": [
"iOS Engineer",
"Mobile Developer",
"iOS Application Developer"
],
"role_archetype": "Engineering",
"slug": ""
},
"nano_parsed": {
"JD_type": "pass",
"about_company": null,
"certifications": [],
"company_name": "Grepix Infotech Pvt Ltd",
"ctc": null,
"domain": {
"primary": {
"aliases": [],
"domain": "IT Services"
},
"secondary": null
},
"education": [],
"experience": {
"max": 5,
"min": 2,
"raw": "2\u20135 Years Experience"
},
"job_locations": [
{
"aliases": [
"Noida"
],
"city": "Noida",
"country": "India",
"state": null,
"work_mode": "onsite"
}
],
"role": "iOS Developer",
"role_aliases": [
"iOS Engineer",
"Mobile Developer",
"iOS Application Developer"
],
"role_archetype": "Engineering",
"roles_and_responsibilities": [
{
"bullet_count": 0,
"heading": "Experience",
"heading_was_present": true,
"source_marker": {
"first_5_words": "Minimum 2 years in iOS",
"last_5_words": "application development"
},
"text": "Minimum 2 years in iOS application development",
"word_count": 9
},
{
"bullet_count": 7,
"heading": "Key Skills Required",
"heading_was_present": true,
"source_marker": {
"first_5_words": "\u2022 Strong experience in Swift",
"last_5_words": "with REST API integration"
},
"text": "\u2022 Strong experience in Swift\n\u2022 Good understanding of iOS frameworks and Apple guidelines\n\u2022 Hands on experience with Maps and location based features\n\u2022 Ability to implement complex business logic\n\u2022 Strong understanding of Data Structures\n\u2022 Excellent debugging and problem solving skills\n\u2022 Experience with REST API integration",
"word_count": 43
},
{
"bullet_count": 2,
"heading": "Good to Have",
"heading_was_present": true,
"source_marker": {
"first_5_words": "\u2022 Experience in apps involving",
"last_5_words": "deployment experience"
},
"text": "\u2022 Experience in apps involving real time location tracking\n\u2022 App Store deployment experience",
"word_count": 18
},
{
"bullet_count": 3,
"heading": "What We Offer",
"heading_was_present": true,
"source_marker": {
"first_5_words": "\u2022 Opportunity to work on",
"last_5_words": "long term career opportunities"
},
"text": "\u2022 Opportunity to work on scalable, real world applications\n\u2022 Growth oriented and collaborative work environment\n\u2022 Long term career opportunities",
"word_count": 22
}
],
"urls": [
{
"type": "other",
"url": "hr@grepixit.com"
}
]
},
"rejected": false,
"rejection_reason": null,
"run_id": "a057c8f6-e315-4a2a-b70a-371e8908bf02",
"stage3_signals": {
"alias_found": true,
"alias_match_roles": [
{
"display_name": "iOS Developer",
"kra_matches": null,
"matched_count": null,
"matched_skills": null,
"role_id": 6,
"score": 1.0,
"slug": "ios-engineer",
"total_count": null
},
{
"display_name": "Native Mobile Developer",
"kra_matches": null,
"matched_count": null,
"matched_skills": null,
"role_id": 75,
"score": 1.0,
"slug": "native-mobile-developer",
"total_count": null
},
{
"display_name": "Android Developer",
"kra_matches": null,
"matched_count": null,
"matched_skills": null,
"role_id": 4,
"score": 1.0,
"slug": "android-engineer",
"total_count": null
}
],
"kra_match_roles": [
{
"display_name": "Java Backend Developer",
"kra_matches": [
{
"kra_text": "Server-side business logic implementation",
"sentence": "Ability to implement complex business logic",
"similarity": 0.6959
},
{
"kra_text": "code refactoring and defect fixes",
"sentence": "Excellent debugging and problem solving skills",
"similarity": 0.4547
},
{
"kra_text": "service contract collaboration",
"sentence": "Growth oriented and collaborative work environment",
"similarity": 0.4029
}
],
"matched_count": null,
"matched_skills": null,
"role_id": 79,
"score": 0.5178,
"slug": "java-backend-developer",
"total_count": null
},
{
"display_name": "Go Backend Developer",
"kra_matches": [
{
"kra_text": "Server-side business logic implementation",
"sentence": "Ability to implement complex business logic",
"similarity": 0.6959
},
{
"kra_text": "code review and testing support",
"sentence": "Excellent debugging and problem solving skills",
"similarity": 0.4804
},
{
"kra_text": "code review and testing support",
"sentence": "Opportunity to work on scalable, real world applications",
"similarity": 0.3629
}
],
"matched_count": null,
"matched_skills": null,
"role_id": 81,
"score": 0.5131,
"slug": "go-backend-developer",
"total_count": null
},
{
"display_name": "Python Backend Developer",
"kra_matches": [
{
"kra_text": "Implement server-side business logic",
"sentence": "Ability to implement complex business logic",
"similarity": 0.6955
},
{
"kra_text": "Troubleshoot server-side defects",
"sentence": "Excellent debugging and problem solving skills",
"similarity": 0.473
},
{
"kra_text": "Support background jobs and async workflows",
"sentence": "Opportunity to work on scalable, real world applications",
"similarity": 0.3606
}
],
"matched_count": null,
"matched_skills": null,
"role_id": 80,
"score": 0.5097,
"slug": "python-backend-developer",
"total_count": null
},
{
"display_name": ".NET Backend Developer",
"kra_matches": [
{
"kra_text": "Server-side business logic implementation",
"sentence": "Ability to implement complex business logic",
"similarity": 0.6959
},
{
"kra_text": "defect investigation and resolution",
"sentence": "Excellent debugging and problem solving skills",
"similarity": 0.4412
},
{
"kra_text": "service-level technical collaboration",
"sentence": "Growth oriented and collaborative work environment",
"similarity": 0.3806
}
],
"matched_count": null,
"matched_skills": null,
"role_id": 83,
"score": 0.5059,
"slug": "dotnet-backend-developer",
"total_count": null
},
{
"display_name": "Kotlin Backend Developer",
"kra_matches": [
{
"kra_text": "Backend business logic implementation",
"sentence": "Ability to implement complex business logic",
"similarity": 0.7089
},
{
"kra_text": "performance and reliability tuning",
"sentence": "Excellent debugging and problem solving skills",
"similarity": 0.4455
},
{
"kra_text": "performance and reliability tuning",
"sentence": "Opportunity to work on scalable, real world applications",
"similarity": 0.3354
}
],
"matched_count": null,
"matched_skills": null,
"role_id": 84,
"score": 0.4966,
"slug": "kotlin-server-backend-developer",
"total_count": null
}
],
"skill_match_roles": [
{
"display_name": "Fullstack Developer",
"kra_matches": null,
"matched_count": 1,
"matched_skills": [
"REST"
],
"role_id": 15,
"score": 0.3333,
"slug": "full-stack-engineer",
"total_count": 3
},
{
"display_name": "iOS Developer",
"kra_matches": null,
"matched_count": 1,
"matched_skills": [
"Swift"
],
"role_id": 6,
"score": 0.3333,
"slug": "ios-engineer",
"total_count": 3
},
{
"display_name": "Pega Developer",
"kra_matches": null,
"matched_count": 1,
"matched_skills": [
"REST"
],
"role_id": 24,
"score": 0.3333,
"slug": "pega-developer",
"total_count": 3
},
{
"display_name": "Native Mobile Developer",
"kra_matches": null,
"matched_count": 1,
"matched_skills": [
"Swift"
],
"role_id": 75,
"score": 0.3333,
"slug": "native-mobile-developer",
"total_count": 3
},
{
"display_name": "Backend Developer",
"kra_matches": null,
"matched_count": 1,
"matched_skills": [
"REST"
],
"role_id": 1,
"score": 0.3333,
"slug": "backend-engineer",
"total_count": 3
}
]
},
"stage4_decision": {
"alias_collision_detected": true,
"case": "A",
"chosen_role": {
"display_name": "Native Mobile Developer",
"kra_matches": null,
"matched_count": null,
"matched_skills": null,
"role_id": 75,
"score": 1.0,
"slug": "native-mobile-developer",
"total_count": null
},
"confidence": 0.95,
"is_new_role": false,
"llm2_fired": false,
"llm2_reasoning": null,
"matched_dimensions": [],
"matched_kras": [],
"matched_skills": [],
"new_role_display_name": null,
"new_role_slug": null,
"queued": false,
"reasoning": "Multi-alias tie (3 roles at 1.0) resolved by TIER_B_TITLE: iOS Developer",
"sub_role": {
"confidence": 0.95,
"display_name": "iOS Developer",
"reasoning": "hoisted from chosen leaf (case=A)",
"role_id": 6,
"slug": "ios-engineer"
}
},
"stage5_updates": null
}
API 2 — extract-details
{
"alias_matches": [
{
"alias_persist_skipped_reason": "alias_text already exists for this canonical skill",
"alias_persisted": false,
"existing_alias_id": 2540,
"existing_alias_text": "iOS",
"input_term": "iOS",
"matched_canonical": {
"category_id": 9,
"display_name": "iOS",
"id": 1594,
"is_also_category": false,
"is_extractable": true,
"skill_nature": "PLATFORM",
"slug": "ios",
"sub_category_id": 1200,
"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": 756,
"existing_alias_text": "Swift",
"input_term": "Swift",
"matched_canonical": {
"category_id": 6,
"display_name": "Swift",
"id": 440,
"is_also_category": false,
"is_extractable": true,
"skill_nature": "LANGUAGE",
"slug": "swift",
"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": 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": 1599,
"existing_alias_text": "location services",
"input_term": "Location Services",
"matched_canonical": {
"category_id": 11,
"display_name": "location services",
"id": 989,
"is_also_category": false,
"is_extractable": true,
"skill_nature": "CLOUD_SERVICE",
"slug": "location-services",
"sub_category_id": 719,
"typical_lifespan": "EVERGREEN",
"volatility": "STABLE"
},
"matched_via": "alias"
},
{
"alias_persist_skipped_reason": "TODO: REMOVE AFTER TESTING \u2014 alias DB write disabled",
"alias_persisted": false,
"existing_alias_id": 1711,
"existing_alias_text": "Apple App Store",
"input_term": "App Store",
"matched_canonical": {
"category_id": 9,
"display_name": "Apple App Store",
"id": 1085,
"is_also_category": false,
"is_extractable": true,
"skill_nature": "PLATFORM",
"slug": "apple-app-store",
"sub_category_id": 347,
"typical_lifespan": "EVERGREEN",
"volatility": "STABLE"
},
"matched_via": "embedding_alias"
}
],
"candidate_roles": [
{
"display_name": "Native Mobile Developer",
"id": 75,
"rationale": null,
"role_archetype": "Engineering",
"slug": "native-mobile-developer",
"source": "db"
},
{
"display_name": "iOS Developer",
"id": 6,
"rationale": null,
"role_archetype": null,
"slug": "ios-engineer",
"source": "db"
},
{
"display_name": "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": ".NET Backend Developer",
"id": 83,
"rationale": null,
"role_archetype": "Engineering",
"slug": "dotnet-backend-developer",
"source": "db"
},
{
"display_name": "Go Backend Developer",
"id": 81,
"rationale": null,
"role_archetype": "Engineering",
"slug": "go-backend-developer",
"source": "db"
},
{
"display_name": "Kotlin Backend Developer",
"id": 84,
"rationale": null,
"role_archetype": "Engineering",
"slug": "kotlin-server-backend-developer",
"source": "db"
},
{
"display_name": "Node.js Backend Developer",
"id": 82,
"rationale": null,
"role_archetype": "Engineering",
"slug": "node-backend-developer",
"source": "db"
},
{
"display_name": "PHP Backend Developer",
"id": 86,
"rationale": null,
"role_archetype": "Engineering",
"slug": "php-backend-developer",
"source": "db"
},
{
"display_name": "Python Backend Developer",
"id": 80,
"rationale": null,
"role_archetype": "Engineering",
"slug": "python-backend-developer",
"source": "db"
},
{
"display_name": "Ruby Backend Developer",
"id": 85,
"rationale": null,
"role_archetype": "Engineering",
"slug": "ruby-backend-developer",
"source": "db"
},
{
"display_name": "Scala Backend Developer",
"id": 87,
"rationale": null,
"role_archetype": "Engineering",
"slug": "scala-backend-developer",
"source": "db"
},
{
"display_name": "Pega Developer",
"id": 24,
"rationale": null,
"role_archetype": null,
"slug": "pega-developer",
"source": "db"
},
{
"display_name": "Sitecore Dev",
"id": 233,
"rationale": null,
"role_archetype": "Engineering",
"slug": "sitecore-dev",
"source": "db"
},
{
"display_name": "Android Developer",
"id": 4,
"rationale": null,
"role_archetype": null,
"slug": "android-engineer",
"source": "db"
},
{
"display_name": "Hybrid Mobile Developer",
"id": 11,
"rationale": null,
"role_archetype": null,
"slug": "hybrid-mobile-developer",
"source": "db"
},
{
"display_name": "React Native Developer",
"id": 73,
"rationale": null,
"role_archetype": "Engineering",
"slug": "react-native-developer",
"source": "db"
}
],
"chosen_role": {
"display_name": "Native Mobile Developer",
"id": 75,
"rationale": "Multi-alias tie (3 roles at 1.0) resolved by TIER_B_TITLE: iOS Developer",
"role_archetype": "Engineering",
"slug": "native-mobile-developer",
"source": "db"
},
"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": "iOS",
"llm_role": null,
"roles_from_db": []
},
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Native Mobile Languages",
"id": 274,
"rationale": "Primary implementation languages used to build platform-specific app features, UI logic, and device integrations. This is the core coding surface for native mobile work on one platform.",
"slug": "native-mobile-languages",
"source": "db"
},
"input_skill": "Swift",
"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": "Swift and Objective-C",
"id": 81,
"rationale": "Primary implementation languages for native iOS app features, platform APIs, and client-side business logic. This is the core coding surface for building and maintaining iPhone and iPad experiences.",
"slug": "swift-and-objective-c",
"source": "db"
},
"input_skill": "Swift",
"llm_role": null,
"roles_from_db": [
{
"display_name": "iOS Developer",
"id": 6,
"rationale": null,
"role_archetype": null,
"slug": "ios-engineer",
"source": "db"
}
]
},
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "API Design and Contracts",
"id": 3,
"rationale": "Designing request/response shapes and the rules that govern client-server interaction. This cluster is coherent because full stack engineers often own the contract between UI behavior and backend implementation.",
"slug": "api-design-and-contracts",
"source": "db"
},
"input_skill": "REST",
"llm_role": null,
"roles_from_db": [
{
"display_name": "Backend 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": "Device APIs and Hardware Features",
"id": 95,
"rationale": "iOS platform APIs that expose hardware and device capabilities to apps. This cluster covers the concrete integrations iOS engineers use for camera, sensors, location, and media experiences.",
"slug": "device-apis-and-hardware-features",
"source": "db"
},
"input_skill": "Location Services",
"llm_role": null,
"roles_from_db": [
{
"display_name": "Android Developer",
"id": 4,
"rationale": null,
"role_archetype": null,
"slug": "android-engineer",
"source": "db"
},
{
"display_name": "Native Mobile Developer",
"id": 75,
"rationale": null,
"role_archetype": "Engineering",
"slug": "native-mobile-developer",
"source": "db"
},
{
"display_name": "iOS Developer",
"id": 6,
"rationale": null,
"role_archetype": null,
"slug": "ios-engineer",
"source": "db"
}
]
},
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Device APIs and Hardware Integration",
"id": 171,
"rationale": "Platform capabilities exposed through mobile devices that shared apps commonly integrate with. This includes sensors, camera, location, Bluetooth, file access, and other device-bound features that require platform-aware adaptation.",
"slug": "device-apis-and-hardware-integration",
"source": "db"
},
"input_skill": "Location Services",
"llm_role": null,
"roles_from_db": [
{
"display_name": "Hybrid Mobile Developer",
"id": 11,
"rationale": null,
"role_archetype": null,
"slug": "hybrid-mobile-developer",
"source": "db"
},
{
"display_name": "React Native Developer",
"id": 73,
"rationale": null,
"role_archetype": "Engineering",
"slug": "react-native-developer",
"source": "db"
}
]
},
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Mobile Vendor Platforms",
"id": 172,
"rationale": "Knowledge of major mobile vendor platforms and their services for app distribution, testing, and analytics.",
"slug": "mobile-vendor-platforms",
"source": "db"
},
"input_skill": "App Store",
"llm_role": null,
"roles_from_db": [
{
"display_name": "Hybrid Mobile Developer",
"id": 11,
"rationale": null,
"role_archetype": null,
"slug": "hybrid-mobile-developer",
"source": "db"
}
]
}
],
"input_final_skills": [
"iOS",
"Swift",
"REST",
"Maps",
"Location Services",
"App Store"
],
"input_llm_skills": [
"iOS",
"Swift",
"REST",
"Maps",
"Location Services",
"App Store"
],
"new_aliases_persisted": 0,
"run_id": "a057c8f6-e315-4a2a-b70a-371e8908bf02",
"skills_detail": [
{
"aliases_in_db": [
{
"alias_text": "iOS",
"alias_type": "CANONICAL",
"id": 2540,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
}
],
"canonical": {
"category_id": 9,
"display_name": "iOS",
"id": 1594,
"is_also_category": false,
"is_extractable": true,
"skill_nature": "PLATFORM",
"slug": "ios",
"sub_category_id": 1200,
"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": "iOS",
"llm_role": null,
"roles_from_db": []
}
],
"input_skill": "iOS",
"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": "Swift",
"alias_type": "CANONICAL",
"id": 756,
"is_primary": true,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "Swift 2.0",
"alias_type": "VERSION",
"id": 757,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "Swift 2.x",
"alias_type": "VERSION",
"id": 758,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "Swift 3.0",
"alias_type": "VERSION",
"id": 759,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "Swift 3.x",
"alias_type": "VERSION",
"id": 760,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "Swift 4.0",
"alias_type": "VERSION",
"id": 761,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "Swift 4.x",
"alias_type": "VERSION",
"id": 762,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "Swift 5.0",
"alias_type": "VERSION",
"id": 763,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "Swift 5.x",
"alias_type": "VERSION",
"id": 764,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "Swift 6.0",
"alias_type": "VERSION",
"id": 765,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "Swift 6.x",
"alias_type": "VERSION",
"id": 766,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
}
],
"canonical": {
"category_id": 6,
"display_name": "Swift",
"id": 440,
"is_also_category": false,
"is_extractable": true,
"skill_nature": "LANGUAGE",
"slug": "swift",
"sub_category_id": 96,
"typical_lifespan": "EVERGREEN",
"volatility": "STABLE"
},
"dimensions": [
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Native Mobile Languages",
"id": 274,
"rationale": "Primary implementation languages used to build platform-specific app features, UI logic, and device integrations. This is the core coding surface for native mobile work on one platform.",
"slug": "native-mobile-languages",
"source": "db"
},
"input_skill": "Swift",
"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": "Swift and Objective-C",
"id": 81,
"rationale": "Primary implementation languages for native iOS app features, platform APIs, and client-side business logic. This is the core coding surface for building and maintaining iPhone and iPad experiences.",
"slug": "swift-and-objective-c",
"source": "db"
},
"input_skill": "Swift",
"llm_role": null,
"roles_from_db": [
{
"display_name": "iOS Developer",
"id": 6,
"rationale": null,
"role_archetype": null,
"slug": "ios-engineer",
"source": "db"
}
]
}
],
"input_skill": "Swift",
"matched_via": "alias",
"new_alias_persisted": false,
"new_alias_text": null,
"new_skill_meta": null,
"source_tag": "db",
"was_in_llm_skills": true
},
{
"aliases_in_db": [
{
"alias_text": "REST",
"alias_type": "CANONICAL",
"id": 106,
"is_primary": true,
"match_strategy": "CASE_INSENSITIVE"
}
],
"canonical": {
"category_id": 2,
"display_name": "REST",
"id": 11,
"is_also_category": false,
"is_extractable": true,
"skill_nature": "CONCEPT",
"slug": "rest",
"sub_category_id": 2122,
"typical_lifespan": "EVERGREEN",
"volatility": "STABLE"
},
"dimensions": [
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "API Design and Contracts",
"id": 3,
"rationale": "Designing request/response shapes and the rules that govern client-server interaction. This cluster is coherent because full stack engineers often own the contract between UI behavior and backend implementation.",
"slug": "api-design-and-contracts",
"source": "db"
},
"input_skill": "REST",
"llm_role": null,
"roles_from_db": [
{
"display_name": "Backend Developer",
"id": 1,
"rationale": null,
"role_archetype": "A Backend Engineer designs, builds, and maintains the server-side logic and data handling that power applications and services. They focus on implementing reliable business functionality, integrating with other systems, and ensuring the backend is scalable, maintainable, and observable.",
"slug": "backend-engineer",
"source": "db"
},
{
"display_name": "Fullstack Developer",
"id": 15,
"rationale": null,
"role_archetype": null,
"slug": "full-stack-engineer",
"source": "db"
}
]
},
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "API Interface and Contract Design",
"id": 289,
"rationale": "Designing backend service interfaces and contracts that other systems consume, including endpoint and operation shape, request/response payloads, schema and validation, pagination, filtering, idempotency, versioning, status codes, and backward compatibility across REST, GraphQL, gRPC, and OpenAPI-based APIs.",
"slug": "api-interface-and-contract-design",
"source": "db"
},
"input_skill": "REST",
"llm_role": null,
"roles_from_db": [
{
"display_name": ".NET Backend Developer",
"id": 83,
"rationale": null,
"role_archetype": "Engineering",
"slug": "dotnet-backend-developer",
"source": "db"
},
{
"display_name": "Go Backend Developer",
"id": 81,
"rationale": null,
"role_archetype": "Engineering",
"slug": "go-backend-developer",
"source": "db"
},
{
"display_name": "Kotlin Backend Developer",
"id": 84,
"rationale": null,
"role_archetype": "Engineering",
"slug": "kotlin-server-backend-developer",
"source": "db"
},
{
"display_name": "Node.js Backend Developer",
"id": 82,
"rationale": null,
"role_archetype": "Engineering",
"slug": "node-backend-developer",
"source": "db"
},
{
"display_name": "PHP Backend Developer",
"id": 86,
"rationale": null,
"role_archetype": "Engineering",
"slug": "php-backend-developer",
"source": "db"
},
{
"display_name": "Python Backend Developer",
"id": 80,
"rationale": null,
"role_archetype": "Engineering",
"slug": "python-backend-developer",
"source": "db"
},
{
"display_name": "Ruby Backend Developer",
"id": 85,
"rationale": null,
"role_archetype": "Engineering",
"slug": "ruby-backend-developer",
"source": "db"
},
{
"display_name": "Scala Backend Developer",
"id": 87,
"rationale": null,
"role_archetype": "Engineering",
"slug": "scala-backend-developer",
"source": "db"
}
]
},
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Integration Protocols \u0026 Standards",
"id": 271,
"rationale": "Standards and protocols for integrating Pega applications.",
"slug": "integration-protocols-standards",
"source": "db"
},
"input_skill": "REST",
"llm_role": null,
"roles_from_db": [
{
"display_name": "Pega Developer",
"id": 24,
"rationale": null,
"role_archetype": null,
"slug": "pega-developer",
"source": "db"
}
]
},
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Standards \u0026 Protocols Compliance",
"id": 452,
"rationale": "Encompasses key web and data standards, protocols, and compliance requirements relevant to Sitecore implementations.",
"slug": "standards-protocols-compliance",
"source": "db"
},
"input_skill": "REST",
"llm_role": null,
"roles_from_db": [
{
"display_name": "Sitecore Dev",
"id": 233,
"rationale": null,
"role_archetype": "Engineering",
"slug": "sitecore-dev",
"source": "db"
}
]
}
],
"input_skill": "REST",
"matched_via": "alias",
"new_alias_persisted": false,
"new_alias_text": null,
"new_skill_meta": null,
"source_tag": "db",
"was_in_llm_skills": true
},
{
"aliases_in_db": [],
"canonical": null,
"dimensions": [],
"input_skill": "Maps",
"matched_via": null,
"new_alias_persisted": false,
"new_alias_text": null,
"new_skill_meta": {
"derived": {
"category": "Other",
"skill_nature": "TOOL",
"sub_category": "general",
"typical_lifespan": "MULTI_YEAR",
"version_strategy": "UNVERSIONED",
"volatility": "MEDIUM"
},
"enrichment": null,
"keep_log": [],
"locked_dimensions": [],
"merge_log": [],
"placed": null,
"relationships": null,
"skill_id": "maps",
"split_log": [],
"typed": null,
"warnings": []
},
"source_tag": "llm",
"was_in_llm_skills": true
},
{
"aliases_in_db": [
{
"alias_text": "location services",
"alias_type": "CANONICAL",
"id": 1599,
"is_primary": true,
"match_strategy": "CASE_INSENSITIVE"
}
],
"canonical": {
"category_id": 11,
"display_name": "location services",
"id": 989,
"is_also_category": false,
"is_extractable": true,
"skill_nature": "CLOUD_SERVICE",
"slug": "location-services",
"sub_category_id": 719,
"typical_lifespan": "EVERGREEN",
"volatility": "STABLE"
},
"dimensions": [
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Device APIs and Hardware Features",
"id": 95,
"rationale": "iOS platform APIs that expose hardware and device capabilities to apps. This cluster covers the concrete integrations iOS engineers use for camera, sensors, location, and media experiences.",
"slug": "device-apis-and-hardware-features",
"source": "db"
},
"input_skill": "Location Services",
"llm_role": null,
"roles_from_db": [
{
"display_name": "Android Developer",
"id": 4,
"rationale": null,
"role_archetype": null,
"slug": "android-engineer",
"source": "db"
},
{
"display_name": "Native Mobile Developer",
"id": 75,
"rationale": null,
"role_archetype": "Engineering",
"slug": "native-mobile-developer",
"source": "db"
},
{
"display_name": "iOS Developer",
"id": 6,
"rationale": null,
"role_archetype": null,
"slug": "ios-engineer",
"source": "db"
}
]
},
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Device APIs and Hardware Integration",
"id": 171,
"rationale": "Platform capabilities exposed through mobile devices that shared apps commonly integrate with. This includes sensors, camera, location, Bluetooth, file access, and other device-bound features that require platform-aware adaptation.",
"slug": "device-apis-and-hardware-integration",
"source": "db"
},
"input_skill": "Location Services",
"llm_role": null,
"roles_from_db": [
{
"display_name": "Hybrid Mobile Developer",
"id": 11,
"rationale": null,
"role_archetype": null,
"slug": "hybrid-mobile-developer",
"source": "db"
},
{
"display_name": "React Native Developer",
"id": 73,
"rationale": null,
"role_archetype": "Engineering",
"slug": "react-native-developer",
"source": "db"
}
]
}
],
"input_skill": "Location Services",
"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": "Apple App Store",
"alias_type": "CANONICAL",
"id": 1711,
"is_primary": true,
"match_strategy": "CASE_INSENSITIVE"
}
],
"canonical": {
"category_id": 9,
"display_name": "Apple App Store",
"id": 1085,
"is_also_category": false,
"is_extractable": true,
"skill_nature": "PLATFORM",
"slug": "apple-app-store",
"sub_category_id": 347,
"typical_lifespan": "EVERGREEN",
"volatility": "STABLE"
},
"dimensions": [
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Mobile Vendor Platforms",
"id": 172,
"rationale": "Knowledge of major mobile vendor platforms and their services for app distribution, testing, and analytics.",
"slug": "mobile-vendor-platforms",
"source": "db"
},
"input_skill": "App Store",
"llm_role": null,
"roles_from_db": [
{
"display_name": "Hybrid Mobile Developer",
"id": 11,
"rationale": null,
"role_archetype": null,
"slug": "hybrid-mobile-developer",
"source": "db"
}
]
}
],
"input_skill": "App Store",
"matched_via": "embedding_alias",
"new_alias_persisted": false,
"new_alias_text": null,
"new_skill_meta": null,
"source_tag": "db",
"was_in_llm_skills": true
}
],
"unmatched_skills": [
"Maps"
]
}
API 3 — final-role-output
{
"chosen_role": {
"display_name": "Native Mobile Developer",
"id": 75,
"rationale": "Multi-alias tie (3 roles at 1.0) resolved by TIER_B_TITLE: iOS Developer",
"role_archetype": "Engineering",
"slug": "native-mobile-developer",
"source": "db"
},
"chosen_role_resolution": "in_db",
"final_input_skills": [
{
"skill": "iOS",
"tag": "in_db"
},
{
"skill": "Swift",
"tag": "in_db"
},
{
"skill": "REST",
"tag": "in_db"
},
{
"skill": "Maps",
"tag": "new"
},
{
"skill": "Location Services",
"tag": "in_db"
},
{
"skill": "App Store",
"tag": "in_db"
}
],
"llm_cost_api1_usd": null,
"llm_cost_api2_usd": null,
"llm_cost_api3_usd": null,
"llm_cost_total_usd": null,
"persistence": {
"items": [
{
"chosen_role_id": 75,
"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": "iOS",
"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": 1594,
"skill_tag": "in_db",
"skipped_reason": null
},
{
"chosen_role_id": 75,
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Native Mobile Languages",
"id": 274,
"rationale": "Primary implementation languages used to build platform-specific app features, UI logic, and device integrations. This is the core coding surface for native mobile work on one platform.",
"slug": "native-mobile-languages",
"source": "db"
},
"dimension_id": 274,
"input_skill": "Swift",
"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": "Native Mobile Developer",
"id": 75,
"rationale": null,
"role_archetype": "Engineering",
"slug": "native-mobile-developer",
"source": "db"
}
],
"skill_dimension_saved": true,
"skill_id": 440,
"skill_tag": "in_db",
"skipped_reason": null
},
{
"chosen_role_id": 75,
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Swift and Objective-C",
"id": 81,
"rationale": "Primary implementation languages for native iOS app features, platform APIs, and client-side business logic. This is the core coding surface for building and maintaining iPhone and iPad experiences.",
"slug": "swift-and-objective-c",
"source": "db"
},
"dimension_id": 81,
"input_skill": "Swift",
"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": "iOS Developer",
"id": 6,
"rationale": null,
"role_archetype": null,
"slug": "ios-engineer",
"source": "db"
}
],
"skill_dimension_saved": true,
"skill_id": 440,
"skill_tag": "in_db",
"skipped_reason": null
},
{
"chosen_role_id": 75,
"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": 75,
"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": 75,
"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": 75,
"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": 75,
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Device APIs and Hardware Features",
"id": 95,
"rationale": "iOS platform APIs that expose hardware and device capabilities to apps. This cluster covers the concrete integrations iOS engineers use for camera, sensors, location, and media experiences.",
"slug": "device-apis-and-hardware-features",
"source": "db"
},
"dimension_id": 95,
"input_skill": "Location Services",
"llm_role": null,
"matched_chosen_role": true,
"outcome_line": "Existing dimension (library) \u00b7 Role\u2194dimension saved",
"role_dimension_saved": true,
"roles_from_db": [
{
"display_name": "Android Developer",
"id": 4,
"rationale": null,
"role_archetype": null,
"slug": "android-engineer",
"source": "db"
},
{
"display_name": "Native Mobile Developer",
"id": 75,
"rationale": null,
"role_archetype": "Engineering",
"slug": "native-mobile-developer",
"source": "db"
},
{
"display_name": "iOS Developer",
"id": 6,
"rationale": null,
"role_archetype": null,
"slug": "ios-engineer",
"source": "db"
}
],
"skill_dimension_saved": true,
"skill_id": 989,
"skill_tag": "in_db",
"skipped_reason": null
},
{
"chosen_role_id": 75,
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Device APIs and Hardware Integration",
"id": 171,
"rationale": "Platform capabilities exposed through mobile devices that shared apps commonly integrate with. This includes sensors, camera, location, Bluetooth, file access, and other device-bound features that require platform-aware adaptation.",
"slug": "device-apis-and-hardware-integration",
"source": "db"
},
"dimension_id": 171,
"input_skill": "Location Services",
"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"
},
{
"display_name": "React Native Developer",
"id": 73,
"rationale": null,
"role_archetype": "Engineering",
"slug": "react-native-developer",
"source": "db"
}
],
"skill_dimension_saved": true,
"skill_id": 989,
"skill_tag": "in_db",
"skipped_reason": null
},
{
"chosen_role_id": 75,
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Mobile Vendor Platforms",
"id": 172,
"rationale": "Knowledge of major mobile vendor platforms and their services for app distribution, testing, and analytics.",
"slug": "mobile-vendor-platforms",
"source": "db"
},
"dimension_id": 172,
"input_skill": "App Store",
"llm_role": null,
"matched_chosen_role": false,
"outcome_line": "Skipped \u2014 no persistable v3 meta for new skill",
"role_dimension_saved": false,
"roles_from_db": [
{
"display_name": "Hybrid Mobile Developer",
"id": 11,
"rationale": null,
"role_archetype": null,
"slug": "hybrid-mobile-developer",
"source": "db"
}
],
"skill_dimension_saved": false,
"skill_id": null,
"skill_tag": "new",
"skipped_reason": "skill_not_in_db_v3_proposed"
}
],
"new_skills_created": 0,
"role_dimension_saved": 0,
"skill_dimension_saved": 0,
"skipped": 1
},
"planner_output": null,
"run_id": "a057c8f6-e315-4a2a-b70a-371e8908bf02"
}
LLM Calls
Every model call made for this run, in pipeline order. Click a card to see the model's response.