Pipeline run
0a5c4054-8355-4b91-882a-9e1fcada5d8d
Client output enrichment
v2 Skill cluster · Nature of work · AI index · Tech stack maturity · Evidence · KRA descriptionvocab breakdown (legacy)
Signals
Post-classification
1 POST /skills/extract-from-jd
2 POST /skills/extract-details
3 POST /skills/final-role-output
MuleSoft Developer
CASE Dslug: mulesoft-developer · id: — · source: llm
The primary skills focus on MuleSoft and API management, which align best with a MuleSoft Developer role.
Resolution:
human_review_required
— role not in DB; role↔dimension links may be deferred.
Job description
Software Engineer • 5+ years of Middleware/Integration experience (any platform) with at least 3 full life cycle MuleSoft Project experience (Analysis, Design, Dev, Testing, Deployment) • Good understanding of MuleSoft Deployment/Physical architecture (On Prem, on Cloud and Hybrid) • Expertise in message transformation, validation, routing, and orchestration in MuleSoft • Ability to define MuleSoft design and development best practices and testing guides etc. • Experience in API Management on MuleSoft platform • Ability to design and develop enterprise services using RAML in Mule, REST-based APIs, SOAP Web Services, and the use of different mule connectors. • Experience in Software Engineering Lifecycle Management using Agile methodology. • Understanding of MuleSoft DevOps support and capabilities. • Experience in managing and deploying MuleSoft applications. • Ability to lead a team of onsite and offshore developers. • Familiarity with Salesforce workbench, orgs, objects, and properties • A basic understanding of API-led connectivity, API reuse, and Salesforce integration patterns. • In depth knowledge on salesforce connector like upsert, create, query query single • Good to have MuleSoft Developer certification and advance level certifications.
Skills from this JD
Each row merges API 1 extraction, API 2 library match / v3 orchestration (dimensions + locked dims), and API 3 persistence tags.
Skill enrichment (orchestrator / LLM)
No Stage 7 enrichment blob on this skill (orchestrator skipped enrichment).
- Category
- Integration Tools
- Sub-category
- general
- Skill nature
- TOOL
- Volatility
- MEDIUM
- Typical lifespan
- MULTI_YEAR
- Version strategy
- UNVERSIONED
Skill enrichment (orchestrator / LLM)
No Stage 7 enrichment blob on this skill (orchestrator skipped enrichment).
- Category
- Concepts
- Sub-category
- general
- Skill nature
- CONCEPT
- Volatility
- MEDIUM
- Typical lifespan
- MULTI_YEAR
- Version strategy
- UNVERSIONED
Skill enrichment (orchestrator / LLM)
No Stage 7 enrichment blob on this skill (orchestrator skipped enrichment).
- Category
- API Description Languages
- Sub-category
- general
- Skill nature
- LANGUAGE
- Volatility
- MEDIUM
- Typical lifespan
- MULTI_YEAR
- Version strategy
- UNVERSIONED
Aliases — catalog
- REST (CANONICAL) primary
Context tags (catalog)
Stored enrichment (catalog DB)
- Category
- Concept
- Sub-category
- Api Architecture Style
- Year introduced
- 2000
- Confidence
- 0.88
- Version strategy
- NOT_APPLICABLE
Maturity reasoning: REST is a default API architecture in many job descriptions and is widely supported by major vendors/frameworks; OpenAPI and RESTful endpoints remain standard in hiring pipelines.
Skill profile (library / DB)
- Skill nature
- PROTOCOL
- Volatility
- STABLE
- Typical lifespan
- EVERGREEN
- Category id
- 10
- Sub-category id
- 48
- Extractable
- True
- Also category
- False
Dimensions (API 2 worklist)
-
API Design and Contracts Catalog dimension db id 3
Library dimension (catalog)
Roles linked in library: Backend Engineer, Full Stack Engineer
API 3 link attempts (this skill)
| Dimension | Skill↔dim | Role↔dim | Outcome |
|---|---|---|---|
|
API Design and Contracts
api-design-and-contracts
|
✓ | — | Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role) |
Aliases — catalog
- SOAP (CANONICAL) primary
Context tags (catalog)
Stored enrichment (catalog DB)
- Category
- Protocol
- Sub-category
- Api Protocol
- Year introduced
- 1998
- Confidence
- 0.97
- Version strategy
- NOT_APPLICABLE
Maturity reasoning: SOAP still appears in enterprise/legacy integration JDs, but far less than REST/GraphQL; many vendors and docs position REST/JSON as the default for new APIs, indicating a narrow, legacy-heavy market signal.
Skill profile (library / DB)
- Skill nature
- PROTOCOL
- Volatility
- STABLE
- Typical lifespan
- EVERGREEN
- Category id
- 10
- Sub-category id
- 54
- Extractable
- True
- Also category
- False
Dimensions (API 2 worklist)
-
External System Integrations Catalog dimension db id 14
Library dimension (catalog)
Roles linked in library: Backend Engineer
API 3 link attempts (this skill)
| Dimension | Skill↔dim | Role↔dim | Outcome |
|---|---|---|---|
|
External System Integrations
external-system-integrations
|
✓ | — | Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role) |
Aliases — catalog
- Agile (CANONICAL) primary
Context tags (catalog)
Stored enrichment (catalog DB)
- Category
- Methodology
- Sub-category
- Agile
- Confidence
- 0.99
- Version strategy
- NOT_APPLICABLE
Maturity reasoning: Agile appears in a large share of software job descriptions and is a standard hiring-pipeline requirement; Scrum/Kanban are commonly listed alongside it, showing broad market adoption.
Skill profile (library / DB)
- Skill nature
- METHODOLOGY
- Volatility
- STABLE
- Typical lifespan
- EVERGREEN
- Category id
- 8
- Sub-category id
- 367
- Extractable
- True
- Also category
- False
Dimensions (API 2 worklist)
-
React Frontend Development Catalog dimension db id 96
Library dimension (catalog)
API 3 link attempts (this skill)
| Dimension | Skill↔dim | Role↔dim | Outcome |
|---|---|---|---|
|
React Frontend Development
d_init_01
|
✓ | — | Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role) |
Aliases — catalog
- DevOps (CANONICAL)
Context tags (catalog)
Stored enrichment (catalog DB)
- Category
- Methodology
- Sub-category
- Devops Methodology
- Confidence
- 0.97
- Version strategy
- NOT_APPLICABLE
Maturity reasoning: DevOps appears in a large share of software and platform engineering job descriptions, often alongside CI/CD, Kubernetes, and cloud tooling; it is a standard hiring-pipeline keyword rather than a niche specialty.
Skill profile (library / DB)
- Skill nature
- METHODOLOGY
- Volatility
- STABLE
- Typical lifespan
- EVERGREEN
- Category id
- 8
- Sub-category id
- 922
- Extractable
- True
- Also category
- False
Dimensions (API 2 worklist)
-
CI/CD Pipeline Platforms Catalog dimension db id 150
Library dimension (catalog)
Roles linked in library: DevOps Engineer
-
Deployment and Release Patterns Catalog dimension db id 140
Library dimension (catalog)
Roles linked in library: Cloud Architect
-
Infrastructure as Code Catalog dimension db id 132
Library dimension (catalog)
Roles linked in library: Cloud Architect, DevOps Engineer
API 3 link attempts (this skill)
| Dimension | Skill↔dim | Role↔dim | Outcome |
|---|---|---|---|
|
CI/CD Pipeline Platforms
ci-cd-pipeline-platforms
|
✓ | — | Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role) |
|
Deployment and Release Patterns
deployment-and-release-patterns
|
✓ | — | Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role) |
|
Infrastructure as Code
infrastructure-as-code
|
✓ | — | Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role) |
Skill enrichment (orchestrator / LLM)
No Stage 7 enrichment blob on this skill (orchestrator skipped enrichment).
- Category
- Cloud Platforms
- Sub-category
- general
- Skill nature
- PLATFORM
- Volatility
- MEDIUM
- Typical lifespan
- MULTI_YEAR
- Version strategy
- UNVERSIONED
Skill enrichment (orchestrator / LLM)
No Stage 7 enrichment blob on this skill (orchestrator skipped enrichment).
- Category
- Integration Tools
- Sub-category
- general
- Skill nature
- TOOL
- Volatility
- MEDIUM
- Typical lifespan
- MULTI_YEAR
- Version strategy
- UNVERSIONED
Skill enrichment (orchestrator / LLM)
No Stage 7 enrichment blob on this skill (orchestrator skipped enrichment).
- Category
- Concepts
- Sub-category
- general
- Skill nature
- CONCEPT
- Volatility
- MEDIUM
- Typical lifespan
- MULTI_YEAR
- Version strategy
- UNVERSIONED
Skill enrichment (orchestrator / LLM)
No Stage 7 enrichment blob on this skill (orchestrator skipped enrichment).
- Category
- Concepts
- Sub-category
- general
- Skill nature
- CONCEPT
- Volatility
- MEDIUM
- Typical lifespan
- MULTI_YEAR
- Version strategy
- UNVERSIONED
All API 3 persistence rows
Same grid as the skill-extractor “Persistence items” table: one row per (skill × dimension) work item.
| Skill | Tag | Dimension | Skill↔dim | Role↔dim | Outcome | Notes |
|---|---|---|---|---|---|---|
| REST | in_db |
API Design and Contracts
api-design-and-contracts
|
✓ | — | Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role) | |
| SOAP | in_db |
External System Integrations
external-system-integrations
|
✓ | — | Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role) | |
| Agile | in_db |
React Frontend Development
d_init_01
|
✓ | — | Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role) | |
| DevOps | in_db |
CI/CD Pipeline Platforms
ci-cd-pipeline-platforms
|
✓ | — | Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role) | |
| DevOps | in_db |
Deployment and Release Patterns
deployment-and-release-patterns
|
✓ | — | Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role) | |
| DevOps | in_db |
Infrastructure as Code
infrastructure-as-code
|
✓ | — | Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role) |
Library artifacts (this run)
| Kind | Detail | DB id |
|---|---|---|
| canonical_skill_proposed | MuleSoft | type=Integration Tools subtype=general nature=TOOL lifespan=MULTI_YEAR | |
| canonical_skill_proposed | API Management | type=Concepts subtype=general nature=CONCEPT lifespan=MULTI_YEAR | |
| canonical_skill_proposed | RAML | type=API Description Languages subtype=general nature=LANGUAGE lifespan=MULTI_YEAR | |
| canonical_skill_proposed | Salesforce | type=Cloud Platforms subtype=general nature=PLATFORM lifespan=MULTI_YEAR | |
| canonical_skill_proposed | Salesforce Workbench | type=Integration Tools subtype=general nature=TOOL lifespan=MULTI_YEAR | |
| canonical_skill_proposed | API-led connectivity | type=Concepts subtype=general nature=CONCEPT lifespan=MULTI_YEAR | |
| canonical_skill_proposed | Integration Patterns | type=Concepts subtype=general nature=CONCEPT lifespan=MULTI_YEAR |
nano JD Parser — gpt-4.1-nano click to toggle
Certifications
Show raw JSON
{
"JD_type": "pass",
"about_company": null,
"certifications": [
"MuleSoft Developer certification"
],
"company_name": null,
"ctc": null,
"domain": {
"primary": {
"aliases": [],
"domain": "IT Services \u0026 Consulting"
},
"secondary": null
},
"education": [],
"experience": {
"max": null,
"min": 5,
"raw": "5+ years of Middleware/Integration experience"
},
"job_locations": [],
"role": "Software Engineer",
"role_aliases": [
"Software Developer",
"SWE",
"Integration Engineer"
],
"role_archetype": "Engineering",
"roles_and_responsibilities": [
{
"bullet_count": 12,
"heading": "Responsibilities",
"heading_was_present": true,
"source_marker": {
"first_5_words": "\u2022 5+ years of Middleware/Integration experience",
"last_5_words": "and advance level certifications."
},
"text": "\u2022 5+ years of Middleware/Integration experience (any platform) with at least 3 full life cycle MuleSoft Project experience (Analysis, Design, Dev, Testing, Deployment)\n\u2022 Good understanding of MuleSoft Deployment/Physical architecture (On Prem, on Cloud and Hybrid)\n\u2022 Expertise in message transformation, validation, routing, and orchestration in MuleSoft\n\u2022 Ability to define MuleSoft design and development best practices and testing guides etc.\n\u2022 Experience in API Management on MuleSoft platform\n\u2022 Ability to design and develop enterprise services using RAML in Mule, REST-based APIs, SOAP Web Services, and the use of different mule connectors.\n\u2022 Experience in Software Engineering Lifecycle Management using Agile methodology.\n\u2022 Understanding of MuleSoft DevOps support and capabilities.\n\u2022 Experience in managing and deploying MuleSoft applications.\n\u2022 Ability to lead a team of onsite and offshore developers.\n\u2022 Familiarity with Salesforce workbench, orgs, objects, and properties\n\u2022 A basic understanding of API-led connectivity, API reuse, and Salesforce integration patterns.\n\u2022 In depth knowledge on salesforce connector like upsert, create, query query single\n\u2022 Good to have MuleSoft Developer certification and advance level certifications.",
"word_count": 186
}
],
"urls": []
}
API 1 — extract-from-jd click to toggle
{
"final_skills": [
{
"is_primary": true,
"skill_name": "MuleSoft"
},
{
"is_primary": true,
"skill_name": "API Management"
},
{
"is_primary": true,
"skill_name": "RAML"
},
{
"is_primary": true,
"skill_name": "REST"
},
{
"is_primary": true,
"skill_name": "SOAP"
},
{
"is_primary": true,
"skill_name": "Agile"
},
{
"is_primary": false,
"skill_name": "DevOps"
},
{
"is_primary": true,
"skill_name": "Salesforce"
},
{
"is_primary": false,
"skill_name": "Salesforce Workbench"
},
{
"is_primary": false,
"skill_name": "API-led connectivity"
},
{
"is_primary": false,
"skill_name": "Integration Patterns"
}
],
"jd_role": {
"display_name": "Software Engineer",
"rationale": null,
"role_aliases": [
"Software Developer",
"SWE",
"Integration Engineer"
],
"role_archetype": "Engineering",
"slug": ""
},
"nano_parsed": {
"JD_type": "pass",
"about_company": null,
"certifications": [
"MuleSoft Developer certification"
],
"company_name": null,
"ctc": null,
"domain": {
"primary": {
"aliases": [],
"domain": "IT Services \u0026 Consulting"
},
"secondary": null
},
"education": [],
"experience": {
"max": null,
"min": 5,
"raw": "5+ years of Middleware/Integration experience"
},
"job_locations": [],
"role": "Software Engineer",
"role_aliases": [
"Software Developer",
"SWE",
"Integration Engineer"
],
"role_archetype": "Engineering",
"roles_and_responsibilities": [
{
"bullet_count": 12,
"heading": "Responsibilities",
"heading_was_present": true,
"source_marker": {
"first_5_words": "\u2022 5+ years of Middleware/Integration experience",
"last_5_words": "and advance level certifications."
},
"text": "\u2022 5+ years of Middleware/Integration experience (any platform) with at least 3 full life cycle MuleSoft Project experience (Analysis, Design, Dev, Testing, Deployment)\n\u2022 Good understanding of MuleSoft Deployment/Physical architecture (On Prem, on Cloud and Hybrid)\n\u2022 Expertise in message transformation, validation, routing, and orchestration in MuleSoft\n\u2022 Ability to define MuleSoft design and development best practices and testing guides etc.\n\u2022 Experience in API Management on MuleSoft platform\n\u2022 Ability to design and develop enterprise services using RAML in Mule, REST-based APIs, SOAP Web Services, and the use of different mule connectors.\n\u2022 Experience in Software Engineering Lifecycle Management using Agile methodology.\n\u2022 Understanding of MuleSoft DevOps support and capabilities.\n\u2022 Experience in managing and deploying MuleSoft applications.\n\u2022 Ability to lead a team of onsite and offshore developers.\n\u2022 Familiarity with Salesforce workbench, orgs, objects, and properties\n\u2022 A basic understanding of API-led connectivity, API reuse, and Salesforce integration patterns.\n\u2022 In depth knowledge on salesforce connector like upsert, create, query query single\n\u2022 Good to have MuleSoft Developer certification and advance level certifications.",
"word_count": 186
}
],
"urls": []
},
"rejected": false,
"rejection_reason": null,
"run_id": "0a5c4054-8355-4b91-882a-9e1fcada5d8d",
"stage3_signals": {
"alias_found": true,
"alias_match_roles": [
{
"display_name": "Data Engineer",
"matched_count": null,
"role_id": 2,
"score": 0.8077,
"slug": "data-engineer",
"total_count": null
},
{
"display_name": "Backend Engineer",
"matched_count": null,
"role_id": 1,
"score": 0.6923,
"slug": "backend-engineer",
"total_count": null
},
{
"display_name": "Android Engineer",
"matched_count": null,
"role_id": 4,
"score": 0.6923,
"slug": "android-engineer",
"total_count": null
},
{
"display_name": "ML Engineer",
"matched_count": null,
"role_id": 3,
"score": 0.5294,
"slug": "ml-engineer",
"total_count": null
},
{
"display_name": "AI Engineer",
"matched_count": null,
"role_id": 13,
"score": 0.4545,
"slug": "ai-engineer",
"total_count": null
}
],
"kra_match_roles": [
{
"display_name": "ML Engineer",
"matched_count": null,
"role_id": 3,
"score": 0.3673,
"slug": "ml-engineer",
"total_count": null
},
{
"display_name": "ML Ops Engineer",
"matched_count": null,
"role_id": 16,
"score": 0.3605,
"slug": "ml-ops-engineer",
"total_count": null
},
{
"display_name": "Hybrid Mobile Developer",
"matched_count": null,
"role_id": 11,
"score": 0.3535,
"slug": "hybrid-mobile-developer",
"total_count": null
},
{
"display_name": "Cloud Security Engineer",
"matched_count": null,
"role_id": 23,
"score": 0.3504,
"slug": "cloud-security-engineer",
"total_count": null
},
{
"display_name": "Cloud Architect",
"matched_count": null,
"role_id": 9,
"score": 0.3493,
"slug": "cloud-architect",
"total_count": null
}
],
"skill_match_roles": [
{
"display_name": "Backend Engineer",
"matched_count": 2,
"role_id": 1,
"score": 0.1818,
"slug": "backend-engineer",
"total_count": 11
},
{
"display_name": "Cloud Architect",
"matched_count": 1,
"role_id": 9,
"score": 0.0909,
"slug": "cloud-architect",
"total_count": 11
},
{
"display_name": "DevOps Engineer",
"matched_count": 1,
"role_id": 10,
"score": 0.0909,
"slug": "devops-engineer",
"total_count": 11
},
{
"display_name": "Full Stack Engineer",
"matched_count": 1,
"role_id": 15,
"score": 0.0909,
"slug": "full-stack-engineer",
"total_count": 11
}
]
},
"stage4_decision": {
"alias_collision_detected": true,
"case": "D",
"chosen_role": null,
"confidence": 0.65,
"is_new_role": false,
"llm2_fired": true,
"llm2_reasoning": "While neither role directly matches MuleSoft integration work, an ML Engineer is more likely to have experience with API design, deployment, and REST-based services compared to an iOS engineer.",
"new_role_display_name": null,
"new_role_slug": null,
"queued": true,
"reasoning": "LLM2 unsure (confidence 0.65 \u003c 0.7); queueing"
},
"stage5_updates": {
"centroid_n_after": null,
"centroid_updated": false,
"collision_log_id": 74,
"new_kra_attached": null,
"new_skills_attached": [],
"queue_entry_id": 46,
"v3_pipeline_triggered": false,
"v3_role_slug": null,
"v3_run_id": null
}
}
API 2 — extract-details
{
"alias_matches": [
{
"alias_persist_skipped_reason": "alias_text already exists for this canonical skill",
"alias_persisted": false,
"existing_alias_id": 106,
"existing_alias_text": "REST",
"input_term": "REST",
"matched_canonical": {
"category_id": 10,
"display_name": "REST",
"id": 11,
"is_also_category": false,
"is_extractable": true,
"skill_nature": "PROTOCOL",
"slug": "rest",
"sub_category_id": 48,
"typical_lifespan": "EVERGREEN",
"volatility": "STABLE"
},
"matched_via": "alias"
},
{
"alias_persist_skipped_reason": "alias_text already exists for this canonical skill",
"alias_persisted": false,
"existing_alias_id": 211,
"existing_alias_text": "SOAP",
"input_term": "SOAP",
"matched_canonical": {
"category_id": 10,
"display_name": "SOAP",
"id": 70,
"is_also_category": false,
"is_extractable": true,
"skill_nature": "PROTOCOL",
"slug": "soap",
"sub_category_id": 54,
"typical_lifespan": "EVERGREEN",
"volatility": "STABLE"
},
"matched_via": "alias"
},
{
"alias_persist_skipped_reason": "alias_text already exists for this canonical skill",
"alias_persisted": false,
"existing_alias_id": 868,
"existing_alias_text": "Agile",
"input_term": "Agile",
"matched_canonical": {
"category_id": 8,
"display_name": "Agile",
"id": 520,
"is_also_category": false,
"is_extractable": true,
"skill_nature": "METHODOLOGY",
"slug": "agile",
"sub_category_id": 367,
"typical_lifespan": "EVERGREEN",
"volatility": "STABLE"
},
"matched_via": "alias"
},
{
"alias_persist_skipped_reason": "alias_text already exists for this canonical skill",
"alias_persisted": false,
"existing_alias_id": 1852,
"existing_alias_text": "DevOps",
"input_term": "DevOps",
"matched_canonical": {
"category_id": 8,
"display_name": "DevOps",
"id": 1216,
"is_also_category": false,
"is_extractable": true,
"skill_nature": "METHODOLOGY",
"slug": "devops",
"sub_category_id": 922,
"typical_lifespan": "EVERGREEN",
"volatility": "STABLE"
},
"matched_via": "alias"
}
],
"candidate_roles": [
{
"display_name": "Backend Engineer",
"id": 1,
"rationale": null,
"role_archetype": "A Backend Engineer designs, builds, and maintains the server-side logic and data handling that power applications and services. They focus on implementing reliable business functionality, integrating with other systems, and ensuring the backend is scalable, maintainable, and observable.",
"slug": "backend-engineer",
"source": "db"
},
{
"display_name": "Full Stack Engineer",
"id": 15,
"rationale": null,
"role_archetype": null,
"slug": "full-stack-engineer",
"source": "db"
},
{
"display_name": "DevOps Engineer",
"id": 10,
"rationale": null,
"role_archetype": null,
"slug": "devops-engineer",
"source": "db"
},
{
"display_name": "Cloud Architect",
"id": 9,
"rationale": null,
"role_archetype": null,
"slug": "cloud-architect",
"source": "db"
}
],
"chosen_role": {
"display_name": "MuleSoft Developer",
"id": null,
"rationale": "The primary skills focus on MuleSoft and API management, which align best with a MuleSoft Developer role.",
"role_archetype": "A specialist in integrating applications and data using MuleSoft technologies.",
"slug": "mulesoft-developer",
"source": "llm"
},
"dimensions": [
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "API Design and Contracts",
"id": 3,
"rationale": "Designing request/response shapes and the rules that govern client-server interaction. This cluster is coherent because full stack engineers often own the contract between UI behavior and backend implementation.",
"slug": "api-design-and-contracts",
"source": "db"
},
"input_skill": "REST",
"llm_role": null,
"roles_from_db": [
{
"display_name": "Backend Engineer",
"id": 1,
"rationale": null,
"role_archetype": "A Backend Engineer designs, builds, and maintains the server-side logic and data handling that power applications and services. They focus on implementing reliable business functionality, integrating with other systems, and ensuring the backend is scalable, maintainable, and observable.",
"slug": "backend-engineer",
"source": "db"
},
{
"display_name": "Full Stack Engineer",
"id": 15,
"rationale": null,
"role_archetype": null,
"slug": "full-stack-engineer",
"source": "db"
}
]
},
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "External System Integrations",
"id": 14,
"rationale": "Connecting backend services to third-party APIs and internal enterprise systems. Covers client libraries, webhooks, retries, data mapping, and integration failure handling.",
"slug": "external-system-integrations",
"source": "db"
},
"input_skill": "SOAP",
"llm_role": null,
"roles_from_db": [
{
"display_name": "Backend Engineer",
"id": 1,
"rationale": null,
"role_archetype": "A Backend Engineer designs, builds, and maintains the server-side logic and data handling that power applications and services. They focus on implementing reliable business functionality, integrating with other systems, and ensuring the backend is scalable, maintainable, and observable.",
"slug": "backend-engineer",
"source": "db"
}
]
},
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "React Frontend Development",
"id": 96,
"rationale": "Building interactive web user interfaces with React.js, including component composition, state management, hooks, and rendering patterns. React.js belongs here because it is a core library for client-side UI development in modern web applications.",
"slug": "d_init_01",
"source": "db"
},
"input_skill": "Agile",
"llm_role": null,
"roles_from_db": []
},
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "CI/CD Pipeline Platforms",
"id": 150,
"rationale": "Systems used to define, run, and maintain automated build and deployment workflows. This cluster is coherent because the role owns delivery automation end to end, including pipeline reliability and promotion logic.",
"slug": "ci-cd-pipeline-platforms",
"source": "db"
},
"input_skill": "DevOps",
"llm_role": null,
"roles_from_db": [
{
"display_name": "DevOps Engineer",
"id": 10,
"rationale": null,
"role_archetype": null,
"slug": "devops-engineer",
"source": "db"
}
]
},
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Deployment and Release Patterns",
"id": 140,
"rationale": "Patterns for promoting changes safely across environments, including rollout, rollback, and release gating strategies. Cloud Architects define these patterns so teams can deploy consistently across the platform.",
"slug": "deployment-and-release-patterns",
"source": "db"
},
"input_skill": "DevOps",
"llm_role": null,
"roles_from_db": [
{
"display_name": "Cloud Architect",
"id": 9,
"rationale": null,
"role_archetype": null,
"slug": "cloud-architect",
"source": "db"
}
]
},
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Infrastructure as Code",
"id": 132,
"rationale": "Declarative provisioning and environment definition tools used to codify cloud infrastructure, repeatable environments, and platform standards. Cloud Architects use these to express reference architectures and guardrails.",
"slug": "infrastructure-as-code",
"source": "db"
},
"input_skill": "DevOps",
"llm_role": null,
"roles_from_db": [
{
"display_name": "Cloud Architect",
"id": 9,
"rationale": null,
"role_archetype": null,
"slug": "cloud-architect",
"source": "db"
},
{
"display_name": "DevOps Engineer",
"id": 10,
"rationale": null,
"role_archetype": null,
"slug": "devops-engineer",
"source": "db"
}
]
}
],
"input_final_skills": [
"MuleSoft",
"API Management",
"RAML",
"REST",
"SOAP",
"Agile",
"DevOps",
"Salesforce",
"Salesforce Workbench",
"API-led connectivity",
"Integration Patterns"
],
"input_llm_skills": [
"MuleSoft",
"API Management",
"RAML",
"REST",
"SOAP",
"Agile",
"DevOps",
"Salesforce",
"Salesforce Workbench",
"API-led connectivity",
"Integration Patterns"
],
"new_aliases_persisted": 0,
"run_id": "0a5c4054-8355-4b91-882a-9e1fcada5d8d",
"skills_detail": [
{
"aliases_in_db": [],
"canonical": null,
"dimensions": [],
"input_skill": "MuleSoft",
"matched_via": null,
"new_alias_persisted": false,
"new_alias_text": null,
"new_skill_meta": {
"derived": {
"category": "Integration Tools",
"skill_nature": "TOOL",
"sub_category": "general",
"typical_lifespan": "MULTI_YEAR",
"version_strategy": "UNVERSIONED",
"volatility": "MEDIUM"
},
"enrichment": null,
"keep_log": [],
"locked_dimensions": [],
"merge_log": [],
"placed": null,
"relationships": null,
"skill_id": "mulesoft",
"split_log": [],
"typed": null,
"warnings": []
},
"source_tag": "llm",
"was_in_llm_skills": true
},
{
"aliases_in_db": [],
"canonical": null,
"dimensions": [],
"input_skill": "API Management",
"matched_via": null,
"new_alias_persisted": false,
"new_alias_text": null,
"new_skill_meta": {
"derived": {
"category": "Concepts",
"skill_nature": "CONCEPT",
"sub_category": "general",
"typical_lifespan": "MULTI_YEAR",
"version_strategy": "UNVERSIONED",
"volatility": "MEDIUM"
},
"enrichment": null,
"keep_log": [],
"locked_dimensions": [],
"merge_log": [],
"placed": null,
"relationships": null,
"skill_id": "api-management",
"split_log": [],
"typed": null,
"warnings": []
},
"source_tag": "llm",
"was_in_llm_skills": true
},
{
"aliases_in_db": [],
"canonical": null,
"dimensions": [],
"input_skill": "RAML",
"matched_via": null,
"new_alias_persisted": false,
"new_alias_text": null,
"new_skill_meta": {
"derived": {
"category": "API Description Languages",
"skill_nature": "LANGUAGE",
"sub_category": "general",
"typical_lifespan": "MULTI_YEAR",
"version_strategy": "UNVERSIONED",
"volatility": "MEDIUM"
},
"enrichment": null,
"keep_log": [],
"locked_dimensions": [],
"merge_log": [],
"placed": null,
"relationships": null,
"skill_id": "raml",
"split_log": [],
"typed": null,
"warnings": []
},
"source_tag": "llm",
"was_in_llm_skills": true
},
{
"aliases_in_db": [
{
"alias_text": "REST",
"alias_type": "CANONICAL",
"id": 106,
"is_primary": true,
"match_strategy": "CASE_INSENSITIVE"
}
],
"canonical": {
"category_id": 10,
"display_name": "REST",
"id": 11,
"is_also_category": false,
"is_extractable": true,
"skill_nature": "PROTOCOL",
"slug": "rest",
"sub_category_id": 48,
"typical_lifespan": "EVERGREEN",
"volatility": "STABLE"
},
"dimensions": [
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "API Design and Contracts",
"id": 3,
"rationale": "Designing request/response shapes and the rules that govern client-server interaction. This cluster is coherent because full stack engineers often own the contract between UI behavior and backend implementation.",
"slug": "api-design-and-contracts",
"source": "db"
},
"input_skill": "REST",
"llm_role": null,
"roles_from_db": [
{
"display_name": "Backend Engineer",
"id": 1,
"rationale": null,
"role_archetype": "A Backend Engineer designs, builds, and maintains the server-side logic and data handling that power applications and services. They focus on implementing reliable business functionality, integrating with other systems, and ensuring the backend is scalable, maintainable, and observable.",
"slug": "backend-engineer",
"source": "db"
},
{
"display_name": "Full Stack Engineer",
"id": 15,
"rationale": null,
"role_archetype": null,
"slug": "full-stack-engineer",
"source": "db"
}
]
}
],
"input_skill": "REST",
"matched_via": "alias",
"new_alias_persisted": false,
"new_alias_text": null,
"new_skill_meta": null,
"source_tag": "db",
"was_in_llm_skills": true
},
{
"aliases_in_db": [
{
"alias_text": "SOAP",
"alias_type": "CANONICAL",
"id": 211,
"is_primary": true,
"match_strategy": "CASE_INSENSITIVE"
}
],
"canonical": {
"category_id": 10,
"display_name": "SOAP",
"id": 70,
"is_also_category": false,
"is_extractable": true,
"skill_nature": "PROTOCOL",
"slug": "soap",
"sub_category_id": 54,
"typical_lifespan": "EVERGREEN",
"volatility": "STABLE"
},
"dimensions": [
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "External System Integrations",
"id": 14,
"rationale": "Connecting backend services to third-party APIs and internal enterprise systems. Covers client libraries, webhooks, retries, data mapping, and integration failure handling.",
"slug": "external-system-integrations",
"source": "db"
},
"input_skill": "SOAP",
"llm_role": null,
"roles_from_db": [
{
"display_name": "Backend Engineer",
"id": 1,
"rationale": null,
"role_archetype": "A Backend Engineer designs, builds, and maintains the server-side logic and data handling that power applications and services. They focus on implementing reliable business functionality, integrating with other systems, and ensuring the backend is scalable, maintainable, and observable.",
"slug": "backend-engineer",
"source": "db"
}
]
}
],
"input_skill": "SOAP",
"matched_via": "alias",
"new_alias_persisted": false,
"new_alias_text": null,
"new_skill_meta": null,
"source_tag": "db",
"was_in_llm_skills": true
},
{
"aliases_in_db": [
{
"alias_text": "Agile",
"alias_type": "CANONICAL",
"id": 868,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
}
],
"canonical": {
"category_id": 8,
"display_name": "Agile",
"id": 520,
"is_also_category": false,
"is_extractable": true,
"skill_nature": "METHODOLOGY",
"slug": "agile",
"sub_category_id": 367,
"typical_lifespan": "EVERGREEN",
"volatility": "STABLE"
},
"dimensions": [
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "React Frontend Development",
"id": 96,
"rationale": "Building interactive web user interfaces with React.js, including component composition, state management, hooks, and rendering patterns. React.js belongs here because it is a core library for client-side UI development in modern web applications.",
"slug": "d_init_01",
"source": "db"
},
"input_skill": "Agile",
"llm_role": null,
"roles_from_db": []
}
],
"input_skill": "Agile",
"matched_via": "alias",
"new_alias_persisted": false,
"new_alias_text": null,
"new_skill_meta": null,
"source_tag": "db",
"was_in_llm_skills": true
},
{
"aliases_in_db": [
{
"alias_text": "DevOps",
"alias_type": "CANONICAL",
"id": 1852,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
}
],
"canonical": {
"category_id": 8,
"display_name": "DevOps",
"id": 1216,
"is_also_category": false,
"is_extractable": true,
"skill_nature": "METHODOLOGY",
"slug": "devops",
"sub_category_id": 922,
"typical_lifespan": "EVERGREEN",
"volatility": "STABLE"
},
"dimensions": [
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "CI/CD Pipeline Platforms",
"id": 150,
"rationale": "Systems used to define, run, and maintain automated build and deployment workflows. This cluster is coherent because the role owns delivery automation end to end, including pipeline reliability and promotion logic.",
"slug": "ci-cd-pipeline-platforms",
"source": "db"
},
"input_skill": "DevOps",
"llm_role": null,
"roles_from_db": [
{
"display_name": "DevOps Engineer",
"id": 10,
"rationale": null,
"role_archetype": null,
"slug": "devops-engineer",
"source": "db"
}
]
},
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Deployment and Release Patterns",
"id": 140,
"rationale": "Patterns for promoting changes safely across environments, including rollout, rollback, and release gating strategies. Cloud Architects define these patterns so teams can deploy consistently across the platform.",
"slug": "deployment-and-release-patterns",
"source": "db"
},
"input_skill": "DevOps",
"llm_role": null,
"roles_from_db": [
{
"display_name": "Cloud Architect",
"id": 9,
"rationale": null,
"role_archetype": null,
"slug": "cloud-architect",
"source": "db"
}
]
},
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Infrastructure as Code",
"id": 132,
"rationale": "Declarative provisioning and environment definition tools used to codify cloud infrastructure, repeatable environments, and platform standards. Cloud Architects use these to express reference architectures and guardrails.",
"slug": "infrastructure-as-code",
"source": "db"
},
"input_skill": "DevOps",
"llm_role": null,
"roles_from_db": [
{
"display_name": "Cloud Architect",
"id": 9,
"rationale": null,
"role_archetype": null,
"slug": "cloud-architect",
"source": "db"
},
{
"display_name": "DevOps Engineer",
"id": 10,
"rationale": null,
"role_archetype": null,
"slug": "devops-engineer",
"source": "db"
}
]
}
],
"input_skill": "DevOps",
"matched_via": "alias",
"new_alias_persisted": false,
"new_alias_text": null,
"new_skill_meta": null,
"source_tag": "db",
"was_in_llm_skills": true
},
{
"aliases_in_db": [],
"canonical": null,
"dimensions": [],
"input_skill": "Salesforce",
"matched_via": null,
"new_alias_persisted": false,
"new_alias_text": null,
"new_skill_meta": {
"derived": {
"category": "Cloud Platforms",
"skill_nature": "PLATFORM",
"sub_category": "general",
"typical_lifespan": "MULTI_YEAR",
"version_strategy": "UNVERSIONED",
"volatility": "MEDIUM"
},
"enrichment": null,
"keep_log": [],
"locked_dimensions": [],
"merge_log": [],
"placed": null,
"relationships": null,
"skill_id": "salesforce",
"split_log": [],
"typed": null,
"warnings": []
},
"source_tag": "llm",
"was_in_llm_skills": true
},
{
"aliases_in_db": [],
"canonical": null,
"dimensions": [],
"input_skill": "Salesforce Workbench",
"matched_via": null,
"new_alias_persisted": false,
"new_alias_text": null,
"new_skill_meta": {
"derived": {
"category": "Integration Tools",
"skill_nature": "TOOL",
"sub_category": "general",
"typical_lifespan": "MULTI_YEAR",
"version_strategy": "UNVERSIONED",
"volatility": "MEDIUM"
},
"enrichment": null,
"keep_log": [],
"locked_dimensions": [],
"merge_log": [],
"placed": null,
"relationships": null,
"skill_id": "salesforce-workbench",
"split_log": [],
"typed": null,
"warnings": []
},
"source_tag": "llm",
"was_in_llm_skills": true
},
{
"aliases_in_db": [],
"canonical": null,
"dimensions": [],
"input_skill": "API-led connectivity",
"matched_via": null,
"new_alias_persisted": false,
"new_alias_text": null,
"new_skill_meta": {
"derived": {
"category": "Concepts",
"skill_nature": "CONCEPT",
"sub_category": "general",
"typical_lifespan": "MULTI_YEAR",
"version_strategy": "UNVERSIONED",
"volatility": "MEDIUM"
},
"enrichment": null,
"keep_log": [],
"locked_dimensions": [],
"merge_log": [],
"placed": null,
"relationships": null,
"skill_id": "api-led-connectivity",
"split_log": [],
"typed": null,
"warnings": []
},
"source_tag": "llm",
"was_in_llm_skills": true
},
{
"aliases_in_db": [],
"canonical": null,
"dimensions": [],
"input_skill": "Integration Patterns",
"matched_via": null,
"new_alias_persisted": false,
"new_alias_text": null,
"new_skill_meta": {
"derived": {
"category": "Concepts",
"skill_nature": "CONCEPT",
"sub_category": "general",
"typical_lifespan": "MULTI_YEAR",
"version_strategy": "UNVERSIONED",
"volatility": "MEDIUM"
},
"enrichment": null,
"keep_log": [],
"locked_dimensions": [],
"merge_log": [],
"placed": null,
"relationships": null,
"skill_id": "integration-patterns",
"split_log": [],
"typed": null,
"warnings": []
},
"source_tag": "llm",
"was_in_llm_skills": true
}
],
"unmatched_skills": [
"MuleSoft",
"API Management",
"RAML",
"Salesforce",
"Salesforce Workbench",
"API-led connectivity",
"Integration Patterns"
]
}
API 3 — final-role-output
{
"chosen_role": {
"display_name": "MuleSoft Developer",
"id": null,
"rationale": "The primary skills focus on MuleSoft and API management, which align best with a MuleSoft Developer role.",
"role_archetype": "A specialist in integrating applications and data using MuleSoft technologies.",
"slug": "mulesoft-developer",
"source": "llm"
},
"chosen_role_resolution": "human_review_required",
"final_input_skills": [
{
"skill": "MuleSoft",
"tag": "new"
},
{
"skill": "API Management",
"tag": "new"
},
{
"skill": "RAML",
"tag": "new"
},
{
"skill": "REST",
"tag": "in_db"
},
{
"skill": "SOAP",
"tag": "in_db"
},
{
"skill": "Agile",
"tag": "in_db"
},
{
"skill": "DevOps",
"tag": "in_db"
},
{
"skill": "Salesforce",
"tag": "new"
},
{
"skill": "Salesforce Workbench",
"tag": "new"
},
{
"skill": "API-led connectivity",
"tag": "new"
},
{
"skill": "Integration Patterns",
"tag": "new"
}
],
"llm_cost_api1_usd": null,
"llm_cost_api2_usd": null,
"llm_cost_api3_usd": null,
"llm_cost_total_usd": null,
"persistence": {
"items": [
{
"chosen_role_id": null,
"dimension": {
"difficulty_hint": "well_known",
"display_name": "API Design and Contracts",
"id": 3,
"rationale": "Designing request/response shapes and the rules that govern client-server interaction. This cluster is coherent because full stack engineers often own the contract between UI behavior and backend implementation.",
"slug": "api-design-and-contracts",
"source": "db"
},
"dimension_id": 3,
"input_skill": "REST",
"llm_role": null,
"matched_chosen_role": false,
"outcome_line": "Existing dimension (library) \u00b7 Role\u2194dimension skipped (dimension not under chosen role)",
"role_dimension_saved": false,
"roles_from_db": [
{
"display_name": "Backend Engineer",
"id": 1,
"rationale": null,
"role_archetype": "A Backend Engineer designs, builds, and maintains the server-side logic and data handling that power applications and services. They focus on implementing reliable business functionality, integrating with other systems, and ensuring the backend is scalable, maintainable, and observable.",
"slug": "backend-engineer",
"source": "db"
},
{
"display_name": "Full Stack Engineer",
"id": 15,
"rationale": null,
"role_archetype": null,
"slug": "full-stack-engineer",
"source": "db"
}
],
"skill_dimension_saved": true,
"skill_id": 11,
"skill_tag": "in_db",
"skipped_reason": null
},
{
"chosen_role_id": null,
"dimension": {
"difficulty_hint": "well_known",
"display_name": "External System Integrations",
"id": 14,
"rationale": "Connecting backend services to third-party APIs and internal enterprise systems. Covers client libraries, webhooks, retries, data mapping, and integration failure handling.",
"slug": "external-system-integrations",
"source": "db"
},
"dimension_id": 14,
"input_skill": "SOAP",
"llm_role": null,
"matched_chosen_role": false,
"outcome_line": "Existing dimension (library) \u00b7 Role\u2194dimension skipped (dimension not under chosen role)",
"role_dimension_saved": false,
"roles_from_db": [
{
"display_name": "Backend Engineer",
"id": 1,
"rationale": null,
"role_archetype": "A Backend Engineer designs, builds, and maintains the server-side logic and data handling that power applications and services. They focus on implementing reliable business functionality, integrating with other systems, and ensuring the backend is scalable, maintainable, and observable.",
"slug": "backend-engineer",
"source": "db"
}
],
"skill_dimension_saved": true,
"skill_id": 70,
"skill_tag": "in_db",
"skipped_reason": null
},
{
"chosen_role_id": null,
"dimension": {
"difficulty_hint": "well_known",
"display_name": "React Frontend Development",
"id": 96,
"rationale": "Building interactive web user interfaces with React.js, including component composition, state management, hooks, and rendering patterns. React.js belongs here because it is a core library for client-side UI development in modern web applications.",
"slug": "d_init_01",
"source": "db"
},
"dimension_id": 96,
"input_skill": "Agile",
"llm_role": null,
"matched_chosen_role": false,
"outcome_line": "Existing dimension (library) \u00b7 Role\u2194dimension skipped (dimension not under chosen role)",
"role_dimension_saved": false,
"roles_from_db": [],
"skill_dimension_saved": true,
"skill_id": 520,
"skill_tag": "in_db",
"skipped_reason": null
},
{
"chosen_role_id": null,
"dimension": {
"difficulty_hint": "well_known",
"display_name": "CI/CD Pipeline Platforms",
"id": 150,
"rationale": "Systems used to define, run, and maintain automated build and deployment workflows. This cluster is coherent because the role owns delivery automation end to end, including pipeline reliability and promotion logic.",
"slug": "ci-cd-pipeline-platforms",
"source": "db"
},
"dimension_id": 150,
"input_skill": "DevOps",
"llm_role": null,
"matched_chosen_role": false,
"outcome_line": "Existing dimension (library) \u00b7 Role\u2194dimension skipped (dimension not under chosen role)",
"role_dimension_saved": false,
"roles_from_db": [
{
"display_name": "DevOps Engineer",
"id": 10,
"rationale": null,
"role_archetype": null,
"slug": "devops-engineer",
"source": "db"
}
],
"skill_dimension_saved": true,
"skill_id": 1216,
"skill_tag": "in_db",
"skipped_reason": null
},
{
"chosen_role_id": null,
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Deployment and Release Patterns",
"id": 140,
"rationale": "Patterns for promoting changes safely across environments, including rollout, rollback, and release gating strategies. Cloud Architects define these patterns so teams can deploy consistently across the platform.",
"slug": "deployment-and-release-patterns",
"source": "db"
},
"dimension_id": 140,
"input_skill": "DevOps",
"llm_role": null,
"matched_chosen_role": false,
"outcome_line": "Existing dimension (library) \u00b7 Role\u2194dimension skipped (dimension not under chosen role)",
"role_dimension_saved": false,
"roles_from_db": [
{
"display_name": "Cloud Architect",
"id": 9,
"rationale": null,
"role_archetype": null,
"slug": "cloud-architect",
"source": "db"
}
],
"skill_dimension_saved": true,
"skill_id": 1216,
"skill_tag": "in_db",
"skipped_reason": null
},
{
"chosen_role_id": null,
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Infrastructure as Code",
"id": 132,
"rationale": "Declarative provisioning and environment definition tools used to codify cloud infrastructure, repeatable environments, and platform standards. Cloud Architects use these to express reference architectures and guardrails.",
"slug": "infrastructure-as-code",
"source": "db"
},
"dimension_id": 132,
"input_skill": "DevOps",
"llm_role": null,
"matched_chosen_role": false,
"outcome_line": "Existing dimension (library) \u00b7 Role\u2194dimension skipped (dimension not under chosen role)",
"role_dimension_saved": false,
"roles_from_db": [
{
"display_name": "Cloud Architect",
"id": 9,
"rationale": null,
"role_archetype": null,
"slug": "cloud-architect",
"source": "db"
},
{
"display_name": "DevOps Engineer",
"id": 10,
"rationale": null,
"role_archetype": null,
"slug": "devops-engineer",
"source": "db"
}
],
"skill_dimension_saved": true,
"skill_id": 1216,
"skill_tag": "in_db",
"skipped_reason": null
}
],
"new_skills_created": 0,
"role_dimension_saved": 0,
"skill_dimension_saved": 0,
"skipped": 0
},
"planner_output": null,
"run_id": "0a5c4054-8355-4b91-882a-9e1fcada5d8d"
}
LLM Calls
Every model call made for this run, in pipeline order. Click a card to see the model's response.