Pipeline run
79ccacca-d272-41ed-ad47-71726ee06e8a
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
PwC Professional skills and responsibilities for this management level include but are not limited to As a Senior Associate, you'll work as part of a team of problem solvers, helping to solve complex…
1 POST /skills/extract-from-jd
2 POST /skills/extract-details
3 POST /skills/final-role-output
Site Reliability Engineer (SRE)
→Data Reliability Engineer
sub-role · 0.93 domain · DevOps & Platform CASE DOMAINslug: site-reliability-engineer-sre · id: 134 · source: db · sub-role slug: data-reliability-engineer
Domain=DevOps & Platform → sub-role data-reliability-engineer; The JD centers on batch/application operations, incident triage, on-call support, availability checks, SLA resolution, problem management, and root cause analysis, which best matches SRE responsibilities.
Matched skills
Matched dimensions
Matched KRAs
Resolution:
in_db
— role exists in library; skill↔dim and role↔dim links saved when applicable.
Job description
Line of Service Internal Firm Services Industry/Sector Not Applicable Specialism IFS - Operations Management Level Senior Associate Job Description & Summary A career in National Special Functions, within Internal Firm Services, will provide you with the opportunity to support service, sector, and market leaders deliver the unique PwC client experience to our clients. You'll play an important part in continuously innovating and improving Firm operations so that we can continue to provide the highest quality of services to our current and prospective clients. Our Analytics Insights team is responsible for serving as a strategic business partner for an assigned customer to identify and pursue new opportunities, conduct market analysis, and prepare revenue projections. You'll also develop new service offerings and solutions, enhance existing delivery capabilities, and support the delivery of solutions on engagements. To really stand out and make us fit for the future in a constantly changing world, each and every one of us at PwC needs to be a purpose-led and values-driven leader at every level. To help us achieve this we have the PwC Professional; our global leadership development framework. It gives us a single set of expectations across our lines, geographies and career paths, and provides transparency on the skills we need as individuals to be successful and progress in our careers, now and in the future. Responsibilities PwC Professional skills and responsibilities for this management level include but are not limited to As a Senior Associate, you'll work as part of a team of problem solvers, helping to solve complex business issues from strategy to execution. • JD: Execution of daily batch processing of data via ETL processes Attending to the operational requests and day-to-day management of the batch, application or environment Deployment of RFCs for UAT and Production deployments (where applicable) Performing triage and remediation of issues and incidents via ServiceNow On-call support for direct escalation of Priority 1 and Priority 2 incidents Performing early morning checks for application availability Resolving technical issues of the applications as per the agreed SLAs Problem Management (including performance and security) Monitoring systems for performance concerns or capacity issues Providing a data fix for an issue (with approval from Data Architects) Providing Root Cause Analysis for Non Conformities Providing Break-Fixes for any outage outside of warranty period Receive Knowledge Transition (KT) from the Scrum team before any new deployment into production environment Education (if blank, degree and/or field of study not specified) Degrees/Field Of Study Required Degrees/Field of Study preferred: Certifications (if blank, certifications not specified) Required Skills Optional Skills Desired Languages (If blank, desired languages not specified) Travel Requirements Not Specified Available for Work Visa Sponsorship? No Government Clearance Required? No Job Posting End Date
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
- Data Engineering Tools
- 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
- Testing Tools
- Sub-category
- general
- Skill nature
- PRACTICE
- Volatility
- MEDIUM
- Typical lifespan
- MULTI_YEAR
- Version strategy
- UNVERSIONED
Aliases — catalog
- production (CANONICAL) primary
Context tags (catalog)
Stored enrichment (catalog DB)
- Category
- Architecture
- Sub-category
- Environment Architecture
- Confidence
- 0.86
- Version strategy
- NOT_APPLICABLE
Maturity reasoning: “Production” as an environment architecture term appears in many JDs, but usually as a deployment target rather than a standalone skill; market signal is low standalone JD volume compared with AWS/Kubernetes/CI-CD roles.
Skill profile (library / DB)
- Skill nature
- PATTERN
- Volatility
- STABLE
- Typical lifespan
- EVERGREEN
- Category id
- 1
- Sub-category id
- 585
- Extractable
- True
- Also category
- False
Dimensions (API 2 worklist)
-
Environment Provisioning and Parity Catalog dimension db id 157
Library dimension (catalog)
Roles linked in library: DevOps Engineer
API 3 link attempts (this skill)
| Dimension | Skill↔dim | Role↔dim | Outcome |
|---|---|---|---|
|
Environment Provisioning and Parity
environment-provisioning-and-parity
|
✓ | — | 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
- Concepts
- Sub-category
- general
- Skill nature
- CONCEPT
- Volatility
- MEDIUM
- Typical lifespan
- MULTI_YEAR
- Version strategy
- UNVERSIONED
Aliases — catalog
- root cause analysis (CANONICAL) primary
- root-cause analysis (CANONICAL)
Context tags (catalog)
Stored enrichment (catalog DB)
- Category
- Methodology
- Sub-category
- Root Cause Analysis Methodology
- Confidence
- 0.96
- Version strategy
- NOT_APPLICABLE
Maturity reasoning: Root cause analysis is a standard incident/postmortem skill in SRE, ITIL, and quality roles; it appears broadly in job descriptions for operations, QA, and manufacturing, not as a niche tool.
Skill profile (library / DB)
- Skill nature
- METHODOLOGY
- Volatility
- STABLE
- Typical lifespan
- EVERGREEN
- Category id
- 8
- Sub-category id
- 3301
- Extractable
- True
- Also category
- False
Dimensions (API 2 worklist)
-
Observability and Diagnostics Catalog dimension db id 287
Library dimension (catalog)
Roles linked in library: Go Backend Developer, Java Backend Developer, Python Backend Developer
-
Site Troubleshooting and Debugging Catalog dimension db id 353
Library dimension (catalog)
Roles linked in library: Drupal Dev
-
Sitecore Troubleshooting and Maintenance Catalog dimension db id 447
Library dimension (catalog)
Roles linked in library: Sitecore Dev
API 3 link attempts (this skill)
| Dimension | Skill↔dim | Role↔dim | Outcome |
|---|---|---|---|
|
Observability and Diagnostics
observability-and-diagnostics
|
✓ | — | Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role) |
|
Site Troubleshooting and Debugging
site-troubleshooting-and-debugging
|
✓ | — | Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role) |
|
Sitecore Troubleshooting and Maintenance
sitecore-troubleshooting-and-maintenance
|
✓ | — | Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role) |
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) |
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 |
|---|---|---|---|---|---|---|
| Production | in_db |
Environment Provisioning and Parity
environment-provisioning-and-parity
|
✓ | — | Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role) | |
| Root Cause Analysis | in_db |
Observability and Diagnostics
observability-and-diagnostics
|
✓ | — | Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role) | |
| Root Cause Analysis | in_db |
Site Troubleshooting and Debugging
site-troubleshooting-and-debugging
|
✓ | — | Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role) | |
| Root Cause Analysis | in_db |
Sitecore Troubleshooting and Maintenance
sitecore-troubleshooting-and-maintenance
|
✓ | — | Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role) | |
| Scrum | in_db |
React Frontend Development
d_init_01
|
✓ | — | Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role) |
Library artifacts (this run)
| Kind | Detail | DB id |
|---|---|---|
| canonical_skill_proposed | ETL | type=Data Engineering Tools subtype=general nature=PRACTICE lifespan=MULTI_YEAR | |
| canonical_skill_proposed | UAT | type=Testing Tools subtype=general nature=PRACTICE lifespan=MULTI_YEAR | |
| canonical_skill_proposed | ServiceNow | type=Cloud Platforms subtype=general nature=PLATFORM lifespan=MULTI_YEAR | |
| canonical_skill_proposed | SLA | type=Concepts subtype=general nature=CONCEPT lifespan=MULTI_YEAR |
nano JD Parser — gpt-4.1-nano click to toggle
Show raw JSON
{
"JD_type": "pass",
"about_company": null,
"archetype_override_applied": true,
"archetype_override_matched_skills": [
"Scrum",
"Escalation",
"Make",
"production",
"Monitoring",
"Analytics",
"Triage",
"On-call support",
"root cause analysis"
],
"certifications": [],
"company_name": "PwC",
"ctc": null,
"domain": {
"primary": {
"aliases": [],
"domain": "Other"
},
"secondary": null
},
"education": [],
"experience": null,
"job_locations": [],
"role": "Senior Associate",
"role_aliases": [
"Associate",
"Senior Consultant",
"Senior Analyst"
],
"role_archetype": "Engineering",
"roles_and_responsibilities": [
{
"bullet_count": 12,
"heading": "Responsibilities",
"heading_was_present": true,
"source_marker": {
"first_5_words": "PwC Professional skills and responsibilities",
"last_5_words": "into production environment"
},
"text": "PwC Professional skills and responsibilities for this management level include but are not limited to\n\nAs a Senior Associate, you\u0027ll work as part of a team of problem solvers, helping to solve complex business issues from strategy to execution.\n\n\u2022 JD:\n\nExecution of daily batch processing of data via ETL processes\nAttending to the operational requests and day-to-day management of the batch, application or environment\nDeployment of RFCs for UAT and Production deployments (where applicable)\nPerforming triage and remediation of issues and incidents via ServiceNow\nOn-call support for direct escalation of Priority 1 and Priority 2 incidents\nPerforming early morning checks for application availability\nResolving technical issues of the applications as per the agreed SLAs\nProblem Management (including performance and security)\nMonitoring systems for performance concerns or capacity issues\nProviding a data fix for an issue (with approval from Data Architects)\nProviding Root Cause Analysis for Non Conformities\nProviding Break-Fixes for any outage outside of warranty period\nReceive Knowledge Transition (KT) from the Scrum team before any new deployment into production environment",
"word_count": 263
}
],
"urls": []
}
API 1 — extract-from-jd click to toggle
{
"final_skills": [
{
"is_primary": true,
"skill_name": "ETL"
},
{
"is_primary": true,
"skill_name": "UAT"
},
{
"is_primary": true,
"skill_name": "Production"
},
{
"is_primary": true,
"skill_name": "ServiceNow"
},
{
"is_primary": true,
"skill_name": "SLA"
},
{
"is_primary": true,
"skill_name": "Root Cause Analysis"
},
{
"is_primary": true,
"skill_name": "Scrum"
}
],
"jd_role": {
"display_name": "Senior Associate",
"rationale": null,
"role_aliases": [
"Associate",
"Senior Consultant",
"Senior Analyst"
],
"role_archetype": "Engineering",
"slug": ""
},
"nano_parsed": {
"JD_type": "pass",
"about_company": null,
"archetype_override_applied": true,
"archetype_override_matched_skills": [
"Scrum",
"Escalation",
"Make",
"production",
"Monitoring",
"Analytics",
"Triage",
"On-call support",
"root cause analysis"
],
"certifications": [],
"company_name": "PwC",
"ctc": null,
"domain": {
"primary": {
"aliases": [],
"domain": "Other"
},
"secondary": null
},
"education": [],
"experience": null,
"job_locations": [],
"role": "Senior Associate",
"role_aliases": [
"Associate",
"Senior Consultant",
"Senior Analyst"
],
"role_archetype": "Engineering",
"roles_and_responsibilities": [
{
"bullet_count": 12,
"heading": "Responsibilities",
"heading_was_present": true,
"source_marker": {
"first_5_words": "PwC Professional skills and responsibilities",
"last_5_words": "into production environment"
},
"text": "PwC Professional skills and responsibilities for this management level include but are not limited to\n\nAs a Senior Associate, you\u0027ll work as part of a team of problem solvers, helping to solve complex business issues from strategy to execution.\n\n\u2022 JD:\n\nExecution of daily batch processing of data via ETL processes\nAttending to the operational requests and day-to-day management of the batch, application or environment\nDeployment of RFCs for UAT and Production deployments (where applicable)\nPerforming triage and remediation of issues and incidents via ServiceNow\nOn-call support for direct escalation of Priority 1 and Priority 2 incidents\nPerforming early morning checks for application availability\nResolving technical issues of the applications as per the agreed SLAs\nProblem Management (including performance and security)\nMonitoring systems for performance concerns or capacity issues\nProviding a data fix for an issue (with approval from Data Architects)\nProviding Root Cause Analysis for Non Conformities\nProviding Break-Fixes for any outage outside of warranty period\nReceive Knowledge Transition (KT) from the Scrum team before any new deployment into production environment",
"word_count": 263
}
],
"urls": []
},
"rejected": false,
"rejection_reason": null,
"run_id": "79ccacca-d272-41ed-ad47-71726ee06e8a",
"stage3_signals": {
"alias_found": false,
"alias_match_roles": [],
"kra_match_roles": [
{
"display_name": "Scala Backend Developer",
"kra_matches": [
{
"kra_text": "performance and reliability tuning",
"sentence": "Monitoring systems for performance concerns or capacity issues",
"similarity": 0.5684
},
{
"kra_text": "automated backend checks",
"sentence": "Performing early morning checks for application availability",
"similarity": 0.5352
},
{
"kra_text": "defect investigation and fixes",
"sentence": "Providing Break-Fixes for any outage outside of warranty period",
"similarity": 0.5078
}
],
"matched_count": null,
"matched_skills": null,
"role_id": 87,
"score": 0.5371,
"slug": "scala-backend-developer",
"total_count": null
},
{
"display_name": "Ruby Backend Developer",
"kra_matches": [
{
"kra_text": "automated backend checks",
"sentence": "Performing early morning checks for application availability",
"similarity": 0.5352
},
{
"kra_text": "backend defect diagnosis and fixes",
"sentence": "Providing Break-Fixes for any outage outside of warranty period",
"similarity": 0.5234
},
{
"kra_text": "backend defect diagnosis and fixes",
"sentence": "Providing a data fix for an issue (with approval from Data Architects)",
"similarity": 0.5147
}
],
"matched_count": null,
"matched_skills": null,
"role_id": 85,
"score": 0.5244,
"slug": "ruby-backend-developer",
"total_count": null
},
{
"display_name": "Java Backend Developer",
"kra_matches": [
{
"kra_text": "backend performance tuning",
"sentence": "Monitoring systems for performance concerns or capacity issues",
"similarity": 0.6022
},
{
"kra_text": "backend performance tuning",
"sentence": "Problem Management (including performance and security)",
"similarity": 0.4908
},
{
"kra_text": "code refactoring and defect fixes",
"sentence": "Providing a data fix for an issue (with approval from Data Architects)",
"similarity": 0.4609
}
],
"matched_count": null,
"matched_skills": null,
"role_id": 79,
"score": 0.518,
"slug": "java-backend-developer",
"total_count": null
},
{
"display_name": ".NET Backend Developer",
"kra_matches": [
{
"kra_text": "service-level technical collaboration",
"sentence": "Resolving technical issues of the applications as per the agreed SLAs",
"similarity": 0.5438
},
{
"kra_text": "automated backend checks",
"sentence": "Performing early morning checks for application availability",
"similarity": 0.5352
},
{
"kra_text": "defect investigation and resolution",
"sentence": "Providing Root Cause Analysis for Non Conformities",
"similarity": 0.4606
}
],
"matched_count": null,
"matched_skills": null,
"role_id": 83,
"score": 0.5132,
"slug": "dotnet-backend-developer",
"total_count": null
},
{
"display_name": "PHP Backend Developer",
"kra_matches": [
{
"kra_text": "performance and reliability tuning",
"sentence": "Monitoring systems for performance concerns or capacity issues",
"similarity": 0.5684
},
{
"kra_text": "performance and reliability tuning",
"sentence": "Problem Management (including performance and security)",
"similarity": 0.5051
},
{
"kra_text": "defect diagnosis and remediation",
"sentence": "Providing Root Cause Analysis for Non Conformities",
"similarity": 0.4554
}
],
"matched_count": null,
"matched_skills": null,
"role_id": 86,
"score": 0.5096,
"slug": "php-backend-developer",
"total_count": null
}
],
"skill_match_roles": [
{
"display_name": "DevOps Engineer",
"kra_matches": null,
"matched_count": 1,
"matched_skills": [
"production"
],
"role_id": 10,
"score": 0.1429,
"slug": "devops-engineer",
"total_count": 7
},
{
"display_name": "Java Backend Developer",
"kra_matches": null,
"matched_count": 1,
"matched_skills": [
"root cause analysis"
],
"role_id": 79,
"score": 0.1429,
"slug": "java-backend-developer",
"total_count": 7
},
{
"display_name": "Python Backend Developer",
"kra_matches": null,
"matched_count": 1,
"matched_skills": [
"root cause analysis"
],
"role_id": 80,
"score": 0.1429,
"slug": "python-backend-developer",
"total_count": 7
},
{
"display_name": "Go Backend Developer",
"kra_matches": null,
"matched_count": 1,
"matched_skills": [
"root cause analysis"
],
"role_id": 81,
"score": 0.1429,
"slug": "go-backend-developer",
"total_count": 7
},
{
"display_name": "Drupal Dev",
"kra_matches": null,
"matched_count": 1,
"matched_skills": [
"root cause analysis"
],
"role_id": 228,
"score": 0.1429,
"slug": "drupal-dev",
"total_count": 7
}
]
},
"stage4_decision": {
"alias_collision_detected": false,
"case": "DOMAIN",
"chosen_role": {
"display_name": "Site Reliability Engineer (SRE)",
"kra_matches": null,
"matched_count": null,
"matched_skills": null,
"role_id": 134,
"score": 0.87,
"slug": "site-reliability-engineer-sre",
"total_count": null
},
"confidence": 0.87,
"is_new_role": false,
"llm2_fired": false,
"llm2_reasoning": null,
"matched_dimensions": [
"Production Operations",
"Incident Management",
"Application Reliability",
"Batch Job Support",
"SLA Management",
"Problem Management",
"Availability Monitoring",
"Capacity and Performance Management"
],
"matched_kras": [
"Execution of daily batch processing of data via ETL processes",
"Attending to the operational requests and day-to-day management",
"Deployment of RFCs for UAT and Production deployments",
"Performing triage and remediation of issues and incidents",
"On-call support for direct escalation of Priority 1 and Priority 2 incidents",
"Performing early morning checks for application availability",
"Resolving technical issues of the applications as per the agreed SLAs",
"Providing Root Cause Analysis for Non Conformities",
"Providing Break-Fixes for any outage outside of warranty period",
"Monitoring systems for performance concerns or capacity issues"
],
"matched_skills": [
"ETL",
"ServiceNow",
"UAT",
"Production deployments",
"Root Cause Analysis"
],
"new_role_display_name": null,
"new_role_slug": null,
"queued": false,
"reasoning": "Domain=DevOps \u0026 Platform \u2192 sub-role data-reliability-engineer; The JD centers on batch/application operations, incident triage, on-call support, availability checks, SLA resolution, problem management, and root cause analysis, which best matches SRE responsibilities.",
"sub_role": {
"confidence": 0.93,
"display_name": "Data Reliability Engineer",
"reasoning": "The JD is centered on ETL/batch data processing, data fixes, and operational support for data systems, which best matches Data Reliability Engineer.",
"role_id": 388,
"slug": "data-reliability-engineer"
}
},
"stage5_updates": {
"centroid_n_after": 4,
"centroid_updated": true,
"collision_log_id": null,
"new_kra_attached": {
"best_kra_similarity": 0.0,
"queue_id": 369,
"r_and_r_preview": "PwC Professional skills and responsibilities for this management level include but are not limited to\n\nAs a Senior Associate, you\u0027ll work as part of a team of problem solvers, helping to solve complex",
"role_display_name": "Site Reliability Engineer (SRE)",
"role_slug": "site-reliability-engineer-sre",
"status": "pending"
},
"new_skills_attached": [
{
"is_primary": true,
"queue_id": 7018,
"role_display_name": "Site Reliability Engineer (SRE)",
"role_slug": "site-reliability-engineer-sre",
"skill_name": "ETL",
"status": "pending"
},
{
"is_primary": true,
"queue_id": 7019,
"role_display_name": "Site Reliability Engineer (SRE)",
"role_slug": "site-reliability-engineer-sre",
"skill_name": "UAT",
"status": "pending"
},
{
"is_primary": true,
"queue_id": 7020,
"role_display_name": "Site Reliability Engineer (SRE)",
"role_slug": "site-reliability-engineer-sre",
"skill_name": "ServiceNow",
"status": "pending"
},
{
"is_primary": true,
"queue_id": 7021,
"role_display_name": "Site Reliability Engineer (SRE)",
"role_slug": "site-reliability-engineer-sre",
"skill_name": "SLA",
"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": 1453,
"existing_alias_text": "production",
"input_term": "Production",
"matched_canonical": {
"category_id": 1,
"display_name": "production",
"id": 891,
"is_also_category": false,
"is_extractable": true,
"skill_nature": "PATTERN",
"slug": "production",
"sub_category_id": 585,
"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": 3688,
"existing_alias_text": "root cause analysis",
"input_term": "Root Cause Analysis",
"matched_canonical": {
"category_id": 8,
"display_name": "root cause analysis",
"id": 2392,
"is_also_category": false,
"is_extractable": true,
"skill_nature": "METHODOLOGY",
"slug": "root-cause-analysis",
"sub_category_id": 3301,
"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": 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"
}
],
"candidate_roles": [
{
"display_name": "DevOps Engineer",
"id": 10,
"rationale": null,
"role_archetype": null,
"slug": "devops-engineer",
"source": "db"
},
{
"display_name": "Go Backend Developer",
"id": 81,
"rationale": null,
"role_archetype": "Engineering",
"slug": "go-backend-developer",
"source": "db"
},
{
"display_name": "Java Backend Developer",
"id": 79,
"rationale": null,
"role_archetype": "Engineering",
"slug": "java-backend-developer",
"source": "db"
},
{
"display_name": "Python Backend Developer",
"id": 80,
"rationale": null,
"role_archetype": "Engineering",
"slug": "python-backend-developer",
"source": "db"
},
{
"display_name": "Drupal Dev",
"id": 228,
"rationale": null,
"role_archetype": "Engineering",
"slug": "drupal-dev",
"source": "db"
},
{
"display_name": "Sitecore Dev",
"id": 233,
"rationale": null,
"role_archetype": "Engineering",
"slug": "sitecore-dev",
"source": "db"
}
],
"chosen_role": {
"display_name": "Site Reliability Engineer (SRE)",
"id": 134,
"rationale": "Domain=DevOps \u0026 Platform \u2192 sub-role data-reliability-engineer; The JD centers on batch/application operations, incident triage, on-call support, availability checks, SLA resolution, problem management, and root cause analysis, which best matches SRE responsibilities.",
"role_archetype": null,
"slug": "site-reliability-engineer-sre",
"source": "db"
},
"dimensions": [
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Environment Provisioning and Parity",
"id": 157,
"rationale": "Creating and maintaining consistent dev, test, staging, and production environments. This cluster is coherent because delivery failures often come from environment drift, missing dependencies, or inconsistent configuration.",
"slug": "environment-provisioning-and-parity",
"source": "db"
},
"input_skill": "Production",
"llm_role": null,
"roles_from_db": [
{
"display_name": "DevOps Engineer",
"id": 10,
"rationale": null,
"role_archetype": null,
"slug": "devops-engineer",
"source": "db"
}
]
},
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Observability and Diagnostics",
"id": 287,
"rationale": "Instrumentation and troubleshooting practices used to understand Java service behavior in production and lower environments. This cluster covers logs, metrics, traces, correlation IDs, and root-cause analysis from service telemetry.",
"slug": "observability-and-diagnostics",
"source": "db"
},
"input_skill": "Root Cause Analysis",
"llm_role": null,
"roles_from_db": [
{
"display_name": "Go Backend Developer",
"id": 81,
"rationale": null,
"role_archetype": "Engineering",
"slug": "go-backend-developer",
"source": "db"
},
{
"display_name": "Java Backend Developer",
"id": 79,
"rationale": null,
"role_archetype": "Engineering",
"slug": "java-backend-developer",
"source": "db"
},
{
"display_name": "Python Backend Developer",
"id": 80,
"rationale": null,
"role_archetype": "Engineering",
"slug": "python-backend-developer",
"source": "db"
}
]
},
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Site Troubleshooting and Debugging",
"id": 353,
"rationale": "Diagnosing and fixing Drupal site defects across custom code, configuration, and runtime behavior. This is a coherent cluster because Drupal developers are expected to trace issues from symptoms back to modules, templates, or config.",
"slug": "site-troubleshooting-and-debugging",
"source": "db"
},
"input_skill": "Root Cause Analysis",
"llm_role": null,
"roles_from_db": [
{
"display_name": "Drupal Dev",
"id": 228,
"rationale": null,
"role_archetype": "Engineering",
"slug": "drupal-dev",
"source": "db"
}
]
},
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Sitecore Troubleshooting and Maintenance",
"id": 447,
"rationale": "Diagnosing defects, regressions, and maintainability issues across Sitecore code, configuration, and content behavior. This is a coherent cluster because the role is expected to stabilize the site experience over time.",
"slug": "sitecore-troubleshooting-and-maintenance",
"source": "db"
},
"input_skill": "Root Cause Analysis",
"llm_role": null,
"roles_from_db": [
{
"display_name": "Sitecore Dev",
"id": 233,
"rationale": null,
"role_archetype": "Engineering",
"slug": "sitecore-dev",
"source": "db"
}
]
},
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "React Frontend Development",
"id": 96,
"rationale": "Building interactive web user interfaces with React.js, including component composition, state management, hooks, and rendering patterns. React.js belongs here because it is a core library for client-side UI development in modern web applications.",
"slug": "d_init_01",
"source": "db"
},
"input_skill": "Scrum",
"llm_role": null,
"roles_from_db": []
}
],
"input_final_skills": [
"ETL",
"UAT",
"Production",
"ServiceNow",
"SLA",
"Root Cause Analysis",
"Scrum"
],
"input_llm_skills": [
"ETL",
"UAT",
"Production",
"ServiceNow",
"SLA",
"Root Cause Analysis",
"Scrum"
],
"new_aliases_persisted": 0,
"run_id": "79ccacca-d272-41ed-ad47-71726ee06e8a",
"skills_detail": [
{
"aliases_in_db": [],
"canonical": null,
"dimensions": [],
"input_skill": "ETL",
"matched_via": null,
"new_alias_persisted": false,
"new_alias_text": null,
"new_skill_meta": {
"derived": {
"category": "Data Engineering Tools",
"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": "etl",
"split_log": [],
"typed": null,
"warnings": []
},
"source_tag": "llm",
"was_in_llm_skills": true
},
{
"aliases_in_db": [],
"canonical": null,
"dimensions": [],
"input_skill": "UAT",
"matched_via": null,
"new_alias_persisted": false,
"new_alias_text": null,
"new_skill_meta": {
"derived": {
"category": "Testing Tools",
"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": "uat",
"split_log": [],
"typed": null,
"warnings": []
},
"source_tag": "llm",
"was_in_llm_skills": true
},
{
"aliases_in_db": [
{
"alias_text": "production",
"alias_type": "CANONICAL",
"id": 1453,
"is_primary": true,
"match_strategy": "CASE_INSENSITIVE"
}
],
"canonical": {
"category_id": 1,
"display_name": "production",
"id": 891,
"is_also_category": false,
"is_extractable": true,
"skill_nature": "PATTERN",
"slug": "production",
"sub_category_id": 585,
"typical_lifespan": "EVERGREEN",
"volatility": "STABLE"
},
"dimensions": [
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Environment Provisioning and Parity",
"id": 157,
"rationale": "Creating and maintaining consistent dev, test, staging, and production environments. This cluster is coherent because delivery failures often come from environment drift, missing dependencies, or inconsistent configuration.",
"slug": "environment-provisioning-and-parity",
"source": "db"
},
"input_skill": "Production",
"llm_role": null,
"roles_from_db": [
{
"display_name": "DevOps Engineer",
"id": 10,
"rationale": null,
"role_archetype": null,
"slug": "devops-engineer",
"source": "db"
}
]
}
],
"input_skill": "Production",
"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": "ServiceNow",
"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": "servicenow",
"split_log": [],
"typed": null,
"warnings": []
},
"source_tag": "llm",
"was_in_llm_skills": true
},
{
"aliases_in_db": [],
"canonical": null,
"dimensions": [],
"input_skill": "SLA",
"matched_via": null,
"new_alias_persisted": false,
"new_alias_text": null,
"new_skill_meta": {
"derived": {
"category": "Concepts",
"skill_nature": "CONCEPT",
"sub_category": "general",
"typical_lifespan": "MULTI_YEAR",
"version_strategy": "UNVERSIONED",
"volatility": "MEDIUM"
},
"enrichment": null,
"keep_log": [],
"locked_dimensions": [],
"merge_log": [],
"placed": null,
"relationships": null,
"skill_id": "sla",
"split_log": [],
"typed": null,
"warnings": []
},
"source_tag": "llm",
"was_in_llm_skills": true
},
{
"aliases_in_db": [
{
"alias_text": "root cause analysis",
"alias_type": "CANONICAL",
"id": 3688,
"is_primary": true,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "root-cause analysis",
"alias_type": "CANONICAL",
"id": 4634,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
}
],
"canonical": {
"category_id": 8,
"display_name": "root cause analysis",
"id": 2392,
"is_also_category": false,
"is_extractable": true,
"skill_nature": "METHODOLOGY",
"slug": "root-cause-analysis",
"sub_category_id": 3301,
"typical_lifespan": "EVERGREEN",
"volatility": "STABLE"
},
"dimensions": [
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Observability and Diagnostics",
"id": 287,
"rationale": "Instrumentation and troubleshooting practices used to understand Java service behavior in production and lower environments. This cluster covers logs, metrics, traces, correlation IDs, and root-cause analysis from service telemetry.",
"slug": "observability-and-diagnostics",
"source": "db"
},
"input_skill": "Root Cause Analysis",
"llm_role": null,
"roles_from_db": [
{
"display_name": "Go Backend Developer",
"id": 81,
"rationale": null,
"role_archetype": "Engineering",
"slug": "go-backend-developer",
"source": "db"
},
{
"display_name": "Java Backend Developer",
"id": 79,
"rationale": null,
"role_archetype": "Engineering",
"slug": "java-backend-developer",
"source": "db"
},
{
"display_name": "Python Backend Developer",
"id": 80,
"rationale": null,
"role_archetype": "Engineering",
"slug": "python-backend-developer",
"source": "db"
}
]
},
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Site Troubleshooting and Debugging",
"id": 353,
"rationale": "Diagnosing and fixing Drupal site defects across custom code, configuration, and runtime behavior. This is a coherent cluster because Drupal developers are expected to trace issues from symptoms back to modules, templates, or config.",
"slug": "site-troubleshooting-and-debugging",
"source": "db"
},
"input_skill": "Root Cause Analysis",
"llm_role": null,
"roles_from_db": [
{
"display_name": "Drupal Dev",
"id": 228,
"rationale": null,
"role_archetype": "Engineering",
"slug": "drupal-dev",
"source": "db"
}
]
},
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Sitecore Troubleshooting and Maintenance",
"id": 447,
"rationale": "Diagnosing defects, regressions, and maintainability issues across Sitecore code, configuration, and content behavior. This is a coherent cluster because the role is expected to stabilize the site experience over time.",
"slug": "sitecore-troubleshooting-and-maintenance",
"source": "db"
},
"input_skill": "Root Cause Analysis",
"llm_role": null,
"roles_from_db": [
{
"display_name": "Sitecore Dev",
"id": 233,
"rationale": null,
"role_archetype": "Engineering",
"slug": "sitecore-dev",
"source": "db"
}
]
}
],
"input_skill": "Root Cause Analysis",
"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": "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
}
],
"unmatched_skills": [
"ETL",
"UAT",
"ServiceNow",
"SLA"
]
}
API 3 — final-role-output
{
"chosen_role": {
"display_name": "Site Reliability Engineer (SRE)",
"id": 134,
"rationale": "Domain=DevOps \u0026 Platform \u2192 sub-role data-reliability-engineer; The JD centers on batch/application operations, incident triage, on-call support, availability checks, SLA resolution, problem management, and root cause analysis, which best matches SRE responsibilities.",
"role_archetype": null,
"slug": "site-reliability-engineer-sre",
"source": "db"
},
"chosen_role_resolution": "in_db",
"final_input_skills": [
{
"skill": "ETL",
"tag": "new"
},
{
"skill": "UAT",
"tag": "new"
},
{
"skill": "Production",
"tag": "in_db"
},
{
"skill": "ServiceNow",
"tag": "new"
},
{
"skill": "SLA",
"tag": "new"
},
{
"skill": "Root Cause Analysis",
"tag": "in_db"
},
{
"skill": "Scrum",
"tag": "in_db"
}
],
"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": 134,
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Environment Provisioning and Parity",
"id": 157,
"rationale": "Creating and maintaining consistent dev, test, staging, and production environments. This cluster is coherent because delivery failures often come from environment drift, missing dependencies, or inconsistent configuration.",
"slug": "environment-provisioning-and-parity",
"source": "db"
},
"dimension_id": 157,
"input_skill": "Production",
"llm_role": null,
"matched_chosen_role": false,
"outcome_line": "Existing dimension (library) \u00b7 Role\u2194dimension skipped (dimension not under chosen role)",
"role_dimension_saved": false,
"roles_from_db": [
{
"display_name": "DevOps Engineer",
"id": 10,
"rationale": null,
"role_archetype": null,
"slug": "devops-engineer",
"source": "db"
}
],
"skill_dimension_saved": true,
"skill_id": 891,
"skill_tag": "in_db",
"skipped_reason": null
},
{
"chosen_role_id": 134,
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Observability and Diagnostics",
"id": 287,
"rationale": "Instrumentation and troubleshooting practices used to understand Java service behavior in production and lower environments. This cluster covers logs, metrics, traces, correlation IDs, and root-cause analysis from service telemetry.",
"slug": "observability-and-diagnostics",
"source": "db"
},
"dimension_id": 287,
"input_skill": "Root Cause Analysis",
"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": "Go Backend Developer",
"id": 81,
"rationale": null,
"role_archetype": "Engineering",
"slug": "go-backend-developer",
"source": "db"
},
{
"display_name": "Java Backend Developer",
"id": 79,
"rationale": null,
"role_archetype": "Engineering",
"slug": "java-backend-developer",
"source": "db"
},
{
"display_name": "Python Backend Developer",
"id": 80,
"rationale": null,
"role_archetype": "Engineering",
"slug": "python-backend-developer",
"source": "db"
}
],
"skill_dimension_saved": true,
"skill_id": 2392,
"skill_tag": "in_db",
"skipped_reason": null
},
{
"chosen_role_id": 134,
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Site Troubleshooting and Debugging",
"id": 353,
"rationale": "Diagnosing and fixing Drupal site defects across custom code, configuration, and runtime behavior. This is a coherent cluster because Drupal developers are expected to trace issues from symptoms back to modules, templates, or config.",
"slug": "site-troubleshooting-and-debugging",
"source": "db"
},
"dimension_id": 353,
"input_skill": "Root Cause Analysis",
"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": "Drupal Dev",
"id": 228,
"rationale": null,
"role_archetype": "Engineering",
"slug": "drupal-dev",
"source": "db"
}
],
"skill_dimension_saved": true,
"skill_id": 2392,
"skill_tag": "in_db",
"skipped_reason": null
},
{
"chosen_role_id": 134,
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Sitecore Troubleshooting and Maintenance",
"id": 447,
"rationale": "Diagnosing defects, regressions, and maintainability issues across Sitecore code, configuration, and content behavior. This is a coherent cluster because the role is expected to stabilize the site experience over time.",
"slug": "sitecore-troubleshooting-and-maintenance",
"source": "db"
},
"dimension_id": 447,
"input_skill": "Root Cause Analysis",
"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": "Sitecore Dev",
"id": 233,
"rationale": null,
"role_archetype": "Engineering",
"slug": "sitecore-dev",
"source": "db"
}
],
"skill_dimension_saved": true,
"skill_id": 2392,
"skill_tag": "in_db",
"skipped_reason": null
},
{
"chosen_role_id": 134,
"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
}
],
"new_skills_created": 0,
"role_dimension_saved": 0,
"skill_dimension_saved": 0,
"skipped": 0
},
"planner_output": null,
"run_id": "79ccacca-d272-41ed-ad47-71726ee06e8a"
}
LLM Calls
Every model call made for this run, in pipeline order. Click a card to see the model's response.