← Back to history

Pipeline run

84e9a01e-215f-4eea-aaa8-71df2717cfd1

Pipeline LLM cost (USD)
API 1: $0.0102 API 2: $0.0001 API 3: $0.0000 Total: $0.0103

Client output enrichment

v2 Skill cluster · Nature of work · AI index · Tech stack maturity · Evidence · KRA description
role baseline loaded sources · ai_index: jd · nature_of_work: jd · tech_stack_maturity: jd
Nature of work · Data access and persistence
Designs and codes software solutions, including database models and technical feasibility, then tests, debugs, documents, and supports fixes for product issues.
"Model, design and implement databases."
Tech stack maturity
Mainstream Legacy
Backend development with debugging, SQL, and unit-testing as primary skills is most commonly associated with established, broadly used server-side systems rather than cloud-native or bleeding-edge stacks.
AI index (0 = no AI use, 5 = totally AI-dependent · v2.1)
0.20 / 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): fine-tuning
Evidence — skills matched in JD (5)
SQL Database Design Unit Testing Performance Testing Debugging
Skill cluster (1 dimension groups, role-scoped)
Cross-cutting / unaligned
SQL Database Design Unit Testing Performance Testing Debugging
Show KRA description ↓
• Has working experience and advanced and specialized technical/functional knowledge in own discipline. Understands how own area contributes to the business. Acts as a reference for colleagues with less experience and supports junior team members. • Influences decisions related to own activity, anticipating dependencies and consequences in complex scenarios, contributes to transversal projects, proposes improvements to processes and is accountable for own and team commitments. • Works independently within plan dictated by manager, with some guidance on most complex situations. • Analyse specifications _ Define user requirements for the development of new (or upgrade of existing) software solutions. • Design systems and code _ Design technical solutions and perform feasibility studies. _ Propose viable technical solutions to Product Management and/or users for validation. _ Develop software according to Amadeus standards. _ Model, design and implement databases. • Test and maintain the software _ Conduct unit, package and performance tests and ensure a level of quality in line with the Amadeus guidelines. _ Participate in the validation phase of the product cycle, fine-tuning when necessary to finalize the product. _ Support the customer by debugging existing solutions in collaboration with Product Manager or Product Definition Analyst • Document your work _ Produce software documentation necessary for the application and issue it to the requesting departments.

Signals

Skill data-engineer
0.20
Alias backend-engineer
1.00
KRA full-stack-engineer
0.57

Post-classification

Centroidupdated · n=1747
Alias collision log
New-role queue
New skills captured2
New KRA captured

Captured for admin review

Database Design primary Backend Developer pending
Performance Testing primary Backend Developer pending
Status: completed Created: 2026-05-27T17:39:51.557674Z Updated: 2026-05-27T17:40:22.488334Z API 3 duration: 3688 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

domain · Software Engineering CASE DOMAIN

slug: backend-engineer · id: 1 · source: db

Domain=Software Engineering; The JD focuses on analyzing specifications, designing technical solutions, modeling databases, testing, debugging, and producing software documentation—typical backend/software engineering responsibilities rather than UI, mobile, or platform-specialized work.

Matched skills

Design systemsdatabasesunit testspackage testsperformance testsdebuggingsoftware documentationfeasibility studiestechnical solutions

Matched dimensions

Backend Software EngineeringSystem DesignDatabase DesignSoftware Testing and Quality AssuranceRequirements AnalysisProduction Support and DebuggingTechnical Documentation

Matched KRAs

Analyse specificationsDefine user requirements for software solutionsDesign technical solutions and perform feasibility studiesPropose viable technical solutions to Product ManagementDevelop software according to Amadeus standardsModel, design and implement databasesConduct unit, package and performance testsParticipate in the validation phase of the product cycleSupport the customer by debugging existing solutionsProduce software documentation necessary for the application

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

0
New skills
0
Skill↔dim saved
0
Role↔dim saved
2
Skipped

Job description

Job Title

Software Development Engineer 4

Common Accountabilities

• Has working experience and advanced and specialized technical/functional knowledge in own discipline. Understands how own area contributes to the business. Acts as a reference for colleagues with less experience and supports junior team members.
• Influences decisions related to own activity, anticipating dependencies and consequences in complex scenarios, contributes to transversal projects, proposes improvements to processes and is accountable for own and team commitments.
• Works independently within plan dictated by manager, with some guidance on most complex situations.


Specific Accountabilities

• Analyse specifications


_ Define user requirements for the development of new (or upgrade of existing) software solutions.

• Design systems and code


_ Design technical solutions and perform feasibility studies.

_ Propose viable technical solutions to Product Management and/or users for validation.

_ Develop software according to Amadeus standards.

_ Model, design and implement databases.

• Test and maintain the software


_ Conduct unit, package and performance tests and ensure a level of quality in line with the Amadeus guidelines.

_ Participate in the validation phase of the product cycle, fine-tuning when necessary to finalize the product.

_ Support the customer by debugging existing solutions in collaboration with Product Manager or Product Definition Analyst

• Document your work


_ Produce software documentation necessary for the application and issue it to the requesting departments.

Diversity & Inclusion

We are an Equal Opportunity Employer and seek to hire the best candidate regardless of age, beliefs, disability, ethnicity, gender or sexual orientation.

Skills from this JD

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

SQL Primary Library skill API 3: existing canonical (in_db) Existing skill (matched library)
Canonical: SQL id=101 · sql

Aliases — catalog

  • SQL (CANONICAL) primary

Context tags (catalog)

ACID CTE DDL DML ETL JOIN MySQL NoSQL OLAP ORM PostgreSQL SQL injection SQLite T-SQL data modeling data warehousing database normalization execution plan indexing joins normalization query optimization stored procedures subquery transaction isolation transaction management window functions

Stored enrichment (catalog DB)

Category
Language
Sub-category
Query Language
Vendor
ANSI
License
unknown
Year introduced
1974
Confidence
0.99
Version strategy
NOT_APPLICABLE

Maturity reasoning: SQL appears in a large share of data, backend, and analytics job descriptions and remains the default query language for PostgreSQL, MySQL, and cloud warehouses like Snowflake/BigQuery.

Skill profile (library / DB)

Skill nature
LANGUAGE
Volatility
STABLE
Typical lifespan
EVERGREEN
Category id
6
Sub-category id
97
Extractable
True
Also category
False

Dimensions (API 2 worklist)

  • Pega Programming Languages & DSLs Catalog dimension db id 267

    Library dimension (catalog)

    Roles linked in library: Pega Developer

  • Programming Languages & DSLs Catalog dimension db id 475

    Library dimension (catalog)

    Roles linked in library: Engineering Manager

  • Programming Languages for Data Work Catalog dimension db id 21

    Library dimension (catalog)

    Roles linked in library: Data Engineer

API 3 link attempts (this skill)

Dimension Skill↔dim Role↔dim Outcome
Pega Programming Languages & DSLs
pega-programming-languages-dsls
Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role)
Programming Languages & DSLs
programming-languages-dsls
Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role)
Programming Languages for Data Work
programming-languages-for-data-work
Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role)
Database Design Primary Library skill API 3: existing canonical (in_db) Existing skill (matched library)
Canonical: schema design id=19 · schema-design

Aliases — catalog

  • schema design (CANONICAL) primary
  • Schema Design (CANONICAL)

Context tags (catalog)

ACID DDL ER modeling ERD NoSQL SQL cardinality constraints data governance data integrity data lineage data model data modeling data normalization data types data warehouse database design database normalization database optimization database schema denormalization dimensional modeling entity relationship entity-relationship entity-relationship diagram foreign key foreign keys indexes indexing metadata management normalization primary key primary keys query optimization relational relational databases relational model relational schema schema evolution schema migration snowflake schema star schema

Stored enrichment (catalog DB)

Category
Concept
Sub-category
Database Schema Design
Confidence
0.84
Version strategy
NOT_APPLICABLE

Maturity reasoning: Schema design is a standard requirement in backend/data JDs and appears across SQL, data engineering, and SaaS roles; it’s a core interview topic rather than a niche specialty.

Skill profile (library / DB)

Skill nature
CONCEPT
Volatility
STABLE
Typical lifespan
EVERGREEN
Category id
2
Sub-category id
2479
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

API 3 link attempts (this skill)

Dimension Skill↔dim Role↔dim Outcome
Relational Data Modeling
relational-data-modeling
Skipped — no persistable v3 meta for new skill
skill_not_in_db_v3_proposed
Relational Database Design
relational-database-design
Skipped — no persistable v3 meta for new skill
skill_not_in_db_v3_proposed
Unit Testing Primary Library skill API 3: existing canonical (in_db) Existing skill (matched library)
Canonical: Unit Testing id=517 · unit-testing

Aliases — catalog

  • Unit Testing (CANONICAL)

Context tags (catalog)

JUnit NUnit TDD arrange-act-assert assertions code coverage fixtures mocking pytest regression stubs test cases test doubles test runner xUnit

Stored enrichment (catalog DB)

Category
Methodology
Sub-category
Testing Methodology
Confidence
0.98
Version strategy
NOT_APPLICABLE

Maturity reasoning: Unit testing is a standard hiring requirement across software JDs and appears in mainstream frameworks/docs; GitHub and Stack Overflow usage remain consistently high, with no successor replacing it.

Skill profile (library / DB)

Skill nature
METHODOLOGY
Volatility
STABLE
Typical lifespan
EVERGREEN
Category id
8
Sub-category id
44
Extractable
True
Also category
False

Dimensions (API 2 worklist)

  • React Frontend Development Catalog dimension db id 96

    Library dimension (catalog)

API 3 link attempts (this skill)

Dimension Skill↔dim Role↔dim Outcome
React Frontend Development
d_init_01
Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role)
Performance Testing Primary 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
Testing Tools
Sub-category
general
Skill nature
PRACTICE
Volatility
MEDIUM
Typical lifespan
MULTI_YEAR
Version strategy
UNVERSIONED
Debugging Primary Library skill API 3: existing canonical (in_db) Existing skill (matched library)
Canonical: debugging id=4182 · debugging

Aliases — catalog

  • debugging (CANONICAL) primary

Context tags (catalog)

assertions breakpoints code review debugger debugging tools error handling interactive debugging logging memory leaks performance tuning profiling root cause analysis stack trace test-driven development unit tests watch expressions

Stored enrichment (catalog DB)

Category
Methodology
Sub-category
Debugging Methodology
Confidence
0.96
Version strategy
NOT_APPLICABLE

Maturity reasoning: Debugging is a universal hiring-pipeline skill across software JDs and interview loops; it appears in role requirements for backend, frontend, SRE, and QA, with no successor replacing it.

Skill profile (library / DB)

Skill nature
METHODOLOGY
Volatility
STABLE
Typical lifespan
EVERGREEN
Category id
8
Sub-category id
3293
Extractable
True
Also category
False

Dimensions (API 2 worklist)

  • Sitecore Troubleshooting and Maintenance Catalog dimension db id 447

    Library dimension (catalog)

    Roles linked in library: Sitecore Dev

API 3 link attempts (this skill)

Dimension Skill↔dim Role↔dim Outcome
Sitecore Troubleshooting and Maintenance
sitecore-troubleshooting-and-maintenance
Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role)

All API 3 persistence rows

Same grid as the skill-extractor “Persistence items” table: one row per (skill × dimension) work item.

Skill Tag Dimension Skill↔dim Role↔dim Outcome Notes
SQL in_db
Pega Programming Languages & DSLs
pega-programming-languages-dsls
Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role)
SQL in_db
Programming Languages & DSLs
programming-languages-dsls
Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role)
SQL in_db
Programming Languages for Data Work
programming-languages-for-data-work
Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role)
Database Design new
Relational Data Modeling
relational-data-modeling
Skipped — no persistable v3 meta for new skill skill_not_in_db_v3_proposed
Database Design new
Relational Database Design
relational-database-design
Skipped — no persistable v3 meta for new skill skill_not_in_db_v3_proposed
Unit Testing in_db
React Frontend Development
d_init_01
Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role)
Debugging in_db
Sitecore Troubleshooting and Maintenance
sitecore-troubleshooting-and-maintenance
Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role)

Library artifacts (this run)

Kind Detail DB id
canonical_skill_proposed Performance Testing | type=Testing Tools subtype=general nature=PRACTICE lifespan=MULTI_YEAR
dimension_skill_link_proposed Database Design ↔ Relational Data Modeling
dimension_skill_link_proposed Database Design ↔ Relational Database Design
role_dimension_link_proposed Backend Developer ↔ Relational Database Design
nano JD Parser — gpt-4.1-nano click to toggle
RoleSoftware Development Engineer 4
DomainOther
JD type pass
Show raw JSON
{
  "JD_type": "pass",
  "about_company": null,
  "certifications": [],
  "company_name": null,
  "ctc": null,
  "domain": {
    "primary": {
      "aliases": [],
      "domain": "Other"
    },
    "secondary": null
  },
  "education": [],
  "experience": null,
  "job_locations": [],
  "role": "Software Development Engineer 4",
  "role_aliases": [
    "SDE 4",
    "Senior Software Engineer",
    "Software Engineer IV"
  ],
  "role_archetype": "Engineering",
  "roles_and_responsibilities": [
    {
      "bullet_count": 3,
      "heading": "Common Accountabilities",
      "heading_was_present": true,
      "source_marker": {
        "first_5_words": "\u2022 Has working experience and",
        "last_5_words": "with some guidance on most"
      },
      "text": "\u2022 Has working experience and advanced and specialized technical/functional knowledge in own discipline. Understands how own area contributes to the business. Acts as a reference for colleagues with less experience and supports junior team members.\n\u2022 Influences decisions related to own activity, anticipating dependencies and consequences in complex scenarios, contributes to transversal projects, proposes improvements to processes and is accountable for own and team commitments.\n\u2022 Works independently within plan dictated by manager, with some guidance on most complex situations.",
      "word_count": 63
    },
    {
      "bullet_count": 10,
      "heading": "Specific Accountabilities",
      "heading_was_present": true,
      "source_marker": {
        "first_5_words": "\u2022 Analyse specifications\n\n_ Define user",
        "last_5_words": "to the requesting departments."
      },
      "text": "\u2022 Analyse specifications\n\n_ Define user requirements for the development of new (or upgrade of existing) software solutions.\n\n\u2022 Design systems and code\n\n_ Design technical solutions and perform feasibility studies.\n\n_ Propose viable technical solutions to Product Management and/or users for validation.\n\n_ Develop software according to Amadeus standards.\n\n_ Model, design and implement databases.\n\n\u2022 Test and maintain the software\n\n_ Conduct unit, package and performance tests and ensure a level of quality in line with the Amadeus guidelines.\n\n_ Participate in the validation phase of the product cycle, fine-tuning when necessary to finalize the product.\n\n_ Support the customer by debugging existing solutions in collaboration with Product Manager or Product Definition Analyst\n\n\u2022 Document your work\n\n_ Produce software documentation necessary for the application and issue it to the requesting departments.",
      "word_count": 186
    }
  ],
  "urls": []
}
API 1 — extract-from-jd click to toggle
{
  "final_skills": [
    {
      "is_primary": true,
      "skill_name": "SQL"
    },
    {
      "is_primary": true,
      "skill_name": "Database Design"
    },
    {
      "is_primary": true,
      "skill_name": "Unit Testing"
    },
    {
      "is_primary": true,
      "skill_name": "Performance Testing"
    },
    {
      "is_primary": true,
      "skill_name": "Debugging"
    }
  ],
  "jd_role": {
    "display_name": "Software Development Engineer 4",
    "rationale": null,
    "role_aliases": [
      "SDE 4",
      "Senior Software Engineer",
      "Software Engineer IV"
    ],
    "role_archetype": "Engineering",
    "slug": ""
  },
  "nano_parsed": {
    "JD_type": "pass",
    "about_company": null,
    "certifications": [],
    "company_name": null,
    "ctc": null,
    "domain": {
      "primary": {
        "aliases": [],
        "domain": "Other"
      },
      "secondary": null
    },
    "education": [],
    "experience": null,
    "job_locations": [],
    "role": "Software Development Engineer 4",
    "role_aliases": [
      "SDE 4",
      "Senior Software Engineer",
      "Software Engineer IV"
    ],
    "role_archetype": "Engineering",
    "roles_and_responsibilities": [
      {
        "bullet_count": 3,
        "heading": "Common Accountabilities",
        "heading_was_present": true,
        "source_marker": {
          "first_5_words": "\u2022 Has working experience and",
          "last_5_words": "with some guidance on most"
        },
        "text": "\u2022 Has working experience and advanced and specialized technical/functional knowledge in own discipline. Understands how own area contributes to the business. Acts as a reference for colleagues with less experience and supports junior team members.\n\u2022 Influences decisions related to own activity, anticipating dependencies and consequences in complex scenarios, contributes to transversal projects, proposes improvements to processes and is accountable for own and team commitments.\n\u2022 Works independently within plan dictated by manager, with some guidance on most complex situations.",
        "word_count": 63
      },
      {
        "bullet_count": 10,
        "heading": "Specific Accountabilities",
        "heading_was_present": true,
        "source_marker": {
          "first_5_words": "\u2022 Analyse specifications\n\n_ Define user",
          "last_5_words": "to the requesting departments."
        },
        "text": "\u2022 Analyse specifications\n\n_ Define user requirements for the development of new (or upgrade of existing) software solutions.\n\n\u2022 Design systems and code\n\n_ Design technical solutions and perform feasibility studies.\n\n_ Propose viable technical solutions to Product Management and/or users for validation.\n\n_ Develop software according to Amadeus standards.\n\n_ Model, design and implement databases.\n\n\u2022 Test and maintain the software\n\n_ Conduct unit, package and performance tests and ensure a level of quality in line with the Amadeus guidelines.\n\n_ Participate in the validation phase of the product cycle, fine-tuning when necessary to finalize the product.\n\n_ Support the customer by debugging existing solutions in collaboration with Product Manager or Product Definition Analyst\n\n\u2022 Document your work\n\n_ Produce software documentation necessary for the application and issue it to the requesting departments.",
        "word_count": 186
      }
    ],
    "urls": []
  },
  "rejected": false,
  "rejection_reason": null,
  "run_id": "84e9a01e-215f-4eea-aaa8-71df2717cfd1",
  "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": "_ Model, design and implement databases.",
            "similarity": 0.6177
          },
          {
            "kra_text": "Works closely with product managers and UX designers to translate requirements and wireframes into working software features through iterative development.",
            "sentence": "_ Propose viable technical solutions to Product Management and/or users for validation.",
            "similarity": 0.556
          },
          {
            "kra_text": "Works closely with product managers and UX designers to translate requirements and wireframes into working software features through iterative development.",
            "sentence": "_ Participate in the validation phase of the product cycle, fine-tuning when necessary to finalize the product.",
            "similarity": 0.5373
          }
        ],
        "matched_count": null,
        "matched_skills": null,
        "role_id": 15,
        "score": 0.5703,
        "slug": "full-stack-engineer",
        "total_count": null
      },
      {
        "display_name": "Angular Frontend Developer",
        "kra_matches": [
          {
            "kra_text": "collaboration with design and QA",
            "sentence": "_ Support the customer by debugging existing solutions in collaboration with Product Manager or Product Definition Analyst",
            "similarity": 0.5195
          },
          {
            "kra_text": "collaboration with design and QA",
            "sentence": "_ Propose viable technical solutions to Product Management and/or users for validation.",
            "similarity": 0.4946
          },
          {
            "kra_text": "collaboration with design and QA",
            "sentence": "_ Participate in the validation phase of the product cycle, fine-tuning when necessary to finalize the product.",
            "similarity": 0.4684
          }
        ],
        "matched_count": null,
        "matched_skills": null,
        "role_id": 90,
        "score": 0.4941,
        "slug": "angular-frontend-developer",
        "total_count": null
      },
      {
        "display_name": "Flutter Developer",
        "kra_matches": [
          {
            "kra_text": "collaborate with design, product, and backend teams",
            "sentence": "_ Support the customer by debugging existing solutions in collaboration with Product Manager or Product Definition Analyst",
            "similarity": 0.5139
          },
          {
            "kra_text": "collaborate with design, product, and backend teams",
            "sentence": "_ Propose viable technical solutions to Product Management and/or users for validation.",
            "similarity": 0.4999
          },
          {
            "kra_text": "translate product and design requirements",
            "sentence": "_ Define user requirements for the development of new (or upgrade of existing) software solutions.",
            "similarity": 0.4676
          }
        ],
        "matched_count": null,
        "matched_skills": null,
        "role_id": 74,
        "score": 0.4938,
        "slug": "flutter-developer",
        "total_count": null
      },
      {
        "display_name": "Pega Developer",
        "kra_matches": [
          {
            "kra_text": "defect troubleshooting and resolution",
            "sentence": "_ Support the customer by debugging existing solutions in collaboration with Product Manager or Product Definition Analyst",
            "similarity": 0.5007
          },
          {
            "kra_text": "Requirements analysis and process translation",
            "sentence": "_ Define user requirements for the development of new (or upgrade of existing) software solutions.",
            "similarity": 0.4943
          },
          {
            "kra_text": "user interaction design and refinement",
            "sentence": "_ Participate in the validation phase of the product cycle, fine-tuning when necessary to finalize the product.",
            "similarity": 0.4772
          }
        ],
        "matched_count": null,
        "matched_skills": null,
        "role_id": 24,
        "score": 0.4908,
        "slug": "pega-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": "_ Model, design and implement databases.",
            "similarity": 0.5101
          },
          {
            "kra_text": "Investigates and resolves production incidents, API bugs, and service degradation through root cause analysis, hotfixes, and post-mortems.",
            "sentence": "_ Support the customer by debugging existing solutions in collaboration with Product Manager or Product Definition Analyst",
            "similarity": 0.5053
          },
          {
            "kra_text": "Investigates and resolves production incidents, API bugs, and service degradation through root cause analysis, hotfixes, and post-mortems.",
            "sentence": "_ Produce software documentation necessary for the application and issue it to the requesting departments.",
            "similarity": 0.4291
          }
        ],
        "matched_count": null,
        "matched_skills": null,
        "role_id": 1,
        "score": 0.4815,
        "slug": "backend-engineer",
        "total_count": null
      }
    ],
    "skill_match_roles": [
      {
        "display_name": "Data Engineer",
        "kra_matches": null,
        "matched_count": 1,
        "matched_skills": [
          "SQL"
        ],
        "role_id": 2,
        "score": 0.2,
        "slug": "data-engineer",
        "total_count": 5
      },
      {
        "display_name": "Pega Developer",
        "kra_matches": null,
        "matched_count": 1,
        "matched_skills": [
          "SQL"
        ],
        "role_id": 24,
        "score": 0.2,
        "slug": "pega-developer",
        "total_count": 5
      },
      {
        "display_name": "Engineering Manager",
        "kra_matches": null,
        "matched_count": 1,
        "matched_skills": [
          "SQL"
        ],
        "role_id": 121,
        "score": 0.2,
        "slug": "engineering-manager",
        "total_count": 5
      },
      {
        "display_name": "Sitecore Dev",
        "kra_matches": null,
        "matched_count": 1,
        "matched_skills": [
          "debugging"
        ],
        "role_id": 233,
        "score": 0.2,
        "slug": "sitecore-dev",
        "total_count": 5
      }
    ]
  },
  "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.92,
      "slug": "backend-engineer",
      "total_count": null
    },
    "confidence": 0.92,
    "is_new_role": false,
    "llm2_fired": false,
    "llm2_reasoning": null,
    "matched_dimensions": [
      "Backend Software Engineering",
      "System Design",
      "Database Design",
      "Software Testing and Quality Assurance",
      "Requirements Analysis",
      "Production Support and Debugging",
      "Technical Documentation"
    ],
    "matched_kras": [
      "Analyse specifications",
      "Define user requirements for software solutions",
      "Design technical solutions and perform feasibility studies",
      "Propose viable technical solutions to Product Management",
      "Develop software according to Amadeus standards",
      "Model, design and implement databases",
      "Conduct unit, package and performance tests",
      "Participate in the validation phase of the product cycle",
      "Support the customer by debugging existing solutions",
      "Produce software documentation necessary for the application"
    ],
    "matched_skills": [
      "Design systems",
      "databases",
      "unit tests",
      "package tests",
      "performance tests",
      "debugging",
      "software documentation",
      "feasibility studies",
      "technical solutions"
    ],
    "new_role_display_name": null,
    "new_role_slug": null,
    "queued": false,
    "reasoning": "Domain=Software Engineering; The JD focuses on analyzing specifications, designing technical solutions, modeling databases, testing, debugging, and producing software documentation\u2014typical backend/software engineering responsibilities rather than UI, mobile, or platform-specialized work.",
    "sub_role": null
  },
  "stage5_updates": {
    "centroid_n_after": 1747,
    "centroid_updated": true,
    "collision_log_id": null,
    "new_kra_attached": null,
    "new_skills_attached": [
      {
        "is_primary": true,
        "queue_id": 25006,
        "role_display_name": "Backend Developer",
        "role_slug": "backend-engineer",
        "skill_name": "Database Design",
        "status": "pending"
      },
      {
        "is_primary": true,
        "queue_id": 25007,
        "role_display_name": "Backend Developer",
        "role_slug": "backend-engineer",
        "skill_name": "Performance Testing",
        "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": 271,
      "existing_alias_text": "SQL",
      "input_term": "SQL",
      "matched_canonical": {
        "category_id": 6,
        "display_name": "SQL",
        "id": 101,
        "is_also_category": false,
        "is_extractable": true,
        "skill_nature": "LANGUAGE",
        "slug": "sql",
        "sub_category_id": 97,
        "typical_lifespan": "EVERGREEN",
        "volatility": "STABLE"
      },
      "matched_via": "alias"
    },
    {
      "alias_persist_skipped_reason": "TODO: REMOVE AFTER TESTING \u2014 alias DB write disabled",
      "alias_persisted": false,
      "existing_alias_id": 5581,
      "existing_alias_text": "Schema Design",
      "input_term": "Database Design",
      "matched_canonical": {
        "category_id": 2,
        "display_name": "schema design",
        "id": 19,
        "is_also_category": false,
        "is_extractable": true,
        "skill_nature": "CONCEPT",
        "slug": "schema-design",
        "sub_category_id": 2479,
        "typical_lifespan": "EVERGREEN",
        "volatility": "STABLE"
      },
      "matched_via": "embedding_alias"
    },
    {
      "alias_persist_skipped_reason": "alias_text already exists for this canonical skill",
      "alias_persisted": false,
      "existing_alias_id": 865,
      "existing_alias_text": "Unit Testing",
      "input_term": "Unit Testing",
      "matched_canonical": {
        "category_id": 8,
        "display_name": "Unit Testing",
        "id": 517,
        "is_also_category": false,
        "is_extractable": true,
        "skill_nature": "METHODOLOGY",
        "slug": "unit-testing",
        "sub_category_id": 44,
        "typical_lifespan": "EVERGREEN",
        "volatility": "STABLE"
      },
      "matched_via": "alias"
    },
    {
      "alias_persist_skipped_reason": "alias_text already exists for this canonical skill",
      "alias_persisted": false,
      "existing_alias_id": 5905,
      "existing_alias_text": "debugging",
      "input_term": "Debugging",
      "matched_canonical": {
        "category_id": 8,
        "display_name": "debugging",
        "id": 4182,
        "is_also_category": false,
        "is_extractable": true,
        "skill_nature": "METHODOLOGY",
        "slug": "debugging",
        "sub_category_id": 3293,
        "typical_lifespan": "EVERGREEN",
        "volatility": "STABLE"
      },
      "matched_via": "alias"
    }
  ],
  "candidate_roles": [
    {
      "display_name": "Pega Developer",
      "id": 24,
      "rationale": null,
      "role_archetype": null,
      "slug": "pega-developer",
      "source": "db"
    },
    {
      "display_name": "Engineering Manager",
      "id": 121,
      "rationale": null,
      "role_archetype": null,
      "slug": "engineering-manager",
      "source": "db"
    },
    {
      "display_name": "Data Engineer",
      "id": 2,
      "rationale": null,
      "role_archetype": null,
      "slug": "data-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": "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": "Sitecore Dev",
      "id": 233,
      "rationale": null,
      "role_archetype": "Engineering",
      "slug": "sitecore-dev",
      "source": "db"
    }
  ],
  "chosen_role": {
    "display_name": "Backend Developer",
    "id": 1,
    "rationale": "Domain=Software Engineering; The JD focuses on analyzing specifications, designing technical solutions, modeling databases, testing, debugging, and producing software documentation\u2014typical backend/software engineering responsibilities rather than UI, mobile, or platform-specialized work.",
    "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": "Pega Programming Languages \u0026 DSLs",
        "id": 267,
        "rationale": "Programming languages and domain-specific languages used in Pega development.",
        "slug": "pega-programming-languages-dsls",
        "source": "db"
      },
      "input_skill": "SQL",
      "llm_role": null,
      "roles_from_db": [
        {
          "display_name": "Pega Developer",
          "id": 24,
          "rationale": null,
          "role_archetype": null,
          "slug": "pega-developer",
          "source": "db"
        }
      ]
    },
    {
      "dimension": {
        "difficulty_hint": "well_known",
        "display_name": "Programming Languages \u0026 DSLs",
        "id": 475,
        "rationale": "Oversee and guide the selection and effective use of programming and domain\u2010specific languages in software projects.",
        "slug": "programming-languages-dsls",
        "source": "db"
      },
      "input_skill": "SQL",
      "llm_role": null,
      "roles_from_db": [
        {
          "display_name": "Engineering Manager",
          "id": 121,
          "rationale": null,
          "role_archetype": null,
          "slug": "engineering-manager",
          "source": "db"
        }
      ]
    },
    {
      "dimension": {
        "difficulty_hint": "well_known",
        "display_name": "Programming Languages for Data Work",
        "id": 21,
        "rationale": "Languages used to implement data pipelines, transformations, and operational glue. This is the primary coding surface for building ingestion, enrichment, and automation logic in data engineering.",
        "slug": "programming-languages-for-data-work",
        "source": "db"
      },
      "input_skill": "SQL",
      "llm_role": null,
      "roles_from_db": [
        {
          "display_name": "Data Engineer",
          "id": 2,
          "rationale": null,
          "role_archetype": null,
          "slug": "data-engineer",
          "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": "Database Design",
      "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": "Database Design",
      "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": "React Frontend Development",
        "id": 96,
        "rationale": "Building interactive web user interfaces with React.js, including component composition, state management, hooks, and rendering patterns. React.js belongs here because it is a core library for client-side UI development in modern web applications.",
        "slug": "d_init_01",
        "source": "db"
      },
      "input_skill": "Unit Testing",
      "llm_role": null,
      "roles_from_db": []
    },
    {
      "dimension": {
        "difficulty_hint": "well_known",
        "display_name": "Sitecore Troubleshooting and Maintenance",
        "id": 447,
        "rationale": "Diagnosing defects, regressions, and maintainability issues across Sitecore code, configuration, and content behavior. This is a coherent cluster because the role is expected to stabilize the site experience over time.",
        "slug": "sitecore-troubleshooting-and-maintenance",
        "source": "db"
      },
      "input_skill": "Debugging",
      "llm_role": null,
      "roles_from_db": [
        {
          "display_name": "Sitecore Dev",
          "id": 233,
          "rationale": null,
          "role_archetype": "Engineering",
          "slug": "sitecore-dev",
          "source": "db"
        }
      ]
    }
  ],
  "input_final_skills": [
    "SQL",
    "Database Design",
    "Unit Testing",
    "Performance Testing",
    "Debugging"
  ],
  "input_llm_skills": [
    "SQL",
    "Database Design",
    "Unit Testing",
    "Performance Testing",
    "Debugging"
  ],
  "new_aliases_persisted": 0,
  "run_id": "84e9a01e-215f-4eea-aaa8-71df2717cfd1",
  "skills_detail": [
    {
      "aliases_in_db": [
        {
          "alias_text": "SQL",
          "alias_type": "CANONICAL",
          "id": 271,
          "is_primary": true,
          "match_strategy": "CASE_INSENSITIVE"
        }
      ],
      "canonical": {
        "category_id": 6,
        "display_name": "SQL",
        "id": 101,
        "is_also_category": false,
        "is_extractable": true,
        "skill_nature": "LANGUAGE",
        "slug": "sql",
        "sub_category_id": 97,
        "typical_lifespan": "EVERGREEN",
        "volatility": "STABLE"
      },
      "dimensions": [
        {
          "dimension": {
            "difficulty_hint": "well_known",
            "display_name": "Pega Programming Languages \u0026 DSLs",
            "id": 267,
            "rationale": "Programming languages and domain-specific languages used in Pega development.",
            "slug": "pega-programming-languages-dsls",
            "source": "db"
          },
          "input_skill": "SQL",
          "llm_role": null,
          "roles_from_db": [
            {
              "display_name": "Pega Developer",
              "id": 24,
              "rationale": null,
              "role_archetype": null,
              "slug": "pega-developer",
              "source": "db"
            }
          ]
        },
        {
          "dimension": {
            "difficulty_hint": "well_known",
            "display_name": "Programming Languages \u0026 DSLs",
            "id": 475,
            "rationale": "Oversee and guide the selection and effective use of programming and domain\u2010specific languages in software projects.",
            "slug": "programming-languages-dsls",
            "source": "db"
          },
          "input_skill": "SQL",
          "llm_role": null,
          "roles_from_db": [
            {
              "display_name": "Engineering Manager",
              "id": 121,
              "rationale": null,
              "role_archetype": null,
              "slug": "engineering-manager",
              "source": "db"
            }
          ]
        },
        {
          "dimension": {
            "difficulty_hint": "well_known",
            "display_name": "Programming Languages for Data Work",
            "id": 21,
            "rationale": "Languages used to implement data pipelines, transformations, and operational glue. This is the primary coding surface for building ingestion, enrichment, and automation logic in data engineering.",
            "slug": "programming-languages-for-data-work",
            "source": "db"
          },
          "input_skill": "SQL",
          "llm_role": null,
          "roles_from_db": [
            {
              "display_name": "Data Engineer",
              "id": 2,
              "rationale": null,
              "role_archetype": null,
              "slug": "data-engineer",
              "source": "db"
            }
          ]
        }
      ],
      "input_skill": "SQL",
      "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": "schema design",
          "alias_type": "CANONICAL",
          "id": 147,
          "is_primary": true,
          "match_strategy": "CASE_INSENSITIVE"
        },
        {
          "alias_text": "Schema Design",
          "alias_type": "CANONICAL",
          "id": 5581,
          "is_primary": false,
          "match_strategy": "CASE_INSENSITIVE"
        }
      ],
      "canonical": {
        "category_id": 2,
        "display_name": "schema design",
        "id": 19,
        "is_also_category": false,
        "is_extractable": true,
        "skill_nature": "CONCEPT",
        "slug": "schema-design",
        "sub_category_id": 2479,
        "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": "Database Design",
          "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": "Database Design",
          "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"
            }
          ]
        }
      ],
      "input_skill": "Database Design",
      "matched_via": "embedding_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": "Unit Testing",
          "alias_type": "CANONICAL",
          "id": 865,
          "is_primary": false,
          "match_strategy": "CASE_INSENSITIVE"
        }
      ],
      "canonical": {
        "category_id": 8,
        "display_name": "Unit Testing",
        "id": 517,
        "is_also_category": false,
        "is_extractable": true,
        "skill_nature": "METHODOLOGY",
        "slug": "unit-testing",
        "sub_category_id": 44,
        "typical_lifespan": "EVERGREEN",
        "volatility": "STABLE"
      },
      "dimensions": [
        {
          "dimension": {
            "difficulty_hint": "well_known",
            "display_name": "React Frontend Development",
            "id": 96,
            "rationale": "Building interactive web user interfaces with React.js, including component composition, state management, hooks, and rendering patterns. React.js belongs here because it is a core library for client-side UI development in modern web applications.",
            "slug": "d_init_01",
            "source": "db"
          },
          "input_skill": "Unit Testing",
          "llm_role": null,
          "roles_from_db": []
        }
      ],
      "input_skill": "Unit Testing",
      "matched_via": "alias",
      "new_alias_persisted": false,
      "new_alias_text": null,
      "new_skill_meta": null,
      "source_tag": "db",
      "was_in_llm_skills": true
    },
    {
      "aliases_in_db": [],
      "canonical": null,
      "dimensions": [],
      "input_skill": "Performance 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": "performance-testing",
        "split_log": [],
        "typed": null,
        "warnings": []
      },
      "source_tag": "llm",
      "was_in_llm_skills": true
    },
    {
      "aliases_in_db": [
        {
          "alias_text": "debugging",
          "alias_type": "CANONICAL",
          "id": 5905,
          "is_primary": true,
          "match_strategy": "CASE_INSENSITIVE"
        }
      ],
      "canonical": {
        "category_id": 8,
        "display_name": "debugging",
        "id": 4182,
        "is_also_category": false,
        "is_extractable": true,
        "skill_nature": "METHODOLOGY",
        "slug": "debugging",
        "sub_category_id": 3293,
        "typical_lifespan": "EVERGREEN",
        "volatility": "STABLE"
      },
      "dimensions": [
        {
          "dimension": {
            "difficulty_hint": "well_known",
            "display_name": "Sitecore Troubleshooting and Maintenance",
            "id": 447,
            "rationale": "Diagnosing defects, regressions, and maintainability issues across Sitecore code, configuration, and content behavior. This is a coherent cluster because the role is expected to stabilize the site experience over time.",
            "slug": "sitecore-troubleshooting-and-maintenance",
            "source": "db"
          },
          "input_skill": "Debugging",
          "llm_role": null,
          "roles_from_db": [
            {
              "display_name": "Sitecore Dev",
              "id": 233,
              "rationale": null,
              "role_archetype": "Engineering",
              "slug": "sitecore-dev",
              "source": "db"
            }
          ]
        }
      ],
      "input_skill": "Debugging",
      "matched_via": "alias",
      "new_alias_persisted": false,
      "new_alias_text": null,
      "new_skill_meta": null,
      "source_tag": "db",
      "was_in_llm_skills": true
    }
  ],
  "unmatched_skills": [
    "Performance Testing"
  ]
}
API 3 — final-role-output
{
  "chosen_role": {
    "display_name": "Backend Developer",
    "id": 1,
    "rationale": "Domain=Software Engineering; The JD focuses on analyzing specifications, designing technical solutions, modeling databases, testing, debugging, and producing software documentation\u2014typical backend/software engineering responsibilities rather than UI, mobile, or platform-specialized work.",
    "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": "SQL",
      "tag": "in_db"
    },
    {
      "skill": "Database Design",
      "tag": "in_db"
    },
    {
      "skill": "Unit Testing",
      "tag": "in_db"
    },
    {
      "skill": "Performance Testing",
      "tag": "new"
    },
    {
      "skill": "Debugging",
      "tag": "in_db"
    }
  ],
  "llm_cost_api1_usd": null,
  "llm_cost_api2_usd": null,
  "llm_cost_api3_usd": null,
  "llm_cost_total_usd": null,
  "persistence": {
    "items": [
      {
        "chosen_role_id": 1,
        "dimension": {
          "difficulty_hint": "well_known",
          "display_name": "Pega Programming Languages \u0026 DSLs",
          "id": 267,
          "rationale": "Programming languages and domain-specific languages used in Pega development.",
          "slug": "pega-programming-languages-dsls",
          "source": "db"
        },
        "dimension_id": 267,
        "input_skill": "SQL",
        "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": "Pega Developer",
            "id": 24,
            "rationale": null,
            "role_archetype": null,
            "slug": "pega-developer",
            "source": "db"
          }
        ],
        "skill_dimension_saved": true,
        "skill_id": 101,
        "skill_tag": "in_db",
        "skipped_reason": null
      },
      {
        "chosen_role_id": 1,
        "dimension": {
          "difficulty_hint": "well_known",
          "display_name": "Programming Languages \u0026 DSLs",
          "id": 475,
          "rationale": "Oversee and guide the selection and effective use of programming and domain\u2010specific languages in software projects.",
          "slug": "programming-languages-dsls",
          "source": "db"
        },
        "dimension_id": 475,
        "input_skill": "SQL",
        "llm_role": null,
        "matched_chosen_role": false,
        "outcome_line": "Existing dimension (library) \u00b7 Role\u2194dimension skipped (dimension not under chosen role)",
        "role_dimension_saved": false,
        "roles_from_db": [
          {
            "display_name": "Engineering Manager",
            "id": 121,
            "rationale": null,
            "role_archetype": null,
            "slug": "engineering-manager",
            "source": "db"
          }
        ],
        "skill_dimension_saved": true,
        "skill_id": 101,
        "skill_tag": "in_db",
        "skipped_reason": null
      },
      {
        "chosen_role_id": 1,
        "dimension": {
          "difficulty_hint": "well_known",
          "display_name": "Programming Languages for Data Work",
          "id": 21,
          "rationale": "Languages used to implement data pipelines, transformations, and operational glue. This is the primary coding surface for building ingestion, enrichment, and automation logic in data engineering.",
          "slug": "programming-languages-for-data-work",
          "source": "db"
        },
        "dimension_id": 21,
        "input_skill": "SQL",
        "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": "Data Engineer",
            "id": 2,
            "rationale": null,
            "role_archetype": null,
            "slug": "data-engineer",
            "source": "db"
          }
        ],
        "skill_dimension_saved": true,
        "skill_id": 101,
        "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": "Database Design",
        "llm_role": null,
        "matched_chosen_role": false,
        "outcome_line": "Skipped \u2014 no persistable v3 meta for new skill",
        "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": false,
        "skill_id": null,
        "skill_tag": "new",
        "skipped_reason": "skill_not_in_db_v3_proposed"
      },
      {
        "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": "Database Design",
        "llm_role": null,
        "matched_chosen_role": true,
        "outcome_line": "Skipped \u2014 no persistable v3 meta for new skill",
        "role_dimension_saved": false,
        "roles_from_db": [
          {
            "display_name": ".NET Backend Developer",
            "id": 83,
            "rationale": null,
            "role_archetype": "Engineering",
            "slug": "dotnet-backend-developer",
            "source": "db"
          },
          {
            "display_name": "Backend Developer",
            "id": 1,
            "rationale": null,
            "role_archetype": "A Backend Engineer designs, builds, and maintains the server-side logic and data handling that power applications and services. They focus on implementing reliable business functionality, integrating with other systems, and ensuring the backend is scalable, maintainable, and observable.",
            "slug": "backend-engineer",
            "source": "db"
          },
          {
            "display_name": "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": false,
        "skill_id": null,
        "skill_tag": "new",
        "skipped_reason": "skill_not_in_db_v3_proposed"
      },
      {
        "chosen_role_id": 1,
        "dimension": {
          "difficulty_hint": "well_known",
          "display_name": "React Frontend Development",
          "id": 96,
          "rationale": "Building interactive web user interfaces with React.js, including component composition, state management, hooks, and rendering patterns. React.js belongs here because it is a core library for client-side UI development in modern web applications.",
          "slug": "d_init_01",
          "source": "db"
        },
        "dimension_id": 96,
        "input_skill": "Unit Testing",
        "llm_role": null,
        "matched_chosen_role": false,
        "outcome_line": "Existing dimension (library) \u00b7 Role\u2194dimension skipped (dimension not under chosen role)",
        "role_dimension_saved": false,
        "roles_from_db": [],
        "skill_dimension_saved": true,
        "skill_id": 517,
        "skill_tag": "in_db",
        "skipped_reason": null
      },
      {
        "chosen_role_id": 1,
        "dimension": {
          "difficulty_hint": "well_known",
          "display_name": "Sitecore Troubleshooting and Maintenance",
          "id": 447,
          "rationale": "Diagnosing defects, regressions, and maintainability issues across Sitecore code, configuration, and content behavior. This is a coherent cluster because the role is expected to stabilize the site experience over time.",
          "slug": "sitecore-troubleshooting-and-maintenance",
          "source": "db"
        },
        "dimension_id": 447,
        "input_skill": "Debugging",
        "llm_role": null,
        "matched_chosen_role": false,
        "outcome_line": "Existing dimension (library) \u00b7 Role\u2194dimension skipped (dimension not under chosen role)",
        "role_dimension_saved": false,
        "roles_from_db": [
          {
            "display_name": "Sitecore Dev",
            "id": 233,
            "rationale": null,
            "role_archetype": "Engineering",
            "slug": "sitecore-dev",
            "source": "db"
          }
        ],
        "skill_dimension_saved": true,
        "skill_id": 4182,
        "skill_tag": "in_db",
        "skipped_reason": null
      }
    ],
    "new_skills_created": 0,
    "role_dimension_saved": 0,
    "skill_dimension_saved": 0,
    "skipped": 2
  },
  "planner_output": null,
  "run_id": "84e9a01e-215f-4eea-aaa8-71df2717cfd1"
}