Pipeline run
04415d67-21ac-4f21-9cb9-6b2b58b7373a
Client output enrichment
v2 Skill cluster · Nature of work · AI index · Tech stack maturity · Evidence · KRA descriptionvocab breakdown (legacy)
Signals
Post-classification
1 POST /skills/extract-from-jd
2 POST /skills/extract-details
3 POST /skills/final-role-output
Fullstack Developer
CASE Aslug: full-stack-engineer · id: 15 · source: db
Exact alias hit on full-stack-engineer (1.0) — no other alias at this confidence; skill_top full-stack-engineer 1.00 does not contradict
Resolution:
in_db
— role exists in library; skill↔dim and role↔dim links saved when applicable.
Job description
Skills: nosql, javascript, Hyperledger, Kubernetes, Golang, React Native, Mobile Application Development, html, Job Description Job title: Full Stack Engineer Status: Work from home Notice Period: Immediate Job Summary The Full Stack Engineer performs a key function in our Product & Engineering team by having knowledge of all stages of software development and working alongside other software engineers & developer Job Objective The Full Stack Engineer is responsible for collaborating closely with the Chief Product Officer & Chief Technology Officer. Required Skills • must have 5+ years of ecperience in Golang, React Native, mobile application development, CSS, JS, and HTML. • must having 3+ years with NoSQL data stores such as MongoDB. Good to have • Blockchain technology such as Microsoft CCF or Hyperledger & Kubernetes experience is highly desirable! • High English language proficiency • Good written and verbal communication for effective stakeholder communication • Great interpersonal, problem-solving, analytical and research skills • An understanding of well-known cryptographic processes • Must be familiar with critical software product concepts such as MVP Past Experience • Must have worked in a startup before. Educational Qualifications Qualifications from reputable institutions such as: • A degree in Computer Science or Information Technology with a focus on Software Engineering • A diploma or bachelors degree majoring in Software Engineering or Information Technology Roles & Responsibilities • Develop high quality code across the system components including front-end, back-end and database • Stay current and provide insight on cutting edge software approaches, architectures and vendors • Ensure requirements such as data security, performance, maintainability, scalability, usability and reliability are always considered • Develop and design RESTful services and APIs • Develop and maintain project delivery and technical systems documentation • Develop and execute unit and system tests • Keep job knowledge up to date by studying new development tools and programming techniques • Support the delivery of projects within the work program including project reporting • Support the engagement process with the Chief Product Officer in gathering requirements and contribute to improved project delivery • Undertake engineering maintenance and enhancements
Skills from this JD
Each row merges API 1 extraction, API 2 library match / v3 orchestration (dimensions + locked dims), and API 3 persistence tags.
Aliases — catalog
- REST (CANONICAL) primary
Context tags (catalog)
Stored enrichment (catalog DB)
- Category
- Concept
- Sub-category
- Api Architecture Style
- Year introduced
- 2000
- Confidence
- 0.88
- Version strategy
- NOT_APPLICABLE
Maturity reasoning: REST is a default API architecture in many job descriptions and is widely supported by major vendors/frameworks; OpenAPI and RESTful endpoints remain standard in hiring pipelines.
Skill profile (library / DB)
- Skill nature
- CONCEPT
- Volatility
- STABLE
- Typical lifespan
- EVERGREEN
- Category id
- 2
- Sub-category id
- 2122
- Extractable
- True
- Also category
- False
Dimensions (API 2 worklist)
-
API Design and Contracts Catalog dimension db id 3
Library dimension (catalog)
Roles linked in library: Backend Developer, Fullstack Developer
-
API Interface and Contract Design Catalog dimension db id 289
Library dimension (catalog)
Roles linked in library: .NET Backend Developer, Go Backend Developer, Kotlin Backend Developer, Node.js Backend Developer, PHP Backend Developer, Python Backend Developer, Ruby Backend Developer, Scala Backend Developer
-
Integration Protocols & Standards Catalog dimension db id 271
Library dimension (catalog)
Roles linked in library: Pega Developer
-
Standards, Protocols & Compliance Catalog dimension db id 452
Library dimension (catalog)
Roles linked in library: Engineering Manager, Sitecore Dev
API 3 link attempts (this skill)
| Dimension | Skill↔dim | Role↔dim | Outcome |
|---|---|---|---|
|
API Design and Contracts
api-design-and-contracts
|
✓ | ✓ | Existing dimension (library) · Role↔dimension saved |
|
API Interface and Contract Design
api-interface-and-contract-design
|
✓ | — | Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role) |
|
Integration Protocols & Standards
integration-protocols-standards
|
✓ | — | Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role) |
|
Standards, Protocols & Compliance
standards-protocols-compliance
|
✓ | — | 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 |
|---|---|---|---|---|---|---|
| REST | in_db |
API Design and Contracts
api-design-and-contracts
|
✓ | ✓ | Existing dimension (library) · Role↔dimension saved | |
| REST | in_db |
API Interface and Contract Design
api-interface-and-contract-design
|
✓ | — | Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role) | |
| REST | in_db |
Integration Protocols & Standards
integration-protocols-standards
|
✓ | — | Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role) | |
| REST | in_db |
Standards, Protocols & Compliance
standards-protocols-compliance
|
✓ | — | Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role) |
Library artifacts (this run)
nano JD Parser — gpt-4.1-nano click to toggle
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 related)",
"raw": "A degree in Computer Science or Information Technology with a focus on Software Engineering",
"requirement": "required"
},
{
"level": "Bachelor\u0027s",
"qualification": "BTECH/BE - Software Engineering (or related)",
"raw": "A diploma or bachelors degree majoring in Software Engineering or Information Technology",
"requirement": "preferred"
}
],
"experience": {
"max": null,
"min": 5,
"raw": "5+ years of experience"
},
"job_locations": [
{
"aliases": [],
"city": null,
"country": null,
"state": null,
"work_mode": "remote"
}
],
"role": "Full Stack Engineer",
"role_aliases": [
"Full Stack Developer",
"Software Engineer",
"SWE"
],
"role_archetype": "Engineering",
"roles_and_responsibilities": [
{
"bullet_count": 10,
"heading": "Roles \u0026 Responsibilities",
"heading_was_present": true,
"source_marker": {
"first_5_words": "\u2022 Develop high quality code",
"last_5_words": "engineering maintenance and enhancements"
},
"text": "\u2022 Develop high quality code across the system components including front-end, back-end and database\n\u2022 Stay current and provide insight on cutting edge software approaches, architectures and vendors\n\u2022 Ensure requirements such as data security, performance, maintainability, scalability, usability and reliability are always considered\n\u2022 Develop and design RESTful services and APIs\n\u2022 Develop and maintain project delivery and technical systems documentation\n\u2022 Develop and execute unit and system tests\n\u2022 Keep job knowledge up to date by studying new development tools and programming techniques\n\u2022 Support the delivery of projects within the work program including project reporting\n\u2022 Support the engagement process with the Chief Product Officer in gathering requirements and contribute to improved project delivery\n\u2022 Undertake engineering maintenance and enhancements",
"word_count": 108
}
],
"urls": []
}
API 1 — extract-from-jd click to toggle
{
"final_skills": [
{
"is_primary": true,
"skill_name": "REST"
}
],
"jd_role": {
"display_name": "Full Stack Engineer",
"rationale": null,
"role_aliases": [
"Full Stack Developer",
"Software Engineer",
"SWE"
],
"role_archetype": "Engineering",
"slug": ""
},
"nano_parsed": {
"JD_type": "pass",
"about_company": null,
"certifications": [],
"company_name": null,
"ctc": null,
"domain": {
"primary": {
"aliases": [],
"domain": "Other"
},
"secondary": null
},
"education": [
{
"level": "Bachelor\u0027s",
"qualification": "BTECH/BE - Computer Science (or related)",
"raw": "A degree in Computer Science or Information Technology with a focus on Software Engineering",
"requirement": "required"
},
{
"level": "Bachelor\u0027s",
"qualification": "BTECH/BE - Software Engineering (or related)",
"raw": "A diploma or bachelors degree majoring in Software Engineering or Information Technology",
"requirement": "preferred"
}
],
"experience": {
"max": null,
"min": 5,
"raw": "5+ years of experience"
},
"job_locations": [
{
"aliases": [],
"city": null,
"country": null,
"state": null,
"work_mode": "remote"
}
],
"role": "Full Stack Engineer",
"role_aliases": [
"Full Stack Developer",
"Software Engineer",
"SWE"
],
"role_archetype": "Engineering",
"roles_and_responsibilities": [
{
"bullet_count": 10,
"heading": "Roles \u0026 Responsibilities",
"heading_was_present": true,
"source_marker": {
"first_5_words": "\u2022 Develop high quality code",
"last_5_words": "engineering maintenance and enhancements"
},
"text": "\u2022 Develop high quality code across the system components including front-end, back-end and database\n\u2022 Stay current and provide insight on cutting edge software approaches, architectures and vendors\n\u2022 Ensure requirements such as data security, performance, maintainability, scalability, usability and reliability are always considered\n\u2022 Develop and design RESTful services and APIs\n\u2022 Develop and maintain project delivery and technical systems documentation\n\u2022 Develop and execute unit and system tests\n\u2022 Keep job knowledge up to date by studying new development tools and programming techniques\n\u2022 Support the delivery of projects within the work program including project reporting\n\u2022 Support the engagement process with the Chief Product Officer in gathering requirements and contribute to improved project delivery\n\u2022 Undertake engineering maintenance and enhancements",
"word_count": 108
}
],
"urls": []
},
"rejected": false,
"rejection_reason": null,
"run_id": "04415d67-21ac-4f21-9cb9-6b2b58b7373a",
"stage3_signals": {
"alias_found": true,
"alias_match_roles": [
{
"display_name": "Fullstack Developer",
"kra_matches": null,
"matched_count": null,
"matched_skills": null,
"role_id": 15,
"score": 1.0,
"slug": "full-stack-engineer",
"total_count": null
}
],
"kra_match_roles": [
{
"display_name": "Python Backend Developer",
"kra_matches": [
{
"kra_text": "Write backend-focused automated checks",
"sentence": "Develop and execute unit and system tests",
"similarity": 0.5626
},
{
"kra_text": "Design backend endpoints and request handling",
"sentence": "Develop high quality code across the system components including front-end, back-end and database",
"similarity": 0.5259
},
{
"kra_text": "Design backend endpoints and request handling",
"sentence": "Develop and design RESTful services and APIs",
"similarity": 0.5069
}
],
"matched_count": null,
"matched_skills": null,
"role_id": 80,
"score": 0.5318,
"slug": "python-backend-developer",
"total_count": null
},
{
"display_name": "React Native Developer",
"kra_matches": [
{
"kra_text": "maintain code quality",
"sentence": "Develop high quality code across the system components including front-end, back-end and database",
"similarity": 0.5912
},
{
"kra_text": "integrate backend APIs",
"sentence": "Develop and design RESTful services and APIs",
"similarity": 0.508
},
{
"kra_text": "maintain code quality",
"sentence": "Ensure requirements such as data security, performance, maintainability, scalability, usability and reliability are always considered",
"similarity": 0.4959
}
],
"matched_count": null,
"matched_skills": null,
"role_id": 73,
"score": 0.5317,
"slug": "react-native-developer",
"total_count": null
},
{
"display_name": "Flutter Developer",
"kra_matches": [
{
"kra_text": "collaborate with design, product, and backend teams",
"sentence": "Develop high quality code across the system components including front-end, back-end and database",
"similarity": 0.5571
},
{
"kra_text": "collaborate with design, product, and backend teams",
"sentence": "Support the engagement process with the Chief Product Officer in gathering requirements and contribute to improved project delivery",
"similarity": 0.5196
},
{
"kra_text": "optimize responsiveness and performance",
"sentence": "Ensure requirements such as data security, performance, maintainability, scalability, usability and reliability are always considered",
"similarity": 0.5042
}
],
"matched_count": null,
"matched_skills": null,
"role_id": 74,
"score": 0.5269,
"slug": "flutter-developer",
"total_count": null
},
{
"display_name": "Fullstack Developer",
"kra_matches": [
{
"kra_text": "Implements complete product features end-to-end from database schema design through backend API to frontend UI using JavaScript, TypeScript, Python, or Ruby on Rails.",
"sentence": "Develop high quality code across the system components including front-end, back-end and database",
"similarity": 0.5719
},
{
"kra_text": "Works closely with product managers and UX designers to translate requirements and wireframes into working software features through iterative development.",
"sentence": "Support the engagement process with the Chief Product Officer in gathering requirements and contribute to improved project delivery",
"similarity": 0.543
},
{
"kra_text": "Implements complete product features end-to-end from database schema design through backend API to frontend UI using JavaScript, TypeScript, Python, or Ruby on Rails.",
"sentence": "Develop and design RESTful services and APIs",
"similarity": 0.4593
}
],
"matched_count": null,
"matched_skills": null,
"role_id": 15,
"score": 0.5247,
"slug": "full-stack-engineer",
"total_count": null
},
{
"display_name": ".NET Backend Developer",
"kra_matches": [
{
"kra_text": "backend code refactoring and maintenance",
"sentence": "Undertake engineering maintenance and enhancements",
"similarity": 0.5371
},
{
"kra_text": "service interface design and implementation",
"sentence": "Develop and design RESTful services and APIs",
"similarity": 0.515
},
{
"kra_text": "backend code refactoring and maintenance",
"sentence": "Develop high quality code across the system components including front-end, back-end and database",
"similarity": 0.5128
}
],
"matched_count": null,
"matched_skills": null,
"role_id": 83,
"score": 0.5216,
"slug": "dotnet-backend-developer",
"total_count": null
}
],
"skill_match_roles": [
{
"display_name": "Fullstack Developer",
"kra_matches": null,
"matched_count": 1,
"matched_skills": [
"REST"
],
"role_id": 15,
"score": 1.0,
"slug": "full-stack-engineer",
"total_count": 1
},
{
"display_name": "Pega Developer",
"kra_matches": null,
"matched_count": 1,
"matched_skills": [
"REST"
],
"role_id": 24,
"score": 1.0,
"slug": "pega-developer",
"total_count": 1
},
{
"display_name": "Python Backend Developer",
"kra_matches": null,
"matched_count": 1,
"matched_skills": [
"REST"
],
"role_id": 80,
"score": 1.0,
"slug": "python-backend-developer",
"total_count": 1
},
{
"display_name": "Go Backend Developer",
"kra_matches": null,
"matched_count": 1,
"matched_skills": [
"REST"
],
"role_id": 81,
"score": 1.0,
"slug": "go-backend-developer",
"total_count": 1
},
{
"display_name": "Backend Developer",
"kra_matches": null,
"matched_count": 1,
"matched_skills": [
"REST"
],
"role_id": 1,
"score": 1.0,
"slug": "backend-engineer",
"total_count": 1
}
]
},
"stage4_decision": {
"alias_collision_detected": false,
"case": "A",
"chosen_role": {
"display_name": "Fullstack Developer",
"kra_matches": null,
"matched_count": null,
"matched_skills": null,
"role_id": 15,
"score": 1.0,
"slug": "full-stack-engineer",
"total_count": null
},
"confidence": 1.0,
"is_new_role": false,
"llm2_fired": false,
"llm2_reasoning": null,
"matched_dimensions": [],
"matched_kras": [],
"matched_skills": [],
"new_role_display_name": null,
"new_role_slug": null,
"queued": false,
"reasoning": "Exact alias hit on full-stack-engineer (1.0) \u2014 no other alias at this confidence; skill_top full-stack-engineer 1.00 does not contradict",
"sub_role": null
},
"stage5_updates": {
"centroid_n_after": 388,
"centroid_updated": true,
"collision_log_id": null,
"new_kra_attached": null,
"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": 106,
"existing_alias_text": "REST",
"input_term": "REST",
"matched_canonical": {
"category_id": 2,
"display_name": "REST",
"id": 11,
"is_also_category": false,
"is_extractable": true,
"skill_nature": "CONCEPT",
"slug": "rest",
"sub_category_id": 2122,
"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": "Fullstack Developer",
"id": 15,
"rationale": null,
"role_archetype": null,
"slug": "full-stack-engineer",
"source": "db"
},
{
"display_name": ".NET Backend Developer",
"id": 83,
"rationale": null,
"role_archetype": "Engineering",
"slug": "dotnet-backend-developer",
"source": "db"
},
{
"display_name": "Go Backend Developer",
"id": 81,
"rationale": null,
"role_archetype": "Engineering",
"slug": "go-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": "Python Backend Developer",
"id": 80,
"rationale": null,
"role_archetype": "Engineering",
"slug": "python-backend-developer",
"source": "db"
},
{
"display_name": "Ruby Backend Developer",
"id": 85,
"rationale": null,
"role_archetype": "Engineering",
"slug": "ruby-backend-developer",
"source": "db"
},
{
"display_name": "Scala Backend Developer",
"id": 87,
"rationale": null,
"role_archetype": "Engineering",
"slug": "scala-backend-developer",
"source": "db"
},
{
"display_name": "Pega Developer",
"id": 24,
"rationale": null,
"role_archetype": null,
"slug": "pega-developer",
"source": "db"
},
{
"display_name": "Engineering Manager",
"id": 121,
"rationale": null,
"role_archetype": null,
"slug": "engineering-manager",
"source": "db"
},
{
"display_name": "Sitecore Dev",
"id": 233,
"rationale": null,
"role_archetype": "Engineering",
"slug": "sitecore-dev",
"source": "db"
}
],
"chosen_role": {
"display_name": "Fullstack Developer",
"id": 15,
"rationale": "Exact alias hit on full-stack-engineer (1.0) \u2014 no other alias at this confidence; skill_top full-stack-engineer 1.00 does not contradict",
"role_archetype": null,
"slug": "full-stack-engineer",
"source": "db"
},
"dimensions": [
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "API Design and Contracts",
"id": 3,
"rationale": "Designing request/response shapes and the rules that govern client-server interaction. This cluster is coherent because full stack engineers often own the contract between UI behavior and backend implementation.",
"slug": "api-design-and-contracts",
"source": "db"
},
"input_skill": "REST",
"llm_role": null,
"roles_from_db": [
{
"display_name": "Backend Developer",
"id": 1,
"rationale": null,
"role_archetype": "A Backend Engineer designs, builds, and maintains the server-side logic and data handling that power applications and services. They focus on implementing reliable business functionality, integrating with other systems, and ensuring the backend is scalable, maintainable, and observable.",
"slug": "backend-engineer",
"source": "db"
},
{
"display_name": "Fullstack Developer",
"id": 15,
"rationale": null,
"role_archetype": null,
"slug": "full-stack-engineer",
"source": "db"
}
]
},
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "API Interface and Contract Design",
"id": 289,
"rationale": "Designing backend service interfaces and contracts that other systems consume, including endpoint and operation shape, request/response payloads, schema and validation, pagination, filtering, idempotency, versioning, status codes, and backward compatibility across REST, GraphQL, gRPC, and OpenAPI-based APIs.",
"slug": "api-interface-and-contract-design",
"source": "db"
},
"input_skill": "REST",
"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": "Go Backend Developer",
"id": 81,
"rationale": null,
"role_archetype": "Engineering",
"slug": "go-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": "Python Backend Developer",
"id": 80,
"rationale": null,
"role_archetype": "Engineering",
"slug": "python-backend-developer",
"source": "db"
},
{
"display_name": "Ruby Backend Developer",
"id": 85,
"rationale": null,
"role_archetype": "Engineering",
"slug": "ruby-backend-developer",
"source": "db"
},
{
"display_name": "Scala Backend Developer",
"id": 87,
"rationale": null,
"role_archetype": "Engineering",
"slug": "scala-backend-developer",
"source": "db"
}
]
},
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Integration Protocols \u0026 Standards",
"id": 271,
"rationale": "Standards and protocols for integrating Pega applications.",
"slug": "integration-protocols-standards",
"source": "db"
},
"input_skill": "REST",
"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": "Standards, Protocols \u0026 Compliance",
"id": 452,
"rationale": "Ensure teams adhere to industry standards, security protocols, and regulatory compliance requirements.",
"slug": "standards-protocols-compliance",
"source": "db"
},
"input_skill": "REST",
"llm_role": null,
"roles_from_db": [
{
"display_name": "Engineering Manager",
"id": 121,
"rationale": null,
"role_archetype": null,
"slug": "engineering-manager",
"source": "db"
},
{
"display_name": "Sitecore Dev",
"id": 233,
"rationale": null,
"role_archetype": "Engineering",
"slug": "sitecore-dev",
"source": "db"
}
]
}
],
"input_final_skills": [
"REST"
],
"input_llm_skills": [
"REST"
],
"new_aliases_persisted": 0,
"run_id": "04415d67-21ac-4f21-9cb9-6b2b58b7373a",
"skills_detail": [
{
"aliases_in_db": [
{
"alias_text": "REST",
"alias_type": "CANONICAL",
"id": 106,
"is_primary": true,
"match_strategy": "CASE_INSENSITIVE"
}
],
"canonical": {
"category_id": 2,
"display_name": "REST",
"id": 11,
"is_also_category": false,
"is_extractable": true,
"skill_nature": "CONCEPT",
"slug": "rest",
"sub_category_id": 2122,
"typical_lifespan": "EVERGREEN",
"volatility": "STABLE"
},
"dimensions": [
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "API Design and Contracts",
"id": 3,
"rationale": "Designing request/response shapes and the rules that govern client-server interaction. This cluster is coherent because full stack engineers often own the contract between UI behavior and backend implementation.",
"slug": "api-design-and-contracts",
"source": "db"
},
"input_skill": "REST",
"llm_role": null,
"roles_from_db": [
{
"display_name": "Backend Developer",
"id": 1,
"rationale": null,
"role_archetype": "A Backend Engineer designs, builds, and maintains the server-side logic and data handling that power applications and services. They focus on implementing reliable business functionality, integrating with other systems, and ensuring the backend is scalable, maintainable, and observable.",
"slug": "backend-engineer",
"source": "db"
},
{
"display_name": "Fullstack Developer",
"id": 15,
"rationale": null,
"role_archetype": null,
"slug": "full-stack-engineer",
"source": "db"
}
]
},
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "API Interface and Contract Design",
"id": 289,
"rationale": "Designing backend service interfaces and contracts that other systems consume, including endpoint and operation shape, request/response payloads, schema and validation, pagination, filtering, idempotency, versioning, status codes, and backward compatibility across REST, GraphQL, gRPC, and OpenAPI-based APIs.",
"slug": "api-interface-and-contract-design",
"source": "db"
},
"input_skill": "REST",
"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": "Go Backend Developer",
"id": 81,
"rationale": null,
"role_archetype": "Engineering",
"slug": "go-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": "Python Backend Developer",
"id": 80,
"rationale": null,
"role_archetype": "Engineering",
"slug": "python-backend-developer",
"source": "db"
},
{
"display_name": "Ruby Backend Developer",
"id": 85,
"rationale": null,
"role_archetype": "Engineering",
"slug": "ruby-backend-developer",
"source": "db"
},
{
"display_name": "Scala Backend Developer",
"id": 87,
"rationale": null,
"role_archetype": "Engineering",
"slug": "scala-backend-developer",
"source": "db"
}
]
},
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Integration Protocols \u0026 Standards",
"id": 271,
"rationale": "Standards and protocols for integrating Pega applications.",
"slug": "integration-protocols-standards",
"source": "db"
},
"input_skill": "REST",
"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": "Standards, Protocols \u0026 Compliance",
"id": 452,
"rationale": "Ensure teams adhere to industry standards, security protocols, and regulatory compliance requirements.",
"slug": "standards-protocols-compliance",
"source": "db"
},
"input_skill": "REST",
"llm_role": null,
"roles_from_db": [
{
"display_name": "Engineering Manager",
"id": 121,
"rationale": null,
"role_archetype": null,
"slug": "engineering-manager",
"source": "db"
},
{
"display_name": "Sitecore Dev",
"id": 233,
"rationale": null,
"role_archetype": "Engineering",
"slug": "sitecore-dev",
"source": "db"
}
]
}
],
"input_skill": "REST",
"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": "Exact alias hit on full-stack-engineer (1.0) \u2014 no other alias at this confidence; skill_top full-stack-engineer 1.00 does not contradict",
"role_archetype": null,
"slug": "full-stack-engineer",
"source": "db"
},
"chosen_role_resolution": "in_db",
"final_input_skills": [
{
"skill": "REST",
"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": "API Design and Contracts",
"id": 3,
"rationale": "Designing request/response shapes and the rules that govern client-server interaction. This cluster is coherent because full stack engineers often own the contract between UI behavior and backend implementation.",
"slug": "api-design-and-contracts",
"source": "db"
},
"dimension_id": 3,
"input_skill": "REST",
"llm_role": null,
"matched_chosen_role": true,
"outcome_line": "Existing dimension (library) \u00b7 Role\u2194dimension saved",
"role_dimension_saved": true,
"roles_from_db": [
{
"display_name": "Backend Developer",
"id": 1,
"rationale": null,
"role_archetype": "A Backend Engineer designs, builds, and maintains the server-side logic and data handling that power applications and services. They focus on implementing reliable business functionality, integrating with other systems, and ensuring the backend is scalable, maintainable, and observable.",
"slug": "backend-engineer",
"source": "db"
},
{
"display_name": "Fullstack Developer",
"id": 15,
"rationale": null,
"role_archetype": null,
"slug": "full-stack-engineer",
"source": "db"
}
],
"skill_dimension_saved": true,
"skill_id": 11,
"skill_tag": "in_db",
"skipped_reason": null
},
{
"chosen_role_id": 15,
"dimension": {
"difficulty_hint": "well_known",
"display_name": "API Interface and Contract Design",
"id": 289,
"rationale": "Designing backend service interfaces and contracts that other systems consume, including endpoint and operation shape, request/response payloads, schema and validation, pagination, filtering, idempotency, versioning, status codes, and backward compatibility across REST, GraphQL, gRPC, and OpenAPI-based APIs.",
"slug": "api-interface-and-contract-design",
"source": "db"
},
"dimension_id": 289,
"input_skill": "REST",
"llm_role": null,
"matched_chosen_role": false,
"outcome_line": "Existing dimension (library) \u00b7 Role\u2194dimension skipped (dimension not under chosen role)",
"role_dimension_saved": false,
"roles_from_db": [
{
"display_name": ".NET Backend Developer",
"id": 83,
"rationale": null,
"role_archetype": "Engineering",
"slug": "dotnet-backend-developer",
"source": "db"
},
{
"display_name": "Go Backend Developer",
"id": 81,
"rationale": null,
"role_archetype": "Engineering",
"slug": "go-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": "Python Backend Developer",
"id": 80,
"rationale": null,
"role_archetype": "Engineering",
"slug": "python-backend-developer",
"source": "db"
},
{
"display_name": "Ruby Backend Developer",
"id": 85,
"rationale": null,
"role_archetype": "Engineering",
"slug": "ruby-backend-developer",
"source": "db"
},
{
"display_name": "Scala Backend Developer",
"id": 87,
"rationale": null,
"role_archetype": "Engineering",
"slug": "scala-backend-developer",
"source": "db"
}
],
"skill_dimension_saved": true,
"skill_id": 11,
"skill_tag": "in_db",
"skipped_reason": null
},
{
"chosen_role_id": 15,
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Integration Protocols \u0026 Standards",
"id": 271,
"rationale": "Standards and protocols for integrating Pega applications.",
"slug": "integration-protocols-standards",
"source": "db"
},
"dimension_id": 271,
"input_skill": "REST",
"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": 11,
"skill_tag": "in_db",
"skipped_reason": null
},
{
"chosen_role_id": 15,
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Standards, Protocols \u0026 Compliance",
"id": 452,
"rationale": "Ensure teams adhere to industry standards, security protocols, and regulatory compliance requirements.",
"slug": "standards-protocols-compliance",
"source": "db"
},
"dimension_id": 452,
"input_skill": "REST",
"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"
},
{
"display_name": "Sitecore Dev",
"id": 233,
"rationale": null,
"role_archetype": "Engineering",
"slug": "sitecore-dev",
"source": "db"
}
],
"skill_dimension_saved": true,
"skill_id": 11,
"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": "04415d67-21ac-4f21-9cb9-6b2b58b7373a"
}
LLM Calls
Every model call made for this run, in pipeline order. Click a card to see the model's response.