Pipeline run
23c596d1-8698-43f6-a9e0-9e4258417dec
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
In this role, you’ll: • Write software to automate everything from manual run-book processes to complete system provisioning • Architect and improve our Infrastructure container orchestration platfor…
1 POST /skills/extract-from-jd
2 POST /skills/extract-details
3 POST /skills/final-role-output
Platform Engineer
→Infrastructure Platform Engineer
sub-role · 0.97 domain · DevOps & Platform CASE DOMAINslug: platform-engineer · id: 133 · source: db · sub-role slug: infrastructure-platform-engineer
Domain=DevOps & Platform → sub-role infrastructure-platform-engineer; The JD centers on internal service platform, developer experience, automation, and large-scale cloud infrastructure, which best matches Platform Engineer over narrower Kubernetes, IaC, or pure SRE roles.
Matched skills
Matched dimensions
Matched KRAs
Resolution:
in_db
— role exists in library; skill↔dim and role↔dim links saved when applicable.
Job description
Principal Software Engineer Experience: 12+ years Expected Notice Period: 2 to 4 Weeks Shift: (GMT+05:30) Asia/Kolkata (IST) Opportunity Type: Onsite - Bengaluru Placement Type: Direct Placement (*Note: This is a requirement for one of Uplers' clients) What do you need for this opportunity? Primary Skills: Terraform, AWS, Golang, Kafka, Kubernetes Assessment: Role based AI Screening covering Communication and Technical Skills Our Hiring Partner is Looking for: Principal Software Engineer who is passionate about their work, eager to learn and grow, and who is committed to delivering exceptional results. If you are a team player, with a positive attitude and a desire to make a difference, then we want to hear from you! Roles & Responsibilities In this role, you’ll: • Write software to automate everything from manual run-book processes to complete system provisioning • Architect and improve our Infrastructure container orchestration platform (Kubernetes). • Build the next version of Segment’s Service Platform to support teams in deploying hundreds of services across a multi-region cloud environment • Support teams working on large scale infrastructure processing millions of events per second and storing hundreds of TBs per month • Participate in agile ceremonies and on a 12/7 on call rotation. • Architect and solve complex infrastructure problems in public cloud (AWS) • As a key member of our engineering team, you will play a crucial role in ensuring the reliability, scalability, and security of our systems on cloud infrastructure. Qualifications Not all applicants will have skills that match a job description exactly. Twilio values diverse experiences in other industries, and we encourage everyone who meets the required qualifications to apply. While having “desired” qualifications make for a strong candidate, we encourage applicants with alternative experiences to also apply. If your career is just starting or hasn't followed a traditional path, don't let that stop you from considering Twilio. We are always looking for people who will bring something new to the table! This Role Requires: If your career is just starting or hasn't followed a traditional path, don't let that stop you from considering Twilio. We are always looking for people who will bring something new to the table! • Minimum of 12-15 years experience as a seasoned Software Engineer, Site Reliability Engineer, Platform Engineer, Infrastructure Engineer or another similar role • AWS Expertise: Leverage your in-depth knowledge of Amazon Web Services (AWS) to architect, optimize, and manage cloud infrastructure for our applications. • Kubernetes Mastery: Drive the adoption and optimization of Kubernetes (K8s) for containerized applications, ensuring scalability, efficiency, and reliability. • Infrastructure as Code (IaC): Strong Terraform experience to design, implement, and maintain infrastructure as code, enabling seamless and reproducible deployments. • Go Lang Automation: Develop and maintain automation scripts and tools using Go lang, streamlining operational tasks and enhancing system efficiency. • Security Focus: Collaborate with our security teams to implement and enhance security measures, ensuring the confidentiality, integrity, and availability of our systems. • Developer Experience: Champion developer experience initiatives, focusing on optimizing workflows, reducing friction, and enhancing the overall development process. • Kafka Expertise: Strong expertise in Kafka design, implement, and manage event streaming architectures • Strong experience in DevOps tools like ArgoCD, Buildkite • Mastery in observability stack like Grafana, Prometheus, Datadog, Loki Bonus: • Are well-versed in architecting distributed workloads in an multi tenant production environment • Have worked on kafka and observability stack like prometheus, Grafana and logging frameworks. • Certified Kubernetes Administrator OR CKA Location: • This role will be based remotely in our Bangalore office. • Approximately 10%travel is anticipated. Note: • We are hiring candidates exclusively from the below cities • Delhi, Maharashtra, Karnataka, Telangana, and Tamil Nadu. • Candidates from service based companies don't fit in our ideal candidate persona, candidates from product companies & start ups are preferred. What we offer There are many benefits to working at Twilio, including things like competitive pay, generous time-off, ample parental and wellness leave, healthcare, a retirement savings program, and much more. Offerings vary by location. Twilio thinks big. Do you? We like to solve problems, take initiative, pitch in when needed, and are always up for trying new things. That's why we seek out colleagues who embody our values — something we call Twilio Magic. Additionally, we empower employees to build positive change in their communities by supporting their volunteering and donation efforts. So, if you're ready to unleash your full potential, do your best work, and be the best version of yourself, apply now! How to apply for this opportunity? • Register or login on our portal & fill out the application • Clear the given AI Screening (30 min) and Click on ‘Apply’ to get shortlisted • Our team of talent matchmakers will matchmake you with the client • Crack a quick interview with our client • Land your global dream job and get your exciting career started! About our Hiring Partner: The company's mission is to unlock the imagination of builders. We are the customer layer for the internet, powering the most engaging interactions companies build for their customers. We provide simple tools that solve hard problems, delivered as a developer-first cloud platform with global reach and no shenanigans pricing. About Uplers: Our goal is to make hiring reliable, simple, and fast. Our role will be to help all our talents find and apply for relevant direct placement onsite opportunities and progress in their career. We will support any grievances or challenges you may face during the engagement. You will also be assigned to a dedicated Talent Success Coach during the engagement. (Note: There are many more opportunities apart from this on the portal. Depending on the assessments you clear, you can apply for them as well). So, if you are ready for a new challenge, a great work environment, and an opportunity to take your career to the next level, don't hesitate to apply today. We are waiting for you!
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
- AWS (CANONICAL) primary
Context tags (catalog)
Stored enrichment (catalog DB)
- Category
- Platform
- Sub-category
- Cloud Platform
- Vendor
- Amazon
- License
- other_open
- Year introduced
- 2006
- Confidence
- 0.99
- Version strategy
- NOT_APPLICABLE
Maturity reasoning: AWS is a hiring-pipeline staple: it appears in a large share of cloud/DevOps job descriptions and dominates public cloud market share, with broad certification and vendor ecosystem support.
Skill profile (library / DB)
- Skill nature
- PLATFORM
- Volatility
- STABLE
- Typical lifespan
- EVERGREEN
- Category id
- 9
- Sub-category id
- 46
- Extractable
- True
- Also category
- False
Dimensions (API 2 worklist)
-
Cloud Platforms Catalog dimension db id 20
Library dimension (catalog)
Roles linked in library: .NET Backend Developer, Backend Developer, Cyber Security Engineer, Data Engineer, DevOps Engineer, Fullstack Developer, Go Backend Developer, Java Backend Developer, Kotlin Backend Developer, ML Engineer, MLOps Engineer, Node.js Backend Developer, Python Backend Developer, Scala Backend Developer
-
Cloud Platforms for AI Deployment Catalog dimension db id 211
Library dimension (catalog)
Roles linked in library: AI Engineer
-
Cloud Provider Platforms Catalog dimension db id 131
Library dimension (catalog)
Roles linked in library: Cloud Architect, Cloud Security Engineer
-
Cloud Security Posture Tools Catalog dimension db id 64
Library dimension (catalog)
Roles linked in library: Cloud Security Engineer, Cyber Security Engineer
-
Vendor Product Families Catalog dimension db id 477
Library dimension (catalog)
Roles linked in library: Engineering Manager
API 3 link attempts (this skill)
| Dimension | Skill↔dim | Role↔dim | Outcome |
|---|---|---|---|
|
Cloud Platforms
cloud-platforms
|
✓ | — | Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role) |
|
Cloud Platforms for AI Deployment
cloud-platforms-for-ai-deployment
|
✓ | — | Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role) |
|
Cloud Provider Platforms
cloud-provider-platforms
|
✓ | — | Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role) |
|
Cloud Security Posture Tools
cloud-security-posture-tools
|
✓ | — | Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role) |
|
Vendor Product Families
vendor-product-families
|
✓ | — | Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role) |
Aliases — catalog
- Kubernetes (CANONICAL) primary
- Kubernetes 1.0+ (VERSION)
- Kubernetes 1.x (VERSION)
- Kubernetes v1 (VERSION)
- k8s (VERSION)
- kubernetes 1.x (VERSION)
- kubernetes latest (VERSION)
Context tags (catalog)
Stored enrichment (catalog DB)
- Category
- Platform
- Sub-category
- Container Orchestration Platform
- Vendor
- Cloud Native Computing Foundation
- License
- apache_2
- Year introduced
- 2014
- Confidence
- 0.90
- Version strategy
- SEPARATE_ENTITY
- Version tag
- 1.30
Maturity reasoning: Broadly adopted in cloud-native stacks; Kubernetes appears in a large share of DevOps/SRE job descriptions and is the default orchestration platform across major cloud vendors.
Skill profile (library / DB)
- Skill nature
- PLATFORM
- Volatility
- STABLE
- Typical lifespan
- EVERGREEN
- Category id
- 9
- Sub-category id
- 557
- Extractable
- True
- Also category
- False
Dimensions (API 2 worklist)
-
Container Orchestration Platforms Catalog dimension db id 134
Library dimension (catalog)
Roles linked in library: Cloud Architect, DevOps Engineer
-
Kubernetes for ML Workloads Catalog dimension db id 47
Library dimension (catalog)
Roles linked in library: ML Engineer, MLOps Engineer
API 3 link attempts (this skill)
| Dimension | Skill↔dim | Role↔dim | Outcome |
|---|---|---|---|
|
Container Orchestration Platforms
container-orchestration-platforms
|
✓ | — | Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role) |
|
Kubernetes for ML Workloads
kubernetes-for-ml-workloads
|
✓ | — | Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role) |
Aliases — catalog
- Terraform (CANONICAL) primary
Context tags (catalog)
Stored enrichment (catalog DB)
- Category
- Tool
- Sub-category
- Infrastructure As Code Tool
- Vendor
- HashiCorp
- License
- mpl
- Year introduced
- 2014
- Confidence
- 0.93
- Version strategy
- NOT_APPLICABLE
Maturity reasoning: Terraform is broadly listed in DevOps/SRE/cloud JDs and remains a standard IaC tool across AWS/Azure/GCP; HashiCorp’s ecosystem and widespread GitHub usage signal strong market adoption.
Skill profile (library / DB)
- Skill nature
- TOOL
- Volatility
- STABLE
- Typical lifespan
- EVERGREEN
- Category id
- 13
- Sub-category id
- 191
- Extractable
- True
- Also category
- False
Dimensions (API 2 worklist)
-
Infrastructure & Security Automation Frameworks Catalog dimension db id 249
Library dimension (catalog)
Roles linked in library: Cloud Security Engineer
-
Infrastructure as Code Catalog dimension db id 132
Library dimension (catalog)
Roles linked in library: Cloud Architect, DevOps Engineer
-
Infrastructure as Code for ML Catalog dimension db id 57
Library dimension (catalog)
Roles linked in library: ML Engineer
API 3 link attempts (this skill)
| Dimension | Skill↔dim | Role↔dim | Outcome |
|---|---|---|---|
|
Infrastructure & Security Automation Frameworks
infrastructure-security-automation-frameworks
|
✓ | — | Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role) |
|
Infrastructure as Code
infrastructure-as-code
|
✓ | — | Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role) |
|
Infrastructure as Code for ML
infrastructure-as-code-for-ml
|
✓ | — | Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role) |
Aliases — catalog
- Go (CANONICAL) primary
- Go 1.0 (VERSION)
- Go 1.1 (VERSION)
- Go 1.10 (VERSION)
- Go 1.11 (VERSION)
- Go 1.12 (VERSION)
- Go 1.13 (VERSION)
- Go 1.14 (VERSION)
- Go 1.15 (VERSION)
- Go 1.16 (VERSION)
- Go 1.17 (VERSION)
- Go 1.18 (VERSION)
- Go 1.19 (VERSION)
- Go 1.2 (VERSION)
- Go 1.20 (VERSION)
- Go 1.21 (VERSION)
- Go 1.22 (VERSION)
- Go 1.3 (VERSION)
- Go 1.4 (VERSION)
- Go 1.5 (VERSION)
- Go 1.6 (VERSION)
- Go 1.7 (VERSION)
- Go 1.8 (VERSION)
- Go 1.9 (VERSION)
- Go 1.x (VERSION)
- Golang (VERSION)
- go 1.18 (VERSION)
- go 1.19 (VERSION)
- go 1.20 (VERSION)
- go 1.21 (VERSION)
- go 1.22 (VERSION)
- go latest (VERSION)
- go1.18 (VERSION)
- go1.19 (VERSION)
- go1.20 (VERSION)
- go1.21 (VERSION)
- go1.22 (VERSION)
- go1.x (VERSION)
- golang (VERSION)
Context tags (catalog)
Stored enrichment (catalog DB)
- Category
- Language
- Sub-category
- Programming Language
- Vendor
- License
- bsd
- Year introduced
- 2009
- Confidence
- 0.99
- Version strategy
- NOT_APPLICABLE
Maturity reasoning: Go appears in many current job descriptions for backend, cloud, and DevOps roles, and is a standard language in Kubernetes, Docker, and cloud-native stacks; strong GitHub and ecosystem adoption signal broad market demand.
Skill profile (library / DB)
- Skill nature
- LANGUAGE
- Volatility
- STABLE
- Typical lifespan
- EVERGREEN
- Category id
- 6
- Sub-category id
- 96
- Extractable
- True
- Also category
- False
Dimensions (API 2 worklist)
-
Cloud Security Scripting & DSL Languages Catalog dimension db id 248
Library dimension (catalog)
Roles linked in library: Cloud Security Engineer
-
Go Language and Toolchain Catalog dimension db id 367
Library dimension (catalog)
Roles linked in library: Go Backend Developer
-
Programming Languages Catalog dimension db id 1
Library dimension (catalog)
Roles linked in library: Backend Developer, Fullstack Developer, Fullstack Developer
-
Programming Languages and Scripting Catalog dimension db id 59
Library dimension (catalog)
Roles linked in library: Cyber Security Engineer
-
Programming Languages for ML Systems Catalog dimension db id 39
Library dimension (catalog)
Roles linked in library: ML Engineer, MLOps Engineer
API 3 link attempts (this skill)
| Dimension | Skill↔dim | Role↔dim | Outcome |
|---|---|---|---|
|
Cloud Security Scripting & DSL Languages
cloud-security-scripting-dsl-languages
|
✓ | — | Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role) |
|
Go Language and Toolchain
go-language-and-toolchain
|
✓ | — | Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role) |
|
Programming Languages
programming-languages
|
✓ | — | Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role) |
|
Programming Languages and Scripting
programming-languages-and-scripting
|
✓ | — | Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role) |
|
Programming Languages for ML Systems
programming-languages-for-ml-systems
|
✓ | — | Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role) |
Aliases — catalog
- Kafka (CANONICAL) primary
Context tags (catalog)
Stored enrichment (catalog DB)
- Category
- Datastore
- Sub-category
- Event Stream Store
- Vendor
- Confluent
- License
- apache_2
- Year introduced
- 2011
- Confidence
- 0.90
- Version strategy
- NOT_APPLICABLE
Maturity reasoning: Kafka appears in many production JDs for event streaming and data pipelines, and remains a standard platform in cloud/vendor offerings (e.g., Confluent, AWS MSK), indicating broad hiring demand.
Skill profile (library / DB)
- Skill nature
- TOOL
- Volatility
- STABLE
- Typical lifespan
- EVERGREEN
- Category id
- 3
- Sub-category id
- 3533
- Extractable
- True
- Also category
- False
Dimensions (API 2 worklist)
-
Asynchronous Messaging and Event Streaming Catalog dimension db id 297
Library dimension (catalog)
Roles linked in library: .NET Backend Developer, Go Backend Developer, Kotlin Backend Developer, Node.js Backend Developer, Scala Backend Developer
-
Messaging and Background Jobs Catalog dimension db id 291
Library dimension (catalog)
Roles linked in library: PHP Backend Developer, Python Backend Developer, Ruby Backend Developer
-
Messaging and Event Streaming Catalog dimension db id 8
Library dimension (catalog)
Roles linked in library: Backend Developer, Data Engineer
API 3 link attempts (this skill)
| Dimension | Skill↔dim | Role↔dim | Outcome |
|---|---|---|---|
|
Asynchronous Messaging and Event Streaming
asynchronous-messaging-and-event-streaming
|
✓ | — | Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role) |
|
Messaging and Background Jobs
messaging-and-background-jobs
|
✓ | — | Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role) |
|
Messaging and Event Streaming
messaging-and-event-streaming
|
✓ | — | Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role) |
Aliases — catalog
- Argo CD (CANONICAL) primary
Context tags (catalog)
Stored enrichment (catalog DB)
- Category
- Tool
- Sub-category
- Gitops Deployment Tool
- Vendor
- Argo Project
- License
- apache_2
- Year introduced
- 2018
- Confidence
- 0.95
- Version strategy
- NOT_APPLICABLE
Maturity reasoning: Common GitOps deployment tool; appears frequently in Kubernetes/platform engineering JDs and has strong GitHub adoption, with broad vendor/docs ecosystem around Argo CD.
Skill profile (library / DB)
- Skill nature
- TOOL
- Volatility
- STABLE
- Typical lifespan
- EVERGREEN
- Category id
- 13
- Sub-category id
- 189
- Extractable
- True
- Also category
- False
Dimensions (API 2 worklist)
-
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 for Machine Learning
ci-cd-for-machine-learning
|
✓ | — | Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role) |
Aliases — catalog
- Buildkite (CANONICAL) primary
Context tags (catalog)
Stored enrichment (catalog DB)
- Category
- Platform
- Sub-category
- Ci Cd Platform
- Vendor
- Buildkite
- License
- other_open
- Year introduced
- 2013
- Confidence
- 0.97
- Version strategy
- NOT_APPLICABLE
Maturity reasoning: Buildkite appears in CI/CD job postings and is used by teams needing scalable pipelines, but JD volume is far below GitHub Actions/Jenkins and it’s not a universal hiring staple.
Skill profile (library / DB)
- Skill nature
- PLATFORM
- Volatility
- EMERGING
- Typical lifespan
- EVERGREEN
- Category id
- 9
- Sub-category id
- 632
- 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
API 3 link attempts (this skill)
| Dimension | Skill↔dim | Role↔dim | Outcome |
|---|---|---|---|
|
CI/CD Pipeline Platforms
ci-cd-pipeline-platforms
|
✓ | — | Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role) |
Aliases — catalog
- Grafana (CANONICAL) primary
Context tags (catalog)
Stored enrichment (catalog DB)
- Category
- Platform
- Sub-category
- Observability Platform
- Vendor
- Grafana Labs
- License
- apache_2
- Year introduced
- 2014
- Confidence
- 0.90
- Version strategy
- NOT_APPLICABLE
Maturity reasoning: Grafana appears in many DevOps/SRE job descriptions and is a standard observability dashboarding tool alongside Prometheus and Loki; strong GitHub/community adoption and broad vendor integrations signal mainstream use.
Skill profile (library / DB)
- Skill nature
- PLATFORM
- Volatility
- STABLE
- Typical lifespan
- EVERGREEN
- Category id
- 9
- Sub-category id
- 176
- 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
-
Observability and Operations Catalog dimension db id 143
Library dimension (catalog)
Roles linked in library: Cloud Architect
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 skipped (dimension not under chosen role) |
|
Observability and Operations
observability-and-operations
|
✓ | — | Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role) |
Aliases — catalog
- Prometheus (CANONICAL) primary
Context tags (catalog)
Stored enrichment (catalog DB)
- Category
- Platform
- Sub-category
- Monitoring Platform
- Vendor
- Cloud Native Computing Foundation
- License
- apache_2
- Year introduced
- 2012
- Confidence
- 0.62
- Version strategy
- NOT_APPLICABLE
Maturity reasoning: Prometheus is widely listed in DevOps/SRE job descriptions and is a standard CNCF monitoring stack component, often paired with Grafana for production observability.
Skill profile (library / DB)
- Skill nature
- PLATFORM
- Volatility
- STABLE
- Typical lifespan
- EVERGREEN
- Category id
- 9
- Sub-category id
- 2837
- 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
-
Observability and Operations Catalog dimension db id 143
Library dimension (catalog)
Roles linked in library: Cloud Architect
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 skipped (dimension not under chosen role) |
|
Observability and Operations
observability-and-operations
|
✓ | — | Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role) |
Aliases — catalog
- Datadog (CANONICAL) primary
Context tags (catalog)
Stored enrichment (catalog DB)
- Category
- Platform
- Sub-category
- Observability Platform
- Vendor
- Datadog, Inc.
- License
- other_open
- Year introduced
- 2010
- Confidence
- 0.99
- Version strategy
- NOT_APPLICABLE
Maturity reasoning: Datadog appears frequently in SRE/DevOps job descriptions and is a standard observability platform alongside Prometheus/Grafana, indicating broad market adoption.
Skill profile (library / DB)
- Skill nature
- PLATFORM
- Volatility
- STABLE
- Typical lifespan
- EVERGREEN
- Category id
- 9
- Sub-category id
- 176
- 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
-
Observability and Operations Catalog dimension db id 143
Library dimension (catalog)
Roles linked in library: Cloud Architect
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 skipped (dimension not under chosen role) |
|
Observability and Operations
observability-and-operations
|
✓ | — | 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
- Monitoring Tools
- Sub-category
- general
- Skill nature
- TOOL
- Volatility
- MEDIUM
- Typical lifespan
- MULTI_YEAR
- Version strategy
- UNVERSIONED
Aliases — catalog
- Agile (CANONICAL) primary
Context tags (catalog)
Stored enrichment (catalog DB)
- Category
- Methodology
- Sub-category
- Agile
- Confidence
- 0.99
- Version strategy
- NOT_APPLICABLE
Maturity reasoning: Agile appears in a large share of software job descriptions and is a standard hiring-pipeline requirement; Scrum/Kanban are commonly listed alongside it, showing broad market adoption.
Skill profile (library / DB)
- Skill nature
- METHODOLOGY
- Volatility
- STABLE
- Typical lifespan
- EVERGREEN
- Category id
- 8
- Sub-category id
- 3594
- Extractable
- True
- Also category
- False
Dimensions (API 2 worklist)
-
React Frontend Development Catalog dimension db id 96
Library dimension (catalog)
-
Software Concepts, Patterns & Practices Catalog dimension db id 478
Library dimension (catalog)
Roles linked in library: Engineering Manager
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) |
|
Software Concepts, Patterns & Practices
software-concepts-patterns-practices
|
✓ | — | 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 |
|---|---|---|---|---|---|---|
| AWS | in_db |
Cloud Platforms
cloud-platforms
|
✓ | — | Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role) | |
| AWS | in_db |
Cloud Platforms for AI Deployment
cloud-platforms-for-ai-deployment
|
✓ | — | Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role) | |
| AWS | in_db |
Cloud Provider Platforms
cloud-provider-platforms
|
✓ | — | Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role) | |
| AWS | in_db |
Cloud Security Posture Tools
cloud-security-posture-tools
|
✓ | — | Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role) | |
| AWS | in_db |
Vendor Product Families
vendor-product-families
|
✓ | — | Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role) | |
| Kubernetes | in_db |
Container Orchestration Platforms
container-orchestration-platforms
|
✓ | — | Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role) | |
| Kubernetes | in_db |
Kubernetes for ML Workloads
kubernetes-for-ml-workloads
|
✓ | — | Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role) | |
| Terraform | in_db |
Infrastructure & Security Automation Frameworks
infrastructure-security-automation-frameworks
|
✓ | — | Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role) | |
| Terraform | in_db |
Infrastructure as Code
infrastructure-as-code
|
✓ | — | Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role) | |
| Terraform | in_db |
Infrastructure as Code for ML
infrastructure-as-code-for-ml
|
✓ | — | Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role) | |
| Go | in_db |
Cloud Security Scripting & DSL Languages
cloud-security-scripting-dsl-languages
|
✓ | — | Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role) | |
| Go | in_db |
Go Language and Toolchain
go-language-and-toolchain
|
✓ | — | Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role) | |
| Go | in_db |
Programming Languages
programming-languages
|
✓ | — | Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role) | |
| Go | in_db |
Programming Languages and Scripting
programming-languages-and-scripting
|
✓ | — | Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role) | |
| Go | in_db |
Programming Languages for ML Systems
programming-languages-for-ml-systems
|
✓ | — | Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role) | |
| Kafka | in_db |
Asynchronous Messaging and Event Streaming
asynchronous-messaging-and-event-streaming
|
✓ | — | Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role) | |
| Kafka | in_db |
Messaging and Background Jobs
messaging-and-background-jobs
|
✓ | — | Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role) | |
| Kafka | in_db |
Messaging and Event Streaming
messaging-and-event-streaming
|
✓ | — | Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role) | |
| Argo CD | in_db |
CI/CD for Machine Learning
ci-cd-for-machine-learning
|
✓ | — | Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role) | |
| Buildkite | in_db |
CI/CD Pipeline Platforms
ci-cd-pipeline-platforms
|
✓ | — | Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role) | |
| Grafana | in_db |
Backend Observability, Logging, and Diagnostics
backend-observability-logging-and-diagnostics
|
✓ | — | Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role) | |
| Grafana | in_db |
Observability and Incident Response
observability-and-incident-response
|
✓ | — | Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role) | |
| Grafana | in_db |
Observability and Incident Triage
observability-and-incident-triage
|
✓ | — | Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role) | |
| Grafana | in_db |
Observability and Operations
observability-and-operations
|
✓ | — | Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role) | |
| Prometheus | in_db |
Backend Observability, Logging, and Diagnostics
backend-observability-logging-and-diagnostics
|
✓ | — | Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role) | |
| Prometheus | in_db |
Observability and Incident Response
observability-and-incident-response
|
✓ | — | Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role) | |
| Prometheus | in_db |
Observability and Incident Triage
observability-and-incident-triage
|
✓ | — | Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role) | |
| Prometheus | in_db |
Observability and Operations
observability-and-operations
|
✓ | — | Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role) | |
| Datadog | in_db |
Observability and Incident Triage
observability-and-incident-triage
|
✓ | — | Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role) | |
| Datadog | in_db |
Observability and Operations
observability-and-operations
|
✓ | — | Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role) | |
| Agile | in_db |
React Frontend Development
d_init_01
|
✓ | — | Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role) | |
| Agile | in_db |
Software Concepts, Patterns & Practices
software-concepts-patterns-practices
|
✓ | — | Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role) |
Library artifacts (this run)
| Kind | Detail | DB id |
|---|---|---|
| canonical_skill_proposed | Loki | type=Monitoring Tools subtype=general nature=TOOL lifespan=MULTI_YEAR |
nano JD Parser — gpt-4.1-nano click to toggle
Certifications
Show raw JSON
{
"JD_type": "pass",
"about_company": {
"source_marker": {
"first_5_words": "The company\u0027s mission is to",
"last_5_words": "with global reach and no"
},
"text": "The company\u0027s mission is to unlock the imagination of builders.\n\nWe are the customer layer for the internet, powering the most engaging interactions companies build for their customers. We provide simple tools that solve hard problems, delivered as a developer-first cloud platform with global reach and no shenanigans pricing.",
"word_count": 51
},
"certifications": [
"Certified Kubernetes Administrator",
"CKA"
],
"company_name": "Uplers",
"ctc": null,
"domain": {
"primary": {
"aliases": [
"Tech Consulting",
"Software Development"
],
"domain": "IT Services \u0026 Consulting"
},
"secondary": null
},
"education": [],
"experience": {
"max": 15,
"min": 12,
"raw": "Minimum of 12-15 years experience as a seasoned Software Engineer, Site Reliability Engineer, Platform Engineer, Infrastructure Engineer or another similar role"
},
"job_locations": [
{
"aliases": [
"Bangalore"
],
"city": "Bengaluru",
"country": "India",
"state": "Karnataka",
"work_mode": "onsite"
}
],
"role": "Principal Software Engineer",
"role_aliases": [
"Software Engineer",
"Senior Software Engineer",
"Lead Software Engineer"
],
"role_archetype": "Engineering",
"roles_and_responsibilities": [
{
"bullet_count": 7,
"heading": "Roles \u0026 Responsibilities",
"heading_was_present": true,
"source_marker": {
"first_5_words": "In this role, you\u2019ll:",
"last_5_words": "and security of our systems"
},
"text": "In this role, you\u2019ll:\n\n\u2022 Write software to automate everything from manual run-book processes to complete system provisioning\n\u2022 Architect and improve our Infrastructure container orchestration platform (Kubernetes).\n\u2022 Build the next version of Segment\u2019s Service Platform to support teams in deploying hundreds of services across a multi-region cloud environment\n\u2022 Support teams working on large scale infrastructure processing millions of events per second and storing hundreds of TBs per month\n\u2022 Participate in agile ceremonies and on a 12/7 on call rotation.\n\u2022 Architect and solve complex infrastructure problems in public cloud (AWS)\n\u2022 As a key member of our engineering team, you will play a crucial role in ensuring the reliability, scalability, and security of our systems on cloud infrastructure.",
"word_count": 134
},
{
"bullet_count": 10,
"heading": "This Role Requires",
"heading_was_present": true,
"source_marker": {
"first_5_words": "This Role Requires:",
"last_5_words": "and observability stack like"
},
"text": "\u2022 Minimum of 12-15 years experience as a seasoned Software Engineer, Site Reliability Engineer, Platform Engineer, Infrastructure Engineer or another similar role\n\u2022 AWS Expertise: Leverage your in-depth knowledge of Amazon Web Services (AWS) to architect, optimize, and manage cloud infrastructure for our applications.\n\u2022 Kubernetes Mastery: Drive the adoption and optimization of Kubernetes (K8s) for containerized applications, ensuring scalability, efficiency, and reliability.\n\u2022 Infrastructure as Code (IaC): Strong Terraform experience to design, implement, and maintain infrastructure as code, enabling seamless and reproducible deployments.\n\u2022 Go Lang Automation: Develop and maintain automation scripts and tools using Go lang, streamlining operational tasks and enhancing system efficiency.\n\u2022 Security Focus: Collaborate with our security teams to implement and enhance security measures, ensuring the confidentiality, integrity, and availability of our systems.\n\u2022 Developer Experience: Champion developer experience initiatives, focusing on optimizing workflows, reducing friction, and enhancing the overall development process.\n\u2022 Kafka Expertise: Strong expertise in Kafka design, implement, and manage event streaming architectures\n\u2022 Strong experience in DevOps tools like ArgoCD, Buildkite\n\u2022 Mastery in observability stack like Grafana, Prometheus, Datadog, Loki.",
"word_count": 218
}
],
"urls": []
}
API 1 — extract-from-jd click to toggle
{
"final_skills": [
{
"is_primary": true,
"skill_name": "AWS"
},
{
"is_primary": true,
"skill_name": "Kubernetes"
},
{
"is_primary": true,
"skill_name": "Terraform"
},
{
"is_primary": true,
"skill_name": "Go"
},
{
"is_primary": true,
"skill_name": "Kafka"
},
{
"is_primary": true,
"skill_name": "Argo CD"
},
{
"is_primary": true,
"skill_name": "Buildkite"
},
{
"is_primary": true,
"skill_name": "Grafana"
},
{
"is_primary": true,
"skill_name": "Prometheus"
},
{
"is_primary": true,
"skill_name": "Datadog"
},
{
"is_primary": true,
"skill_name": "Loki"
},
{
"is_primary": false,
"skill_name": "Agile"
}
],
"jd_role": {
"display_name": "Principal Software Engineer",
"rationale": null,
"role_aliases": [
"Software Engineer",
"Senior Software Engineer",
"Lead Software Engineer"
],
"role_archetype": "Engineering",
"slug": ""
},
"nano_parsed": {
"JD_type": "pass",
"about_company": {
"source_marker": {
"first_5_words": "The company\u0027s mission is to",
"last_5_words": "with global reach and no"
},
"text": "The company\u0027s mission is to unlock the imagination of builders.\n\nWe are the customer layer for the internet, powering the most engaging interactions companies build for their customers. We provide simple tools that solve hard problems, delivered as a developer-first cloud platform with global reach and no shenanigans pricing.",
"word_count": 51
},
"certifications": [
"Certified Kubernetes Administrator",
"CKA"
],
"company_name": "Uplers",
"ctc": null,
"domain": {
"primary": {
"aliases": [
"Tech Consulting",
"Software Development"
],
"domain": "IT Services \u0026 Consulting"
},
"secondary": null
},
"education": [],
"experience": {
"max": 15,
"min": 12,
"raw": "Minimum of 12-15 years experience as a seasoned Software Engineer, Site Reliability Engineer, Platform Engineer, Infrastructure Engineer or another similar role"
},
"job_locations": [
{
"aliases": [
"Bangalore"
],
"city": "Bengaluru",
"country": "India",
"state": "Karnataka",
"work_mode": "onsite"
}
],
"role": "Principal Software Engineer",
"role_aliases": [
"Software Engineer",
"Senior Software Engineer",
"Lead Software Engineer"
],
"role_archetype": "Engineering",
"roles_and_responsibilities": [
{
"bullet_count": 7,
"heading": "Roles \u0026 Responsibilities",
"heading_was_present": true,
"source_marker": {
"first_5_words": "In this role, you\u2019ll:",
"last_5_words": "and security of our systems"
},
"text": "In this role, you\u2019ll:\n\n\u2022 Write software to automate everything from manual run-book processes to complete system provisioning\n\u2022 Architect and improve our Infrastructure container orchestration platform (Kubernetes).\n\u2022 Build the next version of Segment\u2019s Service Platform to support teams in deploying hundreds of services across a multi-region cloud environment\n\u2022 Support teams working on large scale infrastructure processing millions of events per second and storing hundreds of TBs per month\n\u2022 Participate in agile ceremonies and on a 12/7 on call rotation.\n\u2022 Architect and solve complex infrastructure problems in public cloud (AWS)\n\u2022 As a key member of our engineering team, you will play a crucial role in ensuring the reliability, scalability, and security of our systems on cloud infrastructure.",
"word_count": 134
},
{
"bullet_count": 10,
"heading": "This Role Requires",
"heading_was_present": true,
"source_marker": {
"first_5_words": "This Role Requires:",
"last_5_words": "and observability stack like"
},
"text": "\u2022 Minimum of 12-15 years experience as a seasoned Software Engineer, Site Reliability Engineer, Platform Engineer, Infrastructure Engineer or another similar role\n\u2022 AWS Expertise: Leverage your in-depth knowledge of Amazon Web Services (AWS) to architect, optimize, and manage cloud infrastructure for our applications.\n\u2022 Kubernetes Mastery: Drive the adoption and optimization of Kubernetes (K8s) for containerized applications, ensuring scalability, efficiency, and reliability.\n\u2022 Infrastructure as Code (IaC): Strong Terraform experience to design, implement, and maintain infrastructure as code, enabling seamless and reproducible deployments.\n\u2022 Go Lang Automation: Develop and maintain automation scripts and tools using Go lang, streamlining operational tasks and enhancing system efficiency.\n\u2022 Security Focus: Collaborate with our security teams to implement and enhance security measures, ensuring the confidentiality, integrity, and availability of our systems.\n\u2022 Developer Experience: Champion developer experience initiatives, focusing on optimizing workflows, reducing friction, and enhancing the overall development process.\n\u2022 Kafka Expertise: Strong expertise in Kafka design, implement, and manage event streaming architectures\n\u2022 Strong experience in DevOps tools like ArgoCD, Buildkite\n\u2022 Mastery in observability stack like Grafana, Prometheus, Datadog, Loki.",
"word_count": 218
}
],
"urls": []
},
"rejected": false,
"rejection_reason": null,
"run_id": "23c596d1-8698-43f6-a9e0-9e4258417dec",
"stage3_signals": {
"alias_found": true,
"alias_match_roles": [
{
"display_name": "Backend Developer",
"kra_matches": null,
"matched_count": null,
"matched_skills": null,
"role_id": 1,
"score": 1.0,
"slug": "backend-engineer",
"total_count": null
}
],
"kra_match_roles": [
{
"display_name": "DevOps Engineer",
"kra_matches": [
{
"kra_text": "Provisions and manages cloud infrastructure on AWS, Azure, or GCP using Terraform or CloudFormation to enforce infrastructure-as-code standards.",
"sentence": "Infrastructure as Code (IaC): Strong Terraform experience to design, implement, and maintain infrastructure as code, enabling seamless and reproducible deployments.",
"similarity": 0.6324
},
{
"kra_text": "Manages container orchestration with Kubernetes and Docker, deploying applications as pods, managing namespaces, and configuring auto-scaling across cloud environments.",
"sentence": "Architect and improve our Infrastructure container orchestration platform (Kubernetes).",
"similarity": 0.6285
},
{
"kra_text": "Manages container orchestration with Kubernetes and Docker, deploying applications as pods, managing namespaces, and configuring auto-scaling across cloud environments.",
"sentence": "Kubernetes Mastery: Drive the adoption and optimization of Kubernetes (K8s) for containerized applications, ensuring scalability, efficiency, and reliability.",
"similarity": 0.6164
}
],
"matched_count": null,
"matched_skills": null,
"role_id": 10,
"score": 0.6258,
"slug": "devops-engineer",
"total_count": null
},
{
"display_name": "Cloud Architect",
"kra_matches": [
{
"kra_text": "Conducts architecture reviews, approves technical design documents, and guides engineering teams through cloud migration and modernization projects.",
"sentence": "Architect and solve complex infrastructure problems in public cloud (AWS)",
"similarity": 0.5666
},
{
"kra_text": "Designs multi-region and multi-availability-zone cloud infrastructure architectures for high availability, fault tolerance, and horizontal scalability.",
"sentence": "Build the next version of Segment\u2019s Service Platform to support teams in deploying hundreds of services across a multi-region cloud environment",
"similarity": 0.53
},
{
"kra_text": "Defines cloud adoption roadmaps, lift-and-shift vs. refactor migration strategies, and landing zone architectures for workloads moving to AWS, Azure, or GCP.",
"sentence": "AWS Expertise: Leverage your in-depth knowledge of Amazon Web Services (AWS) to architect, optimize, and manage cloud infrastructure for our applications.",
"similarity": 0.5281
}
],
"matched_count": null,
"matched_skills": null,
"role_id": 9,
"score": 0.5415,
"slug": "cloud-architect",
"total_count": null
},
{
"display_name": "Cloud Security Engineer",
"kra_matches": [
{
"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": "Architect and solve complex infrastructure problems in public cloud (AWS)",
"similarity": 0.5652
},
{
"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": "AWS Expertise: Leverage your in-depth knowledge of Amazon Web Services (AWS) to architect, optimize, and manage cloud infrastructure for our applications.",
"similarity": 0.5395
},
{
"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": "As a key member of our engineering team, you will play a crucial role in ensuring the reliability, scalability, and security of our systems on cloud infrastructure.",
"similarity": 0.4937
}
],
"matched_count": null,
"matched_skills": null,
"role_id": 23,
"score": 0.5328,
"slug": "cloud-security-engineer",
"total_count": null
},
{
"display_name": "Data Engineer",
"kra_matches": [
{
"kra_text": "Develops batch and real-time streaming data pipelines using Apache Spark, Apache Kafka, Apache Flink, or Airflow for data movement and processing at scale.",
"sentence": "Kafka Expertise: Strong expertise in Kafka design, implement, and manage event streaming architectures",
"similarity": 0.5479
},
{
"kra_text": "Builds data ingestion pipelines to collect data from transactional databases, third-party APIs, event streams, and file sources into centralized data platforms.",
"sentence": "Support teams working on large scale infrastructure processing millions of events per second and storing hundreds of TBs per month",
"similarity": 0.5159
},
{
"kra_text": "Optimizes pipeline throughput, partitioning strategies, and query performance across cloud data warehouses like Snowflake, BigQuery, or Redshift.",
"sentence": "AWS Expertise: Leverage your in-depth knowledge of Amazon Web Services (AWS) to architect, optimize, and manage cloud infrastructure for our applications.",
"similarity": 0.4252
}
],
"matched_count": null,
"matched_skills": null,
"role_id": 2,
"score": 0.4963,
"slug": "data-engineer",
"total_count": null
},
{
"display_name": "Backend Developer",
"kra_matches": [
{
"kra_text": "Adds structured logging, metrics, distributed tracing, and alerting to improve system observability and support production debugging.",
"sentence": "Mastery in observability stack like Grafana, Prometheus, Datadog, Loki.",
"similarity": 0.5142
},
{
"kra_text": "Configures Docker containers, deployment descriptors, environment variables, and CI/CD pipeline stages for backend service releases.",
"sentence": "Strong experience in DevOps tools like ArgoCD, Buildkite",
"similarity": 0.4609
},
{
"kra_text": "Integrates with third-party services, payment gateways, messaging queues like Kafka or RabbitMQ, and internal microservices via HTTP and event-driven patterns.",
"sentence": "Kafka Expertise: Strong expertise in Kafka design, implement, and manage event streaming architectures",
"similarity": 0.4606
}
],
"matched_count": null,
"matched_skills": null,
"role_id": 1,
"score": 0.4786,
"slug": "backend-engineer",
"total_count": null
}
],
"skill_match_roles": [
{
"display_name": "DevOps Engineer",
"kra_matches": null,
"matched_count": 7,
"matched_skills": [
"AWS",
"Buildkite",
"Datadog",
"Grafana",
"Kubernetes",
"Prometheus",
"Terraform"
],
"role_id": 10,
"score": 0.6364,
"slug": "devops-engineer",
"total_count": 11
},
{
"display_name": "Cloud Architect",
"kra_matches": null,
"matched_count": 6,
"matched_skills": [
"AWS",
"Datadog",
"Grafana",
"Kubernetes",
"Prometheus",
"Terraform"
],
"role_id": 9,
"score": 0.5455,
"slug": "cloud-architect",
"total_count": 11
},
{
"display_name": "ML Engineer",
"kra_matches": null,
"matched_count": 5,
"matched_skills": [
"AWS",
"Argo CD",
"Go",
"Kubernetes",
"Terraform"
],
"role_id": 3,
"score": 0.4545,
"slug": "ml-engineer",
"total_count": 11
},
{
"display_name": "Backend Developer",
"kra_matches": null,
"matched_count": 5,
"matched_skills": [
"AWS",
"Go",
"Grafana",
"Kafka",
"Prometheus"
],
"role_id": 1,
"score": 0.4545,
"slug": "backend-engineer",
"total_count": 11
},
{
"display_name": "Node.js Backend Developer",
"kra_matches": null,
"matched_count": 4,
"matched_skills": [
"AWS",
"Grafana",
"Kafka",
"Prometheus"
],
"role_id": 82,
"score": 0.3636,
"slug": "node-backend-developer",
"total_count": 11
}
]
},
"stage4_decision": {
"alias_collision_detected": false,
"case": "DOMAIN",
"chosen_role": {
"display_name": "Platform Engineer",
"kra_matches": null,
"matched_count": null,
"matched_skills": null,
"role_id": 133,
"score": 0.9,
"slug": "platform-engineer",
"total_count": null
},
"confidence": 0.9,
"is_new_role": false,
"llm2_fired": false,
"llm2_reasoning": null,
"matched_dimensions": [
"Platform Engineering",
"Infrastructure Automation",
"Container Orchestration",
"Cloud Infrastructure Architecture",
"Developer Experience",
"Event Streaming Infrastructure",
"Observability and Monitoring",
"Reliability and Scalability"
],
"matched_kras": [
"Write software to automate everything from manual run-book processes",
"Architect and improve our Infrastructure container orchestration platform",
"Build the next version of Segment\u2019s Service Platform",
"Support teams working on large scale infrastructure",
"Architect and solve complex infrastructure problems in public cloud",
"Ensure the reliability, scalability, and security of our systems"
],
"matched_skills": [
"Kubernetes",
"AWS",
"Terraform",
"Go lang",
"Kafka",
"ArgoCD",
"Buildkite",
"Grafana",
"Prometheus",
"Datadog",
"Loki"
],
"new_role_display_name": null,
"new_role_slug": null,
"queued": false,
"reasoning": "Domain=DevOps \u0026 Platform \u2192 sub-role infrastructure-platform-engineer; The JD centers on internal service platform, developer experience, automation, and large-scale cloud infrastructure, which best matches Platform Engineer over narrower Kubernetes, IaC, or pure SRE roles.",
"sub_role": {
"confidence": 0.97,
"display_name": "Infrastructure Platform Engineer",
"reasoning": "The JD centers on architecting Kubernetes/AWS/Terraform-based infrastructure platforms, service platform scaling, observability, and DevOps automation, which best matches an Infrastructure Platform Engineer.",
"role_id": 373,
"slug": "infrastructure-platform-engineer"
}
},
"stage5_updates": {
"centroid_n_after": 5,
"centroid_updated": true,
"collision_log_id": null,
"new_kra_attached": {
"best_kra_similarity": 0.0,
"queue_id": 1267,
"r_and_r_preview": "In this role, you\u2019ll:\n\n\u2022 Write software to automate everything from manual run-book processes to complete system provisioning\n\u2022 Architect and improve our Infrastructure container orchestration platfor",
"role_display_name": "Platform Engineer",
"role_slug": "platform-engineer",
"status": "pending"
},
"new_skills_attached": [
{
"is_primary": true,
"queue_id": 17479,
"role_display_name": "Platform Engineer",
"role_slug": "platform-engineer",
"skill_name": "Loki",
"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": 406,
"existing_alias_text": "AWS",
"input_term": "AWS",
"matched_canonical": {
"category_id": 9,
"display_name": "AWS",
"id": 187,
"is_also_category": false,
"is_extractable": true,
"skill_nature": "PLATFORM",
"slug": "aws",
"sub_category_id": 46,
"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": 1267,
"existing_alias_text": "Kubernetes",
"input_term": "Kubernetes",
"matched_canonical": {
"category_id": 9,
"display_name": "Kubernetes",
"id": 726,
"is_also_category": false,
"is_extractable": true,
"skill_nature": "PLATFORM",
"slug": "kubernetes",
"sub_category_id": 557,
"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": 547,
"existing_alias_text": "Terraform",
"input_term": "Terraform",
"matched_canonical": {
"category_id": 13,
"display_name": "Terraform",
"id": 286,
"is_also_category": false,
"is_extractable": true,
"skill_nature": "TOOL",
"slug": "terraform",
"sub_category_id": 191,
"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": 25,
"existing_alias_text": "Go",
"input_term": "Go",
"matched_canonical": {
"category_id": 6,
"display_name": "Go",
"id": 3,
"is_also_category": false,
"is_extractable": true,
"skill_nature": "LANGUAGE",
"slug": "go",
"sub_category_id": 96,
"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": 173,
"existing_alias_text": "Kafka",
"input_term": "Kafka",
"matched_canonical": {
"category_id": 3,
"display_name": "Kafka",
"id": 36,
"is_also_category": false,
"is_extractable": true,
"skill_nature": "TOOL",
"slug": "kafka",
"sub_category_id": 3533,
"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": 545,
"existing_alias_text": "Argo CD",
"input_term": "Argo CD",
"matched_canonical": {
"category_id": 13,
"display_name": "Argo CD",
"id": 284,
"is_also_category": false,
"is_extractable": true,
"skill_nature": "TOOL",
"slug": "argo-cd",
"sub_category_id": 189,
"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": 1372,
"existing_alias_text": "Buildkite",
"input_term": "Buildkite",
"matched_canonical": {
"category_id": 9,
"display_name": "Buildkite",
"id": 827,
"is_also_category": false,
"is_extractable": true,
"skill_nature": "PLATFORM",
"slug": "buildkite",
"sub_category_id": 632,
"typical_lifespan": "EVERGREEN",
"volatility": "EMERGING"
},
"matched_via": "alias"
},
{
"alias_persist_skipped_reason": "alias_text already exists for this canonical skill",
"alias_persisted": false,
"existing_alias_id": 184,
"existing_alias_text": "Grafana",
"input_term": "Grafana",
"matched_canonical": {
"category_id": 9,
"display_name": "Grafana",
"id": 47,
"is_also_category": false,
"is_extractable": true,
"skill_nature": "PLATFORM",
"slug": "grafana",
"sub_category_id": 176,
"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": 183,
"existing_alias_text": "Prometheus",
"input_term": "Prometheus",
"matched_canonical": {
"category_id": 9,
"display_name": "Prometheus",
"id": 46,
"is_also_category": false,
"is_extractable": true,
"skill_nature": "PLATFORM",
"slug": "prometheus",
"sub_category_id": 2837,
"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": 1324,
"existing_alias_text": "Datadog",
"input_term": "Datadog",
"matched_canonical": {
"category_id": 9,
"display_name": "Datadog",
"id": 779,
"is_also_category": false,
"is_extractable": true,
"skill_nature": "PLATFORM",
"slug": "datadog",
"sub_category_id": 176,
"typical_lifespan": "EVERGREEN",
"volatility": "STABLE"
},
"matched_via": "alias"
},
{
"alias_persist_skipped_reason": "alias_text already exists for this canonical skill",
"alias_persisted": false,
"existing_alias_id": 868,
"existing_alias_text": "Agile",
"input_term": "Agile",
"matched_canonical": {
"category_id": 8,
"display_name": "Agile",
"id": 520,
"is_also_category": false,
"is_extractable": true,
"skill_nature": "METHODOLOGY",
"slug": "agile",
"sub_category_id": 3594,
"typical_lifespan": "EVERGREEN",
"volatility": "STABLE"
},
"matched_via": "alias"
}
],
"candidate_roles": [
{
"display_name": ".NET Backend Developer",
"id": 83,
"rationale": null,
"role_archetype": "Engineering",
"slug": "dotnet-backend-developer",
"source": "db"
},
{
"display_name": "Backend Developer",
"id": 1,
"rationale": null,
"role_archetype": "A Backend Engineer designs, builds, and maintains the server-side logic and data handling that power applications and services. They focus on implementing reliable business functionality, integrating with other systems, and ensuring the backend is scalable, maintainable, and observable.",
"slug": "backend-engineer",
"source": "db"
},
{
"display_name": "Cyber Security Engineer",
"id": 5,
"rationale": null,
"role_archetype": null,
"slug": "cybersecurity-engineer",
"source": "db"
},
{
"display_name": "Data Engineer",
"id": 2,
"rationale": null,
"role_archetype": null,
"slug": "data-engineer",
"source": "db"
},
{
"display_name": "DevOps Engineer",
"id": 10,
"rationale": null,
"role_archetype": null,
"slug": "devops-engineer",
"source": "db"
},
{
"display_name": "Fullstack Developer",
"id": 15,
"rationale": null,
"role_archetype": null,
"slug": "full-stack-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": "Kotlin Backend Developer",
"id": 84,
"rationale": null,
"role_archetype": "Engineering",
"slug": "kotlin-server-backend-developer",
"source": "db"
},
{
"display_name": "ML Engineer",
"id": 3,
"rationale": null,
"role_archetype": null,
"slug": "ml-engineer",
"source": "db"
},
{
"display_name": "MLOps Engineer",
"id": 16,
"rationale": null,
"role_archetype": null,
"slug": "ml-ops-engineer",
"source": "db"
},
{
"display_name": "Node.js Backend Developer",
"id": 82,
"rationale": null,
"role_archetype": "Engineering",
"slug": "node-backend-developer",
"source": "db"
},
{
"display_name": "Python Backend Developer",
"id": 80,
"rationale": null,
"role_archetype": "Engineering",
"slug": "python-backend-developer",
"source": "db"
},
{
"display_name": "Scala Backend Developer",
"id": 87,
"rationale": null,
"role_archetype": "Engineering",
"slug": "scala-backend-developer",
"source": "db"
},
{
"display_name": "AI Engineer",
"id": 13,
"rationale": null,
"role_archetype": null,
"slug": "ai-engineer",
"source": "db"
},
{
"display_name": "Cloud Architect",
"id": 9,
"rationale": null,
"role_archetype": null,
"slug": "cloud-architect",
"source": "db"
},
{
"display_name": "Cloud Security Engineer",
"id": 23,
"rationale": null,
"role_archetype": null,
"slug": "cloud-security-engineer",
"source": "db"
},
{
"display_name": "Engineering Manager",
"id": 121,
"rationale": null,
"role_archetype": null,
"slug": "engineering-manager",
"source": "db"
},
{
"display_name": "Fullstack Developer",
"id": 435,
"rationale": null,
"role_archetype": "Engineering",
"slug": "fullstack-developer",
"source": "db"
},
{
"display_name": "PHP Backend Developer",
"id": 86,
"rationale": null,
"role_archetype": "Engineering",
"slug": "php-backend-developer",
"source": "db"
},
{
"display_name": "Ruby Backend Developer",
"id": 85,
"rationale": null,
"role_archetype": "Engineering",
"slug": "ruby-backend-developer",
"source": "db"
}
],
"chosen_role": {
"display_name": "Platform Engineer",
"id": 133,
"rationale": "Domain=DevOps \u0026 Platform \u2192 sub-role infrastructure-platform-engineer; The JD centers on internal service platform, developer experience, automation, and large-scale cloud infrastructure, which best matches Platform Engineer over narrower Kubernetes, IaC, or pure SRE roles.",
"role_archetype": null,
"slug": "platform-engineer",
"source": "db"
},
"dimensions": [
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Cloud Platforms",
"id": 20,
"rationale": "Underlying cloud providers that host the managed services or infrastructure used by the role, such as AWS, Azure, and GCP.",
"slug": "cloud-platforms",
"source": "db"
},
"input_skill": "AWS",
"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": "Cyber Security Engineer",
"id": 5,
"rationale": null,
"role_archetype": null,
"slug": "cybersecurity-engineer",
"source": "db"
},
{
"display_name": "Data Engineer",
"id": 2,
"rationale": null,
"role_archetype": null,
"slug": "data-engineer",
"source": "db"
},
{
"display_name": "DevOps Engineer",
"id": 10,
"rationale": null,
"role_archetype": null,
"slug": "devops-engineer",
"source": "db"
},
{
"display_name": "Fullstack Developer",
"id": 15,
"rationale": null,
"role_archetype": null,
"slug": "full-stack-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": "Kotlin Backend Developer",
"id": 84,
"rationale": null,
"role_archetype": "Engineering",
"slug": "kotlin-server-backend-developer",
"source": "db"
},
{
"display_name": "ML Engineer",
"id": 3,
"rationale": null,
"role_archetype": null,
"slug": "ml-engineer",
"source": "db"
},
{
"display_name": "MLOps Engineer",
"id": 16,
"rationale": null,
"role_archetype": null,
"slug": "ml-ops-engineer",
"source": "db"
},
{
"display_name": "Node.js Backend Developer",
"id": 82,
"rationale": null,
"role_archetype": "Engineering",
"slug": "node-backend-developer",
"source": "db"
},
{
"display_name": "Python Backend Developer",
"id": 80,
"rationale": null,
"role_archetype": "Engineering",
"slug": "python-backend-developer",
"source": "db"
},
{
"display_name": "Scala Backend Developer",
"id": 87,
"rationale": null,
"role_archetype": "Engineering",
"slug": "scala-backend-developer",
"source": "db"
}
]
},
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Cloud Platforms for AI Deployment",
"id": 211,
"rationale": "Major cloud services that provide infrastructure and managed services for AI workloads.",
"slug": "cloud-platforms-for-ai-deployment",
"source": "db"
},
"input_skill": "AWS",
"llm_role": null,
"roles_from_db": [
{
"display_name": "AI Engineer",
"id": 13,
"rationale": null,
"role_archetype": null,
"slug": "ai-engineer",
"source": "db"
}
]
},
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Cloud Provider Platforms",
"id": 131,
"rationale": "Major cloud platforms and their core service ecosystems used to design target-state architectures, choose deployment boundaries, and evaluate managed capabilities. This is the primary substrate for cloud architecture decisions.",
"slug": "cloud-provider-platforms",
"source": "db"
},
"input_skill": "AWS",
"llm_role": null,
"roles_from_db": [
{
"display_name": "Cloud Architect",
"id": 9,
"rationale": null,
"role_archetype": null,
"slug": "cloud-architect",
"source": "db"
},
{
"display_name": "Cloud Security Engineer",
"id": 23,
"rationale": null,
"role_archetype": null,
"slug": "cloud-security-engineer",
"source": "db"
}
]
},
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Cloud Security Posture Tools",
"id": 64,
"rationale": "Cloud-native security platforms used to assess misconfiguration, workload exposure, and cloud control coverage. This dimension includes the major CNAPP/CSPM/CWPP vendors and cloud security services the role reviews and tunes.",
"slug": "cloud-security-posture-tools",
"source": "db"
},
"input_skill": "AWS",
"llm_role": null,
"roles_from_db": [
{
"display_name": "Cloud Security Engineer",
"id": 23,
"rationale": null,
"role_archetype": null,
"slug": "cloud-security-engineer",
"source": "db"
},
{
"display_name": "Cyber Security Engineer",
"id": 5,
"rationale": null,
"role_archetype": null,
"slug": "cybersecurity-engineer",
"source": "db"
}
]
},
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Vendor Product Families",
"id": 477,
"rationale": "Coordinate usage, licensing, and architecture decisions for major vendor software and cloud product families.",
"slug": "vendor-product-families",
"source": "db"
},
"input_skill": "AWS",
"llm_role": null,
"roles_from_db": [
{
"display_name": "Engineering Manager",
"id": 121,
"rationale": null,
"role_archetype": null,
"slug": "engineering-manager",
"source": "db"
}
]
},
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Container Orchestration Platforms",
"id": 134,
"rationale": "Platforms that schedule and manage containerized workloads across clusters and environments. Cloud Architects need these to define workload placement standards, cluster boundaries, and platform capabilities.",
"slug": "container-orchestration-platforms",
"source": "db"
},
"input_skill": "Kubernetes",
"llm_role": null,
"roles_from_db": [
{
"display_name": "Cloud Architect",
"id": 9,
"rationale": null,
"role_archetype": null,
"slug": "cloud-architect",
"source": "db"
},
{
"display_name": "DevOps Engineer",
"id": 10,
"rationale": null,
"role_archetype": null,
"slug": "devops-engineer",
"source": "db"
}
]
},
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Kubernetes for ML Workloads",
"id": 47,
"rationale": "Kubernetes-native components used to schedule, accelerate, and isolate ML training and serving workloads. This includes GPU enablement and ML-specific controllers rather than generic cluster administration.",
"slug": "kubernetes-for-ml-workloads",
"source": "db"
},
"input_skill": "Kubernetes",
"llm_role": null,
"roles_from_db": [
{
"display_name": "ML Engineer",
"id": 3,
"rationale": null,
"role_archetype": null,
"slug": "ml-engineer",
"source": "db"
},
{
"display_name": "MLOps Engineer",
"id": 16,
"rationale": null,
"role_archetype": null,
"slug": "ml-ops-engineer",
"source": "db"
}
]
},
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Infrastructure \u0026 Security Automation Frameworks",
"id": 249,
"rationale": "Frameworks and libraries for provisioning, configuring, and automating cloud security infrastructure.",
"slug": "infrastructure-security-automation-frameworks",
"source": "db"
},
"input_skill": "Terraform",
"llm_role": null,
"roles_from_db": [
{
"display_name": "Cloud Security Engineer",
"id": 23,
"rationale": null,
"role_archetype": null,
"slug": "cloud-security-engineer",
"source": "db"
}
]
},
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Infrastructure as Code",
"id": 132,
"rationale": "Declarative provisioning and environment definition tools used to codify cloud infrastructure, repeatable environments, and platform standards. Cloud Architects use these to express reference architectures and guardrails.",
"slug": "infrastructure-as-code",
"source": "db"
},
"input_skill": "Terraform",
"llm_role": null,
"roles_from_db": [
{
"display_name": "Cloud Architect",
"id": 9,
"rationale": null,
"role_archetype": null,
"slug": "cloud-architect",
"source": "db"
},
{
"display_name": "DevOps Engineer",
"id": 10,
"rationale": null,
"role_archetype": null,
"slug": "devops-engineer",
"source": "db"
}
]
},
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Infrastructure as Code for ML",
"id": 57,
"rationale": "Tools for provisioning and managing ML infrastructure resources through code.",
"slug": "infrastructure-as-code-for-ml",
"source": "db"
},
"input_skill": "Terraform",
"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": "Cloud Security Scripting \u0026 DSL Languages",
"id": 248,
"rationale": "Proficiency in programming and domain-specific languages used to automate and script cloud security controls.",
"slug": "cloud-security-scripting-dsl-languages",
"source": "db"
},
"input_skill": "Go",
"llm_role": null,
"roles_from_db": [
{
"display_name": "Cloud Security Engineer",
"id": 23,
"rationale": null,
"role_archetype": null,
"slug": "cloud-security-engineer",
"source": "db"
}
]
},
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Go Language and Toolchain",
"id": 367,
"rationale": "Core Go implementation skills used to build backend service logic, handlers, and internal libraries. This is the primary coding surface for the role and includes language features, module management, and compiler/runtime behavior relevant to service code.",
"slug": "go-language-and-toolchain",
"source": "db"
},
"input_skill": "Go",
"llm_role": null,
"roles_from_db": [
{
"display_name": "Go Backend Developer",
"id": 81,
"rationale": null,
"role_archetype": "Engineering",
"slug": "go-backend-developer",
"source": "db"
}
]
},
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Programming Languages",
"id": 1,
"rationale": "Primary implementation languages used to build client and server feature code. Full stack engineers need enough fluency to move across layers and implement product behavior end to end.",
"slug": "programming-languages",
"source": "db"
},
"input_skill": "Go",
"llm_role": null,
"roles_from_db": [
{
"display_name": "Backend Developer",
"id": 1,
"rationale": null,
"role_archetype": "A Backend Engineer designs, builds, and maintains the server-side logic and data handling that power applications and services. They focus on implementing reliable business functionality, integrating with other systems, and ensuring the backend is scalable, maintainable, and observable.",
"slug": "backend-engineer",
"source": "db"
},
{
"display_name": "Fullstack Developer",
"id": 15,
"rationale": null,
"role_archetype": null,
"slug": "full-stack-engineer",
"source": "db"
},
{
"display_name": "Fullstack Developer",
"id": 435,
"rationale": null,
"role_archetype": "Engineering",
"slug": "fullstack-developer",
"source": "db"
}
]
},
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Programming Languages and Scripting",
"id": 59,
"rationale": "Languages used to write security automation, analysis scripts, detection logic, and remediation helpers. This is the primary implementation surface for a cybersecurity engineer across tooling and response workflows.",
"slug": "programming-languages-and-scripting",
"source": "db"
},
"input_skill": "Go",
"llm_role": null,
"roles_from_db": [
{
"display_name": "Cyber Security Engineer",
"id": 5,
"rationale": null,
"role_archetype": null,
"slug": "cybersecurity-engineer",
"source": "db"
}
]
},
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Programming Languages for ML Systems",
"id": 39,
"rationale": "Languages used to build training code, inference services, evaluation jobs, and ML glue code. This is the primary implementation surface for ML engineers across experimentation and productionization.",
"slug": "programming-languages-for-ml-systems",
"source": "db"
},
"input_skill": "Go",
"llm_role": null,
"roles_from_db": [
{
"display_name": "ML Engineer",
"id": 3,
"rationale": null,
"role_archetype": null,
"slug": "ml-engineer",
"source": "db"
},
{
"display_name": "MLOps Engineer",
"id": 16,
"rationale": null,
"role_archetype": null,
"slug": "ml-ops-engineer",
"source": "db"
}
]
},
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Asynchronous Messaging and Event Streaming",
"id": 297,
"rationale": "Asynchronous communication patterns and broker technologies used to decouple backend services and move work off the request path. Includes queues, pub/sub, event streams, consumer groups, dead-letter queues, and delivery semantics across systems such as Kafka, RabbitMQ, NATS, SQS/SNS, Pulsar, and ActiveMQ.",
"slug": "asynchronous-messaging-and-event-streaming",
"source": "db"
},
"input_skill": "Kafka",
"llm_role": null,
"roles_from_db": [
{
"display_name": ".NET Backend Developer",
"id": 83,
"rationale": null,
"role_archetype": "Engineering",
"slug": "dotnet-backend-developer",
"source": "db"
},
{
"display_name": "Go Backend Developer",
"id": 81,
"rationale": null,
"role_archetype": "Engineering",
"slug": "go-backend-developer",
"source": "db"
},
{
"display_name": "Kotlin Backend Developer",
"id": 84,
"rationale": null,
"role_archetype": "Engineering",
"slug": "kotlin-server-backend-developer",
"source": "db"
},
{
"display_name": "Node.js Backend Developer",
"id": 82,
"rationale": null,
"role_archetype": "Engineering",
"slug": "node-backend-developer",
"source": "db"
},
{
"display_name": "Scala Backend Developer",
"id": 87,
"rationale": null,
"role_archetype": "Engineering",
"slug": "scala-backend-developer",
"source": "db"
}
]
},
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Messaging and Background Jobs",
"id": 291,
"rationale": "Asynchronous processing patterns and worker systems used to decouple backend work from request handling. This is a coherent cluster because the role supports background jobs, retries, and deferred processing.",
"slug": "messaging-and-background-jobs",
"source": "db"
},
"input_skill": "Kafka",
"llm_role": null,
"roles_from_db": [
{
"display_name": "PHP Backend Developer",
"id": 86,
"rationale": null,
"role_archetype": "Engineering",
"slug": "php-backend-developer",
"source": "db"
},
{
"display_name": "Python Backend Developer",
"id": 80,
"rationale": null,
"role_archetype": "Engineering",
"slug": "python-backend-developer",
"source": "db"
},
{
"display_name": "Ruby Backend Developer",
"id": 85,
"rationale": null,
"role_archetype": "Engineering",
"slug": "ruby-backend-developer",
"source": "db"
}
]
},
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Messaging and Event Streaming",
"id": 8,
"rationale": "Transport-layer systems used to move events and decouple producers from consumers. Data engineers use these systems to ingest, buffer, and distribute event data before downstream processing.",
"slug": "messaging-and-event-streaming",
"source": "db"
},
"input_skill": "Kafka",
"llm_role": null,
"roles_from_db": [
{
"display_name": "Backend Developer",
"id": 1,
"rationale": null,
"role_archetype": "A Backend Engineer designs, builds, and maintains the server-side logic and data handling that power applications and services. They focus on implementing reliable business functionality, integrating with other systems, and ensuring the backend is scalable, maintainable, and observable.",
"slug": "backend-engineer",
"source": "db"
},
{
"display_name": "Data Engineer",
"id": 2,
"rationale": null,
"role_archetype": null,
"slug": "data-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": "Argo 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": "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": "Buildkite",
"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": "Grafana",
"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": "Grafana",
"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": "Grafana",
"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 Operations",
"id": 143,
"rationale": "Monitoring, logging, tracing, and operational readiness patterns used to keep cloud platforms supportable. Cloud Architects use this to define what telemetry and operational controls workloads must expose.",
"slug": "observability-and-operations",
"source": "db"
},
"input_skill": "Grafana",
"llm_role": null,
"roles_from_db": [
{
"display_name": "Cloud Architect",
"id": 9,
"rationale": null,
"role_archetype": null,
"slug": "cloud-architect",
"source": "db"
}
]
},
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "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": "Prometheus",
"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": "Prometheus",
"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": "Prometheus",
"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 Operations",
"id": 143,
"rationale": "Monitoring, logging, tracing, and operational readiness patterns used to keep cloud platforms supportable. Cloud Architects use this to define what telemetry and operational controls workloads must expose.",
"slug": "observability-and-operations",
"source": "db"
},
"input_skill": "Prometheus",
"llm_role": null,
"roles_from_db": [
{
"display_name": "Cloud Architect",
"id": 9,
"rationale": null,
"role_archetype": null,
"slug": "cloud-architect",
"source": "db"
}
]
},
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "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": "Datadog",
"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 Operations",
"id": 143,
"rationale": "Monitoring, logging, tracing, and operational readiness patterns used to keep cloud platforms supportable. Cloud Architects use this to define what telemetry and operational controls workloads must expose.",
"slug": "observability-and-operations",
"source": "db"
},
"input_skill": "Datadog",
"llm_role": null,
"roles_from_db": [
{
"display_name": "Cloud Architect",
"id": 9,
"rationale": null,
"role_archetype": null,
"slug": "cloud-architect",
"source": "db"
}
]
},
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "React Frontend Development",
"id": 96,
"rationale": "Building interactive web user interfaces with React.js, including component composition, state management, hooks, and rendering patterns. React.js belongs here because it is a core library for client-side UI development in modern web applications.",
"slug": "d_init_01",
"source": "db"
},
"input_skill": "Agile",
"llm_role": null,
"roles_from_db": []
},
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Software Concepts, Patterns \u0026 Practices",
"id": 478,
"rationale": "Champion foundational software design patterns, development methodologies, and engineering best practices.",
"slug": "software-concepts-patterns-practices",
"source": "db"
},
"input_skill": "Agile",
"llm_role": null,
"roles_from_db": [
{
"display_name": "Engineering Manager",
"id": 121,
"rationale": null,
"role_archetype": null,
"slug": "engineering-manager",
"source": "db"
}
]
}
],
"input_final_skills": [
"AWS",
"Kubernetes",
"Terraform",
"Go",
"Kafka",
"Argo CD",
"Buildkite",
"Grafana",
"Prometheus",
"Datadog",
"Loki",
"Agile"
],
"input_llm_skills": [
"AWS",
"Kubernetes",
"Terraform",
"Go",
"Kafka",
"Argo CD",
"Buildkite",
"Grafana",
"Prometheus",
"Datadog",
"Loki",
"Agile"
],
"new_aliases_persisted": 0,
"run_id": "23c596d1-8698-43f6-a9e0-9e4258417dec",
"skills_detail": [
{
"aliases_in_db": [
{
"alias_text": "AWS",
"alias_type": "CANONICAL",
"id": 406,
"is_primary": true,
"match_strategy": "CASE_INSENSITIVE"
}
],
"canonical": {
"category_id": 9,
"display_name": "AWS",
"id": 187,
"is_also_category": false,
"is_extractable": true,
"skill_nature": "PLATFORM",
"slug": "aws",
"sub_category_id": 46,
"typical_lifespan": "EVERGREEN",
"volatility": "STABLE"
},
"dimensions": [
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Cloud Platforms",
"id": 20,
"rationale": "Underlying cloud providers that host the managed services or infrastructure used by the role, such as AWS, Azure, and GCP.",
"slug": "cloud-platforms",
"source": "db"
},
"input_skill": "AWS",
"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": "Cyber Security Engineer",
"id": 5,
"rationale": null,
"role_archetype": null,
"slug": "cybersecurity-engineer",
"source": "db"
},
{
"display_name": "Data Engineer",
"id": 2,
"rationale": null,
"role_archetype": null,
"slug": "data-engineer",
"source": "db"
},
{
"display_name": "DevOps Engineer",
"id": 10,
"rationale": null,
"role_archetype": null,
"slug": "devops-engineer",
"source": "db"
},
{
"display_name": "Fullstack Developer",
"id": 15,
"rationale": null,
"role_archetype": null,
"slug": "full-stack-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": "Kotlin Backend Developer",
"id": 84,
"rationale": null,
"role_archetype": "Engineering",
"slug": "kotlin-server-backend-developer",
"source": "db"
},
{
"display_name": "ML Engineer",
"id": 3,
"rationale": null,
"role_archetype": null,
"slug": "ml-engineer",
"source": "db"
},
{
"display_name": "MLOps Engineer",
"id": 16,
"rationale": null,
"role_archetype": null,
"slug": "ml-ops-engineer",
"source": "db"
},
{
"display_name": "Node.js Backend Developer",
"id": 82,
"rationale": null,
"role_archetype": "Engineering",
"slug": "node-backend-developer",
"source": "db"
},
{
"display_name": "Python Backend Developer",
"id": 80,
"rationale": null,
"role_archetype": "Engineering",
"slug": "python-backend-developer",
"source": "db"
},
{
"display_name": "Scala Backend Developer",
"id": 87,
"rationale": null,
"role_archetype": "Engineering",
"slug": "scala-backend-developer",
"source": "db"
}
]
},
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Cloud Platforms for AI Deployment",
"id": 211,
"rationale": "Major cloud services that provide infrastructure and managed services for AI workloads.",
"slug": "cloud-platforms-for-ai-deployment",
"source": "db"
},
"input_skill": "AWS",
"llm_role": null,
"roles_from_db": [
{
"display_name": "AI Engineer",
"id": 13,
"rationale": null,
"role_archetype": null,
"slug": "ai-engineer",
"source": "db"
}
]
},
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Cloud Provider Platforms",
"id": 131,
"rationale": "Major cloud platforms and their core service ecosystems used to design target-state architectures, choose deployment boundaries, and evaluate managed capabilities. This is the primary substrate for cloud architecture decisions.",
"slug": "cloud-provider-platforms",
"source": "db"
},
"input_skill": "AWS",
"llm_role": null,
"roles_from_db": [
{
"display_name": "Cloud Architect",
"id": 9,
"rationale": null,
"role_archetype": null,
"slug": "cloud-architect",
"source": "db"
},
{
"display_name": "Cloud Security Engineer",
"id": 23,
"rationale": null,
"role_archetype": null,
"slug": "cloud-security-engineer",
"source": "db"
}
]
},
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Cloud Security Posture Tools",
"id": 64,
"rationale": "Cloud-native security platforms used to assess misconfiguration, workload exposure, and cloud control coverage. This dimension includes the major CNAPP/CSPM/CWPP vendors and cloud security services the role reviews and tunes.",
"slug": "cloud-security-posture-tools",
"source": "db"
},
"input_skill": "AWS",
"llm_role": null,
"roles_from_db": [
{
"display_name": "Cloud Security Engineer",
"id": 23,
"rationale": null,
"role_archetype": null,
"slug": "cloud-security-engineer",
"source": "db"
},
{
"display_name": "Cyber Security Engineer",
"id": 5,
"rationale": null,
"role_archetype": null,
"slug": "cybersecurity-engineer",
"source": "db"
}
]
},
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Vendor Product Families",
"id": 477,
"rationale": "Coordinate usage, licensing, and architecture decisions for major vendor software and cloud product families.",
"slug": "vendor-product-families",
"source": "db"
},
"input_skill": "AWS",
"llm_role": null,
"roles_from_db": [
{
"display_name": "Engineering Manager",
"id": 121,
"rationale": null,
"role_archetype": null,
"slug": "engineering-manager",
"source": "db"
}
]
}
],
"input_skill": "AWS",
"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": "Kubernetes",
"alias_type": "CANONICAL",
"id": 1267,
"is_primary": true,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "Kubernetes 1.0+",
"alias_type": "VERSION",
"id": 1271,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "Kubernetes 1.x",
"alias_type": "VERSION",
"id": 1270,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "Kubernetes v1",
"alias_type": "VERSION",
"id": 1269,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "k8s",
"alias_type": "VERSION",
"id": 1268,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "kubernetes 1.x",
"alias_type": "VERSION",
"id": 1400,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "kubernetes latest",
"alias_type": "VERSION",
"id": 1401,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
}
],
"canonical": {
"category_id": 9,
"display_name": "Kubernetes",
"id": 726,
"is_also_category": false,
"is_extractable": true,
"skill_nature": "PLATFORM",
"slug": "kubernetes",
"sub_category_id": 557,
"typical_lifespan": "EVERGREEN",
"volatility": "STABLE"
},
"dimensions": [
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Container Orchestration Platforms",
"id": 134,
"rationale": "Platforms that schedule and manage containerized workloads across clusters and environments. Cloud Architects need these to define workload placement standards, cluster boundaries, and platform capabilities.",
"slug": "container-orchestration-platforms",
"source": "db"
},
"input_skill": "Kubernetes",
"llm_role": null,
"roles_from_db": [
{
"display_name": "Cloud Architect",
"id": 9,
"rationale": null,
"role_archetype": null,
"slug": "cloud-architect",
"source": "db"
},
{
"display_name": "DevOps Engineer",
"id": 10,
"rationale": null,
"role_archetype": null,
"slug": "devops-engineer",
"source": "db"
}
]
},
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Kubernetes for ML Workloads",
"id": 47,
"rationale": "Kubernetes-native components used to schedule, accelerate, and isolate ML training and serving workloads. This includes GPU enablement and ML-specific controllers rather than generic cluster administration.",
"slug": "kubernetes-for-ml-workloads",
"source": "db"
},
"input_skill": "Kubernetes",
"llm_role": null,
"roles_from_db": [
{
"display_name": "ML Engineer",
"id": 3,
"rationale": null,
"role_archetype": null,
"slug": "ml-engineer",
"source": "db"
},
{
"display_name": "MLOps Engineer",
"id": 16,
"rationale": null,
"role_archetype": null,
"slug": "ml-ops-engineer",
"source": "db"
}
]
}
],
"input_skill": "Kubernetes",
"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": "Terraform",
"alias_type": "CANONICAL",
"id": 547,
"is_primary": true,
"match_strategy": "CASE_INSENSITIVE"
}
],
"canonical": {
"category_id": 13,
"display_name": "Terraform",
"id": 286,
"is_also_category": false,
"is_extractable": true,
"skill_nature": "TOOL",
"slug": "terraform",
"sub_category_id": 191,
"typical_lifespan": "EVERGREEN",
"volatility": "STABLE"
},
"dimensions": [
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Infrastructure \u0026 Security Automation Frameworks",
"id": 249,
"rationale": "Frameworks and libraries for provisioning, configuring, and automating cloud security infrastructure.",
"slug": "infrastructure-security-automation-frameworks",
"source": "db"
},
"input_skill": "Terraform",
"llm_role": null,
"roles_from_db": [
{
"display_name": "Cloud Security Engineer",
"id": 23,
"rationale": null,
"role_archetype": null,
"slug": "cloud-security-engineer",
"source": "db"
}
]
},
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Infrastructure as Code",
"id": 132,
"rationale": "Declarative provisioning and environment definition tools used to codify cloud infrastructure, repeatable environments, and platform standards. Cloud Architects use these to express reference architectures and guardrails.",
"slug": "infrastructure-as-code",
"source": "db"
},
"input_skill": "Terraform",
"llm_role": null,
"roles_from_db": [
{
"display_name": "Cloud Architect",
"id": 9,
"rationale": null,
"role_archetype": null,
"slug": "cloud-architect",
"source": "db"
},
{
"display_name": "DevOps Engineer",
"id": 10,
"rationale": null,
"role_archetype": null,
"slug": "devops-engineer",
"source": "db"
}
]
},
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Infrastructure as Code for ML",
"id": 57,
"rationale": "Tools for provisioning and managing ML infrastructure resources through code.",
"slug": "infrastructure-as-code-for-ml",
"source": "db"
},
"input_skill": "Terraform",
"llm_role": null,
"roles_from_db": [
{
"display_name": "ML Engineer",
"id": 3,
"rationale": null,
"role_archetype": null,
"slug": "ml-engineer",
"source": "db"
}
]
}
],
"input_skill": "Terraform",
"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": "Go",
"alias_type": "CANONICAL",
"id": 25,
"is_primary": true,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "Go 1.0",
"alias_type": "VERSION",
"id": 27,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "Go 1.1",
"alias_type": "VERSION",
"id": 28,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "Go 1.10",
"alias_type": "VERSION",
"id": 39,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "Go 1.11",
"alias_type": "VERSION",
"id": 40,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "Go 1.12",
"alias_type": "VERSION",
"id": 41,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "Go 1.13",
"alias_type": "VERSION",
"id": 42,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "Go 1.14",
"alias_type": "VERSION",
"id": 43,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "Go 1.15",
"alias_type": "VERSION",
"id": 44,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "Go 1.16",
"alias_type": "VERSION",
"id": 45,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "Go 1.17",
"alias_type": "VERSION",
"id": 46,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "Go 1.18",
"alias_type": "VERSION",
"id": 47,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "Go 1.19",
"alias_type": "VERSION",
"id": 48,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "Go 1.2",
"alias_type": "VERSION",
"id": 29,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "Go 1.20",
"alias_type": "VERSION",
"id": 49,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "Go 1.21",
"alias_type": "VERSION",
"id": 50,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "Go 1.22",
"alias_type": "VERSION",
"id": 51,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "Go 1.3",
"alias_type": "VERSION",
"id": 30,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "Go 1.4",
"alias_type": "VERSION",
"id": 31,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "Go 1.5",
"alias_type": "VERSION",
"id": 32,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "Go 1.6",
"alias_type": "VERSION",
"id": 33,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "Go 1.7",
"alias_type": "VERSION",
"id": 34,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "Go 1.8",
"alias_type": "VERSION",
"id": 35,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "Go 1.9",
"alias_type": "VERSION",
"id": 36,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "Go 1.x",
"alias_type": "VERSION",
"id": 37,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "Golang",
"alias_type": "VERSION",
"id": 38,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "go 1.18",
"alias_type": "VERSION",
"id": 2858,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "go 1.19",
"alias_type": "VERSION",
"id": 2859,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "go 1.20",
"alias_type": "VERSION",
"id": 2860,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "go 1.21",
"alias_type": "VERSION",
"id": 2861,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "go 1.22",
"alias_type": "VERSION",
"id": 2407,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "go latest",
"alias_type": "VERSION",
"id": 2408,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "go1.18",
"alias_type": "VERSION",
"id": 2852,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "go1.19",
"alias_type": "VERSION",
"id": 2853,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "go1.20",
"alias_type": "VERSION",
"id": 2854,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "go1.21",
"alias_type": "VERSION",
"id": 2855,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "go1.22",
"alias_type": "VERSION",
"id": 2405,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "go1.x",
"alias_type": "VERSION",
"id": 2404,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "golang",
"alias_type": "VERSION",
"id": 2406,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
}
],
"canonical": {
"category_id": 6,
"display_name": "Go",
"id": 3,
"is_also_category": false,
"is_extractable": true,
"skill_nature": "LANGUAGE",
"slug": "go",
"sub_category_id": 96,
"typical_lifespan": "EVERGREEN",
"volatility": "STABLE"
},
"dimensions": [
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Cloud Security Scripting \u0026 DSL Languages",
"id": 248,
"rationale": "Proficiency in programming and domain-specific languages used to automate and script cloud security controls.",
"slug": "cloud-security-scripting-dsl-languages",
"source": "db"
},
"input_skill": "Go",
"llm_role": null,
"roles_from_db": [
{
"display_name": "Cloud Security Engineer",
"id": 23,
"rationale": null,
"role_archetype": null,
"slug": "cloud-security-engineer",
"source": "db"
}
]
},
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Go Language and Toolchain",
"id": 367,
"rationale": "Core Go implementation skills used to build backend service logic, handlers, and internal libraries. This is the primary coding surface for the role and includes language features, module management, and compiler/runtime behavior relevant to service code.",
"slug": "go-language-and-toolchain",
"source": "db"
},
"input_skill": "Go",
"llm_role": null,
"roles_from_db": [
{
"display_name": "Go Backend Developer",
"id": 81,
"rationale": null,
"role_archetype": "Engineering",
"slug": "go-backend-developer",
"source": "db"
}
]
},
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Programming Languages",
"id": 1,
"rationale": "Primary implementation languages used to build client and server feature code. Full stack engineers need enough fluency to move across layers and implement product behavior end to end.",
"slug": "programming-languages",
"source": "db"
},
"input_skill": "Go",
"llm_role": null,
"roles_from_db": [
{
"display_name": "Backend Developer",
"id": 1,
"rationale": null,
"role_archetype": "A Backend Engineer designs, builds, and maintains the server-side logic and data handling that power applications and services. They focus on implementing reliable business functionality, integrating with other systems, and ensuring the backend is scalable, maintainable, and observable.",
"slug": "backend-engineer",
"source": "db"
},
{
"display_name": "Fullstack Developer",
"id": 15,
"rationale": null,
"role_archetype": null,
"slug": "full-stack-engineer",
"source": "db"
},
{
"display_name": "Fullstack Developer",
"id": 435,
"rationale": null,
"role_archetype": "Engineering",
"slug": "fullstack-developer",
"source": "db"
}
]
},
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Programming Languages and Scripting",
"id": 59,
"rationale": "Languages used to write security automation, analysis scripts, detection logic, and remediation helpers. This is the primary implementation surface for a cybersecurity engineer across tooling and response workflows.",
"slug": "programming-languages-and-scripting",
"source": "db"
},
"input_skill": "Go",
"llm_role": null,
"roles_from_db": [
{
"display_name": "Cyber Security Engineer",
"id": 5,
"rationale": null,
"role_archetype": null,
"slug": "cybersecurity-engineer",
"source": "db"
}
]
},
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Programming Languages for ML Systems",
"id": 39,
"rationale": "Languages used to build training code, inference services, evaluation jobs, and ML glue code. This is the primary implementation surface for ML engineers across experimentation and productionization.",
"slug": "programming-languages-for-ml-systems",
"source": "db"
},
"input_skill": "Go",
"llm_role": null,
"roles_from_db": [
{
"display_name": "ML Engineer",
"id": 3,
"rationale": null,
"role_archetype": null,
"slug": "ml-engineer",
"source": "db"
},
{
"display_name": "MLOps Engineer",
"id": 16,
"rationale": null,
"role_archetype": null,
"slug": "ml-ops-engineer",
"source": "db"
}
]
}
],
"input_skill": "Go",
"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": "Kafka",
"alias_type": "CANONICAL",
"id": 173,
"is_primary": true,
"match_strategy": "CASE_INSENSITIVE"
}
],
"canonical": {
"category_id": 3,
"display_name": "Kafka",
"id": 36,
"is_also_category": false,
"is_extractable": true,
"skill_nature": "TOOL",
"slug": "kafka",
"sub_category_id": 3533,
"typical_lifespan": "EVERGREEN",
"volatility": "STABLE"
},
"dimensions": [
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Asynchronous Messaging and Event Streaming",
"id": 297,
"rationale": "Asynchronous communication patterns and broker technologies used to decouple backend services and move work off the request path. Includes queues, pub/sub, event streams, consumer groups, dead-letter queues, and delivery semantics across systems such as Kafka, RabbitMQ, NATS, SQS/SNS, Pulsar, and ActiveMQ.",
"slug": "asynchronous-messaging-and-event-streaming",
"source": "db"
},
"input_skill": "Kafka",
"llm_role": null,
"roles_from_db": [
{
"display_name": ".NET Backend Developer",
"id": 83,
"rationale": null,
"role_archetype": "Engineering",
"slug": "dotnet-backend-developer",
"source": "db"
},
{
"display_name": "Go Backend Developer",
"id": 81,
"rationale": null,
"role_archetype": "Engineering",
"slug": "go-backend-developer",
"source": "db"
},
{
"display_name": "Kotlin Backend Developer",
"id": 84,
"rationale": null,
"role_archetype": "Engineering",
"slug": "kotlin-server-backend-developer",
"source": "db"
},
{
"display_name": "Node.js Backend Developer",
"id": 82,
"rationale": null,
"role_archetype": "Engineering",
"slug": "node-backend-developer",
"source": "db"
},
{
"display_name": "Scala Backend Developer",
"id": 87,
"rationale": null,
"role_archetype": "Engineering",
"slug": "scala-backend-developer",
"source": "db"
}
]
},
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Messaging and Background Jobs",
"id": 291,
"rationale": "Asynchronous processing patterns and worker systems used to decouple backend work from request handling. This is a coherent cluster because the role supports background jobs, retries, and deferred processing.",
"slug": "messaging-and-background-jobs",
"source": "db"
},
"input_skill": "Kafka",
"llm_role": null,
"roles_from_db": [
{
"display_name": "PHP Backend Developer",
"id": 86,
"rationale": null,
"role_archetype": "Engineering",
"slug": "php-backend-developer",
"source": "db"
},
{
"display_name": "Python Backend Developer",
"id": 80,
"rationale": null,
"role_archetype": "Engineering",
"slug": "python-backend-developer",
"source": "db"
},
{
"display_name": "Ruby Backend Developer",
"id": 85,
"rationale": null,
"role_archetype": "Engineering",
"slug": "ruby-backend-developer",
"source": "db"
}
]
},
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Messaging and Event Streaming",
"id": 8,
"rationale": "Transport-layer systems used to move events and decouple producers from consumers. Data engineers use these systems to ingest, buffer, and distribute event data before downstream processing.",
"slug": "messaging-and-event-streaming",
"source": "db"
},
"input_skill": "Kafka",
"llm_role": null,
"roles_from_db": [
{
"display_name": "Backend Developer",
"id": 1,
"rationale": null,
"role_archetype": "A Backend Engineer designs, builds, and maintains the server-side logic and data handling that power applications and services. They focus on implementing reliable business functionality, integrating with other systems, and ensuring the backend is scalable, maintainable, and observable.",
"slug": "backend-engineer",
"source": "db"
},
{
"display_name": "Data Engineer",
"id": 2,
"rationale": null,
"role_archetype": null,
"slug": "data-engineer",
"source": "db"
}
]
}
],
"input_skill": "Kafka",
"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": "Argo CD",
"alias_type": "CANONICAL",
"id": 545,
"is_primary": true,
"match_strategy": "CASE_INSENSITIVE"
}
],
"canonical": {
"category_id": 13,
"display_name": "Argo CD",
"id": 284,
"is_also_category": false,
"is_extractable": true,
"skill_nature": "TOOL",
"slug": "argo-cd",
"sub_category_id": 189,
"typical_lifespan": "EVERGREEN",
"volatility": "STABLE"
},
"dimensions": [
{
"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": "Argo 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": "Argo 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": [
{
"alias_text": "Buildkite",
"alias_type": "CANONICAL",
"id": 1372,
"is_primary": true,
"match_strategy": "CASE_INSENSITIVE"
}
],
"canonical": {
"category_id": 9,
"display_name": "Buildkite",
"id": 827,
"is_also_category": false,
"is_extractable": true,
"skill_nature": "PLATFORM",
"slug": "buildkite",
"sub_category_id": 632,
"typical_lifespan": "EVERGREEN",
"volatility": "EMERGING"
},
"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": "Buildkite",
"llm_role": null,
"roles_from_db": [
{
"display_name": "DevOps Engineer",
"id": 10,
"rationale": null,
"role_archetype": null,
"slug": "devops-engineer",
"source": "db"
}
]
}
],
"input_skill": "Buildkite",
"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": "Grafana",
"alias_type": "CANONICAL",
"id": 184,
"is_primary": true,
"match_strategy": "CASE_INSENSITIVE"
}
],
"canonical": {
"category_id": 9,
"display_name": "Grafana",
"id": 47,
"is_also_category": false,
"is_extractable": true,
"skill_nature": "PLATFORM",
"slug": "grafana",
"sub_category_id": 176,
"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": "Grafana",
"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": "Grafana",
"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": "Grafana",
"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 Operations",
"id": 143,
"rationale": "Monitoring, logging, tracing, and operational readiness patterns used to keep cloud platforms supportable. Cloud Architects use this to define what telemetry and operational controls workloads must expose.",
"slug": "observability-and-operations",
"source": "db"
},
"input_skill": "Grafana",
"llm_role": null,
"roles_from_db": [
{
"display_name": "Cloud Architect",
"id": 9,
"rationale": null,
"role_archetype": null,
"slug": "cloud-architect",
"source": "db"
}
]
}
],
"input_skill": "Grafana",
"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": "Prometheus",
"alias_type": "CANONICAL",
"id": 183,
"is_primary": true,
"match_strategy": "CASE_INSENSITIVE"
}
],
"canonical": {
"category_id": 9,
"display_name": "Prometheus",
"id": 46,
"is_also_category": false,
"is_extractable": true,
"skill_nature": "PLATFORM",
"slug": "prometheus",
"sub_category_id": 2837,
"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": "Prometheus",
"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": "Prometheus",
"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": "Prometheus",
"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 Operations",
"id": 143,
"rationale": "Monitoring, logging, tracing, and operational readiness patterns used to keep cloud platforms supportable. Cloud Architects use this to define what telemetry and operational controls workloads must expose.",
"slug": "observability-and-operations",
"source": "db"
},
"input_skill": "Prometheus",
"llm_role": null,
"roles_from_db": [
{
"display_name": "Cloud Architect",
"id": 9,
"rationale": null,
"role_archetype": null,
"slug": "cloud-architect",
"source": "db"
}
]
}
],
"input_skill": "Prometheus",
"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": "Datadog",
"alias_type": "CANONICAL",
"id": 1324,
"is_primary": true,
"match_strategy": "CASE_INSENSITIVE"
}
],
"canonical": {
"category_id": 9,
"display_name": "Datadog",
"id": 779,
"is_also_category": false,
"is_extractable": true,
"skill_nature": "PLATFORM",
"slug": "datadog",
"sub_category_id": 176,
"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": "Datadog",
"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 Operations",
"id": 143,
"rationale": "Monitoring, logging, tracing, and operational readiness patterns used to keep cloud platforms supportable. Cloud Architects use this to define what telemetry and operational controls workloads must expose.",
"slug": "observability-and-operations",
"source": "db"
},
"input_skill": "Datadog",
"llm_role": null,
"roles_from_db": [
{
"display_name": "Cloud Architect",
"id": 9,
"rationale": null,
"role_archetype": null,
"slug": "cloud-architect",
"source": "db"
}
]
}
],
"input_skill": "Datadog",
"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": "Loki",
"matched_via": null,
"new_alias_persisted": false,
"new_alias_text": null,
"new_skill_meta": {
"derived": {
"category": "Monitoring Tools",
"skill_nature": "TOOL",
"sub_category": "general",
"typical_lifespan": "MULTI_YEAR",
"version_strategy": "UNVERSIONED",
"volatility": "MEDIUM"
},
"enrichment": null,
"keep_log": [],
"locked_dimensions": [],
"merge_log": [],
"placed": null,
"relationships": null,
"skill_id": "loki",
"split_log": [],
"typed": null,
"warnings": []
},
"source_tag": "llm",
"was_in_llm_skills": true
},
{
"aliases_in_db": [
{
"alias_text": "Agile",
"alias_type": "CANONICAL",
"id": 868,
"is_primary": true,
"match_strategy": "CASE_INSENSITIVE"
}
],
"canonical": {
"category_id": 8,
"display_name": "Agile",
"id": 520,
"is_also_category": false,
"is_extractable": true,
"skill_nature": "METHODOLOGY",
"slug": "agile",
"sub_category_id": 3594,
"typical_lifespan": "EVERGREEN",
"volatility": "STABLE"
},
"dimensions": [
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "React Frontend Development",
"id": 96,
"rationale": "Building interactive web user interfaces with React.js, including component composition, state management, hooks, and rendering patterns. React.js belongs here because it is a core library for client-side UI development in modern web applications.",
"slug": "d_init_01",
"source": "db"
},
"input_skill": "Agile",
"llm_role": null,
"roles_from_db": []
},
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Software Concepts, Patterns \u0026 Practices",
"id": 478,
"rationale": "Champion foundational software design patterns, development methodologies, and engineering best practices.",
"slug": "software-concepts-patterns-practices",
"source": "db"
},
"input_skill": "Agile",
"llm_role": null,
"roles_from_db": [
{
"display_name": "Engineering Manager",
"id": 121,
"rationale": null,
"role_archetype": null,
"slug": "engineering-manager",
"source": "db"
}
]
}
],
"input_skill": "Agile",
"matched_via": "alias",
"new_alias_persisted": false,
"new_alias_text": null,
"new_skill_meta": null,
"source_tag": "db",
"was_in_llm_skills": true
}
],
"unmatched_skills": [
"Loki"
]
}
API 3 — final-role-output
{
"chosen_role": {
"display_name": "Platform Engineer",
"id": 133,
"rationale": "Domain=DevOps \u0026 Platform \u2192 sub-role infrastructure-platform-engineer; The JD centers on internal service platform, developer experience, automation, and large-scale cloud infrastructure, which best matches Platform Engineer over narrower Kubernetes, IaC, or pure SRE roles.",
"role_archetype": null,
"slug": "platform-engineer",
"source": "db"
},
"chosen_role_resolution": "in_db",
"final_input_skills": [
{
"skill": "AWS",
"tag": "in_db"
},
{
"skill": "Kubernetes",
"tag": "in_db"
},
{
"skill": "Terraform",
"tag": "in_db"
},
{
"skill": "Go",
"tag": "in_db"
},
{
"skill": "Kafka",
"tag": "in_db"
},
{
"skill": "Argo CD",
"tag": "in_db"
},
{
"skill": "Buildkite",
"tag": "in_db"
},
{
"skill": "Grafana",
"tag": "in_db"
},
{
"skill": "Prometheus",
"tag": "in_db"
},
{
"skill": "Datadog",
"tag": "in_db"
},
{
"skill": "Loki",
"tag": "new"
},
{
"skill": "Agile",
"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": 133,
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Cloud Platforms",
"id": 20,
"rationale": "Underlying cloud providers that host the managed services or infrastructure used by the role, such as AWS, Azure, and GCP.",
"slug": "cloud-platforms",
"source": "db"
},
"dimension_id": 20,
"input_skill": "AWS",
"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": "Cyber Security Engineer",
"id": 5,
"rationale": null,
"role_archetype": null,
"slug": "cybersecurity-engineer",
"source": "db"
},
{
"display_name": "Data Engineer",
"id": 2,
"rationale": null,
"role_archetype": null,
"slug": "data-engineer",
"source": "db"
},
{
"display_name": "DevOps Engineer",
"id": 10,
"rationale": null,
"role_archetype": null,
"slug": "devops-engineer",
"source": "db"
},
{
"display_name": "Fullstack Developer",
"id": 15,
"rationale": null,
"role_archetype": null,
"slug": "full-stack-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": "Kotlin Backend Developer",
"id": 84,
"rationale": null,
"role_archetype": "Engineering",
"slug": "kotlin-server-backend-developer",
"source": "db"
},
{
"display_name": "ML Engineer",
"id": 3,
"rationale": null,
"role_archetype": null,
"slug": "ml-engineer",
"source": "db"
},
{
"display_name": "MLOps Engineer",
"id": 16,
"rationale": null,
"role_archetype": null,
"slug": "ml-ops-engineer",
"source": "db"
},
{
"display_name": "Node.js Backend Developer",
"id": 82,
"rationale": null,
"role_archetype": "Engineering",
"slug": "node-backend-developer",
"source": "db"
},
{
"display_name": "Python Backend Developer",
"id": 80,
"rationale": null,
"role_archetype": "Engineering",
"slug": "python-backend-developer",
"source": "db"
},
{
"display_name": "Scala Backend Developer",
"id": 87,
"rationale": null,
"role_archetype": "Engineering",
"slug": "scala-backend-developer",
"source": "db"
}
],
"skill_dimension_saved": true,
"skill_id": 187,
"skill_tag": "in_db",
"skipped_reason": null
},
{
"chosen_role_id": 133,
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Cloud Platforms for AI Deployment",
"id": 211,
"rationale": "Major cloud services that provide infrastructure and managed services for AI workloads.",
"slug": "cloud-platforms-for-ai-deployment",
"source": "db"
},
"dimension_id": 211,
"input_skill": "AWS",
"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": "AI Engineer",
"id": 13,
"rationale": null,
"role_archetype": null,
"slug": "ai-engineer",
"source": "db"
}
],
"skill_dimension_saved": true,
"skill_id": 187,
"skill_tag": "in_db",
"skipped_reason": null
},
{
"chosen_role_id": 133,
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Cloud Provider Platforms",
"id": 131,
"rationale": "Major cloud platforms and their core service ecosystems used to design target-state architectures, choose deployment boundaries, and evaluate managed capabilities. This is the primary substrate for cloud architecture decisions.",
"slug": "cloud-provider-platforms",
"source": "db"
},
"dimension_id": 131,
"input_skill": "AWS",
"llm_role": null,
"matched_chosen_role": false,
"outcome_line": "Existing dimension (library) \u00b7 Role\u2194dimension skipped (dimension not under chosen role)",
"role_dimension_saved": false,
"roles_from_db": [
{
"display_name": "Cloud Architect",
"id": 9,
"rationale": null,
"role_archetype": null,
"slug": "cloud-architect",
"source": "db"
},
{
"display_name": "Cloud Security Engineer",
"id": 23,
"rationale": null,
"role_archetype": null,
"slug": "cloud-security-engineer",
"source": "db"
}
],
"skill_dimension_saved": true,
"skill_id": 187,
"skill_tag": "in_db",
"skipped_reason": null
},
{
"chosen_role_id": 133,
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Cloud Security Posture Tools",
"id": 64,
"rationale": "Cloud-native security platforms used to assess misconfiguration, workload exposure, and cloud control coverage. This dimension includes the major CNAPP/CSPM/CWPP vendors and cloud security services the role reviews and tunes.",
"slug": "cloud-security-posture-tools",
"source": "db"
},
"dimension_id": 64,
"input_skill": "AWS",
"llm_role": null,
"matched_chosen_role": false,
"outcome_line": "Existing dimension (library) \u00b7 Role\u2194dimension skipped (dimension not under chosen role)",
"role_dimension_saved": false,
"roles_from_db": [
{
"display_name": "Cloud Security Engineer",
"id": 23,
"rationale": null,
"role_archetype": null,
"slug": "cloud-security-engineer",
"source": "db"
},
{
"display_name": "Cyber Security Engineer",
"id": 5,
"rationale": null,
"role_archetype": null,
"slug": "cybersecurity-engineer",
"source": "db"
}
],
"skill_dimension_saved": true,
"skill_id": 187,
"skill_tag": "in_db",
"skipped_reason": null
},
{
"chosen_role_id": 133,
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Vendor Product Families",
"id": 477,
"rationale": "Coordinate usage, licensing, and architecture decisions for major vendor software and cloud product families.",
"slug": "vendor-product-families",
"source": "db"
},
"dimension_id": 477,
"input_skill": "AWS",
"llm_role": null,
"matched_chosen_role": false,
"outcome_line": "Existing dimension (library) \u00b7 Role\u2194dimension skipped (dimension not under chosen role)",
"role_dimension_saved": false,
"roles_from_db": [
{
"display_name": "Engineering Manager",
"id": 121,
"rationale": null,
"role_archetype": null,
"slug": "engineering-manager",
"source": "db"
}
],
"skill_dimension_saved": true,
"skill_id": 187,
"skill_tag": "in_db",
"skipped_reason": null
},
{
"chosen_role_id": 133,
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Container Orchestration Platforms",
"id": 134,
"rationale": "Platforms that schedule and manage containerized workloads across clusters and environments. Cloud Architects need these to define workload placement standards, cluster boundaries, and platform capabilities.",
"slug": "container-orchestration-platforms",
"source": "db"
},
"dimension_id": 134,
"input_skill": "Kubernetes",
"llm_role": null,
"matched_chosen_role": false,
"outcome_line": "Existing dimension (library) \u00b7 Role\u2194dimension skipped (dimension not under chosen role)",
"role_dimension_saved": false,
"roles_from_db": [
{
"display_name": "Cloud Architect",
"id": 9,
"rationale": null,
"role_archetype": null,
"slug": "cloud-architect",
"source": "db"
},
{
"display_name": "DevOps Engineer",
"id": 10,
"rationale": null,
"role_archetype": null,
"slug": "devops-engineer",
"source": "db"
}
],
"skill_dimension_saved": true,
"skill_id": 726,
"skill_tag": "in_db",
"skipped_reason": null
},
{
"chosen_role_id": 133,
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Kubernetes for ML Workloads",
"id": 47,
"rationale": "Kubernetes-native components used to schedule, accelerate, and isolate ML training and serving workloads. This includes GPU enablement and ML-specific controllers rather than generic cluster administration.",
"slug": "kubernetes-for-ml-workloads",
"source": "db"
},
"dimension_id": 47,
"input_skill": "Kubernetes",
"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"
},
{
"display_name": "MLOps Engineer",
"id": 16,
"rationale": null,
"role_archetype": null,
"slug": "ml-ops-engineer",
"source": "db"
}
],
"skill_dimension_saved": true,
"skill_id": 726,
"skill_tag": "in_db",
"skipped_reason": null
},
{
"chosen_role_id": 133,
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Infrastructure \u0026 Security Automation Frameworks",
"id": 249,
"rationale": "Frameworks and libraries for provisioning, configuring, and automating cloud security infrastructure.",
"slug": "infrastructure-security-automation-frameworks",
"source": "db"
},
"dimension_id": 249,
"input_skill": "Terraform",
"llm_role": null,
"matched_chosen_role": false,
"outcome_line": "Existing dimension (library) \u00b7 Role\u2194dimension skipped (dimension not under chosen role)",
"role_dimension_saved": false,
"roles_from_db": [
{
"display_name": "Cloud Security Engineer",
"id": 23,
"rationale": null,
"role_archetype": null,
"slug": "cloud-security-engineer",
"source": "db"
}
],
"skill_dimension_saved": true,
"skill_id": 286,
"skill_tag": "in_db",
"skipped_reason": null
},
{
"chosen_role_id": 133,
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Infrastructure as Code",
"id": 132,
"rationale": "Declarative provisioning and environment definition tools used to codify cloud infrastructure, repeatable environments, and platform standards. Cloud Architects use these to express reference architectures and guardrails.",
"slug": "infrastructure-as-code",
"source": "db"
},
"dimension_id": 132,
"input_skill": "Terraform",
"llm_role": null,
"matched_chosen_role": false,
"outcome_line": "Existing dimension (library) \u00b7 Role\u2194dimension skipped (dimension not under chosen role)",
"role_dimension_saved": false,
"roles_from_db": [
{
"display_name": "Cloud Architect",
"id": 9,
"rationale": null,
"role_archetype": null,
"slug": "cloud-architect",
"source": "db"
},
{
"display_name": "DevOps Engineer",
"id": 10,
"rationale": null,
"role_archetype": null,
"slug": "devops-engineer",
"source": "db"
}
],
"skill_dimension_saved": true,
"skill_id": 286,
"skill_tag": "in_db",
"skipped_reason": null
},
{
"chosen_role_id": 133,
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Infrastructure as Code for ML",
"id": 57,
"rationale": "Tools for provisioning and managing ML infrastructure resources through code.",
"slug": "infrastructure-as-code-for-ml",
"source": "db"
},
"dimension_id": 57,
"input_skill": "Terraform",
"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": 286,
"skill_tag": "in_db",
"skipped_reason": null
},
{
"chosen_role_id": 133,
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Cloud Security Scripting \u0026 DSL Languages",
"id": 248,
"rationale": "Proficiency in programming and domain-specific languages used to automate and script cloud security controls.",
"slug": "cloud-security-scripting-dsl-languages",
"source": "db"
},
"dimension_id": 248,
"input_skill": "Go",
"llm_role": null,
"matched_chosen_role": false,
"outcome_line": "Existing dimension (library) \u00b7 Role\u2194dimension skipped (dimension not under chosen role)",
"role_dimension_saved": false,
"roles_from_db": [
{
"display_name": "Cloud Security Engineer",
"id": 23,
"rationale": null,
"role_archetype": null,
"slug": "cloud-security-engineer",
"source": "db"
}
],
"skill_dimension_saved": true,
"skill_id": 3,
"skill_tag": "in_db",
"skipped_reason": null
},
{
"chosen_role_id": 133,
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Go Language and Toolchain",
"id": 367,
"rationale": "Core Go implementation skills used to build backend service logic, handlers, and internal libraries. This is the primary coding surface for the role and includes language features, module management, and compiler/runtime behavior relevant to service code.",
"slug": "go-language-and-toolchain",
"source": "db"
},
"dimension_id": 367,
"input_skill": "Go",
"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"
}
],
"skill_dimension_saved": true,
"skill_id": 3,
"skill_tag": "in_db",
"skipped_reason": null
},
{
"chosen_role_id": 133,
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Programming Languages",
"id": 1,
"rationale": "Primary implementation languages used to build client and server feature code. Full stack engineers need enough fluency to move across layers and implement product behavior end to end.",
"slug": "programming-languages",
"source": "db"
},
"dimension_id": 1,
"input_skill": "Go",
"llm_role": null,
"matched_chosen_role": false,
"outcome_line": "Existing dimension (library) \u00b7 Role\u2194dimension skipped (dimension not under chosen role)",
"role_dimension_saved": false,
"roles_from_db": [
{
"display_name": "Backend Developer",
"id": 1,
"rationale": null,
"role_archetype": "A Backend Engineer designs, builds, and maintains the server-side logic and data handling that power applications and services. They focus on implementing reliable business functionality, integrating with other systems, and ensuring the backend is scalable, maintainable, and observable.",
"slug": "backend-engineer",
"source": "db"
},
{
"display_name": "Fullstack Developer",
"id": 15,
"rationale": null,
"role_archetype": null,
"slug": "full-stack-engineer",
"source": "db"
},
{
"display_name": "Fullstack Developer",
"id": 435,
"rationale": null,
"role_archetype": "Engineering",
"slug": "fullstack-developer",
"source": "db"
}
],
"skill_dimension_saved": true,
"skill_id": 3,
"skill_tag": "in_db",
"skipped_reason": null
},
{
"chosen_role_id": 133,
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Programming Languages and Scripting",
"id": 59,
"rationale": "Languages used to write security automation, analysis scripts, detection logic, and remediation helpers. This is the primary implementation surface for a cybersecurity engineer across tooling and response workflows.",
"slug": "programming-languages-and-scripting",
"source": "db"
},
"dimension_id": 59,
"input_skill": "Go",
"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": "Cyber Security Engineer",
"id": 5,
"rationale": null,
"role_archetype": null,
"slug": "cybersecurity-engineer",
"source": "db"
}
],
"skill_dimension_saved": true,
"skill_id": 3,
"skill_tag": "in_db",
"skipped_reason": null
},
{
"chosen_role_id": 133,
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Programming Languages for ML Systems",
"id": 39,
"rationale": "Languages used to build training code, inference services, evaluation jobs, and ML glue code. This is the primary implementation surface for ML engineers across experimentation and productionization.",
"slug": "programming-languages-for-ml-systems",
"source": "db"
},
"dimension_id": 39,
"input_skill": "Go",
"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"
},
{
"display_name": "MLOps Engineer",
"id": 16,
"rationale": null,
"role_archetype": null,
"slug": "ml-ops-engineer",
"source": "db"
}
],
"skill_dimension_saved": true,
"skill_id": 3,
"skill_tag": "in_db",
"skipped_reason": null
},
{
"chosen_role_id": 133,
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Asynchronous Messaging and Event Streaming",
"id": 297,
"rationale": "Asynchronous communication patterns and broker technologies used to decouple backend services and move work off the request path. Includes queues, pub/sub, event streams, consumer groups, dead-letter queues, and delivery semantics across systems such as Kafka, RabbitMQ, NATS, SQS/SNS, Pulsar, and ActiveMQ.",
"slug": "asynchronous-messaging-and-event-streaming",
"source": "db"
},
"dimension_id": 297,
"input_skill": "Kafka",
"llm_role": null,
"matched_chosen_role": false,
"outcome_line": "Existing dimension (library) \u00b7 Role\u2194dimension skipped (dimension not under chosen role)",
"role_dimension_saved": false,
"roles_from_db": [
{
"display_name": ".NET Backend Developer",
"id": 83,
"rationale": null,
"role_archetype": "Engineering",
"slug": "dotnet-backend-developer",
"source": "db"
},
{
"display_name": "Go Backend Developer",
"id": 81,
"rationale": null,
"role_archetype": "Engineering",
"slug": "go-backend-developer",
"source": "db"
},
{
"display_name": "Kotlin Backend Developer",
"id": 84,
"rationale": null,
"role_archetype": "Engineering",
"slug": "kotlin-server-backend-developer",
"source": "db"
},
{
"display_name": "Node.js Backend Developer",
"id": 82,
"rationale": null,
"role_archetype": "Engineering",
"slug": "node-backend-developer",
"source": "db"
},
{
"display_name": "Scala Backend Developer",
"id": 87,
"rationale": null,
"role_archetype": "Engineering",
"slug": "scala-backend-developer",
"source": "db"
}
],
"skill_dimension_saved": true,
"skill_id": 36,
"skill_tag": "in_db",
"skipped_reason": null
},
{
"chosen_role_id": 133,
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Messaging and Background Jobs",
"id": 291,
"rationale": "Asynchronous processing patterns and worker systems used to decouple backend work from request handling. This is a coherent cluster because the role supports background jobs, retries, and deferred processing.",
"slug": "messaging-and-background-jobs",
"source": "db"
},
"dimension_id": 291,
"input_skill": "Kafka",
"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": "PHP Backend Developer",
"id": 86,
"rationale": null,
"role_archetype": "Engineering",
"slug": "php-backend-developer",
"source": "db"
},
{
"display_name": "Python Backend Developer",
"id": 80,
"rationale": null,
"role_archetype": "Engineering",
"slug": "python-backend-developer",
"source": "db"
},
{
"display_name": "Ruby Backend Developer",
"id": 85,
"rationale": null,
"role_archetype": "Engineering",
"slug": "ruby-backend-developer",
"source": "db"
}
],
"skill_dimension_saved": true,
"skill_id": 36,
"skill_tag": "in_db",
"skipped_reason": null
},
{
"chosen_role_id": 133,
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Messaging and Event Streaming",
"id": 8,
"rationale": "Transport-layer systems used to move events and decouple producers from consumers. Data engineers use these systems to ingest, buffer, and distribute event data before downstream processing.",
"slug": "messaging-and-event-streaming",
"source": "db"
},
"dimension_id": 8,
"input_skill": "Kafka",
"llm_role": null,
"matched_chosen_role": false,
"outcome_line": "Existing dimension (library) \u00b7 Role\u2194dimension skipped (dimension not under chosen role)",
"role_dimension_saved": false,
"roles_from_db": [
{
"display_name": "Backend Developer",
"id": 1,
"rationale": null,
"role_archetype": "A Backend Engineer designs, builds, and maintains the server-side logic and data handling that power applications and services. They focus on implementing reliable business functionality, integrating with other systems, and ensuring the backend is scalable, maintainable, and observable.",
"slug": "backend-engineer",
"source": "db"
},
{
"display_name": "Data Engineer",
"id": 2,
"rationale": null,
"role_archetype": null,
"slug": "data-engineer",
"source": "db"
}
],
"skill_dimension_saved": true,
"skill_id": 36,
"skill_tag": "in_db",
"skipped_reason": null
},
{
"chosen_role_id": 133,
"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": "Argo 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": 284,
"skill_tag": "in_db",
"skipped_reason": null
},
{
"chosen_role_id": 133,
"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": "Buildkite",
"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": 827,
"skill_tag": "in_db",
"skipped_reason": null
},
{
"chosen_role_id": 133,
"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": "Grafana",
"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": 47,
"skill_tag": "in_db",
"skipped_reason": null
},
{
"chosen_role_id": 133,
"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": "Grafana",
"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": 47,
"skill_tag": "in_db",
"skipped_reason": null
},
{
"chosen_role_id": 133,
"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": "Grafana",
"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": 47,
"skill_tag": "in_db",
"skipped_reason": null
},
{
"chosen_role_id": 133,
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Observability and Operations",
"id": 143,
"rationale": "Monitoring, logging, tracing, and operational readiness patterns used to keep cloud platforms supportable. Cloud Architects use this to define what telemetry and operational controls workloads must expose.",
"slug": "observability-and-operations",
"source": "db"
},
"dimension_id": 143,
"input_skill": "Grafana",
"llm_role": null,
"matched_chosen_role": false,
"outcome_line": "Existing dimension (library) \u00b7 Role\u2194dimension skipped (dimension not under chosen role)",
"role_dimension_saved": false,
"roles_from_db": [
{
"display_name": "Cloud Architect",
"id": 9,
"rationale": null,
"role_archetype": null,
"slug": "cloud-architect",
"source": "db"
}
],
"skill_dimension_saved": true,
"skill_id": 47,
"skill_tag": "in_db",
"skipped_reason": null
},
{
"chosen_role_id": 133,
"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": "Prometheus",
"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": 46,
"skill_tag": "in_db",
"skipped_reason": null
},
{
"chosen_role_id": 133,
"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": "Prometheus",
"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": 46,
"skill_tag": "in_db",
"skipped_reason": null
},
{
"chosen_role_id": 133,
"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": "Prometheus",
"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": 46,
"skill_tag": "in_db",
"skipped_reason": null
},
{
"chosen_role_id": 133,
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Observability and Operations",
"id": 143,
"rationale": "Monitoring, logging, tracing, and operational readiness patterns used to keep cloud platforms supportable. Cloud Architects use this to define what telemetry and operational controls workloads must expose.",
"slug": "observability-and-operations",
"source": "db"
},
"dimension_id": 143,
"input_skill": "Prometheus",
"llm_role": null,
"matched_chosen_role": false,
"outcome_line": "Existing dimension (library) \u00b7 Role\u2194dimension skipped (dimension not under chosen role)",
"role_dimension_saved": false,
"roles_from_db": [
{
"display_name": "Cloud Architect",
"id": 9,
"rationale": null,
"role_archetype": null,
"slug": "cloud-architect",
"source": "db"
}
],
"skill_dimension_saved": true,
"skill_id": 46,
"skill_tag": "in_db",
"skipped_reason": null
},
{
"chosen_role_id": 133,
"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": "Datadog",
"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": 779,
"skill_tag": "in_db",
"skipped_reason": null
},
{
"chosen_role_id": 133,
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Observability and Operations",
"id": 143,
"rationale": "Monitoring, logging, tracing, and operational readiness patterns used to keep cloud platforms supportable. Cloud Architects use this to define what telemetry and operational controls workloads must expose.",
"slug": "observability-and-operations",
"source": "db"
},
"dimension_id": 143,
"input_skill": "Datadog",
"llm_role": null,
"matched_chosen_role": false,
"outcome_line": "Existing dimension (library) \u00b7 Role\u2194dimension skipped (dimension not under chosen role)",
"role_dimension_saved": false,
"roles_from_db": [
{
"display_name": "Cloud Architect",
"id": 9,
"rationale": null,
"role_archetype": null,
"slug": "cloud-architect",
"source": "db"
}
],
"skill_dimension_saved": true,
"skill_id": 779,
"skill_tag": "in_db",
"skipped_reason": null
},
{
"chosen_role_id": 133,
"dimension": {
"difficulty_hint": "well_known",
"display_name": "React Frontend Development",
"id": 96,
"rationale": "Building interactive web user interfaces with React.js, including component composition, state management, hooks, and rendering patterns. React.js belongs here because it is a core library for client-side UI development in modern web applications.",
"slug": "d_init_01",
"source": "db"
},
"dimension_id": 96,
"input_skill": "Agile",
"llm_role": null,
"matched_chosen_role": false,
"outcome_line": "Existing dimension (library) \u00b7 Role\u2194dimension skipped (dimension not under chosen role)",
"role_dimension_saved": false,
"roles_from_db": [],
"skill_dimension_saved": true,
"skill_id": 520,
"skill_tag": "in_db",
"skipped_reason": null
},
{
"chosen_role_id": 133,
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Software Concepts, Patterns \u0026 Practices",
"id": 478,
"rationale": "Champion foundational software design patterns, development methodologies, and engineering best practices.",
"slug": "software-concepts-patterns-practices",
"source": "db"
},
"dimension_id": 478,
"input_skill": "Agile",
"llm_role": null,
"matched_chosen_role": false,
"outcome_line": "Existing dimension (library) \u00b7 Role\u2194dimension skipped (dimension not under chosen role)",
"role_dimension_saved": false,
"roles_from_db": [
{
"display_name": "Engineering Manager",
"id": 121,
"rationale": null,
"role_archetype": null,
"slug": "engineering-manager",
"source": "db"
}
],
"skill_dimension_saved": true,
"skill_id": 520,
"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": "23c596d1-8698-43f6-a9e0-9e4258417dec"
}
LLM Calls
Every model call made for this run, in pipeline order. Click a card to see the model's response.