Pipeline run
c109cdd1-f6fd-459e-96f2-c7e0a80b22f1
Client output enrichment
v2 Skill cluster · Nature of work · AI index · Tech stack maturity · Evidence · KRA descriptionNature 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-08T10:32:08.006628Z
Updated: 2026-05-08T10:34:14.760897Z
API 3 duration: 1186 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
Business Analyst
slug: business-analyst · id: — · source: llm
The strongest evidence centers on requirements, UAT, FRDs, QA, and process/documentation work, aligning best with Business Analyst.
0
New skills
0
Skill↔dim saved
0
Role↔dim saved
15
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 |
User Acceptance Validation
d_init_01
|
— | — | — | skill_not_in_db_v3_proposed |
| BI | new |
Business Intelligence Reporting
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 Reporting
d_init_01
|
— | — | — | skill_not_in_db_v3_proposed |
| FRDs | new |
Functional Requirements Documentation
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 Model
d_init_01
|
— | — | — | skill_not_in_db_v3_proposed |
| UAT | new |
User Acceptance Testing
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=Concept subtype=application_programming_interfaces nature=CONCEPT 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 | QA | type=Methodology subtype=quality_assurance nature=METHODOLOGY 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 | 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 | User Acceptance Validation | |
| dimension_skill_link_proposed | Acceptance ↔ User Acceptance Validation | |
| dimension_proposed | Business Intelligence Reporting | |
| dimension_skill_link_proposed | BI ↔ Business Intelligence Reporting | |
| 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 Reporting | |
| dimension_skill_link_proposed | Excel ↔ Spreadsheet Analysis and Reporting | |
| dimension_proposed | Functional Requirements Documentation | |
| dimension_skill_link_proposed | FRDs ↔ Functional Requirements Documentation | |
| 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 Model | |
| dimension_skill_link_proposed | SaaS ↔ SaaS Product Model | |
| dimension_proposed | User Acceptance Testing | |
| dimension_skill_link_proposed | UAT ↔ User Acceptance Testing | |
| 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",
"Familiarity",
"Gather",
"Health",
"Hybrid",
"Job",
"Key",
"Knowledge",
"Learning",
"Location",
"Monitor",
"Power",
"Preferred",
"Qualifications",
"Remote",
"Required",
"Responsibilities",
"Role",
"Science",
"Skills",
"Support",
"Testing",
"Title",
"Understanding",
"User",
"Years",
"abilities",
"analysis",
"candidate",
"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",
"software",
"solutions",
"specifications",
"stakeholder",
"stakeholders",
"stories",
"strategies",
"teams",
"tools",
"trends",
"work",
"workshops"
],
"final_skills": [
"Argo Workflows",
"Power BI",
"Tableau",
"APIs",
"Acceptance",
"BI",
"CBAP",
"CCBA",
"Excel",
"FRDs",
"QA",
"SDLC",
"SaaS",
"UAT",
"Visio"
],
"initial_skills": [
"Argo Workflows",
"Power BI",
"Tableau"
],
"jd_role_hint": {
"display_name": "Business Analyst",
"rationale": "The excerpt explicitly states the role title and repeatedly describes requirement gathering, process analysis, and stakeholder coordination.",
"role_archetype": "Business analysis professional who gathers requirements, documents processes, and translates stakeholder needs into functional specifications.",
"slug": "business-analyst"
},
"llm_non_skills": [
"2\u20135",
"Ability",
"Analyst",
"BRDs",
"Bachelor",
"Benefits",
"Business",
"Certification",
"Computer",
"Conduct",
"Description",
"Ensure",
"Experience",
"Exposure",
"Familiarity",
"Gather",
"Health",
"Hybrid",
"Job",
"Key",
"Knowledge",
"Learning",
"Location",
"Monitor",
"Power",
"Preferred",
"Qualifications",
"Remote",
"Required",
"Responsibilities",
"Role",
"Science",
"Skills",
"Support",
"Testing",
"Title",
"Understanding",
"User",
"Years",
"abilities",
"analysis",
"candidate",
"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",
"software",
"solutions",
"specifications",
"stakeholder",
"stakeholders",
"stories",
"strategies",
"teams",
"tools",
"trends",
"work",
"workshops"
],
"llm_skills": [
"APIs",
"Acceptance",
"BI",
"CBAP",
"CCBA",
"Excel",
"FRDs",
"QA",
"SDLC",
"SaaS",
"UAT",
"Visio"
],
"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": "Business Analyst",
"id": null,
"rationale": "The strongest evidence centers on requirements, UAT, FRDs, QA, and process/documentation work, aligning best with Business Analyst.",
"role_archetype": "Business analysis professional who gathers requirements, documents processes, and translates stakeholder needs into functional specifications.",
"slug": "business-analyst",
"source": "llm"
},
"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": "Designing how systems expose and consume APIs, including contracts, endpoints, and integration patterns. APIs belong here because they are the primary interface for connecting business capabilities across applications and external partners.",
"slug": "d_init_01",
"source": "llm"
},
"input_skill": "APIs",
"llm_role": null,
"roles_from_db": []
},
{
"dimension": {
"difficulty_hint": null,
"display_name": "User Acceptance Validation",
"id": null,
"rationale": "Covers confirming that a feature, process, or deliverable meets business expectations and is ready for sign-off. This fits the skill \u0027Acceptance\u0027 when used in a business analysis or requirements context, especially around stakeholder approval and user acceptance testing.",
"slug": "d_init_01",
"source": "llm"
},
"input_skill": "Acceptance",
"llm_role": null,
"roles_from_db": []
},
{
"dimension": {
"difficulty_hint": null,
"display_name": "Business Intelligence Reporting",
"id": null,
"rationale": "Covers the creation and use of reports, dashboards, KPIs, and ad hoc analysis that help business users monitor performance and make decisions. BI fits here because it commonly refers to the reporting and analytical layer used by analysts and stakeholders.",
"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 body of knowledge associated with it. CBAP belongs here because it is a certification for experienced business analysts and signals mastery of requirements, stakeholder, and solution analysis practices.",
"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": "Professional business analysis credentialing and exam-oriented competency for analysts. CCBA belongs here because it is a recognized certification focused on business analysis knowledge, techniques, and standards rather than a specific tool or platform.",
"slug": "d_init_01",
"source": "llm"
},
"input_skill": "CCBA",
"llm_role": null,
"roles_from_db": []
},
{
"dimension": {
"difficulty_hint": null,
"display_name": "Spreadsheet Analysis and Reporting",
"id": null,
"rationale": "Covers using Excel for tabular analysis, calculations, reporting, and lightweight business modeling. This fits Excel because the skill is primarily about working with spreadsheets to organize data, summarize findings, and communicate results.",
"slug": "d_init_01",
"source": "llm"
},
"input_skill": "Excel",
"llm_role": null,
"roles_from_db": []
},
{
"dimension": {
"difficulty_hint": null,
"display_name": "Functional Requirements Documentation",
"id": null,
"rationale": "Covers writing and maintaining functional requirement documents that define what a product or process must do. FRDs belong here because they capture business needs, scope, rules, and acceptance intent in a structured specification.",
"slug": "d_init_01",
"source": "llm"
},
"input_skill": "FRDs",
"llm_role": null,
"roles_from_db": []
},
{
"dimension": {
"difficulty_hint": null,
"display_name": "Quality Assurance Testing",
"id": null,
"rationale": "Planning and performing manual validation to confirm features meet requirements and acceptance criteria. QA belongs here when it means checking product behavior, finding defects, and verifying fixes rather than automated framework work.",
"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 overall lifecycle framework rather than a single technical practice.",
"slug": "d_init_01",
"source": "llm"
},
"input_skill": "SDLC",
"llm_role": null,
"roles_from_db": []
},
{
"dimension": {
"difficulty_hint": null,
"display_name": "SaaS Product Model",
"id": null,
"rationale": "Covers software delivered as a subscription-based hosted service, including multi-tenant product concepts, packaging, pricing, and customer lifecycle considerations. SaaS belongs here because it describes the delivery and business model of the software rather than a specific technical implementation area.",
"slug": "d_init_01",
"source": "llm"
},
"input_skill": "SaaS",
"llm_role": null,
"roles_from_db": []
},
{
"dimension": {
"difficulty_hint": null,
"display_name": "User Acceptance Testing",
"id": null,
"rationale": "Validating that a feature meets business requirements and is ready for user sign-off. UAT belongs here because it focuses on end-user scenarios, acceptance criteria, and stakeholder approval rather than technical test automation.",
"slug": "d_init_01",
"source": "llm"
},
"input_skill": "UAT",
"llm_role": null,
"roles_from_db": []
},
{
"dimension": {
"difficulty_hint": null,
"display_name": "Diagramming and Process Modeling",
"id": null,
"rationale": "Creating business and technical diagrams to communicate workflows, systems, and relationships. Visio belongs here because it is commonly used to draw process maps, flowcharts, swimlanes, and architecture sketches for analysis and documentation.",
"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",
"QA",
"SDLC",
"SaaS",
"UAT",
"Visio"
],
"input_llm_skills": [
"APIs",
"Acceptance",
"BI",
"CBAP",
"CCBA",
"Excel",
"FRDs",
"QA",
"SDLC",
"SaaS",
"UAT",
"Visio"
],
"new_aliases_persisted": 0,
"run_id": "c109cdd1-f6fd-459e-96f2-c7e0a80b22f1",
"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": "Designing how systems expose and consume APIs, including contracts, endpoints, and integration patterns. APIs belong here because they are the primary interface for connecting business capabilities across applications and external partners.",
"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": "Concept",
"skill_nature": "CONCEPT",
"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, widely used term in JDs and usually appears in clear software context; it is unlikely to be confused with a different catalog skill."
},
"context_keywords": {
"context_keywords": [
"REST",
"GraphQL",
"OpenAPI",
"Swagger",
"JSON",
"XML",
"OAuth 2.0",
"API gateway",
"endpoint",
"webhooks",
"rate limiting",
"versioning",
"microservices",
"SDK",
"Postman"
]
},
"maturity": {
"confidence": 0.97,
"maturity": "well_known",
"reasoning": "APIs are a hiring-pipeline staple across backend, frontend, and platform JDs; REST/GraphQL/API design appears in large volumes of job postings and vendor docs."
},
"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": "Designing how systems expose and consume APIs, including contracts, endpoints, and integration patterns. APIs belong here because they are the primary interface for connecting business capabilities across applications and external partners.",
"exemplar_skills": [
"APIs",
"REST APIs",
"API design",
"service contracts",
"webhooks",
"endpoint versioning"
],
"in_scope": "APIs, REST APIs, endpoint design, request/response schemas, service contracts, versioning, pagination, error handling, webhook integration",
"name": "API Design and Integration",
"out_of_scope": "UI component behavior, database schema design, packet-level network analysis, automated API test frameworks, authentication session UI flows",
"overlap_flags": [
{
"reason": "API work often overlaps with validating endpoints, but this dimension is about designing and integrating APIs rather than automating their tests.",
"with_dim_id": "api-and-service-test-automation",
"with_dim_name": null,
"with_role": null
},
{
"reason": "APIs frequently carry auth concerns, but session and sign-in implementation belongs to the authentication dimension.",
"with_dim_id": "authentication-flows-and-session-handling",
"with_dim_name": null,
"with_role": null
}
],
"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",
"aws-cdk",
"mock-servers",
"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.97,
"name": "APIs",
"reasoning": "APIs are a named technical knowledge unit describing how software systems expose and consume functionality, so by the Concept vs Methodology rule they are a Concept rather than a Tool or Platform.",
"skill_id": "apis",
"subtype": "application_programming_interfaces",
"type": "Concept"
},
"warnings": []
},
"source_tag": "llm",
"was_in_llm_skills": true
},
{
"aliases_in_db": [],
"canonical": null,
"dimensions": [
{
"dimension": {
"difficulty_hint": null,
"display_name": "User Acceptance Validation",
"id": null,
"rationale": "Covers confirming that a feature, process, or deliverable meets business expectations and is ready for sign-off. This fits the skill \u0027Acceptance\u0027 when used in a business analysis or requirements context, especially around stakeholder approval and user acceptance testing.",
"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 term in JDs and could easily be used to mean acceptance testing or user acceptance, which is a distinct catalog skill."
},
"context_keywords": {
"context_keywords": [
"UAT",
"user acceptance testing",
"acceptance criteria",
"acceptance test",
"sign-off",
"definition of done",
"test cases",
"QA",
"stakeholder approval",
"validation",
"verification",
"requirements traceability",
"release readiness",
"go/no-go",
"test plan"
]
},
"maturity": {
"confidence": 0.78,
"maturity": "niche",
"reasoning": "\u201cAcceptance\u201d as a standalone engineering concept appears in few job descriptions; market demand is usually for specific acceptance testing/UAT tools or frameworks rather than the concept itself."
},
"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": "Covers confirming that a feature, process, or deliverable meets business expectations and is ready for sign-off. This fits the skill \u0027Acceptance\u0027 when used in a business analysis or requirements context, especially around stakeholder approval and user acceptance testing.",
"exemplar_skills": [
"Acceptance",
"acceptance criteria",
"user acceptance testing",
"business sign-off",
"stakeholder approval",
"requirement validation"
],
"in_scope": "Acceptance, acceptance criteria, user acceptance testing, business sign-off, stakeholder approval, requirement validation, fit-for-use review",
"name": "User Acceptance Validation",
"out_of_scope": "Manual test case authoring, automated regression suites, API test automation, those belong to testing execution dimensions",
"overlap_flags": [
{
"reason": "Acceptance often appears in UAT and manual testing workflows, so it can overlap with test case execution when the focus is verification rather than business approval.",
"with_dim_id": "test-case-design-and-execution",
"with_dim_name": null,
"with_role": null
},
{
"reason": "In analytics contexts, acceptance may mean approving data quality or fitness for use, which overlaps with dataset assessment.",
"with_dim_id": "data-quality-assessment",
"with_dim_name": null,
"with_role": null
}
],
"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 acceptance is not a process or workflow like Agile or TDD.",
"SoftSkill: ruled out \u2014 while acceptance can be interpersonal in plain English, the skill name here most likely refers to the technical/product concept."
],
"confidence": 0.72,
"name": "Acceptance",
"reasoning": "By the Concept vs Methodology rule, Acceptance is best treated as a named knowledge unit about validating whether requirements or criteria are met, rather than a way of working.",
"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 Reporting",
"id": null,
"rationale": "Covers the creation and use of reports, dashboards, KPIs, and ad hoc analysis that help business users monitor performance and make decisions. BI fits here because it commonly refers to the reporting and analytical layer used by analysts and stakeholders.",
"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/reporting contexts that may map to the fuller business_intelligence skill."
},
"context_keywords": {
"context_keywords": [
"dashboards",
"KPI",
"ETL",
"data warehouse",
"OLAP",
"SQL",
"Tableau",
"Power BI",
"Looker",
"reporting",
"data modeling",
"semantic layer",
"ad hoc analysis",
"data mart",
"SSRS"
]
},
"maturity": {
"confidence": 0.91,
"maturity": "well_known",
"reasoning": "BI is a common hiring keyword across analytics, reporting, and data roles; job boards regularly list Tableau/Power BI/Looker BI experience as a baseline requirement, showing broad market adoption."
},
"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 creation and use of reports, dashboards, KPIs, and ad hoc analysis that help business users monitor performance and make decisions. BI fits here because it commonly refers to the reporting and analytical layer used by analysts and stakeholders.",
"exemplar_skills": [
"BI",
"dashboard design",
"KPI reporting",
"ad hoc analysis",
"report writing",
"self-service analytics",
"business metrics analysis"
],
"in_scope": "BI, dashboards, KPI reporting, ad hoc analysis, operational reports, executive scorecards, self-service analytics, drill-down reporting, slice-and-dice analysis, business metrics",
"name": "Business Intelligence Reporting",
"out_of_scope": "Data preparation and ETL, database administration, machine learning model development, low-level data engineering pipelines, statistical research analysis",
"overlap_flags": [
{
"reason": "BI work often depends on preparing and combining source data before reporting, but that transformation layer is a separate dimension.",
"with_dim_id": "data-preparation-and-blending",
"with_dim_name": null,
"with_role": null
},
{
"reason": "Some BI analysis is done in notebooks, but the core BI skill is business-facing reporting and decision support rather than reproducible research workflows.",
"with_dim_id": "notebook-and-reproducible-analysis-workflow",
"with_dim_name": null,
"with_role": null
}
],
"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.96,
"name": "BI",
"reasoning": "BI is fundamentally a business intelligence domain of knowledge and practice, not a specific tool, language, 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 body of knowledge associated with it. CBAP belongs here because it is a certification for experienced business analysts and signals mastery of requirements, stakeholder, and solution analysis practices.",
"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, especially in enterprise and consulting roles, indicating broad hiring-pipeline recognition."
},
"skill_id": "cbap",
"vendor_license": {
"confidence": 0.97,
"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 body of knowledge associated with it. CBAP belongs here because it is a certification for experienced business analysts and signals mastery of requirements, stakeholder, and solution analysis practices.",
"exemplar_skills": [
"CBAP",
"CCBA",
"ECBA",
"IIBA certification",
"business analysis certification",
"requirements elicitation",
"stakeholder analysis"
],
"in_scope": "CBAP, business analysis certification, IIBA certification, requirements elicitation, stakeholder analysis, process modeling, solution assessment, business case analysis",
"name": "Business Analysis Certification",
"out_of_scope": "project management certification, agile delivery certification, software testing certification, data analysis certification, those belong to separate professional domains",
"overlap_flags": [
{
"reason": "Business analysts may support acceptance criteria and validation, but that is distinct from formal test design and execution.",
"with_dim_id": "test-case-design-and-execution",
"with_dim_name": null,
"with_role": null
},
{
"reason": "Business analysis can touch solution design, but architecture and integration decisions belong to the engineering architecture dimension.",
"with_dim_id": "service-architecture-and-integration",
"with_dim_name": null,
"with_role": null
}
],
"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"
],
"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 not a concept or methodology but a certification.",
"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": "Professional business analysis credentialing and exam-oriented competency for analysts. CCBA belongs here because it is a recognized certification focused on business analysis knowledge, techniques, and standards rather than a specific tool or platform.",
"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 listed without expansion."
},
"context_keywords": {
"context_keywords": [
"IIBA",
"BABOK",
"business analysis",
"requirements elicitation",
"stakeholder analysis",
"process modeling",
"gap analysis",
"use cases",
"user stories",
"traceability matrix",
"solution assessment",
"validation and verification",
"requirements management",
"UAT",
"workshop facilitation"
]
},
"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": 2008
},
"versioning": {
"current_version": null,
"version_aliases": {},
"versioned": false
}
},
"keep_log": [],
"locked_dimensions": [
{
"description": "Professional business analysis credentialing and exam-oriented competency for analysts. CCBA belongs here because it is a recognized certification focused on business analysis knowledge, techniques, and standards rather than a specific tool or platform.",
"exemplar_skills": [
"CCBA",
"CBAP",
"ECBA",
"BABOK",
"business analysis certification",
"requirements elicitation",
"stakeholder analysis"
],
"in_scope": "CCBA, CBAP, ECBA, business analysis certification, BABOK knowledge areas, requirements elicitation, stakeholder analysis, solution assessment, business process analysis",
"name": "Business Analysis Certification",
"out_of_scope": "Software testing certifications, project management credentials, ServiceNow platform training, data analysis tooling, process modeling software usage",
"overlap_flags": [
{
"reason": "Business analysts may support acceptance testing, but CCBA is primarily about analysis competency and certification rather than test execution.",
"with_dim_id": "test-case-design-and-execution",
"with_dim_name": null,
"with_role": null
}
],
"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": [
"scorecards",
"acceptance-criteria-checks",
"acceptance-criteria-validation",
"risk-based-testing",
"charter-based-testing",
"session-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 Reporting",
"id": null,
"rationale": "Covers using Excel for tabular analysis, calculations, reporting, and lightweight business modeling. This fits Excel because the skill is primarily about working with spreadsheets to organize data, summarize findings, and communicate results.",
"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\" in JDs almost always refers to Microsoft Excel spreadsheet software; the name is specific enough that reasonable extractors are unlikely to confuse it with another catalog skill."
},
"context_keywords": {
"context_keywords": [
"pivot tables",
"VLOOKUP",
"XLOOKUP",
"INDEX MATCH",
"macros",
"VBA",
"Power Query",
"Power Pivot",
"data validation",
"conditional formatting",
"charts",
"dashboards",
"SUMIFS",
"COUNTIFS",
"CSV"
]
},
"maturity": {
"confidence": 0.99,
"maturity": "well_known",
"reasoning": "Excel appears in a very large share of business, finance, ops, and analyst job descriptions, and Microsoft continues active support and feature releases via Microsoft 365."
},
"skill_id": "excel",
"vendor_license": {
"confidence": 0.99,
"license": "proprietary",
"vendor": "Microsoft",
"year_introduced": 1985
},
"versioning": {
"current_version": "Microsoft 365 / Excel 2024",
"version_aliases": {
"Excel 2007": "Microsoft 365 / Excel 2024",
"Excel 2010": "Microsoft 365 / Excel 2024",
"Excel 2013": "Microsoft 365 / Excel 2024",
"Excel 2016": "Microsoft 365 / Excel 2024",
"Excel 2019": "Microsoft 365 / Excel 2024",
"Excel 2021": "Microsoft 365 / Excel 2024",
"Excel 2024": "Microsoft 365 / Excel 2024",
"Excel 365": "Microsoft 365 / Excel 2024",
"Microsoft 365 Excel": "Microsoft 365 / Excel 2024"
},
"versioned": true
}
},
"keep_log": [],
"locked_dimensions": [
{
"description": "Covers using Excel for tabular analysis, calculations, reporting, and lightweight business modeling. This fits Excel because the skill is primarily about working with spreadsheets to organize data, summarize findings, and communicate results.",
"exemplar_skills": [
"Excel",
"Pivot Tables",
"VLOOKUP",
"XLOOKUP",
"Conditional Formatting",
"Data Validation",
"Spreadsheet Modeling"
],
"in_scope": "Excel, formulas, functions, pivot tables, charts, filters, sorting, conditional formatting, lookup functions, data validation, worksheet modeling, ad hoc reporting",
"name": "Spreadsheet Analysis and Reporting",
"out_of_scope": "SQL querying and database design, statistical programming in Python or R, enterprise BI dashboarding in Power BI or Tableau, data engineering pipelines and ETL orchestration",
"overlap_flags": [
{
"reason": "Excel often performs light joins, reshaping, and cleanup that can overlap with data preparation work.",
"with_dim_id": "data-preparation-and-blending",
"with_dim_name": null,
"with_role": null
},
{
"reason": "Excel can be used for analysis workflows, but notebooks own scripted, reproducible analytical work.",
"with_dim_id": "notebook-and-reproducible-analysis-workflow",
"with_dim_name": null,
"with_role": null
}
],
"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",
"runbooks"
],
"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, so by the Tool vs Framework rule it is a Tool rather than a library or platform.",
"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 Documentation",
"id": null,
"rationale": "Covers writing and maintaining functional requirement documents that define what a product or process must do. FRDs belong here because they capture business needs, scope, rules, and acceptance intent in a structured specification.",
"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",
"scope definition",
"gap analysis",
"sign-off"
]
},
"maturity": {
"confidence": 0.84,
"maturity": "well_known",
"reasoning": "Functional requirements documents are a standard artifact in many product and systems roles; job descriptions for business analysts, product managers, and systems analysts commonly request requirements documentation and BRD/FRD experience."
},
"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 and maintaining functional requirement documents that define what a product or process must do. FRDs belong here because they capture business needs, scope, rules, and acceptance intent in a structured specification.",
"exemplar_skills": [
"FRDs",
"functional requirements documentation",
"business requirements analysis",
"requirements elicitation",
"scope definition",
"acceptance criteria writing"
],
"in_scope": "FRDs, functional requirements documents, business requirements translation, scope definition, process rules, acceptance criteria, requirement traceability",
"name": "Functional Requirements Documentation",
"out_of_scope": "Technical design specs, API implementation details, database schema design, test execution, project scheduling, which belong to engineering design, testing, or delivery planning dimensions",
"overlap_flags": [
{
"reason": "FRDs often inform test cases, but this dimension covers documenting requirements rather than executing validation.",
"with_dim_id": "test-case-design-and-execution",
"with_dim_name": null,
"with_role": null
},
{
"reason": "Some FRDs may mention service interactions, but architecture design belongs to the backend system design dimension.",
"with_dim_id": "service-architecture-and-integration",
"with_dim_name": null,
"with_role": null
}
],
"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",
"contract-tests",
"feature-flags",
"runbooks",
"rollback-readiness"
],
"requires": [],
"skill_id": "frds",
"suppress_on_match": []
},
"skill_id": "frds",
"split_log": [],
"typed": {
"alternatives_considered": [
"Concept: ruled out \u2014 this is more of a document/artifact category than a named theory or principle",
"Standard: ruled out \u2014 FRDs are not an industry-defined specification",
"Format: ruled out \u2014 it does not define a data structure or wire format"
],
"confidence": 0.72,
"name": "FRDs",
"reasoning": "FRDs most likely refers to functional requirements documents, which are a body of knowledge/artifact category rather than software, so the best fit is Domain under the Concept vs Methodology and general typology rules.",
"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": "Quality Assurance Testing",
"id": null,
"rationale": "Planning and performing manual validation to confirm features meet requirements and acceptance criteria. QA belongs here when it means checking product behavior, finding defects, and verifying fixes rather than automated framework work.",
"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": "Methodology",
"skill_nature": "METHODOLOGY",
"sub_category": "quality_assurance",
"typical_lifespan": "EVERGREEN",
"version_strategy": "NOT_APPLICABLE",
"volatility": "STABLE"
},
"enrichment": {
"ambiguity": {
"ambiguity_flag": true,
"confused_with": [
"quality_assurance"
],
"reasoning": "\"QA\" is a common abbreviation for quality assurance, but in JDs it can also mean quality analyst/assurance roles or be used loosely for testing work; the catalog likely has the fuller quality_assurance skill, so an extractor could conflate them."
},
"context_keywords": {
"context_keywords": [
"test cases",
"test plan",
"test strategy",
"test automation",
"regression testing",
"smoke testing",
"UAT",
"defect tracking",
"bug triage",
"test scripts",
"Selenium",
"JUnit",
"pytest",
"JIRA",
"traceability matrix"
]
},
"maturity": {
"confidence": 0.95,
"maturity": "well_known",
"reasoning": "QA appears in a large share of software job descriptions and is a standard hiring-pipeline requirement across manual and automated testing roles; it is not tied to a sunset or replacement technology."
},
"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": "Planning and performing manual validation to confirm features meet requirements and acceptance criteria. QA belongs here when it means checking product behavior, finding defects, and verifying fixes rather than automated framework work.",
"exemplar_skills": [
"QA",
"manual testing",
"test case design",
"test execution",
"regression testing",
"exploratory testing"
],
"in_scope": "QA, manual testing, test case creation, test execution, regression testing, smoke testing, exploratory testing, acceptance testing, defect verification",
"name": "Quality Assurance Testing",
"out_of_scope": "Automated framework development, API automation, performance testing, data quality assessment, release governance",
"overlap_flags": [
{
"reason": "QA work can include automation, but this dimension owns the frameworks and code used to automate tests.",
"with_dim_id": "testing-and-automation-frameworks",
"with_dim_name": null,
"with_role": null
},
{
"reason": "If QA is focused on automated API validation, that belongs in service test automation rather than manual QA.",
"with_dim_id": "api-and-service-test-automation",
"with_dim_name": null,
"with_role": null
}
],
"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",
"risk-based-testing",
"cross-browser-testing",
"defect-retest",
"health-checks",
"session-based-testing",
"charter-based-testing"
],
"requires": [],
"skill_id": "qa",
"suppress_on_match": []
},
"skill_id": "qa",
"split_log": [],
"typed": {
"alternatives_considered": [
"Concept: ruled out \u2014 it is an operational practice area, not a single named theory or principle.",
"SoftSkill: ruled out \u2014 despite involving communication, QA is fundamentally a technical process discipline."
],
"confidence": 0.78,
"name": "QA",
"reasoning": "QA is best treated as a quality assurance practice/way of working rather than a software artifact, and under the Concept vs Methodology rule it fits a methodology more than a knowledge unit.",
"skill_id": "qa",
"subtype": "quality_assurance",
"type": "Methodology"
},
"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 overall lifecycle framework rather than a single technical practice.",
"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 across industries; it appears broadly in hiring pipelines rather than as 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 overall lifecycle framework rather than a single technical practice.",
"exemplar_skills": [
"SDLC",
"software development lifecycle",
"requirements gathering",
"release management",
"change control",
"defect triage"
],
"in_scope": "SDLC, requirements analysis, design, implementation, testing, release management, maintenance, change control, defect triage, iterative delivery, waterfall, agile delivery",
"name": "Software Delivery Lifecycle",
"out_of_scope": "Specific test design and execution, deployment tooling, environment provisioning, or service architecture, which are owned by narrower engineering dimensions",
"overlap_flags": [
{
"reason": "Testing is one phase of SDLC, but this dimension focuses on the full lifecycle rather than manual test design and execution.",
"with_dim_id": "test-case-design-and-execution",
"with_dim_name": null,
"with_role": null
},
{
"reason": "Environment setup and promotion support delivery, but they are operational subtopics within the broader lifecycle.",
"with_dim_id": "environment-provisioning-and-promotion",
"with_dim_name": null,
"with_role": null
}
],
"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.88,
"name": "SDLC",
"reasoning": "SDLC is best treated as a methodology because it describes the process and phases for how software is developed and delivered, matching the Concept vs Methodology rule.",
"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 Model",
"id": null,
"rationale": "Covers software delivered as a subscription-based hosted service, including multi-tenant product concepts, packaging, pricing, and customer lifecycle considerations. SaaS belongs here because it describes the delivery and business model of the software rather than a specific technical implementation area.",
"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",
"usage-based pricing",
"SAML",
"SSO",
"RBAC",
"API integrations",
"webhooks",
"customer provisioning",
"admin console",
"SLAs",
"churn",
"renewal"
]
},
"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 broadly, indicating mainstream adoption."
},
"skill_id": "saas",
"vendor_license": {
"confidence": 0.78,
"license": "proprietary",
"vendor": "Salesforce",
"year_introduced": 1999
},
"versioning": {
"current_version": null,
"version_aliases": {},
"versioned": false
}
},
"keep_log": [],
"locked_dimensions": [
{
"description": "Covers software delivered as a subscription-based hosted service, including multi-tenant product concepts, packaging, pricing, and customer lifecycle considerations. SaaS belongs here because it describes the delivery and business model of the software rather than a specific technical implementation area.",
"exemplar_skills": [
"SaaS",
"software as a service",
"multi-tenant architecture",
"subscription product management",
"hosted software delivery",
"tenant isolation"
],
"in_scope": "SaaS, software as a service, subscription software, multi-tenant application model, hosted application delivery, tenant isolation concepts, usage-based packaging, trial-to-paid conversion, renewals and churn, customer onboarding for SaaS products",
"name": "SaaS Product Model",
"out_of_scope": "cloud infrastructure provisioning, container orchestration, API design, frontend styling, security hardening, data pipeline operations",
"overlap_flags": [
{
"reason": "SaaS products are often implemented as services, but this dimension is about the commercial delivery model rather than backend service decomposition.",
"with_dim_id": "service-architecture-and-integration",
"with_dim_name": null,
"with_role": null
},
{
"reason": "SaaS platforms require security controls, but those controls belong to the security dimension rather than the SaaS business model.",
"with_dim_id": "cloud-security-guardrails",
"with_dim_name": null,
"with_role": null
}
],
"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",
"azure-backup",
"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 environment rather than a specific managed capability inside a platform."
],
"confidence": 0.91,
"name": "SaaS",
"reasoning": "By the Platform vs Tool rule, SaaS is a hosted, multi-tenant environment delivered over APIs and managed by the provider, so it is fundamentally a Platform.",
"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",
"id": null,
"rationale": "Validating that a feature meets business requirements and is ready for user sign-off. UAT belongs here because it focuses on end-user scenarios, acceptance criteria, and stakeholder approval rather than technical test automation.",
"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",
"test scripts",
"acceptance criteria",
"business users",
"end users",
"sign-off",
"test scenarios",
"defect triage",
"test plan",
"regression testing",
"stakeholder review",
"go-live",
"test environment",
"smoke testing"
]
},
"maturity": {
"confidence": 0.86,
"maturity": "well_known",
"reasoning": "UAT is a standard QA phase in many software JDs and delivery pipelines; it appears routinely in job postings for QA, BA, and product roles as a required acceptance-testing practice."
},
"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": "Validating that a feature meets business requirements and is ready for user sign-off. UAT belongs here because it focuses on end-user scenarios, acceptance criteria, and stakeholder approval rather than technical test automation.",
"exemplar_skills": [
"UAT",
"user acceptance testing",
"acceptance criteria validation",
"stakeholder sign-off",
"manual test execution",
"business scenario testing"
],
"in_scope": "UAT, user acceptance testing, acceptance criteria validation, business scenario walkthroughs, end-user sign-off, manual acceptance test execution, defect logging from business review, release readiness checks",
"name": "User Acceptance Testing",
"out_of_scope": "Unit testing, API automation, performance testing, production monitoring, technical regression suites, these belong to engineering test or operations dimensions",
"overlap_flags": [
{
"reason": "UAT uses manual test cases, but the emphasis is business acceptance and sign-off rather than general test design and execution.",
"with_dim_id": "test-case-design-and-execution",
"with_dim_name": null,
"with_role": null
},
{
"reason": "UAT may be tracked in test management tools, but it is not primarily about automation frameworks or technical test infrastructure.",
"with_dim_id": "testing-and-automation-frameworks",
"with_dim_name": null,
"with_role": null
}
],
"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.93,
"name": "UAT",
"reasoning": "UAT is 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": "Diagramming and Process Modeling",
"id": null,
"rationale": "Creating business and technical diagrams to communicate workflows, systems, and relationships. Visio belongs here because it is commonly used to draw process maps, flowcharts, swimlanes, and architecture sketches for analysis and documentation.",
"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 well-known Microsoft diagramming tool with a specific JD context; it is unlikely to be reasonably confused with another catalog skill."
},
"context_keywords": {
"context_keywords": [
"flowchart",
"swimlane",
"process map",
"BPMN",
"UML",
"network diagram",
"org chart",
"data flow diagram",
"wireframe",
"site map",
"cross-functional diagram",
"business process",
"workflow",
"ERD",
"stencil"
]
},
"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": "Creating business and technical diagrams to communicate workflows, systems, and relationships. Visio belongs here because it is commonly used to draw process maps, flowcharts, swimlanes, and architecture sketches for analysis and documentation.",
"exemplar_skills": [
"Visio",
"process mapping",
"flowchart creation",
"swimlane diagramming",
"BPMN modeling",
"org chart design"
],
"in_scope": "Visio, flowcharts, process maps, swimlane diagrams, BPMN diagrams, org charts, system context diagrams, UML sketches, business process modeling",
"name": "Diagramming and Process Modeling",
"out_of_scope": "Spreadsheet analysis, database querying, requirements elicitation, UI mockups, those belong to other analysis or design dimensions",
"overlap_flags": [
{
"reason": "System and integration diagrams can overlap with architecture work, but this dimension focuses on communication diagrams rather than backend design decisions.",
"with_dim_id": "service-architecture-and-integration",
"with_dim_name": null,
"with_role": null
}
],
"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",
"mvvm",
"portal-pages",
"portal-navigation",
"threat-modeling"
],
"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
}
],
"unmatched_skills": [
"APIs",
"Acceptance",
"BI",
"CBAP",
"CCBA",
"Excel",
"FRDs",
"QA",
"SDLC",
"SaaS",
"UAT",
"Visio"
]
}
API 3 — final-role-output
{
"chosen_role": {
"display_name": "Business Analyst",
"id": null,
"rationale": "The strongest evidence centers on requirements, UAT, FRDs, QA, and process/documentation work, aligning best with Business Analyst.",
"role_archetype": "Business analysis professional who gathers requirements, documents processes, and translates stakeholder needs into functional specifications.",
"slug": "business-analyst",
"source": "llm"
},
"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": "QA",
"tag": "new"
},
{
"skill": "SDLC",
"tag": "new"
},
{
"skill": "SaaS",
"tag": "new"
},
{
"skill": "UAT",
"tag": "new"
},
{
"skill": "Visio",
"tag": "new"
}
],
"persistence": {
"items": [
{
"chosen_role_id": null,
"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": null,
"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": false,
"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": null,
"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": false,
"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": null,
"dimension": {
"difficulty_hint": null,
"display_name": "API Design and Integration",
"id": null,
"rationale": "Designing how systems expose and consume APIs, including contracts, endpoints, and integration patterns. APIs belong here because they are the primary interface for connecting business capabilities across applications and external partners.",
"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": null,
"dimension": {
"difficulty_hint": null,
"display_name": "User Acceptance Validation",
"id": null,
"rationale": "Covers confirming that a feature, process, or deliverable meets business expectations and is ready for sign-off. This fits the skill \u0027Acceptance\u0027 when used in a business analysis or requirements context, especially around stakeholder approval and user acceptance testing.",
"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": null,
"dimension": {
"difficulty_hint": null,
"display_name": "Business Intelligence Reporting",
"id": null,
"rationale": "Covers the creation and use of reports, dashboards, KPIs, and ad hoc analysis that help business users monitor performance and make decisions. BI fits here because it commonly refers to the reporting and analytical layer used by analysts and stakeholders.",
"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": null,
"dimension": {
"difficulty_hint": null,
"display_name": "Business Analysis Certification",
"id": null,
"rationale": "Formal business analysis credentialing and the body of knowledge associated with it. CBAP belongs here because it is a certification for experienced business analysts and signals mastery of requirements, stakeholder, and solution analysis practices.",
"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": null,
"dimension": {
"difficulty_hint": null,
"display_name": "Business Analysis Certification",
"id": null,
"rationale": "Professional business analysis credentialing and exam-oriented competency for analysts. CCBA belongs here because it is a recognized certification focused on business analysis knowledge, techniques, and standards rather than a specific tool or platform.",
"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": null,
"dimension": {
"difficulty_hint": null,
"display_name": "Spreadsheet Analysis and Reporting",
"id": null,
"rationale": "Covers using Excel for tabular analysis, calculations, reporting, and lightweight business modeling. This fits Excel because the skill is primarily about working with spreadsheets to organize data, summarize findings, and communicate results.",
"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": null,
"dimension": {
"difficulty_hint": null,
"display_name": "Functional Requirements Documentation",
"id": null,
"rationale": "Covers writing and maintaining functional requirement documents that define what a product or process must do. FRDs belong here because they capture business needs, scope, rules, and acceptance intent in a structured specification.",
"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": null,
"dimension": {
"difficulty_hint": null,
"display_name": "Quality Assurance Testing",
"id": null,
"rationale": "Planning and performing manual validation to confirm features meet requirements and acceptance criteria. QA belongs here when it means checking product behavior, finding defects, and verifying fixes rather than automated framework work.",
"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": null,
"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 overall lifecycle framework rather than a single technical practice.",
"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": null,
"dimension": {
"difficulty_hint": null,
"display_name": "SaaS Product Model",
"id": null,
"rationale": "Covers software delivered as a subscription-based hosted service, including multi-tenant product concepts, packaging, pricing, and customer lifecycle considerations. SaaS belongs here because it describes the delivery and business model of the software rather than a specific technical implementation area.",
"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": null,
"dimension": {
"difficulty_hint": null,
"display_name": "User Acceptance Testing",
"id": null,
"rationale": "Validating that a feature meets business requirements and is ready for user sign-off. UAT belongs here because it focuses on end-user scenarios, acceptance criteria, and stakeholder approval rather than technical test automation.",
"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": null,
"dimension": {
"difficulty_hint": null,
"display_name": "Diagramming and Process Modeling",
"id": null,
"rationale": "Creating business and technical diagrams to communicate workflows, systems, and relationships. Visio belongs here because it is commonly used to draw process maps, flowcharts, swimlanes, and architecture sketches for analysis and documentation.",
"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": 15
},
"planner_output": null,
"run_id": "c109cdd1-f6fd-459e-96f2-c7e0a80b22f1"
}
LLM Calls
Every model call made for this run, in pipeline order. Click a card to see the model's response.
Loading…