Pipeline run
d0a20afe-dfff-4daf-b1ba-93d574198a9e
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:45:03.832001Z
Updated: 2026-05-08T10:46:55.966688Z
API 3 duration: 906 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
Reporting/dashboard skills map strongly to Data Analyst, and the remaining evidence is broader but still data- and analysis-oriented.
0
New skills
0
Skill↔dim saved
0
Role↔dim saved
14
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 Reporting
d_init_01
|
— | — | — | skill_not_in_db_v3_proposed |
| CBAP | new |
Business Analysis Certification
d_init_01
|
— | — | — | skill_not_in_db_v3_proposed |
| CCBA | new |
Business Analysis Certification
d_init_01
|
— | — | — | skill_not_in_db_v3_proposed |
| Excel | new |
Spreadsheet Analysis and Reporting
d_init_01
|
— | — | — | skill_not_in_db_v3_proposed |
| FRDs | new |
Functional Requirements Documentation
d_init_01
|
— | — | — | skill_not_in_db_v3_proposed |
| QA | new |
Quality Assurance Testing
d_init_01
|
— | — | — | skill_not_in_db_v3_proposed |
| SDLC | new |
Software Delivery Lifecycle
d_init_01
|
— | — | — | skill_not_in_db_v3_proposed |
| SaaS | new |
Software as a Service
d_init_01
|
— | — | — | skill_not_in_db_v3_proposed |
| UAT | new |
User Acceptance Testing
d_init_01
|
— | — | — | skill_not_in_db_v3_proposed |
| Visio | new |
Process Modeling and Diagramming
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_interface nature=PROTOCOL 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 | 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 Reporting | |
| dimension_skill_link_proposed | BI ↔ Business Intelligence Reporting | |
| dimension_proposed | Business Analysis Certification | |
| dimension_skill_link_proposed | CBAP ↔ Business Analysis Certification | |
| dimension_proposed | Business Analysis Certification | |
| dimension_skill_link_proposed | CCBA ↔ Business Analysis Certification | |
| dimension_proposed | Spreadsheet Analysis and Reporting | |
| dimension_skill_link_proposed | Excel ↔ Spreadsheet Analysis and Reporting | |
| dimension_proposed | Functional Requirements Documentation | |
| dimension_skill_link_proposed | FRDs ↔ Functional Requirements Documentation | |
| dimension_proposed | Quality Assurance Testing | |
| dimension_skill_link_proposed | QA ↔ Quality Assurance Testing | |
| dimension_proposed | Software Delivery Lifecycle | |
| dimension_skill_link_proposed | SDLC ↔ Software Delivery Lifecycle | |
| dimension_proposed | Software as a Service | |
| dimension_skill_link_proposed | SaaS ↔ Software as a Service | |
| dimension_proposed | User Acceptance Testing | |
| dimension_skill_link_proposed | UAT ↔ User Acceptance Testing | |
| dimension_proposed | Process Modeling and Diagramming | |
| dimension_skill_link_proposed | Visio ↔ Process Modeling and Diagramming |
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",
"Acceptance",
"Analyst",
"BRDs",
"Bachelor",
"Benefits",
"Business",
"Certification",
"Computer",
"Conduct",
"Description",
"Ensure",
"Experience",
"Exposure",
"Familiarity",
"Gather",
"Health",
"Hybrid",
"Job",
"Key",
"Knowledge",
"Learning",
"Location",
"Monitor",
"Power",
"Preferred",
"Qualifications",
"Remote",
"Required",
"Responsibilities",
"Role",
"Science",
"Skills",
"Support",
"Testing",
"Title",
"Understanding",
"User",
"Years",
"abilities",
"candidate",
"commerce",
"company",
"degree",
"delivery",
"dependencies",
"developers",
"domains",
"environment",
"field",
"gap",
"gathering",
"goals",
"growth",
"insurance",
"leaves",
"management",
"managers",
"meetings",
"methodologies",
"needs",
"opportunities",
"problem",
"process",
"processes",
"product",
"progress",
"project",
"requirement",
"requirements",
"risks",
"salary",
"site",
"solutions",
"stakeholder",
"stakeholders",
"strategies",
"teams",
"tools",
"work"
],
"final_skills": [
"Power BI",
"Tableau",
"Argo Workflows",
"APIs",
"BI",
"CBAP",
"CCBA",
"Excel",
"FRDs",
"QA",
"SDLC",
"SaaS",
"UAT",
"Visio",
"analysis",
"communication",
"data",
"databases",
"development",
"documentation",
"fintech",
"healthcare",
"insights",
"optimization",
"reporting",
"software",
"specifications",
"stories",
"trends",
"workshops"
],
"initial_skills": [
"Power BI",
"Tableau",
"Argo Workflows"
],
"jd_role_hint": {
"display_name": "Business Analyst",
"rationale": "The excerpt centers on requirement gathering, stakeholder collaboration, process analysis, and business documentation typical of a Business Analyst.",
"role_archetype": "Analyzes business needs, gathers requirements, and translates them into functional specifications and process documentation.",
"slug": "business-analyst"
},
"llm_non_skills": [
"2\u20135",
"Ability",
"Acceptance",
"Analyst",
"BRDs",
"Bachelor",
"Benefits",
"Business",
"Certification",
"Computer",
"Conduct",
"Description",
"Ensure",
"Experience",
"Exposure",
"Familiarity",
"Gather",
"Health",
"Hybrid",
"Job",
"Key",
"Knowledge",
"Learning",
"Location",
"Monitor",
"Power",
"Preferred",
"Qualifications",
"Remote",
"Required",
"Responsibilities",
"Role",
"Science",
"Skills",
"Support",
"Testing",
"Title",
"Understanding",
"User",
"Years",
"abilities",
"candidate",
"commerce",
"company",
"degree",
"delivery",
"dependencies",
"developers",
"domains",
"environment",
"field",
"gap",
"gathering",
"goals",
"growth",
"insurance",
"leaves",
"management",
"managers",
"meetings",
"methodologies",
"needs",
"opportunities",
"problem",
"process",
"processes",
"product",
"progress",
"project",
"requirement",
"requirements",
"risks",
"salary",
"site",
"solutions",
"stakeholder",
"stakeholders",
"strategies",
"teams",
"tools",
"work"
],
"llm_skills": [
"APIs",
"BI",
"CBAP",
"CCBA",
"Excel",
"FRDs",
"QA",
"SDLC",
"SaaS",
"UAT",
"Visio",
"analysis",
"communication",
"data",
"databases",
"development",
"documentation",
"fintech",
"healthcare",
"insights",
"optimization",
"reporting",
"software",
"specifications",
"stories",
"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": "Reporting/dashboard skills map strongly to Data Analyst, and the remaining evidence is broader but still data- and analysis-oriented.",
"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 as a way for systems to exchange data and capabilities. This fits APIs because the skill centers on endpoints, contracts, request/response behavior, and integration patterns.",
"slug": "d_init_01",
"source": "llm"
},
"input_skill": "APIs",
"llm_role": null,
"roles_from_db": []
},
{
"dimension": {
"difficulty_hint": null,
"display_name": "Business Intelligence Reporting",
"id": null,
"rationale": "Covers the creation and interpretation of dashboards, reports, KPIs, and ad hoc analysis used to support business decisions. BI belongs here because, in a business analyst context, it usually refers to turning data into actionable reporting and insights.",
"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 professional standards for analysts who elicit requirements, model processes, and support solution delivery. CBAP belongs here because it is a business analysis certification rather than a technical implementation skill.",
"slug": "d_init_01",
"source": "llm"
},
"input_skill": "CBAP",
"llm_role": null,
"roles_from_db": []
},
{
"dimension": {
"difficulty_hint": null,
"display_name": "Business Analysis Certification",
"id": null,
"rationale": "Professional certification credentials for business analysts that validate knowledge of requirements elicitation, stakeholder analysis, and solution assessment. CCBA belongs here as a recognized business analysis certification rather than a technical skill.",
"slug": "d_init_01",
"source": "llm"
},
"input_skill": "CCBA",
"llm_role": null,
"roles_from_db": []
},
{
"dimension": {
"difficulty_hint": null,
"display_name": "Spreadsheet Analysis and Reporting",
"id": null,
"rationale": "Using Excel to organize, analyze, summarize, and present business data. This fits a Business Analyst context because Excel is commonly used for ad hoc analysis, reporting, and lightweight decision support.",
"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 creating and maintaining functional requirements documents that define what a product or feature must do. FRDs belong here because they capture business needs, scope, behaviors, and acceptance-oriented detail for delivery teams.",
"slug": "d_init_01",
"source": "llm"
},
"input_skill": "FRDs",
"llm_role": null,
"roles_from_db": []
},
{
"dimension": {
"difficulty_hint": null,
"display_name": "Quality Assurance Testing",
"id": null,
"rationale": "Validating that a product or process meets requirements through planned test execution and defect verification. QA fits here because, in a business analyst context, it usually means checking expected behavior, acceptance criteria, and release readiness.",
"slug": "d_init_01",
"source": "llm"
},
"input_skill": "QA",
"llm_role": null,
"roles_from_db": []
},
{
"dimension": {
"difficulty_hint": null,
"display_name": "Software Delivery Lifecycle",
"id": null,
"rationale": "Covers the end-to-end process used to plan, build, test, release, and maintain software products. SDLC belongs here because it refers to the lifecycle framework that organizes requirements through deployment and support.",
"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 the product and delivery model where software is delivered over the internet as a subscription service. This skill belongs here because SaaS is the umbrella concept for multi-tenant, continuously delivered business applications.",
"slug": "d_init_01",
"source": "llm"
},
"input_skill": "SaaS",
"llm_role": null,
"roles_from_db": []
},
{
"dimension": {
"difficulty_hint": null,
"display_name": "User Acceptance Testing",
"id": null,
"rationale": "Business-facing validation of a solution against agreed acceptance criteria before release. UAT belongs here because it is the formal check that the delivered process or feature works for end users and is ready for sign-off.",
"slug": "d_init_01",
"source": "llm"
},
"input_skill": "UAT",
"llm_role": null,
"roles_from_db": []
},
{
"dimension": {
"difficulty_hint": null,
"display_name": "Process Modeling and Diagramming",
"id": null,
"rationale": "Covers creating business and systems diagrams to communicate workflows, roles, dependencies, and structure. Visio belongs here because it is commonly used to model processes, map information flow, and document business or technical designs.",
"slug": "d_init_01",
"source": "llm"
},
"input_skill": "Visio",
"llm_role": null,
"roles_from_db": []
}
],
"input_final_skills": [
"Power BI",
"Tableau",
"Argo Workflows",
"APIs",
"BI",
"CBAP",
"CCBA",
"Excel",
"FRDs",
"QA",
"SDLC",
"SaaS",
"UAT",
"Visio",
"analysis",
"communication",
"data",
"databases",
"development",
"documentation",
"fintech",
"healthcare",
"insights",
"optimization",
"reporting",
"software",
"specifications",
"stories",
"trends",
"workshops"
],
"input_llm_skills": [
"APIs",
"BI",
"CBAP",
"CCBA",
"Excel",
"FRDs",
"QA",
"SDLC",
"SaaS",
"UAT",
"Visio",
"analysis",
"communication",
"data",
"databases",
"development",
"documentation",
"fintech",
"healthcare",
"insights",
"optimization",
"reporting",
"software",
"specifications",
"stories",
"trends",
"workshops"
],
"new_aliases_persisted": 0,
"run_id": "d0a20afe-dfff-4daf-b1ba-93d574198a9e",
"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 as a way for systems to exchange data and capabilities. This fits APIs because the skill centers on endpoints, contracts, request/response behavior, and integration patterns.",
"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_interface",
"typical_lifespan": "EVERGREEN",
"version_strategy": "NOT_APPLICABLE",
"volatility": "STABLE"
},
"enrichment": {
"ambiguity": {
"ambiguity_flag": true,
"confused_with": [
"api"
],
"reasoning": "\"APIs\" is a generic plural term and can be used loosely to mean API design/integration work; a JD extractor could confuse it with the singular skill entry \"API\" in the catalog."
},
"context_keywords": {
"context_keywords": [
"REST",
"GraphQL",
"OpenAPI",
"Swagger",
"JSON",
"OAuth 2.0",
"webhooks",
"endpoints",
"rate limiting",
"API gateway",
"microservices",
"SDK",
"versioning",
"authentication",
"HTTP"
]
},
"maturity": {
"confidence": 0.97,
"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 vendor docs from AWS, Google, and Microsoft."
},
"skill_id": "apis",
"vendor_license": {
"confidence": 0.99,
"license": null,
"vendor": null,
"year_introduced": null
},
"versioning": {
"current_version": null,
"version_aliases": {},
"versioned": false
}
},
"keep_log": [],
"locked_dimensions": [
{
"description": "Designing and using application programming interfaces as a way for systems to exchange data and capabilities. This fits APIs because the skill centers on endpoints, contracts, request/response behavior, and integration patterns.",
"exemplar_skills": [
"APIs",
"REST APIs",
"API design",
"endpoint integration",
"webhooks",
"API versioning",
"service contracts"
],
"in_scope": "APIs, REST endpoints, request/response formats, JSON payloads, XML payloads, API versioning, pagination, error handling, webhook integration, API gateways",
"name": "API Design and Integration",
"out_of_scope": "Manual test execution, automated endpoint verification, service decomposition, database design, and UI implementation; those belong to testing or broader service architecture dimensions.",
"overlap_flags": [
{
"reason": "API design is often part of service integration, but this dimension is narrower and centered on the interface itself.",
"with_dim_id": "service-architecture-and-integration",
"with_dim_name": null,
"with_role": "Backend Engineer"
},
{
"reason": "APIs are also tested, but this dimension covers designing and consuming them rather than automating validation.",
"with_dim_id": "api-and-service-test-automation",
"with_dim_name": null,
"with_role": "Automation Tester"
}
],
"tentative_id": "d_init_01"
}
],
"merge_log": [],
"placed": {
"name": "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",
"aws-iam",
"scripted-rest-api",
"outbound-rest-messages",
"mock-servers"
],
"requires": [],
"skill_id": "apis",
"suppress_on_match": []
},
"skill_id": "apis",
"split_log": [],
"typed": {
"alternatives_considered": [],
"confidence": 0.93,
"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_interface",
"type": "Protocol"
},
"warnings": []
},
"source_tag": "llm",
"was_in_llm_skills": true
},
{
"aliases_in_db": [],
"canonical": null,
"dimensions": [
{
"dimension": {
"difficulty_hint": null,
"display_name": "Business Intelligence Reporting",
"id": null,
"rationale": "Covers the creation and interpretation of dashboards, reports, KPIs, and ad hoc analysis used to support business decisions. BI belongs here because, in a business analyst context, it usually refers to turning data into actionable reporting and insights.",
"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 other initials or broader business terms. A reasonable extractor could confuse the shorthand with the full skill entry."
},
"context_keywords": {
"context_keywords": [
"dashboard",
"KPI",
"ETL",
"data warehouse",
"OLAP",
"SQL",
"Tableau",
"Power BI",
"Looker",
"reporting",
"ad hoc analysis",
"dimensional modeling",
"star schema",
"data mart",
"semantic layer"
]
},
"maturity": {
"confidence": 0.88,
"maturity": "well_known",
"reasoning": "BI is a common hiring keyword across analytics and data roles; job boards routinely list Tableau/Power BI/Looker alongside BI, and major vendors continue to invest in the category."
},
"skill_id": "bi",
"vendor_license": {
"confidence": 0.98,
"license": null,
"vendor": null,
"year_introduced": null
},
"versioning": {
"current_version": null,
"version_aliases": {},
"versioned": false
}
},
"keep_log": [],
"locked_dimensions": [
{
"description": "Covers the creation and interpretation of dashboards, reports, KPIs, and ad hoc analysis used to support business decisions. BI belongs here because, in a business analyst context, it usually refers to turning data into actionable reporting and insights.",
"exemplar_skills": [
"BI",
"dashboard design",
"KPI reporting",
"ad hoc reporting",
"business metrics analysis",
"executive scorecards"
],
"in_scope": "BI, dashboards, KPI reporting, ad hoc analysis, executive scorecards, operational reports, self-service analytics, report requirements, business metrics, trend analysis",
"name": "Business Intelligence Reporting",
"out_of_scope": "Data preparation and blending for shaping source data, notebook and reproducible analysis workflow for exploratory coding, data quality assessment for validating dataset fitness",
"overlap_flags": [
{
"reason": "BI reporting often depends on prepared datasets, but this dimension owns the transformation and joining work.",
"with_dim_id": "data-preparation-and-blending",
"with_dim_name": null,
"with_role": "Data Analyst"
},
{
"reason": "Analysts may use notebooks for BI exploration, but the core BI skill is reporting and decision support rather than reproducible coding workflows.",
"with_dim_id": "notebook-and-reproducible-analysis-workflow",
"with_dim_name": null,
"with_role": "Data Scientist"
}
],
"tentative_id": "d_init_01"
}
],
"merge_log": [
{
"a_dim_id": "d_init_02",
"a_name": "Data Preparation and Blending",
"a_role": "__skill_focal__",
"b_dim_id": "data-preparation-and-blending",
"b_name": "Data Preparation and Blending",
"b_role": "Data Analyst",
"into": "d_merge_01",
"into_name": "Data Preparation, Blending, and Light Transformation",
"merged_from": [
"d_init_02",
"data-preparation-and-blending"
],
"pair_kind": "cross_role",
"reasoning": "These are the same conceptual cluster with nearly identical wording and scope. Dim A describes combining source tables/extracts into analysis-ready datasets for BI, including joins, reshaping, aggregation, source-to-report mapping, and light transformation; Dim B says the same thing, emphasizing joins logic, reshaping, and light transformation before analysis and reporting. The exemplar skills in Dim A \u2014 \"data preparation and blending,\" \"joins,\" \"reshaping data,\" and \"aggregation\" \u2014 are exactly the kinds of work Dim B names, and there is no meaningful distinction in scope or level of abstraction. The cross-role label appears to be a naming duplication rather than a role-specific difference.",
"similarity": 0.8621846237012764
}
],
"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.96,
"name": "BI",
"reasoning": "BI is fundamentally a business intelligence problem space and body of knowledge, so it fits the Domain type rather than a tool 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 professional standards for analysts who elicit requirements, model processes, and support solution delivery. CBAP belongs here because it is a business analysis certification rather than a technical implementation skill.",
"slug": "d_init_01",
"source": "llm"
},
"input_skill": "CBAP",
"llm_role": null,
"roles_from_db": []
}
],
"input_skill": "CBAP",
"matched_via": null,
"new_alias_persisted": false,
"new_alias_text": null,
"new_skill_meta": {
"derived": {
"category": "Certification",
"skill_nature": "CREDENTIAL",
"sub_category": "business_analysis_professional_certification",
"typical_lifespan": "EVERGREEN",
"version_strategy": "NOT_APPLICABLE",
"volatility": "STABLE"
},
"enrichment": {
"ambiguity": {
"ambiguity_flag": false,
"confused_with": [],
"reasoning": "CBAP is a specific certification acronym (Certified Business Analysis Professional) and is unlikely to be confused with another catalog skill in typical job descriptions."
},
"context_keywords": {
"context_keywords": [
"BABOK",
"IIBA",
"requirements elicitation",
"stakeholder analysis",
"process modeling",
"use cases",
"user stories",
"gap analysis",
"business process improvement",
"solution assessment",
"traceability matrix",
"workshops",
"SWOT analysis",
"UML",
"BRD"
]
},
"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.95,
"license": null,
"vendor": "International Institute of Business Analysis",
"year_introduced": 2006
},
"versioning": {
"current_version": null,
"version_aliases": {},
"versioned": false
}
},
"keep_log": [],
"locked_dimensions": [
{
"description": "Formal business analysis credentialing and professional standards for analysts who elicit requirements, model processes, and support solution delivery. CBAP belongs here because it is a business analysis certification rather than a technical implementation skill.",
"exemplar_skills": [
"CBAP",
"CCBA",
"ECBA",
"BABOK",
"requirements elicitation",
"stakeholder analysis",
"process modeling"
],
"in_scope": "CBAP, CCBA, ECBA, business analysis certification, BABOK knowledge areas, requirements elicitation, stakeholder analysis, process modeling, solution assessment",
"name": "Business Analysis Certification",
"out_of_scope": "Technical system design, software testing execution, project management certification, product management strategy, these belong to other role-specific dimensions",
"overlap_flags": [
{
"reason": "Business analysts may support acceptance criteria and validation, but CBAP is primarily about analysis practice and certification.",
"with_dim_id": "test-case-design-and-execution",
"with_dim_name": null,
"with_role": "Manual Tester"
}
],
"tentative_id": "d_init_01"
}
],
"merge_log": [],
"placed": {
"name": "CBAP",
"placement_confidence": 0.92,
"primary_dimension": "d_init_01",
"reasoning": "Deterministic JD placement: locked_dimensions has 1 dimension(s) from skill-driven dimension generation after reconciliation; primary_dimension is the first locked dim.",
"secondary_dimensions": [],
"skill_id": "cbap"
},
"relationships": {
"child_skills": [],
"parent_skills": [],
"related_to": [
"risk-based-testing",
"acceptance-criteria-validation",
"acceptance-criteria-checks",
"capacity-planning",
"session-based-testing",
"contract-tests"
],
"requires": [],
"skill_id": "cbap",
"suppress_on_match": []
},
"skill_id": "cbap",
"split_log": [],
"typed": {
"alternatives_considered": [],
"confidence": 0.98,
"name": "CBAP",
"reasoning": "CBAP is a formal third-party credential, so by the Certification rule it is not a concept or methodology.",
"skill_id": "cbap",
"subtype": "business_analysis_professional_certification",
"type": "Certification"
},
"warnings": []
},
"source_tag": "llm",
"was_in_llm_skills": true
},
{
"aliases_in_db": [],
"canonical": null,
"dimensions": [
{
"dimension": {
"difficulty_hint": null,
"display_name": "Business Analysis Certification",
"id": null,
"rationale": "Professional certification credentials for business analysts that validate knowledge of requirements elicitation, stakeholder analysis, and solution assessment. CCBA belongs here as a recognized business analysis certification rather than a technical skill.",
"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",
"gap analysis",
"use cases",
"user stories",
"business process improvement",
"solution assessment",
"traceability matrix",
"SWOT analysis",
"UML",
"workshops",
"facilitation"
]
},
"maturity": {
"confidence": 0.84,
"maturity": "well_known",
"reasoning": "CCBA is a widely recognized business analysis certification; it appears in many job descriptions for BA roles and is offered by IIBA as a mainstream credential alongside CBAP."
},
"skill_id": "ccba",
"vendor_license": {
"confidence": 0.92,
"license": null,
"vendor": "International Institute of Business Analysis",
"year_introduced": 2008
},
"versioning": {
"current_version": null,
"version_aliases": {},
"versioned": false
}
},
"keep_log": [],
"locked_dimensions": [
{
"description": "Professional certification credentials for business analysts that validate knowledge of requirements elicitation, stakeholder analysis, and solution assessment. CCBA belongs here as a recognized business analysis certification rather than a technical skill.",
"exemplar_skills": [
"CCBA",
"CBAP",
"ECBA",
"business analysis certification",
"requirements elicitation",
"stakeholder analysis"
],
"in_scope": "CCBA, CBAP, ECBA, business analysis certification, requirements elicitation, stakeholder analysis, solution assessment, business analysis body of knowledge",
"name": "Business Analysis Certification",
"out_of_scope": "business process modeling notation, SQL querying, user story writing, project scheduling, product management strategy",
"overlap_flags": [],
"tentative_id": "d_init_01"
}
],
"merge_log": [],
"placed": {
"name": "CCBA",
"placement_confidence": 0.92,
"primary_dimension": "d_init_01",
"reasoning": "Deterministic JD placement: locked_dimensions has 1 dimension(s) from skill-driven dimension generation after reconciliation; primary_dimension is the first locked dim.",
"secondary_dimensions": [],
"skill_id": "ccba"
},
"relationships": {
"child_skills": [],
"parent_skills": [],
"related_to": [
"scorecards",
"acceptance-criteria-checks",
"acceptance-criteria-validation",
"risk-based-testing",
"charter-based-testing",
"session-based-testing"
],
"requires": [],
"skill_id": "ccba",
"suppress_on_match": []
},
"skill_id": "ccba",
"split_log": [],
"typed": {
"alternatives_considered": [],
"confidence": 0.98,
"name": "CCBA",
"reasoning": "CCBA is a formal third-party credential, so by the Certification rule it is 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 Reporting",
"id": null,
"rationale": "Using Excel to organize, analyze, summarize, and present business data. This fits a Business Analyst context because Excel is commonly used for ad hoc analysis, reporting, and lightweight decision support.",
"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",
"macros",
"VBA",
"Power Query",
"Power Pivot",
"data validation",
"conditional formatting",
"SUMIFS",
"charts",
"dashboards",
"CSV",
"workbooks"
]
},
"maturity": {
"confidence": 0.99,
"maturity": "well_known",
"reasoning": "Excel appears in a very large share of business, finance, ops, and analyst job descriptions; Microsoft continues active development and support, with no announced sunset or replacement."
},
"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 2003": "Excel 2003",
"Excel 2007": "Excel 2007",
"Excel 2010": "Excel 2010",
"Excel 2013": "Excel 2013",
"Excel 2016": "Excel 2016",
"Excel 2019": "Excel 2019",
"Excel 2021": "Excel 2021",
"Excel 2024": "Microsoft 365 / Excel 2024",
"Excel 365": "Microsoft 365 / Excel 2024",
"Microsoft 365 Excel": "Microsoft 365 / Excel 2024"
},
"versioned": true
}
},
"keep_log": [],
"locked_dimensions": [
{
"description": "Using Excel to organize, analyze, summarize, and present business data. This fits a Business Analyst context because Excel is commonly used for ad hoc analysis, reporting, and lightweight decision support.",
"exemplar_skills": [
"Excel",
"Pivot Tables",
"VLOOKUP",
"XLOOKUP",
"Conditional Formatting",
"Charts",
"Formulas",
"Data Validation"
],
"in_scope": "Excel, formulas, functions, pivot tables, charts, filters, conditional formatting, data validation, lookup functions, basic dashboards, ad hoc reporting, workbook organization",
"name": "Spreadsheet Analysis and Reporting",
"out_of_scope": "SQL querying and database modeling, statistical programming in Python or R, enterprise BI semantic modeling, data engineering pipelines",
"overlap_flags": [
{
"reason": "Excel often supports light data shaping and combining sources, but that dimension owns multi-source transformation workflows.",
"with_dim_id": "data-preparation-and-blending",
"with_dim_name": null,
"with_role": "Data Analyst"
},
{
"reason": "Excel can be used for analysis, but notebooks own scripted, reproducible analytical workflows.",
"with_dim_id": "notebook-and-reproducible-analysis-workflow",
"with_dim_name": null,
"with_role": "Data Scientist"
}
],
"tentative_id": "d_init_01"
}
],
"merge_log": [],
"placed": {
"name": "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",
"scorecards",
"summary-statistics",
"outlier-detection"
],
"requires": [],
"skill_id": "excel",
"suppress_on_match": []
},
"skill_id": "excel",
"split_log": [],
"typed": {
"alternatives_considered": [],
"confidence": 0.98,
"name": "Excel",
"reasoning": "Excel is software you operate directly as a user, so by the Tool vs Framework rule it is a Tool rather than a library or framework.",
"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 creating and maintaining functional requirements documents that define what a product or feature must do. FRDs belong here because they capture business needs, scope, behaviors, and acceptance-oriented detail for delivery teams.",
"slug": "d_init_01",
"source": "llm"
},
"input_skill": "FRDs",
"llm_role": null,
"roles_from_db": []
}
],
"input_skill": "FRDs",
"matched_via": null,
"new_alias_persisted": false,
"new_alias_text": null,
"new_skill_meta": {
"derived": {
"category": "Domain",
"skill_nature": "CONCEPT",
"sub_category": "functional_requirements_documents",
"typical_lifespan": "EVERGREEN",
"version_strategy": "NOT_APPLICABLE",
"volatility": "STABLE"
},
"enrichment": {
"ambiguity": {
"ambiguity_flag": false,
"confused_with": [],
"reasoning": "FRDs is a fairly specific plural abbreviation for functional requirements documents; in JDs it is unlikely to be mistaken for another catalog skill."
},
"context_keywords": {
"context_keywords": [
"BRD",
"PRD",
"use cases",
"user stories",
"acceptance criteria",
"functional specification",
"requirements traceability",
"stakeholder interviews",
"process flows",
"wireframes",
"UAT",
"business rules",
"scope definition",
"gap analysis",
"sign-off"
]
},
"maturity": {
"confidence": 0.78,
"maturity": "well_known",
"reasoning": "Functional requirements documents are a standard artifact in many product and systems JDs; market demand is broad even as formats vary by org."
},
"skill_id": "frds",
"vendor_license": {
"confidence": 0.98,
"license": null,
"vendor": null,
"year_introduced": null
},
"versioning": {
"current_version": null,
"version_aliases": {},
"versioned": false
}
},
"keep_log": [],
"locked_dimensions": [
{
"description": "Covers creating and maintaining functional requirements documents that define what a product or feature must do. FRDs belong here because they capture business needs, scope, behaviors, and acceptance-oriented detail for delivery teams.",
"exemplar_skills": [
"FRDs",
"functional requirements documentation",
"business requirements analysis",
"requirements elicitation",
"scope definition",
"acceptance criteria writing"
],
"in_scope": "FRDs, functional requirements documents, business requirements translation, feature scope definition, user stories, acceptance criteria, process flows, requirement traceability",
"name": "Functional Requirements Documentation",
"out_of_scope": "technical architecture design, API implementation details, test automation, UX visual design, project scheduling",
"overlap_flags": [
{
"reason": "Functional requirements often inform service boundaries and integrations, but this dimension owns the technical system design.",
"with_dim_id": "service-architecture-and-integration",
"with_dim_name": null,
"with_role": "Backend Engineer"
},
{
"reason": "FRDs may feed test cases and acceptance checks, but test design is a separate validation discipline.",
"with_dim_id": "test-case-design-and-execution",
"with_dim_name": null,
"with_role": "Manual Tester"
}
],
"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",
"runbooks"
],
"requires": [],
"skill_id": "frds",
"suppress_on_match": []
},
"skill_id": "frds",
"split_log": [],
"typed": {
"alternatives_considered": [
"Concept: ruled out \u2014 it is not a single theoretical principle but a document-oriented knowledge area.",
"Methodology: ruled out \u2014 it does not describe a way of working or process.",
"Format: ruled out \u2014 although documents have structure, FRDs refers to the document type/knowledge area rather than a wire or data format."
],
"confidence": 0.78,
"name": "FRDs",
"reasoning": "FRDs is best treated as a Domain because it names a body of requirements-document knowledge rather than a software artifact, and the Tool/Framework/Format rules do not apply.",
"skill_id": "frds",
"subtype": "functional_requirements_documents",
"type": "Domain"
},
"warnings": []
},
"source_tag": "llm",
"was_in_llm_skills": true
},
{
"aliases_in_db": [],
"canonical": null,
"dimensions": [
{
"dimension": {
"difficulty_hint": null,
"display_name": "Quality Assurance Testing",
"id": null,
"rationale": "Validating that a product or process meets requirements through planned test execution and defect verification. QA fits here because, in a business analyst context, it usually means checking expected behavior, acceptance criteria, and release readiness.",
"slug": "d_init_01",
"source": "llm"
},
"input_skill": "QA",
"llm_role": null,
"roles_from_db": []
}
],
"input_skill": "QA",
"matched_via": null,
"new_alias_persisted": false,
"new_alias_text": null,
"new_skill_meta": {
"derived": {
"category": "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 be used generically for testing roles. A catalog extractor could confuse this with the broader quality_assurance skill."
},
"context_keywords": {
"context_keywords": [
"test cases",
"test plans",
"test scripts",
"regression testing",
"UAT",
"bug tracking",
"defect triage",
"test automation",
"manual testing",
"acceptance criteria",
"traceability matrix",
"JIRA",
"Selenium",
"smoke testing",
"sanity testing"
]
},
"maturity": {
"confidence": 0.93,
"maturity": "well_known",
"reasoning": "QA is a standard hiring requirement across software JDs, with widespread listings for QA engineer/test analyst roles and strong demand for test automation in major job boards."
},
"skill_id": "qa",
"vendor_license": {
"confidence": 0.99,
"license": null,
"vendor": null,
"year_introduced": null
},
"versioning": {
"current_version": null,
"version_aliases": {},
"versioned": false
}
},
"keep_log": [],
"locked_dimensions": [
{
"description": "Validating that a product or process meets requirements through planned test execution and defect verification. QA fits here because, in a business analyst context, it usually means checking expected behavior, acceptance criteria, and release readiness.",
"exemplar_skills": [
"QA",
"manual testing",
"test case design",
"test execution",
"regression testing",
"user acceptance testing"
],
"in_scope": "QA, manual testing, test case design, test execution, regression testing, exploratory testing, defect logging, UAT support, acceptance criteria validation",
"name": "Quality Assurance Testing",
"out_of_scope": "Automated API test frameworks, unit testing frameworks, performance/load testing, security testing, data quality assessment",
"overlap_flags": [
{
"reason": "This is the closest existing catalog concept; if the catalog is expanded, QA may be normalized into that more specific testing dimension.",
"with_dim_id": "test-case-design-and-execution",
"with_dim_name": null,
"with_role": "Manual Tester"
},
{
"reason": "QA can include backend verification, but automated API and service contract testing is a distinct engineering dimension.",
"with_dim_id": "api-and-service-test-automation",
"with_dim_name": null,
"with_role": "Automation Tester"
},
{
"reason": "QA sometimes includes checking data outputs, but dataset fitness and bias evaluation belong to data quality assessment.",
"with_dim_id": "data-quality-assessment",
"with_dim_name": null,
"with_role": "Data Analyst, Data Scientist"
}
],
"tentative_id": "d_init_01"
}
],
"merge_log": [],
"placed": {
"name": "QA",
"placement_confidence": 0.92,
"primary_dimension": "d_init_01",
"reasoning": "Deterministic JD placement: locked_dimensions has 1 dimension(s) from skill-driven dimension generation after reconciliation; primary_dimension is the first locked dim.",
"secondary_dimensions": [],
"skill_id": "qa"
},
"relationships": {
"child_skills": [],
"parent_skills": [],
"related_to": [
"acceptance-criteria-checks",
"acceptance-criteria-validation",
"test-case-authoring",
"defect-retest",
"risk-based-testing",
"cross-browser-testing",
"session-based-testing",
"charter-based-testing"
],
"requires": [],
"skill_id": "qa",
"suppress_on_match": []
},
"skill_id": "qa",
"split_log": [],
"typed": {
"alternatives_considered": [
"Methodology: ruled out \u2014 QA is broader than a specific process like TDD or Scrum and is often used as an umbrella practice rather than a named methodology.",
"Concept: ruled out \u2014 QA is not primarily a theory or principle to know, but an operational discipline."
],
"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 more than a knowledge unit.",
"skill_id": "qa",
"subtype": "quality_assurance",
"type": "SoftSkill"
},
"warnings": []
},
"source_tag": "llm",
"was_in_llm_skills": true
},
{
"aliases_in_db": [],
"canonical": null,
"dimensions": [
{
"dimension": {
"difficulty_hint": null,
"display_name": "Software Delivery Lifecycle",
"id": null,
"rationale": "Covers the end-to-end process used to plan, build, test, release, and maintain software products. SDLC belongs here because it refers to the lifecycle framework that organizes requirements through deployment and support.",
"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-scoped acronym for software development lifecycle in JDs; it is unlikely to be reasonably confused with a different catalog skill."
},
"context_keywords": {
"context_keywords": [
"requirements gathering",
"design review",
"implementation",
"code review",
"testing",
"QA",
"UAT",
"deployment",
"release management",
"CI/CD",
"Agile",
"Scrum",
"waterfall",
"change management",
"version control"
]
},
"maturity": {
"confidence": 0.96,
"maturity": "well_known",
"reasoning": "SDLC is a standard term in software job descriptions and engineering interviews, with widespread use across Agile, Waterfall, and DevOps process docs; it is not a sunset technology."
},
"skill_id": "sdlc",
"vendor_license": {
"confidence": 0.99,
"license": null,
"vendor": null,
"year_introduced": null
},
"versioning": {
"current_version": null,
"version_aliases": {},
"versioned": false
}
},
"keep_log": [],
"locked_dimensions": [
{
"description": "Covers the end-to-end process used to plan, build, test, release, and maintain software products. SDLC belongs here because it refers to the lifecycle framework that organizes requirements through deployment and support.",
"exemplar_skills": [
"SDLC",
"software development lifecycle",
"requirements analysis",
"release management",
"change control",
"software delivery process"
],
"in_scope": "SDLC, requirements gathering, analysis, design, development, testing, release management, deployment, maintenance, change control, documentation, software delivery process",
"name": "Software Delivery Lifecycle",
"out_of_scope": "Specific test case authoring and execution, API automation, environment provisioning, or platform administration, which belong to dedicated testing, environment, or operations dimensions.",
"overlap_flags": [
{
"reason": "SDLC includes testing as a phase, but that dimension owns the hands-on design and execution of test cases.",
"with_dim_id": "test-case-design-and-execution",
"with_dim_name": null,
"with_role": "Manual Tester"
},
{
"reason": "SDLC often references promotion across environments, but that dimension owns the actual environment lifecycle work.",
"with_dim_id": "environment-provisioning-and-promotion",
"with_dim_name": null,
"with_role": "DevOps Engineer"
},
{
"reason": "SDLC can include design activities, but architecture and integration are a separate technical specialization.",
"with_dim_id": "service-architecture-and-integration",
"with_dim_name": null,
"with_role": "Backend Engineer"
}
],
"tentative_id": "d_init_01"
}
],
"merge_log": [],
"placed": {
"name": "SDLC",
"placement_confidence": 0.92,
"primary_dimension": "d_init_01",
"reasoning": "Deterministic JD placement: locked_dimensions has 1 dimension(s) from skill-driven dimension generation after reconciliation; primary_dimension is the first locked dim.",
"secondary_dimensions": [],
"skill_id": "sdlc"
},
"relationships": {
"child_skills": [],
"parent_skills": [],
"related_to": [
"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 a process model rather than a standalone knowledge unit.",
"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 the product and delivery model where software is delivered over the internet as a subscription service. This skill belongs here because SaaS is the umbrella concept for multi-tenant, continuously delivered business applications.",
"slug": "d_init_01",
"source": "llm"
},
"input_skill": "SaaS",
"llm_role": null,
"roles_from_db": []
}
],
"input_skill": "SaaS",
"matched_via": null,
"new_alias_persisted": false,
"new_alias_text": null,
"new_skill_meta": {
"derived": {
"category": "Platform",
"skill_nature": "PLATFORM",
"sub_category": "software_as_a_service_platform",
"typical_lifespan": "EVERGREEN",
"version_strategy": "NOT_APPLICABLE",
"volatility": "STABLE"
},
"enrichment": {
"ambiguity": {
"ambiguity_flag": false,
"confused_with": [],
"reasoning": "SaaS is a standard, well-scoped term for software-as-a-service platforms in JDs; it is unlikely to be mistaken for a different catalog skill."
},
"context_keywords": {
"context_keywords": [
"multi-tenant",
"subscription billing",
"tenant isolation",
"self-service onboarding",
"usage-based pricing",
"provisioning",
"SAML",
"SSO",
"RBAC",
"API integrations",
"webhooks",
"admin console",
"trial conversion",
"churn",
"customer lifecycle"
]
},
"maturity": {
"confidence": 0.96,
"maturity": "well_known",
"reasoning": "SaaS is a standard cloud delivery model; job postings routinely ask for SaaS product, implementation, and admin experience across sales, support, and engineering roles."
},
"skill_id": "saas",
"vendor_license": {
"confidence": 0.88,
"license": null,
"vendor": null,
"year_introduced": 1999
},
"versioning": {
"current_version": null,
"version_aliases": {},
"versioned": false
}
},
"keep_log": [],
"locked_dimensions": [
{
"description": "Covers the product and delivery model where software is delivered over the internet as a subscription service. This skill belongs here because SaaS is the umbrella concept for multi-tenant, continuously delivered business applications.",
"exemplar_skills": [
"SaaS",
"multi-tenant architecture",
"subscription software",
"web-based software delivery",
"software subscription model"
],
"in_scope": "SaaS, subscription software, multi-tenant application delivery, web-hosted business applications, recurring billing models, customer-managed access to hosted software",
"name": "Software as a Service",
"out_of_scope": "On-premises packaged software, infrastructure hosting mechanics, cloud security controls, product analytics implementation, these belong to other dimensions",
"overlap_flags": [
{
"reason": "SaaS products are often implemented as services, but this dimension is about the delivery model rather than service decomposition or integration patterns.",
"with_dim_id": "service-architecture-and-integration",
"with_dim_name": null,
"with_role": "Backend Engineer"
},
{
"reason": "SaaS operations may involve environment management, but that dimension focuses on delivery environments rather than the SaaS business/application model.",
"with_dim_id": "environment-provisioning-and-promotion",
"with_dim_name": null,
"with_role": "DevOps Engineer"
}
],
"tentative_id": "d_init_01"
}
],
"merge_log": [],
"placed": {
"name": "SaaS",
"placement_confidence": 0.92,
"primary_dimension": "d_init_01",
"reasoning": "Deterministic JD placement: locked_dimensions has 1 dimension(s) from skill-driven dimension generation after reconciliation; primary_dimension is the first locked dim.",
"secondary_dimensions": [],
"skill_id": "saas"
},
"relationships": {
"child_skills": [],
"parent_skills": [],
"related_to": [
"cloud-run",
"azure-backup",
"cspm",
"policy-as-code",
"cloud-reference-architecture"
],
"requires": [],
"skill_id": "saas",
"suppress_on_match": []
},
"skill_id": "saas",
"split_log": [],
"typed": {
"alternatives_considered": [],
"confidence": 0.93,
"name": "SaaS",
"reasoning": "By the Platform vs Tool rule, SaaS is a hosted multi-tenant environment delivered over APIs and managed services 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": [
{
"dimension": {
"difficulty_hint": null,
"display_name": "User Acceptance Testing",
"id": null,
"rationale": "Business-facing validation of a solution against agreed acceptance criteria before release. UAT belongs here because it is the formal check that the delivered process or feature works for end users and is ready for sign-off.",
"slug": "d_init_01",
"source": "llm"
},
"input_skill": "UAT",
"llm_role": null,
"roles_from_db": []
}
],
"input_skill": "UAT",
"matched_via": null,
"new_alias_persisted": false,
"new_alias_text": null,
"new_skill_meta": {
"derived": {
"category": "Methodology",
"skill_nature": "METHODOLOGY",
"sub_category": "user_acceptance_testing",
"typical_lifespan": "EVERGREEN",
"version_strategy": "NOT_APPLICABLE",
"volatility": "STABLE"
},
"enrichment": {
"ambiguity": {
"ambiguity_flag": false,
"confused_with": [],
"reasoning": "UAT in JDs almost always means User Acceptance Testing; the acronym is standard and unlikely to be mistaken for another catalog skill in typical hiring context."
},
"context_keywords": {
"context_keywords": [
"test cases",
"acceptance criteria",
"test scripts",
"business users",
"end users",
"sign-off",
"defect triage",
"test scenarios",
"test plan",
"go-live",
"stakeholder review",
"regression testing",
"test environment",
"requirements validation",
"smoke testing"
]
},
"maturity": {
"confidence": 0.88,
"maturity": "well_known",
"reasoning": "UAT is a standard QA phase in many software JDs and delivery pipelines; market listings commonly mention user acceptance testing alongside QA/UAT sign-off for release readiness."
},
"skill_id": "uat",
"vendor_license": {
"confidence": 0.99,
"license": null,
"vendor": null,
"year_introduced": null
},
"versioning": {
"current_version": null,
"version_aliases": {},
"versioned": false
}
},
"keep_log": [],
"locked_dimensions": [
{
"description": "Business-facing validation of a solution against agreed acceptance criteria before release. UAT belongs here because it is the formal check that the delivered process or feature works for end users and is ready for sign-off.",
"exemplar_skills": [
"UAT",
"user acceptance testing",
"acceptance criteria validation",
"business scenario testing",
"stakeholder sign-off",
"manual end-to-end validation"
],
"in_scope": "UAT, user acceptance testing, acceptance criteria validation, business scenario testing, stakeholder sign-off, manual end-to-end validation, defect capture during acceptance testing",
"name": "User Acceptance Testing",
"out_of_scope": "Automated unit testing, API regression automation, performance/load testing, production monitoring, requirements gathering, project planning, technical code review",
"overlap_flags": [
{
"reason": "UAT uses test-case execution techniques, but this dimension is broader and owns general manual test design and execution.",
"with_dim_id": "test-case-design-and-execution",
"with_dim_name": null,
"with_role": "Manual Tester"
}
],
"tentative_id": "d_init_01"
}
],
"merge_log": [],
"placed": {
"name": "UAT",
"placement_confidence": 0.92,
"primary_dimension": "d_init_01",
"reasoning": "Deterministic JD placement: locked_dimensions has 1 dimension(s) from skill-driven dimension generation after reconciliation; primary_dimension is the first locked dim.",
"secondary_dimensions": [],
"skill_id": "uat"
},
"relationships": {
"child_skills": [],
"parent_skills": [],
"related_to": [
"acceptance-criteria-checks",
"session-based-testing",
"test-case-authoring"
],
"requires": [],
"skill_id": "uat",
"suppress_on_match": []
},
"skill_id": "uat",
"split_log": [],
"typed": {
"alternatives_considered": [],
"confidence": 0.91,
"name": "UAT",
"reasoning": "UAT is a way of working in which users validate the system 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": []
},
"source_tag": "llm",
"was_in_llm_skills": true
},
{
"aliases_in_db": [],
"canonical": null,
"dimensions": [
{
"dimension": {
"difficulty_hint": null,
"display_name": "Process Modeling and Diagramming",
"id": null,
"rationale": "Covers creating business and systems diagrams to communicate workflows, roles, dependencies, and structure. Visio belongs here because it is commonly used to model processes, map information flow, and document business or technical designs.",
"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": [
"process flow",
"swimlane",
"BPMN",
"UML",
"network diagram",
"org chart",
"floor plan",
"workflow",
"data flow",
"ERD",
"cross-functional",
"stencil",
"shapes",
"blueprint",
"SIPOC"
]
},
"maturity": {
"confidence": 0.86,
"maturity": "well_known",
"reasoning": "Common in enterprise JDs for process/network diagrams and Microsoft 365 stacks; no vendor sunset, and it remains a standard diagramming tool alongside Lucidchart/draw.io."
},
"skill_id": "visio",
"vendor_license": {
"confidence": 0.99,
"license": "proprietary",
"vendor": "Microsoft",
"year_introduced": 1992
},
"versioning": {
"current_version": null,
"version_aliases": {},
"versioned": false
}
},
"keep_log": [],
"locked_dimensions": [
{
"description": "Covers creating business and systems diagrams to communicate workflows, roles, dependencies, and structure. Visio belongs here because it is commonly used to model processes, map information flow, and document business or technical designs.",
"exemplar_skills": [
"Visio",
"flowcharting",
"swimlane diagramming",
"BPMN modeling",
"process mapping",
"UML diagramming"
],
"in_scope": "Visio, process maps, flowcharts, swimlane diagrams, BPMN diagrams, org charts, network diagrams, UML sketches, system context diagrams",
"name": "Process Modeling and Diagramming",
"out_of_scope": "Requirements elicitation, business analysis documentation, project planning, spreadsheet-based analysis, presentation design, these belong to other business analysis or documentation dimensions",
"overlap_flags": [
{
"reason": "Some Visio diagrams may depict service interactions or integration flows, which can overlap with architecture documentation.",
"with_dim_id": "service-architecture-and-integration",
"with_dim_name": null,
"with_role": "Backend Engineer"
},
{
"reason": "Visio is sometimes used to document current-state and target-state migration diagrams, which can overlap with planning artifacts.",
"with_dim_id": "migration-and-modernization-planning",
"with_dim_name": null,
"with_role": "Cloud Architect"
}
],
"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": [],
"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": "development",
"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": "optimization",
"matched_via": null,
"new_alias_persisted": false,
"new_alias_text": null,
"new_skill_meta": null,
"source_tag": "llm",
"was_in_llm_skills": true
},
{
"aliases_in_db": [],
"canonical": null,
"dimensions": [],
"input_skill": "reporting",
"matched_via": null,
"new_alias_persisted": false,
"new_alias_text": null,
"new_skill_meta": null,
"source_tag": "llm",
"was_in_llm_skills": true
},
{
"aliases_in_db": [],
"canonical": null,
"dimensions": [],
"input_skill": "software",
"matched_via": null,
"new_alias_persisted": false,
"new_alias_text": null,
"new_skill_meta": null,
"source_tag": "llm",
"was_in_llm_skills": true
},
{
"aliases_in_db": [],
"canonical": null,
"dimensions": [],
"input_skill": "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": "stories",
"matched_via": null,
"new_alias_persisted": false,
"new_alias_text": null,
"new_skill_meta": null,
"source_tag": "llm",
"was_in_llm_skills": true
},
{
"aliases_in_db": [],
"canonical": null,
"dimensions": [],
"input_skill": "trends",
"matched_via": null,
"new_alias_persisted": false,
"new_alias_text": null,
"new_skill_meta": null,
"source_tag": "llm",
"was_in_llm_skills": true
},
{
"aliases_in_db": [],
"canonical": null,
"dimensions": [],
"input_skill": "workshops",
"matched_via": null,
"new_alias_persisted": false,
"new_alias_text": null,
"new_skill_meta": null,
"source_tag": "llm",
"was_in_llm_skills": true
}
],
"unmatched_skills": [
"APIs",
"BI",
"CBAP",
"CCBA",
"Excel",
"FRDs",
"QA",
"SDLC",
"SaaS",
"UAT",
"Visio"
]
}
API 3 — final-role-output
{
"chosen_role": {
"display_name": "Data Analyst",
"id": 20,
"rationale": "Reporting/dashboard skills map strongly to Data Analyst, and the remaining evidence is broader but still data- and analysis-oriented.",
"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": "BI",
"tag": "new"
},
{
"skill": "CBAP",
"tag": "new"
},
{
"skill": "CCBA",
"tag": "new"
},
{
"skill": "Excel",
"tag": "new"
},
{
"skill": "FRDs",
"tag": "new"
},
{
"skill": "QA",
"tag": "new"
},
{
"skill": "SDLC",
"tag": "new"
},
{
"skill": "SaaS",
"tag": "new"
},
{
"skill": "UAT",
"tag": "new"
},
{
"skill": "Visio",
"tag": "new"
},
{
"skill": "analysis",
"tag": "new"
},
{
"skill": "communication",
"tag": "new"
},
{
"skill": "data",
"tag": "new"
},
{
"skill": "databases",
"tag": "new"
},
{
"skill": "development",
"tag": "new"
},
{
"skill": "documentation",
"tag": "new"
},
{
"skill": "fintech",
"tag": "new"
},
{
"skill": "healthcare",
"tag": "new"
},
{
"skill": "insights",
"tag": "new"
},
{
"skill": "optimization",
"tag": "new"
},
{
"skill": "reporting",
"tag": "new"
},
{
"skill": "software",
"tag": "new"
},
{
"skill": "specifications",
"tag": "new"
},
{
"skill": "stories",
"tag": "new"
},
{
"skill": "trends",
"tag": "new"
},
{
"skill": "workshops",
"tag": "new"
}
],
"persistence": {
"items": [
{
"chosen_role_id": 20,
"dimension": {
"difficulty_hint": "well_known",
"display_name": "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 as a way for systems to exchange data and capabilities. This fits APIs because the skill centers on endpoints, contracts, request/response behavior, and integration patterns.",
"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 Reporting",
"id": null,
"rationale": "Covers the creation and interpretation of dashboards, reports, KPIs, and ad hoc analysis used to support business decisions. BI belongs here because, in a business analyst context, it usually refers to turning data into actionable reporting and insights.",
"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 professional standards for analysts who elicit requirements, model processes, and support solution delivery. CBAP belongs here because it is a business analysis certification rather than a technical implementation skill.",
"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": "Professional certification credentials for business analysts that validate knowledge of requirements elicitation, stakeholder analysis, and solution assessment. CCBA belongs here as a recognized business analysis certification rather than a technical skill.",
"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 Reporting",
"id": null,
"rationale": "Using Excel to organize, analyze, summarize, and present business data. This fits a Business Analyst context because Excel is commonly used for ad hoc analysis, reporting, and lightweight decision support.",
"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 creating and maintaining functional requirements documents that define what a product or feature must do. FRDs belong here because they capture business needs, scope, behaviors, and acceptance-oriented detail for delivery teams.",
"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": "Quality Assurance Testing",
"id": null,
"rationale": "Validating that a product or process meets requirements through planned test execution and defect verification. QA fits here because, in a business analyst context, it usually means checking expected behavior, acceptance criteria, and release readiness.",
"slug": "d_init_01",
"source": "llm"
},
"dimension_id": null,
"input_skill": "QA",
"llm_role": null,
"matched_chosen_role": false,
"role_dimension_saved": false,
"roles_from_db": [],
"skill_dimension_saved": false,
"skill_id": null,
"skill_tag": "new",
"skipped_reason": "skill_not_in_db_v3_proposed"
},
{
"chosen_role_id": 20,
"dimension": {
"difficulty_hint": null,
"display_name": "Software Delivery Lifecycle",
"id": null,
"rationale": "Covers the end-to-end process used to plan, build, test, release, and maintain software products. SDLC belongs here because it refers to the lifecycle framework that organizes requirements through deployment and support.",
"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 the product and delivery model where software is delivered over the internet as a subscription service. This skill belongs here because SaaS is the umbrella concept for multi-tenant, continuously delivered business applications.",
"slug": "d_init_01",
"source": "llm"
},
"dimension_id": null,
"input_skill": "SaaS",
"llm_role": null,
"matched_chosen_role": false,
"role_dimension_saved": false,
"roles_from_db": [],
"skill_dimension_saved": false,
"skill_id": null,
"skill_tag": "new",
"skipped_reason": "skill_not_in_db_v3_proposed"
},
{
"chosen_role_id": 20,
"dimension": {
"difficulty_hint": null,
"display_name": "User Acceptance Testing",
"id": null,
"rationale": "Business-facing validation of a solution against agreed acceptance criteria before release. UAT belongs here because it is the formal check that the delivered process or feature works for end users and is ready for sign-off.",
"slug": "d_init_01",
"source": "llm"
},
"dimension_id": null,
"input_skill": "UAT",
"llm_role": null,
"matched_chosen_role": false,
"role_dimension_saved": false,
"roles_from_db": [],
"skill_dimension_saved": false,
"skill_id": null,
"skill_tag": "new",
"skipped_reason": "skill_not_in_db_v3_proposed"
},
{
"chosen_role_id": 20,
"dimension": {
"difficulty_hint": null,
"display_name": "Process Modeling and Diagramming",
"id": null,
"rationale": "Covers creating business and systems diagrams to communicate workflows, roles, dependencies, and structure. Visio belongs here because it is commonly used to model processes, map information flow, and document business or technical designs.",
"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": 14
},
"planner_output": null,
"run_id": "d0a20afe-dfff-4daf-b1ba-93d574198a9e"
}
LLM Calls
Every model call made for this run, in pipeline order. Click a card to see the model's response.
Loading…