Pipeline run
d957d5c0-9584-4f40-aef9-56f810a35523
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:27:45.929543Z
Updated: 2026-05-08T09:29:33.530998Z
API 3 duration: 968 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
Full Stack Developer
slug: full-stack-developer · id: 2 · source: db
The dimensions most consistently point to web/API work with backend, cloud, and deployment concerns, and the JD hint also aligns with Full Stack Developer.
0
New skills
0
Skill↔dim saved
0
Role↔dim saved
10
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 |
Service API Design
d_init_01
|
— | — | — | skill_not_in_db_v3_proposed |
| APIs | new |
Backend Request Handling
d_init_02
|
— | — | — | skill_not_in_db_v3_proposed |
| Node.js | new |
Backend JavaScript Runtime Development
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 | Service API Design | |
| dimension_skill_link_proposed | APIs ↔ Service API Design | |
| dimension_proposed | Backend Request Handling | |
| dimension_skill_link_proposed | APIs ↔ Backend Request Handling | |
| dimension_proposed | Backend JavaScript Runtime Development | |
| dimension_skill_link_proposed | Node.js ↔ Backend JavaScript Runtime Development |
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",
"communication",
"control",
"courage",
"customer",
"database",
"day",
"debug",
"detail",
"development",
"door",
"ecosystem",
"environments",
"expertise",
"eye",
"frameworks",
"issues",
"life",
"matters",
"mission",
"missions",
"noon",
"party",
"people",
"pivot",
"platforms",
"power",
"problem",
"products",
"region",
"requirements",
"services",
"skills",
"solutions",
"speed",
"standards",
"teams",
"technology",
"title",
"tools",
"version",
"years"
],
"final_skills": [
"REST APIs",
"MongoDB",
"Azure",
"AWS",
"APIs",
"Node.js",
"cloud",
"deployment",
"ecommerce",
"performance",
"pipelines",
"security",
"technologies",
"web"
],
"initial_skills": [
"REST APIs",
"MongoDB",
"Azure",
"AWS"
],
"jd_role_hint": {
"display_name": "Full Stack Developer",
"rationale": "The excerpt centers on a full stack web developer role involving APIs, backend technologies, deployment, and cloud platforms.",
"role_archetype": "Builds and maintains end-to-end web applications across frontend and backend systems.",
"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",
"communication",
"control",
"courage",
"customer",
"database",
"day",
"debug",
"detail",
"development",
"door",
"ecosystem",
"environments",
"expertise",
"eye",
"frameworks",
"issues",
"life",
"matters",
"mission",
"missions",
"noon",
"party",
"people",
"pivot",
"platforms",
"power",
"problem",
"products",
"region",
"requirements",
"services",
"skills",
"solutions",
"speed",
"standards",
"teams",
"technology",
"title",
"tools",
"version",
"years"
],
"llm_skills": [
"APIs",
"Node.js",
"cloud",
"deployment",
"ecommerce",
"performance",
"pipelines",
"security",
"technologies",
"web"
],
"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": "Full Stack Developer",
"id": 2,
"rationale": "The dimensions most consistently point to web/API work with backend, cloud, and deployment concerns, and the JD hint also aligns with Full Stack Developer.",
"role_archetype": null,
"slug": "full-stack-developer",
"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": "Service API Design",
"id": null,
"rationale": "Designing and consuming application interfaces between services, clients, and external systems. APIs fit here because they define how software components communicate, what contracts they expose, and how integrations are structured.",
"slug": "d_init_01",
"source": "llm"
},
"input_skill": "APIs",
"llm_role": null,
"roles_from_db": []
},
{
"dimension": {
"difficulty_hint": null,
"display_name": "Backend Request Handling",
"id": null,
"rationale": "Implementing server-side endpoints that receive requests and return structured responses. APIs belong here when the skill is about coding handlers, routing, validation, and backend business logic behind the interface.",
"slug": "d_init_02",
"source": "llm"
},
"input_skill": "APIs",
"llm_role": null,
"roles_from_db": []
},
{
"dimension": {
"difficulty_hint": null,
"display_name": "Backend JavaScript Runtime Development",
"id": null,
"rationale": "Server-side application development using Node.js to build APIs, workers, and integration services. Node.js belongs here because it is the primary runtime and programming environment for backend JavaScript code.",
"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",
"cloud",
"deployment",
"ecommerce",
"performance",
"pipelines",
"security",
"technologies",
"web"
],
"input_llm_skills": [
"APIs",
"Node.js",
"cloud",
"deployment",
"ecommerce",
"performance",
"pipelines",
"security",
"technologies",
"web"
],
"new_aliases_persisted": 0,
"run_id": "d957d5c0-9584-4f40-aef9-56f810a35523",
"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": "Service API Design",
"id": null,
"rationale": "Designing and consuming application interfaces between services, clients, and external systems. APIs fit here because they define how software components communicate, what contracts they expose, and how integrations are structured.",
"slug": "d_init_01",
"source": "llm"
},
"input_skill": "APIs",
"llm_role": null,
"roles_from_db": []
},
{
"dimension": {
"difficulty_hint": null,
"display_name": "Backend Request Handling",
"id": null,
"rationale": "Implementing server-side endpoints that receive requests and return structured responses. APIs belong here when the skill is about coding handlers, routing, validation, and backend business logic behind the interface.",
"slug": "d_init_02",
"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": false,
"confused_with": [],
"reasoning": "APIs is a standard, well-scoped term in JDs and usually refers to application programming interfaces; it is not typically confused with a different catalog skill."
},
"context_keywords": {
"context_keywords": [
"REST",
"GraphQL",
"OpenAPI",
"Swagger",
"JSON",
"OAuth 2.0",
"webhooks",
"endpoints",
"rate limiting",
"API gateway",
"microservices",
"SDK",
"versioning",
"authentication",
"HTTP"
]
},
"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 interfaces between services, clients, and external systems. APIs fit here because they define how software components communicate, what contracts they expose, and how integrations are structured.",
"exemplar_skills": [
"APIs",
"REST APIs",
"GraphQL APIs",
"API versioning",
"Webhook design",
"Service contracts"
],
"in_scope": "APIs, REST APIs, GraphQL APIs, RPC interfaces, service contracts, request/response schemas, versioning, pagination, idempotency, error handling, webhooks",
"name": "Service API Design",
"out_of_scope": "Authentication flows, session handling, UI state management, database schema design, message queue internals",
"overlap_flags": [
{
"reason": "API work often includes auth headers and token exchange, but that dimension owns client-side sign-in and session behavior.",
"with_dim_id": "authentication-flows-and-session-handling",
"with_dim_name": null,
"with_role": null
},
{
"reason": "Both involve callable interfaces, but this dimension is about product/service integration rather than model tool invocation.",
"with_dim_id": "tool-use-and-function-calling",
"with_dim_name": null,
"with_role": null
}
],
"tentative_id": "d_init_01"
},
{
"description": "Implementing server-side endpoints that receive requests and return structured responses. APIs belong here when the skill is about coding handlers, routing, validation, and backend business logic behind the interface.",
"exemplar_skills": [
"APIs",
"HTTP endpoints",
"Request validation",
"Response serialization",
"Route handlers",
"Controller logic"
],
"in_scope": "APIs, endpoint handlers, routing, request validation, response serialization, middleware, controller logic, backend service endpoints, HTTP status codes",
"name": "Backend Request Handling",
"out_of_scope": "Frontend data fetching, UI components, database administration, cloud service selection, authentication UX",
"overlap_flags": [
{
"reason": "API implementation overlaps with service design, but this dimension emphasizes backend code rather than cross-service architecture.",
"with_dim_id": "service-architecture-and-integration",
"with_dim_name": null,
"with_role": null
}
],
"tentative_id": "d_init_02"
}
],
"merge_log": [],
"placed": {
"name": "APIs",
"placement_confidence": 0.92,
"primary_dimension": "d_init_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_init_02"
],
"skill_id": "apis"
},
"relationships": {
"child_skills": [],
"parent_skills": [],
"related_to": [
"rest-apis",
"grpc",
"http",
"json",
"oauth-2-0",
"aws-iam",
"outbound-rest-messages",
"scripted-rest-api"
],
"requires": [],
"skill_id": "apis",
"suppress_on_match": []
},
"skill_id": "apis",
"split_log": [],
"typed": {
"alternatives_considered": [],
"confidence": 0.91,
"name": "APIs",
"reasoning": "APIs are a communication interface standard between systems, so by the Protocol rule they fit best as a protocol-like contract rather than a 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": "Backend JavaScript Runtime Development",
"id": null,
"rationale": "Server-side application development using Node.js to build APIs, workers, and integration services. Node.js belongs here because it is the primary runtime and programming environment for backend JavaScript code.",
"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 with a distinctive name; in typical JDs it is unlikely to be 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 frameworks like Next.js and NestJS."
},
"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 12": "12.x",
"Node 14": "14.x",
"Node 16": "16.x",
"Node 18": "18.x",
"Node 20": "20.x",
"Node 22": "22.x",
"Node.js 12": "12.x",
"Node.js 12.x": "12.x",
"Node.js 14": "14.x",
"Node.js 14.x": "14.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 application development using Node.js to build APIs, workers, and integration services. Node.js belongs here because it is the primary runtime and programming environment for backend JavaScript code.",
"exemplar_skills": [
"Node.js",
"Express.js",
"Fastify",
"NestJS",
"server-side JavaScript",
"async/await in backend code",
"npm"
],
"in_scope": "Node.js, JavaScript runtime on the server, Express.js, Fastify, NestJS, request handlers, background workers, API endpoints, async I/O, npm package usage, server-side module patterns",
"name": "Backend JavaScript Runtime Development",
"out_of_scope": "Frontend JavaScript frameworks, browser DOM manipulation, mobile app code, database administration, infrastructure provisioning, observability tooling, which belong to other dimensions",
"overlap_flags": [
{
"reason": "Node.js is often used to implement service endpoints and integrations, but that dimension focuses on system decomposition and inter-service patterns rather than the runtime itself.",
"with_dim_id": "service-architecture-and-integration",
"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": [
"javascript",
"npm",
"typescript",
"python",
"java",
"bash",
"http",
"rest-apis"
],
"requires": [],
"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
},
{
"aliases_in_db": [],
"canonical": null,
"dimensions": [],
"input_skill": "cloud",
"matched_via": null,
"new_alias_persisted": false,
"new_alias_text": null,
"new_skill_meta": null,
"source_tag": "llm",
"was_in_llm_skills": true
},
{
"aliases_in_db": [],
"canonical": null,
"dimensions": [],
"input_skill": "deployment",
"matched_via": null,
"new_alias_persisted": false,
"new_alias_text": null,
"new_skill_meta": null,
"source_tag": "llm",
"was_in_llm_skills": true
},
{
"aliases_in_db": [],
"canonical": null,
"dimensions": [],
"input_skill": "ecommerce",
"matched_via": null,
"new_alias_persisted": false,
"new_alias_text": null,
"new_skill_meta": null,
"source_tag": "llm",
"was_in_llm_skills": true
},
{
"aliases_in_db": [],
"canonical": null,
"dimensions": [],
"input_skill": "performance",
"matched_via": null,
"new_alias_persisted": false,
"new_alias_text": null,
"new_skill_meta": null,
"source_tag": "llm",
"was_in_llm_skills": true
},
{
"aliases_in_db": [],
"canonical": null,
"dimensions": [],
"input_skill": "pipelines",
"matched_via": null,
"new_alias_persisted": false,
"new_alias_text": null,
"new_skill_meta": null,
"source_tag": "llm",
"was_in_llm_skills": true
},
{
"aliases_in_db": [],
"canonical": null,
"dimensions": [],
"input_skill": "security",
"matched_via": null,
"new_alias_persisted": false,
"new_alias_text": null,
"new_skill_meta": null,
"source_tag": "llm",
"was_in_llm_skills": true
},
{
"aliases_in_db": [],
"canonical": null,
"dimensions": [],
"input_skill": "technologies",
"matched_via": null,
"new_alias_persisted": false,
"new_alias_text": null,
"new_skill_meta": null,
"source_tag": "llm",
"was_in_llm_skills": true
},
{
"aliases_in_db": [],
"canonical": null,
"dimensions": [],
"input_skill": "web",
"matched_via": null,
"new_alias_persisted": false,
"new_alias_text": null,
"new_skill_meta": null,
"source_tag": "llm",
"was_in_llm_skills": true
}
],
"unmatched_skills": [
"APIs",
"Node.js"
]
}
API 3 — final-role-output
{
"chosen_role": {
"display_name": "Full Stack Developer",
"id": 2,
"rationale": "The dimensions most consistently point to web/API work with backend, cloud, and deployment concerns, and the JD hint also aligns with Full Stack Developer.",
"role_archetype": null,
"slug": "full-stack-developer",
"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"
},
{
"skill": "cloud",
"tag": "new"
},
{
"skill": "deployment",
"tag": "new"
},
{
"skill": "ecommerce",
"tag": "new"
},
{
"skill": "performance",
"tag": "new"
},
{
"skill": "pipelines",
"tag": "new"
},
{
"skill": "security",
"tag": "new"
},
{
"skill": "technologies",
"tag": "new"
},
{
"skill": "web",
"tag": "new"
}
],
"persistence": {
"items": [
{
"chosen_role_id": 2,
"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": true,
"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": 2,
"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": 2,
"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": 2,
"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": 2,
"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": 2,
"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": false,
"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": 2,
"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": false,
"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": 2,
"dimension": {
"difficulty_hint": null,
"display_name": "Service API Design",
"id": null,
"rationale": "Designing and consuming application interfaces between services, clients, and external systems. APIs fit here because they define how software components communicate, what contracts they expose, and how integrations are structured.",
"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": 2,
"dimension": {
"difficulty_hint": null,
"display_name": "Backend Request Handling",
"id": null,
"rationale": "Implementing server-side endpoints that receive requests and return structured responses. APIs belong here when the skill is about coding handlers, routing, validation, and backend business logic behind the interface.",
"slug": "d_init_02",
"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": 2,
"dimension": {
"difficulty_hint": null,
"display_name": "Backend JavaScript Runtime Development",
"id": null,
"rationale": "Server-side application development using Node.js to build APIs, workers, and integration services. Node.js belongs here because it is the primary runtime and programming environment for backend JavaScript code.",
"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": 10
},
"planner_output": null,
"run_id": "d957d5c0-9584-4f40-aef9-56f810a35523"
}
LLM Calls
Every model call made for this run, in pipeline order. Click a card to see the model's response.
Loading…