Pipeline run
34bc1c8d-ac29-42d1-bc19-0edf868f8315
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
• Review product design and suggest improvements from testability and user perspective • Design and deliver effective and automatable test plans. • Write test automation which can execute on large par…
1 POST /skills/extract-from-jd
2 POST /skills/extract-details
3 POST /skills/final-role-output
SDET
domain · Testing & Quality CASE DOMAINslug: sdet · id: 66 · source: db
Domain=Testing & Quality; The JD centers on test design, automation, code review, CI/CD execution, root cause analysis, and collaboration across product development, which aligns strongly with an SDET.
Matched skills
Matched dimensions
Matched KRAs
Resolution:
in_db
— role exists in library; skill↔dim and role↔dim links saved when applicable.
Job description
About Netskope Today, there's more data and users outside the enterprise than inside, causing the network perimeter as we know it to dissolve. We realized a new perimeter was needed, one that is built in the cloud and follows and protects data wherever it goes, so we started Netskope to redefine Cloud, Network and Data Security. Since 2012, we have built the market-leading cloud security company and an award-winning culture powered by hundreds of employees spread across offices in Santa Clara, St. Louis, Bangalore, London, Paris, Melbourne, Taipei, and Tokyo. Our core values are openness, honesty, and transparency, and we purposely developed our open desk layouts and large meeting spaces to support and promote partnerships, collaboration, and teamwork. From catered lunches and office celebrations to employee recognition events and social professional groups such as the Awesome Women of Netskope (AWON), we strive to keep work fun, supportive and interactive. Visit us at Netskope Careers. Please follow us on LinkedIn and Twitter@Netskope. About The Role Please note, this team is hiring across all levels and candidates are individually assessed and appropriately leveled based upon their skills and experience. Netskope Digital Rights Management (DRM) product line is a broad set of solutions that controls access and protection to digital content. This helps the security administrator with content classification, access control, content encryption, etc., ensuring enhanced Data Loss Prevention. These solutions empower security administrators with robust tools for content classification, granular access control, and advanced content encryption. By integrating these capabilities, Netskope DRM significantly enhances an organization's overall Data Loss Prevention (DLP) posture, ensuring sensitive information remains secure and compliant with regulatory requirements. What’s In It For You • Impactful Work: Contribute to a critical security product line that directly protects sensitive enterprise data. • Innovation: Work on cutting-edge technologies in digital rights management, encryption, and data lineage. • Career Growth: Opportunities for technical leadership and mentorship within a rapidly growing security company. • Collaborative Environment: Join a talented team of engineers passionate about solving complex security challenges. Key Responsibilities • Review product design and suggest improvements from testability and user perspective • Design and deliver effective and automatable test plans. • Write test automation which can execute on large parallelized CI/CD Infrastructure • Be an effective code reviewer for automation and product code. • Analyze and recommend the right tools for automation. • Simulate negative scenarios and perform chaos testing • Handle customer escalations, perform root cause analysis and drive customer issues to closure from QE perspective. • Work closely with the development team, product management and other stakeholders in various phases of product development to ensure alignment with strategy, planning, risks and mitigations. Required Skills And Experience • 7+ years of experience preferably a mix of SDET and product testing. • Strong expertise in programming languages like Python or Java (Python preferred). • Experience in designing test framework • Strong expertise in RESTful Web Service automation and Day-1 automation readiness. • Deep knowledge in containerization technologies like Docker, Kubernetes, and cloud platforms like AWS/GCP • System/server side experience for troubleshooting and strong knowledge of Linux. • Understanding of technologies like Redis, Kafka and NoSQL databases. • Good working experience in CI/CD tools like Jenkins, Spinnaker, Drone etc. • Should have worked on a cloud based product and have addressed reliability, resiliency and scale related problems • Working knowledge of git or other version controlling tools. Additional Skills • Eager to learn new products and technologies • Strong verbal and written communication skills. Able to communicate in an open, transparent and consistent manner with team and co-workers. • Determined and ever ready to roll up sleeves to respond to the needs of customers proactively and promptly. • Achievement oriented and willing to take responsibility for their own actions. • Believe in innovation and out-of-the box thinking to foster originality of ideas. Education • BSCS or equivalent required, MSCS or equivalent strongly preferred Netskope is committed to implementing equal employment opportunities for all employees and applicants for employment. Netskope does not discriminate in employment opportunities or practices based on religion, race, color, sex, marital or veteran statues, age, national origin, ancestry, physical or mental disability, medical condition, sexual orientation, gender identity/expression, genetic information, pregnancy (including childbirth, lactation and related medical conditions), or any other characteristic protected by the laws or regulations of any jurisdiction in which we operate. Netskope respects your privacy and is committed to protecting the personal information you share with us, please refer to Netskope's Privacy Policy for more details.
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
- CI/CD (CANONICAL)
Context tags (catalog)
Stored enrichment (catalog DB)
- Category
- Methodology
- Sub-category
- Ci Cd Process
- Confidence
- 0.93
- Version strategy
- NOT_APPLICABLE
Maturity reasoning: CI/CD appears in a large share of software engineering JDs and is a standard requirement across DevOps, platform, and backend roles; major vendors like GitHub, GitLab, and AWS all center product roadmaps on CI/CD pipelines.
Skill profile (library / DB)
- Skill nature
- METHODOLOGY
- Volatility
- STABLE
- Typical lifespan
- EVERGREEN
- Category id
- 8
- Sub-category id
- 900
- Extractable
- True
- Also category
- False
Dimensions (API 2 worklist)
-
CI/CD Pipeline Platforms Catalog dimension db id 150
Library dimension (catalog)
Roles linked in library: DevOps Engineer
-
CI/CD for Machine Learning Catalog dimension db id 56
Library dimension (catalog)
Roles linked in library: ML Engineer
API 3 link attempts (this skill)
| Dimension | Skill↔dim | Role↔dim | Outcome |
|---|---|---|---|
|
CI/CD Pipeline Platforms
ci-cd-pipeline-platforms
|
✓ | — | Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role) |
|
CI/CD for Machine Learning
ci-cd-for-machine-learning
|
✓ | — | Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role) |
Aliases — catalog
- Code Review (CANONICAL)
Context tags (catalog)
Stored enrichment (catalog DB)
- Category
- SoftSkill
- Sub-category
- Code Review
- Confidence
- 0.96
- Version strategy
- NOT_APPLICABLE
Maturity reasoning: Code review is a standard hiring-pipeline requirement in engineering JDs and is built into major platforms like GitHub/GitLab pull-request workflows, indicating broad adoption.
Skill profile (library / DB)
- Skill nature
- PRACTICE
- Volatility
- STABLE
- Typical lifespan
- EVERGREEN
- Category id
- 58
- Sub-category id
- 364
- Extractable
- True
- Also category
- False
Dimensions (API 2 worklist)
-
React Frontend Development Catalog dimension db id 96
Library dimension (catalog)
API 3 link attempts (this skill)
| Dimension | Skill↔dim | Role↔dim | Outcome |
|---|---|---|---|
|
React Frontend Development
d_init_01
|
✓ | — | Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role) |
Skill enrichment (orchestrator / LLM)
No Stage 7 enrichment blob on this skill (orchestrator skipped enrichment).
- Category
- Practices
- Sub-category
- general
- Skill nature
- PRACTICE
- Volatility
- MEDIUM
- Typical lifespan
- MULTI_YEAR
- Version strategy
- UNVERSIONED
Aliases — catalog
- root cause analysis (CANONICAL) primary
- root-cause analysis (CANONICAL)
Context tags (catalog)
Stored enrichment (catalog DB)
- Category
- Methodology
- Sub-category
- Root Cause Analysis Methodology
- Confidence
- 0.96
- Version strategy
- NOT_APPLICABLE
Maturity reasoning: Root cause analysis is a standard incident/postmortem skill in SRE, ITIL, and quality roles; it appears broadly in job descriptions for operations, QA, and manufacturing, not as a niche tool.
Skill profile (library / DB)
- Skill nature
- METHODOLOGY
- Volatility
- STABLE
- Typical lifespan
- EVERGREEN
- Category id
- 8
- Sub-category id
- 3301
- Extractable
- True
- Also category
- False
Dimensions (API 2 worklist)
-
Observability and Diagnostics Catalog dimension db id 287
Library dimension (catalog)
Roles linked in library: Go Backend Developer, Java Backend Developer, Python Backend Developer
-
Site Troubleshooting and Debugging Catalog dimension db id 353
Library dimension (catalog)
Roles linked in library: Drupal Dev
-
Sitecore Troubleshooting and Maintenance Catalog dimension db id 447
Library dimension (catalog)
Roles linked in library: Sitecore Dev
API 3 link attempts (this skill)
| Dimension | Skill↔dim | Role↔dim | Outcome |
|---|---|---|---|
|
Observability and Diagnostics
observability-and-diagnostics
|
✓ | — | Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role) |
|
Site Troubleshooting and Debugging
site-troubleshooting-and-debugging
|
✓ | — | Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role) |
|
Sitecore Troubleshooting and Maintenance
sitecore-troubleshooting-and-maintenance
|
✓ | — | 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 |
|---|---|---|---|---|---|---|
| CI/CD | in_db |
CI/CD Pipeline Platforms
ci-cd-pipeline-platforms
|
✓ | — | Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role) | |
| CI/CD | in_db |
CI/CD for Machine Learning
ci-cd-for-machine-learning
|
✓ | — | Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role) | |
| Code Review | in_db |
React Frontend Development
d_init_01
|
✓ | — | Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role) | |
| Root Cause Analysis | in_db |
Observability and Diagnostics
observability-and-diagnostics
|
✓ | — | Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role) | |
| Root Cause Analysis | in_db |
Site Troubleshooting and Debugging
site-troubleshooting-and-debugging
|
✓ | — | Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role) | |
| Root Cause Analysis | in_db |
Sitecore Troubleshooting and Maintenance
sitecore-troubleshooting-and-maintenance
|
✓ | — | Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role) |
Library artifacts (this run)
| Kind | Detail | DB id |
|---|---|---|
| canonical_skill_proposed | Chaos Testing | type=Practices subtype=general nature=PRACTICE lifespan=MULTI_YEAR |
nano JD Parser — gpt-4.1-nano click to toggle
Show raw JSON
{
"JD_type": "pass",
"about_company": {
"source_marker": {
"first_5_words": "Today, there\u0027s more data and",
"last_5_words": "fun, supportive and interactive."
},
"text": "Today, there\u0027s more data and users outside the enterprise than inside, causing the network perimeter as we know it to dissolve. We realized a new perimeter was needed, one that is built in the cloud and follows and protects data wherever it goes, so we started Netskope to redefine Cloud, Network and Data Security.\n\nSince 2012, we have built the market-leading cloud security company and an award-winning culture powered by hundreds of employees spread across offices in Santa Clara, St. Louis, Bangalore, London, Paris, Melbourne, Taipei, and Tokyo. Our core values are openness, honesty, and transparency, and we purposely developed our open desk layouts and large meeting spaces to support and promote partnerships, collaboration, and teamwork. From catered lunches and office celebrations to employee recognition events and social professional groups such as the Awesome Women of Netskope (AWON), we strive to keep work fun, supportive and interactive.",
"word_count": 139
},
"certifications": [],
"company_name": "Netskope",
"ctc": null,
"domain": {
"primary": {
"aliases": [
"Tech Consulting",
"Cloud Security"
],
"domain": "IT Services \u0026 Consulting"
},
"secondary": null
},
"education": [
{
"level": "Bachelor\u0027s",
"qualification": "BTECH/BE/BSC - Computer Science",
"raw": "BSCS or equivalent required",
"requirement": "required"
},
{
"level": "Master\u0027s",
"qualification": "MTECH/ME/MSC - Computer Science",
"raw": "MSCS or equivalent strongly preferred",
"requirement": "preferred"
}
],
"experience": {
"max": null,
"min": 7,
"raw": "7+ years of experience preferably a mix of SDET and product testing."
},
"job_locations": [
{
"aliases": [
"Silicon Valley"
],
"city": "Santa Clara",
"country": "United States",
"state": "California",
"work_mode": "null"
},
{
"aliases": [],
"city": "St. Louis",
"country": "United States",
"state": "Missouri",
"work_mode": "null"
},
{
"aliases": [
"Bengaluru"
],
"city": "Bangalore",
"country": "India",
"state": "Karnataka",
"work_mode": "null"
},
{
"aliases": [],
"city": "London",
"country": "United Kingdom",
"state": "England",
"work_mode": "null"
},
{
"aliases": [],
"city": "Paris",
"country": "France",
"state": "\u00cele-de-France",
"work_mode": "null"
},
{
"aliases": [],
"city": "Melbourne",
"country": "Australia",
"state": "Victoria",
"work_mode": "null"
},
{
"aliases": [],
"city": "Taipei",
"country": "Taiwan",
"state": "Taiwan",
"work_mode": "null"
},
{
"aliases": [],
"city": "Tokyo",
"country": "Japan",
"state": "Tokyo",
"work_mode": "null"
}
],
"role": "Software Development Engineer in Test (SDET)",
"role_aliases": [
"SDET",
"Test Engineer",
"Quality Engineer"
],
"role_archetype": "QA",
"roles_and_responsibilities": [
{
"bullet_count": 8,
"heading": "Key Responsibilities",
"heading_was_present": true,
"source_marker": {
"first_5_words": "\u2022 Review product design and",
"last_5_words": "strategy, planning, risks and mitigations."
},
"text": "\u2022 Review product design and suggest improvements from testability and user perspective\n\u2022 Design and deliver effective and automatable test plans.\n\u2022 Write test automation which can execute on large parallelized CI/CD Infrastructure\n\u2022 Be an effective code reviewer for automation and product code.\n\u2022 Analyze and recommend the right tools for automation.\n\u2022 Simulate negative scenarios and perform chaos testing\n\u2022 Handle customer escalations, perform root cause analysis and drive customer issues to closure from QE perspective.\n\u2022 Work closely with the development team, product management and other stakeholders in various phases of product development to ensure alignment with strategy, planning, risks and mitigations.",
"word_count": 104
}
],
"urls": [
{
"type": "careers",
"url": "https://www.netskope.com/careers"
},
{
"type": "linkedin",
"url": "https://www.linkedin.com/company/netskope"
},
{
"type": "twitter",
"url": "https://twitter.com/Netskope"
}
]
}
API 1 — extract-from-jd click to toggle
{
"final_skills": [
{
"is_primary": true,
"skill_name": "CI/CD"
},
{
"is_primary": true,
"skill_name": "Code Review"
},
{
"is_primary": true,
"skill_name": "Chaos Testing"
},
{
"is_primary": true,
"skill_name": "Root Cause Analysis"
}
],
"jd_role": {
"display_name": "Software Development Engineer in Test (SDET)",
"rationale": null,
"role_aliases": [
"SDET",
"Test Engineer",
"Quality Engineer"
],
"role_archetype": "QA",
"slug": ""
},
"nano_parsed": {
"JD_type": "pass",
"about_company": {
"source_marker": {
"first_5_words": "Today, there\u0027s more data and",
"last_5_words": "fun, supportive and interactive."
},
"text": "Today, there\u0027s more data and users outside the enterprise than inside, causing the network perimeter as we know it to dissolve. We realized a new perimeter was needed, one that is built in the cloud and follows and protects data wherever it goes, so we started Netskope to redefine Cloud, Network and Data Security.\n\nSince 2012, we have built the market-leading cloud security company and an award-winning culture powered by hundreds of employees spread across offices in Santa Clara, St. Louis, Bangalore, London, Paris, Melbourne, Taipei, and Tokyo. Our core values are openness, honesty, and transparency, and we purposely developed our open desk layouts and large meeting spaces to support and promote partnerships, collaboration, and teamwork. From catered lunches and office celebrations to employee recognition events and social professional groups such as the Awesome Women of Netskope (AWON), we strive to keep work fun, supportive and interactive.",
"word_count": 139
},
"certifications": [],
"company_name": "Netskope",
"ctc": null,
"domain": {
"primary": {
"aliases": [
"Tech Consulting",
"Cloud Security"
],
"domain": "IT Services \u0026 Consulting"
},
"secondary": null
},
"education": [
{
"level": "Bachelor\u0027s",
"qualification": "BTECH/BE/BSC - Computer Science",
"raw": "BSCS or equivalent required",
"requirement": "required"
},
{
"level": "Master\u0027s",
"qualification": "MTECH/ME/MSC - Computer Science",
"raw": "MSCS or equivalent strongly preferred",
"requirement": "preferred"
}
],
"experience": {
"max": null,
"min": 7,
"raw": "7+ years of experience preferably a mix of SDET and product testing."
},
"job_locations": [
{
"aliases": [
"Silicon Valley"
],
"city": "Santa Clara",
"country": "United States",
"state": "California",
"work_mode": "null"
},
{
"aliases": [],
"city": "St. Louis",
"country": "United States",
"state": "Missouri",
"work_mode": "null"
},
{
"aliases": [
"Bengaluru"
],
"city": "Bangalore",
"country": "India",
"state": "Karnataka",
"work_mode": "null"
},
{
"aliases": [],
"city": "London",
"country": "United Kingdom",
"state": "England",
"work_mode": "null"
},
{
"aliases": [],
"city": "Paris",
"country": "France",
"state": "\u00cele-de-France",
"work_mode": "null"
},
{
"aliases": [],
"city": "Melbourne",
"country": "Australia",
"state": "Victoria",
"work_mode": "null"
},
{
"aliases": [],
"city": "Taipei",
"country": "Taiwan",
"state": "Taiwan",
"work_mode": "null"
},
{
"aliases": [],
"city": "Tokyo",
"country": "Japan",
"state": "Tokyo",
"work_mode": "null"
}
],
"role": "Software Development Engineer in Test (SDET)",
"role_aliases": [
"SDET",
"Test Engineer",
"Quality Engineer"
],
"role_archetype": "QA",
"roles_and_responsibilities": [
{
"bullet_count": 8,
"heading": "Key Responsibilities",
"heading_was_present": true,
"source_marker": {
"first_5_words": "\u2022 Review product design and",
"last_5_words": "strategy, planning, risks and mitigations."
},
"text": "\u2022 Review product design and suggest improvements from testability and user perspective\n\u2022 Design and deliver effective and automatable test plans.\n\u2022 Write test automation which can execute on large parallelized CI/CD Infrastructure\n\u2022 Be an effective code reviewer for automation and product code.\n\u2022 Analyze and recommend the right tools for automation.\n\u2022 Simulate negative scenarios and perform chaos testing\n\u2022 Handle customer escalations, perform root cause analysis and drive customer issues to closure from QE perspective.\n\u2022 Work closely with the development team, product management and other stakeholders in various phases of product development to ensure alignment with strategy, planning, risks and mitigations.",
"word_count": 104
}
],
"urls": [
{
"type": "careers",
"url": "https://www.netskope.com/careers"
},
{
"type": "linkedin",
"url": "https://www.linkedin.com/company/netskope"
},
{
"type": "twitter",
"url": "https://twitter.com/Netskope"
}
]
},
"rejected": false,
"rejection_reason": null,
"run_id": "34bc1c8d-ac29-42d1-bc19-0edf868f8315",
"stage3_signals": {
"alias_found": true,
"alias_match_roles": [
{
"display_name": "SDET",
"kra_matches": null,
"matched_count": null,
"matched_skills": null,
"role_id": 66,
"score": 1.0,
"slug": "sdet",
"total_count": null
}
],
"kra_match_roles": [
{
"display_name": "Go Backend Developer",
"kra_matches": [
{
"kra_text": "code review and testing support",
"sentence": "Be an effective code reviewer for automation and product code.",
"similarity": 0.614
},
{
"kra_text": "code review and testing support",
"sentence": "Review product design and suggest improvements from testability and user perspective",
"similarity": 0.5324
},
{
"kra_text": "defect investigation and resolution",
"sentence": "Handle customer escalations, perform root cause analysis and drive customer issues to closure from QE perspective.",
"similarity": 0.4901
}
],
"matched_count": null,
"matched_skills": null,
"role_id": 81,
"score": 0.5455,
"slug": "go-backend-developer",
"total_count": null
},
{
"display_name": "Fullstack Developer",
"kra_matches": [
{
"kra_text": "Works closely with product managers and UX designers to translate requirements and wireframes into working software features through iterative development.",
"sentence": "Work closely with the development team, product management and other stakeholders in various phases of product development to ensure alignment with strategy, planning, risks and mitigations.",
"similarity": 0.6557
},
{
"kra_text": "Delivers features through CI/CD pipelines using automated tests, staged rollouts, feature flags, and incremental deployments.",
"sentence": "Write test automation which can execute on large parallelized CI/CD Infrastructure",
"similarity": 0.5016
},
{
"kra_text": "Works closely with product managers and UX designers to translate requirements and wireframes into working software features through iterative development.",
"sentence": "Review product design and suggest improvements from testability and user perspective",
"similarity": 0.478
}
],
"matched_count": null,
"matched_skills": null,
"role_id": 15,
"score": 0.5451,
"slug": "full-stack-engineer",
"total_count": null
},
{
"display_name": "Angular Frontend Developer",
"kra_matches": [
{
"kra_text": "code review and refactoring",
"sentence": "Be an effective code reviewer for automation and product code.",
"similarity": 0.5732
},
{
"kra_text": "collaboration with design and QA",
"sentence": "Review product design and suggest improvements from testability and user perspective",
"similarity": 0.561
},
{
"kra_text": "collaboration with design and QA",
"sentence": "Work closely with the development team, product management and other stakeholders in various phases of product development to ensure alignment with strategy, planning, risks and mitigations.",
"similarity": 0.5005
}
],
"matched_count": null,
"matched_skills": null,
"role_id": 90,
"score": 0.5449,
"slug": "angular-frontend-developer",
"total_count": null
},
{
"display_name": "Python Backend Developer",
"kra_matches": [
{
"kra_text": "Write backend-focused automated checks",
"sentence": "Write test automation which can execute on large parallelized CI/CD Infrastructure",
"similarity": 0.5657
},
{
"kra_text": "Write backend-focused automated checks",
"sentence": "Be an effective code reviewer for automation and product code.",
"similarity": 0.5486
},
{
"kra_text": "Write backend-focused automated checks",
"sentence": "Design and deliver effective and automatable test plans.",
"similarity": 0.4924
}
],
"matched_count": null,
"matched_skills": null,
"role_id": 80,
"score": 0.5356,
"slug": "python-backend-developer",
"total_count": null
},
{
"display_name": "Node.js Backend Developer",
"kra_matches": [
{
"kra_text": "code review and refactoring",
"sentence": "Be an effective code reviewer for automation and product code.",
"similarity": 0.5732
},
{
"kra_text": "code review and refactoring",
"sentence": "Review product design and suggest improvements from testability and user perspective",
"similarity": 0.5002
},
{
"kra_text": "automated backend checks",
"sentence": "Write test automation which can execute on large parallelized CI/CD Infrastructure",
"similarity": 0.4776
}
],
"matched_count": null,
"matched_skills": null,
"role_id": 82,
"score": 0.517,
"slug": "node-backend-developer",
"total_count": null
}
],
"skill_match_roles": [
{
"display_name": "ML Engineer",
"kra_matches": null,
"matched_count": 1,
"matched_skills": [
"CI/CD"
],
"role_id": 3,
"score": 0.25,
"slug": "ml-engineer",
"total_count": 4
},
{
"display_name": "DevOps Engineer",
"kra_matches": null,
"matched_count": 1,
"matched_skills": [
"CI/CD"
],
"role_id": 10,
"score": 0.25,
"slug": "devops-engineer",
"total_count": 4
},
{
"display_name": "Java Backend Developer",
"kra_matches": null,
"matched_count": 1,
"matched_skills": [
"root cause analysis"
],
"role_id": 79,
"score": 0.25,
"slug": "java-backend-developer",
"total_count": 4
},
{
"display_name": "Python Backend Developer",
"kra_matches": null,
"matched_count": 1,
"matched_skills": [
"root cause analysis"
],
"role_id": 80,
"score": 0.25,
"slug": "python-backend-developer",
"total_count": 4
},
{
"display_name": "Go Backend Developer",
"kra_matches": null,
"matched_count": 1,
"matched_skills": [
"root cause analysis"
],
"role_id": 81,
"score": 0.25,
"slug": "go-backend-developer",
"total_count": 4
}
]
},
"stage4_decision": {
"alias_collision_detected": false,
"case": "DOMAIN",
"chosen_role": {
"display_name": "SDET",
"kra_matches": null,
"matched_count": null,
"matched_skills": null,
"role_id": 66,
"score": 0.98,
"slug": "sdet",
"total_count": null
},
"confidence": 0.98,
"is_new_role": false,
"llm2_fired": false,
"llm2_reasoning": null,
"matched_dimensions": [
"Testability and quality review",
"Automated test strategy design",
"CI/CD test execution at scale",
"Automation tooling evaluation",
"Defect analysis and customer issue resolution",
"Cross-functional product collaboration"
],
"matched_kras": [
"Review product design and suggest improvements",
"Design and deliver effective and automatable test plans",
"Write test automation which can execute on large parallelized CI/CD Infrastructure",
"Be an effective code reviewer for automation and product code",
"Analyze and recommend the right tools for automation",
"Simulate negative scenarios and perform chaos testing",
"Handle customer escalations, perform root cause analysis",
"Drive customer issues to closure from QE perspective"
],
"matched_skills": [
"test automation",
"CI/CD Infrastructure",
"code reviewer",
"automation tools",
"chaos testing",
"root cause analysis"
],
"new_role_display_name": null,
"new_role_slug": null,
"queued": false,
"reasoning": "Domain=Testing \u0026 Quality; The JD centers on test design, automation, code review, CI/CD execution, root cause analysis, and collaboration across product development, which aligns strongly with an SDET.",
"sub_role": null
},
"stage5_updates": {
"centroid_n_after": 3,
"centroid_updated": true,
"collision_log_id": null,
"new_kra_attached": {
"best_kra_similarity": 0.0,
"queue_id": 203,
"r_and_r_preview": "\u2022 Review product design and suggest improvements from testability and user perspective\n\u2022 Design and deliver effective and automatable test plans.\n\u2022 Write test automation which can execute on large par",
"role_display_name": "SDET",
"role_slug": "sdet",
"status": "pending"
},
"new_skills_attached": [
{
"is_primary": true,
"queue_id": 4639,
"role_display_name": "SDET",
"role_slug": "sdet",
"skill_name": "Chaos Testing",
"status": "pending"
}
],
"queue_entry_id": null,
"v3_pipeline_triggered": false,
"v3_role_slug": null,
"v3_run_id": null
}
}
API 2 — extract-details
{
"alias_matches": [
{
"alias_persist_skipped_reason": "alias_text already exists for this canonical skill",
"alias_persisted": false,
"existing_alias_id": 1826,
"existing_alias_text": "CI/CD",
"input_term": "CI/CD",
"matched_canonical": {
"category_id": 8,
"display_name": "CI/CD",
"id": 1190,
"is_also_category": false,
"is_extractable": true,
"skill_nature": "METHODOLOGY",
"slug": "ci-cd",
"sub_category_id": 900,
"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": 864,
"existing_alias_text": "Code Review",
"input_term": "Code Review",
"matched_canonical": {
"category_id": 58,
"display_name": "Code Review",
"id": 516,
"is_also_category": false,
"is_extractable": true,
"skill_nature": "PRACTICE",
"slug": "code-review",
"sub_category_id": 364,
"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": 3688,
"existing_alias_text": "root cause analysis",
"input_term": "Root Cause Analysis",
"matched_canonical": {
"category_id": 8,
"display_name": "root cause analysis",
"id": 2392,
"is_also_category": false,
"is_extractable": true,
"skill_nature": "METHODOLOGY",
"slug": "root-cause-analysis",
"sub_category_id": 3301,
"typical_lifespan": "EVERGREEN",
"volatility": "STABLE"
},
"matched_via": "alias"
}
],
"candidate_roles": [
{
"display_name": "DevOps Engineer",
"id": 10,
"rationale": null,
"role_archetype": null,
"slug": "devops-engineer",
"source": "db"
},
{
"display_name": "ML Engineer",
"id": 3,
"rationale": null,
"role_archetype": null,
"slug": "ml-engineer",
"source": "db"
},
{
"display_name": "Go Backend Developer",
"id": 81,
"rationale": null,
"role_archetype": "Engineering",
"slug": "go-backend-developer",
"source": "db"
},
{
"display_name": "Java Backend Developer",
"id": 79,
"rationale": null,
"role_archetype": "Engineering",
"slug": "java-backend-developer",
"source": "db"
},
{
"display_name": "Python Backend Developer",
"id": 80,
"rationale": null,
"role_archetype": "Engineering",
"slug": "python-backend-developer",
"source": "db"
},
{
"display_name": "Drupal Dev",
"id": 228,
"rationale": null,
"role_archetype": "Engineering",
"slug": "drupal-dev",
"source": "db"
},
{
"display_name": "Sitecore Dev",
"id": 233,
"rationale": null,
"role_archetype": "Engineering",
"slug": "sitecore-dev",
"source": "db"
}
],
"chosen_role": {
"display_name": "SDET",
"id": 66,
"rationale": "Domain=Testing \u0026 Quality; The JD centers on test design, automation, code review, CI/CD execution, root cause analysis, and collaboration across product development, which aligns strongly with an SDET.",
"role_archetype": null,
"slug": "sdet",
"source": "db"
},
"dimensions": [
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "CI/CD Pipeline Platforms",
"id": 150,
"rationale": "Systems used to define, run, and maintain automated build and deployment workflows. This cluster is coherent because the role owns delivery automation end to end, including pipeline reliability and promotion logic.",
"slug": "ci-cd-pipeline-platforms",
"source": "db"
},
"input_skill": "CI/CD",
"llm_role": null,
"roles_from_db": [
{
"display_name": "DevOps Engineer",
"id": 10,
"rationale": null,
"role_archetype": null,
"slug": "devops-engineer",
"source": "db"
}
]
},
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "CI/CD for Machine Learning",
"id": 56,
"rationale": "Tools and platforms for automating ML model integration, testing, and deployment pipelines.",
"slug": "ci-cd-for-machine-learning",
"source": "db"
},
"input_skill": "CI/CD",
"llm_role": null,
"roles_from_db": [
{
"display_name": "ML Engineer",
"id": 3,
"rationale": null,
"role_archetype": null,
"slug": "ml-engineer",
"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": "Code Review",
"llm_role": null,
"roles_from_db": []
},
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Observability and Diagnostics",
"id": 287,
"rationale": "Instrumentation and troubleshooting practices used to understand Java service behavior in production and lower environments. This cluster covers logs, metrics, traces, correlation IDs, and root-cause analysis from service telemetry.",
"slug": "observability-and-diagnostics",
"source": "db"
},
"input_skill": "Root Cause Analysis",
"llm_role": null,
"roles_from_db": [
{
"display_name": "Go Backend Developer",
"id": 81,
"rationale": null,
"role_archetype": "Engineering",
"slug": "go-backend-developer",
"source": "db"
},
{
"display_name": "Java Backend Developer",
"id": 79,
"rationale": null,
"role_archetype": "Engineering",
"slug": "java-backend-developer",
"source": "db"
},
{
"display_name": "Python Backend Developer",
"id": 80,
"rationale": null,
"role_archetype": "Engineering",
"slug": "python-backend-developer",
"source": "db"
}
]
},
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Site Troubleshooting and Debugging",
"id": 353,
"rationale": "Diagnosing and fixing Drupal site defects across custom code, configuration, and runtime behavior. This is a coherent cluster because Drupal developers are expected to trace issues from symptoms back to modules, templates, or config.",
"slug": "site-troubleshooting-and-debugging",
"source": "db"
},
"input_skill": "Root Cause Analysis",
"llm_role": null,
"roles_from_db": [
{
"display_name": "Drupal Dev",
"id": 228,
"rationale": null,
"role_archetype": "Engineering",
"slug": "drupal-dev",
"source": "db"
}
]
},
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Sitecore Troubleshooting and Maintenance",
"id": 447,
"rationale": "Diagnosing defects, regressions, and maintainability issues across Sitecore code, configuration, and content behavior. This is a coherent cluster because the role is expected to stabilize the site experience over time.",
"slug": "sitecore-troubleshooting-and-maintenance",
"source": "db"
},
"input_skill": "Root Cause Analysis",
"llm_role": null,
"roles_from_db": [
{
"display_name": "Sitecore Dev",
"id": 233,
"rationale": null,
"role_archetype": "Engineering",
"slug": "sitecore-dev",
"source": "db"
}
]
}
],
"input_final_skills": [
"CI/CD",
"Code Review",
"Chaos Testing",
"Root Cause Analysis"
],
"input_llm_skills": [
"CI/CD",
"Code Review",
"Chaos Testing",
"Root Cause Analysis"
],
"new_aliases_persisted": 0,
"run_id": "34bc1c8d-ac29-42d1-bc19-0edf868f8315",
"skills_detail": [
{
"aliases_in_db": [
{
"alias_text": "CI/CD",
"alias_type": "CANONICAL",
"id": 1826,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
}
],
"canonical": {
"category_id": 8,
"display_name": "CI/CD",
"id": 1190,
"is_also_category": false,
"is_extractable": true,
"skill_nature": "METHODOLOGY",
"slug": "ci-cd",
"sub_category_id": 900,
"typical_lifespan": "EVERGREEN",
"volatility": "STABLE"
},
"dimensions": [
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "CI/CD Pipeline Platforms",
"id": 150,
"rationale": "Systems used to define, run, and maintain automated build and deployment workflows. This cluster is coherent because the role owns delivery automation end to end, including pipeline reliability and promotion logic.",
"slug": "ci-cd-pipeline-platforms",
"source": "db"
},
"input_skill": "CI/CD",
"llm_role": null,
"roles_from_db": [
{
"display_name": "DevOps Engineer",
"id": 10,
"rationale": null,
"role_archetype": null,
"slug": "devops-engineer",
"source": "db"
}
]
},
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "CI/CD for Machine Learning",
"id": 56,
"rationale": "Tools and platforms for automating ML model integration, testing, and deployment pipelines.",
"slug": "ci-cd-for-machine-learning",
"source": "db"
},
"input_skill": "CI/CD",
"llm_role": null,
"roles_from_db": [
{
"display_name": "ML Engineer",
"id": 3,
"rationale": null,
"role_archetype": null,
"slug": "ml-engineer",
"source": "db"
}
]
}
],
"input_skill": "CI/CD",
"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": "Code Review",
"alias_type": "CANONICAL",
"id": 864,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
}
],
"canonical": {
"category_id": 58,
"display_name": "Code Review",
"id": 516,
"is_also_category": false,
"is_extractable": true,
"skill_nature": "PRACTICE",
"slug": "code-review",
"sub_category_id": 364,
"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": "Code Review",
"llm_role": null,
"roles_from_db": []
}
],
"input_skill": "Code Review",
"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": [],
"canonical": null,
"dimensions": [],
"input_skill": "Chaos Testing",
"matched_via": null,
"new_alias_persisted": false,
"new_alias_text": null,
"new_skill_meta": {
"derived": {
"category": "Practices",
"skill_nature": "PRACTICE",
"sub_category": "general",
"typical_lifespan": "MULTI_YEAR",
"version_strategy": "UNVERSIONED",
"volatility": "MEDIUM"
},
"enrichment": null,
"keep_log": [],
"locked_dimensions": [],
"merge_log": [],
"placed": null,
"relationships": null,
"skill_id": "chaos-testing",
"split_log": [],
"typed": null,
"warnings": []
},
"source_tag": "llm",
"was_in_llm_skills": true
},
{
"aliases_in_db": [
{
"alias_text": "root cause analysis",
"alias_type": "CANONICAL",
"id": 3688,
"is_primary": true,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "root-cause analysis",
"alias_type": "CANONICAL",
"id": 4634,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
}
],
"canonical": {
"category_id": 8,
"display_name": "root cause analysis",
"id": 2392,
"is_also_category": false,
"is_extractable": true,
"skill_nature": "METHODOLOGY",
"slug": "root-cause-analysis",
"sub_category_id": 3301,
"typical_lifespan": "EVERGREEN",
"volatility": "STABLE"
},
"dimensions": [
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Observability and Diagnostics",
"id": 287,
"rationale": "Instrumentation and troubleshooting practices used to understand Java service behavior in production and lower environments. This cluster covers logs, metrics, traces, correlation IDs, and root-cause analysis from service telemetry.",
"slug": "observability-and-diagnostics",
"source": "db"
},
"input_skill": "Root Cause Analysis",
"llm_role": null,
"roles_from_db": [
{
"display_name": "Go Backend Developer",
"id": 81,
"rationale": null,
"role_archetype": "Engineering",
"slug": "go-backend-developer",
"source": "db"
},
{
"display_name": "Java Backend Developer",
"id": 79,
"rationale": null,
"role_archetype": "Engineering",
"slug": "java-backend-developer",
"source": "db"
},
{
"display_name": "Python Backend Developer",
"id": 80,
"rationale": null,
"role_archetype": "Engineering",
"slug": "python-backend-developer",
"source": "db"
}
]
},
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Site Troubleshooting and Debugging",
"id": 353,
"rationale": "Diagnosing and fixing Drupal site defects across custom code, configuration, and runtime behavior. This is a coherent cluster because Drupal developers are expected to trace issues from symptoms back to modules, templates, or config.",
"slug": "site-troubleshooting-and-debugging",
"source": "db"
},
"input_skill": "Root Cause Analysis",
"llm_role": null,
"roles_from_db": [
{
"display_name": "Drupal Dev",
"id": 228,
"rationale": null,
"role_archetype": "Engineering",
"slug": "drupal-dev",
"source": "db"
}
]
},
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Sitecore Troubleshooting and Maintenance",
"id": 447,
"rationale": "Diagnosing defects, regressions, and maintainability issues across Sitecore code, configuration, and content behavior. This is a coherent cluster because the role is expected to stabilize the site experience over time.",
"slug": "sitecore-troubleshooting-and-maintenance",
"source": "db"
},
"input_skill": "Root Cause Analysis",
"llm_role": null,
"roles_from_db": [
{
"display_name": "Sitecore Dev",
"id": 233,
"rationale": null,
"role_archetype": "Engineering",
"slug": "sitecore-dev",
"source": "db"
}
]
}
],
"input_skill": "Root Cause Analysis",
"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": [
"Chaos Testing"
]
}
API 3 — final-role-output
{
"chosen_role": {
"display_name": "SDET",
"id": 66,
"rationale": "Domain=Testing \u0026 Quality; The JD centers on test design, automation, code review, CI/CD execution, root cause analysis, and collaboration across product development, which aligns strongly with an SDET.",
"role_archetype": null,
"slug": "sdet",
"source": "db"
},
"chosen_role_resolution": "in_db",
"final_input_skills": [
{
"skill": "CI/CD",
"tag": "in_db"
},
{
"skill": "Code Review",
"tag": "in_db"
},
{
"skill": "Chaos Testing",
"tag": "new"
},
{
"skill": "Root Cause Analysis",
"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": 66,
"dimension": {
"difficulty_hint": "well_known",
"display_name": "CI/CD Pipeline Platforms",
"id": 150,
"rationale": "Systems used to define, run, and maintain automated build and deployment workflows. This cluster is coherent because the role owns delivery automation end to end, including pipeline reliability and promotion logic.",
"slug": "ci-cd-pipeline-platforms",
"source": "db"
},
"dimension_id": 150,
"input_skill": "CI/CD",
"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": "DevOps Engineer",
"id": 10,
"rationale": null,
"role_archetype": null,
"slug": "devops-engineer",
"source": "db"
}
],
"skill_dimension_saved": true,
"skill_id": 1190,
"skill_tag": "in_db",
"skipped_reason": null
},
{
"chosen_role_id": 66,
"dimension": {
"difficulty_hint": "well_known",
"display_name": "CI/CD for Machine Learning",
"id": 56,
"rationale": "Tools and platforms for automating ML model integration, testing, and deployment pipelines.",
"slug": "ci-cd-for-machine-learning",
"source": "db"
},
"dimension_id": 56,
"input_skill": "CI/CD",
"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": "ML Engineer",
"id": 3,
"rationale": null,
"role_archetype": null,
"slug": "ml-engineer",
"source": "db"
}
],
"skill_dimension_saved": true,
"skill_id": 1190,
"skill_tag": "in_db",
"skipped_reason": null
},
{
"chosen_role_id": 66,
"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": "Code Review",
"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": 516,
"skill_tag": "in_db",
"skipped_reason": null
},
{
"chosen_role_id": 66,
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Observability and Diagnostics",
"id": 287,
"rationale": "Instrumentation and troubleshooting practices used to understand Java service behavior in production and lower environments. This cluster covers logs, metrics, traces, correlation IDs, and root-cause analysis from service telemetry.",
"slug": "observability-and-diagnostics",
"source": "db"
},
"dimension_id": 287,
"input_skill": "Root Cause Analysis",
"llm_role": null,
"matched_chosen_role": false,
"outcome_line": "Existing dimension (library) \u00b7 Role\u2194dimension skipped (dimension not under chosen role)",
"role_dimension_saved": false,
"roles_from_db": [
{
"display_name": "Go Backend Developer",
"id": 81,
"rationale": null,
"role_archetype": "Engineering",
"slug": "go-backend-developer",
"source": "db"
},
{
"display_name": "Java Backend Developer",
"id": 79,
"rationale": null,
"role_archetype": "Engineering",
"slug": "java-backend-developer",
"source": "db"
},
{
"display_name": "Python Backend Developer",
"id": 80,
"rationale": null,
"role_archetype": "Engineering",
"slug": "python-backend-developer",
"source": "db"
}
],
"skill_dimension_saved": true,
"skill_id": 2392,
"skill_tag": "in_db",
"skipped_reason": null
},
{
"chosen_role_id": 66,
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Site Troubleshooting and Debugging",
"id": 353,
"rationale": "Diagnosing and fixing Drupal site defects across custom code, configuration, and runtime behavior. This is a coherent cluster because Drupal developers are expected to trace issues from symptoms back to modules, templates, or config.",
"slug": "site-troubleshooting-and-debugging",
"source": "db"
},
"dimension_id": 353,
"input_skill": "Root Cause Analysis",
"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": "Drupal Dev",
"id": 228,
"rationale": null,
"role_archetype": "Engineering",
"slug": "drupal-dev",
"source": "db"
}
],
"skill_dimension_saved": true,
"skill_id": 2392,
"skill_tag": "in_db",
"skipped_reason": null
},
{
"chosen_role_id": 66,
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Sitecore Troubleshooting and Maintenance",
"id": 447,
"rationale": "Diagnosing defects, regressions, and maintainability issues across Sitecore code, configuration, and content behavior. This is a coherent cluster because the role is expected to stabilize the site experience over time.",
"slug": "sitecore-troubleshooting-and-maintenance",
"source": "db"
},
"dimension_id": 447,
"input_skill": "Root Cause Analysis",
"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": "Sitecore Dev",
"id": 233,
"rationale": null,
"role_archetype": "Engineering",
"slug": "sitecore-dev",
"source": "db"
}
],
"skill_dimension_saved": true,
"skill_id": 2392,
"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": "34bc1c8d-ac29-42d1-bc19-0edf868f8315"
}
LLM Calls
Every model call made for this run, in pipeline order. Click a card to see the model's response.