Pipeline run
4bba8f21-38ff-42d8-a2ef-6098afdcbcb1
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
• You will be creating Secure, Robust and scalable solutions for e-Banking platform. • While you work as part of the scrum team, you'll also work closely with Product Owners, and relevant subject matt…
1 POST /skills/extract-from-jd
2 POST /skills/extract-details
3 POST /skills/final-role-output
Hybrid Mobile Developer
→Flutter Developer
sub-role · 0.58 CASE Bslug: hybrid-mobile-developer · id: 11 · source: db · sub-role slug: flutter-developer
KRA-led classification on flutter-developer (skill weak, KRA 0.58)
Resolution:
in_db
— role exists in library; skill↔dim and role↔dim links saved when applicable.
Job description
Job Title: Mobile Architect Grade : C2/D1 Location : Bangalore/Gurgaon NP-Immediate At least 3 Must have skills : Java 8/API Microservice Architect, Backbase, Mobile App Development and deployment. Job Description • You will be creating Secure, Robust and scalable solutions for e-Banking platform. • While you work as part of the scrum team, you'll also work closely with Product Owners, and relevant subject matter experts, as well as other scrum teams across the locations to deliver solutions. • You'll work with journey delivery, Business Analysts, Product Owner, UI/UX, and developers to come up with best solution for the platform. Act as a go-to between non-technical team members like BA, Product Owner etc and developers, infrastructure specialists, security specialists, third parties, other solution architects etc. • Work on design which impact external and as well as internal customers. • Participate in issues / incidents to provide possible solutions. • You will be part of Digital Architecture forum which will be responsible for • Reviewing the changes to the platform, • Define platform technical roadmap, • Define Architectural Patterns • Consult with stakeholders outside Digital Delivery on platforms capabilities and roadmap etc.. In this role, you'll also: • Help to define technical user stories, including acceptance criteria • Debug and investigate bugs and issues during testing and development phase and assign them to relevant teams • Facilitate technical end to end testing. Support functional and non-functional testing. • Take part in daily stand-up meetings and regular sprint planning, retrospective and backlog refinement sessions • Continuously build your knowledge of the roadmap for the platform and associated technologies • Support release management activities during production releases (scheduled and emergencies).
Skills from this JD
Each row merges API 1 extraction, API 2 library match / v3 orchestration (dimensions + locked dims), and API 3 persistence tags.
Aliases — catalog
- Scrum (CANONICAL) primary
Context tags (catalog)
Stored enrichment (catalog DB)
- Category
- Methodology
- Sub-category
- Scrum
- Confidence
- 0.99
- Version strategy
- NOT_APPLICABLE
Maturity reasoning: Scrum appears in a large share of agile project-management and product-owner job descriptions, and Scrum Alliance/PSM certifications are widely requested in hiring pipelines.
Skill profile (library / DB)
- Skill nature
- METHODOLOGY
- Volatility
- STABLE
- Typical lifespan
- EVERGREEN
- Category id
- 8
- Sub-category id
- 921
- 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
- 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
- UI/UX (CANONICAL)
Context tags (catalog)
Stored enrichment (catalog DB)
- Category
- Domain
- Sub-category
- Ui Ux Design
- Confidence
- 0.96
- Version strategy
- NOT_APPLICABLE
Maturity reasoning: UI/UX appears in a large share of product/design job descriptions across industries and is a standard hiring requirement, with strong demand on major job boards and design-tool ecosystems.
Skill profile (library / DB)
- Skill nature
- CONCEPT
- Volatility
- STABLE
- Typical lifespan
- EVERGREEN
- Category id
- 37
- Sub-category id
- 1255
- 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) |
Skill enrichment (orchestrator / LLM)
No Stage 7 enrichment blob on this skill (orchestrator skipped enrichment).
- Category
- Conceptual Architectures
- 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
- Conceptual Architectures
- 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
- Agile Practices
- Sub-category
- general
- Skill nature
- PRACTICE
- Volatility
- MEDIUM
- Typical lifespan
- MULTI_YEAR
- Version strategy
- UNVERSIONED
Aliases — catalog
- end-to-end tests (CANONICAL) primary
Context tags (catalog)
Stored enrichment (catalog DB)
- Category
- Methodology
- Sub-category
- Testing Methodology
- Confidence
- 0.97
- Version strategy
- NOT_APPLICABLE
Maturity reasoning: Commonly listed in QA/SDET and frontend/backend JDs; tools like Cypress, Playwright, and Selenium show strong GitHub and job-market demand for E2E testing.
Skill profile (library / DB)
- Skill nature
- METHODOLOGY
- Volatility
- STABLE
- Typical lifespan
- EVERGREEN
- Category id
- 8
- Sub-category id
- 44
- Extractable
- True
- Also category
- False
Dimensions (API 2 worklist)
-
Testing and Quality Assurance Catalog dimension db id 12
Library dimension (catalog)
Roles linked in library: .NET Backend Developer, Backend Developer, Node.js Backend Developer, PHP Backend Developer, Python Backend Developer, Scala Backend Developer
API 3 link attempts (this skill)
| Dimension | Skill↔dim | Role↔dim | Outcome |
|---|---|---|---|
|
Testing and Quality Assurance
testing-and-quality-assurance
|
— | — |
Skipped — no persistable v3 meta for new skill
skill_not_in_db_v3_proposed
|
Aliases — catalog
- Integration testing (CANONICAL) primary
- integration testing (CANONICAL)
Context tags (catalog)
Stored enrichment (catalog DB)
- Category
- Methodology
- Sub-category
- Testing Methodology
- Confidence
- 0.97
- Version strategy
- NOT_APPLICABLE
Maturity reasoning: Integration testing is a standard QA skill in job descriptions across backend, frontend, and DevOps roles; it’s commonly paired with CI/CD and tools like Jest, Cypress, and Testcontainers.
Skill profile (library / DB)
- Skill nature
- METHODOLOGY
- Volatility
- STABLE
- Typical lifespan
- EVERGREEN
- Category id
- 8
- Sub-category id
- 44
- Extractable
- True
- Also category
- False
Dimensions (API 2 worklist)
-
Testing and Defect Resolution Catalog dimension db id 262
Library dimension (catalog)
Roles linked in library: Pega Developer
-
Testing and Quality Assurance Catalog dimension db id 12
Library dimension (catalog)
Roles linked in library: .NET Backend Developer, Backend Developer, Node.js Backend Developer, PHP Backend Developer, Python Backend Developer, Scala Backend Developer
API 3 link attempts (this skill)
| Dimension | Skill↔dim | Role↔dim | Outcome |
|---|---|---|---|
|
Testing and Defect Resolution
testing-and-defect-resolution
|
— | — |
Skipped — no persistable v3 meta for new skill
skill_not_in_db_v3_proposed
|
|
Testing and Quality Assurance
testing-and-quality-assurance
|
— | — |
Skipped — no persistable v3 meta for new skill
skill_not_in_db_v3_proposed
|
Skill enrichment (orchestrator / LLM)
No Stage 7 enrichment blob on this skill (orchestrator skipped enrichment).
- Category
- Testing Practices
- Sub-category
- general
- Skill nature
- PRACTICE
- 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
- Agile Practices
- Sub-category
- general
- Skill nature
- PRACTICE
- 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
- Agile Practices
- Sub-category
- general
- Skill nature
- PRACTICE
- 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
- Agile Practices
- Sub-category
- general
- Skill nature
- PRACTICE
- 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
- Software Development Practices
- Sub-category
- general
- Skill nature
- PRACTICE
- 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 |
|---|---|---|---|---|---|---|
| Scrum | in_db |
React Frontend Development
d_init_01
|
✓ | — | 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) | |
| UI/UX | in_db |
React Frontend Development
d_init_01
|
✓ | — | Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role) | |
| End-to-End Testing | new |
Testing and Quality Assurance
testing-and-quality-assurance
|
— | — | Skipped — no persistable v3 meta for new skill | skill_not_in_db_v3_proposed |
| Functional Testing | new |
Testing and Defect Resolution
testing-and-defect-resolution
|
— | — | Skipped — no persistable v3 meta for new skill | skill_not_in_db_v3_proposed |
| Functional Testing | new |
Testing and Quality Assurance
testing-and-quality-assurance
|
— | — | Skipped — no persistable v3 meta for new skill | skill_not_in_db_v3_proposed |
Library artifacts (this run)
| Kind | Detail | DB id |
|---|---|---|
| canonical_skill_proposed | Digital Architecture | type=Conceptual Architectures subtype=general nature=CONCEPT lifespan=MULTI_YEAR | |
| canonical_skill_proposed | Architectural Patterns | type=Conceptual Architectures subtype=general nature=CONCEPT lifespan=MULTI_YEAR | |
| canonical_skill_proposed | Acceptance Criteria | type=Agile Practices subtype=general nature=PRACTICE lifespan=MULTI_YEAR | |
| canonical_skill_proposed | Non-Functional Testing | type=Testing Practices subtype=general nature=PRACTICE lifespan=MULTI_YEAR | |
| canonical_skill_proposed | Sprint Planning | type=Agile Practices subtype=general nature=PRACTICE lifespan=MULTI_YEAR | |
| canonical_skill_proposed | Retrospective | type=Agile Practices subtype=general nature=PRACTICE lifespan=MULTI_YEAR | |
| canonical_skill_proposed | Backlog Refinement | type=Agile Practices subtype=general nature=PRACTICE lifespan=MULTI_YEAR | |
| canonical_skill_proposed | Release Management | type=Software Development Practices subtype=general nature=PRACTICE lifespan=MULTI_YEAR | |
| dimension_skill_link_proposed | End-to-End Testing ↔ Testing and Quality Assurance | |
| dimension_skill_link_proposed | Functional Testing ↔ Testing and Defect Resolution | |
| dimension_skill_link_proposed | Functional Testing ↔ Testing and Quality Assurance |
nano JD Parser — gpt-4.1-nano click to toggle
Show raw JSON
{
"JD_type": "pass",
"about_company": null,
"certifications": [],
"company_name": null,
"ctc": null,
"domain": {
"primary": {
"aliases": [
"ITES",
"BPO"
],
"domain": "IT Services \u0026 Consulting"
},
"secondary": null
},
"education": [],
"experience": {
"max": null,
"min": 3,
"raw": "At least 3 Must have skills"
},
"job_locations": [
{
"aliases": [
"Bengaluru"
],
"city": "Bangalore",
"country": "India",
"state": null,
"work_mode": null
},
{
"aliases": [
"Gurugram"
],
"city": "Gurgaon",
"country": "India",
"state": null,
"work_mode": null
}
],
"role": "Mobile Architect",
"role_aliases": [
"Mobile Architect",
"Mobile Solutions Architect",
"Mobile App Architect"
],
"role_archetype": "Engineering",
"roles_and_responsibilities": [
{
"bullet_count": 8,
"heading": "Job Description",
"heading_was_present": true,
"source_marker": {
"first_5_words": "You will be creating Secure,",
"last_5_words": "capabilities and roadmap etc.."
},
"text": "\u2022 You will be creating Secure, Robust and scalable solutions for e-Banking platform.\n\u2022 While you work as part of the scrum team, you\u0027ll also work closely with Product Owners, and relevant subject matter experts, as well as other scrum teams across the locations to deliver solutions.\n\u2022 You\u0027ll work with journey delivery, Business Analysts, Product Owner, UI/UX, and developers to come up with best solution for the platform. Act as a go-to between non-technical team members like BA, Product Owner etc and developers, infrastructure specialists, security specialists, third parties, other solution architects etc.\n\u2022 Work on design which impact external and as well as internal customers.\n\u2022 Participate in issues / incidents to provide possible solutions.\n\u2022 You will be part of Digital Architecture forum which will be responsible for\n\u2022 Reviewing the changes to the platform,\n\u2022 Define platform technical roadmap,\n\u2022 Define Architectural Patterns\n\u2022 Consult with stakeholders outside Digital Delivery on platforms capabilities and roadmap etc..",
"word_count": 174
},
{
"bullet_count": 6,
"heading": "In this role, you\u0027ll also:",
"heading_was_present": true,
"source_marker": {
"first_5_words": "Help to define technical user",
"last_5_words": "scheduled and emergencies)."
},
"text": "\u2022 Help to define technical user stories, including acceptance criteria\n\u2022 Debug and investigate bugs and issues during testing and development phase and assign them to relevant teams\n\u2022 Facilitate technical end to end testing. Support functional and non-functional testing.\n\u2022 Take part in daily stand-up meetings and regular sprint planning, retrospective and backlog refinement sessions\n\u2022 Continuously build your knowledge of the roadmap for the platform and associated technologies\n\u2022 Support release management activities during production releases (scheduled and emergencies).",
"word_count": 81
}
],
"urls": []
}
API 1 — extract-from-jd click to toggle
{
"final_skills": [
{
"is_primary": true,
"skill_name": "Scrum"
},
{
"is_primary": true,
"skill_name": "Agile"
},
{
"is_primary": false,
"skill_name": "UI/UX"
},
{
"is_primary": false,
"skill_name": "Digital Architecture"
},
{
"is_primary": false,
"skill_name": "Architectural Patterns"
},
{
"is_primary": false,
"skill_name": "Acceptance Criteria"
},
{
"is_primary": false,
"skill_name": "End-to-End Testing"
},
{
"is_primary": false,
"skill_name": "Functional Testing"
},
{
"is_primary": false,
"skill_name": "Non-Functional Testing"
},
{
"is_primary": false,
"skill_name": "Sprint Planning"
},
{
"is_primary": false,
"skill_name": "Retrospective"
},
{
"is_primary": false,
"skill_name": "Backlog Refinement"
},
{
"is_primary": false,
"skill_name": "Release Management"
}
],
"jd_role": {
"display_name": "Mobile Architect",
"rationale": null,
"role_aliases": [
"Mobile Architect",
"Mobile Solutions Architect",
"Mobile App Architect"
],
"role_archetype": "Engineering",
"slug": ""
},
"nano_parsed": {
"JD_type": "pass",
"about_company": null,
"certifications": [],
"company_name": null,
"ctc": null,
"domain": {
"primary": {
"aliases": [
"ITES",
"BPO"
],
"domain": "IT Services \u0026 Consulting"
},
"secondary": null
},
"education": [],
"experience": {
"max": null,
"min": 3,
"raw": "At least 3 Must have skills"
},
"job_locations": [
{
"aliases": [
"Bengaluru"
],
"city": "Bangalore",
"country": "India",
"state": null,
"work_mode": null
},
{
"aliases": [
"Gurugram"
],
"city": "Gurgaon",
"country": "India",
"state": null,
"work_mode": null
}
],
"role": "Mobile Architect",
"role_aliases": [
"Mobile Architect",
"Mobile Solutions Architect",
"Mobile App Architect"
],
"role_archetype": "Engineering",
"roles_and_responsibilities": [
{
"bullet_count": 8,
"heading": "Job Description",
"heading_was_present": true,
"source_marker": {
"first_5_words": "You will be creating Secure,",
"last_5_words": "capabilities and roadmap etc.."
},
"text": "\u2022 You will be creating Secure, Robust and scalable solutions for e-Banking platform.\n\u2022 While you work as part of the scrum team, you\u0027ll also work closely with Product Owners, and relevant subject matter experts, as well as other scrum teams across the locations to deliver solutions.\n\u2022 You\u0027ll work with journey delivery, Business Analysts, Product Owner, UI/UX, and developers to come up with best solution for the platform. Act as a go-to between non-technical team members like BA, Product Owner etc and developers, infrastructure specialists, security specialists, third parties, other solution architects etc.\n\u2022 Work on design which impact external and as well as internal customers.\n\u2022 Participate in issues / incidents to provide possible solutions.\n\u2022 You will be part of Digital Architecture forum which will be responsible for\n\u2022 Reviewing the changes to the platform,\n\u2022 Define platform technical roadmap,\n\u2022 Define Architectural Patterns\n\u2022 Consult with stakeholders outside Digital Delivery on platforms capabilities and roadmap etc..",
"word_count": 174
},
{
"bullet_count": 6,
"heading": "In this role, you\u0027ll also:",
"heading_was_present": true,
"source_marker": {
"first_5_words": "Help to define technical user",
"last_5_words": "scheduled and emergencies)."
},
"text": "\u2022 Help to define technical user stories, including acceptance criteria\n\u2022 Debug and investigate bugs and issues during testing and development phase and assign them to relevant teams\n\u2022 Facilitate technical end to end testing. Support functional and non-functional testing.\n\u2022 Take part in daily stand-up meetings and regular sprint planning, retrospective and backlog refinement sessions\n\u2022 Continuously build your knowledge of the roadmap for the platform and associated technologies\n\u2022 Support release management activities during production releases (scheduled and emergencies).",
"word_count": 81
}
],
"urls": []
},
"rejected": false,
"rejection_reason": null,
"run_id": "4bba8f21-38ff-42d8-a2ef-6098afdcbcb1",
"stage3_signals": {
"alias_found": true,
"alias_match_roles": [
{
"display_name": "Android Developer",
"kra_matches": null,
"matched_count": null,
"matched_skills": null,
"role_id": 4,
"score": 1.0,
"slug": "android-engineer",
"total_count": null
},
{
"display_name": "iOS Developer",
"kra_matches": null,
"matched_count": null,
"matched_skills": null,
"role_id": 6,
"score": 1.0,
"slug": "ios-engineer",
"total_count": null
}
],
"kra_match_roles": [
{
"display_name": "Flutter Developer",
"kra_matches": [
{
"kra_text": "support release readiness",
"sentence": "Support release management activities during production releases (scheduled and emergencies).",
"similarity": 0.6602
},
{
"kra_text": "collaborate with design, product, and backend teams",
"sentence": "Act as a go-to between non-technical team members like BA, Product Owner etc and developers, infrastructure specialists, security specialists, third parties, other solution architects etc. \u2022 Work on design which impact external and as well as internal customers.",
"similarity": 0.5865
},
{
"kra_text": "collaborate with design, product, and backend teams",
"sentence": "You\u0027ll work with journey delivery, Business Analysts, Product Owner, UI/UX, and developers to come up with best solution for the platform.",
"similarity": 0.5072
}
],
"matched_count": null,
"matched_skills": null,
"role_id": 74,
"score": 0.5846,
"slug": "flutter-developer",
"total_count": null
},
{
"display_name": "Fullstack Developer",
"kra_matches": [
{
"kra_text": "Debugs full-stack issues that span frontend rendering, API behavior, database queries, and infrastructure configuration to identify root causes.",
"sentence": "Debug and investigate bugs and issues during testing and development phase and assign them to relevant teams",
"similarity": 0.5695
},
{
"kra_text": "Works closely with product managers and UX designers to translate requirements and wireframes into working software features through iterative development.",
"sentence": "Act as a go-to between non-technical team members like BA, Product Owner etc and developers, infrastructure specialists, security specialists, third parties, other solution architects etc. \u2022 Work on design which impact external and as well as internal customers.",
"similarity": 0.5508
},
{
"kra_text": "Works closely with product managers and UX designers to translate requirements and wireframes into working software features through iterative development.",
"sentence": "You\u0027ll work with journey delivery, Business Analysts, Product Owner, UI/UX, and developers to come up with best solution for the platform.",
"similarity": 0.5458
}
],
"matched_count": null,
"matched_skills": null,
"role_id": 15,
"score": 0.5554,
"slug": "full-stack-engineer",
"total_count": null
},
{
"display_name": "Backend Developer",
"kra_matches": [
{
"kra_text": "Investigates and resolves production incidents, API bugs, and service degradation through root cause analysis, hotfixes, and post-mortems.",
"sentence": "Debug and investigate bugs and issues during testing and development phase and assign them to relevant teams",
"similarity": 0.5984
},
{
"kra_text": "Investigates and resolves production incidents, API bugs, and service degradation through root cause analysis, hotfixes, and post-mortems.",
"sentence": "Support release management activities during production releases (scheduled and emergencies).",
"similarity": 0.5241
},
{
"kra_text": "Investigates and resolves production incidents, API bugs, and service degradation through root cause analysis, hotfixes, and post-mortems.",
"sentence": "Participate in issues / incidents to provide possible solutions.",
"similarity": 0.5034
}
],
"matched_count": null,
"matched_skills": null,
"role_id": 1,
"score": 0.542,
"slug": "backend-engineer",
"total_count": null
},
{
"display_name": "Frontend Developer",
"kra_matches": [
{
"kra_text": "Supports production releases by diagnosing cross-browser compatibility issues, investigating UI regressions, and resolving frontend performance degradation.",
"sentence": "Debug and investigate bugs and issues during testing and development phase and assign them to relevant teams",
"similarity": 0.5524
},
{
"kra_text": "Supports production releases by diagnosing cross-browser compatibility issues, investigating UI regressions, and resolving frontend performance degradation.",
"sentence": "Support release management activities during production releases (scheduled and emergencies).",
"similarity": 0.5214
},
{
"kra_text": "Supports production releases by diagnosing cross-browser compatibility issues, investigating UI regressions, and resolving frontend performance degradation.",
"sentence": "Support functional and non-functional testing.",
"similarity": 0.4807
}
],
"matched_count": null,
"matched_skills": null,
"role_id": 7,
"score": 0.5182,
"slug": "frontend-engineer",
"total_count": null
},
{
"display_name": "DevOps Engineer",
"kra_matches": [
{
"kra_text": "Manages release management processes including environment promotion gates, deployment approval workflows, change management records, and rollback procedures.",
"sentence": "Support release management activities during production releases (scheduled and emergencies).",
"similarity": 0.5934
},
{
"kra_text": "Responds to deployment failures, infrastructure incidents, and environment misconfiguration issues to restore service availability and prevent recurrence.",
"sentence": "Participate in issues / incidents to provide possible solutions.",
"similarity": 0.4805
},
{
"kra_text": "Collaborates with development teams to improve build processes, reduce deployment friction, containerize applications, and adopt DevOps best practices.",
"sentence": "Act as a go-to between non-technical team members like BA, Product Owner etc and developers, infrastructure specialists, security specialists, third parties, other solution architects etc. \u2022 Work on design which impact external and as well as internal customers.",
"similarity": 0.4741
}
],
"matched_count": null,
"matched_skills": null,
"role_id": 10,
"score": 0.516,
"slug": "devops-engineer",
"total_count": null
}
],
"skill_match_roles": []
},
"stage4_decision": {
"alias_collision_detected": true,
"case": "B",
"chosen_role": {
"display_name": "Hybrid Mobile Developer",
"kra_matches": null,
"matched_count": null,
"matched_skills": null,
"role_id": 11,
"score": 0.5846,
"slug": "hybrid-mobile-developer",
"total_count": null
},
"confidence": 0.5846,
"is_new_role": false,
"llm2_fired": false,
"llm2_reasoning": null,
"matched_dimensions": [],
"matched_kras": [],
"matched_skills": [],
"new_role_display_name": null,
"new_role_slug": null,
"queued": false,
"reasoning": "KRA-led classification on flutter-developer (skill weak, KRA 0.58)",
"sub_role": {
"confidence": 0.5846,
"display_name": "Flutter Developer",
"reasoning": "hoisted from chosen leaf (case=B)",
"role_id": 74,
"slug": "flutter-developer"
}
},
"stage5_updates": {
"centroid_n_after": 28,
"centroid_updated": true,
"collision_log_id": 397,
"new_kra_attached": {
"best_kra_similarity": 0.0,
"queue_id": 527,
"r_and_r_preview": "\u2022 You will be creating Secure, Robust and scalable solutions for e-Banking platform.\n\u2022 While you work as part of the scrum team, you\u0027ll also work closely with Product Owners, and relevant subject matt",
"role_display_name": "Hybrid Mobile Developer",
"role_slug": "hybrid-mobile-developer",
"status": "pending"
},
"new_skills_attached": [
{
"is_primary": false,
"queue_id": 8773,
"role_display_name": "Hybrid Mobile Developer",
"role_slug": "hybrid-mobile-developer",
"skill_name": "Digital Architecture",
"status": "pending"
},
{
"is_primary": false,
"queue_id": 8774,
"role_display_name": "Hybrid Mobile Developer",
"role_slug": "hybrid-mobile-developer",
"skill_name": "Architectural Patterns",
"status": "pending"
},
{
"is_primary": false,
"queue_id": 8775,
"role_display_name": "Hybrid Mobile Developer",
"role_slug": "hybrid-mobile-developer",
"skill_name": "Acceptance Criteria",
"status": "pending"
},
{
"is_primary": false,
"queue_id": 8776,
"role_display_name": "Hybrid Mobile Developer",
"role_slug": "hybrid-mobile-developer",
"skill_name": "End-to-End Testing",
"status": "pending"
},
{
"is_primary": false,
"queue_id": 8777,
"role_display_name": "Hybrid Mobile Developer",
"role_slug": "hybrid-mobile-developer",
"skill_name": "Functional Testing",
"status": "pending"
},
{
"is_primary": false,
"queue_id": 8778,
"role_display_name": "Hybrid Mobile Developer",
"role_slug": "hybrid-mobile-developer",
"skill_name": "Non-Functional Testing",
"status": "pending"
},
{
"is_primary": false,
"queue_id": 8779,
"role_display_name": "Hybrid Mobile Developer",
"role_slug": "hybrid-mobile-developer",
"skill_name": "Sprint Planning",
"status": "pending"
},
{
"is_primary": false,
"queue_id": 8780,
"role_display_name": "Hybrid Mobile Developer",
"role_slug": "hybrid-mobile-developer",
"skill_name": "Retrospective",
"status": "pending"
},
{
"is_primary": false,
"queue_id": 8781,
"role_display_name": "Hybrid Mobile Developer",
"role_slug": "hybrid-mobile-developer",
"skill_name": "Backlog Refinement",
"status": "pending"
},
{
"is_primary": false,
"queue_id": 8782,
"role_display_name": "Hybrid Mobile Developer",
"role_slug": "hybrid-mobile-developer",
"skill_name": "Release Management",
"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": 1851,
"existing_alias_text": "Scrum",
"input_term": "Scrum",
"matched_canonical": {
"category_id": 8,
"display_name": "Scrum",
"id": 1215,
"is_also_category": false,
"is_extractable": true,
"skill_nature": "METHODOLOGY",
"slug": "scrum",
"sub_category_id": 921,
"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": 2632,
"existing_alias_text": "UI/UX",
"input_term": "UI/UX",
"matched_canonical": {
"category_id": 37,
"display_name": "UI/UX",
"id": 1662,
"is_also_category": false,
"is_extractable": true,
"skill_nature": "CONCEPT",
"slug": "ui-ux",
"sub_category_id": 1255,
"typical_lifespan": "EVERGREEN",
"volatility": "STABLE"
},
"matched_via": "alias"
},
{
"alias_persist_skipped_reason": "TODO: REMOVE AFTER TESTING \u2014 alias DB write disabled",
"alias_persisted": false,
"existing_alias_id": 195,
"existing_alias_text": "end-to-end tests",
"input_term": "End-to-End Testing",
"matched_canonical": {
"category_id": 8,
"display_name": "end-to-end tests",
"id": 58,
"is_also_category": false,
"is_extractable": true,
"skill_nature": "METHODOLOGY",
"slug": "end-to-end-tests",
"sub_category_id": 44,
"typical_lifespan": "EVERGREEN",
"volatility": "STABLE"
},
"matched_via": "embedding_alias"
},
{
"alias_persist_skipped_reason": "TODO: REMOVE AFTER TESTING \u2014 alias DB write disabled",
"alias_persisted": false,
"existing_alias_id": 2945,
"existing_alias_text": "Integration testing",
"input_term": "Functional Testing",
"matched_canonical": {
"category_id": 8,
"display_name": "Integration testing",
"id": 56,
"is_also_category": false,
"is_extractable": true,
"skill_nature": "METHODOLOGY",
"slug": "integration-testing",
"sub_category_id": 44,
"typical_lifespan": "EVERGREEN",
"volatility": "STABLE"
},
"matched_via": "embedding_alias"
}
],
"candidate_roles": [
{
"display_name": ".NET Backend Developer",
"id": 83,
"rationale": null,
"role_archetype": "Engineering",
"slug": "dotnet-backend-developer",
"source": "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": "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": "Scala Backend Developer",
"id": 87,
"rationale": null,
"role_archetype": "Engineering",
"slug": "scala-backend-developer",
"source": "db"
},
{
"display_name": "Pega Developer",
"id": 24,
"rationale": null,
"role_archetype": null,
"slug": "pega-developer",
"source": "db"
}
],
"chosen_role": {
"display_name": "Hybrid Mobile Developer",
"id": 11,
"rationale": "KRA-led classification on flutter-developer (skill weak, KRA 0.58)",
"role_archetype": null,
"slug": "hybrid-mobile-developer",
"source": "db"
},
"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": "Scrum",
"llm_role": null,
"roles_from_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": "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": "UI/UX",
"llm_role": null,
"roles_from_db": []
},
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Testing and Quality Assurance",
"id": 12,
"rationale": "Backend-specific test strategies used to validate service behavior and integration points. Covers automated test layers, contract checks, fixtures, and regression prevention.",
"slug": "testing-and-quality-assurance",
"source": "db"
},
"input_skill": "End-to-End Testing",
"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": "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": "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": "Scala Backend Developer",
"id": 87,
"rationale": null,
"role_archetype": "Engineering",
"slug": "scala-backend-developer",
"source": "db"
}
]
},
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Testing and Defect Resolution",
"id": 262,
"rationale": "Validates Pega rules, flows, and integrations and then troubleshoots defects found in lower environments or production. This is a coherent cluster because the role is expected to verify platform behavior and fix rule-level issues.",
"slug": "testing-and-defect-resolution",
"source": "db"
},
"input_skill": "Functional Testing",
"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": "Testing and Quality Assurance",
"id": 12,
"rationale": "Backend-specific test strategies used to validate service behavior and integration points. Covers automated test layers, contract checks, fixtures, and regression prevention.",
"slug": "testing-and-quality-assurance",
"source": "db"
},
"input_skill": "Functional Testing",
"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": "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": "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": "Scala Backend Developer",
"id": 87,
"rationale": null,
"role_archetype": "Engineering",
"slug": "scala-backend-developer",
"source": "db"
}
]
}
],
"input_final_skills": [
"Scrum",
"Agile",
"UI/UX",
"Digital Architecture",
"Architectural Patterns",
"Acceptance Criteria",
"End-to-End Testing",
"Functional Testing",
"Non-Functional Testing",
"Sprint Planning",
"Retrospective",
"Backlog Refinement",
"Release Management"
],
"input_llm_skills": [
"Scrum",
"Agile",
"UI/UX",
"Digital Architecture",
"Architectural Patterns",
"Acceptance Criteria",
"End-to-End Testing",
"Functional Testing",
"Non-Functional Testing",
"Sprint Planning",
"Retrospective",
"Backlog Refinement",
"Release Management"
],
"new_aliases_persisted": 0,
"run_id": "4bba8f21-38ff-42d8-a2ef-6098afdcbcb1",
"skills_detail": [
{
"aliases_in_db": [
{
"alias_text": "Scrum",
"alias_type": "CANONICAL",
"id": 1851,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
}
],
"canonical": {
"category_id": 8,
"display_name": "Scrum",
"id": 1215,
"is_also_category": false,
"is_extractable": true,
"skill_nature": "METHODOLOGY",
"slug": "scrum",
"sub_category_id": 921,
"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": "Scrum",
"llm_role": null,
"roles_from_db": []
}
],
"input_skill": "Scrum",
"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": "UI/UX",
"alias_type": "CANONICAL",
"id": 2632,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
}
],
"canonical": {
"category_id": 37,
"display_name": "UI/UX",
"id": 1662,
"is_also_category": false,
"is_extractable": true,
"skill_nature": "CONCEPT",
"slug": "ui-ux",
"sub_category_id": 1255,
"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": "UI/UX",
"llm_role": null,
"roles_from_db": []
}
],
"input_skill": "UI/UX",
"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": "Digital Architecture",
"matched_via": null,
"new_alias_persisted": false,
"new_alias_text": null,
"new_skill_meta": {
"derived": {
"category": "Conceptual Architectures",
"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": "digital-architecture",
"split_log": [],
"typed": null,
"warnings": []
},
"source_tag": "llm",
"was_in_llm_skills": true
},
{
"aliases_in_db": [],
"canonical": null,
"dimensions": [],
"input_skill": "Architectural Patterns",
"matched_via": null,
"new_alias_persisted": false,
"new_alias_text": null,
"new_skill_meta": {
"derived": {
"category": "Conceptual Architectures",
"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": "architectural-patterns",
"split_log": [],
"typed": null,
"warnings": []
},
"source_tag": "llm",
"was_in_llm_skills": true
},
{
"aliases_in_db": [],
"canonical": null,
"dimensions": [],
"input_skill": "Acceptance Criteria",
"matched_via": null,
"new_alias_persisted": false,
"new_alias_text": null,
"new_skill_meta": {
"derived": {
"category": "Agile Practices",
"skill_nature": "PRACTICE",
"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": "acceptance-criteria",
"split_log": [],
"typed": null,
"warnings": []
},
"source_tag": "llm",
"was_in_llm_skills": true
},
{
"aliases_in_db": [
{
"alias_text": "end-to-end tests",
"alias_type": "CANONICAL",
"id": 195,
"is_primary": true,
"match_strategy": "CASE_INSENSITIVE"
}
],
"canonical": {
"category_id": 8,
"display_name": "end-to-end tests",
"id": 58,
"is_also_category": false,
"is_extractable": true,
"skill_nature": "METHODOLOGY",
"slug": "end-to-end-tests",
"sub_category_id": 44,
"typical_lifespan": "EVERGREEN",
"volatility": "STABLE"
},
"dimensions": [
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Testing and Quality Assurance",
"id": 12,
"rationale": "Backend-specific test strategies used to validate service behavior and integration points. Covers automated test layers, contract checks, fixtures, and regression prevention.",
"slug": "testing-and-quality-assurance",
"source": "db"
},
"input_skill": "End-to-End Testing",
"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": "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": "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": "Scala Backend Developer",
"id": 87,
"rationale": null,
"role_archetype": "Engineering",
"slug": "scala-backend-developer",
"source": "db"
}
]
}
],
"input_skill": "End-to-End Testing",
"matched_via": "embedding_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": "Integration testing",
"alias_type": "CANONICAL",
"id": 2945,
"is_primary": true,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "integration testing",
"alias_type": "CANONICAL",
"id": 193,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
}
],
"canonical": {
"category_id": 8,
"display_name": "Integration testing",
"id": 56,
"is_also_category": false,
"is_extractable": true,
"skill_nature": "METHODOLOGY",
"slug": "integration-testing",
"sub_category_id": 44,
"typical_lifespan": "EVERGREEN",
"volatility": "STABLE"
},
"dimensions": [
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Testing and Defect Resolution",
"id": 262,
"rationale": "Validates Pega rules, flows, and integrations and then troubleshoots defects found in lower environments or production. This is a coherent cluster because the role is expected to verify platform behavior and fix rule-level issues.",
"slug": "testing-and-defect-resolution",
"source": "db"
},
"input_skill": "Functional Testing",
"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": "Testing and Quality Assurance",
"id": 12,
"rationale": "Backend-specific test strategies used to validate service behavior and integration points. Covers automated test layers, contract checks, fixtures, and regression prevention.",
"slug": "testing-and-quality-assurance",
"source": "db"
},
"input_skill": "Functional Testing",
"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": "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": "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": "Scala Backend Developer",
"id": 87,
"rationale": null,
"role_archetype": "Engineering",
"slug": "scala-backend-developer",
"source": "db"
}
]
}
],
"input_skill": "Functional Testing",
"matched_via": "embedding_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": "Non-Functional Testing",
"matched_via": null,
"new_alias_persisted": false,
"new_alias_text": null,
"new_skill_meta": {
"derived": {
"category": "Testing Practices",
"skill_nature": "PRACTICE",
"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": "non-functional-testing",
"split_log": [],
"typed": null,
"warnings": []
},
"source_tag": "llm",
"was_in_llm_skills": true
},
{
"aliases_in_db": [],
"canonical": null,
"dimensions": [],
"input_skill": "Sprint Planning",
"matched_via": null,
"new_alias_persisted": false,
"new_alias_text": null,
"new_skill_meta": {
"derived": {
"category": "Agile Practices",
"skill_nature": "PRACTICE",
"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": "sprint-planning",
"split_log": [],
"typed": null,
"warnings": []
},
"source_tag": "llm",
"was_in_llm_skills": true
},
{
"aliases_in_db": [],
"canonical": null,
"dimensions": [],
"input_skill": "Retrospective",
"matched_via": null,
"new_alias_persisted": false,
"new_alias_text": null,
"new_skill_meta": {
"derived": {
"category": "Agile Practices",
"skill_nature": "PRACTICE",
"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": "retrospective",
"split_log": [],
"typed": null,
"warnings": []
},
"source_tag": "llm",
"was_in_llm_skills": true
},
{
"aliases_in_db": [],
"canonical": null,
"dimensions": [],
"input_skill": "Backlog Refinement",
"matched_via": null,
"new_alias_persisted": false,
"new_alias_text": null,
"new_skill_meta": {
"derived": {
"category": "Agile Practices",
"skill_nature": "PRACTICE",
"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": "backlog-refinement",
"split_log": [],
"typed": null,
"warnings": []
},
"source_tag": "llm",
"was_in_llm_skills": true
},
{
"aliases_in_db": [],
"canonical": null,
"dimensions": [],
"input_skill": "Release Management",
"matched_via": null,
"new_alias_persisted": false,
"new_alias_text": null,
"new_skill_meta": {
"derived": {
"category": "Software Development Practices",
"skill_nature": "PRACTICE",
"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": "release-management",
"split_log": [],
"typed": null,
"warnings": []
},
"source_tag": "llm",
"was_in_llm_skills": true
}
],
"unmatched_skills": [
"Digital Architecture",
"Architectural Patterns",
"Acceptance Criteria",
"Non-Functional Testing",
"Sprint Planning",
"Retrospective",
"Backlog Refinement",
"Release Management"
]
}
API 3 — final-role-output
{
"chosen_role": {
"display_name": "Hybrid Mobile Developer",
"id": 11,
"rationale": "KRA-led classification on flutter-developer (skill weak, KRA 0.58)",
"role_archetype": null,
"slug": "hybrid-mobile-developer",
"source": "db"
},
"chosen_role_resolution": "in_db",
"final_input_skills": [
{
"skill": "Scrum",
"tag": "in_db"
},
{
"skill": "Agile",
"tag": "in_db"
},
{
"skill": "UI/UX",
"tag": "in_db"
},
{
"skill": "Digital Architecture",
"tag": "new"
},
{
"skill": "Architectural Patterns",
"tag": "new"
},
{
"skill": "Acceptance Criteria",
"tag": "new"
},
{
"skill": "End-to-End Testing",
"tag": "in_db"
},
{
"skill": "Functional Testing",
"tag": "in_db"
},
{
"skill": "Non-Functional Testing",
"tag": "new"
},
{
"skill": "Sprint Planning",
"tag": "new"
},
{
"skill": "Retrospective",
"tag": "new"
},
{
"skill": "Backlog Refinement",
"tag": "new"
},
{
"skill": "Release Management",
"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": 11,
"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": "Scrum",
"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": 1215,
"skill_tag": "in_db",
"skipped_reason": null
},
{
"chosen_role_id": 11,
"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": 11,
"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": "UI/UX",
"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": 1662,
"skill_tag": "in_db",
"skipped_reason": null
},
{
"chosen_role_id": 11,
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Testing and Quality Assurance",
"id": 12,
"rationale": "Backend-specific test strategies used to validate service behavior and integration points. Covers automated test layers, contract checks, fixtures, and regression prevention.",
"slug": "testing-and-quality-assurance",
"source": "db"
},
"dimension_id": 12,
"input_skill": "End-to-End Testing",
"llm_role": null,
"matched_chosen_role": false,
"outcome_line": "Skipped \u2014 no persistable v3 meta for new skill",
"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": "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": "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": "Scala Backend Developer",
"id": 87,
"rationale": null,
"role_archetype": "Engineering",
"slug": "scala-backend-developer",
"source": "db"
}
],
"skill_dimension_saved": false,
"skill_id": null,
"skill_tag": "new",
"skipped_reason": "skill_not_in_db_v3_proposed"
},
{
"chosen_role_id": 11,
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Testing and Defect Resolution",
"id": 262,
"rationale": "Validates Pega rules, flows, and integrations and then troubleshoots defects found in lower environments or production. This is a coherent cluster because the role is expected to verify platform behavior and fix rule-level issues.",
"slug": "testing-and-defect-resolution",
"source": "db"
},
"dimension_id": 262,
"input_skill": "Functional Testing",
"llm_role": null,
"matched_chosen_role": false,
"outcome_line": "Skipped \u2014 no persistable v3 meta for new skill",
"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": false,
"skill_id": null,
"skill_tag": "new",
"skipped_reason": "skill_not_in_db_v3_proposed"
},
{
"chosen_role_id": 11,
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Testing and Quality Assurance",
"id": 12,
"rationale": "Backend-specific test strategies used to validate service behavior and integration points. Covers automated test layers, contract checks, fixtures, and regression prevention.",
"slug": "testing-and-quality-assurance",
"source": "db"
},
"dimension_id": 12,
"input_skill": "Functional Testing",
"llm_role": null,
"matched_chosen_role": false,
"outcome_line": "Skipped \u2014 no persistable v3 meta for new skill",
"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": "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": "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": "Scala Backend Developer",
"id": 87,
"rationale": null,
"role_archetype": "Engineering",
"slug": "scala-backend-developer",
"source": "db"
}
],
"skill_dimension_saved": false,
"skill_id": null,
"skill_tag": "new",
"skipped_reason": "skill_not_in_db_v3_proposed"
}
],
"new_skills_created": 0,
"role_dimension_saved": 0,
"skill_dimension_saved": 0,
"skipped": 3
},
"planner_output": null,
"run_id": "4bba8f21-38ff-42d8-a2ef-6098afdcbcb1"
}
LLM Calls
Every model call made for this run, in pipeline order. Click a card to see the model's response.