Pipeline run
6ee16beb-ecd6-48e9-a377-342fc481493b
Client output enrichment
v2 Skill cluster · Nature of work · AI index · Tech stack maturity · Evidence · KRA descriptionvocab breakdown (legacy)
1 POST /skills/extract-from-jd
2 POST /skills/extract-details
3 POST /skills/final-role-output
iOS Engineer
slug: ios-engineer · id: 13 · source: db
The primary skills of iOS and Objective C align directly with the responsibilities of an iOS Engineer.
Resolution:
in_db
— role exists in library; skill↔dim and role↔dim links saved when applicable.
Job description
About the job 24X7Table.com provides Real time table reservation to diners at their favorite restaurants round the clock. It also provides CRM dashboard app for the restaurants by which they can track reservations and retain customers for future dealings. A well-funded innovative concept, we are now searching for people who can join us in our exciting journey of becoming one of the most preferred brands in promising food industry segment. We are looking for ambitious people who can contribute and be part of a young intellectual team. Expectations & Eligibility Criteria Designing, building, quality testing, and rolling out the 24X7Table iOS app. Work closely with 24x7Table Tech Team on Varied projects and timely delivery. Strong Development experience with iOS and demonstrated track record of developing and releasing IOS applications. Demonstrated experience in object oriented design and development of applications and systems. Must be capable to utilize all the opportunities provided in the Objective C for the robust IOS mobile application development. Strong grasp of algorithms, scalability and data structures. Passionate about Internet and mobile services and application technologies. Comfortable in a start-up culture based on respect, low hierarchy, high transparency and fast sprint work styles. Preferably should have 1-2 commercially deployed IOS applications.
Skills from this JD
Each row merges API 1 extraction, API 2 library match / v3 orchestration (dimensions + locked dims), and API 3 persistence tags.
Skill enrichment (orchestrator / LLM)
iOS is a mainstream mobile platform with high JD volume for Swift/iOS roles and strong Apple ecosystem support; it remains a common hiring-pipeline requirement rather than a niche or sunset tech.
Apple ·proprietary ·since 2007 (0.99)
iOS is a well-known mobile operating platform name and is typically unambiguous in JDs; it is unlikely to be confused with a different catalog skill.
Versioned iOS 18
{
"iOS": "18",
"iOS 1": "1",
"iOS 10": "10",
"iOS 11": "11",
"iOS 12": "12",
"iOS 13": "13",
"iOS 14": "14",
"iOS 15": "15",
"iOS 16": "16",
"iOS 17": "17",
"iOS 18": "18",
"iOS 2": "2",
"iOS 3": "3",
"iOS 4": "4",
"iOS 5": "5",
"iOS 6": "6",
"iOS 7": "7",
"iOS 8": "8",
"iOS 9": "9"
}
Platform ·mobile_operating_platform confidence 0.90
By the Platform vs Tool rule, iOS is a hosted mobile operating platform with APIs and managed services rather than software you run yourself.
- Category
- Platform
- Sub-category
- mobile_operating_platform
- Skill nature
- PLATFORM
- Volatility
- STABLE
- Typical lifespan
- EVERGREEN
- Version strategy
- SEPARATE_ENTITY
Dimensions (API 2 worklist)
-
Apple iOS UI Development (UIKit and SwiftUI) Proposed / LLM
Proposed / LLM dimension (no DB id yet)
Locked dimensions (v3 placement)
-
Apple iOS UI Development (UIKit and SwiftUI)
Pipeline tentative id
Native Apple UI development for building iOS screens, components, and interactive app experiences using UIKit and SwiftUI. Includes composing views, managing navigation and state, handling gestures and events, and using iOS-native patterns such as UIViewController, SwiftUI views, Auto Layout, tabs, and modals. iOS is included as the primary platform where these frameworks are applied.
API 3 link attempts (this skill)
| Dimension | Skill↔dim | Role↔dim | Outcome |
|---|---|---|---|
|
Apple iOS UI Development (UIKit and SwiftUI)
d_merge_01
|
✓ | — | New skill saved · Existing dimension (reconciliation merge) · Role↔dimension skipped (dimension not under chosen role) |
Skill enrichment (orchestrator / LLM)
Objective-C still appears in iOS/macOS legacy job postings, but most new Apple development JDs now prioritize Swift; Apple’s docs and ecosystem have shifted to Swift as the primary language.
NeXT ·other_open ·since 1984 (0.98)
Objective-C is a specific programming language name and is usually written distinctly in JDs. It is unlikely to be reasonably confused with another catalog skill in typical job descriptions.
Not versioned
Language ·programming_language confidence 0.99
Objective-C is a programming language used to write software, so it fits the Language type.
- Category
- Language
- Sub-category
- programming_language
- Skill nature
- LANGUAGE
- Volatility
- STABLE
- Typical lifespan
- EVERGREEN
- Version strategy
- NOT_APPLICABLE
Dimensions (API 2 worklist)
-
Apple Native UI Frameworks Proposed / LLM
Proposed / LLM dimension (no DB id yet)
-
App Security and Privacy Catalog dimension db id 135
Library dimension (catalog)
Roles linked in library: Android Engineer, iOS Engineer
-
App Security and Privacy Catalog dimension db id 135
Library dimension (catalog)
Roles linked in library: Android Engineer, iOS Engineer
Locked dimensions (v3 placement)
-
Apple Native UI Frameworks
Pipeline tentative id
Native Apple UI frameworks and related legacy Cocoa technologies used to build iOS and macOS app screens, components, and interactive experiences. Includes UIKit, SwiftUI, Cocoa Touch, AppKit interop, Objective-C-based Apple UI development, view controllers, delegates and protocols, Interface Builder, storyboards, and nibs.
-
App Security and Privacy
Reuses catalog slug
Security and privacy practices specific to native mobile apps and Apple platform expectations. Objective C can appear in this area when implementing secure iOS app behavior, but it is not the core focus of the language itself.
-
App Security and Privacy
Reuses catalog slug
Security and privacy practices specific to native mobile apps and Apple platform expectations. This cluster is coherent because iOS engineers handle sensitive data, permissions, and platform security controls in the client.
API 3 link attempts (this skill)
| Dimension | Skill↔dim | Role↔dim | Outcome |
|---|---|---|---|
|
Apple Native UI Frameworks
d_merge_01
|
✓ | — | New skill saved · Existing dimension (reconciliation merge) · Role↔dimension skipped (dimension not under chosen role) |
|
App Security and Privacy
app-security-and-privacy
|
✓ | ✓ | New skill saved · Existing dimension (library) · Role↔dimension saved |
Skill enrichment (orchestrator / LLM)
Algorithms are a standard hiring-pipeline topic in software JDs and interview loops across major employers; they’re foundational rather than niche or sunsetted.
(0.99)
“Algorithms” is a broad but standard CS concept; in JDs it usually refers to algorithmic knowledge and is not typically mistaken for a distinct catalog skill.
Not versioned
Concept ·algorithms confidence 0.97
Algorithms are a named knowledge unit about problem-solving procedures, so by the Concept vs Methodology rule they are a Concept rather than a Methodology or Architecture.
- Category
- Concept
- Sub-category
- algorithms
- Skill nature
- CONCEPT
- Volatility
- STABLE
- Typical lifespan
- EVERGREEN
- Version strategy
- NOT_APPLICABLE
Dimensions (API 2 worklist)
-
Version Control Systems Catalog dimension db id 365
Library dimension (catalog)
Locked dimensions (v3 placement)
-
Algorithm Design and Analysis
Pipeline tentative id
Covers the design, selection, and analysis of algorithms for solving computational problems efficiently. This includes reasoning about correctness, time and space complexity, and choosing appropriate algorithmic approaches for a task.
API 3 link attempts (this skill)
| Dimension | Skill↔dim | Role↔dim | Outcome |
|---|---|---|---|
|
Version Control Systems
d_init_01
|
✓ | — | New skill saved · Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role) |
Skill enrichment (orchestrator / LLM)
Core CS topic in nearly all software engineering JDs and interview pipelines; widely taught and used across languages/frameworks, with no sunset or replacement signal.
(0.99)
“Data structures” is a standard, specific CS concept and is unlikely to be confused with a different catalog skill in typical job descriptions.
Not versioned
Concept ·data_structures confidence 0.97
This is a named knowledge unit about how data is organized and manipulated, so by the Concept vs Methodology rule it is a Concept rather than a tool, format, or architecture.
- Category
- Concept
- Sub-category
- data_structures
- Skill nature
- CONCEPT
- Volatility
- STABLE
- Typical lifespan
- EVERGREEN
- Version strategy
- NOT_APPLICABLE
Dimensions (API 2 worklist)
-
Version Control Systems Catalog dimension db id 365
Library dimension (catalog)
Locked dimensions (v3 placement)
-
Core Data Structures
Pipeline tentative id
Fundamental abstract and concrete structures used to organize, store, and access data efficiently in software. This skill belongs here because it is the base knowledge for choosing representations and reasoning about time and space tradeoffs.
API 3 link attempts (this skill)
| Dimension | Skill↔dim | Role↔dim | Outcome |
|---|---|---|---|
|
Version Control Systems
d_init_01
|
✓ | — | New skill saved · Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role) |
All API 3 persistence rows
Same grid as the skill-extractor “Persistence items” table: one row per (skill × dimension) work item.
| Skill | Tag | Dimension | Skill↔dim | Role↔dim | Outcome | Notes |
|---|---|---|---|---|---|---|
| iOS | in_db |
Apple iOS UI Development (UIKit and SwiftUI)
d_merge_01
|
✓ | — | New skill saved · Existing dimension (reconciliation merge) · Role↔dimension skipped (dimension not under chosen role) | |
| Objective C | in_db |
Apple Native UI Frameworks
d_merge_01
|
✓ | — | New skill saved · Existing dimension (reconciliation merge) · Role↔dimension skipped (dimension not under chosen role) | |
| Objective C | in_db |
App Security and Privacy
app-security-and-privacy
|
✓ | ✓ | New skill saved · Existing dimension (library) · Role↔dimension saved | |
| algorithms | in_db |
Version Control Systems
d_init_01
|
✓ | — | New skill saved · Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role) | |
| data structures | in_db |
Version Control Systems
d_init_01
|
✓ | — | New skill saved · Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role) |
Library artifacts (this run)
| Kind | Detail | DB id |
|---|---|---|
| canonical_skill_added | iOS | 2624 |
| canonical_skill_added | Objective C | 2625 |
| canonical_skill_added | algorithms | 2626 |
| canonical_skill_added | data structures | 2627 |
| dimension_skill_link | iOS ↔ Apple iOS UI Development (UIKit and SwiftUI) | 125 |
| dimension_skill_link | Objective C ↔ Apple Native UI Frameworks | 125 |
| dimension_skill_link | Objective C ↔ App Security and Privacy | 135 |
| dimension_skill_link | algorithms ↔ Version Control Systems | 365 |
| dimension_skill_link | data structures ↔ Version Control Systems | 365 |
API 1 — extract-from-jd click to toggle
{
"final_skills": [
{
"is_primary": true,
"skill_name": "iOS"
},
{
"is_primary": true,
"skill_name": "Objective C"
},
{
"is_primary": false,
"skill_name": "algorithms"
},
{
"is_primary": false,
"skill_name": "data structures"
}
],
"run_id": null
}
API 2 — extract-details
{
"alias_matches": [],
"candidate_roles": [
{
"display_name": "Android Engineer",
"id": 15,
"rationale": null,
"role_archetype": null,
"slug": "android-engineer",
"source": "db"
},
{
"display_name": "iOS Engineer",
"id": 13,
"rationale": null,
"role_archetype": null,
"slug": "ios-engineer",
"source": "db"
}
],
"chosen_role": {
"display_name": "iOS Engineer",
"id": 13,
"rationale": "The primary skills of iOS and Objective C align directly with the responsibilities of an iOS Engineer.",
"role_archetype": null,
"slug": "ios-engineer",
"source": "db"
},
"dimensions": [
{
"dimension": {
"difficulty_hint": null,
"display_name": "Apple iOS UI Development (UIKit and SwiftUI)",
"id": null,
"rationale": "Native Apple UI development for building iOS screens, components, and interactive app experiences using UIKit and SwiftUI. Includes composing views, managing navigation and state, handling gestures and events, and using iOS-native patterns such as UIViewController, SwiftUI views, Auto Layout, tabs, and modals. iOS is included as the primary platform where these frameworks are applied.",
"slug": "d_merge_01",
"source": "llm"
},
"input_skill": "iOS",
"llm_role": null,
"roles_from_db": []
},
{
"dimension": {
"difficulty_hint": null,
"display_name": "Apple Native UI Frameworks",
"id": null,
"rationale": "Native Apple UI frameworks and related legacy Cocoa technologies used to build iOS and macOS app screens, components, and interactive experiences. Includes UIKit, SwiftUI, Cocoa Touch, AppKit interop, Objective-C-based Apple UI development, view controllers, delegates and protocols, Interface Builder, storyboards, and nibs.",
"slug": "d_merge_01",
"source": "llm"
},
"input_skill": "Objective C",
"llm_role": null,
"roles_from_db": []
},
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "App Security and Privacy",
"id": 135,
"rationale": "Security and privacy practices specific to native mobile apps and Apple platform expectations. This cluster is coherent because iOS engineers handle sensitive data, permissions, and platform security controls in the client.",
"slug": "app-security-and-privacy",
"source": "db"
},
"input_skill": "Objective C",
"llm_role": null,
"roles_from_db": [
{
"display_name": "Android Engineer",
"id": 15,
"rationale": null,
"role_archetype": null,
"slug": "android-engineer",
"source": "db"
},
{
"display_name": "iOS Engineer",
"id": 13,
"rationale": null,
"role_archetype": null,
"slug": "ios-engineer",
"source": "db"
}
]
},
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "App Security and Privacy",
"id": 135,
"rationale": "Security and privacy practices specific to native mobile apps and Apple platform expectations. This cluster is coherent because iOS engineers handle sensitive data, permissions, and platform security controls in the client.",
"slug": "app-security-and-privacy",
"source": "db"
},
"input_skill": "Objective C",
"llm_role": null,
"roles_from_db": [
{
"display_name": "Android Engineer",
"id": 15,
"rationale": null,
"role_archetype": null,
"slug": "android-engineer",
"source": "db"
},
{
"display_name": "iOS Engineer",
"id": 13,
"rationale": null,
"role_archetype": null,
"slug": "ios-engineer",
"source": "db"
}
]
},
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Version Control Systems",
"id": 365,
"rationale": "Tools and workflows for tracking source changes, branching, merging, and collaborating on code history. Git belongs here because it is the canonical distributed version control system used to manage revisions and coordinate team development.",
"slug": "d_init_01",
"source": "db"
},
"input_skill": "algorithms",
"llm_role": null,
"roles_from_db": []
},
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Version Control Systems",
"id": 365,
"rationale": "Tools and workflows for tracking source changes, branching, merging, and collaborating on code history. Git belongs here because it is the canonical distributed version control system used to manage revisions and coordinate team development.",
"slug": "d_init_01",
"source": "db"
},
"input_skill": "data structures",
"llm_role": null,
"roles_from_db": []
}
],
"input_final_skills": [
"iOS",
"Objective C",
"algorithms",
"data structures"
],
"input_llm_skills": [
"iOS",
"Objective C",
"algorithms",
"data structures"
],
"new_aliases_persisted": 0,
"run_id": "6ee16beb-ecd6-48e9-a377-342fc481493b",
"skills_detail": [
{
"aliases_in_db": [],
"canonical": null,
"dimensions": [
{
"dimension": {
"difficulty_hint": null,
"display_name": "Apple iOS UI Development (UIKit and SwiftUI)",
"id": null,
"rationale": "Native Apple UI development for building iOS screens, components, and interactive app experiences using UIKit and SwiftUI. Includes composing views, managing navigation and state, handling gestures and events, and using iOS-native patterns such as UIViewController, SwiftUI views, Auto Layout, tabs, and modals. iOS is included as the primary platform where these frameworks are applied.",
"slug": "d_merge_01",
"source": "llm"
},
"input_skill": "iOS",
"llm_role": null,
"roles_from_db": []
}
],
"input_skill": "iOS",
"matched_via": null,
"new_alias_persisted": false,
"new_alias_text": null,
"new_skill_meta": {
"derived": {
"category": "Platform",
"skill_nature": "PLATFORM",
"sub_category": "mobile_operating_platform",
"typical_lifespan": "EVERGREEN",
"version_strategy": "SEPARATE_ENTITY",
"volatility": "STABLE"
},
"enrichment": {
"ambiguity": {
"ambiguity_flag": false,
"confused_with": [],
"reasoning": "iOS is a well-known mobile operating platform name and is typically unambiguous in JDs; it is unlikely to be confused with a different catalog skill."
},
"context_keywords": {
"context_keywords": [
"Swift",
"Objective-C",
"Xcode",
"UIKit",
"SwiftUI",
"Cocoa Touch",
"Core Data",
"Combine",
"Auto Layout",
"Interface Builder",
"TestFlight",
"App Store Connect",
"Instruments",
"Carthage",
"CocoaPods"
]
},
"maturity": {
"confidence": 0.98,
"maturity": "well_known",
"reasoning": "iOS is a mainstream mobile platform with high JD volume for Swift/iOS roles and strong Apple ecosystem support; it remains a common hiring-pipeline requirement rather than a niche or sunset tech."
},
"skill_id": "ios",
"vendor_license": {
"confidence": 0.99,
"license": "proprietary",
"vendor": "Apple",
"year_introduced": 2007
},
"versioning": {
"current_version": "iOS 18",
"version_aliases": {
"iOS": "18",
"iOS 1": "1",
"iOS 10": "10",
"iOS 11": "11",
"iOS 12": "12",
"iOS 13": "13",
"iOS 14": "14",
"iOS 15": "15",
"iOS 16": "16",
"iOS 17": "17",
"iOS 18": "18",
"iOS 2": "2",
"iOS 3": "3",
"iOS 4": "4",
"iOS 5": "5",
"iOS 6": "6",
"iOS 7": "7",
"iOS 8": "8",
"iOS 9": "9"
},
"versioned": true
}
},
"keep_log": [],
"locked_dimensions": [
{
"description": "Native Apple UI development for building iOS screens, components, and interactive app experiences using UIKit and SwiftUI. Includes composing views, managing navigation and state, handling gestures and events, and using iOS-native patterns such as UIViewController, SwiftUI views, Auto Layout, tabs, and modals. iOS is included as the primary platform where these frameworks are applied.",
"exemplar_skills": [
"Apple iOS UI Development (UIKit and SwiftUI)"
],
"in_scope": "Skills, tools, and practices that belong under Apple iOS UI Development (UIKit and SwiftUI) for the target role, including items implied by the dimension rationale.",
"name": "Apple iOS UI Development (UIKit and SwiftUI)",
"out_of_scope": "Adjacent clusters explicitly not owned by Apple iOS UI Development (UIKit and SwiftUI), including unrelated platforms, roles, and skill families per library policy.",
"overlap_flags": [],
"tentative_id": "d_merge_01"
}
],
"merge_log": [
{
"a_dim_id": "uikit-and-swiftui",
"a_name": "UIKit and SwiftUI",
"a_role": "__skill_focal__",
"b_dim_id": "uikit-and-swiftui",
"b_name": "UIKit and SwiftUI",
"b_role": "iOS Engineer",
"into": "d_merge_01",
"into_name": "Apple iOS UI Development (UIKit and SwiftUI)",
"merged_from": [
"uikit-and-swiftui",
"uikit-and-swiftui"
],
"pair_kind": "cross_role",
"reasoning": "Both dims describe the same iOS UI implementation cluster. Dim A covers UIKit, SwiftUI, UIViewController, Auto Layout, navigation stacks, tabs, modals, and gesture handling for iOS screens. Dim B describes the same native Apple UI work, emphasizing composing views, handling events, and rendering state in iOS-native paradigms. The exemplar skills in A are fully contained in B\u2019s scope, so this is a true duplicate rather than a role-specific distinction.",
"similarity": 0.9317909586742327
}
],
"placed": {
"name": "iOS",
"placement_confidence": 0.92,
"primary_dimension": "d_merge_01",
"reasoning": "Deterministic JD placement: locked_dimensions has 1 dimension(s) from skill-driven dimension generation after reconciliation; primary_dimension is the first locked dim.",
"secondary_dimensions": [],
"skill_id": "ios"
},
"relationships": {
"child_skills": [],
"parent_skills": [],
"related_to": [
"javascript",
"python",
"go",
"solidity",
"bash",
"powershell",
"aws",
"ansible",
"wagmi",
"truffle"
],
"requires": [],
"skill_id": "ios",
"suppress_on_match": []
},
"skill_id": "ios",
"split_log": [],
"typed": {
"alternatives_considered": [
"Runtime: ruled out \u2014 iOS is not primarily an execution environment for code in the sense of Node.js or JVM.",
"Architecture: ruled out \u2014 iOS is a platform, not a system-shape pattern."
],
"confidence": 0.9,
"name": "iOS",
"reasoning": "By the Platform vs Tool rule, iOS is a hosted mobile operating platform with APIs and managed services rather than software you run yourself.",
"skill_id": "ios",
"subtype": "mobile_operating_platform",
"type": "Platform"
},
"warnings": [
"stage3_post_filter_dropped_catalog_only_locked_dims:40-\u003e1"
]
},
"source_tag": "llm",
"was_in_llm_skills": true
},
{
"aliases_in_db": [],
"canonical": null,
"dimensions": [
{
"dimension": {
"difficulty_hint": null,
"display_name": "Apple Native UI Frameworks",
"id": null,
"rationale": "Native Apple UI frameworks and related legacy Cocoa technologies used to build iOS and macOS app screens, components, and interactive experiences. Includes UIKit, SwiftUI, Cocoa Touch, AppKit interop, Objective-C-based Apple UI development, view controllers, delegates and protocols, Interface Builder, storyboards, and nibs.",
"slug": "d_merge_01",
"source": "llm"
},
"input_skill": "Objective C",
"llm_role": null,
"roles_from_db": []
},
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "App Security and Privacy",
"id": 135,
"rationale": "Security and privacy practices specific to native mobile apps and Apple platform expectations. This cluster is coherent because iOS engineers handle sensitive data, permissions, and platform security controls in the client.",
"slug": "app-security-and-privacy",
"source": "db"
},
"input_skill": "Objective C",
"llm_role": null,
"roles_from_db": [
{
"display_name": "Android Engineer",
"id": 15,
"rationale": null,
"role_archetype": null,
"slug": "android-engineer",
"source": "db"
},
{
"display_name": "iOS Engineer",
"id": 13,
"rationale": null,
"role_archetype": null,
"slug": "ios-engineer",
"source": "db"
}
]
},
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "App Security and Privacy",
"id": 135,
"rationale": "Security and privacy practices specific to native mobile apps and Apple platform expectations. This cluster is coherent because iOS engineers handle sensitive data, permissions, and platform security controls in the client.",
"slug": "app-security-and-privacy",
"source": "db"
},
"input_skill": "Objective C",
"llm_role": null,
"roles_from_db": [
{
"display_name": "Android Engineer",
"id": 15,
"rationale": null,
"role_archetype": null,
"slug": "android-engineer",
"source": "db"
},
{
"display_name": "iOS Engineer",
"id": 13,
"rationale": null,
"role_archetype": null,
"slug": "ios-engineer",
"source": "db"
}
]
}
],
"input_skill": "Objective C",
"matched_via": null,
"new_alias_persisted": false,
"new_alias_text": null,
"new_skill_meta": {
"derived": {
"category": "Language",
"skill_nature": "LANGUAGE",
"sub_category": "programming_language",
"typical_lifespan": "EVERGREEN",
"version_strategy": "NOT_APPLICABLE",
"volatility": "STABLE"
},
"enrichment": {
"ambiguity": {
"ambiguity_flag": false,
"confused_with": [],
"reasoning": "Objective-C is a specific programming language name and is usually written distinctly in JDs. It is unlikely to be reasonably confused with another catalog skill in typical job descriptions."
},
"context_keywords": {
"context_keywords": [
"Cocoa",
"Cocoa Touch",
"Xcode",
"UIKit",
"Foundation",
"AppKit",
"ARC",
"NSLog",
"IBOutlet",
"IBAction",
"delegates",
"protocols",
"categories",
"selectors",
"iOS",
"macOS"
]
},
"maturity": {
"confidence": 0.91,
"maturity": "niche",
"reasoning": "Objective-C still appears in iOS/macOS legacy job postings, but most new Apple development JDs now prioritize Swift; Apple\u2019s docs and ecosystem have shifted to Swift as the primary language."
},
"skill_id": "objective-c",
"vendor_license": {
"confidence": 0.98,
"license": "other_open",
"vendor": "NeXT",
"year_introduced": 1984
},
"versioning": {
"current_version": null,
"version_aliases": {},
"versioned": false
}
},
"keep_log": [
{
"a_dim_id": "app-security-and-privacy",
"a_name": "App Security and Privacy",
"a_role": "__skill_focal__",
"b_dim_id": "app-security-and-privacy",
"b_name": "App Security and Privacy",
"b_role": "Android Engineer",
"pair_kind": "cross_role",
"reasoning": "Same name, but cross-role and platform-specific. Dim A is clearly Apple/iOS-focused: Objective C, Keychain Services, iOS sandboxing, certificate pinning, Apple security APIs. Dim B is labeled Android Engineer, so it should map to Android security/privacy concerns, not Apple platform expectations. The overlap is wording, not the skill cluster.",
"similarity": 0.8460670898923773
}
],
"locked_dimensions": [
{
"description": "Native Apple UI frameworks and related legacy Cocoa technologies used to build iOS and macOS app screens, components, and interactive experiences. Includes UIKit, SwiftUI, Cocoa Touch, AppKit interop, Objective-C-based Apple UI development, view controllers, delegates and protocols, Interface Builder, storyboards, and nibs.",
"exemplar_skills": [
"Apple Native UI Frameworks"
],
"in_scope": "Skills, tools, and practices that belong under Apple Native UI Frameworks for the target role, including items implied by the dimension rationale.",
"name": "Apple Native UI Frameworks",
"out_of_scope": "Adjacent clusters explicitly not owned by Apple Native UI Frameworks, including unrelated platforms, roles, and skill families per library policy.",
"overlap_flags": [],
"tentative_id": "d_merge_01"
},
{
"description": "Security and privacy practices specific to native mobile apps and Apple platform expectations. Objective C can appear in this area when implementing secure iOS app behavior, but it is not the core focus of the language itself.",
"exemplar_skills": [
"Objective C",
"Keychain Services",
"iOS sandboxing",
"privacy permissions",
"certificate pinning",
"secure networking",
"Apple security APIs"
],
"in_scope": "Objective C, keychain access, secure storage, privacy permissions, app sandboxing, certificate handling, secure networking patterns, Apple platform security APIs",
"name": "App Security and Privacy",
"out_of_scope": "General UI construction, navigation flows, state management, backend service integration, non-mobile security operations",
"overlap_flags": [
{
"reason": "Objective C is frequently used in iOS app code that also implements UI and app behavior, so security-related usage can overlap with general app development.",
"with_dim_id": "uikit-and-swiftui",
"with_dim_name": null,
"with_role": "iOS Engineer"
}
],
"tentative_id": "app-security-and-privacy"
},
{
"description": "Security and privacy practices specific to native mobile apps and Apple platform expectations. This cluster is coherent because iOS engineers handle sensitive data, permissions, and platform security controls in the client.",
"exemplar_skills": [
"App Security and Privacy"
],
"in_scope": "Skills, tools, and practices that belong under App Security and Privacy for the target role, including items implied by the dimension rationale.",
"name": "App Security and Privacy",
"out_of_scope": "Adjacent clusters explicitly not owned by App Security and Privacy, including unrelated platforms, roles, and skill families per library policy.",
"overlap_flags": [],
"tentative_id": "app-security-and-privacy"
}
],
"merge_log": [
{
"a_dim_id": "uikit-and-swiftui",
"a_name": "UIKit and SwiftUI",
"a_role": "__skill_focal__",
"b_dim_id": "uikit-and-swiftui",
"b_name": "UIKit and SwiftUI",
"b_role": "iOS Engineer",
"into": "d_merge_01",
"into_name": "Apple Native UI Frameworks",
"merged_from": [
"uikit-and-swiftui",
"uikit-and-swiftui"
],
"pair_kind": "cross_role",
"reasoning": "Both dims describe the same Apple-native UI framework cluster. A centers on UIKit/AppKit-era implementation details (Objective C, UIKit view controllers, Cocoa Touch, Interface Builder, storyboards, nibs), while B describes the same work more generally as building screens, components, and interactive app experiences in iOS-native paradigms. The exemplar skills in A are a direct subset of B\u2019s scope, and B adds no distinct skill cluster beyond the same native UI framework work.",
"similarity": 0.8950647144893952
}
],
"placed": {
"name": "Objective C",
"placement_confidence": 0.92,
"primary_dimension": "d_merge_01",
"reasoning": "Deterministic JD placement: locked_dimensions has 3 dimension(s) from skill-driven dimension generation after reconciliation; primary_dimension is the first locked dim.",
"secondary_dimensions": [
"app-security-and-privacy"
],
"skill_id": "objective-c"
},
"relationships": {
"child_skills": [],
"parent_skills": [],
"related_to": [
"javascript",
"python",
"go",
"r",
"bash",
"powershell",
"solidity"
],
"requires": [],
"skill_id": "objective-c",
"suppress_on_match": []
},
"skill_id": "objective-c",
"split_log": [],
"typed": {
"alternatives_considered": [],
"confidence": 0.99,
"name": "Objective C",
"reasoning": "Objective-C is a programming language used to write software, so it fits the Language type.",
"skill_id": "objective-c",
"subtype": "programming_language",
"type": "Language"
},
"warnings": [
"stage3_post_filter_dropped_catalog_only_locked_dims:41-\u003e3"
]
},
"source_tag": "llm",
"was_in_llm_skills": true
},
{
"aliases_in_db": [],
"canonical": null,
"dimensions": [
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Version Control Systems",
"id": 365,
"rationale": "Tools and workflows for tracking source changes, branching, merging, and collaborating on code history. Git belongs here because it is the canonical distributed version control system used to manage revisions and coordinate team development.",
"slug": "d_init_01",
"source": "db"
},
"input_skill": "algorithms",
"llm_role": null,
"roles_from_db": []
}
],
"input_skill": "algorithms",
"matched_via": null,
"new_alias_persisted": false,
"new_alias_text": null,
"new_skill_meta": {
"derived": {
"category": "Concept",
"skill_nature": "CONCEPT",
"sub_category": "algorithms",
"typical_lifespan": "EVERGREEN",
"version_strategy": "NOT_APPLICABLE",
"volatility": "STABLE"
},
"enrichment": {
"ambiguity": {
"ambiguity_flag": false,
"confused_with": [],
"reasoning": "\u201cAlgorithms\u201d is a broad but standard CS concept; in JDs it usually refers to algorithmic knowledge and is not typically mistaken for a distinct catalog skill."
},
"context_keywords": {
"context_keywords": [
"Big-O",
"time complexity",
"space complexity",
"dynamic programming",
"greedy",
"divide and conquer",
"recursion",
"graph traversal",
"sorting",
"searching",
"data structures",
"hash table",
"binary search",
"backtracking",
"memoization"
]
},
"maturity": {
"confidence": 0.97,
"maturity": "well_known",
"reasoning": "Algorithms are a standard hiring-pipeline topic in software JDs and interview loops across major employers; they\u2019re foundational rather than niche or sunsetted."
},
"skill_id": "algorithms",
"vendor_license": {
"confidence": 0.99,
"license": null,
"vendor": null,
"year_introduced": null
},
"versioning": {
"current_version": null,
"version_aliases": {},
"versioned": false
}
},
"keep_log": [],
"locked_dimensions": [
{
"description": "Covers the design, selection, and analysis of algorithms for solving computational problems efficiently. This includes reasoning about correctness, time and space complexity, and choosing appropriate algorithmic approaches for a task.",
"exemplar_skills": [
"algorithms",
"algorithm design",
"algorithm analysis",
"time complexity",
"space complexity",
"dynamic programming",
"greedy algorithms",
"graph algorithms"
],
"in_scope": "algorithms, algorithm design, algorithm analysis, correctness proofs, time complexity, space complexity, greedy algorithms, divide and conquer, dynamic programming, graph algorithms, sorting, searching, recursion, amortized analysis",
"name": "Algorithm Design and Analysis",
"out_of_scope": "Data structures such as trees, heaps, hash tables, and linked lists when the focus is storage organization rather than algorithmic strategy; system performance tuning and capacity planning; application-level UI or API implementation details.",
"overlap_flags": [
{
"reason": "Algorithm implementation often uses analytical languages, but this dimension is about the algorithmic method rather than the programming surface.",
"with_dim_id": "analytical-programming-languages",
"with_dim_name": null,
"with_role": "Data Analyst, Data Scientist"
},
{
"reason": "Problem framing can precede algorithm choice, but this dimension focuses on the concrete computational solution once the problem is defined.",
"with_dim_id": "domain-problem-framing",
"with_dim_name": null,
"with_role": "Data Scientist"
}
],
"tentative_id": "d_init_01"
}
],
"merge_log": [],
"placed": {
"name": "algorithms",
"placement_confidence": 0.92,
"primary_dimension": "d_init_01",
"reasoning": "Deterministic JD placement: locked_dimensions has 1 dimension(s) from skill-driven dimension generation after reconciliation; primary_dimension is the first locked dim.",
"secondary_dimensions": [],
"skill_id": "algorithms"
},
"relationships": {
"child_skills": [],
"parent_skills": [],
"related_to": [
"duplicate-detection",
"correlation-analysis",
"anomaly-investigation",
"root-cause-analysis",
"segment-analysis",
"scorecards",
"subgraphs",
"proxy-patterns",
"pandas",
"javascript"
],
"requires": [],
"skill_id": "algorithms",
"suppress_on_match": []
},
"skill_id": "algorithms",
"split_log": [],
"typed": {
"alternatives_considered": [
"Methodology: ruled out \u2014 algorithms describe knowledge and techniques, not an operating process or way of working.",
"Architecture: ruled out \u2014 algorithms are not a system-shape pattern."
],
"confidence": 0.97,
"name": "algorithms",
"reasoning": "Algorithms are a named knowledge unit about problem-solving procedures, so by the Concept vs Methodology rule they are a Concept rather than a Methodology or Architecture.",
"skill_id": "algorithms",
"subtype": "algorithms",
"type": "Concept"
},
"warnings": []
},
"source_tag": "llm",
"was_in_llm_skills": true
},
{
"aliases_in_db": [],
"canonical": null,
"dimensions": [
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Version Control Systems",
"id": 365,
"rationale": "Tools and workflows for tracking source changes, branching, merging, and collaborating on code history. Git belongs here because it is the canonical distributed version control system used to manage revisions and coordinate team development.",
"slug": "d_init_01",
"source": "db"
},
"input_skill": "data structures",
"llm_role": null,
"roles_from_db": []
}
],
"input_skill": "data structures",
"matched_via": null,
"new_alias_persisted": false,
"new_alias_text": null,
"new_skill_meta": {
"derived": {
"category": "Concept",
"skill_nature": "CONCEPT",
"sub_category": "data_structures",
"typical_lifespan": "EVERGREEN",
"version_strategy": "NOT_APPLICABLE",
"volatility": "STABLE"
},
"enrichment": {
"ambiguity": {
"ambiguity_flag": false,
"confused_with": [],
"reasoning": "\u201cData structures\u201d is a standard, specific CS concept and is unlikely to be confused with a different catalog skill in typical job descriptions."
},
"context_keywords": {
"context_keywords": [
"arrays",
"linked lists",
"stacks",
"queues",
"trees",
"graphs",
"hash tables",
"heaps",
"tries",
"binary search trees",
"balanced trees",
"adjacency list",
"recursion",
"dynamic programming",
"Big-O"
]
},
"maturity": {
"confidence": 0.98,
"maturity": "well_known",
"reasoning": "Core CS topic in nearly all software engineering JDs and interview pipelines; widely taught and used across languages/frameworks, with no sunset or replacement signal."
},
"skill_id": "data-structures",
"vendor_license": {
"confidence": 0.99,
"license": null,
"vendor": null,
"year_introduced": null
},
"versioning": {
"current_version": null,
"version_aliases": {},
"versioned": false
}
},
"keep_log": [],
"locked_dimensions": [
{
"description": "Fundamental abstract and concrete structures used to organize, store, and access data efficiently in software. This skill belongs here because it is the base knowledge for choosing representations and reasoning about time and space tradeoffs.",
"exemplar_skills": [
"data structures",
"arrays",
"linked lists",
"stacks",
"queues",
"hash tables",
"trees",
"graphs",
"heaps"
],
"in_scope": "data structures, arrays, linked lists, stacks, queues, hash tables, sets, trees, heaps, graphs, tries, maps, dictionaries, binary search trees, balanced trees, adjacency lists",
"name": "Core Data Structures",
"out_of_scope": "Algorithms and problem solving, database schema design, distributed storage systems, UI state management, language syntax and control flow",
"overlap_flags": [
{
"reason": "Some languages teach data structures as part of programming fundamentals, but this dimension is about the structures themselves rather than the language used to implement them.",
"with_dim_id": "analytical-programming-languages",
"with_dim_name": null,
"with_role": "Data Analyst, Data Scientist"
}
],
"tentative_id": "d_init_01"
}
],
"merge_log": [],
"placed": {
"name": "data structures",
"placement_confidence": 0.92,
"primary_dimension": "d_init_01",
"reasoning": "Deterministic JD placement: locked_dimensions has 1 dimension(s) from skill-driven dimension generation after reconciliation; primary_dimension is the first locked dim.",
"secondary_dimensions": [],
"skill_id": "data-structures"
},
"relationships": {
"child_skills": [],
"parent_skills": [],
"related_to": [
"storage-layout",
"storage-layout-compatibility",
"subgraphs",
"segment-analysis",
"summary-statistics",
"metadata-json",
"state-transitions",
"derived-views",
"missing-data-analysis",
"capacity-forecasting"
],
"requires": [],
"skill_id": "data-structures",
"suppress_on_match": []
},
"skill_id": "data-structures",
"split_log": [],
"typed": {
"alternatives_considered": [],
"confidence": 0.97,
"name": "data structures",
"reasoning": "This is a named knowledge unit about how data is organized and manipulated, so by the Concept vs Methodology rule it is a Concept rather than a tool, format, or architecture.",
"skill_id": "data-structures",
"subtype": "data_structures",
"type": "Concept"
},
"warnings": []
},
"source_tag": "llm",
"was_in_llm_skills": true
}
],
"unmatched_skills": [
"iOS",
"Objective C",
"algorithms",
"data structures"
]
}
API 3 — final-role-output
{
"chosen_role": {
"display_name": "iOS Engineer",
"id": 13,
"rationale": "The primary skills of iOS and Objective C align directly with the responsibilities of an iOS Engineer.",
"role_archetype": null,
"slug": "ios-engineer",
"source": "db"
},
"chosen_role_resolution": "in_db",
"final_input_skills": [
{
"skill": "iOS",
"tag": "new"
},
{
"skill": "Objective C",
"tag": "new"
},
{
"skill": "algorithms",
"tag": "new"
},
{
"skill": "data structures",
"tag": "new"
}
],
"persistence": {
"items": [
{
"chosen_role_id": 13,
"dimension": {
"difficulty_hint": null,
"display_name": "Apple iOS UI Development (UIKit and SwiftUI)",
"id": null,
"rationale": "Native Apple UI development for building iOS screens, components, and interactive app experiences using UIKit and SwiftUI. Includes composing views, managing navigation and state, handling gestures and events, and using iOS-native patterns such as UIViewController, SwiftUI views, Auto Layout, tabs, and modals. iOS is included as the primary platform where these frameworks are applied.",
"slug": "d_merge_01",
"source": "llm"
},
"dimension_id": 125,
"input_skill": "iOS",
"llm_role": null,
"matched_chosen_role": false,
"outcome_line": "New skill saved \u00b7 Existing dimension (reconciliation merge) \u00b7 Role\u2194dimension skipped (dimension not under chosen role)",
"role_dimension_saved": false,
"roles_from_db": [],
"skill_dimension_saved": true,
"skill_id": 2624,
"skill_tag": "in_db",
"skipped_reason": null
},
{
"chosen_role_id": 13,
"dimension": {
"difficulty_hint": null,
"display_name": "Apple Native UI Frameworks",
"id": null,
"rationale": "Native Apple UI frameworks and related legacy Cocoa technologies used to build iOS and macOS app screens, components, and interactive experiences. Includes UIKit, SwiftUI, Cocoa Touch, AppKit interop, Objective-C-based Apple UI development, view controllers, delegates and protocols, Interface Builder, storyboards, and nibs.",
"slug": "d_merge_01",
"source": "llm"
},
"dimension_id": 125,
"input_skill": "Objective C",
"llm_role": null,
"matched_chosen_role": false,
"outcome_line": "New skill saved \u00b7 Existing dimension (reconciliation merge) \u00b7 Role\u2194dimension skipped (dimension not under chosen role)",
"role_dimension_saved": false,
"roles_from_db": [],
"skill_dimension_saved": true,
"skill_id": 2625,
"skill_tag": "in_db",
"skipped_reason": null
},
{
"chosen_role_id": 13,
"dimension": {
"difficulty_hint": "well_known",
"display_name": "App Security and Privacy",
"id": 135,
"rationale": "Security and privacy practices specific to native mobile apps and Apple platform expectations. This cluster is coherent because iOS engineers handle sensitive data, permissions, and platform security controls in the client.",
"slug": "app-security-and-privacy",
"source": "db"
},
"dimension_id": 135,
"input_skill": "Objective C",
"llm_role": null,
"matched_chosen_role": true,
"outcome_line": "New skill saved \u00b7 Existing dimension (library) \u00b7 Role\u2194dimension saved",
"role_dimension_saved": true,
"roles_from_db": [
{
"display_name": "Android Engineer",
"id": 15,
"rationale": null,
"role_archetype": null,
"slug": "android-engineer",
"source": "db"
},
{
"display_name": "iOS Engineer",
"id": 13,
"rationale": null,
"role_archetype": null,
"slug": "ios-engineer",
"source": "db"
}
],
"skill_dimension_saved": true,
"skill_id": 2625,
"skill_tag": "in_db",
"skipped_reason": null
},
{
"chosen_role_id": 13,
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Version Control Systems",
"id": 365,
"rationale": "Tools and workflows for tracking source changes, branching, merging, and collaborating on code history. Git belongs here because it is the canonical distributed version control system used to manage revisions and coordinate team development.",
"slug": "d_init_01",
"source": "db"
},
"dimension_id": 365,
"input_skill": "algorithms",
"llm_role": null,
"matched_chosen_role": false,
"outcome_line": "New skill saved \u00b7 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": 2626,
"skill_tag": "in_db",
"skipped_reason": null
},
{
"chosen_role_id": 13,
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Version Control Systems",
"id": 365,
"rationale": "Tools and workflows for tracking source changes, branching, merging, and collaborating on code history. Git belongs here because it is the canonical distributed version control system used to manage revisions and coordinate team development.",
"slug": "d_init_01",
"source": "db"
},
"dimension_id": 365,
"input_skill": "data structures",
"llm_role": null,
"matched_chosen_role": false,
"outcome_line": "New skill saved \u00b7 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": 2627,
"skill_tag": "in_db",
"skipped_reason": null
}
],
"new_skills_created": 4,
"role_dimension_saved": 0,
"skill_dimension_saved": 5,
"skipped": 0
},
"planner_output": null,
"run_id": "6ee16beb-ecd6-48e9-a377-342fc481493b"
}
LLM Calls
Every model call made for this run, in pipeline order. Click a card to see the model's response.