Pipeline run
91515540-2d18-424c-95a5-337c30a51070
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
• Checklists tailoring and compliance verification for specific Lab/Estt. needs • Analysis of software code, design and related artifacts (code, documents, scripts) and preparation of reports • High l…
1 POST /skills/extract-from-jd
2 POST /skills/extract-details
3 POST /skills/final-role-output
Manual Test Engineer
domain · Testing & Quality CASE DOMAINslug: manual-test-engineer · id: 65 · source: db
Domain=Testing & Quality; The JD is centered on verification, traceability, test execution, reporting, reviews, and V&V activities, with only limited automation mention, which best matches manual testing rather than automation or performance/security specialties.
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: Artificial Intelligence (AI), Machine Learning, python, software testing, ai, ml, About Us GVR Technolabs Pvt Ltd, an Information Technology services company with expertise in design, deployment and management of hardware and software applications and technology infrastructures. We offer services to improve our clients efficiency, strengthen partnerships, increase profitability, and improve business processes with quality and value in a secure environment. Designation: Software Quality Assurance (IV & V Services) Locations: Delhi Qualification: B.Tech/BE/M.Tech/ME in ECE/CSE/EEE/ECE/E & TCE or MSc (CS) or MCA Additional Qualification: IEEE-12207, IEEE-29119, DO-178B/C, DDPMAS, MIL-STD-498, DRDO Standard for software development (DDSD; will be provided) for all the activities. Experience Required 2 Years for Regular level 4 Years for High level 6 Years for Expert level. No. Of Vacancies (Approx) Regular 2 Roles & Responsibilities • Checklists tailoring and compliance verification for specific Lab/Estt. needs • Analysis of software code, design and related artifacts (code, documents, scripts) and preparation of reports • High level requirements to low level requirements to design to implementation to test cases traceability and report generation • Execution of test vectors, generation of test oracles / data set • Test coverage based on test execution plan and report generation • Execution of functional, non-functional and endurance tests w.r.t ATP document • First level identification, reporting verification on closure of defects & bug • Review of documentation for completeness, consistency, traceability and reporting • Test measurements reports generation and analysis • Static and dynamic testing reports generation and review • Development of automated regression test suites and regression testing based as per test plans. • Test report generation for certification, where applicable • Preparation of required documentation for the air-worthiness certification or equivalent certifications for all levels of criticality • Generation of result reports for the IV&V activities carried out • Use of configuration tools for software configuration control • Configuration audits and report generation • Software quality metrics data recording and analysis, and reporting • Review of requirements, design, interfaces/ protocols and documents and release the review reports/ audit reports • Verification/ updating of low level test plan, test cases and test procedures (Unit testing and module testing) • Integration testing and analysis and report generation • Requirements based testing &test case generation w.r.t functional requirements • Generation of endurance test cases and realization of endurance test beds. • Generation of smoke &sanity tests results, review and validation of the same • Reverification of identification and reporting on closure of defects & bugs • Verification of test beds/prototypes similar to deliverable system • Development of test procedure and test scripts for HSI testing based on requirements • Execution & reporting and review of HSI testing • Phase checks, Integration testing and analysis of final V&V reports • End to end traceability review • Generation and verification of functional and non-functional requirement test cases. • Code walkthrough and review and reporting • Object code testing and review and reporting • FPGA/ Verilog/ VHDL code review and reporting • Third party library testing and report generation • Verification of software tool qualification and documentation • Impact analysis and change request-based testing and regression analysis • Mutation testing with debugging, fault injection at unit, component & system level • Defect identification and tracking • Preparation and management of trace data • Development/ updation of software IV&V plan as per the standard/ guidelines • Testing using jigs, simulators and test beds • Define IV&V processes and methodologies • Review and validation of all test plans, suites and results including automated regression test suites • Analysis of software quality metrics data as per established process and product metrics • Audit of all reviews • Audit of all IV&V processes • Validation of deliverable systems w.r.t functional and non-functional requirements • Behavioral testing and reliability assessment • Generation/ validation of FAT and ATP documents • Review of all documents related to qualification and certification and release the same Requirements • Flight control software (S/W residing on on-board computers of launch vehicles) and on-board mission systems and avionics • Ground based software (S/W residing in checkout systems and simulation test facilities of launch vehicles) • Ground based armament and combat systems • Verification simulators software and Test rig software • Mission planning, design and training Software • Engine control software • Radar and Communication software Signal processing & analysis software • Shipborne/ Under water systems software • Simulation & Modeling software • Other software required to build mission critical / safety critical systems • Other general-purpose software in Aerospace and Defence domain. • Other software application using web technologies and RDBMS
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
- Agile (CANONICAL) primary
Context tags (catalog)
Stored enrichment (catalog DB)
- Category
- Methodology
- Sub-category
- Agile
- Confidence
- 0.99
- Version strategy
- NOT_APPLICABLE
Maturity reasoning: Agile appears in a large share of software job descriptions and is a standard hiring-pipeline requirement; Scrum/Kanban are commonly listed alongside it, showing broad market adoption.
Skill profile (library / DB)
- Skill nature
- METHODOLOGY
- Volatility
- STABLE
- Typical lifespan
- EVERGREEN
- Category id
- 8
- Sub-category id
- 3594
- Extractable
- True
- Also category
- False
Dimensions (API 2 worklist)
-
React Frontend Development Catalog dimension db id 96
Library dimension (catalog)
-
Software Concepts, Patterns & Practices Catalog dimension db id 478
Library dimension (catalog)
Roles linked in library: Engineering Manager
API 3 link attempts (this skill)
| Dimension | Skill↔dim | Role↔dim | Outcome |
|---|---|---|---|
|
React Frontend Development
d_init_01
|
✓ | — | Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role) |
|
Software Concepts, Patterns & Practices
software-concepts-patterns-practices
|
✓ | — | Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role) |
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
- debugging (CANONICAL) primary
Context tags (catalog)
Stored enrichment (catalog DB)
- Category
- Methodology
- Sub-category
- Debugging Methodology
- Confidence
- 0.96
- Version strategy
- NOT_APPLICABLE
Maturity reasoning: Debugging is a universal hiring-pipeline skill across software JDs and interview loops; it appears in role requirements for backend, frontend, SRE, and QA, with no successor replacing it.
Skill profile (library / DB)
- Skill nature
- METHODOLOGY
- Volatility
- STABLE
- Typical lifespan
- EVERGREEN
- Category id
- 8
- Sub-category id
- 3293
- Extractable
- True
- Also category
- False
Dimensions (API 2 worklist)
-
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 |
|---|---|---|---|
|
Sitecore Troubleshooting and Maintenance
sitecore-troubleshooting-and-maintenance
|
✓ | — | Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role) |
Aliases — catalog
- end-to-end tests (CANONICAL) primary
Context tags (catalog)
Stored enrichment (catalog DB)
- Category
- Methodology
- Sub-category
- Testing Methodology
- Confidence
- 0.97
- Version strategy
- NOT_APPLICABLE
Maturity reasoning: Commonly listed in QA/SDET and frontend/backend JDs; tools like Cypress, Playwright, and Selenium show strong GitHub and job-market demand for E2E testing.
Skill profile (library / DB)
- Skill nature
- METHODOLOGY
- Volatility
- STABLE
- Typical lifespan
- EVERGREEN
- Category id
- 8
- Sub-category id
- 44
- Extractable
- True
- Also category
- False
Dimensions (API 2 worklist)
-
Testing and Quality Assurance Catalog dimension db id 12
Library dimension (catalog)
Roles linked in library: .NET Backend Developer, Backend Developer, Node.js Backend Developer, PHP Backend Developer, Python Backend Developer, Scala Backend Developer
API 3 link attempts (this skill)
| Dimension | Skill↔dim | Role↔dim | Outcome |
|---|---|---|---|
|
Testing and Quality Assurance
testing-and-quality-assurance
|
— | — |
Skipped — no persistable v3 meta for new skill
skill_not_in_db_v3_proposed
|
Aliases — catalog
- Integration testing (CANONICAL) primary
- integration testing (CANONICAL)
Context tags (catalog)
Stored enrichment (catalog DB)
- Category
- Methodology
- Sub-category
- Testing Methodology
- Confidence
- 0.97
- Version strategy
- NOT_APPLICABLE
Maturity reasoning: Integration testing is a standard QA skill in job descriptions across backend, frontend, and DevOps roles; it’s commonly paired with CI/CD and tools like Jest, Cypress, and Testcontainers.
Skill profile (library / DB)
- Skill nature
- METHODOLOGY
- Volatility
- STABLE
- Typical lifespan
- EVERGREEN
- Category id
- 8
- Sub-category id
- 44
- Extractable
- True
- Also category
- False
Dimensions (API 2 worklist)
-
Testing and Defect Resolution Catalog dimension db id 262
Library dimension (catalog)
Roles linked in library: Pega Developer
-
Testing and Quality Assurance Catalog dimension db id 12
Library dimension (catalog)
Roles linked in library: .NET Backend Developer, Backend Developer, Node.js Backend Developer, PHP Backend Developer, Python Backend Developer, Scala Backend Developer
API 3 link attempts (this skill)
| Dimension | Skill↔dim | Role↔dim | Outcome |
|---|---|---|---|
|
Testing and Defect Resolution
testing-and-defect-resolution
|
— | — |
Skipped — no persistable v3 meta for new skill
skill_not_in_db_v3_proposed
|
|
Testing and Quality Assurance
testing-and-quality-assurance
|
— | — |
Skipped — no persistable v3 meta for new skill
skill_not_in_db_v3_proposed
|
Aliases — catalog
- Integration testing (CANONICAL) primary
- integration testing (CANONICAL)
Context tags (catalog)
Stored enrichment (catalog DB)
- Category
- Methodology
- Sub-category
- Testing Methodology
- Confidence
- 0.97
- Version strategy
- NOT_APPLICABLE
Maturity reasoning: Integration testing is a standard QA skill in job descriptions across backend, frontend, and DevOps roles; it’s commonly paired with CI/CD and tools like Jest, Cypress, and Testcontainers.
Skill profile (library / DB)
- Skill nature
- METHODOLOGY
- Volatility
- STABLE
- Typical lifespan
- EVERGREEN
- Category id
- 8
- Sub-category id
- 44
- Extractable
- True
- Also category
- False
Dimensions (API 2 worklist)
-
Testing and Defect Resolution Catalog dimension db id 262
Library dimension (catalog)
Roles linked in library: Pega Developer
-
Testing and Quality Assurance Catalog dimension db id 12
Library dimension (catalog)
Roles linked in library: .NET Backend Developer, Backend Developer, Node.js Backend Developer, PHP Backend Developer, Python Backend Developer, Scala Backend Developer
API 3 link attempts (this skill)
| Dimension | Skill↔dim | Role↔dim | Outcome |
|---|---|---|---|
|
Testing and Defect Resolution
testing-and-defect-resolution
|
✓ | — | Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role) |
|
Testing and Quality Assurance
testing-and-quality-assurance
|
✓ | — | Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role) |
Skill enrichment (orchestrator / LLM)
No Stage 7 enrichment blob on this skill (orchestrator skipped enrichment).
- Category
- Testing Tools
- Sub-category
- general
- Skill nature
- TOOL
- Volatility
- MEDIUM
- Typical lifespan
- MULTI_YEAR
- Version strategy
- UNVERSIONED
Aliases — catalog
- Regression testing (CANONICAL) primary
Context tags (catalog)
Stored enrichment (catalog DB)
- Category
- Methodology
- Sub-category
- Regression Testing
- Confidence
- 0.98
- Version strategy
- NOT_APPLICABLE
Maturity reasoning: Regression testing is a standard QA practice in most software JDs and test plans; CI/CD tools and vendor docs routinely include it as a core safeguard against reintroducing bugs.
Skill profile (library / DB)
- Skill nature
- METHODOLOGY
- Volatility
- STABLE
- Typical lifespan
- EVERGREEN
- Category id
- 8
- Sub-category id
- 2940
- Extractable
- True
- Also category
- False
Dimensions (API 2 worklist)
-
Magento Testing and Upgrade Safety Catalog dimension db id 405
Library dimension (catalog)
Roles linked in library: Magento Dev
API 3 link attempts (this skill)
| Dimension | Skill↔dim | Role↔dim | Outcome |
|---|---|---|---|
|
Magento Testing and Upgrade Safety
magento-testing-and-upgrade-safety
|
✓ | — | 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
- Concepts
- Sub-category
- general
- Skill nature
- CONCEPT
- Volatility
- STABLE
- Typical lifespan
- EVERGREEN
- Version strategy
- UNVERSIONED
Skill enrichment (orchestrator / LLM)
No Stage 7 enrichment blob on this skill (orchestrator skipped enrichment).
- Category
- Practices
- Sub-category
- general
- Skill nature
- PRACTICE
- Volatility
- STABLE
- Typical lifespan
- EVERGREEN
- Version strategy
- UNVERSIONED
Aliases — catalog
- Integration testing (CANONICAL) primary
- integration testing (CANONICAL)
Context tags (catalog)
Stored enrichment (catalog DB)
- Category
- Methodology
- Sub-category
- Testing Methodology
- Confidence
- 0.97
- Version strategy
- NOT_APPLICABLE
Maturity reasoning: Integration testing is a standard QA skill in job descriptions across backend, frontend, and DevOps roles; it’s commonly paired with CI/CD and tools like Jest, Cypress, and Testcontainers.
Skill profile (library / DB)
- Skill nature
- METHODOLOGY
- Volatility
- STABLE
- Typical lifespan
- EVERGREEN
- Category id
- 8
- Sub-category id
- 44
- Extractable
- True
- Also category
- False
Dimensions (API 2 worklist)
-
Testing and Defect Resolution Catalog dimension db id 262
Library dimension (catalog)
Roles linked in library: Pega Developer
-
Testing and Quality Assurance Catalog dimension db id 12
Library dimension (catalog)
Roles linked in library: .NET Backend Developer, Backend Developer, Node.js Backend Developer, PHP Backend Developer, Python Backend Developer, Scala Backend Developer
API 3 link attempts (this skill)
| Dimension | Skill↔dim | Role↔dim | Outcome |
|---|---|---|---|
|
Testing and Defect Resolution
testing-and-defect-resolution
|
— | — |
Skipped — no persistable v3 meta for new skill
skill_not_in_db_v3_proposed
|
|
Testing and Quality Assurance
testing-and-quality-assurance
|
— | — |
Skipped — no persistable v3 meta for new skill
skill_not_in_db_v3_proposed
|
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
Skill enrichment (orchestrator / LLM)
No Stage 7 enrichment blob on this skill (orchestrator skipped enrichment).
- Category
- Practices
- Sub-category
- general
- Skill nature
- PRACTICE
- Volatility
- STABLE
- Typical lifespan
- EVERGREEN
- Version strategy
- UNVERSIONED
Skill enrichment (orchestrator / LLM)
No Stage 7 enrichment blob on this skill (orchestrator skipped enrichment).
- Category
- Concepts
- Sub-category
- general
- Skill nature
- CONCEPT
- Volatility
- STABLE
- Typical lifespan
- EVERGREEN
- Version strategy
- UNVERSIONED
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
Skill enrichment (orchestrator / LLM)
No Stage 7 enrichment blob on this skill (orchestrator skipped enrichment).
- Category
- Practices
- Sub-category
- general
- Skill nature
- PRACTICE
- Volatility
- STABLE
- Typical lifespan
- EVERGREEN
- Version strategy
- UNVERSIONED
Skill enrichment (orchestrator / LLM)
No Stage 7 enrichment blob on this skill (orchestrator skipped enrichment).
- Category
- Practices
- Sub-category
- general
- Skill nature
- PRACTICE
- Volatility
- STABLE
- Typical lifespan
- EVERGREEN
- Version strategy
- UNVERSIONED
Skill enrichment (orchestrator / LLM)
No Stage 7 enrichment blob on this skill (orchestrator skipped enrichment).
- Category
- Testing Tools
- Sub-category
- general
- Skill nature
- TOOL
- Volatility
- MEDIUM
- Typical lifespan
- MULTI_YEAR
- Version strategy
- UNVERSIONED
Aliases — catalog
- Unit Testing (CANONICAL)
Context tags (catalog)
Stored enrichment (catalog DB)
- Category
- Methodology
- Sub-category
- Testing Methodology
- Confidence
- 0.98
- Version strategy
- NOT_APPLICABLE
Maturity reasoning: Unit testing is a standard hiring requirement across software JDs and appears in mainstream frameworks/docs; GitHub and Stack Overflow usage remain consistently high, with no successor replacing it.
Skill profile (library / DB)
- Skill nature
- METHODOLOGY
- Volatility
- STABLE
- Typical lifespan
- EVERGREEN
- Category id
- 8
- Sub-category id
- 44
- Extractable
- True
- Also category
- False
Dimensions (API 2 worklist)
-
React Frontend Development Catalog dimension db id 96
Library dimension (catalog)
API 3 link attempts (this skill)
| Dimension | Skill↔dim | Role↔dim | Outcome |
|---|---|---|---|
|
React Frontend Development
d_init_01
|
✓ | — | Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role) |
Skill enrichment (orchestrator / LLM)
No Stage 7 enrichment blob on this skill (orchestrator skipped enrichment).
- Category
- Programming Languages
- Sub-category
- general
- Skill nature
- LANGUAGE
- Volatility
- MEDIUM
- Typical lifespan
- MULTI_YEAR
- Version strategy
- UNVERSIONED
Skill enrichment (orchestrator / LLM)
No Stage 7 enrichment blob on this skill (orchestrator skipped enrichment).
- Category
- Programming Languages
- Sub-category
- general
- Skill nature
- LANGUAGE
- Volatility
- MEDIUM
- Typical lifespan
- MULTI_YEAR
- Version strategy
- UNVERSIONED
All API 3 persistence rows
Same grid as the skill-extractor “Persistence items” table: one row per (skill × dimension) work item.
| Skill | Tag | Dimension | Skill↔dim | Role↔dim | Outcome | Notes |
|---|---|---|---|---|---|---|
| Agile | in_db |
React Frontend Development
d_init_01
|
✓ | — | Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role) | |
| Agile | in_db |
Software Concepts, Patterns & Practices
software-concepts-patterns-practices
|
✓ | — | Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role) | |
| 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) | |
| Debugging | in_db |
Sitecore Troubleshooting and Maintenance
sitecore-troubleshooting-and-maintenance
|
✓ | — | Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role) | |
| End-to-End Testing | new |
Testing and Quality Assurance
testing-and-quality-assurance
|
— | — | Skipped — no persistable v3 meta for new skill | skill_not_in_db_v3_proposed |
| Functional Testing | new |
Testing and Defect Resolution
testing-and-defect-resolution
|
— | — | Skipped — no persistable v3 meta for new skill | skill_not_in_db_v3_proposed |
| Functional Testing | new |
Testing and Quality Assurance
testing-and-quality-assurance
|
— | — | Skipped — no persistable v3 meta for new skill | skill_not_in_db_v3_proposed |
| Integration Testing | in_db |
Testing and Defect Resolution
testing-and-defect-resolution
|
✓ | — | Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role) | |
| Integration Testing | in_db |
Testing and Quality Assurance
testing-and-quality-assurance
|
✓ | — | Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role) | |
| Regression Testing | in_db |
Magento Testing and Upgrade Safety
magento-testing-and-upgrade-safety
|
✓ | — | Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role) | |
| System Testing | new |
Testing and Defect Resolution
testing-and-defect-resolution
|
— | — | Skipped — no persistable v3 meta for new skill | skill_not_in_db_v3_proposed |
| System Testing | new |
Testing and Quality Assurance
testing-and-quality-assurance
|
— | — | Skipped — no persistable v3 meta for new skill | skill_not_in_db_v3_proposed |
| Unit Testing | in_db |
React Frontend Development
d_init_01
|
✓ | — | Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role) |
Library artifacts (this run)
| Kind | Detail | DB id |
|---|---|---|
| canonical_skill_proposed | JUnit | type=Testing Tools subtype=general nature=TOOL lifespan=MULTI_YEAR | |
| canonical_skill_proposed | Software Quality Metrics | type=Concepts subtype=general nature=CONCEPT lifespan=EVERGREEN | |
| canonical_skill_proposed | Static Testing | type=Practices subtype=general nature=PRACTICE lifespan=EVERGREEN | |
| canonical_skill_proposed | Test Automation | type=Practices subtype=general nature=PRACTICE lifespan=MULTI_YEAR | |
| canonical_skill_proposed | Test Case Design | type=Practices subtype=general nature=PRACTICE lifespan=EVERGREEN | |
| canonical_skill_proposed | Test Coverage | type=Concepts subtype=general nature=CONCEPT lifespan=EVERGREEN | |
| canonical_skill_proposed | Test Data | type=Practices subtype=general nature=PRACTICE lifespan=MULTI_YEAR | |
| canonical_skill_proposed | Test Execution | type=Practices subtype=general nature=PRACTICE lifespan=EVERGREEN | |
| canonical_skill_proposed | Test Planning | type=Practices subtype=general nature=PRACTICE lifespan=EVERGREEN | |
| canonical_skill_proposed | Test Scripts | type=Testing Tools subtype=general nature=TOOL lifespan=MULTI_YEAR | |
| canonical_skill_proposed | Verilog | type=Programming Languages subtype=general nature=LANGUAGE lifespan=MULTI_YEAR | |
| canonical_skill_proposed | VHDL | type=Programming Languages subtype=general nature=LANGUAGE lifespan=MULTI_YEAR | |
| dimension_skill_link_proposed | End-to-End Testing ↔ Testing and Quality Assurance | |
| dimension_skill_link_proposed | Functional Testing ↔ Testing and Defect Resolution | |
| dimension_skill_link_proposed | Functional Testing ↔ Testing and Quality Assurance | |
| dimension_skill_link_proposed | System Testing ↔ Testing and Defect Resolution | |
| dimension_skill_link_proposed | System Testing ↔ Testing and Quality Assurance |
nano JD Parser — gpt-4.1-nano click to toggle
Certifications
Show raw JSON
{
"JD_type": "pass",
"about_company": {
"source_marker": {
"first_5_words": "GVR Technolabs Pvt Ltd, an",
"last_5_words": "quality and value in a secure environment."
},
"text": "GVR Technolabs Pvt Ltd, an Information Technology services company with expertise in design, deployment and management of hardware and software applications and technology infrastructures. We offer services to improve our clients efficiency, strengthen partnerships, increase profitability, and improve business processes with quality and value in a secure environment.",
"word_count": 54
},
"certifications": [
"IEEE-12207",
"IEEE-29119",
"DO-178B/C",
"DDPMAS",
"MIL-STD-498",
"DRDO Standard for software development (DDSD; will be provided)"
],
"company_name": "GVR Technolabs Pvt Ltd",
"ctc": null,
"domain": {
"primary": {
"aliases": [
"Aerospace",
"Defense"
],
"domain": "Aerospace \u0026 Defense"
},
"secondary": null
},
"education": [
{
"level": "Bachelor\u0027s",
"qualification": "BTECH/BE - ECE/CSE/EEE/ECE/E \u0026 TCE or MSc (CS) or MCA",
"raw": "B.Tech/BE/M.Tech/ME in ECE/CSE/EEE/ECE/E \u0026 TCE or MSc (CS) or MCA",
"requirement": "required"
}
],
"experience": {
"max": 6,
"min": 2,
"raw": "2 Years for Regular level, 4 Years for High level, 6 Years for Expert level."
},
"job_locations": [
{
"aliases": [],
"city": "Delhi",
"country": "India",
"state": null,
"work_mode": null
}
],
"role": "Software Quality Assurance (IV \u0026 V Services)",
"role_aliases": [
"QA Engineer",
"Quality Assurance Engineer",
"Software Tester"
],
"role_archetype": "QA",
"roles_and_responsibilities": [
{
"bullet_count": 60,
"heading": "Roles \u0026 Responsibilities",
"heading_was_present": true,
"source_marker": {
"first_5_words": "\u2022 Checklists tailoring and compliance",
"last_5_words": "qualification and certification and release the same"
},
"text": "\u2022 Checklists tailoring and compliance verification for specific Lab/Estt. needs\n\u2022 Analysis of software code, design and related artifacts (code, documents, scripts) and preparation of reports\n\u2022 High level requirements to low level requirements to design to implementation to test cases traceability and report generation\n\u2022 Execution of test vectors, generation of test oracles / data set\n\u2022 Test coverage based on test execution plan and report generation\n\u2022 Execution of functional, non-functional and endurance tests w.r.t ATP document\n\u2022 First level identification, reporting verification on closure of defects \u0026 bug\n\u2022 Review of documentation for completeness, consistency, traceability and reporting\n\u2022 Test measurements reports generation and analysis\n\u2022 Static and dynamic testing reports generation and review\n\u2022 Development of automated regression test suites and regression testing based as per test plans.\n\u2022 Test report generation for certification, where applicable\n\u2022 Preparation of required documentation for the air-worthiness certification or equivalent certifications for all levels of criticality\n\u2022 Generation of result reports for the IV\u0026V activities carried out\n\u2022 Use of configuration tools for software configuration control\n\u2022 Configuration audits and report generation\n\u2022 Software quality metrics data recording and analysis, and reporting\n\u2022 Review of requirements, design, interfaces/ protocols and documents and release the review reports/ audit reports\n\u2022 Verification/ updating of low level test plan, test cases and test procedures (Unit testing and module testing)\n\u2022 Integration testing and analysis and report generation\n\u2022 Requirements based testing \u0026test case generation w.r.t functional requirements\n\u2022 Generation of endurance test cases and realization of endurance test beds.\n\u2022 Generation of smoke \u0026sanity tests results, review and validation of the same\n\u2022 Reverification of identification and reporting on closure of defects \u0026 bugs\n\u2022 Verification of test beds/prototypes similar to deliverable system\n\u2022 Development of test procedure and test scripts for HSI testing based on requirements\n\u2022 Execution \u0026 reporting and review of HSI testing\n\u2022 Phase checks, Integration testing and analysis of final V\u0026V reports\n\u2022 End to end traceability review\n\u2022 Generation and verification of functional and non-functional requirement test cases.\n\u2022 Code walkthrough and review and reporting\n\u2022 Object code testing and review and reporting\n\u2022 FPGA/ Verilog/ VHDL code review and reporting\n\u2022 Third party library testing and report generation\n\u2022 Verification of software tool qualification and documentation\n\u2022 Impact analysis and change request-based testing and regression analysis\n\u2022 Mutation testing with debugging, fault injection at unit, component \u0026 system level\n\u2022 Defect identification and tracking\n\u2022 Preparation and management of trace data\n\u2022 Development/ updation of software IV\u0026V plan as per the standard/ guidelines\n\u2022 Testing using jigs, simulators and test beds\n\u2022 Define IV\u0026V processes and methodologies\n\u2022 Review and validation of all test plans, suites and results including automated regression test suites\n\u2022 Analysis of software quality metrics data as per established process and product metrics\n\u2022 Audit of all reviews\n\u2022 Audit of all IV\u0026V processes\n\u2022 Validation of deliverable systems w.r.t functional and non-functional requirements\n\u2022 Behavioral testing and reliability assessment\n\u2022 Generation/ validation of FAT and ATP documents\n\u2022 Review of all documents related to qualification and certification and release the same",
"word_count": 564
}
],
"urls": []
}
API 1 — extract-from-jd click to toggle
{
"final_skills": [
{
"is_primary": false,
"skill_name": "Agile"
},
{
"is_primary": false,
"skill_name": "CI/CD"
},
{
"is_primary": false,
"skill_name": "Debugging"
},
{
"is_primary": true,
"skill_name": "End-to-End Testing"
},
{
"is_primary": true,
"skill_name": "Functional Testing"
},
{
"is_primary": true,
"skill_name": "Integration Testing"
},
{
"is_primary": false,
"skill_name": "JUnit"
},
{
"is_primary": true,
"skill_name": "Regression Testing"
},
{
"is_primary": true,
"skill_name": "Software Quality Metrics"
},
{
"is_primary": true,
"skill_name": "Static Testing"
},
{
"is_primary": true,
"skill_name": "System Testing"
},
{
"is_primary": true,
"skill_name": "Test Automation"
},
{
"is_primary": true,
"skill_name": "Test Case Design"
},
{
"is_primary": true,
"skill_name": "Test Coverage"
},
{
"is_primary": true,
"skill_name": "Test Data"
},
{
"is_primary": true,
"skill_name": "Test Execution"
},
{
"is_primary": true,
"skill_name": "Test Planning"
},
{
"is_primary": true,
"skill_name": "Test Scripts"
},
{
"is_primary": true,
"skill_name": "Unit Testing"
},
{
"is_primary": true,
"skill_name": "Verilog"
},
{
"is_primary": true,
"skill_name": "VHDL"
}
],
"jd_role": {
"display_name": "Software Quality Assurance (IV \u0026 V Services)",
"rationale": null,
"role_aliases": [
"QA Engineer",
"Quality Assurance Engineer",
"Software Tester"
],
"role_archetype": "QA",
"slug": ""
},
"nano_parsed": {
"JD_type": "pass",
"about_company": {
"source_marker": {
"first_5_words": "GVR Technolabs Pvt Ltd, an",
"last_5_words": "quality and value in a secure environment."
},
"text": "GVR Technolabs Pvt Ltd, an Information Technology services company with expertise in design, deployment and management of hardware and software applications and technology infrastructures. We offer services to improve our clients efficiency, strengthen partnerships, increase profitability, and improve business processes with quality and value in a secure environment.",
"word_count": 54
},
"certifications": [
"IEEE-12207",
"IEEE-29119",
"DO-178B/C",
"DDPMAS",
"MIL-STD-498",
"DRDO Standard for software development (DDSD; will be provided)"
],
"company_name": "GVR Technolabs Pvt Ltd",
"ctc": null,
"domain": {
"primary": {
"aliases": [
"Aerospace",
"Defense"
],
"domain": "Aerospace \u0026 Defense"
},
"secondary": null
},
"education": [
{
"level": "Bachelor\u0027s",
"qualification": "BTECH/BE - ECE/CSE/EEE/ECE/E \u0026 TCE or MSc (CS) or MCA",
"raw": "B.Tech/BE/M.Tech/ME in ECE/CSE/EEE/ECE/E \u0026 TCE or MSc (CS) or MCA",
"requirement": "required"
}
],
"experience": {
"max": 6,
"min": 2,
"raw": "2 Years for Regular level, 4 Years for High level, 6 Years for Expert level."
},
"job_locations": [
{
"aliases": [],
"city": "Delhi",
"country": "India",
"state": null,
"work_mode": null
}
],
"role": "Software Quality Assurance (IV \u0026 V Services)",
"role_aliases": [
"QA Engineer",
"Quality Assurance Engineer",
"Software Tester"
],
"role_archetype": "QA",
"roles_and_responsibilities": [
{
"bullet_count": 60,
"heading": "Roles \u0026 Responsibilities",
"heading_was_present": true,
"source_marker": {
"first_5_words": "\u2022 Checklists tailoring and compliance",
"last_5_words": "qualification and certification and release the same"
},
"text": "\u2022 Checklists tailoring and compliance verification for specific Lab/Estt. needs\n\u2022 Analysis of software code, design and related artifacts (code, documents, scripts) and preparation of reports\n\u2022 High level requirements to low level requirements to design to implementation to test cases traceability and report generation\n\u2022 Execution of test vectors, generation of test oracles / data set\n\u2022 Test coverage based on test execution plan and report generation\n\u2022 Execution of functional, non-functional and endurance tests w.r.t ATP document\n\u2022 First level identification, reporting verification on closure of defects \u0026 bug\n\u2022 Review of documentation for completeness, consistency, traceability and reporting\n\u2022 Test measurements reports generation and analysis\n\u2022 Static and dynamic testing reports generation and review\n\u2022 Development of automated regression test suites and regression testing based as per test plans.\n\u2022 Test report generation for certification, where applicable\n\u2022 Preparation of required documentation for the air-worthiness certification or equivalent certifications for all levels of criticality\n\u2022 Generation of result reports for the IV\u0026V activities carried out\n\u2022 Use of configuration tools for software configuration control\n\u2022 Configuration audits and report generation\n\u2022 Software quality metrics data recording and analysis, and reporting\n\u2022 Review of requirements, design, interfaces/ protocols and documents and release the review reports/ audit reports\n\u2022 Verification/ updating of low level test plan, test cases and test procedures (Unit testing and module testing)\n\u2022 Integration testing and analysis and report generation\n\u2022 Requirements based testing \u0026test case generation w.r.t functional requirements\n\u2022 Generation of endurance test cases and realization of endurance test beds.\n\u2022 Generation of smoke \u0026sanity tests results, review and validation of the same\n\u2022 Reverification of identification and reporting on closure of defects \u0026 bugs\n\u2022 Verification of test beds/prototypes similar to deliverable system\n\u2022 Development of test procedure and test scripts for HSI testing based on requirements\n\u2022 Execution \u0026 reporting and review of HSI testing\n\u2022 Phase checks, Integration testing and analysis of final V\u0026V reports\n\u2022 End to end traceability review\n\u2022 Generation and verification of functional and non-functional requirement test cases.\n\u2022 Code walkthrough and review and reporting\n\u2022 Object code testing and review and reporting\n\u2022 FPGA/ Verilog/ VHDL code review and reporting\n\u2022 Third party library testing and report generation\n\u2022 Verification of software tool qualification and documentation\n\u2022 Impact analysis and change request-based testing and regression analysis\n\u2022 Mutation testing with debugging, fault injection at unit, component \u0026 system level\n\u2022 Defect identification and tracking\n\u2022 Preparation and management of trace data\n\u2022 Development/ updation of software IV\u0026V plan as per the standard/ guidelines\n\u2022 Testing using jigs, simulators and test beds\n\u2022 Define IV\u0026V processes and methodologies\n\u2022 Review and validation of all test plans, suites and results including automated regression test suites\n\u2022 Analysis of software quality metrics data as per established process and product metrics\n\u2022 Audit of all reviews\n\u2022 Audit of all IV\u0026V processes\n\u2022 Validation of deliverable systems w.r.t functional and non-functional requirements\n\u2022 Behavioral testing and reliability assessment\n\u2022 Generation/ validation of FAT and ATP documents\n\u2022 Review of all documents related to qualification and certification and release the same",
"word_count": 564
}
],
"urls": []
},
"rejected": false,
"rejection_reason": null,
"run_id": "91515540-2d18-424c-95a5-337c30a51070",
"stage3_signals": {
"alias_found": false,
"alias_match_roles": [],
"kra_match_roles": [
{
"display_name": "Scala Backend Developer",
"kra_matches": [
{
"kra_text": "defect investigation and fixes",
"sentence": "First level identification, reporting verification on closure of defects \u0026 bug",
"similarity": 0.5985
},
{
"kra_text": "defect investigation and fixes",
"sentence": "Reverification of identification and reporting on closure of defects \u0026 bugs",
"similarity": 0.5813
},
{
"kra_text": "automated backend checks",
"sentence": "Configuration audits and report generation",
"similarity": 0.4947
}
],
"matched_count": null,
"matched_skills": null,
"role_id": 87,
"score": 0.5582,
"slug": "scala-backend-developer",
"total_count": null
},
{
"display_name": "Ruby Backend Developer",
"kra_matches": [
{
"kra_text": "backend defect diagnosis and fixes",
"sentence": "First level identification, reporting verification on closure of defects \u0026 bug",
"similarity": 0.5958
},
{
"kra_text": "backend defect diagnosis and fixes",
"sentence": "Reverification of identification and reporting on closure of defects \u0026 bugs",
"similarity": 0.559
},
{
"kra_text": "automated backend checks",
"sentence": "Configuration audits and report generation",
"similarity": 0.4947
}
],
"matched_count": null,
"matched_skills": null,
"role_id": 85,
"score": 0.5499,
"slug": "ruby-backend-developer",
"total_count": null
},
{
"display_name": "PHP Backend Developer",
"kra_matches": [
{
"kra_text": "automated backend regression checks",
"sentence": "Development of automated regression test suites and regression testing based as per test plans.",
"similarity": 0.5837
},
{
"kra_text": "defect diagnosis and remediation",
"sentence": "First level identification, reporting verification on closure of defects \u0026 bug",
"similarity": 0.5356
},
{
"kra_text": "defect diagnosis and remediation",
"sentence": "Reverification of identification and reporting on closure of defects \u0026 bugs",
"similarity": 0.5301
}
],
"matched_count": null,
"matched_skills": null,
"role_id": 86,
"score": 0.5498,
"slug": "php-backend-developer",
"total_count": null
},
{
"display_name": "Go Backend Developer",
"kra_matches": [
{
"kra_text": "defect investigation and resolution",
"sentence": "First level identification, reporting verification on closure of defects \u0026 bug",
"similarity": 0.5603
},
{
"kra_text": "code review and testing support",
"sentence": "Integration testing and analysis and report generation",
"similarity": 0.5469
},
{
"kra_text": "defect investigation and resolution",
"sentence": "Reverification of identification and reporting on closure of defects \u0026 bugs",
"similarity": 0.5405
}
],
"matched_count": null,
"matched_skills": null,
"role_id": 81,
"score": 0.5492,
"slug": "go-backend-developer",
"total_count": null
},
{
"display_name": ".NET Backend Developer",
"kra_matches": [
{
"kra_text": "defect investigation and resolution",
"sentence": "First level identification, reporting verification on closure of defects \u0026 bug",
"similarity": 0.5603
},
{
"kra_text": "defect investigation and resolution",
"sentence": "Reverification of identification and reporting on closure of defects \u0026 bugs",
"similarity": 0.5405
},
{
"kra_text": "automated backend checks",
"sentence": "Configuration audits and report generation",
"similarity": 0.4947
}
],
"matched_count": null,
"matched_skills": null,
"role_id": 83,
"score": 0.5318,
"slug": "dotnet-backend-developer",
"total_count": null
}
],
"skill_match_roles": [
{
"display_name": "Backend Developer",
"kra_matches": null,
"matched_count": 1,
"matched_skills": [
"Integration testing"
],
"role_id": 1,
"score": 0.0588,
"slug": "backend-engineer",
"total_count": 17
},
{
"display_name": "Pega Developer",
"kra_matches": null,
"matched_count": 1,
"matched_skills": [
"Integration testing"
],
"role_id": 24,
"score": 0.0588,
"slug": "pega-developer",
"total_count": 17
},
{
"display_name": "Python Backend Developer",
"kra_matches": null,
"matched_count": 1,
"matched_skills": [
"Integration testing"
],
"role_id": 80,
"score": 0.0588,
"slug": "python-backend-developer",
"total_count": 17
},
{
"display_name": "Node.js Backend Developer",
"kra_matches": null,
"matched_count": 1,
"matched_skills": [
"Integration testing"
],
"role_id": 82,
"score": 0.0588,
"slug": "node-backend-developer",
"total_count": 17
},
{
"display_name": ".NET Backend Developer",
"kra_matches": null,
"matched_count": 1,
"matched_skills": [
"Integration testing"
],
"role_id": 83,
"score": 0.0588,
"slug": "dotnet-backend-developer",
"total_count": 17
}
]
},
"stage4_decision": {
"alias_collision_detected": false,
"case": "DOMAIN",
"chosen_role": {
"display_name": "Manual Test Engineer",
"kra_matches": null,
"matched_count": null,
"matched_skills": null,
"role_id": 65,
"score": 0.97,
"slug": "manual-test-engineer",
"total_count": null
},
"confidence": 0.97,
"is_new_role": false,
"llm2_fired": false,
"llm2_reasoning": null,
"matched_dimensions": [
"Software Verification and Validation",
"Requirements Traceability",
"Test Planning and Execution",
"Defect Verification and Closure",
"Documentation Review and Reporting",
"Configuration Control and Audits",
"Certification Support",
"Embedded/IV\u0026V Quality Assurance"
],
"matched_kras": [
"Checklists tailoring and compliance verification",
"Analysis of software code, design and related artifacts",
"Preparation of reports",
"Test coverage based on test execution plan",
"Execution of functional, non-functional and endurance tests",
"First level identification, reporting verification on closure of defects \u0026 bug",
"Review of documentation for completeness, consistency, traceability",
"Development of automated regression test suites",
"Configuration audits and report generation",
"End to end traceability review"
],
"matched_skills": [
"test cases traceability",
"test vectors",
"test oracles",
"functional testing",
"non-functional testing",
"endurance tests",
"automated regression test suites",
"software configuration control",
"configuration audits",
"static testing",
"dynamic testing",
"code walkthrough",
"object code testing",
"FPGA/ Verilog/ VHDL code review",
"HSI testing"
],
"new_role_display_name": null,
"new_role_slug": null,
"queued": false,
"reasoning": "Domain=Testing \u0026 Quality; The JD is centered on verification, traceability, test execution, reporting, reviews, and V\u0026V activities, with only limited automation mention, which best matches manual testing rather than automation or performance/security specialties.",
"sub_role": null
},
"stage5_updates": {
"centroid_n_after": 13,
"centroid_updated": true,
"collision_log_id": null,
"new_kra_attached": {
"best_kra_similarity": 0.0,
"queue_id": 2016,
"r_and_r_preview": "\u2022 Checklists tailoring and compliance verification for specific Lab/Estt. needs\n\u2022 Analysis of software code, design and related artifacts (code, documents, scripts) and preparation of reports\n\u2022 High l",
"role_display_name": "Manual Test Engineer",
"role_slug": "manual-test-engineer",
"status": "pending"
},
"new_skills_attached": [
{
"is_primary": true,
"queue_id": 25652,
"role_display_name": "Manual Test Engineer",
"role_slug": "manual-test-engineer",
"skill_name": "End-to-End Testing",
"status": "pending"
},
{
"is_primary": true,
"queue_id": 25653,
"role_display_name": "Manual Test Engineer",
"role_slug": "manual-test-engineer",
"skill_name": "Functional Testing",
"status": "pending"
},
{
"is_primary": false,
"queue_id": 25654,
"role_display_name": "Manual Test Engineer",
"role_slug": "manual-test-engineer",
"skill_name": "JUnit",
"status": "pending"
},
{
"is_primary": true,
"queue_id": 25655,
"role_display_name": "Manual Test Engineer",
"role_slug": "manual-test-engineer",
"skill_name": "Software Quality Metrics",
"status": "pending"
},
{
"is_primary": true,
"queue_id": 25656,
"role_display_name": "Manual Test Engineer",
"role_slug": "manual-test-engineer",
"skill_name": "Static Testing",
"status": "pending"
},
{
"is_primary": true,
"queue_id": 25657,
"role_display_name": "Manual Test Engineer",
"role_slug": "manual-test-engineer",
"skill_name": "System Testing",
"status": "pending"
},
{
"is_primary": true,
"queue_id": 25658,
"role_display_name": "Manual Test Engineer",
"role_slug": "manual-test-engineer",
"skill_name": "Test Automation",
"status": "pending"
},
{
"is_primary": true,
"queue_id": 25659,
"role_display_name": "Manual Test Engineer",
"role_slug": "manual-test-engineer",
"skill_name": "Test Case Design",
"status": "pending"
},
{
"is_primary": true,
"queue_id": 25660,
"role_display_name": "Manual Test Engineer",
"role_slug": "manual-test-engineer",
"skill_name": "Test Coverage",
"status": "pending"
},
{
"is_primary": true,
"queue_id": 25661,
"role_display_name": "Manual Test Engineer",
"role_slug": "manual-test-engineer",
"skill_name": "Test Data",
"status": "pending"
},
{
"is_primary": true,
"queue_id": 25662,
"role_display_name": "Manual Test Engineer",
"role_slug": "manual-test-engineer",
"skill_name": "Test Execution",
"status": "pending"
},
{
"is_primary": true,
"queue_id": 25663,
"role_display_name": "Manual Test Engineer",
"role_slug": "manual-test-engineer",
"skill_name": "Test Planning",
"status": "pending"
},
{
"is_primary": true,
"queue_id": 25664,
"role_display_name": "Manual Test Engineer",
"role_slug": "manual-test-engineer",
"skill_name": "Test Scripts",
"status": "pending"
},
{
"is_primary": true,
"queue_id": 25665,
"role_display_name": "Manual Test Engineer",
"role_slug": "manual-test-engineer",
"skill_name": "Verilog",
"status": "pending"
},
{
"is_primary": true,
"queue_id": 25666,
"role_display_name": "Manual Test Engineer",
"role_slug": "manual-test-engineer",
"skill_name": "VHDL",
"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": 868,
"existing_alias_text": "Agile",
"input_term": "Agile",
"matched_canonical": {
"category_id": 8,
"display_name": "Agile",
"id": 520,
"is_also_category": false,
"is_extractable": true,
"skill_nature": "METHODOLOGY",
"slug": "agile",
"sub_category_id": 3594,
"typical_lifespan": "EVERGREEN",
"volatility": "STABLE"
},
"matched_via": "alias"
},
{
"alias_persist_skipped_reason": "alias_text already exists for this canonical skill",
"alias_persisted": false,
"existing_alias_id": 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": 5905,
"existing_alias_text": "debugging",
"input_term": "Debugging",
"matched_canonical": {
"category_id": 8,
"display_name": "debugging",
"id": 4182,
"is_also_category": false,
"is_extractable": true,
"skill_nature": "METHODOLOGY",
"slug": "debugging",
"sub_category_id": 3293,
"typical_lifespan": "EVERGREEN",
"volatility": "STABLE"
},
"matched_via": "alias"
},
{
"alias_persist_skipped_reason": "TODO: REMOVE AFTER TESTING \u2014 alias DB write disabled",
"alias_persisted": false,
"existing_alias_id": 195,
"existing_alias_text": "end-to-end tests",
"input_term": "End-to-End Testing",
"matched_canonical": {
"category_id": 8,
"display_name": "end-to-end tests",
"id": 58,
"is_also_category": false,
"is_extractable": true,
"skill_nature": "METHODOLOGY",
"slug": "end-to-end-tests",
"sub_category_id": 44,
"typical_lifespan": "EVERGREEN",
"volatility": "STABLE"
},
"matched_via": "embedding_alias"
},
{
"alias_persist_skipped_reason": "TODO: REMOVE AFTER TESTING \u2014 alias DB write disabled",
"alias_persisted": false,
"existing_alias_id": 2945,
"existing_alias_text": "Integration testing",
"input_term": "Functional Testing",
"matched_canonical": {
"category_id": 8,
"display_name": "Integration testing",
"id": 56,
"is_also_category": false,
"is_extractable": true,
"skill_nature": "METHODOLOGY",
"slug": "integration-testing",
"sub_category_id": 44,
"typical_lifespan": "EVERGREEN",
"volatility": "STABLE"
},
"matched_via": "embedding_alias"
},
{
"alias_persist_skipped_reason": "alias_text already exists for this canonical skill",
"alias_persisted": false,
"existing_alias_id": 193,
"existing_alias_text": "integration testing",
"input_term": "Integration Testing",
"matched_canonical": {
"category_id": 8,
"display_name": "Integration testing",
"id": 56,
"is_also_category": false,
"is_extractable": true,
"skill_nature": "METHODOLOGY",
"slug": "integration-testing",
"sub_category_id": 44,
"typical_lifespan": "EVERGREEN",
"volatility": "STABLE"
},
"matched_via": "alias"
},
{
"alias_persist_skipped_reason": "alias_text already exists for this canonical skill",
"alias_persisted": false,
"existing_alias_id": 5380,
"existing_alias_text": "Regression testing",
"input_term": "Regression Testing",
"matched_canonical": {
"category_id": 8,
"display_name": "Regression testing",
"id": 3758,
"is_also_category": false,
"is_extractable": true,
"skill_nature": "METHODOLOGY",
"slug": "regression-testing",
"sub_category_id": 2940,
"typical_lifespan": "EVERGREEN",
"volatility": "STABLE"
},
"matched_via": "alias"
},
{
"alias_persist_skipped_reason": "TODO: REMOVE AFTER TESTING \u2014 alias DB write disabled",
"alias_persisted": false,
"existing_alias_id": 2945,
"existing_alias_text": "Integration testing",
"input_term": "System Testing",
"matched_canonical": {
"category_id": 8,
"display_name": "Integration testing",
"id": 56,
"is_also_category": false,
"is_extractable": true,
"skill_nature": "METHODOLOGY",
"slug": "integration-testing",
"sub_category_id": 44,
"typical_lifespan": "EVERGREEN",
"volatility": "STABLE"
},
"matched_via": "embedding_alias"
},
{
"alias_persist_skipped_reason": "alias_text already exists for this canonical skill",
"alias_persisted": false,
"existing_alias_id": 865,
"existing_alias_text": "Unit Testing",
"input_term": "Unit Testing",
"matched_canonical": {
"category_id": 8,
"display_name": "Unit Testing",
"id": 517,
"is_also_category": false,
"is_extractable": true,
"skill_nature": "METHODOLOGY",
"slug": "unit-testing",
"sub_category_id": 44,
"typical_lifespan": "EVERGREEN",
"volatility": "STABLE"
},
"matched_via": "alias"
}
],
"candidate_roles": [
{
"display_name": "Engineering Manager",
"id": 121,
"rationale": null,
"role_archetype": null,
"slug": "engineering-manager",
"source": "db"
},
{
"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": "Sitecore Dev",
"id": 233,
"rationale": null,
"role_archetype": "Engineering",
"slug": "sitecore-dev",
"source": "db"
},
{
"display_name": ".NET Backend Developer",
"id": 83,
"rationale": null,
"role_archetype": "Engineering",
"slug": "dotnet-backend-developer",
"source": "db"
},
{
"display_name": "Backend Developer",
"id": 1,
"rationale": null,
"role_archetype": "A Backend Engineer designs, builds, and maintains the server-side logic and data handling that power applications and services. They focus on implementing reliable business functionality, integrating with other systems, and ensuring the backend is scalable, maintainable, and observable.",
"slug": "backend-engineer",
"source": "db"
},
{
"display_name": "Node.js Backend Developer",
"id": 82,
"rationale": null,
"role_archetype": "Engineering",
"slug": "node-backend-developer",
"source": "db"
},
{
"display_name": "PHP Backend Developer",
"id": 86,
"rationale": null,
"role_archetype": "Engineering",
"slug": "php-backend-developer",
"source": "db"
},
{
"display_name": "Python Backend Developer",
"id": 80,
"rationale": null,
"role_archetype": "Engineering",
"slug": "python-backend-developer",
"source": "db"
},
{
"display_name": "Scala Backend Developer",
"id": 87,
"rationale": null,
"role_archetype": "Engineering",
"slug": "scala-backend-developer",
"source": "db"
},
{
"display_name": "Pega Developer",
"id": 24,
"rationale": null,
"role_archetype": null,
"slug": "pega-developer",
"source": "db"
},
{
"display_name": "Magento Dev",
"id": 231,
"rationale": null,
"role_archetype": "Engineering",
"slug": "magento-dev",
"source": "db"
}
],
"chosen_role": {
"display_name": "Manual Test Engineer",
"id": 65,
"rationale": "Domain=Testing \u0026 Quality; The JD is centered on verification, traceability, test execution, reporting, reviews, and V\u0026V activities, with only limited automation mention, which best matches manual testing rather than automation or performance/security specialties.",
"role_archetype": null,
"slug": "manual-test-engineer",
"source": "db"
},
"dimensions": [
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "React Frontend Development",
"id": 96,
"rationale": "Building interactive web user interfaces with React.js, including component composition, state management, hooks, and rendering patterns. React.js belongs here because it is a core library for client-side UI development in modern web applications.",
"slug": "d_init_01",
"source": "db"
},
"input_skill": "Agile",
"llm_role": null,
"roles_from_db": []
},
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Software Concepts, Patterns \u0026 Practices",
"id": 478,
"rationale": "Champion foundational software design patterns, development methodologies, and engineering best practices.",
"slug": "software-concepts-patterns-practices",
"source": "db"
},
"input_skill": "Agile",
"llm_role": null,
"roles_from_db": [
{
"display_name": "Engineering Manager",
"id": 121,
"rationale": null,
"role_archetype": null,
"slug": "engineering-manager",
"source": "db"
}
]
},
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "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": "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": "Debugging",
"llm_role": null,
"roles_from_db": [
{
"display_name": "Sitecore Dev",
"id": 233,
"rationale": null,
"role_archetype": "Engineering",
"slug": "sitecore-dev",
"source": "db"
}
]
},
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Testing and Quality Assurance",
"id": 12,
"rationale": "Backend-specific test strategies used to validate service behavior and integration points. Covers automated test layers, contract checks, fixtures, and regression prevention.",
"slug": "testing-and-quality-assurance",
"source": "db"
},
"input_skill": "End-to-End Testing",
"llm_role": null,
"roles_from_db": [
{
"display_name": ".NET Backend Developer",
"id": 83,
"rationale": null,
"role_archetype": "Engineering",
"slug": "dotnet-backend-developer",
"source": "db"
},
{
"display_name": "Backend Developer",
"id": 1,
"rationale": null,
"role_archetype": "A Backend Engineer designs, builds, and maintains the server-side logic and data handling that power applications and services. They focus on implementing reliable business functionality, integrating with other systems, and ensuring the backend is scalable, maintainable, and observable.",
"slug": "backend-engineer",
"source": "db"
},
{
"display_name": "Node.js Backend Developer",
"id": 82,
"rationale": null,
"role_archetype": "Engineering",
"slug": "node-backend-developer",
"source": "db"
},
{
"display_name": "PHP Backend Developer",
"id": 86,
"rationale": null,
"role_archetype": "Engineering",
"slug": "php-backend-developer",
"source": "db"
},
{
"display_name": "Python Backend Developer",
"id": 80,
"rationale": null,
"role_archetype": "Engineering",
"slug": "python-backend-developer",
"source": "db"
},
{
"display_name": "Scala Backend Developer",
"id": 87,
"rationale": null,
"role_archetype": "Engineering",
"slug": "scala-backend-developer",
"source": "db"
}
]
},
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Testing and Defect Resolution",
"id": 262,
"rationale": "Validates Pega rules, flows, and integrations and then troubleshoots defects found in lower environments or production. This is a coherent cluster because the role is expected to verify platform behavior and fix rule-level issues.",
"slug": "testing-and-defect-resolution",
"source": "db"
},
"input_skill": "Functional Testing",
"llm_role": null,
"roles_from_db": [
{
"display_name": "Pega Developer",
"id": 24,
"rationale": null,
"role_archetype": null,
"slug": "pega-developer",
"source": "db"
}
]
},
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Testing and Quality Assurance",
"id": 12,
"rationale": "Backend-specific test strategies used to validate service behavior and integration points. Covers automated test layers, contract checks, fixtures, and regression prevention.",
"slug": "testing-and-quality-assurance",
"source": "db"
},
"input_skill": "Functional Testing",
"llm_role": null,
"roles_from_db": [
{
"display_name": ".NET Backend Developer",
"id": 83,
"rationale": null,
"role_archetype": "Engineering",
"slug": "dotnet-backend-developer",
"source": "db"
},
{
"display_name": "Backend Developer",
"id": 1,
"rationale": null,
"role_archetype": "A Backend Engineer designs, builds, and maintains the server-side logic and data handling that power applications and services. They focus on implementing reliable business functionality, integrating with other systems, and ensuring the backend is scalable, maintainable, and observable.",
"slug": "backend-engineer",
"source": "db"
},
{
"display_name": "Node.js Backend Developer",
"id": 82,
"rationale": null,
"role_archetype": "Engineering",
"slug": "node-backend-developer",
"source": "db"
},
{
"display_name": "PHP Backend Developer",
"id": 86,
"rationale": null,
"role_archetype": "Engineering",
"slug": "php-backend-developer",
"source": "db"
},
{
"display_name": "Python Backend Developer",
"id": 80,
"rationale": null,
"role_archetype": "Engineering",
"slug": "python-backend-developer",
"source": "db"
},
{
"display_name": "Scala Backend Developer",
"id": 87,
"rationale": null,
"role_archetype": "Engineering",
"slug": "scala-backend-developer",
"source": "db"
}
]
},
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Testing and Defect Resolution",
"id": 262,
"rationale": "Validates Pega rules, flows, and integrations and then troubleshoots defects found in lower environments or production. This is a coherent cluster because the role is expected to verify platform behavior and fix rule-level issues.",
"slug": "testing-and-defect-resolution",
"source": "db"
},
"input_skill": "Integration Testing",
"llm_role": null,
"roles_from_db": [
{
"display_name": "Pega Developer",
"id": 24,
"rationale": null,
"role_archetype": null,
"slug": "pega-developer",
"source": "db"
}
]
},
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Testing and Quality Assurance",
"id": 12,
"rationale": "Backend-specific test strategies used to validate service behavior and integration points. Covers automated test layers, contract checks, fixtures, and regression prevention.",
"slug": "testing-and-quality-assurance",
"source": "db"
},
"input_skill": "Integration Testing",
"llm_role": null,
"roles_from_db": [
{
"display_name": ".NET Backend Developer",
"id": 83,
"rationale": null,
"role_archetype": "Engineering",
"slug": "dotnet-backend-developer",
"source": "db"
},
{
"display_name": "Backend Developer",
"id": 1,
"rationale": null,
"role_archetype": "A Backend Engineer designs, builds, and maintains the server-side logic and data handling that power applications and services. They focus on implementing reliable business functionality, integrating with other systems, and ensuring the backend is scalable, maintainable, and observable.",
"slug": "backend-engineer",
"source": "db"
},
{
"display_name": "Node.js Backend Developer",
"id": 82,
"rationale": null,
"role_archetype": "Engineering",
"slug": "node-backend-developer",
"source": "db"
},
{
"display_name": "PHP Backend Developer",
"id": 86,
"rationale": null,
"role_archetype": "Engineering",
"slug": "php-backend-developer",
"source": "db"
},
{
"display_name": "Python Backend Developer",
"id": 80,
"rationale": null,
"role_archetype": "Engineering",
"slug": "python-backend-developer",
"source": "db"
},
{
"display_name": "Scala Backend Developer",
"id": 87,
"rationale": null,
"role_archetype": "Engineering",
"slug": "scala-backend-developer",
"source": "db"
}
]
},
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Magento Testing and Upgrade Safety",
"id": 405,
"rationale": "Validation practices used to keep Magento customizations stable across releases and platform upgrades. This cluster is coherent because Magento work must protect storefront behavior while remaining compatible with core and extension updates.",
"slug": "magento-testing-and-upgrade-safety",
"source": "db"
},
"input_skill": "Regression Testing",
"llm_role": null,
"roles_from_db": [
{
"display_name": "Magento Dev",
"id": 231,
"rationale": null,
"role_archetype": "Engineering",
"slug": "magento-dev",
"source": "db"
}
]
},
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Testing and Defect Resolution",
"id": 262,
"rationale": "Validates Pega rules, flows, and integrations and then troubleshoots defects found in lower environments or production. This is a coherent cluster because the role is expected to verify platform behavior and fix rule-level issues.",
"slug": "testing-and-defect-resolution",
"source": "db"
},
"input_skill": "System Testing",
"llm_role": null,
"roles_from_db": [
{
"display_name": "Pega Developer",
"id": 24,
"rationale": null,
"role_archetype": null,
"slug": "pega-developer",
"source": "db"
}
]
},
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Testing and Quality Assurance",
"id": 12,
"rationale": "Backend-specific test strategies used to validate service behavior and integration points. Covers automated test layers, contract checks, fixtures, and regression prevention.",
"slug": "testing-and-quality-assurance",
"source": "db"
},
"input_skill": "System Testing",
"llm_role": null,
"roles_from_db": [
{
"display_name": ".NET Backend Developer",
"id": 83,
"rationale": null,
"role_archetype": "Engineering",
"slug": "dotnet-backend-developer",
"source": "db"
},
{
"display_name": "Backend Developer",
"id": 1,
"rationale": null,
"role_archetype": "A Backend Engineer designs, builds, and maintains the server-side logic and data handling that power applications and services. They focus on implementing reliable business functionality, integrating with other systems, and ensuring the backend is scalable, maintainable, and observable.",
"slug": "backend-engineer",
"source": "db"
},
{
"display_name": "Node.js Backend Developer",
"id": 82,
"rationale": null,
"role_archetype": "Engineering",
"slug": "node-backend-developer",
"source": "db"
},
{
"display_name": "PHP Backend Developer",
"id": 86,
"rationale": null,
"role_archetype": "Engineering",
"slug": "php-backend-developer",
"source": "db"
},
{
"display_name": "Python Backend Developer",
"id": 80,
"rationale": null,
"role_archetype": "Engineering",
"slug": "python-backend-developer",
"source": "db"
},
{
"display_name": "Scala Backend Developer",
"id": 87,
"rationale": null,
"role_archetype": "Engineering",
"slug": "scala-backend-developer",
"source": "db"
}
]
},
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "React Frontend Development",
"id": 96,
"rationale": "Building interactive web user interfaces with React.js, including component composition, state management, hooks, and rendering patterns. React.js belongs here because it is a core library for client-side UI development in modern web applications.",
"slug": "d_init_01",
"source": "db"
},
"input_skill": "Unit Testing",
"llm_role": null,
"roles_from_db": []
}
],
"input_final_skills": [
"Agile",
"CI/CD",
"Debugging",
"End-to-End Testing",
"Functional Testing",
"Integration Testing",
"JUnit",
"Regression Testing",
"Software Quality Metrics",
"Static Testing",
"System Testing",
"Test Automation",
"Test Case Design",
"Test Coverage",
"Test Data",
"Test Execution",
"Test Planning",
"Test Scripts",
"Unit Testing",
"Verilog",
"VHDL"
],
"input_llm_skills": [
"Agile",
"CI/CD",
"Debugging",
"End-to-End Testing",
"Functional Testing",
"Integration Testing",
"JUnit",
"Regression Testing",
"Software Quality Metrics",
"Static Testing",
"System Testing",
"Test Automation",
"Test Case Design",
"Test Coverage",
"Test Data",
"Test Execution",
"Test Planning",
"Test Scripts",
"Unit Testing",
"Verilog",
"VHDL"
],
"new_aliases_persisted": 0,
"run_id": "91515540-2d18-424c-95a5-337c30a51070",
"skills_detail": [
{
"aliases_in_db": [
{
"alias_text": "Agile",
"alias_type": "CANONICAL",
"id": 868,
"is_primary": true,
"match_strategy": "CASE_INSENSITIVE"
}
],
"canonical": {
"category_id": 8,
"display_name": "Agile",
"id": 520,
"is_also_category": false,
"is_extractable": true,
"skill_nature": "METHODOLOGY",
"slug": "agile",
"sub_category_id": 3594,
"typical_lifespan": "EVERGREEN",
"volatility": "STABLE"
},
"dimensions": [
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "React Frontend Development",
"id": 96,
"rationale": "Building interactive web user interfaces with React.js, including component composition, state management, hooks, and rendering patterns. React.js belongs here because it is a core library for client-side UI development in modern web applications.",
"slug": "d_init_01",
"source": "db"
},
"input_skill": "Agile",
"llm_role": null,
"roles_from_db": []
},
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Software Concepts, Patterns \u0026 Practices",
"id": 478,
"rationale": "Champion foundational software design patterns, development methodologies, and engineering best practices.",
"slug": "software-concepts-patterns-practices",
"source": "db"
},
"input_skill": "Agile",
"llm_role": null,
"roles_from_db": [
{
"display_name": "Engineering Manager",
"id": 121,
"rationale": null,
"role_archetype": null,
"slug": "engineering-manager",
"source": "db"
}
]
}
],
"input_skill": "Agile",
"matched_via": "alias",
"new_alias_persisted": false,
"new_alias_text": null,
"new_skill_meta": null,
"source_tag": "db",
"was_in_llm_skills": true
},
{
"aliases_in_db": [
{
"alias_text": "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": "debugging",
"alias_type": "CANONICAL",
"id": 5905,
"is_primary": true,
"match_strategy": "CASE_INSENSITIVE"
}
],
"canonical": {
"category_id": 8,
"display_name": "debugging",
"id": 4182,
"is_also_category": false,
"is_extractable": true,
"skill_nature": "METHODOLOGY",
"slug": "debugging",
"sub_category_id": 3293,
"typical_lifespan": "EVERGREEN",
"volatility": "STABLE"
},
"dimensions": [
{
"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": "Debugging",
"llm_role": null,
"roles_from_db": [
{
"display_name": "Sitecore Dev",
"id": 233,
"rationale": null,
"role_archetype": "Engineering",
"slug": "sitecore-dev",
"source": "db"
}
]
}
],
"input_skill": "Debugging",
"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": "end-to-end tests",
"alias_type": "CANONICAL",
"id": 195,
"is_primary": true,
"match_strategy": "CASE_INSENSITIVE"
}
],
"canonical": {
"category_id": 8,
"display_name": "end-to-end tests",
"id": 58,
"is_also_category": false,
"is_extractable": true,
"skill_nature": "METHODOLOGY",
"slug": "end-to-end-tests",
"sub_category_id": 44,
"typical_lifespan": "EVERGREEN",
"volatility": "STABLE"
},
"dimensions": [
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Testing and Quality Assurance",
"id": 12,
"rationale": "Backend-specific test strategies used to validate service behavior and integration points. Covers automated test layers, contract checks, fixtures, and regression prevention.",
"slug": "testing-and-quality-assurance",
"source": "db"
},
"input_skill": "End-to-End Testing",
"llm_role": null,
"roles_from_db": [
{
"display_name": ".NET Backend Developer",
"id": 83,
"rationale": null,
"role_archetype": "Engineering",
"slug": "dotnet-backend-developer",
"source": "db"
},
{
"display_name": "Backend Developer",
"id": 1,
"rationale": null,
"role_archetype": "A Backend Engineer designs, builds, and maintains the server-side logic and data handling that power applications and services. They focus on implementing reliable business functionality, integrating with other systems, and ensuring the backend is scalable, maintainable, and observable.",
"slug": "backend-engineer",
"source": "db"
},
{
"display_name": "Node.js Backend Developer",
"id": 82,
"rationale": null,
"role_archetype": "Engineering",
"slug": "node-backend-developer",
"source": "db"
},
{
"display_name": "PHP Backend Developer",
"id": 86,
"rationale": null,
"role_archetype": "Engineering",
"slug": "php-backend-developer",
"source": "db"
},
{
"display_name": "Python Backend Developer",
"id": 80,
"rationale": null,
"role_archetype": "Engineering",
"slug": "python-backend-developer",
"source": "db"
},
{
"display_name": "Scala Backend Developer",
"id": 87,
"rationale": null,
"role_archetype": "Engineering",
"slug": "scala-backend-developer",
"source": "db"
}
]
}
],
"input_skill": "End-to-End Testing",
"matched_via": "embedding_alias",
"new_alias_persisted": false,
"new_alias_text": null,
"new_skill_meta": null,
"source_tag": "db",
"was_in_llm_skills": true
},
{
"aliases_in_db": [
{
"alias_text": "Integration testing",
"alias_type": "CANONICAL",
"id": 2945,
"is_primary": true,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "integration testing",
"alias_type": "CANONICAL",
"id": 193,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
}
],
"canonical": {
"category_id": 8,
"display_name": "Integration testing",
"id": 56,
"is_also_category": false,
"is_extractable": true,
"skill_nature": "METHODOLOGY",
"slug": "integration-testing",
"sub_category_id": 44,
"typical_lifespan": "EVERGREEN",
"volatility": "STABLE"
},
"dimensions": [
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Testing and Defect Resolution",
"id": 262,
"rationale": "Validates Pega rules, flows, and integrations and then troubleshoots defects found in lower environments or production. This is a coherent cluster because the role is expected to verify platform behavior and fix rule-level issues.",
"slug": "testing-and-defect-resolution",
"source": "db"
},
"input_skill": "Functional Testing",
"llm_role": null,
"roles_from_db": [
{
"display_name": "Pega Developer",
"id": 24,
"rationale": null,
"role_archetype": null,
"slug": "pega-developer",
"source": "db"
}
]
},
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Testing and Quality Assurance",
"id": 12,
"rationale": "Backend-specific test strategies used to validate service behavior and integration points. Covers automated test layers, contract checks, fixtures, and regression prevention.",
"slug": "testing-and-quality-assurance",
"source": "db"
},
"input_skill": "Functional Testing",
"llm_role": null,
"roles_from_db": [
{
"display_name": ".NET Backend Developer",
"id": 83,
"rationale": null,
"role_archetype": "Engineering",
"slug": "dotnet-backend-developer",
"source": "db"
},
{
"display_name": "Backend Developer",
"id": 1,
"rationale": null,
"role_archetype": "A Backend Engineer designs, builds, and maintains the server-side logic and data handling that power applications and services. They focus on implementing reliable business functionality, integrating with other systems, and ensuring the backend is scalable, maintainable, and observable.",
"slug": "backend-engineer",
"source": "db"
},
{
"display_name": "Node.js Backend Developer",
"id": 82,
"rationale": null,
"role_archetype": "Engineering",
"slug": "node-backend-developer",
"source": "db"
},
{
"display_name": "PHP Backend Developer",
"id": 86,
"rationale": null,
"role_archetype": "Engineering",
"slug": "php-backend-developer",
"source": "db"
},
{
"display_name": "Python Backend Developer",
"id": 80,
"rationale": null,
"role_archetype": "Engineering",
"slug": "python-backend-developer",
"source": "db"
},
{
"display_name": "Scala Backend Developer",
"id": 87,
"rationale": null,
"role_archetype": "Engineering",
"slug": "scala-backend-developer",
"source": "db"
}
]
}
],
"input_skill": "Functional Testing",
"matched_via": "embedding_alias",
"new_alias_persisted": false,
"new_alias_text": null,
"new_skill_meta": null,
"source_tag": "db",
"was_in_llm_skills": true
},
{
"aliases_in_db": [
{
"alias_text": "Integration testing",
"alias_type": "CANONICAL",
"id": 2945,
"is_primary": true,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "integration testing",
"alias_type": "CANONICAL",
"id": 193,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
}
],
"canonical": {
"category_id": 8,
"display_name": "Integration testing",
"id": 56,
"is_also_category": false,
"is_extractable": true,
"skill_nature": "METHODOLOGY",
"slug": "integration-testing",
"sub_category_id": 44,
"typical_lifespan": "EVERGREEN",
"volatility": "STABLE"
},
"dimensions": [
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Testing and Defect Resolution",
"id": 262,
"rationale": "Validates Pega rules, flows, and integrations and then troubleshoots defects found in lower environments or production. This is a coherent cluster because the role is expected to verify platform behavior and fix rule-level issues.",
"slug": "testing-and-defect-resolution",
"source": "db"
},
"input_skill": "Integration Testing",
"llm_role": null,
"roles_from_db": [
{
"display_name": "Pega Developer",
"id": 24,
"rationale": null,
"role_archetype": null,
"slug": "pega-developer",
"source": "db"
}
]
},
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Testing and Quality Assurance",
"id": 12,
"rationale": "Backend-specific test strategies used to validate service behavior and integration points. Covers automated test layers, contract checks, fixtures, and regression prevention.",
"slug": "testing-and-quality-assurance",
"source": "db"
},
"input_skill": "Integration Testing",
"llm_role": null,
"roles_from_db": [
{
"display_name": ".NET Backend Developer",
"id": 83,
"rationale": null,
"role_archetype": "Engineering",
"slug": "dotnet-backend-developer",
"source": "db"
},
{
"display_name": "Backend Developer",
"id": 1,
"rationale": null,
"role_archetype": "A Backend Engineer designs, builds, and maintains the server-side logic and data handling that power applications and services. They focus on implementing reliable business functionality, integrating with other systems, and ensuring the backend is scalable, maintainable, and observable.",
"slug": "backend-engineer",
"source": "db"
},
{
"display_name": "Node.js Backend Developer",
"id": 82,
"rationale": null,
"role_archetype": "Engineering",
"slug": "node-backend-developer",
"source": "db"
},
{
"display_name": "PHP Backend Developer",
"id": 86,
"rationale": null,
"role_archetype": "Engineering",
"slug": "php-backend-developer",
"source": "db"
},
{
"display_name": "Python Backend Developer",
"id": 80,
"rationale": null,
"role_archetype": "Engineering",
"slug": "python-backend-developer",
"source": "db"
},
{
"display_name": "Scala Backend Developer",
"id": 87,
"rationale": null,
"role_archetype": "Engineering",
"slug": "scala-backend-developer",
"source": "db"
}
]
}
],
"input_skill": "Integration Testing",
"matched_via": "alias",
"new_alias_persisted": false,
"new_alias_text": null,
"new_skill_meta": null,
"source_tag": "db",
"was_in_llm_skills": true
},
{
"aliases_in_db": [],
"canonical": null,
"dimensions": [],
"input_skill": "JUnit",
"matched_via": null,
"new_alias_persisted": false,
"new_alias_text": null,
"new_skill_meta": {
"derived": {
"category": "Testing Tools",
"skill_nature": "TOOL",
"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": "junit",
"split_log": [],
"typed": null,
"warnings": []
},
"source_tag": "llm",
"was_in_llm_skills": true
},
{
"aliases_in_db": [
{
"alias_text": "Regression testing",
"alias_type": "CANONICAL",
"id": 5380,
"is_primary": true,
"match_strategy": "CASE_INSENSITIVE"
}
],
"canonical": {
"category_id": 8,
"display_name": "Regression testing",
"id": 3758,
"is_also_category": false,
"is_extractable": true,
"skill_nature": "METHODOLOGY",
"slug": "regression-testing",
"sub_category_id": 2940,
"typical_lifespan": "EVERGREEN",
"volatility": "STABLE"
},
"dimensions": [
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Magento Testing and Upgrade Safety",
"id": 405,
"rationale": "Validation practices used to keep Magento customizations stable across releases and platform upgrades. This cluster is coherent because Magento work must protect storefront behavior while remaining compatible with core and extension updates.",
"slug": "magento-testing-and-upgrade-safety",
"source": "db"
},
"input_skill": "Regression Testing",
"llm_role": null,
"roles_from_db": [
{
"display_name": "Magento Dev",
"id": 231,
"rationale": null,
"role_archetype": "Engineering",
"slug": "magento-dev",
"source": "db"
}
]
}
],
"input_skill": "Regression Testing",
"matched_via": "alias",
"new_alias_persisted": false,
"new_alias_text": null,
"new_skill_meta": null,
"source_tag": "db",
"was_in_llm_skills": true
},
{
"aliases_in_db": [],
"canonical": null,
"dimensions": [],
"input_skill": "Software Quality Metrics",
"matched_via": null,
"new_alias_persisted": false,
"new_alias_text": null,
"new_skill_meta": {
"derived": {
"category": "Concepts",
"skill_nature": "CONCEPT",
"sub_category": "general",
"typical_lifespan": "EVERGREEN",
"version_strategy": "UNVERSIONED",
"volatility": "STABLE"
},
"enrichment": null,
"keep_log": [],
"locked_dimensions": [],
"merge_log": [],
"placed": null,
"relationships": null,
"skill_id": "software-quality-metrics",
"split_log": [],
"typed": null,
"warnings": []
},
"source_tag": "llm",
"was_in_llm_skills": true
},
{
"aliases_in_db": [],
"canonical": null,
"dimensions": [],
"input_skill": "Static 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": "EVERGREEN",
"version_strategy": "UNVERSIONED",
"volatility": "STABLE"
},
"enrichment": null,
"keep_log": [],
"locked_dimensions": [],
"merge_log": [],
"placed": null,
"relationships": null,
"skill_id": "static-testing",
"split_log": [],
"typed": null,
"warnings": []
},
"source_tag": "llm",
"was_in_llm_skills": true
},
{
"aliases_in_db": [
{
"alias_text": "Integration testing",
"alias_type": "CANONICAL",
"id": 2945,
"is_primary": true,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "integration testing",
"alias_type": "CANONICAL",
"id": 193,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
}
],
"canonical": {
"category_id": 8,
"display_name": "Integration testing",
"id": 56,
"is_also_category": false,
"is_extractable": true,
"skill_nature": "METHODOLOGY",
"slug": "integration-testing",
"sub_category_id": 44,
"typical_lifespan": "EVERGREEN",
"volatility": "STABLE"
},
"dimensions": [
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Testing and Defect Resolution",
"id": 262,
"rationale": "Validates Pega rules, flows, and integrations and then troubleshoots defects found in lower environments or production. This is a coherent cluster because the role is expected to verify platform behavior and fix rule-level issues.",
"slug": "testing-and-defect-resolution",
"source": "db"
},
"input_skill": "System Testing",
"llm_role": null,
"roles_from_db": [
{
"display_name": "Pega Developer",
"id": 24,
"rationale": null,
"role_archetype": null,
"slug": "pega-developer",
"source": "db"
}
]
},
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Testing and Quality Assurance",
"id": 12,
"rationale": "Backend-specific test strategies used to validate service behavior and integration points. Covers automated test layers, contract checks, fixtures, and regression prevention.",
"slug": "testing-and-quality-assurance",
"source": "db"
},
"input_skill": "System Testing",
"llm_role": null,
"roles_from_db": [
{
"display_name": ".NET Backend Developer",
"id": 83,
"rationale": null,
"role_archetype": "Engineering",
"slug": "dotnet-backend-developer",
"source": "db"
},
{
"display_name": "Backend Developer",
"id": 1,
"rationale": null,
"role_archetype": "A Backend Engineer designs, builds, and maintains the server-side logic and data handling that power applications and services. They focus on implementing reliable business functionality, integrating with other systems, and ensuring the backend is scalable, maintainable, and observable.",
"slug": "backend-engineer",
"source": "db"
},
{
"display_name": "Node.js Backend Developer",
"id": 82,
"rationale": null,
"role_archetype": "Engineering",
"slug": "node-backend-developer",
"source": "db"
},
{
"display_name": "PHP Backend Developer",
"id": 86,
"rationale": null,
"role_archetype": "Engineering",
"slug": "php-backend-developer",
"source": "db"
},
{
"display_name": "Python Backend Developer",
"id": 80,
"rationale": null,
"role_archetype": "Engineering",
"slug": "python-backend-developer",
"source": "db"
},
{
"display_name": "Scala Backend Developer",
"id": 87,
"rationale": null,
"role_archetype": "Engineering",
"slug": "scala-backend-developer",
"source": "db"
}
]
}
],
"input_skill": "System Testing",
"matched_via": "embedding_alias",
"new_alias_persisted": false,
"new_alias_text": null,
"new_skill_meta": null,
"source_tag": "db",
"was_in_llm_skills": true
},
{
"aliases_in_db": [],
"canonical": null,
"dimensions": [],
"input_skill": "Test Automation",
"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": "test-automation",
"split_log": [],
"typed": null,
"warnings": []
},
"source_tag": "llm",
"was_in_llm_skills": true
},
{
"aliases_in_db": [],
"canonical": null,
"dimensions": [],
"input_skill": "Test Case Design",
"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": "EVERGREEN",
"version_strategy": "UNVERSIONED",
"volatility": "STABLE"
},
"enrichment": null,
"keep_log": [],
"locked_dimensions": [],
"merge_log": [],
"placed": null,
"relationships": null,
"skill_id": "test-case-design",
"split_log": [],
"typed": null,
"warnings": []
},
"source_tag": "llm",
"was_in_llm_skills": true
},
{
"aliases_in_db": [],
"canonical": null,
"dimensions": [],
"input_skill": "Test Coverage",
"matched_via": null,
"new_alias_persisted": false,
"new_alias_text": null,
"new_skill_meta": {
"derived": {
"category": "Concepts",
"skill_nature": "CONCEPT",
"sub_category": "general",
"typical_lifespan": "EVERGREEN",
"version_strategy": "UNVERSIONED",
"volatility": "STABLE"
},
"enrichment": null,
"keep_log": [],
"locked_dimensions": [],
"merge_log": [],
"placed": null,
"relationships": null,
"skill_id": "test-coverage",
"split_log": [],
"typed": null,
"warnings": []
},
"source_tag": "llm",
"was_in_llm_skills": true
},
{
"aliases_in_db": [],
"canonical": null,
"dimensions": [],
"input_skill": "Test Data",
"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": "test-data",
"split_log": [],
"typed": null,
"warnings": []
},
"source_tag": "llm",
"was_in_llm_skills": true
},
{
"aliases_in_db": [],
"canonical": null,
"dimensions": [],
"input_skill": "Test Execution",
"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": "EVERGREEN",
"version_strategy": "UNVERSIONED",
"volatility": "STABLE"
},
"enrichment": null,
"keep_log": [],
"locked_dimensions": [],
"merge_log": [],
"placed": null,
"relationships": null,
"skill_id": "test-execution",
"split_log": [],
"typed": null,
"warnings": []
},
"source_tag": "llm",
"was_in_llm_skills": true
},
{
"aliases_in_db": [],
"canonical": null,
"dimensions": [],
"input_skill": "Test Planning",
"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": "EVERGREEN",
"version_strategy": "UNVERSIONED",
"volatility": "STABLE"
},
"enrichment": null,
"keep_log": [],
"locked_dimensions": [],
"merge_log": [],
"placed": null,
"relationships": null,
"skill_id": "test-planning",
"split_log": [],
"typed": null,
"warnings": []
},
"source_tag": "llm",
"was_in_llm_skills": true
},
{
"aliases_in_db": [],
"canonical": null,
"dimensions": [],
"input_skill": "Test Scripts",
"matched_via": null,
"new_alias_persisted": false,
"new_alias_text": null,
"new_skill_meta": {
"derived": {
"category": "Testing Tools",
"skill_nature": "TOOL",
"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": "test-scripts",
"split_log": [],
"typed": null,
"warnings": []
},
"source_tag": "llm",
"was_in_llm_skills": true
},
{
"aliases_in_db": [
{
"alias_text": "Unit Testing",
"alias_type": "CANONICAL",
"id": 865,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
}
],
"canonical": {
"category_id": 8,
"display_name": "Unit Testing",
"id": 517,
"is_also_category": false,
"is_extractable": true,
"skill_nature": "METHODOLOGY",
"slug": "unit-testing",
"sub_category_id": 44,
"typical_lifespan": "EVERGREEN",
"volatility": "STABLE"
},
"dimensions": [
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "React Frontend Development",
"id": 96,
"rationale": "Building interactive web user interfaces with React.js, including component composition, state management, hooks, and rendering patterns. React.js belongs here because it is a core library for client-side UI development in modern web applications.",
"slug": "d_init_01",
"source": "db"
},
"input_skill": "Unit Testing",
"llm_role": null,
"roles_from_db": []
}
],
"input_skill": "Unit Testing",
"matched_via": "alias",
"new_alias_persisted": false,
"new_alias_text": null,
"new_skill_meta": null,
"source_tag": "db",
"was_in_llm_skills": true
},
{
"aliases_in_db": [],
"canonical": null,
"dimensions": [],
"input_skill": "Verilog",
"matched_via": null,
"new_alias_persisted": false,
"new_alias_text": null,
"new_skill_meta": {
"derived": {
"category": "Programming Languages",
"skill_nature": "LANGUAGE",
"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": "verilog",
"split_log": [],
"typed": null,
"warnings": []
},
"source_tag": "llm",
"was_in_llm_skills": true
},
{
"aliases_in_db": [],
"canonical": null,
"dimensions": [],
"input_skill": "VHDL",
"matched_via": null,
"new_alias_persisted": false,
"new_alias_text": null,
"new_skill_meta": {
"derived": {
"category": "Programming Languages",
"skill_nature": "LANGUAGE",
"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": "vhdl",
"split_log": [],
"typed": null,
"warnings": []
},
"source_tag": "llm",
"was_in_llm_skills": true
}
],
"unmatched_skills": [
"JUnit",
"Software Quality Metrics",
"Static Testing",
"Test Automation",
"Test Case Design",
"Test Coverage",
"Test Data",
"Test Execution",
"Test Planning",
"Test Scripts",
"Verilog",
"VHDL"
]
}
API 3 — final-role-output
{
"chosen_role": {
"display_name": "Manual Test Engineer",
"id": 65,
"rationale": "Domain=Testing \u0026 Quality; The JD is centered on verification, traceability, test execution, reporting, reviews, and V\u0026V activities, with only limited automation mention, which best matches manual testing rather than automation or performance/security specialties.",
"role_archetype": null,
"slug": "manual-test-engineer",
"source": "db"
},
"chosen_role_resolution": "in_db",
"final_input_skills": [
{
"skill": "Agile",
"tag": "in_db"
},
{
"skill": "CI/CD",
"tag": "in_db"
},
{
"skill": "Debugging",
"tag": "in_db"
},
{
"skill": "End-to-End Testing",
"tag": "in_db"
},
{
"skill": "Functional Testing",
"tag": "in_db"
},
{
"skill": "Integration Testing",
"tag": "in_db"
},
{
"skill": "JUnit",
"tag": "new"
},
{
"skill": "Regression Testing",
"tag": "in_db"
},
{
"skill": "Software Quality Metrics",
"tag": "new"
},
{
"skill": "Static Testing",
"tag": "new"
},
{
"skill": "System Testing",
"tag": "in_db"
},
{
"skill": "Test Automation",
"tag": "new"
},
{
"skill": "Test Case Design",
"tag": "new"
},
{
"skill": "Test Coverage",
"tag": "new"
},
{
"skill": "Test Data",
"tag": "new"
},
{
"skill": "Test Execution",
"tag": "new"
},
{
"skill": "Test Planning",
"tag": "new"
},
{
"skill": "Test Scripts",
"tag": "new"
},
{
"skill": "Unit Testing",
"tag": "in_db"
},
{
"skill": "Verilog",
"tag": "new"
},
{
"skill": "VHDL",
"tag": "new"
}
],
"llm_cost_api1_usd": null,
"llm_cost_api2_usd": null,
"llm_cost_api3_usd": null,
"llm_cost_total_usd": null,
"persistence": {
"items": [
{
"chosen_role_id": 65,
"dimension": {
"difficulty_hint": "well_known",
"display_name": "React Frontend Development",
"id": 96,
"rationale": "Building interactive web user interfaces with React.js, including component composition, state management, hooks, and rendering patterns. React.js belongs here because it is a core library for client-side UI development in modern web applications.",
"slug": "d_init_01",
"source": "db"
},
"dimension_id": 96,
"input_skill": "Agile",
"llm_role": null,
"matched_chosen_role": false,
"outcome_line": "Existing dimension (library) \u00b7 Role\u2194dimension skipped (dimension not under chosen role)",
"role_dimension_saved": false,
"roles_from_db": [],
"skill_dimension_saved": true,
"skill_id": 520,
"skill_tag": "in_db",
"skipped_reason": null
},
{
"chosen_role_id": 65,
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Software Concepts, Patterns \u0026 Practices",
"id": 478,
"rationale": "Champion foundational software design patterns, development methodologies, and engineering best practices.",
"slug": "software-concepts-patterns-practices",
"source": "db"
},
"dimension_id": 478,
"input_skill": "Agile",
"llm_role": null,
"matched_chosen_role": false,
"outcome_line": "Existing dimension (library) \u00b7 Role\u2194dimension skipped (dimension not under chosen role)",
"role_dimension_saved": false,
"roles_from_db": [
{
"display_name": "Engineering Manager",
"id": 121,
"rationale": null,
"role_archetype": null,
"slug": "engineering-manager",
"source": "db"
}
],
"skill_dimension_saved": true,
"skill_id": 520,
"skill_tag": "in_db",
"skipped_reason": null
},
{
"chosen_role_id": 65,
"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": 65,
"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": 65,
"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": "Debugging",
"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": 4182,
"skill_tag": "in_db",
"skipped_reason": null
},
{
"chosen_role_id": 65,
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Testing and Quality Assurance",
"id": 12,
"rationale": "Backend-specific test strategies used to validate service behavior and integration points. Covers automated test layers, contract checks, fixtures, and regression prevention.",
"slug": "testing-and-quality-assurance",
"source": "db"
},
"dimension_id": 12,
"input_skill": "End-to-End Testing",
"llm_role": null,
"matched_chosen_role": false,
"outcome_line": "Skipped \u2014 no persistable v3 meta for new skill",
"role_dimension_saved": false,
"roles_from_db": [
{
"display_name": ".NET Backend Developer",
"id": 83,
"rationale": null,
"role_archetype": "Engineering",
"slug": "dotnet-backend-developer",
"source": "db"
},
{
"display_name": "Backend Developer",
"id": 1,
"rationale": null,
"role_archetype": "A Backend Engineer designs, builds, and maintains the server-side logic and data handling that power applications and services. They focus on implementing reliable business functionality, integrating with other systems, and ensuring the backend is scalable, maintainable, and observable.",
"slug": "backend-engineer",
"source": "db"
},
{
"display_name": "Node.js Backend Developer",
"id": 82,
"rationale": null,
"role_archetype": "Engineering",
"slug": "node-backend-developer",
"source": "db"
},
{
"display_name": "PHP Backend Developer",
"id": 86,
"rationale": null,
"role_archetype": "Engineering",
"slug": "php-backend-developer",
"source": "db"
},
{
"display_name": "Python Backend Developer",
"id": 80,
"rationale": null,
"role_archetype": "Engineering",
"slug": "python-backend-developer",
"source": "db"
},
{
"display_name": "Scala Backend Developer",
"id": 87,
"rationale": null,
"role_archetype": "Engineering",
"slug": "scala-backend-developer",
"source": "db"
}
],
"skill_dimension_saved": false,
"skill_id": null,
"skill_tag": "new",
"skipped_reason": "skill_not_in_db_v3_proposed"
},
{
"chosen_role_id": 65,
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Testing and Defect Resolution",
"id": 262,
"rationale": "Validates Pega rules, flows, and integrations and then troubleshoots defects found in lower environments or production. This is a coherent cluster because the role is expected to verify platform behavior and fix rule-level issues.",
"slug": "testing-and-defect-resolution",
"source": "db"
},
"dimension_id": 262,
"input_skill": "Functional Testing",
"llm_role": null,
"matched_chosen_role": false,
"outcome_line": "Skipped \u2014 no persistable v3 meta for new skill",
"role_dimension_saved": false,
"roles_from_db": [
{
"display_name": "Pega Developer",
"id": 24,
"rationale": null,
"role_archetype": null,
"slug": "pega-developer",
"source": "db"
}
],
"skill_dimension_saved": false,
"skill_id": null,
"skill_tag": "new",
"skipped_reason": "skill_not_in_db_v3_proposed"
},
{
"chosen_role_id": 65,
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Testing and Quality Assurance",
"id": 12,
"rationale": "Backend-specific test strategies used to validate service behavior and integration points. Covers automated test layers, contract checks, fixtures, and regression prevention.",
"slug": "testing-and-quality-assurance",
"source": "db"
},
"dimension_id": 12,
"input_skill": "Functional Testing",
"llm_role": null,
"matched_chosen_role": false,
"outcome_line": "Skipped \u2014 no persistable v3 meta for new skill",
"role_dimension_saved": false,
"roles_from_db": [
{
"display_name": ".NET Backend Developer",
"id": 83,
"rationale": null,
"role_archetype": "Engineering",
"slug": "dotnet-backend-developer",
"source": "db"
},
{
"display_name": "Backend Developer",
"id": 1,
"rationale": null,
"role_archetype": "A Backend Engineer designs, builds, and maintains the server-side logic and data handling that power applications and services. They focus on implementing reliable business functionality, integrating with other systems, and ensuring the backend is scalable, maintainable, and observable.",
"slug": "backend-engineer",
"source": "db"
},
{
"display_name": "Node.js Backend Developer",
"id": 82,
"rationale": null,
"role_archetype": "Engineering",
"slug": "node-backend-developer",
"source": "db"
},
{
"display_name": "PHP Backend Developer",
"id": 86,
"rationale": null,
"role_archetype": "Engineering",
"slug": "php-backend-developer",
"source": "db"
},
{
"display_name": "Python Backend Developer",
"id": 80,
"rationale": null,
"role_archetype": "Engineering",
"slug": "python-backend-developer",
"source": "db"
},
{
"display_name": "Scala Backend Developer",
"id": 87,
"rationale": null,
"role_archetype": "Engineering",
"slug": "scala-backend-developer",
"source": "db"
}
],
"skill_dimension_saved": false,
"skill_id": null,
"skill_tag": "new",
"skipped_reason": "skill_not_in_db_v3_proposed"
},
{
"chosen_role_id": 65,
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Testing and Defect Resolution",
"id": 262,
"rationale": "Validates Pega rules, flows, and integrations and then troubleshoots defects found in lower environments or production. This is a coherent cluster because the role is expected to verify platform behavior and fix rule-level issues.",
"slug": "testing-and-defect-resolution",
"source": "db"
},
"dimension_id": 262,
"input_skill": "Integration Testing",
"llm_role": null,
"matched_chosen_role": false,
"outcome_line": "Existing dimension (library) \u00b7 Role\u2194dimension skipped (dimension not under chosen role)",
"role_dimension_saved": false,
"roles_from_db": [
{
"display_name": "Pega Developer",
"id": 24,
"rationale": null,
"role_archetype": null,
"slug": "pega-developer",
"source": "db"
}
],
"skill_dimension_saved": true,
"skill_id": 56,
"skill_tag": "in_db",
"skipped_reason": null
},
{
"chosen_role_id": 65,
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Testing and Quality Assurance",
"id": 12,
"rationale": "Backend-specific test strategies used to validate service behavior and integration points. Covers automated test layers, contract checks, fixtures, and regression prevention.",
"slug": "testing-and-quality-assurance",
"source": "db"
},
"dimension_id": 12,
"input_skill": "Integration Testing",
"llm_role": null,
"matched_chosen_role": 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": "Backend Developer",
"id": 1,
"rationale": null,
"role_archetype": "A Backend Engineer designs, builds, and maintains the server-side logic and data handling that power applications and services. They focus on implementing reliable business functionality, integrating with other systems, and ensuring the backend is scalable, maintainable, and observable.",
"slug": "backend-engineer",
"source": "db"
},
{
"display_name": "Node.js Backend Developer",
"id": 82,
"rationale": null,
"role_archetype": "Engineering",
"slug": "node-backend-developer",
"source": "db"
},
{
"display_name": "PHP Backend Developer",
"id": 86,
"rationale": null,
"role_archetype": "Engineering",
"slug": "php-backend-developer",
"source": "db"
},
{
"display_name": "Python Backend Developer",
"id": 80,
"rationale": null,
"role_archetype": "Engineering",
"slug": "python-backend-developer",
"source": "db"
},
{
"display_name": "Scala Backend Developer",
"id": 87,
"rationale": null,
"role_archetype": "Engineering",
"slug": "scala-backend-developer",
"source": "db"
}
],
"skill_dimension_saved": true,
"skill_id": 56,
"skill_tag": "in_db",
"skipped_reason": null
},
{
"chosen_role_id": 65,
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Magento Testing and Upgrade Safety",
"id": 405,
"rationale": "Validation practices used to keep Magento customizations stable across releases and platform upgrades. This cluster is coherent because Magento work must protect storefront behavior while remaining compatible with core and extension updates.",
"slug": "magento-testing-and-upgrade-safety",
"source": "db"
},
"dimension_id": 405,
"input_skill": "Regression Testing",
"llm_role": null,
"matched_chosen_role": false,
"outcome_line": "Existing dimension (library) \u00b7 Role\u2194dimension skipped (dimension not under chosen role)",
"role_dimension_saved": false,
"roles_from_db": [
{
"display_name": "Magento Dev",
"id": 231,
"rationale": null,
"role_archetype": "Engineering",
"slug": "magento-dev",
"source": "db"
}
],
"skill_dimension_saved": true,
"skill_id": 3758,
"skill_tag": "in_db",
"skipped_reason": null
},
{
"chosen_role_id": 65,
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Testing and Defect Resolution",
"id": 262,
"rationale": "Validates Pega rules, flows, and integrations and then troubleshoots defects found in lower environments or production. This is a coherent cluster because the role is expected to verify platform behavior and fix rule-level issues.",
"slug": "testing-and-defect-resolution",
"source": "db"
},
"dimension_id": 262,
"input_skill": "System Testing",
"llm_role": null,
"matched_chosen_role": false,
"outcome_line": "Skipped \u2014 no persistable v3 meta for new skill",
"role_dimension_saved": false,
"roles_from_db": [
{
"display_name": "Pega Developer",
"id": 24,
"rationale": null,
"role_archetype": null,
"slug": "pega-developer",
"source": "db"
}
],
"skill_dimension_saved": false,
"skill_id": null,
"skill_tag": "new",
"skipped_reason": "skill_not_in_db_v3_proposed"
},
{
"chosen_role_id": 65,
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Testing and Quality Assurance",
"id": 12,
"rationale": "Backend-specific test strategies used to validate service behavior and integration points. Covers automated test layers, contract checks, fixtures, and regression prevention.",
"slug": "testing-and-quality-assurance",
"source": "db"
},
"dimension_id": 12,
"input_skill": "System Testing",
"llm_role": null,
"matched_chosen_role": false,
"outcome_line": "Skipped \u2014 no persistable v3 meta for new skill",
"role_dimension_saved": false,
"roles_from_db": [
{
"display_name": ".NET Backend Developer",
"id": 83,
"rationale": null,
"role_archetype": "Engineering",
"slug": "dotnet-backend-developer",
"source": "db"
},
{
"display_name": "Backend Developer",
"id": 1,
"rationale": null,
"role_archetype": "A Backend Engineer designs, builds, and maintains the server-side logic and data handling that power applications and services. They focus on implementing reliable business functionality, integrating with other systems, and ensuring the backend is scalable, maintainable, and observable.",
"slug": "backend-engineer",
"source": "db"
},
{
"display_name": "Node.js Backend Developer",
"id": 82,
"rationale": null,
"role_archetype": "Engineering",
"slug": "node-backend-developer",
"source": "db"
},
{
"display_name": "PHP Backend Developer",
"id": 86,
"rationale": null,
"role_archetype": "Engineering",
"slug": "php-backend-developer",
"source": "db"
},
{
"display_name": "Python Backend Developer",
"id": 80,
"rationale": null,
"role_archetype": "Engineering",
"slug": "python-backend-developer",
"source": "db"
},
{
"display_name": "Scala Backend Developer",
"id": 87,
"rationale": null,
"role_archetype": "Engineering",
"slug": "scala-backend-developer",
"source": "db"
}
],
"skill_dimension_saved": false,
"skill_id": null,
"skill_tag": "new",
"skipped_reason": "skill_not_in_db_v3_proposed"
},
{
"chosen_role_id": 65,
"dimension": {
"difficulty_hint": "well_known",
"display_name": "React Frontend Development",
"id": 96,
"rationale": "Building interactive web user interfaces with React.js, including component composition, state management, hooks, and rendering patterns. React.js belongs here because it is a core library for client-side UI development in modern web applications.",
"slug": "d_init_01",
"source": "db"
},
"dimension_id": 96,
"input_skill": "Unit Testing",
"llm_role": null,
"matched_chosen_role": false,
"outcome_line": "Existing dimension (library) \u00b7 Role\u2194dimension skipped (dimension not under chosen role)",
"role_dimension_saved": false,
"roles_from_db": [],
"skill_dimension_saved": true,
"skill_id": 517,
"skill_tag": "in_db",
"skipped_reason": null
}
],
"new_skills_created": 0,
"role_dimension_saved": 0,
"skill_dimension_saved": 0,
"skipped": 5
},
"planner_output": null,
"run_id": "91515540-2d18-424c-95a5-337c30a51070"
}