Pipeline run
590a2f20-9b65-4324-8e3e-79ba678de779
Client output enrichment
v2 Skill cluster · Nature of work · AI index · Tech stack maturity · Evidence · KRA descriptionNature of work
no kras
Vague JD — no KRAs present to derive a specific nature of work.
Tech stack maturity
Mainstream Modern
AI index (0 = no AI use, 5 = totally AI-dependent · v2.1)
0.00 / 5
· Title match
· Has AI skill
· AI skill (primary)
· AI skill (secondary)
· On AI team
· Builds AI products
vocab breakdown (legacy)
Assistants (×1):
—
Frameworks (×2):
—
Models / concepts (×3):
—
Evidence — skills matched in JD (0)
Skill cluster (0 dimension groups, role-scoped)
Status:
completed
Created: 2026-05-08T10:01:59.491324Z
Updated: 2026-05-08T10:03:52.947957Z
API 3 duration: 891 ms
Flow
Current 3-step pipeline
1 POST /skills/extract-from-jd
2 POST /skills/extract-details
3 POST /skills/final-role-output
Role
Chosen role & resolution
Data Analyst
slug: data-analyst · id: 20 · source: db
The strongest mapped dimension is reporting and dashboard development, which links directly to Data Analyst and has the clearest evidence weight.
0
New skills
0
Skill↔dim saved
0
Role↔dim saved
12
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 |
|---|---|---|---|---|---|---|
| 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) |
| Argo Workflows | in_db |
Workflow Orchestration Systems
workflow-orchestration-systems
|
— | — | — | 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 |
| BI | new |
Business Intelligence
d_init_01
|
— | — | — | skill_not_in_db_v3_proposed |
| CBAP | new |
Business Analysis Certification
d_init_01
|
— | — | — | skill_not_in_db_v3_proposed |
| CCBA | new |
Business Analysis Certification
d_init_01
|
— | — | — | skill_not_in_db_v3_proposed |
| Excel | new |
Spreadsheet Analysis and Modeling
d_init_01
|
— | — | — | skill_not_in_db_v3_proposed |
| FRDs | new |
Functional Requirements Documentation
d_init_01
|
— | — | — | skill_not_in_db_v3_proposed |
| SDLC | new |
Software Development Lifecycle
d_init_01
|
— | — | — | skill_not_in_db_v3_proposed |
| SaaS | new |
Software as a Service
d_init_01
|
— | — | — | skill_not_in_db_v3_proposed |
| Visio | new |
Diagramming and Process Modeling
d_init_01
|
— | — | — | skill_not_in_db_v3_proposed |
Library artifacts (this run)
| Kind | Detail | DB id |
|---|---|---|
| canonical_skill_proposed | APIs | type=Protocol subtype=application_programming_interfaces nature=PROTOCOL lifespan=EVERGREEN | |
| canonical_skill_proposed | Acceptance | type=Concept subtype=acceptance_concept nature=CONCEPT lifespan=EVERGREEN | |
| canonical_skill_proposed | BI | type=Domain subtype=business_intelligence nature=CONCEPT lifespan=EVERGREEN | |
| canonical_skill_proposed | CBAP | type=Certification subtype=business_analysis_professional_certification nature=CREDENTIAL lifespan=EVERGREEN | |
| canonical_skill_proposed | CCBA | type=Certification subtype=business_analysis_certification nature=CREDENTIAL lifespan=EVERGREEN | |
| canonical_skill_proposed | Excel | type=Tool subtype=spreadsheet_software nature=TOOL lifespan=EVERGREEN | |
| canonical_skill_proposed | FRDs | type=Domain subtype=functional_requirements_documents nature=CONCEPT lifespan=EVERGREEN | |
| canonical_skill_proposed | QA | type=SoftSkill subtype=quality_assurance nature=PRACTICE 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 | Testing | type=Methodology subtype=software_testing_methodology nature=METHODOLOGY 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 | Business Intelligence | |
| dimension_skill_link_proposed | BI ↔ Business Intelligence | |
| dimension_proposed | Business Analysis Certification | |
| dimension_skill_link_proposed | CBAP ↔ Business Analysis Certification | |
| dimension_proposed | Business Analysis Certification | |
| dimension_skill_link_proposed | CCBA ↔ Business Analysis Certification | |
| dimension_proposed | Spreadsheet Analysis and Modeling | |
| dimension_skill_link_proposed | Excel ↔ Spreadsheet Analysis and Modeling | |
| dimension_proposed | Functional Requirements Documentation | |
| dimension_skill_link_proposed | FRDs ↔ Functional Requirements Documentation | |
| dimension_proposed | Software Development Lifecycle | |
| dimension_skill_link_proposed | SDLC ↔ Software Development Lifecycle | |
| dimension_proposed | Software as a Service | |
| dimension_skill_link_proposed | SaaS ↔ Software as a Service | |
| 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",
"Career",
"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",
"Title",
"Understanding",
"User",
"Years",
"abilities",
"candidate",
"commerce",
"company",
"degree",
"delivery",
"dependencies",
"developers",
"development",
"diagrams",
"document",
"domains",
"environment",
"field",
"gap",
"gathering",
"goals",
"growth",
"insurance",
"leaves",
"management",
"managers",
"meetings",
"needs",
"opportunities",
"process",
"processes",
"product",
"progress",
"project",
"requirement",
"risks",
"salary",
"site",
"solutions",
"stakeholders",
"teams",
"work"
],
"final_skills": [
"Power BI",
"Tableau",
"Argo Workflows",
"APIs",
"Acceptance",
"BI",
"CBAP",
"CCBA",
"Excel",
"FRDs",
"QA",
"SDLC",
"SaaS",
"Testing",
"UAT",
"Visio",
"analysis",
"communication",
"data",
"databases",
"documentation",
"fintech",
"healthcare",
"insights",
"methodologies",
"optimization",
"problem",
"reporting",
"requirements",
"software",
"specifications",
"stakeholder",
"stories",
"strategies",
"tools",
"trends",
"workshops"
],
"initial_skills": [
"Power BI",
"Tableau",
"Argo Workflows"
],
"jd_role_hint": {
"display_name": "Business Analyst",
"rationale": "The excerpt centers on requirement gathering, stakeholder communication, process analysis, and documentation, which are core Business Analyst responsibilities.",
"role_archetype": "Business analysis professional focused on gathering requirements, documenting processes, and translating business needs into functional specs.",
"slug": "business-analyst"
},
"llm_non_skills": [
"2\u20135",
"Ability",
"Analyst",
"BRDs",
"Bachelor",
"Benefits",
"Business",
"Career",
"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",
"Title",
"Understanding",
"User",
"Years",
"abilities",
"candidate",
"commerce",
"company",
"degree",
"delivery",
"dependencies",
"developers",
"development",
"diagrams",
"document",
"domains",
"environment",
"field",
"gap",
"gathering",
"goals",
"growth",
"insurance",
"leaves",
"management",
"managers",
"meetings",
"needs",
"opportunities",
"process",
"processes",
"product",
"progress",
"project",
"requirement",
"risks",
"salary",
"site",
"solutions",
"stakeholders",
"teams",
"work"
],
"llm_skills": [
"APIs",
"Acceptance",
"BI",
"CBAP",
"CCBA",
"Excel",
"FRDs",
"QA",
"SDLC",
"SaaS",
"Testing",
"UAT",
"Visio",
"analysis",
"communication",
"data",
"databases",
"documentation",
"fintech",
"healthcare",
"insights",
"methodologies",
"optimization",
"problem",
"reporting",
"requirements",
"software",
"specifications",
"stakeholder",
"stories",
"strategies",
"tools",
"trends",
"workshops"
],
"run_id": null,
"unknown_words": [
"2\u20135",
"APIs",
"Ability",
"Acceptance",
"Analyst",
"BI",
"BRDs",
"Bachelor",
"Benefits",
"Business",
"CBAP",
"CCBA",
"Career",
"Certification",
"Computer",
"Conduct",
"Description",
"Ensure",
"Excel",
"Experience",
"Exposure",
"FRDs",
"Familiarity",
"Gather",
"Health",
"Hybrid",
"Job",
"Key",
"Knowledge",
"Learning",
"Location",
"Monitor",
"Power",
"Preferred",
"QA",
"Qualifications",
"Remote",
"Required",
"Responsibilities",
"Role",
"SDLC",
"SaaS",
"Science",
"Skills",
"Support",
"Testing",
"Title",
"UAT",
"Understanding",
"User",
"Visio",
"Years",
"abilities",
"analysis",
"benefits",
"business",
"candidate",
"certification",
"commerce",
"communication",
"company",
"data",
"databases",
"degree",
"delivery",
"dependencies",
"developers",
"development",
"diagrams",
"document",
"documentation",
"domains",
"environment",
"field",
"fintech",
"gap",
"gathering",
"goals",
"growth",
"healthcare",
"insights",
"insurance",
"leaves",
"management",
"managers",
"meetings",
"methodologies",
"needs",
"opportunities",
"optimization",
"problem",
"process",
"processes",
"product",
"progress",
"project",
"reporting",
"requirement",
"requirements",
"risks",
"salary",
"site",
"skills",
"software",
"solutions",
"specifications",
"stakeholder",
"stakeholders",
"stories",
"strategies",
"teams",
"tools",
"trends",
"understanding",
"user",
"work",
"workshops"
]
}
API 2 — extract-details
{
"alias_matches": [],
"candidate_roles": [
{
"display_name": "Data Analyst",
"id": 20,
"rationale": null,
"role_archetype": null,
"slug": "data-analyst",
"source": "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"
}
],
"chosen_role": {
"display_name": "Data Analyst",
"id": 20,
"rationale": "The strongest mapped dimension is reporting and dashboard development, which links directly to Data Analyst and has the clearest evidence weight.",
"role_archetype": null,
"slug": "data-analyst",
"source": "db"
},
"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"
}
]
},
{
"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": "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": null,
"display_name": "API Design and Integration",
"id": null,
"rationale": "Designing and using application programming interfaces for system-to-system communication. This covers how business systems expose, consume, version, and document interfaces, which is the core meaning of APIs for an analyst working with process and integration requirements.",
"slug": "d_init_01",
"source": "llm"
},
"input_skill": "APIs",
"llm_role": null,
"roles_from_db": []
},
{
"dimension": {
"difficulty_hint": null,
"display_name": "Business Intelligence",
"id": null,
"rationale": "Covers the use of data to create reports, dashboards, and decision-support views for business users. BI fits here because it commonly refers to the discipline of turning operational data into accessible insights for analysis and management.",
"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 body-of-knowledge preparation. CBAP belongs here because it is a certification focused on advanced business analysis practices, techniques, and professional standards rather than a single tool or technical domain.",
"slug": "d_init_01",
"source": "llm"
},
"input_skill": "CBAP",
"llm_role": null,
"roles_from_db": []
},
{
"dimension": {
"difficulty_hint": null,
"display_name": "Business Analysis Certification",
"id": null,
"rationale": "Formal business analysis credentialing and exam-based professional standards. CCBA belongs here because it is a recognized certification for practicing business analysts, focused on validated competency rather than a specific technical tool or method.",
"slug": "d_init_01",
"source": "llm"
},
"input_skill": "CCBA",
"llm_role": null,
"roles_from_db": []
},
{
"dimension": {
"difficulty_hint": null,
"display_name": "Spreadsheet Analysis and Modeling",
"id": null,
"rationale": "Using spreadsheets to organize, analyze, and present business data. Excel belongs here because it is the standard tool for tabular analysis, formulas, pivoting, and lightweight reporting in business analysis work.",
"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 requirements documents that specify what a product or process must do. FRDs belong here because they capture business needs, scope, workflows, and acceptance expectations in a formal requirements artifact.",
"slug": "d_init_01",
"source": "llm"
},
"input_skill": "FRDs",
"llm_role": null,
"roles_from_db": []
},
{
"dimension": {
"difficulty_hint": null,
"display_name": "Software Development Lifecycle",
"id": null,
"rationale": "Covers the end-to-end process used to plan, build, test, release, and maintain software products. SDLC belongs here because it refers to the overall delivery lifecycle 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": "Software as a Service",
"id": null,
"rationale": "Covers cloud-delivered subscription software products and the business/operational concepts around them. SaaS fits here because it refers to a software delivery and commercial model rather than a specific technical implementation skill.",
"slug": "d_init_01",
"source": "llm"
},
"input_skill": "SaaS",
"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, swimlanes, org charts, and system diagrams for analysis and documentation.",
"slug": "d_init_01",
"source": "llm"
},
"input_skill": "Visio",
"llm_role": null,
"roles_from_db": []
}
],
"input_final_skills": [
"Power BI",
"Tableau",
"Argo Workflows",
"APIs",
"Acceptance",
"BI",
"CBAP",
"CCBA",
"Excel",
"FRDs",
"QA",
"SDLC",
"SaaS",
"Testing",
"UAT",
"Visio",
"analysis",
"communication",
"data",
"databases",
"documentation",
"fintech",
"healthcare",
"insights",
"methodologies",
"optimization",
"problem",
"reporting",
"requirements",
"software",
"specifications",
"stakeholder",
"stories",
"strategies",
"tools",
"trends",
"workshops"
],
"input_llm_skills": [
"APIs",
"Acceptance",
"BI",
"CBAP",
"CCBA",
"Excel",
"FRDs",
"QA",
"SDLC",
"SaaS",
"Testing",
"UAT",
"Visio",
"analysis",
"communication",
"data",
"databases",
"documentation",
"fintech",
"healthcare",
"insights",
"methodologies",
"optimization",
"problem",
"reporting",
"requirements",
"software",
"specifications",
"stakeholder",
"stories",
"strategies",
"tools",
"trends",
"workshops"
],
"new_aliases_persisted": 0,
"run_id": "590a2f20-9b65-4324-8e3e-79ba678de779",
"skills_detail": [
{
"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": [
{
"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": [],
"canonical": null,
"dimensions": [
{
"dimension": {
"difficulty_hint": null,
"display_name": "API Design and Integration",
"id": null,
"rationale": "Designing and using application programming interfaces for system-to-system communication. This covers how business systems expose, consume, version, and document interfaces, which is the core meaning of APIs for an analyst working with process and integration requirements.",
"slug": "d_init_01",
"source": "llm"
},
"input_skill": "APIs",
"llm_role": null,
"roles_from_db": []
}
],
"input_skill": "APIs",
"matched_via": null,
"new_alias_persisted": false,
"new_alias_text": null,
"new_skill_meta": {
"derived": {
"category": "Protocol",
"skill_nature": "PROTOCOL",
"sub_category": "application_programming_interfaces",
"typical_lifespan": "EVERGREEN",
"version_strategy": "NOT_APPLICABLE",
"volatility": "STABLE"
},
"enrichment": {
"ambiguity": {
"ambiguity_flag": false,
"confused_with": [],
"reasoning": "APIs is a standard, well-scoped term in JDs and usually refers to application programming interfaces; it is not typically confused with a different catalog skill."
},
"context_keywords": {
"context_keywords": [
"REST",
"GraphQL",
"OpenAPI",
"Swagger",
"JSON",
"XML",
"OAuth 2.0",
"JWT",
"webhooks",
"endpoint",
"rate limiting",
"API gateway",
"microservices",
"SDK",
"versioning"
]
},
"maturity": {
"confidence": 0.98,
"maturity": "well_known",
"reasoning": "APIs are a hiring-pipeline staple across backend, mobile, and platform JDs; REST/GraphQL/API design appears in large volumes of job postings and is foundational in cloud vendor docs and SDK ecosystems."
},
"skill_id": "apis",
"vendor_license": {
"confidence": 0.99,
"license": null,
"vendor": null,
"year_introduced": null
},
"versioning": {
"current_version": null,
"version_aliases": {},
"versioned": false
}
},
"locked_dimensions": [
{
"description": "Designing and using application programming interfaces for system-to-system communication. This covers how business systems expose, consume, version, and document interfaces, which is the core meaning of APIs for an analyst working with process and integration requirements.",
"exemplar_skills": [
"APIs",
"REST API design",
"GraphQL APIs",
"Webhook integration",
"API versioning",
"API documentation"
],
"in_scope": "APIs, REST APIs, SOAP APIs, GraphQL endpoints, webhook contracts, request and response schemas, versioning, pagination, error handling, API documentation",
"name": "API Design and Integration",
"out_of_scope": "UI navigation, database administration, authentication session state, cloud infrastructure provisioning, these belong to frontend, data, security, or infrastructure dimensions",
"overlap_flags": [
{
"reason": "API design is often part of broader service integration work, but this dimension is specifically centered on interface contracts.",
"with_dim_id": "service-architecture-and-integration",
"with_dim_name": null,
"with_role": null
},
{
"reason": "Both involve calling external interfaces, but tool use is about model actions rather than enterprise API design.",
"with_dim_id": "tool-use-and-function-calling",
"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": [],
"parent_skills": [],
"related_to": [
"rest-apis",
"grpc",
"http",
"json",
"oauth-2-0",
"private-endpoints",
"acls",
"mock-servers"
],
"requires": [],
"skill_id": "apis",
"suppress_on_match": []
},
"skill_id": "apis",
"split_log": [],
"typed": {
"alternatives_considered": [],
"confidence": 0.91,
"name": "APIs",
"reasoning": "APIs are a communication interface standard between software systems, so by the Protocol rule they fit best as a protocol-like interface rather than a tool or platform.",
"skill_id": "apis",
"subtype": "application_programming_interfaces",
"type": "Protocol"
},
"warnings": []
},
"source_tag": "llm",
"was_in_llm_skills": true
},
{
"aliases_in_db": [],
"canonical": null,
"dimensions": [],
"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",
"user_acceptance_testing",
"acceptance_criteria"
],
"reasoning": "\u201cAcceptance\u201d is a generic term in JDs and could refer to acceptance testing, user acceptance testing, or acceptance criteria rather than the standalone concept."
},
"context_keywords": {
"context_keywords": [
"UAT",
"user acceptance testing",
"acceptance criteria",
"acceptance test",
"sign-off",
"go-live",
"definition of done",
"test cases",
"requirements validation",
"stakeholder approval",
"quality assurance",
"release readiness",
"verification",
"validation",
"test plan"
]
},
"maturity": {
"confidence": 0.86,
"maturity": "well_known",
"reasoning": "Acceptance is a standard software/testing concept; it appears broadly in job descriptions for QA, product, and agile roles, especially in phrases like acceptance criteria and user acceptance testing (UAT)."
},
"skill_id": "acceptance",
"vendor_license": {
"confidence": 0.99,
"license": null,
"vendor": null,
"year_introduced": null
},
"versioning": {
"current_version": null,
"version_aliases": {},
"versioned": false
}
},
"locked_dimensions": [],
"merge_log": [
{
"a_dim_id": "d_init_01",
"a_name": "Requirements Acceptance Validation",
"a_role": "__skill_focal__",
"b_dim_id": "requirements-and-acceptance-validation",
"b_name": "Requirements and Acceptance Validation",
"b_role": "existing_catalog",
"into": "d_merge_01",
"into_name": "Requirements and Acceptance Validation",
"merged_from": [
"d_init_01",
"requirements-and-acceptance-validation"
],
"pair_kind": "cross_role",
"reasoning": "Both dims describe the same acceptance-validation cluster: checking delivered/implemented behavior against requirements, user stories, and acceptance criteria. Dim A\u2019s exemplars (\"Acceptance\", \"user story acceptance\", \"UAT coordination\") and in-scope items (sign-off readiness, defect verification against requirements) match Dim B\u2019s description of implemented behavior matching documented requirements. The wording differs, but the substance is identical; cross-role similarity is a false positive.",
"similarity": 0.8130120222496946
}
],
"placed": {
"name": "Acceptance",
"placement_confidence": 0.0,
"primary_dimension": "d_init_00",
"reasoning": "Stub placement: no locked_dimensions after Stage 2/3; downstream containment and enrichment use placeholders only.",
"secondary_dimensions": [],
"skill_id": "acceptance"
},
"relationships": {
"child_skills": [],
"parent_skills": [],
"related_to": [
"acceptance-criteria-validation",
"acceptance-criteria-checks",
"contract-tests",
"defect-retest",
"change-requests"
],
"requires": [],
"skill_id": "acceptance",
"suppress_on_match": []
},
"skill_id": "acceptance",
"split_log": [],
"typed": {
"alternatives_considered": [
"Methodology: ruled out \u2014 it would imply a process or workflow, but Acceptance here is a concept rather than an operating method.",
"SoftSkill: ruled out \u2014 although acceptance can appear in interpersonal contexts, the skill name most fundamentally refers to a knowledge concept."
],
"confidence": 0.78,
"name": "Acceptance",
"reasoning": "By the Concept vs Methodology rule, Acceptance is best treated as a named knowledge unit about approval or meeting criteria, rather than a way of working.",
"skill_id": "acceptance",
"subtype": "acceptance_concept",
"type": "Concept"
},
"warnings": [
"placement_stub_no_locked_dimensions"
]
},
"source_tag": "llm",
"was_in_llm_skills": true
},
{
"aliases_in_db": [],
"canonical": null,
"dimensions": [
{
"dimension": {
"difficulty_hint": null,
"display_name": "Business Intelligence",
"id": null,
"rationale": "Covers the use of data to create reports, dashboards, and decision-support views for business users. BI fits here because it commonly refers to the discipline of turning operational data into accessible insights for analysis and management.",
"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 read as a generic business term or other BI-related tooling/context. A reasonable extractor could confuse the shorthand with the full business_intelligence skill."
},
"context_keywords": {
"context_keywords": [
"dashboard",
"KPI",
"data warehouse",
"ETL",
"OLAP",
"reporting",
"Tableau",
"Power BI",
"Looker",
"SQL",
"dimensional modeling",
"star schema",
"data mart",
"ad hoc analysis",
"drill-down"
]
},
"maturity": {
"confidence": 0.92,
"maturity": "well_known",
"reasoning": "BI is a common hiring keyword across analytics and data roles; job postings routinely ask for Power BI/Tableau/Looker or BI reporting experience, showing broad market demand."
},
"skill_id": "bi",
"vendor_license": {
"confidence": 0.99,
"license": null,
"vendor": null,
"year_introduced": null
},
"versioning": {
"current_version": null,
"version_aliases": {},
"versioned": false
}
},
"locked_dimensions": [
{
"description": "Covers the use of data to create reports, dashboards, and decision-support views for business users. BI fits here because it commonly refers to the discipline of turning operational data into accessible insights for analysis and management.",
"exemplar_skills": [
"BI",
"business intelligence",
"dashboard design",
"reporting",
"KPI reporting",
"data visualization",
"self-service analytics"
],
"in_scope": "BI, business intelligence, reporting, dashboards, KPI tracking, ad hoc analysis, OLAP, semantic layers, self-service analytics, executive scorecards, data visualization, drill-down reporting",
"name": "Business Intelligence",
"out_of_scope": "Data engineering pipelines and ETL orchestration, statistical modeling and causal inference, data quality auditing, which belong to other analytics or engineering dimensions",
"overlap_flags": [
{
"reason": "BI often includes building dashboards and reports, but this catalog dimension is narrower and platform-specific.",
"with_dim_id": "reporting-and-dashboard-configuration",
"with_dim_name": null,
"with_role": null
},
{
"reason": "BI work may use basic statistics, but the core skill is business-facing reporting and insight delivery rather than statistical analysis.",
"with_dim_id": "statistical-reasoning-for-analysis",
"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"
],
"requires": [],
"skill_id": "bi",
"suppress_on_match": []
},
"skill_id": "bi",
"split_log": [],
"typed": {
"alternatives_considered": [],
"confidence": 0.93,
"name": "BI",
"reasoning": "BI is best classified as a Domain because it denotes the business intelligence problem-space and body of knowledge rather than 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 body-of-knowledge preparation. CBAP belongs here because it is a certification focused on advanced business analysis practices, techniques, and professional standards rather than a single tool or technical domain.",
"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 reasonably confused with another catalog skill in typical job descriptions."
},
"context_keywords": {
"context_keywords": [
"BABOK",
"requirements elicitation",
"stakeholder analysis",
"process modeling",
"use cases",
"user stories",
"gap analysis",
"business process improvement",
"UML",
"SWOT analysis",
"workshops",
"traceability matrix",
"functional requirements",
"solution assessment",
"acceptance criteria"
]
},
"maturity": {
"confidence": 0.84,
"maturity": "well_known",
"reasoning": "CBAP appears frequently in business analyst job descriptions and certification requirements, especially in enterprise BA roles; IIBA continues to maintain and promote it as a standard credential."
},
"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
}
},
"locked_dimensions": [
{
"description": "Formal business analysis credentialing and body-of-knowledge preparation. CBAP belongs here because it is a certification focused on advanced business analysis practices, techniques, and professional standards rather than a single tool or technical domain.",
"exemplar_skills": [
"CBAP",
"CCBA",
"ECBA",
"BABOK",
"requirements elicitation",
"stakeholder analysis",
"process modeling",
"solution evaluation"
],
"in_scope": "CBAP, CCBA, ECBA, business analysis certification prep, BABOK knowledge areas, requirements elicitation, stakeholder analysis, process modeling, solution evaluation",
"name": "Business Analysis Certification",
"out_of_scope": "Software testing execution, project management certification, data analysis methods, technical implementation skills, product design work",
"overlap_flags": [
{
"reason": "Business analysts often validate requirements and acceptance criteria, but CBAP is broader professional certification knowledge rather than test validation practice.",
"with_dim_id": "requirements-and-acceptance-validation",
"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",
"capacity-planning",
"acceptance-criteria-validation",
"acceptance-criteria-checks",
"session-based-testing"
],
"requires": [],
"skill_id": "cbap",
"suppress_on_match": []
},
"skill_id": "cbap",
"split_log": [],
"typed": {
"alternatives_considered": [],
"confidence": 0.99,
"name": "CBAP",
"reasoning": "CBAP is a formal third-party credential, so by the Certification rule it is a Certification rather than a concept or methodology.",
"skill_id": "cbap",
"subtype": "business_analysis_professional_certification",
"type": "Certification"
},
"warnings": []
},
"source_tag": "llm",
"was_in_llm_skills": true
},
{
"aliases_in_db": [],
"canonical": null,
"dimensions": [
{
"dimension": {
"difficulty_hint": null,
"display_name": "Business Analysis Certification",
"id": null,
"rationale": "Formal business analysis credentialing and exam-based professional standards. CCBA belongs here because it is a recognized certification for practicing business analysts, focused on validated competency rather than a specific technical tool or method.",
"slug": "d_init_01",
"source": "llm"
},
"input_skill": "CCBA",
"llm_role": null,
"roles_from_db": []
}
],
"input_skill": "CCBA",
"matched_via": null,
"new_alias_persisted": false,
"new_alias_text": null,
"new_skill_meta": {
"derived": {
"category": "Certification",
"skill_nature": "CREDENTIAL",
"sub_category": "business_analysis_certification",
"typical_lifespan": "EVERGREEN",
"version_strategy": "NOT_APPLICABLE",
"volatility": "STABLE"
},
"enrichment": {
"ambiguity": {
"ambiguity_flag": true,
"confused_with": [
"cbap"
],
"reasoning": "CCBA is a business analysis certification acronym and can be mistaken for the closely related CBAP certification in job descriptions, especially when abbreviations are used loosely."
},
"context_keywords": {
"context_keywords": [
"BABOK",
"IIBA",
"requirements elicitation",
"stakeholder analysis",
"process modeling",
"use cases",
"user stories",
"gap analysis",
"business process improvement",
"solution assessment",
"traceability matrix",
"SWOT analysis",
"workshop facilitation",
"UML",
"BRD"
]
},
"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.93,
"license": null,
"vendor": "International Institute of Business Analysis",
"year_introduced": 2008
},
"versioning": {
"current_version": null,
"version_aliases": {},
"versioned": false
}
},
"locked_dimensions": [
{
"description": "Formal business analysis credentialing and exam-based professional standards. CCBA belongs here because it is a recognized certification for practicing business analysts, focused on validated competency rather than a specific technical tool or method.",
"exemplar_skills": [
"CCBA",
"CBAP",
"ECBA",
"IIBA certification",
"business analysis certification",
"exam preparation"
],
"in_scope": "CCBA, CBAP, ECBA, business analysis certification, IIBA certification, exam preparation, certification maintenance, professional competency validation",
"name": "Business Analysis Certification",
"out_of_scope": "requirements elicitation, process modeling, stakeholder analysis, user stories, acceptance criteria, which belong to business analysis practice and requirements dimensions rather than the credential itself",
"overlap_flags": [
{
"reason": "Certified business analysts often work with requirements, but the certification itself is a credentialing dimension rather than a requirements practice dimension.",
"with_dim_id": "requirements-and-acceptance-validation",
"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"
],
"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 a Certification rather than a concept or methodology.",
"skill_id": "ccba",
"subtype": "business_analysis_certification",
"type": "Certification"
},
"warnings": []
},
"source_tag": "llm",
"was_in_llm_skills": true
},
{
"aliases_in_db": [],
"canonical": null,
"dimensions": [
{
"dimension": {
"difficulty_hint": null,
"display_name": "Spreadsheet Analysis and Modeling",
"id": null,
"rationale": "Using spreadsheets to organize, analyze, and present business data. Excel belongs here because it is the standard tool for tabular analysis, formulas, pivoting, and lightweight reporting in business analysis work.",
"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 and unlikely to be confused with another catalog skill."
},
"context_keywords": {
"context_keywords": [
"pivot tables",
"VLOOKUP",
"XLOOKUP",
"INDEX MATCH",
"Power Query",
"Power Pivot",
"macros",
"VBA",
"data validation",
"conditional formatting",
"SUMIFS",
"charts",
"dashboards",
"CSV",
"workbooks"
]
},
"maturity": {
"confidence": 0.98,
"maturity": "well_known",
"reasoning": "Excel appears in a very large share of business, finance, ops, and analyst job descriptions; Microsoft continues active support and it remains a standard spreadsheet tool rather than a sunset product."
},
"skill_id": "excel",
"vendor_license": {
"confidence": 0.99,
"license": "proprietary",
"vendor": "Microsoft",
"year_introduced": 1985
},
"versioning": {
"current_version": "Microsoft 365 / Excel 2024",
"version_aliases": {
"Excel 2007": "Excel 2007",
"Excel 2010": "Excel 2010",
"Excel 2013": "Excel 2013",
"Excel 2016": "Excel 2016",
"Excel 2019": "Excel 2019",
"Excel 2021": "Excel 2021",
"Excel 2024": "Microsoft 365 / Excel 2024",
"Excel 365": "Microsoft 365 / Excel 2024",
"Microsoft 365 Excel": "Microsoft 365 / Excel 2024"
},
"versioned": true
}
},
"locked_dimensions": [
{
"description": "Using spreadsheets to organize, analyze, and present business data. Excel belongs here because it is the standard tool for tabular analysis, formulas, pivoting, and lightweight reporting in business analysis work.",
"exemplar_skills": [
"Excel",
"Pivot Tables",
"VLOOKUP",
"XLOOKUP",
"Conditional Formatting",
"What-If Analysis",
"Spreadsheet Modeling"
],
"in_scope": "Excel, formulas and functions, pivot tables, charts, conditional formatting, data validation, lookup functions, what-if analysis, basic financial models, worksheet design, spreadsheet reporting",
"name": "Spreadsheet Analysis and Modeling",
"out_of_scope": "SQL querying and database design, statistical inference and experiment design, BI dashboard platforms, programming languages for automation, enterprise data governance",
"overlap_flags": [
{
"reason": "Excel is often used for descriptive analysis, but deeper statistical interpretation belongs to the statistics dimension.",
"with_dim_id": "statistical-reasoning-for-analysis",
"with_dim_name": null,
"with_role": null
},
{
"reason": "Excel can produce reports and charts, but dedicated dashboard configuration is a separate reporting skill set.",
"with_dim_id": "reporting-and-dashboard-configuration",
"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 rather than a hosted multi-tenant environment, so by the Tool vs Platform rule it is a Tool.",
"skill_id": "excel",
"subtype": "spreadsheet_software",
"type": "Tool"
},
"warnings": []
},
"source_tag": "llm",
"was_in_llm_skills": true
},
{
"aliases_in_db": [],
"canonical": null,
"dimensions": [
{
"dimension": {
"difficulty_hint": null,
"display_name": "Functional Requirements Documentation",
"id": null,
"rationale": "Covers writing and maintaining functional requirements documents that specify what a product or process must do. FRDs belong here because they capture business needs, scope, workflows, and acceptance expectations in a formal requirements artifact.",
"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",
"requirements traceability matrix",
"functional specification",
"business requirements",
"stakeholder interviews",
"process flows",
"wireframes",
"UAT",
"scope definition",
"change requests",
"sign-off"
]
},
"maturity": {
"confidence": 0.78,
"maturity": "well_known",
"reasoning": "Functional requirements documents (FRDs) are a standard artifact in many product and business-analysis job descriptions and enterprise SDLC templates; they remain a common hiring-pipeline expectation for BA/PM roles."
},
"skill_id": "frds",
"vendor_license": {
"confidence": 0.98,
"license": null,
"vendor": null,
"year_introduced": null
},
"versioning": {
"current_version": null,
"version_aliases": {},
"versioned": false
}
},
"locked_dimensions": [
{
"description": "Covers writing and maintaining functional requirements documents that specify what a product or process must do. FRDs belong here because they capture business needs, scope, workflows, and acceptance expectations in a formal requirements artifact.",
"exemplar_skills": [
"FRDs",
"functional requirements documentation",
"business requirements gathering",
"use case writing",
"user story elaboration",
"acceptance criteria definition"
],
"in_scope": "FRDs, functional requirements documents, business requirements, use cases, user flows, scope definitions, acceptance criteria, process rules, feature specifications",
"name": "Functional Requirements Documentation",
"out_of_scope": "Technical design specs, API contracts, database schemas, test execution, project planning, which belong to architecture, engineering, QA, or delivery management dimensions",
"overlap_flags": [
{
"reason": "FRDs often feed validation, but this dimension is about authoring the requirements artifact rather than checking implementation against it.",
"with_dim_id": "requirements-and-acceptance-validation",
"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 it is not a single knowledge principle but a document/artifact category.",
"Methodology: ruled out \u2014 it does not describe a way of working or process.",
"Format: ruled out \u2014 it is not primarily a data structure or wire format."
],
"confidence": 0.67,
"name": "FRDs",
"reasoning": "FRDs are a body of knowledge/artifact category used in product and systems work, so by the Concept vs Methodology and Domain guidance they fit best as a Domain rather than a tool or format.",
"skill_id": "frds",
"subtype": "functional_requirements_documents",
"type": "Domain"
},
"warnings": []
},
"source_tag": "llm",
"was_in_llm_skills": true
},
{
"aliases_in_db": [],
"canonical": null,
"dimensions": [],
"input_skill": "QA",
"matched_via": null,
"new_alias_persisted": false,
"new_alias_text": null,
"new_skill_meta": {
"derived": {
"category": "SoftSkill",
"skill_nature": "PRACTICE",
"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 or QA testing roles; a parser could confuse the shorthand with the broader quality_assurance skill entry."
},
"context_keywords": {
"context_keywords": [
"test cases",
"test plans",
"test scripts",
"defect tracking",
"bug triage",
"regression testing",
"UAT",
"manual testing",
"automation testing",
"test coverage",
"acceptance criteria",
"JIRA",
"Selenium",
"QA process",
"test strategy"
]
},
"maturity": {
"confidence": 0.93,
"maturity": "well_known",
"reasoning": "QA is a standard hiring-pipeline requirement across software JDs, with frequent mentions of test planning, defect tracking, and regression testing; market demand remains broad rather than niche."
},
"skill_id": "qa",
"vendor_license": {
"confidence": 0.99,
"license": null,
"vendor": null,
"year_introduced": null
},
"versioning": {
"current_version": null,
"version_aliases": {},
"versioned": false
}
},
"locked_dimensions": [],
"merge_log": [
{
"a_dim_id": "d_init_01",
"a_name": "Requirements and Acceptance Validation",
"a_role": "__skill_focal__",
"b_dim_id": "requirements-and-acceptance-validation",
"b_name": "Requirements and Acceptance Validation",
"b_role": "existing_catalog",
"into": "d_merge_01",
"into_name": "Requirements and Acceptance Validation",
"merged_from": [
"d_init_01",
"requirements-and-acceptance-validation"
],
"pair_kind": "cross_role",
"reasoning": "Both dims describe the same QA activity: checking implemented behavior against requirements, user stories, and acceptance criteria. Dim A adds business-analyst/UAT wording plus manual test case execution and defect logging; Dim B states the same core scope more concisely. The exemplar skills in A (QA, requirements validation, acceptance testing, UAT, defect reporting) are direct matches to B\u2019s description, so this is one cluster, not two.",
"similarity": 0.7761651637290947
}
],
"placed": {
"name": "QA",
"placement_confidence": 0.0,
"primary_dimension": "d_init_00",
"reasoning": "Stub placement: no locked_dimensions after Stage 2/3; downstream containment and enrichment use placeholders only.",
"secondary_dimensions": [],
"skill_id": "qa"
},
"relationships": {
"child_skills": [],
"parent_skills": [],
"related_to": [
"acceptance-criteria-checks",
"acceptance-criteria-validation",
"test-case-authoring",
"defect-retest",
"risk-based-testing",
"cross-browser-testing",
"session-based-testing",
"charter-based-testing",
"health-checks"
],
"requires": [],
"skill_id": "qa",
"suppress_on_match": []
},
"skill_id": "qa",
"split_log": [],
"typed": {
"alternatives_considered": [
"Methodology: ruled out \u2014 QA is often a process, but the term here is broader and commonly denotes the quality assurance function rather than a named process like TDD or Scrum.",
"Concept: ruled out \u2014 it is not primarily a knowledge unit like idempotency or CAP theorem."
],
"confidence": 0.78,
"name": "QA",
"reasoning": "QA is best treated as a quality assurance practice/role-related capability rather than a software artifact, and under the Concept vs Methodology rule it fits a way of working focused on verifying quality.",
"skill_id": "qa",
"subtype": "quality_assurance",
"type": "SoftSkill"
},
"warnings": [
"placement_stub_no_locked_dimensions"
]
},
"source_tag": "llm",
"was_in_llm_skills": true
},
{
"aliases_in_db": [],
"canonical": null,
"dimensions": [
{
"dimension": {
"difficulty_hint": null,
"display_name": "Software Development Lifecycle",
"id": null,
"rationale": "Covers the end-to-end process used to plan, build, test, release, and maintain software products. SDLC belongs here because it refers to the overall delivery lifecycle 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-established acronym for software development lifecycle; in typical JDs it is unlikely to be mistaken for a different catalog skill."
},
"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
}
},
"locked_dimensions": [
{
"description": "Covers the end-to-end process used to plan, build, test, release, and maintain software products. SDLC belongs here because it refers to the overall delivery lifecycle rather than a single technical practice.",
"exemplar_skills": [
"SDLC",
"software development lifecycle",
"application lifecycle management",
"release lifecycle planning",
"development process management"
],
"in_scope": "SDLC, requirements gathering, design, implementation, testing, release management, maintenance, change control, development process, software delivery lifecycle",
"name": "Software Development Lifecycle",
"out_of_scope": "specific QA execution, coding in a particular language, CI/CD tooling, production incident handling, project management methodology",
"overlap_flags": [
{
"reason": "SDLC often includes requirements and acceptance steps, but that catalog dimension is narrower and focused on validating implemented behavior.",
"with_dim_id": "requirements-and-acceptance-validation",
"with_dim_name": null,
"with_role": null
},
{
"reason": "SDLC can include release activities, but this catalog dimension is specifically about build and release preparation rather than the full lifecycle.",
"with_dim_id": "build-configuration-and-release",
"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": [
"acceptance-criteria-checks",
"acceptance-criteria-validation",
"defect-retest",
"dependency-mapping",
"shutdown-sequencing"
],
"requires": [],
"skill_id": "sdlc",
"suppress_on_match": []
},
"skill_id": "sdlc",
"split_log": [],
"typed": {
"alternatives_considered": [
"Concept: ruled out \u2014 it is more than a knowledge unit; it is a process model for working through software development.",
"Architecture: ruled out \u2014 it does not describe a system shape or structural pattern."
],
"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": "Software as a Service",
"id": null,
"rationale": "Covers cloud-delivered subscription software products and the business/operational concepts around them. SaaS fits here because it refers to a software delivery and commercial model rather than a specific technical implementation skill.",
"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-established term for software as a service; in JDs it is usually unambiguous and not likely 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",
"admin console",
"provisioning",
"SLAs",
"customer portal",
"metering"
]
},
"maturity": {
"confidence": 0.97,
"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.88,
"license": null,
"vendor": null,
"year_introduced": 1999
},
"versioning": {
"current_version": null,
"version_aliases": {},
"versioned": false
}
},
"locked_dimensions": [
{
"description": "Covers cloud-delivered subscription software products and the business/operational concepts around them. SaaS fits here because it refers to a software delivery and commercial model rather than a specific technical implementation skill.",
"exemplar_skills": [
"SaaS",
"subscription software",
"multi-tenant applications",
"hosted software products",
"recurring revenue models"
],
"in_scope": "SaaS, subscription software, multi-tenant application delivery, hosted web applications, recurring billing models, customer onboarding for SaaS, product packaging and tiers, service availability expectations",
"name": "Software as a Service",
"out_of_scope": "On-premises software deployment, infrastructure provisioning, API integration, mobile app development, which belong to other engineering dimensions or product areas",
"overlap_flags": [
{
"reason": "SaaS products are often built on cloud services, but this dimension is about selecting platform primitives rather than the SaaS delivery model itself.",
"with_dim_id": "cloud-platform-service-selection",
"with_dim_name": null,
"with_role": null
},
{
"reason": "SaaS systems commonly use service-oriented architectures, but that dimension focuses on backend structure and integration patterns.",
"with_dim_id": "service-architecture-and-integration",
"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, not a specific managed capability inside another platform.",
"Tool: ruled out \u2014 SaaS is not software you operate locally; it is hosted for users."
],
"confidence": 0.88,
"name": "SaaS",
"reasoning": "By the Platform vs Tool rule, SaaS is a hosted multi-tenant environment delivered over APIs and managed services rather than software you run yourself.",
"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": [],
"input_skill": "Testing",
"matched_via": null,
"new_alias_persisted": false,
"new_alias_text": null,
"new_skill_meta": {
"derived": {
"category": "Methodology",
"skill_nature": "METHODOLOGY",
"sub_category": "software_testing_methodology",
"typical_lifespan": "EVERGREEN",
"version_strategy": "NOT_APPLICABLE",
"volatility": "STABLE"
},
"enrichment": {
"ambiguity": {
"ambiguity_flag": true,
"confused_with": [
"unit_testing",
"integration_testing",
"automated_testing",
"manual_testing",
"test_automation"
],
"reasoning": "\u201cTesting\u201d is a broad umbrella term in JDs and can easily refer to specific testing methodologies or automation practices rather than the generic skill itself."
},
"context_keywords": {
"context_keywords": [
"unit testing",
"integration testing",
"test automation",
"test cases",
"regression testing",
"TDD",
"BDD",
"pytest",
"JUnit",
"Selenium",
"Cypress",
"mocking",
"test coverage",
"QA",
"CI/CD"
]
},
"maturity": {
"confidence": 0.97,
"maturity": "well_known",
"reasoning": "Software testing is a standard requirement in most engineering JDs and appears across QA, SDET, and developer roles; CI/CD tooling and frameworks like pytest, JUnit, and Playwright reinforce broad market adoption."
},
"skill_id": "testing",
"vendor_license": {
"confidence": 0.99,
"license": null,
"vendor": null,
"year_introduced": null
},
"versioning": {
"current_version": null,
"version_aliases": {},
"versioned": false
}
},
"locked_dimensions": [],
"merge_log": [
{
"a_dim_id": "d_init_01",
"a_name": "Requirements and Acceptance Validation",
"a_role": "__skill_focal__",
"b_dim_id": "requirements-and-acceptance-validation",
"b_name": "Requirements and Acceptance Validation",
"b_role": "existing_catalog",
"into": "d_merge_01",
"into_name": "Requirements and Acceptance Validation",
"merged_from": [
"d_init_01",
"requirements-and-acceptance-validation"
],
"pair_kind": "cross_role",
"reasoning": "Both dims describe the same skill cluster: checking delivered behavior against requirements, user stories, and acceptance criteria. Dim A adds BA/UAT framing plus manual test execution, defect logging, and traceability; Dim B states the same core idea in broader terms. The exemplar skills in A (requirements validation, acceptance criteria verification, user acceptance testing, manual test execution, traceability matrix) all fit B as well.",
"similarity": 0.8129248235661417
}
],
"placed": {
"name": "Testing",
"placement_confidence": 0.0,
"primary_dimension": "d_init_00",
"reasoning": "Stub placement: no locked_dimensions after Stage 2/3; downstream containment and enrichment use placeholders only.",
"secondary_dimensions": [],
"skill_id": "testing"
},
"relationships": {
"child_skills": [],
"parent_skills": [],
"related_to": [
"risk-based-testing",
"session-based-testing",
"cross-browser-testing",
"smoke-testing",
"fuzzing",
"charter-based-testing",
"defect-retest",
"restore-testing"
],
"requires": [],
"skill_id": "testing",
"suppress_on_match": []
},
"skill_id": "testing",
"split_log": [],
"typed": {
"alternatives_considered": [],
"confidence": 0.92,
"name": "Testing",
"reasoning": "Testing is fundamentally a way of working for validating software behavior, so by the Concept vs Methodology rule it fits Methodology rather than a tool or concept.",
"skill_id": "testing",
"subtype": "software_testing_methodology",
"type": "Methodology"
},
"warnings": [
"placement_stub_no_locked_dimensions"
]
},
"source_tag": "llm",
"was_in_llm_skills": true
},
{
"aliases_in_db": [],
"canonical": null,
"dimensions": [],
"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",
"defect triage",
"test scenarios",
"regression testing",
"test plan",
"stakeholder review",
"go-live",
"sandbox",
"pilot testing",
"smoke testing"
]
},
"maturity": {
"confidence": 0.86,
"maturity": "well_known",
"reasoning": "UAT appears routinely in QA/BA job descriptions and enterprise release checklists as a standard pre-production signoff step, with no vendor sunset or replacement trend."
},
"skill_id": "uat",
"vendor_license": {
"confidence": 0.99,
"license": null,
"vendor": null,
"year_introduced": null
},
"versioning": {
"current_version": null,
"version_aliases": {},
"versioned": false
}
},
"locked_dimensions": [],
"merge_log": [
{
"a_dim_id": "d_init_01",
"a_name": "Requirements and Acceptance Validation",
"a_role": "__skill_focal__",
"b_dim_id": "requirements-and-acceptance-validation",
"b_name": "Requirements and Acceptance Validation",
"b_role": "existing_catalog",
"into": "d_merge_01",
"into_name": "Requirements and Acceptance Validation",
"merged_from": [
"d_init_01",
"requirements-and-acceptance-validation"
],
"pair_kind": "cross_role",
"reasoning": "Both dims describe the same skill cluster: validating delivered behavior against requirements, user stories, and acceptance criteria. Dim A explicitly covers UAT, acceptance criteria verification, requirements traceability, business scenario validation, stakeholder sign-off, and defect confirmation against stories. Dim B says the same thing in broader wording: checking implemented behavior matches documented requirements, user stories, and acceptance criteria. The overlap is substantive, not just naming, and no distinct skill boundary appears.",
"similarity": 0.7556975361219991
}
],
"placed": {
"name": "UAT",
"placement_confidence": 0.0,
"primary_dimension": "d_init_00",
"reasoning": "Stub placement: no locked_dimensions after Stage 2/3; downstream containment and enrichment use placeholders only.",
"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 users before release, so by the Concept vs Methodology rule it is a Methodology rather than a Concept or Tool.",
"skill_id": "uat",
"subtype": "user_acceptance_testing",
"type": "Methodology"
},
"warnings": [
"placement_stub_no_locked_dimensions"
]
},
"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, swimlanes, org charts, and system diagrams 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 specific Microsoft diagramming tool; in typical JDs it is unlikely to be confused with another catalog skill."
},
"context_keywords": {
"context_keywords": [
"flowchart",
"swimlane",
"process map",
"BPMN",
"UML",
"network diagram",
"org chart",
"data flow diagram",
"wireframe",
"floor plan",
"SIPOC",
"value stream map",
"Visio stencils",
"cross-functional diagram",
"process documentation"
]
},
"maturity": {
"confidence": 0.86,
"maturity": "well_known",
"reasoning": "Common in enterprise JDs for process/network diagrams and Microsoft 365 ecosystems; Microsoft continues to support and sell Visio, with no vendor sunset announced."
},
"skill_id": "visio",
"vendor_license": {
"confidence": 0.99,
"license": "proprietary",
"vendor": "Microsoft",
"year_introduced": 1992
},
"versioning": {
"current_version": null,
"version_aliases": {},
"versioned": false
}
},
"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, swimlanes, org charts, and system diagrams for analysis and documentation.",
"exemplar_skills": [
"Visio",
"flowcharting",
"swimlane diagramming",
"process mapping",
"org chart creation",
"BPMN diagramming",
"system diagramming"
],
"in_scope": "Visio, process maps, swimlane diagrams, flowcharts, org charts, UML sketches, network diagrams, system context diagrams, BPMN-style modeling, wireframe sketches, documentation diagrams",
"name": "Diagramming and Process Modeling",
"out_of_scope": "Hands-on process improvement methods, requirements elicitation, data modeling, and project management artifacts, which belong to other analysis or architecture dimensions",
"overlap_flags": [
{
"reason": "Visio is often used to produce network diagrams and operational documentation, which can overlap with network documentation work.",
"with_dim_id": "network-documentation-and-standards",
"with_dim_name": null,
"with_role": null
},
{
"reason": "System and integration diagrams made in Visio can support architecture communication, though the core skill here is diagram creation rather than architecture design.",
"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",
"session-charters",
"scorecards",
"threat-modeling",
"mvvm",
"portal-pages",
"portal-navigation"
],
"requires": [],
"skill_id": "visio",
"suppress_on_match": []
},
"skill_id": "visio",
"split_log": [],
"typed": {
"alternatives_considered": [],
"confidence": 0.98,
"name": "Visio",
"reasoning": "Visio is software you operate to create diagrams, so by the Tool vs Framework rule it is a Tool rather than something you build applications inside.",
"skill_id": "visio",
"subtype": "diagramming_tool",
"type": "Tool"
},
"warnings": []
},
"source_tag": "llm",
"was_in_llm_skills": true
},
{
"aliases_in_db": [],
"canonical": null,
"dimensions": [],
"input_skill": "analysis",
"matched_via": null,
"new_alias_persisted": false,
"new_alias_text": null,
"new_skill_meta": null,
"source_tag": "llm",
"was_in_llm_skills": true
},
{
"aliases_in_db": [],
"canonical": null,
"dimensions": [],
"input_skill": "communication",
"matched_via": null,
"new_alias_persisted": false,
"new_alias_text": null,
"new_skill_meta": null,
"source_tag": "llm",
"was_in_llm_skills": true
},
{
"aliases_in_db": [],
"canonical": null,
"dimensions": [],
"input_skill": "data",
"matched_via": null,
"new_alias_persisted": false,
"new_alias_text": null,
"new_skill_meta": null,
"source_tag": "llm",
"was_in_llm_skills": true
},
{
"aliases_in_db": [],
"canonical": null,
"dimensions": [],
"input_skill": "databases",
"matched_via": null,
"new_alias_persisted": false,
"new_alias_text": null,
"new_skill_meta": null,
"source_tag": "llm",
"was_in_llm_skills": true
},
{
"aliases_in_db": [],
"canonical": null,
"dimensions": [],
"input_skill": "documentation",
"matched_via": null,
"new_alias_persisted": false,
"new_alias_text": null,
"new_skill_meta": null,
"source_tag": "llm",
"was_in_llm_skills": true
},
{
"aliases_in_db": [],
"canonical": null,
"dimensions": [],
"input_skill": "fintech",
"matched_via": null,
"new_alias_persisted": false,
"new_alias_text": null,
"new_skill_meta": null,
"source_tag": "llm",
"was_in_llm_skills": true
},
{
"aliases_in_db": [],
"canonical": null,
"dimensions": [],
"input_skill": "healthcare",
"matched_via": null,
"new_alias_persisted": false,
"new_alias_text": null,
"new_skill_meta": null,
"source_tag": "llm",
"was_in_llm_skills": true
},
{
"aliases_in_db": [],
"canonical": null,
"dimensions": [],
"input_skill": "insights",
"matched_via": null,
"new_alias_persisted": false,
"new_alias_text": null,
"new_skill_meta": null,
"source_tag": "llm",
"was_in_llm_skills": true
},
{
"aliases_in_db": [],
"canonical": null,
"dimensions": [],
"input_skill": "methodologies",
"matched_via": null,
"new_alias_persisted": false,
"new_alias_text": null,
"new_skill_meta": null,
"source_tag": "llm",
"was_in_llm_skills": true
},
{
"aliases_in_db": [],
"canonical": null,
"dimensions": [],
"input_skill": "optimization",
"matched_via": null,
"new_alias_persisted": false,
"new_alias_text": null,
"new_skill_meta": null,
"source_tag": "llm",
"was_in_llm_skills": true
},
{
"aliases_in_db": [],
"canonical": null,
"dimensions": [],
"input_skill": "problem",
"matched_via": null,
"new_alias_persisted": false,
"new_alias_text": null,
"new_skill_meta": null,
"source_tag": "llm",
"was_in_llm_skills": true
},
{
"aliases_in_db": [],
"canonical": null,
"dimensions": [],
"input_skill": "reporting",
"matched_via": null,
"new_alias_persisted": false,
"new_alias_text": null,
"new_skill_meta": null,
"source_tag": "llm",
"was_in_llm_skills": true
},
{
"aliases_in_db": [],
"canonical": null,
"dimensions": [],
"input_skill": "requirements",
"matched_via": null,
"new_alias_persisted": false,
"new_alias_text": null,
"new_skill_meta": null,
"source_tag": "llm",
"was_in_llm_skills": true
},
{
"aliases_in_db": [],
"canonical": null,
"dimensions": [],
"input_skill": "software",
"matched_via": null,
"new_alias_persisted": false,
"new_alias_text": null,
"new_skill_meta": null,
"source_tag": "llm",
"was_in_llm_skills": true
},
{
"aliases_in_db": [],
"canonical": null,
"dimensions": [],
"input_skill": "specifications",
"matched_via": null,
"new_alias_persisted": false,
"new_alias_text": null,
"new_skill_meta": null,
"source_tag": "llm",
"was_in_llm_skills": true
},
{
"aliases_in_db": [],
"canonical": null,
"dimensions": [],
"input_skill": "stakeholder",
"matched_via": null,
"new_alias_persisted": false,
"new_alias_text": null,
"new_skill_meta": null,
"source_tag": "llm",
"was_in_llm_skills": true
},
{
"aliases_in_db": [],
"canonical": null,
"dimensions": [],
"input_skill": "stories",
"matched_via": null,
"new_alias_persisted": false,
"new_alias_text": null,
"new_skill_meta": null,
"source_tag": "llm",
"was_in_llm_skills": true
},
{
"aliases_in_db": [],
"canonical": null,
"dimensions": [],
"input_skill": "strategies",
"matched_via": null,
"new_alias_persisted": false,
"new_alias_text": null,
"new_skill_meta": null,
"source_tag": "llm",
"was_in_llm_skills": true
},
{
"aliases_in_db": [],
"canonical": null,
"dimensions": [],
"input_skill": "tools",
"matched_via": null,
"new_alias_persisted": false,
"new_alias_text": null,
"new_skill_meta": null,
"source_tag": "llm",
"was_in_llm_skills": true
},
{
"aliases_in_db": [],
"canonical": null,
"dimensions": [],
"input_skill": "trends",
"matched_via": null,
"new_alias_persisted": false,
"new_alias_text": null,
"new_skill_meta": null,
"source_tag": "llm",
"was_in_llm_skills": true
},
{
"aliases_in_db": [],
"canonical": null,
"dimensions": [],
"input_skill": "workshops",
"matched_via": null,
"new_alias_persisted": false,
"new_alias_text": null,
"new_skill_meta": null,
"source_tag": "llm",
"was_in_llm_skills": true
}
],
"unmatched_skills": [
"APIs",
"Acceptance",
"BI",
"CBAP",
"CCBA",
"Excel",
"FRDs",
"QA",
"SDLC",
"SaaS",
"Testing",
"UAT",
"Visio"
]
}
API 3 — final-role-output
{
"chosen_role": {
"display_name": "Data Analyst",
"id": 20,
"rationale": "The strongest mapped dimension is reporting and dashboard development, which links directly to Data Analyst and has the clearest evidence weight.",
"role_archetype": null,
"slug": "data-analyst",
"source": "db"
},
"final_input_skills": [
{
"skill": "Power BI",
"tag": "in_db"
},
{
"skill": "Tableau",
"tag": "in_db"
},
{
"skill": "Argo Workflows",
"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": "Testing",
"tag": "new"
},
{
"skill": "UAT",
"tag": "new"
},
{
"skill": "Visio",
"tag": "new"
},
{
"skill": "analysis",
"tag": "new"
},
{
"skill": "communication",
"tag": "new"
},
{
"skill": "data",
"tag": "new"
},
{
"skill": "databases",
"tag": "new"
},
{
"skill": "documentation",
"tag": "new"
},
{
"skill": "fintech",
"tag": "new"
},
{
"skill": "healthcare",
"tag": "new"
},
{
"skill": "insights",
"tag": "new"
},
{
"skill": "methodologies",
"tag": "new"
},
{
"skill": "optimization",
"tag": "new"
},
{
"skill": "problem",
"tag": "new"
},
{
"skill": "reporting",
"tag": "new"
},
{
"skill": "requirements",
"tag": "new"
},
{
"skill": "software",
"tag": "new"
},
{
"skill": "specifications",
"tag": "new"
},
{
"skill": "stakeholder",
"tag": "new"
},
{
"skill": "stories",
"tag": "new"
},
{
"skill": "strategies",
"tag": "new"
},
{
"skill": "tools",
"tag": "new"
},
{
"skill": "trends",
"tag": "new"
},
{
"skill": "workshops",
"tag": "new"
}
],
"persistence": {
"items": [
{
"chosen_role_id": 20,
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Reporting and Dashboard Development",
"id": 295,
"rationale": "Building recurring reports and dashboards that track performance over time and across segments. This is a distinct cluster because the analyst must package metrics into reusable views for stakeholders.",
"slug": "reporting-and-dashboard-development",
"source": "db"
},
"dimension_id": 295,
"input_skill": "Power BI",
"llm_role": null,
"matched_chosen_role": true,
"role_dimension_saved": false,
"roles_from_db": [
{
"display_name": "Data Analyst",
"id": 20,
"rationale": null,
"role_archetype": null,
"slug": "data-analyst",
"source": "db"
}
],
"skill_dimension_saved": false,
"skill_id": 1884,
"skill_tag": "in_db",
"skipped_reason": "TODO: REMOVE AFTER TESTING \u2014 api3_writes_enabled=False (writes disabled)"
},
{
"chosen_role_id": 20,
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Reporting and Dashboard Development",
"id": 295,
"rationale": "Building recurring reports and dashboards that track performance over time and across segments. This is a distinct cluster because the analyst must package metrics into reusable views for stakeholders.",
"slug": "reporting-and-dashboard-development",
"source": "db"
},
"dimension_id": 295,
"input_skill": "Tableau",
"llm_role": null,
"matched_chosen_role": true,
"role_dimension_saved": false,
"roles_from_db": [
{
"display_name": "Data Analyst",
"id": 20,
"rationale": null,
"role_archetype": null,
"slug": "data-analyst",
"source": "db"
}
],
"skill_dimension_saved": false,
"skill_id": 1883,
"skill_tag": "in_db",
"skipped_reason": "TODO: REMOVE AFTER TESTING \u2014 api3_writes_enabled=False (writes disabled)"
},
{
"chosen_role_id": 20,
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Workflow Orchestration Systems",
"id": 64,
"rationale": "Operational orchestration of ML jobs, dependencies, and handoffs across training, validation, deployment, and retraining. This is a useful split from training pipelines because it emphasizes the scheduler and control plane.",
"slug": "workflow-orchestration-systems",
"source": "db"
},
"dimension_id": 64,
"input_skill": "Argo Workflows",
"llm_role": null,
"matched_chosen_role": false,
"role_dimension_saved": false,
"roles_from_db": [
{
"display_name": "Data Engineer",
"id": 6,
"rationale": null,
"role_archetype": null,
"slug": "data-engineer",
"source": "db"
},
{
"display_name": "MLOps Engineer",
"id": 5,
"rationale": null,
"role_archetype": null,
"slug": "mlops-engineer",
"source": "db"
}
],
"skill_dimension_saved": false,
"skill_id": 380,
"skill_tag": "in_db",
"skipped_reason": "TODO: REMOVE AFTER TESTING \u2014 api3_writes_enabled=False (writes disabled)"
},
{
"chosen_role_id": 20,
"dimension": {
"difficulty_hint": null,
"display_name": "API Design and Integration",
"id": null,
"rationale": "Designing and using application programming interfaces for system-to-system communication. This covers how business systems expose, consume, version, and document interfaces, which is the core meaning of APIs for an analyst working with process and integration requirements.",
"slug": "d_init_01",
"source": "llm"
},
"dimension_id": null,
"input_skill": "APIs",
"llm_role": null,
"matched_chosen_role": false,
"role_dimension_saved": false,
"roles_from_db": [],
"skill_dimension_saved": false,
"skill_id": null,
"skill_tag": "new",
"skipped_reason": "skill_not_in_db_v3_proposed"
},
{
"chosen_role_id": 20,
"dimension": {
"difficulty_hint": null,
"display_name": "Business Intelligence",
"id": null,
"rationale": "Covers the use of data to create reports, dashboards, and decision-support views for business users. BI fits here because it commonly refers to the discipline of turning operational data into accessible insights for analysis and management.",
"slug": "d_init_01",
"source": "llm"
},
"dimension_id": null,
"input_skill": "BI",
"llm_role": null,
"matched_chosen_role": false,
"role_dimension_saved": false,
"roles_from_db": [],
"skill_dimension_saved": false,
"skill_id": null,
"skill_tag": "new",
"skipped_reason": "skill_not_in_db_v3_proposed"
},
{
"chosen_role_id": 20,
"dimension": {
"difficulty_hint": null,
"display_name": "Business Analysis Certification",
"id": null,
"rationale": "Formal business analysis credentialing and body-of-knowledge preparation. CBAP belongs here because it is a certification focused on advanced business analysis practices, techniques, and professional standards rather than a single tool or technical domain.",
"slug": "d_init_01",
"source": "llm"
},
"dimension_id": null,
"input_skill": "CBAP",
"llm_role": null,
"matched_chosen_role": false,
"role_dimension_saved": false,
"roles_from_db": [],
"skill_dimension_saved": false,
"skill_id": null,
"skill_tag": "new",
"skipped_reason": "skill_not_in_db_v3_proposed"
},
{
"chosen_role_id": 20,
"dimension": {
"difficulty_hint": null,
"display_name": "Business Analysis Certification",
"id": null,
"rationale": "Formal business analysis credentialing and exam-based professional standards. CCBA belongs here because it is a recognized certification for practicing business analysts, focused on validated competency rather than a specific technical tool or method.",
"slug": "d_init_01",
"source": "llm"
},
"dimension_id": null,
"input_skill": "CCBA",
"llm_role": null,
"matched_chosen_role": false,
"role_dimension_saved": false,
"roles_from_db": [],
"skill_dimension_saved": false,
"skill_id": null,
"skill_tag": "new",
"skipped_reason": "skill_not_in_db_v3_proposed"
},
{
"chosen_role_id": 20,
"dimension": {
"difficulty_hint": null,
"display_name": "Spreadsheet Analysis and Modeling",
"id": null,
"rationale": "Using spreadsheets to organize, analyze, and present business data. Excel belongs here because it is the standard tool for tabular analysis, formulas, pivoting, and lightweight reporting in business analysis work.",
"slug": "d_init_01",
"source": "llm"
},
"dimension_id": null,
"input_skill": "Excel",
"llm_role": null,
"matched_chosen_role": false,
"role_dimension_saved": false,
"roles_from_db": [],
"skill_dimension_saved": false,
"skill_id": null,
"skill_tag": "new",
"skipped_reason": "skill_not_in_db_v3_proposed"
},
{
"chosen_role_id": 20,
"dimension": {
"difficulty_hint": null,
"display_name": "Functional Requirements Documentation",
"id": null,
"rationale": "Covers writing and maintaining functional requirements documents that specify what a product or process must do. FRDs belong here because they capture business needs, scope, workflows, and acceptance expectations in a formal requirements artifact.",
"slug": "d_init_01",
"source": "llm"
},
"dimension_id": null,
"input_skill": "FRDs",
"llm_role": null,
"matched_chosen_role": false,
"role_dimension_saved": false,
"roles_from_db": [],
"skill_dimension_saved": false,
"skill_id": null,
"skill_tag": "new",
"skipped_reason": "skill_not_in_db_v3_proposed"
},
{
"chosen_role_id": 20,
"dimension": {
"difficulty_hint": null,
"display_name": "Software Development Lifecycle",
"id": null,
"rationale": "Covers the end-to-end process used to plan, build, test, release, and maintain software products. SDLC belongs here because it refers to the overall delivery lifecycle 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": 20,
"dimension": {
"difficulty_hint": null,
"display_name": "Software as a Service",
"id": null,
"rationale": "Covers cloud-delivered subscription software products and the business/operational concepts around them. SaaS fits here because it refers to a software delivery and commercial model rather than a specific technical implementation skill.",
"slug": "d_init_01",
"source": "llm"
},
"dimension_id": null,
"input_skill": "SaaS",
"llm_role": null,
"matched_chosen_role": false,
"role_dimension_saved": false,
"roles_from_db": [],
"skill_dimension_saved": false,
"skill_id": null,
"skill_tag": "new",
"skipped_reason": "skill_not_in_db_v3_proposed"
},
{
"chosen_role_id": 20,
"dimension": {
"difficulty_hint": null,
"display_name": "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, swimlanes, org charts, and system diagrams 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": 12
},
"planner_output": null,
"run_id": "590a2f20-9b65-4324-8e3e-79ba678de779"
}
LLM Calls
Every model call made for this run, in pipeline order. Click a card to see the model's response.
Loading…