Pipeline run
6697c94e-1108-4609-ab24-bb3717ce6d03
Client output enrichment
v2 Skill cluster · Nature of work · AI index · Tech stack maturity · Evidence · KRA descriptionvocab breakdown (legacy)
Signals
Post-classification
Captured for admin review
• Collaborate with cross-functional teams to develop, test, and deploy web applications using modern technologies. • Design and implement front-end interfaces with a focus on responsive design and imp…
1 POST /skills/extract-from-jd
2 POST /skills/extract-details
3 POST /skills/final-role-output
Fullstack Developer
domain · Software Engineering CASE DOMAINslug: full-stack-engineer · id: 15 · source: db
Domain=Software Engineering; The JD describes end-to-end web application work spanning front-end interfaces, back-end systems, APIs, testing, deployment, and code optimization, which best fits a full stack role.
Matched skills
Matched dimensions
Matched KRAs
Resolution:
in_db
— role exists in library; skill↔dim and role↔dim links saved when applicable.
Job description
Skills: HTML/CSS, JavaScript, React, Node.js, Express.js, MongoDB, Git, Problem Solving, Job Overview We are seeking a dedicated Full Stack Developer Intern to join our team at TwiLearn. This is a remote internship for freshers, available in multiple locations including Bangalore, Hyderabad, Chennai, Noida, Gurgaon, Pune, and Mumbai. As a Full Stack Developer Intern, you will gain hands-on experience in building and maintaining dynamic web applications, working alongside our seasoned professionals. Qualifications And Skills • Proficiency in HTML/CSS (Mandatory skill) for designing and crafting web pages with an emphasis on visual aesthetics and user experience. • Strong command over JavaScript (Mandatory skill) to create interactive and dynamic web elements that enhance user engagement. • Experience with React (Mandatory skill) for building user interfaces and managing the view layer in web and mobile applications. • Familiarity with Node.js to build scalable server-side applications and efficiently handle asynchronous events. • Knowledge of Express.js for creating robust and secure RESTful APIs, enabling seamless communication with client applications. • Understanding of MongoDB, a NoSQL database, for storing and retrieving data seamlessly within a web application. • Experience with Git for version control, allowing collaborative development and efficient tracking of code changes. • Strong problem-solving skills to identify, analyze, and rectify issues promptly in a dynamic development environment. Roles And Responsibilities • Collaborate with cross-functional teams to develop, test, and deploy web applications using modern technologies. • Design and implement front-end interfaces with a focus on responsive design and improved user interaction. • Build and maintain scalable back-end systems, ensuring efficient data handling and processing. • Participate in code reviews and contribute to the optimization of existing codebases. • Assist in the integration of RESTful APIs to facilitate seamless communication between client and server components. • Conduct debugging and troubleshooting to resolve application issues encountered during development. • Stay updated with the latest industry trends and technologies, suggesting improvements to enhance product quality. • Contribute to documentation and report-writing to ensure clear communication of processes and solutions.
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": "TwiLearn",
"ctc": null,
"domain": {
"primary": {
"aliases": [],
"domain": "IT Services \u0026 Consulting"
},
"secondary": null
},
"education": [],
"experience": {
"max": null,
"min": null,
"raw": "internship for freshers"
},
"job_locations": [
{
"aliases": [
"Bengaluru"
],
"city": "Bangalore",
"country": "India",
"state": null,
"work_mode": "remote"
},
{
"aliases": [],
"city": "Hyderabad",
"country": "India",
"state": null,
"work_mode": "remote"
},
{
"aliases": [],
"city": "Chennai",
"country": "India",
"state": null,
"work_mode": "remote"
},
{
"aliases": [],
"city": "Noida",
"country": "India",
"state": null,
"work_mode": "remote"
},
{
"aliases": [
"Gurugram"
],
"city": "Gurgaon",
"country": "India",
"state": null,
"work_mode": "remote"
},
{
"aliases": [],
"city": "Pune",
"country": "India",
"state": null,
"work_mode": "remote"
},
{
"aliases": [],
"city": "Mumbai",
"country": "India",
"state": null,
"work_mode": "remote"
}
],
"role": "Full Stack Developer Intern",
"role_aliases": [
"Full Stack Intern",
"Software Development Intern",
"Web Developer Intern"
],
"role_archetype": "Engineering",
"roles_and_responsibilities": [
{
"bullet_count": 8,
"heading": "Roles And Responsibilities",
"heading_was_present": true,
"source_marker": {
"first_5_words": "\u2022 Collaborate with cross-functional teams",
"last_5_words": "communication of processes and solutions."
},
"text": "\u2022 Collaborate with cross-functional teams to develop, test, and deploy web applications using modern technologies.\n\u2022 Design and implement front-end interfaces with a focus on responsive design and improved user interaction.\n\u2022 Build and maintain scalable back-end systems, ensuring efficient data handling and processing.\n\u2022 Participate in code reviews and contribute to the optimization of existing codebases.\n\u2022 Assist in the integration of RESTful APIs to facilitate seamless communication between client and server components.\n\u2022 Conduct debugging and troubleshooting to resolve application issues encountered during development.\n\u2022 Stay updated with the latest industry trends and technologies, suggesting improvements to enhance product quality.\n\u2022 Contribute to documentation and report-writing to ensure clear communication of processes and solutions.",
"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 Developer Intern",
"rationale": null,
"role_aliases": [
"Full Stack Intern",
"Software Development Intern",
"Web Developer Intern"
],
"role_archetype": "Engineering",
"slug": ""
},
"nano_parsed": {
"JD_type": "pass",
"about_company": null,
"certifications": [],
"company_name": "TwiLearn",
"ctc": null,
"domain": {
"primary": {
"aliases": [],
"domain": "IT Services \u0026 Consulting"
},
"secondary": null
},
"education": [],
"experience": {
"max": null,
"min": null,
"raw": "internship for freshers"
},
"job_locations": [
{
"aliases": [
"Bengaluru"
],
"city": "Bangalore",
"country": "India",
"state": null,
"work_mode": "remote"
},
{
"aliases": [],
"city": "Hyderabad",
"country": "India",
"state": null,
"work_mode": "remote"
},
{
"aliases": [],
"city": "Chennai",
"country": "India",
"state": null,
"work_mode": "remote"
},
{
"aliases": [],
"city": "Noida",
"country": "India",
"state": null,
"work_mode": "remote"
},
{
"aliases": [
"Gurugram"
],
"city": "Gurgaon",
"country": "India",
"state": null,
"work_mode": "remote"
},
{
"aliases": [],
"city": "Pune",
"country": "India",
"state": null,
"work_mode": "remote"
},
{
"aliases": [],
"city": "Mumbai",
"country": "India",
"state": null,
"work_mode": "remote"
}
],
"role": "Full Stack Developer Intern",
"role_aliases": [
"Full Stack Intern",
"Software Development Intern",
"Web Developer Intern"
],
"role_archetype": "Engineering",
"roles_and_responsibilities": [
{
"bullet_count": 8,
"heading": "Roles And Responsibilities",
"heading_was_present": true,
"source_marker": {
"first_5_words": "\u2022 Collaborate with cross-functional teams",
"last_5_words": "communication of processes and solutions."
},
"text": "\u2022 Collaborate with cross-functional teams to develop, test, and deploy web applications using modern technologies.\n\u2022 Design and implement front-end interfaces with a focus on responsive design and improved user interaction.\n\u2022 Build and maintain scalable back-end systems, ensuring efficient data handling and processing.\n\u2022 Participate in code reviews and contribute to the optimization of existing codebases.\n\u2022 Assist in the integration of RESTful APIs to facilitate seamless communication between client and server components.\n\u2022 Conduct debugging and troubleshooting to resolve application issues encountered during development.\n\u2022 Stay updated with the latest industry trends and technologies, suggesting improvements to enhance product quality.\n\u2022 Contribute to documentation and report-writing to ensure clear communication of processes and solutions.",
"word_count": 108
}
],
"urls": []
},
"rejected": false,
"rejection_reason": null,
"run_id": "6697c94e-1108-4609-ab24-bb3717ce6d03",
"stage3_signals": {
"alias_found": false,
"alias_match_roles": [],
"kra_match_roles": [
{
"display_name": "Angular Frontend Developer",
"kra_matches": [
{
"kra_text": "code review and refactoring",
"sentence": "Participate in code reviews and contribute to the optimization of existing codebases.",
"similarity": 0.6009
},
{
"kra_text": "UI responsiveness and performance",
"sentence": "Design and implement front-end interfaces with a focus on responsive design and improved user interaction.",
"similarity": 0.5906
},
{
"kra_text": "backend endpoint integration",
"sentence": "Assist in the integration of RESTful APIs to facilitate seamless communication between client and server components.",
"similarity": 0.5295
}
],
"matched_count": null,
"matched_skills": null,
"role_id": 90,
"score": 0.5737,
"slug": "angular-frontend-developer",
"total_count": null
},
{
"display_name": "Frontend Developer",
"kra_matches": [
{
"kra_text": "Collaborates with UX designers to refine interaction details, animations, responsive breakpoints, and micro-interaction behavior.",
"sentence": "Design and implement front-end interfaces with a focus on responsive design and improved user interaction.",
"similarity": 0.6484
},
{
"kra_text": "Integrates frontend views with RESTful or GraphQL backend APIs, handling async data fetching, loading states, error boundaries, and cache invalidation.",
"sentence": "Assist in the integration of RESTful APIs to facilitate seamless communication between client and server components.",
"similarity": 0.5416
},
{
"kra_text": "Supports production releases by diagnosing cross-browser compatibility issues, investigating UI regressions, and resolving frontend performance degradation.",
"sentence": "Conduct debugging and troubleshooting to resolve application issues encountered during development.",
"similarity": 0.5298
}
],
"matched_count": null,
"matched_skills": null,
"role_id": 7,
"score": 0.5733,
"slug": "frontend-engineer",
"total_count": null
},
{
"display_name": "Flutter Developer",
"kra_matches": [
{
"kra_text": "collaborate with design, product, and backend teams",
"sentence": "Collaborate with cross-functional teams to develop, test, and deploy web applications using modern technologies.",
"similarity": 0.6084
},
{
"kra_text": "Implement user-facing screens and flows",
"sentence": "Design and implement front-end interfaces with a focus on responsive design and improved user interaction.",
"similarity": 0.5471
},
{
"kra_text": "integrate external APIs and data sources",
"sentence": "Assist in the integration of RESTful APIs to facilitate seamless communication between client and server components.",
"similarity": 0.5095
}
],
"matched_count": null,
"matched_skills": null,
"role_id": 74,
"score": 0.555,
"slug": "flutter-developer",
"total_count": null
},
{
"display_name": "Pega Developer",
"kra_matches": [
{
"kra_text": "user interaction design and refinement",
"sentence": "Design and implement front-end interfaces with a focus on responsive design and improved user interaction.",
"similarity": 0.6596
},
{
"kra_text": "defect troubleshooting and resolution",
"sentence": "Conduct debugging and troubleshooting to resolve application issues encountered during development.",
"similarity": 0.5708
},
{
"kra_text": "external system integration implementation",
"sentence": "Assist in the integration of RESTful APIs to facilitate seamless communication between client and server components.",
"similarity": 0.4335
}
],
"matched_count": null,
"matched_skills": null,
"role_id": 24,
"score": 0.5546,
"slug": "pega-developer",
"total_count": null
},
{
"display_name": "Backend Developer",
"kra_matches": [
{
"kra_text": "Integrates with third-party services, payment gateways, messaging queues like Kafka or RabbitMQ, and internal microservices via HTTP and event-driven patterns.",
"sentence": "Assist in the integration of RESTful APIs to facilitate seamless communication between client and server components.",
"similarity": 0.5611
},
{
"kra_text": "Investigates and resolves production incidents, API bugs, and service degradation through root cause analysis, hotfixes, and post-mortems.",
"sentence": "Conduct debugging and troubleshooting to resolve application issues encountered during development.",
"similarity": 0.5532
},
{
"kra_text": "Identifies and resolves backend performance bottlenecks through query optimization, indexing strategies, connection pooling, and distributed caching with Redis.",
"sentence": "Build and maintain scalable back-end systems, ensuring efficient data handling and processing.",
"similarity": 0.5421
}
],
"matched_count": null,
"matched_skills": null,
"role_id": 1,
"score": 0.5521,
"slug": "backend-engineer",
"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": "DOMAIN",
"chosen_role": {
"display_name": "Fullstack Developer",
"kra_matches": null,
"matched_count": null,
"matched_skills": null,
"role_id": 15,
"score": 0.96,
"slug": "full-stack-engineer",
"total_count": null
},
"confidence": 0.96,
"is_new_role": false,
"llm2_fired": false,
"llm2_reasoning": null,
"matched_dimensions": [
"Full-Stack Web Development",
"Frontend UI Implementation",
"Backend System Development",
"API Integration",
"Application Testing and Deployment",
"Code Quality and Optimization"
],
"matched_kras": [
"develop, test, and deploy web applications",
"design and implement front-end interfaces",
"build and maintain scalable back-end systems",
"participate in code reviews",
"optimize existing codebases",
"assist in the integration of RESTful APIs",
"conduct debugging and troubleshooting",
"contribute to documentation and report-writing"
],
"matched_skills": [
"web applications",
"responsive design",
"back-end systems",
"data handling",
"RESTful APIs",
"code reviews",
"debugging",
"troubleshooting",
"documentation"
],
"new_role_display_name": null,
"new_role_slug": null,
"queued": false,
"reasoning": "Domain=Software Engineering; The JD describes end-to-end web application work spanning front-end interfaces, back-end systems, APIs, testing, deployment, and code optimization, which best fits a full stack role.",
"sub_role": null
},
"stage5_updates": {
"centroid_n_after": 382,
"centroid_updated": true,
"collision_log_id": null,
"new_kra_attached": {
"best_kra_similarity": 0.0,
"queue_id": 865,
"r_and_r_preview": "\u2022 Collaborate with cross-functional teams to develop, test, and deploy web applications using modern technologies.\n\u2022 Design and implement front-end interfaces with a focus on responsive design and imp",
"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": 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": "Domain=Software Engineering; The JD describes end-to-end web application work spanning front-end interfaces, back-end systems, APIs, testing, deployment, and code optimization, which best fits a full stack role.",
"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": "6697c94e-1108-4609-ab24-bb3717ce6d03",
"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": "Domain=Software Engineering; The JD describes end-to-end web application work spanning front-end interfaces, back-end systems, APIs, testing, deployment, and code optimization, which best fits a full stack role.",
"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": "6697c94e-1108-4609-ab24-bb3717ce6d03"
}
LLM Calls
Every model call made for this run, in pipeline order. Click a card to see the model's response.