Pipeline run
db06e85d-5e2c-4647-9ef2-1cdac6390266
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
1 POST /skills/extract-from-jd
2 POST /skills/extract-details
3 POST /skills/final-role-output
DevOps Engineer
→CI/CD Engineer
sub-role · 0.93 domain · DevOps & Platform CASE DOMAINslug: devops-engineer · id: 10 · source: db · sub-role slug: ci-cd-engineer
Domain=DevOps & Platform → sub-role ci-cd-engineer; The JD emphasizes CI/CD, infrastructure as code, containerized deployments, secure software delivery, and site reliability practices, which best matches DevOps Engineering.
Matched skills
Matched dimensions
Matched KRAs
Resolution:
in_db
— role exists in library; skill↔dim and role↔dim links saved when applicable.
Job description
Description: Part of a cross-disciplinary team, working closely with other data engineers, software engineers, data scientists, data managers and business partners. Requirements: • BS degree in computer science • Deep and hands-on experience (typically 5+ years) designing, planning, productionizing, maintaining and documenting reliable and scalable data infrastructure and data products in complex environments • Development experience in one or more object-oriented programming languages (e.g. Python, Go, Java, C++) • Advanced SQL knowledge • Experience designing and implementing large-scale distributed systems • Deep knowledge and hands-on experience in technologies across all data lifecycle stages . • Strong stakeholder management and ability to lead large organizations through influence • Continuous learning and improvement mindset • No prior experience in the energy industry required Preferences: SQL, Python,Java, Docker, Data Engineer Job Responsibilities: • Architects, designs, implements and maintains reliable and scalable data infrastructure. • Writes, deploys and maintains software to build, integrate, manage, maintain, and quality assure data at bp. • Adheres to and advocates for software engineering best practices (e.g. technical design, technical design review, unit testing, monitoring & alerting, checking in code, code review, documentation), • Responsible for deploying secure and well-tested software that meets privacy and compliance requirements; develops, maintains and improves CI / CD pipeline, • Responsible for service reliability and following site-reliability engineering best practices: on-call rotations for services they maintain, responsible for defining and maintaining SLAs. Design, build, deploy and maintain infrastructure as code. Containerizes server deployments. • Actively contributes to improve developer velocity. What We Offer Exciting Projects: We focus on industries like High-Tech, communication, media, healthcare, retail and telecom. Our customer list is full of fantastic global brands and leaders who love what we build for them. Collaborative Environment: You Can expand your skills by collaborating with a diverse team of highly talented people in an open, laidback environment — or even abroad in one of our global centers or client facilities! Work-Life Balance: GlobalLogic prioritizes work-life balance, which is why we offer flexible work schedules, opportunities to work from home, and paid time off and holidays. Professional Development: Our dedicated Learning & Development team regularly organizes Communication skills training(GL Vantage, Toast Master),Stress Management program, professional certifications, and technical and soft skill trainings. Excellent Benefits: We provide our employees with competitive salaries, family medical insurance, Group Term Life Insurance, Group Personal Accident Insurance , NPS(National Pension Scheme ), Periodic health awareness program, extended maternity leave, annual performance bonuses, and referral bonuses. Fun Perks: We want you to love where you work, which is why we host sports events, cultural activities, offer food on subsidies rates, Corporate parties. Our vibrant offices also include dedicated GL Zones, rooftop decks and GL Club where you can drink coffee or tea with your colleagues over a game of table and offer discounts for popular stores and restaurants! About GlobalLogic GlobalLogic is a leader in digital engineering. We help brands across the globe design and build innovative products, platforms, and digital experiences for the modern world. By integrating experience design, complex engineering, and data expertise—we help our clients imagine what’s possible, and accelerate their transition into tomorrow’s digital businesses. Headquartered in Silicon Valley, GlobalLogic operates design studios and engineering centers around the world, extending our deep expertise to customers in the automotive, communications, financial services, healthcare and life sciences, manufacturing, media and entertainment, semiconductor, and technology industries. GlobalLogic is a Hitachi Group Company operating under Hitachi, Ltd. (TSE: 6501) which contributes to a sustainable society with a higher quality of life by driving innovation through data and technology as the Social Innovation Business.
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
- CI/CD (CANONICAL)
Context tags (catalog)
Stored enrichment (catalog DB)
- Category
- Methodology
- Sub-category
- Ci Cd Process
- Confidence
- 0.93
- Version strategy
- NOT_APPLICABLE
Maturity reasoning: CI/CD appears in a large share of software engineering JDs and is a standard requirement across DevOps, platform, and backend roles; major vendors like GitHub, GitLab, and AWS all center product roadmaps on CI/CD pipelines.
Skill profile (library / DB)
- Skill nature
- METHODOLOGY
- Volatility
- STABLE
- Typical lifespan
- EVERGREEN
- Category id
- 8
- Sub-category id
- 900
- Extractable
- True
- Also category
- False
Dimensions (API 2 worklist)
-
CI/CD Pipeline Platforms Catalog dimension db id 150
Library dimension (catalog)
Roles linked in library: DevOps Engineer
-
CI/CD for Machine Learning Catalog dimension db id 56
Library dimension (catalog)
Roles linked in library: ML Engineer
API 3 link attempts (this skill)
| Dimension | Skill↔dim | Role↔dim | Outcome |
|---|---|---|---|
|
CI/CD Pipeline Platforms
ci-cd-pipeline-platforms
|
✓ | ✓ | Existing dimension (library) · Role↔dimension saved |
|
CI/CD for Machine Learning
ci-cd-for-machine-learning
|
✓ | — | 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
- Practice
- 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
- Concepts
- Sub-category
- general
- Skill nature
- CONCEPT
- Volatility
- MEDIUM
- Typical lifespan
- MULTI_YEAR
- Version strategy
- UNVERSIONED
Aliases — catalog
- Unit Testing (CANONICAL)
Context tags (catalog)
Stored enrichment (catalog DB)
- Category
- Methodology
- Sub-category
- Testing Methodology
- Confidence
- 0.98
- Version strategy
- NOT_APPLICABLE
Maturity reasoning: Unit testing is a standard hiring requirement across software JDs and appears in mainstream frameworks/docs; GitHub and Stack Overflow usage remain consistently high, with no successor replacing it.
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)
-
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
- Monitoring (CANONICAL)
Context tags (catalog)
Stored enrichment (catalog DB)
- Category
- Concept
- Sub-category
- Observability Monitoring
- Confidence
- 0.88
- Version strategy
- NOT_APPLICABLE
Maturity reasoning: Monitoring is a standard requirement in most SRE/DevOps job descriptions and is bundled into major platforms like AWS CloudWatch, Datadog, and Prometheus, indicating broad market adoption.
Skill profile (library / DB)
- Skill nature
- CONCEPT
- Volatility
- STABLE
- Typical lifespan
- EVERGREEN
- Category id
- 2
- Sub-category id
- 924
- Extractable
- True
- Also category
- False
Dimensions (API 2 worklist)
-
Observability and Incident Triage Catalog dimension db id 155
Library dimension (catalog)
Roles linked in library: DevOps Engineer
API 3 link attempts (this skill)
| Dimension | Skill↔dim | Role↔dim | Outcome |
|---|---|---|---|
|
Observability and Incident Triage
observability-and-incident-triage
|
✓ | ✓ | Existing dimension (library) · Role↔dimension saved |
Aliases — catalog
- alerting (CANONICAL) primary
Context tags (catalog)
Stored enrichment (catalog DB)
- Category
- Concept
- Sub-category
- Alerting
- Confidence
- 0.90
- Version strategy
- NOT_APPLICABLE
Maturity reasoning: Alerting is a standard SRE/DevOps requirement and appears in many JDs alongside Prometheus, Grafana, PagerDuty, and Datadog; vendors actively market alerting features rather than sunsetting them.
Skill profile (library / DB)
- Skill nature
- CONCEPT
- Volatility
- STABLE
- Typical lifespan
- EVERGREEN
- Category id
- 2
- Sub-category id
- 3472
- Extractable
- True
- Also category
- False
Dimensions (API 2 worklist)
-
Backend Observability, Logging, and Diagnostics Catalog dimension db id 388
Library dimension (catalog)
Roles linked in library: Kotlin Backend Developer, Scala Backend Developer
-
Observability and Incident Response Catalog dimension db id 10
Library dimension (catalog)
Roles linked in library: .NET Backend Developer, Backend Developer, Node.js Backend Developer, PHP Backend Developer
-
Observability and Incident Triage Catalog dimension db id 155
Library dimension (catalog)
Roles linked in library: DevOps Engineer
API 3 link attempts (this skill)
| Dimension | Skill↔dim | Role↔dim | Outcome |
|---|---|---|---|
|
Backend Observability, Logging, and Diagnostics
backend-observability-logging-and-diagnostics
|
✓ | — | Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role) |
|
Observability and Incident Response
observability-and-incident-response
|
✓ | — | Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role) |
|
Observability and Incident Triage
observability-and-incident-triage
|
✓ | ✓ | Existing dimension (library) · Role↔dimension saved |
Aliases — catalog
- Code Review (CANONICAL)
Context tags (catalog)
Stored enrichment (catalog DB)
- Category
- SoftSkill
- Sub-category
- Code Review
- Confidence
- 0.96
- Version strategy
- NOT_APPLICABLE
Maturity reasoning: Code review is a standard hiring-pipeline requirement in engineering JDs and is built into major platforms like GitHub/GitLab pull-request workflows, indicating broad adoption.
Skill profile (library / DB)
- Skill nature
- PRACTICE
- Volatility
- STABLE
- Typical lifespan
- EVERGREEN
- Category id
- 58
- Sub-category id
- 364
- 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
- Soft Skills
- Sub-category
- general
- Skill nature
- PRACTICE
- Volatility
- STABLE
- Typical lifespan
- EVERGREEN
- Version strategy
- UNVERSIONED
Aliases — catalog
- Site Reliability Engineering (CANONICAL)
Context tags (catalog)
Stored enrichment (catalog DB)
- Category
- Methodology
- Sub-category
- Site Reliability Engineering
- Confidence
- 0.94
- Version strategy
- NOT_APPLICABLE
Maturity reasoning: SRE is a hiring-pipeline staple: job boards and LinkedIn show many roles explicitly asking for Site Reliability Engineering, and major vendors like Google, AWS, and Datadog publish SRE guidance and tooling around it.
Skill profile (library / DB)
- Skill nature
- METHODOLOGY
- Volatility
- STABLE
- Typical lifespan
- EVERGREEN
- Category id
- 8
- Sub-category id
- 1223
- 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
- Concepts
- Sub-category
- general
- Skill nature
- CONCEPT
- Volatility
- MEDIUM
- Typical lifespan
- MULTI_YEAR
- Version strategy
- UNVERSIONED
All API 3 persistence rows
Same grid as the skill-extractor “Persistence items” table: one row per (skill × dimension) work item.
| Skill | Tag | Dimension | Skill↔dim | Role↔dim | Outcome | Notes |
|---|---|---|---|---|---|---|
| CI/CD | in_db |
CI/CD Pipeline Platforms
ci-cd-pipeline-platforms
|
✓ | ✓ | Existing dimension (library) · Role↔dimension saved | |
| CI/CD | in_db |
CI/CD for Machine Learning
ci-cd-for-machine-learning
|
✓ | — | Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role) | |
| Unit Testing | in_db |
React Frontend Development
d_init_01
|
✓ | — | Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role) | |
| Monitoring | in_db |
Observability and Incident Triage
observability-and-incident-triage
|
✓ | ✓ | Existing dimension (library) · Role↔dimension saved | |
| Alerting | in_db |
Backend Observability, Logging, and Diagnostics
backend-observability-logging-and-diagnostics
|
✓ | — | Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role) | |
| Alerting | in_db |
Observability and Incident Response
observability-and-incident-response
|
✓ | — | Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role) | |
| Alerting | in_db |
Observability and Incident Triage
observability-and-incident-triage
|
✓ | ✓ | Existing dimension (library) · Role↔dimension saved | |
| Code Review | in_db |
React Frontend Development
d_init_01
|
✓ | — | Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role) | |
| Site Reliability Engineering | 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 | Infrastructure as Code | type=Practice subtype=general nature=PRACTICE lifespan=MULTI_YEAR | |
| canonical_skill_proposed | Containerization | type=Concepts subtype=general nature=CONCEPT lifespan=MULTI_YEAR | |
| canonical_skill_proposed | Documentation | type=Soft Skills subtype=general nature=PRACTICE lifespan=EVERGREEN | |
| 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": {
"source_marker": {
"first_5_words": "GlobalLogic is a leader in",
"last_5_words": "through data and technology as"
},
"text": "GlobalLogic is a leader in digital engineering. We help brands across the globe design and build innovative products, platforms, and digital experiences for the modern world. By integrating experience design, complex engineering, and data expertise\u2014we help our clients imagine what\u2019s possible, and accelerate their transition into tomorrow\u2019s digital businesses. Headquartered in Silicon Valley, GlobalLogic operates design studios and engineering centers around the world, extending our deep expertise to customers in the automotive, communications, financial services, healthcare and life sciences, manufacturing, media and entertainment, semiconductor, and technology industries. GlobalLogic is a Hitachi Group Company operating under Hitachi, Ltd. (TSE: 6501) which contributes to a sustainable society with a higher quality of life by driving innovation through data and technology as the Social Innovation Business.",
"word_count": 116
},
"certifications": [],
"company_name": "GlobalLogic",
"ctc": null,
"domain": {
"primary": {
"aliases": [
"ITES",
"BPO",
"Tech Consulting"
],
"domain": "IT Services \u0026 Consulting"
},
"secondary": null
},
"education": [
{
"level": "Bachelor\u0027s",
"qualification": "BTECH/BE - Computer Science",
"raw": "BS degree in computer science",
"requirement": "required"
}
],
"experience": {
"max": null,
"min": 5,
"raw": "typically 5+ years"
},
"job_locations": [],
"role": "Data Engineer",
"role_aliases": [
"Data Engineer",
"Data Developer",
"Data Infrastructure Engineer"
],
"role_archetype": "Data",
"roles_and_responsibilities": [
{
"bullet_count": 6,
"heading": "Job Responsibilities",
"heading_was_present": true,
"source_marker": {
"first_5_words": "\u2022 Architects, designs, implements and",
"last_5_words": "improve developer velocity."
},
"text": "\u2022 Architects, designs, implements and maintains reliable and scalable data infrastructure.\n\u2022 Writes, deploys and maintains software to build, integrate, manage, maintain, and quality assure data at bp.\n\u2022 Adheres to and advocates for software engineering best practices (e.g. technical design, technical design review, unit testing, monitoring \u0026 alerting, checking in code, code review, documentation),\n\u2022 Responsible for deploying secure and well-tested software that meets privacy and compliance requirements; develops, maintains and improves CI / CD pipeline,\n\u2022 Responsible for service reliability and following site-reliability engineering best practices: on-call rotations for services they maintain, responsible for defining and maintaining SLAs. Design, build, deploy and maintain infrastructure as code. Containerizes server deployments.\n\u2022 Actively contributes to improve developer velocity.",
"word_count": 134
}
],
"urls": []
}
API 1 — extract-from-jd click to toggle
{
"final_skills": [
{
"is_primary": true,
"skill_name": "CI/CD"
},
{
"is_primary": true,
"skill_name": "Infrastructure as Code"
},
{
"is_primary": true,
"skill_name": "Containerization"
},
{
"is_primary": true,
"skill_name": "Unit Testing"
},
{
"is_primary": true,
"skill_name": "Monitoring"
},
{
"is_primary": true,
"skill_name": "Alerting"
},
{
"is_primary": true,
"skill_name": "Code Review"
},
{
"is_primary": true,
"skill_name": "Documentation"
},
{
"is_primary": true,
"skill_name": "Site Reliability Engineering"
},
{
"is_primary": true,
"skill_name": "SLA"
}
],
"jd_role": {
"display_name": "Data Engineer",
"rationale": null,
"role_aliases": [
"Data Engineer",
"Data Developer",
"Data Infrastructure Engineer"
],
"role_archetype": "Data",
"slug": ""
},
"nano_parsed": {
"JD_type": "pass",
"about_company": {
"source_marker": {
"first_5_words": "GlobalLogic is a leader in",
"last_5_words": "through data and technology as"
},
"text": "GlobalLogic is a leader in digital engineering. We help brands across the globe design and build innovative products, platforms, and digital experiences for the modern world. By integrating experience design, complex engineering, and data expertise\u2014we help our clients imagine what\u2019s possible, and accelerate their transition into tomorrow\u2019s digital businesses. Headquartered in Silicon Valley, GlobalLogic operates design studios and engineering centers around the world, extending our deep expertise to customers in the automotive, communications, financial services, healthcare and life sciences, manufacturing, media and entertainment, semiconductor, and technology industries. GlobalLogic is a Hitachi Group Company operating under Hitachi, Ltd. (TSE: 6501) which contributes to a sustainable society with a higher quality of life by driving innovation through data and technology as the Social Innovation Business.",
"word_count": 116
},
"certifications": [],
"company_name": "GlobalLogic",
"ctc": null,
"domain": {
"primary": {
"aliases": [
"ITES",
"BPO",
"Tech Consulting"
],
"domain": "IT Services \u0026 Consulting"
},
"secondary": null
},
"education": [
{
"level": "Bachelor\u0027s",
"qualification": "BTECH/BE - Computer Science",
"raw": "BS degree in computer science",
"requirement": "required"
}
],
"experience": {
"max": null,
"min": 5,
"raw": "typically 5+ years"
},
"job_locations": [],
"role": "Data Engineer",
"role_aliases": [
"Data Engineer",
"Data Developer",
"Data Infrastructure Engineer"
],
"role_archetype": "Data",
"roles_and_responsibilities": [
{
"bullet_count": 6,
"heading": "Job Responsibilities",
"heading_was_present": true,
"source_marker": {
"first_5_words": "\u2022 Architects, designs, implements and",
"last_5_words": "improve developer velocity."
},
"text": "\u2022 Architects, designs, implements and maintains reliable and scalable data infrastructure.\n\u2022 Writes, deploys and maintains software to build, integrate, manage, maintain, and quality assure data at bp.\n\u2022 Adheres to and advocates for software engineering best practices (e.g. technical design, technical design review, unit testing, monitoring \u0026 alerting, checking in code, code review, documentation),\n\u2022 Responsible for deploying secure and well-tested software that meets privacy and compliance requirements; develops, maintains and improves CI / CD pipeline,\n\u2022 Responsible for service reliability and following site-reliability engineering best practices: on-call rotations for services they maintain, responsible for defining and maintaining SLAs. Design, build, deploy and maintain infrastructure as code. Containerizes server deployments.\n\u2022 Actively contributes to improve developer velocity.",
"word_count": 134
}
],
"urls": []
},
"rejected": false,
"rejection_reason": null,
"run_id": "db06e85d-5e2c-4647-9ef2-1cdac6390266",
"stage3_signals": {
"alias_found": true,
"alias_match_roles": [
{
"display_name": "Data Engineer",
"kra_matches": null,
"matched_count": null,
"matched_skills": null,
"role_id": 2,
"score": 1.0,
"slug": "data-engineer",
"total_count": null
}
],
"kra_match_roles": [
{
"display_name": "DevOps Engineer",
"kra_matches": [
{
"kra_text": "Builds and maintains CI/CD pipelines using Jenkins, GitHub Actions, GitLab CI, or CircleCI to automate build, test, security scanning, and deployment workflows.",
"sentence": "Responsible for deploying secure and well-tested software that meets privacy and compliance requirements; develops, maintains and improves CI / CD pipeline,",
"similarity": 0.6488
},
{
"kra_text": "Provisions and manages cloud infrastructure on AWS, Azure, or GCP using Terraform or CloudFormation to enforce infrastructure-as-code standards.",
"sentence": "Design, build, deploy and maintain infrastructure as code.",
"similarity": 0.6158
},
{
"kra_text": "Collaborates with development teams to improve build processes, reduce deployment friction, containerize applications, and adopt DevOps best practices.",
"sentence": "Actively contributes to improve developer velocity.",
"similarity": 0.566
}
],
"matched_count": null,
"matched_skills": null,
"role_id": 10,
"score": 0.6102,
"slug": "devops-engineer",
"total_count": null
},
{
"display_name": "Fullstack Developer",
"kra_matches": [
{
"kra_text": "Delivers features through CI/CD pipelines using automated tests, staged rollouts, feature flags, and incremental deployments.",
"sentence": "Responsible for deploying secure and well-tested software that meets privacy and compliance requirements; develops, maintains and improves CI / CD pipeline,",
"similarity": 0.6066
},
{
"kra_text": "Designs and queries relational databases like PostgreSQL and document stores like MongoDB, writing migrations, indexes, and optimized queries.",
"sentence": "Architects, designs, implements and maintains reliable and scalable data infrastructure.",
"similarity": 0.5691
},
{
"kra_text": "Delivers features through CI/CD pipelines using automated tests, staged rollouts, feature flags, and incremental deployments.",
"sentence": "Design, build, deploy and maintain infrastructure as code.",
"similarity": 0.5298
}
],
"matched_count": null,
"matched_skills": null,
"role_id": 15,
"score": 0.5685,
"slug": "full-stack-engineer",
"total_count": null
},
{
"display_name": "Cloud Architect",
"kra_matches": [
{
"kra_text": "Designs multi-region and multi-availability-zone cloud infrastructure architectures for high availability, fault tolerance, and horizontal scalability.",
"sentence": "Architects, designs, implements and maintains reliable and scalable data infrastructure.",
"similarity": 0.591
},
{
"kra_text": "Conducts architecture reviews, approves technical design documents, and guides engineering teams through cloud migration and modernization projects.",
"sentence": "Adheres to and advocates for software engineering best practices (e.g. technical design, technical design review, unit testing, monitoring \u0026 alerting, checking in code, code review, documentation),",
"similarity": 0.5579
},
{
"kra_text": "Architects blue-green, canary, and immutable infrastructure deployment patterns for zero-downtime releases and fast rollback capabilities.",
"sentence": "Design, build, deploy and maintain infrastructure as code.",
"similarity": 0.5083
}
],
"matched_count": null,
"matched_skills": null,
"role_id": 9,
"score": 0.5524,
"slug": "cloud-architect",
"total_count": null
},
{
"display_name": "Cloud Security Engineer",
"kra_matches": [
{
"kra_text": "Reviews cloud infrastructure-as-code configurations for security misconfigurations and implements CIS Benchmark hardening baselines using CSPM tools.",
"sentence": "Responsible for deploying secure and well-tested software that meets privacy and compliance requirements; develops, maintains and improves CI / CD pipeline,",
"similarity": 0.5558
},
{
"kra_text": "Documents cloud security standards, approved architecture patterns, security exceptions, and remediation guidance for engineering teams.",
"sentence": "Adheres to and advocates for software engineering best practices (e.g. technical design, technical design review, unit testing, monitoring \u0026 alerting, checking in code, code review, documentation),",
"similarity": 0.5365
},
{
"kra_text": "Designs and implements cloud security controls including KMS encryption, secrets management, and data-at-rest protection for AWS, Azure, or GCP workloads.",
"sentence": "Architects, designs, implements and maintains reliable and scalable data infrastructure.",
"similarity": 0.4823
}
],
"matched_count": null,
"matched_skills": null,
"role_id": 23,
"score": 0.5248,
"slug": "cloud-security-engineer",
"total_count": null
},
{
"display_name": "Data Engineer",
"kra_matches": [
{
"kra_text": "Designs dimensional models, star schemas, data vault structures, and curated data mart tables to support BI tools and self-service analytics consumption.",
"sentence": "Architects, designs, implements and maintains reliable and scalable data infrastructure.",
"similarity": 0.5898
},
{
"kra_text": "Monitors pipeline health, SLA breach alerts, and job failure notifications, and performs root cause analysis for data pipeline incidents.",
"sentence": "Responsible for deploying secure and well-tested software that meets privacy and compliance requirements; develops, maintains and improves CI / CD pipeline,",
"similarity": 0.4969
},
{
"kra_text": "Monitors pipeline health, SLA breach alerts, and job failure notifications, and performs root cause analysis for data pipeline incidents.",
"sentence": "Responsible for service reliability and following site-reliability engineering best practices: on-call rotations for services they maintain, responsible for defining and maintaining SLAs.",
"similarity": 0.4731
}
],
"matched_count": null,
"matched_skills": null,
"role_id": 2,
"score": 0.5199,
"slug": "data-engineer",
"total_count": null
}
],
"skill_match_roles": [
{
"display_name": "DevOps Engineer",
"kra_matches": null,
"matched_count": 3,
"matched_skills": [
"CI/CD",
"Monitoring",
"alerting"
],
"role_id": 10,
"score": 0.3,
"slug": "devops-engineer",
"total_count": 10
},
{
"display_name": "ML Engineer",
"kra_matches": null,
"matched_count": 1,
"matched_skills": [
"CI/CD"
],
"role_id": 3,
"score": 0.1,
"slug": "ml-engineer",
"total_count": 10
},
{
"display_name": "Node.js Backend Developer",
"kra_matches": null,
"matched_count": 1,
"matched_skills": [
"alerting"
],
"role_id": 82,
"score": 0.1,
"slug": "node-backend-developer",
"total_count": 10
},
{
"display_name": ".NET Backend Developer",
"kra_matches": null,
"matched_count": 1,
"matched_skills": [
"alerting"
],
"role_id": 83,
"score": 0.1,
"slug": "dotnet-backend-developer",
"total_count": 10
},
{
"display_name": "Kotlin Backend Developer",
"kra_matches": null,
"matched_count": 1,
"matched_skills": [
"alerting"
],
"role_id": 84,
"score": 0.1,
"slug": "kotlin-server-backend-developer",
"total_count": 10
}
]
},
"stage4_decision": {
"alias_collision_detected": false,
"case": "DOMAIN",
"chosen_role": {
"display_name": "DevOps Engineer",
"kra_matches": null,
"matched_count": null,
"matched_skills": null,
"role_id": 10,
"score": 0.96,
"slug": "devops-engineer",
"total_count": null
},
"confidence": 0.96,
"is_new_role": false,
"llm2_fired": false,
"llm2_reasoning": null,
"matched_dimensions": [
"Data Infrastructure Engineering",
"CI/CD and Release Automation",
"Infrastructure as Code",
"Site Reliability and Service Operations",
"Secure Software Delivery",
"Developer Productivity Improvement"
],
"matched_kras": [
"Architects, designs, implements and maintains reliable and scalable data infrastructure",
"Writes, deploys and maintains software to build, integrate, manage, maintain, and quality assure data",
"Adheres to and advocates for software engineering best practices",
"Develops, maintains and improves CI / CD pipeline",
"Design, build, deploy and maintain infrastructure as code",
"Containerizes server deployments",
"Responsible for service reliability and following site-reliability engineering best practices",
"Defining and maintaining SLAs",
"Actively contributes to improve developer velocity"
],
"matched_skills": [
"CI / CD pipeline",
"site-reliability engineering",
"infrastructure as code",
"Containerizes server deployments",
"unit testing",
"monitoring \u0026 alerting",
"code review",
"documentation",
"privacy and compliance requirements",
"SLAs"
],
"new_role_display_name": null,
"new_role_slug": null,
"queued": false,
"reasoning": "Domain=DevOps \u0026 Platform \u2192 sub-role ci-cd-engineer; The JD emphasizes CI/CD, infrastructure as code, containerized deployments, secure software delivery, and site reliability practices, which best matches DevOps Engineering.",
"sub_role": {
"confidence": 0.93,
"display_name": "CI/CD Engineer",
"reasoning": "The JD explicitly emphasizes maintaining and improving CI/CD pipelines, along with DevOps-style delivery and reliability work, which most strongly matches CI/CD Engineer.",
"role_id": 369,
"slug": "ci-cd-engineer"
}
},
"stage5_updates": {
"centroid_n_after": 58,
"centroid_updated": true,
"collision_log_id": null,
"new_kra_attached": null,
"new_skills_attached": [
{
"is_primary": true,
"queue_id": 8353,
"role_display_name": "DevOps Engineer",
"role_slug": "devops-engineer",
"skill_name": "Infrastructure as Code",
"status": "pending"
},
{
"is_primary": true,
"queue_id": 8354,
"role_display_name": "DevOps Engineer",
"role_slug": "devops-engineer",
"skill_name": "Containerization",
"status": "pending"
},
{
"is_primary": true,
"queue_id": 8355,
"role_display_name": "DevOps Engineer",
"role_slug": "devops-engineer",
"skill_name": "Documentation",
"status": "pending"
},
{
"is_primary": true,
"queue_id": 8356,
"role_display_name": "DevOps Engineer",
"role_slug": "devops-engineer",
"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": 1826,
"existing_alias_text": "CI/CD",
"input_term": "CI/CD",
"matched_canonical": {
"category_id": 8,
"display_name": "CI/CD",
"id": 1190,
"is_also_category": false,
"is_extractable": true,
"skill_nature": "METHODOLOGY",
"slug": "ci-cd",
"sub_category_id": 900,
"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": 865,
"existing_alias_text": "Unit Testing",
"input_term": "Unit Testing",
"matched_canonical": {
"category_id": 8,
"display_name": "Unit Testing",
"id": 517,
"is_also_category": false,
"is_extractable": true,
"skill_nature": "METHODOLOGY",
"slug": "unit-testing",
"sub_category_id": 44,
"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": 1854,
"existing_alias_text": "Monitoring",
"input_term": "Monitoring",
"matched_canonical": {
"category_id": 2,
"display_name": "Monitoring",
"id": 1218,
"is_also_category": false,
"is_extractable": true,
"skill_nature": "CONCEPT",
"slug": "monitoring",
"sub_category_id": 924,
"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": 1444,
"existing_alias_text": "alerting",
"input_term": "Alerting",
"matched_canonical": {
"category_id": 2,
"display_name": "alerting",
"id": 882,
"is_also_category": false,
"is_extractable": true,
"skill_nature": "CONCEPT",
"slug": "alerting",
"sub_category_id": 3472,
"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": 864,
"existing_alias_text": "Code Review",
"input_term": "Code Review",
"matched_canonical": {
"category_id": 58,
"display_name": "Code Review",
"id": 516,
"is_also_category": false,
"is_extractable": true,
"skill_nature": "PRACTICE",
"slug": "code-review",
"sub_category_id": 364,
"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": 2578,
"existing_alias_text": "Site Reliability Engineering",
"input_term": "Site Reliability Engineering",
"matched_canonical": {
"category_id": 8,
"display_name": "Site Reliability Engineering",
"id": 1623,
"is_also_category": false,
"is_extractable": true,
"skill_nature": "METHODOLOGY",
"slug": "site-reliability-engineering",
"sub_category_id": 1223,
"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": "ML Engineer",
"id": 3,
"rationale": null,
"role_archetype": null,
"slug": "ml-engineer",
"source": "db"
},
{
"display_name": "Kotlin Backend Developer",
"id": 84,
"rationale": null,
"role_archetype": "Engineering",
"slug": "kotlin-server-backend-developer",
"source": "db"
},
{
"display_name": "Scala Backend Developer",
"id": 87,
"rationale": null,
"role_archetype": "Engineering",
"slug": "scala-backend-developer",
"source": "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"
}
],
"chosen_role": {
"display_name": "DevOps Engineer",
"id": 10,
"rationale": "Domain=DevOps \u0026 Platform \u2192 sub-role ci-cd-engineer; The JD emphasizes CI/CD, infrastructure as code, containerized deployments, secure software delivery, and site reliability practices, which best matches DevOps Engineering.",
"role_archetype": null,
"slug": "devops-engineer",
"source": "db"
},
"dimensions": [
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "CI/CD Pipeline Platforms",
"id": 150,
"rationale": "Systems used to define, run, and maintain automated build and deployment workflows. This cluster is coherent because the role owns delivery automation end to end, including pipeline reliability and promotion logic.",
"slug": "ci-cd-pipeline-platforms",
"source": "db"
},
"input_skill": "CI/CD",
"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": "CI/CD for Machine Learning",
"id": 56,
"rationale": "Tools and platforms for automating ML model integration, testing, and deployment pipelines.",
"slug": "ci-cd-for-machine-learning",
"source": "db"
},
"input_skill": "CI/CD",
"llm_role": null,
"roles_from_db": [
{
"display_name": "ML Engineer",
"id": 3,
"rationale": null,
"role_archetype": null,
"slug": "ml-engineer",
"source": "db"
}
]
},
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "React Frontend Development",
"id": 96,
"rationale": "Building interactive web user interfaces with React.js, including component composition, state management, hooks, and rendering patterns. React.js belongs here because it is a core library for client-side UI development in modern web applications.",
"slug": "d_init_01",
"source": "db"
},
"input_skill": "Unit Testing",
"llm_role": null,
"roles_from_db": []
},
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Observability and Incident Triage",
"id": 155,
"rationale": "Telemetry, alerting, and troubleshooting practices used to diagnose failed builds, broken deployments, and unhealthy release environments. This is a coherent cluster because delivery reliability depends on quickly identifying where the workflow failed.",
"slug": "observability-and-incident-triage",
"source": "db"
},
"input_skill": "Monitoring",
"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": "Backend Observability, Logging, and Diagnostics",
"id": 388,
"rationale": "Instrumentation and troubleshooting practices used to understand and improve backend service behavior in production and lower environments. This includes logs, metrics, traces, alerting, dashboards, structured logging, distributed tracing, health checks, and root-cause analysis using ecosystem-specific tools such as SLF4J, Logback, Micrometer, OpenTelemetry, Prometheus, Grafana, ILogger, Serilog, and Application Insights.",
"slug": "backend-observability-logging-and-diagnostics",
"source": "db"
},
"input_skill": "Alerting",
"llm_role": null,
"roles_from_db": [
{
"display_name": "Kotlin Backend Developer",
"id": 84,
"rationale": null,
"role_archetype": "Engineering",
"slug": "kotlin-server-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": "Observability and Incident Response",
"id": 10,
"rationale": "Instrumentation and production troubleshooting practices used to keep backend services reliable. Includes logs, metrics, traces, alerting, dashboards, and incident diagnosis.",
"slug": "observability-and-incident-response",
"source": "db"
},
"input_skill": "Alerting",
"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"
}
]
},
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Observability and Incident Triage",
"id": 155,
"rationale": "Telemetry, alerting, and troubleshooting practices used to diagnose failed builds, broken deployments, and unhealthy release environments. This is a coherent cluster because delivery reliability depends on quickly identifying where the workflow failed.",
"slug": "observability-and-incident-triage",
"source": "db"
},
"input_skill": "Alerting",
"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": "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": "Code Review",
"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": "Site Reliability Engineering",
"llm_role": null,
"roles_from_db": []
}
],
"input_final_skills": [
"CI/CD",
"Infrastructure as Code",
"Containerization",
"Unit Testing",
"Monitoring",
"Alerting",
"Code Review",
"Documentation",
"Site Reliability Engineering",
"SLA"
],
"input_llm_skills": [
"CI/CD",
"Infrastructure as Code",
"Containerization",
"Unit Testing",
"Monitoring",
"Alerting",
"Code Review",
"Documentation",
"Site Reliability Engineering",
"SLA"
],
"new_aliases_persisted": 0,
"run_id": "db06e85d-5e2c-4647-9ef2-1cdac6390266",
"skills_detail": [
{
"aliases_in_db": [
{
"alias_text": "CI/CD",
"alias_type": "CANONICAL",
"id": 1826,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
}
],
"canonical": {
"category_id": 8,
"display_name": "CI/CD",
"id": 1190,
"is_also_category": false,
"is_extractable": true,
"skill_nature": "METHODOLOGY",
"slug": "ci-cd",
"sub_category_id": 900,
"typical_lifespan": "EVERGREEN",
"volatility": "STABLE"
},
"dimensions": [
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "CI/CD Pipeline Platforms",
"id": 150,
"rationale": "Systems used to define, run, and maintain automated build and deployment workflows. This cluster is coherent because the role owns delivery automation end to end, including pipeline reliability and promotion logic.",
"slug": "ci-cd-pipeline-platforms",
"source": "db"
},
"input_skill": "CI/CD",
"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": "CI/CD for Machine Learning",
"id": 56,
"rationale": "Tools and platforms for automating ML model integration, testing, and deployment pipelines.",
"slug": "ci-cd-for-machine-learning",
"source": "db"
},
"input_skill": "CI/CD",
"llm_role": null,
"roles_from_db": [
{
"display_name": "ML Engineer",
"id": 3,
"rationale": null,
"role_archetype": null,
"slug": "ml-engineer",
"source": "db"
}
]
}
],
"input_skill": "CI/CD",
"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": "Infrastructure as Code",
"matched_via": null,
"new_alias_persisted": false,
"new_alias_text": null,
"new_skill_meta": {
"derived": {
"category": "Practice",
"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": "infrastructure-as-code",
"split_log": [],
"typed": null,
"warnings": []
},
"source_tag": "llm",
"was_in_llm_skills": true
},
{
"aliases_in_db": [],
"canonical": null,
"dimensions": [],
"input_skill": "Containerization",
"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": "containerization",
"split_log": [],
"typed": null,
"warnings": []
},
"source_tag": "llm",
"was_in_llm_skills": true
},
{
"aliases_in_db": [
{
"alias_text": "Unit Testing",
"alias_type": "CANONICAL",
"id": 865,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
}
],
"canonical": {
"category_id": 8,
"display_name": "Unit Testing",
"id": 517,
"is_also_category": false,
"is_extractable": true,
"skill_nature": "METHODOLOGY",
"slug": "unit-testing",
"sub_category_id": 44,
"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": "Unit Testing",
"llm_role": null,
"roles_from_db": []
}
],
"input_skill": "Unit Testing",
"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": "Monitoring",
"alias_type": "CANONICAL",
"id": 1854,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
}
],
"canonical": {
"category_id": 2,
"display_name": "Monitoring",
"id": 1218,
"is_also_category": false,
"is_extractable": true,
"skill_nature": "CONCEPT",
"slug": "monitoring",
"sub_category_id": 924,
"typical_lifespan": "EVERGREEN",
"volatility": "STABLE"
},
"dimensions": [
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Observability and Incident Triage",
"id": 155,
"rationale": "Telemetry, alerting, and troubleshooting practices used to diagnose failed builds, broken deployments, and unhealthy release environments. This is a coherent cluster because delivery reliability depends on quickly identifying where the workflow failed.",
"slug": "observability-and-incident-triage",
"source": "db"
},
"input_skill": "Monitoring",
"llm_role": null,
"roles_from_db": [
{
"display_name": "DevOps Engineer",
"id": 10,
"rationale": null,
"role_archetype": null,
"slug": "devops-engineer",
"source": "db"
}
]
}
],
"input_skill": "Monitoring",
"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": "alerting",
"alias_type": "CANONICAL",
"id": 1444,
"is_primary": true,
"match_strategy": "CASE_INSENSITIVE"
}
],
"canonical": {
"category_id": 2,
"display_name": "alerting",
"id": 882,
"is_also_category": false,
"is_extractable": true,
"skill_nature": "CONCEPT",
"slug": "alerting",
"sub_category_id": 3472,
"typical_lifespan": "EVERGREEN",
"volatility": "STABLE"
},
"dimensions": [
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Backend Observability, Logging, and Diagnostics",
"id": 388,
"rationale": "Instrumentation and troubleshooting practices used to understand and improve backend service behavior in production and lower environments. This includes logs, metrics, traces, alerting, dashboards, structured logging, distributed tracing, health checks, and root-cause analysis using ecosystem-specific tools such as SLF4J, Logback, Micrometer, OpenTelemetry, Prometheus, Grafana, ILogger, Serilog, and Application Insights.",
"slug": "backend-observability-logging-and-diagnostics",
"source": "db"
},
"input_skill": "Alerting",
"llm_role": null,
"roles_from_db": [
{
"display_name": "Kotlin Backend Developer",
"id": 84,
"rationale": null,
"role_archetype": "Engineering",
"slug": "kotlin-server-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": "Observability and Incident Response",
"id": 10,
"rationale": "Instrumentation and production troubleshooting practices used to keep backend services reliable. Includes logs, metrics, traces, alerting, dashboards, and incident diagnosis.",
"slug": "observability-and-incident-response",
"source": "db"
},
"input_skill": "Alerting",
"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"
}
]
},
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Observability and Incident Triage",
"id": 155,
"rationale": "Telemetry, alerting, and troubleshooting practices used to diagnose failed builds, broken deployments, and unhealthy release environments. This is a coherent cluster because delivery reliability depends on quickly identifying where the workflow failed.",
"slug": "observability-and-incident-triage",
"source": "db"
},
"input_skill": "Alerting",
"llm_role": null,
"roles_from_db": [
{
"display_name": "DevOps Engineer",
"id": 10,
"rationale": null,
"role_archetype": null,
"slug": "devops-engineer",
"source": "db"
}
]
}
],
"input_skill": "Alerting",
"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": "Code Review",
"alias_type": "CANONICAL",
"id": 864,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
}
],
"canonical": {
"category_id": 58,
"display_name": "Code Review",
"id": 516,
"is_also_category": false,
"is_extractable": true,
"skill_nature": "PRACTICE",
"slug": "code-review",
"sub_category_id": 364,
"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": "Code Review",
"llm_role": null,
"roles_from_db": []
}
],
"input_skill": "Code Review",
"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": "Documentation",
"matched_via": null,
"new_alias_persisted": false,
"new_alias_text": null,
"new_skill_meta": {
"derived": {
"category": "Soft Skills",
"skill_nature": "PRACTICE",
"sub_category": "general",
"typical_lifespan": "EVERGREEN",
"version_strategy": "UNVERSIONED",
"volatility": "STABLE"
},
"enrichment": null,
"keep_log": [],
"locked_dimensions": [],
"merge_log": [],
"placed": null,
"relationships": null,
"skill_id": "documentation",
"split_log": [],
"typed": null,
"warnings": []
},
"source_tag": "llm",
"was_in_llm_skills": true
},
{
"aliases_in_db": [
{
"alias_text": "Site Reliability Engineering",
"alias_type": "CANONICAL",
"id": 2578,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
}
],
"canonical": {
"category_id": 8,
"display_name": "Site Reliability Engineering",
"id": 1623,
"is_also_category": false,
"is_extractable": true,
"skill_nature": "METHODOLOGY",
"slug": "site-reliability-engineering",
"sub_category_id": 1223,
"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": "Site Reliability Engineering",
"llm_role": null,
"roles_from_db": []
}
],
"input_skill": "Site Reliability Engineering",
"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": "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
}
],
"unmatched_skills": [
"Infrastructure as Code",
"Containerization",
"Documentation",
"SLA"
]
}
API 3 — final-role-output
{
"chosen_role": {
"display_name": "DevOps Engineer",
"id": 10,
"rationale": "Domain=DevOps \u0026 Platform \u2192 sub-role ci-cd-engineer; The JD emphasizes CI/CD, infrastructure as code, containerized deployments, secure software delivery, and site reliability practices, which best matches DevOps Engineering.",
"role_archetype": null,
"slug": "devops-engineer",
"source": "db"
},
"chosen_role_resolution": "in_db",
"final_input_skills": [
{
"skill": "CI/CD",
"tag": "in_db"
},
{
"skill": "Infrastructure as Code",
"tag": "new"
},
{
"skill": "Containerization",
"tag": "new"
},
{
"skill": "Unit Testing",
"tag": "in_db"
},
{
"skill": "Monitoring",
"tag": "in_db"
},
{
"skill": "Alerting",
"tag": "in_db"
},
{
"skill": "Code Review",
"tag": "in_db"
},
{
"skill": "Documentation",
"tag": "new"
},
{
"skill": "Site Reliability Engineering",
"tag": "in_db"
},
{
"skill": "SLA",
"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": 10,
"dimension": {
"difficulty_hint": "well_known",
"display_name": "CI/CD Pipeline Platforms",
"id": 150,
"rationale": "Systems used to define, run, and maintain automated build and deployment workflows. This cluster is coherent because the role owns delivery automation end to end, including pipeline reliability and promotion logic.",
"slug": "ci-cd-pipeline-platforms",
"source": "db"
},
"dimension_id": 150,
"input_skill": "CI/CD",
"llm_role": null,
"matched_chosen_role": true,
"outcome_line": "Existing dimension (library) \u00b7 Role\u2194dimension saved",
"role_dimension_saved": true,
"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": 1190,
"skill_tag": "in_db",
"skipped_reason": null
},
{
"chosen_role_id": 10,
"dimension": {
"difficulty_hint": "well_known",
"display_name": "CI/CD for Machine Learning",
"id": 56,
"rationale": "Tools and platforms for automating ML model integration, testing, and deployment pipelines.",
"slug": "ci-cd-for-machine-learning",
"source": "db"
},
"dimension_id": 56,
"input_skill": "CI/CD",
"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": "ML Engineer",
"id": 3,
"rationale": null,
"role_archetype": null,
"slug": "ml-engineer",
"source": "db"
}
],
"skill_dimension_saved": true,
"skill_id": 1190,
"skill_tag": "in_db",
"skipped_reason": null
},
{
"chosen_role_id": 10,
"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": "Unit Testing",
"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": 517,
"skill_tag": "in_db",
"skipped_reason": null
},
{
"chosen_role_id": 10,
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Observability and Incident Triage",
"id": 155,
"rationale": "Telemetry, alerting, and troubleshooting practices used to diagnose failed builds, broken deployments, and unhealthy release environments. This is a coherent cluster because delivery reliability depends on quickly identifying where the workflow failed.",
"slug": "observability-and-incident-triage",
"source": "db"
},
"dimension_id": 155,
"input_skill": "Monitoring",
"llm_role": null,
"matched_chosen_role": true,
"outcome_line": "Existing dimension (library) \u00b7 Role\u2194dimension saved",
"role_dimension_saved": true,
"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": 1218,
"skill_tag": "in_db",
"skipped_reason": null
},
{
"chosen_role_id": 10,
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Backend Observability, Logging, and Diagnostics",
"id": 388,
"rationale": "Instrumentation and troubleshooting practices used to understand and improve backend service behavior in production and lower environments. This includes logs, metrics, traces, alerting, dashboards, structured logging, distributed tracing, health checks, and root-cause analysis using ecosystem-specific tools such as SLF4J, Logback, Micrometer, OpenTelemetry, Prometheus, Grafana, ILogger, Serilog, and Application Insights.",
"slug": "backend-observability-logging-and-diagnostics",
"source": "db"
},
"dimension_id": 388,
"input_skill": "Alerting",
"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": "Kotlin Backend Developer",
"id": 84,
"rationale": null,
"role_archetype": "Engineering",
"slug": "kotlin-server-backend-developer",
"source": "db"
},
{
"display_name": "Scala Backend Developer",
"id": 87,
"rationale": null,
"role_archetype": "Engineering",
"slug": "scala-backend-developer",
"source": "db"
}
],
"skill_dimension_saved": true,
"skill_id": 882,
"skill_tag": "in_db",
"skipped_reason": null
},
{
"chosen_role_id": 10,
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Observability and Incident Response",
"id": 10,
"rationale": "Instrumentation and production troubleshooting practices used to keep backend services reliable. Includes logs, metrics, traces, alerting, dashboards, and incident diagnosis.",
"slug": "observability-and-incident-response",
"source": "db"
},
"dimension_id": 10,
"input_skill": "Alerting",
"llm_role": null,
"matched_chosen_role": false,
"outcome_line": "Existing dimension (library) \u00b7 Role\u2194dimension skipped (dimension not under chosen role)",
"role_dimension_saved": false,
"roles_from_db": [
{
"display_name": ".NET Backend Developer",
"id": 83,
"rationale": null,
"role_archetype": "Engineering",
"slug": "dotnet-backend-developer",
"source": "db"
},
{
"display_name": "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"
}
],
"skill_dimension_saved": true,
"skill_id": 882,
"skill_tag": "in_db",
"skipped_reason": null
},
{
"chosen_role_id": 10,
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Observability and Incident Triage",
"id": 155,
"rationale": "Telemetry, alerting, and troubleshooting practices used to diagnose failed builds, broken deployments, and unhealthy release environments. This is a coherent cluster because delivery reliability depends on quickly identifying where the workflow failed.",
"slug": "observability-and-incident-triage",
"source": "db"
},
"dimension_id": 155,
"input_skill": "Alerting",
"llm_role": null,
"matched_chosen_role": true,
"outcome_line": "Existing dimension (library) \u00b7 Role\u2194dimension saved",
"role_dimension_saved": true,
"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": 882,
"skill_tag": "in_db",
"skipped_reason": null
},
{
"chosen_role_id": 10,
"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": "Code Review",
"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": 516,
"skill_tag": "in_db",
"skipped_reason": null
},
{
"chosen_role_id": 10,
"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": "Site Reliability Engineering",
"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": 1623,
"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": "db06e85d-5e2c-4647-9ef2-1cdac6390266"
}
LLM Calls
Every model call made for this run, in pipeline order. Click a card to see the model's response.