Pipeline run
d3796043-b383-4453-b1be-f092c9b5635c
Client output enrichment
v2 Skill cluster · Nature of work · AI index · Tech stack maturity · Evidence · KRA descriptionNature of work
no kras
Vague JD — no KRAs present to derive a specific nature of work.
Tech stack maturity
Mainstream Modern
AI index (0 = no AI use, 5 = totally AI-dependent · v2.1)
0.00 / 5
· Title match
· Has AI skill
· AI skill (primary)
· AI skill (secondary)
· On AI team
· Builds AI products
vocab breakdown (legacy)
Assistants (×1):
—
Frameworks (×2):
—
Models / concepts (×3):
—
Evidence — skills matched in JD (0)
Skill cluster (0 dimension groups, role-scoped)
Status:
completed
Created: 2026-05-08T12:06:43.189755Z
Updated: 2026-05-08T12:08:37.703857Z
API 3 duration: 703 ms
Flow
Current 3-step pipeline
1 POST /skills/extract-from-jd
2 POST /skills/extract-details
3 POST /skills/final-role-output
Role
Chosen role & resolution
Data Analyst
slug: data-analyst · id: 20 · source: db
The strongest dimension signal is reporting and dashboard development mapped directly to Data Analyst, with the remaining dimensions being broader and less specific.
0
New skills
0
Skill↔dim saved
0
Role↔dim saved
18
Skipped
Job description
Business Analyst Job Description Job Title: Business Analyst Experience: 2–5 Years Location: Remote / Hybrid / On-site About the Role We are looking for a Business Analyst to bridge the gap between business needs and technical solutions. The ideal candidate will work closely with stakeholders, product teams, and developers to gather requirements, analyze business processes, and support successful project delivery. Key Responsibilities Gather, analyze, and document business requirements from stakeholders Translate business needs into functional specifications and user stories Work with cross-functional teams including developers, QA, and product managers Conduct requirement workshops, stakeholder meetings, and process analysis Create BRDs, FRDs, workflows, process diagrams, and reports Analyze data to identify trends, opportunities, and business insights Support UAT (User Acceptance Testing) and validate delivered solutions Monitor project progress and help manage risks and dependencies Improve existing business processes and recommend optimization strategies Ensure solutions align with business goals and operational needs Required Skills Strong understanding of business analysis methodologies Experience with requirement gathering and documentation Knowledge of Agile/Scrum methodologies Excellent communication and stakeholder management skills Strong analytical and problem-solving abilities Experience with tools like JIRA, Confluence, Excel, Visio, or Power BI Ability to create reports, dashboards, and process flows Understanding of SDLC and software development processes Preferred Qualifications Bachelor’s degree in Business, Computer Science, IT, or related field Experience working with technical and non-technical teams Familiarity with SQL, data analysis, or reporting tools is a plus Certification such as CBAP, CCBA, or Agile certification is preferred Nice to Have Experience in fintech, healthcare, e-commerce, or SaaS domains Exposure to BI tools like Tableau or Power BI Basic understanding of APIs and databases Benefits Competitive salary Flexible work environment Health insurance Learning and development opportunities Career growth and mentorship Paid leaves and company benefits
history_view bundle (older API). Showing raw API payloads below.
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 |
|---|---|---|---|---|---|---|
| Argo Workflows | in_db |
Workflow Orchestration Systems
workflow-orchestration-systems
|
— | — | — | TODO: REMOVE AFTER TESTING — api3_writes_enabled=False (writes disabled) |
| Power BI | in_db |
Reporting and Dashboard Development
reporting-and-dashboard-development
|
— | — | — | TODO: REMOVE AFTER TESTING — api3_writes_enabled=False (writes disabled) |
| Tableau | in_db |
Reporting and Dashboard Development
reporting-and-dashboard-development
|
— | — | — | TODO: REMOVE AFTER TESTING — api3_writes_enabled=False (writes disabled) |
| APIs | new |
API Design and Integration
d_init_01
|
— | — | — | skill_not_in_db_v3_proposed |
| Acceptance | new |
Acceptance Testing
d_init_01
|
— | — | — | skill_not_in_db_v3_proposed |
| BI | new |
Business Intelligence
d_init_01
|
— | — | — | skill_not_in_db_v3_proposed |
| CBAP | new |
Business Analysis Certification
d_init_01
|
— | — | — | skill_not_in_db_v3_proposed |
| CCBA | new |
Business Analysis Certification
d_init_01
|
— | — | — | skill_not_in_db_v3_proposed |
| Excel | new |
Spreadsheet Analysis and Modeling
d_init_01
|
— | — | — | skill_not_in_db_v3_proposed |
| FRDs | new |
Functional Requirements Documents
d_init_01
|
— | — | — | skill_not_in_db_v3_proposed |
| Familiarity | new |
Domain Familiarity
d_init_01
|
— | — | — | skill_not_in_db_v3_proposed |
| Knowledge | new |
Domain Knowledge
d_init_01
|
— | — | — | skill_not_in_db_v3_proposed |
| QA | new |
Quality Assurance Testing
d_init_01
|
— | — | — | skill_not_in_db_v3_proposed |
| SDLC | new |
Software Delivery Lifecycle
d_init_01
|
— | — | — | skill_not_in_db_v3_proposed |
| SaaS | new |
SaaS Product Delivery
d_init_01
|
— | — | — | skill_not_in_db_v3_proposed |
| UAT | new |
User Acceptance Testing Execution
d_init_01
|
— | — | — | skill_not_in_db_v3_proposed |
| Understanding | new |
Conceptual Understanding
d_init_01
|
— | — | — | skill_not_in_db_v3_proposed |
| Visio | new |
Diagramming and Process Modeling
d_init_01
|
— | — | — | skill_not_in_db_v3_proposed |
Library artifacts (this run)
| Kind | Detail | DB id |
|---|---|---|
| canonical_skill_proposed | APIs | type=Protocol subtype=application_programming_interfaces nature=PROTOCOL lifespan=EVERGREEN | |
| canonical_skill_proposed | Acceptance | type=Concept subtype=acceptance_concept nature=CONCEPT lifespan=EVERGREEN | |
| canonical_skill_proposed | BI | type=Domain subtype=business_intelligence nature=CONCEPT lifespan=EVERGREEN | |
| canonical_skill_proposed | CBAP | type=Certification subtype=business_analysis_professional_certification nature=CREDENTIAL lifespan=EVERGREEN | |
| canonical_skill_proposed | CCBA | type=Certification subtype=business_analysis_certification nature=CREDENTIAL lifespan=EVERGREEN | |
| canonical_skill_proposed | Excel | type=Tool subtype=spreadsheet_software nature=TOOL lifespan=EVERGREEN | |
| canonical_skill_proposed | FRDs | type=Domain subtype=functional_requirements_documents nature=CONCEPT lifespan=EVERGREEN | |
| canonical_skill_proposed | Familiarity | type=Concept subtype=familiarity nature=CONCEPT lifespan=EVERGREEN | |
| canonical_skill_proposed | Knowledge | type=Concept subtype=general_knowledge nature=CONCEPT lifespan=EVERGREEN | |
| canonical_skill_proposed | QA | type=Domain subtype=quality_assurance nature=CONCEPT lifespan=EVERGREEN | |
| canonical_skill_proposed | SDLC | type=Methodology subtype=software_development_lifecycle nature=METHODOLOGY lifespan=EVERGREEN | |
| canonical_skill_proposed | SaaS | type=Platform subtype=software_as_a_service_platform nature=PLATFORM lifespan=EVERGREEN | |
| canonical_skill_proposed | UAT | type=Methodology subtype=user_acceptance_testing nature=METHODOLOGY lifespan=EVERGREEN | |
| canonical_skill_proposed | Understanding | type=Concept subtype=comprehension nature=CONCEPT lifespan=EVERGREEN | |
| canonical_skill_proposed | Visio | type=Tool subtype=diagramming_tool nature=TOOL lifespan=EVERGREEN | |
| dimension_proposed | API Design and Integration | |
| dimension_skill_link_proposed | APIs ↔ API Design and Integration | |
| dimension_proposed | Acceptance Testing | |
| dimension_skill_link_proposed | Acceptance ↔ Acceptance Testing | |
| dimension_proposed | Business Intelligence | |
| dimension_skill_link_proposed | BI ↔ Business Intelligence | |
| dimension_proposed | Business Analysis Certification | |
| dimension_skill_link_proposed | CBAP ↔ Business Analysis Certification | |
| dimension_proposed | Business Analysis Certification | |
| dimension_skill_link_proposed | CCBA ↔ Business Analysis Certification | |
| dimension_proposed | Spreadsheet Analysis and Modeling | |
| dimension_skill_link_proposed | Excel ↔ Spreadsheet Analysis and Modeling | |
| dimension_proposed | Functional Requirements Documents | |
| dimension_skill_link_proposed | FRDs ↔ Functional Requirements Documents | |
| dimension_proposed | Domain Familiarity | |
| dimension_skill_link_proposed | Familiarity ↔ Domain Familiarity | |
| dimension_proposed | Domain Knowledge | |
| dimension_skill_link_proposed | Knowledge ↔ Domain Knowledge | |
| dimension_proposed | Quality Assurance Testing | |
| dimension_skill_link_proposed | QA ↔ Quality Assurance Testing | |
| dimension_proposed | Software Delivery Lifecycle | |
| dimension_skill_link_proposed | SDLC ↔ Software Delivery Lifecycle | |
| dimension_proposed | SaaS Product Delivery | |
| dimension_skill_link_proposed | SaaS ↔ SaaS Product Delivery | |
| dimension_proposed | User Acceptance Testing Execution | |
| dimension_skill_link_proposed | UAT ↔ User Acceptance Testing Execution | |
| dimension_proposed | Conceptual Understanding | |
| dimension_skill_link_proposed | Understanding ↔ Conceptual Understanding | |
| dimension_proposed | Diagramming and Process Modeling | |
| dimension_skill_link_proposed | Visio ↔ Diagramming and Process Modeling |
API 1 — extract-from-jd click to toggle
{
"filtered_unknown_words": [
"2\u20135",
"APIs",
"Ability",
"Acceptance",
"Analyst",
"BI",
"BRDs",
"Bachelor",
"Benefits",
"Business",
"CBAP",
"CCBA",
"Career",
"Certification",
"Computer",
"Conduct",
"Description",
"Ensure",
"Excel",
"Experience",
"Exposure",
"FRDs",
"Familiarity",
"Gather",
"Health",
"Hybrid",
"Job",
"Key",
"Knowledge",
"Learning",
"Location",
"Monitor",
"Power",
"Preferred",
"QA",
"Qualifications",
"Remote",
"Required",
"Responsibilities",
"Role",
"SDLC",
"SaaS",
"Science",
"Skills",
"Support",
"Testing",
"Title",
"UAT",
"Understanding",
"User",
"Visio",
"Years",
"abilities",
"analysis",
"benefits",
"business",
"candidate",
"certification",
"commerce",
"communication",
"company",
"data",
"databases",
"degree",
"delivery",
"dependencies",
"developers",
"development",
"diagrams",
"document",
"documentation",
"domains",
"environment",
"field",
"fintech",
"gap",
"gathering",
"goals",
"growth",
"healthcare",
"insights",
"insurance",
"leaves",
"management",
"managers",
"meetings",
"methodologies",
"needs",
"opportunities",
"optimization",
"problem",
"process",
"processes",
"product",
"progress",
"project",
"reporting",
"requirement",
"requirements",
"risks",
"salary",
"site",
"skills",
"software",
"solutions",
"specifications",
"stakeholder",
"stakeholders",
"stories",
"strategies",
"teams",
"tools",
"trends",
"understanding",
"user",
"work",
"workshops"
],
"final_non_skills": [
"2\u20135",
"Ability",
"Analyst",
"BRDs",
"Bachelor",
"Benefits",
"Business",
"Certification",
"Computer",
"Conduct",
"Description",
"Ensure",
"Experience",
"Exposure",
"Gather",
"Health",
"Hybrid",
"Job",
"Key",
"Learning",
"Location",
"Monitor",
"Power",
"Preferred",
"Qualifications",
"Remote",
"Required",
"Responsibilities",
"Role",
"Science",
"Skills",
"Support",
"Testing",
"Title",
"Years",
"abilities",
"candidate",
"commerce",
"company",
"degree",
"delivery",
"dependencies",
"developers",
"development",
"diagrams",
"document",
"domains",
"environment",
"field",
"gap",
"gathering",
"goals",
"growth",
"insurance",
"leaves",
"managers",
"meetings",
"needs",
"opportunities",
"problem",
"process",
"processes",
"product",
"progress",
"project",
"requirement",
"requirements",
"risks",
"salary",
"site",
"solutions",
"specifications",
"stakeholders",
"strategies",
"teams",
"tools",
"work"
],
"final_skills": [
"Argo Workflows",
"Power BI",
"Tableau",
"APIs",
"Acceptance",
"BI",
"CBAP",
"CCBA",
"Excel",
"FRDs",
"Familiarity",
"Knowledge",
"QA",
"SDLC",
"SaaS",
"UAT",
"Understanding",
"Visio",
"analysis",
"communication",
"data",
"databases",
"documentation",
"fintech",
"healthcare",
"insights",
"management",
"methodologies",
"optimization",
"reporting",
"software",
"stakeholder",
"stories",
"trends",
"workshops"
],
"initial_skills": [
"Argo Workflows",
"Power BI",
"Tableau"
],
"jd_role_hint": null,
"llm_non_skills": [
"2\u20135",
"Ability",
"Analyst",
"BRDs",
"Bachelor",
"Benefits",
"Business",
"Certification",
"Computer",
"Conduct",
"Description",
"Ensure",
"Experience",
"Exposure",
"Gather",
"Health",
"Hybrid",
"Job",
"Key",
"Learning",
"Location",
"Monitor",
"Power",
"Preferred",
"Qualifications",
"Remote",
"Required",
"Responsibilities",
"Role",
"Science",
"Skills",
"Support",
"Testing",
"Title",
"Years",
"abilities",
"candidate",
"commerce",
"company",
"degree",
"delivery",
"dependencies",
"developers",
"development",
"diagrams",
"document",
"domains",
"environment",
"field",
"gap",
"gathering",
"goals",
"growth",
"insurance",
"leaves",
"managers",
"meetings",
"needs",
"opportunities",
"problem",
"process",
"processes",
"product",
"progress",
"project",
"requirement",
"requirements",
"risks",
"salary",
"site",
"solutions",
"specifications",
"stakeholders",
"strategies",
"teams",
"tools",
"work"
],
"llm_skills": [
"APIs",
"Acceptance",
"BI",
"CBAP",
"CCBA",
"Excel",
"FRDs",
"Familiarity",
"Knowledge",
"QA",
"SDLC",
"SaaS",
"UAT",
"Understanding",
"Visio",
"analysis",
"communication",
"data",
"databases",
"documentation",
"fintech",
"healthcare",
"insights",
"management",
"methodologies",
"optimization",
"reporting",
"software",
"stakeholder",
"stories",
"trends",
"understanding",
"workshops"
],
"run_id": null,
"unknown_words": [
"2\u20135",
"APIs",
"Ability",
"Acceptance",
"Analyst",
"BI",
"BRDs",
"Bachelor",
"Benefits",
"Business",
"CBAP",
"CCBA",
"Career",
"Certification",
"Computer",
"Conduct",
"Description",
"Ensure",
"Excel",
"Experience",
"Exposure",
"FRDs",
"Familiarity",
"Gather",
"Health",
"Hybrid",
"Job",
"Key",
"Knowledge",
"Learning",
"Location",
"Monitor",
"Power",
"Preferred",
"QA",
"Qualifications",
"Remote",
"Required",
"Responsibilities",
"Role",
"SDLC",
"SaaS",
"Science",
"Skills",
"Support",
"Testing",
"Title",
"UAT",
"Understanding",
"User",
"Visio",
"Years",
"abilities",
"analysis",
"benefits",
"business",
"candidate",
"certification",
"commerce",
"communication",
"company",
"data",
"databases",
"degree",
"delivery",
"dependencies",
"developers",
"development",
"diagrams",
"document",
"documentation",
"domains",
"environment",
"field",
"fintech",
"gap",
"gathering",
"goals",
"growth",
"healthcare",
"insights",
"insurance",
"leaves",
"management",
"managers",
"meetings",
"methodologies",
"needs",
"opportunities",
"optimization",
"problem",
"process",
"processes",
"product",
"progress",
"project",
"reporting",
"requirement",
"requirements",
"risks",
"salary",
"site",
"skills",
"software",
"solutions",
"specifications",
"stakeholder",
"stakeholders",
"stories",
"strategies",
"teams",
"tools",
"trends",
"understanding",
"user",
"work",
"workshops"
]
}
API 2 — extract-details
{
"alias_matches": [],
"candidate_roles": [
{
"display_name": "Data Engineer",
"id": 6,
"rationale": null,
"role_archetype": null,
"slug": "data-engineer",
"source": "db"
},
{
"display_name": "MLOps Engineer",
"id": 5,
"rationale": null,
"role_archetype": null,
"slug": "mlops-engineer",
"source": "db"
},
{
"display_name": "Data Analyst",
"id": 20,
"rationale": null,
"role_archetype": null,
"slug": "data-analyst",
"source": "db"
}
],
"chosen_role": {
"display_name": "Data Analyst",
"id": 20,
"rationale": "The strongest dimension signal is reporting and dashboard development mapped directly to Data Analyst, with the remaining dimensions being broader and less specific.",
"role_archetype": null,
"slug": "data-analyst",
"source": "db"
},
"dimensions": [
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Workflow Orchestration Systems",
"id": 64,
"rationale": "Operational orchestration of ML jobs, dependencies, and handoffs across training, validation, deployment, and retraining. This is a useful split from training pipelines because it emphasizes the scheduler and control plane.",
"slug": "workflow-orchestration-systems",
"source": "db"
},
"input_skill": "Argo Workflows",
"llm_role": null,
"roles_from_db": [
{
"display_name": "Data Engineer",
"id": 6,
"rationale": null,
"role_archetype": null,
"slug": "data-engineer",
"source": "db"
},
{
"display_name": "MLOps Engineer",
"id": 5,
"rationale": null,
"role_archetype": null,
"slug": "mlops-engineer",
"source": "db"
}
]
},
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Reporting and Dashboard Development",
"id": 295,
"rationale": "Building recurring reports and dashboards that track performance over time and across segments. This is a distinct cluster because the analyst must package metrics into reusable views for stakeholders.",
"slug": "reporting-and-dashboard-development",
"source": "db"
},
"input_skill": "Power BI",
"llm_role": null,
"roles_from_db": [
{
"display_name": "Data Analyst",
"id": 20,
"rationale": null,
"role_archetype": null,
"slug": "data-analyst",
"source": "db"
}
]
},
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Reporting and Dashboard Development",
"id": 295,
"rationale": "Building recurring reports and dashboards that track performance over time and across segments. This is a distinct cluster because the analyst must package metrics into reusable views for stakeholders.",
"slug": "reporting-and-dashboard-development",
"source": "db"
},
"input_skill": "Tableau",
"llm_role": null,
"roles_from_db": [
{
"display_name": "Data Analyst",
"id": 20,
"rationale": null,
"role_archetype": null,
"slug": "data-analyst",
"source": "db"
}
]
},
{
"dimension": {
"difficulty_hint": null,
"display_name": "API Design and Integration",
"id": null,
"rationale": "Covers designing, consuming, and coordinating application programming interfaces across services and clients. APIs belongs here because it is the core surface for defining contracts, endpoints, and request/response interactions.",
"slug": "d_init_01",
"source": "llm"
},
"input_skill": "APIs",
"llm_role": null,
"roles_from_db": []
},
{
"dimension": {
"difficulty_hint": null,
"display_name": "Acceptance Testing",
"id": null,
"rationale": "Validating that a feature, change, or deliverable meets agreed requirements and acceptance criteria. This is the most direct fit for the skill Acceptance when it refers to sign-off, user acceptance, or requirement-based approval.",
"slug": "d_init_01",
"source": "llm"
},
"input_skill": "Acceptance",
"llm_role": null,
"roles_from_db": []
},
{
"dimension": {
"difficulty_hint": null,
"display_name": "Business Intelligence",
"id": null,
"rationale": "Covers the analysis, reporting, and dashboarding work used to turn data into business-facing insights. BI belongs here because it typically refers to the practice of building and consuming reports, metrics, and visual summaries for decision-making.",
"slug": "d_init_01",
"source": "llm"
},
"input_skill": "BI",
"llm_role": null,
"roles_from_db": []
},
{
"dimension": {
"difficulty_hint": null,
"display_name": "Business Analysis Certification",
"id": null,
"rationale": "Formal business analysis credentialing and the competency set associated with the CBAP designation. This belongs here because CBAP is a certification focused on business analysis practices, requirements work, and stakeholder-centered analysis.",
"slug": "d_init_01",
"source": "llm"
},
"input_skill": "CBAP",
"llm_role": null,
"roles_from_db": []
},
{
"dimension": {
"difficulty_hint": null,
"display_name": "Business Analysis Certification",
"id": null,
"rationale": "Formal business analysis credentialing and competency standards for practitioners who elicit, analyze, document, and validate business requirements. CCBA fits here as a recognized certification focused on business analysis knowledge and practice.",
"slug": "d_init_01",
"source": "llm"
},
"input_skill": "CCBA",
"llm_role": null,
"roles_from_db": []
},
{
"dimension": {
"difficulty_hint": null,
"display_name": "Spreadsheet Analysis and Modeling",
"id": null,
"rationale": "Covers using Excel to organize, analyze, and model tabular data with formulas, functions, pivots, and charts. Excel belongs here because it is the primary spreadsheet tool for ad hoc analysis, reporting, and lightweight business modeling.",
"slug": "d_init_01",
"source": "llm"
},
"input_skill": "Excel",
"llm_role": null,
"roles_from_db": []
},
{
"dimension": {
"difficulty_hint": null,
"display_name": "Functional Requirements Documents",
"id": null,
"rationale": "Covers writing, reviewing, and maintaining FRDs that define product behavior, scope, and acceptance expectations. This belongs here because FRDs are a requirements artifact used to align stakeholders before implementation and testing.",
"slug": "d_init_01",
"source": "llm"
},
"input_skill": "FRDs",
"llm_role": null,
"roles_from_db": []
},
{
"dimension": {
"difficulty_hint": null,
"display_name": "Domain Familiarity",
"id": null,
"rationale": "Baseline awareness of a technology, platform, or process sufficient to follow discussions and work effectively with guidance. This fits the target skill because it signals exposure and working recognition rather than deep ownership or hands-on expertise.",
"slug": "d_init_01",
"source": "llm"
},
"input_skill": "Familiarity",
"llm_role": null,
"roles_from_db": []
},
{
"dimension": {
"difficulty_hint": null,
"display_name": "Domain Knowledge",
"id": null,
"rationale": "Subject-matter understanding of the business, product, or technical area a role works in. This skill is broad and often underpins effective decisions, communication, and problem-solving across many engineering tasks.",
"slug": "d_init_01",
"source": "llm"
},
"input_skill": "Knowledge",
"llm_role": null,
"roles_from_db": []
},
{
"dimension": {
"difficulty_hint": null,
"display_name": "Quality Assurance Testing",
"id": null,
"rationale": "Validating software behavior against requirements through manual and exploratory testing, defect reporting, and regression checks. QA belongs here when it refers to the hands-on verification discipline used to catch issues before release.",
"slug": "d_init_01",
"source": "llm"
},
"input_skill": "QA",
"llm_role": null,
"roles_from_db": []
},
{
"dimension": {
"difficulty_hint": null,
"display_name": "Software Delivery Lifecycle",
"id": null,
"rationale": "Covers the end-to-end process of planning, building, testing, releasing, and maintaining software. SDLC belongs here because it refers to the lifecycle framework that organizes engineering work across development stages.",
"slug": "d_init_01",
"source": "llm"
},
"input_skill": "SDLC",
"llm_role": null,
"roles_from_db": []
},
{
"dimension": {
"difficulty_hint": null,
"display_name": "SaaS Product Delivery",
"id": null,
"rationale": "Covers building, packaging, and operating software delivered as a subscription-hosted service. SaaS belongs here because it refers to the product and delivery model rather than a specific technical subsystem.",
"slug": "d_init_01",
"source": "llm"
},
"input_skill": "SaaS",
"llm_role": null,
"roles_from_db": []
},
{
"dimension": {
"difficulty_hint": null,
"display_name": "User Acceptance Testing Execution",
"id": null,
"rationale": "Covers planning and running user acceptance tests to confirm a feature meets business requirements before release. UAT belongs here because it is a manual, acceptance-focused validation step rather than automated technical testing.",
"slug": "d_init_01",
"source": "llm"
},
"input_skill": "UAT",
"llm_role": null,
"roles_from_db": []
},
{
"dimension": {
"difficulty_hint": null,
"display_name": "Conceptual Understanding",
"id": null,
"rationale": "Covers the ability to comprehend domain concepts, requirements, and system behavior at a high level. This skill is too generic to map cleanly to a narrower engineering cluster, so it is best represented as a foundational cognitive dimension.",
"slug": "d_init_01",
"source": "llm"
},
"input_skill": "Understanding",
"llm_role": null,
"roles_from_db": []
},
{
"dimension": {
"difficulty_hint": null,
"display_name": "Diagramming and Process Modeling",
"id": null,
"rationale": "Covers creating business, system, and workflow diagrams used to communicate structure, process flow, and relationships. Visio belongs here because it is commonly used to draw formal diagrams, maps, and process models.",
"slug": "d_init_01",
"source": "llm"
},
"input_skill": "Visio",
"llm_role": null,
"roles_from_db": []
}
],
"input_final_skills": [
"Argo Workflows",
"Power BI",
"Tableau",
"APIs",
"Acceptance",
"BI",
"CBAP",
"CCBA",
"Excel",
"FRDs",
"Familiarity",
"Knowledge",
"QA",
"SDLC",
"SaaS",
"UAT",
"Understanding",
"Visio",
"analysis",
"communication",
"data",
"databases",
"documentation",
"fintech",
"healthcare",
"insights",
"management",
"methodologies",
"optimization",
"reporting",
"software",
"stakeholder",
"stories",
"trends",
"workshops"
],
"input_llm_skills": [
"APIs",
"Acceptance",
"BI",
"CBAP",
"CCBA",
"Excel",
"FRDs",
"Familiarity",
"Knowledge",
"QA",
"SDLC",
"SaaS",
"UAT",
"Understanding",
"Visio",
"analysis",
"communication",
"data",
"databases",
"documentation",
"fintech",
"healthcare",
"insights",
"management",
"methodologies",
"optimization",
"reporting",
"software",
"stakeholder",
"stories",
"trends",
"workshops"
],
"new_aliases_persisted": 0,
"run_id": "d3796043-b383-4453-b1be-f092c9b5635c",
"skills_detail": [
{
"aliases_in_db": [
{
"alias_text": "Argo Workflows",
"alias_type": "CANONICAL",
"id": 595,
"is_primary": true,
"match_strategy": "CASE_INSENSITIVE"
}
],
"canonical": {
"category_id": 11,
"display_name": "Argo Workflows",
"id": 380,
"is_also_category": false,
"is_extractable": true,
"skill_nature": "TOOL",
"slug": "argo-workflows",
"sub_category_id": 335,
"typical_lifespan": "EVERGREEN",
"volatility": "EMERGING"
},
"dimensions": [
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Workflow Orchestration Systems",
"id": 64,
"rationale": "Operational orchestration of ML jobs, dependencies, and handoffs across training, validation, deployment, and retraining. This is a useful split from training pipelines because it emphasizes the scheduler and control plane.",
"slug": "workflow-orchestration-systems",
"source": "db"
},
"input_skill": "Argo Workflows",
"llm_role": null,
"roles_from_db": [
{
"display_name": "Data Engineer",
"id": 6,
"rationale": null,
"role_archetype": null,
"slug": "data-engineer",
"source": "db"
},
{
"display_name": "MLOps Engineer",
"id": 5,
"rationale": null,
"role_archetype": null,
"slug": "mlops-engineer",
"source": "db"
}
]
}
],
"input_skill": "Argo Workflows",
"matched_via": "alias",
"new_alias_persisted": false,
"new_alias_text": null,
"new_skill_meta": null,
"source_tag": "db",
"was_in_llm_skills": false
},
{
"aliases_in_db": [
{
"alias_text": "Power BI",
"alias_type": "CANONICAL",
"id": 2535,
"is_primary": true,
"match_strategy": "CASE_INSENSITIVE"
}
],
"canonical": {
"category_id": 11,
"display_name": "Power BI",
"id": 1884,
"is_also_category": false,
"is_extractable": true,
"skill_nature": "TOOL",
"slug": "power-bi",
"sub_category_id": 1618,
"typical_lifespan": "EVERGREEN",
"volatility": "STABLE"
},
"dimensions": [
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Reporting and Dashboard Development",
"id": 295,
"rationale": "Building recurring reports and dashboards that track performance over time and across segments. This is a distinct cluster because the analyst must package metrics into reusable views for stakeholders.",
"slug": "reporting-and-dashboard-development",
"source": "db"
},
"input_skill": "Power BI",
"llm_role": null,
"roles_from_db": [
{
"display_name": "Data Analyst",
"id": 20,
"rationale": null,
"role_archetype": null,
"slug": "data-analyst",
"source": "db"
}
]
}
],
"input_skill": "Power BI",
"matched_via": "alias",
"new_alias_persisted": false,
"new_alias_text": null,
"new_skill_meta": null,
"source_tag": "db",
"was_in_llm_skills": false
},
{
"aliases_in_db": [
{
"alias_text": "Tableau",
"alias_type": "CANONICAL",
"id": 2534,
"is_primary": true,
"match_strategy": "CASE_INSENSITIVE"
}
],
"canonical": {
"category_id": 11,
"display_name": "Tableau",
"id": 1883,
"is_also_category": false,
"is_extractable": true,
"skill_nature": "TOOL",
"slug": "tableau",
"sub_category_id": 1618,
"typical_lifespan": "EVERGREEN",
"volatility": "STABLE"
},
"dimensions": [
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Reporting and Dashboard Development",
"id": 295,
"rationale": "Building recurring reports and dashboards that track performance over time and across segments. This is a distinct cluster because the analyst must package metrics into reusable views for stakeholders.",
"slug": "reporting-and-dashboard-development",
"source": "db"
},
"input_skill": "Tableau",
"llm_role": null,
"roles_from_db": [
{
"display_name": "Data Analyst",
"id": 20,
"rationale": null,
"role_archetype": null,
"slug": "data-analyst",
"source": "db"
}
]
}
],
"input_skill": "Tableau",
"matched_via": "alias",
"new_alias_persisted": false,
"new_alias_text": null,
"new_skill_meta": null,
"source_tag": "db",
"was_in_llm_skills": false
},
{
"aliases_in_db": [],
"canonical": null,
"dimensions": [
{
"dimension": {
"difficulty_hint": null,
"display_name": "API Design and Integration",
"id": null,
"rationale": "Covers designing, consuming, and coordinating application programming interfaces across services and clients. APIs belongs here because it is the core surface for defining contracts, endpoints, and request/response interactions.",
"slug": "d_init_01",
"source": "llm"
},
"input_skill": "APIs",
"llm_role": null,
"roles_from_db": []
}
],
"input_skill": "APIs",
"matched_via": null,
"new_alias_persisted": false,
"new_alias_text": null,
"new_skill_meta": {
"derived": {
"category": "Protocol",
"skill_nature": "PROTOCOL",
"sub_category": "application_programming_interfaces",
"typical_lifespan": "EVERGREEN",
"version_strategy": "NOT_APPLICABLE",
"volatility": "STABLE"
},
"enrichment": {
"ambiguity": {
"ambiguity_flag": false,
"confused_with": [],
"reasoning": "APIs is a standard, well-scoped term in JDs and usually refers to application programming interfaces; it is not typically confused with a different catalog skill."
},
"context_keywords": {
"context_keywords": [
"REST",
"GraphQL",
"OpenAPI",
"Swagger",
"JSON",
"XML",
"OAuth 2.0",
"JWT",
"webhooks",
"endpoint",
"rate limiting",
"API gateway",
"microservices",
"SDK",
"versioning"
]
},
"maturity": {
"confidence": 0.96,
"maturity": "well_known",
"reasoning": "APIs are a hiring-pipeline staple across backend, mobile, and platform JDs; REST/GraphQL/gRPC appear routinely in job postings and vendor docs, indicating broad adoption rather than niche use."
},
"skill_id": "apis",
"vendor_license": {
"confidence": 0.99,
"license": null,
"vendor": null,
"year_introduced": null
},
"versioning": {
"current_version": null,
"version_aliases": {},
"versioned": false
}
},
"keep_log": [],
"locked_dimensions": [
{
"description": "Covers designing, consuming, and coordinating application programming interfaces across services and clients. APIs belongs here because it is the core surface for defining contracts, endpoints, and request/response interactions.",
"exemplar_skills": [
"APIs",
"REST APIs",
"gRPC",
"API versioning",
"endpoint design",
"service-to-service integration"
],
"in_scope": "APIs, REST APIs, JSON APIs, gRPC endpoints, endpoint design, request/response contracts, API versioning, pagination, error handling, service-to-service integration",
"name": "API Design and Integration",
"out_of_scope": "API test automation, UI component state, authentication session management, database schema design, infrastructure provisioning, which are owned by other dimensions",
"overlap_flags": [
{
"reason": "API design overlaps with endpoint validation, but this dimension focuses on building and integrating APIs rather than testing them.",
"with_dim_id": "api-and-service-test-automation",
"with_dim_name": null,
"with_role": "Automation Tester"
},
{
"reason": "APIs often carry auth concerns, but sign-in and session behavior are handled in the authentication dimension.",
"with_dim_id": "authentication-flows-and-session-handling",
"with_dim_name": null,
"with_role": "Android Engineer, Frontend Engineer, Full Stack Developer"
},
{
"reason": "API work is a subset of broader service integration and may overlap with service decomposition and inter-service communication.",
"with_dim_id": "service-architecture-and-integration",
"with_dim_name": null,
"with_role": "Backend Engineer"
}
],
"tentative_id": "d_init_01"
}
],
"merge_log": [],
"placed": {
"name": "APIs",
"placement_confidence": 0.92,
"primary_dimension": "d_init_01",
"reasoning": "Deterministic JD placement: locked_dimensions has 1 dimension(s) from skill-driven dimension generation after reconciliation; primary_dimension is the first locked dim.",
"secondary_dimensions": [],
"skill_id": "apis"
},
"relationships": {
"child_skills": [
"rest-apis",
"scripted-rest-api",
"outbound-rest-messages"
],
"parent_skills": [],
"related_to": [
"grpc",
"private-endpoints",
"acls",
"portal-pages",
"expressroute",
"aks",
"aws-iam",
"repository-pattern",
"deep-links",
"angularjs",
"refresh-tokens",
"mock-servers",
"aws-cdk",
"policy-as-code"
],
"requires": [
"http",
"json",
"oauth-2-0"
],
"skill_id": "apis",
"suppress_on_match": []
},
"skill_id": "apis",
"split_log": [],
"typed": {
"alternatives_considered": [],
"confidence": 0.91,
"name": "APIs",
"reasoning": "APIs are fundamentally a communication interface between systems, so by the Protocol rule they fit best as a protocol-like standard for interaction rather than a tool or platform.",
"skill_id": "apis",
"subtype": "application_programming_interfaces",
"type": "Protocol"
},
"warnings": []
},
"source_tag": "llm",
"was_in_llm_skills": true
},
{
"aliases_in_db": [],
"canonical": null,
"dimensions": [
{
"dimension": {
"difficulty_hint": null,
"display_name": "Acceptance Testing",
"id": null,
"rationale": "Validating that a feature, change, or deliverable meets agreed requirements and acceptance criteria. This is the most direct fit for the skill Acceptance when it refers to sign-off, user acceptance, or requirement-based approval.",
"slug": "d_init_01",
"source": "llm"
},
"input_skill": "Acceptance",
"llm_role": null,
"roles_from_db": []
}
],
"input_skill": "Acceptance",
"matched_via": null,
"new_alias_persisted": false,
"new_alias_text": null,
"new_skill_meta": {
"derived": {
"category": "Concept",
"skill_nature": "CONCEPT",
"sub_category": "acceptance_concept",
"typical_lifespan": "EVERGREEN",
"version_strategy": "NOT_APPLICABLE",
"volatility": "STABLE"
},
"enrichment": {
"ambiguity": {
"ambiguity_flag": true,
"confused_with": [
"acceptance_testing"
],
"reasoning": "\u201cAcceptance\u201d is a generic concept and in JDs could easily mean acceptance testing or user acceptance, not the standalone concept."
},
"context_keywords": {
"context_keywords": [
"UAT",
"user acceptance testing",
"acceptance criteria",
"acceptance test",
"sign-off",
"go-live",
"test cases",
"requirements validation",
"stakeholder approval",
"definition of done",
"QA",
"regression testing",
"test plan",
"validation",
"verification"
]
},
"maturity": {
"confidence": 0.78,
"maturity": "niche",
"reasoning": "\u201cAcceptance\u201d as a standalone engineering concept appears in far fewer JDs than concrete tools; market signals are mostly in QA/UAT and acceptance-testing roles rather than general software hiring pipelines."
},
"skill_id": "acceptance",
"vendor_license": {
"confidence": 0.99,
"license": null,
"vendor": null,
"year_introduced": null
},
"versioning": {
"current_version": null,
"version_aliases": {},
"versioned": false
}
},
"keep_log": [],
"locked_dimensions": [
{
"description": "Validating that a feature, change, or deliverable meets agreed requirements and acceptance criteria. This is the most direct fit for the skill Acceptance when it refers to sign-off, user acceptance, or requirement-based approval.",
"exemplar_skills": [
"Acceptance",
"User Acceptance Testing",
"Acceptance Criteria Review",
"Requirement Validation",
"Release Sign-off",
"Feature Acceptance"
],
"in_scope": "Acceptance, acceptance criteria, user acceptance testing, sign-off checks, requirement validation, feature acceptance, release acceptance, stakeholder approval, definition of done",
"name": "Acceptance Testing",
"out_of_scope": "Automated test framework implementation, API contract automation, unit test authoring, performance benchmarking, security review, production monitoring",
"overlap_flags": [
{
"reason": "Acceptance testing often uses manual test cases, but that dimension is broader and centered on test case authoring and execution.",
"with_dim_id": "test-case-design-and-execution",
"with_dim_name": null,
"with_role": "Manual Tester"
},
{
"reason": "Acceptance checks can be automated at the API layer, but this dimension owns backend automation rather than acceptance semantics.",
"with_dim_id": "api-and-service-test-automation",
"with_dim_name": null,
"with_role": "Automation Tester"
}
],
"tentative_id": "d_init_01"
}
],
"merge_log": [],
"placed": {
"name": "Acceptance",
"placement_confidence": 0.92,
"primary_dimension": "d_init_01",
"reasoning": "Deterministic JD placement: locked_dimensions has 1 dimension(s) from skill-driven dimension generation after reconciliation; primary_dimension is the first locked dim.",
"secondary_dimensions": [],
"skill_id": "acceptance"
},
"relationships": {
"child_skills": [],
"parent_skills": [],
"related_to": [
"acceptance-criteria-validation",
"acceptance-criteria-checks",
"contract-tests",
"defect-retest",
"change-requests"
],
"requires": [],
"skill_id": "acceptance",
"suppress_on_match": []
},
"skill_id": "acceptance",
"split_log": [],
"typed": {
"alternatives_considered": [
"Methodology: ruled out \u2014 it is not a way of working or process like Agile or TDD.",
"SoftSkill: ruled out \u2014 despite the interpersonal connotation, the standalone skill name here is more about a requirement/criteria concept than communication behavior."
],
"confidence": 0.78,
"name": "Acceptance",
"reasoning": "Acceptance is best treated as a Concept because it names a knowledge unit about whether something meets expected conditions, rather than a process or tool.",
"skill_id": "acceptance",
"subtype": "acceptance_concept",
"type": "Concept"
},
"warnings": []
},
"source_tag": "llm",
"was_in_llm_skills": true
},
{
"aliases_in_db": [],
"canonical": null,
"dimensions": [
{
"dimension": {
"difficulty_hint": null,
"display_name": "Business Intelligence",
"id": null,
"rationale": "Covers the analysis, reporting, and dashboarding work used to turn data into business-facing insights. BI belongs here because it typically refers to the practice of building and consuming reports, metrics, and visual summaries for decision-making.",
"slug": "d_init_01",
"source": "llm"
},
"input_skill": "BI",
"llm_role": null,
"roles_from_db": []
}
],
"input_skill": "BI",
"matched_via": null,
"new_alias_persisted": false,
"new_alias_text": null,
"new_skill_meta": {
"derived": {
"category": "Domain",
"skill_nature": "CONCEPT",
"sub_category": "business_intelligence",
"typical_lifespan": "EVERGREEN",
"version_strategy": "NOT_APPLICABLE",
"volatility": "STABLE"
},
"enrichment": {
"ambiguity": {
"ambiguity_flag": true,
"confused_with": [
"business_intelligence"
],
"reasoning": "\"BI\" is a common abbreviation for Business Intelligence, but in JDs it can also be used more broadly for business/analytics contexts. A reasonable extractor could map it to the full Business Intelligence skill in the catalog."
},
"context_keywords": {
"context_keywords": [
"dashboarding",
"KPI",
"data warehouse",
"ETL",
"OLAP",
"reporting",
"ad hoc analysis",
"data modeling",
"star schema",
"dimensional modeling",
"Tableau",
"Power BI",
"Looker",
"SQL",
"semantic layer"
]
},
"maturity": {
"confidence": 0.9,
"maturity": "well_known",
"reasoning": "BI appears in many job descriptions across analyst, data, and reporting roles; vendors like Microsoft, Tableau, and Power BI show sustained enterprise demand."
},
"skill_id": "bi",
"vendor_license": {
"confidence": 0.98,
"license": null,
"vendor": null,
"year_introduced": null
},
"versioning": {
"current_version": null,
"version_aliases": {},
"versioned": false
}
},
"keep_log": [],
"locked_dimensions": [
{
"description": "Covers the analysis, reporting, and dashboarding work used to turn data into business-facing insights. BI belongs here because it typically refers to the practice of building and consuming reports, metrics, and visual summaries for decision-making.",
"exemplar_skills": [
"BI",
"dashboard development",
"KPI reporting",
"ad hoc analysis",
"data visualization",
"self-service reporting",
"executive scorecards"
],
"in_scope": "BI, dashboards, KPI reporting, ad hoc analysis, executive scorecards, self-service reporting, OLAP analysis, report development, data visualization, business metrics",
"name": "Business Intelligence",
"out_of_scope": "data preparation and ETL, warehouse modeling, streaming ingestion, model training and deployment, operational monitoring of pipelines, database administration",
"overlap_flags": [
{
"reason": "BI work often depends on shaping source data, but the transformation and joining logic itself belongs to data preparation.",
"with_dim_id": "data-preparation-and-blending",
"with_dim_name": null,
"with_role": "Data Analyst"
},
{
"reason": "Analytical exploration may happen in notebooks, but BI is centered on business-facing reporting and dashboards rather than reproducible research workflows.",
"with_dim_id": "notebook-and-reproducible-analysis-workflow",
"with_dim_name": null,
"with_role": "Data Scientist"
}
],
"tentative_id": "d_init_01"
}
],
"merge_log": [],
"placed": {
"name": "BI",
"placement_confidence": 0.92,
"primary_dimension": "d_init_01",
"reasoning": "Deterministic JD placement: locked_dimensions has 1 dimension(s) from skill-driven dimension generation after reconciliation; primary_dimension is the first locked dim.",
"secondary_dimensions": [],
"skill_id": "bi"
},
"relationships": {
"child_skills": [],
"parent_skills": [],
"related_to": [
"dashboards",
"risk-based-testing",
"session-based-testing"
],
"requires": [],
"skill_id": "bi",
"suppress_on_match": []
},
"skill_id": "bi",
"split_log": [],
"typed": {
"alternatives_considered": [],
"confidence": 0.97,
"name": "BI",
"reasoning": "BI is fundamentally a business intelligence problem space and body of knowledge, so by the Domain rule it is not a tool, framework, or methodology.",
"skill_id": "bi",
"subtype": "business_intelligence",
"type": "Domain"
},
"warnings": []
},
"source_tag": "llm",
"was_in_llm_skills": true
},
{
"aliases_in_db": [],
"canonical": null,
"dimensions": [
{
"dimension": {
"difficulty_hint": null,
"display_name": "Business Analysis Certification",
"id": null,
"rationale": "Formal business analysis credentialing and the competency set associated with the CBAP designation. This belongs here because CBAP is a certification focused on business analysis practices, requirements work, and stakeholder-centered analysis.",
"slug": "d_init_01",
"source": "llm"
},
"input_skill": "CBAP",
"llm_role": null,
"roles_from_db": []
}
],
"input_skill": "CBAP",
"matched_via": null,
"new_alias_persisted": false,
"new_alias_text": null,
"new_skill_meta": {
"derived": {
"category": "Certification",
"skill_nature": "CREDENTIAL",
"sub_category": "business_analysis_professional_certification",
"typical_lifespan": "EVERGREEN",
"version_strategy": "NOT_APPLICABLE",
"volatility": "STABLE"
},
"enrichment": {
"ambiguity": {
"ambiguity_flag": false,
"confused_with": [],
"reasoning": "CBAP is a specific certification acronym (Certified Business Analysis Professional) and is unlikely to be confused with another catalog skill in typical job descriptions."
},
"context_keywords": {
"context_keywords": [
"BABOK",
"IIBA",
"requirements elicitation",
"stakeholder analysis",
"process modeling",
"use cases",
"user stories",
"gap analysis",
"business process improvement",
"UML",
"SWOT analysis",
"traceability matrix",
"functional requirements",
"workshops",
"facilitation"
]
},
"maturity": {
"confidence": 0.84,
"maturity": "well_known",
"reasoning": "CBAP appears in many business analyst job descriptions as a preferred certification, and IIBA continues to maintain and promote it as an active credential."
},
"skill_id": "cbap",
"vendor_license": {
"confidence": 0.95,
"license": null,
"vendor": "International Institute of Business Analysis",
"year_introduced": 2006
},
"versioning": {
"current_version": null,
"version_aliases": {},
"versioned": false
}
},
"keep_log": [],
"locked_dimensions": [
{
"description": "Formal business analysis credentialing and the competency set associated with the CBAP designation. This belongs here because CBAP is a certification focused on business analysis practices, requirements work, and stakeholder-centered analysis.",
"exemplar_skills": [
"CBAP",
"business analysis certification",
"requirements elicitation",
"stakeholder analysis",
"business process analysis",
"solution assessment",
"requirements lifecycle management"
],
"in_scope": "CBAP, business analysis certification, requirements elicitation, stakeholder analysis, business process analysis, solution assessment, requirements lifecycle management, BABOK-aligned practices",
"name": "Business Analysis Certification",
"out_of_scope": "Software testing execution, project management certification, data analysis tooling, product management strategy, technical architecture design",
"overlap_flags": [
{
"reason": "Business analysts may discuss service boundaries and integrations, but CBAP is centered on requirements and stakeholder analysis rather than system architecture.",
"with_dim_id": "service-architecture-and-integration",
"with_dim_name": null,
"with_role": "Backend Engineer"
}
],
"tentative_id": "d_init_01"
}
],
"merge_log": [],
"placed": {
"name": "CBAP",
"placement_confidence": 0.92,
"primary_dimension": "d_init_01",
"reasoning": "Deterministic JD placement: locked_dimensions has 1 dimension(s) from skill-driven dimension generation after reconciliation; primary_dimension is the first locked dim.",
"secondary_dimensions": [],
"skill_id": "cbap"
},
"relationships": {
"child_skills": [],
"parent_skills": [],
"related_to": [
"risk-based-testing",
"acceptance-criteria-validation",
"acceptance-criteria-checks",
"capacity-planning",
"session-based-testing"
],
"requires": [],
"skill_id": "cbap",
"suppress_on_match": []
},
"skill_id": "cbap",
"split_log": [],
"typed": {
"alternatives_considered": [],
"confidence": 0.98,
"name": "CBAP",
"reasoning": "CBAP is a formal third-party credential, so by the Certification rule it is a certification rather than a concept or methodology.",
"skill_id": "cbap",
"subtype": "business_analysis_professional_certification",
"type": "Certification"
},
"warnings": []
},
"source_tag": "llm",
"was_in_llm_skills": true
},
{
"aliases_in_db": [],
"canonical": null,
"dimensions": [
{
"dimension": {
"difficulty_hint": null,
"display_name": "Business Analysis Certification",
"id": null,
"rationale": "Formal business analysis credentialing and competency standards for practitioners who elicit, analyze, document, and validate business requirements. CCBA fits here as a recognized certification focused on business analysis knowledge and practice.",
"slug": "d_init_01",
"source": "llm"
},
"input_skill": "CCBA",
"llm_role": null,
"roles_from_db": []
}
],
"input_skill": "CCBA",
"matched_via": null,
"new_alias_persisted": false,
"new_alias_text": null,
"new_skill_meta": {
"derived": {
"category": "Certification",
"skill_nature": "CREDENTIAL",
"sub_category": "business_analysis_certification",
"typical_lifespan": "EVERGREEN",
"version_strategy": "NOT_APPLICABLE",
"volatility": "STABLE"
},
"enrichment": {
"ambiguity": {
"ambiguity_flag": true,
"confused_with": [
"cbap"
],
"reasoning": "CCBA is a business analysis certification acronym and can be mistaken for the closely related CBAP certification in job descriptions, especially when abbreviations are used loosely."
},
"context_keywords": {
"context_keywords": [
"BABOK",
"IIBA",
"requirements elicitation",
"stakeholder analysis",
"process modeling",
"use cases",
"user stories",
"gap analysis",
"business process improvement",
"solution assessment",
"traceability matrix",
"SWOT analysis",
"UML",
"workshops",
"acceptance criteria"
]
},
"maturity": {
"confidence": 0.84,
"maturity": "well_known",
"reasoning": "CCBA is a widely recognized business analysis certification; it appears in many job descriptions for BA roles and is offered by IIBA as a mainstream credential alongside CBAP."
},
"skill_id": "ccba",
"vendor_license": {
"confidence": 0.92,
"license": null,
"vendor": "International Institute of Business Analysis",
"year_introduced": 2007
},
"versioning": {
"current_version": null,
"version_aliases": {},
"versioned": false
}
},
"keep_log": [],
"locked_dimensions": [
{
"description": "Formal business analysis credentialing and competency standards for practitioners who elicit, analyze, document, and validate business requirements. CCBA fits here as a recognized certification focused on business analysis knowledge and practice.",
"exemplar_skills": [
"CCBA",
"business analysis certification",
"requirements elicitation",
"stakeholder analysis",
"process modeling",
"solution assessment"
],
"in_scope": "CCBA, business analysis certification, requirements elicitation, stakeholder analysis, process modeling, solution assessment, business case analysis, BABOK-aligned competencies",
"name": "Business Analysis Certification",
"out_of_scope": "Software testing certifications, project management credentials, data analysis tooling, product management strategy, which belong to other professional or technical dimensions",
"overlap_flags": [
{
"reason": "Business analysts may work with service boundaries and integrations, but CCBA is primarily about analysis practice rather than system architecture.",
"with_dim_id": "service-architecture-and-integration",
"with_dim_name": null,
"with_role": "Backend Engineer"
},
{
"reason": "Business analysis can support migration initiatives, but CCBA is broader than planning a specific modernization program.",
"with_dim_id": "migration-and-modernization-planning",
"with_dim_name": null,
"with_role": "Cloud Architect"
}
],
"tentative_id": "d_init_01"
}
],
"merge_log": [],
"placed": {
"name": "CCBA",
"placement_confidence": 0.92,
"primary_dimension": "d_init_01",
"reasoning": "Deterministic JD placement: locked_dimensions has 1 dimension(s) from skill-driven dimension generation after reconciliation; primary_dimension is the first locked dim.",
"secondary_dimensions": [],
"skill_id": "ccba"
},
"relationships": {
"child_skills": [],
"parent_skills": [],
"related_to": [
"acceptance-criteria-checks",
"acceptance-criteria-validation",
"risk-based-testing",
"session-based-testing",
"charter-based-testing"
],
"requires": [],
"skill_id": "ccba",
"suppress_on_match": []
},
"skill_id": "ccba",
"split_log": [],
"typed": {
"alternatives_considered": [],
"confidence": 0.98,
"name": "CCBA",
"reasoning": "CCBA is a formal third-party credential, so by the Certification rule it is not a concept or methodology.",
"skill_id": "ccba",
"subtype": "business_analysis_certification",
"type": "Certification"
},
"warnings": []
},
"source_tag": "llm",
"was_in_llm_skills": true
},
{
"aliases_in_db": [],
"canonical": null,
"dimensions": [
{
"dimension": {
"difficulty_hint": null,
"display_name": "Spreadsheet Analysis and Modeling",
"id": null,
"rationale": "Covers using Excel to organize, analyze, and model tabular data with formulas, functions, pivots, and charts. Excel belongs here because it is the primary spreadsheet tool for ad hoc analysis, reporting, and lightweight business modeling.",
"slug": "d_init_01",
"source": "llm"
},
"input_skill": "Excel",
"llm_role": null,
"roles_from_db": []
}
],
"input_skill": "Excel",
"matched_via": null,
"new_alias_persisted": false,
"new_alias_text": null,
"new_skill_meta": {
"derived": {
"category": "Tool",
"skill_nature": "TOOL",
"sub_category": "spreadsheet_software",
"typical_lifespan": "EVERGREEN",
"version_strategy": "SEPARATE_ENTITY",
"volatility": "STABLE"
},
"enrichment": {
"ambiguity": {
"ambiguity_flag": false,
"confused_with": [],
"reasoning": "Excel is a well-known spreadsheet application and, in typical JDs, is unlikely to be confused with a different catalog skill."
},
"context_keywords": {
"context_keywords": [
"pivot tables",
"VLOOKUP",
"XLOOKUP",
"SUMIF",
"INDEX MATCH",
"macros",
"VBA",
"Power Query",
"Power Pivot",
"data validation",
"conditional formatting",
"charts",
"dashboards",
"CSV",
"financial modeling"
]
},
"maturity": {
"confidence": 0.99,
"maturity": "well_known",
"reasoning": "Excel appears in a very large share of business, finance, ops, and analyst job descriptions; Microsoft continues active support and it remains a standard spreadsheet tool rather than a sunset product."
},
"skill_id": "excel",
"vendor_license": {
"confidence": 0.99,
"license": "proprietary",
"vendor": "Microsoft",
"year_introduced": 1985
},
"versioning": {
"current_version": "Microsoft 365 / Excel 2021+",
"version_aliases": {
"Excel 2003": "Excel 2003",
"Excel 2007": "Excel 2007",
"Excel 2010": "Excel 2010",
"Excel 2013": "Excel 2013",
"Excel 2016": "Excel 2016",
"Excel 2019": "Excel 2019",
"Excel 2021": "Microsoft 365 / Excel 2021+",
"Excel 365": "Microsoft 365 / Excel 2021+",
"Microsoft 365": "Microsoft 365 / Excel 2021+"
},
"versioned": true
}
},
"keep_log": [],
"locked_dimensions": [
{
"description": "Covers using Excel to organize, analyze, and model tabular data with formulas, functions, pivots, and charts. Excel belongs here because it is the primary spreadsheet tool for ad hoc analysis, reporting, and lightweight business modeling.",
"exemplar_skills": [
"Excel",
"Pivot Tables",
"VLOOKUP",
"XLOOKUP",
"SUMIFS",
"Conditional Formatting",
"Data Validation",
"What-If Analysis"
],
"in_scope": "Excel, formulas, functions, pivot tables, charts, conditional formatting, lookup functions, data validation, filters, sorting, what-if analysis, basic dashboards",
"name": "Spreadsheet Analysis and Modeling",
"out_of_scope": "SQL-based analytics and warehouse querying, notebook-based analysis workflows, ETL pipeline engineering, statistical programming in Python or R, presentation design in PowerPoint",
"overlap_flags": [
{
"reason": "Excel is often used to combine and reshape tables, but that dimension is more about joining and transforming source data than spreadsheet analysis itself.",
"with_dim_id": "data-preparation-and-blending",
"with_dim_name": null,
"with_role": "Data Analyst"
},
{
"reason": "Excel can support analysis workflows, but notebooks own reproducible scripted analysis rather than interactive spreadsheet work.",
"with_dim_id": "notebook-and-reproducible-analysis-workflow",
"with_dim_name": null,
"with_role": "Data Scientist"
}
],
"tentative_id": "d_init_01"
}
],
"merge_log": [],
"placed": {
"name": "Excel",
"placement_confidence": 0.92,
"primary_dimension": "d_init_01",
"reasoning": "Deterministic JD placement: locked_dimensions has 1 dimension(s) from skill-driven dimension generation after reconciliation; primary_dimension is the first locked dim.",
"secondary_dimensions": [],
"skill_id": "excel"
},
"relationships": {
"child_skills": [],
"parent_skills": [],
"related_to": [
"dashboards",
"summary-statistics",
"scorecards",
"error-analysis",
"outlier-detection"
],
"requires": [],
"skill_id": "excel",
"suppress_on_match": []
},
"skill_id": "excel",
"split_log": [],
"typed": {
"alternatives_considered": [],
"confidence": 0.98,
"name": "Excel",
"reasoning": "Excel is software you operate directly as a user rather than a hosted environment or code package, so by the Tool vs Framework rule it is a Tool.",
"skill_id": "excel",
"subtype": "spreadsheet_software",
"type": "Tool"
},
"warnings": []
},
"source_tag": "llm",
"was_in_llm_skills": true
},
{
"aliases_in_db": [],
"canonical": null,
"dimensions": [
{
"dimension": {
"difficulty_hint": null,
"display_name": "Functional Requirements Documents",
"id": null,
"rationale": "Covers writing, reviewing, and maintaining FRDs that define product behavior, scope, and acceptance expectations. This belongs here because FRDs are a requirements artifact used to align stakeholders before implementation and testing.",
"slug": "d_init_01",
"source": "llm"
},
"input_skill": "FRDs",
"llm_role": null,
"roles_from_db": []
}
],
"input_skill": "FRDs",
"matched_via": null,
"new_alias_persisted": false,
"new_alias_text": null,
"new_skill_meta": {
"derived": {
"category": "Domain",
"skill_nature": "CONCEPT",
"sub_category": "functional_requirements_documents",
"typical_lifespan": "EVERGREEN",
"version_strategy": "NOT_APPLICABLE",
"volatility": "STABLE"
},
"enrichment": {
"ambiguity": {
"ambiguity_flag": false,
"confused_with": [],
"reasoning": "FRDs is a fairly specific plural abbreviation for functional requirements documents; in JDs it is unlikely to be mistaken for another catalog skill."
},
"context_keywords": {
"context_keywords": [
"BRD",
"PRD",
"use cases",
"user stories",
"acceptance criteria",
"functional specification",
"requirements traceability",
"stakeholder interviews",
"process flows",
"wireframes",
"UAT",
"business rules",
"gap analysis",
"scope definition",
"sign-off"
]
},
"maturity": {
"confidence": 0.78,
"maturity": "well_known",
"reasoning": "Functional requirements documents (FRDs) are a standard artifact in many product and business-analysis job descriptions and RFP workflows, with broad use across enterprise software teams."
},
"skill_id": "frds",
"vendor_license": {
"confidence": 0.98,
"license": null,
"vendor": null,
"year_introduced": null
},
"versioning": {
"current_version": null,
"version_aliases": {},
"versioned": false
}
},
"keep_log": [],
"locked_dimensions": [
{
"description": "Covers writing, reviewing, and maintaining FRDs that define product behavior, scope, and acceptance expectations. This belongs here because FRDs are a requirements artifact used to align stakeholders before implementation and testing.",
"exemplar_skills": [
"FRDs",
"functional requirements documentation",
"requirements gathering",
"requirements specification",
"acceptance criteria definition",
"feature scoping",
"FRD review"
],
"in_scope": "FRDs, functional requirements documents, requirement statements, scope definitions, business rules, acceptance criteria, feature specifications, FRD review, FRD sign-off",
"name": "Functional Requirements Documents",
"out_of_scope": "Technical design docs, API contracts, test case execution, user stories, and project plans, which are owned by architecture, testing, or delivery planning dimensions.",
"overlap_flags": [
{
"reason": "FRDs often feed test design, but this dimension covers the requirements artifact itself rather than test authoring.",
"with_dim_id": "test-case-design-and-execution",
"with_dim_name": null,
"with_role": "Manual Tester"
},
{
"reason": "Some FRDs describe service behavior, but architecture dimensions own the technical implementation details.",
"with_dim_id": "service-architecture-and-integration",
"with_dim_name": null,
"with_role": "Backend Engineer"
}
],
"tentative_id": "d_init_01"
}
],
"merge_log": [],
"placed": {
"name": "FRDs",
"placement_confidence": 0.92,
"primary_dimension": "d_init_01",
"reasoning": "Deterministic JD placement: locked_dimensions has 1 dimension(s) from skill-driven dimension generation after reconciliation; primary_dimension is the first locked dim.",
"secondary_dimensions": [],
"skill_id": "frds"
},
"relationships": {
"child_skills": [],
"parent_skills": [],
"related_to": [
"change-requests",
"runbooks",
"contract-tests",
"risk-based-testing",
"rollback-readiness"
],
"requires": [],
"skill_id": "frds",
"suppress_on_match": []
},
"skill_id": "frds",
"split_log": [],
"typed": {
"alternatives_considered": [
"Concept: ruled out \u2014 it is not a single theory or principle but a documentation artifact/body of practice.",
"Format: ruled out \u2014 although documents have structure, FRDs are not a wire/data format specification.",
"Methodology: ruled out \u2014 FRDs describe requirements, not a way of working."
],
"confidence": 0.67,
"name": "FRDs",
"reasoning": "FRDs are a body of knowledge/documentation used in product and systems work, so by the Concept vs Methodology rule they fit best as a Domain rather than a tool or format.",
"skill_id": "frds",
"subtype": "functional_requirements_documents",
"type": "Domain"
},
"warnings": []
},
"source_tag": "llm",
"was_in_llm_skills": true
},
{
"aliases_in_db": [],
"canonical": null,
"dimensions": [
{
"dimension": {
"difficulty_hint": null,
"display_name": "Domain Familiarity",
"id": null,
"rationale": "Baseline awareness of a technology, platform, or process sufficient to follow discussions and work effectively with guidance. This fits the target skill because it signals exposure and working recognition rather than deep ownership or hands-on expertise.",
"slug": "d_init_01",
"source": "llm"
},
"input_skill": "Familiarity",
"llm_role": null,
"roles_from_db": []
}
],
"input_skill": "Familiarity",
"matched_via": null,
"new_alias_persisted": false,
"new_alias_text": null,
"new_skill_meta": {
"derived": {
"category": "Concept",
"skill_nature": "CONCEPT",
"sub_category": "familiarity",
"typical_lifespan": "EVERGREEN",
"version_strategy": "NOT_APPLICABLE",
"volatility": "STABLE"
},
"enrichment": {
"ambiguity": {
"ambiguity_flag": false,
"confused_with": [],
"reasoning": "\u201cFamiliarity\u201d is a generic concept, but it is not a plausible alternate reading of a distinct catalog skill in typical JDs; it usually just means prior exposure or experience."
},
"context_keywords": {
"context_keywords": [
"working knowledge",
"hands-on experience",
"exposure",
"proficiency",
"awareness",
"understanding",
"practical experience",
"subject matter",
"domain knowledge",
"baseline knowledge",
"prior experience",
"comfort level",
"familiarity with",
"knowledge of",
"experience with"
]
},
"maturity": {
"confidence": 0.86,
"maturity": "niche",
"reasoning": "\u201cFamiliarity\u201d is a generic concept, not a commonly listed skill in job descriptions; market signals are sparse compared with concrete tools/tech, so it appears only in narrow competency frameworks."
},
"skill_id": "familiarity",
"vendor_license": {
"confidence": 0.99,
"license": null,
"vendor": null,
"year_introduced": null
},
"versioning": {
"current_version": null,
"version_aliases": {},
"versioned": false
}
},
"keep_log": [],
"locked_dimensions": [
{
"description": "Baseline awareness of a technology, platform, or process sufficient to follow discussions and work effectively with guidance. This fits the target skill because it signals exposure and working recognition rather than deep ownership or hands-on expertise.",
"exemplar_skills": [
"Familiarity",
"Working knowledge",
"Exposure to the technology",
"Awareness of platform concepts",
"Basic understanding"
],
"in_scope": "Familiarity with product areas, platform concepts, common terminology, Familiarity with workflows, conventions, and standard practices, Familiarity with tools, frameworks, and services listed in a job description, Familiarity with Familiarity as a stated proficiency level",
"name": "Domain Familiarity",
"out_of_scope": "Deep implementation skill, architecture ownership, or troubleshooting expertise, Formal certification or subject-matter authority, Specific technical disciplines such as API design, testing, or security hardening",
"overlap_flags": [
{
"reason": "Familiarity can be used to describe awareness of service design topics, but this dimension owns the actual architecture and integration skills.",
"with_dim_id": "service-architecture-and-integration",
"with_dim_name": null,
"with_role": "Backend Engineer"
},
{
"reason": "Job descriptions may list familiarity with test frameworks, but the framework-specific competency belongs in the testing dimension.",
"with_dim_id": "testing-and-automation-frameworks",
"with_dim_name": null,
"with_role": "iOS Engineer"
}
],
"tentative_id": "d_init_01"
}
],
"merge_log": [],
"placed": {
"name": "Familiarity",
"placement_confidence": 0.92,
"primary_dimension": "d_init_01",
"reasoning": "Deterministic JD placement: locked_dimensions has 1 dimension(s) from skill-driven dimension generation after reconciliation; primary_dimension is the first locked dim.",
"secondary_dimensions": [],
"skill_id": "familiarity"
},
"relationships": {
"child_skills": [],
"parent_skills": [],
"related_to": [
"confidence-thresholds",
"naming-conventions",
"naming-standards",
"memory-summarization",
"sampling-bias",
"duplicate-detection",
"acceptance-criteria-checks",
"smoke-tests"
],
"requires": [],
"skill_id": "familiarity",
"suppress_on_match": []
},
"skill_id": "familiarity",
"split_log": [],
"typed": {
"alternatives_considered": [],
"confidence": 0.96,
"name": "Familiarity",
"reasoning": "Familiarity is a named knowledge unit about recognition or prior exposure, so by the Concept vs Methodology rule it is a Concept rather than a way of working.",
"skill_id": "familiarity",
"subtype": "familiarity",
"type": "Concept"
},
"warnings": []
},
"source_tag": "llm",
"was_in_llm_skills": true
},
{
"aliases_in_db": [],
"canonical": null,
"dimensions": [
{
"dimension": {
"difficulty_hint": null,
"display_name": "Domain Knowledge",
"id": null,
"rationale": "Subject-matter understanding of the business, product, or technical area a role works in. This skill is broad and often underpins effective decisions, communication, and problem-solving across many engineering tasks.",
"slug": "d_init_01",
"source": "llm"
},
"input_skill": "Knowledge",
"llm_role": null,
"roles_from_db": []
}
],
"input_skill": "Knowledge",
"matched_via": null,
"new_alias_persisted": false,
"new_alias_text": null,
"new_skill_meta": {
"derived": {
"category": "Concept",
"skill_nature": "CONCEPT",
"sub_category": "general_knowledge",
"typical_lifespan": "EVERGREEN",
"version_strategy": "NOT_APPLICABLE",
"volatility": "STABLE"
},
"enrichment": {
"ambiguity": {
"ambiguity_flag": true,
"confused_with": [
"knowledge_management",
"knowledge_graph",
"knowledge_base"
],
"reasoning": "\"Knowledge\" is a very broad concept and in JDs could refer to knowledge management, knowledge graphs, or a knowledge base rather than the generic concept."
},
"context_keywords": {
"context_keywords": [
"domain expertise",
"subject matter expert",
"SME",
"institutional knowledge",
"knowledge base",
"knowledge management",
"knowledge transfer",
"knowledge sharing",
"knowledge graph",
"taxonomy",
"ontology",
"information architecture",
"documentation",
"lessons learned",
"best practices"
]
},
"maturity": {
"confidence": 0.93,
"maturity": "niche",
"reasoning": "\u201cKnowledge\u201d is a generic concept, not a specific engineering skill; it rarely appears as a standalone requirement in job descriptions compared with concrete tools or languages."
},
"skill_id": "knowledge",
"vendor_license": {
"confidence": 0.99,
"license": null,
"vendor": null,
"year_introduced": null
},
"versioning": {
"current_version": null,
"version_aliases": {},
"versioned": false
}
},
"keep_log": [],
"locked_dimensions": [
{
"description": "Subject-matter understanding of the business, product, or technical area a role works in. This skill is broad and often underpins effective decisions, communication, and problem-solving across many engineering tasks.",
"exemplar_skills": [
"Knowledge",
"Domain Knowledge",
"Business Knowledge",
"Product Knowledge",
"Technical Knowledge"
],
"in_scope": "Knowledge, domain knowledge, business context, product understanding, system context, terminology, process awareness, operational concepts, stakeholder needs",
"name": "Domain Knowledge",
"out_of_scope": "Specific implementation skills, coding languages, testing methods, platform administration, security controls, data engineering techniques",
"overlap_flags": [
{
"reason": "Domain understanding often informs service boundaries and integration choices, but the dimension itself is about architecture patterns rather than subject-matter knowledge.",
"with_dim_id": "service-architecture-and-integration",
"with_dim_name": null,
"with_role": "Backend Engineer"
},
{
"reason": "AI product context can require domain knowledge, but this catalog dimension focuses on how AI capabilities are structured in systems.",
"with_dim_id": "ai-service-architecture-patterns",
"with_dim_name": null,
"with_role": "AI Engineer"
}
],
"tentative_id": "d_init_01"
}
],
"merge_log": [],
"placed": {
"name": "Knowledge",
"placement_confidence": 0.92,
"primary_dimension": "d_init_01",
"reasoning": "Deterministic JD placement: locked_dimensions has 1 dimension(s) from skill-driven dimension generation after reconciliation; primary_dimension is the first locked dim.",
"secondary_dimensions": [],
"skill_id": "knowledge"
},
"relationships": {
"child_skills": [],
"parent_skills": [],
"related_to": [],
"requires": [],
"skill_id": "knowledge",
"suppress_on_match": []
},
"skill_id": "knowledge",
"split_log": [],
"typed": {
"alternatives_considered": [],
"confidence": 0.98,
"name": "Knowledge",
"reasoning": "Knowledge is a named knowledge unit rather than a way of working, so by the Concept vs Methodology rule it fits Concept.",
"skill_id": "knowledge",
"subtype": "general_knowledge",
"type": "Concept"
},
"warnings": []
},
"source_tag": "llm",
"was_in_llm_skills": true
},
{
"aliases_in_db": [],
"canonical": null,
"dimensions": [
{
"dimension": {
"difficulty_hint": null,
"display_name": "Quality Assurance Testing",
"id": null,
"rationale": "Validating software behavior against requirements through manual and exploratory testing, defect reporting, and regression checks. QA belongs here when it refers to the hands-on verification discipline used to catch issues before release.",
"slug": "d_init_01",
"source": "llm"
},
"input_skill": "QA",
"llm_role": null,
"roles_from_db": []
}
],
"input_skill": "QA",
"matched_via": null,
"new_alias_persisted": false,
"new_alias_text": null,
"new_skill_meta": {
"derived": {
"category": "Domain",
"skill_nature": "CONCEPT",
"sub_category": "quality_assurance",
"typical_lifespan": "EVERGREEN",
"version_strategy": "NOT_APPLICABLE",
"volatility": "STABLE"
},
"enrichment": {
"ambiguity": {
"ambiguity_flag": true,
"confused_with": [
"quality_assurance",
"quality_control"
],
"reasoning": "\"QA\" is a common abbreviation for Quality Assurance, but in JDs it can also be used loosely for Quality Control or broader testing roles, so an extractor could confuse it with nearby catalog skills."
},
"context_keywords": {
"context_keywords": [
"test cases",
"test plan",
"test strategy",
"regression testing",
"smoke testing",
"UAT",
"bug tracking",
"defect lifecycle",
"test automation",
"Selenium",
"JIRA",
"manual testing",
"acceptance criteria",
"traceability matrix"
]
},
"maturity": {
"confidence": 0.93,
"maturity": "well_known",
"reasoning": "QA appears in a large volume of job descriptions across software teams, often as a standard hiring requirement for test planning, automation, and release validation."
},
"skill_id": "qa",
"vendor_license": {
"confidence": 0.99,
"license": null,
"vendor": null,
"year_introduced": null
},
"versioning": {
"current_version": null,
"version_aliases": {},
"versioned": false
}
},
"keep_log": [],
"locked_dimensions": [
{
"description": "Validating software behavior against requirements through manual and exploratory testing, defect reporting, and regression checks. QA belongs here when it refers to the hands-on verification discipline used to catch issues before release.",
"exemplar_skills": [
"QA",
"manual testing",
"exploratory testing",
"regression testing",
"defect reproduction",
"acceptance testing"
],
"in_scope": "QA, manual testing, exploratory testing, regression testing, defect reproduction, test case execution, acceptance testing, test evidence",
"name": "Quality Assurance Testing",
"out_of_scope": "Automated unit tests, API automation frameworks, CI/CD test orchestration, performance/load testing, which are owned by automation or specialized testing dimensions",
"overlap_flags": [
{
"reason": "This is closely related to manual test design and execution, but QA is the broader quality verification label.",
"with_dim_id": "test-case-design-and-execution",
"with_dim_name": null,
"with_role": "Manual Tester"
},
{
"reason": "QA can overlap with automated testing work when the role includes building or maintaining test frameworks.",
"with_dim_id": "testing-and-automation-frameworks",
"with_dim_name": null,
"with_role": "iOS Engineer"
}
],
"tentative_id": "d_init_01"
}
],
"merge_log": [],
"placed": {
"name": "QA",
"placement_confidence": 0.92,
"primary_dimension": "d_init_01",
"reasoning": "Deterministic JD placement: locked_dimensions has 1 dimension(s) from skill-driven dimension generation after reconciliation; primary_dimension is the first locked dim.",
"secondary_dimensions": [],
"skill_id": "qa"
},
"relationships": {
"child_skills": [],
"parent_skills": [],
"related_to": [
"acceptance-criteria-checks",
"acceptance-criteria-validation",
"test-case-authoring",
"defect-retest",
"risk-based-testing",
"cross-browser-testing",
"session-based-testing",
"charter-based-testing",
"health-checks"
],
"requires": [],
"skill_id": "qa",
"suppress_on_match": []
},
"skill_id": "qa",
"split_log": [],
"typed": {
"alternatives_considered": [],
"confidence": 0.91,
"name": "QA",
"reasoning": "QA is best treated as a Domain because it names a body of knowledge and practice area around software quality, not a specific tool, methodology, or architecture.",
"skill_id": "qa",
"subtype": "quality_assurance",
"type": "Domain"
},
"warnings": []
},
"source_tag": "llm",
"was_in_llm_skills": true
},
{
"aliases_in_db": [],
"canonical": null,
"dimensions": [
{
"dimension": {
"difficulty_hint": null,
"display_name": "Software Delivery Lifecycle",
"id": null,
"rationale": "Covers the end-to-end process of planning, building, testing, releasing, and maintaining software. SDLC belongs here because it refers to the lifecycle framework that organizes engineering work across development stages.",
"slug": "d_init_01",
"source": "llm"
},
"input_skill": "SDLC",
"llm_role": null,
"roles_from_db": []
}
],
"input_skill": "SDLC",
"matched_via": null,
"new_alias_persisted": false,
"new_alias_text": null,
"new_skill_meta": {
"derived": {
"category": "Methodology",
"skill_nature": "METHODOLOGY",
"sub_category": "software_development_lifecycle",
"typical_lifespan": "EVERGREEN",
"version_strategy": "NOT_APPLICABLE",
"volatility": "STABLE"
},
"enrichment": {
"ambiguity": {
"ambiguity_flag": false,
"confused_with": [],
"reasoning": "SDLC is a standard, well-known acronym for software development lifecycle and is usually unambiguous in job descriptions."
},
"context_keywords": {
"context_keywords": [
"requirements gathering",
"design review",
"implementation",
"code review",
"testing",
"QA",
"UAT",
"deployment",
"release management",
"change management",
"Agile",
"Scrum",
"waterfall",
"CI/CD",
"DevOps"
]
},
"maturity": {
"confidence": 0.93,
"maturity": "well_known",
"reasoning": "SDLC is a standard term in software job descriptions and engineering process docs; it appears broadly across roles from dev to QA to DevOps rather than a niche specialty."
},
"skill_id": "sdlc",
"vendor_license": {
"confidence": 0.99,
"license": null,
"vendor": null,
"year_introduced": null
},
"versioning": {
"current_version": null,
"version_aliases": {},
"versioned": false
}
},
"keep_log": [],
"locked_dimensions": [
{
"description": "Covers the end-to-end process of planning, building, testing, releasing, and maintaining software. SDLC belongs here because it refers to the lifecycle framework that organizes engineering work across development stages.",
"exemplar_skills": [
"SDLC",
"software development lifecycle",
"release management",
"change control",
"requirements analysis",
"code review",
"deployment planning"
],
"in_scope": "SDLC, requirements analysis, design, implementation, code review, testing, release management, maintenance, change control, versioning, deployment planning",
"name": "Software Delivery Lifecycle",
"out_of_scope": "Specific test case authoring, API automation, cloud infrastructure provisioning, incident response, product management, and platform administration, which are owned by more specialized dimensions",
"overlap_flags": [
{
"reason": "SDLC includes testing as a phase, but detailed test design and execution belong to the testing dimension.",
"with_dim_id": "test-case-design-and-execution",
"with_dim_name": null,
"with_role": "Manual Tester"
},
{
"reason": "SDLC often involves moving work through environments, but environment setup and promotion are a separate operational concern.",
"with_dim_id": "environment-provisioning-and-promotion",
"with_dim_name": null,
"with_role": "DevOps Engineer"
},
{
"reason": "SDLC can influence design and implementation choices, but service decomposition and integration patterns are a distinct architecture dimension.",
"with_dim_id": "service-architecture-and-integration",
"with_dim_name": null,
"with_role": "Backend Engineer"
}
],
"tentative_id": "d_init_01"
}
],
"merge_log": [],
"placed": {
"name": "SDLC",
"placement_confidence": 0.92,
"primary_dimension": "d_init_01",
"reasoning": "Deterministic JD placement: locked_dimensions has 1 dimension(s) from skill-driven dimension generation after reconciliation; primary_dimension is the first locked dim.",
"secondary_dimensions": [],
"skill_id": "sdlc"
},
"relationships": {
"child_skills": [],
"parent_skills": [],
"related_to": [
"clean-architecture",
"acceptance-criteria-checks",
"acceptance-criteria-validation",
"defect-retest",
"dependency-mapping",
"dashboards",
"scorecards"
],
"requires": [],
"skill_id": "sdlc",
"suppress_on_match": []
},
"skill_id": "sdlc",
"split_log": [],
"typed": {
"alternatives_considered": [],
"confidence": 0.93,
"name": "SDLC",
"reasoning": "SDLC is fundamentally a way of working that describes the process of building software, so by the Concept vs Methodology rule it fits Methodology rather than a tool or architecture.",
"skill_id": "sdlc",
"subtype": "software_development_lifecycle",
"type": "Methodology"
},
"warnings": []
},
"source_tag": "llm",
"was_in_llm_skills": true
},
{
"aliases_in_db": [],
"canonical": null,
"dimensions": [
{
"dimension": {
"difficulty_hint": null,
"display_name": "SaaS Product Delivery",
"id": null,
"rationale": "Covers building, packaging, and operating software delivered as a subscription-hosted service. SaaS belongs here because it refers to the product and delivery model rather than a specific technical subsystem.",
"slug": "d_init_01",
"source": "llm"
},
"input_skill": "SaaS",
"llm_role": null,
"roles_from_db": []
}
],
"input_skill": "SaaS",
"matched_via": null,
"new_alias_persisted": false,
"new_alias_text": null,
"new_skill_meta": {
"derived": {
"category": "Platform",
"skill_nature": "PLATFORM",
"sub_category": "software_as_a_service_platform",
"typical_lifespan": "EVERGREEN",
"version_strategy": "NOT_APPLICABLE",
"volatility": "STABLE"
},
"enrichment": {
"ambiguity": {
"ambiguity_flag": false,
"confused_with": [],
"reasoning": "SaaS is a standard, well-scoped term for software-as-a-service platforms in JDs; it is unlikely to be mistaken for a different catalog skill."
},
"context_keywords": {
"context_keywords": [
"multi-tenant",
"subscription billing",
"tenant isolation",
"self-service onboarding",
"provisioning",
"usage-based pricing",
"SSO",
"SCIM",
"RBAC",
"API integrations",
"admin console",
"customer portal",
"SLAs",
"uptime",
"feature flags"
]
},
"maturity": {
"confidence": 0.96,
"maturity": "well_known",
"reasoning": "SaaS is a standard deployment model in job postings across product, sales, and engineering roles; major vendors like Salesforce, Microsoft, and Google market SaaS offerings as mainstream cloud software."
},
"skill_id": "saas",
"vendor_license": {
"confidence": 0.78,
"license": null,
"vendor": "Salesforce",
"year_introduced": 1999
},
"versioning": {
"current_version": null,
"version_aliases": {},
"versioned": false
}
},
"keep_log": [],
"locked_dimensions": [
{
"description": "Covers building, packaging, and operating software delivered as a subscription-hosted service. SaaS belongs here because it refers to the product and delivery model rather than a specific technical subsystem.",
"exemplar_skills": [
"SaaS",
"software as a service",
"multi-tenant architecture",
"subscription product delivery",
"hosted application operations"
],
"in_scope": "SaaS, software as a service, multi-tenant product delivery, subscription-based application delivery, hosted web application, tenant isolation, service tiers, feature rollout for SaaS products",
"name": "SaaS Product Delivery",
"out_of_scope": "On-premises software deployment, internal enterprise tooling, mobile app lifecycle, cloud infrastructure provisioning, which belong to other platform or application dimensions",
"overlap_flags": [
{
"reason": "SaaS products are often implemented as service-oriented systems, but this dimension is about the delivery model rather than service decomposition.",
"with_dim_id": "service-architecture-and-integration",
"with_dim_name": null,
"with_role": "Backend Engineer"
},
{
"reason": "SaaS operations may involve environment promotion, but that dimension focuses on lifecycle environments rather than the SaaS product model.",
"with_dim_id": "environment-provisioning-and-promotion",
"with_dim_name": null,
"with_role": "DevOps Engineer"
}
],
"tentative_id": "d_init_01"
}
],
"merge_log": [],
"placed": {
"name": "SaaS",
"placement_confidence": 0.92,
"primary_dimension": "d_init_01",
"reasoning": "Deterministic JD placement: locked_dimensions has 1 dimension(s) from skill-driven dimension generation after reconciliation; primary_dimension is the first locked dim.",
"secondary_dimensions": [],
"skill_id": "saas"
},
"relationships": {
"child_skills": [],
"parent_skills": [],
"related_to": [
"cloud-run",
"cspm",
"policy-as-code",
"cloud-reference-architecture"
],
"requires": [],
"skill_id": "saas",
"suppress_on_match": []
},
"skill_id": "saas",
"split_log": [],
"typed": {
"alternatives_considered": [
"Service: ruled out \u2014 SaaS is the broader hosted delivery model, not a specific managed capability inside another platform."
],
"confidence": 0.93,
"name": "SaaS",
"reasoning": "By the Platform vs Tool rule, SaaS is a hosted multi-tenant environment delivered over APIs and managed services, so it is fundamentally a Platform rather than a Tool.",
"skill_id": "saas",
"subtype": "software_as_a_service_platform",
"type": "Platform"
},
"warnings": []
},
"source_tag": "llm",
"was_in_llm_skills": true
},
{
"aliases_in_db": [],
"canonical": null,
"dimensions": [
{
"dimension": {
"difficulty_hint": null,
"display_name": "User Acceptance Testing Execution",
"id": null,
"rationale": "Covers planning and running user acceptance tests to confirm a feature meets business requirements before release. UAT belongs here because it is a manual, acceptance-focused validation step rather than automated technical testing.",
"slug": "d_init_01",
"source": "llm"
},
"input_skill": "UAT",
"llm_role": null,
"roles_from_db": []
}
],
"input_skill": "UAT",
"matched_via": null,
"new_alias_persisted": false,
"new_alias_text": null,
"new_skill_meta": {
"derived": {
"category": "Methodology",
"skill_nature": "METHODOLOGY",
"sub_category": "user_acceptance_testing",
"typical_lifespan": "EVERGREEN",
"version_strategy": "NOT_APPLICABLE",
"volatility": "STABLE"
},
"enrichment": {
"ambiguity": {
"ambiguity_flag": false,
"confused_with": [],
"reasoning": "UAT in JDs almost always means User Acceptance Testing; the acronym is standard and unlikely to be mistaken for another catalog skill in typical hiring context."
},
"context_keywords": {
"context_keywords": [
"test cases",
"acceptance criteria",
"business users",
"end users",
"sign-off",
"test scripts",
"test scenarios",
"defect triage",
"UAT environment",
"test plan",
"go-live",
"stakeholder review",
"regression testing",
"test data",
"issue log"
]
},
"maturity": {
"confidence": 0.93,
"maturity": "well_known",
"reasoning": "UAT is a standard QA/SDLC practice and appears routinely in job descriptions for QA, BA, and release roles; it is not a sunset technology and remains a common acceptance gate in enterprise delivery."
},
"skill_id": "uat",
"vendor_license": {
"confidence": 0.99,
"license": null,
"vendor": null,
"year_introduced": null
},
"versioning": {
"current_version": null,
"version_aliases": {},
"versioned": false
}
},
"keep_log": [],
"locked_dimensions": [
{
"description": "Covers planning and running user acceptance tests to confirm a feature meets business requirements before release. UAT belongs here because it is a manual, acceptance-focused validation step rather than automated technical testing.",
"exemplar_skills": [
"UAT",
"user acceptance testing",
"acceptance test execution",
"manual test cases",
"stakeholder sign-off"
],
"in_scope": "UAT, user acceptance testing, acceptance test execution, business requirement validation, manual test execution, stakeholder sign-off checks, test evidence collection",
"name": "User Acceptance Testing Execution",
"out_of_scope": "unit testing, API contract automation, performance testing, production monitoring, defect triage after release",
"overlap_flags": [
{
"reason": "UAT is a specialized form of manual test execution and acceptance validation, so it overlaps with broader test case work.",
"with_dim_id": "test-case-design-and-execution",
"with_dim_name": null,
"with_role": "Manual Tester"
},
{
"reason": "UAT may validate backend behavior, but automated API and service checks belong to the automation dimension.",
"with_dim_id": "api-and-service-test-automation",
"with_dim_name": null,
"with_role": "Automation Tester"
},
{
"reason": "UAT often depends on test environment readiness and access, but coordinating those prerequisites is a separate concern.",
"with_dim_id": "environment-and-access-coordination",
"with_dim_name": null,
"with_role": "Cloud Migration Engineer"
}
],
"tentative_id": "d_init_01"
}
],
"merge_log": [],
"placed": {
"name": "UAT",
"placement_confidence": 0.92,
"primary_dimension": "d_init_01",
"reasoning": "Deterministic JD placement: locked_dimensions has 1 dimension(s) from skill-driven dimension generation after reconciliation; primary_dimension is the first locked dim.",
"secondary_dimensions": [],
"skill_id": "uat"
},
"relationships": {
"child_skills": [],
"parent_skills": [],
"related_to": [
"acceptance-criteria-checks",
"session-based-testing",
"test-case-authoring"
],
"requires": [],
"skill_id": "uat",
"suppress_on_match": []
},
"skill_id": "uat",
"split_log": [],
"typed": {
"alternatives_considered": [],
"confidence": 0.91,
"name": "UAT",
"reasoning": "UAT is fundamentally a way of working for validating software with end users, so by the Concept vs Methodology rule it is a Methodology rather than a tool or concept.",
"skill_id": "uat",
"subtype": "user_acceptance_testing",
"type": "Methodology"
},
"warnings": []
},
"source_tag": "llm",
"was_in_llm_skills": true
},
{
"aliases_in_db": [],
"canonical": null,
"dimensions": [
{
"dimension": {
"difficulty_hint": null,
"display_name": "Conceptual Understanding",
"id": null,
"rationale": "Covers the ability to comprehend domain concepts, requirements, and system behavior at a high level. This skill is too generic to map cleanly to a narrower engineering cluster, so it is best represented as a foundational cognitive dimension.",
"slug": "d_init_01",
"source": "llm"
},
"input_skill": "Understanding",
"llm_role": null,
"roles_from_db": []
}
],
"input_skill": "Understanding",
"matched_via": null,
"new_alias_persisted": false,
"new_alias_text": null,
"new_skill_meta": {
"derived": {
"category": "Concept",
"skill_nature": "CONCEPT",
"sub_category": "comprehension",
"typical_lifespan": "EVERGREEN",
"version_strategy": "NOT_APPLICABLE",
"volatility": "STABLE"
},
"enrichment": {
"ambiguity": {
"ambiguity_flag": true,
"confused_with": [
"understanding_user_needs",
"understanding_business_requirements"
],
"reasoning": "\"Understanding\" is a generic noun, not a specific skill name. In JDs it could easily refer to understanding user needs or business requirements rather than a distinct catalog skill."
},
"context_keywords": {
"context_keywords": [
"requirements analysis",
"stakeholder needs",
"problem solving",
"root cause analysis",
"domain knowledge",
"system design",
"specification",
"interpretation",
"critical thinking",
"requirements gathering",
"trade-offs",
"user stories",
"acceptance criteria",
"gap analysis"
]
},
"maturity": {
"confidence": 0.86,
"maturity": "well_known",
"reasoning": "Core comprehension is a universal hiring requirement across roles; it appears implicitly in nearly all job descriptions and interview rubrics, though not always named as a standalone skill."
},
"skill_id": "understanding",
"vendor_license": {
"confidence": 0.99,
"license": null,
"vendor": null,
"year_introduced": null
},
"versioning": {
"current_version": null,
"version_aliases": {},
"versioned": false
}
},
"keep_log": [],
"locked_dimensions": [
{
"description": "Covers the ability to comprehend domain concepts, requirements, and system behavior at a high level. This skill is too generic to map cleanly to a narrower engineering cluster, so it is best represented as a foundational cognitive dimension.",
"exemplar_skills": [
"Understanding",
"Comprehension",
"Interpreting requirements",
"Grasping concepts",
"Domain awareness"
],
"in_scope": "Understanding, comprehension, grasping requirements, interpreting concepts, reading system behavior, mental models, domain awareness",
"name": "Conceptual Understanding",
"out_of_scope": "Implementation coding, debugging, testing, architecture design, operational monitoring, security hardening",
"overlap_flags": [],
"tentative_id": "d_init_01"
}
],
"merge_log": [],
"placed": {
"name": "Understanding",
"placement_confidence": 0.92,
"primary_dimension": "d_init_01",
"reasoning": "Deterministic JD placement: locked_dimensions has 1 dimension(s) from skill-driven dimension generation after reconciliation; primary_dimension is the first locked dim.",
"secondary_dimensions": [],
"skill_id": "understanding"
},
"relationships": {
"child_skills": [],
"parent_skills": [],
"related_to": [],
"requires": [],
"skill_id": "understanding",
"suppress_on_match": []
},
"skill_id": "understanding",
"split_log": [],
"typed": {
"alternatives_considered": [],
"confidence": 0.97,
"name": "Understanding",
"reasoning": "Understanding is a named knowledge unit you must know, so by the Concept vs Methodology rule it is a Concept rather than a way of working.",
"skill_id": "understanding",
"subtype": "comprehension",
"type": "Concept"
},
"warnings": []
},
"source_tag": "llm",
"was_in_llm_skills": true
},
{
"aliases_in_db": [],
"canonical": null,
"dimensions": [
{
"dimension": {
"difficulty_hint": null,
"display_name": "Diagramming and Process Modeling",
"id": null,
"rationale": "Covers creating business, system, and workflow diagrams used to communicate structure, process flow, and relationships. Visio belongs here because it is commonly used to draw formal diagrams, maps, and process models.",
"slug": "d_init_01",
"source": "llm"
},
"input_skill": "Visio",
"llm_role": null,
"roles_from_db": []
}
],
"input_skill": "Visio",
"matched_via": null,
"new_alias_persisted": false,
"new_alias_text": null,
"new_skill_meta": {
"derived": {
"category": "Tool",
"skill_nature": "TOOL",
"sub_category": "diagramming_tool",
"typical_lifespan": "EVERGREEN",
"version_strategy": "NOT_APPLICABLE",
"volatility": "STABLE"
},
"enrichment": {
"ambiguity": {
"ambiguity_flag": false,
"confused_with": [],
"reasoning": "Visio is a specific Microsoft diagramming tool; in typical JDs it is unlikely to be confused with another catalog skill."
},
"context_keywords": {
"context_keywords": [
"flowchart",
"swimlane",
"process map",
"BPMN",
"UML",
"network diagram",
"org chart",
"wireframe",
"data flow diagram",
"ERD",
"cross-functional diagram",
"business process",
"workflow",
"site map",
"architecture diagram"
]
},
"maturity": {
"confidence": 0.84,
"maturity": "well_known",
"reasoning": "Common in enterprise JDs for process/network diagrams and Microsoft 365 environments; no vendor sunset, and it remains a standard diagramming tool alongside newer alternatives."
},
"skill_id": "visio",
"vendor_license": {
"confidence": 0.99,
"license": "proprietary",
"vendor": "Microsoft",
"year_introduced": 1992
},
"versioning": {
"current_version": null,
"version_aliases": {},
"versioned": false
}
},
"keep_log": [],
"locked_dimensions": [
{
"description": "Covers creating business, system, and workflow diagrams used to communicate structure, process flow, and relationships. Visio belongs here because it is commonly used to draw formal diagrams, maps, and process models.",
"exemplar_skills": [
"Visio",
"flowchart creation",
"process mapping",
"swimlane diagramming",
"network diagramming",
"UML diagramming",
"BPMN modeling"
],
"in_scope": "Visio, flowcharts, process maps, swimlane diagrams, org charts, network diagrams, UML sketches, BPMN diagrams, system architecture diagrams, floor plans, diagram templates",
"name": "Diagramming and Process Modeling",
"out_of_scope": "Presentation slide design, spreadsheet analysis, CAD drafting, code-based diagram generation, these belong to other document, analytics, or engineering design dimensions",
"overlap_flags": [
{
"reason": "Architecture diagrams can overlap with backend service design, but this dimension is about the diagramming tool and notation rather than service implementation.",
"with_dim_id": "service-architecture-and-integration",
"with_dim_name": null,
"with_role": "Backend Engineer"
}
],
"tentative_id": "d_init_01"
}
],
"merge_log": [],
"placed": {
"name": "Visio",
"placement_confidence": 0.92,
"primary_dimension": "d_init_01",
"reasoning": "Deterministic JD placement: locked_dimensions has 1 dimension(s) from skill-driven dimension generation after reconciliation; primary_dimension is the first locked dim.",
"secondary_dimensions": [],
"skill_id": "visio"
},
"relationships": {
"child_skills": [],
"parent_skills": [],
"related_to": [
"navgraph",
"dashboards",
"session-charters",
"scorecards",
"threat-modeling",
"mvvm",
"portal-pages",
"portal-navigation"
],
"requires": [],
"skill_id": "visio",
"suppress_on_match": []
},
"skill_id": "visio",
"split_log": [],
"typed": {
"alternatives_considered": [],
"confidence": 0.98,
"name": "Visio",
"reasoning": "Visio is software you operate to create diagrams, so by the Tool vs Framework rule it is a Tool rather than something you build applications inside.",
"skill_id": "visio",
"subtype": "diagramming_tool",
"type": "Tool"
},
"warnings": []
},
"source_tag": "llm",
"was_in_llm_skills": true
},
{
"aliases_in_db": [],
"canonical": null,
"dimensions": [],
"input_skill": "analysis",
"matched_via": null,
"new_alias_persisted": false,
"new_alias_text": null,
"new_skill_meta": null,
"source_tag": "llm",
"was_in_llm_skills": true
},
{
"aliases_in_db": [],
"canonical": null,
"dimensions": [],
"input_skill": "communication",
"matched_via": null,
"new_alias_persisted": false,
"new_alias_text": null,
"new_skill_meta": null,
"source_tag": "llm",
"was_in_llm_skills": true
},
{
"aliases_in_db": [],
"canonical": null,
"dimensions": [],
"input_skill": "data",
"matched_via": null,
"new_alias_persisted": false,
"new_alias_text": null,
"new_skill_meta": null,
"source_tag": "llm",
"was_in_llm_skills": true
},
{
"aliases_in_db": [],
"canonical": null,
"dimensions": [],
"input_skill": "databases",
"matched_via": null,
"new_alias_persisted": false,
"new_alias_text": null,
"new_skill_meta": null,
"source_tag": "llm",
"was_in_llm_skills": true
},
{
"aliases_in_db": [],
"canonical": null,
"dimensions": [],
"input_skill": "documentation",
"matched_via": null,
"new_alias_persisted": false,
"new_alias_text": null,
"new_skill_meta": null,
"source_tag": "llm",
"was_in_llm_skills": true
},
{
"aliases_in_db": [],
"canonical": null,
"dimensions": [],
"input_skill": "fintech",
"matched_via": null,
"new_alias_persisted": false,
"new_alias_text": null,
"new_skill_meta": null,
"source_tag": "llm",
"was_in_llm_skills": true
},
{
"aliases_in_db": [],
"canonical": null,
"dimensions": [],
"input_skill": "healthcare",
"matched_via": null,
"new_alias_persisted": false,
"new_alias_text": null,
"new_skill_meta": null,
"source_tag": "llm",
"was_in_llm_skills": true
},
{
"aliases_in_db": [],
"canonical": null,
"dimensions": [],
"input_skill": "insights",
"matched_via": null,
"new_alias_persisted": false,
"new_alias_text": null,
"new_skill_meta": null,
"source_tag": "llm",
"was_in_llm_skills": true
},
{
"aliases_in_db": [],
"canonical": null,
"dimensions": [],
"input_skill": "management",
"matched_via": null,
"new_alias_persisted": false,
"new_alias_text": null,
"new_skill_meta": null,
"source_tag": "llm",
"was_in_llm_skills": true
},
{
"aliases_in_db": [],
"canonical": null,
"dimensions": [],
"input_skill": "methodologies",
"matched_via": null,
"new_alias_persisted": false,
"new_alias_text": null,
"new_skill_meta": null,
"source_tag": "llm",
"was_in_llm_skills": true
},
{
"aliases_in_db": [],
"canonical": null,
"dimensions": [],
"input_skill": "optimization",
"matched_via": null,
"new_alias_persisted": false,
"new_alias_text": null,
"new_skill_meta": null,
"source_tag": "llm",
"was_in_llm_skills": true
},
{
"aliases_in_db": [],
"canonical": null,
"dimensions": [],
"input_skill": "reporting",
"matched_via": null,
"new_alias_persisted": false,
"new_alias_text": null,
"new_skill_meta": null,
"source_tag": "llm",
"was_in_llm_skills": true
},
{
"aliases_in_db": [],
"canonical": null,
"dimensions": [],
"input_skill": "software",
"matched_via": null,
"new_alias_persisted": false,
"new_alias_text": null,
"new_skill_meta": null,
"source_tag": "llm",
"was_in_llm_skills": true
},
{
"aliases_in_db": [],
"canonical": null,
"dimensions": [],
"input_skill": "stakeholder",
"matched_via": null,
"new_alias_persisted": false,
"new_alias_text": null,
"new_skill_meta": null,
"source_tag": "llm",
"was_in_llm_skills": true
},
{
"aliases_in_db": [],
"canonical": null,
"dimensions": [],
"input_skill": "stories",
"matched_via": null,
"new_alias_persisted": false,
"new_alias_text": null,
"new_skill_meta": null,
"source_tag": "llm",
"was_in_llm_skills": true
},
{
"aliases_in_db": [],
"canonical": null,
"dimensions": [],
"input_skill": "trends",
"matched_via": null,
"new_alias_persisted": false,
"new_alias_text": null,
"new_skill_meta": null,
"source_tag": "llm",
"was_in_llm_skills": true
},
{
"aliases_in_db": [],
"canonical": null,
"dimensions": [],
"input_skill": "workshops",
"matched_via": null,
"new_alias_persisted": false,
"new_alias_text": null,
"new_skill_meta": null,
"source_tag": "llm",
"was_in_llm_skills": true
}
],
"unmatched_skills": [
"APIs",
"Acceptance",
"BI",
"CBAP",
"CCBA",
"Excel",
"FRDs",
"Familiarity",
"Knowledge",
"QA",
"SDLC",
"SaaS",
"UAT",
"Understanding",
"Visio"
]
}
API 3 — final-role-output
{
"chosen_role": {
"display_name": "Data Analyst",
"id": 20,
"rationale": "The strongest dimension signal is reporting and dashboard development mapped directly to Data Analyst, with the remaining dimensions being broader and less specific.",
"role_archetype": null,
"slug": "data-analyst",
"source": "db"
},
"final_input_skills": [
{
"skill": "Argo Workflows",
"tag": "in_db"
},
{
"skill": "Power BI",
"tag": "in_db"
},
{
"skill": "Tableau",
"tag": "in_db"
},
{
"skill": "APIs",
"tag": "new"
},
{
"skill": "Acceptance",
"tag": "new"
},
{
"skill": "BI",
"tag": "new"
},
{
"skill": "CBAP",
"tag": "new"
},
{
"skill": "CCBA",
"tag": "new"
},
{
"skill": "Excel",
"tag": "new"
},
{
"skill": "FRDs",
"tag": "new"
},
{
"skill": "Familiarity",
"tag": "new"
},
{
"skill": "Knowledge",
"tag": "new"
},
{
"skill": "QA",
"tag": "new"
},
{
"skill": "SDLC",
"tag": "new"
},
{
"skill": "SaaS",
"tag": "new"
},
{
"skill": "UAT",
"tag": "new"
},
{
"skill": "Understanding",
"tag": "new"
},
{
"skill": "Visio",
"tag": "new"
},
{
"skill": "analysis",
"tag": "new"
},
{
"skill": "communication",
"tag": "new"
},
{
"skill": "data",
"tag": "new"
},
{
"skill": "databases",
"tag": "new"
},
{
"skill": "documentation",
"tag": "new"
},
{
"skill": "fintech",
"tag": "new"
},
{
"skill": "healthcare",
"tag": "new"
},
{
"skill": "insights",
"tag": "new"
},
{
"skill": "management",
"tag": "new"
},
{
"skill": "methodologies",
"tag": "new"
},
{
"skill": "optimization",
"tag": "new"
},
{
"skill": "reporting",
"tag": "new"
},
{
"skill": "software",
"tag": "new"
},
{
"skill": "stakeholder",
"tag": "new"
},
{
"skill": "stories",
"tag": "new"
},
{
"skill": "trends",
"tag": "new"
},
{
"skill": "workshops",
"tag": "new"
}
],
"persistence": {
"items": [
{
"chosen_role_id": 20,
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Workflow Orchestration Systems",
"id": 64,
"rationale": "Operational orchestration of ML jobs, dependencies, and handoffs across training, validation, deployment, and retraining. This is a useful split from training pipelines because it emphasizes the scheduler and control plane.",
"slug": "workflow-orchestration-systems",
"source": "db"
},
"dimension_id": 64,
"input_skill": "Argo Workflows",
"llm_role": null,
"matched_chosen_role": false,
"role_dimension_saved": false,
"roles_from_db": [
{
"display_name": "Data Engineer",
"id": 6,
"rationale": null,
"role_archetype": null,
"slug": "data-engineer",
"source": "db"
},
{
"display_name": "MLOps Engineer",
"id": 5,
"rationale": null,
"role_archetype": null,
"slug": "mlops-engineer",
"source": "db"
}
],
"skill_dimension_saved": false,
"skill_id": 380,
"skill_tag": "in_db",
"skipped_reason": "TODO: REMOVE AFTER TESTING \u2014 api3_writes_enabled=False (writes disabled)"
},
{
"chosen_role_id": 20,
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Reporting and Dashboard Development",
"id": 295,
"rationale": "Building recurring reports and dashboards that track performance over time and across segments. This is a distinct cluster because the analyst must package metrics into reusable views for stakeholders.",
"slug": "reporting-and-dashboard-development",
"source": "db"
},
"dimension_id": 295,
"input_skill": "Power BI",
"llm_role": null,
"matched_chosen_role": true,
"role_dimension_saved": false,
"roles_from_db": [
{
"display_name": "Data Analyst",
"id": 20,
"rationale": null,
"role_archetype": null,
"slug": "data-analyst",
"source": "db"
}
],
"skill_dimension_saved": false,
"skill_id": 1884,
"skill_tag": "in_db",
"skipped_reason": "TODO: REMOVE AFTER TESTING \u2014 api3_writes_enabled=False (writes disabled)"
},
{
"chosen_role_id": 20,
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Reporting and Dashboard Development",
"id": 295,
"rationale": "Building recurring reports and dashboards that track performance over time and across segments. This is a distinct cluster because the analyst must package metrics into reusable views for stakeholders.",
"slug": "reporting-and-dashboard-development",
"source": "db"
},
"dimension_id": 295,
"input_skill": "Tableau",
"llm_role": null,
"matched_chosen_role": true,
"role_dimension_saved": false,
"roles_from_db": [
{
"display_name": "Data Analyst",
"id": 20,
"rationale": null,
"role_archetype": null,
"slug": "data-analyst",
"source": "db"
}
],
"skill_dimension_saved": false,
"skill_id": 1883,
"skill_tag": "in_db",
"skipped_reason": "TODO: REMOVE AFTER TESTING \u2014 api3_writes_enabled=False (writes disabled)"
},
{
"chosen_role_id": 20,
"dimension": {
"difficulty_hint": null,
"display_name": "API Design and Integration",
"id": null,
"rationale": "Covers designing, consuming, and coordinating application programming interfaces across services and clients. APIs belongs here because it is the core surface for defining contracts, endpoints, and request/response interactions.",
"slug": "d_init_01",
"source": "llm"
},
"dimension_id": null,
"input_skill": "APIs",
"llm_role": null,
"matched_chosen_role": false,
"role_dimension_saved": false,
"roles_from_db": [],
"skill_dimension_saved": false,
"skill_id": null,
"skill_tag": "new",
"skipped_reason": "skill_not_in_db_v3_proposed"
},
{
"chosen_role_id": 20,
"dimension": {
"difficulty_hint": null,
"display_name": "Acceptance Testing",
"id": null,
"rationale": "Validating that a feature, change, or deliverable meets agreed requirements and acceptance criteria. This is the most direct fit for the skill Acceptance when it refers to sign-off, user acceptance, or requirement-based approval.",
"slug": "d_init_01",
"source": "llm"
},
"dimension_id": null,
"input_skill": "Acceptance",
"llm_role": null,
"matched_chosen_role": false,
"role_dimension_saved": false,
"roles_from_db": [],
"skill_dimension_saved": false,
"skill_id": null,
"skill_tag": "new",
"skipped_reason": "skill_not_in_db_v3_proposed"
},
{
"chosen_role_id": 20,
"dimension": {
"difficulty_hint": null,
"display_name": "Business Intelligence",
"id": null,
"rationale": "Covers the analysis, reporting, and dashboarding work used to turn data into business-facing insights. BI belongs here because it typically refers to the practice of building and consuming reports, metrics, and visual summaries for decision-making.",
"slug": "d_init_01",
"source": "llm"
},
"dimension_id": null,
"input_skill": "BI",
"llm_role": null,
"matched_chosen_role": false,
"role_dimension_saved": false,
"roles_from_db": [],
"skill_dimension_saved": false,
"skill_id": null,
"skill_tag": "new",
"skipped_reason": "skill_not_in_db_v3_proposed"
},
{
"chosen_role_id": 20,
"dimension": {
"difficulty_hint": null,
"display_name": "Business Analysis Certification",
"id": null,
"rationale": "Formal business analysis credentialing and the competency set associated with the CBAP designation. This belongs here because CBAP is a certification focused on business analysis practices, requirements work, and stakeholder-centered analysis.",
"slug": "d_init_01",
"source": "llm"
},
"dimension_id": null,
"input_skill": "CBAP",
"llm_role": null,
"matched_chosen_role": false,
"role_dimension_saved": false,
"roles_from_db": [],
"skill_dimension_saved": false,
"skill_id": null,
"skill_tag": "new",
"skipped_reason": "skill_not_in_db_v3_proposed"
},
{
"chosen_role_id": 20,
"dimension": {
"difficulty_hint": null,
"display_name": "Business Analysis Certification",
"id": null,
"rationale": "Formal business analysis credentialing and competency standards for practitioners who elicit, analyze, document, and validate business requirements. CCBA fits here as a recognized certification focused on business analysis knowledge and practice.",
"slug": "d_init_01",
"source": "llm"
},
"dimension_id": null,
"input_skill": "CCBA",
"llm_role": null,
"matched_chosen_role": false,
"role_dimension_saved": false,
"roles_from_db": [],
"skill_dimension_saved": false,
"skill_id": null,
"skill_tag": "new",
"skipped_reason": "skill_not_in_db_v3_proposed"
},
{
"chosen_role_id": 20,
"dimension": {
"difficulty_hint": null,
"display_name": "Spreadsheet Analysis and Modeling",
"id": null,
"rationale": "Covers using Excel to organize, analyze, and model tabular data with formulas, functions, pivots, and charts. Excel belongs here because it is the primary spreadsheet tool for ad hoc analysis, reporting, and lightweight business modeling.",
"slug": "d_init_01",
"source": "llm"
},
"dimension_id": null,
"input_skill": "Excel",
"llm_role": null,
"matched_chosen_role": false,
"role_dimension_saved": false,
"roles_from_db": [],
"skill_dimension_saved": false,
"skill_id": null,
"skill_tag": "new",
"skipped_reason": "skill_not_in_db_v3_proposed"
},
{
"chosen_role_id": 20,
"dimension": {
"difficulty_hint": null,
"display_name": "Functional Requirements Documents",
"id": null,
"rationale": "Covers writing, reviewing, and maintaining FRDs that define product behavior, scope, and acceptance expectations. This belongs here because FRDs are a requirements artifact used to align stakeholders before implementation and testing.",
"slug": "d_init_01",
"source": "llm"
},
"dimension_id": null,
"input_skill": "FRDs",
"llm_role": null,
"matched_chosen_role": false,
"role_dimension_saved": false,
"roles_from_db": [],
"skill_dimension_saved": false,
"skill_id": null,
"skill_tag": "new",
"skipped_reason": "skill_not_in_db_v3_proposed"
},
{
"chosen_role_id": 20,
"dimension": {
"difficulty_hint": null,
"display_name": "Domain Familiarity",
"id": null,
"rationale": "Baseline awareness of a technology, platform, or process sufficient to follow discussions and work effectively with guidance. This fits the target skill because it signals exposure and working recognition rather than deep ownership or hands-on expertise.",
"slug": "d_init_01",
"source": "llm"
},
"dimension_id": null,
"input_skill": "Familiarity",
"llm_role": null,
"matched_chosen_role": false,
"role_dimension_saved": false,
"roles_from_db": [],
"skill_dimension_saved": false,
"skill_id": null,
"skill_tag": "new",
"skipped_reason": "skill_not_in_db_v3_proposed"
},
{
"chosen_role_id": 20,
"dimension": {
"difficulty_hint": null,
"display_name": "Domain Knowledge",
"id": null,
"rationale": "Subject-matter understanding of the business, product, or technical area a role works in. This skill is broad and often underpins effective decisions, communication, and problem-solving across many engineering tasks.",
"slug": "d_init_01",
"source": "llm"
},
"dimension_id": null,
"input_skill": "Knowledge",
"llm_role": null,
"matched_chosen_role": false,
"role_dimension_saved": false,
"roles_from_db": [],
"skill_dimension_saved": false,
"skill_id": null,
"skill_tag": "new",
"skipped_reason": "skill_not_in_db_v3_proposed"
},
{
"chosen_role_id": 20,
"dimension": {
"difficulty_hint": null,
"display_name": "Quality Assurance Testing",
"id": null,
"rationale": "Validating software behavior against requirements through manual and exploratory testing, defect reporting, and regression checks. QA belongs here when it refers to the hands-on verification discipline used to catch issues before release.",
"slug": "d_init_01",
"source": "llm"
},
"dimension_id": null,
"input_skill": "QA",
"llm_role": null,
"matched_chosen_role": false,
"role_dimension_saved": false,
"roles_from_db": [],
"skill_dimension_saved": false,
"skill_id": null,
"skill_tag": "new",
"skipped_reason": "skill_not_in_db_v3_proposed"
},
{
"chosen_role_id": 20,
"dimension": {
"difficulty_hint": null,
"display_name": "Software Delivery Lifecycle",
"id": null,
"rationale": "Covers the end-to-end process of planning, building, testing, releasing, and maintaining software. SDLC belongs here because it refers to the lifecycle framework that organizes engineering work across development stages.",
"slug": "d_init_01",
"source": "llm"
},
"dimension_id": null,
"input_skill": "SDLC",
"llm_role": null,
"matched_chosen_role": false,
"role_dimension_saved": false,
"roles_from_db": [],
"skill_dimension_saved": false,
"skill_id": null,
"skill_tag": "new",
"skipped_reason": "skill_not_in_db_v3_proposed"
},
{
"chosen_role_id": 20,
"dimension": {
"difficulty_hint": null,
"display_name": "SaaS Product Delivery",
"id": null,
"rationale": "Covers building, packaging, and operating software delivered as a subscription-hosted service. SaaS belongs here because it refers to the product and delivery model rather than a specific technical subsystem.",
"slug": "d_init_01",
"source": "llm"
},
"dimension_id": null,
"input_skill": "SaaS",
"llm_role": null,
"matched_chosen_role": false,
"role_dimension_saved": false,
"roles_from_db": [],
"skill_dimension_saved": false,
"skill_id": null,
"skill_tag": "new",
"skipped_reason": "skill_not_in_db_v3_proposed"
},
{
"chosen_role_id": 20,
"dimension": {
"difficulty_hint": null,
"display_name": "User Acceptance Testing Execution",
"id": null,
"rationale": "Covers planning and running user acceptance tests to confirm a feature meets business requirements before release. UAT belongs here because it is a manual, acceptance-focused validation step rather than automated technical testing.",
"slug": "d_init_01",
"source": "llm"
},
"dimension_id": null,
"input_skill": "UAT",
"llm_role": null,
"matched_chosen_role": false,
"role_dimension_saved": false,
"roles_from_db": [],
"skill_dimension_saved": false,
"skill_id": null,
"skill_tag": "new",
"skipped_reason": "skill_not_in_db_v3_proposed"
},
{
"chosen_role_id": 20,
"dimension": {
"difficulty_hint": null,
"display_name": "Conceptual Understanding",
"id": null,
"rationale": "Covers the ability to comprehend domain concepts, requirements, and system behavior at a high level. This skill is too generic to map cleanly to a narrower engineering cluster, so it is best represented as a foundational cognitive dimension.",
"slug": "d_init_01",
"source": "llm"
},
"dimension_id": null,
"input_skill": "Understanding",
"llm_role": null,
"matched_chosen_role": false,
"role_dimension_saved": false,
"roles_from_db": [],
"skill_dimension_saved": false,
"skill_id": null,
"skill_tag": "new",
"skipped_reason": "skill_not_in_db_v3_proposed"
},
{
"chosen_role_id": 20,
"dimension": {
"difficulty_hint": null,
"display_name": "Diagramming and Process Modeling",
"id": null,
"rationale": "Covers creating business, system, and workflow diagrams used to communicate structure, process flow, and relationships. Visio belongs here because it is commonly used to draw formal diagrams, maps, and process models.",
"slug": "d_init_01",
"source": "llm"
},
"dimension_id": null,
"input_skill": "Visio",
"llm_role": null,
"matched_chosen_role": false,
"role_dimension_saved": false,
"roles_from_db": [],
"skill_dimension_saved": false,
"skill_id": null,
"skill_tag": "new",
"skipped_reason": "skill_not_in_db_v3_proposed"
}
],
"new_skills_created": 0,
"role_dimension_saved": 0,
"skill_dimension_saved": 0,
"skipped": 18
},
"planner_output": null,
"run_id": "d3796043-b383-4453-b1be-f092c9b5635c"
}
LLM Calls
Every model call made for this run, in pipeline order. Click a card to see the model's response.
Loading…