← Back to history

Pipeline run

e3cc2eb5-c066-4a6b-8329-e69fe536af3f

Pipeline LLM cost (USD)
API 1: $0.0082 API 2: $0.0000 API 3: $0.0000 Total: $0.0082

Client output enrichment

v2 Skill cluster · Nature of work · AI index · Tech stack maturity · Evidence · KRA description
SPARSE JD role baseline loaded sources · ai_index: role_baseline · nature_of_work: jd · tech_stack_maturity: jd
Nature of work · End-to-end feature delivery
Build and improve scalable microservice/API/UI components, review code, troubleshoot production issues, and drive performance, reliability, and architecture improvements in Agile sprints while mentoring junior developers.
"“Contribute to the development of microservices, APIs, or UI components as per the project requirements.”"
Tech stack maturity
Mainstream Modern
The combination of fullstack development with agile practices and microservices is characteristic of a mainstream modern engineering stack, without explicit signals of legacy systems or cutting-edge AI-native tooling.
AI index (0 = no AI use, 5 = totally AI-dependent · v2.1)
2.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 (3)
Microservices Agile Scrum
Skill cluster (1 dimension groups, role-scoped)
Cross-cutting / unaligned
Microservices Agile Scrum
Show KRA description ↓
• Design, implement, and optimize clean, scalable, and reliable code across systems. • Contribute to the development of microservices, APIs, or UI components as per the project requirements. • Collaborate design and enhance system architecture. • Analyse and identify opportunities for performance improvements and scalability. • Conduct thorough code reviews to ensure code quality, maintainability, and adherence to best practices. • Mentor and support junior developers, fostering a culture of learning and growth. • Work within an Agile/Scrum framework, participating in sprint planning, daily stand-ups, and retrospectives. • Collaborate with Carbon Science, Designer, and other stakeholders to translate requirements into technical solutions. • Investigate, troubleshoot, and resolve complex issues in production and development environments. • Contribute to incident management and root cause analysis to improve system reliability. • Stay up-to-date with emerging technologies and industry trends. • Propose and implement improvements to existing codebases, tools, and development.

Signals

Skill engineering-manager
0.67
Alias
KRA backend-engineer
0.65

Post-classification

Centroidupdated · n=554
Alias collision log
New-role queue
New skills captured0
New KRA capturedyes

Captured for admin review

R&R fragment (sim 0.00) Fullstack Developer pending

• Design, implement, and optimize clean, scalable, and reliable code across systems. • Contribute to the development of microservices, APIs, or UI components as per the project requirements. • Collabo…

Status: completed Created: 2026-05-27T15:50:57.667461Z Updated: 2026-06-12T15:50:52.164762Z API 3 duration: 10405 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

Fullstack Developer

domain · Software Engineering CASE DOMAIN

slug: full-stack-engineer · id: 15 · source: db

Domain=Software Engineering; The JD describes a general software engineer working across microservices, APIs, UI components, architecture, code quality, troubleshooting, and Agile collaboration, which best matches a full-stack engineering role.

Matched skills

microservicesAPIsUI componentssystem architecturecode reviewsAgile/Scrumsprint planningdaily stand-upsretrospectivesroot cause analysis

Matched dimensions

Software EngineeringFull-Stack DevelopmentSystem ArchitecturePerformance and ScalabilityCode Quality and MaintainabilityProduction Support and ReliabilityAgile Team CollaborationMentoring and Technical Leadership

Matched KRAs

Design, implement, and optimize clean, scalable, and reliable codeContribute to the development of microservices, APIs, or UI componentsCollaborate design and enhance system architectureAnalyse and identify opportunities for performance improvements and scalabilityConduct thorough code reviewsMentor and support junior developersInvestigate, troubleshoot, and resolve complex issuesContribute to incident management and root cause analysisPropose and implement improvements to existing codebases

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 Description

Responsibilities :

• Design, implement, and optimize clean, scalable, and reliable code across systems.
• Contribute to the development of microservices, APIs, or UI components as per the project requirements.
• Collaborate design and enhance system architecture.
• Analyse and identify opportunities for performance improvements and scalability.
• Conduct thorough code reviews to ensure code quality, maintainability, and adherence to best practices.
• Mentor and support junior developers, fostering a culture of learning and growth.
• Work within an Agile/Scrum framework, participating in sprint planning, daily stand-ups, and retrospectives.
• Collaborate with Carbon Science, Designer, and other stakeholders to translate requirements into technical solutions.
• Investigate, troubleshoot, and resolve complex issues in production and development environments.
• Contribute to incident management and root cause analysis to improve system reliability.
• Stay up-to-date with emerging technologies and industry trends.
• Propose and implement improvements to existing codebases, tools, and development :
• 2-5 years of professional software development experience in Java, Python, JavaScript, etc.
• Bachelor's degree in Computer Science, Engineering, or equivalent experience.
• Experience with cloud platforms like AWS, Azure, or GCP.
• Knowledge of version control tools (e. g., Git) and CI/CD pipelines.
• Understanding of data structures, algorithms, and system design principles.
• Knowledge of database technologies (SQL and NoSQL).
• Strong analytical and problem-solving skills.
• Excellent written and verbal communication skills.
• Ability to work in a fast-paced environment and manage multiple priorities effectively.


(ref:hirist.tech)

Skills from this JD

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

Microservices Primary Library skill API 3: existing canonical (in_db) Existing skill (matched library)
Canonical: microservices id=41 · microservices

Aliases — catalog

  • microservices (CANONICAL) primary

Context tags (catalog)

API Gateway API gateway CQRS DevOps Docker Kubernetes REST API RESTful services Saga pattern Spring Boot circuit breaker containerization decentralized distributed tracing domain-driven design event sourcing event-driven event-driven architecture gRPC load balancing message broker microservices patterns monitoring scalability service discovery service mesh

Stored enrichment (catalog DB)

Category
Architecture
Sub-category
Distributed System Architecture
Confidence
0.99
Version strategy
NOT_APPLICABLE

Maturity reasoning: Microservices is a common architecture in job descriptions across backend/cloud roles, and major vendors like AWS, Google Cloud, and Kubernetes ecosystems provide first-class support and reference patterns.

Skill profile (library / DB)

Skill nature
PATTERN
Volatility
STABLE
Typical lifespan
EVERGREEN
Category id
1
Sub-category id
1
Extractable
True
Also category
False

Dimensions (API 2 worklist)

  • Microservices and Distributed Systems Catalog dimension db id 9

    Library dimension (catalog)

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

API 3 link attempts (this skill)

Dimension Skill↔dim Role↔dim Outcome
Microservices and Distributed Systems
microservices-and-distributed-systems
Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role)
Agile Primary Library skill API 3: existing canonical (in_db) Existing skill (matched library)
Canonical: Agile id=520 · agile

Aliases — catalog

  • Agile (CANONICAL) primary

Context tags (catalog)

Kanban SAFe Scrum backlog backlog grooming burndown burndown chart continuous delivery continuous improvement cross-functional daily standup epics incremental development iteration iteration planning lean product backlog product owner retrospective sprint sprint planning stand-up story points user stories velocity

Stored enrichment (catalog DB)

Category
Methodology
Sub-category
Agile
Confidence
0.99
Version strategy
NOT_APPLICABLE

Maturity reasoning: Agile appears in a large share of software job descriptions and is a standard hiring-pipeline requirement; Scrum/Kanban are commonly listed alongside it, showing broad market adoption.

Skill profile (library / DB)

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

Dimensions (API 2 worklist)

  • React Frontend Development Catalog dimension db id 96

    Library dimension (catalog)

  • Software Concepts, Patterns & Practices Catalog dimension db id 478

    Library dimension (catalog)

    Roles linked in library: Engineering Manager

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)
Software Concepts, Patterns & Practices
software-concepts-patterns-practices
Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role)
Scrum Primary Library skill API 3: existing canonical (in_db) Existing skill (matched library)
Canonical: Scrum id=1215 · scrum

Aliases — catalog

  • Scrum (CANONICAL) primary

Context tags (catalog)

Agile Kanban backlog burndown chart cross-functional team daily standup definition of done increment product owner release planning retrospective scrum framework scrum master sprint story points user stories velocity

Stored enrichment (catalog DB)

Category
Methodology
Sub-category
Scrum
Confidence
0.99
Version strategy
NOT_APPLICABLE

Maturity reasoning: Scrum appears in a large share of agile project-management and product-owner job descriptions, and Scrum Alliance/PSM certifications are widely requested in hiring pipelines.

Skill profile (library / DB)

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

Dimensions (API 2 worklist)

  • React Frontend Development Catalog dimension db id 96

    Library dimension (catalog)

  • Software Concepts, Patterns & Practices Catalog dimension db id 478

    Library dimension (catalog)

    Roles linked in library: Engineering Manager

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)
Software Concepts, Patterns & Practices
software-concepts-patterns-practices
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
Microservices in_db
Microservices and Distributed Systems
microservices-and-distributed-systems
Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role)
Agile in_db
React Frontend Development
d_init_01
Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role)
Agile in_db
Software Concepts, Patterns & Practices
software-concepts-patterns-practices
Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role)
Scrum in_db
React Frontend Development
d_init_01
Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role)
Scrum in_db
Software Concepts, Patterns & Practices
software-concepts-patterns-practices
Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role)

Library artifacts (this run)

No artifact rows for this run.
nano JD Parser — gpt-4.1-nano click to toggle
Experience2-5 years of professional software development experience
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 (or equivalent)",
      "raw": "Bachelor\u0027s degree in Computer Science, Engineering, or equivalent experience",
      "requirement": "required"
    }
  ],
  "experience": {
    "max": 5,
    "min": 2,
    "raw": "2-5 years of professional software development experience"
  },
  "job_locations": [],
  "role": null,
  "role_aliases": [],
  "role_archetype": "Engineering",
  "roles_and_responsibilities": [
    {
      "bullet_count": 12,
      "heading": "Responsibilities",
      "heading_was_present": true,
      "source_marker": {
        "first_5_words": "\u2022 Design, implement, and optimize",
        "last_5_words": "improvements to existing codebases, tools,"
      },
      "text": "\u2022 Design, implement, and optimize clean, scalable, and reliable code across systems.\n\u2022 Contribute to the development of microservices, APIs, or UI components as per the project requirements.\n\u2022 Collaborate design and enhance system architecture.\n\u2022 Analyse and identify opportunities for performance improvements and scalability.\n\u2022 Conduct thorough code reviews to ensure code quality, maintainability, and adherence to best practices.\n\u2022 Mentor and support junior developers, fostering a culture of learning and growth.\n\u2022 Work within an Agile/Scrum framework, participating in sprint planning, daily stand-ups, and retrospectives.\n\u2022 Collaborate with Carbon Science, Designer, and other stakeholders to translate requirements into technical solutions.\n\u2022 Investigate, troubleshoot, and resolve complex issues in production and development environments.\n\u2022 Contribute to incident management and root cause analysis to improve system reliability.\n\u2022 Stay up-to-date with emerging technologies and industry trends.\n\u2022 Propose and implement improvements to existing codebases, tools, and development.",
      "word_count": 186
    }
  ],
  "urls": [
    {
      "type": "other",
      "url": "https://hirist.tech"
    }
  ]
}
API 1 — extract-from-jd click to toggle
{
  "final_skills": [
    {
      "is_primary": true,
      "skill_name": "Microservices"
    },
    {
      "is_primary": true,
      "skill_name": "Agile"
    },
    {
      "is_primary": true,
      "skill_name": "Scrum"
    }
  ],
  "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 (or equivalent)",
        "raw": "Bachelor\u0027s degree in Computer Science, Engineering, or equivalent experience",
        "requirement": "required"
      }
    ],
    "experience": {
      "max": 5,
      "min": 2,
      "raw": "2-5 years of professional software development experience"
    },
    "job_locations": [],
    "role": null,
    "role_aliases": [],
    "role_archetype": "Engineering",
    "roles_and_responsibilities": [
      {
        "bullet_count": 12,
        "heading": "Responsibilities",
        "heading_was_present": true,
        "source_marker": {
          "first_5_words": "\u2022 Design, implement, and optimize",
          "last_5_words": "improvements to existing codebases, tools,"
        },
        "text": "\u2022 Design, implement, and optimize clean, scalable, and reliable code across systems.\n\u2022 Contribute to the development of microservices, APIs, or UI components as per the project requirements.\n\u2022 Collaborate design and enhance system architecture.\n\u2022 Analyse and identify opportunities for performance improvements and scalability.\n\u2022 Conduct thorough code reviews to ensure code quality, maintainability, and adherence to best practices.\n\u2022 Mentor and support junior developers, fostering a culture of learning and growth.\n\u2022 Work within an Agile/Scrum framework, participating in sprint planning, daily stand-ups, and retrospectives.\n\u2022 Collaborate with Carbon Science, Designer, and other stakeholders to translate requirements into technical solutions.\n\u2022 Investigate, troubleshoot, and resolve complex issues in production and development environments.\n\u2022 Contribute to incident management and root cause analysis to improve system reliability.\n\u2022 Stay up-to-date with emerging technologies and industry trends.\n\u2022 Propose and implement improvements to existing codebases, tools, and development.",
        "word_count": 186
      }
    ],
    "urls": [
      {
        "type": "other",
        "url": "https://hirist.tech"
      }
    ]
  },
  "rejected": false,
  "rejection_reason": null,
  "run_id": "e3cc2eb5-c066-4a6b-8329-e69fe536af3f",
  "stage3_signals": {
    "alias_found": false,
    "alias_match_roles": [],
    "kra_match_roles": [
      {
        "display_name": "Backend Developer",
        "kra_matches": [
          {
            "kra_text": "Investigates and resolves production incidents, API bugs, and service degradation through root cause analysis, hotfixes, and post-mortems.",
            "sentence": "Investigate, troubleshoot, and resolve complex issues in production and development environments.",
            "similarity": 0.7323
          },
          {
            "kra_text": "Investigates and resolves production incidents, API bugs, and service degradation through root cause analysis, hotfixes, and post-mortems.",
            "sentence": "Contribute to incident management and root cause analysis to improve system reliability.",
            "similarity": 0.6451
          },
          {
            "kra_text": "Identifies and resolves backend performance bottlenecks through query optimization, indexing strategies, connection pooling, and distributed caching with Redis.",
            "sentence": "Analyse and identify opportunities for performance improvements and scalability.",
            "similarity": 0.5696
          }
        ],
        "matched_count": null,
        "matched_skills": null,
        "role_id": 1,
        "score": 0.649,
        "slug": "backend-engineer",
        "total_count": null
      },
      {
        "display_name": "React Native Developer",
        "kra_matches": [
          {
            "kra_text": "maintain code quality",
            "sentence": "Conduct thorough code reviews to ensure code quality, maintainability, and adherence to best practices.",
            "similarity": 0.7531
          },
          {
            "kra_text": "maintain code quality",
            "sentence": "Design, implement, and optimize clean, scalable, and reliable code across systems.",
            "similarity": 0.5824
          },
          {
            "kra_text": "maintain code quality",
            "sentence": "Propose and implement improvements to existing codebases, tools, and development.",
            "similarity": 0.5282
          }
        ],
        "matched_count": null,
        "matched_skills": null,
        "role_id": 73,
        "score": 0.6212,
        "slug": "react-native-developer",
        "total_count": null
      },
      {
        "display_name": "Flutter Developer",
        "kra_matches": [
          {
            "kra_text": "collaborate with design, product, and backend teams",
            "sentence": "Collaborate design and enhance system architecture.",
            "similarity": 0.6726
          },
          {
            "kra_text": "collaborate with design, product, and backend teams",
            "sentence": "Collaborate with Carbon Science, Designer, and other stakeholders to translate requirements into technical solutions.",
            "similarity": 0.585
          },
          {
            "kra_text": "optimize responsiveness and performance",
            "sentence": "Analyse and identify opportunities for performance improvements and scalability.",
            "similarity": 0.5634
          }
        ],
        "matched_count": null,
        "matched_skills": null,
        "role_id": 74,
        "score": 0.607,
        "slug": "flutter-developer",
        "total_count": null
      },
      {
        "display_name": "Angular Frontend Developer",
        "kra_matches": [
          {
            "kra_text": "code review and refactoring",
            "sentence": "Conduct thorough code reviews to ensure code quality, maintainability, and adherence to best practices.",
            "similarity": 0.6218
          },
          {
            "kra_text": "collaboration with design and QA",
            "sentence": "Collaborate design and enhance system architecture.",
            "similarity": 0.6013
          },
          {
            "kra_text": "code review and refactoring",
            "sentence": "Propose and implement improvements to existing codebases, tools, and development.",
            "similarity": 0.5704
          }
        ],
        "matched_count": null,
        "matched_skills": null,
        "role_id": 90,
        "score": 0.5978,
        "slug": "angular-frontend-developer",
        "total_count": null
      },
      {
        "display_name": "Node.js Backend Developer",
        "kra_matches": [
          {
            "kra_text": "code review and refactoring",
            "sentence": "Conduct thorough code reviews to ensure code quality, maintainability, and adherence to best practices.",
            "similarity": 0.6218
          },
          {
            "kra_text": "code review and refactoring",
            "sentence": "Propose and implement improvements to existing codebases, tools, and development.",
            "similarity": 0.5704
          },
          {
            "kra_text": "code review and refactoring",
            "sentence": "Design, implement, and optimize clean, scalable, and reliable code across systems.",
            "similarity": 0.538
          }
        ],
        "matched_count": null,
        "matched_skills": null,
        "role_id": 82,
        "score": 0.5767,
        "slug": "node-backend-developer",
        "total_count": null
      }
    ],
    "skill_match_roles": [
      {
        "display_name": "Engineering Manager",
        "kra_matches": null,
        "matched_count": 2,
        "matched_skills": [
          "Agile",
          "Scrum"
        ],
        "role_id": 121,
        "score": 0.6667,
        "slug": "engineering-manager",
        "total_count": 3
      },
      {
        "display_name": "Backend Developer",
        "kra_matches": null,
        "matched_count": 1,
        "matched_skills": [
          "microservices"
        ],
        "role_id": 1,
        "score": 0.3333,
        "slug": "backend-engineer",
        "total_count": 3
      },
      {
        "display_name": "Node.js Backend Developer",
        "kra_matches": null,
        "matched_count": 1,
        "matched_skills": [
          "microservices"
        ],
        "role_id": 82,
        "score": 0.3333,
        "slug": "node-backend-developer",
        "total_count": 3
      },
      {
        "display_name": "Scala Backend Developer",
        "kra_matches": null,
        "matched_count": 1,
        "matched_skills": [
          "microservices"
        ],
        "role_id": 87,
        "score": 0.3333,
        "slug": "scala-backend-developer",
        "total_count": 3
      }
    ]
  },
  "stage4_decision": {
    "alias_collision_detected": false,
    "case": "DOMAIN",
    "chosen_role": {
      "display_name": "Fullstack Developer",
      "kra_matches": null,
      "matched_count": null,
      "matched_skills": null,
      "role_id": 15,
      "score": 0.86,
      "slug": "full-stack-engineer",
      "total_count": null
    },
    "confidence": 0.86,
    "is_new_role": false,
    "llm2_fired": false,
    "llm2_reasoning": null,
    "matched_dimensions": [
      "Software Engineering",
      "Full-Stack Development",
      "System Architecture",
      "Performance and Scalability",
      "Code Quality and Maintainability",
      "Production Support and Reliability",
      "Agile Team Collaboration",
      "Mentoring and Technical Leadership"
    ],
    "matched_kras": [
      "Design, implement, and optimize clean, scalable, and reliable code",
      "Contribute to the development of microservices, APIs, or UI components",
      "Collaborate design and enhance system architecture",
      "Analyse and identify opportunities for performance improvements and scalability",
      "Conduct thorough code reviews",
      "Mentor and support junior developers",
      "Investigate, troubleshoot, and resolve complex issues",
      "Contribute to incident management and root cause analysis",
      "Propose and implement improvements to existing codebases"
    ],
    "matched_skills": [
      "microservices",
      "APIs",
      "UI components",
      "system architecture",
      "code reviews",
      "Agile/Scrum",
      "sprint planning",
      "daily stand-ups",
      "retrospectives",
      "root cause analysis"
    ],
    "new_role_display_name": null,
    "new_role_slug": null,
    "queued": false,
    "reasoning": "Domain=Software Engineering; The JD describes a general software engineer working across microservices, APIs, UI components, architecture, code quality, troubleshooting, and Agile collaboration, which best matches a full-stack engineering role.",
    "sub_role": null
  },
  "stage5_updates": {
    "centroid_n_after": 554,
    "centroid_updated": true,
    "collision_log_id": null,
    "new_kra_attached": {
      "best_kra_similarity": 0.0,
      "queue_id": 1201,
      "r_and_r_preview": "\u2022 Design, implement, and optimize clean, scalable, and reliable code across systems.\n\u2022 Contribute to the development of microservices, APIs, or UI components as per the project requirements.\n\u2022 Collabo",
      "role_display_name": "Fullstack Developer",
      "role_slug": "full-stack-engineer",
      "status": "pending"
    },
    "new_skills_attached": [],
    "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": 178,
      "existing_alias_text": "microservices",
      "input_term": "Microservices",
      "matched_canonical": {
        "category_id": 1,
        "display_name": "microservices",
        "id": 41,
        "is_also_category": false,
        "is_extractable": true,
        "skill_nature": "PATTERN",
        "slug": "microservices",
        "sub_category_id": 1,
        "typical_lifespan": "EVERGREEN",
        "volatility": "STABLE"
      },
      "matched_via": "alias"
    },
    {
      "alias_persist_skipped_reason": "alias_text already exists for this canonical skill",
      "alias_persisted": false,
      "existing_alias_id": 868,
      "existing_alias_text": "Agile",
      "input_term": "Agile",
      "matched_canonical": {
        "category_id": 8,
        "display_name": "Agile",
        "id": 520,
        "is_also_category": false,
        "is_extractable": true,
        "skill_nature": "METHODOLOGY",
        "slug": "agile",
        "sub_category_id": 3594,
        "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": 1851,
      "existing_alias_text": "Scrum",
      "input_term": "Scrum",
      "matched_canonical": {
        "category_id": 8,
        "display_name": "Scrum",
        "id": 1215,
        "is_also_category": false,
        "is_extractable": true,
        "skill_nature": "METHODOLOGY",
        "slug": "scrum",
        "sub_category_id": 3627,
        "typical_lifespan": "EVERGREEN",
        "volatility": "STABLE"
      },
      "matched_via": "alias"
    }
  ],
  "candidate_roles": [
    {
      "display_name": "Backend Developer",
      "id": 1,
      "rationale": null,
      "role_archetype": "A Backend Engineer designs, builds, and maintains the server-side logic and data handling that power applications and services. They focus on implementing reliable business functionality, integrating with other systems, and ensuring the backend is scalable, maintainable, and observable.",
      "slug": "backend-engineer",
      "source": "db"
    },
    {
      "display_name": "Node.js Backend Developer",
      "id": 82,
      "rationale": null,
      "role_archetype": "Engineering",
      "slug": "node-backend-developer",
      "source": "db"
    },
    {
      "display_name": "Scala Backend Developer",
      "id": 87,
      "rationale": null,
      "role_archetype": "Engineering",
      "slug": "scala-backend-developer",
      "source": "db"
    },
    {
      "display_name": "Engineering Manager",
      "id": 121,
      "rationale": null,
      "role_archetype": null,
      "slug": "engineering-manager",
      "source": "db"
    }
  ],
  "chosen_role": {
    "display_name": "Fullstack Developer",
    "id": 15,
    "rationale": "Domain=Software Engineering; The JD describes a general software engineer working across microservices, APIs, UI components, architecture, code quality, troubleshooting, and Agile collaboration, which best matches a full-stack engineering role.",
    "role_archetype": null,
    "slug": "full-stack-engineer",
    "source": "db"
  },
  "dimensions": [
    {
      "dimension": {
        "difficulty_hint": "well_known",
        "display_name": "Microservices and Distributed Systems",
        "id": 9,
        "rationale": "Architectural patterns for decomposed backend systems and the operational concerns they introduce. Covers service boundaries, consistency tradeoffs, retries, circuit breakers, and distributed coordination.",
        "slug": "microservices-and-distributed-systems",
        "source": "db"
      },
      "input_skill": "Microservices",
      "llm_role": null,
      "roles_from_db": [
        {
          "display_name": "Backend Developer",
          "id": 1,
          "rationale": null,
          "role_archetype": "A Backend Engineer designs, builds, and maintains the server-side logic and data handling that power applications and services. They focus on implementing reliable business functionality, integrating with other systems, and ensuring the backend is scalable, maintainable, and observable.",
          "slug": "backend-engineer",
          "source": "db"
        },
        {
          "display_name": "Node.js Backend Developer",
          "id": 82,
          "rationale": null,
          "role_archetype": "Engineering",
          "slug": "node-backend-developer",
          "source": "db"
        },
        {
          "display_name": "Scala Backend Developer",
          "id": 87,
          "rationale": null,
          "role_archetype": "Engineering",
          "slug": "scala-backend-developer",
          "source": "db"
        }
      ]
    },
    {
      "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": "Agile",
      "llm_role": null,
      "roles_from_db": []
    },
    {
      "dimension": {
        "difficulty_hint": "well_known",
        "display_name": "Software Concepts, Patterns \u0026 Practices",
        "id": 478,
        "rationale": "Champion foundational software design patterns, development methodologies, and engineering best practices.",
        "slug": "software-concepts-patterns-practices",
        "source": "db"
      },
      "input_skill": "Agile",
      "llm_role": null,
      "roles_from_db": [
        {
          "display_name": "Engineering Manager",
          "id": 121,
          "rationale": null,
          "role_archetype": null,
          "slug": "engineering-manager",
          "source": "db"
        }
      ]
    },
    {
      "dimension": {
        "difficulty_hint": "well_known",
        "display_name": "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": "Scrum",
      "llm_role": null,
      "roles_from_db": []
    },
    {
      "dimension": {
        "difficulty_hint": "well_known",
        "display_name": "Software Concepts, Patterns \u0026 Practices",
        "id": 478,
        "rationale": "Champion foundational software design patterns, development methodologies, and engineering best practices.",
        "slug": "software-concepts-patterns-practices",
        "source": "db"
      },
      "input_skill": "Scrum",
      "llm_role": null,
      "roles_from_db": [
        {
          "display_name": "Engineering Manager",
          "id": 121,
          "rationale": null,
          "role_archetype": null,
          "slug": "engineering-manager",
          "source": "db"
        }
      ]
    }
  ],
  "input_final_skills": [
    "Microservices",
    "Agile",
    "Scrum"
  ],
  "input_llm_skills": [
    "Microservices",
    "Agile",
    "Scrum"
  ],
  "new_aliases_persisted": 0,
  "run_id": "e3cc2eb5-c066-4a6b-8329-e69fe536af3f",
  "skills_detail": [
    {
      "aliases_in_db": [
        {
          "alias_text": "microservices",
          "alias_type": "CANONICAL",
          "id": 178,
          "is_primary": true,
          "match_strategy": "CASE_INSENSITIVE"
        }
      ],
      "canonical": {
        "category_id": 1,
        "display_name": "microservices",
        "id": 41,
        "is_also_category": false,
        "is_extractable": true,
        "skill_nature": "PATTERN",
        "slug": "microservices",
        "sub_category_id": 1,
        "typical_lifespan": "EVERGREEN",
        "volatility": "STABLE"
      },
      "dimensions": [
        {
          "dimension": {
            "difficulty_hint": "well_known",
            "display_name": "Microservices and Distributed Systems",
            "id": 9,
            "rationale": "Architectural patterns for decomposed backend systems and the operational concerns they introduce. Covers service boundaries, consistency tradeoffs, retries, circuit breakers, and distributed coordination.",
            "slug": "microservices-and-distributed-systems",
            "source": "db"
          },
          "input_skill": "Microservices",
          "llm_role": null,
          "roles_from_db": [
            {
              "display_name": "Backend Developer",
              "id": 1,
              "rationale": null,
              "role_archetype": "A Backend Engineer designs, builds, and maintains the server-side logic and data handling that power applications and services. They focus on implementing reliable business functionality, integrating with other systems, and ensuring the backend is scalable, maintainable, and observable.",
              "slug": "backend-engineer",
              "source": "db"
            },
            {
              "display_name": "Node.js Backend Developer",
              "id": 82,
              "rationale": null,
              "role_archetype": "Engineering",
              "slug": "node-backend-developer",
              "source": "db"
            },
            {
              "display_name": "Scala Backend Developer",
              "id": 87,
              "rationale": null,
              "role_archetype": "Engineering",
              "slug": "scala-backend-developer",
              "source": "db"
            }
          ]
        }
      ],
      "input_skill": "Microservices",
      "matched_via": "alias",
      "new_alias_persisted": false,
      "new_alias_text": null,
      "new_skill_meta": null,
      "source_tag": "db",
      "was_in_llm_skills": true
    },
    {
      "aliases_in_db": [
        {
          "alias_text": "Agile",
          "alias_type": "CANONICAL",
          "id": 868,
          "is_primary": true,
          "match_strategy": "CASE_INSENSITIVE"
        }
      ],
      "canonical": {
        "category_id": 8,
        "display_name": "Agile",
        "id": 520,
        "is_also_category": false,
        "is_extractable": true,
        "skill_nature": "METHODOLOGY",
        "slug": "agile",
        "sub_category_id": 3594,
        "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": "Agile",
          "llm_role": null,
          "roles_from_db": []
        },
        {
          "dimension": {
            "difficulty_hint": "well_known",
            "display_name": "Software Concepts, Patterns \u0026 Practices",
            "id": 478,
            "rationale": "Champion foundational software design patterns, development methodologies, and engineering best practices.",
            "slug": "software-concepts-patterns-practices",
            "source": "db"
          },
          "input_skill": "Agile",
          "llm_role": null,
          "roles_from_db": [
            {
              "display_name": "Engineering Manager",
              "id": 121,
              "rationale": null,
              "role_archetype": null,
              "slug": "engineering-manager",
              "source": "db"
            }
          ]
        }
      ],
      "input_skill": "Agile",
      "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": "Scrum",
          "alias_type": "CANONICAL",
          "id": 1851,
          "is_primary": true,
          "match_strategy": "CASE_INSENSITIVE"
        }
      ],
      "canonical": {
        "category_id": 8,
        "display_name": "Scrum",
        "id": 1215,
        "is_also_category": false,
        "is_extractable": true,
        "skill_nature": "METHODOLOGY",
        "slug": "scrum",
        "sub_category_id": 3627,
        "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": "Scrum",
          "llm_role": null,
          "roles_from_db": []
        },
        {
          "dimension": {
            "difficulty_hint": "well_known",
            "display_name": "Software Concepts, Patterns \u0026 Practices",
            "id": 478,
            "rationale": "Champion foundational software design patterns, development methodologies, and engineering best practices.",
            "slug": "software-concepts-patterns-practices",
            "source": "db"
          },
          "input_skill": "Scrum",
          "llm_role": null,
          "roles_from_db": [
            {
              "display_name": "Engineering Manager",
              "id": 121,
              "rationale": null,
              "role_archetype": null,
              "slug": "engineering-manager",
              "source": "db"
            }
          ]
        }
      ],
      "input_skill": "Scrum",
      "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": []
}
API 3 — final-role-output
{
  "chosen_role": {
    "display_name": "Fullstack Developer",
    "id": 15,
    "rationale": "Domain=Software Engineering; The JD describes a general software engineer working across microservices, APIs, UI components, architecture, code quality, troubleshooting, and Agile collaboration, which best matches a full-stack engineering role.",
    "role_archetype": null,
    "slug": "full-stack-engineer",
    "source": "db"
  },
  "chosen_role_resolution": "in_db",
  "final_input_skills": [
    {
      "skill": "Microservices",
      "tag": "in_db"
    },
    {
      "skill": "Agile",
      "tag": "in_db"
    },
    {
      "skill": "Scrum",
      "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": 15,
        "dimension": {
          "difficulty_hint": "well_known",
          "display_name": "Microservices and Distributed Systems",
          "id": 9,
          "rationale": "Architectural patterns for decomposed backend systems and the operational concerns they introduce. Covers service boundaries, consistency tradeoffs, retries, circuit breakers, and distributed coordination.",
          "slug": "microservices-and-distributed-systems",
          "source": "db"
        },
        "dimension_id": 9,
        "input_skill": "Microservices",
        "llm_role": null,
        "matched_chosen_role": false,
        "outcome_line": "Existing dimension (library) \u00b7 Role\u2194dimension skipped (dimension not under chosen role)",
        "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": "Node.js Backend Developer",
            "id": 82,
            "rationale": null,
            "role_archetype": "Engineering",
            "slug": "node-backend-developer",
            "source": "db"
          },
          {
            "display_name": "Scala Backend Developer",
            "id": 87,
            "rationale": null,
            "role_archetype": "Engineering",
            "slug": "scala-backend-developer",
            "source": "db"
          }
        ],
        "skill_dimension_saved": true,
        "skill_id": 41,
        "skill_tag": "in_db",
        "skipped_reason": null
      },
      {
        "chosen_role_id": 15,
        "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": "Agile",
        "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": 520,
        "skill_tag": "in_db",
        "skipped_reason": null
      },
      {
        "chosen_role_id": 15,
        "dimension": {
          "difficulty_hint": "well_known",
          "display_name": "Software Concepts, Patterns \u0026 Practices",
          "id": 478,
          "rationale": "Champion foundational software design patterns, development methodologies, and engineering best practices.",
          "slug": "software-concepts-patterns-practices",
          "source": "db"
        },
        "dimension_id": 478,
        "input_skill": "Agile",
        "llm_role": null,
        "matched_chosen_role": false,
        "outcome_line": "Existing dimension (library) \u00b7 Role\u2194dimension skipped (dimension not under chosen role)",
        "role_dimension_saved": false,
        "roles_from_db": [
          {
            "display_name": "Engineering Manager",
            "id": 121,
            "rationale": null,
            "role_archetype": null,
            "slug": "engineering-manager",
            "source": "db"
          }
        ],
        "skill_dimension_saved": true,
        "skill_id": 520,
        "skill_tag": "in_db",
        "skipped_reason": null
      },
      {
        "chosen_role_id": 15,
        "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": "Scrum",
        "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": 1215,
        "skill_tag": "in_db",
        "skipped_reason": null
      },
      {
        "chosen_role_id": 15,
        "dimension": {
          "difficulty_hint": "well_known",
          "display_name": "Software Concepts, Patterns \u0026 Practices",
          "id": 478,
          "rationale": "Champion foundational software design patterns, development methodologies, and engineering best practices.",
          "slug": "software-concepts-patterns-practices",
          "source": "db"
        },
        "dimension_id": 478,
        "input_skill": "Scrum",
        "llm_role": null,
        "matched_chosen_role": false,
        "outcome_line": "Existing dimension (library) \u00b7 Role\u2194dimension skipped (dimension not under chosen role)",
        "role_dimension_saved": false,
        "roles_from_db": [
          {
            "display_name": "Engineering Manager",
            "id": 121,
            "rationale": null,
            "role_archetype": null,
            "slug": "engineering-manager",
            "source": "db"
          }
        ],
        "skill_dimension_saved": true,
        "skill_id": 1215,
        "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": "e3cc2eb5-c066-4a6b-8329-e69fe536af3f"
}

LLM Calls

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

Loading…