← Back to history

Pipeline run

0b709bbb-1e9c-468e-b605-2af9714674f1

Pipeline LLM cost (USD)
API 1: $0.0099 API 2: $0.0001 API 3: $0.0000 Total: $0.0101

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/re-engineers data and application processes, writes technical specs, and builds database structures, code, tests, and batch jobs, then supports releases, L2 issues, and ad-hoc investment-team data requests.
"Designing database architecture, services and user interfaces"
Tech stack maturity
Mainstream Modern
Backend development focused on integration and unit testing typically aligns with widely adopted, current engineering practices rather than legacy 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): NLP, AI
Evidence — skills matched in JD (5)
Database Architecture Unit Testing Integration Testing Data Modeling Batch Processing
Skill cluster (2 dimension groups, role-scoped)
Testing and Quality Assurance
Integration Testing
Cross-cutting / unaligned
Database Architecture Unit Testing Data Modeling Batch Processing
Show KRA description ↓
• Designing / re-engineering processes • Writing technical specifications • Designing database architecture, services and user interfaces • Developing code, development, unit and integration testing • Post-launch maintenance; enhancement prioritization in conjunction with the business; on-going release management • Analyzing and implementing new data models • Providing Level 2 application support • Providing support for ad-hoc data and research requests from the investment team • Providing support for overnight batch jobs

Signals

Skill backend-engineer
0.20
Alias
KRA go-backend-developer
0.57

Post-classification

Centroidupdated · n=1101
Alias collision log
New-role queue
New skills captured3
New KRA capturedyes

Captured for admin review

Database Architecture primary Backend Developer pending
Data Modeling primary Backend Developer pending
Batch Processing primary Backend Developer pending
R&R fragment (sim 0.00) Backend Developer pending

• Designing / re-engineering processes • Writing technical specifications • Designing database architecture, services and user interfaces • Developing code, development, unit and integration testing •…

Status: completed Created: 2026-05-27T15:46:32.685490Z Updated: 2026-06-12T15:58:54.170697Z API 3 duration: 5514 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 centers on designing services, writing technical specs, developing and testing code, data models, release management, and application support, which best matches a backend/application engineer role.

Matched skills

technical specificationsdatabase architectureservicesuser interfacesdevelopmentunit and integration testingrelease managementdata modelsLevel 2 application supportovernight batch jobs

Matched dimensions

Process re-engineeringApplication and service designDatabase architecture and data modelingSoftware development and testingProduction support and maintenanceBatch job support

Matched KRAs

Designing / re-engineering processesWriting technical specificationsDesigning database architecture, services and user interfacesDeveloping code, development, unit and integration testingPost-launch maintenance; enhancement prioritizationAnalyzing and implementing new data modelsProviding Level 2 application supportProviding support for ad-hoc data and research requestsProviding support for overnight batch jobs

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

HIR ING

Job Skills

Dotnet Core 2.0, Application Framework, Microsoft

Description

Primary Skill (C#, Net,Angular, SQL)

• 10 + years of industry experience in coding, designing and building software.
• Knowledge and understanding of Object-Oriented Programming
• Must be proficient in C# .NET Framework
• Core understanding of relational databases
• Basic knowledge of PowerShell
• Experience of building UI using Angular 8+/TypeScript
• Fundamental programming concepts like SOLID principles, dependency injection, etc. 
• Should have a good understanding of Design Patterns, Git, Continuous Integration, Continuous Deployment tooling
• Practical or theoretical experience with NLP and AI
• BS / MS in Computer Science, Math, Engineering and/or related experience



Responsibilities

• Designing / re-engineering processes
• Writing technical specifications
• Designing database architecture, services and user interfaces
• Developing code, development, unit and integration testing
• Post-launch maintenance; enhancement prioritization in conjunction with the business; on-going release management
• Analyzing and implementing new data models
• Providing Level 2 application support
• Providing support for ad-hoc data and research requests from the investment team
• Providing support for overnight batch jobs

Skills from this JD

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

Database Architecture 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
Concepts
Sub-category
general
Skill nature
CONCEPT
Volatility
STABLE
Typical lifespan
EVERGREEN
Version strategy
UNVERSIONED
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)
Integration Testing Primary Library skill API 3: existing canonical (in_db) Existing skill (matched library)
Canonical: Integration testing id=56 · integration-testing

Aliases — catalog

  • Integration testing (CANONICAL) primary
  • integration testing (CANONICAL)

Context tags (catalog)

API testing CI/CD Cucumber JUnit Selenium behavior-driven development continuous integration contract testing end-to-end end-to-end testing fixtures mocking pytest quality assurance regression testing smoke testing stubs system testing test automation test cases test coverage test data test frameworks test harness test strategy test suite test-driven development

Stored enrichment (catalog DB)

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

Maturity reasoning: Integration testing is a standard QA skill in job descriptions across backend, frontend, and DevOps roles; it’s commonly paired with CI/CD and tools like Jest, Cypress, and Testcontainers.

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)

  • Testing and Defect Resolution Catalog dimension db id 262

    Library dimension (catalog)

    Roles linked in library: Pega Developer

  • Testing and Quality Assurance Catalog dimension db id 12

    Library dimension (catalog)

    Roles linked in library: .NET Backend Developer, Backend Developer, Node.js Backend Developer, PHP Backend Developer, Python Backend Developer, Scala Backend Developer

API 3 link attempts (this skill)

Dimension Skill↔dim Role↔dim Outcome
Testing and Defect Resolution
testing-and-defect-resolution
Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role)
Testing and Quality Assurance
testing-and-quality-assurance
Existing dimension (library) · Role↔dimension saved
Data Modeling Primary Library skill API 3: existing canonical (in_db) Existing skill (matched library)
Canonical: domain modeling id=2379 · domain-modeling

Aliases — catalog

  • domain modeling (CANONICAL) primary
  • Domain Modeling (CANONICAL)

Context tags (catalog)

CQRS DDD ERD UML aggregate bounded context business logic context map context mapping data modeling domain events domain-driven design entities entity event sourcing event storming microservices repositories repository pattern service layer services value object value objects

Stored enrichment (catalog DB)

Category
Methodology
Sub-category
Domain Modeling
Confidence
0.90
Version strategy
NOT_APPLICABLE

Maturity reasoning: Common in software JDs under DDD/business analysis; many roles ask for domain modeling or domain-driven design, and it remains a standard design skill rather than a niche tool.

Skill profile (library / DB)

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

Dimensions (API 2 worklist)

  • Application Architecture Patterns Catalog dimension db id 293

    Library dimension (catalog)

    Roles linked in library: .NET Backend Developer, Python Backend Developer

  • Service Architecture and Design Patterns Catalog dimension db id 18

    Library dimension (catalog)

    Roles linked in library: Backend Developer, Java Backend Developer, Kotlin Backend Developer, Node.js Backend Developer, PHP Backend Developer, Ruby Backend Developer, Scala Backend Developer

API 3 link attempts (this skill)

Dimension Skill↔dim Role↔dim Outcome
Application Architecture Patterns
application-architecture-patterns
Skipped — no persistable v3 meta for new skill
skill_not_in_db_v3_proposed
Service Architecture and Design Patterns
service-architecture-and-design-patterns
Skipped — no persistable v3 meta for new skill
skill_not_in_db_v3_proposed
Batch Processing 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
Concepts
Sub-category
general
Skill nature
CONCEPT
Volatility
MEDIUM
Typical lifespan
MULTI_YEAR
Version strategy
UNVERSIONED

All API 3 persistence rows

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

Skill Tag Dimension Skill↔dim Role↔dim Outcome Notes
Unit Testing in_db
React Frontend Development
d_init_01
Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role)
Integration Testing in_db
Testing and Defect Resolution
testing-and-defect-resolution
Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role)
Integration Testing in_db
Testing and Quality Assurance
testing-and-quality-assurance
Existing dimension (library) · Role↔dimension saved
Data Modeling new
Application Architecture Patterns
application-architecture-patterns
Skipped — no persistable v3 meta for new skill skill_not_in_db_v3_proposed
Data Modeling new
Service Architecture and Design Patterns
service-architecture-and-design-patterns
Skipped — no persistable v3 meta for new skill skill_not_in_db_v3_proposed

Library artifacts (this run)

Kind Detail DB id
canonical_skill_proposed Database Architecture | type=Concepts subtype=general nature=CONCEPT lifespan=EVERGREEN
canonical_skill_proposed Batch Processing | type=Concepts subtype=general nature=CONCEPT lifespan=MULTI_YEAR
dimension_skill_link_proposed Data Modeling ↔ Application Architecture Patterns
dimension_skill_link_proposed Data Modeling ↔ Service Architecture and Design Patterns
role_dimension_link_proposed Backend Developer ↔ Service Architecture and Design Patterns
nano JD Parser — gpt-4.1-nano click to toggle
Experience10 + years of industry experience in coding, designing and building software.
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": [
    {
      "level": "Bachelor\u0027s",
      "qualification": "BTECH/BE - Computer Science / Math / Engineering (or related)",
      "raw": "BS / MS in Computer Science, Math, Engineering and/or related experience",
      "requirement": "required"
    }
  ],
  "experience": {
    "max": null,
    "min": 10,
    "raw": "10 + years of industry experience in coding, designing and building software."
  },
  "job_locations": [],
  "role": null,
  "role_aliases": [],
  "role_archetype": "Engineering",
  "roles_and_responsibilities": [
    {
      "bullet_count": 9,
      "heading": "Responsibilities",
      "heading_was_present": true,
      "source_marker": {
        "first_5_words": "\u2022 Designing / re-engineering processes",
        "last_5_words": "support for overnight batch jobs"
      },
      "text": "\u2022 Designing / re-engineering processes\n\u2022 Writing technical specifications\n\u2022 Designing database architecture, services and user interfaces\n\u2022 Developing code, development, unit and integration testing\n\u2022 Post-launch maintenance; enhancement prioritization in conjunction with the business; on-going release management\n\u2022 Analyzing and implementing new data models\n\u2022 Providing Level 2 application support\n\u2022 Providing support for ad-hoc data and research requests from the investment team\n\u2022 Providing support for overnight batch jobs",
      "word_count": 81
    }
  ],
  "urls": []
}
API 1 — extract-from-jd click to toggle
{
  "final_skills": [
    {
      "is_primary": true,
      "skill_name": "Database Architecture"
    },
    {
      "is_primary": true,
      "skill_name": "Unit Testing"
    },
    {
      "is_primary": true,
      "skill_name": "Integration Testing"
    },
    {
      "is_primary": true,
      "skill_name": "Data Modeling"
    },
    {
      "is_primary": true,
      "skill_name": "Batch Processing"
    }
  ],
  "jd_role": null,
  "nano_parsed": {
    "JD_type": "pass",
    "about_company": null,
    "certifications": [],
    "company_name": null,
    "ctc": null,
    "domain": {
      "primary": {
        "aliases": [],
        "domain": "Other"
      },
      "secondary": null
    },
    "education": [
      {
        "level": "Bachelor\u0027s",
        "qualification": "BTECH/BE - Computer Science / Math / Engineering (or related)",
        "raw": "BS / MS in Computer Science, Math, Engineering and/or related experience",
        "requirement": "required"
      }
    ],
    "experience": {
      "max": null,
      "min": 10,
      "raw": "10 + years of industry experience in coding, designing and building software."
    },
    "job_locations": [],
    "role": null,
    "role_aliases": [],
    "role_archetype": "Engineering",
    "roles_and_responsibilities": [
      {
        "bullet_count": 9,
        "heading": "Responsibilities",
        "heading_was_present": true,
        "source_marker": {
          "first_5_words": "\u2022 Designing / re-engineering processes",
          "last_5_words": "support for overnight batch jobs"
        },
        "text": "\u2022 Designing / re-engineering processes\n\u2022 Writing technical specifications\n\u2022 Designing database architecture, services and user interfaces\n\u2022 Developing code, development, unit and integration testing\n\u2022 Post-launch maintenance; enhancement prioritization in conjunction with the business; on-going release management\n\u2022 Analyzing and implementing new data models\n\u2022 Providing Level 2 application support\n\u2022 Providing support for ad-hoc data and research requests from the investment team\n\u2022 Providing support for overnight batch jobs",
        "word_count": 81
      }
    ],
    "urls": []
  },
  "rejected": false,
  "rejection_reason": null,
  "run_id": "0b709bbb-1e9c-468e-b605-2af9714674f1",
  "stage3_signals": {
    "alias_found": false,
    "alias_match_roles": [],
    "kra_match_roles": [
      {
        "display_name": "Go Backend Developer",
        "kra_matches": [
          {
            "kra_text": "code review and testing support",
            "sentence": "Developing code, development, unit and integration testing",
            "similarity": 0.6049
          },
          {
            "kra_text": "service interface design",
            "sentence": "Designing database architecture, services and user interfaces",
            "similarity": 0.5918
          },
          {
            "kra_text": "background job processing",
            "sentence": "Providing support for overnight batch jobs",
            "similarity": 0.518
          }
        ],
        "matched_count": null,
        "matched_skills": null,
        "role_id": 81,
        "score": 0.5715,
        "slug": "go-backend-developer",
        "total_count": null
      },
      {
        "display_name": "Java Backend Developer",
        "kra_matches": [
          {
            "kra_text": "persistence and data modeling",
            "sentence": "Analyzing and implementing new data models",
            "similarity": 0.5899
          },
          {
            "kra_text": "code refactoring and defect fixes",
            "sentence": "Developing code, development, unit and integration testing",
            "similarity": 0.5411
          },
          {
            "kra_text": "asynchronous job processing",
            "sentence": "Providing support for overnight batch jobs",
            "similarity": 0.5124
          }
        ],
        "matched_count": null,
        "matched_skills": null,
        "role_id": 79,
        "score": 0.5478,
        "slug": "java-backend-developer",
        "total_count": null
      },
      {
        "display_name": ".NET Backend Developer",
        "kra_matches": [
          {
            "kra_text": "service interface design and implementation",
            "sentence": "Designing database architecture, services and user interfaces",
            "similarity": 0.6289
          },
          {
            "kra_text": "backend code refactoring and maintenance",
            "sentence": "Developing code, development, unit and integration testing",
            "similarity": 0.5461
          },
          {
            "kra_text": "backend code refactoring and maintenance",
            "sentence": "Post-launch maintenance; enhancement prioritization in conjunction with the business; on-going release management",
            "similarity": 0.4588
          }
        ],
        "matched_count": null,
        "matched_skills": null,
        "role_id": 83,
        "score": 0.5446,
        "slug": "dotnet-backend-developer",
        "total_count": null
      },
      {
        "display_name": "Node.js Backend Developer",
        "kra_matches": [
          {
            "kra_text": "code review and refactoring",
            "sentence": "Developing code, development, unit and integration testing",
            "similarity": 0.5284
          },
          {
            "kra_text": "data modeling and persistence access",
            "sentence": "Analyzing and implementing new data models",
            "similarity": 0.5217
          },
          {
            "kra_text": "asynchronous job processing",
            "sentence": "Providing support for overnight batch jobs",
            "similarity": 0.5124
          }
        ],
        "matched_count": null,
        "matched_skills": null,
        "role_id": 82,
        "score": 0.5208,
        "slug": "node-backend-developer",
        "total_count": null
      },
      {
        "display_name": "Python Backend Developer",
        "kra_matches": [
          {
            "kra_text": "Support background jobs and async workflows",
            "sentence": "Providing support for overnight batch jobs",
            "similarity": 0.5557
          },
          {
            "kra_text": "Design backend endpoints and request handling",
            "sentence": "Designing database architecture, services and user interfaces",
            "similarity": 0.5161
          },
          {
            "kra_text": "Build service and external integrations",
            "sentence": "Developing code, development, unit and integration testing",
            "similarity": 0.4847
          }
        ],
        "matched_count": null,
        "matched_skills": null,
        "role_id": 80,
        "score": 0.5188,
        "slug": "python-backend-developer",
        "total_count": null
      }
    ],
    "skill_match_roles": [
      {
        "display_name": "Backend Developer",
        "kra_matches": null,
        "matched_count": 1,
        "matched_skills": [
          "Integration testing"
        ],
        "role_id": 1,
        "score": 0.2,
        "slug": "backend-engineer",
        "total_count": 5
      },
      {
        "display_name": "Pega Developer",
        "kra_matches": null,
        "matched_count": 1,
        "matched_skills": [
          "Integration testing"
        ],
        "role_id": 24,
        "score": 0.2,
        "slug": "pega-developer",
        "total_count": 5
      },
      {
        "display_name": "Python Backend Developer",
        "kra_matches": null,
        "matched_count": 1,
        "matched_skills": [
          "Integration testing"
        ],
        "role_id": 80,
        "score": 0.2,
        "slug": "python-backend-developer",
        "total_count": 5
      },
      {
        "display_name": "Node.js Backend Developer",
        "kra_matches": null,
        "matched_count": 1,
        "matched_skills": [
          "Integration testing"
        ],
        "role_id": 82,
        "score": 0.2,
        "slug": "node-backend-developer",
        "total_count": 5
      },
      {
        "display_name": ".NET Backend Developer",
        "kra_matches": null,
        "matched_count": 1,
        "matched_skills": [
          "Integration testing"
        ],
        "role_id": 83,
        "score": 0.2,
        "slug": "dotnet-backend-developer",
        "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.9,
      "slug": "backend-engineer",
      "total_count": null
    },
    "confidence": 0.9,
    "is_new_role": false,
    "llm2_fired": false,
    "llm2_reasoning": null,
    "matched_dimensions": [
      "Process re-engineering",
      "Application and service design",
      "Database architecture and data modeling",
      "Software development and testing",
      "Production support and maintenance",
      "Batch job support"
    ],
    "matched_kras": [
      "Designing / re-engineering processes",
      "Writing technical specifications",
      "Designing database architecture, services and user interfaces",
      "Developing code, development, unit and integration testing",
      "Post-launch maintenance; enhancement prioritization",
      "Analyzing and implementing new data models",
      "Providing Level 2 application support",
      "Providing support for ad-hoc data and research requests",
      "Providing support for overnight batch jobs"
    ],
    "matched_skills": [
      "technical specifications",
      "database architecture",
      "services",
      "user interfaces",
      "development",
      "unit and integration testing",
      "release management",
      "data models",
      "Level 2 application support",
      "overnight batch jobs"
    ],
    "new_role_display_name": null,
    "new_role_slug": null,
    "queued": false,
    "reasoning": "Domain=Software Engineering; The JD centers on designing services, writing technical specs, developing and testing code, data models, release management, and application support, which best matches a backend/application engineer role.",
    "sub_role": null
  },
  "stage5_updates": {
    "centroid_n_after": 1101,
    "centroid_updated": true,
    "collision_log_id": null,
    "new_kra_attached": {
      "best_kra_similarity": 0.0,
      "queue_id": 1156,
      "r_and_r_preview": "\u2022 Designing / re-engineering processes\n\u2022 Writing technical specifications\n\u2022 Designing database architecture, services and user interfaces\n\u2022 Developing code, development, unit and integration testing\n\u2022",
      "role_display_name": "Backend Developer",
      "role_slug": "backend-engineer",
      "status": "pending"
    },
    "new_skills_attached": [
      {
        "is_primary": true,
        "queue_id": 16257,
        "role_display_name": "Backend Developer",
        "role_slug": "backend-engineer",
        "skill_name": "Database Architecture",
        "status": "pending"
      },
      {
        "is_primary": true,
        "queue_id": 16258,
        "role_display_name": "Backend Developer",
        "role_slug": "backend-engineer",
        "skill_name": "Data Modeling",
        "status": "pending"
      },
      {
        "is_primary": true,
        "queue_id": 16259,
        "role_display_name": "Backend Developer",
        "role_slug": "backend-engineer",
        "skill_name": "Batch Processing",
        "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": 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": 193,
      "existing_alias_text": "integration testing",
      "input_term": "Integration Testing",
      "matched_canonical": {
        "category_id": 8,
        "display_name": "Integration testing",
        "id": 56,
        "is_also_category": false,
        "is_extractable": true,
        "skill_nature": "METHODOLOGY",
        "slug": "integration-testing",
        "sub_category_id": 44,
        "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": 5644,
      "existing_alias_text": "Domain Modeling",
      "input_term": "Data Modeling",
      "matched_canonical": {
        "category_id": 8,
        "display_name": "domain modeling",
        "id": 2379,
        "is_also_category": false,
        "is_extractable": true,
        "skill_nature": "METHODOLOGY",
        "slug": "domain-modeling",
        "sub_category_id": 2831,
        "typical_lifespan": "EVERGREEN",
        "volatility": "STABLE"
      },
      "matched_via": "embedding_alias"
    }
  ],
  "candidate_roles": [
    {
      "display_name": "Pega Developer",
      "id": 24,
      "rationale": null,
      "role_archetype": null,
      "slug": "pega-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": "Node.js Backend Developer",
      "id": 82,
      "rationale": null,
      "role_archetype": "Engineering",
      "slug": "node-backend-developer",
      "source": "db"
    },
    {
      "display_name": "PHP Backend Developer",
      "id": 86,
      "rationale": null,
      "role_archetype": "Engineering",
      "slug": "php-backend-developer",
      "source": "db"
    },
    {
      "display_name": "Python Backend Developer",
      "id": 80,
      "rationale": null,
      "role_archetype": "Engineering",
      "slug": "python-backend-developer",
      "source": "db"
    },
    {
      "display_name": "Scala Backend Developer",
      "id": 87,
      "rationale": null,
      "role_archetype": "Engineering",
      "slug": "scala-backend-developer",
      "source": "db"
    },
    {
      "display_name": "Java Backend Developer",
      "id": 79,
      "rationale": null,
      "role_archetype": "Engineering",
      "slug": "java-backend-developer",
      "source": "db"
    },
    {
      "display_name": "Kotlin Backend Developer",
      "id": 84,
      "rationale": null,
      "role_archetype": "Engineering",
      "slug": "kotlin-server-backend-developer",
      "source": "db"
    },
    {
      "display_name": "Ruby Backend Developer",
      "id": 85,
      "rationale": null,
      "role_archetype": "Engineering",
      "slug": "ruby-backend-developer",
      "source": "db"
    }
  ],
  "chosen_role": {
    "display_name": "Backend Developer",
    "id": 1,
    "rationale": "Domain=Software Engineering; The JD centers on designing services, writing technical specs, developing and testing code, data models, release management, and application support, which best matches a backend/application engineer role.",
    "role_archetype": "A Backend Engineer designs, builds, and maintains the server-side logic and data handling that power applications and services. They focus on implementing reliable business functionality, integrating with other systems, and ensuring the backend is scalable, maintainable, and observable.",
    "slug": "backend-engineer",
    "source": "db"
  },
  "dimensions": [
    {
      "dimension": {
        "difficulty_hint": "well_known",
        "display_name": "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": "Testing and Defect Resolution",
        "id": 262,
        "rationale": "Validates Pega rules, flows, and integrations and then troubleshoots defects found in lower environments or production. This is a coherent cluster because the role is expected to verify platform behavior and fix rule-level issues.",
        "slug": "testing-and-defect-resolution",
        "source": "db"
      },
      "input_skill": "Integration Testing",
      "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": "Testing and Quality Assurance",
        "id": 12,
        "rationale": "Backend-specific test strategies used to validate service behavior and integration points. Covers automated test layers, contract checks, fixtures, and regression prevention.",
        "slug": "testing-and-quality-assurance",
        "source": "db"
      },
      "input_skill": "Integration Testing",
      "llm_role": null,
      "roles_from_db": [
        {
          "display_name": ".NET Backend Developer",
          "id": 83,
          "rationale": null,
          "role_archetype": "Engineering",
          "slug": "dotnet-backend-developer",
          "source": "db"
        },
        {
          "display_name": "Backend Developer",
          "id": 1,
          "rationale": null,
          "role_archetype": "A Backend Engineer designs, builds, and maintains the server-side logic and data handling that power applications and services. They focus on implementing reliable business functionality, integrating with other systems, and ensuring the backend is scalable, maintainable, and observable.",
          "slug": "backend-engineer",
          "source": "db"
        },
        {
          "display_name": "Node.js Backend Developer",
          "id": 82,
          "rationale": null,
          "role_archetype": "Engineering",
          "slug": "node-backend-developer",
          "source": "db"
        },
        {
          "display_name": "PHP Backend Developer",
          "id": 86,
          "rationale": null,
          "role_archetype": "Engineering",
          "slug": "php-backend-developer",
          "source": "db"
        },
        {
          "display_name": "Python Backend Developer",
          "id": 80,
          "rationale": null,
          "role_archetype": "Engineering",
          "slug": "python-backend-developer",
          "source": "db"
        },
        {
          "display_name": "Scala Backend Developer",
          "id": 87,
          "rationale": null,
          "role_archetype": "Engineering",
          "slug": "scala-backend-developer",
          "source": "db"
        }
      ]
    },
    {
      "dimension": {
        "difficulty_hint": "well_known",
        "display_name": "Application Architecture Patterns",
        "id": 293,
        "rationale": "Structural patterns for organizing Python backend code into maintainable modules, layers, and feature boundaries. This is a coherent cluster because senior backend developers are expected to refactor and shape service internals over time.",
        "slug": "application-architecture-patterns",
        "source": "db"
      },
      "input_skill": "Data Modeling",
      "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": "Python Backend Developer",
          "id": 80,
          "rationale": null,
          "role_archetype": "Engineering",
          "slug": "python-backend-developer",
          "source": "db"
        }
      ]
    },
    {
      "dimension": {
        "difficulty_hint": "well_known",
        "display_name": "Service Architecture and Design Patterns",
        "id": 18,
        "rationale": "Reusable backend design patterns used to structure service code and boundaries. Covers layering, dependency management, domain modeling, and maintainable service organization.",
        "slug": "service-architecture-and-design-patterns",
        "source": "db"
      },
      "input_skill": "Data Modeling",
      "llm_role": null,
      "roles_from_db": [
        {
          "display_name": "Backend Developer",
          "id": 1,
          "rationale": null,
          "role_archetype": "A Backend Engineer designs, builds, and maintains the server-side logic and data handling that power applications and services. They focus on implementing reliable business functionality, integrating with other systems, and ensuring the backend is scalable, maintainable, and observable.",
          "slug": "backend-engineer",
          "source": "db"
        },
        {
          "display_name": "Java Backend Developer",
          "id": 79,
          "rationale": null,
          "role_archetype": "Engineering",
          "slug": "java-backend-developer",
          "source": "db"
        },
        {
          "display_name": "Kotlin Backend Developer",
          "id": 84,
          "rationale": null,
          "role_archetype": "Engineering",
          "slug": "kotlin-server-backend-developer",
          "source": "db"
        },
        {
          "display_name": "Node.js Backend Developer",
          "id": 82,
          "rationale": null,
          "role_archetype": "Engineering",
          "slug": "node-backend-developer",
          "source": "db"
        },
        {
          "display_name": "PHP Backend Developer",
          "id": 86,
          "rationale": null,
          "role_archetype": "Engineering",
          "slug": "php-backend-developer",
          "source": "db"
        },
        {
          "display_name": "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_final_skills": [
    "Database Architecture",
    "Unit Testing",
    "Integration Testing",
    "Data Modeling",
    "Batch Processing"
  ],
  "input_llm_skills": [
    "Database Architecture",
    "Unit Testing",
    "Integration Testing",
    "Data Modeling",
    "Batch Processing"
  ],
  "new_aliases_persisted": 0,
  "run_id": "0b709bbb-1e9c-468e-b605-2af9714674f1",
  "skills_detail": [
    {
      "aliases_in_db": [],
      "canonical": null,
      "dimensions": [],
      "input_skill": "Database Architecture",
      "matched_via": null,
      "new_alias_persisted": false,
      "new_alias_text": null,
      "new_skill_meta": {
        "derived": {
          "category": "Concepts",
          "skill_nature": "CONCEPT",
          "sub_category": "general",
          "typical_lifespan": "EVERGREEN",
          "version_strategy": "UNVERSIONED",
          "volatility": "STABLE"
        },
        "enrichment": null,
        "keep_log": [],
        "locked_dimensions": [],
        "merge_log": [],
        "placed": null,
        "relationships": null,
        "skill_id": "database-architecture",
        "split_log": [],
        "typed": null,
        "warnings": []
      },
      "source_tag": "llm",
      "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": [
        {
          "alias_text": "Integration testing",
          "alias_type": "CANONICAL",
          "id": 2945,
          "is_primary": true,
          "match_strategy": "CASE_INSENSITIVE"
        },
        {
          "alias_text": "integration testing",
          "alias_type": "CANONICAL",
          "id": 193,
          "is_primary": false,
          "match_strategy": "CASE_INSENSITIVE"
        }
      ],
      "canonical": {
        "category_id": 8,
        "display_name": "Integration testing",
        "id": 56,
        "is_also_category": false,
        "is_extractable": true,
        "skill_nature": "METHODOLOGY",
        "slug": "integration-testing",
        "sub_category_id": 44,
        "typical_lifespan": "EVERGREEN",
        "volatility": "STABLE"
      },
      "dimensions": [
        {
          "dimension": {
            "difficulty_hint": "well_known",
            "display_name": "Testing and Defect Resolution",
            "id": 262,
            "rationale": "Validates Pega rules, flows, and integrations and then troubleshoots defects found in lower environments or production. This is a coherent cluster because the role is expected to verify platform behavior and fix rule-level issues.",
            "slug": "testing-and-defect-resolution",
            "source": "db"
          },
          "input_skill": "Integration Testing",
          "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": "Testing and Quality Assurance",
            "id": 12,
            "rationale": "Backend-specific test strategies used to validate service behavior and integration points. Covers automated test layers, contract checks, fixtures, and regression prevention.",
            "slug": "testing-and-quality-assurance",
            "source": "db"
          },
          "input_skill": "Integration Testing",
          "llm_role": null,
          "roles_from_db": [
            {
              "display_name": ".NET Backend Developer",
              "id": 83,
              "rationale": null,
              "role_archetype": "Engineering",
              "slug": "dotnet-backend-developer",
              "source": "db"
            },
            {
              "display_name": "Backend Developer",
              "id": 1,
              "rationale": null,
              "role_archetype": "A Backend Engineer designs, builds, and maintains the server-side logic and data handling that power applications and services. They focus on implementing reliable business functionality, integrating with other systems, and ensuring the backend is scalable, maintainable, and observable.",
              "slug": "backend-engineer",
              "source": "db"
            },
            {
              "display_name": "Node.js Backend Developer",
              "id": 82,
              "rationale": null,
              "role_archetype": "Engineering",
              "slug": "node-backend-developer",
              "source": "db"
            },
            {
              "display_name": "PHP Backend Developer",
              "id": 86,
              "rationale": null,
              "role_archetype": "Engineering",
              "slug": "php-backend-developer",
              "source": "db"
            },
            {
              "display_name": "Python Backend Developer",
              "id": 80,
              "rationale": null,
              "role_archetype": "Engineering",
              "slug": "python-backend-developer",
              "source": "db"
            },
            {
              "display_name": "Scala Backend Developer",
              "id": 87,
              "rationale": null,
              "role_archetype": "Engineering",
              "slug": "scala-backend-developer",
              "source": "db"
            }
          ]
        }
      ],
      "input_skill": "Integration 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": [
        {
          "alias_text": "domain modeling",
          "alias_type": "CANONICAL",
          "id": 3675,
          "is_primary": true,
          "match_strategy": "CASE_INSENSITIVE"
        },
        {
          "alias_text": "Domain Modeling",
          "alias_type": "CANONICAL",
          "id": 5644,
          "is_primary": false,
          "match_strategy": "CASE_INSENSITIVE"
        }
      ],
      "canonical": {
        "category_id": 8,
        "display_name": "domain modeling",
        "id": 2379,
        "is_also_category": false,
        "is_extractable": true,
        "skill_nature": "METHODOLOGY",
        "slug": "domain-modeling",
        "sub_category_id": 2831,
        "typical_lifespan": "EVERGREEN",
        "volatility": "STABLE"
      },
      "dimensions": [
        {
          "dimension": {
            "difficulty_hint": "well_known",
            "display_name": "Application Architecture Patterns",
            "id": 293,
            "rationale": "Structural patterns for organizing Python backend code into maintainable modules, layers, and feature boundaries. This is a coherent cluster because senior backend developers are expected to refactor and shape service internals over time.",
            "slug": "application-architecture-patterns",
            "source": "db"
          },
          "input_skill": "Data Modeling",
          "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": "Python Backend Developer",
              "id": 80,
              "rationale": null,
              "role_archetype": "Engineering",
              "slug": "python-backend-developer",
              "source": "db"
            }
          ]
        },
        {
          "dimension": {
            "difficulty_hint": "well_known",
            "display_name": "Service Architecture and Design Patterns",
            "id": 18,
            "rationale": "Reusable backend design patterns used to structure service code and boundaries. Covers layering, dependency management, domain modeling, and maintainable service organization.",
            "slug": "service-architecture-and-design-patterns",
            "source": "db"
          },
          "input_skill": "Data Modeling",
          "llm_role": null,
          "roles_from_db": [
            {
              "display_name": "Backend Developer",
              "id": 1,
              "rationale": null,
              "role_archetype": "A Backend Engineer designs, builds, and maintains the server-side logic and data handling that power applications and services. They focus on implementing reliable business functionality, integrating with other systems, and ensuring the backend is scalable, maintainable, and observable.",
              "slug": "backend-engineer",
              "source": "db"
            },
            {
              "display_name": "Java Backend Developer",
              "id": 79,
              "rationale": null,
              "role_archetype": "Engineering",
              "slug": "java-backend-developer",
              "source": "db"
            },
            {
              "display_name": "Kotlin Backend Developer",
              "id": 84,
              "rationale": null,
              "role_archetype": "Engineering",
              "slug": "kotlin-server-backend-developer",
              "source": "db"
            },
            {
              "display_name": "Node.js Backend Developer",
              "id": 82,
              "rationale": null,
              "role_archetype": "Engineering",
              "slug": "node-backend-developer",
              "source": "db"
            },
            {
              "display_name": "PHP Backend Developer",
              "id": 86,
              "rationale": null,
              "role_archetype": "Engineering",
              "slug": "php-backend-developer",
              "source": "db"
            },
            {
              "display_name": "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": "Data Modeling",
      "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": [],
      "canonical": null,
      "dimensions": [],
      "input_skill": "Batch Processing",
      "matched_via": null,
      "new_alias_persisted": false,
      "new_alias_text": null,
      "new_skill_meta": {
        "derived": {
          "category": "Concepts",
          "skill_nature": "CONCEPT",
          "sub_category": "general",
          "typical_lifespan": "MULTI_YEAR",
          "version_strategy": "UNVERSIONED",
          "volatility": "MEDIUM"
        },
        "enrichment": null,
        "keep_log": [],
        "locked_dimensions": [],
        "merge_log": [],
        "placed": null,
        "relationships": null,
        "skill_id": "batch-processing",
        "split_log": [],
        "typed": null,
        "warnings": []
      },
      "source_tag": "llm",
      "was_in_llm_skills": true
    }
  ],
  "unmatched_skills": [
    "Database Architecture",
    "Batch Processing"
  ]
}
API 3 — final-role-output
{
  "chosen_role": {
    "display_name": "Backend Developer",
    "id": 1,
    "rationale": "Domain=Software Engineering; The JD centers on designing services, writing technical specs, developing and testing code, data models, release management, and application support, which best matches a backend/application engineer role.",
    "role_archetype": "A Backend Engineer designs, builds, and maintains the server-side logic and data handling that power applications and services. They focus on implementing reliable business functionality, integrating with other systems, and ensuring the backend is scalable, maintainable, and observable.",
    "slug": "backend-engineer",
    "source": "db"
  },
  "chosen_role_resolution": "in_db",
  "final_input_skills": [
    {
      "skill": "Database Architecture",
      "tag": "new"
    },
    {
      "skill": "Unit Testing",
      "tag": "in_db"
    },
    {
      "skill": "Integration Testing",
      "tag": "in_db"
    },
    {
      "skill": "Data Modeling",
      "tag": "in_db"
    },
    {
      "skill": "Batch Processing",
      "tag": "new"
    }
  ],
  "llm_cost_api1_usd": null,
  "llm_cost_api2_usd": null,
  "llm_cost_api3_usd": null,
  "llm_cost_total_usd": null,
  "persistence": {
    "items": [
      {
        "chosen_role_id": 1,
        "dimension": {
          "difficulty_hint": "well_known",
          "display_name": "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": "Testing and Defect Resolution",
          "id": 262,
          "rationale": "Validates Pega rules, flows, and integrations and then troubleshoots defects found in lower environments or production. This is a coherent cluster because the role is expected to verify platform behavior and fix rule-level issues.",
          "slug": "testing-and-defect-resolution",
          "source": "db"
        },
        "dimension_id": 262,
        "input_skill": "Integration 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": [
          {
            "display_name": "Pega Developer",
            "id": 24,
            "rationale": null,
            "role_archetype": null,
            "slug": "pega-developer",
            "source": "db"
          }
        ],
        "skill_dimension_saved": true,
        "skill_id": 56,
        "skill_tag": "in_db",
        "skipped_reason": null
      },
      {
        "chosen_role_id": 1,
        "dimension": {
          "difficulty_hint": "well_known",
          "display_name": "Testing and Quality Assurance",
          "id": 12,
          "rationale": "Backend-specific test strategies used to validate service behavior and integration points. Covers automated test layers, contract checks, fixtures, and regression prevention.",
          "slug": "testing-and-quality-assurance",
          "source": "db"
        },
        "dimension_id": 12,
        "input_skill": "Integration Testing",
        "llm_role": null,
        "matched_chosen_role": true,
        "outcome_line": "Existing dimension (library) \u00b7 Role\u2194dimension saved",
        "role_dimension_saved": true,
        "roles_from_db": [
          {
            "display_name": ".NET Backend Developer",
            "id": 83,
            "rationale": null,
            "role_archetype": "Engineering",
            "slug": "dotnet-backend-developer",
            "source": "db"
          },
          {
            "display_name": "Backend Developer",
            "id": 1,
            "rationale": null,
            "role_archetype": "A Backend Engineer designs, builds, and maintains the server-side logic and data handling that power applications and services. They focus on implementing reliable business functionality, integrating with other systems, and ensuring the backend is scalable, maintainable, and observable.",
            "slug": "backend-engineer",
            "source": "db"
          },
          {
            "display_name": "Node.js Backend Developer",
            "id": 82,
            "rationale": null,
            "role_archetype": "Engineering",
            "slug": "node-backend-developer",
            "source": "db"
          },
          {
            "display_name": "PHP Backend Developer",
            "id": 86,
            "rationale": null,
            "role_archetype": "Engineering",
            "slug": "php-backend-developer",
            "source": "db"
          },
          {
            "display_name": "Python Backend Developer",
            "id": 80,
            "rationale": null,
            "role_archetype": "Engineering",
            "slug": "python-backend-developer",
            "source": "db"
          },
          {
            "display_name": "Scala Backend Developer",
            "id": 87,
            "rationale": null,
            "role_archetype": "Engineering",
            "slug": "scala-backend-developer",
            "source": "db"
          }
        ],
        "skill_dimension_saved": true,
        "skill_id": 56,
        "skill_tag": "in_db",
        "skipped_reason": null
      },
      {
        "chosen_role_id": 1,
        "dimension": {
          "difficulty_hint": "well_known",
          "display_name": "Application Architecture Patterns",
          "id": 293,
          "rationale": "Structural patterns for organizing Python backend code into maintainable modules, layers, and feature boundaries. This is a coherent cluster because senior backend developers are expected to refactor and shape service internals over time.",
          "slug": "application-architecture-patterns",
          "source": "db"
        },
        "dimension_id": 293,
        "input_skill": "Data Modeling",
        "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": ".NET Backend Developer",
            "id": 83,
            "rationale": null,
            "role_archetype": "Engineering",
            "slug": "dotnet-backend-developer",
            "source": "db"
          },
          {
            "display_name": "Python Backend Developer",
            "id": 80,
            "rationale": null,
            "role_archetype": "Engineering",
            "slug": "python-backend-developer",
            "source": "db"
          }
        ],
        "skill_dimension_saved": 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": "Service Architecture and Design Patterns",
          "id": 18,
          "rationale": "Reusable backend design patterns used to structure service code and boundaries. Covers layering, dependency management, domain modeling, and maintainable service organization.",
          "slug": "service-architecture-and-design-patterns",
          "source": "db"
        },
        "dimension_id": 18,
        "input_skill": "Data Modeling",
        "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": "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": "Java Backend Developer",
            "id": 79,
            "rationale": null,
            "role_archetype": "Engineering",
            "slug": "java-backend-developer",
            "source": "db"
          },
          {
            "display_name": "Kotlin Backend Developer",
            "id": 84,
            "rationale": null,
            "role_archetype": "Engineering",
            "slug": "kotlin-server-backend-developer",
            "source": "db"
          },
          {
            "display_name": "Node.js Backend Developer",
            "id": 82,
            "rationale": null,
            "role_archetype": "Engineering",
            "slug": "node-backend-developer",
            "source": "db"
          },
          {
            "display_name": "PHP Backend Developer",
            "id": 86,
            "rationale": null,
            "role_archetype": "Engineering",
            "slug": "php-backend-developer",
            "source": "db"
          },
          {
            "display_name": "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"
      }
    ],
    "new_skills_created": 0,
    "role_dimension_saved": 0,
    "skill_dimension_saved": 0,
    "skipped": 2
  },
  "planner_output": null,
  "run_id": "0b709bbb-1e9c-468e-b605-2af9714674f1"
}

LLM Calls

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

Loading…