Pipeline run
bb7c5611-af3b-49f4-9328-45612647f083
Pipeline LLM cost (USD)
API 1: $0.0100
API 2: $0.0003
API 3: $0.0000
Total: $0.0103
Client output enrichment
v2 Skill cluster · Nature of work · AI index · Tech stack maturity · Evidence · KRA description
SPARSE JD
role baseline loaded
sources · ai_index: role_baseline · nature_of_work: no_kras · tech_stack_maturity: jd
Nature of work
no kras
Vague JD — no KRAs present to derive a specific nature of work.
Tech stack maturity
Mainstream Modern
Native mobile development with Android and iOS using Swift, SwiftUI, MVVM, VIPER, and REST reflects a current, widely adopted mainstream modern stack rather than bleeding-edge or legacy technology.
AI index (0 = no AI use, 5 = totally AI-dependent · v2.1)
1.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 (18)
Android Studio
Android SDK
Android
API
REST
MVC
MVVM
Viper
SwiftUI
Swift
iOS
AppCode
CodeRunner
Xcode
Core Animation
Core Data
Core Graphics
Core Text
Skill cluster (7 dimension groups, role-scoped)
Native Mobile App Architecture and Dependency Injection
MVC
MVVM
Viper
Android UI Frameworks
SwiftUI
Integration Protocols & Standards
REST
Local Persistence and Offline Behavior
Core Data
Native Mobile Build and Release Tooling
Xcode
Native Mobile Languages
Swift
Cross-cutting / unaligned
Android Studio
Android SDK
Android
API
iOS
AppCode
CodeRunner
Core Animation
Core Graphics
Core Text
Signals
Skill
native-mobile-developer
0.45
Alias
—
—
KRA
hybrid-mobile-developer
0.59
Post-classification
Centroidupdated · n=13
Alias collision log—
New-role queue—
New skills captured7
New KRA captured—
Captured for admin review
Android Studio
primary
↔
Native Mobile Developer
pending
Android SDK
primary
↔
Native Mobile Developer
pending
AppCode
↔
Native Mobile Developer
pending
CodeRunner
↔
Native Mobile Developer
pending
Core Animation
↔
Native Mobile Developer
pending
Core Graphics
↔
Native Mobile Developer
pending
Core Text
↔
Native Mobile Developer
pending
Status:
completed
Created: 2026-05-27T14:08:46.326888Z
Updated: 2026-05-27T14:10:44.662992Z
API 3 duration: 61844 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
Native Mobile Developer
domain · Software Engineering CASE DOMAINslug: native-mobile-developer · id: 75 · source: db
Domain=Software Engineering; The JD is centered on full-cycle iOS and Android mobile app development with native SDKs, IDEs, and mobile UI/UX, which best matches Native Mobile Developer.
Matched skills
UI and UX design principlesAndroid StudioAndroid SDKfull-cycle mobile app developmentAPIRESTful web servicesMVCMVVMViperSwift UISwiftAppCodeCodeRunnerXcodeApple OS frameworks
Matched dimensions
Native Mobile App DevelopmentMobile UI/UX DesignAPI IntegrationiOS DevelopmentAndroid Development
Matched KRAs
Experience with full-cycle mobile app development in AndroidExperience with full-cycle mobile app development in iOSAbility to integrate APIs and RESTful web services for mobile appsKnowledge of UI and UX design principles
Resolution:
in_db
— role exists in library; skill↔dim and role↔dim links saved when applicable.
0
New skills
0
Skill↔dim saved
0
Role↔dim saved
0
Skipped
Job description
Job Description:: Shift: 8PM-5AM • Experience in UI and UX design principles and Android Studio & SDK • Experience with full-cycle mobile app development in Android • Ability to integrate APIs and RESTful web services for mobile apps. • Design pattern - MVC, MVVM, Viper, Swift UI • Programming language expertise in Swift • Experience using IDEs (AppCode, CodeRunner, Xcode) • Experience with full-cycle mobile app development in iOS • Ability to integrate APIs and RESTful web services for mobile apps. • Familiarity with Apple OS frameworks (Core Animation, Core Data, Core Graphics, Core Text). • Knowledge of UI and UX design principles
Skills from this JD
Each row merges API 1 extraction, API 2 library match / v3 orchestration (dimensions + locked dims), and API 3 persistence tags.
Android Studio
Primary
New / orchestrated
API 3: new canonical path (new)
New / unmatched skill (orchestrated in API 2)
Skill enrichment (orchestrator / LLM)
No Stage 7 enrichment blob on this skill (orchestrator skipped enrichment).
Derived legacy fields
- Category
- Development Environments
- Sub-category
- general
- Skill nature
- TOOL
- Volatility
- MEDIUM
- Typical lifespan
- MULTI_YEAR
- Version strategy
- UNVERSIONED
Android SDK
Primary
New / orchestrated
API 3: new canonical path (new)
New / unmatched skill (orchestrated in API 2)
Skill enrichment (orchestrator / LLM)
No Stage 7 enrichment blob on this skill (orchestrator skipped enrichment).
Derived legacy fields
- Category
- Mobile Development
- Sub-category
- general
- Skill nature
- TOOL
- Volatility
- MEDIUM
- Typical lifespan
- MULTI_YEAR
- Version strategy
- UNVERSIONED
Android
Primary
Library skill
API 3: existing canonical (in_db)
Existing skill (matched library)
Canonical: Android
id=1595
· android
Aliases — catalog
- Android (CANONICAL)
Context tags (catalog)
API Level
Android SDK
Android Studio
Firebase
Gradle
Java
Jetpack
Kotlin
LiveData
MVVM
Material Design
RecyclerView
Retrofit
Room
XML
Stored enrichment (catalog DB)
- Category
- Platform
- Sub-category
- Mobile Platform
- Vendor
- License
- apache_2
- Year introduced
- 2008
- Confidence
- 0.95
- Version strategy
- NOT_APPLICABLE
Maturity reasoning: Android appears in large volumes of mobile job postings and remains a standard platform in hiring pipelines; Google continues active platform releases and OEM ecosystem support, indicating broad adoption.
Skill profile (library / DB)
- Skill nature
- PLATFORM
- Volatility
- STABLE
- Typical lifespan
- EVERGREEN
- Category id
- 9
- Sub-category id
- 1201
- 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) |
API
Primary
Library skill
API 3: existing canonical (in_db)
Existing skill (matched library)
Canonical: API
id=1568
· api
Aliases — catalog
- API (CANONICAL)
Context tags (catalog)
API gateway
GraphQL
JSON
OAuth
REST
SDK
SOAP
XML
authentication
endpoint
microservices
rate limiting
throttling
versioning
webhooks
Stored enrichment (catalog DB)
- Category
- Concept
- Sub-category
- Application Programming Interface
- Confidence
- 0.93
- Version strategy
- NOT_APPLICABLE
Maturity reasoning: APIs are a core requirement in most software engineering JDs and underpin common integrations across cloud, mobile, and web stacks; major vendors like AWS, Stripe, and Google Cloud center products on API-first usage.
Skill profile (library / DB)
- Skill nature
- CONCEPT
- Volatility
- STABLE
- Typical lifespan
- EVERGREEN
- Category id
- 2
- Sub-category id
- 1174
- Extractable
- True
- Also category
- False
Dimensions (API 2 worklist)
-
API Integration and Data Fetching Catalog dimension db id 127
Library dimension (catalog)
Roles linked in library: Angular Frontend Developer, Frontend Developer, Fullstack Developer, React Frontend Developer, Svelte Frontend Developer, Vue Frontend Developer, Web Developer
API 3 link attempts (this skill)
| Dimension | Skill↔dim | Role↔dim | Outcome |
|---|---|---|---|
|
API Integration and Data Fetching
api-integration-and-data-fetching
|
✓ | — | Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role) |
REST
Primary
Library skill
API 3: existing canonical (in_db)
Existing skill (matched library)
Canonical: REST
id=11
· rest
Aliases — catalog
- REST (CANONICAL) primary
Context tags (catalog)
API
API design
API versioning
CRUD
DELETE
GET
HATEOAS
HTTP
JSON
OAuth
OAuth2
OpenAPI
POST
PUT
Postman
RESTful
Swagger
URI
Webhooks
XML
authentication
client-server
content negotiation
endpoint
endpoints
middleware
resource
resource-oriented
serialization
stateless
status codes
versioning
web services
Stored enrichment (catalog DB)
- Category
- Concept
- Sub-category
- Api Architecture Style
- Year introduced
- 2000
- Confidence
- 0.88
- Version strategy
- NOT_APPLICABLE
Maturity reasoning: REST is a default API architecture in many job descriptions and is widely supported by major vendors/frameworks; OpenAPI and RESTful endpoints remain standard in hiring pipelines.
Skill profile (library / DB)
- Skill nature
- CONCEPT
- Volatility
- STABLE
- Typical lifespan
- EVERGREEN
- Category id
- 2
- Sub-category id
- 2122
- Extractable
- True
- Also category
- False
Dimensions (API 2 worklist)
-
API Design and Contracts Catalog dimension db id 3
Library dimension (catalog)
Roles linked in library: Backend Developer, Fullstack Developer
-
API Interface and Contract Design Catalog dimension db id 289
Library dimension (catalog)
Roles linked in library: .NET Backend Developer, Go Backend Developer, Kotlin Backend Developer, Node.js Backend Developer, PHP Backend Developer, Python Backend Developer, Ruby Backend Developer, Scala Backend Developer
-
Integration Protocols & Standards Catalog dimension db id 271
Library dimension (catalog)
Roles linked in library: Pega Developer
-
Standards & Protocols Compliance Catalog dimension db id 452
Library dimension (catalog)
Roles linked in library: Sitecore Dev
API 3 link attempts (this skill)
| Dimension | Skill↔dim | Role↔dim | Outcome |
|---|---|---|---|
|
API Design and Contracts
api-design-and-contracts
|
✓ | — | Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role) |
|
API Interface and Contract Design
api-interface-and-contract-design
|
✓ | — | Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role) |
|
Integration Protocols & Standards
integration-protocols-standards
|
✓ | — | Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role) |
|
Standards & Protocols Compliance
standards-protocols-compliance
|
✓ | — | Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role) |
MVC
Primary
Library skill
API 3: existing canonical (in_db)
Existing skill (matched library)
Canonical: MVC
id=505
· mvc
Aliases — catalog
- MVC (CANONICAL) primary
Context tags (catalog)
ASP.NET
ASP.NET MVC
Angular
Backend
Controller
Data binding
Dependency injection
Express.js
Flask
Frontend
Laravel
Model
Model-View-Controller
RESTful
Rails
React
Routing
Ruby on Rails
Separation of concerns
Spring MVC
UI components
View
action methods
controller
data binding
dependency injection
event handling
layout pages
model
partial views
routing
separation of concerns
state management
template engine
templating
view
Stored enrichment (catalog DB)
- Category
- Architecture
- Sub-category
- Model View Controller
- Year introduced
- 1979
- Confidence
- 0.93
- Version strategy
- NOT_APPLICABLE
Maturity reasoning: MVC remains a standard web/app architecture in many job descriptions and frameworks (e.g., ASP.NET MVC, Spring MVC, Rails), with no vendor sunset or replacement making it obsolete.
Skill profile (library / DB)
- Skill nature
- PATTERN
- Volatility
- STABLE
- Typical lifespan
- EVERGREEN
- Category id
- 1
- Sub-category id
- 2462
- Extractable
- True
- Also category
- False
Dimensions (API 2 worklist)
-
ASP.NET Core Web Frameworks Catalog dimension db id 363
Library dimension (catalog)
Roles linked in library: .NET Backend Developer
-
App Architecture and Dependency Injection Catalog dimension db id 94
Library dimension (catalog)
Roles linked in library: Android Developer, iOS Developer
-
Application Architecture and Code Organization Catalog dimension db id 220
Library dimension (catalog)
Roles linked in library: Fullstack Developer
-
Native Mobile App Architecture and Dependency Injection Catalog dimension db id 273
Library dimension (catalog)
Roles linked in library: Native Mobile Developer
API 3 link attempts (this skill)
| Dimension | Skill↔dim | Role↔dim | Outcome |
|---|---|---|---|
|
ASP.NET Core Web Frameworks
asp-net-core-web-frameworks
|
✓ | — | Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role) |
|
App Architecture and Dependency Injection
app-architecture-and-dependency-injection
|
✓ | — | Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role) |
|
Application Architecture and Code Organization
application-architecture-and-code-organization
|
✓ | — | Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role) |
|
Native Mobile App Architecture and Dependency Injection
native-mobile-app-architecture-and-dependency-injection
|
✓ | ✓ | Existing dimension (library) · Role↔dimension saved |
MVVM
Primary
Library skill
API 3: existing canonical (in_db)
Existing skill (matched library)
Canonical: MVVM
id=504
· mvvm
Aliases — catalog
- MVVM (CANONICAL) primary
Context tags (catalog)
Activity
Android Architecture Components
Caliburn.Micro
Data Binding
Fragment
ICommand
Jetpack Compose
Kotlin
LiveData
MVVM Light
Observable
ObservableCollection
ReactiveUI
RecyclerView
StateFlow
SwiftUI
Two-way binding
UI framework
ViewModel
WPF
XAML
command binding
command pattern
data binding
dependency injection
event aggregation
navigation service
platform independence
property change notification
testability
testable UI
unit testing
view model
Stored enrichment (catalog DB)
- Category
- Architecture
- Sub-category
- Presentation Architecture
- Confidence
- 0.95
- Version strategy
- NOT_APPLICABLE
Maturity reasoning: MVVM is widely used in mobile and desktop JDs, especially Android, WPF, and SwiftUI ecosystems; it remains a common hiring keyword rather than a sunset pattern.
Skill profile (library / DB)
- Skill nature
- PATTERN
- Volatility
- STABLE
- Typical lifespan
- EVERGREEN
- Category id
- 1
- Sub-category id
- 662
- Extractable
- True
- Also category
- False
Dimensions (API 2 worklist)
-
App Architecture and Dependency Injection Catalog dimension db id 94
Library dimension (catalog)
Roles linked in library: Android Developer, iOS Developer
-
Mobile Architecture and Code Organization Catalog dimension db id 170
Library dimension (catalog)
Roles linked in library: Hybrid Mobile Developer, React Native Developer
-
Native Mobile App Architecture and Dependency Injection Catalog dimension db id 273
Library dimension (catalog)
Roles linked in library: Native Mobile Developer
API 3 link attempts (this skill)
| Dimension | Skill↔dim | Role↔dim | Outcome |
|---|---|---|---|
|
App Architecture and Dependency Injection
app-architecture-and-dependency-injection
|
✓ | — | Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role) |
|
Mobile Architecture and Code Organization
mobile-architecture-and-code-organization
|
✓ | — | Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role) |
|
Native Mobile App Architecture and Dependency Injection
native-mobile-app-architecture-and-dependency-injection
|
✓ | ✓ | Existing dimension (library) · Role↔dimension saved |
Viper
Primary
Library skill
API 3: existing canonical (in_db)
Existing skill (matched library)
Canonical: VIPER
id=2056
· viper
Aliases — catalog
- VIPER (CANONICAL) primary
Context tags (catalog)
Cocoa
Swift
UI components
Xcode
clean architecture
dependency injection
iOS
interactor
module
presenter
protocols
router
test-driven development
unit testing
view controllers
Stored enrichment (catalog DB)
- Category
- Architecture
- Sub-category
- Presentation Architecture
- Confidence
- 0.95
- Version strategy
- NOT_APPLICABLE
Maturity reasoning: VIPER appears in some iOS job descriptions and tutorials, but JD volume is far below MVC/MVVM and it’s mostly used in specialized Swift codebases rather than broadly adopted teams.
Skill profile (library / DB)
- Skill nature
- PATTERN
- Volatility
- STABLE
- Typical lifespan
- EVERGREEN
- Category id
- 1
- Sub-category id
- 662
- Extractable
- True
- Also category
- False
Dimensions (API 2 worklist)
-
Native Mobile App Architecture and Dependency Injection Catalog dimension db id 273
Library dimension (catalog)
Roles linked in library: Native Mobile Developer
API 3 link attempts (this skill)
| Dimension | Skill↔dim | Role↔dim | Outcome |
|---|---|---|---|
|
Native Mobile App Architecture and Dependency Injection
native-mobile-app-architecture-and-dependency-injection
|
✓ | ✓ | Existing dimension (library) · Role↔dimension saved |
SwiftUI
Primary
Library skill
API 3: existing canonical (in_db)
Existing skill (matched library)
Canonical: SwiftUI
id=444
· swiftui
Aliases — catalog
- SwiftUI (CANONICAL) primary
Context tags (catalog)
@Binding
@State
Accessibility
Animations
Combine
Core Data
Declarative syntax
ForEach
List
MVVM
Modifiers
NavigationStack
Preview
State management
Swift
Swift Concurrency
Swift Package Manager
Swift Playgrounds
UIKit
Views
Xcode
iOS
macOS
tvOS
watchOS
Stored enrichment (catalog DB)
- Category
- Framework
- Sub-category
- Ui Framework
- Vendor
- Apple
- License
- other_open
- Year introduced
- 2019
- Confidence
- 0.98
- Version strategy
- NOT_APPLICABLE
Maturity reasoning: SwiftUI is widely listed in iOS/macOS job postings and is Apple’s primary UI framework for new apps, with strong ecosystem adoption replacing much UIKit-only greenfield work.
Skill profile (library / DB)
- Skill nature
- FRAMEWORK
- Volatility
- STABLE
- Typical lifespan
- EVERGREEN
- Category id
- 5
- Sub-category id
- 341
- Extractable
- True
- Also category
- False
Dimensions (API 2 worklist)
-
Android UI Frameworks Catalog dimension db id 162
Library dimension (catalog)
Roles linked in library: Android Developer, Native Mobile Developer
-
UIKit and SwiftUI Catalog dimension db id 82
Library dimension (catalog)
Roles linked in library: iOS Developer
API 3 link attempts (this skill)
| Dimension | Skill↔dim | Role↔dim | Outcome |
|---|---|---|---|
|
Android UI Frameworks
android-ui-frameworks
|
✓ | ✓ | Existing dimension (library) · Role↔dimension saved |
|
UIKit and SwiftUI
uikit-and-swiftui
|
✓ | — | Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role) |
Swift
Primary
Library skill
API 3: existing canonical (in_db)
Existing skill (matched library)
Canonical: Swift
id=440
· swift
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)
ARC
Cocoa
Cocoa Touch
CocoaPods
Combine
Core Data
Grand Central Dispatch
MVVM
Objective-C
Optionals
SPM
Swift Package Manager
SwiftUI
UIKit
Xcode
async/await
asynchronous programming
closure
closures
error handling
iOS Development
protocol-oriented programming
type safety
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) |
AppCode
Secondary
New / orchestrated
API 3: new canonical path (new)
New / unmatched skill (orchestrated in API 2)
Skill enrichment (orchestrator / LLM)
No Stage 7 enrichment blob on this skill (orchestrator skipped enrichment).
Derived legacy fields
- Category
- Development Environments
- Sub-category
- general
- Skill nature
- TOOL
- Volatility
- MEDIUM
- Typical lifespan
- MULTI_YEAR
- Version strategy
- UNVERSIONED
CodeRunner
Secondary
New / orchestrated
API 3: new canonical path (new)
New / unmatched skill (orchestrated in API 2)
Skill enrichment (orchestrator / LLM)
No Stage 7 enrichment blob on this skill (orchestrator skipped enrichment).
Derived legacy fields
- Category
- Development Environments
- Sub-category
- general
- Skill nature
- TOOL
- Volatility
- FAST
- Typical lifespan
- SHORT_LIVED
- Version strategy
- VERSIONED
Xcode
Secondary
Library skill
API 3: existing canonical (in_db)
Existing skill (matched library)
Canonical: Xcode
id=479
· xcode
Aliases — catalog
- Xcode (CANONICAL) primary
Context tags (catalog)
App Store
Asset Catalog
Build Phases
Cocoa
Cocoa Touch
CocoaPods
Code Signing
Debugging
Git integration
Instruments
Interface Builder
Objective-C
Provisioning Profiles
Simulator
Storyboard
Swift
Swift Package Manager
SwiftUI
TestFlight
UIKit
Version Control
XCTest
Xcode Server
code signing
debugging
iOS SDK
storyboards
Stored enrichment (catalog DB)
- Category
- Tool
- Sub-category
- Ide Tool
- Vendor
- Apple
- License
- proprietary
- Year introduced
- 2003
- Confidence
- 0.98
- Version strategy
- NOT_APPLICABLE
Maturity reasoning: Xcode is the standard IDE in iOS/macOS job postings and Apple’s official toolchain for Swift/Objective-C development; it remains a common hiring requirement for Apple-platform roles.
Skill profile (library / DB)
- Skill nature
- TOOL
- Volatility
- STABLE
- Typical lifespan
- EVERGREEN
- Category id
- 13
- Sub-category id
- 359
- Extractable
- True
- Also category
- False
Dimensions (API 2 worklist)
-
Build and Release Tooling Catalog dimension db id 89
Library dimension (catalog)
Roles linked in library: Android Developer, Flutter Developer, Hybrid Mobile Developer, iOS Developer
-
Native Mobile Build and Release Tooling Catalog dimension db id 272
Library dimension (catalog)
Roles linked in library: Flutter Developer, Native Mobile Developer, React Native Developer
API 3 link attempts (this skill)
| Dimension | Skill↔dim | Role↔dim | Outcome |
|---|---|---|---|
|
Build and Release Tooling
build-and-release-tooling
|
✓ | — | Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role) |
|
Native Mobile Build and Release Tooling
native-mobile-build-and-release-tooling
|
✓ | ✓ | Existing dimension (library) · Role↔dimension saved |
iOS
Primary
Library skill
API 3: existing canonical (in_db)
Existing skill (matched library)
Canonical: iOS
id=1594
· ios
Aliases — catalog
- iOS (CANONICAL)
Context tags (catalog)
App Store
Auto Layout
Cocoa Touch
CocoaPods
Core Data
MVVM
Objective-C
Push Notifications
RESTful APIs
Swift
SwiftUI
TestFlight
UIKit
Xcode
iCloud
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) |
Core Animation
Secondary
New / orchestrated
API 3: new canonical path (new)
New / unmatched skill (orchestrated in API 2)
Skill enrichment (orchestrator / LLM)
No Stage 7 enrichment blob on this skill (orchestrator skipped enrichment).
Derived legacy fields
- Category
- Mobile Development
- Sub-category
- general
- Skill nature
- CONCEPT
- Volatility
- MEDIUM
- Typical lifespan
- MULTI_YEAR
- Version strategy
- UNVERSIONED
Core Data
Secondary
Library skill
API 3: existing canonical (in_db)
Existing skill (matched library)
Canonical: Core Data
id=459
· core-data
Aliases — catalog
- Core Data (CANONICAL) primary
Context tags (catalog)
Batch Updates
Concurrency
Context
Core Data Framework
Core Data Stack
Data Model
Entity
Faulting
Fetch Request
Migration
NSFetchRequest
NSFetchedResultsController
NSManagedObject
NSManagedObjectContext
NSPersistentContainer
NSPredicate
Relationships
SQLite store
SwiftUI
Xcode
batch updates
entity model
faulting
fetch predicates
iOS
merge policies
migration
object graph
xcdatamodeld
Stored enrichment (catalog DB)
- Category
- Framework
- Sub-category
- Persistence Framework
- Vendor
- Apple
- License
- proprietary
- Year introduced
- 2008
- Confidence
- 0.90
- Version strategy
- NOT_APPLICABLE
Maturity reasoning: Core Data appears mainly in Apple/iOS-specific job postings and legacy Cocoa codebases; market demand is far narrower than cross-platform persistence stacks like SQLite/Realm, with no broad hiring-pipeline ubiquity.
Skill profile (library / DB)
- Skill nature
- FRAMEWORK
- Volatility
- STABLE
- Typical lifespan
- EVERGREEN
- Category id
- 5
- Sub-category id
- 336
- Extractable
- True
- Also category
- False
Dimensions (API 2 worklist)
-
Local Persistence and Offline Behavior Catalog dimension db id 85
Library dimension (catalog)
Roles linked in library: Android Developer, Flutter Developer, Hybrid Mobile Developer, Native Mobile Developer, React Native Developer, iOS Developer
API 3 link attempts (this skill)
| Dimension | Skill↔dim | Role↔dim | Outcome |
|---|---|---|---|
|
Local Persistence and Offline Behavior
local-persistence-and-offline-behavior
|
✓ | ✓ | Existing dimension (library) · Role↔dimension saved |
Core Graphics
Secondary
New / orchestrated
API 3: new canonical path (new)
New / unmatched skill (orchestrated in API 2)
Skill enrichment (orchestrator / LLM)
No Stage 7 enrichment blob on this skill (orchestrator skipped enrichment).
Derived legacy fields
- Category
- Mobile Development
- Sub-category
- general
- Skill nature
- CONCEPT
- Volatility
- MEDIUM
- Typical lifespan
- MULTI_YEAR
- Version strategy
- UNVERSIONED
Core Text
Secondary
New / orchestrated
API 3: new canonical path (new)
New / unmatched skill (orchestrated in API 2)
Skill enrichment (orchestrator / LLM)
No Stage 7 enrichment blob on this skill (orchestrator skipped enrichment).
Derived legacy fields
- Category
- Mobile Development
- Sub-category
- general
- Skill nature
- CONCEPT
- Volatility
- MEDIUM
- Typical lifespan
- MULTI_YEAR
- Version strategy
- UNVERSIONED
All API 3 persistence rows
Same grid as the skill-extractor “Persistence items” table: one row per (skill × dimension) work item.
| Skill | Tag | Dimension | Skill↔dim | Role↔dim | Outcome | Notes |
|---|---|---|---|---|---|---|
| Android | in_db |
React Frontend Development
d_init_01
|
✓ | — | Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role) | |
| API | in_db |
API Integration and Data Fetching
api-integration-and-data-fetching
|
✓ | — | 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) | |
| MVC | in_db |
ASP.NET Core Web Frameworks
asp-net-core-web-frameworks
|
✓ | — | Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role) | |
| MVC | in_db |
App Architecture and Dependency Injection
app-architecture-and-dependency-injection
|
✓ | — | Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role) | |
| MVC | in_db |
Application Architecture and Code Organization
application-architecture-and-code-organization
|
✓ | — | Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role) | |
| MVC | in_db |
Native Mobile App Architecture and Dependency Injection
native-mobile-app-architecture-and-dependency-injection
|
✓ | ✓ | Existing dimension (library) · Role↔dimension saved | |
| MVVM | in_db |
App Architecture and Dependency Injection
app-architecture-and-dependency-injection
|
✓ | — | Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role) | |
| MVVM | in_db |
Mobile Architecture and Code Organization
mobile-architecture-and-code-organization
|
✓ | — | Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role) | |
| MVVM | in_db |
Native Mobile App Architecture and Dependency Injection
native-mobile-app-architecture-and-dependency-injection
|
✓ | ✓ | Existing dimension (library) · Role↔dimension saved | |
| Viper | in_db |
Native Mobile App Architecture and Dependency Injection
native-mobile-app-architecture-and-dependency-injection
|
✓ | ✓ | Existing dimension (library) · Role↔dimension saved | |
| SwiftUI | in_db |
Android UI Frameworks
android-ui-frameworks
|
✓ | ✓ | Existing dimension (library) · Role↔dimension saved | |
| SwiftUI | in_db |
UIKit and SwiftUI
uikit-and-swiftui
|
✓ | — | 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) | |
| Xcode | in_db |
Build and Release Tooling
build-and-release-tooling
|
✓ | — | Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role) | |
| Xcode | in_db |
Native Mobile Build and Release Tooling
native-mobile-build-and-release-tooling
|
✓ | ✓ | Existing dimension (library) · Role↔dimension saved | |
| iOS | in_db |
React Frontend Development
d_init_01
|
✓ | — | Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role) | |
| Core Data | in_db |
Local Persistence and Offline Behavior
local-persistence-and-offline-behavior
|
✓ | ✓ | Existing dimension (library) · Role↔dimension saved |
Library artifacts (this run)
| Kind | Detail | DB id |
|---|---|---|
| canonical_skill_proposed | Android Studio | type=Development Environments subtype=general nature=TOOL lifespan=MULTI_YEAR | |
| canonical_skill_proposed | Android SDK | type=Mobile Development subtype=general nature=TOOL lifespan=MULTI_YEAR | |
| canonical_skill_proposed | AppCode | type=Development Environments subtype=general nature=TOOL lifespan=MULTI_YEAR | |
| canonical_skill_proposed | CodeRunner | type=Development Environments subtype=general nature=TOOL lifespan=SHORT_LIVED | |
| canonical_skill_proposed | Core Animation | type=Mobile Development subtype=general nature=CONCEPT lifespan=MULTI_YEAR | |
| canonical_skill_proposed | Core Graphics | type=Mobile Development subtype=general nature=CONCEPT lifespan=MULTI_YEAR | |
| canonical_skill_proposed | Core Text | type=Mobile Development subtype=general nature=CONCEPT lifespan=MULTI_YEAR |
nano JD Parser — gpt-4.1-nano click to toggle
JD type
fail
Show raw JSON
{
"JD_type": "fail",
"archetype_override_applied": true,
"archetype_override_matched_skills": [
"Swift",
"APIs",
"Xcode",
"MVC",
"iOS",
"Android",
"MVVM",
"VIPER",
"Core Data"
],
"role_archetype": "Engineering"
}
API 1 — extract-from-jd click to toggle
{
"final_skills": [
{
"is_primary": true,
"skill_name": "Android Studio"
},
{
"is_primary": true,
"skill_name": "Android SDK"
},
{
"is_primary": true,
"skill_name": "Android"
},
{
"is_primary": true,
"skill_name": "API"
},
{
"is_primary": true,
"skill_name": "REST"
},
{
"is_primary": true,
"skill_name": "MVC"
},
{
"is_primary": true,
"skill_name": "MVVM"
},
{
"is_primary": true,
"skill_name": "Viper"
},
{
"is_primary": true,
"skill_name": "SwiftUI"
},
{
"is_primary": true,
"skill_name": "Swift"
},
{
"is_primary": false,
"skill_name": "AppCode"
},
{
"is_primary": false,
"skill_name": "CodeRunner"
},
{
"is_primary": false,
"skill_name": "Xcode"
},
{
"is_primary": true,
"skill_name": "iOS"
},
{
"is_primary": false,
"skill_name": "Core Animation"
},
{
"is_primary": false,
"skill_name": "Core Data"
},
{
"is_primary": false,
"skill_name": "Core Graphics"
},
{
"is_primary": false,
"skill_name": "Core Text"
}
],
"jd_role": null,
"nano_parsed": {
"JD_type": "fail",
"archetype_override_applied": true,
"archetype_override_matched_skills": [
"Swift",
"APIs",
"Xcode",
"MVC",
"iOS",
"Android",
"MVVM",
"VIPER",
"Core Data"
],
"role_archetype": "Engineering"
},
"rejected": false,
"rejection_reason": null,
"run_id": "bb7c5611-af3b-49f4-9328-45612647f083",
"stage3_signals": {
"alias_found": false,
"alias_match_roles": [],
"kra_match_roles": [
{
"display_name": "Hybrid Mobile Developer",
"kra_matches": [
{
"kra_text": "Integrates cross-platform mobile apps with REST and GraphQL backend APIs, handling JWT authentication, token refresh, and error recovery.",
"sentence": "Ability to integrate APIs and RESTful web services for mobile apps.",
"similarity": 0.6435
},
{
"kra_text": "Integrates cross-platform mobile apps with REST and GraphQL backend APIs, handling JWT authentication, token refresh, and error recovery.",
"sentence": "Ability to integrate APIs and RESTful web services for mobile apps.",
"similarity": 0.6435
},
{
"kra_text": "Adapts shared UI codebase to handle platform-specific constraints including different navigation paradigms, gesture behaviors, and OS-level UI patterns.",
"sentence": "Design pattern - MVC, MVVM, Viper, Swift UI",
"similarity": 0.4916
}
],
"matched_count": null,
"matched_skills": null,
"role_id": 11,
"score": 0.5929,
"slug": "hybrid-mobile-developer",
"total_count": null
},
{
"display_name": "iOS Developer",
"kra_matches": [
{
"kra_text": "Integrates iOS apps with RESTful backend APIs using URLSession or Alamofire, handling JSON decoding, OAuth tokens, and network error recovery.",
"sentence": "Ability to integrate APIs and RESTful web services for mobile apps.",
"similarity": 0.5976
},
{
"kra_text": "Integrates iOS apps with RESTful backend APIs using URLSession or Alamofire, handling JSON decoding, OAuth tokens, and network error recovery.",
"sentence": "Ability to integrate APIs and RESTful web services for mobile apps.",
"similarity": 0.5976
},
{
"kra_text": "Manages reactive state updates, view model bindings, and UI logic using Combine, RxSwift, or Swift Concurrency async/await patterns.",
"sentence": "Design pattern - MVC, MVVM, Viper, Swift UI",
"similarity": 0.5572
}
],
"matched_count": null,
"matched_skills": null,
"role_id": 6,
"score": 0.5841,
"slug": "ios-engineer",
"total_count": null
},
{
"display_name": "Ionic Developer",
"kra_matches": [
{
"kra_text": "service and API integration",
"sentence": "Ability to integrate APIs and RESTful web services for mobile apps.",
"similarity": 0.625
},
{
"kra_text": "service and API integration",
"sentence": "Ability to integrate APIs and RESTful web services for mobile apps.",
"similarity": 0.625
},
{
"kra_text": "Mobile app screens and navigation",
"sentence": "Design pattern - MVC, MVVM, Viper, Swift UI",
"similarity": 0.4581
}
],
"matched_count": null,
"matched_skills": null,
"role_id": 434,
"score": 0.5694,
"slug": "ionic-developer",
"total_count": null
},
{
"display_name": "Flutter Developer",
"kra_matches": [
{
"kra_text": "integrate external APIs and data sources",
"sentence": "Ability to integrate APIs and RESTful web services for mobile apps.",
"similarity": 0.5846
},
{
"kra_text": "integrate external APIs and data sources",
"sentence": "Ability to integrate APIs and RESTful web services for mobile apps.",
"similarity": 0.5846
},
{
"kra_text": "Implement user-facing screens and flows",
"sentence": "Design pattern - MVC, MVVM, Viper, Swift UI",
"similarity": 0.4665
}
],
"matched_count": null,
"matched_skills": null,
"role_id": 74,
"score": 0.5452,
"slug": "flutter-developer",
"total_count": null
},
{
"display_name": "Android Developer",
"kra_matches": [
{
"kra_text": "Integrates Android apps with RESTful backend APIs using Retrofit and OkHttp, handling JSON parsing, authentication headers, and network error recovery.",
"sentence": "Ability to integrate APIs and RESTful web services for mobile apps.",
"similarity": 0.6235
},
{
"kra_text": "Integrates Android apps with RESTful backend APIs using Retrofit and OkHttp, handling JSON parsing, authentication headers, and network error recovery.",
"sentence": "Ability to integrate APIs and RESTful web services for mobile apps.",
"similarity": 0.6235
},
{
"kra_text": "Develops native Android features using Kotlin or Java with Android SDK, Jetpack Compose, and Material Design components following platform conventions.",
"sentence": "Design pattern - MVC, MVVM, Viper, Swift UI",
"similarity": 0.3782
}
],
"matched_count": null,
"matched_skills": null,
"role_id": 4,
"score": 0.5417,
"slug": "android-engineer",
"total_count": null
}
],
"skill_match_roles": [
{
"display_name": "Native Mobile Developer",
"kra_matches": null,
"matched_count": 5,
"matched_skills": [
"MVC",
"MVVM",
"Swift",
"SwiftUI",
"VIPER"
],
"role_id": 75,
"score": 0.4545,
"slug": "native-mobile-developer",
"total_count": 11
},
{
"display_name": "iOS Developer",
"kra_matches": null,
"matched_count": 4,
"matched_skills": [
"MVC",
"MVVM",
"Swift",
"SwiftUI"
],
"role_id": 6,
"score": 0.3636,
"slug": "ios-engineer",
"total_count": 11
},
{
"display_name": "Fullstack Developer",
"kra_matches": null,
"matched_count": 3,
"matched_skills": [
"API",
"MVC",
"REST"
],
"role_id": 15,
"score": 0.2727,
"slug": "full-stack-engineer",
"total_count": 11
},
{
"display_name": "Android Developer",
"kra_matches": null,
"matched_count": 3,
"matched_skills": [
"MVC",
"MVVM",
"SwiftUI"
],
"role_id": 4,
"score": 0.2727,
"slug": "android-engineer",
"total_count": 11
},
{
"display_name": ".NET Backend Developer",
"kra_matches": null,
"matched_count": 2,
"matched_skills": [
"MVC",
"REST"
],
"role_id": 83,
"score": 0.1818,
"slug": "dotnet-backend-developer",
"total_count": 11
}
]
},
"stage4_decision": {
"alias_collision_detected": false,
"case": "DOMAIN",
"chosen_role": {
"display_name": "Native Mobile Developer",
"kra_matches": null,
"matched_count": null,
"matched_skills": null,
"role_id": 75,
"score": 0.98,
"slug": "native-mobile-developer",
"total_count": null
},
"confidence": 0.98,
"is_new_role": false,
"llm2_fired": false,
"llm2_reasoning": null,
"matched_dimensions": [
"Native Mobile App Development",
"Mobile UI/UX Design",
"API Integration",
"iOS Development",
"Android Development"
],
"matched_kras": [
"Experience with full-cycle mobile app development in Android",
"Experience with full-cycle mobile app development in iOS",
"Ability to integrate APIs and RESTful web services for mobile apps",
"Knowledge of UI and UX design principles"
],
"matched_skills": [
"UI and UX design principles",
"Android Studio",
"Android SDK",
"full-cycle mobile app development",
"API",
"RESTful web services",
"MVC",
"MVVM",
"Viper",
"Swift UI",
"Swift",
"AppCode",
"CodeRunner",
"Xcode",
"Apple OS frameworks"
],
"new_role_display_name": null,
"new_role_slug": null,
"queued": false,
"reasoning": "Domain=Software Engineering; The JD is centered on full-cycle iOS and Android mobile app development with native SDKs, IDEs, and mobile UI/UX, which best matches Native Mobile Developer.",
"sub_role": null
},
"stage5_updates": {
"centroid_n_after": 13,
"centroid_updated": true,
"collision_log_id": null,
"new_kra_attached": null,
"new_skills_attached": [
{
"is_primary": true,
"queue_id": 7184,
"role_display_name": "Native Mobile Developer",
"role_slug": "native-mobile-developer",
"skill_name": "Android Studio",
"status": "pending"
},
{
"is_primary": true,
"queue_id": 7185,
"role_display_name": "Native Mobile Developer",
"role_slug": "native-mobile-developer",
"skill_name": "Android SDK",
"status": "pending"
},
{
"is_primary": false,
"queue_id": 7186,
"role_display_name": "Native Mobile Developer",
"role_slug": "native-mobile-developer",
"skill_name": "AppCode",
"status": "pending"
},
{
"is_primary": false,
"queue_id": 7187,
"role_display_name": "Native Mobile Developer",
"role_slug": "native-mobile-developer",
"skill_name": "CodeRunner",
"status": "pending"
},
{
"is_primary": false,
"queue_id": 7188,
"role_display_name": "Native Mobile Developer",
"role_slug": "native-mobile-developer",
"skill_name": "Core Animation",
"status": "pending"
},
{
"is_primary": false,
"queue_id": 7189,
"role_display_name": "Native Mobile Developer",
"role_slug": "native-mobile-developer",
"skill_name": "Core Graphics",
"status": "pending"
},
{
"is_primary": false,
"queue_id": 7190,
"role_display_name": "Native Mobile Developer",
"role_slug": "native-mobile-developer",
"skill_name": "Core Text",
"status": "pending"
}
],
"queue_entry_id": null,
"v3_pipeline_triggered": false,
"v3_role_slug": null,
"v3_run_id": null
}
}
API 2 — extract-details
{
"alias_matches": [
{
"alias_persist_skipped_reason": "alias_text already exists for this canonical skill",
"alias_persisted": false,
"existing_alias_id": 2541,
"existing_alias_text": "Android",
"input_term": "Android",
"matched_canonical": {
"category_id": 9,
"display_name": "Android",
"id": 1595,
"is_also_category": false,
"is_extractable": true,
"skill_nature": "PLATFORM",
"slug": "android",
"sub_category_id": 1201,
"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": 2514,
"existing_alias_text": "API",
"input_term": "API",
"matched_canonical": {
"category_id": 2,
"display_name": "API",
"id": 1568,
"is_also_category": false,
"is_extractable": true,
"skill_nature": "CONCEPT",
"slug": "api",
"sub_category_id": 1174,
"typical_lifespan": "EVERGREEN",
"volatility": "STABLE"
},
"matched_via": "alias"
},
{
"alias_persist_skipped_reason": "alias_text already exists for this canonical skill",
"alias_persisted": false,
"existing_alias_id": 106,
"existing_alias_text": "REST",
"input_term": "REST",
"matched_canonical": {
"category_id": 2,
"display_name": "REST",
"id": 11,
"is_also_category": false,
"is_extractable": true,
"skill_nature": "CONCEPT",
"slug": "rest",
"sub_category_id": 2122,
"typical_lifespan": "EVERGREEN",
"volatility": "STABLE"
},
"matched_via": "alias"
},
{
"alias_persist_skipped_reason": "alias_text already exists for this canonical skill",
"alias_persisted": false,
"existing_alias_id": 831,
"existing_alias_text": "MVC",
"input_term": "MVC",
"matched_canonical": {
"category_id": 1,
"display_name": "MVC",
"id": 505,
"is_also_category": false,
"is_extractable": true,
"skill_nature": "PATTERN",
"slug": "mvc",
"sub_category_id": 2462,
"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": 830,
"existing_alias_text": "MVVM",
"input_term": "MVVM",
"matched_canonical": {
"category_id": 1,
"display_name": "MVVM",
"id": 504,
"is_also_category": false,
"is_extractable": true,
"skill_nature": "PATTERN",
"slug": "mvvm",
"sub_category_id": 662,
"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": 3090,
"existing_alias_text": "VIPER",
"input_term": "Viper",
"matched_canonical": {
"category_id": 1,
"display_name": "VIPER",
"id": 2056,
"is_also_category": false,
"is_extractable": true,
"skill_nature": "PATTERN",
"slug": "viper",
"sub_category_id": 662,
"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": 770,
"existing_alias_text": "SwiftUI",
"input_term": "SwiftUI",
"matched_canonical": {
"category_id": 5,
"display_name": "SwiftUI",
"id": 444,
"is_also_category": false,
"is_extractable": true,
"skill_nature": "FRAMEWORK",
"slug": "swiftui",
"sub_category_id": 341,
"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": 805,
"existing_alias_text": "Xcode",
"input_term": "Xcode",
"matched_canonical": {
"category_id": 13,
"display_name": "Xcode",
"id": 479,
"is_also_category": false,
"is_extractable": true,
"skill_nature": "TOOL",
"slug": "xcode",
"sub_category_id": 359,
"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": 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": 785,
"existing_alias_text": "Core Data",
"input_term": "Core Data",
"matched_canonical": {
"category_id": 5,
"display_name": "Core Data",
"id": 459,
"is_also_category": false,
"is_extractable": true,
"skill_nature": "FRAMEWORK",
"slug": "core-data",
"sub_category_id": 336,
"typical_lifespan": "EVERGREEN",
"volatility": "STABLE"
},
"matched_via": "alias"
}
],
"candidate_roles": [
{
"display_name": "Angular Frontend Developer",
"id": 90,
"rationale": null,
"role_archetype": "Engineering",
"slug": "angular-frontend-developer",
"source": "db"
},
{
"display_name": "Frontend Developer",
"id": 7,
"rationale": null,
"role_archetype": null,
"slug": "frontend-engineer",
"source": "db"
},
{
"display_name": "Fullstack Developer",
"id": 15,
"rationale": null,
"role_archetype": null,
"slug": "full-stack-engineer",
"source": "db"
},
{
"display_name": "React Frontend Developer",
"id": 89,
"rationale": null,
"role_archetype": "Engineering",
"slug": "react-frontend-developer",
"source": "db"
},
{
"display_name": "Svelte Frontend Developer",
"id": 92,
"rationale": null,
"role_archetype": "Engineering",
"slug": "svelte-frontend-developer",
"source": "db"
},
{
"display_name": "Vue Frontend Developer",
"id": 91,
"rationale": null,
"role_archetype": "Engineering",
"slug": "vue-frontend-developer",
"source": "db"
},
{
"display_name": "Web Developer",
"id": 25,
"rationale": null,
"role_archetype": null,
"slug": "web-developer",
"source": "db"
},
{
"display_name": "Backend Developer",
"id": 1,
"rationale": null,
"role_archetype": "A Backend Engineer designs, builds, and maintains the server-side logic and data handling that power applications and services. They focus on implementing reliable business functionality, integrating with other systems, and ensuring the backend is scalable, maintainable, and observable.",
"slug": "backend-engineer",
"source": "db"
},
{
"display_name": ".NET Backend Developer",
"id": 83,
"rationale": null,
"role_archetype": "Engineering",
"slug": "dotnet-backend-developer",
"source": "db"
},
{
"display_name": "Go Backend Developer",
"id": 81,
"rationale": null,
"role_archetype": "Engineering",
"slug": "go-backend-developer",
"source": "db"
},
{
"display_name": "Kotlin Backend Developer",
"id": 84,
"rationale": null,
"role_archetype": "Engineering",
"slug": "kotlin-server-backend-developer",
"source": "db"
},
{
"display_name": "Node.js Backend Developer",
"id": 82,
"rationale": null,
"role_archetype": "Engineering",
"slug": "node-backend-developer",
"source": "db"
},
{
"display_name": "PHP Backend Developer",
"id": 86,
"rationale": null,
"role_archetype": "Engineering",
"slug": "php-backend-developer",
"source": "db"
},
{
"display_name": "Python Backend Developer",
"id": 80,
"rationale": null,
"role_archetype": "Engineering",
"slug": "python-backend-developer",
"source": "db"
},
{
"display_name": "Ruby Backend Developer",
"id": 85,
"rationale": null,
"role_archetype": "Engineering",
"slug": "ruby-backend-developer",
"source": "db"
},
{
"display_name": "Scala Backend Developer",
"id": 87,
"rationale": null,
"role_archetype": "Engineering",
"slug": "scala-backend-developer",
"source": "db"
},
{
"display_name": "Pega Developer",
"id": 24,
"rationale": null,
"role_archetype": null,
"slug": "pega-developer",
"source": "db"
},
{
"display_name": "Sitecore Dev",
"id": 233,
"rationale": null,
"role_archetype": "Engineering",
"slug": "sitecore-dev",
"source": "db"
},
{
"display_name": "Android Developer",
"id": 4,
"rationale": null,
"role_archetype": null,
"slug": "android-engineer",
"source": "db"
},
{
"display_name": "iOS Developer",
"id": 6,
"rationale": null,
"role_archetype": null,
"slug": "ios-engineer",
"source": "db"
},
{
"display_name": "Native Mobile Developer",
"id": 75,
"rationale": null,
"role_archetype": "Engineering",
"slug": "native-mobile-developer",
"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"
},
{
"display_name": "Flutter Developer",
"id": 74,
"rationale": null,
"role_archetype": "Engineering",
"slug": "flutter-developer",
"source": "db"
}
],
"chosen_role": {
"display_name": "Native Mobile Developer",
"id": 75,
"rationale": "Domain=Software Engineering; The JD is centered on full-cycle iOS and Android mobile app development with native SDKs, IDEs, and mobile UI/UX, which best matches Native Mobile 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": "Android",
"llm_role": null,
"roles_from_db": []
},
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "API Integration and Data Fetching",
"id": 127,
"rationale": "Client-side integration with backend endpoints and third-party services, including request shaping, response handling, and synchronization with UI state. This is central to frontend work because most screens depend on remote data.",
"slug": "api-integration-and-data-fetching",
"source": "db"
},
"input_skill": "API",
"llm_role": null,
"roles_from_db": [
{
"display_name": "Angular Frontend Developer",
"id": 90,
"rationale": null,
"role_archetype": "Engineering",
"slug": "angular-frontend-developer",
"source": "db"
},
{
"display_name": "Frontend Developer",
"id": 7,
"rationale": null,
"role_archetype": null,
"slug": "frontend-engineer",
"source": "db"
},
{
"display_name": "Fullstack Developer",
"id": 15,
"rationale": null,
"role_archetype": null,
"slug": "full-stack-engineer",
"source": "db"
},
{
"display_name": "React Frontend Developer",
"id": 89,
"rationale": null,
"role_archetype": "Engineering",
"slug": "react-frontend-developer",
"source": "db"
},
{
"display_name": "Svelte Frontend Developer",
"id": 92,
"rationale": null,
"role_archetype": "Engineering",
"slug": "svelte-frontend-developer",
"source": "db"
},
{
"display_name": "Vue Frontend Developer",
"id": 91,
"rationale": null,
"role_archetype": "Engineering",
"slug": "vue-frontend-developer",
"source": "db"
},
{
"display_name": "Web Developer",
"id": 25,
"rationale": null,
"role_archetype": null,
"slug": "web-developer",
"source": "db"
}
]
},
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "API Design and Contracts",
"id": 3,
"rationale": "Designing request/response shapes and the rules that govern client-server interaction. This cluster is coherent because full stack engineers often own the contract between UI behavior and backend implementation.",
"slug": "api-design-and-contracts",
"source": "db"
},
"input_skill": "REST",
"llm_role": null,
"roles_from_db": [
{
"display_name": "Backend Developer",
"id": 1,
"rationale": null,
"role_archetype": "A Backend Engineer designs, builds, and maintains the server-side logic and data handling that power applications and services. They focus on implementing reliable business functionality, integrating with other systems, and ensuring the backend is scalable, maintainable, and observable.",
"slug": "backend-engineer",
"source": "db"
},
{
"display_name": "Fullstack Developer",
"id": 15,
"rationale": null,
"role_archetype": null,
"slug": "full-stack-engineer",
"source": "db"
}
]
},
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "API Interface and Contract Design",
"id": 289,
"rationale": "Designing backend service interfaces and contracts that other systems consume, including endpoint and operation shape, request/response payloads, schema and validation, pagination, filtering, idempotency, versioning, status codes, and backward compatibility across REST, GraphQL, gRPC, and OpenAPI-based APIs.",
"slug": "api-interface-and-contract-design",
"source": "db"
},
"input_skill": "REST",
"llm_role": null,
"roles_from_db": [
{
"display_name": ".NET Backend Developer",
"id": 83,
"rationale": null,
"role_archetype": "Engineering",
"slug": "dotnet-backend-developer",
"source": "db"
},
{
"display_name": "Go Backend Developer",
"id": 81,
"rationale": null,
"role_archetype": "Engineering",
"slug": "go-backend-developer",
"source": "db"
},
{
"display_name": "Kotlin Backend Developer",
"id": 84,
"rationale": null,
"role_archetype": "Engineering",
"slug": "kotlin-server-backend-developer",
"source": "db"
},
{
"display_name": "Node.js Backend Developer",
"id": 82,
"rationale": null,
"role_archetype": "Engineering",
"slug": "node-backend-developer",
"source": "db"
},
{
"display_name": "PHP Backend Developer",
"id": 86,
"rationale": null,
"role_archetype": "Engineering",
"slug": "php-backend-developer",
"source": "db"
},
{
"display_name": "Python Backend Developer",
"id": 80,
"rationale": null,
"role_archetype": "Engineering",
"slug": "python-backend-developer",
"source": "db"
},
{
"display_name": "Ruby Backend Developer",
"id": 85,
"rationale": null,
"role_archetype": "Engineering",
"slug": "ruby-backend-developer",
"source": "db"
},
{
"display_name": "Scala Backend Developer",
"id": 87,
"rationale": null,
"role_archetype": "Engineering",
"slug": "scala-backend-developer",
"source": "db"
}
]
},
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Integration Protocols \u0026 Standards",
"id": 271,
"rationale": "Standards and protocols for integrating Pega applications.",
"slug": "integration-protocols-standards",
"source": "db"
},
"input_skill": "REST",
"llm_role": null,
"roles_from_db": [
{
"display_name": "Pega Developer",
"id": 24,
"rationale": null,
"role_archetype": null,
"slug": "pega-developer",
"source": "db"
}
]
},
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Standards \u0026 Protocols Compliance",
"id": 452,
"rationale": "Encompasses key web and data standards, protocols, and compliance requirements relevant to Sitecore implementations.",
"slug": "standards-protocols-compliance",
"source": "db"
},
"input_skill": "REST",
"llm_role": null,
"roles_from_db": [
{
"display_name": "Sitecore Dev",
"id": 233,
"rationale": null,
"role_archetype": "Engineering",
"slug": "sitecore-dev",
"source": "db"
}
]
},
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "ASP.NET Core Web Frameworks",
"id": 363,
"rationale": "Server-side web frameworks and hosting models used to build HTTP APIs, middleware, filters, and request pipelines. This cluster is coherent because it defines how backend services receive, process, and return requests.",
"slug": "asp-net-core-web-frameworks",
"source": "db"
},
"input_skill": "MVC",
"llm_role": null,
"roles_from_db": [
{
"display_name": ".NET Backend Developer",
"id": 83,
"rationale": null,
"role_archetype": "Engineering",
"slug": "dotnet-backend-developer",
"source": "db"
}
]
},
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "App Architecture and Dependency Injection",
"id": 94,
"rationale": "Structural patterns used to organize iOS code into testable, maintainable feature modules and layers. iOS engineers use these patterns to separate UI, state, and service integration concerns.",
"slug": "app-architecture-and-dependency-injection",
"source": "db"
},
"input_skill": "MVC",
"llm_role": null,
"roles_from_db": [
{
"display_name": "Android Developer",
"id": 4,
"rationale": null,
"role_archetype": null,
"slug": "android-engineer",
"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": "Application Architecture and Code Organization",
"id": 220,
"rationale": "Structural patterns for organizing product code into maintainable modules, layers, and feature boundaries. Full stack engineers need this to keep cross-layer feature work understandable as the product grows.",
"slug": "application-architecture-and-code-organization",
"source": "db"
},
"input_skill": "MVC",
"llm_role": null,
"roles_from_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": "Native Mobile App Architecture and Dependency Injection",
"id": 273,
"rationale": "Structural patterns for organizing native mobile application code into maintainable, testable modules, layers, and feature boundaries. This includes app architecture patterns such as MVVM, MVC, MVI, VIPER, and Clean Architecture; dependency injection frameworks and patterns such as Hilt, Dagger, and Koin; and code organization techniques such as modularization, feature modules, repository pattern, and use-case layering to separate UI, state, data, and platform concerns across a growing codebase.",
"slug": "native-mobile-app-architecture-and-dependency-injection",
"source": "db"
},
"input_skill": "MVC",
"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": "App Architecture and Dependency Injection",
"id": 94,
"rationale": "Structural patterns used to organize iOS code into testable, maintainable feature modules and layers. iOS engineers use these patterns to separate UI, state, and service integration concerns.",
"slug": "app-architecture-and-dependency-injection",
"source": "db"
},
"input_skill": "MVVM",
"llm_role": null,
"roles_from_db": [
{
"display_name": "Android Developer",
"id": 4,
"rationale": null,
"role_archetype": null,
"slug": "android-engineer",
"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": "Mobile Architecture and Code Organization",
"id": 170,
"rationale": "Structural patterns used to organize shared mobile code into maintainable modules, layers, and feature boundaries. Senior hybrid developers often own these patterns to keep cross-platform code testable and adaptable to platform exceptions.",
"slug": "mobile-architecture-and-code-organization",
"source": "db"
},
"input_skill": "MVVM",
"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": "Native Mobile App Architecture and Dependency Injection",
"id": 273,
"rationale": "Structural patterns for organizing native mobile application code into maintainable, testable modules, layers, and feature boundaries. This includes app architecture patterns such as MVVM, MVC, MVI, VIPER, and Clean Architecture; dependency injection frameworks and patterns such as Hilt, Dagger, and Koin; and code organization techniques such as modularization, feature modules, repository pattern, and use-case layering to separate UI, state, data, and platform concerns across a growing codebase.",
"slug": "native-mobile-app-architecture-and-dependency-injection",
"source": "db"
},
"input_skill": "MVVM",
"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": "Native Mobile App Architecture and Dependency Injection",
"id": 273,
"rationale": "Structural patterns for organizing native mobile application code into maintainable, testable modules, layers, and feature boundaries. This includes app architecture patterns such as MVVM, MVC, MVI, VIPER, and Clean Architecture; dependency injection frameworks and patterns such as Hilt, Dagger, and Koin; and code organization techniques such as modularization, feature modules, repository pattern, and use-case layering to separate UI, state, data, and platform concerns across a growing codebase.",
"slug": "native-mobile-app-architecture-and-dependency-injection",
"source": "db"
},
"input_skill": "Viper",
"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": "Android UI Frameworks",
"id": 162,
"rationale": "Frameworks and component models used to build Android screens, layouts, and interactive UI behavior. This cluster covers both modern declarative UI and legacy view-based interfaces that Android engineers maintain in real products.",
"slug": "android-ui-frameworks",
"source": "db"
},
"input_skill": "SwiftUI",
"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"
}
]
},
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "UIKit and SwiftUI",
"id": 82,
"rationale": "Frameworks and component models used to build screens, layouts, and interactive UI behavior on iOS. This cluster covers both declarative and imperative UI work needed to implement app flows.",
"slug": "uikit-and-swiftui",
"source": "db"
},
"input_skill": "SwiftUI",
"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": "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": "Build and Release Tooling",
"id": 89,
"rationale": "Tooling used to compile, sign, package, and automate iOS app builds. iOS engineers rely on this stack to produce reproducible release artifacts and manage build-time configuration.",
"slug": "build-and-release-tooling",
"source": "db"
},
"input_skill": "Xcode",
"llm_role": null,
"roles_from_db": [
{
"display_name": "Android Developer",
"id": 4,
"rationale": null,
"role_archetype": null,
"slug": "android-engineer",
"source": "db"
},
{
"display_name": "Flutter Developer",
"id": 74,
"rationale": null,
"role_archetype": "Engineering",
"slug": "flutter-developer",
"source": "db"
},
{
"display_name": "Hybrid Mobile Developer",
"id": 11,
"rationale": null,
"role_archetype": null,
"slug": "hybrid-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": "Native Mobile Build and Release Tooling",
"id": 272,
"rationale": "Tooling used to compile, sign, package, version, and automate release-ready builds for native mobile apps across iOS and Android. This cluster includes platform-specific build systems and release automation used to produce reproducible app artifacts and prepare internal or public release candidates.",
"slug": "native-mobile-build-and-release-tooling",
"source": "db"
},
"input_skill": "Xcode",
"llm_role": null,
"roles_from_db": [
{
"display_name": "Flutter Developer",
"id": 74,
"rationale": null,
"role_archetype": "Engineering",
"slug": "flutter-developer",
"source": "db"
},
{
"display_name": "Native Mobile Developer",
"id": 75,
"rationale": null,
"role_archetype": "Engineering",
"slug": "native-mobile-developer",
"source": "db"
},
{
"display_name": "React Native Developer",
"id": 73,
"rationale": null,
"role_archetype": "Engineering",
"slug": "react-native-developer",
"source": "db"
}
]
},
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "React Frontend Development",
"id": 96,
"rationale": "Building interactive web user interfaces with React.js, including component composition, state management, hooks, and rendering patterns. React.js belongs here because it is a core library for client-side UI development in modern web applications.",
"slug": "d_init_01",
"source": "db"
},
"input_skill": "iOS",
"llm_role": null,
"roles_from_db": []
},
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Local Persistence and Offline Behavior",
"id": 85,
"rationale": "On-device storage used for caching, offline support, and durable client state. This cluster is coherent because iOS apps often need to preserve user progress and data when connectivity is limited.",
"slug": "local-persistence-and-offline-behavior",
"source": "db"
},
"input_skill": "Core Data",
"llm_role": null,
"roles_from_db": [
{
"display_name": "Android Developer",
"id": 4,
"rationale": null,
"role_archetype": null,
"slug": "android-engineer",
"source": "db"
},
{
"display_name": "Flutter Developer",
"id": 74,
"rationale": null,
"role_archetype": "Engineering",
"slug": "flutter-developer",
"source": "db"
},
{
"display_name": "Hybrid Mobile Developer",
"id": 11,
"rationale": null,
"role_archetype": null,
"slug": "hybrid-mobile-developer",
"source": "db"
},
{
"display_name": "Native Mobile Developer",
"id": 75,
"rationale": null,
"role_archetype": "Engineering",
"slug": "native-mobile-developer",
"source": "db"
},
{
"display_name": "React Native Developer",
"id": 73,
"rationale": null,
"role_archetype": "Engineering",
"slug": "react-native-developer",
"source": "db"
},
{
"display_name": "iOS Developer",
"id": 6,
"rationale": null,
"role_archetype": null,
"slug": "ios-engineer",
"source": "db"
}
]
}
],
"input_final_skills": [
"Android Studio",
"Android SDK",
"Android",
"API",
"REST",
"MVC",
"MVVM",
"Viper",
"SwiftUI",
"Swift",
"AppCode",
"CodeRunner",
"Xcode",
"iOS",
"Core Animation",
"Core Data",
"Core Graphics",
"Core Text"
],
"input_llm_skills": [
"Android Studio",
"Android SDK",
"Android",
"API",
"REST",
"MVC",
"MVVM",
"Viper",
"SwiftUI",
"Swift",
"AppCode",
"CodeRunner",
"Xcode",
"iOS",
"Core Animation",
"Core Data",
"Core Graphics",
"Core Text"
],
"new_aliases_persisted": 0,
"run_id": "bb7c5611-af3b-49f4-9328-45612647f083",
"skills_detail": [
{
"aliases_in_db": [],
"canonical": null,
"dimensions": [],
"input_skill": "Android Studio",
"matched_via": null,
"new_alias_persisted": false,
"new_alias_text": null,
"new_skill_meta": {
"derived": {
"category": "Development Environments",
"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": "android-studio",
"split_log": [],
"typed": null,
"warnings": []
},
"source_tag": "llm",
"was_in_llm_skills": true
},
{
"aliases_in_db": [],
"canonical": null,
"dimensions": [],
"input_skill": "Android SDK",
"matched_via": null,
"new_alias_persisted": false,
"new_alias_text": null,
"new_skill_meta": {
"derived": {
"category": "Mobile Development",
"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": "android-sdk",
"split_log": [],
"typed": null,
"warnings": []
},
"source_tag": "llm",
"was_in_llm_skills": true
},
{
"aliases_in_db": [
{
"alias_text": "Android",
"alias_type": "CANONICAL",
"id": 2541,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
}
],
"canonical": {
"category_id": 9,
"display_name": "Android",
"id": 1595,
"is_also_category": false,
"is_extractable": true,
"skill_nature": "PLATFORM",
"slug": "android",
"sub_category_id": 1201,
"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": "Android",
"llm_role": null,
"roles_from_db": []
}
],
"input_skill": "Android",
"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": "API",
"alias_type": "CANONICAL",
"id": 2514,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
}
],
"canonical": {
"category_id": 2,
"display_name": "API",
"id": 1568,
"is_also_category": false,
"is_extractable": true,
"skill_nature": "CONCEPT",
"slug": "api",
"sub_category_id": 1174,
"typical_lifespan": "EVERGREEN",
"volatility": "STABLE"
},
"dimensions": [
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "API Integration and Data Fetching",
"id": 127,
"rationale": "Client-side integration with backend endpoints and third-party services, including request shaping, response handling, and synchronization with UI state. This is central to frontend work because most screens depend on remote data.",
"slug": "api-integration-and-data-fetching",
"source": "db"
},
"input_skill": "API",
"llm_role": null,
"roles_from_db": [
{
"display_name": "Angular Frontend Developer",
"id": 90,
"rationale": null,
"role_archetype": "Engineering",
"slug": "angular-frontend-developer",
"source": "db"
},
{
"display_name": "Frontend Developer",
"id": 7,
"rationale": null,
"role_archetype": null,
"slug": "frontend-engineer",
"source": "db"
},
{
"display_name": "Fullstack Developer",
"id": 15,
"rationale": null,
"role_archetype": null,
"slug": "full-stack-engineer",
"source": "db"
},
{
"display_name": "React Frontend Developer",
"id": 89,
"rationale": null,
"role_archetype": "Engineering",
"slug": "react-frontend-developer",
"source": "db"
},
{
"display_name": "Svelte Frontend Developer",
"id": 92,
"rationale": null,
"role_archetype": "Engineering",
"slug": "svelte-frontend-developer",
"source": "db"
},
{
"display_name": "Vue Frontend Developer",
"id": 91,
"rationale": null,
"role_archetype": "Engineering",
"slug": "vue-frontend-developer",
"source": "db"
},
{
"display_name": "Web Developer",
"id": 25,
"rationale": null,
"role_archetype": null,
"slug": "web-developer",
"source": "db"
}
]
}
],
"input_skill": "API",
"matched_via": "alias",
"new_alias_persisted": false,
"new_alias_text": null,
"new_skill_meta": null,
"source_tag": "db",
"was_in_llm_skills": true
},
{
"aliases_in_db": [
{
"alias_text": "REST",
"alias_type": "CANONICAL",
"id": 106,
"is_primary": true,
"match_strategy": "CASE_INSENSITIVE"
}
],
"canonical": {
"category_id": 2,
"display_name": "REST",
"id": 11,
"is_also_category": false,
"is_extractable": true,
"skill_nature": "CONCEPT",
"slug": "rest",
"sub_category_id": 2122,
"typical_lifespan": "EVERGREEN",
"volatility": "STABLE"
},
"dimensions": [
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "API Design and Contracts",
"id": 3,
"rationale": "Designing request/response shapes and the rules that govern client-server interaction. This cluster is coherent because full stack engineers often own the contract between UI behavior and backend implementation.",
"slug": "api-design-and-contracts",
"source": "db"
},
"input_skill": "REST",
"llm_role": null,
"roles_from_db": [
{
"display_name": "Backend Developer",
"id": 1,
"rationale": null,
"role_archetype": "A Backend Engineer designs, builds, and maintains the server-side logic and data handling that power applications and services. They focus on implementing reliable business functionality, integrating with other systems, and ensuring the backend is scalable, maintainable, and observable.",
"slug": "backend-engineer",
"source": "db"
},
{
"display_name": "Fullstack Developer",
"id": 15,
"rationale": null,
"role_archetype": null,
"slug": "full-stack-engineer",
"source": "db"
}
]
},
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "API Interface and Contract Design",
"id": 289,
"rationale": "Designing backend service interfaces and contracts that other systems consume, including endpoint and operation shape, request/response payloads, schema and validation, pagination, filtering, idempotency, versioning, status codes, and backward compatibility across REST, GraphQL, gRPC, and OpenAPI-based APIs.",
"slug": "api-interface-and-contract-design",
"source": "db"
},
"input_skill": "REST",
"llm_role": null,
"roles_from_db": [
{
"display_name": ".NET Backend Developer",
"id": 83,
"rationale": null,
"role_archetype": "Engineering",
"slug": "dotnet-backend-developer",
"source": "db"
},
{
"display_name": "Go Backend Developer",
"id": 81,
"rationale": null,
"role_archetype": "Engineering",
"slug": "go-backend-developer",
"source": "db"
},
{
"display_name": "Kotlin Backend Developer",
"id": 84,
"rationale": null,
"role_archetype": "Engineering",
"slug": "kotlin-server-backend-developer",
"source": "db"
},
{
"display_name": "Node.js Backend Developer",
"id": 82,
"rationale": null,
"role_archetype": "Engineering",
"slug": "node-backend-developer",
"source": "db"
},
{
"display_name": "PHP Backend Developer",
"id": 86,
"rationale": null,
"role_archetype": "Engineering",
"slug": "php-backend-developer",
"source": "db"
},
{
"display_name": "Python Backend Developer",
"id": 80,
"rationale": null,
"role_archetype": "Engineering",
"slug": "python-backend-developer",
"source": "db"
},
{
"display_name": "Ruby Backend Developer",
"id": 85,
"rationale": null,
"role_archetype": "Engineering",
"slug": "ruby-backend-developer",
"source": "db"
},
{
"display_name": "Scala Backend Developer",
"id": 87,
"rationale": null,
"role_archetype": "Engineering",
"slug": "scala-backend-developer",
"source": "db"
}
]
},
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Integration Protocols \u0026 Standards",
"id": 271,
"rationale": "Standards and protocols for integrating Pega applications.",
"slug": "integration-protocols-standards",
"source": "db"
},
"input_skill": "REST",
"llm_role": null,
"roles_from_db": [
{
"display_name": "Pega Developer",
"id": 24,
"rationale": null,
"role_archetype": null,
"slug": "pega-developer",
"source": "db"
}
]
},
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Standards \u0026 Protocols Compliance",
"id": 452,
"rationale": "Encompasses key web and data standards, protocols, and compliance requirements relevant to Sitecore implementations.",
"slug": "standards-protocols-compliance",
"source": "db"
},
"input_skill": "REST",
"llm_role": null,
"roles_from_db": [
{
"display_name": "Sitecore Dev",
"id": 233,
"rationale": null,
"role_archetype": "Engineering",
"slug": "sitecore-dev",
"source": "db"
}
]
}
],
"input_skill": "REST",
"matched_via": "alias",
"new_alias_persisted": false,
"new_alias_text": null,
"new_skill_meta": null,
"source_tag": "db",
"was_in_llm_skills": true
},
{
"aliases_in_db": [
{
"alias_text": "MVC",
"alias_type": "CANONICAL",
"id": 831,
"is_primary": true,
"match_strategy": "CASE_INSENSITIVE"
}
],
"canonical": {
"category_id": 1,
"display_name": "MVC",
"id": 505,
"is_also_category": false,
"is_extractable": true,
"skill_nature": "PATTERN",
"slug": "mvc",
"sub_category_id": 2462,
"typical_lifespan": "EVERGREEN",
"volatility": "STABLE"
},
"dimensions": [
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "ASP.NET Core Web Frameworks",
"id": 363,
"rationale": "Server-side web frameworks and hosting models used to build HTTP APIs, middleware, filters, and request pipelines. This cluster is coherent because it defines how backend services receive, process, and return requests.",
"slug": "asp-net-core-web-frameworks",
"source": "db"
},
"input_skill": "MVC",
"llm_role": null,
"roles_from_db": [
{
"display_name": ".NET Backend Developer",
"id": 83,
"rationale": null,
"role_archetype": "Engineering",
"slug": "dotnet-backend-developer",
"source": "db"
}
]
},
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "App Architecture and Dependency Injection",
"id": 94,
"rationale": "Structural patterns used to organize iOS code into testable, maintainable feature modules and layers. iOS engineers use these patterns to separate UI, state, and service integration concerns.",
"slug": "app-architecture-and-dependency-injection",
"source": "db"
},
"input_skill": "MVC",
"llm_role": null,
"roles_from_db": [
{
"display_name": "Android Developer",
"id": 4,
"rationale": null,
"role_archetype": null,
"slug": "android-engineer",
"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": "Application Architecture and Code Organization",
"id": 220,
"rationale": "Structural patterns for organizing product code into maintainable modules, layers, and feature boundaries. Full stack engineers need this to keep cross-layer feature work understandable as the product grows.",
"slug": "application-architecture-and-code-organization",
"source": "db"
},
"input_skill": "MVC",
"llm_role": null,
"roles_from_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": "Native Mobile App Architecture and Dependency Injection",
"id": 273,
"rationale": "Structural patterns for organizing native mobile application code into maintainable, testable modules, layers, and feature boundaries. This includes app architecture patterns such as MVVM, MVC, MVI, VIPER, and Clean Architecture; dependency injection frameworks and patterns such as Hilt, Dagger, and Koin; and code organization techniques such as modularization, feature modules, repository pattern, and use-case layering to separate UI, state, data, and platform concerns across a growing codebase.",
"slug": "native-mobile-app-architecture-and-dependency-injection",
"source": "db"
},
"input_skill": "MVC",
"llm_role": null,
"roles_from_db": [
{
"display_name": "Native Mobile Developer",
"id": 75,
"rationale": null,
"role_archetype": "Engineering",
"slug": "native-mobile-developer",
"source": "db"
}
]
}
],
"input_skill": "MVC",
"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": "MVVM",
"alias_type": "CANONICAL",
"id": 830,
"is_primary": true,
"match_strategy": "CASE_INSENSITIVE"
}
],
"canonical": {
"category_id": 1,
"display_name": "MVVM",
"id": 504,
"is_also_category": false,
"is_extractable": true,
"skill_nature": "PATTERN",
"slug": "mvvm",
"sub_category_id": 662,
"typical_lifespan": "EVERGREEN",
"volatility": "STABLE"
},
"dimensions": [
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "App Architecture and Dependency Injection",
"id": 94,
"rationale": "Structural patterns used to organize iOS code into testable, maintainable feature modules and layers. iOS engineers use these patterns to separate UI, state, and service integration concerns.",
"slug": "app-architecture-and-dependency-injection",
"source": "db"
},
"input_skill": "MVVM",
"llm_role": null,
"roles_from_db": [
{
"display_name": "Android Developer",
"id": 4,
"rationale": null,
"role_archetype": null,
"slug": "android-engineer",
"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": "Mobile Architecture and Code Organization",
"id": 170,
"rationale": "Structural patterns used to organize shared mobile code into maintainable modules, layers, and feature boundaries. Senior hybrid developers often own these patterns to keep cross-platform code testable and adaptable to platform exceptions.",
"slug": "mobile-architecture-and-code-organization",
"source": "db"
},
"input_skill": "MVVM",
"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": "Native Mobile App Architecture and Dependency Injection",
"id": 273,
"rationale": "Structural patterns for organizing native mobile application code into maintainable, testable modules, layers, and feature boundaries. This includes app architecture patterns such as MVVM, MVC, MVI, VIPER, and Clean Architecture; dependency injection frameworks and patterns such as Hilt, Dagger, and Koin; and code organization techniques such as modularization, feature modules, repository pattern, and use-case layering to separate UI, state, data, and platform concerns across a growing codebase.",
"slug": "native-mobile-app-architecture-and-dependency-injection",
"source": "db"
},
"input_skill": "MVVM",
"llm_role": null,
"roles_from_db": [
{
"display_name": "Native Mobile Developer",
"id": 75,
"rationale": null,
"role_archetype": "Engineering",
"slug": "native-mobile-developer",
"source": "db"
}
]
}
],
"input_skill": "MVVM",
"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": "VIPER",
"alias_type": "CANONICAL",
"id": 3090,
"is_primary": true,
"match_strategy": "CASE_INSENSITIVE"
}
],
"canonical": {
"category_id": 1,
"display_name": "VIPER",
"id": 2056,
"is_also_category": false,
"is_extractable": true,
"skill_nature": "PATTERN",
"slug": "viper",
"sub_category_id": 662,
"typical_lifespan": "EVERGREEN",
"volatility": "STABLE"
},
"dimensions": [
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Native Mobile App Architecture and Dependency Injection",
"id": 273,
"rationale": "Structural patterns for organizing native mobile application code into maintainable, testable modules, layers, and feature boundaries. This includes app architecture patterns such as MVVM, MVC, MVI, VIPER, and Clean Architecture; dependency injection frameworks and patterns such as Hilt, Dagger, and Koin; and code organization techniques such as modularization, feature modules, repository pattern, and use-case layering to separate UI, state, data, and platform concerns across a growing codebase.",
"slug": "native-mobile-app-architecture-and-dependency-injection",
"source": "db"
},
"input_skill": "Viper",
"llm_role": null,
"roles_from_db": [
{
"display_name": "Native Mobile Developer",
"id": 75,
"rationale": null,
"role_archetype": "Engineering",
"slug": "native-mobile-developer",
"source": "db"
}
]
}
],
"input_skill": "Viper",
"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": "SwiftUI",
"alias_type": "CANONICAL",
"id": 770,
"is_primary": true,
"match_strategy": "CASE_INSENSITIVE"
}
],
"canonical": {
"category_id": 5,
"display_name": "SwiftUI",
"id": 444,
"is_also_category": false,
"is_extractable": true,
"skill_nature": "FRAMEWORK",
"slug": "swiftui",
"sub_category_id": 341,
"typical_lifespan": "EVERGREEN",
"volatility": "STABLE"
},
"dimensions": [
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Android UI Frameworks",
"id": 162,
"rationale": "Frameworks and component models used to build Android screens, layouts, and interactive UI behavior. This cluster covers both modern declarative UI and legacy view-based interfaces that Android engineers maintain in real products.",
"slug": "android-ui-frameworks",
"source": "db"
},
"input_skill": "SwiftUI",
"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"
}
]
},
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "UIKit and SwiftUI",
"id": 82,
"rationale": "Frameworks and component models used to build screens, layouts, and interactive UI behavior on iOS. This cluster covers both declarative and imperative UI work needed to implement app flows.",
"slug": "uikit-and-swiftui",
"source": "db"
},
"input_skill": "SwiftUI",
"llm_role": null,
"roles_from_db": [
{
"display_name": "iOS Developer",
"id": 6,
"rationale": null,
"role_archetype": null,
"slug": "ios-engineer",
"source": "db"
}
]
}
],
"input_skill": "SwiftUI",
"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": [],
"canonical": null,
"dimensions": [],
"input_skill": "AppCode",
"matched_via": null,
"new_alias_persisted": false,
"new_alias_text": null,
"new_skill_meta": {
"derived": {
"category": "Development Environments",
"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": "appcode",
"split_log": [],
"typed": null,
"warnings": []
},
"source_tag": "llm",
"was_in_llm_skills": true
},
{
"aliases_in_db": [],
"canonical": null,
"dimensions": [],
"input_skill": "CodeRunner",
"matched_via": null,
"new_alias_persisted": false,
"new_alias_text": null,
"new_skill_meta": {
"derived": {
"category": "Development Environments",
"skill_nature": "TOOL",
"sub_category": "general",
"typical_lifespan": "SHORT_LIVED",
"version_strategy": "VERSIONED",
"volatility": "FAST"
},
"enrichment": null,
"keep_log": [],
"locked_dimensions": [],
"merge_log": [],
"placed": null,
"relationships": null,
"skill_id": "coderunner",
"split_log": [],
"typed": null,
"warnings": []
},
"source_tag": "llm",
"was_in_llm_skills": true
},
{
"aliases_in_db": [
{
"alias_text": "Xcode",
"alias_type": "CANONICAL",
"id": 805,
"is_primary": true,
"match_strategy": "CASE_INSENSITIVE"
}
],
"canonical": {
"category_id": 13,
"display_name": "Xcode",
"id": 479,
"is_also_category": false,
"is_extractable": true,
"skill_nature": "TOOL",
"slug": "xcode",
"sub_category_id": 359,
"typical_lifespan": "EVERGREEN",
"volatility": "STABLE"
},
"dimensions": [
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Build and Release Tooling",
"id": 89,
"rationale": "Tooling used to compile, sign, package, and automate iOS app builds. iOS engineers rely on this stack to produce reproducible release artifacts and manage build-time configuration.",
"slug": "build-and-release-tooling",
"source": "db"
},
"input_skill": "Xcode",
"llm_role": null,
"roles_from_db": [
{
"display_name": "Android Developer",
"id": 4,
"rationale": null,
"role_archetype": null,
"slug": "android-engineer",
"source": "db"
},
{
"display_name": "Flutter Developer",
"id": 74,
"rationale": null,
"role_archetype": "Engineering",
"slug": "flutter-developer",
"source": "db"
},
{
"display_name": "Hybrid Mobile Developer",
"id": 11,
"rationale": null,
"role_archetype": null,
"slug": "hybrid-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": "Native Mobile Build and Release Tooling",
"id": 272,
"rationale": "Tooling used to compile, sign, package, version, and automate release-ready builds for native mobile apps across iOS and Android. This cluster includes platform-specific build systems and release automation used to produce reproducible app artifacts and prepare internal or public release candidates.",
"slug": "native-mobile-build-and-release-tooling",
"source": "db"
},
"input_skill": "Xcode",
"llm_role": null,
"roles_from_db": [
{
"display_name": "Flutter Developer",
"id": 74,
"rationale": null,
"role_archetype": "Engineering",
"slug": "flutter-developer",
"source": "db"
},
{
"display_name": "Native Mobile Developer",
"id": 75,
"rationale": null,
"role_archetype": "Engineering",
"slug": "native-mobile-developer",
"source": "db"
},
{
"display_name": "React Native Developer",
"id": 73,
"rationale": null,
"role_archetype": "Engineering",
"slug": "react-native-developer",
"source": "db"
}
]
}
],
"input_skill": "Xcode",
"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": "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": [],
"canonical": null,
"dimensions": [],
"input_skill": "Core Animation",
"matched_via": null,
"new_alias_persisted": false,
"new_alias_text": null,
"new_skill_meta": {
"derived": {
"category": "Mobile Development",
"skill_nature": "CONCEPT",
"sub_category": "general",
"typical_lifespan": "MULTI_YEAR",
"version_strategy": "UNVERSIONED",
"volatility": "MEDIUM"
},
"enrichment": null,
"keep_log": [],
"locked_dimensions": [],
"merge_log": [],
"placed": null,
"relationships": null,
"skill_id": "core-animation",
"split_log": [],
"typed": null,
"warnings": []
},
"source_tag": "llm",
"was_in_llm_skills": true
},
{
"aliases_in_db": [
{
"alias_text": "Core Data",
"alias_type": "CANONICAL",
"id": 785,
"is_primary": true,
"match_strategy": "CASE_INSENSITIVE"
}
],
"canonical": {
"category_id": 5,
"display_name": "Core Data",
"id": 459,
"is_also_category": false,
"is_extractable": true,
"skill_nature": "FRAMEWORK",
"slug": "core-data",
"sub_category_id": 336,
"typical_lifespan": "EVERGREEN",
"volatility": "STABLE"
},
"dimensions": [
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Local Persistence and Offline Behavior",
"id": 85,
"rationale": "On-device storage used for caching, offline support, and durable client state. This cluster is coherent because iOS apps often need to preserve user progress and data when connectivity is limited.",
"slug": "local-persistence-and-offline-behavior",
"source": "db"
},
"input_skill": "Core Data",
"llm_role": null,
"roles_from_db": [
{
"display_name": "Android Developer",
"id": 4,
"rationale": null,
"role_archetype": null,
"slug": "android-engineer",
"source": "db"
},
{
"display_name": "Flutter Developer",
"id": 74,
"rationale": null,
"role_archetype": "Engineering",
"slug": "flutter-developer",
"source": "db"
},
{
"display_name": "Hybrid Mobile Developer",
"id": 11,
"rationale": null,
"role_archetype": null,
"slug": "hybrid-mobile-developer",
"source": "db"
},
{
"display_name": "Native Mobile Developer",
"id": 75,
"rationale": null,
"role_archetype": "Engineering",
"slug": "native-mobile-developer",
"source": "db"
},
{
"display_name": "React Native Developer",
"id": 73,
"rationale": null,
"role_archetype": "Engineering",
"slug": "react-native-developer",
"source": "db"
},
{
"display_name": "iOS Developer",
"id": 6,
"rationale": null,
"role_archetype": null,
"slug": "ios-engineer",
"source": "db"
}
]
}
],
"input_skill": "Core Data",
"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": "Core Graphics",
"matched_via": null,
"new_alias_persisted": false,
"new_alias_text": null,
"new_skill_meta": {
"derived": {
"category": "Mobile Development",
"skill_nature": "CONCEPT",
"sub_category": "general",
"typical_lifespan": "MULTI_YEAR",
"version_strategy": "UNVERSIONED",
"volatility": "MEDIUM"
},
"enrichment": null,
"keep_log": [],
"locked_dimensions": [],
"merge_log": [],
"placed": null,
"relationships": null,
"skill_id": "core-graphics",
"split_log": [],
"typed": null,
"warnings": []
},
"source_tag": "llm",
"was_in_llm_skills": true
},
{
"aliases_in_db": [],
"canonical": null,
"dimensions": [],
"input_skill": "Core Text",
"matched_via": null,
"new_alias_persisted": false,
"new_alias_text": null,
"new_skill_meta": {
"derived": {
"category": "Mobile Development",
"skill_nature": "CONCEPT",
"sub_category": "general",
"typical_lifespan": "MULTI_YEAR",
"version_strategy": "UNVERSIONED",
"volatility": "MEDIUM"
},
"enrichment": null,
"keep_log": [],
"locked_dimensions": [],
"merge_log": [],
"placed": null,
"relationships": null,
"skill_id": "core-text",
"split_log": [],
"typed": null,
"warnings": []
},
"source_tag": "llm",
"was_in_llm_skills": true
}
],
"unmatched_skills": [
"Android Studio",
"Android SDK",
"AppCode",
"CodeRunner",
"Core Animation",
"Core Graphics",
"Core Text"
]
}
API 3 — final-role-output
{
"chosen_role": {
"display_name": "Native Mobile Developer",
"id": 75,
"rationale": "Domain=Software Engineering; The JD is centered on full-cycle iOS and Android mobile app development with native SDKs, IDEs, and mobile UI/UX, which best matches Native Mobile Developer.",
"role_archetype": "Engineering",
"slug": "native-mobile-developer",
"source": "db"
},
"chosen_role_resolution": "in_db",
"final_input_skills": [
{
"skill": "Android Studio",
"tag": "new"
},
{
"skill": "Android SDK",
"tag": "new"
},
{
"skill": "Android",
"tag": "in_db"
},
{
"skill": "API",
"tag": "in_db"
},
{
"skill": "REST",
"tag": "in_db"
},
{
"skill": "MVC",
"tag": "in_db"
},
{
"skill": "MVVM",
"tag": "in_db"
},
{
"skill": "Viper",
"tag": "in_db"
},
{
"skill": "SwiftUI",
"tag": "in_db"
},
{
"skill": "Swift",
"tag": "in_db"
},
{
"skill": "AppCode",
"tag": "new"
},
{
"skill": "CodeRunner",
"tag": "new"
},
{
"skill": "Xcode",
"tag": "in_db"
},
{
"skill": "iOS",
"tag": "in_db"
},
{
"skill": "Core Animation",
"tag": "new"
},
{
"skill": "Core Data",
"tag": "in_db"
},
{
"skill": "Core Graphics",
"tag": "new"
},
{
"skill": "Core Text",
"tag": "new"
}
],
"llm_cost_api1_usd": null,
"llm_cost_api2_usd": null,
"llm_cost_api3_usd": null,
"llm_cost_total_usd": null,
"persistence": {
"items": [
{
"chosen_role_id": 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": "Android",
"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": 1595,
"skill_tag": "in_db",
"skipped_reason": null
},
{
"chosen_role_id": 75,
"dimension": {
"difficulty_hint": "well_known",
"display_name": "API Integration and Data Fetching",
"id": 127,
"rationale": "Client-side integration with backend endpoints and third-party services, including request shaping, response handling, and synchronization with UI state. This is central to frontend work because most screens depend on remote data.",
"slug": "api-integration-and-data-fetching",
"source": "db"
},
"dimension_id": 127,
"input_skill": "API",
"llm_role": null,
"matched_chosen_role": false,
"outcome_line": "Existing dimension (library) \u00b7 Role\u2194dimension skipped (dimension not under chosen role)",
"role_dimension_saved": false,
"roles_from_db": [
{
"display_name": "Angular Frontend Developer",
"id": 90,
"rationale": null,
"role_archetype": "Engineering",
"slug": "angular-frontend-developer",
"source": "db"
},
{
"display_name": "Frontend Developer",
"id": 7,
"rationale": null,
"role_archetype": null,
"slug": "frontend-engineer",
"source": "db"
},
{
"display_name": "Fullstack Developer",
"id": 15,
"rationale": null,
"role_archetype": null,
"slug": "full-stack-engineer",
"source": "db"
},
{
"display_name": "React Frontend Developer",
"id": 89,
"rationale": null,
"role_archetype": "Engineering",
"slug": "react-frontend-developer",
"source": "db"
},
{
"display_name": "Svelte Frontend Developer",
"id": 92,
"rationale": null,
"role_archetype": "Engineering",
"slug": "svelte-frontend-developer",
"source": "db"
},
{
"display_name": "Vue Frontend Developer",
"id": 91,
"rationale": null,
"role_archetype": "Engineering",
"slug": "vue-frontend-developer",
"source": "db"
},
{
"display_name": "Web Developer",
"id": 25,
"rationale": null,
"role_archetype": null,
"slug": "web-developer",
"source": "db"
}
],
"skill_dimension_saved": true,
"skill_id": 1568,
"skill_tag": "in_db",
"skipped_reason": null
},
{
"chosen_role_id": 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": "ASP.NET Core Web Frameworks",
"id": 363,
"rationale": "Server-side web frameworks and hosting models used to build HTTP APIs, middleware, filters, and request pipelines. This cluster is coherent because it defines how backend services receive, process, and return requests.",
"slug": "asp-net-core-web-frameworks",
"source": "db"
},
"dimension_id": 363,
"input_skill": "MVC",
"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"
}
],
"skill_dimension_saved": true,
"skill_id": 505,
"skill_tag": "in_db",
"skipped_reason": null
},
{
"chosen_role_id": 75,
"dimension": {
"difficulty_hint": "well_known",
"display_name": "App Architecture and Dependency Injection",
"id": 94,
"rationale": "Structural patterns used to organize iOS code into testable, maintainable feature modules and layers. iOS engineers use these patterns to separate UI, state, and service integration concerns.",
"slug": "app-architecture-and-dependency-injection",
"source": "db"
},
"dimension_id": 94,
"input_skill": "MVC",
"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": "Android Developer",
"id": 4,
"rationale": null,
"role_archetype": null,
"slug": "android-engineer",
"source": "db"
},
{
"display_name": "iOS Developer",
"id": 6,
"rationale": null,
"role_archetype": null,
"slug": "ios-engineer",
"source": "db"
}
],
"skill_dimension_saved": true,
"skill_id": 505,
"skill_tag": "in_db",
"skipped_reason": null
},
{
"chosen_role_id": 75,
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Application Architecture and Code Organization",
"id": 220,
"rationale": "Structural patterns for organizing product code into maintainable modules, layers, and feature boundaries. Full stack engineers need this to keep cross-layer feature work understandable as the product grows.",
"slug": "application-architecture-and-code-organization",
"source": "db"
},
"dimension_id": 220,
"input_skill": "MVC",
"llm_role": null,
"matched_chosen_role": false,
"outcome_line": "Existing dimension (library) \u00b7 Role\u2194dimension skipped (dimension not under chosen role)",
"role_dimension_saved": false,
"roles_from_db": [
{
"display_name": "Fullstack Developer",
"id": 15,
"rationale": null,
"role_archetype": null,
"slug": "full-stack-engineer",
"source": "db"
}
],
"skill_dimension_saved": true,
"skill_id": 505,
"skill_tag": "in_db",
"skipped_reason": null
},
{
"chosen_role_id": 75,
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Native Mobile App Architecture and Dependency Injection",
"id": 273,
"rationale": "Structural patterns for organizing native mobile application code into maintainable, testable modules, layers, and feature boundaries. This includes app architecture patterns such as MVVM, MVC, MVI, VIPER, and Clean Architecture; dependency injection frameworks and patterns such as Hilt, Dagger, and Koin; and code organization techniques such as modularization, feature modules, repository pattern, and use-case layering to separate UI, state, data, and platform concerns across a growing codebase.",
"slug": "native-mobile-app-architecture-and-dependency-injection",
"source": "db"
},
"dimension_id": 273,
"input_skill": "MVC",
"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": 505,
"skill_tag": "in_db",
"skipped_reason": null
},
{
"chosen_role_id": 75,
"dimension": {
"difficulty_hint": "well_known",
"display_name": "App Architecture and Dependency Injection",
"id": 94,
"rationale": "Structural patterns used to organize iOS code into testable, maintainable feature modules and layers. iOS engineers use these patterns to separate UI, state, and service integration concerns.",
"slug": "app-architecture-and-dependency-injection",
"source": "db"
},
"dimension_id": 94,
"input_skill": "MVVM",
"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": "Android Developer",
"id": 4,
"rationale": null,
"role_archetype": null,
"slug": "android-engineer",
"source": "db"
},
{
"display_name": "iOS Developer",
"id": 6,
"rationale": null,
"role_archetype": null,
"slug": "ios-engineer",
"source": "db"
}
],
"skill_dimension_saved": true,
"skill_id": 504,
"skill_tag": "in_db",
"skipped_reason": null
},
{
"chosen_role_id": 75,
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Mobile Architecture and Code Organization",
"id": 170,
"rationale": "Structural patterns used to organize shared mobile code into maintainable modules, layers, and feature boundaries. Senior hybrid developers often own these patterns to keep cross-platform code testable and adaptable to platform exceptions.",
"slug": "mobile-architecture-and-code-organization",
"source": "db"
},
"dimension_id": 170,
"input_skill": "MVVM",
"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": 504,
"skill_tag": "in_db",
"skipped_reason": null
},
{
"chosen_role_id": 75,
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Native Mobile App Architecture and Dependency Injection",
"id": 273,
"rationale": "Structural patterns for organizing native mobile application code into maintainable, testable modules, layers, and feature boundaries. This includes app architecture patterns such as MVVM, MVC, MVI, VIPER, and Clean Architecture; dependency injection frameworks and patterns such as Hilt, Dagger, and Koin; and code organization techniques such as modularization, feature modules, repository pattern, and use-case layering to separate UI, state, data, and platform concerns across a growing codebase.",
"slug": "native-mobile-app-architecture-and-dependency-injection",
"source": "db"
},
"dimension_id": 273,
"input_skill": "MVVM",
"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": 504,
"skill_tag": "in_db",
"skipped_reason": null
},
{
"chosen_role_id": 75,
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Native Mobile App Architecture and Dependency Injection",
"id": 273,
"rationale": "Structural patterns for organizing native mobile application code into maintainable, testable modules, layers, and feature boundaries. This includes app architecture patterns such as MVVM, MVC, MVI, VIPER, and Clean Architecture; dependency injection frameworks and patterns such as Hilt, Dagger, and Koin; and code organization techniques such as modularization, feature modules, repository pattern, and use-case layering to separate UI, state, data, and platform concerns across a growing codebase.",
"slug": "native-mobile-app-architecture-and-dependency-injection",
"source": "db"
},
"dimension_id": 273,
"input_skill": "Viper",
"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": 2056,
"skill_tag": "in_db",
"skipped_reason": null
},
{
"chosen_role_id": 75,
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Android UI Frameworks",
"id": 162,
"rationale": "Frameworks and component models used to build Android screens, layouts, and interactive UI behavior. This cluster covers both modern declarative UI and legacy view-based interfaces that Android engineers maintain in real products.",
"slug": "android-ui-frameworks",
"source": "db"
},
"dimension_id": 162,
"input_skill": "SwiftUI",
"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"
}
],
"skill_dimension_saved": true,
"skill_id": 444,
"skill_tag": "in_db",
"skipped_reason": null
},
{
"chosen_role_id": 75,
"dimension": {
"difficulty_hint": "well_known",
"display_name": "UIKit and SwiftUI",
"id": 82,
"rationale": "Frameworks and component models used to build screens, layouts, and interactive UI behavior on iOS. This cluster covers both declarative and imperative UI work needed to implement app flows.",
"slug": "uikit-and-swiftui",
"source": "db"
},
"dimension_id": 82,
"input_skill": "SwiftUI",
"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": 444,
"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": "Build and Release Tooling",
"id": 89,
"rationale": "Tooling used to compile, sign, package, and automate iOS app builds. iOS engineers rely on this stack to produce reproducible release artifacts and manage build-time configuration.",
"slug": "build-and-release-tooling",
"source": "db"
},
"dimension_id": 89,
"input_skill": "Xcode",
"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": "Android Developer",
"id": 4,
"rationale": null,
"role_archetype": null,
"slug": "android-engineer",
"source": "db"
},
{
"display_name": "Flutter Developer",
"id": 74,
"rationale": null,
"role_archetype": "Engineering",
"slug": "flutter-developer",
"source": "db"
},
{
"display_name": "Hybrid Mobile Developer",
"id": 11,
"rationale": null,
"role_archetype": null,
"slug": "hybrid-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": 479,
"skill_tag": "in_db",
"skipped_reason": null
},
{
"chosen_role_id": 75,
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Native Mobile Build and Release Tooling",
"id": 272,
"rationale": "Tooling used to compile, sign, package, version, and automate release-ready builds for native mobile apps across iOS and Android. This cluster includes platform-specific build systems and release automation used to produce reproducible app artifacts and prepare internal or public release candidates.",
"slug": "native-mobile-build-and-release-tooling",
"source": "db"
},
"dimension_id": 272,
"input_skill": "Xcode",
"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": "Flutter Developer",
"id": 74,
"rationale": null,
"role_archetype": "Engineering",
"slug": "flutter-developer",
"source": "db"
},
{
"display_name": "Native Mobile Developer",
"id": 75,
"rationale": null,
"role_archetype": "Engineering",
"slug": "native-mobile-developer",
"source": "db"
},
{
"display_name": "React Native Developer",
"id": 73,
"rationale": null,
"role_archetype": "Engineering",
"slug": "react-native-developer",
"source": "db"
}
],
"skill_dimension_saved": true,
"skill_id": 479,
"skill_tag": "in_db",
"skipped_reason": null
},
{
"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": "Local Persistence and Offline Behavior",
"id": 85,
"rationale": "On-device storage used for caching, offline support, and durable client state. This cluster is coherent because iOS apps often need to preserve user progress and data when connectivity is limited.",
"slug": "local-persistence-and-offline-behavior",
"source": "db"
},
"dimension_id": 85,
"input_skill": "Core Data",
"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": "Flutter Developer",
"id": 74,
"rationale": null,
"role_archetype": "Engineering",
"slug": "flutter-developer",
"source": "db"
},
{
"display_name": "Hybrid Mobile Developer",
"id": 11,
"rationale": null,
"role_archetype": null,
"slug": "hybrid-mobile-developer",
"source": "db"
},
{
"display_name": "Native Mobile Developer",
"id": 75,
"rationale": null,
"role_archetype": "Engineering",
"slug": "native-mobile-developer",
"source": "db"
},
{
"display_name": "React Native Developer",
"id": 73,
"rationale": null,
"role_archetype": "Engineering",
"slug": "react-native-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": 459,
"skill_tag": "in_db",
"skipped_reason": null
}
],
"new_skills_created": 0,
"role_dimension_saved": 0,
"skill_dimension_saved": 0,
"skipped": 0
},
"planner_output": null,
"run_id": "bb7c5611-af3b-49f4-9328-45612647f083"
}
LLM Calls
Every model call made for this run, in pipeline order. Click a card to see the model's response.
Loading…