Pipeline run
dc80fd71-01d5-4819-9e8f-4d7d1223f832
Client output enrichment
v2 Skill cluster · Nature of work · AI index · Tech stack maturity · Evidence · KRA description
role baseline loaded
sources · ai_index: jd · 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
AI index (0 = no AI use, 5 = totally AI-dependent · v2.1)
0.00 / 5
· Title match
· Has AI skill
· AI skill (primary)
· AI skill (secondary)
· On AI team
· Builds AI products
vocab breakdown (legacy)
Assistants (×1):
—
Frameworks (×2):
—
Models / concepts (×3):
—
Evidence — skills matched in JD (0)
Skill cluster (0 dimension groups, role-scoped)
Status:
completed
Created: 2026-05-08T09:18:21.186008Z
Updated: 2026-05-08T09:20:10.334151Z
API 3 duration: 921 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
DevOps Engineer
slug: devops-engineer · id: 1 · source: db
Cloud Platform Operations is the strongest repeated signal, with additional API and Node.js backend-adjacent evidence supporting a platform/operations role.
0
New skills
0
Skill↔dim saved
0
Role↔dim saved
9
Skipped
Job description
About the job Job title: Full Stack Developer Location: Gurgaon, Haryana, India About noon We’re building an ecosystem of digital products and services that power everyday life across the Middle East—fast, scalable, and deeply customer-centric. Our mission is to deliver to every door every day. We want to redefine what technology can do in this region, and we’re looking for a Full Stack Developer who can help us move even faster. noon’s mission: Every door, every day. What you'll do: Team noon has some of the fastest, smartest, and hardest-working people we've encountered. With a young, aggressive, and talented team, we're driving major missions forward. Responsibilities: Design, develop, and maintain robust web applications for ecommerce platforms. Work across backend technologies (e.g., Django, Node.js, or similar frameworks) to build scalable services. Create and maintain RESTful APIs and integrate third-party services. Optimize applications for speed, scalability, and performance. Handle the deployment of web applications using CI/CD pipelines and cloud platforms such as AWS, GCP, or Azure. Optimize applications for performance, scalability, and security. Collaborate with cross-functional teams to translate business requirements into technical solutions. Troubleshoot, debug, and resolve issues in applications and deployment environments. Monitor deployed applications to ensure high availability and performance. What you'll need: 3-5 years of professional experience in web development. Strong expertise in backend development using Django, Node.js, or other frameworks. Experience with database management (e.g., PostgreSQL, MySQL, MongoDB). Familiarity with version control tools, especially Git. Knowledge of cloud platforms (e.g., AWS, GCP, Azure) and deployment pipelines. Hands-on experience with building APIs and integrating third-party tools. Strong problem-solving skills and an eye for detail. Excellent communication and team collaboration abilities. Who will excel? We’re looking for people with high standards, who understand that hard work matters. You need to be relentlessly resourceful and operate with a deep bias for action. We need people with the courage to be fiercely original. noon is not for everyone; readiness to adapt, pivot, and learn is essential.
history_view bundle (older API). Showing raw API payloads below.
All API 3 persistence rows
Same grid as the skill-extractor “Persistence items” table: one row per (skill × dimension) work item.
| Skill | Tag | Dimension | Skill↔dim | Role↔dim | Outcome | Notes |
|---|---|---|---|---|---|---|
| REST APIs | in_db |
API Integration and Data Fetching
api-integration-and-data-fetching
|
— | — | — | TODO: REMOVE AFTER TESTING — api3_writes_enabled=False (writes disabled) |
| REST APIs | in_db |
API Integration and Serialization
api-integration-and-serialization
|
— | — | — | TODO: REMOVE AFTER TESTING — api3_writes_enabled=False (writes disabled) |
| REST APIs | in_db |
Network Automation and Scripting
network-automation-and-scripting
|
— | — | — | TODO: REMOVE AFTER TESTING — api3_writes_enabled=False (writes disabled) |
| MongoDB | in_db |
NoSQL and Cache Stores
nosql-and-cache-stores
|
— | — | — | TODO: REMOVE AFTER TESTING — api3_writes_enabled=False (writes disabled) |
| MongoDB | in_db |
NoSQL and Data Lake Storage
nosql-and-data-lake-storage
|
— | — | — | TODO: REMOVE AFTER TESTING — api3_writes_enabled=False (writes disabled) |
| Azure | in_db |
Cloud Platform Operations
cloud-platform-operations
|
— | — | — | TODO: REMOVE AFTER TESTING — api3_writes_enabled=False (writes disabled) |
| AWS | in_db |
Cloud Platform Operations
cloud-platform-operations
|
— | — | — | TODO: REMOVE AFTER TESTING — api3_writes_enabled=False (writes disabled) |
| APIs | new |
API Design and Integration
d_init_01
|
— | — | — | skill_not_in_db_v3_proposed |
| Node.js | new |
Node.js Backend Runtime
d_init_01
|
— | — | — | skill_not_in_db_v3_proposed |
Library artifacts (this run)
| Kind | Detail | DB id |
|---|---|---|
| canonical_skill_proposed | APIs | type=Protocol subtype=application_programming_interface nature=PROTOCOL lifespan=EVERGREEN | |
| canonical_skill_proposed | Node.js | type=Runtime subtype=javascript_runtime nature=RUNTIME lifespan=EVERGREEN | |
| dimension_proposed | API Design and Integration | |
| dimension_skill_link_proposed | APIs ↔ API Design and Integration | |
| dimension_proposed | Node.js Backend Runtime | |
| dimension_skill_link_proposed | Node.js ↔ Node.js Backend Runtime |
API 1 — extract-from-jd click to toggle
{
"filtered_unknown_words": [
"APIs",
"CD",
"CI",
"Design",
"Developer",
"East",
"Experience",
"Familiarity",
"Gurgaon",
"Hands",
"Haryana",
"India",
"Job",
"Knowledge",
"Location",
"Middle",
"Monitor",
"Node.js",
"Optimize",
"Responsibilities",
"Stack",
"Team",
"Troubleshoot",
"Work",
"abilities",
"action",
"applications",
"availability",
"bias",
"business",
"centric",
"cloud",
"communication",
"control",
"courage",
"customer",
"database",
"day",
"debug",
"deployment",
"detail",
"development",
"door",
"ecommerce",
"ecosystem",
"environments",
"experience",
"expertise",
"eye",
"frameworks",
"issues",
"job",
"life",
"matters",
"mission",
"missions",
"noon",
"party",
"people",
"performance",
"pipelines",
"pivot",
"platforms",
"power",
"problem",
"products",
"region",
"requirements",
"security",
"services",
"skills",
"solutions",
"speed",
"standards",
"team",
"teams",
"technologies",
"technology",
"title",
"tools",
"version",
"web",
"work",
"years"
],
"final_non_skills": [
"CD",
"CI",
"Design",
"Developer",
"East",
"Experience",
"Familiarity",
"Gurgaon",
"Hands",
"Haryana",
"India",
"Job",
"Knowledge",
"Location",
"Middle",
"Monitor",
"Optimize",
"Responsibilities",
"Stack",
"Team",
"Troubleshoot",
"Work",
"abilities",
"action",
"applications",
"availability",
"bias",
"business",
"centric",
"cloud",
"communication",
"control",
"courage",
"customer",
"database",
"day",
"debug",
"deployment",
"detail",
"development",
"door",
"ecommerce",
"ecosystem",
"environments",
"expertise",
"eye",
"frameworks",
"issues",
"life",
"matters",
"mission",
"missions",
"noon",
"party",
"people",
"performance",
"pipelines",
"pivot",
"platforms",
"power",
"problem",
"products",
"region",
"requirements",
"security",
"services",
"skills",
"solutions",
"speed",
"standards",
"teams",
"technologies",
"technology",
"title",
"tools",
"version",
"web",
"years"
],
"final_skills": [
"REST APIs",
"MongoDB",
"Azure",
"AWS",
"APIs",
"Node.js"
],
"initial_skills": [
"REST APIs",
"MongoDB",
"Azure",
"AWS"
],
"jd_role_hint": {
"display_name": "Full Stack Developer",
"rationale": "The excerpt centers on a full stack developer building scalable web applications, APIs, and backend services.",
"role_archetype": "Builds and maintains end-to-end web applications across frontend and backend services.",
"slug": "full-stack-developer"
},
"llm_non_skills": [
"CD",
"CI",
"Design",
"Developer",
"East",
"Experience",
"Familiarity",
"Gurgaon",
"Hands",
"Haryana",
"India",
"Job",
"Knowledge",
"Location",
"Middle",
"Monitor",
"Optimize",
"Responsibilities",
"Stack",
"Team",
"Troubleshoot",
"Work",
"abilities",
"action",
"applications",
"availability",
"bias",
"business",
"centric",
"cloud",
"communication",
"control",
"courage",
"customer",
"database",
"day",
"debug",
"deployment",
"detail",
"development",
"door",
"ecommerce",
"ecosystem",
"environments",
"expertise",
"eye",
"frameworks",
"issues",
"life",
"matters",
"mission",
"missions",
"noon",
"party",
"people",
"performance",
"pipelines",
"pivot",
"platforms",
"power",
"problem",
"products",
"region",
"requirements",
"security",
"services",
"skills",
"solutions",
"speed",
"standards",
"teams",
"technologies",
"technology",
"title",
"tools",
"version",
"web",
"years"
],
"llm_skills": [
"APIs",
"Node.js"
],
"run_id": null,
"unknown_words": [
"APIs",
"CD",
"CI",
"Design",
"Developer",
"East",
"Experience",
"Familiarity",
"Gurgaon",
"Hands",
"Haryana",
"India",
"Job",
"Knowledge",
"Location",
"Middle",
"Monitor",
"Node.js",
"Optimize",
"Responsibilities",
"Stack",
"Team",
"Troubleshoot",
"Work",
"abilities",
"action",
"applications",
"availability",
"bias",
"business",
"centric",
"cloud",
"communication",
"control",
"courage",
"customer",
"database",
"day",
"debug",
"deployment",
"detail",
"development",
"door",
"ecommerce",
"ecosystem",
"environments",
"experience",
"expertise",
"eye",
"frameworks",
"issues",
"job",
"life",
"matters",
"mission",
"missions",
"noon",
"party",
"people",
"performance",
"pipelines",
"pivot",
"platforms",
"power",
"problem",
"products",
"region",
"requirements",
"security",
"services",
"skills",
"solutions",
"speed",
"standards",
"team",
"teams",
"technologies",
"technology",
"title",
"tools",
"version",
"web",
"work",
"years"
]
}
API 2 — extract-details
{
"alias_matches": [],
"candidate_roles": [
{
"display_name": "Frontend Engineer",
"id": 3,
"rationale": null,
"role_archetype": "Frontend Engineers design and build the user-facing parts of applications, translating product and design requirements into interactive experiences. They focus on how the application looks, behaves, and responds in the browser, ensuring usability, accessibility, and consistency across the interface.",
"slug": "frontend-engineer",
"source": "db"
},
{
"display_name": "Full Stack Developer",
"id": 2,
"rationale": null,
"role_archetype": null,
"slug": "full-stack-developer",
"source": "db"
},
{
"display_name": "iOS Engineer",
"id": 13,
"rationale": null,
"role_archetype": null,
"slug": "ios-engineer",
"source": "db"
},
{
"display_name": "Network Engineer",
"id": 21,
"rationale": null,
"role_archetype": null,
"slug": "network-engineer",
"source": "db"
},
{
"display_name": "Backend Engineer",
"id": 14,
"rationale": null,
"role_archetype": null,
"slug": "backend-engineer",
"source": "db"
},
{
"display_name": "Data Engineer",
"id": 6,
"rationale": null,
"role_archetype": null,
"slug": "data-engineer",
"source": "db"
},
{
"display_name": "DevOps Engineer",
"id": 1,
"rationale": null,
"role_archetype": "A DevOps Engineer enables reliable, repeatable delivery of software by designing and operating the processes that connect development and production. They focus on improving deployment flow, operational stability, and collaboration between teams through automation, standardization, and monitoring of delivery and runtime practices.",
"slug": "devops-engineer",
"source": "db"
}
],
"chosen_role": {
"display_name": "DevOps Engineer",
"id": 1,
"rationale": "Cloud Platform Operations is the strongest repeated signal, with additional API and Node.js backend-adjacent evidence supporting a platform/operations role.",
"role_archetype": "A DevOps Engineer enables reliable, repeatable delivery of software by designing and operating the processes that connect development and production. They focus on improving deployment flow, operational stability, and collaboration between teams through automation, standardization, and monitoring of delivery and runtime practices.",
"slug": "devops-engineer",
"source": "db"
},
"dimensions": [
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "API Integration and Data Fetching",
"id": 9,
"rationale": "Connecting frontend applications to backend services and third-party endpoints. This covers request orchestration, error handling, pagination, and shaping remote data for UI consumption.",
"slug": "api-integration-and-data-fetching",
"source": "db"
},
"input_skill": "REST APIs",
"llm_role": null,
"roles_from_db": [
{
"display_name": "Frontend Engineer",
"id": 3,
"rationale": null,
"role_archetype": "Frontend Engineers design and build the user-facing parts of applications, translating product and design requirements into interactive experiences. They focus on how the application looks, behaves, and responds in the browser, ensuring usability, accessibility, and consistency across the interface.",
"slug": "frontend-engineer",
"source": "db"
},
{
"display_name": "Full Stack Developer",
"id": 2,
"rationale": null,
"role_archetype": null,
"slug": "full-stack-developer",
"source": "db"
}
]
},
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "API Integration and Serialization",
"id": 128,
"rationale": "Client-side integration with backend services, including request handling, response parsing, and contract alignment. This cluster is coherent because iOS features frequently depend on stable data exchange with server APIs.",
"slug": "api-integration-and-serialization",
"source": "db"
},
"input_skill": "REST APIs",
"llm_role": null,
"roles_from_db": [
{
"display_name": "iOS Engineer",
"id": 13,
"rationale": null,
"role_archetype": null,
"slug": "ios-engineer",
"source": "db"
}
]
},
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Network Automation and Scripting",
"id": 285,
"rationale": "Covers scripts and automation used to configure, validate, and audit network devices and services. This cluster is coherent because repeatable network operations increasingly depend on programmatic changes and checks.",
"slug": "network-automation-and-scripting",
"source": "db"
},
"input_skill": "REST APIs",
"llm_role": null,
"roles_from_db": [
{
"display_name": "Network Engineer",
"id": 21,
"rationale": null,
"role_archetype": null,
"slug": "network-engineer",
"source": "db"
}
]
},
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "NoSQL and Cache Stores",
"id": 145,
"rationale": "Non-relational databases and in-memory stores used for low-latency access, flexible schemas, and specialized persistence patterns. This cluster is coherent because backend services often combine these stores with relational systems.",
"slug": "nosql-and-cache-stores",
"source": "db"
},
"input_skill": "MongoDB",
"llm_role": null,
"roles_from_db": [
{
"display_name": "Backend Engineer",
"id": 14,
"rationale": null,
"role_archetype": null,
"slug": "backend-engineer",
"source": "db"
}
]
},
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "NoSQL and Data Lake Storage",
"id": 73,
"rationale": "Non-relational stores and lake storage used for semi-structured, large-scale, or raw data retention. This cluster is coherent because many pipelines land and serve data outside classic relational warehouses.",
"slug": "nosql-and-data-lake-storage",
"source": "db"
},
"input_skill": "MongoDB",
"llm_role": null,
"roles_from_db": [
{
"display_name": "Data Engineer",
"id": 6,
"rationale": null,
"role_archetype": null,
"slug": "data-engineer",
"source": "db"
}
]
},
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Cloud Platform Operations",
"id": 26,
"rationale": "Uses cloud provider services to support delivery and runtime environments. The focus is on consumer-level operation of cloud services rather than deep cloud architecture ownership.",
"slug": "cloud-platform-operations",
"source": "db"
},
"input_skill": "Azure",
"llm_role": null,
"roles_from_db": [
{
"display_name": "DevOps Engineer",
"id": 1,
"rationale": null,
"role_archetype": "A DevOps Engineer enables reliable, repeatable delivery of software by designing and operating the processes that connect development and production. They focus on improving deployment flow, operational stability, and collaboration between teams through automation, standardization, and monitoring of delivery and runtime practices.",
"slug": "devops-engineer",
"source": "db"
}
]
},
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Cloud Platform Operations",
"id": 26,
"rationale": "Uses cloud provider services to support delivery and runtime environments. The focus is on consumer-level operation of cloud services rather than deep cloud architecture ownership.",
"slug": "cloud-platform-operations",
"source": "db"
},
"input_skill": "AWS",
"llm_role": null,
"roles_from_db": [
{
"display_name": "DevOps Engineer",
"id": 1,
"rationale": null,
"role_archetype": "A DevOps Engineer enables reliable, repeatable delivery of software by designing and operating the processes that connect development and production. They focus on improving deployment flow, operational stability, and collaboration between teams through automation, standardization, and monitoring of delivery and runtime practices.",
"slug": "devops-engineer",
"source": "db"
}
]
},
{
"dimension": {
"difficulty_hint": null,
"display_name": "API Design and Integration",
"id": null,
"rationale": "Designing and consuming application programming interfaces for client-server and service-to-service communication. This fits APIs because the skill covers contracts, request/response shapes, versioning, and reliable integration patterns.",
"slug": "d_init_01",
"source": "llm"
},
"input_skill": "APIs",
"llm_role": null,
"roles_from_db": []
},
{
"dimension": {
"difficulty_hint": null,
"display_name": "Node.js Backend Runtime",
"id": null,
"rationale": "Server-side JavaScript development using Node.js for APIs, workers, and backend services. This belongs here because Node.js is the primary runtime for implementing backend logic and integrations in JavaScript.",
"slug": "d_init_01",
"source": "llm"
},
"input_skill": "Node.js",
"llm_role": null,
"roles_from_db": []
}
],
"input_final_skills": [
"REST APIs",
"MongoDB",
"Azure",
"AWS",
"APIs",
"Node.js"
],
"input_llm_skills": [
"APIs",
"Node.js"
],
"new_aliases_persisted": 0,
"run_id": "dc80fd71-01d5-4819-9e8f-4d7d1223f832",
"skills_detail": [
{
"aliases_in_db": [
{
"alias_text": "REST APIs",
"alias_type": "CANONICAL",
"id": 174,
"is_primary": true,
"match_strategy": "CASE_INSENSITIVE"
}
],
"canonical": {
"category_id": 8,
"display_name": "REST APIs",
"id": 49,
"is_also_category": false,
"is_extractable": true,
"skill_nature": "PROTOCOL",
"slug": "rest-apis",
"sub_category_id": 67,
"typical_lifespan": "EVERGREEN",
"volatility": "STABLE"
},
"dimensions": [
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "API Integration and Data Fetching",
"id": 9,
"rationale": "Connecting frontend applications to backend services and third-party endpoints. This covers request orchestration, error handling, pagination, and shaping remote data for UI consumption.",
"slug": "api-integration-and-data-fetching",
"source": "db"
},
"input_skill": "REST APIs",
"llm_role": null,
"roles_from_db": [
{
"display_name": "Frontend Engineer",
"id": 3,
"rationale": null,
"role_archetype": "Frontend Engineers design and build the user-facing parts of applications, translating product and design requirements into interactive experiences. They focus on how the application looks, behaves, and responds in the browser, ensuring usability, accessibility, and consistency across the interface.",
"slug": "frontend-engineer",
"source": "db"
},
{
"display_name": "Full Stack Developer",
"id": 2,
"rationale": null,
"role_archetype": null,
"slug": "full-stack-developer",
"source": "db"
}
]
},
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "API Integration and Serialization",
"id": 128,
"rationale": "Client-side integration with backend services, including request handling, response parsing, and contract alignment. This cluster is coherent because iOS features frequently depend on stable data exchange with server APIs.",
"slug": "api-integration-and-serialization",
"source": "db"
},
"input_skill": "REST APIs",
"llm_role": null,
"roles_from_db": [
{
"display_name": "iOS Engineer",
"id": 13,
"rationale": null,
"role_archetype": null,
"slug": "ios-engineer",
"source": "db"
}
]
},
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Network Automation and Scripting",
"id": 285,
"rationale": "Covers scripts and automation used to configure, validate, and audit network devices and services. This cluster is coherent because repeatable network operations increasingly depend on programmatic changes and checks.",
"slug": "network-automation-and-scripting",
"source": "db"
},
"input_skill": "REST APIs",
"llm_role": null,
"roles_from_db": [
{
"display_name": "Network Engineer",
"id": 21,
"rationale": null,
"role_archetype": null,
"slug": "network-engineer",
"source": "db"
}
]
}
],
"input_skill": "REST APIs",
"matched_via": "alias",
"new_alias_persisted": false,
"new_alias_text": null,
"new_skill_meta": null,
"source_tag": "db",
"was_in_llm_skills": false
},
{
"aliases_in_db": [
{
"alias_text": "MongoDB",
"alias_type": "CANONICAL",
"id": 684,
"is_primary": true,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "MongoDB 3",
"alias_type": "VERSION",
"id": 685,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "MongoDB 3.x",
"alias_type": "VERSION",
"id": 691,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "MongoDB 4",
"alias_type": "VERSION",
"id": 686,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "MongoDB 4.x",
"alias_type": "VERSION",
"id": 692,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "MongoDB 5",
"alias_type": "VERSION",
"id": 687,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "MongoDB 5.x",
"alias_type": "VERSION",
"id": 693,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "MongoDB 6",
"alias_type": "VERSION",
"id": 688,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "MongoDB 6.x",
"alias_type": "VERSION",
"id": 694,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "MongoDB 7",
"alias_type": "VERSION",
"id": 689,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "MongoDB 7.x",
"alias_type": "VERSION",
"id": 695,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "MongoDB 8",
"alias_type": "VERSION",
"id": 690,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "MongoDB 8.x",
"alias_type": "VERSION",
"id": 696,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
}
],
"canonical": {
"category_id": 12,
"display_name": "MongoDB",
"id": 432,
"is_also_category": false,
"is_extractable": true,
"skill_nature": "TOOL",
"slug": "mongodb",
"sub_category_id": 360,
"typical_lifespan": "EVERGREEN",
"volatility": "STABLE"
},
"dimensions": [
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "NoSQL and Cache Stores",
"id": 145,
"rationale": "Non-relational databases and in-memory stores used for low-latency access, flexible schemas, and specialized persistence patterns. This cluster is coherent because backend services often combine these stores with relational systems.",
"slug": "nosql-and-cache-stores",
"source": "db"
},
"input_skill": "MongoDB",
"llm_role": null,
"roles_from_db": [
{
"display_name": "Backend Engineer",
"id": 14,
"rationale": null,
"role_archetype": null,
"slug": "backend-engineer",
"source": "db"
}
]
},
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "NoSQL and Data Lake Storage",
"id": 73,
"rationale": "Non-relational stores and lake storage used for semi-structured, large-scale, or raw data retention. This cluster is coherent because many pipelines land and serve data outside classic relational warehouses.",
"slug": "nosql-and-data-lake-storage",
"source": "db"
},
"input_skill": "MongoDB",
"llm_role": null,
"roles_from_db": [
{
"display_name": "Data Engineer",
"id": 6,
"rationale": null,
"role_archetype": null,
"slug": "data-engineer",
"source": "db"
}
]
}
],
"input_skill": "MongoDB",
"matched_via": "alias",
"new_alias_persisted": false,
"new_alias_text": null,
"new_skill_meta": null,
"source_tag": "db",
"was_in_llm_skills": false
},
{
"aliases_in_db": [
{
"alias_text": "Azure",
"alias_type": "CANONICAL",
"id": 349,
"is_primary": true,
"match_strategy": "CASE_INSENSITIVE"
}
],
"canonical": {
"category_id": 13,
"display_name": "Azure",
"id": 164,
"is_also_category": false,
"is_extractable": true,
"skill_nature": "PLATFORM",
"slug": "azure",
"sub_category_id": 161,
"typical_lifespan": "EVERGREEN",
"volatility": "STABLE"
},
"dimensions": [
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Cloud Platform Operations",
"id": 26,
"rationale": "Uses cloud provider services to support delivery and runtime environments. The focus is on consumer-level operation of cloud services rather than deep cloud architecture ownership.",
"slug": "cloud-platform-operations",
"source": "db"
},
"input_skill": "Azure",
"llm_role": null,
"roles_from_db": [
{
"display_name": "DevOps Engineer",
"id": 1,
"rationale": null,
"role_archetype": "A DevOps Engineer enables reliable, repeatable delivery of software by designing and operating the processes that connect development and production. They focus on improving deployment flow, operational stability, and collaboration between teams through automation, standardization, and monitoring of delivery and runtime practices.",
"slug": "devops-engineer",
"source": "db"
}
]
}
],
"input_skill": "Azure",
"matched_via": "alias",
"new_alias_persisted": false,
"new_alias_text": null,
"new_skill_meta": null,
"source_tag": "db",
"was_in_llm_skills": false
},
{
"aliases_in_db": [
{
"alias_text": "AWS",
"alias_type": "CANONICAL",
"id": 348,
"is_primary": true,
"match_strategy": "CASE_INSENSITIVE"
}
],
"canonical": {
"category_id": 13,
"display_name": "AWS",
"id": 163,
"is_also_category": false,
"is_extractable": true,
"skill_nature": "PLATFORM",
"slug": "aws",
"sub_category_id": 161,
"typical_lifespan": "EVERGREEN",
"volatility": "STABLE"
},
"dimensions": [
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Cloud Platform Operations",
"id": 26,
"rationale": "Uses cloud provider services to support delivery and runtime environments. The focus is on consumer-level operation of cloud services rather than deep cloud architecture ownership.",
"slug": "cloud-platform-operations",
"source": "db"
},
"input_skill": "AWS",
"llm_role": null,
"roles_from_db": [
{
"display_name": "DevOps Engineer",
"id": 1,
"rationale": null,
"role_archetype": "A DevOps Engineer enables reliable, repeatable delivery of software by designing and operating the processes that connect development and production. They focus on improving deployment flow, operational stability, and collaboration between teams through automation, standardization, and monitoring of delivery and runtime practices.",
"slug": "devops-engineer",
"source": "db"
}
]
}
],
"input_skill": "AWS",
"matched_via": "alias",
"new_alias_persisted": false,
"new_alias_text": null,
"new_skill_meta": null,
"source_tag": "db",
"was_in_llm_skills": false
},
{
"aliases_in_db": [],
"canonical": null,
"dimensions": [
{
"dimension": {
"difficulty_hint": null,
"display_name": "API Design and Integration",
"id": null,
"rationale": "Designing and consuming application programming interfaces for client-server and service-to-service communication. This fits APIs because the skill covers contracts, request/response shapes, versioning, and reliable integration patterns.",
"slug": "d_init_01",
"source": "llm"
},
"input_skill": "APIs",
"llm_role": null,
"roles_from_db": []
}
],
"input_skill": "APIs",
"matched_via": null,
"new_alias_persisted": false,
"new_alias_text": null,
"new_skill_meta": {
"derived": {
"category": "Protocol",
"skill_nature": "PROTOCOL",
"sub_category": "application_programming_interface",
"typical_lifespan": "EVERGREEN",
"version_strategy": "NOT_APPLICABLE",
"volatility": "STABLE"
},
"enrichment": {
"ambiguity": {
"ambiguity_flag": true,
"confused_with": [
"api"
],
"reasoning": "\u201cAPIs\u201d is a generic plural term and can be used interchangeably with the singular skill \u201cAPI\u201d; a JD extractor could map either mention to the other catalog entry."
},
"context_keywords": {
"context_keywords": [
"REST",
"GraphQL",
"OpenAPI",
"Swagger",
"JSON",
"XML",
"OAuth 2.0",
"API gateway",
"endpoint",
"webhooks",
"rate limiting",
"pagination",
"versioning",
"microservices",
"SDK"
]
},
"maturity": {
"confidence": 0.98,
"maturity": "well_known",
"reasoning": "APIs are a hiring-pipeline staple across backend, mobile, and platform JDs; REST/GraphQL/API design appears in large volumes of job postings and cloud vendor docs."
},
"skill_id": "apis",
"vendor_license": {
"confidence": 0.99,
"license": null,
"vendor": null,
"year_introduced": null
},
"versioning": {
"current_version": null,
"version_aliases": {},
"versioned": false
}
},
"locked_dimensions": [
{
"description": "Designing and consuming application programming interfaces for client-server and service-to-service communication. This fits APIs because the skill covers contracts, request/response shapes, versioning, and reliable integration patterns.",
"exemplar_skills": [
"APIs",
"REST APIs",
"OpenAPI",
"Swagger",
"JSON APIs",
"gRPC",
"Webhook design",
"API versioning"
],
"in_scope": "APIs, REST APIs, OpenAPI, Swagger, JSON APIs, gRPC, webhooks, API versioning, pagination, filtering, rate limiting",
"name": "API Design and Integration",
"out_of_scope": "Authentication session flows, UI state management, database access control, and backend business logic, which belong to authentication, frontend, governance, or service-architecture dimensions.",
"overlap_flags": [
{
"reason": "Both involve invoking external interfaces, but this dimension is about application/service contracts rather than model tool invocation.",
"with_dim_id": "tool-use-and-function-calling",
"with_dim_name": null,
"with_role": null
},
{
"reason": "API implementations often carry auth tokens, but login/session lifecycle belongs to the authentication dimension.",
"with_dim_id": "authentication-flows-and-session-handling",
"with_dim_name": null,
"with_role": null
}
],
"tentative_id": "d_init_01"
}
],
"merge_log": [],
"placed": {
"name": "APIs",
"placement_confidence": 0.92,
"primary_dimension": "d_init_01",
"reasoning": "Deterministic JD placement: locked_dimensions has 1 dimension(s) from skill-driven dimension generation after reconciliation; primary_dimension is the first locked dim.",
"secondary_dimensions": [],
"skill_id": "apis"
},
"relationships": {
"child_skills": [],
"parent_skills": [],
"related_to": [
"rest-apis",
"grpc",
"http",
"json",
"scripted-rest-api",
"outbound-rest-messages",
"mock-servers"
],
"requires": [],
"skill_id": "apis",
"suppress_on_match": []
},
"skill_id": "apis",
"split_log": [],
"typed": {
"alternatives_considered": [
"Concept: ruled out \u2014 APIs are not just a knowledge unit; they define an interaction interface.",
"Format: ruled out \u2014 APIs are not primarily a data structure or wire format."
],
"confidence": 0.88,
"name": "APIs",
"reasoning": "APIs are best treated as a communication interface standard between systems, so under the Protocol rule they fit Protocol rather than Tool or Platform.",
"skill_id": "apis",
"subtype": "application_programming_interface",
"type": "Protocol"
},
"warnings": []
},
"source_tag": "llm",
"was_in_llm_skills": true
},
{
"aliases_in_db": [],
"canonical": null,
"dimensions": [
{
"dimension": {
"difficulty_hint": null,
"display_name": "Node.js Backend Runtime",
"id": null,
"rationale": "Server-side JavaScript development using Node.js for APIs, workers, and backend services. This belongs here because Node.js is the primary runtime for implementing backend logic and integrations in JavaScript.",
"slug": "d_init_01",
"source": "llm"
},
"input_skill": "Node.js",
"llm_role": null,
"roles_from_db": []
}
],
"input_skill": "Node.js",
"matched_via": null,
"new_alias_persisted": false,
"new_alias_text": null,
"new_skill_meta": {
"derived": {
"category": "Runtime",
"skill_nature": "RUNTIME",
"sub_category": "javascript_runtime",
"typical_lifespan": "EVERGREEN",
"version_strategy": "SEPARATE_ENTITY",
"volatility": "STABLE"
},
"enrichment": {
"ambiguity": {
"ambiguity_flag": false,
"confused_with": [],
"reasoning": "Node.js is a specific JavaScript runtime and is usually mentioned unambiguously in JDs; it is not commonly confused with another catalog skill."
},
"context_keywords": {
"context_keywords": [
"Express",
"NestJS",
"npm",
"yarn",
"TypeScript",
"REST API",
"GraphQL",
"microservices",
"event loop",
"async/await",
"CommonJS",
"ES modules",
"Socket.io",
"JWT",
"MongoDB"
]
},
"maturity": {
"confidence": 0.98,
"maturity": "well_known",
"reasoning": "Node.js appears in high-volume job postings across backend, full-stack, and cloud roles, and remains a standard runtime in major vendor docs and ecosystem tooling."
},
"skill_id": "node-js",
"vendor_license": {
"confidence": 0.98,
"license": "mit",
"vendor": "OpenJS Foundation",
"year_introduced": 2009
},
"versioning": {
"current_version": "22.x",
"version_aliases": {
"Node 16": "16.x",
"Node 18": "18.x",
"Node 20": "20.x",
"Node 22": "22.x",
"Node.js 16": "16.x",
"Node.js 16.x": "16.x",
"Node.js 18": "18.x",
"Node.js 18.x": "18.x",
"Node.js 20": "20.x",
"Node.js 20.x": "20.x",
"Node.js 22": "22.x",
"Node.js 22.x": "22.x"
},
"versioned": true
}
},
"locked_dimensions": [
{
"description": "Server-side JavaScript development using Node.js for APIs, workers, and backend services. This belongs here because Node.js is the primary runtime for implementing backend logic and integrations in JavaScript.",
"exemplar_skills": [
"Node.js",
"Express.js",
"NestJS",
"server-side JavaScript",
"async/await",
"event loop",
"API development"
],
"in_scope": "Node.js, JavaScript runtime on the server, Express.js, NestJS backend code, API handlers, request/response logic, async I/O, event loop basics, server-side modules",
"name": "Node.js Backend Runtime",
"out_of_scope": "Frontend JavaScript frameworks, browser DOM manipulation, mobile app code, database administration, infrastructure provisioning, client-side state management",
"overlap_flags": [
{
"reason": "Node.js is often used to build services, but that dimension owns the higher-level service decomposition and integration patterns.",
"with_dim_id": "service-architecture-and-integration",
"with_dim_name": null,
"with_role": null
},
{
"reason": "Node.js is a backend language/runtime skill, but this catalog has no existing runtime-specific backend language dimension to reuse.",
"with_dim_id": "programming-languages-for-backend-systems",
"with_dim_name": null,
"with_role": null
}
],
"tentative_id": "d_init_01"
}
],
"merge_log": [],
"placed": {
"name": "Node.js",
"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": "node-js"
},
"relationships": {
"child_skills": [],
"parent_skills": [],
"related_to": [
"typescript",
"angularjs",
"python",
"java",
"bash",
"kubernetes",
"rest-apis",
"http"
],
"requires": [
"javascript",
"npm"
],
"skill_id": "node-js",
"suppress_on_match": []
},
"skill_id": "node-js",
"split_log": [],
"typed": {
"alternatives_considered": [],
"confidence": 0.99,
"name": "Node.js",
"reasoning": "By the Runtime rule, Node.js is an execution environment for code rather than a library, framework, or tool.",
"skill_id": "node-js",
"subtype": "javascript_runtime",
"type": "Runtime"
},
"warnings": []
},
"source_tag": "llm",
"was_in_llm_skills": true
}
],
"unmatched_skills": [
"APIs",
"Node.js"
]
}
API 3 — final-role-output
{
"chosen_role": {
"display_name": "DevOps Engineer",
"id": 1,
"rationale": "Cloud Platform Operations is the strongest repeated signal, with additional API and Node.js backend-adjacent evidence supporting a platform/operations role.",
"role_archetype": "A DevOps Engineer enables reliable, repeatable delivery of software by designing and operating the processes that connect development and production. They focus on improving deployment flow, operational stability, and collaboration between teams through automation, standardization, and monitoring of delivery and runtime practices.",
"slug": "devops-engineer",
"source": "db"
},
"final_input_skills": [
{
"skill": "REST APIs",
"tag": "in_db"
},
{
"skill": "MongoDB",
"tag": "in_db"
},
{
"skill": "Azure",
"tag": "in_db"
},
{
"skill": "AWS",
"tag": "in_db"
},
{
"skill": "APIs",
"tag": "new"
},
{
"skill": "Node.js",
"tag": "new"
}
],
"persistence": {
"items": [
{
"chosen_role_id": 1,
"dimension": {
"difficulty_hint": "well_known",
"display_name": "API Integration and Data Fetching",
"id": 9,
"rationale": "Connecting frontend applications to backend services and third-party endpoints. This covers request orchestration, error handling, pagination, and shaping remote data for UI consumption.",
"slug": "api-integration-and-data-fetching",
"source": "db"
},
"dimension_id": 9,
"input_skill": "REST APIs",
"llm_role": null,
"matched_chosen_role": false,
"role_dimension_saved": false,
"roles_from_db": [
{
"display_name": "Frontend Engineer",
"id": 3,
"rationale": null,
"role_archetype": "Frontend Engineers design and build the user-facing parts of applications, translating product and design requirements into interactive experiences. They focus on how the application looks, behaves, and responds in the browser, ensuring usability, accessibility, and consistency across the interface.",
"slug": "frontend-engineer",
"source": "db"
},
{
"display_name": "Full Stack Developer",
"id": 2,
"rationale": null,
"role_archetype": null,
"slug": "full-stack-developer",
"source": "db"
}
],
"skill_dimension_saved": false,
"skill_id": 49,
"skill_tag": "in_db",
"skipped_reason": "TODO: REMOVE AFTER TESTING \u2014 api3_writes_enabled=False (writes disabled)"
},
{
"chosen_role_id": 1,
"dimension": {
"difficulty_hint": "well_known",
"display_name": "API Integration and Serialization",
"id": 128,
"rationale": "Client-side integration with backend services, including request handling, response parsing, and contract alignment. This cluster is coherent because iOS features frequently depend on stable data exchange with server APIs.",
"slug": "api-integration-and-serialization",
"source": "db"
},
"dimension_id": 128,
"input_skill": "REST APIs",
"llm_role": null,
"matched_chosen_role": false,
"role_dimension_saved": false,
"roles_from_db": [
{
"display_name": "iOS Engineer",
"id": 13,
"rationale": null,
"role_archetype": null,
"slug": "ios-engineer",
"source": "db"
}
],
"skill_dimension_saved": false,
"skill_id": 49,
"skill_tag": "in_db",
"skipped_reason": "TODO: REMOVE AFTER TESTING \u2014 api3_writes_enabled=False (writes disabled)"
},
{
"chosen_role_id": 1,
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Network Automation and Scripting",
"id": 285,
"rationale": "Covers scripts and automation used to configure, validate, and audit network devices and services. This cluster is coherent because repeatable network operations increasingly depend on programmatic changes and checks.",
"slug": "network-automation-and-scripting",
"source": "db"
},
"dimension_id": 285,
"input_skill": "REST APIs",
"llm_role": null,
"matched_chosen_role": false,
"role_dimension_saved": false,
"roles_from_db": [
{
"display_name": "Network Engineer",
"id": 21,
"rationale": null,
"role_archetype": null,
"slug": "network-engineer",
"source": "db"
}
],
"skill_dimension_saved": false,
"skill_id": 49,
"skill_tag": "in_db",
"skipped_reason": "TODO: REMOVE AFTER TESTING \u2014 api3_writes_enabled=False (writes disabled)"
},
{
"chosen_role_id": 1,
"dimension": {
"difficulty_hint": "well_known",
"display_name": "NoSQL and Cache Stores",
"id": 145,
"rationale": "Non-relational databases and in-memory stores used for low-latency access, flexible schemas, and specialized persistence patterns. This cluster is coherent because backend services often combine these stores with relational systems.",
"slug": "nosql-and-cache-stores",
"source": "db"
},
"dimension_id": 145,
"input_skill": "MongoDB",
"llm_role": null,
"matched_chosen_role": false,
"role_dimension_saved": false,
"roles_from_db": [
{
"display_name": "Backend Engineer",
"id": 14,
"rationale": null,
"role_archetype": null,
"slug": "backend-engineer",
"source": "db"
}
],
"skill_dimension_saved": false,
"skill_id": 432,
"skill_tag": "in_db",
"skipped_reason": "TODO: REMOVE AFTER TESTING \u2014 api3_writes_enabled=False (writes disabled)"
},
{
"chosen_role_id": 1,
"dimension": {
"difficulty_hint": "well_known",
"display_name": "NoSQL and Data Lake Storage",
"id": 73,
"rationale": "Non-relational stores and lake storage used for semi-structured, large-scale, or raw data retention. This cluster is coherent because many pipelines land and serve data outside classic relational warehouses.",
"slug": "nosql-and-data-lake-storage",
"source": "db"
},
"dimension_id": 73,
"input_skill": "MongoDB",
"llm_role": null,
"matched_chosen_role": false,
"role_dimension_saved": false,
"roles_from_db": [
{
"display_name": "Data Engineer",
"id": 6,
"rationale": null,
"role_archetype": null,
"slug": "data-engineer",
"source": "db"
}
],
"skill_dimension_saved": false,
"skill_id": 432,
"skill_tag": "in_db",
"skipped_reason": "TODO: REMOVE AFTER TESTING \u2014 api3_writes_enabled=False (writes disabled)"
},
{
"chosen_role_id": 1,
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Cloud Platform Operations",
"id": 26,
"rationale": "Uses cloud provider services to support delivery and runtime environments. The focus is on consumer-level operation of cloud services rather than deep cloud architecture ownership.",
"slug": "cloud-platform-operations",
"source": "db"
},
"dimension_id": 26,
"input_skill": "Azure",
"llm_role": null,
"matched_chosen_role": true,
"role_dimension_saved": false,
"roles_from_db": [
{
"display_name": "DevOps Engineer",
"id": 1,
"rationale": null,
"role_archetype": "A DevOps Engineer enables reliable, repeatable delivery of software by designing and operating the processes that connect development and production. They focus on improving deployment flow, operational stability, and collaboration between teams through automation, standardization, and monitoring of delivery and runtime practices.",
"slug": "devops-engineer",
"source": "db"
}
],
"skill_dimension_saved": false,
"skill_id": 164,
"skill_tag": "in_db",
"skipped_reason": "TODO: REMOVE AFTER TESTING \u2014 api3_writes_enabled=False (writes disabled)"
},
{
"chosen_role_id": 1,
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Cloud Platform Operations",
"id": 26,
"rationale": "Uses cloud provider services to support delivery and runtime environments. The focus is on consumer-level operation of cloud services rather than deep cloud architecture ownership.",
"slug": "cloud-platform-operations",
"source": "db"
},
"dimension_id": 26,
"input_skill": "AWS",
"llm_role": null,
"matched_chosen_role": true,
"role_dimension_saved": false,
"roles_from_db": [
{
"display_name": "DevOps Engineer",
"id": 1,
"rationale": null,
"role_archetype": "A DevOps Engineer enables reliable, repeatable delivery of software by designing and operating the processes that connect development and production. They focus on improving deployment flow, operational stability, and collaboration between teams through automation, standardization, and monitoring of delivery and runtime practices.",
"slug": "devops-engineer",
"source": "db"
}
],
"skill_dimension_saved": false,
"skill_id": 163,
"skill_tag": "in_db",
"skipped_reason": "TODO: REMOVE AFTER TESTING \u2014 api3_writes_enabled=False (writes disabled)"
},
{
"chosen_role_id": 1,
"dimension": {
"difficulty_hint": null,
"display_name": "API Design and Integration",
"id": null,
"rationale": "Designing and consuming application programming interfaces for client-server and service-to-service communication. This fits APIs because the skill covers contracts, request/response shapes, versioning, and reliable integration patterns.",
"slug": "d_init_01",
"source": "llm"
},
"dimension_id": null,
"input_skill": "APIs",
"llm_role": null,
"matched_chosen_role": false,
"role_dimension_saved": false,
"roles_from_db": [],
"skill_dimension_saved": false,
"skill_id": null,
"skill_tag": "new",
"skipped_reason": "skill_not_in_db_v3_proposed"
},
{
"chosen_role_id": 1,
"dimension": {
"difficulty_hint": null,
"display_name": "Node.js Backend Runtime",
"id": null,
"rationale": "Server-side JavaScript development using Node.js for APIs, workers, and backend services. This belongs here because Node.js is the primary runtime for implementing backend logic and integrations in JavaScript.",
"slug": "d_init_01",
"source": "llm"
},
"dimension_id": null,
"input_skill": "Node.js",
"llm_role": null,
"matched_chosen_role": false,
"role_dimension_saved": false,
"roles_from_db": [],
"skill_dimension_saved": false,
"skill_id": null,
"skill_tag": "new",
"skipped_reason": "skill_not_in_db_v3_proposed"
}
],
"new_skills_created": 0,
"role_dimension_saved": 0,
"skill_dimension_saved": 0,
"skipped": 9
},
"planner_output": null,
"run_id": "dc80fd71-01d5-4819-9e8f-4d7d1223f832"
}
LLM Calls
Every model call made for this run, in pipeline order. Click a card to see the model's response.
Loading…