← Back to history

Pipeline run

430fe59b-c76e-4510-9953-f365f5bcc694

Pipeline LLM cost (USD)
API 1: $0.0071 API 2: $0.0001 API 3: $0.0000 Total: $0.0072

Client output enrichment

v2 Skill cluster · Nature of work · AI index · Tech stack maturity · Evidence · KRA description
SPARSE JD sources · ai_index: jd · nature_of_work: jd · tech_stack_maturity: jd
Nature of work · Database Administration
Monitors database performance, fixes user-reported issues, and keeps backups, recovery, and security controls in place. Also reports usage/performance metrics and works with IT/project teams to improve database design and maintenance.
"“Monitoring system performance and identifying problems that arise.”"
Tech stack maturity
Mainstream Legacy
The role centers on traditional database administration (SQL Server/MySQL DBA) with primary skills in Hadoop, Oracle, and PostgreSQL, indicating established enterprise technologies rather than cloud-native or bleeding-edge stacks.
AI index (0 = no AI use, 5 = totally AI-dependent · v2.1)
0.00 / 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)
MS SQL Oracle Database Hadoop PostgreSQL
Skill cluster (3 dimension groups, role-scoped)
Relational Database Design
Oracle Database
Relational Database Usage
PostgreSQL
Cross-cutting / unaligned
MS SQL Hadoop
Show KRA description ↓
• Monitoring system performance and identifying problems that arise. • Responding in a timely manner to user-reported errors. • Protecting the database against threats or unauthorized access. • Ensuring that the database is adequately backed up and able to be recovered in the event of memory loss. • Reporting on metrics regarding usage and performance. • Suggesting changes and improvements for database maintenance or protection. • Regularly liaising with IT project managers and database programmers. • Designing databases with both front-end and back-end users in mind. • A bachelor's degree in computer science or a related field. • Advanced certification as an MCDBA or MCSD for .NET is advantageous. • A minimum of 3 years' experience as a database administrator. • Proficiency in data manipulation languages, including MS SQL, Oracle Database, Hadoop, or PostgreSQL. • Analytical mindset and good problem-solving skills. • Excellent verbal and written communication skills. • Highly organized and responsible. • Capable of working under pressure. • Up-to-date with trends and developments in database administration.

Signals

Skill node-backend-developer
0.50
Alias
KRA full-stack-engineer
0.52

Post-classification

Centroidupdated · n=1
Alias collision log
New-role queue
New skills captured1
New KRA capturedyes

Captured for admin review

MS SQL primary SQL Server / MySQL DBA pending
R&R fragment (sim 0.00) SQL Server / MySQL DBA pending

• Monitoring system performance and identifying problems that arise. • Responding in a timely manner to user-reported errors. • Protecting the database against threats or unauthorized access. • Ensuri…

Status: completed Created: 2026-05-27T13:58:21.847340Z Updated: 2026-05-27T13:59:22.305680Z API 3 duration: 15015 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

SQL Server / MySQL DBA

domain · Database Specialists CASE DOMAIN

slug: sql-server-mysql-dba · id: 198 · source: db

Domain=Database Specialists; The JD describes a general database administrator focused on monitoring, backup/recovery, security, performance, and SQL database platforms, which best matches SQL Server / MySQL DBA among the candidates.

Matched skills

MS SQLOracle DatabaseHadoopPostgreSQLdatabase administrationdatabase maintenancedatabase protectiondata manipulation languages

Matched dimensions

Database Performance MonitoringBackup and Recovery ManagementDatabase Security and Access ControlDatabase Maintenance and OptimizationDatabase Design and CollaborationIncident Response and Support

Matched KRAs

Monitoring system performance and identifying problemsResponding in a timely manner to user-reported errorsProtecting the database against threats or unauthorized accessEnsuring that the database is adequately backed upReporting on metrics regarding usage and performanceSuggesting changes and improvements for database maintenanceRegularly liaising with IT project managersDesigning databases with both front-end and back-end users in mind

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
0
Skipped

Job description

Job DescriptionDatabase Administrator
We are seeking to hire a technically skilled database administrator that is capable of holding positions of great responsibility. In this role, you'll be the first respondent to database problems that arise and carry out periodic maintenance and troubleshooting.
To ensure success as a database administrator, you should be an excellent problem-solver and communicator that is fluent in most data manipulation languages. Ultimately, a top-notch database administrator should have extensive knowledge of the databases under their administration and display sound technical skills and administrative aptitude.


Database Administrator Responsibilities:
• Monitoring system performance and identifying problems that arise.
• Responding in a timely manner to user-reported errors.
• Protecting the database against threats or unauthorized access.
• Ensuring that the database is adequately backed up and able to be recovered in the event of memory loss.
• Reporting on metrics regarding usage and performance.
• Suggesting changes and improvements for database maintenance or protection.
• Regularly liaising with IT project managers and database programmers.
• Designing databases with both front-end and back-end users in mind.


Database Administrator Requirements:
• A bachelor's degree in computer science or a related field.
• Advanced certification as an MCDBA or MCSD for .NET is advantageous.
• A minimum of 3 years' experience as a database administrator.
• Proficiency in data manipulation languages, including MS SQL, Oracle Database, Hadoop, or PostgreSQL.
• Analytical mindset and good problem-solving skills.
• Excellent verbal and written communication skills.
• Highly organized and responsible.
• Capable of working under pressure.
• Up-to-date with trends and developments in database administration. 
CategoryDatabase Administrator (IT & Networking)
ExpertiseSQL - 3 Years, MySQL ,Database Administrator - 3 Years

Skills from this JD

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

MS SQL 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
Databases
Sub-category
general
Skill nature
TOOL
Volatility
MEDIUM
Typical lifespan
MULTI_YEAR
Version strategy
UNVERSIONED
Oracle Database Primary Library skill API 3: existing canonical (in_db) Existing skill (matched library)
Canonical: Oracle Database id=1566 · oracle-database

Aliases — catalog

  • Oracle Database (CANONICAL) primary

Context tags (catalog)

Backup and Recovery Data Guard Data Warehousing Indexing Oracle APEX Oracle Cloud Oracle Enterprise Manager Oracle Exadata Oracle Forms Oracle Fusion Middleware Oracle RAC Oracle SQL Oracle SQL*Plus PL/SQL Partitioning Performance Tuning RMAN SQL Developer

Stored enrichment (catalog DB)

Category
Datastore
Sub-category
Relational Database
Vendor
Oracle Corporation
License
proprietary
Year introduced
1979
Confidence
0.98
Version strategy
NOT_APPLICABLE

Maturity reasoning: Oracle Database appears in many enterprise job postings and remains a standard RDBMS in large regulated environments; Oracle continues active vendor support and releases, indicating broad market demand.

Skill profile (library / DB)

Skill nature
TOOL
Volatility
STABLE
Typical lifespan
EVERGREEN
Category id
3
Sub-category id
29
Extractable
True
Also category
False

Dimensions (API 2 worklist)

  • React Frontend Development Catalog dimension db id 96

    Library dimension (catalog)

  • 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
React Frontend Development
d_init_01
Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role)
Relational Database Design
relational-database-design
Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role)
Hadoop Primary Library skill API 3: existing canonical (in_db) Existing skill (matched library)
Canonical: Hadoop id=1351 · hadoop

Aliases — catalog

  • Hadoop (CANONICAL)

Context tags (catalog)

Big Data Data Lake Distributed Computing ELT ETL Flume HDFS Hive Kafka MapReduce NoSQL Oozie Pig Spark Sqoop YARN

Stored enrichment (catalog DB)

Category
Framework
Sub-category
Data Processing Framework
Vendor
Apache Software Foundation
License
apache_2
Year introduced
2006
Confidence
0.90
Version strategy
NOT_APPLICABLE

Maturity reasoning: Job postings still mention Hadoop for legacy big-data stacks, but JD volume has fallen as Spark and cloud warehouses replaced MapReduce-era clusters.

Skill profile (library / DB)

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

Dimensions (API 2 worklist)

  • ETL and ELT Tooling Catalog dimension db id 24

    Library dimension (catalog)

    Roles linked in library: Data Engineer

API 3 link attempts (this skill)

Dimension Skill↔dim Role↔dim Outcome
ETL and ELT Tooling
etl-and-elt-tooling
Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role)
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, 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 skipped (dimension not under chosen role)
Relational Database Usage
relational-database-usage
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
Oracle Database in_db
React Frontend Development
d_init_01
Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role)
Oracle Database in_db
Relational Database Design
relational-database-design
Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role)
Hadoop in_db
ETL and ELT Tooling
etl-and-elt-tooling
Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role)
PostgreSQL in_db
Relational Data Modeling
relational-data-modeling
Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role)
PostgreSQL in_db
Relational Database Design
relational-database-design
Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role)
PostgreSQL in_db
Relational Database Usage
relational-database-usage
Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role)

Library artifacts (this run)

Kind Detail DB id
canonical_skill_proposed MS SQL | type=Databases subtype=general nature=TOOL lifespan=MULTI_YEAR
nano JD Parser — gpt-4.1-nano click to toggle
RoleDatabase Administrator
ExperienceA minimum of 3 years' experience as a database administrator.
DomainIT Services & Consulting
JD type pass

Certifications

MCDBA MCSD for .NET
Show raw JSON
{
  "JD_type": "pass",
  "about_company": null,
  "certifications": [
    "MCDBA",
    "MCSD for .NET"
  ],
  "company_name": null,
  "ctc": null,
  "domain": {
    "primary": {
      "aliases": [],
      "domain": "IT Services \u0026 Consulting"
    },
    "secondary": null
  },
  "education": [
    {
      "level": "Bachelor\u0027s",
      "qualification": "BTECH/BE/BSC - Computer Science (or related)",
      "raw": "A bachelor\u0027s degree in computer science or a related field.",
      "requirement": "required"
    }
  ],
  "experience": {
    "max": null,
    "min": 3,
    "raw": "A minimum of 3 years\u0027 experience as a database administrator."
  },
  "job_locations": [],
  "role": "Database Administrator",
  "role_aliases": [
    "DBA",
    "Database Admin",
    "Database Engineer"
  ],
  "role_archetype": "Engineering",
  "roles_and_responsibilities": [
    {
      "bullet_count": 8,
      "heading": "Database Administrator Responsibilities",
      "heading_was_present": true,
      "source_marker": {
        "first_5_words": "\u2022 Monitoring system performance and",
        "last_5_words": "front-end and back-end users in mind."
      },
      "text": "\u2022 Monitoring system performance and identifying problems that arise.\n\u2022 Responding in a timely manner to user-reported errors.\n\u2022 Protecting the database against threats or unauthorized access.\n\u2022 Ensuring that the database is adequately backed up and able to be recovered in the event of memory loss.\n\u2022 Reporting on metrics regarding usage and performance.\n\u2022 Suggesting changes and improvements for database maintenance or protection.\n\u2022 Regularly liaising with IT project managers and database programmers.\n\u2022 Designing databases with both front-end and back-end users in mind.",
      "word_count": 88
    },
    {
      "bullet_count": 9,
      "heading": "Database Administrator Requirements",
      "heading_was_present": true,
      "source_marker": {
        "first_5_words": "\u2022 A bachelor\u0027s degree in",
        "last_5_words": "in database administration."
      },
      "text": "\u2022 A bachelor\u0027s degree in computer science or a related field.\n\u2022 Advanced certification as an MCDBA or MCSD for .NET is advantageous.\n\u2022 A minimum of 3 years\u0027 experience as a database administrator.\n\u2022 Proficiency in data manipulation languages, including MS SQL, Oracle Database, Hadoop, or PostgreSQL.\n\u2022 Analytical mindset and good problem-solving skills.\n\u2022 Excellent verbal and written communication skills.\n\u2022 Highly organized and responsible.\n\u2022 Capable of working under pressure.\n\u2022 Up-to-date with trends and developments in database administration.",
      "word_count": 97
    }
  ],
  "urls": []
}
API 1 — extract-from-jd click to toggle
{
  "final_skills": [
    {
      "is_primary": true,
      "skill_name": "MS SQL"
    },
    {
      "is_primary": true,
      "skill_name": "Oracle Database"
    },
    {
      "is_primary": true,
      "skill_name": "Hadoop"
    },
    {
      "is_primary": true,
      "skill_name": "PostgreSQL"
    }
  ],
  "jd_role": {
    "display_name": "Database Administrator",
    "rationale": null,
    "role_aliases": [
      "DBA",
      "Database Admin",
      "Database Engineer"
    ],
    "role_archetype": "Engineering",
    "slug": ""
  },
  "nano_parsed": {
    "JD_type": "pass",
    "about_company": null,
    "certifications": [
      "MCDBA",
      "MCSD for .NET"
    ],
    "company_name": null,
    "ctc": null,
    "domain": {
      "primary": {
        "aliases": [],
        "domain": "IT Services \u0026 Consulting"
      },
      "secondary": null
    },
    "education": [
      {
        "level": "Bachelor\u0027s",
        "qualification": "BTECH/BE/BSC - Computer Science (or related)",
        "raw": "A bachelor\u0027s degree in computer science or a related field.",
        "requirement": "required"
      }
    ],
    "experience": {
      "max": null,
      "min": 3,
      "raw": "A minimum of 3 years\u0027 experience as a database administrator."
    },
    "job_locations": [],
    "role": "Database Administrator",
    "role_aliases": [
      "DBA",
      "Database Admin",
      "Database Engineer"
    ],
    "role_archetype": "Engineering",
    "roles_and_responsibilities": [
      {
        "bullet_count": 8,
        "heading": "Database Administrator Responsibilities",
        "heading_was_present": true,
        "source_marker": {
          "first_5_words": "\u2022 Monitoring system performance and",
          "last_5_words": "front-end and back-end users in mind."
        },
        "text": "\u2022 Monitoring system performance and identifying problems that arise.\n\u2022 Responding in a timely manner to user-reported errors.\n\u2022 Protecting the database against threats or unauthorized access.\n\u2022 Ensuring that the database is adequately backed up and able to be recovered in the event of memory loss.\n\u2022 Reporting on metrics regarding usage and performance.\n\u2022 Suggesting changes and improvements for database maintenance or protection.\n\u2022 Regularly liaising with IT project managers and database programmers.\n\u2022 Designing databases with both front-end and back-end users in mind.",
        "word_count": 88
      },
      {
        "bullet_count": 9,
        "heading": "Database Administrator Requirements",
        "heading_was_present": true,
        "source_marker": {
          "first_5_words": "\u2022 A bachelor\u0027s degree in",
          "last_5_words": "in database administration."
        },
        "text": "\u2022 A bachelor\u0027s degree in computer science or a related field.\n\u2022 Advanced certification as an MCDBA or MCSD for .NET is advantageous.\n\u2022 A minimum of 3 years\u0027 experience as a database administrator.\n\u2022 Proficiency in data manipulation languages, including MS SQL, Oracle Database, Hadoop, or PostgreSQL.\n\u2022 Analytical mindset and good problem-solving skills.\n\u2022 Excellent verbal and written communication skills.\n\u2022 Highly organized and responsible.\n\u2022 Capable of working under pressure.\n\u2022 Up-to-date with trends and developments in database administration.",
        "word_count": 97
      }
    ],
    "urls": []
  },
  "rejected": false,
  "rejection_reason": null,
  "run_id": "430fe59b-c76e-4510-9953-f365f5bcc694",
  "stage3_signals": {
    "alias_found": false,
    "alias_match_roles": [],
    "kra_match_roles": [
      {
        "display_name": "Fullstack Developer",
        "kra_matches": [
          {
            "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": "Designing databases with both front-end and back-end users in mind.",
            "similarity": 0.5967
          },
          {
            "kra_text": "Works closely with product managers and UX designers to translate requirements and wireframes into working software features through iterative development.",
            "sentence": "Regularly liaising with IT project managers and database programmers.",
            "similarity": 0.4847
          },
          {
            "kra_text": "Designs and queries relational databases like PostgreSQL and document stores like MongoDB, writing migrations, indexes, and optimized queries.",
            "sentence": "Up-to-date with trends and developments in database administration.",
            "similarity": 0.4779
          }
        ],
        "matched_count": null,
        "matched_skills": null,
        "role_id": 15,
        "score": 0.5198,
        "slug": "full-stack-engineer",
        "total_count": null
      },
      {
        "display_name": "PHP Backend Developer",
        "kra_matches": [
          {
            "kra_text": "performance and reliability tuning",
            "sentence": "Monitoring system performance and identifying problems that arise.",
            "similarity": 0.5232
          },
          {
            "kra_text": "validation and authorization safeguards",
            "sentence": "Protecting the database against threats or unauthorized access.",
            "similarity": 0.4986
          },
          {
            "kra_text": "performance and reliability tuning",
            "sentence": "Reporting on metrics regarding usage and performance.",
            "similarity": 0.4611
          }
        ],
        "matched_count": null,
        "matched_skills": null,
        "role_id": 86,
        "score": 0.4943,
        "slug": "php-backend-developer",
        "total_count": null
      },
      {
        "display_name": "Python Backend Developer",
        "kra_matches": [
          {
            "kra_text": "Design backend endpoints and request handling",
            "sentence": "Designing databases with both front-end and back-end users in mind.",
            "similarity": 0.557
          },
          {
            "kra_text": "Maintain data access and persistence",
            "sentence": "Ensuring that the database is adequately backed up and able to be recovered in the event of memory loss.",
            "similarity": 0.4704
          },
          {
            "kra_text": "Maintain data access and persistence",
            "sentence": "Suggesting changes and improvements for database maintenance or protection.",
            "similarity": 0.4439
          }
        ],
        "matched_count": null,
        "matched_skills": null,
        "role_id": 80,
        "score": 0.4904,
        "slug": "python-backend-developer",
        "total_count": null
      },
      {
        "display_name": "Kotlin Backend Developer",
        "kra_matches": [
          {
            "kra_text": "performance and reliability tuning",
            "sentence": "Monitoring system performance and identifying problems that arise.",
            "similarity": 0.5232
          },
          {
            "kra_text": "backend refactoring and maintenance",
            "sentence": "Suggesting changes and improvements for database maintenance or protection.",
            "similarity": 0.4751
          },
          {
            "kra_text": "performance and reliability tuning",
            "sentence": "Reporting on metrics regarding usage and performance.",
            "similarity": 0.4611
          }
        ],
        "matched_count": null,
        "matched_skills": null,
        "role_id": 84,
        "score": 0.4865,
        "slug": "kotlin-server-backend-developer",
        "total_count": null
      },
      {
        "display_name": "Java Backend Developer",
        "kra_matches": [
          {
            "kra_text": "backend performance tuning",
            "sentence": "Reporting on metrics regarding usage and performance.",
            "similarity": 0.507
          },
          {
            "kra_text": "backend performance tuning",
            "sentence": "Monitoring system performance and identifying problems that arise.",
            "similarity": 0.5049
          },
          {
            "kra_text": "persistence and data modeling",
            "sentence": "Designing databases with both front-end and back-end users in mind.",
            "similarity": 0.4416
          }
        ],
        "matched_count": null,
        "matched_skills": null,
        "role_id": 79,
        "score": 0.4845,
        "slug": "java-backend-developer",
        "total_count": null
      }
    ],
    "skill_match_roles": [
      {
        "display_name": "Node.js Backend Developer",
        "kra_matches": null,
        "matched_count": 2,
        "matched_skills": [
          "Oracle Database",
          "PostgreSQL"
        ],
        "role_id": 82,
        "score": 0.5,
        "slug": "node-backend-developer",
        "total_count": 4
      },
      {
        "display_name": ".NET Backend Developer",
        "kra_matches": null,
        "matched_count": 2,
        "matched_skills": [
          "Oracle Database",
          "PostgreSQL"
        ],
        "role_id": 83,
        "score": 0.5,
        "slug": "dotnet-backend-developer",
        "total_count": 4
      },
      {
        "display_name": "Python Backend Developer",
        "kra_matches": null,
        "matched_count": 2,
        "matched_skills": [
          "Oracle Database",
          "PostgreSQL"
        ],
        "role_id": 80,
        "score": 0.5,
        "slug": "python-backend-developer",
        "total_count": 4
      },
      {
        "display_name": "Backend Developer",
        "kra_matches": null,
        "matched_count": 2,
        "matched_skills": [
          "Oracle Database",
          "PostgreSQL"
        ],
        "role_id": 1,
        "score": 0.5,
        "slug": "backend-engineer",
        "total_count": 4
      },
      {
        "display_name": "Kotlin Backend Developer",
        "kra_matches": null,
        "matched_count": 2,
        "matched_skills": [
          "Oracle Database",
          "PostgreSQL"
        ],
        "role_id": 84,
        "score": 0.5,
        "slug": "kotlin-server-backend-developer",
        "total_count": 4
      }
    ]
  },
  "stage4_decision": {
    "alias_collision_detected": false,
    "case": "DOMAIN",
    "chosen_role": {
      "display_name": "SQL Server / MySQL DBA",
      "kra_matches": null,
      "matched_count": null,
      "matched_skills": null,
      "role_id": 198,
      "score": 0.98,
      "slug": "sql-server-mysql-dba",
      "total_count": null
    },
    "confidence": 0.98,
    "is_new_role": false,
    "llm2_fired": false,
    "llm2_reasoning": null,
    "matched_dimensions": [
      "Database Performance Monitoring",
      "Backup and Recovery Management",
      "Database Security and Access Control",
      "Database Maintenance and Optimization",
      "Database Design and Collaboration",
      "Incident Response and Support"
    ],
    "matched_kras": [
      "Monitoring system performance and identifying problems",
      "Responding in a timely manner to user-reported errors",
      "Protecting the database against threats or unauthorized access",
      "Ensuring that the database is adequately backed up",
      "Reporting on metrics regarding usage and performance",
      "Suggesting changes and improvements for database maintenance",
      "Regularly liaising with IT project managers",
      "Designing databases with both front-end and back-end users in mind"
    ],
    "matched_skills": [
      "MS SQL",
      "Oracle Database",
      "Hadoop",
      "PostgreSQL",
      "database administration",
      "database maintenance",
      "database protection",
      "data manipulation languages"
    ],
    "new_role_display_name": null,
    "new_role_slug": null,
    "queued": false,
    "reasoning": "Domain=Database Specialists; The JD describes a general database administrator focused on monitoring, backup/recovery, security, performance, and SQL database platforms, which best matches SQL Server / MySQL DBA among the candidates.",
    "sub_role": null
  },
  "stage5_updates": {
    "centroid_n_after": 1,
    "centroid_updated": true,
    "collision_log_id": null,
    "new_kra_attached": {
      "best_kra_similarity": 0.0,
      "queue_id": 310,
      "r_and_r_preview": "\u2022 Monitoring system performance and identifying problems that arise.\n\u2022 Responding in a timely manner to user-reported errors.\n\u2022 Protecting the database against threats or unauthorized access.\n\u2022 Ensuri",
      "role_display_name": "SQL Server / MySQL DBA",
      "role_slug": "sql-server-mysql-dba",
      "status": "pending"
    },
    "new_skills_attached": [
      {
        "is_primary": true,
        "queue_id": 6102,
        "role_display_name": "SQL Server / MySQL DBA",
        "role_slug": "sql-server-mysql-dba",
        "skill_name": "MS SQL",
        "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": 2512,
      "existing_alias_text": "Oracle Database",
      "input_term": "Oracle Database",
      "matched_canonical": {
        "category_id": 3,
        "display_name": "Oracle Database",
        "id": 1566,
        "is_also_category": false,
        "is_extractable": true,
        "skill_nature": "TOOL",
        "slug": "oracle-database",
        "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": 2010,
      "existing_alias_text": "Hadoop",
      "input_term": "Hadoop",
      "matched_canonical": {
        "category_id": 5,
        "display_name": "Hadoop",
        "id": 1351,
        "is_also_category": false,
        "is_extractable": true,
        "skill_nature": "FRAMEWORK",
        "slug": "hadoop",
        "sub_category_id": 91,
        "typical_lifespan": "EVERGREEN",
        "volatility": "STABLE"
      },
      "matched_via": "alias"
    },
    {
      "alias_persist_skipped_reason": "alias_text already exists for this canonical skill",
      "alias_persisted": false,
      "existing_alias_id": 121,
      "existing_alias_text": "PostgreSQL",
      "input_term": "PostgreSQL",
      "matched_canonical": {
        "category_id": 3,
        "display_name": "PostgreSQL",
        "id": 16,
        "is_also_category": false,
        "is_extractable": true,
        "skill_nature": "TOOL",
        "slug": "postgresql",
        "sub_category_id": 29,
        "typical_lifespan": "EVERGREEN",
        "volatility": "STABLE"
      },
      "matched_via": "alias"
    }
  ],
  "candidate_roles": [
    {
      "display_name": ".NET Backend Developer",
      "id": 83,
      "rationale": null,
      "role_archetype": "Engineering",
      "slug": "dotnet-backend-developer",
      "source": "db"
    },
    {
      "display_name": "Backend Developer",
      "id": 1,
      "rationale": null,
      "role_archetype": "A Backend Engineer designs, builds, and maintains the server-side logic and data handling that power applications and services. They focus on implementing reliable business functionality, integrating with other systems, and ensuring the backend is scalable, maintainable, and observable.",
      "slug": "backend-engineer",
      "source": "db"
    },
    {
      "display_name": "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": "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": "PHP Backend Developer",
      "id": 86,
      "rationale": null,
      "role_archetype": "Engineering",
      "slug": "php-backend-developer",
      "source": "db"
    },
    {
      "display_name": "Go Backend Developer",
      "id": 81,
      "rationale": null,
      "role_archetype": "Engineering",
      "slug": "go-backend-developer",
      "source": "db"
    }
  ],
  "chosen_role": {
    "display_name": "SQL Server / MySQL DBA",
    "id": 198,
    "rationale": "Domain=Database Specialists; The JD describes a general database administrator focused on monitoring, backup/recovery, security, performance, and SQL database platforms, which best matches SQL Server / MySQL DBA among the candidates.",
    "role_archetype": null,
    "slug": "sql-server-mysql-dba",
    "source": "db"
  },
  "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": "Oracle Database",
      "llm_role": null,
      "roles_from_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": "Oracle Database",
      "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": "ETL and ELT Tooling",
        "id": 24,
        "rationale": "Packaged tools for extracting, loading, and transforming data across systems. This dimension covers connector-based ingestion, transformation frameworks, and managed integration products.",
        "slug": "etl-and-elt-tooling",
        "source": "db"
      },
      "input_skill": "Hadoop",
      "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": "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": "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_final_skills": [
    "MS SQL",
    "Oracle Database",
    "Hadoop",
    "PostgreSQL"
  ],
  "input_llm_skills": [
    "MS SQL",
    "Oracle Database",
    "Hadoop",
    "PostgreSQL"
  ],
  "new_aliases_persisted": 0,
  "run_id": "430fe59b-c76e-4510-9953-f365f5bcc694",
  "skills_detail": [
    {
      "aliases_in_db": [],
      "canonical": null,
      "dimensions": [],
      "input_skill": "MS SQL",
      "matched_via": null,
      "new_alias_persisted": false,
      "new_alias_text": null,
      "new_skill_meta": {
        "derived": {
          "category": "Databases",
          "skill_nature": "TOOL",
          "sub_category": "general",
          "typical_lifespan": "MULTI_YEAR",
          "version_strategy": "UNVERSIONED",
          "volatility": "MEDIUM"
        },
        "enrichment": null,
        "keep_log": [],
        "locked_dimensions": [],
        "merge_log": [],
        "placed": null,
        "relationships": null,
        "skill_id": "ms-sql",
        "split_log": [],
        "typed": null,
        "warnings": []
      },
      "source_tag": "llm",
      "was_in_llm_skills": true
    },
    {
      "aliases_in_db": [
        {
          "alias_text": "Oracle Database",
          "alias_type": "CANONICAL",
          "id": 2512,
          "is_primary": true,
          "match_strategy": "CASE_INSENSITIVE"
        }
      ],
      "canonical": {
        "category_id": 3,
        "display_name": "Oracle Database",
        "id": 1566,
        "is_also_category": false,
        "is_extractable": true,
        "skill_nature": "TOOL",
        "slug": "oracle-database",
        "sub_category_id": 29,
        "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": "Oracle Database",
          "llm_role": null,
          "roles_from_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": "Oracle Database",
          "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": "Oracle Database",
      "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": "Hadoop",
          "alias_type": "CANONICAL",
          "id": 2010,
          "is_primary": false,
          "match_strategy": "CASE_INSENSITIVE"
        }
      ],
      "canonical": {
        "category_id": 5,
        "display_name": "Hadoop",
        "id": 1351,
        "is_also_category": false,
        "is_extractable": true,
        "skill_nature": "FRAMEWORK",
        "slug": "hadoop",
        "sub_category_id": 91,
        "typical_lifespan": "EVERGREEN",
        "volatility": "STABLE"
      },
      "dimensions": [
        {
          "dimension": {
            "difficulty_hint": "well_known",
            "display_name": "ETL and ELT Tooling",
            "id": 24,
            "rationale": "Packaged tools for extracting, loading, and transforming data across systems. This dimension covers connector-based ingestion, transformation frameworks, and managed integration products.",
            "slug": "etl-and-elt-tooling",
            "source": "db"
          },
          "input_skill": "Hadoop",
          "llm_role": null,
          "roles_from_db": [
            {
              "display_name": "Data Engineer",
              "id": 2,
              "rationale": null,
              "role_archetype": null,
              "slug": "data-engineer",
              "source": "db"
            }
          ]
        }
      ],
      "input_skill": "Hadoop",
      "matched_via": "alias",
      "new_alias_persisted": false,
      "new_alias_text": null,
      "new_skill_meta": null,
      "source_tag": "db",
      "was_in_llm_skills": true
    },
    {
      "aliases_in_db": [
        {
          "alias_text": "PostgreSQL",
          "alias_type": "CANONICAL",
          "id": 121,
          "is_primary": true,
          "match_strategy": "CASE_INSENSITIVE"
        },
        {
          "alias_text": "PG 13",
          "alias_type": "VERSION",
          "id": 122,
          "is_primary": false,
          "match_strategy": "CASE_INSENSITIVE"
        },
        {
          "alias_text": "PG 14",
          "alias_type": "VERSION",
          "id": 123,
          "is_primary": false,
          "match_strategy": "CASE_INSENSITIVE"
        },
        {
          "alias_text": "PG 15",
          "alias_type": "VERSION",
          "id": 124,
          "is_primary": false,
          "match_strategy": "CASE_INSENSITIVE"
        },
        {
          "alias_text": "PG 16",
          "alias_type": "VERSION",
          "id": 125,
          "is_primary": false,
          "match_strategy": "CASE_INSENSITIVE"
        },
        {
          "alias_text": "PostgreSQL 13",
          "alias_type": "VERSION",
          "id": 130,
          "is_primary": false,
          "match_strategy": "CASE_INSENSITIVE"
        },
        {
          "alias_text": "PostgreSQL 14",
          "alias_type": "VERSION",
          "id": 131,
          "is_primary": false,
          "match_strategy": "CASE_INSENSITIVE"
        },
        {
          "alias_text": "PostgreSQL 15",
          "alias_type": "VERSION",
          "id": 132,
          "is_primary": false,
          "match_strategy": "CASE_INSENSITIVE"
        },
        {
          "alias_text": "PostgreSQL 16",
          "alias_type": "VERSION",
          "id": 133,
          "is_primary": false,
          "match_strategy": "CASE_INSENSITIVE"
        },
        {
          "alias_text": "Postgres 13",
          "alias_type": "VERSION",
          "id": 126,
          "is_primary": false,
          "match_strategy": "CASE_INSENSITIVE"
        },
        {
          "alias_text": "Postgres 14",
          "alias_type": "VERSION",
          "id": 127,
          "is_primary": false,
          "match_strategy": "CASE_INSENSITIVE"
        },
        {
          "alias_text": "Postgres 15",
          "alias_type": "VERSION",
          "id": 128,
          "is_primary": false,
          "match_strategy": "CASE_INSENSITIVE"
        },
        {
          "alias_text": "Postgres 16",
          "alias_type": "VERSION",
          "id": 129,
          "is_primary": false,
          "match_strategy": "CASE_INSENSITIVE"
        },
        {
          "alias_text": "pg10",
          "alias_type": "VERSION",
          "id": 4714,
          "is_primary": false,
          "match_strategy": "CASE_INSENSITIVE"
        },
        {
          "alias_text": "pg11",
          "alias_type": "VERSION",
          "id": 4715,
          "is_primary": false,
          "match_strategy": "CASE_INSENSITIVE"
        },
        {
          "alias_text": "pg12",
          "alias_type": "VERSION",
          "id": 4716,
          "is_primary": false,
          "match_strategy": "CASE_INSENSITIVE"
        },
        {
          "alias_text": "pg13",
          "alias_type": "VERSION",
          "id": 4717,
          "is_primary": false,
          "match_strategy": "CASE_INSENSITIVE"
        },
        {
          "alias_text": "pg14",
          "alias_type": "VERSION",
          "id": 4718,
          "is_primary": false,
          "match_strategy": "CASE_INSENSITIVE"
        },
        {
          "alias_text": "pg15",
          "alias_type": "VERSION",
          "id": 4719,
          "is_primary": false,
          "match_strategy": "CASE_INSENSITIVE"
        },
        {
          "alias_text": "pg16",
          "alias_type": "VERSION",
          "id": 4720,
          "is_primary": false,
          "match_strategy": "CASE_INSENSITIVE"
        },
        {
          "alias_text": "postgres",
          "alias_type": "VERSION",
          "id": 4721,
          "is_primary": false,
          "match_strategy": "CASE_INSENSITIVE"
        },
        {
          "alias_text": "postgresql 10",
          "alias_type": "VERSION",
          "id": 4729,
          "is_primary": false,
          "match_strategy": "CASE_INSENSITIVE"
        },
        {
          "alias_text": "postgresql 11",
          "alias_type": "VERSION",
          "id": 4730,
          "is_primary": false,
          "match_strategy": "CASE_INSENSITIVE"
        },
        {
          "alias_text": "postgresql 12",
          "alias_type": "VERSION",
          "id": 4731,
          "is_primary": false,
          "match_strategy": "CASE_INSENSITIVE"
        },
        {
          "alias_text": "postgresql 13",
          "alias_type": "VERSION",
          "id": 4732,
          "is_primary": false,
          "match_strategy": "CASE_INSENSITIVE"
        },
        {
          "alias_text": "postgresql 14",
          "alias_type": "VERSION",
          "id": 4733,
          "is_primary": false,
          "match_strategy": "CASE_INSENSITIVE"
        },
        {
          "alias_text": "postgresql 15",
          "alias_type": "VERSION",
          "id": 4734,
          "is_primary": false,
          "match_strategy": "CASE_INSENSITIVE"
        },
        {
          "alias_text": "postgresql 16",
          "alias_type": "VERSION",
          "id": 4735,
          "is_primary": false,
          "match_strategy": "CASE_INSENSITIVE"
        },
        {
          "alias_text": "postgresql-16",
          "alias_type": "VERSION",
          "id": 4736,
          "is_primary": false,
          "match_strategy": "CASE_INSENSITIVE"
        },
        {
          "alias_text": "postgresql10",
          "alias_type": "VERSION",
          "id": 4722,
          "is_primary": false,
          "match_strategy": "CASE_INSENSITIVE"
        },
        {
          "alias_text": "postgresql11",
          "alias_type": "VERSION",
          "id": 4723,
          "is_primary": false,
          "match_strategy": "CASE_INSENSITIVE"
        },
        {
          "alias_text": "postgresql12",
          "alias_type": "VERSION",
          "id": 4724,
          "is_primary": false,
          "match_strategy": "CASE_INSENSITIVE"
        },
        {
          "alias_text": "postgresql13",
          "alias_type": "VERSION",
          "id": 4725,
          "is_primary": false,
          "match_strategy": "CASE_INSENSITIVE"
        },
        {
          "alias_text": "postgresql14",
          "alias_type": "VERSION",
          "id": 4726,
          "is_primary": false,
          "match_strategy": "CASE_INSENSITIVE"
        },
        {
          "alias_text": "postgresql15",
          "alias_type": "VERSION",
          "id": 4727,
          "is_primary": false,
          "match_strategy": "CASE_INSENSITIVE"
        },
        {
          "alias_text": "postgresql16",
          "alias_type": "VERSION",
          "id": 4728,
          "is_primary": false,
          "match_strategy": "CASE_INSENSITIVE"
        }
      ],
      "canonical": {
        "category_id": 3,
        "display_name": "PostgreSQL",
        "id": 16,
        "is_also_category": false,
        "is_extractable": true,
        "skill_nature": "TOOL",
        "slug": "postgresql",
        "sub_category_id": 29,
        "typical_lifespan": "EVERGREEN",
        "volatility": "STABLE"
      },
      "dimensions": [
        {
          "dimension": {
            "difficulty_hint": "well_known",
            "display_name": "Relational Data Modeling",
            "id": 216,
            "rationale": "Modeling and tuning relational persistence for backend features. PHP backend developers need this to shape schemas, indexes, transactions, and query-aware data structures that support application behavior.",
            "slug": "relational-data-modeling",
            "source": "db"
          },
          "input_skill": "PostgreSQL",
          "llm_role": null,
          "roles_from_db": [
            {
              "display_name": "Fullstack Developer",
              "id": 15,
              "rationale": null,
              "role_archetype": null,
              "slug": "full-stack-engineer",
              "source": "db"
            },
            {
              "display_name": "PHP Backend Developer",
              "id": 86,
              "rationale": null,
              "role_archetype": "Engineering",
              "slug": "php-backend-developer",
              "source": "db"
            }
          ]
        },
        {
          "dimension": {
            "difficulty_hint": "well_known",
            "display_name": "Relational Database Design",
            "id": 4,
            "rationale": "Modeling and operating relational persistence for backend services. Includes schema design, normalization, indexing, transactions, and query tuning for operational data stores.",
            "slug": "relational-database-design",
            "source": "db"
          },
          "input_skill": "PostgreSQL",
          "llm_role": null,
          "roles_from_db": [
            {
              "display_name": ".NET Backend Developer",
              "id": 83,
              "rationale": null,
              "role_archetype": "Engineering",
              "slug": "dotnet-backend-developer",
              "source": "db"
            },
            {
              "display_name": "Backend Developer",
              "id": 1,
              "rationale": null,
              "role_archetype": "A Backend Engineer designs, builds, and maintains the server-side logic and data handling that power applications and services. They focus on implementing reliable business functionality, integrating with other systems, and ensuring the backend is scalable, maintainable, and observable.",
              "slug": "backend-engineer",
              "source": "db"
            },
            {
              "display_name": "Kotlin Backend Developer",
              "id": 84,
              "rationale": null,
              "role_archetype": "Engineering",
              "slug": "kotlin-server-backend-developer",
              "source": "db"
            },
            {
              "display_name": "Node.js Backend Developer",
              "id": 82,
              "rationale": null,
              "role_archetype": "Engineering",
              "slug": "node-backend-developer",
              "source": "db"
            },
            {
              "display_name": "Python Backend Developer",
              "id": 80,
              "rationale": null,
              "role_archetype": "Engineering",
              "slug": "python-backend-developer",
              "source": "db"
            },
            {
              "display_name": "Ruby Backend Developer",
              "id": 85,
              "rationale": null,
              "role_archetype": "Engineering",
              "slug": "ruby-backend-developer",
              "source": "db"
            },
            {
              "display_name": "Scala Backend Developer",
              "id": 87,
              "rationale": null,
              "role_archetype": "Engineering",
              "slug": "scala-backend-developer",
              "source": "db"
            }
          ]
        },
        {
          "dimension": {
            "difficulty_hint": "well_known",
            "display_name": "Relational Database Usage",
            "id": 371,
            "rationale": "Working effectively with operational relational databases from Go backend services. This includes schema-aware querying, indexing awareness, transactions, and understanding how service code interacts with PostgreSQL or similar systems.",
            "slug": "relational-database-usage",
            "source": "db"
          },
          "input_skill": "PostgreSQL",
          "llm_role": null,
          "roles_from_db": [
            {
              "display_name": "Go Backend Developer",
              "id": 81,
              "rationale": null,
              "role_archetype": "Engineering",
              "slug": "go-backend-developer",
              "source": "db"
            }
          ]
        }
      ],
      "input_skill": "PostgreSQL",
      "matched_via": "alias",
      "new_alias_persisted": false,
      "new_alias_text": null,
      "new_skill_meta": null,
      "source_tag": "db",
      "was_in_llm_skills": true
    }
  ],
  "unmatched_skills": [
    "MS SQL"
  ]
}
API 3 — final-role-output
{
  "chosen_role": {
    "display_name": "SQL Server / MySQL DBA",
    "id": 198,
    "rationale": "Domain=Database Specialists; The JD describes a general database administrator focused on monitoring, backup/recovery, security, performance, and SQL database platforms, which best matches SQL Server / MySQL DBA among the candidates.",
    "role_archetype": null,
    "slug": "sql-server-mysql-dba",
    "source": "db"
  },
  "chosen_role_resolution": "in_db",
  "final_input_skills": [
    {
      "skill": "MS SQL",
      "tag": "new"
    },
    {
      "skill": "Oracle Database",
      "tag": "in_db"
    },
    {
      "skill": "Hadoop",
      "tag": "in_db"
    },
    {
      "skill": "PostgreSQL",
      "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": 198,
        "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": "Oracle Database",
        "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": 1566,
        "skill_tag": "in_db",
        "skipped_reason": null
      },
      {
        "chosen_role_id": 198,
        "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": "Oracle Database",
        "llm_role": null,
        "matched_chosen_role": false,
        "outcome_line": "Existing dimension (library) \u00b7 Role\u2194dimension skipped (dimension not under chosen role)",
        "role_dimension_saved": false,
        "roles_from_db": [
          {
            "display_name": ".NET Backend Developer",
            "id": 83,
            "rationale": null,
            "role_archetype": "Engineering",
            "slug": "dotnet-backend-developer",
            "source": "db"
          },
          {
            "display_name": "Backend Developer",
            "id": 1,
            "rationale": null,
            "role_archetype": "A Backend Engineer designs, builds, and maintains the server-side logic and data handling that power applications and services. They focus on implementing reliable business functionality, integrating with other systems, and ensuring the backend is scalable, maintainable, and observable.",
            "slug": "backend-engineer",
            "source": "db"
          },
          {
            "display_name": "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": 1566,
        "skill_tag": "in_db",
        "skipped_reason": null
      },
      {
        "chosen_role_id": 198,
        "dimension": {
          "difficulty_hint": "well_known",
          "display_name": "ETL and ELT Tooling",
          "id": 24,
          "rationale": "Packaged tools for extracting, loading, and transforming data across systems. This dimension covers connector-based ingestion, transformation frameworks, and managed integration products.",
          "slug": "etl-and-elt-tooling",
          "source": "db"
        },
        "dimension_id": 24,
        "input_skill": "Hadoop",
        "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": 1351,
        "skill_tag": "in_db",
        "skipped_reason": null
      },
      {
        "chosen_role_id": 198,
        "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": "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": 198,
        "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": false,
        "outcome_line": "Existing dimension (library) \u00b7 Role\u2194dimension skipped (dimension not under chosen role)",
        "role_dimension_saved": false,
        "roles_from_db": [
          {
            "display_name": ".NET Backend Developer",
            "id": 83,
            "rationale": null,
            "role_archetype": "Engineering",
            "slug": "dotnet-backend-developer",
            "source": "db"
          },
          {
            "display_name": "Backend Developer",
            "id": 1,
            "rationale": null,
            "role_archetype": "A Backend Engineer designs, builds, and maintains the server-side logic and data handling that power applications and services. They focus on implementing reliable business functionality, integrating with other systems, and ensuring the backend is scalable, maintainable, and observable.",
            "slug": "backend-engineer",
            "source": "db"
          },
          {
            "display_name": "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": 198,
        "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
      }
    ],
    "new_skills_created": 0,
    "role_dimension_saved": 0,
    "skill_dimension_saved": 0,
    "skipped": 0
  },
  "planner_output": null,
  "run_id": "430fe59b-c76e-4510-9953-f365f5bcc694"
}

LLM Calls

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

Loading…