Pipeline run
306c9c8a-47e8-4d43-b101-0a3c345b159d
Client output enrichment
v2 Skill cluster · Nature of work · AI index · Tech stack maturity · Evidence · KRA descriptionvocab breakdown (legacy)
Signals
Post-classification
Captured for admin review
• Design and implement integrations using MuleSoft Anypoint Platform (Anypoint Studio, API Manager, Exchange, Runtime Manager, Design Center, CloudHub 2.0). • Develop and manage microservices-based ar…
1 POST /skills/extract-from-jd
2 POST /skills/extract-details
3 POST /skills/final-role-output
MuleSoft Developer
domain · Salesforce CASE DOMAINslug: mulesoft-developer · id: 113 · source: db
Domain=Salesforce; The JD focuses heavily on MuleSoft Anypoint Platform integration design and implementation, which is the core responsibility of a MuleSoft Developer.
Matched skills
Matched dimensions
Matched KRAs
Resolution:
in_db
— role exists in library; skill↔dim and role↔dim links saved when applicable.
Job description
We are seeking a Salesforce MuleSoft / Marketing Integration Engineer to design and implement robust integration solutions connecting Salesforce platforms with marketing tools and enterprise systems. This role involves leveraging MuleSoft for API-led connectivity, ensuring seamless data flow across applications, and supporting marketing technology integrations. Key Responsibilities • Design and implement integrations using MuleSoft Anypoint Platform (Anypoint Studio, API Manager, Exchange, Runtime Manager, Design Center, CloudHub 2.0). • Develop and manage microservices-based architecture, including RESTful APIs and web services. • Configure and monitor MuleSoft APIs and connected apps for secure and scalable integrations. • Build and optimize data flows between Salesforce (including Data Cloud) and external systems. • Implement system integrations using inbuilt connectors and APIs, ensuring adherence to HTTP standards and request/response patterns (GET, POST, PUT, DELETE). • Collaborate with marketing teams to integrate tools like Salesforce Marketing Cloud, Adobe Workfront, DAM, Microsoft Teams. • Support troubleshooting, performance tuning, and monitoring of integration solutions. Required Skills & Qualifications • Strong knowledge of Microservice Architecture, REST APIs, and web services. • Hands‑on experience with MuleSoft Anypoint Studio, DataWeave, API Manager, Exchange, Runtime Manager, Design Center, and CloudHub 2.0. • Proficiency in system integration using connectors and APIs. • Working knowledge of HTTP protocols and methods. • Familiarity with Salesforce platforms and data models. Nice to Have • Experience with Salesforce Data Cloud and Data Objects using MuleSoft as an integration tool. • Exposure to marketing technology integrations (Salesforce Marketing Cloud, Adobe Workfront, DAM). • MuleSoft and Salesforce 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
- 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
- Development 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
- API Management 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
- API Management 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
- Cloud Platforms
- 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
- Design 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
- Cloud Platforms
- Sub-category
- general
- Skill nature
- PLATFORM
- Volatility
- MEDIUM
- Typical lifespan
- MULTI_YEAR
- Version strategy
- UNVERSIONED
Aliases — catalog
- microservices (CANONICAL) primary
Context tags (catalog)
Stored enrichment (catalog DB)
- Category
- Architecture
- Sub-category
- Distributed System Architecture
- Confidence
- 0.99
- Version strategy
- NOT_APPLICABLE
Maturity reasoning: Microservices is a common architecture in job descriptions across backend/cloud roles, and major vendors like AWS, Google Cloud, and Kubernetes ecosystems provide first-class support and reference patterns.
Skill profile (library / DB)
- Skill nature
- PATTERN
- Volatility
- STABLE
- Typical lifespan
- EVERGREEN
- Category id
- 1
- Sub-category id
- 1
- Extractable
- True
- Also category
- False
Dimensions (API 2 worklist)
-
Microservices and Distributed Systems Catalog dimension db id 9
Library dimension (catalog)
Roles linked in library: Backend Developer, Node.js Backend Developer, Scala Backend Developer
API 3 link attempts (this skill)
| Dimension | Skill↔dim | Role↔dim | Outcome |
|---|---|---|---|
|
Microservices and Distributed Systems
microservices-and-distributed-systems
|
✓ | — | Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role) |
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
- CONCEPT
- Volatility
- STABLE
- Typical lifespan
- EVERGREEN
- Category id
- 2
- Sub-category id
- 2122
- 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 Developer, Fullstack Developer, Fullstack Developer
-
API Interface and Contract Design Catalog dimension db id 289
Library dimension (catalog)
Roles linked in library: .NET Backend Developer, Go Backend Developer, Kotlin Backend Developer, Node.js Backend Developer, PHP Backend Developer, Python Backend Developer, Ruby Backend Developer, Scala Backend Developer
-
Integration Protocols & Standards Catalog dimension db id 271
Library dimension (catalog)
Roles linked in library: Pega Developer
-
Standards, Protocols & Compliance Catalog dimension db id 452
Library dimension (catalog)
Roles linked in library: Engineering Manager, Sitecore Dev
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) |
|
API Interface and Contract Design
api-interface-and-contract-design
|
✓ | — | Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role) |
|
Integration Protocols & Standards
integration-protocols-standards
|
✓ | — | Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role) |
|
Standards, Protocols & Compliance
standards-protocols-compliance
|
✓ | — | Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role) |
Aliases — catalog
- Salesforce (CANONICAL) primary
Context tags (catalog)
Stored enrichment (catalog DB)
- Category
- Platform
- Sub-category
- Saas Platform
- Vendor
- Salesforce, Inc.
- License
- proprietary
- Year introduced
- 1999
- Confidence
- 0.99
- Version strategy
- NOT_APPLICABLE
Maturity reasoning: Salesforce appears in large volumes of enterprise job postings across sales, admin, and developer roles, and its AppExchange/ecosystem remains actively supported by the vendor.
Skill profile (library / DB)
- Skill nature
- PLATFORM
- Volatility
- STABLE
- Typical lifespan
- EVERGREEN
- Category id
- 9
- Sub-category id
- 3633
- Extractable
- True
- Also category
- False
Dimensions (API 2 worklist)
-
Vendor Product Families Catalog dimension db id 477
Library dimension (catalog)
Roles linked in library: Engineering Manager
API 3 link attempts (this skill)
| Dimension | Skill↔dim | Role↔dim | Outcome |
|---|---|---|---|
|
Vendor Product Families
vendor-product-families
|
✓ | — | 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
- Data Transformation Tools
- Sub-category
- general
- Skill nature
- TOOL
- Volatility
- MEDIUM
- Typical lifespan
- MULTI_YEAR
- Version strategy
- UNVERSIONED
Aliases — catalog
- HTTP (CANONICAL) primary
Context tags (catalog)
Stored enrichment (catalog DB)
- Category
- Protocol
- Sub-category
- Application Protocol
- Confidence
- 0.99
- Version strategy
- NOT_APPLICABLE
Maturity reasoning: HTTP is a foundational web protocol present in nearly all backend/frontend JDs and cloud docs; it underpins REST APIs and browser traffic, with no successor replacing it.
Skill profile (library / DB)
- Skill nature
- PROTOCOL
- Volatility
- STABLE
- Typical lifespan
- EVERGREEN
- Category id
- 10
- Sub-category id
- 710
- Extractable
- True
- Also category
- False
Dimensions (API 2 worklist)
-
Networking and API Integration Catalog dimension db id 84
Library dimension (catalog)
Roles linked in library: Android Developer, Hybrid Mobile Developer, Native Mobile Developer, iOS Developer
API 3 link attempts (this skill)
| Dimension | Skill↔dim | Role↔dim | Outcome |
|---|---|---|---|
|
Networking and API Integration
networking-and-api-integration
|
✓ | — | 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
- Project Management 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
- Digital Asset Management 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
- Collaboration Tools
- Sub-category
- general
- Skill nature
- PLATFORM
- 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 |
|---|---|---|---|---|---|---|
| Microservices | in_db |
Microservices and Distributed Systems
microservices-and-distributed-systems
|
✓ | — | Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role) | |
| REST | in_db |
API Design and Contracts
api-design-and-contracts
|
✓ | — | Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role) | |
| REST | in_db |
API Interface and Contract Design
api-interface-and-contract-design
|
✓ | — | Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role) | |
| REST | in_db |
Integration Protocols & Standards
integration-protocols-standards
|
✓ | — | Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role) | |
| REST | in_db |
Standards, Protocols & Compliance
standards-protocols-compliance
|
✓ | — | Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role) | |
| Salesforce | in_db |
Vendor Product Families
vendor-product-families
|
✓ | — | Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role) | |
| HTTP | in_db |
Networking and API Integration
networking-and-api-integration
|
✓ | — | Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role) |
Library artifacts (this run)
| Kind | Detail | DB id |
|---|---|---|
| canonical_skill_proposed | MuleSoft Anypoint Platform | type=Cloud Platforms subtype=general nature=PLATFORM lifespan=MULTI_YEAR | |
| canonical_skill_proposed | Anypoint Studio | type=Development Tools subtype=general nature=TOOL lifespan=MULTI_YEAR | |
| canonical_skill_proposed | API Manager | type=API Management subtype=general nature=TOOL lifespan=MULTI_YEAR | |
| canonical_skill_proposed | Exchange | type=API Management subtype=general nature=TOOL lifespan=MULTI_YEAR | |
| canonical_skill_proposed | Runtime Manager | type=Cloud Platforms subtype=general nature=TOOL lifespan=MULTI_YEAR | |
| canonical_skill_proposed | Design Center | type=Development Tools subtype=general nature=TOOL lifespan=MULTI_YEAR | |
| canonical_skill_proposed | CloudHub 2.0 | type=Cloud Platforms subtype=general nature=PLATFORM lifespan=MULTI_YEAR | |
| canonical_skill_proposed | Data Cloud | type=Cloud Platforms subtype=general nature=PLATFORM lifespan=MULTI_YEAR | |
| canonical_skill_proposed | DataWeave | type=Data Transformation subtype=general nature=LANGUAGE lifespan=MULTI_YEAR | |
| canonical_skill_proposed | Salesforce Marketing Cloud | type=Cloud Platforms subtype=general nature=PLATFORM lifespan=MULTI_YEAR | |
| canonical_skill_proposed | Adobe Workfront | type=Project Management Tools subtype=general nature=TOOL lifespan=MULTI_YEAR | |
| canonical_skill_proposed | DAM | type=Digital Asset Management subtype=general nature=CONCEPT lifespan=MULTI_YEAR | |
| canonical_skill_proposed | Microsoft Teams | type=Collaboration Tools subtype=general nature=PLATFORM lifespan=MULTI_YEAR | |
| canonical_skill_proposed | MuleSoft Anypoint Platform | type=Cloud Platforms subtype=general nature=PLATFORM lifespan=MULTI_YEAR | |
| canonical_skill_proposed | Anypoint Studio | type=Development Tools subtype=general nature=TOOL lifespan=MULTI_YEAR | |
| canonical_skill_proposed | API Manager | type=API Management Tools subtype=general nature=TOOL lifespan=MULTI_YEAR | |
| canonical_skill_proposed | Exchange | type=API Management Tools subtype=general nature=TOOL lifespan=MULTI_YEAR | |
| canonical_skill_proposed | Runtime Manager | type=Cloud Platforms subtype=general nature=TOOL lifespan=MULTI_YEAR | |
| canonical_skill_proposed | Design Center | type=Design Tools subtype=general nature=TOOL lifespan=MULTI_YEAR | |
| canonical_skill_proposed | CloudHub 2.0 | type=Cloud Platforms subtype=general nature=PLATFORM lifespan=MULTI_YEAR | |
| canonical_skill_proposed | Data Cloud | type=Cloud Platforms subtype=general nature=PLATFORM lifespan=MULTI_YEAR | |
| canonical_skill_proposed | DataWeave | type=Data Transformation Tools subtype=general nature=TOOL lifespan=MULTI_YEAR | |
| canonical_skill_proposed | Salesforce Marketing Cloud | type=Cloud Platforms subtype=general nature=PLATFORM lifespan=MULTI_YEAR | |
| canonical_skill_proposed | Adobe Workfront | type=Project Management Tools subtype=general nature=TOOL lifespan=MULTI_YEAR | |
| canonical_skill_proposed | DAM | type=Digital Asset Management Tools subtype=general nature=TOOL lifespan=MULTI_YEAR | |
| canonical_skill_proposed | Microsoft Teams | type=Collaboration Tools subtype=general nature=PLATFORM lifespan=MULTI_YEAR |
nano JD Parser — gpt-4.1-nano click to toggle
Certifications
Show raw JSON
{
"JD_type": "pass",
"about_company": null,
"ai_kras": [],
"certifications": [
"MuleSoft certifications",
"Salesforce certifications"
],
"company_name": null,
"ctc": null,
"domain": {
"primary": {
"aliases": [],
"domain": "IT Services \u0026 Consulting"
},
"secondary": null
},
"education": [],
"experience": {
"max": null,
"min": null,
"raw": null
},
"job_locations": [],
"role": "Salesforce MuleSoft / Marketing Integration Engineer",
"role_aliases": [
{
"name": "MuleSoft Integration Engineer",
"reasoning": "specific role focusing on MuleSoft integrations",
"relation": "synonym"
},
{
"name": "Integration Engineer",
"reasoning": "role involves integration work across platforms",
"relation": "adjacent"
},
{
"name": "Salesforce Integration Engineer",
"reasoning": "role focuses on Salesforce platform integrations",
"relation": "adjacent"
}
],
"role_archetype": "Engineering",
"roles_and_responsibilities": [
{
"bullet_count": 7,
"heading": "Key Responsibilities",
"heading_was_present": true,
"source_marker": {
"first_5_words": "\u2022 Design and implement integrations",
"last_5_words": "performance tuning, and monitoring of"
},
"text": "\u2022 Design and implement integrations using MuleSoft Anypoint Platform (Anypoint Studio, API Manager, Exchange, Runtime Manager, Design Center, CloudHub 2.0).\n\u2022 Develop and manage microservices-based architecture, including RESTful APIs and web services.\n\u2022 Configure and monitor MuleSoft APIs and connected apps for secure and scalable integrations.\n\u2022 Build and optimize data flows between Salesforce (including Data Cloud) and external systems.\n\u2022 Implement system integrations using inbuilt connectors and APIs, ensuring adherence to HTTP standards and request/response patterns (GET, POST, PUT, DELETE).\n\u2022 Collaborate with marketing teams to integrate tools like Salesforce Marketing Cloud, Adobe Workfront, DAM, Microsoft Teams.\n\u2022 Support troubleshooting, performance tuning, and monitoring of integration solutions.",
"word_count": 104
},
{
"bullet_count": 5,
"heading": "Required Skills \u0026 Qualifications",
"heading_was_present": true,
"source_marker": {
"first_5_words": "\u2022 Strong knowledge of Microservice",
"last_5_words": "Salesforce platforms and data models."
},
"text": "\u2022 Strong knowledge of Microservice Architecture, REST APIs, and web services.\n\u2022 Hands\u2011on experience with MuleSoft Anypoint Studio, DataWeave, API Manager, Exchange, Runtime Manager, Design Center, and CloudHub 2.0.\n\u2022 Proficiency in system integration using connectors and APIs.\n\u2022 Working knowledge of HTTP protocols and methods.\n\u2022 Familiarity with Salesforce platforms and data models.",
"word_count": 66
},
{
"bullet_count": 3,
"heading": "Nice to Have",
"heading_was_present": true,
"source_marker": {
"first_5_words": "\u2022 Experience with Salesforce Data",
"last_5_words": "MuleSoft and Salesforce certifications."
},
"text": "\u2022 Experience with Salesforce Data Cloud and Data Objects using MuleSoft as an integration tool.\n\u2022 Exposure to marketing technology integrations (Salesforce Marketing Cloud, Adobe Workfront, DAM).\n\u2022 MuleSoft and Salesforce certifications.",
"word_count": 36
}
],
"urls": []
}
API 1 — extract-from-jd click to toggle
{
"final_skills": [
{
"is_primary": true,
"skill_name": "MuleSoft Anypoint Platform"
},
{
"is_primary": true,
"skill_name": "Anypoint Studio"
},
{
"is_primary": true,
"skill_name": "API Manager"
},
{
"is_primary": true,
"skill_name": "Exchange"
},
{
"is_primary": true,
"skill_name": "Runtime Manager"
},
{
"is_primary": true,
"skill_name": "Design Center"
},
{
"is_primary": true,
"skill_name": "CloudHub 2.0"
},
{
"is_primary": true,
"skill_name": "Microservices"
},
{
"is_primary": true,
"skill_name": "REST"
},
{
"is_primary": true,
"skill_name": "Salesforce"
},
{
"is_primary": true,
"skill_name": "Data Cloud"
},
{
"is_primary": true,
"skill_name": "DataWeave"
},
{
"is_primary": true,
"skill_name": "HTTP"
},
{
"is_primary": false,
"skill_name": "Salesforce Marketing Cloud"
},
{
"is_primary": false,
"skill_name": "Adobe Workfront"
},
{
"is_primary": false,
"skill_name": "DAM"
},
{
"is_primary": false,
"skill_name": "Microsoft Teams"
}
],
"jd_role": {
"display_name": "Salesforce MuleSoft / Marketing Integration Engineer",
"rationale": null,
"role_aliases": [
"MuleSoft Integration Engineer",
"Integration Engineer",
"Salesforce Integration Engineer"
],
"role_archetype": "Engineering",
"slug": ""
},
"nano_parsed": {
"JD_type": "pass",
"about_company": null,
"ai_kras": [],
"certifications": [
"MuleSoft certifications",
"Salesforce certifications"
],
"company_name": null,
"ctc": null,
"domain": {
"primary": {
"aliases": [],
"domain": "IT Services \u0026 Consulting"
},
"secondary": null
},
"education": [],
"experience": {
"max": null,
"min": null,
"raw": null
},
"job_locations": [],
"role": "Salesforce MuleSoft / Marketing Integration Engineer",
"role_aliases": [
{
"name": "MuleSoft Integration Engineer",
"reasoning": "specific role focusing on MuleSoft integrations",
"relation": "synonym"
},
{
"name": "Integration Engineer",
"reasoning": "role involves integration work across platforms",
"relation": "adjacent"
},
{
"name": "Salesforce Integration Engineer",
"reasoning": "role focuses on Salesforce platform integrations",
"relation": "adjacent"
}
],
"role_archetype": "Engineering",
"roles_and_responsibilities": [
{
"bullet_count": 7,
"heading": "Key Responsibilities",
"heading_was_present": true,
"source_marker": {
"first_5_words": "\u2022 Design and implement integrations",
"last_5_words": "performance tuning, and monitoring of"
},
"text": "\u2022 Design and implement integrations using MuleSoft Anypoint Platform (Anypoint Studio, API Manager, Exchange, Runtime Manager, Design Center, CloudHub 2.0).\n\u2022 Develop and manage microservices-based architecture, including RESTful APIs and web services.\n\u2022 Configure and monitor MuleSoft APIs and connected apps for secure and scalable integrations.\n\u2022 Build and optimize data flows between Salesforce (including Data Cloud) and external systems.\n\u2022 Implement system integrations using inbuilt connectors and APIs, ensuring adherence to HTTP standards and request/response patterns (GET, POST, PUT, DELETE).\n\u2022 Collaborate with marketing teams to integrate tools like Salesforce Marketing Cloud, Adobe Workfront, DAM, Microsoft Teams.\n\u2022 Support troubleshooting, performance tuning, and monitoring of integration solutions.",
"word_count": 104
},
{
"bullet_count": 5,
"heading": "Required Skills \u0026 Qualifications",
"heading_was_present": true,
"source_marker": {
"first_5_words": "\u2022 Strong knowledge of Microservice",
"last_5_words": "Salesforce platforms and data models."
},
"text": "\u2022 Strong knowledge of Microservice Architecture, REST APIs, and web services.\n\u2022 Hands\u2011on experience with MuleSoft Anypoint Studio, DataWeave, API Manager, Exchange, Runtime Manager, Design Center, and CloudHub 2.0.\n\u2022 Proficiency in system integration using connectors and APIs.\n\u2022 Working knowledge of HTTP protocols and methods.\n\u2022 Familiarity with Salesforce platforms and data models.",
"word_count": 66
},
{
"bullet_count": 3,
"heading": "Nice to Have",
"heading_was_present": true,
"source_marker": {
"first_5_words": "\u2022 Experience with Salesforce Data",
"last_5_words": "MuleSoft and Salesforce certifications."
},
"text": "\u2022 Experience with Salesforce Data Cloud and Data Objects using MuleSoft as an integration tool.\n\u2022 Exposure to marketing technology integrations (Salesforce Marketing Cloud, Adobe Workfront, DAM).\n\u2022 MuleSoft and Salesforce certifications.",
"word_count": 36
}
],
"urls": []
},
"rejected": false,
"rejection_reason": null,
"run_id": "306c9c8a-47e8-4d43-b101-0a3c345b159d",
"stage3_signals": {
"alias_found": false,
"alias_match_roles": [],
"kra_match_roles": [
{
"display_name": "Backend Developer",
"kra_matches": [
{
"kra_text": "Integrates with third-party services, payment gateways, messaging queues like Kafka or RabbitMQ, and internal microservices via HTTP and event-driven patterns.",
"sentence": "Implement system integrations using inbuilt connectors and APIs, ensuring adherence to HTTP standards and request/response patterns (GET, POST, PUT, DELETE).",
"similarity": 0.631
},
{
"kra_text": "Implements server-side business logic, REST API endpoints, and microservice handlers using Java, Python, Go, or Node.js to process application requests and enforce business rules.",
"sentence": "Develop and manage microservices-based architecture, including RESTful APIs and web services.",
"similarity": 0.5659
},
{
"kra_text": "Identifies and resolves backend performance bottlenecks through query optimization, indexing strategies, connection pooling, and distributed caching with Redis.",
"sentence": "Support troubleshooting, performance tuning, and monitoring of integration solutions.",
"similarity": 0.5355
}
],
"matched_count": null,
"matched_skills": null,
"role_id": 1,
"score": 0.5775,
"slug": "backend-engineer",
"total_count": null
},
{
"display_name": "Flutter Developer",
"kra_matches": [
{
"kra_text": "collaborate with design, product, and backend teams",
"sentence": "Collaborate with marketing teams to integrate tools like Salesforce Marketing Cloud, Adobe Workfront, DAM, Microsoft Teams.",
"similarity": 0.575
},
{
"kra_text": "integrate external APIs and data sources",
"sentence": "Implement system integrations using inbuilt connectors and APIs, ensuring adherence to HTTP standards and request/response patterns (GET, POST, PUT, DELETE).",
"similarity": 0.5289
},
{
"kra_text": "integrate external APIs and data sources",
"sentence": "Build and optimize data flows between Salesforce (including Data Cloud) and external systems.",
"similarity": 0.4974
}
],
"matched_count": null,
"matched_skills": null,
"role_id": 74,
"score": 0.5338,
"slug": "flutter-developer",
"total_count": null
},
{
"display_name": "Ionic Developer",
"kra_matches": [
{
"kra_text": "service and API integration",
"sentence": "Implement system integrations using inbuilt connectors and APIs, ensuring adherence to HTTP standards and request/response patterns (GET, POST, PUT, DELETE).",
"similarity": 0.5366
},
{
"kra_text": "service and API integration",
"sentence": "Develop and manage microservices-based architecture, including RESTful APIs and web services.",
"similarity": 0.5345
},
{
"kra_text": "service and API integration",
"sentence": "Configure and monitor MuleSoft APIs and connected apps for secure and scalable integrations.",
"similarity": 0.5282
}
],
"matched_count": null,
"matched_skills": null,
"role_id": 434,
"score": 0.5331,
"slug": "ionic-developer",
"total_count": null
},
{
"display_name": "PHP Backend Developer",
"kra_matches": [
{
"kra_text": "performance and reliability tuning",
"sentence": "Support troubleshooting, performance tuning, and monitoring of integration solutions.",
"similarity": 0.555
},
{
"kra_text": "external system integration",
"sentence": "Implement system integrations using inbuilt connectors and APIs, ensuring adherence to HTTP standards and request/response patterns (GET, POST, PUT, DELETE).",
"similarity": 0.5427
},
{
"kra_text": "API and service contract support",
"sentence": "Develop and manage microservices-based architecture, including RESTful APIs and web services.",
"similarity": 0.4796
}
],
"matched_count": null,
"matched_skills": null,
"role_id": 86,
"score": 0.5258,
"slug": "php-backend-developer",
"total_count": null
},
{
"display_name": "Java Backend Developer",
"kra_matches": [
{
"kra_text": "backend performance tuning",
"sentence": "Support troubleshooting, performance tuning, and monitoring of integration solutions.",
"similarity": 0.547
},
{
"kra_text": "external system integration",
"sentence": "Implement system integrations using inbuilt connectors and APIs, ensuring adherence to HTTP standards and request/response patterns (GET, POST, PUT, DELETE).",
"similarity": 0.5427
},
{
"kra_text": "service endpoint development",
"sentence": "Develop and manage microservices-based architecture, including RESTful APIs and web services.",
"similarity": 0.4578
}
],
"matched_count": null,
"matched_skills": null,
"role_id": 79,
"score": 0.5158,
"slug": "java-backend-developer",
"total_count": null
}
],
"skill_match_roles": [
{
"display_name": "Scala Backend Developer",
"kra_matches": null,
"matched_count": 2,
"matched_skills": [
"REST",
"microservices"
],
"role_id": 87,
"score": 0.1538,
"slug": "scala-backend-developer",
"total_count": 13
},
{
"display_name": "Engineering Manager",
"kra_matches": null,
"matched_count": 2,
"matched_skills": [
"REST",
"Salesforce"
],
"role_id": 121,
"score": 0.1538,
"slug": "engineering-manager",
"total_count": 13
},
{
"display_name": "Backend Developer",
"kra_matches": null,
"matched_count": 2,
"matched_skills": [
"REST",
"microservices"
],
"role_id": 1,
"score": 0.1538,
"slug": "backend-engineer",
"total_count": 13
},
{
"display_name": "Node.js Backend Developer",
"kra_matches": null,
"matched_count": 2,
"matched_skills": [
"REST",
"microservices"
],
"role_id": 82,
"score": 0.1538,
"slug": "node-backend-developer",
"total_count": 13
},
{
"display_name": "iOS Developer",
"kra_matches": null,
"matched_count": 1,
"matched_skills": [
"HTTP"
],
"role_id": 6,
"score": 0.0769,
"slug": "ios-engineer",
"total_count": 13
}
]
},
"stage4_decision": {
"alias_collision_detected": false,
"case": "DOMAIN",
"chosen_role": {
"display_name": "MuleSoft Developer",
"kra_matches": null,
"matched_count": null,
"matched_skills": null,
"role_id": 113,
"score": 0.95,
"slug": "mulesoft-developer",
"total_count": null
},
"confidence": 0.95,
"consensus_evidence": {},
"is_new_role": false,
"llm2_fired": false,
"llm2_reasoning": null,
"matched_dimensions": [
"Integration Architecture \u0026 Design",
"API Management \u0026 Governance",
"Microservices Development",
"Data Flow Optimization",
"Marketing Technology Integration",
"System Troubleshooting \u0026 Performance Tuning"
],
"matched_kras": [
"Design and implement integrations using MuleSoft Anypoint Platform",
"Develop and manage microservices-based architecture",
"Configure and monitor MuleSoft APIs and connected apps",
"Build and optimize data flows between Salesforce and external systems",
"Implement system integrations using inbuilt connectors and APIs",
"Collaborate with marketing teams to integrate tools",
"Support troubleshooting, performance tuning, and monitoring"
],
"matched_skills": [
"MuleSoft Anypoint Platform",
"Anypoint Studio",
"API Manager",
"Exchange",
"Runtime Manager",
"Design Center",
"CloudHub 2.0",
"DataWeave",
"RESTful APIs",
"Microservice Architecture",
"Salesforce Data Cloud",
"Salesforce Marketing Cloud",
"Adobe Workfront",
"HTTP protocols",
"Data Objects"
],
"new_role_display_name": null,
"new_role_domain": null,
"new_role_slug": null,
"queued": false,
"reasoning": "Domain=Salesforce; The JD focuses heavily on MuleSoft Anypoint Platform integration design and implementation, which is the core responsibility of a MuleSoft Developer.",
"role_aliases": [
{
"name": "Salesforce MuleSoft Integration Architect",
"reason": "The JD includes design and architecture of integrations, aligning with an architect role.",
"relation": "synonym"
},
{
"name": "Salesforce Marketing Cloud Consultant",
"reason": "The JD mentions marketing tool integrations (Marketing Cloud, Adobe Workfront) which overlap with that role.",
"relation": "adjacent"
}
],
"sub_role": null
},
"stage5_updates": {
"centroid_n_after": 2,
"centroid_updated": true,
"collision_log_id": null,
"new_kra_attached": {
"best_kra_similarity": 0.0,
"queue_id": 2036,
"r_and_r_preview": "\u2022 Design and implement integrations using MuleSoft Anypoint Platform (Anypoint Studio, API Manager, Exchange, Runtime Manager, Design Center, CloudHub 2.0).\n\u2022 Develop and manage microservices-based ar",
"role_display_name": "MuleSoft Developer",
"role_slug": "mulesoft-developer",
"status": "pending"
},
"new_skills_attached": [
{
"is_primary": true,
"queue_id": 26027,
"role_display_name": "MuleSoft Developer",
"role_slug": "mulesoft-developer",
"skill_name": "MuleSoft Anypoint Platform",
"status": "pending"
},
{
"is_primary": true,
"queue_id": 26028,
"role_display_name": "MuleSoft Developer",
"role_slug": "mulesoft-developer",
"skill_name": "Anypoint Studio",
"status": "pending"
},
{
"is_primary": true,
"queue_id": 26029,
"role_display_name": "MuleSoft Developer",
"role_slug": "mulesoft-developer",
"skill_name": "API Manager",
"status": "pending"
},
{
"is_primary": true,
"queue_id": 26030,
"role_display_name": "MuleSoft Developer",
"role_slug": "mulesoft-developer",
"skill_name": "Exchange",
"status": "pending"
},
{
"is_primary": true,
"queue_id": 26031,
"role_display_name": "MuleSoft Developer",
"role_slug": "mulesoft-developer",
"skill_name": "Runtime Manager",
"status": "pending"
},
{
"is_primary": true,
"queue_id": 26032,
"role_display_name": "MuleSoft Developer",
"role_slug": "mulesoft-developer",
"skill_name": "Design Center",
"status": "pending"
},
{
"is_primary": true,
"queue_id": 26033,
"role_display_name": "MuleSoft Developer",
"role_slug": "mulesoft-developer",
"skill_name": "CloudHub 2.0",
"status": "pending"
},
{
"is_primary": true,
"queue_id": 26034,
"role_display_name": "MuleSoft Developer",
"role_slug": "mulesoft-developer",
"skill_name": "Data Cloud",
"status": "pending"
},
{
"is_primary": true,
"queue_id": 26035,
"role_display_name": "MuleSoft Developer",
"role_slug": "mulesoft-developer",
"skill_name": "DataWeave",
"status": "pending"
},
{
"is_primary": false,
"queue_id": 26036,
"role_display_name": "MuleSoft Developer",
"role_slug": "mulesoft-developer",
"skill_name": "Salesforce Marketing Cloud",
"status": "pending"
},
{
"is_primary": false,
"queue_id": 26037,
"role_display_name": "MuleSoft Developer",
"role_slug": "mulesoft-developer",
"skill_name": "Adobe Workfront",
"status": "pending"
},
{
"is_primary": false,
"queue_id": 26038,
"role_display_name": "MuleSoft Developer",
"role_slug": "mulesoft-developer",
"skill_name": "DAM",
"status": "pending"
},
{
"is_primary": false,
"queue_id": 26039,
"role_display_name": "MuleSoft Developer",
"role_slug": "mulesoft-developer",
"skill_name": "Microsoft Teams",
"status": "pending"
}
],
"queue_entry_id": null,
"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": 178,
"existing_alias_text": "microservices",
"input_term": "Microservices",
"matched_canonical": {
"category_id": 1,
"display_name": "microservices",
"id": 41,
"is_also_category": false,
"is_extractable": true,
"skill_nature": "PATTERN",
"slug": "microservices",
"sub_category_id": 1,
"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": 106,
"existing_alias_text": "REST",
"input_term": "REST",
"matched_canonical": {
"category_id": 2,
"display_name": "REST",
"id": 11,
"is_also_category": false,
"is_extractable": true,
"skill_nature": "CONCEPT",
"slug": "rest",
"sub_category_id": 2122,
"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": 6567,
"existing_alias_text": "Salesforce",
"input_term": "Salesforce",
"matched_canonical": {
"category_id": 9,
"display_name": "Salesforce",
"id": 4632,
"is_also_category": false,
"is_extractable": true,
"skill_nature": "PLATFORM",
"slug": "salesforce",
"sub_category_id": 3633,
"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": 1538,
"existing_alias_text": "HTTP",
"input_term": "HTTP",
"matched_canonical": {
"category_id": 10,
"display_name": "HTTP",
"id": 935,
"is_also_category": false,
"is_extractable": true,
"skill_nature": "PROTOCOL",
"slug": "http",
"sub_category_id": 710,
"typical_lifespan": "EVERGREEN",
"volatility": "STABLE"
},
"matched_via": "alias"
}
],
"candidate_roles": [
{
"display_name": "Backend Developer",
"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": "Node.js Backend Developer",
"id": 82,
"rationale": null,
"role_archetype": "Engineering",
"slug": "node-backend-developer",
"source": "db"
},
{
"display_name": "Scala Backend Developer",
"id": 87,
"rationale": null,
"role_archetype": "Engineering",
"slug": "scala-backend-developer",
"source": "db"
},
{
"display_name": "Fullstack Developer",
"id": 435,
"rationale": null,
"role_archetype": "Engineering",
"slug": "fullstack-developer",
"source": "db"
},
{
"display_name": "Fullstack Developer",
"id": 15,
"rationale": null,
"role_archetype": null,
"slug": "full-stack-engineer",
"source": "db"
},
{
"display_name": ".NET Backend Developer",
"id": 83,
"rationale": null,
"role_archetype": "Engineering",
"slug": "dotnet-backend-developer",
"source": "db"
},
{
"display_name": "Go Backend Developer",
"id": 81,
"rationale": null,
"role_archetype": "Engineering",
"slug": "go-backend-developer",
"source": "db"
},
{
"display_name": "Kotlin Backend Developer",
"id": 84,
"rationale": null,
"role_archetype": "Engineering",
"slug": "kotlin-server-backend-developer",
"source": "db"
},
{
"display_name": "PHP Backend Developer",
"id": 86,
"rationale": null,
"role_archetype": "Engineering",
"slug": "php-backend-developer",
"source": "db"
},
{
"display_name": "Python Backend Developer",
"id": 80,
"rationale": null,
"role_archetype": "Engineering",
"slug": "python-backend-developer",
"source": "db"
},
{
"display_name": "Ruby Backend Developer",
"id": 85,
"rationale": null,
"role_archetype": "Engineering",
"slug": "ruby-backend-developer",
"source": "db"
},
{
"display_name": "Pega Developer",
"id": 24,
"rationale": null,
"role_archetype": null,
"slug": "pega-developer",
"source": "db"
},
{
"display_name": "Engineering Manager",
"id": 121,
"rationale": null,
"role_archetype": null,
"slug": "engineering-manager",
"source": "db"
},
{
"display_name": "Sitecore Dev",
"id": 233,
"rationale": null,
"role_archetype": "Engineering",
"slug": "sitecore-dev",
"source": "db"
},
{
"display_name": "Android Developer",
"id": 4,
"rationale": null,
"role_archetype": null,
"slug": "android-engineer",
"source": "db"
},
{
"display_name": "Hybrid Mobile Developer",
"id": 11,
"rationale": null,
"role_archetype": null,
"slug": "hybrid-mobile-developer",
"source": "db"
},
{
"display_name": "Native Mobile Developer",
"id": 75,
"rationale": null,
"role_archetype": "Engineering",
"slug": "native-mobile-developer",
"source": "db"
},
{
"display_name": "iOS Developer",
"id": 6,
"rationale": null,
"role_archetype": null,
"slug": "ios-engineer",
"source": "db"
}
],
"chosen_role": {
"display_name": "MuleSoft Developer",
"id": 113,
"rationale": "Domain=Salesforce; The JD focuses heavily on MuleSoft Anypoint Platform integration design and implementation, which is the core responsibility of a MuleSoft Developer.",
"role_archetype": null,
"slug": "mulesoft-developer",
"source": "db"
},
"dimensions": [
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Microservices and Distributed Systems",
"id": 9,
"rationale": "Architectural patterns for decomposed backend systems and the operational concerns they introduce. Covers service boundaries, consistency tradeoffs, retries, circuit breakers, and distributed coordination.",
"slug": "microservices-and-distributed-systems",
"source": "db"
},
"input_skill": "Microservices",
"llm_role": null,
"roles_from_db": [
{
"display_name": "Backend Developer",
"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": "Node.js Backend Developer",
"id": 82,
"rationale": null,
"role_archetype": "Engineering",
"slug": "node-backend-developer",
"source": "db"
},
{
"display_name": "Scala Backend Developer",
"id": 87,
"rationale": null,
"role_archetype": "Engineering",
"slug": "scala-backend-developer",
"source": "db"
}
]
},
{
"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 Developer",
"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": "Fullstack Developer",
"id": 435,
"rationale": null,
"role_archetype": "Engineering",
"slug": "fullstack-developer",
"source": "db"
},
{
"display_name": "Fullstack Developer",
"id": 15,
"rationale": null,
"role_archetype": null,
"slug": "full-stack-engineer",
"source": "db"
}
]
},
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "API Interface and Contract Design",
"id": 289,
"rationale": "Designing backend service interfaces and contracts that other systems consume, including endpoint and operation shape, request/response payloads, schema and validation, pagination, filtering, idempotency, versioning, status codes, and backward compatibility across REST, GraphQL, gRPC, and OpenAPI-based APIs.",
"slug": "api-interface-and-contract-design",
"source": "db"
},
"input_skill": "REST",
"llm_role": null,
"roles_from_db": [
{
"display_name": ".NET Backend Developer",
"id": 83,
"rationale": null,
"role_archetype": "Engineering",
"slug": "dotnet-backend-developer",
"source": "db"
},
{
"display_name": "Go Backend Developer",
"id": 81,
"rationale": null,
"role_archetype": "Engineering",
"slug": "go-backend-developer",
"source": "db"
},
{
"display_name": "Kotlin Backend Developer",
"id": 84,
"rationale": null,
"role_archetype": "Engineering",
"slug": "kotlin-server-backend-developer",
"source": "db"
},
{
"display_name": "Node.js Backend Developer",
"id": 82,
"rationale": null,
"role_archetype": "Engineering",
"slug": "node-backend-developer",
"source": "db"
},
{
"display_name": "PHP Backend Developer",
"id": 86,
"rationale": null,
"role_archetype": "Engineering",
"slug": "php-backend-developer",
"source": "db"
},
{
"display_name": "Python Backend Developer",
"id": 80,
"rationale": null,
"role_archetype": "Engineering",
"slug": "python-backend-developer",
"source": "db"
},
{
"display_name": "Ruby Backend Developer",
"id": 85,
"rationale": null,
"role_archetype": "Engineering",
"slug": "ruby-backend-developer",
"source": "db"
},
{
"display_name": "Scala Backend Developer",
"id": 87,
"rationale": null,
"role_archetype": "Engineering",
"slug": "scala-backend-developer",
"source": "db"
}
]
},
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Integration Protocols \u0026 Standards",
"id": 271,
"rationale": "Standards and protocols for integrating Pega applications.",
"slug": "integration-protocols-standards",
"source": "db"
},
"input_skill": "REST",
"llm_role": null,
"roles_from_db": [
{
"display_name": "Pega Developer",
"id": 24,
"rationale": null,
"role_archetype": null,
"slug": "pega-developer",
"source": "db"
}
]
},
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Standards, Protocols \u0026 Compliance",
"id": 452,
"rationale": "Ensure teams adhere to industry standards, security protocols, and regulatory compliance requirements.",
"slug": "standards-protocols-compliance",
"source": "db"
},
"input_skill": "REST",
"llm_role": null,
"roles_from_db": [
{
"display_name": "Engineering Manager",
"id": 121,
"rationale": null,
"role_archetype": null,
"slug": "engineering-manager",
"source": "db"
},
{
"display_name": "Sitecore Dev",
"id": 233,
"rationale": null,
"role_archetype": "Engineering",
"slug": "sitecore-dev",
"source": "db"
}
]
},
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Vendor Product Families",
"id": 477,
"rationale": "Coordinate usage, licensing, and architecture decisions for major vendor software and cloud product families.",
"slug": "vendor-product-families",
"source": "db"
},
"input_skill": "Salesforce",
"llm_role": null,
"roles_from_db": [
{
"display_name": "Engineering Manager",
"id": 121,
"rationale": null,
"role_archetype": null,
"slug": "engineering-manager",
"source": "db"
}
]
},
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Networking and API Integration",
"id": 84,
"rationale": "Client-side HTTP communication with backend services, including request construction, response parsing, retries, and error handling. iOS engineers use this to connect native screens to server-owned APIs.",
"slug": "networking-and-api-integration",
"source": "db"
},
"input_skill": "HTTP",
"llm_role": null,
"roles_from_db": [
{
"display_name": "Android Developer",
"id": 4,
"rationale": null,
"role_archetype": null,
"slug": "android-engineer",
"source": "db"
},
{
"display_name": "Hybrid Mobile Developer",
"id": 11,
"rationale": null,
"role_archetype": null,
"slug": "hybrid-mobile-developer",
"source": "db"
},
{
"display_name": "Native Mobile Developer",
"id": 75,
"rationale": null,
"role_archetype": "Engineering",
"slug": "native-mobile-developer",
"source": "db"
},
{
"display_name": "iOS Developer",
"id": 6,
"rationale": null,
"role_archetype": null,
"slug": "ios-engineer",
"source": "db"
}
]
}
],
"input_final_skills": [
"MuleSoft Anypoint Platform",
"Anypoint Studio",
"API Manager",
"Exchange",
"Runtime Manager",
"Design Center",
"CloudHub 2.0",
"Microservices",
"REST",
"Salesforce",
"Data Cloud",
"DataWeave",
"HTTP",
"Salesforce Marketing Cloud",
"Adobe Workfront",
"DAM",
"Microsoft Teams"
],
"input_llm_skills": [
"MuleSoft Anypoint Platform",
"Anypoint Studio",
"API Manager",
"Exchange",
"Runtime Manager",
"Design Center",
"CloudHub 2.0",
"Microservices",
"REST",
"Salesforce",
"Data Cloud",
"DataWeave",
"HTTP",
"Salesforce Marketing Cloud",
"Adobe Workfront",
"DAM",
"Microsoft Teams"
],
"new_aliases_persisted": 0,
"run_id": "306c9c8a-47e8-4d43-b101-0a3c345b159d",
"skills_detail": [
{
"aliases_in_db": [],
"canonical": null,
"dimensions": [],
"input_skill": "MuleSoft Anypoint Platform",
"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": "mulesoft-anypoint-platform",
"split_log": [],
"typed": null,
"warnings": []
},
"source_tag": "llm",
"was_in_llm_skills": true
},
{
"aliases_in_db": [],
"canonical": null,
"dimensions": [],
"input_skill": "Anypoint Studio",
"matched_via": null,
"new_alias_persisted": false,
"new_alias_text": null,
"new_skill_meta": {
"derived": {
"category": "Development 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": "anypoint-studio",
"split_log": [],
"typed": null,
"warnings": []
},
"source_tag": "llm",
"was_in_llm_skills": true
},
{
"aliases_in_db": [],
"canonical": null,
"dimensions": [],
"input_skill": "API Manager",
"matched_via": null,
"new_alias_persisted": false,
"new_alias_text": null,
"new_skill_meta": {
"derived": {
"category": "API Management 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": "api-manager",
"split_log": [],
"typed": null,
"warnings": []
},
"source_tag": "llm",
"was_in_llm_skills": true
},
{
"aliases_in_db": [],
"canonical": null,
"dimensions": [],
"input_skill": "Exchange",
"matched_via": null,
"new_alias_persisted": false,
"new_alias_text": null,
"new_skill_meta": {
"derived": {
"category": "API Management 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": "exchange",
"split_log": [],
"typed": null,
"warnings": []
},
"source_tag": "llm",
"was_in_llm_skills": true
},
{
"aliases_in_db": [],
"canonical": null,
"dimensions": [],
"input_skill": "Runtime Manager",
"matched_via": null,
"new_alias_persisted": false,
"new_alias_text": null,
"new_skill_meta": {
"derived": {
"category": "Cloud Platforms",
"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": "runtime-manager",
"split_log": [],
"typed": null,
"warnings": []
},
"source_tag": "llm",
"was_in_llm_skills": true
},
{
"aliases_in_db": [],
"canonical": null,
"dimensions": [],
"input_skill": "Design Center",
"matched_via": null,
"new_alias_persisted": false,
"new_alias_text": null,
"new_skill_meta": {
"derived": {
"category": "Design 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": "design-center",
"split_log": [],
"typed": null,
"warnings": []
},
"source_tag": "llm",
"was_in_llm_skills": true
},
{
"aliases_in_db": [],
"canonical": null,
"dimensions": [],
"input_skill": "CloudHub 2.0",
"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": "cloudhub-2-0",
"split_log": [],
"typed": null,
"warnings": []
},
"source_tag": "llm",
"was_in_llm_skills": true
},
{
"aliases_in_db": [
{
"alias_text": "microservices",
"alias_type": "CANONICAL",
"id": 178,
"is_primary": true,
"match_strategy": "CASE_INSENSITIVE"
}
],
"canonical": {
"category_id": 1,
"display_name": "microservices",
"id": 41,
"is_also_category": false,
"is_extractable": true,
"skill_nature": "PATTERN",
"slug": "microservices",
"sub_category_id": 1,
"typical_lifespan": "EVERGREEN",
"volatility": "STABLE"
},
"dimensions": [
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Microservices and Distributed Systems",
"id": 9,
"rationale": "Architectural patterns for decomposed backend systems and the operational concerns they introduce. Covers service boundaries, consistency tradeoffs, retries, circuit breakers, and distributed coordination.",
"slug": "microservices-and-distributed-systems",
"source": "db"
},
"input_skill": "Microservices",
"llm_role": null,
"roles_from_db": [
{
"display_name": "Backend Developer",
"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": "Node.js Backend Developer",
"id": 82,
"rationale": null,
"role_archetype": "Engineering",
"slug": "node-backend-developer",
"source": "db"
},
{
"display_name": "Scala Backend Developer",
"id": 87,
"rationale": null,
"role_archetype": "Engineering",
"slug": "scala-backend-developer",
"source": "db"
}
]
}
],
"input_skill": "Microservices",
"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": "REST",
"alias_type": "CANONICAL",
"id": 106,
"is_primary": true,
"match_strategy": "CASE_INSENSITIVE"
}
],
"canonical": {
"category_id": 2,
"display_name": "REST",
"id": 11,
"is_also_category": false,
"is_extractable": true,
"skill_nature": "CONCEPT",
"slug": "rest",
"sub_category_id": 2122,
"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 Developer",
"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": "Fullstack Developer",
"id": 435,
"rationale": null,
"role_archetype": "Engineering",
"slug": "fullstack-developer",
"source": "db"
},
{
"display_name": "Fullstack Developer",
"id": 15,
"rationale": null,
"role_archetype": null,
"slug": "full-stack-engineer",
"source": "db"
}
]
},
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "API Interface and Contract Design",
"id": 289,
"rationale": "Designing backend service interfaces and contracts that other systems consume, including endpoint and operation shape, request/response payloads, schema and validation, pagination, filtering, idempotency, versioning, status codes, and backward compatibility across REST, GraphQL, gRPC, and OpenAPI-based APIs.",
"slug": "api-interface-and-contract-design",
"source": "db"
},
"input_skill": "REST",
"llm_role": null,
"roles_from_db": [
{
"display_name": ".NET Backend Developer",
"id": 83,
"rationale": null,
"role_archetype": "Engineering",
"slug": "dotnet-backend-developer",
"source": "db"
},
{
"display_name": "Go Backend Developer",
"id": 81,
"rationale": null,
"role_archetype": "Engineering",
"slug": "go-backend-developer",
"source": "db"
},
{
"display_name": "Kotlin Backend Developer",
"id": 84,
"rationale": null,
"role_archetype": "Engineering",
"slug": "kotlin-server-backend-developer",
"source": "db"
},
{
"display_name": "Node.js Backend Developer",
"id": 82,
"rationale": null,
"role_archetype": "Engineering",
"slug": "node-backend-developer",
"source": "db"
},
{
"display_name": "PHP Backend Developer",
"id": 86,
"rationale": null,
"role_archetype": "Engineering",
"slug": "php-backend-developer",
"source": "db"
},
{
"display_name": "Python Backend Developer",
"id": 80,
"rationale": null,
"role_archetype": "Engineering",
"slug": "python-backend-developer",
"source": "db"
},
{
"display_name": "Ruby Backend Developer",
"id": 85,
"rationale": null,
"role_archetype": "Engineering",
"slug": "ruby-backend-developer",
"source": "db"
},
{
"display_name": "Scala Backend Developer",
"id": 87,
"rationale": null,
"role_archetype": "Engineering",
"slug": "scala-backend-developer",
"source": "db"
}
]
},
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Integration Protocols \u0026 Standards",
"id": 271,
"rationale": "Standards and protocols for integrating Pega applications.",
"slug": "integration-protocols-standards",
"source": "db"
},
"input_skill": "REST",
"llm_role": null,
"roles_from_db": [
{
"display_name": "Pega Developer",
"id": 24,
"rationale": null,
"role_archetype": null,
"slug": "pega-developer",
"source": "db"
}
]
},
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Standards, Protocols \u0026 Compliance",
"id": 452,
"rationale": "Ensure teams adhere to industry standards, security protocols, and regulatory compliance requirements.",
"slug": "standards-protocols-compliance",
"source": "db"
},
"input_skill": "REST",
"llm_role": null,
"roles_from_db": [
{
"display_name": "Engineering Manager",
"id": 121,
"rationale": null,
"role_archetype": null,
"slug": "engineering-manager",
"source": "db"
},
{
"display_name": "Sitecore Dev",
"id": 233,
"rationale": null,
"role_archetype": "Engineering",
"slug": "sitecore-dev",
"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": "Salesforce",
"alias_type": "CANONICAL",
"id": 6567,
"is_primary": true,
"match_strategy": "CASE_INSENSITIVE"
}
],
"canonical": {
"category_id": 9,
"display_name": "Salesforce",
"id": 4632,
"is_also_category": false,
"is_extractable": true,
"skill_nature": "PLATFORM",
"slug": "salesforce",
"sub_category_id": 3633,
"typical_lifespan": "EVERGREEN",
"volatility": "STABLE"
},
"dimensions": [
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Vendor Product Families",
"id": 477,
"rationale": "Coordinate usage, licensing, and architecture decisions for major vendor software and cloud product families.",
"slug": "vendor-product-families",
"source": "db"
},
"input_skill": "Salesforce",
"llm_role": null,
"roles_from_db": [
{
"display_name": "Engineering Manager",
"id": 121,
"rationale": null,
"role_archetype": null,
"slug": "engineering-manager",
"source": "db"
}
]
}
],
"input_skill": "Salesforce",
"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": "Data Cloud",
"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": "data-cloud",
"split_log": [],
"typed": null,
"warnings": []
},
"source_tag": "llm",
"was_in_llm_skills": true
},
{
"aliases_in_db": [],
"canonical": null,
"dimensions": [],
"input_skill": "DataWeave",
"matched_via": null,
"new_alias_persisted": false,
"new_alias_text": null,
"new_skill_meta": {
"derived": {
"category": "Data Transformation 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": "dataweave",
"split_log": [],
"typed": null,
"warnings": []
},
"source_tag": "llm",
"was_in_llm_skills": true
},
{
"aliases_in_db": [
{
"alias_text": "HTTP",
"alias_type": "CANONICAL",
"id": 1538,
"is_primary": true,
"match_strategy": "CASE_INSENSITIVE"
}
],
"canonical": {
"category_id": 10,
"display_name": "HTTP",
"id": 935,
"is_also_category": false,
"is_extractable": true,
"skill_nature": "PROTOCOL",
"slug": "http",
"sub_category_id": 710,
"typical_lifespan": "EVERGREEN",
"volatility": "STABLE"
},
"dimensions": [
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Networking and API Integration",
"id": 84,
"rationale": "Client-side HTTP communication with backend services, including request construction, response parsing, retries, and error handling. iOS engineers use this to connect native screens to server-owned APIs.",
"slug": "networking-and-api-integration",
"source": "db"
},
"input_skill": "HTTP",
"llm_role": null,
"roles_from_db": [
{
"display_name": "Android Developer",
"id": 4,
"rationale": null,
"role_archetype": null,
"slug": "android-engineer",
"source": "db"
},
{
"display_name": "Hybrid Mobile Developer",
"id": 11,
"rationale": null,
"role_archetype": null,
"slug": "hybrid-mobile-developer",
"source": "db"
},
{
"display_name": "Native Mobile Developer",
"id": 75,
"rationale": null,
"role_archetype": "Engineering",
"slug": "native-mobile-developer",
"source": "db"
},
{
"display_name": "iOS Developer",
"id": 6,
"rationale": null,
"role_archetype": null,
"slug": "ios-engineer",
"source": "db"
}
]
}
],
"input_skill": "HTTP",
"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 Marketing Cloud",
"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-marketing-cloud",
"split_log": [],
"typed": null,
"warnings": []
},
"source_tag": "llm",
"was_in_llm_skills": true
},
{
"aliases_in_db": [],
"canonical": null,
"dimensions": [],
"input_skill": "Adobe Workfront",
"matched_via": null,
"new_alias_persisted": false,
"new_alias_text": null,
"new_skill_meta": {
"derived": {
"category": "Project Management 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": "adobe-workfront",
"split_log": [],
"typed": null,
"warnings": []
},
"source_tag": "llm",
"was_in_llm_skills": true
},
{
"aliases_in_db": [],
"canonical": null,
"dimensions": [],
"input_skill": "DAM",
"matched_via": null,
"new_alias_persisted": false,
"new_alias_text": null,
"new_skill_meta": {
"derived": {
"category": "Digital Asset Management 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": "dam",
"split_log": [],
"typed": null,
"warnings": []
},
"source_tag": "llm",
"was_in_llm_skills": true
},
{
"aliases_in_db": [],
"canonical": null,
"dimensions": [],
"input_skill": "Microsoft Teams",
"matched_via": null,
"new_alias_persisted": false,
"new_alias_text": null,
"new_skill_meta": {
"derived": {
"category": "Collaboration Tools",
"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": "microsoft-teams",
"split_log": [],
"typed": null,
"warnings": []
},
"source_tag": "llm",
"was_in_llm_skills": true
}
],
"unmatched_skills": [
"MuleSoft Anypoint Platform",
"Anypoint Studio",
"API Manager",
"Exchange",
"Runtime Manager",
"Design Center",
"CloudHub 2.0",
"Data Cloud",
"DataWeave",
"Salesforce Marketing Cloud",
"Adobe Workfront",
"DAM",
"Microsoft Teams"
]
}
API 3 — final-role-output
{
"chosen_role": {
"display_name": "MuleSoft Developer",
"id": 113,
"rationale": "Domain=Salesforce; The JD focuses heavily on MuleSoft Anypoint Platform integration design and implementation, which is the core responsibility of a MuleSoft Developer.",
"role_archetype": null,
"slug": "mulesoft-developer",
"source": "db"
},
"chosen_role_resolution": "in_db",
"final_input_skills": [
{
"skill": "MuleSoft Anypoint Platform",
"tag": "new"
},
{
"skill": "Anypoint Studio",
"tag": "new"
},
{
"skill": "API Manager",
"tag": "new"
},
{
"skill": "Exchange",
"tag": "new"
},
{
"skill": "Runtime Manager",
"tag": "new"
},
{
"skill": "Design Center",
"tag": "new"
},
{
"skill": "CloudHub 2.0",
"tag": "new"
},
{
"skill": "Microservices",
"tag": "in_db"
},
{
"skill": "REST",
"tag": "in_db"
},
{
"skill": "Salesforce",
"tag": "in_db"
},
{
"skill": "Data Cloud",
"tag": "new"
},
{
"skill": "DataWeave",
"tag": "new"
},
{
"skill": "HTTP",
"tag": "in_db"
},
{
"skill": "Salesforce Marketing Cloud",
"tag": "new"
},
{
"skill": "Adobe Workfront",
"tag": "new"
},
{
"skill": "DAM",
"tag": "new"
},
{
"skill": "Microsoft Teams",
"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": 113,
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Microservices and Distributed Systems",
"id": 9,
"rationale": "Architectural patterns for decomposed backend systems and the operational concerns they introduce. Covers service boundaries, consistency tradeoffs, retries, circuit breakers, and distributed coordination.",
"slug": "microservices-and-distributed-systems",
"source": "db"
},
"dimension_id": 9,
"input_skill": "Microservices",
"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 Developer",
"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": "Node.js Backend Developer",
"id": 82,
"rationale": null,
"role_archetype": "Engineering",
"slug": "node-backend-developer",
"source": "db"
},
{
"display_name": "Scala Backend Developer",
"id": 87,
"rationale": null,
"role_archetype": "Engineering",
"slug": "scala-backend-developer",
"source": "db"
}
],
"skill_dimension_saved": true,
"skill_id": 41,
"skill_tag": "in_db",
"skipped_reason": null
},
{
"chosen_role_id": 113,
"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 Developer",
"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": "Fullstack Developer",
"id": 435,
"rationale": null,
"role_archetype": "Engineering",
"slug": "fullstack-developer",
"source": "db"
},
{
"display_name": "Fullstack Developer",
"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": 113,
"dimension": {
"difficulty_hint": "well_known",
"display_name": "API Interface and Contract Design",
"id": 289,
"rationale": "Designing backend service interfaces and contracts that other systems consume, including endpoint and operation shape, request/response payloads, schema and validation, pagination, filtering, idempotency, versioning, status codes, and backward compatibility across REST, GraphQL, gRPC, and OpenAPI-based APIs.",
"slug": "api-interface-and-contract-design",
"source": "db"
},
"dimension_id": 289,
"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": ".NET Backend Developer",
"id": 83,
"rationale": null,
"role_archetype": "Engineering",
"slug": "dotnet-backend-developer",
"source": "db"
},
{
"display_name": "Go Backend Developer",
"id": 81,
"rationale": null,
"role_archetype": "Engineering",
"slug": "go-backend-developer",
"source": "db"
},
{
"display_name": "Kotlin Backend Developer",
"id": 84,
"rationale": null,
"role_archetype": "Engineering",
"slug": "kotlin-server-backend-developer",
"source": "db"
},
{
"display_name": "Node.js Backend Developer",
"id": 82,
"rationale": null,
"role_archetype": "Engineering",
"slug": "node-backend-developer",
"source": "db"
},
{
"display_name": "PHP Backend Developer",
"id": 86,
"rationale": null,
"role_archetype": "Engineering",
"slug": "php-backend-developer",
"source": "db"
},
{
"display_name": "Python Backend Developer",
"id": 80,
"rationale": null,
"role_archetype": "Engineering",
"slug": "python-backend-developer",
"source": "db"
},
{
"display_name": "Ruby Backend Developer",
"id": 85,
"rationale": null,
"role_archetype": "Engineering",
"slug": "ruby-backend-developer",
"source": "db"
},
{
"display_name": "Scala Backend Developer",
"id": 87,
"rationale": null,
"role_archetype": "Engineering",
"slug": "scala-backend-developer",
"source": "db"
}
],
"skill_dimension_saved": true,
"skill_id": 11,
"skill_tag": "in_db",
"skipped_reason": null
},
{
"chosen_role_id": 113,
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Integration Protocols \u0026 Standards",
"id": 271,
"rationale": "Standards and protocols for integrating Pega applications.",
"slug": "integration-protocols-standards",
"source": "db"
},
"dimension_id": 271,
"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": "Pega Developer",
"id": 24,
"rationale": null,
"role_archetype": null,
"slug": "pega-developer",
"source": "db"
}
],
"skill_dimension_saved": true,
"skill_id": 11,
"skill_tag": "in_db",
"skipped_reason": null
},
{
"chosen_role_id": 113,
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Standards, Protocols \u0026 Compliance",
"id": 452,
"rationale": "Ensure teams adhere to industry standards, security protocols, and regulatory compliance requirements.",
"slug": "standards-protocols-compliance",
"source": "db"
},
"dimension_id": 452,
"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": "Engineering Manager",
"id": 121,
"rationale": null,
"role_archetype": null,
"slug": "engineering-manager",
"source": "db"
},
{
"display_name": "Sitecore Dev",
"id": 233,
"rationale": null,
"role_archetype": "Engineering",
"slug": "sitecore-dev",
"source": "db"
}
],
"skill_dimension_saved": true,
"skill_id": 11,
"skill_tag": "in_db",
"skipped_reason": null
},
{
"chosen_role_id": 113,
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Vendor Product Families",
"id": 477,
"rationale": "Coordinate usage, licensing, and architecture decisions for major vendor software and cloud product families.",
"slug": "vendor-product-families",
"source": "db"
},
"dimension_id": 477,
"input_skill": "Salesforce",
"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": "Engineering Manager",
"id": 121,
"rationale": null,
"role_archetype": null,
"slug": "engineering-manager",
"source": "db"
}
],
"skill_dimension_saved": true,
"skill_id": 4632,
"skill_tag": "in_db",
"skipped_reason": null
},
{
"chosen_role_id": 113,
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Networking and API Integration",
"id": 84,
"rationale": "Client-side HTTP communication with backend services, including request construction, response parsing, retries, and error handling. iOS engineers use this to connect native screens to server-owned APIs.",
"slug": "networking-and-api-integration",
"source": "db"
},
"dimension_id": 84,
"input_skill": "HTTP",
"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": "Android Developer",
"id": 4,
"rationale": null,
"role_archetype": null,
"slug": "android-engineer",
"source": "db"
},
{
"display_name": "Hybrid Mobile Developer",
"id": 11,
"rationale": null,
"role_archetype": null,
"slug": "hybrid-mobile-developer",
"source": "db"
},
{
"display_name": "Native Mobile Developer",
"id": 75,
"rationale": null,
"role_archetype": "Engineering",
"slug": "native-mobile-developer",
"source": "db"
},
{
"display_name": "iOS Developer",
"id": 6,
"rationale": null,
"role_archetype": null,
"slug": "ios-engineer",
"source": "db"
}
],
"skill_dimension_saved": true,
"skill_id": 935,
"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": "306c9c8a-47e8-4d43-b101-0a3c345b159d"
}
LLM Calls
Every model call made for this run, in pipeline order. Click a card to see the model's response.