Pipeline run

e85a9814-a694-4e27-b9bc-bdf252ef233c

Pipeline LLM cost (USD)

API 1: $0.0103 API 2: $0.0001 API 3: $0.0000 Total: $0.0104

Client output enrichment

v2 Skill cluster · Nature of work · AI index · Tech stack maturity · Evidence · KRA description

SPARSE JD role baseline loaded sources · ai_index: role_baseline · nature_of_work: jd · tech_stack_maturity: role_baseline

Nature of work · Data access and persistence

Own PostgreSQL-backed Ruby on Rails work in a large, remote SaaS environment, contributing to GitLab while collaborating cross-functionally and communicating clearly across a global team.

"professional software engineering experience with PostgreSQL in large production environments"

Tech stack maturity

Modern Cloud Native

Backend development today is typically built around cloud-hosted services, containers, CI/CD, and distributed systems, but AI is usually only an optional integration rather than the core of the role.

AI index (0 = no AI use, 5 = totally AI-dependent · v2.1)

1.80 / 5

· Title match

· Has AI skill

· AI skill (primary)

· AI skill (secondary)

· On AI team

· Builds AI products

vocab breakdown (legacy)

Assistants (×1): —

Frameworks (×2): —

Models / concepts (×3): —

Evidence — skills matched in JD (4)

PostgreSQL Ruby on Rails GitLab SaaS

Skill cluster (3 dimension groups, role-scoped)

Relational Database Design

PostgreSQL

Web Application Frameworks

Ruby on Rails

Cross-cutting / unaligned

GitLab SaaS

Show KRA description ↓

You have professional software engineering experience with PostgreSQL in large production environments. You have production experience with Ruby on Rails. You are familiar with open source. You have strong written communication skills. You are self-motivated and have strong organizational skills. You have demonstrated the ability to onboard and integrate with an organization long-term. Within the last 5 years, you've worked at one company for at least 2 years. You are comfortable working in a cross functional organization. You are able to thrive in a fully remote organization. You are able to use GitLab. You share our values, and work in accordance with those values. Experience with the GitLab product as a user or contributor. Experience working with a remote team. Enterprise software company experience. Experience scaling a successful SaaS product. Developer platform/tool industry experience. Experience working with a global team.

Signals

Skill full-stack-engineer

1.00

Alias backend-engineer

1.00

KRA full-stack-engineer

0.45

Post-classification

Centroidupdated · n=1151

Alias collision log—

New-role queue—

New skills captured1

New KRA capturedyes

Captured for admin review

SaaS ↔ Backend Developer pending

R&R fragment (sim 0.38) ↔ Backend Developer pending

Status: completed Created: 2026-05-27T15:52:10.899678Z Updated: 2026-06-12T15:49:01.532711Z API 3 duration: 12811 ms

Flow Current 3-step pipeline

1 POST /skills/extract-from-jd

2 POST /skills/extract-details

3 POST /skills/final-role-output

Role Chosen role & resolution

Backend Developer

→

Ruby Backend Developer

sub-role · 0.99 domain · Software Engineering CASE DOMAIN

slug: backend-engineer · id: 1 · source: db · sub-role slug: ruby-backend-developer

Domain=Software Engineering → sub-role ruby-backend-developer; The JD centers on server-side backend work with PostgreSQL, Ruby on Rails, GitLab, and production SaaS/enterprise experience, which best matches Backend Engineer.

Matched skills

PostgreSQLRuby on RailsGitLabopen sourceremote teamfully remote organizationcross functional organizationenterprise software companySaaS productdeveloper platform/tool

Matched dimensions

Backend EngineeringDatabase EngineeringRuby on Rails DevelopmentRemote CollaborationCross-functional WorkEnterprise SaaS ExperienceDeveloper Platform Experience

Matched KRAs

work with PostgreSQL in large production environmentshave production experience with Ruby on Railsuse GitLabexperience with the GitLab product as a user or contributorwork with a remote teamscale a successful SaaS productwork in a cross functional organization

Resolution: in_db — role exists in library; skill↔dim and role↔dim links saved when applicable.

New skills

Skill↔dim saved

Role↔dim saved

Skipped

Job description

GitLab's DevOps platform empowers 100,000+ organizations to deliver software faster and more efficiently. We are one of the world’s largest all-remote companies with 1,600+ team members and values that guide a culture where people embrace the belief that everyone can contribute .

An Overview of the GitLab Development Team

The GitLab Development Team is a 260+ person globally distributed team that consists of Backend Engineers , Frontend Engineers , Fullstack Engineers , and Management .

The Vision of the Development Team is to be a world class team of software engineers and managers who make our customers happy when using our product(s). Our products should contain broad rich features, high availability, high quality, fast performance, trustworthy security, and reliable operation.

The Development Team is responsible for developing products in the following categories:
Dev Enablement Fulfillment Growth Ops Secure Threat Management
We're hiring for Backend Engineer positions across the Dev sub-team. The Dev team manages the first key stages of the DevSecOps lifecycle: Manage, Plan and Create .

Backend Engineers at GitLab work on our product. This includes both the open source version of GitLab, the enterprise editions, and the GitLab.com service as well. They work with peers on teams dedicated to areas of the product. They work together with product managers, designers, and frontend engineers to solve common goals.

At GitLab, developers are independent and self-organized individual contributors who work together as a tight team in a remote and agile way. Most backend developers work on all aspects of GitLab, building features, fixing bugs, and generally improving the application.

Learn more about Backend Engineering at GitLab

Required Qualifications
You have professional software engineering experience with PostgreSQL in large production environments You have production experience with Ruby on Rails You are familiar with open source You have strong written communication skills You are self-motivated and have strong organizational skills You have demonstrated the ability to onboard and integrate with an organization long-term. Within the last 5 years, you've worked at one company for at least 2 years. You are comfortable working in a cross functional organization You are able to thrive in a fully remote organization You are able to use GitLab You share our values , and work in accordance with those values Preferred Qualifications
Experience with the GitLab product as a user or contributor Experience working with a remote team Enterprise software company experience Experience scaling a successful SaaS product Developer platform/tool industry experience Experience working with a global team Compensation

To view the full job description and its compensation calculator, view our handbook. Candidates will have access to the compensation calculator after an initial screen conversation with a member of our recruiting team. Additional details about our process can be found on our hiring page .

For Colorado residents: The base salary range for this role’s listed level is currently $107,500 - $188,900 for Colorado residents only. Grade level and salary ranges are determined through interviews and a review of education, experience, knowledge, skills, abilities of the applicant, equity with other team members, and alignment with market data. See more information on our benefits and equity . Sales roles are also eligible for incentive pay targeted at up to 100% of the offered base salary. Disclosure as required by the Colorado Equal Pay for Equal Work Act, C.R.S.
8-5-101 et seq.
Remote-Global

Country Hiring Guidelines: GitLab hires new team members in countries around the world. All of our roles are remote, however some roles may carry specific location-based eligibility requirements. Our Talent Acquisition team can help answer any questions about location after starting the recruiting process.

GitLab is proud to be an equal opportunity workplace and is an affirmative action employer. GitLab’s policies and practices relating to recruitment, employment, career development and advancement, promotion, and retirement are based solely on merit, regardless of race, color, religion, ancestry, sex (including pregnancy, lactation, sexual orientation, gender identity, or gender expression), national origin, age, citizenship, marital status, mental or physical disability, genetic information (including family medical history), discharge status from the military, protected veteran status (which includes disabled veterans, recently separated veterans, active duty wartime or campaign badge veterans, and Armed Forces service medal veterans), or any other basis protected by law. GitLab will not tolerate discrimination or harassment based on any of these characteristics. See also GitLab’s EEO Policy and EEO is the Law . If you have a disability or special need that requires accommodation , please let us know during the recruiting process .

Skills from this JD

Each row merges API 1 extraction, API 2 library match / v3 orchestration (dimensions + locked dims), and API 3 persistence tags.

PostgreSQL Primary Library skill API 3: existing canonical (in_db) Existing skill (matched library)

Canonical: PostgreSQL id=16 · postgresql

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)

ACID EXPLAIN JSONB PL/pgSQL PostGIS SQL VACUUM backup data integrity database migration extensions indexes indexing joins migration partitioning performance tuning pgAdmin query optimization replication schema stored procedures table partitioning transaction transactions triggers views

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)

Ruby on Rails Primary Library skill API 3: existing canonical (in_db) Existing skill (matched library)

Canonical: Ruby on Rails id=10 · ruby-on-rails

Aliases — catalog

Ruby on Rails (CANONICAL) primary
Rails 5 (VERSION)
Rails 5.x (VERSION)
Rails 6 (VERSION)
Rails 6.x (VERSION)
Rails 7 (VERSION)
Rails 7.x (VERSION)
Ruby on Rails 5 (VERSION)
Ruby on Rails 5.x (VERSION)
Ruby on Rails 6 (VERSION)
Ruby on Rails 6.x (VERSION)
Ruby on Rails 7 (VERSION)
Ruby on Rails 7.x (VERSION)

Context tags (catalog)

ActionCable ActionController ActionView ActiveRecord Bundler Capistrano Capybara Devise Gemfile Heroku Hotwire MVC Migrations PostgreSQL Puma Pundit RESTful RESTful routes RSpec Rails API Sidekiq Stimulus Turbo Webpacker

Stored enrichment (catalog DB)

Category: Framework
Sub-category: Web Framework
Vendor: David Heinemeier Hansson
License: mit
Year introduced: 2005
Confidence: 0.99
Version strategy: NOT_APPLICABLE

Maturity reasoning: Ruby on Rails remains widely listed in job descriptions and powers many production web apps; GitHub activity and hiring demand are steady, though below newer stacks like React/Node.

Skill profile (library / DB)

Skill nature: FRAMEWORK
Volatility: STABLE
Typical lifespan: EVERGREEN
Category id: 5
Sub-category id: 35
Extractable: True
Also category: False

Dimensions (API 2 worklist)

Ruby Web Frameworks Catalog dimension db id 416

Library dimension (catalog)

Roles linked in library: Ruby Backend Developer
Web Application Frameworks Catalog dimension db id 2

Library dimension (catalog)

Roles linked in library: Backend Developer, Fullstack Developer, Fullstack Developer, Java Backend Developer, Node.js Backend Developer, PHP Backend Developer, Python Backend Developer

API 3 link attempts (this skill)

Dimension	Skill↔dim	Role↔dim	Outcome
Ruby Web Frameworks ruby-web-frameworks	✓	—	Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role)
Web Application Frameworks web-application-frameworks	✓	✓	Existing dimension (library) · Role↔dimension saved

GitLab Secondary Library skill API 3: existing canonical (in_db) Existing skill (matched library)

Canonical: GitLab id=279 · gitlab

Aliases — catalog

GitLab (CANONICAL) primary

Context tags (catalog)

.gitlab-ci.yml CI/CD DevOps DevSecOps GitLab CI GitLab Pages GitLab Runner Kubernetes YAML artifact registry automated testing code review container registry issue boards issues merge requests monitoring pipelines repository management runners security scanning self-hosted version control webhooks

Stored enrichment (catalog DB)

Category: Platform
Sub-category: Devops Platform
Vendor: GitLab Inc.
License: mit
Year introduced: 2011
Confidence: 0.96
Version strategy: NOT_APPLICABLE

Maturity reasoning: GitLab appears in many DevOps/CI-CD job descriptions and is widely used as an integrated source control and pipeline platform; its GitLab CI/CD and self-managed/SaaS offerings are common hiring signals.

Skill profile (library / DB)

Skill nature: PLATFORM
Volatility: STABLE
Typical lifespan: EVERGREEN
Category id: 9
Sub-category id: 170
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)

SaaS Secondary New / orchestrated API 3: new canonical path (new) New / unmatched skill (orchestrated in API 2)

Skill enrichment (orchestrator / LLM)

No Stage 7 enrichment blob on this skill (orchestrator skipped enrichment).

Derived legacy fields

Category: Cloud Platforms
Sub-category: general
Skill nature: CONCEPT
Volatility: STABLE
Typical lifespan: EVERGREEN
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
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)
Ruby on Rails	in_db	Ruby Web Frameworks ruby-web-frameworks	✓	—	Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role)
Ruby on Rails	in_db	Web Application Frameworks web-application-frameworks	✓	✓	Existing dimension (library) · Role↔dimension saved
GitLab	in_db	CI/CD Pipeline Platforms ci-cd-pipeline-platforms	✓	—	Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role)
GitLab	in_db	CI/CD for Machine Learning ci-cd-for-machine-learning	✓	—	Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role)

Library artifacts (this run)

Kind	Detail	DB id
canonical_skill_proposed	SaaS \| type=Cloud Platforms subtype=general nature=CONCEPT lifespan=EVERGREEN

nano JD Parser — gpt-4.1-nano click to toggle

RoleBackend Engineer

CompanyGitLab

ExperienceWithin the last 5 years, you've worked at one company for at least 2 years.

CTC{'max': 188.9, 'min': 107.5, 'raw': '$107,500 - $188,900', 'period': 'annual', 'currency': 'USD'}

DomainSoftware & SaaS Products

Location Global (remote)

JD type pass

Show raw JSON

{
  "JD_type": "pass",
  "about_company": {
    "source_marker": {
      "first_5_words": "GitLab\u0027s DevOps platform empowers 100,000+",
      "last_5_words": "belief that everyone can contribute."
    },
    "text": "GitLab\u0027s DevOps platform empowers 100,000+ organizations to deliver software faster and more efficiently. We are one of the world\u2019s largest all-remote companies with 1,600+ team members and values that guide a culture where people embrace the belief that everyone can contribute.",
    "word_count": 43
  },
  "certifications": [],
  "company_name": "GitLab",
  "ctc": {
    "currency": "USD",
    "max": 188.9,
    "min": 107.5,
    "period": "annual",
    "raw": "$107,500 - $188,900"
  },
  "domain": {
    "primary": {
      "aliases": [
        "SaaS",
        "Software Development"
      ],
      "domain": "Software \u0026 SaaS Products"
    },
    "secondary": null
  },
  "education": [],
  "experience": {
    "max": 5,
    "min": 2,
    "raw": "Within the last 5 years, you\u0027ve worked at one company for at least 2 years."
  },
  "job_locations": [
    {
      "aliases": [],
      "city": null,
      "country": "Global",
      "state": null,
      "work_mode": "remote"
    }
  ],
  "role": "Backend Engineer",
  "role_aliases": [
    "Software Engineer",
    "Backend Developer",
    "SWE"
  ],
  "role_archetype": "Engineering",
  "roles_and_responsibilities": [
    {
      "bullet_count": 9,
      "heading": "Required Qualifications",
      "heading_was_present": true,
      "source_marker": {
        "first_5_words": "You have professional software engineering",
        "last_5_words": "work in accordance with those values."
      },
      "text": "You have professional software engineering experience with PostgreSQL in large production environments.\nYou have production experience with Ruby on Rails.\nYou are familiar with open source.\nYou have strong written communication skills.\nYou are self-motivated and have strong organizational skills.\nYou have demonstrated the ability to onboard and integrate with an organization long-term. Within the last 5 years, you\u0027ve worked at one company for at least 2 years.\nYou are comfortable working in a cross functional organization.\nYou are able to thrive in a fully remote organization.\nYou are able to use GitLab.\nYou share our values, and work in accordance with those values.",
      "word_count": 92
    },
    {
      "bullet_count": 6,
      "heading": "Preferred Qualifications",
      "heading_was_present": true,
      "source_marker": {
        "first_5_words": "Experience with the GitLab product",
        "last_5_words": "working with a global team."
      },
      "text": "Experience with the GitLab product as a user or contributor.\nExperience working with a remote team.\nEnterprise software company experience.\nExperience scaling a successful SaaS product.\nDeveloper platform/tool industry experience.\nExperience working with a global team.",
      "word_count": 41
    }
  ],
  "urls": []
}

API 1 — extract-from-jd click to toggle

{
  "final_skills": [
    {
      "is_primary": true,
      "skill_name": "PostgreSQL"
    },
    {
      "is_primary": true,
      "skill_name": "Ruby on Rails"
    },
    {
      "is_primary": false,
      "skill_name": "GitLab"
    },
    {
      "is_primary": false,
      "skill_name": "SaaS"
    }
  ],
  "jd_role": {
    "display_name": "Backend Engineer",
    "rationale": null,
    "role_aliases": [
      "Software Engineer",
      "Backend Developer",
      "SWE"
    ],
    "role_archetype": "Engineering",
    "slug": ""
  },
  "nano_parsed": {
    "JD_type": "pass",
    "about_company": {
      "source_marker": {
        "first_5_words": "GitLab\u0027s DevOps platform empowers 100,000+",
        "last_5_words": "belief that everyone can contribute."
      },
      "text": "GitLab\u0027s DevOps platform empowers 100,000+ organizations to deliver software faster and more efficiently. We are one of the world\u2019s largest all-remote companies with 1,600+ team members and values that guide a culture where people embrace the belief that everyone can contribute.",
      "word_count": 43
    },
    "certifications": [],
    "company_name": "GitLab",
    "ctc": {
      "currency": "USD",
      "max": 188.9,
      "min": 107.5,
      "period": "annual",
      "raw": "$107,500 - $188,900"
    },
    "domain": {
      "primary": {
        "aliases": [
          "SaaS",
          "Software Development"
        ],
        "domain": "Software \u0026 SaaS Products"
      },
      "secondary": null
    },
    "education": [],
    "experience": {
      "max": 5,
      "min": 2,
      "raw": "Within the last 5 years, you\u0027ve worked at one company for at least 2 years."
    },
    "job_locations": [
      {
        "aliases": [],
        "city": null,
        "country": "Global",
        "state": null,
        "work_mode": "remote"
      }
    ],
    "role": "Backend Engineer",
    "role_aliases": [
      "Software Engineer",
      "Backend Developer",
      "SWE"
    ],
    "role_archetype": "Engineering",
    "roles_and_responsibilities": [
      {
        "bullet_count": 9,
        "heading": "Required Qualifications",
        "heading_was_present": true,
        "source_marker": {
          "first_5_words": "You have professional software engineering",
          "last_5_words": "work in accordance with those values."
        },
        "text": "You have professional software engineering experience with PostgreSQL in large production environments.\nYou have production experience with Ruby on Rails.\nYou are familiar with open source.\nYou have strong written communication skills.\nYou are self-motivated and have strong organizational skills.\nYou have demonstrated the ability to onboard and integrate with an organization long-term. Within the last 5 years, you\u0027ve worked at one company for at least 2 years.\nYou are comfortable working in a cross functional organization.\nYou are able to thrive in a fully remote organization.\nYou are able to use GitLab.\nYou share our values, and work in accordance with those values.",
        "word_count": 92
      },
      {
        "bullet_count": 6,
        "heading": "Preferred Qualifications",
        "heading_was_present": true,
        "source_marker": {
          "first_5_words": "Experience with the GitLab product",
          "last_5_words": "working with a global team."
        },
        "text": "Experience with the GitLab product as a user or contributor.\nExperience working with a remote team.\nEnterprise software company experience.\nExperience scaling a successful SaaS product.\nDeveloper platform/tool industry experience.\nExperience working with a global team.",
        "word_count": 41
      }
    ],
    "urls": []
  },
  "rejected": false,
  "rejection_reason": null,
  "run_id": "e85a9814-a694-4e27-b9bc-bdf252ef233c",
  "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": "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 professional software engineering experience with PostgreSQL in large production environments.",
            "similarity": 0.528
          },
          {
            "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": "Developer platform/tool industry experience.",
            "similarity": 0.4167
          },
          {
            "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 production experience with Ruby on Rails.",
            "similarity": 0.4098
          }
        ],
        "matched_count": null,
        "matched_skills": null,
        "role_id": 15,
        "score": 0.4515,
        "slug": "full-stack-engineer",
        "total_count": null
      },
      {
        "display_name": "Engineering Manager",
        "kra_matches": [
          {
            "kra_text": "support hiring and onboarding",
            "sentence": "You have demonstrated the ability to onboard and integrate with an organization long-term.",
            "similarity": 0.4219
          },
          {
            "kra_text": "support hiring and onboarding",
            "sentence": "Experience scaling a successful SaaS product.",
            "similarity": 0.373
          },
          {
            "kra_text": "manage stakeholder alignment and tradeoffs",
            "sentence": "You are comfortable working in a cross functional organization.",
            "similarity": 0.355
          }
        ],
        "matched_count": null,
        "matched_skills": null,
        "role_id": 121,
        "score": 0.3833,
        "slug": "engineering-manager",
        "total_count": null
      },
      {
        "display_name": "Flutter Developer",
        "kra_matches": [
          {
            "kra_text": "collaborate with design, product, and backend teams",
            "sentence": "Developer platform/tool industry experience.",
            "similarity": 0.4115
          },
          {
            "kra_text": "collaborate with design, product, and backend teams",
            "sentence": "You are comfortable working in a cross functional organization.",
            "similarity": 0.3748
          },
          {
            "kra_text": "collaborate with design, product, and backend teams",
            "sentence": "Experience scaling a successful SaaS product.",
            "similarity": 0.3578
          }
        ],
        "matched_count": null,
        "matched_skills": null,
        "role_id": 74,
        "score": 0.3814,
        "slug": "flutter-developer",
        "total_count": null
      },
      {
        "display_name": "Backend Developer",
        "kra_matches": [
          {
            "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 professional software engineering experience with PostgreSQL in large production environments.",
            "similarity": 0.4515
          },
          {
            "kra_text": "Configures Docker containers, deployment descriptors, environment variables, and CI/CD pipeline stages for backend service releases.",
            "sentence": "Developer platform/tool industry experience.",
            "similarity": 0.3619
          },
          {
            "kra_text": "Investigates and resolves production incidents, API bugs, and service degradation through root cause analysis, hotfixes, and post-mortems.",
            "sentence": "You have production experience with Ruby on Rails.",
            "similarity": 0.3299
          }
        ],
        "matched_count": null,
        "matched_skills": null,
        "role_id": 1,
        "score": 0.3811,
        "slug": "backend-engineer",
        "total_count": null
      },
      {
        "display_name": "Scala Backend Developer",
        "kra_matches": [
          {
            "kra_text": "internal and external system integration",
            "sentence": "You have demonstrated the ability to onboard and integrate with an organization long-term.",
            "similarity": 0.4001
          },
          {
            "kra_text": "service endpoint development",
            "sentence": "Developer platform/tool industry experience.",
            "similarity": 0.3961
          },
          {
            "kra_text": "performance and reliability tuning",
            "sentence": "Experience scaling a successful SaaS product.",
            "similarity": 0.3457
          }
        ],
        "matched_count": null,
        "matched_skills": null,
        "role_id": 87,
        "score": 0.3807,
        "slug": "scala-backend-developer",
        "total_count": null
      }
    ],
    "skill_match_roles": [
      {
        "display_name": "Fullstack Developer",
        "kra_matches": null,
        "matched_count": 2,
        "matched_skills": [
          "PostgreSQL",
          "Ruby on Rails"
        ],
        "role_id": 15,
        "score": 1.0,
        "slug": "full-stack-engineer",
        "total_count": 2
      },
      {
        "display_name": "Node.js Backend Developer",
        "kra_matches": null,
        "matched_count": 2,
        "matched_skills": [
          "PostgreSQL",
          "Ruby on Rails"
        ],
        "role_id": 82,
        "score": 1.0,
        "slug": "node-backend-developer",
        "total_count": 2
      },
      {
        "display_name": "Backend Developer",
        "kra_matches": null,
        "matched_count": 2,
        "matched_skills": [
          "PostgreSQL",
          "Ruby on Rails"
        ],
        "role_id": 1,
        "score": 1.0,
        "slug": "backend-engineer",
        "total_count": 2
      },
      {
        "display_name": "Python Backend Developer",
        "kra_matches": null,
        "matched_count": 2,
        "matched_skills": [
          "PostgreSQL",
          "Ruby on Rails"
        ],
        "role_id": 80,
        "score": 1.0,
        "slug": "python-backend-developer",
        "total_count": 2
      },
      {
        "display_name": "Ruby Backend Developer",
        "kra_matches": null,
        "matched_count": 2,
        "matched_skills": [
          "PostgreSQL",
          "Ruby on Rails"
        ],
        "role_id": 85,
        "score": 1.0,
        "slug": "ruby-backend-developer",
        "total_count": 2
      }
    ]
  },
  "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.98,
      "slug": "backend-engineer",
      "total_count": null
    },
    "confidence": 0.98,
    "is_new_role": false,
    "llm2_fired": false,
    "llm2_reasoning": null,
    "matched_dimensions": [
      "Backend Engineering",
      "Database Engineering",
      "Ruby on Rails Development",
      "Remote Collaboration",
      "Cross-functional Work",
      "Enterprise SaaS Experience",
      "Developer Platform Experience"
    ],
    "matched_kras": [
      "work with PostgreSQL in large production environments",
      "have production experience with Ruby on Rails",
      "use GitLab",
      "experience with the GitLab product as a user or contributor",
      "work with a remote team",
      "scale a successful SaaS product",
      "work in a cross functional organization"
    ],
    "matched_skills": [
      "PostgreSQL",
      "Ruby on Rails",
      "GitLab",
      "open source",
      "remote team",
      "fully remote organization",
      "cross functional organization",
      "enterprise software company",
      "SaaS product",
      "developer platform/tool"
    ],
    "new_role_display_name": null,
    "new_role_slug": null,
    "queued": false,
    "reasoning": "Domain=Software Engineering \u2192 sub-role ruby-backend-developer; The JD centers on server-side backend work with PostgreSQL, Ruby on Rails, GitLab, and production SaaS/enterprise experience, which best matches Backend Engineer.",
    "sub_role": {
      "confidence": 0.99,
      "display_name": "Ruby Backend Developer",
      "reasoning": "The JD explicitly requires production experience with Ruby on Rails, which strongly indicates a Ruby backend role.",
      "role_id": 85,
      "slug": "ruby-backend-developer"
    }
  },
  "stage5_updates": {
    "centroid_n_after": 1151,
    "centroid_updated": true,
    "collision_log_id": null,
    "new_kra_attached": {
      "best_kra_similarity": 0.3811,
      "queue_id": 1210,
      "r_and_r_preview": "You have professional software engineering experience with PostgreSQL in large production environments.\nYou have production experience with Ruby on Rails.\nYou are familiar with open source.\nYou have s",
      "role_display_name": "Backend Developer",
      "role_slug": "backend-engineer",
      "status": "pending"
    },
    "new_skills_attached": [
      {
        "is_primary": false,
        "queue_id": 16853,
        "role_display_name": "Backend Developer",
        "role_slug": "backend-engineer",
        "skill_name": "SaaS",
        "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": 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": 93,
      "existing_alias_text": "Ruby on Rails",
      "input_term": "Ruby on Rails",
      "matched_canonical": {
        "category_id": 5,
        "display_name": "Ruby on Rails",
        "id": 10,
        "is_also_category": false,
        "is_extractable": true,
        "skill_nature": "FRAMEWORK",
        "slug": "ruby-on-rails",
        "sub_category_id": 35,
        "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": 540,
      "existing_alias_text": "GitLab",
      "input_term": "GitLab",
      "matched_canonical": {
        "category_id": 9,
        "display_name": "GitLab",
        "id": 279,
        "is_also_category": false,
        "is_extractable": true,
        "skill_nature": "PLATFORM",
        "slug": "gitlab",
        "sub_category_id": 170,
        "typical_lifespan": "EVERGREEN",
        "volatility": "STABLE"
      },
      "matched_via": "alias"
    }
  ],
  "candidate_roles": [
    {
      "display_name": "Fullstack Developer",
      "id": 15,
      "rationale": null,
      "role_archetype": null,
      "slug": "full-stack-engineer",
      "source": "db"
    },
    {
      "display_name": "Fullstack Developer",
      "id": 435,
      "rationale": null,
      "role_archetype": "Engineering",
      "slug": "fullstack-developer",
      "source": "db"
    },
    {
      "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": "Java Backend Developer",
      "id": 79,
      "rationale": null,
      "role_archetype": "Engineering",
      "slug": "java-backend-developer",
      "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"
    }
  ],
  "chosen_role": {
    "display_name": "Backend Developer",
    "id": 1,
    "rationale": "Domain=Software Engineering \u2192 sub-role ruby-backend-developer; The JD centers on server-side backend work with PostgreSQL, Ruby on Rails, GitLab, and production SaaS/enterprise experience, which best matches Backend Engineer.",
    "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": "PostgreSQL",
      "llm_role": null,
      "roles_from_db": [
        {
          "display_name": "Fullstack Developer",
          "id": 15,
          "rationale": null,
          "role_archetype": null,
          "slug": "full-stack-engineer",
          "source": "db"
        },
        {
          "display_name": "Fullstack Developer",
          "id": 435,
          "rationale": null,
          "role_archetype": "Engineering",
          "slug": "fullstack-developer",
          "source": "db"
        },
        {
          "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": "Ruby Web Frameworks",
        "id": 416,
        "rationale": "Server-side Ruby frameworks and runtimes used to handle requests, controllers, middleware, and service composition. This cluster is coherent because it defines how backend endpoints are structured and executed.",
        "slug": "ruby-web-frameworks",
        "source": "db"
      },
      "input_skill": "Ruby on Rails",
      "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": "Web Application Frameworks",
        "id": 2,
        "rationale": "Server frameworks and runtimes used to build HTTP services, controllers, middleware, and request pipelines. These frameworks shape how backend endpoints are structured and delivered.",
        "slug": "web-application-frameworks",
        "source": "db"
      },
      "input_skill": "Ruby on Rails",
      "llm_role": null,
      "roles_from_db": [
        {
          "display_name": "Backend Developer",
          "id": 1,
          "rationale": null,
          "role_archetype": "A Backend Engineer designs, builds, and maintains the server-side logic and data handling that power applications and services. They focus on implementing reliable business functionality, integrating with other systems, and ensuring the backend is scalable, maintainable, and observable.",
          "slug": "backend-engineer",
          "source": "db"
        },
        {
          "display_name": "Fullstack Developer",
          "id": 15,
          "rationale": null,
          "role_archetype": null,
          "slug": "full-stack-engineer",
          "source": "db"
        },
        {
          "display_name": "Fullstack Developer",
          "id": 435,
          "rationale": null,
          "role_archetype": "Engineering",
          "slug": "fullstack-developer",
          "source": "db"
        },
        {
          "display_name": "Java Backend Developer",
          "id": 79,
          "rationale": null,
          "role_archetype": "Engineering",
          "slug": "java-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"
        }
      ]
    },
    {
      "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": "GitLab",
      "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": "GitLab",
      "llm_role": null,
      "roles_from_db": [
        {
          "display_name": "ML Engineer",
          "id": 3,
          "rationale": null,
          "role_archetype": null,
          "slug": "ml-engineer",
          "source": "db"
        }
      ]
    }
  ],
  "input_final_skills": [
    "PostgreSQL",
    "Ruby on Rails",
    "GitLab",
    "SaaS"
  ],
  "input_llm_skills": [
    "PostgreSQL",
    "Ruby on Rails",
    "GitLab",
    "SaaS"
  ],
  "new_aliases_persisted": 0,
  "run_id": "e85a9814-a694-4e27-b9bc-bdf252ef233c",
  "skills_detail": [
    {
      "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": 15,
              "rationale": null,
              "role_archetype": null,
              "slug": "full-stack-engineer",
              "source": "db"
            },
            {
              "display_name": "Fullstack Developer",
              "id": 435,
              "rationale": null,
              "role_archetype": "Engineering",
              "slug": "fullstack-developer",
              "source": "db"
            },
            {
              "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": [
        {
          "alias_text": "Ruby on Rails",
          "alias_type": "CANONICAL",
          "id": 93,
          "is_primary": true,
          "match_strategy": "CASE_INSENSITIVE"
        },
        {
          "alias_text": "Rails 5",
          "alias_type": "VERSION",
          "id": 94,
          "is_primary": false,
          "match_strategy": "CASE_INSENSITIVE"
        },
        {
          "alias_text": "Rails 5.x",
          "alias_type": "VERSION",
          "id": 97,
          "is_primary": false,
          "match_strategy": "CASE_INSENSITIVE"
        },
        {
          "alias_text": "Rails 6",
          "alias_type": "VERSION",
          "id": 95,
          "is_primary": false,
          "match_strategy": "CASE_INSENSITIVE"
        },
        {
          "alias_text": "Rails 6.x",
          "alias_type": "VERSION",
          "id": 98,
          "is_primary": false,
          "match_strategy": "CASE_INSENSITIVE"
        },
        {
          "alias_text": "Rails 7",
          "alias_type": "VERSION",
          "id": 96,
          "is_primary": false,
          "match_strategy": "CASE_INSENSITIVE"
        },
        {
          "alias_text": "Rails 7.x",
          "alias_type": "VERSION",
          "id": 99,
          "is_primary": false,
          "match_strategy": "CASE_INSENSITIVE"
        },
        {
          "alias_text": "Ruby on Rails 5",
          "alias_type": "VERSION",
          "id": 100,
          "is_primary": false,
          "match_strategy": "CASE_INSENSITIVE"
        },
        {
          "alias_text": "Ruby on Rails 5.x",
          "alias_type": "VERSION",
          "id": 103,
          "is_primary": false,
          "match_strategy": "CASE_INSENSITIVE"
        },
        {
          "alias_text": "Ruby on Rails 6",
          "alias_type": "VERSION",
          "id": 101,
          "is_primary": false,
          "match_strategy": "CASE_INSENSITIVE"
        },
        {
          "alias_text": "Ruby on Rails 6.x",
          "alias_type": "VERSION",
          "id": 104,
          "is_primary": false,
          "match_strategy": "CASE_INSENSITIVE"
        },
        {
          "alias_text": "Ruby on Rails 7",
          "alias_type": "VERSION",
          "id": 102,
          "is_primary": false,
          "match_strategy": "CASE_INSENSITIVE"
        },
        {
          "alias_text": "Ruby on Rails 7.x",
          "alias_type": "VERSION",
          "id": 105,
          "is_primary": false,
          "match_strategy": "CASE_INSENSITIVE"
        }
      ],
      "canonical": {
        "category_id": 5,
        "display_name": "Ruby on Rails",
        "id": 10,
        "is_also_category": false,
        "is_extractable": true,
        "skill_nature": "FRAMEWORK",
        "slug": "ruby-on-rails",
        "sub_category_id": 35,
        "typical_lifespan": "EVERGREEN",
        "volatility": "STABLE"
      },
      "dimensions": [
        {
          "dimension": {
            "difficulty_hint": "well_known",
            "display_name": "Ruby Web Frameworks",
            "id": 416,
            "rationale": "Server-side Ruby frameworks and runtimes used to handle requests, controllers, middleware, and service composition. This cluster is coherent because it defines how backend endpoints are structured and executed.",
            "slug": "ruby-web-frameworks",
            "source": "db"
          },
          "input_skill": "Ruby on Rails",
          "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": "Web Application Frameworks",
            "id": 2,
            "rationale": "Server frameworks and runtimes used to build HTTP services, controllers, middleware, and request pipelines. These frameworks shape how backend endpoints are structured and delivered.",
            "slug": "web-application-frameworks",
            "source": "db"
          },
          "input_skill": "Ruby on Rails",
          "llm_role": null,
          "roles_from_db": [
            {
              "display_name": "Backend Developer",
              "id": 1,
              "rationale": null,
              "role_archetype": "A Backend Engineer designs, builds, and maintains the server-side logic and data handling that power applications and services. They focus on implementing reliable business functionality, integrating with other systems, and ensuring the backend is scalable, maintainable, and observable.",
              "slug": "backend-engineer",
              "source": "db"
            },
            {
              "display_name": "Fullstack Developer",
              "id": 15,
              "rationale": null,
              "role_archetype": null,
              "slug": "full-stack-engineer",
              "source": "db"
            },
            {
              "display_name": "Fullstack Developer",
              "id": 435,
              "rationale": null,
              "role_archetype": "Engineering",
              "slug": "fullstack-developer",
              "source": "db"
            },
            {
              "display_name": "Java Backend Developer",
              "id": 79,
              "rationale": null,
              "role_archetype": "Engineering",
              "slug": "java-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"
            }
          ]
        }
      ],
      "input_skill": "Ruby on Rails",
      "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": "GitLab",
          "alias_type": "CANONICAL",
          "id": 540,
          "is_primary": true,
          "match_strategy": "CASE_INSENSITIVE"
        }
      ],
      "canonical": {
        "category_id": 9,
        "display_name": "GitLab",
        "id": 279,
        "is_also_category": false,
        "is_extractable": true,
        "skill_nature": "PLATFORM",
        "slug": "gitlab",
        "sub_category_id": 170,
        "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": "GitLab",
          "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": "GitLab",
          "llm_role": null,
          "roles_from_db": [
            {
              "display_name": "ML Engineer",
              "id": 3,
              "rationale": null,
              "role_archetype": null,
              "slug": "ml-engineer",
              "source": "db"
            }
          ]
        }
      ],
      "input_skill": "GitLab",
      "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": "SaaS",
      "matched_via": null,
      "new_alias_persisted": false,
      "new_alias_text": null,
      "new_skill_meta": {
        "derived": {
          "category": "Cloud Platforms",
          "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": "saas",
        "split_log": [],
        "typed": null,
        "warnings": []
      },
      "source_tag": "llm",
      "was_in_llm_skills": true
    }
  ],
  "unmatched_skills": [
    "SaaS"
  ]
}

API 3 — final-role-output

{
  "chosen_role": {
    "display_name": "Backend Developer",
    "id": 1,
    "rationale": "Domain=Software Engineering \u2192 sub-role ruby-backend-developer; The JD centers on server-side backend work with PostgreSQL, Ruby on Rails, GitLab, and production SaaS/enterprise experience, which best matches Backend Engineer.",
    "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": "PostgreSQL",
      "tag": "in_db"
    },
    {
      "skill": "Ruby on Rails",
      "tag": "in_db"
    },
    {
      "skill": "GitLab",
      "tag": "in_db"
    },
    {
      "skill": "SaaS",
      "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": "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": 15,
            "rationale": null,
            "role_archetype": null,
            "slug": "full-stack-engineer",
            "source": "db"
          },
          {
            "display_name": "Fullstack Developer",
            "id": 435,
            "rationale": null,
            "role_archetype": "Engineering",
            "slug": "fullstack-developer",
            "source": "db"
          },
          {
            "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": "Ruby Web Frameworks",
          "id": 416,
          "rationale": "Server-side Ruby frameworks and runtimes used to handle requests, controllers, middleware, and service composition. This cluster is coherent because it defines how backend endpoints are structured and executed.",
          "slug": "ruby-web-frameworks",
          "source": "db"
        },
        "dimension_id": 416,
        "input_skill": "Ruby on Rails",
        "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": 10,
        "skill_tag": "in_db",
        "skipped_reason": null
      },
      {
        "chosen_role_id": 1,
        "dimension": {
          "difficulty_hint": "well_known",
          "display_name": "Web Application Frameworks",
          "id": 2,
          "rationale": "Server frameworks and runtimes used to build HTTP services, controllers, middleware, and request pipelines. These frameworks shape how backend endpoints are structured and delivered.",
          "slug": "web-application-frameworks",
          "source": "db"
        },
        "dimension_id": 2,
        "input_skill": "Ruby on Rails",
        "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": "Fullstack Developer",
            "id": 15,
            "rationale": null,
            "role_archetype": null,
            "slug": "full-stack-engineer",
            "source": "db"
          },
          {
            "display_name": "Fullstack Developer",
            "id": 435,
            "rationale": null,
            "role_archetype": "Engineering",
            "slug": "fullstack-developer",
            "source": "db"
          },
          {
            "display_name": "Java Backend Developer",
            "id": 79,
            "rationale": null,
            "role_archetype": "Engineering",
            "slug": "java-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"
          }
        ],
        "skill_dimension_saved": true,
        "skill_id": 10,
        "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": "GitLab",
        "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": 279,
        "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": "GitLab",
        "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": 279,
        "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": "e85a9814-a694-4e27-b9bc-bdf252ef233c"
}

LLM Calls

Every model call made for this run, in pipeline order. Click a card to see the model's response.

Loading…