Pipeline run
aa83281f-1ea5-4d0d-8b2b-5233ba238859
Client output enrichment
v2 Skill cluster · Nature of work · AI index · Tech stack maturity · Evidence · KRA descriptionvocab breakdown (legacy)
Signals
Post-classification
Captured for admin review
1 POST /skills/extract-from-jd
2 POST /skills/extract-details
3 POST /skills/final-role-output
Backend Developer
domain · Software Engineering CASE DOMAINslug: backend-engineer · id: 1 · source: db
Domain=Software Engineering; The JD centers on scalable software, APIs, microservices, databases, containers, CI, and infrastructure tooling, which best matches a backend engineering role.
Matched skills
Matched dimensions
Matched KRAs
Resolution:
in_db
— role exists in library; skill↔dim and role↔dim links saved when applicable.
Job description
THE CHALLENGE Eventbrite is the leading global ticketing and event technology platform, powering over five million live experiences and 300 million tickets every year. We empower creators of events of all shapes and sizes – from music festivals, experiential yoga, and political rallies to gaming competitions –– by providing them the tools and resources they need to seamlessly plan, promote, and produce live experiences around the world. Getting high-quality, high-volume organic search traffic is essential for all sites, but at Eventbrite, it’s critical to our business. Our ability to surface the event pages created by our organizers to relevant people across all search platforms is central to our product offering and one of Eventbrite’s key advantages for our customers. We are growing our engineering team quickly in Hyderabad, India. Our SEO (Search Engine Optimization) team is looking for a talented senior software engineer who wants to make a direct and measured impact on our business. THE TEAM The SEO team is a cross-functional team including engineers, product, and strategy. We take an agile approach to our work, and we learn from each other as we go. We meet daily to share progress and identify impediments, hone our skills through code reviews, perform demos of the code we ship, and retrospect to improve the way we work. As part of the broader Eventbrite Engineering team, we share our learnings on our Engineering Blog and, during non-pandemic times, read about how Eventbrite approaches SEO on our engineering blog THE TECH STACK Eventbrite is one of the world’s largest Django-powered sites by request volume. Python, Django, and MySQL are the primary off-the-shelf technologies in our stack. We are hosted on AWS.Our primary stack is Python and Django, all running on Amazon AWS with a MySQL backend. Some of the other tools that we use are ElasticSearch, Sass, Git, Backbone, React, and an endless supply of coffee. YOU HAVE You have 5 - 8 years of experience and a proven track record of building software applications at scale in one or more mainstream programming languages as well as having developed web applications at scale using one or more mainstream web application. You have 3+ years of working with relational databases, such as MySQL, PostgreSQL, MSSQL, or non-relational databases like Elasticsearch and Redis You have 2+ years of experience in designing, implementing, and supporting containerized environments. You have a meaningful understanding of modern microservices architecture. You are willing to work with a distributed team across several neighboring time zones. You develop code that is easilRemovey maintainable, thoroughly documented, and well-tested. You have an understanding of the tradeoffs between building new technology and buying existing technology. You have a passion for learning and to mentor others. BONUS POINTS You have experience designing and developing APIs, including RPC and HTTP-based APIs, ideally through an API Gateway platform Comfortable developing in a container environment like Docker Familiarity with continuous integration tools like Jenkins or CircleCI Experience with automated testing frameworks and methodologies Experience with Terraform, Nomad, and other HashiCorp technologies Has led teams in making architectural decisions What We Offer At Eventbrite, we strive to support our Britelings and their loved ones through different stages of life with robust and attractive benefits, financial and physical wellness options, and great perks. In addition to offering a competitive salary and company stock, we have other great benefits available. In the Briteland, you’ll find great medical plans, fertility and adoption benefits, wellness reimbursement, generous parental leave, and much more. We Care About Your Mental Health And Wellbeing. Our employees enjoy free coaching sessions with Modern Health. We also offer free therapy sessions with a psychologist. You’ll also have access to private medical insurance for you and your family, that includes dental care. And our wellness program to pay for your gym expenses. We work hard to cultivate a diverse, equitable and inclusive culture where Britelings feel like they belong. Employees can participate in resource groups and we offer programming throughout the year to support a diverse and inclusive workplace. We offer ongoing training and career development that meets people where they are in their careers. We offer unlimited access to courses in Udemy, leadership coaching for all managers, Briteling led talks, and weekly company-wide town halls with our CEO. We take culture seriously and design programs with employee feedback in mind to make Eventbrite a great place to work no matter where you work from in the world. Work-life balance & flexibility is extremely important to us. Our employees can choose what works best for them: work in one of our offices, be fully remote or the best of both worlds! We believe in a flexible working environment to allow Britelings to perform at their best ensuring a healthy work-life balance. We have recently implemented Britebreak Fridays: all Britelings turn off their computers and take the first Friday of every month off to focus on their wellbeing. About Eventbrite Eventbrite is a global self-service ticketing and experience technology platform that serves a community of hundreds of thousands of event creators in nearly 180 countries. Since inception, Eventbrite has been at the center of the experience economy, transforming the way people organize and attend events. The company was founded by Julia Hartz, Kevin Hartz and Renaud Visage, with a vision to build a self-service platform that would make it possible for anyone to create and sell tickets to live experiences. The Eventbrite platform provides an intuitive, secure, and reliable service that enables creators to plan and execute their live and online events, whether it’s an annual culinary festival attracting thousands of foodies, a professional webinar, a weekly yoga workshop or a youth dance class. With over 290 million tickets distributed for over 5 million total events in 2021, Eventbrite is where people all over the world discover new things to do or new ways to do more of what they love. Learn more at www.eventbrite.com . IS THIS ROLE NOT AN EXACT FIT? Sign up to keep in touch and we’ll let you know when we have new positions on our team . Eventbrite is committed to equality of opportunity for all staff, and applications from all suitably qualified individuals are encouraged, regardless of age, disability, sex, gender reassignment, sexual orientation, pregnancy and maternity, race, religion or belief and marriage and civil partnerships. Applicant Privacy Notice
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
- MySQL (CANONICAL) primary
Context tags (catalog)
Stored enrichment (catalog DB)
- Category
- Datastore
- Sub-category
- Relational Database
- Vendor
- Oracle Corporation
- License
- gpl_v2
- Year introduced
- 1995
- Confidence
- 0.99
- Version strategy
- NOT_APPLICABLE
Maturity reasoning: MySQL appears in a large share of backend/DB job descriptions and remains a standard managed offering across AWS RDS, Cloud SQL, and Azure Database, indicating broad hiring-pipeline demand.
Skill profile (library / DB)
- Skill nature
- TOOL
- Volatility
- STABLE
- Typical lifespan
- EVERGREEN
- Category id
- 3
- Sub-category id
- 29
- Extractable
- True
- Also category
- False
Dimensions (API 2 worklist)
-
Relational Data Modeling Catalog dimension db id 216
Library dimension (catalog)
Roles linked in library: Fullstack Developer, Fullstack Developer, PHP Backend Developer
-
Relational Database Design Catalog dimension db id 4
Library dimension (catalog)
Roles linked in library: .NET Backend Developer, Backend Developer, Kotlin Backend Developer, Node.js Backend Developer, Python Backend Developer, Ruby Backend Developer, Scala Backend Developer
-
Relational Database Usage Catalog dimension db id 371
Library dimension (catalog)
Roles linked in library: Go Backend Developer
API 3 link attempts (this skill)
| Dimension | Skill↔dim | Role↔dim | Outcome |
|---|---|---|---|
|
Relational Data Modeling
relational-data-modeling
|
✓ | — | Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role) |
|
Relational Database Design
relational-database-design
|
✓ | ✓ | Existing dimension (library) · Role↔dimension saved |
|
Relational Database Usage
relational-database-usage
|
✓ | — | Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role) |
Aliases — catalog
- PostgreSQL (CANONICAL) primary
- PG 13 (VERSION)
- PG 14 (VERSION)
- PG 15 (VERSION)
- PG 16 (VERSION)
- PostgreSQL 13 (VERSION)
- PostgreSQL 14 (VERSION)
- PostgreSQL 15 (VERSION)
- PostgreSQL 16 (VERSION)
- Postgres 13 (VERSION)
- Postgres 14 (VERSION)
- Postgres 15 (VERSION)
- Postgres 16 (VERSION)
- pg10 (VERSION)
- pg11 (VERSION)
- pg12 (VERSION)
- pg13 (VERSION)
- pg14 (VERSION)
- pg15 (VERSION)
- pg16 (VERSION)
- postgres (VERSION)
- postgresql 10 (VERSION)
- postgresql 11 (VERSION)
- postgresql 12 (VERSION)
- postgresql 13 (VERSION)
- postgresql 14 (VERSION)
- postgresql 15 (VERSION)
- postgresql 16 (VERSION)
- postgresql-16 (VERSION)
- postgresql10 (VERSION)
- postgresql11 (VERSION)
- postgresql12 (VERSION)
- postgresql13 (VERSION)
- postgresql14 (VERSION)
- postgresql15 (VERSION)
- postgresql16 (VERSION)
Context tags (catalog)
Stored enrichment (catalog DB)
- Category
- Datastore
- Sub-category
- Relational Database
- Vendor
- PostgreSQL Global Development Group
- License
- other_open
- Year introduced
- 1996
- Confidence
- 0.99
- Version strategy
- NOT_APPLICABLE
Maturity reasoning: PostgreSQL appears in a large share of backend/data engineering job postings and is a default managed option across AWS RDS, GCP Cloud SQL, and Azure Database, indicating broad hiring-pipeline adoption.
Skill profile (library / DB)
- Skill nature
- TOOL
- Volatility
- STABLE
- Typical lifespan
- EVERGREEN
- Category id
- 3
- Sub-category id
- 29
- Extractable
- True
- Also category
- False
Dimensions (API 2 worklist)
-
Relational Data Modeling Catalog dimension db id 216
Library dimension (catalog)
Roles linked in library: Fullstack Developer, Fullstack Developer, PHP Backend Developer
-
Relational Database Design Catalog dimension db id 4
Library dimension (catalog)
Roles linked in library: .NET Backend Developer, Backend Developer, Kotlin Backend Developer, Node.js Backend Developer, Python Backend Developer, Ruby Backend Developer, Scala Backend Developer
-
Relational Database Usage Catalog dimension db id 371
Library dimension (catalog)
Roles linked in library: Go Backend Developer
API 3 link attempts (this skill)
| Dimension | Skill↔dim | Role↔dim | Outcome |
|---|---|---|---|
|
Relational Data Modeling
relational-data-modeling
|
✓ | — | Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role) |
|
Relational Database Design
relational-database-design
|
✓ | ✓ | Existing dimension (library) · Role↔dimension saved |
|
Relational Database Usage
relational-database-usage
|
✓ | — | 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
- Databases
- Sub-category
- general
- Skill nature
- TOOL
- Volatility
- MEDIUM
- Typical lifespan
- MULTI_YEAR
- Version strategy
- UNVERSIONED
Aliases — catalog
- Elasticsearch (CANONICAL) primary
- ES (VERSION)
- ElasticSearch (VERSION)
- Elasticsearch 6 (VERSION)
- Elasticsearch 6.x (VERSION)
- Elasticsearch 7 (VERSION)
- Elasticsearch 7.x (VERSION)
- Elasticsearch 8 (VERSION)
- Elasticsearch 8.x (VERSION)
- Elasticsearch v6 (VERSION)
- Elasticsearch v7 (VERSION)
- Elasticsearch v8 (VERSION)
Context tags (catalog)
Stored enrichment (catalog DB)
- Category
- Datastore
- Sub-category
- Search Datastore
- Vendor
- Elastic NV
- License
- apache_2
- Year introduced
- 2010
- Confidence
- 0.93
- Version strategy
- SEPARATE_ENTITY
- Version tag
- 8.x
Maturity reasoning: Commonly listed in job descriptions for search/log analytics roles and widely deployed in production; Elastic’s docs and ecosystem show sustained adoption rather than sunset or replacement.
Skill profile (library / DB)
- Skill nature
- TOOL
- Volatility
- STABLE
- Typical lifespan
- EVERGREEN
- Category id
- 3
- Sub-category id
- 2925
- Extractable
- True
- Also category
- False
Dimensions (API 2 worklist)
-
Magento Search and Indexing Catalog dimension db id 403
Library dimension (catalog)
Roles linked in library: Magento Dev
-
Search and Content Discovery Catalog dimension db id 356
Library dimension (catalog)
Roles linked in library: Drupal Dev, Sitecore Dev
API 3 link attempts (this skill)
| Dimension | Skill↔dim | Role↔dim | Outcome |
|---|---|---|---|
|
Magento Search and Indexing
magento-search-and-indexing
|
✓ | — | Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role) |
|
Search and Content Discovery
search-and-content-discovery
|
✓ | — | Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role) |
Aliases — catalog
- Redis (CANONICAL) primary
Context tags (catalog)
Stored enrichment (catalog DB)
- Category
- Datastore
- Sub-category
- Key Value Store
- Vendor
- Redis Labs
- License
- apache_2
- Year introduced
- 2009
- Confidence
- 0.95
- Version strategy
- NOT_APPLICABLE
Maturity reasoning: Redis appears in many job descriptions for caching, queues, and session storage, and is a standard datastore in modern backend stacks; vendor activity and broad ecosystem support indicate strong market demand.
Skill profile (library / DB)
- Skill nature
- TOOL
- Volatility
- STABLE
- Typical lifespan
- EVERGREEN
- Category id
- 3
- Sub-category id
- 28
- Extractable
- True
- Also category
- False
Dimensions (API 2 worklist)
-
Caching and State Management Catalog dimension db id 7
Library dimension (catalog)
Roles linked in library: .NET Backend Developer, Backend Developer, Kotlin Backend Developer, Node.js Backend Developer, PHP Backend Developer, Python Backend Developer, Ruby Backend Developer, Scala Backend Developer
-
Magento Caching and Performance Catalog dimension db id 404
Library dimension (catalog)
Roles linked in library: Magento Dev
API 3 link attempts (this skill)
| Dimension | Skill↔dim | Role↔dim | Outcome |
|---|---|---|---|
|
Caching and State Management
caching-and-state-management
|
✓ | ✓ | Existing dimension (library) · Role↔dimension saved |
|
Magento Caching and Performance
magento-caching-and-performance
|
✓ | — | Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role) |
Aliases — catalog
- microservices (CANONICAL) primary
Context tags (catalog)
Stored enrichment (catalog DB)
- Category
- Architecture
- Sub-category
- Distributed System Architecture
- Confidence
- 0.99
- Version strategy
- NOT_APPLICABLE
Maturity reasoning: Microservices is a common architecture in job descriptions across backend/cloud roles, and major vendors like AWS, Google Cloud, and Kubernetes ecosystems provide first-class support and reference patterns.
Skill profile (library / DB)
- Skill nature
- PATTERN
- Volatility
- STABLE
- Typical lifespan
- EVERGREEN
- Category id
- 1
- Sub-category id
- 1
- Extractable
- True
- Also category
- False
Dimensions (API 2 worklist)
-
Microservices and Distributed Systems Catalog dimension db id 9
Library dimension (catalog)
Roles linked in library: Backend Developer, Node.js Backend Developer, Scala Backend Developer
API 3 link attempts (this skill)
| Dimension | Skill↔dim | Role↔dim | Outcome |
|---|---|---|---|
|
Microservices and Distributed Systems
microservices-and-distributed-systems
|
✓ | ✓ | Existing dimension (library) · Role↔dimension saved |
Aliases — catalog
- API (CANONICAL)
Context tags (catalog)
Stored enrichment (catalog DB)
- Category
- Concept
- Sub-category
- Application Programming Interface
- Confidence
- 0.93
- Version strategy
- NOT_APPLICABLE
Maturity reasoning: APIs are a core requirement in most software engineering JDs and underpin common integrations across cloud, mobile, and web stacks; major vendors like AWS, Stripe, and Google Cloud center products on API-first usage.
Skill profile (library / DB)
- Skill nature
- CONCEPT
- Volatility
- STABLE
- Typical lifespan
- EVERGREEN
- Category id
- 2
- Sub-category id
- 1174
- Extractable
- True
- Also category
- False
Dimensions (API 2 worklist)
-
API Integration and Data Fetching Catalog dimension db id 127
Library dimension (catalog)
Roles linked in library: Angular Frontend Developer, Frontend Developer, Fullstack Developer, Fullstack Developer, React Frontend Developer, Svelte Frontend Developer, Vue Frontend Developer, Web Developer
API 3 link attempts (this skill)
| Dimension | Skill↔dim | Role↔dim | Outcome |
|---|---|---|---|
|
API Integration and Data Fetching
api-integration-and-data-fetching
|
✓ | — | Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role) |
Skill enrichment (orchestrator / LLM)
No Stage 7 enrichment blob on this skill (orchestrator skipped enrichment).
- Category
- Concepts
- Sub-category
- general
- Skill nature
- CONCEPT
- Volatility
- STABLE
- Typical lifespan
- EVERGREEN
- Version strategy
- UNVERSIONED
Aliases — catalog
- HTTP (CANONICAL) primary
Context tags (catalog)
Stored enrichment (catalog DB)
- Category
- Protocol
- Sub-category
- Application Protocol
- Confidence
- 0.99
- Version strategy
- NOT_APPLICABLE
Maturity reasoning: HTTP is a foundational web protocol present in nearly all backend/frontend JDs and cloud docs; it underpins REST APIs and browser traffic, with no successor replacing it.
Skill profile (library / DB)
- Skill nature
- PROTOCOL
- Volatility
- STABLE
- Typical lifespan
- EVERGREEN
- Category id
- 10
- Sub-category id
- 710
- Extractable
- True
- Also category
- False
Dimensions (API 2 worklist)
-
Networking and API Integration Catalog dimension db id 84
Library dimension (catalog)
Roles linked in library: Android Developer, Hybrid Mobile Developer, Native Mobile Developer, iOS Developer
API 3 link attempts (this skill)
| Dimension | Skill↔dim | Role↔dim | Outcome |
|---|---|---|---|
|
Networking and API Integration
networking-and-api-integration
|
✓ | — | Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role) |
Skill enrichment (orchestrator / LLM)
No Stage 7 enrichment blob on this skill (orchestrator skipped enrichment).
- Category
- Web Frameworks
- Sub-category
- general
- Skill nature
- TOOL
- Volatility
- MEDIUM
- Typical lifespan
- MULTI_YEAR
- Version strategy
- UNVERSIONED
Aliases — catalog
- Docker (CANONICAL) primary
Context tags (catalog)
Stored enrichment (catalog DB)
- Category
- Tool
- Sub-category
- Containerization Tool
- Vendor
- Docker, Inc.
- License
- apache_2
- Year introduced
- 2013
- Confidence
- 0.98
- Version strategy
- NOT_APPLICABLE
Maturity reasoning: Docker is a hiring-pipeline staple: it appears in many DevOps, backend, and platform JDs, and remains a standard containerization tool alongside Kubernetes in production stacks.
Skill profile (library / DB)
- Skill nature
- TOOL
- Volatility
- STABLE
- Typical lifespan
- EVERGREEN
- Category id
- 13
- Sub-category id
- 63
- Extractable
- True
- Also category
- False
Dimensions (API 2 worklist)
-
Containerization and Image Builds Catalog dimension db id 152
Library dimension (catalog)
Roles linked in library: DevOps Engineer
-
Deployment and Cloud Platforms Catalog dimension db id 418
Library dimension (catalog)
Roles linked in library: Ruby Backend Developer
-
Deployment and Runtime Configuration Catalog dimension db id 13
Library dimension (catalog)
Roles linked in library: .NET Backend Developer, Backend Developer, Go Backend Developer, PHP Backend Developer
API 3 link attempts (this skill)
| Dimension | Skill↔dim | Role↔dim | Outcome |
|---|---|---|---|
|
Containerization and Image Builds
containerization-and-image-builds
|
✓ | — | Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role) |
|
Deployment and Cloud Platforms
deployment-and-cloud-platforms
|
✓ | — | Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role) |
|
Deployment and Runtime Configuration
deployment-and-runtime-configuration
|
✓ | ✓ | Existing dimension (library) · Role↔dimension saved |
Aliases — catalog
- Jenkins (CANONICAL) primary
Context tags (catalog)
Stored enrichment (catalog DB)
- Category
- Tool
- Sub-category
- Ci Cd Tool
- Vendor
- CloudBees
- License
- mit
- Year introduced
- 2011
- Confidence
- 0.99
- Version strategy
- NOT_APPLICABLE
Maturity reasoning: Jenkins remains a common CI/CD requirement in job postings and enterprise DevOps stacks, with broad plugin ecosystem and long-running GitHub activity despite newer alternatives.
Skill profile (library / DB)
- Skill nature
- TOOL
- Volatility
- STABLE
- Typical lifespan
- EVERGREEN
- Category id
- 13
- Sub-category id
- 184
- Extractable
- True
- Also category
- False
Dimensions (API 2 worklist)
-
CI/CD Pipeline Platforms Catalog dimension db id 150
Library dimension (catalog)
Roles linked in library: DevOps Engineer
-
CI/CD for Machine Learning Catalog dimension db id 56
Library dimension (catalog)
Roles linked in library: ML Engineer
API 3 link attempts (this skill)
| Dimension | Skill↔dim | Role↔dim | Outcome |
|---|---|---|---|
|
CI/CD Pipeline Platforms
ci-cd-pipeline-platforms
|
✓ | — | Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role) |
|
CI/CD for Machine Learning
ci-cd-for-machine-learning
|
✓ | — | Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role) |
Aliases — catalog
- CircleCI (CANONICAL) primary
Context tags (catalog)
Stored enrichment (catalog DB)
- Category
- Platform
- Sub-category
- Ci Cd Platform
- Vendor
- CircleCI, Inc.
- License
- other_open
- Year introduced
- 2011
- Confidence
- 0.97
- Version strategy
- NOT_APPLICABLE
Maturity reasoning: CircleCI appears frequently in DevOps/CI-CD job descriptions and remains a mainstream hosted CI platform alongside GitHub Actions and GitLab CI, indicating broad hiring-market familiarity.
Skill profile (library / DB)
- Skill nature
- PLATFORM
- Volatility
- STABLE
- 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) |
Skill enrichment (orchestrator / LLM)
No Stage 7 enrichment blob on this skill (orchestrator skipped enrichment).
- Category
- Testing Tools
- Sub-category
- general
- Skill nature
- PRACTICE
- Volatility
- MEDIUM
- Typical lifespan
- MULTI_YEAR
- Version strategy
- UNVERSIONED
Aliases — catalog
- 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
- Nomad (CANONICAL) primary
Context tags (catalog)
Stored enrichment (catalog DB)
- Category
- Tool
- Sub-category
- Orchestration Tool
- Vendor
- HashiCorp
- License
- mpl
- Year introduced
- 2015
- Confidence
- 0.95
- Version strategy
- NOT_APPLICABLE
Maturity reasoning: HashiCorp Nomad appears in some DevOps/SRE job postings and has growing GitHub activity, but JD volume is far below Kubernetes, indicating adoption is still limited.
Skill profile (library / DB)
- Skill nature
- TOOL
- Volatility
- EMERGING
- Typical lifespan
- EVERGREEN
- Category id
- 13
- Sub-category id
- 580
- 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
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) |
Skill enrichment (orchestrator / LLM)
No Stage 7 enrichment blob on this skill (orchestrator skipped enrichment).
- Category
- Infrastructure Tools
- Sub-category
- general
- Skill nature
- TOOL
- Volatility
- MEDIUM
- Typical lifespan
- MULTI_YEAR
- Version strategy
- UNVERSIONED
All API 3 persistence rows
Same grid as the skill-extractor “Persistence items” table: one row per (skill × dimension) work item.
| Skill | Tag | Dimension | Skill↔dim | Role↔dim | Outcome | Notes |
|---|---|---|---|---|---|---|
| MySQL | in_db |
Relational Data Modeling
relational-data-modeling
|
✓ | — | Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role) | |
| MySQL | in_db |
Relational Database Design
relational-database-design
|
✓ | ✓ | Existing dimension (library) · Role↔dimension saved | |
| MySQL | in_db |
Relational Database Usage
relational-database-usage
|
✓ | — | Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role) | |
| PostgreSQL | in_db |
Relational Data Modeling
relational-data-modeling
|
✓ | — | Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role) | |
| PostgreSQL | in_db |
Relational Database Design
relational-database-design
|
✓ | ✓ | Existing dimension (library) · Role↔dimension saved | |
| PostgreSQL | in_db |
Relational Database Usage
relational-database-usage
|
✓ | — | Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role) | |
| Elasticsearch | in_db |
Magento Search and Indexing
magento-search-and-indexing
|
✓ | — | Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role) | |
| Elasticsearch | in_db |
Search and Content Discovery
search-and-content-discovery
|
✓ | — | Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role) | |
| Redis | in_db |
Caching and State Management
caching-and-state-management
|
✓ | ✓ | Existing dimension (library) · Role↔dimension saved | |
| Redis | in_db |
Magento Caching and Performance
magento-caching-and-performance
|
✓ | — | Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role) | |
| Microservices | in_db |
Microservices and Distributed Systems
microservices-and-distributed-systems
|
✓ | ✓ | Existing dimension (library) · Role↔dimension saved | |
| API | in_db |
API Integration and Data Fetching
api-integration-and-data-fetching
|
✓ | — | Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role) | |
| HTTP | in_db |
Networking and API Integration
networking-and-api-integration
|
✓ | — | Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role) | |
| Docker | in_db |
Containerization and Image Builds
containerization-and-image-builds
|
✓ | — | Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role) | |
| Docker | in_db |
Deployment and Cloud Platforms
deployment-and-cloud-platforms
|
✓ | — | Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role) | |
| Docker | in_db |
Deployment and Runtime Configuration
deployment-and-runtime-configuration
|
✓ | ✓ | Existing dimension (library) · Role↔dimension saved | |
| Jenkins | in_db |
CI/CD Pipeline Platforms
ci-cd-pipeline-platforms
|
✓ | — | Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role) | |
| Jenkins | in_db |
CI/CD for Machine Learning
ci-cd-for-machine-learning
|
✓ | — | Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role) | |
| CircleCI | in_db |
CI/CD Pipeline Platforms
ci-cd-pipeline-platforms
|
✓ | — | 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) | |
| Nomad | in_db |
Container Orchestration Platforms
container-orchestration-platforms
|
✓ | — | Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role) |
Library artifacts (this run)
| Kind | Detail | DB id |
|---|---|---|
| canonical_skill_proposed | MSSQL | type=Databases subtype=general nature=TOOL lifespan=MULTI_YEAR | |
| canonical_skill_proposed | RPC | type=Concepts subtype=general nature=CONCEPT lifespan=EVERGREEN | |
| canonical_skill_proposed | API Gateway | type=Web Frameworks subtype=general nature=TOOL lifespan=MULTI_YEAR | |
| canonical_skill_proposed | Automated Testing | type=Testing Tools subtype=general nature=PRACTICE lifespan=MULTI_YEAR | |
| canonical_skill_proposed | HashiCorp | type=Infrastructure Tools subtype=general nature=TOOL lifespan=MULTI_YEAR |
nano JD Parser — gpt-4.1-nano click to toggle
Show raw JSON
{
"JD_type": "pass",
"about_company": {
"source_marker": {
"first_5_words": "Eventbrite is a global self-service",
"last_5_words": "do more of what they love."
},
"text": "Eventbrite is a global self-service ticketing and experience technology platform that serves a community of hundreds of thousands of event creators in nearly 180 countries. Since inception, Eventbrite has been at the center of the experience economy, transforming the way people organize and attend events. The company was founded by Julia Hartz, Kevin Hartz and Renaud Visage, with a vision to build a self-service platform that would make it possible for anyone to create and sell tickets to live experiences. The Eventbrite platform provides an intuitive, secure, and reliable service that enables creators to plan and execute their live and online events, whether it\u2019s an annual culinary festival attracting thousands of foodies, a professional webinar, a weekly yoga workshop or a youth dance class. With over 290 million tickets distributed for over 5 million total events in 2021, Eventbrite is where people all over the world discover new things to do or new ways to do more of what they love.",
"word_count": 164
},
"certifications": [],
"company_name": "Eventbrite",
"ctc": null,
"domain": {
"primary": {
"aliases": [
"SaaS",
"Event Technology"
],
"domain": "Software \u0026 SaaS Products"
},
"secondary": null
},
"education": [],
"experience": {
"max": 8,
"min": 5,
"raw": "5 - 8 years of experience"
},
"job_locations": [
{
"aliases": [
"Hyderabad, IN"
],
"city": "Hyderabad",
"country": "India",
"state": "Telangana",
"work_mode": "hybrid"
}
],
"role": "Senior Software Engineer, SEO",
"role_aliases": [
"Software Engineer",
"SWE",
"Backend Engineer"
],
"role_archetype": "Engineering",
"roles_and_responsibilities": [
{
"bullet_count": 7,
"heading": "You Have",
"heading_was_present": true,
"source_marker": {
"first_5_words": "You have 5 - 8 years",
"last_5_words": "and to mentor others."
},
"text": "You have 5 - 8 years of experience and a proven track record of building software applications at scale in one or more mainstream programming languages as well as having developed web applications at scale using one or more mainstream web application.\nYou have 3+ years of working with relational databases, such as MySQL, PostgreSQL, MSSQL, or non-relational databases like Elasticsearch and Redis\nYou have 2+ years of experience in designing, implementing, and supporting containerized environments.\nYou have a meaningful understanding of modern microservices architecture.\nYou are willing to work with a distributed team across several neighboring time zones.\nYou develop code that is easily maintainable, thoroughly documented, and well-tested.\nYou have an understanding of the tradeoffs between building new technology and buying existing technology.\nYou have a passion for learning and to mentor others.",
"word_count": 104
},
{
"bullet_count": 6,
"heading": "Bonus Points",
"heading_was_present": true,
"source_marker": {
"first_5_words": "You have experience designing and",
"last_5_words": "making architectural decisions."
},
"text": "You have experience designing and developing APIs, including RPC and HTTP-based APIs, ideally through an API Gateway platform\nComfortable developing in a container environment like Docker\nFamiliarity with continuous integration tools like Jenkins or CircleCI\nExperience with automated testing frameworks and methodologies\nExperience with Terraform, Nomad, and other HashiCorp technologies\nHas led teams in making architectural decisions.",
"word_count": 56
}
],
"urls": [
{
"type": "website",
"url": "www.eventbrite.com"
}
]
}
API 1 — extract-from-jd click to toggle
{
"final_skills": [
{
"is_primary": true,
"skill_name": "MySQL"
},
{
"is_primary": true,
"skill_name": "PostgreSQL"
},
{
"is_primary": true,
"skill_name": "MSSQL"
},
{
"is_primary": true,
"skill_name": "Elasticsearch"
},
{
"is_primary": true,
"skill_name": "Redis"
},
{
"is_primary": true,
"skill_name": "Microservices"
},
{
"is_primary": true,
"skill_name": "API"
},
{
"is_primary": true,
"skill_name": "RPC"
},
{
"is_primary": true,
"skill_name": "HTTP"
},
{
"is_primary": true,
"skill_name": "API Gateway"
},
{
"is_primary": true,
"skill_name": "Docker"
},
{
"is_primary": true,
"skill_name": "Jenkins"
},
{
"is_primary": true,
"skill_name": "CircleCI"
},
{
"is_primary": true,
"skill_name": "Automated Testing"
},
{
"is_primary": true,
"skill_name": "Terraform"
},
{
"is_primary": true,
"skill_name": "Nomad"
},
{
"is_primary": true,
"skill_name": "HashiCorp"
}
],
"jd_role": {
"display_name": "Senior Software Engineer, SEO",
"rationale": null,
"role_aliases": [
"Software Engineer",
"SWE",
"Backend Engineer"
],
"role_archetype": "Engineering",
"slug": ""
},
"nano_parsed": {
"JD_type": "pass",
"about_company": {
"source_marker": {
"first_5_words": "Eventbrite is a global self-service",
"last_5_words": "do more of what they love."
},
"text": "Eventbrite is a global self-service ticketing and experience technology platform that serves a community of hundreds of thousands of event creators in nearly 180 countries. Since inception, Eventbrite has been at the center of the experience economy, transforming the way people organize and attend events. The company was founded by Julia Hartz, Kevin Hartz and Renaud Visage, with a vision to build a self-service platform that would make it possible for anyone to create and sell tickets to live experiences. The Eventbrite platform provides an intuitive, secure, and reliable service that enables creators to plan and execute their live and online events, whether it\u2019s an annual culinary festival attracting thousands of foodies, a professional webinar, a weekly yoga workshop or a youth dance class. With over 290 million tickets distributed for over 5 million total events in 2021, Eventbrite is where people all over the world discover new things to do or new ways to do more of what they love.",
"word_count": 164
},
"certifications": [],
"company_name": "Eventbrite",
"ctc": null,
"domain": {
"primary": {
"aliases": [
"SaaS",
"Event Technology"
],
"domain": "Software \u0026 SaaS Products"
},
"secondary": null
},
"education": [],
"experience": {
"max": 8,
"min": 5,
"raw": "5 - 8 years of experience"
},
"job_locations": [
{
"aliases": [
"Hyderabad, IN"
],
"city": "Hyderabad",
"country": "India",
"state": "Telangana",
"work_mode": "hybrid"
}
],
"role": "Senior Software Engineer, SEO",
"role_aliases": [
"Software Engineer",
"SWE",
"Backend Engineer"
],
"role_archetype": "Engineering",
"roles_and_responsibilities": [
{
"bullet_count": 7,
"heading": "You Have",
"heading_was_present": true,
"source_marker": {
"first_5_words": "You have 5 - 8 years",
"last_5_words": "and to mentor others."
},
"text": "You have 5 - 8 years of experience and a proven track record of building software applications at scale in one or more mainstream programming languages as well as having developed web applications at scale using one or more mainstream web application.\nYou have 3+ years of working with relational databases, such as MySQL, PostgreSQL, MSSQL, or non-relational databases like Elasticsearch and Redis\nYou have 2+ years of experience in designing, implementing, and supporting containerized environments.\nYou have a meaningful understanding of modern microservices architecture.\nYou are willing to work with a distributed team across several neighboring time zones.\nYou develop code that is easily maintainable, thoroughly documented, and well-tested.\nYou have an understanding of the tradeoffs between building new technology and buying existing technology.\nYou have a passion for learning and to mentor others.",
"word_count": 104
},
{
"bullet_count": 6,
"heading": "Bonus Points",
"heading_was_present": true,
"source_marker": {
"first_5_words": "You have experience designing and",
"last_5_words": "making architectural decisions."
},
"text": "You have experience designing and developing APIs, including RPC and HTTP-based APIs, ideally through an API Gateway platform\nComfortable developing in a container environment like Docker\nFamiliarity with continuous integration tools like Jenkins or CircleCI\nExperience with automated testing frameworks and methodologies\nExperience with Terraform, Nomad, and other HashiCorp technologies\nHas led teams in making architectural decisions.",
"word_count": 56
}
],
"urls": [
{
"type": "website",
"url": "www.eventbrite.com"
}
]
},
"rejected": false,
"rejection_reason": null,
"run_id": "aa83281f-1ea5-4d0d-8b2b-5233ba238859",
"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": "Backend Developer",
"kra_matches": [
{
"kra_text": "Designs and maintains RESTful and GraphQL API interfaces with proper authentication, versioning, rate limiting, and documentation for frontend and third-party consumers.",
"sentence": "You have experience designing and developing APIs, including RPC and HTTP-based APIs, ideally through an API Gateway platform",
"similarity": 0.5295
},
{
"kra_text": "Configures Docker containers, deployment descriptors, environment variables, and CI/CD pipeline stages for backend service releases.",
"sentence": "Comfortable developing in a container environment like Docker",
"similarity": 0.4847
},
{
"kra_text": "Writes database access logic including SQL queries, ORM mappings, stored procedures, and migration scripts for relational databases like PostgreSQL and MySQL.",
"sentence": "You have 3+ years of working with relational databases, such as MySQL, PostgreSQL, MSSQL, or non-relational databases like Elasticsearch and Redis",
"similarity": 0.469
}
],
"matched_count": null,
"matched_skills": null,
"role_id": 1,
"score": 0.4944,
"slug": "backend-engineer",
"total_count": null
},
{
"display_name": "React Native Developer",
"kra_matches": [
{
"kra_text": "maintain code quality",
"sentence": "You develop code that is easily maintainable, thoroughly documented, and well-tested.",
"similarity": 0.6213
},
{
"kra_text": "integrate backend APIs",
"sentence": "You have experience designing and developing APIs, including RPC and HTTP-based APIs, ideally through an API Gateway platform",
"similarity": 0.4756
},
{
"kra_text": "maintain code quality",
"sentence": "Comfortable developing in a container environment like Docker",
"similarity": 0.3393
}
],
"matched_count": null,
"matched_skills": null,
"role_id": 73,
"score": 0.4787,
"slug": "react-native-developer",
"total_count": null
},
{
"display_name": "Fullstack Developer",
"kra_matches": [
{
"kra_text": "Designs and queries relational databases like PostgreSQL and document stores like MongoDB, writing migrations, indexes, and optimized queries.",
"sentence": "You have 3+ years of working with relational databases, such as MySQL, PostgreSQL, MSSQL, or non-relational databases like Elasticsearch and Redis",
"similarity": 0.5375
},
{
"kra_text": "Implements complete product features end-to-end from database schema design through backend API to frontend UI using JavaScript, TypeScript, Python, or Ruby on Rails.",
"sentence": "You have experience designing and developing APIs, including RPC and HTTP-based APIs, ideally through an API Gateway platform",
"similarity": 0.439
},
{
"kra_text": "Delivers features through CI/CD pipelines using automated tests, staged rollouts, feature flags, and incremental deployments.",
"sentence": "You develop code that is easily maintainable, thoroughly documented, and well-tested.",
"similarity": 0.3968
}
],
"matched_count": null,
"matched_skills": null,
"role_id": 15,
"score": 0.4578,
"slug": "full-stack-engineer",
"total_count": null
},
{
"display_name": "DevOps Engineer",
"kra_matches": [
{
"kra_text": "Collaborates with development teams to improve build processes, reduce deployment friction, containerize applications, and adopt DevOps best practices.",
"sentence": "Comfortable developing in a container environment like Docker",
"similarity": 0.4938
},
{
"kra_text": "Manages container orchestration with Kubernetes and Docker, deploying applications as pods, managing namespaces, and configuring auto-scaling across cloud environments.",
"sentence": "You have 2+ years of experience in designing, implementing, and supporting containerized environments.",
"similarity": 0.4826
},
{
"kra_text": "Collaborates with development teams to improve build processes, reduce deployment friction, containerize applications, and adopt DevOps best practices.",
"sentence": "You develop code that is easily maintainable, thoroughly documented, and well-tested.",
"similarity": 0.3792
}
],
"matched_count": null,
"matched_skills": null,
"role_id": 10,
"score": 0.4518,
"slug": "devops-engineer",
"total_count": null
},
{
"display_name": "Node.js Backend Developer",
"kra_matches": [
{
"kra_text": "code review and refactoring",
"sentence": "You develop code that is easily maintainable, thoroughly documented, and well-tested.",
"similarity": 0.4931
},
{
"kra_text": "API design and request handling",
"sentence": "You have experience designing and developing APIs, including RPC and HTTP-based APIs, ideally through an API Gateway platform",
"similarity": 0.486
},
{
"kra_text": "asynchronous job processing",
"sentence": "You are willing to work with a distributed team across several neighboring time zones.",
"similarity": 0.3618
}
],
"matched_count": null,
"matched_skills": null,
"role_id": 82,
"score": 0.447,
"slug": "node-backend-developer",
"total_count": null
}
],
"skill_match_roles": [
{
"display_name": "DevOps Engineer",
"kra_matches": null,
"matched_count": 5,
"matched_skills": [
"CircleCI",
"Docker",
"Jenkins",
"Nomad",
"Terraform"
],
"role_id": 10,
"score": 0.2941,
"slug": "devops-engineer",
"total_count": 17
},
{
"display_name": "Backend Developer",
"kra_matches": null,
"matched_count": 5,
"matched_skills": [
"Docker",
"MySQL",
"PostgreSQL",
"Redis",
"microservices"
],
"role_id": 1,
"score": 0.2941,
"slug": "backend-engineer",
"total_count": 17
},
{
"display_name": ".NET Backend Developer",
"kra_matches": null,
"matched_count": 4,
"matched_skills": [
"Docker",
"MySQL",
"PostgreSQL",
"Redis"
],
"role_id": 83,
"score": 0.2353,
"slug": "dotnet-backend-developer",
"total_count": 17
},
{
"display_name": "Node.js Backend Developer",
"kra_matches": null,
"matched_count": 4,
"matched_skills": [
"MySQL",
"PostgreSQL",
"Redis",
"microservices"
],
"role_id": 82,
"score": 0.2353,
"slug": "node-backend-developer",
"total_count": 17
},
{
"display_name": "Ruby Backend Developer",
"kra_matches": null,
"matched_count": 4,
"matched_skills": [
"Docker",
"MySQL",
"PostgreSQL",
"Redis"
],
"role_id": 85,
"score": 0.2353,
"slug": "ruby-backend-developer",
"total_count": 17
}
]
},
"stage4_decision": {
"alias_collision_detected": false,
"case": "DOMAIN",
"chosen_role": {
"display_name": "Backend Developer",
"kra_matches": null,
"matched_count": null,
"matched_skills": null,
"role_id": 1,
"score": 0.94,
"slug": "backend-engineer",
"total_count": null
},
"confidence": 0.94,
"is_new_role": false,
"llm2_fired": false,
"llm2_reasoning": null,
"matched_dimensions": [
"Scalable backend application development",
"Database engineering",
"Containerized environments",
"Microservices architecture",
"API design and integration",
"Continuous integration and testing",
"Infrastructure as code",
"Technical leadership and mentorship"
],
"matched_kras": [
"building software applications at scale",
"developed web applications at scale",
"designing, implementing, and supporting containerized environments",
"developing code that is easily maintainable",
"well-tested",
"designing and developing APIs",
"comfortable developing in a container environment",
"experience with automated testing frameworks",
"Experience with Terraform, Nomad, and other HashiCorp technologies",
"led teams in making architectural decisions"
],
"matched_skills": [
"mainstream programming languages",
"mainstream web application",
"MySQL",
"PostgreSQL",
"MSSQL",
"Elasticsearch",
"Redis",
"Docker",
"Jenkins",
"CircleCI",
"Terraform",
"Nomad",
"HashiCorp technologies",
"RPC",
"HTTP-based APIs"
],
"new_role_display_name": null,
"new_role_slug": null,
"queued": false,
"reasoning": "Domain=Software Engineering; The JD centers on scalable software, APIs, microservices, databases, containers, CI, and infrastructure tooling, which best matches a backend engineering role.",
"sub_role": null
},
"stage5_updates": {
"centroid_n_after": 1044,
"centroid_updated": true,
"collision_log_id": null,
"new_kra_attached": null,
"new_skills_attached": [
{
"is_primary": true,
"queue_id": 15681,
"role_display_name": "Backend Developer",
"role_slug": "backend-engineer",
"skill_name": "MSSQL",
"status": "pending"
},
{
"is_primary": true,
"queue_id": 15682,
"role_display_name": "Backend Developer",
"role_slug": "backend-engineer",
"skill_name": "RPC",
"status": "pending"
},
{
"is_primary": true,
"queue_id": 15683,
"role_display_name": "Backend Developer",
"role_slug": "backend-engineer",
"skill_name": "API Gateway",
"status": "pending"
},
{
"is_primary": true,
"queue_id": 15684,
"role_display_name": "Backend Developer",
"role_slug": "backend-engineer",
"skill_name": "Automated Testing",
"status": "pending"
},
{
"is_primary": true,
"queue_id": 15685,
"role_display_name": "Backend Developer",
"role_slug": "backend-engineer",
"skill_name": "HashiCorp",
"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": 134,
"existing_alias_text": "MySQL",
"input_term": "MySQL",
"matched_canonical": {
"category_id": 3,
"display_name": "MySQL",
"id": 17,
"is_also_category": false,
"is_extractable": true,
"skill_nature": "TOOL",
"slug": "mysql",
"sub_category_id": 29,
"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": 121,
"existing_alias_text": "PostgreSQL",
"input_term": "PostgreSQL",
"matched_canonical": {
"category_id": 3,
"display_name": "PostgreSQL",
"id": 16,
"is_also_category": false,
"is_extractable": true,
"skill_nature": "TOOL",
"slug": "postgresql",
"sub_category_id": 29,
"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": 4648,
"existing_alias_text": "Elasticsearch",
"input_term": "Elasticsearch",
"matched_canonical": {
"category_id": 3,
"display_name": "Elasticsearch",
"id": 3171,
"is_also_category": false,
"is_extractable": true,
"skill_nature": "TOOL",
"slug": "elasticsearch",
"sub_category_id": 2925,
"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": 168,
"existing_alias_text": "Redis",
"input_term": "Redis",
"matched_canonical": {
"category_id": 3,
"display_name": "Redis",
"id": 31,
"is_also_category": false,
"is_extractable": true,
"skill_nature": "TOOL",
"slug": "redis",
"sub_category_id": 28,
"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": 178,
"existing_alias_text": "microservices",
"input_term": "Microservices",
"matched_canonical": {
"category_id": 1,
"display_name": "microservices",
"id": 41,
"is_also_category": false,
"is_extractable": true,
"skill_nature": "PATTERN",
"slug": "microservices",
"sub_category_id": 1,
"typical_lifespan": "EVERGREEN",
"volatility": "STABLE"
},
"matched_via": "alias"
},
{
"alias_persist_skipped_reason": "alias_text already exists for this canonical skill",
"alias_persisted": false,
"existing_alias_id": 2514,
"existing_alias_text": "API",
"input_term": "API",
"matched_canonical": {
"category_id": 2,
"display_name": "API",
"id": 1568,
"is_also_category": false,
"is_extractable": true,
"skill_nature": "CONCEPT",
"slug": "api",
"sub_category_id": 1174,
"typical_lifespan": "EVERGREEN",
"volatility": "STABLE"
},
"matched_via": "alias"
},
{
"alias_persist_skipped_reason": "alias_text already exists for this canonical skill",
"alias_persisted": false,
"existing_alias_id": 1538,
"existing_alias_text": "HTTP",
"input_term": "HTTP",
"matched_canonical": {
"category_id": 10,
"display_name": "HTTP",
"id": 935,
"is_also_category": false,
"is_extractable": true,
"skill_nature": "PROTOCOL",
"slug": "http",
"sub_category_id": 710,
"typical_lifespan": "EVERGREEN",
"volatility": "STABLE"
},
"matched_via": "alias"
},
{
"alias_persist_skipped_reason": "alias_text already exists for this canonical skill",
"alias_persisted": false,
"existing_alias_id": 198,
"existing_alias_text": "Docker",
"input_term": "Docker",
"matched_canonical": {
"category_id": 13,
"display_name": "Docker",
"id": 61,
"is_also_category": false,
"is_extractable": true,
"skill_nature": "TOOL",
"slug": "docker",
"sub_category_id": 63,
"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": 544,
"existing_alias_text": "Jenkins",
"input_term": "Jenkins",
"matched_canonical": {
"category_id": 13,
"display_name": "Jenkins",
"id": 283,
"is_also_category": false,
"is_extractable": true,
"skill_nature": "TOOL",
"slug": "jenkins",
"sub_category_id": 184,
"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": 1371,
"existing_alias_text": "CircleCI",
"input_term": "CircleCI",
"matched_canonical": {
"category_id": 9,
"display_name": "CircleCI",
"id": 826,
"is_also_category": false,
"is_extractable": true,
"skill_nature": "PLATFORM",
"slug": "circleci",
"sub_category_id": 632,
"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": 1403,
"existing_alias_text": "Nomad",
"input_term": "Nomad",
"matched_canonical": {
"category_id": 13,
"display_name": "Nomad",
"id": 855,
"is_also_category": false,
"is_extractable": true,
"skill_nature": "TOOL",
"slug": "nomad",
"sub_category_id": 580,
"typical_lifespan": "EVERGREEN",
"volatility": "EMERGING"
},
"matched_via": "alias"
}
],
"candidate_roles": [
{
"display_name": "Fullstack Developer",
"id": 435,
"rationale": null,
"role_archetype": "Engineering",
"slug": "fullstack-developer",
"source": "db"
},
{
"display_name": "Fullstack Developer",
"id": 15,
"rationale": null,
"role_archetype": null,
"slug": "full-stack-engineer",
"source": "db"
},
{
"display_name": "PHP Backend Developer",
"id": 86,
"rationale": null,
"role_archetype": "Engineering",
"slug": "php-backend-developer",
"source": "db"
},
{
"display_name": ".NET Backend Developer",
"id": 83,
"rationale": null,
"role_archetype": "Engineering",
"slug": "dotnet-backend-developer",
"source": "db"
},
{
"display_name": "Backend Developer",
"id": 1,
"rationale": null,
"role_archetype": "A Backend Engineer designs, builds, and maintains the server-side logic and data handling that power applications and services. They focus on implementing reliable business functionality, integrating with other systems, and ensuring the backend is scalable, maintainable, and observable.",
"slug": "backend-engineer",
"source": "db"
},
{
"display_name": "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": "Python Backend Developer",
"id": 80,
"rationale": null,
"role_archetype": "Engineering",
"slug": "python-backend-developer",
"source": "db"
},
{
"display_name": "Ruby Backend Developer",
"id": 85,
"rationale": null,
"role_archetype": "Engineering",
"slug": "ruby-backend-developer",
"source": "db"
},
{
"display_name": "Scala Backend Developer",
"id": 87,
"rationale": null,
"role_archetype": "Engineering",
"slug": "scala-backend-developer",
"source": "db"
},
{
"display_name": "Go Backend Developer",
"id": 81,
"rationale": null,
"role_archetype": "Engineering",
"slug": "go-backend-developer",
"source": "db"
},
{
"display_name": "Magento Dev",
"id": 231,
"rationale": null,
"role_archetype": "Engineering",
"slug": "magento-dev",
"source": "db"
},
{
"display_name": "Drupal Dev",
"id": 228,
"rationale": null,
"role_archetype": "Engineering",
"slug": "drupal-dev",
"source": "db"
},
{
"display_name": "Sitecore Dev",
"id": 233,
"rationale": null,
"role_archetype": "Engineering",
"slug": "sitecore-dev",
"source": "db"
},
{
"display_name": "Angular Frontend Developer",
"id": 90,
"rationale": null,
"role_archetype": "Engineering",
"slug": "angular-frontend-developer",
"source": "db"
},
{
"display_name": "Frontend Developer",
"id": 7,
"rationale": null,
"role_archetype": null,
"slug": "frontend-engineer",
"source": "db"
},
{
"display_name": "React Frontend Developer",
"id": 89,
"rationale": null,
"role_archetype": "Engineering",
"slug": "react-frontend-developer",
"source": "db"
},
{
"display_name": "Svelte Frontend Developer",
"id": 92,
"rationale": null,
"role_archetype": "Engineering",
"slug": "svelte-frontend-developer",
"source": "db"
},
{
"display_name": "Vue Frontend Developer",
"id": 91,
"rationale": null,
"role_archetype": "Engineering",
"slug": "vue-frontend-developer",
"source": "db"
},
{
"display_name": "Web Developer",
"id": 25,
"rationale": null,
"role_archetype": null,
"slug": "web-developer",
"source": "db"
},
{
"display_name": "Android Developer",
"id": 4,
"rationale": null,
"role_archetype": null,
"slug": "android-engineer",
"source": "db"
},
{
"display_name": "Hybrid Mobile Developer",
"id": 11,
"rationale": null,
"role_archetype": null,
"slug": "hybrid-mobile-developer",
"source": "db"
},
{
"display_name": "Native Mobile Developer",
"id": 75,
"rationale": null,
"role_archetype": "Engineering",
"slug": "native-mobile-developer",
"source": "db"
},
{
"display_name": "iOS Developer",
"id": 6,
"rationale": null,
"role_archetype": null,
"slug": "ios-engineer",
"source": "db"
},
{
"display_name": "DevOps Engineer",
"id": 10,
"rationale": null,
"role_archetype": null,
"slug": "devops-engineer",
"source": "db"
},
{
"display_name": "ML Engineer",
"id": 3,
"rationale": null,
"role_archetype": null,
"slug": "ml-engineer",
"source": "db"
},
{
"display_name": "Cloud Security Engineer",
"id": 23,
"rationale": null,
"role_archetype": null,
"slug": "cloud-security-engineer",
"source": "db"
},
{
"display_name": "Cloud Architect",
"id": 9,
"rationale": null,
"role_archetype": null,
"slug": "cloud-architect",
"source": "db"
}
],
"chosen_role": {
"display_name": "Backend Developer",
"id": 1,
"rationale": "Domain=Software Engineering; The JD centers on scalable software, APIs, microservices, databases, containers, CI, and infrastructure tooling, which best matches a backend engineering role.",
"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"
},
"dimensions": [
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Relational Data Modeling",
"id": 216,
"rationale": "Modeling and tuning relational persistence for backend features. PHP backend developers need this to shape schemas, indexes, transactions, and query-aware data structures that support application behavior.",
"slug": "relational-data-modeling",
"source": "db"
},
"input_skill": "MySQL",
"llm_role": null,
"roles_from_db": [
{
"display_name": "Fullstack Developer",
"id": 435,
"rationale": null,
"role_archetype": "Engineering",
"slug": "fullstack-developer",
"source": "db"
},
{
"display_name": "Fullstack Developer",
"id": 15,
"rationale": null,
"role_archetype": null,
"slug": "full-stack-engineer",
"source": "db"
},
{
"display_name": "PHP Backend Developer",
"id": 86,
"rationale": null,
"role_archetype": "Engineering",
"slug": "php-backend-developer",
"source": "db"
}
]
},
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Relational Database Design",
"id": 4,
"rationale": "Modeling and operating relational persistence for backend services. Includes schema design, normalization, indexing, transactions, and query tuning for operational data stores.",
"slug": "relational-database-design",
"source": "db"
},
"input_skill": "MySQL",
"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": "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": "Python Backend Developer",
"id": 80,
"rationale": null,
"role_archetype": "Engineering",
"slug": "python-backend-developer",
"source": "db"
},
{
"display_name": "Ruby Backend Developer",
"id": 85,
"rationale": null,
"role_archetype": "Engineering",
"slug": "ruby-backend-developer",
"source": "db"
},
{
"display_name": "Scala Backend Developer",
"id": 87,
"rationale": null,
"role_archetype": "Engineering",
"slug": "scala-backend-developer",
"source": "db"
}
]
},
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Relational Database Usage",
"id": 371,
"rationale": "Working effectively with operational relational databases from Go backend services. This includes schema-aware querying, indexing awareness, transactions, and understanding how service code interacts with PostgreSQL or similar systems.",
"slug": "relational-database-usage",
"source": "db"
},
"input_skill": "MySQL",
"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": "Relational Data Modeling",
"id": 216,
"rationale": "Modeling and tuning relational persistence for backend features. PHP backend developers need this to shape schemas, indexes, transactions, and query-aware data structures that support application behavior.",
"slug": "relational-data-modeling",
"source": "db"
},
"input_skill": "PostgreSQL",
"llm_role": null,
"roles_from_db": [
{
"display_name": "Fullstack Developer",
"id": 435,
"rationale": null,
"role_archetype": "Engineering",
"slug": "fullstack-developer",
"source": "db"
},
{
"display_name": "Fullstack Developer",
"id": 15,
"rationale": null,
"role_archetype": null,
"slug": "full-stack-engineer",
"source": "db"
},
{
"display_name": "PHP Backend Developer",
"id": 86,
"rationale": null,
"role_archetype": "Engineering",
"slug": "php-backend-developer",
"source": "db"
}
]
},
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Relational Database Design",
"id": 4,
"rationale": "Modeling and operating relational persistence for backend services. Includes schema design, normalization, indexing, transactions, and query tuning for operational data stores.",
"slug": "relational-database-design",
"source": "db"
},
"input_skill": "PostgreSQL",
"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": "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": "Python Backend Developer",
"id": 80,
"rationale": null,
"role_archetype": "Engineering",
"slug": "python-backend-developer",
"source": "db"
},
{
"display_name": "Ruby Backend Developer",
"id": 85,
"rationale": null,
"role_archetype": "Engineering",
"slug": "ruby-backend-developer",
"source": "db"
},
{
"display_name": "Scala Backend Developer",
"id": 87,
"rationale": null,
"role_archetype": "Engineering",
"slug": "scala-backend-developer",
"source": "db"
}
]
},
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Relational Database Usage",
"id": 371,
"rationale": "Working effectively with operational relational databases from Go backend services. This includes schema-aware querying, indexing awareness, transactions, and understanding how service code interacts with PostgreSQL or similar systems.",
"slug": "relational-database-usage",
"source": "db"
},
"input_skill": "PostgreSQL",
"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": "Magento Search and Indexing",
"id": 403,
"rationale": "Index-driven storefront data freshness and search behavior. This cluster is coherent because Magento commerce sites depend on indexing to keep catalog, price, and search results aligned with changing data.",
"slug": "magento-search-and-indexing",
"source": "db"
},
"input_skill": "Elasticsearch",
"llm_role": null,
"roles_from_db": [
{
"display_name": "Magento Dev",
"id": 231,
"rationale": null,
"role_archetype": "Engineering",
"slug": "magento-dev",
"source": "db"
}
]
},
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Search and Content Discovery",
"id": 356,
"rationale": "Implementing site search, indexing, and content discovery features in Drupal. This cluster is coherent because many Drupal sites need structured search experiences beyond basic navigation.",
"slug": "search-and-content-discovery",
"source": "db"
},
"input_skill": "Elasticsearch",
"llm_role": null,
"roles_from_db": [
{
"display_name": "Drupal Dev",
"id": 228,
"rationale": null,
"role_archetype": "Engineering",
"slug": "drupal-dev",
"source": "db"
},
{
"display_name": "Sitecore Dev",
"id": 233,
"rationale": null,
"role_archetype": "Engineering",
"slug": "sitecore-dev",
"source": "db"
}
]
},
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Caching and State Management",
"id": 7,
"rationale": "Techniques and systems for reducing latency and managing ephemeral backend state. Covers cache-aside patterns, distributed caches, session stores, and invalidation strategies.",
"slug": "caching-and-state-management",
"source": "db"
},
"input_skill": "Redis",
"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": "Kotlin Backend Developer",
"id": 84,
"rationale": null,
"role_archetype": "Engineering",
"slug": "kotlin-server-backend-developer",
"source": "db"
},
{
"display_name": "Node.js Backend Developer",
"id": 82,
"rationale": null,
"role_archetype": "Engineering",
"slug": "node-backend-developer",
"source": "db"
},
{
"display_name": "PHP Backend Developer",
"id": 86,
"rationale": null,
"role_archetype": "Engineering",
"slug": "php-backend-developer",
"source": "db"
},
{
"display_name": "Python Backend Developer",
"id": 80,
"rationale": null,
"role_archetype": "Engineering",
"slug": "python-backend-developer",
"source": "db"
},
{
"display_name": "Ruby Backend Developer",
"id": 85,
"rationale": null,
"role_archetype": "Engineering",
"slug": "ruby-backend-developer",
"source": "db"
},
{
"display_name": "Scala Backend Developer",
"id": 87,
"rationale": null,
"role_archetype": "Engineering",
"slug": "scala-backend-developer",
"source": "db"
}
]
},
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Magento Caching and Performance",
"id": 404,
"rationale": "Performance tuning specific to Magento storefronts and their rendering pipeline. This includes cache layers, page generation costs, and practical optimizations that preserve upgradeability while improving shopper experience.",
"slug": "magento-caching-and-performance",
"source": "db"
},
"input_skill": "Redis",
"llm_role": null,
"roles_from_db": [
{
"display_name": "Magento Dev",
"id": 231,
"rationale": null,
"role_archetype": "Engineering",
"slug": "magento-dev",
"source": "db"
}
]
},
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Microservices and Distributed Systems",
"id": 9,
"rationale": "Architectural patterns for decomposed backend systems and the operational concerns they introduce. Covers service boundaries, consistency tradeoffs, retries, circuit breakers, and distributed coordination.",
"slug": "microservices-and-distributed-systems",
"source": "db"
},
"input_skill": "Microservices",
"llm_role": null,
"roles_from_db": [
{
"display_name": "Backend Developer",
"id": 1,
"rationale": null,
"role_archetype": "A Backend Engineer designs, builds, and maintains the server-side logic and data handling that power applications and services. They focus on implementing reliable business functionality, integrating with other systems, and ensuring the backend is scalable, maintainable, and observable.",
"slug": "backend-engineer",
"source": "db"
},
{
"display_name": "Node.js Backend Developer",
"id": 82,
"rationale": null,
"role_archetype": "Engineering",
"slug": "node-backend-developer",
"source": "db"
},
{
"display_name": "Scala Backend Developer",
"id": 87,
"rationale": null,
"role_archetype": "Engineering",
"slug": "scala-backend-developer",
"source": "db"
}
]
},
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "API Integration and Data Fetching",
"id": 127,
"rationale": "Client-side integration with backend endpoints and third-party services, including request shaping, response handling, and synchronization with UI state. This is central to frontend work because most screens depend on remote data.",
"slug": "api-integration-and-data-fetching",
"source": "db"
},
"input_skill": "API",
"llm_role": null,
"roles_from_db": [
{
"display_name": "Angular Frontend Developer",
"id": 90,
"rationale": null,
"role_archetype": "Engineering",
"slug": "angular-frontend-developer",
"source": "db"
},
{
"display_name": "Frontend Developer",
"id": 7,
"rationale": null,
"role_archetype": null,
"slug": "frontend-engineer",
"source": "db"
},
{
"display_name": "Fullstack Developer",
"id": 435,
"rationale": null,
"role_archetype": "Engineering",
"slug": "fullstack-developer",
"source": "db"
},
{
"display_name": "Fullstack Developer",
"id": 15,
"rationale": null,
"role_archetype": null,
"slug": "full-stack-engineer",
"source": "db"
},
{
"display_name": "React Frontend Developer",
"id": 89,
"rationale": null,
"role_archetype": "Engineering",
"slug": "react-frontend-developer",
"source": "db"
},
{
"display_name": "Svelte Frontend Developer",
"id": 92,
"rationale": null,
"role_archetype": "Engineering",
"slug": "svelte-frontend-developer",
"source": "db"
},
{
"display_name": "Vue Frontend Developer",
"id": 91,
"rationale": null,
"role_archetype": "Engineering",
"slug": "vue-frontend-developer",
"source": "db"
},
{
"display_name": "Web Developer",
"id": 25,
"rationale": null,
"role_archetype": null,
"slug": "web-developer",
"source": "db"
}
]
},
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Networking and API Integration",
"id": 84,
"rationale": "Client-side HTTP communication with backend services, including request construction, response parsing, retries, and error handling. iOS engineers use this to connect native screens to server-owned APIs.",
"slug": "networking-and-api-integration",
"source": "db"
},
"input_skill": "HTTP",
"llm_role": null,
"roles_from_db": [
{
"display_name": "Android Developer",
"id": 4,
"rationale": null,
"role_archetype": null,
"slug": "android-engineer",
"source": "db"
},
{
"display_name": "Hybrid Mobile Developer",
"id": 11,
"rationale": null,
"role_archetype": null,
"slug": "hybrid-mobile-developer",
"source": "db"
},
{
"display_name": "Native Mobile Developer",
"id": 75,
"rationale": null,
"role_archetype": "Engineering",
"slug": "native-mobile-developer",
"source": "db"
},
{
"display_name": "iOS Developer",
"id": 6,
"rationale": null,
"role_archetype": null,
"slug": "ios-engineer",
"source": "db"
}
]
},
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Containerization and Image Builds",
"id": 152,
"rationale": "Container image creation, tagging, hardening, and registry workflows used to package services for deployment. This is coherent because DevOps often owns the build-to-image path that feeds runtime environments.",
"slug": "containerization-and-image-builds",
"source": "db"
},
"input_skill": "Docker",
"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": "Deployment and Cloud Platforms",
"id": 418,
"rationale": "Platform-as-a-Service and container environments for deploying Ruby applications.",
"slug": "deployment-and-cloud-platforms",
"source": "db"
},
"input_skill": "Docker",
"llm_role": null,
"roles_from_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": "Deployment and Runtime Configuration",
"id": 13,
"rationale": "Configuration and release artifacts that control how backend services run in environments. Includes environment variables, manifests, feature flags, and release-safe configuration management.",
"slug": "deployment-and-runtime-configuration",
"source": "db"
},
"input_skill": "Docker",
"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": "Go Backend Developer",
"id": 81,
"rationale": null,
"role_archetype": "Engineering",
"slug": "go-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": "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": "Jenkins",
"llm_role": null,
"roles_from_db": [
{
"display_name": "DevOps Engineer",
"id": 10,
"rationale": null,
"role_archetype": null,
"slug": "devops-engineer",
"source": "db"
}
]
},
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "CI/CD for Machine Learning",
"id": 56,
"rationale": "Tools and platforms for automating ML model integration, testing, and deployment pipelines.",
"slug": "ci-cd-for-machine-learning",
"source": "db"
},
"input_skill": "Jenkins",
"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": "CircleCI",
"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": "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": "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": "Nomad",
"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"
}
]
}
],
"input_final_skills": [
"MySQL",
"PostgreSQL",
"MSSQL",
"Elasticsearch",
"Redis",
"Microservices",
"API",
"RPC",
"HTTP",
"API Gateway",
"Docker",
"Jenkins",
"CircleCI",
"Automated Testing",
"Terraform",
"Nomad",
"HashiCorp"
],
"input_llm_skills": [
"MySQL",
"PostgreSQL",
"MSSQL",
"Elasticsearch",
"Redis",
"Microservices",
"API",
"RPC",
"HTTP",
"API Gateway",
"Docker",
"Jenkins",
"CircleCI",
"Automated Testing",
"Terraform",
"Nomad",
"HashiCorp"
],
"new_aliases_persisted": 0,
"run_id": "aa83281f-1ea5-4d0d-8b2b-5233ba238859",
"skills_detail": [
{
"aliases_in_db": [
{
"alias_text": "MySQL",
"alias_type": "CANONICAL",
"id": 134,
"is_primary": true,
"match_strategy": "CASE_INSENSITIVE"
}
],
"canonical": {
"category_id": 3,
"display_name": "MySQL",
"id": 17,
"is_also_category": false,
"is_extractable": true,
"skill_nature": "TOOL",
"slug": "mysql",
"sub_category_id": 29,
"typical_lifespan": "EVERGREEN",
"volatility": "STABLE"
},
"dimensions": [
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Relational Data Modeling",
"id": 216,
"rationale": "Modeling and tuning relational persistence for backend features. PHP backend developers need this to shape schemas, indexes, transactions, and query-aware data structures that support application behavior.",
"slug": "relational-data-modeling",
"source": "db"
},
"input_skill": "MySQL",
"llm_role": null,
"roles_from_db": [
{
"display_name": "Fullstack Developer",
"id": 435,
"rationale": null,
"role_archetype": "Engineering",
"slug": "fullstack-developer",
"source": "db"
},
{
"display_name": "Fullstack Developer",
"id": 15,
"rationale": null,
"role_archetype": null,
"slug": "full-stack-engineer",
"source": "db"
},
{
"display_name": "PHP Backend Developer",
"id": 86,
"rationale": null,
"role_archetype": "Engineering",
"slug": "php-backend-developer",
"source": "db"
}
]
},
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Relational Database Design",
"id": 4,
"rationale": "Modeling and operating relational persistence for backend services. Includes schema design, normalization, indexing, transactions, and query tuning for operational data stores.",
"slug": "relational-database-design",
"source": "db"
},
"input_skill": "MySQL",
"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": "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": "Python Backend Developer",
"id": 80,
"rationale": null,
"role_archetype": "Engineering",
"slug": "python-backend-developer",
"source": "db"
},
{
"display_name": "Ruby Backend Developer",
"id": 85,
"rationale": null,
"role_archetype": "Engineering",
"slug": "ruby-backend-developer",
"source": "db"
},
{
"display_name": "Scala Backend Developer",
"id": 87,
"rationale": null,
"role_archetype": "Engineering",
"slug": "scala-backend-developer",
"source": "db"
}
]
},
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Relational Database Usage",
"id": 371,
"rationale": "Working effectively with operational relational databases from Go backend services. This includes schema-aware querying, indexing awareness, transactions, and understanding how service code interacts with PostgreSQL or similar systems.",
"slug": "relational-database-usage",
"source": "db"
},
"input_skill": "MySQL",
"llm_role": null,
"roles_from_db": [
{
"display_name": "Go Backend Developer",
"id": 81,
"rationale": null,
"role_archetype": "Engineering",
"slug": "go-backend-developer",
"source": "db"
}
]
}
],
"input_skill": "MySQL",
"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": "PostgreSQL",
"alias_type": "CANONICAL",
"id": 121,
"is_primary": true,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "PG 13",
"alias_type": "VERSION",
"id": 122,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "PG 14",
"alias_type": "VERSION",
"id": 123,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "PG 15",
"alias_type": "VERSION",
"id": 124,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "PG 16",
"alias_type": "VERSION",
"id": 125,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "PostgreSQL 13",
"alias_type": "VERSION",
"id": 130,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "PostgreSQL 14",
"alias_type": "VERSION",
"id": 131,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "PostgreSQL 15",
"alias_type": "VERSION",
"id": 132,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "PostgreSQL 16",
"alias_type": "VERSION",
"id": 133,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "Postgres 13",
"alias_type": "VERSION",
"id": 126,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "Postgres 14",
"alias_type": "VERSION",
"id": 127,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "Postgres 15",
"alias_type": "VERSION",
"id": 128,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "Postgres 16",
"alias_type": "VERSION",
"id": 129,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "pg10",
"alias_type": "VERSION",
"id": 4714,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "pg11",
"alias_type": "VERSION",
"id": 4715,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "pg12",
"alias_type": "VERSION",
"id": 4716,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "pg13",
"alias_type": "VERSION",
"id": 4717,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "pg14",
"alias_type": "VERSION",
"id": 4718,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "pg15",
"alias_type": "VERSION",
"id": 4719,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "pg16",
"alias_type": "VERSION",
"id": 4720,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "postgres",
"alias_type": "VERSION",
"id": 4721,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "postgresql 10",
"alias_type": "VERSION",
"id": 4729,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "postgresql 11",
"alias_type": "VERSION",
"id": 4730,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "postgresql 12",
"alias_type": "VERSION",
"id": 4731,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "postgresql 13",
"alias_type": "VERSION",
"id": 4732,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "postgresql 14",
"alias_type": "VERSION",
"id": 4733,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "postgresql 15",
"alias_type": "VERSION",
"id": 4734,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "postgresql 16",
"alias_type": "VERSION",
"id": 4735,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "postgresql-16",
"alias_type": "VERSION",
"id": 4736,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "postgresql10",
"alias_type": "VERSION",
"id": 4722,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "postgresql11",
"alias_type": "VERSION",
"id": 4723,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "postgresql12",
"alias_type": "VERSION",
"id": 4724,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "postgresql13",
"alias_type": "VERSION",
"id": 4725,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "postgresql14",
"alias_type": "VERSION",
"id": 4726,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "postgresql15",
"alias_type": "VERSION",
"id": 4727,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "postgresql16",
"alias_type": "VERSION",
"id": 4728,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
}
],
"canonical": {
"category_id": 3,
"display_name": "PostgreSQL",
"id": 16,
"is_also_category": false,
"is_extractable": true,
"skill_nature": "TOOL",
"slug": "postgresql",
"sub_category_id": 29,
"typical_lifespan": "EVERGREEN",
"volatility": "STABLE"
},
"dimensions": [
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Relational Data Modeling",
"id": 216,
"rationale": "Modeling and tuning relational persistence for backend features. PHP backend developers need this to shape schemas, indexes, transactions, and query-aware data structures that support application behavior.",
"slug": "relational-data-modeling",
"source": "db"
},
"input_skill": "PostgreSQL",
"llm_role": null,
"roles_from_db": [
{
"display_name": "Fullstack Developer",
"id": 435,
"rationale": null,
"role_archetype": "Engineering",
"slug": "fullstack-developer",
"source": "db"
},
{
"display_name": "Fullstack Developer",
"id": 15,
"rationale": null,
"role_archetype": null,
"slug": "full-stack-engineer",
"source": "db"
},
{
"display_name": "PHP Backend Developer",
"id": 86,
"rationale": null,
"role_archetype": "Engineering",
"slug": "php-backend-developer",
"source": "db"
}
]
},
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Relational Database Design",
"id": 4,
"rationale": "Modeling and operating relational persistence for backend services. Includes schema design, normalization, indexing, transactions, and query tuning for operational data stores.",
"slug": "relational-database-design",
"source": "db"
},
"input_skill": "PostgreSQL",
"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": "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": "Python Backend Developer",
"id": 80,
"rationale": null,
"role_archetype": "Engineering",
"slug": "python-backend-developer",
"source": "db"
},
{
"display_name": "Ruby Backend Developer",
"id": 85,
"rationale": null,
"role_archetype": "Engineering",
"slug": "ruby-backend-developer",
"source": "db"
},
{
"display_name": "Scala Backend Developer",
"id": 87,
"rationale": null,
"role_archetype": "Engineering",
"slug": "scala-backend-developer",
"source": "db"
}
]
},
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Relational Database Usage",
"id": 371,
"rationale": "Working effectively with operational relational databases from Go backend services. This includes schema-aware querying, indexing awareness, transactions, and understanding how service code interacts with PostgreSQL or similar systems.",
"slug": "relational-database-usage",
"source": "db"
},
"input_skill": "PostgreSQL",
"llm_role": null,
"roles_from_db": [
{
"display_name": "Go Backend Developer",
"id": 81,
"rationale": null,
"role_archetype": "Engineering",
"slug": "go-backend-developer",
"source": "db"
}
]
}
],
"input_skill": "PostgreSQL",
"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": "MSSQL",
"matched_via": null,
"new_alias_persisted": false,
"new_alias_text": null,
"new_skill_meta": {
"derived": {
"category": "Databases",
"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": "mssql",
"split_log": [],
"typed": null,
"warnings": []
},
"source_tag": "llm",
"was_in_llm_skills": true
},
{
"aliases_in_db": [
{
"alias_text": "Elasticsearch",
"alias_type": "CANONICAL",
"id": 4648,
"is_primary": true,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "ES",
"alias_type": "VERSION",
"id": 4649,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "ElasticSearch",
"alias_type": "VERSION",
"id": 4650,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "Elasticsearch 6",
"alias_type": "VERSION",
"id": 4651,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "Elasticsearch 6.x",
"alias_type": "VERSION",
"id": 4657,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "Elasticsearch 7",
"alias_type": "VERSION",
"id": 4652,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "Elasticsearch 7.x",
"alias_type": "VERSION",
"id": 4658,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "Elasticsearch 8",
"alias_type": "VERSION",
"id": 4653,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "Elasticsearch 8.x",
"alias_type": "VERSION",
"id": 4659,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "Elasticsearch v6",
"alias_type": "VERSION",
"id": 4654,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "Elasticsearch v7",
"alias_type": "VERSION",
"id": 4655,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "Elasticsearch v8",
"alias_type": "VERSION",
"id": 4656,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
}
],
"canonical": {
"category_id": 3,
"display_name": "Elasticsearch",
"id": 3171,
"is_also_category": false,
"is_extractable": true,
"skill_nature": "TOOL",
"slug": "elasticsearch",
"sub_category_id": 2925,
"typical_lifespan": "EVERGREEN",
"volatility": "STABLE"
},
"dimensions": [
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Magento Search and Indexing",
"id": 403,
"rationale": "Index-driven storefront data freshness and search behavior. This cluster is coherent because Magento commerce sites depend on indexing to keep catalog, price, and search results aligned with changing data.",
"slug": "magento-search-and-indexing",
"source": "db"
},
"input_skill": "Elasticsearch",
"llm_role": null,
"roles_from_db": [
{
"display_name": "Magento Dev",
"id": 231,
"rationale": null,
"role_archetype": "Engineering",
"slug": "magento-dev",
"source": "db"
}
]
},
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Search and Content Discovery",
"id": 356,
"rationale": "Implementing site search, indexing, and content discovery features in Drupal. This cluster is coherent because many Drupal sites need structured search experiences beyond basic navigation.",
"slug": "search-and-content-discovery",
"source": "db"
},
"input_skill": "Elasticsearch",
"llm_role": null,
"roles_from_db": [
{
"display_name": "Drupal Dev",
"id": 228,
"rationale": null,
"role_archetype": "Engineering",
"slug": "drupal-dev",
"source": "db"
},
{
"display_name": "Sitecore Dev",
"id": 233,
"rationale": null,
"role_archetype": "Engineering",
"slug": "sitecore-dev",
"source": "db"
}
]
}
],
"input_skill": "Elasticsearch",
"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": "Redis",
"alias_type": "CANONICAL",
"id": 168,
"is_primary": true,
"match_strategy": "CASE_INSENSITIVE"
}
],
"canonical": {
"category_id": 3,
"display_name": "Redis",
"id": 31,
"is_also_category": false,
"is_extractable": true,
"skill_nature": "TOOL",
"slug": "redis",
"sub_category_id": 28,
"typical_lifespan": "EVERGREEN",
"volatility": "STABLE"
},
"dimensions": [
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Caching and State Management",
"id": 7,
"rationale": "Techniques and systems for reducing latency and managing ephemeral backend state. Covers cache-aside patterns, distributed caches, session stores, and invalidation strategies.",
"slug": "caching-and-state-management",
"source": "db"
},
"input_skill": "Redis",
"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": "Kotlin Backend Developer",
"id": 84,
"rationale": null,
"role_archetype": "Engineering",
"slug": "kotlin-server-backend-developer",
"source": "db"
},
{
"display_name": "Node.js Backend Developer",
"id": 82,
"rationale": null,
"role_archetype": "Engineering",
"slug": "node-backend-developer",
"source": "db"
},
{
"display_name": "PHP Backend Developer",
"id": 86,
"rationale": null,
"role_archetype": "Engineering",
"slug": "php-backend-developer",
"source": "db"
},
{
"display_name": "Python Backend Developer",
"id": 80,
"rationale": null,
"role_archetype": "Engineering",
"slug": "python-backend-developer",
"source": "db"
},
{
"display_name": "Ruby Backend Developer",
"id": 85,
"rationale": null,
"role_archetype": "Engineering",
"slug": "ruby-backend-developer",
"source": "db"
},
{
"display_name": "Scala Backend Developer",
"id": 87,
"rationale": null,
"role_archetype": "Engineering",
"slug": "scala-backend-developer",
"source": "db"
}
]
},
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Magento Caching and Performance",
"id": 404,
"rationale": "Performance tuning specific to Magento storefronts and their rendering pipeline. This includes cache layers, page generation costs, and practical optimizations that preserve upgradeability while improving shopper experience.",
"slug": "magento-caching-and-performance",
"source": "db"
},
"input_skill": "Redis",
"llm_role": null,
"roles_from_db": [
{
"display_name": "Magento Dev",
"id": 231,
"rationale": null,
"role_archetype": "Engineering",
"slug": "magento-dev",
"source": "db"
}
]
}
],
"input_skill": "Redis",
"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": "microservices",
"alias_type": "CANONICAL",
"id": 178,
"is_primary": true,
"match_strategy": "CASE_INSENSITIVE"
}
],
"canonical": {
"category_id": 1,
"display_name": "microservices",
"id": 41,
"is_also_category": false,
"is_extractable": true,
"skill_nature": "PATTERN",
"slug": "microservices",
"sub_category_id": 1,
"typical_lifespan": "EVERGREEN",
"volatility": "STABLE"
},
"dimensions": [
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Microservices and Distributed Systems",
"id": 9,
"rationale": "Architectural patterns for decomposed backend systems and the operational concerns they introduce. Covers service boundaries, consistency tradeoffs, retries, circuit breakers, and distributed coordination.",
"slug": "microservices-and-distributed-systems",
"source": "db"
},
"input_skill": "Microservices",
"llm_role": null,
"roles_from_db": [
{
"display_name": "Backend Developer",
"id": 1,
"rationale": null,
"role_archetype": "A Backend Engineer designs, builds, and maintains the server-side logic and data handling that power applications and services. They focus on implementing reliable business functionality, integrating with other systems, and ensuring the backend is scalable, maintainable, and observable.",
"slug": "backend-engineer",
"source": "db"
},
{
"display_name": "Node.js Backend Developer",
"id": 82,
"rationale": null,
"role_archetype": "Engineering",
"slug": "node-backend-developer",
"source": "db"
},
{
"display_name": "Scala Backend Developer",
"id": 87,
"rationale": null,
"role_archetype": "Engineering",
"slug": "scala-backend-developer",
"source": "db"
}
]
}
],
"input_skill": "Microservices",
"matched_via": "alias",
"new_alias_persisted": false,
"new_alias_text": null,
"new_skill_meta": null,
"source_tag": "db",
"was_in_llm_skills": true
},
{
"aliases_in_db": [
{
"alias_text": "API",
"alias_type": "CANONICAL",
"id": 2514,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
}
],
"canonical": {
"category_id": 2,
"display_name": "API",
"id": 1568,
"is_also_category": false,
"is_extractable": true,
"skill_nature": "CONCEPT",
"slug": "api",
"sub_category_id": 1174,
"typical_lifespan": "EVERGREEN",
"volatility": "STABLE"
},
"dimensions": [
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "API Integration and Data Fetching",
"id": 127,
"rationale": "Client-side integration with backend endpoints and third-party services, including request shaping, response handling, and synchronization with UI state. This is central to frontend work because most screens depend on remote data.",
"slug": "api-integration-and-data-fetching",
"source": "db"
},
"input_skill": "API",
"llm_role": null,
"roles_from_db": [
{
"display_name": "Angular Frontend Developer",
"id": 90,
"rationale": null,
"role_archetype": "Engineering",
"slug": "angular-frontend-developer",
"source": "db"
},
{
"display_name": "Frontend Developer",
"id": 7,
"rationale": null,
"role_archetype": null,
"slug": "frontend-engineer",
"source": "db"
},
{
"display_name": "Fullstack Developer",
"id": 435,
"rationale": null,
"role_archetype": "Engineering",
"slug": "fullstack-developer",
"source": "db"
},
{
"display_name": "Fullstack Developer",
"id": 15,
"rationale": null,
"role_archetype": null,
"slug": "full-stack-engineer",
"source": "db"
},
{
"display_name": "React Frontend Developer",
"id": 89,
"rationale": null,
"role_archetype": "Engineering",
"slug": "react-frontend-developer",
"source": "db"
},
{
"display_name": "Svelte Frontend Developer",
"id": 92,
"rationale": null,
"role_archetype": "Engineering",
"slug": "svelte-frontend-developer",
"source": "db"
},
{
"display_name": "Vue Frontend Developer",
"id": 91,
"rationale": null,
"role_archetype": "Engineering",
"slug": "vue-frontend-developer",
"source": "db"
},
{
"display_name": "Web Developer",
"id": 25,
"rationale": null,
"role_archetype": null,
"slug": "web-developer",
"source": "db"
}
]
}
],
"input_skill": "API",
"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": "RPC",
"matched_via": null,
"new_alias_persisted": false,
"new_alias_text": null,
"new_skill_meta": {
"derived": {
"category": "Concepts",
"skill_nature": "CONCEPT",
"sub_category": "general",
"typical_lifespan": "EVERGREEN",
"version_strategy": "UNVERSIONED",
"volatility": "STABLE"
},
"enrichment": null,
"keep_log": [],
"locked_dimensions": [],
"merge_log": [],
"placed": null,
"relationships": null,
"skill_id": "rpc",
"split_log": [],
"typed": null,
"warnings": []
},
"source_tag": "llm",
"was_in_llm_skills": true
},
{
"aliases_in_db": [
{
"alias_text": "HTTP",
"alias_type": "CANONICAL",
"id": 1538,
"is_primary": true,
"match_strategy": "CASE_INSENSITIVE"
}
],
"canonical": {
"category_id": 10,
"display_name": "HTTP",
"id": 935,
"is_also_category": false,
"is_extractable": true,
"skill_nature": "PROTOCOL",
"slug": "http",
"sub_category_id": 710,
"typical_lifespan": "EVERGREEN",
"volatility": "STABLE"
},
"dimensions": [
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Networking and API Integration",
"id": 84,
"rationale": "Client-side HTTP communication with backend services, including request construction, response parsing, retries, and error handling. iOS engineers use this to connect native screens to server-owned APIs.",
"slug": "networking-and-api-integration",
"source": "db"
},
"input_skill": "HTTP",
"llm_role": null,
"roles_from_db": [
{
"display_name": "Android Developer",
"id": 4,
"rationale": null,
"role_archetype": null,
"slug": "android-engineer",
"source": "db"
},
{
"display_name": "Hybrid Mobile Developer",
"id": 11,
"rationale": null,
"role_archetype": null,
"slug": "hybrid-mobile-developer",
"source": "db"
},
{
"display_name": "Native Mobile Developer",
"id": 75,
"rationale": null,
"role_archetype": "Engineering",
"slug": "native-mobile-developer",
"source": "db"
},
{
"display_name": "iOS Developer",
"id": 6,
"rationale": null,
"role_archetype": null,
"slug": "ios-engineer",
"source": "db"
}
]
}
],
"input_skill": "HTTP",
"matched_via": "alias",
"new_alias_persisted": false,
"new_alias_text": null,
"new_skill_meta": null,
"source_tag": "db",
"was_in_llm_skills": true
},
{
"aliases_in_db": [],
"canonical": null,
"dimensions": [],
"input_skill": "API Gateway",
"matched_via": null,
"new_alias_persisted": false,
"new_alias_text": null,
"new_skill_meta": {
"derived": {
"category": "Web Frameworks",
"skill_nature": "TOOL",
"sub_category": "general",
"typical_lifespan": "MULTI_YEAR",
"version_strategy": "UNVERSIONED",
"volatility": "MEDIUM"
},
"enrichment": null,
"keep_log": [],
"locked_dimensions": [],
"merge_log": [],
"placed": null,
"relationships": null,
"skill_id": "api-gateway",
"split_log": [],
"typed": null,
"warnings": []
},
"source_tag": "llm",
"was_in_llm_skills": true
},
{
"aliases_in_db": [
{
"alias_text": "Docker",
"alias_type": "CANONICAL",
"id": 198,
"is_primary": true,
"match_strategy": "CASE_INSENSITIVE"
}
],
"canonical": {
"category_id": 13,
"display_name": "Docker",
"id": 61,
"is_also_category": false,
"is_extractable": true,
"skill_nature": "TOOL",
"slug": "docker",
"sub_category_id": 63,
"typical_lifespan": "EVERGREEN",
"volatility": "STABLE"
},
"dimensions": [
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Containerization and Image Builds",
"id": 152,
"rationale": "Container image creation, tagging, hardening, and registry workflows used to package services for deployment. This is coherent because DevOps often owns the build-to-image path that feeds runtime environments.",
"slug": "containerization-and-image-builds",
"source": "db"
},
"input_skill": "Docker",
"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": "Deployment and Cloud Platforms",
"id": 418,
"rationale": "Platform-as-a-Service and container environments for deploying Ruby applications.",
"slug": "deployment-and-cloud-platforms",
"source": "db"
},
"input_skill": "Docker",
"llm_role": null,
"roles_from_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": "Deployment and Runtime Configuration",
"id": 13,
"rationale": "Configuration and release artifacts that control how backend services run in environments. Includes environment variables, manifests, feature flags, and release-safe configuration management.",
"slug": "deployment-and-runtime-configuration",
"source": "db"
},
"input_skill": "Docker",
"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": "Go Backend Developer",
"id": 81,
"rationale": null,
"role_archetype": "Engineering",
"slug": "go-backend-developer",
"source": "db"
},
{
"display_name": "PHP Backend Developer",
"id": 86,
"rationale": null,
"role_archetype": "Engineering",
"slug": "php-backend-developer",
"source": "db"
}
]
}
],
"input_skill": "Docker",
"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": "Jenkins",
"alias_type": "CANONICAL",
"id": 544,
"is_primary": true,
"match_strategy": "CASE_INSENSITIVE"
}
],
"canonical": {
"category_id": 13,
"display_name": "Jenkins",
"id": 283,
"is_also_category": false,
"is_extractable": true,
"skill_nature": "TOOL",
"slug": "jenkins",
"sub_category_id": 184,
"typical_lifespan": "EVERGREEN",
"volatility": "STABLE"
},
"dimensions": [
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "CI/CD Pipeline Platforms",
"id": 150,
"rationale": "Systems used to define, run, and maintain automated build and deployment workflows. This cluster is coherent because the role owns delivery automation end to end, including pipeline reliability and promotion logic.",
"slug": "ci-cd-pipeline-platforms",
"source": "db"
},
"input_skill": "Jenkins",
"llm_role": null,
"roles_from_db": [
{
"display_name": "DevOps Engineer",
"id": 10,
"rationale": null,
"role_archetype": null,
"slug": "devops-engineer",
"source": "db"
}
]
},
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "CI/CD for Machine Learning",
"id": 56,
"rationale": "Tools and platforms for automating ML model integration, testing, and deployment pipelines.",
"slug": "ci-cd-for-machine-learning",
"source": "db"
},
"input_skill": "Jenkins",
"llm_role": null,
"roles_from_db": [
{
"display_name": "ML Engineer",
"id": 3,
"rationale": null,
"role_archetype": null,
"slug": "ml-engineer",
"source": "db"
}
]
}
],
"input_skill": "Jenkins",
"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": "CircleCI",
"alias_type": "CANONICAL",
"id": 1371,
"is_primary": true,
"match_strategy": "CASE_INSENSITIVE"
}
],
"canonical": {
"category_id": 9,
"display_name": "CircleCI",
"id": 826,
"is_also_category": false,
"is_extractable": true,
"skill_nature": "PLATFORM",
"slug": "circleci",
"sub_category_id": 632,
"typical_lifespan": "EVERGREEN",
"volatility": "STABLE"
},
"dimensions": [
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "CI/CD Pipeline Platforms",
"id": 150,
"rationale": "Systems used to define, run, and maintain automated build and deployment workflows. This cluster is coherent because the role owns delivery automation end to end, including pipeline reliability and promotion logic.",
"slug": "ci-cd-pipeline-platforms",
"source": "db"
},
"input_skill": "CircleCI",
"llm_role": null,
"roles_from_db": [
{
"display_name": "DevOps Engineer",
"id": 10,
"rationale": null,
"role_archetype": null,
"slug": "devops-engineer",
"source": "db"
}
]
}
],
"input_skill": "CircleCI",
"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": "Automated Testing",
"matched_via": null,
"new_alias_persisted": false,
"new_alias_text": null,
"new_skill_meta": {
"derived": {
"category": "Testing Tools",
"skill_nature": "PRACTICE",
"sub_category": "general",
"typical_lifespan": "MULTI_YEAR",
"version_strategy": "UNVERSIONED",
"volatility": "MEDIUM"
},
"enrichment": null,
"keep_log": [],
"locked_dimensions": [],
"merge_log": [],
"placed": null,
"relationships": null,
"skill_id": "automated-testing",
"split_log": [],
"typed": null,
"warnings": []
},
"source_tag": "llm",
"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": "Nomad",
"alias_type": "CANONICAL",
"id": 1403,
"is_primary": true,
"match_strategy": "CASE_INSENSITIVE"
}
],
"canonical": {
"category_id": 13,
"display_name": "Nomad",
"id": 855,
"is_also_category": false,
"is_extractable": true,
"skill_nature": "TOOL",
"slug": "nomad",
"sub_category_id": 580,
"typical_lifespan": "EVERGREEN",
"volatility": "EMERGING"
},
"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": "Nomad",
"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"
}
]
}
],
"input_skill": "Nomad",
"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": "HashiCorp",
"matched_via": null,
"new_alias_persisted": false,
"new_alias_text": null,
"new_skill_meta": {
"derived": {
"category": "Infrastructure 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": "hashicorp",
"split_log": [],
"typed": null,
"warnings": []
},
"source_tag": "llm",
"was_in_llm_skills": true
}
],
"unmatched_skills": [
"MSSQL",
"RPC",
"API Gateway",
"Automated Testing",
"HashiCorp"
]
}
API 3 — final-role-output
{
"chosen_role": {
"display_name": "Backend Developer",
"id": 1,
"rationale": "Domain=Software Engineering; The JD centers on scalable software, APIs, microservices, databases, containers, CI, and infrastructure tooling, which best matches a backend engineering role.",
"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"
},
"chosen_role_resolution": "in_db",
"final_input_skills": [
{
"skill": "MySQL",
"tag": "in_db"
},
{
"skill": "PostgreSQL",
"tag": "in_db"
},
{
"skill": "MSSQL",
"tag": "new"
},
{
"skill": "Elasticsearch",
"tag": "in_db"
},
{
"skill": "Redis",
"tag": "in_db"
},
{
"skill": "Microservices",
"tag": "in_db"
},
{
"skill": "API",
"tag": "in_db"
},
{
"skill": "RPC",
"tag": "new"
},
{
"skill": "HTTP",
"tag": "in_db"
},
{
"skill": "API Gateway",
"tag": "new"
},
{
"skill": "Docker",
"tag": "in_db"
},
{
"skill": "Jenkins",
"tag": "in_db"
},
{
"skill": "CircleCI",
"tag": "in_db"
},
{
"skill": "Automated Testing",
"tag": "new"
},
{
"skill": "Terraform",
"tag": "in_db"
},
{
"skill": "Nomad",
"tag": "in_db"
},
{
"skill": "HashiCorp",
"tag": "new"
}
],
"llm_cost_api1_usd": null,
"llm_cost_api2_usd": null,
"llm_cost_api3_usd": null,
"llm_cost_total_usd": null,
"persistence": {
"items": [
{
"chosen_role_id": 1,
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Relational Data Modeling",
"id": 216,
"rationale": "Modeling and tuning relational persistence for backend features. PHP backend developers need this to shape schemas, indexes, transactions, and query-aware data structures that support application behavior.",
"slug": "relational-data-modeling",
"source": "db"
},
"dimension_id": 216,
"input_skill": "MySQL",
"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": "Fullstack Developer",
"id": 435,
"rationale": null,
"role_archetype": "Engineering",
"slug": "fullstack-developer",
"source": "db"
},
{
"display_name": "Fullstack Developer",
"id": 15,
"rationale": null,
"role_archetype": null,
"slug": "full-stack-engineer",
"source": "db"
},
{
"display_name": "PHP Backend Developer",
"id": 86,
"rationale": null,
"role_archetype": "Engineering",
"slug": "php-backend-developer",
"source": "db"
}
],
"skill_dimension_saved": true,
"skill_id": 17,
"skill_tag": "in_db",
"skipped_reason": null
},
{
"chosen_role_id": 1,
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Relational Database Design",
"id": 4,
"rationale": "Modeling and operating relational persistence for backend services. Includes schema design, normalization, indexing, transactions, and query tuning for operational data stores.",
"slug": "relational-database-design",
"source": "db"
},
"dimension_id": 4,
"input_skill": "MySQL",
"llm_role": null,
"matched_chosen_role": true,
"outcome_line": "Existing dimension (library) \u00b7 Role\u2194dimension saved",
"role_dimension_saved": true,
"roles_from_db": [
{
"display_name": ".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": "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": "Python Backend Developer",
"id": 80,
"rationale": null,
"role_archetype": "Engineering",
"slug": "python-backend-developer",
"source": "db"
},
{
"display_name": "Ruby Backend Developer",
"id": 85,
"rationale": null,
"role_archetype": "Engineering",
"slug": "ruby-backend-developer",
"source": "db"
},
{
"display_name": "Scala Backend Developer",
"id": 87,
"rationale": null,
"role_archetype": "Engineering",
"slug": "scala-backend-developer",
"source": "db"
}
],
"skill_dimension_saved": true,
"skill_id": 17,
"skill_tag": "in_db",
"skipped_reason": null
},
{
"chosen_role_id": 1,
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Relational Database Usage",
"id": 371,
"rationale": "Working effectively with operational relational databases from Go backend services. This includes schema-aware querying, indexing awareness, transactions, and understanding how service code interacts with PostgreSQL or similar systems.",
"slug": "relational-database-usage",
"source": "db"
},
"dimension_id": 371,
"input_skill": "MySQL",
"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": 17,
"skill_tag": "in_db",
"skipped_reason": null
},
{
"chosen_role_id": 1,
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Relational Data Modeling",
"id": 216,
"rationale": "Modeling and tuning relational persistence for backend features. PHP backend developers need this to shape schemas, indexes, transactions, and query-aware data structures that support application behavior.",
"slug": "relational-data-modeling",
"source": "db"
},
"dimension_id": 216,
"input_skill": "PostgreSQL",
"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": "Fullstack Developer",
"id": 435,
"rationale": null,
"role_archetype": "Engineering",
"slug": "fullstack-developer",
"source": "db"
},
{
"display_name": "Fullstack Developer",
"id": 15,
"rationale": null,
"role_archetype": null,
"slug": "full-stack-engineer",
"source": "db"
},
{
"display_name": "PHP Backend Developer",
"id": 86,
"rationale": null,
"role_archetype": "Engineering",
"slug": "php-backend-developer",
"source": "db"
}
],
"skill_dimension_saved": true,
"skill_id": 16,
"skill_tag": "in_db",
"skipped_reason": null
},
{
"chosen_role_id": 1,
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Relational Database Design",
"id": 4,
"rationale": "Modeling and operating relational persistence for backend services. Includes schema design, normalization, indexing, transactions, and query tuning for operational data stores.",
"slug": "relational-database-design",
"source": "db"
},
"dimension_id": 4,
"input_skill": "PostgreSQL",
"llm_role": null,
"matched_chosen_role": true,
"outcome_line": "Existing dimension (library) \u00b7 Role\u2194dimension saved",
"role_dimension_saved": true,
"roles_from_db": [
{
"display_name": ".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": "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": "Python Backend Developer",
"id": 80,
"rationale": null,
"role_archetype": "Engineering",
"slug": "python-backend-developer",
"source": "db"
},
{
"display_name": "Ruby Backend Developer",
"id": 85,
"rationale": null,
"role_archetype": "Engineering",
"slug": "ruby-backend-developer",
"source": "db"
},
{
"display_name": "Scala Backend Developer",
"id": 87,
"rationale": null,
"role_archetype": "Engineering",
"slug": "scala-backend-developer",
"source": "db"
}
],
"skill_dimension_saved": true,
"skill_id": 16,
"skill_tag": "in_db",
"skipped_reason": null
},
{
"chosen_role_id": 1,
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Relational Database Usage",
"id": 371,
"rationale": "Working effectively with operational relational databases from Go backend services. This includes schema-aware querying, indexing awareness, transactions, and understanding how service code interacts with PostgreSQL or similar systems.",
"slug": "relational-database-usage",
"source": "db"
},
"dimension_id": 371,
"input_skill": "PostgreSQL",
"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": 16,
"skill_tag": "in_db",
"skipped_reason": null
},
{
"chosen_role_id": 1,
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Magento Search and Indexing",
"id": 403,
"rationale": "Index-driven storefront data freshness and search behavior. This cluster is coherent because Magento commerce sites depend on indexing to keep catalog, price, and search results aligned with changing data.",
"slug": "magento-search-and-indexing",
"source": "db"
},
"dimension_id": 403,
"input_skill": "Elasticsearch",
"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": "Magento Dev",
"id": 231,
"rationale": null,
"role_archetype": "Engineering",
"slug": "magento-dev",
"source": "db"
}
],
"skill_dimension_saved": true,
"skill_id": 3171,
"skill_tag": "in_db",
"skipped_reason": null
},
{
"chosen_role_id": 1,
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Search and Content Discovery",
"id": 356,
"rationale": "Implementing site search, indexing, and content discovery features in Drupal. This cluster is coherent because many Drupal sites need structured search experiences beyond basic navigation.",
"slug": "search-and-content-discovery",
"source": "db"
},
"dimension_id": 356,
"input_skill": "Elasticsearch",
"llm_role": null,
"matched_chosen_role": false,
"outcome_line": "Existing dimension (library) \u00b7 Role\u2194dimension skipped (dimension not under chosen role)",
"role_dimension_saved": false,
"roles_from_db": [
{
"display_name": "Drupal Dev",
"id": 228,
"rationale": null,
"role_archetype": "Engineering",
"slug": "drupal-dev",
"source": "db"
},
{
"display_name": "Sitecore Dev",
"id": 233,
"rationale": null,
"role_archetype": "Engineering",
"slug": "sitecore-dev",
"source": "db"
}
],
"skill_dimension_saved": true,
"skill_id": 3171,
"skill_tag": "in_db",
"skipped_reason": null
},
{
"chosen_role_id": 1,
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Caching and State Management",
"id": 7,
"rationale": "Techniques and systems for reducing latency and managing ephemeral backend state. Covers cache-aside patterns, distributed caches, session stores, and invalidation strategies.",
"slug": "caching-and-state-management",
"source": "db"
},
"dimension_id": 7,
"input_skill": "Redis",
"llm_role": null,
"matched_chosen_role": true,
"outcome_line": "Existing dimension (library) \u00b7 Role\u2194dimension saved",
"role_dimension_saved": true,
"roles_from_db": [
{
"display_name": ".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": "Kotlin Backend Developer",
"id": 84,
"rationale": null,
"role_archetype": "Engineering",
"slug": "kotlin-server-backend-developer",
"source": "db"
},
{
"display_name": "Node.js Backend Developer",
"id": 82,
"rationale": null,
"role_archetype": "Engineering",
"slug": "node-backend-developer",
"source": "db"
},
{
"display_name": "PHP Backend Developer",
"id": 86,
"rationale": null,
"role_archetype": "Engineering",
"slug": "php-backend-developer",
"source": "db"
},
{
"display_name": "Python Backend Developer",
"id": 80,
"rationale": null,
"role_archetype": "Engineering",
"slug": "python-backend-developer",
"source": "db"
},
{
"display_name": "Ruby Backend Developer",
"id": 85,
"rationale": null,
"role_archetype": "Engineering",
"slug": "ruby-backend-developer",
"source": "db"
},
{
"display_name": "Scala Backend Developer",
"id": 87,
"rationale": null,
"role_archetype": "Engineering",
"slug": "scala-backend-developer",
"source": "db"
}
],
"skill_dimension_saved": true,
"skill_id": 31,
"skill_tag": "in_db",
"skipped_reason": null
},
{
"chosen_role_id": 1,
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Magento Caching and Performance",
"id": 404,
"rationale": "Performance tuning specific to Magento storefronts and their rendering pipeline. This includes cache layers, page generation costs, and practical optimizations that preserve upgradeability while improving shopper experience.",
"slug": "magento-caching-and-performance",
"source": "db"
},
"dimension_id": 404,
"input_skill": "Redis",
"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": "Magento Dev",
"id": 231,
"rationale": null,
"role_archetype": "Engineering",
"slug": "magento-dev",
"source": "db"
}
],
"skill_dimension_saved": true,
"skill_id": 31,
"skill_tag": "in_db",
"skipped_reason": null
},
{
"chosen_role_id": 1,
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Microservices and Distributed Systems",
"id": 9,
"rationale": "Architectural patterns for decomposed backend systems and the operational concerns they introduce. Covers service boundaries, consistency tradeoffs, retries, circuit breakers, and distributed coordination.",
"slug": "microservices-and-distributed-systems",
"source": "db"
},
"dimension_id": 9,
"input_skill": "Microservices",
"llm_role": null,
"matched_chosen_role": true,
"outcome_line": "Existing dimension (library) \u00b7 Role\u2194dimension saved",
"role_dimension_saved": true,
"roles_from_db": [
{
"display_name": "Backend Developer",
"id": 1,
"rationale": null,
"role_archetype": "A Backend Engineer designs, builds, and maintains the server-side logic and data handling that power applications and services. They focus on implementing reliable business functionality, integrating with other systems, and ensuring the backend is scalable, maintainable, and observable.",
"slug": "backend-engineer",
"source": "db"
},
{
"display_name": "Node.js Backend Developer",
"id": 82,
"rationale": null,
"role_archetype": "Engineering",
"slug": "node-backend-developer",
"source": "db"
},
{
"display_name": "Scala Backend Developer",
"id": 87,
"rationale": null,
"role_archetype": "Engineering",
"slug": "scala-backend-developer",
"source": "db"
}
],
"skill_dimension_saved": true,
"skill_id": 41,
"skill_tag": "in_db",
"skipped_reason": null
},
{
"chosen_role_id": 1,
"dimension": {
"difficulty_hint": "well_known",
"display_name": "API Integration and Data Fetching",
"id": 127,
"rationale": "Client-side integration with backend endpoints and third-party services, including request shaping, response handling, and synchronization with UI state. This is central to frontend work because most screens depend on remote data.",
"slug": "api-integration-and-data-fetching",
"source": "db"
},
"dimension_id": 127,
"input_skill": "API",
"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": "Angular Frontend Developer",
"id": 90,
"rationale": null,
"role_archetype": "Engineering",
"slug": "angular-frontend-developer",
"source": "db"
},
{
"display_name": "Frontend Developer",
"id": 7,
"rationale": null,
"role_archetype": null,
"slug": "frontend-engineer",
"source": "db"
},
{
"display_name": "Fullstack Developer",
"id": 435,
"rationale": null,
"role_archetype": "Engineering",
"slug": "fullstack-developer",
"source": "db"
},
{
"display_name": "Fullstack Developer",
"id": 15,
"rationale": null,
"role_archetype": null,
"slug": "full-stack-engineer",
"source": "db"
},
{
"display_name": "React Frontend Developer",
"id": 89,
"rationale": null,
"role_archetype": "Engineering",
"slug": "react-frontend-developer",
"source": "db"
},
{
"display_name": "Svelte Frontend Developer",
"id": 92,
"rationale": null,
"role_archetype": "Engineering",
"slug": "svelte-frontend-developer",
"source": "db"
},
{
"display_name": "Vue Frontend Developer",
"id": 91,
"rationale": null,
"role_archetype": "Engineering",
"slug": "vue-frontend-developer",
"source": "db"
},
{
"display_name": "Web Developer",
"id": 25,
"rationale": null,
"role_archetype": null,
"slug": "web-developer",
"source": "db"
}
],
"skill_dimension_saved": true,
"skill_id": 1568,
"skill_tag": "in_db",
"skipped_reason": null
},
{
"chosen_role_id": 1,
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Networking and API Integration",
"id": 84,
"rationale": "Client-side HTTP communication with backend services, including request construction, response parsing, retries, and error handling. iOS engineers use this to connect native screens to server-owned APIs.",
"slug": "networking-and-api-integration",
"source": "db"
},
"dimension_id": 84,
"input_skill": "HTTP",
"llm_role": null,
"matched_chosen_role": false,
"outcome_line": "Existing dimension (library) \u00b7 Role\u2194dimension skipped (dimension not under chosen role)",
"role_dimension_saved": false,
"roles_from_db": [
{
"display_name": "Android Developer",
"id": 4,
"rationale": null,
"role_archetype": null,
"slug": "android-engineer",
"source": "db"
},
{
"display_name": "Hybrid Mobile Developer",
"id": 11,
"rationale": null,
"role_archetype": null,
"slug": "hybrid-mobile-developer",
"source": "db"
},
{
"display_name": "Native Mobile Developer",
"id": 75,
"rationale": null,
"role_archetype": "Engineering",
"slug": "native-mobile-developer",
"source": "db"
},
{
"display_name": "iOS Developer",
"id": 6,
"rationale": null,
"role_archetype": null,
"slug": "ios-engineer",
"source": "db"
}
],
"skill_dimension_saved": true,
"skill_id": 935,
"skill_tag": "in_db",
"skipped_reason": null
},
{
"chosen_role_id": 1,
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Containerization and Image Builds",
"id": 152,
"rationale": "Container image creation, tagging, hardening, and registry workflows used to package services for deployment. This is coherent because DevOps often owns the build-to-image path that feeds runtime environments.",
"slug": "containerization-and-image-builds",
"source": "db"
},
"dimension_id": 152,
"input_skill": "Docker",
"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": 61,
"skill_tag": "in_db",
"skipped_reason": null
},
{
"chosen_role_id": 1,
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Deployment and Cloud Platforms",
"id": 418,
"rationale": "Platform-as-a-Service and container environments for deploying Ruby applications.",
"slug": "deployment-and-cloud-platforms",
"source": "db"
},
"dimension_id": 418,
"input_skill": "Docker",
"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": "Ruby Backend Developer",
"id": 85,
"rationale": null,
"role_archetype": "Engineering",
"slug": "ruby-backend-developer",
"source": "db"
}
],
"skill_dimension_saved": true,
"skill_id": 61,
"skill_tag": "in_db",
"skipped_reason": null
},
{
"chosen_role_id": 1,
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Deployment and Runtime Configuration",
"id": 13,
"rationale": "Configuration and release artifacts that control how backend services run in environments. Includes environment variables, manifests, feature flags, and release-safe configuration management.",
"slug": "deployment-and-runtime-configuration",
"source": "db"
},
"dimension_id": 13,
"input_skill": "Docker",
"llm_role": null,
"matched_chosen_role": true,
"outcome_line": "Existing dimension (library) \u00b7 Role\u2194dimension saved",
"role_dimension_saved": true,
"roles_from_db": [
{
"display_name": ".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": "Go Backend Developer",
"id": 81,
"rationale": null,
"role_archetype": "Engineering",
"slug": "go-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": 61,
"skill_tag": "in_db",
"skipped_reason": null
},
{
"chosen_role_id": 1,
"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": "Jenkins",
"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": 283,
"skill_tag": "in_db",
"skipped_reason": null
},
{
"chosen_role_id": 1,
"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": "Jenkins",
"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": 283,
"skill_tag": "in_db",
"skipped_reason": null
},
{
"chosen_role_id": 1,
"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": "CircleCI",
"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": 826,
"skill_tag": "in_db",
"skipped_reason": null
},
{
"chosen_role_id": 1,
"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": 1,
"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": 1,
"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": 1,
"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": "Nomad",
"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": 855,
"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": "aa83281f-1ea5-4d0d-8b2b-5233ba238859"
}
LLM Calls
Every model call made for this run, in pipeline order. Click a card to see the model's response.