Pipeline run
15713f4f-e8c3-4853-8537-7ce6e2e99ad5
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
No chosen role stored for this run.
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 iOS engineers and Swift/Objective-C roles across consumer and enterprise apps; Apple continues active platform support and releases.
Apple ·proprietary ·since 2007 (0.99)
iOS is a well-known mobile operating platform with a specific JD context. It is unlikely to be reasonably confused with another catalog skill in typical job descriptions.
Versioned iOS 18
{
"iOS 1.x": "iOS 1",
"iOS 10.x": "iOS 10",
"iOS 11.x": "iOS 11",
"iOS 12.x": "iOS 12",
"iOS 13.x": "iOS 13",
"iOS 14.x": "iOS 14",
"iOS 15.x": "iOS 15",
"iOS 16.x": "iOS 16",
"iOS 17.x": "iOS 17",
"iOS 18.x": "iOS 18",
"iOS 2.x": "iOS 2",
"iOS 3.x": "iOS 3",
"iOS 4.x": "iOS 4",
"iOS 5.x": "iOS 5",
"iOS 6.x": "iOS 6",
"iOS 7.x": "iOS 7",
"iOS 8.x": "iOS 8",
"iOS 9.x": "iOS 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 Native UI Frameworks (UIKit and SwiftUI) Proposed / LLM
Proposed / LLM dimension (no DB id yet)
Locked dimensions (v3 placement)
-
Apple Native UI Frameworks (UIKit and SwiftUI)
Pipeline tentative id
Native Apple UI frameworks and iOS-native UI patterns used to build screens, components, layouts, navigation, gestures, animations, and interactive app experiences for iPhone and iPad apps. Includes UIKit, SwiftUI, view controllers, views, Auto Layout, reusable components, and event-driven rendering of app state in native mobile interfaces.
Skill enrichment (orchestrator / LLM)
Still appears in iOS/macOS legacy job postings, but most new Apple development JDs now prefer Swift; GitHub activity is far lower than modern mobile languages.
NeXT ·other_open ·since 1984 (0.98)
Objective-C is a specific programming language name and is usually written distinctly in JDs. It is not commonly confused with other catalog skills 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 (UIKit and SwiftUI) Proposed / LLM
Proposed / LLM dimension (no DB id yet)
-
Mobile App Security and Privacy Proposed / LLM
Proposed / LLM dimension (no DB id yet)
Locked dimensions (v3 placement)
-
Apple Native UI Frameworks (UIKit and SwiftUI)
Pipeline tentative id
Native Apple UI frameworks and related implementation skills used to build iOS and macOS app screens, components, and interactive experiences. Includes UIKit and SwiftUI, Objective-C legacy UI code, view controllers, views, table and collection views, event handling, state-driven rendering, and SwiftUI/UIKit interoperability. Excludes backend APIs, database access, app security, and other non-UI platform services.
-
Mobile App Security and Privacy
Pipeline tentative id
Security and privacy practices for native mobile applications, including secure storage and credential handling, platform security controls, app transport/network security, privacy permissions, and hardening against device compromise or jailbreak/root risks. Covers secure client-side handling of sensitive data across mobile platforms.
Skill enrichment (orchestrator / LLM)
Algorithms are a core CS hiring staple: they appear in most software engineering JDs and interview loops, and are foundational in university curricula and coding platforms like LeetCode.
(0.99)
“Algorithms” is a broad but standard CS concept; in JDs it usually refers to algorithmic knowledge or algorithm design, not a distinct catalog skill with a competing meaning.
Not versioned
Concept ·algorithms confidence 0.98
Algorithms are a named knowledge unit about problem-solving procedures, so by the Concept vs Methodology rule they are a Concept rather than a tool or methodology.
- 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)
-
Algorithms and Problem Solving
Pipeline tentative id
Core algorithmic thinking for designing, analyzing, and implementing efficient solutions to computational problems. This covers selecting appropriate data structures, reasoning about complexity, and applying standard algorithmic techniques.
Skill enrichment (orchestrator / LLM)
Core CS topic in nearly all software engineering JDs and interview loops; 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, language, 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)
-
Data Structures
Pipeline tentative id
Core abstract and concrete ways to organize and access data in software. This belongs here because the skill refers to fundamental representations used across algorithms, APIs, and system design.
Library artifacts (this run)
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": [],
"chosen_role": null,
"dimensions": [
{
"dimension": {
"difficulty_hint": null,
"display_name": "Apple Native UI Frameworks (UIKit and SwiftUI)",
"id": null,
"rationale": "Native Apple UI frameworks and iOS-native UI patterns used to build screens, components, layouts, navigation, gestures, animations, and interactive app experiences for iPhone and iPad apps. Includes UIKit, SwiftUI, view controllers, views, Auto Layout, reusable components, and event-driven rendering of app state in native mobile interfaces.",
"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 (UIKit and SwiftUI)",
"id": null,
"rationale": "Native Apple UI frameworks and related implementation skills used to build iOS and macOS app screens, components, and interactive experiences. Includes UIKit and SwiftUI, Objective-C legacy UI code, view controllers, views, table and collection views, event handling, state-driven rendering, and SwiftUI/UIKit interoperability. Excludes backend APIs, database access, app security, and other non-UI platform services.",
"slug": "d_merge_01",
"source": "llm"
},
"input_skill": "Objective C",
"llm_role": null,
"roles_from_db": []
},
{
"dimension": {
"difficulty_hint": null,
"display_name": "Mobile App Security and Privacy",
"id": null,
"rationale": "Security and privacy practices for native mobile applications, including secure storage and credential handling, platform security controls, app transport/network security, privacy permissions, and hardening against device compromise or jailbreak/root risks. Covers secure client-side handling of sensitive data across mobile platforms.",
"slug": "d_merge_02",
"source": "llm"
},
"input_skill": "Objective C",
"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": "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": "15713f4f-e8c3-4853-8537-7ce6e2e99ad5",
"skills_detail": [
{
"aliases_in_db": [],
"canonical": null,
"dimensions": [
{
"dimension": {
"difficulty_hint": null,
"display_name": "Apple Native UI Frameworks (UIKit and SwiftUI)",
"id": null,
"rationale": "Native Apple UI frameworks and iOS-native UI patterns used to build screens, components, layouts, navigation, gestures, animations, and interactive app experiences for iPhone and iPad apps. Includes UIKit, SwiftUI, view controllers, views, Auto Layout, reusable components, and event-driven rendering of app state in native mobile interfaces.",
"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 with a specific JD context. It is unlikely to be reasonably confused with another catalog skill in typical job descriptions."
},
"context_keywords": {
"context_keywords": [
"Swift",
"Objective-C",
"Xcode",
"UIKit",
"SwiftUI",
"Cocoa Touch",
"Core Data",
"Auto Layout",
"Interface Builder",
"TestFlight",
"App Store Connect",
"Instruments",
"Carthage",
"CocoaPods",
"Combine"
]
},
"maturity": {
"confidence": 0.98,
"maturity": "well_known",
"reasoning": "iOS is a mainstream mobile platform with high JD volume for iOS engineers and Swift/Objective-C roles across consumer and enterprise apps; Apple continues active platform support and releases."
},
"skill_id": "ios",
"vendor_license": {
"confidence": 0.99,
"license": "proprietary",
"vendor": "Apple",
"year_introduced": 2007
},
"versioning": {
"current_version": "iOS 18",
"version_aliases": {
"iOS 1.x": "iOS 1",
"iOS 10.x": "iOS 10",
"iOS 11.x": "iOS 11",
"iOS 12.x": "iOS 12",
"iOS 13.x": "iOS 13",
"iOS 14.x": "iOS 14",
"iOS 15.x": "iOS 15",
"iOS 16.x": "iOS 16",
"iOS 17.x": "iOS 17",
"iOS 18.x": "iOS 18",
"iOS 2.x": "iOS 2",
"iOS 3.x": "iOS 3",
"iOS 4.x": "iOS 4",
"iOS 5.x": "iOS 5",
"iOS 6.x": "iOS 6",
"iOS 7.x": "iOS 7",
"iOS 8.x": "iOS 8",
"iOS 9.x": "iOS 9"
},
"versioned": true
}
},
"keep_log": [],
"locked_dimensions": [
{
"description": "Native Apple UI frameworks and iOS-native UI patterns used to build screens, components, layouts, navigation, gestures, animations, and interactive app experiences for iPhone and iPad apps. Includes UIKit, SwiftUI, view controllers, views, Auto Layout, reusable components, and event-driven rendering of app state in native mobile interfaces.",
"exemplar_skills": [
"Apple Native UI Frameworks (UIKit and SwiftUI)"
],
"in_scope": "Skills, tools, and practices that belong under Apple Native UI Frameworks (UIKit and SwiftUI) for the target role, including items implied by the dimension rationale.",
"name": "Apple Native UI Frameworks (UIKit and SwiftUI)",
"out_of_scope": "Adjacent clusters explicitly not owned by Apple Native UI Frameworks (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 Native UI Frameworks (UIKit and SwiftUI)",
"merged_from": [
"uikit-and-swiftui",
"uikit-and-swiftui"
],
"pair_kind": "cross_role",
"reasoning": "Both dims describe the same Apple-native UI framework cluster. A covers native Apple UI frameworks for iPhone/iPad screens and interactions, explicitly listing UIKit, SwiftUI, view controllers, Auto Layout, gestures, and reusable components. B uses the same name and nearly identical scope: native Apple UI frameworks for screens, components, and interactive app experiences, with composing views, handling events, and rendering state in iOS-native paradigms. The exemplar skills in A map directly to B\u0027s description, so this is one conceptual cluster, not two.",
"similarity": 0.9258636773189943
}
],
"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": [
"android",
"javascript",
"python",
"go",
"solidity",
"aws",
"powershell",
"ansible",
"dex"
],
"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 a language runtime like JVM or Node.js.",
"Concept: ruled out \u2014 iOS is a concrete platform, not a knowledge unit."
],
"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 (UIKit and SwiftUI)",
"id": null,
"rationale": "Native Apple UI frameworks and related implementation skills used to build iOS and macOS app screens, components, and interactive experiences. Includes UIKit and SwiftUI, Objective-C legacy UI code, view controllers, views, table and collection views, event handling, state-driven rendering, and SwiftUI/UIKit interoperability. Excludes backend APIs, database access, app security, and other non-UI platform services.",
"slug": "d_merge_01",
"source": "llm"
},
"input_skill": "Objective C",
"llm_role": null,
"roles_from_db": []
},
{
"dimension": {
"difficulty_hint": null,
"display_name": "Mobile App Security and Privacy",
"id": null,
"rationale": "Security and privacy practices for native mobile applications, including secure storage and credential handling, platform security controls, app transport/network security, privacy permissions, and hardening against device compromise or jailbreak/root risks. Covers secure client-side handling of sensitive data across mobile platforms.",
"slug": "d_merge_02",
"source": "llm"
},
"input_skill": "Objective C",
"llm_role": null,
"roles_from_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 not commonly confused with other catalog skills in typical job descriptions."
},
"context_keywords": {
"context_keywords": [
"Cocoa",
"Cocoa Touch",
"Xcode",
"UIKit",
"Foundation",
"AppKit",
"ARC",
"delegates",
"protocols",
"categories",
"selectors",
"NSURLConnection",
"Core Data",
"iOS",
"macOS"
]
},
"maturity": {
"confidence": 0.89,
"maturity": "niche",
"reasoning": "Still appears in iOS/macOS legacy job postings, but most new Apple development JDs now prefer Swift; GitHub activity is far lower than modern mobile languages."
},
"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": [],
"locked_dimensions": [
{
"description": "Native Apple UI frameworks and related implementation skills used to build iOS and macOS app screens, components, and interactive experiences. Includes UIKit and SwiftUI, Objective-C legacy UI code, view controllers, views, table and collection views, event handling, state-driven rendering, and SwiftUI/UIKit interoperability. Excludes backend APIs, database access, app security, and other non-UI platform services.",
"exemplar_skills": [
"Apple Native UI Frameworks (UIKit and SwiftUI)"
],
"in_scope": "Skills, tools, and practices that belong under Apple Native UI Frameworks (UIKit and SwiftUI) for the target role, including items implied by the dimension rationale.",
"name": "Apple Native UI Frameworks (UIKit and SwiftUI)",
"out_of_scope": "Adjacent clusters explicitly not owned by Apple Native UI Frameworks (UIKit and SwiftUI), including unrelated platforms, roles, and skill families per library policy.",
"overlap_flags": [],
"tentative_id": "d_merge_01"
},
{
"description": "Security and privacy practices for native mobile applications, including secure storage and credential handling, platform security controls, app transport/network security, privacy permissions, and hardening against device compromise or jailbreak/root risks. Covers secure client-side handling of sensitive data across mobile platforms.",
"exemplar_skills": [
"Mobile App Security and Privacy"
],
"in_scope": "Skills, tools, and practices that belong under Mobile App Security and Privacy for the target role, including items implied by the dimension rationale.",
"name": "Mobile App Security and Privacy",
"out_of_scope": "Adjacent clusters explicitly not owned by Mobile App Security and Privacy, including unrelated platforms, roles, and skill families per library policy.",
"overlap_flags": [],
"tentative_id": "d_merge_02"
}
],
"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 (UIKit and SwiftUI)",
"merged_from": [
"uikit-and-swiftui",
"uikit-and-swiftui"
],
"pair_kind": "cross_role",
"reasoning": "Both dims describe the same Apple-native UI implementation cluster. A covers native Apple UI frameworks for iOS/macOS screens, components, interactions, with Objective C, UIKit view controllers, table/collection views, SwiftUI interoperability, and event handling. B says the same thing in slightly different words: native Apple UI frameworks for screens, components, interactive experiences, with composing views, handling events, and rendering state. The exemplar skills in A map directly to B\u2019s description, and there is no separate non-overlapping skill set.",
"similarity": 0.8995214566720908
},
{
"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",
"into": "d_merge_02",
"into_name": "Mobile App Security and Privacy",
"merged_from": [
"app-security-and-privacy",
"app-security-and-privacy"
],
"pair_kind": "cross_role",
"reasoning": "Both dimensions describe the same mobile app security/privacy cluster. Dim A covers secure storage, Keychain access, App Transport Security, privacy permissions, and jailbreak-aware controls for native mobile apps. Dim B repeats the same description and even cites the same client-side sensitive-data and platform-security concerns. There is no distinct Android-vs-iOS skill split here; the content is identical, so MERGE is appropriate.",
"similarity": 0.8374822370390889
}
],
"placed": {
"name": "Objective C",
"placement_confidence": 0.92,
"primary_dimension": "d_merge_01",
"reasoning": "Deterministic JD placement: locked_dimensions has 2 dimension(s) from skill-driven dimension generation after reconciliation; primary_dimension is the first locked dim.",
"secondary_dimensions": [
"d_merge_02"
],
"skill_id": "objective-c"
},
"relationships": {
"child_skills": [],
"parent_skills": [],
"related_to": [
"javascript",
"python",
"go",
"r",
"bash",
"powershell",
"solidity",
"ethereum",
"bash-scripting",
"powercli"
],
"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:40-\u003e2"
]
},
"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 or algorithm design, not a distinct catalog skill with a competing meaning."
},
"context_keywords": {
"context_keywords": [
"Big-O",
"time complexity",
"space complexity",
"dynamic programming",
"greedy",
"divide and conquer",
"recursion",
"graph traversal",
"sorting",
"searching",
"hashing",
"data structures",
"backtracking",
"memoization",
"complexity analysis"
]
},
"maturity": {
"confidence": 0.98,
"maturity": "well_known",
"reasoning": "Algorithms are a core CS hiring staple: they appear in most software engineering JDs and interview loops, and are foundational in university curricula and coding platforms like LeetCode."
},
"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": "Core algorithmic thinking for designing, analyzing, and implementing efficient solutions to computational problems. This covers selecting appropriate data structures, reasoning about complexity, and applying standard algorithmic techniques.",
"exemplar_skills": [
"algorithms",
"algorithm design",
"complexity analysis",
"data structures",
"sorting algorithms",
"graph algorithms"
],
"in_scope": "algorithms, algorithm design, complexity analysis, data structures, sorting, searching, recursion, dynamic programming, greedy methods, graph algorithms, divide and conquer",
"name": "Algorithms and Problem Solving",
"out_of_scope": "language syntax and idioms, UI component implementation, database schema design, model training and evaluation, infrastructure tuning",
"overlap_flags": [
{
"reason": "Algorithm implementation is often expressed in a programming language, but this dimension is about the algorithmic method rather than the language itself.",
"with_dim_id": "analytical-programming-languages",
"with_dim_name": null,
"with_role": "Data Analyst, Data Scientist"
},
{
"reason": "Debugging can involve algorithmic reasoning, but that dimension owns defect diagnosis and incident investigation rather than algorithm design.",
"with_dim_id": "troubleshooting-and-incident-resolution",
"with_dim_name": null,
"with_role": "ServiceNOW Developer"
}
],
"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": [],
"confidence": 0.98,
"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 tool or methodology.",
"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",
"hash tables",
"trees",
"binary trees",
"heaps",
"graphs",
"tries",
"hash maps",
"priority queue",
"recursion",
"Big O",
"algorithm design"
]
},
"maturity": {
"confidence": 0.98,
"maturity": "well_known",
"reasoning": "Core CS topic in nearly all software engineering JDs and interview loops; 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": "Core abstract and concrete ways to organize and access data in software. This belongs here because the skill refers to fundamental representations used across algorithms, APIs, and system design.",
"exemplar_skills": [
"data structures",
"arrays",
"linked lists",
"stacks",
"queues",
"hash tables",
"trees",
"graphs",
"heaps",
"tries"
],
"in_scope": "data structures, arrays, linked lists, stacks, queues, hash tables, trees, graphs, heaps, tries, sets, maps, tuples, records",
"name": "Data Structures",
"out_of_scope": "algorithms and complexity analysis, database schema design, storage engines, UI state management, memory management internals",
"overlap_flags": [
{
"reason": "Programming in languages like Python or Java often includes implementing and using data structures, but the dimension here is the data organization concepts themselves.",
"with_dim_id": "analytical-programming-languages",
"with_dim_name": null,
"with_role": "Data Analyst, Data Scientist"
},
{
"reason": "Frontend state containers may use data structures, but that catalog dimension is about application state patterns rather than the underlying structures.",
"with_dim_id": "state-management-and-client-data",
"with_dim_name": null,
"with_role": "Frontend Engineer, Full Stack Developer, iOS Engineer"
}
],
"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",
"summary-statistics",
"state-transitions",
"derived-views",
"missing-data-analysis",
"segment-analysis",
"capacity-forecasting",
"metadata-json",
"subgraphs"
],
"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, language, 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": null,
"chosen_role_resolution": null,
"final_input_skills": [
{
"skill": "iOS",
"tag": "new"
},
{
"skill": "Objective C",
"tag": "new"
},
{
"skill": "algorithms",
"tag": "new"
},
{
"skill": "data structures",
"tag": "new"
}
],
"persistence": {
"items": [],
"new_skills_created": 0,
"role_dimension_saved": 0,
"skill_dimension_saved": 0,
"skipped": 0
},
"planner_output": null,
"run_id": "15713f4f-e8c3-4853-8537-7ce6e2e99ad5"
}
LLM Calls
Every model call made for this run, in pipeline order. Click a card to see the model's response.