Pipeline run
eb02168f-026f-4c93-8b0c-84ebc7c90426
Client output enrichment
v2 Skill cluster · Nature of work · AI index · Tech stack maturity · Evidence · KRA descriptionNature of work
—
Tech stack maturity
Mainstream Modern
AI index (0 = no AI use, 5 = totally AI-dependent · v2.1)
0.00 / 5
· Title match
· Has AI skill
· AI skill (primary)
· AI skill (secondary)
· On AI team
· Builds AI products
vocab breakdown (legacy)
Assistants (×1):
—
Frameworks (×2):
—
Models / concepts (×3):
—
Evidence — skills matched in JD (0)
Skill cluster (0 dimension groups, role-scoped)
Status:
completed
Created: 2026-05-08T07:22:25.667549Z
Updated: 2026-05-08T07:24:17.039648Z
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
Business Analyst
slug: business-analyst · id: — · source: llm
The strongest signal is the API/BRD/FRD/UAT/SDLC-heavy business analysis dimension, with supporting dashboard/reporting work and only a minor data engineering signal.
0
New skills
0
Skill↔dim saved
0
Role↔dim saved
17
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 |
|---|---|---|---|---|---|---|
| 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) |
| Power BI | in_db |
Reporting and Dashboard Development
reporting-and-dashboard-development
|
— | — | — | TODO: REMOVE AFTER TESTING — api3_writes_enabled=False (writes disabled) |
| APIs | new |
API Design and Integration
d_init_01
|
— | — | — | skill_not_in_db_v3_proposed |
| BI | new |
Business Intelligence
d_init_01
|
— | — | — | skill_not_in_db_v3_proposed |
| BRDs | new |
Business Requirements Documentation
d_init_01
|
— | — | — | skill_not_in_db_v3_proposed |
| CBAP | new |
Business Analysis Certification
d_init_01
|
— | — | — | skill_not_in_db_v3_proposed |
| CCBA | new |
Business Analysis Certification
d_init_01
|
— | — | — | skill_not_in_db_v3_proposed |
| Excel | new |
Spreadsheet Analysis and Modeling
d_init_01
|
— | — | — | skill_not_in_db_v3_proposed |
| FRDs | new |
Functional Requirements Documents
d_init_01
|
— | — | — | skill_not_in_db_v3_proposed |
| Familiarity | new |
Domain Familiarity
d_init_01
|
— | — | — | skill_not_in_db_v3_proposed |
| Familiarity | new |
Business Domain Awareness
d_init_02
|
— | — | — | skill_not_in_db_v3_proposed |
| Knowledge | new |
Domain Knowledge and Business Context
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 |
| UAT | new |
User Acceptance Testing
d_init_01
|
— | — | — | skill_not_in_db_v3_proposed |
| Visio | new |
Diagramming and Process Modeling
d_init_01
|
— | — | — | skill_not_in_db_v3_proposed |
Library artifacts (this run)
| Kind | Detail | DB id |
|---|---|---|
| canonical_skill_proposed | APIs | type=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 | BRDs | type=Concept subtype=business_requirements_document 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=Concept subtype=functional_requirements_document nature=CONCEPT lifespan=EVERGREEN | |
| canonical_skill_proposed | Familiarity | type=Concept subtype=familiarity nature=CONCEPT lifespan=EVERGREEN | |
| canonical_skill_proposed | Knowledge | type=Concept subtype=general_knowledge nature=CONCEPT lifespan=EVERGREEN | |
| canonical_skill_proposed | QA | type=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 Requirements Documentation | |
| dimension_skill_link_proposed | BRDs ↔ Business Requirements Documentation | |
| dimension_proposed | Business Analysis Certification | |
| dimension_skill_link_proposed | CBAP ↔ Business Analysis Certification | |
| dimension_proposed | Business Analysis Certification | |
| dimension_skill_link_proposed | CCBA ↔ Business Analysis Certification | |
| dimension_proposed | Spreadsheet Analysis and Modeling | |
| dimension_skill_link_proposed | Excel ↔ Spreadsheet Analysis and Modeling | |
| dimension_proposed | Functional Requirements Documents | |
| dimension_skill_link_proposed | FRDs ↔ Functional Requirements Documents | |
| dimension_proposed | Domain Familiarity | |
| dimension_skill_link_proposed | Familiarity ↔ Domain Familiarity | |
| dimension_proposed | Business Domain Awareness | |
| dimension_skill_link_proposed | Familiarity ↔ Business Domain Awareness | |
| dimension_proposed | Domain Knowledge and Business Context | |
| dimension_skill_link_proposed | Knowledge ↔ Domain Knowledge and Business Context | |
| 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 | User Acceptance Testing | |
| dimension_skill_link_proposed | UAT ↔ User Acceptance Testing | |
| dimension_proposed | Diagramming and Process Modeling | |
| dimension_skill_link_proposed | Visio ↔ Diagramming and Process Modeling |
API 1 — extract-from-jd click to toggle
{
"filtered_unknown_words": [
"2\u20135",
"APIs",
"Ability",
"Acceptance",
"Analyst",
"BI",
"BRDs",
"Bachelor",
"Benefits",
"Business",
"CBAP",
"CCBA",
"Career",
"Certification",
"Computer",
"Conduct",
"Description",
"Ensure",
"Excel",
"Experience",
"Exposure",
"FRDs",
"Familiarity",
"Gather",
"Health",
"Hybrid",
"Job",
"Key",
"Knowledge",
"Learning",
"Location",
"Monitor",
"Power",
"Preferred",
"QA",
"Qualifications",
"Remote",
"Required",
"Responsibilities",
"Role",
"SDLC",
"SaaS",
"Science",
"Skills",
"Support",
"Testing",
"Title",
"UAT",
"Understanding",
"User",
"Visio",
"Years",
"abilities",
"analysis",
"benefits",
"business",
"candidate",
"certification",
"commerce",
"communication",
"company",
"data",
"databases",
"degree",
"delivery",
"dependencies",
"developers",
"development",
"diagrams",
"document",
"documentation",
"domains",
"environment",
"field",
"fintech",
"gap",
"gathering",
"goals",
"growth",
"healthcare",
"insights",
"insurance",
"leaves",
"management",
"managers",
"meetings",
"methodologies",
"needs",
"opportunities",
"optimization",
"problem",
"process",
"processes",
"product",
"progress",
"project",
"reporting",
"requirement",
"requirements",
"risks",
"salary",
"site",
"skills",
"software",
"solutions",
"specifications",
"stakeholder",
"stakeholders",
"stories",
"strategies",
"teams",
"tools",
"trends",
"understanding",
"user",
"work",
"workshops"
],
"final_non_skills": [
"2\u20135",
"Ability",
"Analyst",
"Bachelor",
"Benefits",
"Business",
"Certification",
"Computer",
"Conduct",
"Description",
"Ensure",
"Experience",
"Exposure",
"Gather",
"Health",
"Hybrid",
"Job",
"Key",
"Learning",
"Location",
"Monitor",
"Power",
"Preferred",
"Qualifications",
"Remote",
"Required",
"Responsibilities",
"Role",
"Science",
"Skills",
"Support",
"Title",
"Understanding",
"User",
"Years",
"abilities",
"analysis",
"candidate",
"commerce",
"communication",
"company",
"data",
"databases",
"degree",
"delivery",
"dependencies",
"developers",
"development",
"diagrams",
"document",
"documentation",
"domains",
"environment",
"field",
"fintech",
"gap",
"gathering",
"goals",
"growth",
"healthcare",
"insights",
"insurance",
"leaves",
"management",
"managers",
"meetings",
"methodologies",
"needs",
"opportunities",
"optimization",
"problem",
"process",
"processes",
"product",
"progress",
"project",
"reporting",
"requirement",
"requirements",
"risks",
"salary",
"site",
"software",
"solutions",
"specifications",
"stakeholder",
"stakeholders",
"stories",
"strategies",
"teams",
"tools",
"trends",
"work",
"workshops"
],
"final_skills": [
"Tableau",
"Argo Workflows",
"Power BI",
"APIs",
"Acceptance",
"BI",
"BRDs",
"CBAP",
"CCBA",
"Excel",
"FRDs",
"Familiarity",
"Knowledge",
"QA",
"SDLC",
"SaaS",
"Testing",
"UAT",
"Visio"
],
"initial_skills": [
"Tableau",
"Argo Workflows",
"Power BI"
],
"jd_role_hint": {
"display_name": "Business Analyst",
"rationale": "The excerpt centers on gathering, analyzing, documenting requirements, and translating business needs into functional specifications and user stories.",
"role_archetype": "Requirements and process-focused analyst who bridges business stakeholders and technical teams.",
"slug": "business-analyst"
},
"llm_non_skills": [
"2\u20135",
"Ability",
"Analyst",
"Bachelor",
"Benefits",
"Business",
"Certification",
"Computer",
"Conduct",
"Description",
"Ensure",
"Experience",
"Exposure",
"Gather",
"Health",
"Hybrid",
"Job",
"Key",
"Learning",
"Location",
"Monitor",
"Power",
"Preferred",
"Qualifications",
"Remote",
"Required",
"Responsibilities",
"Role",
"Science",
"Skills",
"Support",
"Title",
"Understanding",
"User",
"Years",
"abilities",
"analysis",
"candidate",
"commerce",
"communication",
"company",
"data",
"databases",
"degree",
"delivery",
"dependencies",
"developers",
"development",
"diagrams",
"document",
"documentation",
"domains",
"environment",
"field",
"fintech",
"gap",
"gathering",
"goals",
"growth",
"healthcare",
"insights",
"insurance",
"leaves",
"management",
"managers",
"meetings",
"methodologies",
"needs",
"opportunities",
"optimization",
"problem",
"process",
"processes",
"product",
"progress",
"project",
"reporting",
"requirement",
"requirements",
"risks",
"salary",
"site",
"software",
"solutions",
"specifications",
"stakeholder",
"stakeholders",
"stories",
"strategies",
"teams",
"tools",
"trends",
"work",
"workshops"
],
"llm_skills": [
"APIs",
"Acceptance",
"BI",
"BRDs",
"CBAP",
"CCBA",
"Excel",
"FRDs",
"Familiarity",
"Knowledge",
"QA",
"SDLC",
"SaaS",
"Testing",
"UAT",
"Visio"
],
"run_id": null,
"unknown_words": [
"2\u20135",
"APIs",
"Ability",
"Acceptance",
"Analyst",
"BI",
"BRDs",
"Bachelor",
"Benefits",
"Business",
"CBAP",
"CCBA",
"Career",
"Certification",
"Computer",
"Conduct",
"Description",
"Ensure",
"Excel",
"Experience",
"Exposure",
"FRDs",
"Familiarity",
"Gather",
"Health",
"Hybrid",
"Job",
"Key",
"Knowledge",
"Learning",
"Location",
"Monitor",
"Power",
"Preferred",
"QA",
"Qualifications",
"Remote",
"Required",
"Responsibilities",
"Role",
"SDLC",
"SaaS",
"Science",
"Skills",
"Support",
"Testing",
"Title",
"UAT",
"Understanding",
"User",
"Visio",
"Years",
"abilities",
"analysis",
"benefits",
"business",
"candidate",
"certification",
"commerce",
"communication",
"company",
"data",
"databases",
"degree",
"delivery",
"dependencies",
"developers",
"development",
"diagrams",
"document",
"documentation",
"domains",
"environment",
"field",
"fintech",
"gap",
"gathering",
"goals",
"growth",
"healthcare",
"insights",
"insurance",
"leaves",
"management",
"managers",
"meetings",
"methodologies",
"needs",
"opportunities",
"optimization",
"problem",
"process",
"processes",
"product",
"progress",
"project",
"reporting",
"requirement",
"requirements",
"risks",
"salary",
"site",
"skills",
"software",
"solutions",
"specifications",
"stakeholder",
"stakeholders",
"stories",
"strategies",
"teams",
"tools",
"trends",
"understanding",
"user",
"work",
"workshops"
]
}
API 2 — extract-details
{
"alias_matches": [],
"candidate_roles": [
{
"display_name": "Data 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": "Business Analyst",
"id": null,
"rationale": "The strongest signal is the API/BRD/FRD/UAT/SDLC-heavy business analysis dimension, with supporting dashboard/reporting work and only a minor data engineering signal.",
"role_archetype": "Requirements and process-focused analyst who bridges business stakeholders and technical teams. Often documents BRDs/FRDs, supports UAT, and collaborates on systems and reporting needs.",
"slug": "business-analyst",
"source": "llm"
},
"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"
}
]
},
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Workflow Orchestration Systems",
"id": 64,
"rationale": "Operational orchestration of ML jobs, dependencies, and handoffs across training, validation, deployment, and retraining. This is a useful split from training pipelines because it emphasizes the scheduler and control plane.",
"slug": "workflow-orchestration-systems",
"source": "db"
},
"input_skill": "Argo Workflows",
"llm_role": null,
"roles_from_db": [
{
"display_name": "Data Engineer",
"id": 6,
"rationale": null,
"role_archetype": null,
"slug": "data-engineer",
"source": "db"
},
{
"display_name": "MLOps Engineer",
"id": 5,
"rationale": null,
"role_archetype": null,
"slug": "mlops-engineer",
"source": "db"
}
]
},
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Reporting and Dashboard Development",
"id": 295,
"rationale": "Building recurring reports and dashboards that track performance over time and across segments. This is a distinct cluster because the analyst must package metrics into reusable views for stakeholders.",
"slug": "reporting-and-dashboard-development",
"source": "db"
},
"input_skill": "Power BI",
"llm_role": null,
"roles_from_db": [
{
"display_name": "Data Analyst",
"id": 20,
"rationale": null,
"role_archetype": null,
"slug": "data-analyst",
"source": "db"
}
]
},
{
"dimension": {
"difficulty_hint": null,
"display_name": "API Design and Integration",
"id": null,
"rationale": "Designing, consuming, and integrating application programming interfaces that connect systems and exchange data. APIs fit here because they define the contract for requests, responses, and interoperability between services and external platforms.",
"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 practice of turning business data into reports, dashboards, and decision-support insights. BI fits here because it commonly refers to the tools and workflows used by analysts to explore, summarize, and communicate business performance.",
"slug": "d_init_01",
"source": "llm"
},
"input_skill": "BI",
"llm_role": null,
"roles_from_db": []
},
{
"dimension": {
"difficulty_hint": null,
"display_name": "Business Requirements Documentation",
"id": null,
"rationale": "Covers creating and maintaining BRDs that capture business goals, scope, assumptions, constraints, and stakeholder needs. This fits BRDs because they are a formal requirements artifact used to align business and delivery teams before implementation.",
"slug": "d_init_01",
"source": "llm"
},
"input_skill": "BRDs",
"llm_role": null,
"roles_from_db": []
},
{
"dimension": {
"difficulty_hint": null,
"display_name": "Business Analysis Certification",
"id": null,
"rationale": "Professional certification knowledge for business analysts, especially the CBAP credential. It covers the BABOK-aligned competencies, techniques, and terminology used to analyze needs, define requirements, and support solution delivery.",
"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 competency for practitioners who elicit, analyze, document, and validate requirements. CCBA fits here as a recognized business analysis certification rather than a tooling or technical implementation 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 Modeling",
"id": null,
"rationale": "Using spreadsheets to organize, analyze, and present data for business decisions. Excel belongs here because it is the core tool for formulas, pivots, charts, and ad hoc analysis in analyst workflows.",
"slug": "d_init_01",
"source": "llm"
},
"input_skill": "Excel",
"llm_role": null,
"roles_from_db": []
},
{
"dimension": {
"difficulty_hint": null,
"display_name": "Functional Requirements Documents",
"id": null,
"rationale": "Covers creating, reviewing, and maintaining FRDs that define what a product or system must do from a business perspective. This fits a Business Analyst role because FRDs translate stakeholder needs into structured functional requirements for delivery teams.",
"slug": "d_init_01",
"source": "llm"
},
"input_skill": "FRDs",
"llm_role": null,
"roles_from_db": []
},
{
"dimension": {
"difficulty_hint": null,
"display_name": "Domain Familiarity",
"id": null,
"rationale": "General working familiarity with a business or technical domain, including its terminology, common workflows, and key stakeholders. This fits the target skill because it signals awareness and context rather than deep specialization in a specific engineering practice.",
"slug": "d_init_01",
"source": "llm"
},
"input_skill": "Familiarity",
"llm_role": null,
"roles_from_db": []
},
{
"dimension": {
"difficulty_hint": null,
"display_name": "Business Domain Awareness",
"id": null,
"rationale": "Understanding the business context, operating model, and terminology relevant to analysis work. For a Business Analyst, familiarity often means enough context to communicate effectively with stakeholders and interpret process or requirement discussions.",
"slug": "d_init_02",
"source": "llm"
},
"input_skill": "Familiarity",
"llm_role": null,
"roles_from_db": []
},
{
"dimension": {
"difficulty_hint": null,
"display_name": "Domain Knowledge and Business Context",
"id": null,
"rationale": "Understanding the business domain, terminology, processes, and rules that shape analysis and decisions. This skill belongs here because a Business Analyst must know the subject matter well enough to interpret requirements and communicate accurately.",
"slug": "d_init_01",
"source": "llm"
},
"input_skill": "Knowledge",
"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. SDLC belongs here because it refers to the overall delivery lifecycle rather than a single technical specialty.",
"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 software products that are accessed by subscription through a browser or thin client. This fits SaaS because the skill refers to the product delivery and operating model rather than a specific technical implementation detail.",
"slug": "d_init_01",
"source": "llm"
},
"input_skill": "SaaS",
"llm_role": null,
"roles_from_db": []
},
{
"dimension": {
"difficulty_hint": null,
"display_name": "User Acceptance Testing",
"id": null,
"rationale": "Validating that a delivered feature meets documented business requirements, user stories, and acceptance criteria. UAT belongs here because it is the business-facing check that the solution works as intended before sign-off.",
"slug": "d_init_01",
"source": "llm"
},
"input_skill": "UAT",
"llm_role": null,
"roles_from_db": []
},
{
"dimension": {
"difficulty_hint": null,
"display_name": "Diagramming and Process Modeling",
"id": null,
"rationale": "Creating business and technical diagrams to communicate workflows, systems, and relationships. Visio belongs here because it is commonly used to draw process maps, 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": [
"Tableau",
"Argo Workflows",
"Power BI",
"APIs",
"Acceptance",
"BI",
"BRDs",
"CBAP",
"CCBA",
"Excel",
"FRDs",
"Familiarity",
"Knowledge",
"QA",
"SDLC",
"SaaS",
"Testing",
"UAT",
"Visio"
],
"input_llm_skills": [
"APIs",
"Acceptance",
"BI",
"BRDs",
"CBAP",
"CCBA",
"Excel",
"FRDs",
"Familiarity",
"Knowledge",
"QA",
"SDLC",
"SaaS",
"Testing",
"UAT",
"Visio"
],
"new_aliases_persisted": 0,
"run_id": "eb02168f-026f-4c93-8b0c-84ebc7c90426",
"skills_detail": [
{
"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": [
{
"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": [],
"canonical": null,
"dimensions": [
{
"dimension": {
"difficulty_hint": null,
"display_name": "API Design and Integration",
"id": null,
"rationale": "Designing, consuming, and integrating application programming interfaces that connect systems and exchange data. APIs fit here because they define the contract for requests, responses, and interoperability between services and external platforms.",
"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-volume job postings and cloud vendor docs."
},
"skill_id": "apis",
"vendor_license": {
"confidence": 0.99,
"license": null,
"vendor": null,
"year_introduced": null
},
"versioning": {
"current_version": null,
"version_aliases": {},
"versioned": false
}
},
"locked_dimensions": [
{
"description": "Designing, consuming, and integrating application programming interfaces that connect systems and exchange data. APIs fit here because they define the contract for requests, responses, and interoperability between services and external platforms.",
"exemplar_skills": [
"APIs",
"REST APIs",
"GraphQL",
"webhooks",
"API versioning",
"endpoint design"
],
"in_scope": "APIs, REST APIs, SOAP APIs, GraphQL APIs, webhook contracts, request and response payloads, endpoint design, versioning, pagination, idempotency",
"name": "API Design and Integration",
"out_of_scope": "UI behavior and client state management, authentication session handling, database schema design, message queue internals, these belong to other dimensions",
"overlap_flags": [
{
"reason": "Both involve calling external interfaces, but this dimension is about software integration contracts rather than model tool invocation.",
"with_dim_id": "tool-use-and-function-calling",
"with_dim_name": null,
"with_role": null
},
{
"reason": "API usage often includes auth concerns, but sign-in and session behavior are owned by the authentication dimension.",
"with_dim_id": "authentication-flows-and-session-handling",
"with_dim_name": null,
"with_role": null
},
{
"reason": "Service integration and API work are closely related, but this dimension is narrower and centered on interface design and consumption.",
"with_dim_id": "service-architecture-and-integration",
"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"
],
"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 between systems, so by the Protocol rule they fit best as a protocol-like standard for interaction rather than a tool or platform.",
"skill_id": "apis",
"subtype": "application_programming_interfaces",
"type": "Protocol"
},
"warnings": []
},
"source_tag": "llm",
"was_in_llm_skills": true
},
{
"aliases_in_db": [],
"canonical": null,
"dimensions": [],
"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"
],
"reasoning": "\u201cAcceptance\u201d is a generic term and in JDs could refer to acceptance testing or user acceptance testing rather than the standalone concept."
},
"context_keywords": {
"context_keywords": [
"UAT",
"user acceptance testing",
"acceptance criteria",
"acceptance test",
"sign-off",
"go-live",
"test cases",
"requirements validation",
"stakeholder approval",
"definition of done",
"QA",
"regression testing",
"test plan",
"business acceptance"
]
},
"maturity": {
"confidence": 0.78,
"maturity": "niche",
"reasoning": "Acceptance is a QA/UAT concept that appears in some test and product JDs, but market demand is far lower than core engineering skills; it\u2019s usually listed as \u201cacceptance testing/UAT\u201d rather than a standalone hiring staple."
},
"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": [
{
"into": "d_merge_01",
"into_name": "Requirements and Acceptance Validation",
"merged_from": [
"d_init_01",
"requirements-and-acceptance-validation"
],
"reasoning": "Both dimensions describe the same conceptual cluster: validating delivered/implemented behavior against documented requirements, user stories, and acceptance criteria. Dim A explicitly covers acceptance, requirements validation, user story verification, UAT support, and stakeholder sign-off checks; Dim B uses the same core framing and adds that implemented behavior matches requirements and acceptance criteria. The overlap is not just lexical: the exemplar skills in A (Acceptance, Requirements validation, Acceptance criteria review, User story verification, UAT coordination, Stakeholder sign-off) are exactly the activities implied by B\u2019s description. The difference is only wording and role emphasis (A is business-analyst oriented, B is manual-testing oriented), not a distinct skill cluster."
}
],
"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 acceptance is not a process or operating method like Agile or TDD.",
"SoftSkill: ruled out \u2014 although acceptance can involve interpersonal agreement, the skill name here refers to the technical/product concept."
],
"confidence": 0.74,
"name": "Acceptance",
"reasoning": "By the Concept vs Methodology rule, Acceptance is best treated as a named knowledge unit about validating whether work meets requirements, 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 practice of turning business data into reports, dashboards, and decision-support insights. BI fits here because it commonly refers to the tools and workflows used by analysts to explore, summarize, and communicate business performance.",
"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 BI-related terms or the full phrase. A reasonable extractor could confuse the shorthand with the catalog\u0027s 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",
"semantic layer"
]
},
"maturity": {
"confidence": 0.93,
"maturity": "well_known",
"reasoning": "BI is a common hiring keyword across analytics and data roles; job postings frequently ask for Power BI/Tableau/Looker skills, showing broad market demand rather than a niche toolset."
},
"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 practice of turning business data into reports, dashboards, and decision-support insights. BI fits here because it commonly refers to the tools and workflows used by analysts to explore, summarize, and communicate business performance.",
"exemplar_skills": [
"BI",
"dashboard creation",
"KPI reporting",
"ad hoc reporting",
"self-service analytics",
"data visualization",
"business reporting"
],
"in_scope": "BI, dashboards, KPI reporting, ad hoc analysis, OLAP, semantic layers, self-service analytics, data visualization, business reporting, slice-and-dice analysis",
"name": "Business Intelligence",
"out_of_scope": "statistical hypothesis testing and causal inference, data engineering pipelines and ETL orchestration, data quality auditing, access control and governance policies",
"overlap_flags": [
{
"reason": "BI often uses dashboards and reports, but that catalog dimension is platform-specific configuration rather than the broader analytics practice.",
"with_dim_id": "reporting-and-dashboard-configuration",
"with_dim_name": null,
"with_role": null
},
{
"reason": "BI work may use basic statistics, but deeper statistical interpretation belongs in the analysis-focused dimension.",
"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.94,
"name": "BI",
"reasoning": "BI is fundamentally a business intelligence knowledge area and problem-space, so it fits the Domain type rather than a tool, platform, 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 Requirements Documentation",
"id": null,
"rationale": "Covers creating and maintaining BRDs that capture business goals, scope, assumptions, constraints, and stakeholder needs. This fits BRDs because they are a formal requirements artifact used to align business and delivery teams before implementation.",
"slug": "d_init_01",
"source": "llm"
},
"input_skill": "BRDs",
"llm_role": null,
"roles_from_db": []
}
],
"input_skill": "BRDs",
"matched_via": null,
"new_alias_persisted": false,
"new_alias_text": null,
"new_skill_meta": {
"derived": {
"category": "Concept",
"skill_nature": "CONCEPT",
"sub_category": "business_requirements_document",
"typical_lifespan": "EVERGREEN",
"version_strategy": "NOT_APPLICABLE",
"volatility": "STABLE"
},
"enrichment": {
"ambiguity": {
"ambiguity_flag": false,
"confused_with": [],
"reasoning": "BRDs is a common abbreviation for Business Requirements Documents; in JDs it is usually unambiguous and not plausibly confused with a different catalog skill."
},
"context_keywords": {
"context_keywords": [
"requirements gathering",
"stakeholder interviews",
"functional requirements",
"non-functional requirements",
"use cases",
"user stories",
"scope definition",
"acceptance criteria",
"process flows",
"business analysis",
"traceability matrix",
"gap analysis",
"solution design",
"sign-off",
"change requests"
]
},
"maturity": {
"confidence": 0.86,
"maturity": "well_known",
"reasoning": "BRDs are a standard artifact in business analysis and product roles; job descriptions commonly ask for business requirements documentation or BRD experience, especially in enterprise and consulting hiring."
},
"skill_id": "brds",
"vendor_license": {
"confidence": 0.99,
"license": null,
"vendor": null,
"year_introduced": null
},
"versioning": {
"current_version": null,
"version_aliases": {},
"versioned": false
}
},
"locked_dimensions": [
{
"description": "Covers creating and maintaining BRDs that capture business goals, scope, assumptions, constraints, and stakeholder needs. This fits BRDs because they are a formal requirements artifact used to align business and delivery teams before implementation.",
"exemplar_skills": [
"BRDs",
"business requirements gathering",
"business requirements documentation",
"requirements elicitation",
"scope definition",
"stakeholder alignment",
"requirements sign-off"
],
"in_scope": "BRDs, business requirements documents, scope statements, stakeholder needs, business objectives, assumptions, constraints, high-level requirements, approval sign-off, requirement traceability",
"name": "Business Requirements Documentation",
"out_of_scope": "User stories and acceptance criteria, which belong to requirements-and-acceptance-validation, technical design specs, which belong to solution architecture, process maps and SOPs, which belong to business process documentation",
"overlap_flags": [
{
"reason": "BRDs often feed acceptance criteria and validation, but that dimension focuses on checking implemented behavior rather than authoring business requirements.",
"with_dim_id": "requirements-and-acceptance-validation",
"with_dim_name": null,
"with_role": null
}
],
"tentative_id": "d_init_01"
}
],
"merge_log": [],
"placed": {
"name": "BRDs",
"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": "brds"
},
"relationships": {
"child_skills": [],
"parent_skills": [],
"related_to": [
"runbooks",
"order-guides",
"rollback-readiness"
],
"requires": [],
"skill_id": "brds",
"suppress_on_match": []
},
"skill_id": "brds",
"split_log": [],
"typed": {
"alternatives_considered": [],
"confidence": 0.88,
"name": "BRDs",
"reasoning": "BRDs (business requirements documents) are a named knowledge artifact used to capture requirements, so they fit the Concept category rather than a tool, framework, or methodology.",
"skill_id": "brds",
"subtype": "business_requirements_document",
"type": "Concept"
},
"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 knowledge for business analysts, especially the CBAP credential. It covers the BABOK-aligned competencies, techniques, and terminology used to analyze needs, define requirements, and support solution delivery.",
"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",
"SWOT analysis",
"UML",
"traceability matrix",
"workshops",
"functional requirements"
]
},
"maturity": {
"confidence": 0.84,
"maturity": "well_known",
"reasoning": "CBAP is a widely recognized business analysis certification and appears frequently in BA job descriptions as a preferred credential, especially in enterprise and consulting hiring pipelines."
},
"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": "Professional certification knowledge for business analysts, especially the CBAP credential. It covers the BABOK-aligned competencies, techniques, and terminology used to analyze needs, define requirements, and support solution delivery.",
"exemplar_skills": [
"CBAP",
"BABOK",
"requirements elicitation",
"stakeholder analysis",
"process modeling",
"business case analysis"
],
"in_scope": "CBAP, BABOK, business analysis certification, requirements elicitation, stakeholder analysis, process modeling, solution assessment, business case analysis",
"name": "Business Analysis Certification",
"out_of_scope": "requirements and acceptance validation, product management strategy, project management scheduling, software testing execution, data analysis methods",
"overlap_flags": [
{
"reason": "CBAP includes requirements work, but this catalog dimension is about validating implemented behavior rather than the broader business analysis body of knowledge.",
"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",
"acceptance-criteria-validation",
"acceptance-criteria-checks",
"capacity-planning",
"session-based-testing"
],
"requires": [],
"skill_id": "cbap",
"suppress_on_match": []
},
"skill_id": "cbap",
"split_log": [],
"typed": {
"alternatives_considered": [],
"confidence": 0.98,
"name": "CBAP",
"reasoning": "CBAP is a formal third-party credential, so by the Certification rule it is a certification rather than a concept or methodology.",
"skill_id": "cbap",
"subtype": "business_analysis_professional_certification",
"type": "Certification"
},
"warnings": []
},
"source_tag": "llm",
"was_in_llm_skills": true
},
{
"aliases_in_db": [],
"canonical": null,
"dimensions": [
{
"dimension": {
"difficulty_hint": null,
"display_name": "Business Analysis Certification",
"id": null,
"rationale": "Formal business analysis credentialing and exam-based competency for practitioners who elicit, analyze, document, and validate requirements. CCBA fits here as a recognized business analysis certification rather than a tooling or technical implementation 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",
"use cases",
"user stories",
"gap analysis",
"traceability matrix",
"business process improvement",
"solution assessment",
"SWOT analysis",
"MoSCoW",
"UML",
"workshops"
]
},
"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 competency for practitioners who elicit, analyze, document, and validate requirements. CCBA fits here as a recognized business analysis certification rather than a tooling or technical implementation skill.",
"exemplar_skills": [
"CCBA",
"CBAP",
"ECBA",
"business analysis certification",
"requirements elicitation",
"stakeholder analysis",
"process modeling"
],
"in_scope": "CCBA, CBAP, ECBA, business analysis certification, requirements elicitation, stakeholder analysis, process modeling, solution assessment, business analysis planning",
"name": "Business Analysis Certification",
"out_of_scope": "Requirements and Acceptance Validation, software testing execution, project management certification, data analysis tooling, technical architecture design",
"overlap_flags": [
{
"reason": "Business analysts often validate requirements, but CCBA is primarily a credential covering broader BA competency rather than acceptance testing itself.",
"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",
"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 the Certification of Capability in Business Analysis, which is a formal third-party credential 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 data for business decisions. Excel belongs here because it is the core tool for formulas, pivots, charts, and ad hoc analysis in analyst workflows.",
"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": [
"PivotTables",
"VLOOKUP",
"XLOOKUP",
"INDEX-MATCH",
"Power Query",
"Power Pivot",
"macros",
"VBA",
"conditional formatting",
"data validation",
"charts",
"dashboards",
"CSV",
"formulas",
"Excel formulas"
]
},
"maturity": {
"confidence": 0.99,
"maturity": "well_known",
"reasoning": "Excel appears in a very high volume of job descriptions across finance, ops, analytics, and admin roles, and Microsoft continues active support and cloud integration via Microsoft 365."
},
"skill_id": "excel",
"vendor_license": {
"confidence": 0.99,
"license": "proprietary",
"vendor": "Microsoft",
"year_introduced": 1985
},
"versioning": {
"current_version": "Microsoft 365 / Excel 2024",
"version_aliases": {
"Excel 2007": "Microsoft 365 / Excel 2024",
"Excel 2010": "Microsoft 365 / Excel 2024",
"Excel 2013": "Microsoft 365 / Excel 2024",
"Excel 2016": "Microsoft 365 / Excel 2024",
"Excel 2019": "Microsoft 365 / Excel 2024",
"Excel 2021": "Microsoft 365 / Excel 2024",
"Excel 2024": "Microsoft 365 / Excel 2024",
"Excel 365": "Microsoft 365 / Excel 2024",
"Microsoft 365 Excel": "Microsoft 365 / Excel 2024"
},
"versioned": true
}
},
"locked_dimensions": [
{
"description": "Using spreadsheets to organize, analyze, and present data for business decisions. Excel belongs here because it is the core tool for formulas, pivots, charts, and ad hoc analysis in analyst workflows.",
"exemplar_skills": [
"Excel",
"Pivot Tables",
"VLOOKUP",
"XLOOKUP",
"Conditional Formatting",
"Data Validation",
"Chart Creation",
"Spreadsheet Modeling"
],
"in_scope": "Excel, formulas and functions, pivot tables, charts and graphs, filters and sorting, conditional formatting, lookup functions, data validation, basic financial and operational models",
"name": "Spreadsheet Analysis and Modeling",
"out_of_scope": "SQL querying and database design, statistical inference and experiment analysis, dashboard platforms like Power BI or Tableau, programming languages such as Python or R",
"overlap_flags": [
{
"reason": "Excel is often used for descriptive analysis, but statistical interpretation and inference belong 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 persistent dashboard configuration is a separate reporting skill cluster.",
"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 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 Documents",
"id": null,
"rationale": "Covers creating, reviewing, and maintaining FRDs that define what a product or system must do from a business perspective. This fits a Business Analyst role because FRDs translate stakeholder needs into structured functional requirements 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": "Concept",
"skill_nature": "CONCEPT",
"sub_category": "functional_requirements_document",
"typical_lifespan": "EVERGREEN",
"version_strategy": "NOT_APPLICABLE",
"volatility": "STABLE"
},
"enrichment": {
"ambiguity": {
"ambiguity_flag": false,
"confused_with": [],
"reasoning": "FRDs is a fairly specific requirements-document acronym; in typical JDs it would be read as functional requirements documents, not a common overloaded term with a close catalog alternative."
},
"context_keywords": {
"context_keywords": [
"BRD",
"PRD",
"use cases",
"user stories",
"acceptance criteria",
"functional specification",
"requirements traceability",
"scope definition",
"process flows",
"wireframes",
"stakeholder review",
"business rules",
"non-functional requirements",
"UAT",
"sign-off"
]
},
"maturity": {
"confidence": 0.86,
"maturity": "well_known",
"reasoning": "Functional requirements documents are a standard artifact in software and systems JDs/SDLCs, commonly requested alongside BRDs/PRDs and used across enterprise delivery teams."
},
"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 creating, reviewing, and maintaining FRDs that define what a product or system must do from a business perspective. This fits a Business Analyst role because FRDs translate stakeholder needs into structured functional requirements for delivery teams.",
"exemplar_skills": [
"FRDs",
"Functional Requirements Documents",
"Business Requirements Documentation",
"Use Case Writing",
"Requirements Elicitation",
"Acceptance Criteria Definition"
],
"in_scope": "FRDs, functional requirements documents, business requirements, use cases, user stories, acceptance criteria, process flows, stakeholder requirements, requirement traceability",
"name": "Functional Requirements Documents",
"out_of_scope": "Technical architecture design, API implementation details, test automation code, data modeling, which belong to engineering or testing dimensions",
"overlap_flags": [
{
"reason": "FRDs often feed acceptance validation, but this dimension is about authoring requirements rather than checking implementation against them.",
"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": [
"Format: ruled out \u2014 although documents have structure, FRDs fundamentally denote the requirements artifact/idea rather than a wire or data format.",
"Methodology: ruled out \u2014 FRDs are not a way of working or process."
],
"confidence": 0.78,
"name": "FRDs",
"reasoning": "FRDs are a named knowledge artifact describing requirements, so by the Concept vs Methodology rule they fit Concept rather than a tool or format.",
"skill_id": "frds",
"subtype": "functional_requirements_document",
"type": "Concept"
},
"warnings": []
},
"source_tag": "llm",
"was_in_llm_skills": true
},
{
"aliases_in_db": [],
"canonical": null,
"dimensions": [
{
"dimension": {
"difficulty_hint": null,
"display_name": "Domain Familiarity",
"id": null,
"rationale": "General working familiarity with a business or technical domain, including its terminology, common workflows, and key stakeholders. This fits the target skill because it signals awareness and context rather than deep specialization in a specific engineering practice.",
"slug": "d_init_01",
"source": "llm"
},
"input_skill": "Familiarity",
"llm_role": null,
"roles_from_db": []
},
{
"dimension": {
"difficulty_hint": null,
"display_name": "Business Domain Awareness",
"id": null,
"rationale": "Understanding the business context, operating model, and terminology relevant to analysis work. For a Business Analyst, familiarity often means enough context to communicate effectively with stakeholders and interpret process or requirement discussions.",
"slug": "d_init_02",
"source": "llm"
},
"input_skill": "Familiarity",
"llm_role": null,
"roles_from_db": []
}
],
"input_skill": "Familiarity",
"matched_via": null,
"new_alias_persisted": false,
"new_alias_text": null,
"new_skill_meta": {
"derived": {
"category": "Concept",
"skill_nature": "CONCEPT",
"sub_category": "familiarity",
"typical_lifespan": "EVERGREEN",
"version_strategy": "NOT_APPLICABLE",
"volatility": "STABLE"
},
"enrichment": {
"ambiguity": {
"ambiguity_flag": false,
"confused_with": [],
"reasoning": "\u201cFamiliarity\u201d is a generic concept term, but it is not a likely extractor collision with a distinct catalog skill in typical JDs."
},
"context_keywords": {
"context_keywords": [
"working knowledge",
"hands-on experience",
"exposure to",
"awareness of",
"proficiency",
"understanding of",
"basic knowledge",
"practical experience",
"familiar with",
"subject matter",
"domain knowledge",
"operational knowledge",
"prior exposure",
"working familiarity"
]
},
"maturity": {
"confidence": 0.86,
"maturity": "niche",
"reasoning": "\u201cFamiliarity\u201d is a generic concept, not a commonly listed standalone skill in job postings; market signals are sparse compared with concrete tools/tech stacks."
},
"skill_id": "familiarity",
"vendor_license": {
"confidence": 0.99,
"license": null,
"vendor": null,
"year_introduced": null
},
"versioning": {
"current_version": null,
"version_aliases": {},
"versioned": false
}
},
"locked_dimensions": [
{
"description": "General working familiarity with a business or technical domain, including its terminology, common workflows, and key stakeholders. This fits the target skill because it signals awareness and context rather than deep specialization in a specific engineering practice.",
"exemplar_skills": [
"Familiarity",
"Domain Familiarity",
"Business Process Awareness",
"Terminology Recognition",
"Stakeholder Context"
],
"in_scope": "Familiarity, domain familiarity, business process awareness, terminology recognition, stakeholder context, workflow awareness, product context, industry concepts",
"name": "Domain Familiarity",
"out_of_scope": "Deep subject-matter expertise, hands-on implementation, requirements elicitation, data analysis methods, system design, which belong to more specific functional dimensions",
"overlap_flags": [
{
"reason": "Some roles use domain familiarity to understand requirements, but that dimension is about verifying implemented behavior against acceptance criteria.",
"with_dim_id": "requirements-and-acceptance-validation",
"with_dim_name": null,
"with_role": null
},
{
"reason": "Technical domain familiarity can overlap with architecture knowledge, but this dimension is about structuring and integrating backend services.",
"with_dim_id": "service-architecture-and-integration",
"with_dim_name": null,
"with_role": null
}
],
"tentative_id": "d_init_01"
},
{
"description": "Understanding the business context, operating model, and terminology relevant to analysis work. For a Business Analyst, familiarity often means enough context to communicate effectively with stakeholders and interpret process or requirement discussions.",
"exemplar_skills": [
"Familiarity",
"Business Domain Awareness",
"Business Terminology",
"Process Context",
"Product Knowledge"
],
"in_scope": "Familiarity, business domain awareness, business terminology, process context, stakeholder language, operational context, product knowledge",
"name": "Business Domain Awareness",
"out_of_scope": "Requirements documentation, process mapping, data modeling, reporting configuration, test execution, which are separate analytical or delivery skills",
"overlap_flags": [
{
"reason": "Business analysts may need awareness of data handling rules, but that dimension is specifically about permissions, masking, and stewardship controls.",
"with_dim_id": "data-governance-and-access-control",
"with_dim_name": null,
"with_role": null
}
],
"tentative_id": "d_init_02"
}
],
"merge_log": [],
"placed": {
"name": "Familiarity",
"placement_confidence": 0.92,
"primary_dimension": "d_init_01",
"reasoning": "Deterministic JD placement: locked_dimensions has 2 dimension(s) from skill-driven dimension generation after reconciliation; primary_dimension is the first locked dim.",
"secondary_dimensions": [
"d_init_02"
],
"skill_id": "familiarity"
},
"relationships": {
"child_skills": [],
"parent_skills": [],
"related_to": [],
"requires": [],
"skill_id": "familiarity",
"suppress_on_match": []
},
"skill_id": "familiarity",
"split_log": [],
"typed": {
"alternatives_considered": [],
"confidence": 0.97,
"name": "Familiarity",
"reasoning": "Familiarity is a named knowledge unit about recognition or prior exposure, so by the Concept vs Methodology rule it is a Concept rather than a way of working.",
"skill_id": "familiarity",
"subtype": "familiarity",
"type": "Concept"
},
"warnings": []
},
"source_tag": "llm",
"was_in_llm_skills": true
},
{
"aliases_in_db": [],
"canonical": null,
"dimensions": [
{
"dimension": {
"difficulty_hint": null,
"display_name": "Domain Knowledge and Business Context",
"id": null,
"rationale": "Understanding the business domain, terminology, processes, and rules that shape analysis and decisions. This skill belongs here because a Business Analyst must know the subject matter well enough to interpret requirements and communicate accurately.",
"slug": "d_init_01",
"source": "llm"
},
"input_skill": "Knowledge",
"llm_role": null,
"roles_from_db": []
}
],
"input_skill": "Knowledge",
"matched_via": null,
"new_alias_persisted": false,
"new_alias_text": null,
"new_skill_meta": {
"derived": {
"category": "Concept",
"skill_nature": "CONCEPT",
"sub_category": "general_knowledge",
"typical_lifespan": "EVERGREEN",
"version_strategy": "NOT_APPLICABLE",
"volatility": "STABLE"
},
"enrichment": {
"ambiguity": {
"ambiguity_flag": true,
"confused_with": [
"knowledge_management",
"knowledge_graph",
"knowledge_base"
],
"reasoning": "\"Knowledge\" is very generic in JDs and could easily be intended as knowledge management, knowledge graph, or knowledge base rather than the abstract concept itself."
},
"context_keywords": {
"context_keywords": [
"domain expertise",
"subject matter expert",
"SME",
"institutional knowledge",
"knowledge base",
"knowledge management",
"knowledge transfer",
"knowledge sharing",
"knowledge graph",
"taxonomy",
"ontology",
"information architecture",
"lessons learned",
"best practices",
"documentation"
]
},
"maturity": {
"confidence": 0.93,
"maturity": "niche",
"reasoning": "\u201cKnowledge\u201d is a generic concept, not a specific engineering skill; it rarely appears as a standalone JD requirement, unlike concrete tools or languages. Market signal is effectively near-zero direct hiring volume."
},
"skill_id": "knowledge",
"vendor_license": {
"confidence": 0.99,
"license": null,
"vendor": null,
"year_introduced": null
},
"versioning": {
"current_version": null,
"version_aliases": {},
"versioned": false
}
},
"locked_dimensions": [
{
"description": "Understanding the business domain, terminology, processes, and rules that shape analysis and decisions. This skill belongs here because a Business Analyst must know the subject matter well enough to interpret requirements and communicate accurately.",
"exemplar_skills": [
"Knowledge",
"business domain knowledge",
"process knowledge",
"subject matter expertise",
"business rules understanding",
"stakeholder context awareness"
],
"in_scope": "Knowledge, business domain knowledge, process knowledge, terminology, policies, operating rules, stakeholder context, product knowledge, regulatory context, workflow understanding",
"name": "Domain Knowledge and Business Context",
"out_of_scope": "Requirements elicitation techniques, acceptance testing, data quality checks, statistical analysis, technical system design, project management methods",
"overlap_flags": [
{
"reason": "Business knowledge often informs requirement interpretation, but this dimension is about validating behavior against criteria rather than knowing the domain itself.",
"with_dim_id": "requirements-and-acceptance-validation",
"with_dim_name": null,
"with_role": null
},
{
"reason": "Some business knowledge includes policy awareness, but governance focuses on data permissions and stewardship controls.",
"with_dim_id": "data-governance-and-access-control",
"with_dim_name": null,
"with_role": null
}
],
"tentative_id": "d_init_01"
}
],
"merge_log": [],
"placed": {
"name": "Knowledge",
"placement_confidence": 0.92,
"primary_dimension": "d_init_01",
"reasoning": "Deterministic JD placement: locked_dimensions has 1 dimension(s) from skill-driven dimension generation after reconciliation; primary_dimension is the first locked dim.",
"secondary_dimensions": [],
"skill_id": "knowledge"
},
"relationships": {
"child_skills": [],
"parent_skills": [],
"related_to": [],
"requires": [],
"skill_id": "knowledge",
"suppress_on_match": []
},
"skill_id": "knowledge",
"split_log": [],
"typed": {
"alternatives_considered": [],
"confidence": 0.97,
"name": "Knowledge",
"reasoning": "Knowledge is a named body of understanding, so by the Concept vs Methodology rule it is a knowledge unit rather than a way of working.",
"skill_id": "knowledge",
"subtype": "general_knowledge",
"type": "Concept"
},
"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 testing-related roles; a catalog extractor could confuse the shorthand with the broader quality_assurance skill."
},
"context_keywords": {
"context_keywords": [
"test cases",
"test plans",
"test automation",
"regression testing",
"defect tracking",
"bug triage",
"UAT",
"Selenium",
"JIRA",
"manual testing",
"acceptance criteria",
"test scripts",
"smoke testing",
"QA process",
"traceability matrix"
]
},
"maturity": {
"confidence": 0.95,
"maturity": "well_known",
"reasoning": "QA is a standard hiring requirement across software JDs, with broad demand for test planning, defect tracking, and automation; it appears in large volumes on job boards and ATS filters."
},
"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": [
{
"into": "d_merge_01",
"into_name": "Requirements and Acceptance Validation",
"merged_from": [
"d_init_01",
"requirements-and-acceptance-validation"
],
"reasoning": "Both dims describe the same QA/acceptance-validation cluster: checking delivered behavior against requirements, user stories, and acceptance criteria. Dim A\u2019s in_scope items (QA, acceptance criteria review, user story validation, manual test execution, UAT support, defect verification, business rule checks) match Dim B\u2019s description of implemented behavior matching documented requirements and acceptance criteria. The exemplar skills also overlap directly (requirements validation, acceptance testing, UAT, manual testing)."
}
],
"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"
],
"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.",
"Concept: ruled out \u2014 QA is an operational practice, not a standalone theory or principle.",
"Domain: ruled out \u2014 QA is not a vertical industry or problem space."
],
"confidence": 0.67,
"name": "QA",
"reasoning": "QA is best treated as a quality-assurance practice/role 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": [
"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. SDLC belongs here because it refers to the overall delivery lifecycle rather than a single technical specialty.",
"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 Life Cycle and is usually unambiguous in job descriptions."
},
"context_keywords": {
"context_keywords": [
"requirements gathering",
"design review",
"implementation",
"code review",
"testing",
"QA",
"UAT",
"deployment",
"release management",
"change management",
"Agile",
"Scrum",
"waterfall",
"CI/CD",
"DevOps"
]
},
"maturity": {
"confidence": 0.93,
"maturity": "well_known",
"reasoning": "SDLC is a standard term in software job descriptions and enterprise process docs; it appears broadly across hiring pipelines and vendor frameworks like ISO/IEC 12207 and CMMI rather than as a niche tool."
},
"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. SDLC belongs here because it refers to the overall delivery lifecycle rather than a single technical specialty.",
"exemplar_skills": [
"SDLC",
"software development lifecycle",
"development lifecycle management",
"release planning",
"change management",
"requirements analysis",
"software maintenance"
],
"in_scope": "SDLC, requirements gathering, design, implementation, testing, release management, maintenance, change control, version control workflows, development process models, agile SDLC, waterfall SDLC",
"name": "Software Development Lifecycle",
"out_of_scope": "Specific test case design and execution, which belongs to requirements-and-acceptance-validation or frontend-testing-and-quality; build tooling and packaging, which belongs to build-configuration-and-release; production incident handling, which belongs to incident-response-and-remediation",
"overlap_flags": [
{
"reason": "SDLC often includes validation steps, but that catalog dimension is specifically about checking implemented behavior against requirements.",
"with_dim_id": "requirements-and-acceptance-validation",
"with_dim_name": null,
"with_role": null
},
{
"reason": "SDLC includes release activities, but this catalog dimension is narrower and focused on build and release preparation.",
"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": [
"clean-architecture",
"acceptance-criteria-checks",
"acceptance-criteria-validation",
"defect-retest",
"dependency-mapping",
"dashboards",
"scorecards"
],
"requires": [],
"skill_id": "sdlc",
"suppress_on_match": []
},
"skill_id": "sdlc",
"split_log": [],
"typed": {
"alternatives_considered": [
"Concept: ruled out \u2014 it is not just a knowledge unit but 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 software products that are accessed by subscription through a browser or thin client. This fits SaaS because the skill refers to the product delivery and operating model rather than a specific technical implementation detail.",
"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, widely used term for software-as-a-service and is usually clear in job descriptions; 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",
"SSO",
"SCIM",
"admin console",
"feature flags",
"API integrations",
"customer portal",
"SLAs",
"webhooks",
"RBAC"
]
},
"maturity": {
"confidence": 0.96,
"maturity": "well_known",
"reasoning": "SaaS is a standard deployment model in job postings across product, sales, and engineering roles; major vendors like Salesforce, Microsoft, and Google market SaaS offerings broadly, indicating mainstream adoption."
},
"skill_id": "saas",
"vendor_license": {
"confidence": 0.78,
"license": null,
"vendor": "Salesforce",
"year_introduced": 1999
},
"versioning": {
"current_version": null,
"version_aliases": {},
"versioned": false
}
},
"locked_dimensions": [
{
"description": "Covers cloud-delivered software products that are accessed by subscription through a browser or thin client. This fits SaaS because the skill refers to the product delivery and operating model rather than a specific technical implementation detail.",
"exemplar_skills": [
"SaaS",
"multi-tenant SaaS",
"subscription software",
"cloud-delivered software",
"hosted application service"
],
"in_scope": "SaaS, subscription software, multi-tenant applications, web-delivered business software, hosted application services, recurring-revenue software products",
"name": "Software as a Service",
"out_of_scope": "On-premises packaged software, infrastructure hosting primitives, internal enterprise platforms without external subscription delivery, mobile app distribution models",
"overlap_flags": [
{
"reason": "SaaS products are often built on cloud services, but this dimension is about selecting platform services rather than the software delivery model.",
"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 integrations rather than the business model.",
"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": [],
"confidence": 0.9,
"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": false,
"confused_with": [],
"reasoning": "In JDs, \"testing\" usually clearly means software testing methodology; it is broad but not typically confused with a different catalog skill."
},
"context_keywords": {
"context_keywords": [
"unit testing",
"integration testing",
"test automation",
"test cases",
"test plan",
"regression testing",
"smoke testing",
"mocking",
"stubs",
"fixtures",
"assertions",
"test coverage",
"TDD",
"BDD",
"Selenium"
]
},
"maturity": {
"confidence": 0.96,
"maturity": "well_known",
"reasoning": "Software testing is a standard requirement in most engineering JDs and appears across QA, SDET, and developer roles; major frameworks and CI pipelines make it a baseline hiring signal rather than a niche specialty."
},
"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": [],
"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",
"contract-tests",
"charter-based-testing",
"defect-retest",
"restore-testing"
],
"requires": [],
"skill_id": "testing",
"suppress_on_match": []
},
"skill_id": "testing",
"split_log": [],
"typed": {
"alternatives_considered": [],
"confidence": 0.91,
"name": "Testing",
"reasoning": "Testing is fundamentally a way of working to verify 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": [
"stage2_dim_gen_failed: ValidationError: 1 validation error for SkillDimensionList\ncandidate_dimensions.0.tentative_id\n String should match pattern \u0027^d_init_\\d{2,3}$\u0027 [type=string_pattern_mismatch, input_value=\u0027requirements-and-acceptance-validation\u0027, input_type=str]\n For further information visit https://errors.pydantic.dev/2.13/v/string_pattern_mismatch",
"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": "User Acceptance Testing",
"id": null,
"rationale": "Validating that a delivered feature meets documented business requirements, user stories, and acceptance criteria. UAT belongs here because it is the business-facing check that the solution works as intended before 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",
"stakeholder sign-off",
"end-to-end testing",
"test scenarios",
"defect triage",
"test plan",
"go-live",
"regression testing",
"test environment",
"user stories",
"smoke testing",
"traceability matrix"
]
},
"maturity": {
"confidence": 0.86,
"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, test planning, and release sign-off."
},
"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": [
{
"description": "Validating that a delivered feature meets documented business requirements, user stories, and acceptance criteria. UAT belongs here because it is the business-facing check that the solution works as intended before sign-off.",
"exemplar_skills": [
"UAT",
"user acceptance testing",
"acceptance criteria validation",
"business scenario testing",
"requirements validation",
"stakeholder sign-off"
],
"in_scope": "UAT, user acceptance testing, acceptance criteria validation, business scenario validation, requirement traceability, sign-off readiness, stakeholder walkthroughs, defect confirmation",
"name": "User Acceptance Testing",
"out_of_scope": "Unit testing, integration testing, performance testing, security testing, which belong to engineering QA or specialized test dimensions; production monitoring and incident response, which belong elsewhere",
"overlap_flags": [
{
"reason": "UAT can use UI test execution, but this dimension owns technical verification of frontend behavior rather than business acceptance.",
"with_dim_id": "frontend-testing-and-quality",
"with_dim_name": null,
"with_role": null
},
{
"reason": "If the catalog later includes a dedicated requirements validation dimension, UAT would overlap strongly with business acceptance checks.",
"with_dim_id": "requirements-and-acceptance-validation",
"with_dim_name": null,
"with_role": null
}
],
"tentative_id": "d_init_01"
}
],
"merge_log": [],
"placed": {
"name": "UAT",
"placement_confidence": 0.92,
"primary_dimension": "d_init_01",
"reasoning": "Deterministic JD placement: locked_dimensions has 1 dimension(s) from skill-driven dimension generation after reconciliation; primary_dimension is the first locked dim.",
"secondary_dimensions": [],
"skill_id": "uat"
},
"relationships": {
"child_skills": [],
"parent_skills": [],
"related_to": [
"acceptance-criteria-checks",
"session-based-testing",
"test-case-authoring"
],
"requires": [],
"skill_id": "uat",
"suppress_on_match": []
},
"skill_id": "uat",
"split_log": [],
"typed": {
"alternatives_considered": [],
"confidence": 0.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 tool or concept.",
"skill_id": "uat",
"subtype": "user_acceptance_testing",
"type": "Methodology"
},
"warnings": []
},
"source_tag": "llm",
"was_in_llm_skills": true
},
{
"aliases_in_db": [],
"canonical": null,
"dimensions": [
{
"dimension": {
"difficulty_hint": null,
"display_name": "Diagramming and Process Modeling",
"id": null,
"rationale": "Creating business and technical diagrams to communicate workflows, systems, and relationships. Visio belongs here because it is commonly used to draw process maps, 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",
"BPMN",
"UML",
"org chart",
"process map",
"network diagram",
"data flow diagram",
"wireframe",
"site map",
"as-is",
"to-be",
"business process",
"Visio stencils",
"cross-functional diagram"
]
},
"maturity": {
"confidence": 0.86,
"maturity": "well_known",
"reasoning": "Common in enterprise JDs for process/network diagrams and Microsoft 365 environments; Microsoft continues to support and market Visio with active desktop/web offerings, indicating broad ongoing adoption."
},
"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",
"process mapping",
"swimlane diagrams",
"BPMN diagramming",
"org chart creation",
"system diagramming"
],
"in_scope": "Visio, process flow diagrams, swimlane diagrams, BPMN sketches, org charts, network diagrams, system architecture diagrams, UML-style sketches, wireframes, business process mapping",
"name": "Diagramming and Process Modeling",
"out_of_scope": "Requirements elicitation and stakeholder interviewing, formal BPMN execution modeling in workflow engines, data modeling in ERD tools, project scheduling in Gantt or PPM tools",
"overlap_flags": [
{
"reason": "Network diagrams can overlap with network documentation, but Visio is broader and also covers business process and organizational diagrams.",
"with_dim_id": "network-documentation-and-standards",
"with_dim_name": null,
"with_role": null
},
{
"reason": "Service and system architecture diagrams may be created in Visio, but the dimension here is the diagramming tool and notation rather than backend 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": [],
"requires": [],
"skill_id": "visio",
"suppress_on_match": []
},
"skill_id": "visio",
"split_log": [],
"typed": {
"alternatives_considered": [],
"confidence": 0.98,
"name": "Visio",
"reasoning": "Visio is software you operate to create diagrams, so by the Tool vs Framework rule it is a Tool rather than something you build applications inside.",
"skill_id": "visio",
"subtype": "diagramming_tool",
"type": "Tool"
},
"warnings": []
},
"source_tag": "llm",
"was_in_llm_skills": true
}
],
"unmatched_skills": [
"APIs",
"Acceptance",
"BI",
"BRDs",
"CBAP",
"CCBA",
"Excel",
"FRDs",
"Familiarity",
"Knowledge",
"QA",
"SDLC",
"SaaS",
"Testing",
"UAT",
"Visio"
]
}
API 3 — final-role-output
{
"chosen_role": {
"display_name": "Business Analyst",
"id": null,
"rationale": "The strongest signal is the API/BRD/FRD/UAT/SDLC-heavy business analysis dimension, with supporting dashboard/reporting work and only a minor data engineering signal.",
"role_archetype": "Requirements and process-focused analyst who bridges business stakeholders and technical teams. Often documents BRDs/FRDs, supports UAT, and collaborates on systems and reporting needs.",
"slug": "business-analyst",
"source": "llm"
},
"final_input_skills": [
{
"skill": "Tableau",
"tag": "in_db"
},
{
"skill": "Argo Workflows",
"tag": "in_db"
},
{
"skill": "Power BI",
"tag": "in_db"
},
{
"skill": "APIs",
"tag": "new"
},
{
"skill": "Acceptance",
"tag": "new"
},
{
"skill": "BI",
"tag": "new"
},
{
"skill": "BRDs",
"tag": "new"
},
{
"skill": "CBAP",
"tag": "new"
},
{
"skill": "CCBA",
"tag": "new"
},
{
"skill": "Excel",
"tag": "new"
},
{
"skill": "FRDs",
"tag": "new"
},
{
"skill": "Familiarity",
"tag": "new"
},
{
"skill": "Knowledge",
"tag": "new"
},
{
"skill": "QA",
"tag": "new"
},
{
"skill": "SDLC",
"tag": "new"
},
{
"skill": "SaaS",
"tag": "new"
},
{
"skill": "Testing",
"tag": "new"
},
{
"skill": "UAT",
"tag": "new"
},
{
"skill": "Visio",
"tag": "new"
}
],
"persistence": {
"items": [
{
"chosen_role_id": null,
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Reporting and Dashboard Development",
"id": 295,
"rationale": "Building recurring reports and dashboards that track performance over time and across segments. This is a distinct cluster because the analyst must package metrics into reusable views for stakeholders.",
"slug": "reporting-and-dashboard-development",
"source": "db"
},
"dimension_id": 295,
"input_skill": "Tableau",
"llm_role": null,
"matched_chosen_role": false,
"role_dimension_saved": false,
"roles_from_db": [
{
"display_name": "Data Analyst",
"id": 20,
"rationale": null,
"role_archetype": null,
"slug": "data-analyst",
"source": "db"
}
],
"skill_dimension_saved": false,
"skill_id": 1883,
"skill_tag": "in_db",
"skipped_reason": "TODO: REMOVE AFTER TESTING \u2014 api3_writes_enabled=False (writes disabled)"
},
{
"chosen_role_id": null,
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Workflow Orchestration Systems",
"id": 64,
"rationale": "Operational orchestration of ML jobs, dependencies, and handoffs across training, validation, deployment, and retraining. This is a useful split from training pipelines because it emphasizes the scheduler and control plane.",
"slug": "workflow-orchestration-systems",
"source": "db"
},
"dimension_id": 64,
"input_skill": "Argo Workflows",
"llm_role": null,
"matched_chosen_role": false,
"role_dimension_saved": false,
"roles_from_db": [
{
"display_name": "Data Engineer",
"id": 6,
"rationale": null,
"role_archetype": null,
"slug": "data-engineer",
"source": "db"
},
{
"display_name": "MLOps Engineer",
"id": 5,
"rationale": null,
"role_archetype": null,
"slug": "mlops-engineer",
"source": "db"
}
],
"skill_dimension_saved": false,
"skill_id": 380,
"skill_tag": "in_db",
"skipped_reason": "TODO: REMOVE AFTER TESTING \u2014 api3_writes_enabled=False (writes disabled)"
},
{
"chosen_role_id": null,
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Reporting and Dashboard Development",
"id": 295,
"rationale": "Building recurring reports and dashboards that track performance over time and across segments. This is a distinct cluster because the analyst must package metrics into reusable views for stakeholders.",
"slug": "reporting-and-dashboard-development",
"source": "db"
},
"dimension_id": 295,
"input_skill": "Power BI",
"llm_role": null,
"matched_chosen_role": false,
"role_dimension_saved": false,
"roles_from_db": [
{
"display_name": "Data Analyst",
"id": 20,
"rationale": null,
"role_archetype": null,
"slug": "data-analyst",
"source": "db"
}
],
"skill_dimension_saved": false,
"skill_id": 1884,
"skill_tag": "in_db",
"skipped_reason": "TODO: REMOVE AFTER TESTING \u2014 api3_writes_enabled=False (writes disabled)"
},
{
"chosen_role_id": null,
"dimension": {
"difficulty_hint": null,
"display_name": "API Design and Integration",
"id": null,
"rationale": "Designing, consuming, and integrating application programming interfaces that connect systems and exchange data. APIs fit here because they define the contract for requests, responses, and interoperability between services and external platforms.",
"slug": "d_init_01",
"source": "llm"
},
"dimension_id": null,
"input_skill": "APIs",
"llm_role": null,
"matched_chosen_role": false,
"role_dimension_saved": false,
"roles_from_db": [],
"skill_dimension_saved": false,
"skill_id": null,
"skill_tag": "new",
"skipped_reason": "skill_not_in_db_v3_proposed"
},
{
"chosen_role_id": null,
"dimension": {
"difficulty_hint": null,
"display_name": "Business Intelligence",
"id": null,
"rationale": "Covers the practice of turning business data into reports, dashboards, and decision-support insights. BI fits here because it commonly refers to the tools and workflows used by analysts to explore, summarize, and communicate business performance.",
"slug": "d_init_01",
"source": "llm"
},
"dimension_id": null,
"input_skill": "BI",
"llm_role": null,
"matched_chosen_role": false,
"role_dimension_saved": false,
"roles_from_db": [],
"skill_dimension_saved": false,
"skill_id": null,
"skill_tag": "new",
"skipped_reason": "skill_not_in_db_v3_proposed"
},
{
"chosen_role_id": null,
"dimension": {
"difficulty_hint": null,
"display_name": "Business Requirements Documentation",
"id": null,
"rationale": "Covers creating and maintaining BRDs that capture business goals, scope, assumptions, constraints, and stakeholder needs. This fits BRDs because they are a formal requirements artifact used to align business and delivery teams before implementation.",
"slug": "d_init_01",
"source": "llm"
},
"dimension_id": null,
"input_skill": "BRDs",
"llm_role": null,
"matched_chosen_role": false,
"role_dimension_saved": false,
"roles_from_db": [],
"skill_dimension_saved": false,
"skill_id": null,
"skill_tag": "new",
"skipped_reason": "skill_not_in_db_v3_proposed"
},
{
"chosen_role_id": null,
"dimension": {
"difficulty_hint": null,
"display_name": "Business Analysis Certification",
"id": null,
"rationale": "Professional certification knowledge for business analysts, especially the CBAP credential. It covers the BABOK-aligned competencies, techniques, and terminology used to analyze needs, define requirements, and support solution delivery.",
"slug": "d_init_01",
"source": "llm"
},
"dimension_id": null,
"input_skill": "CBAP",
"llm_role": null,
"matched_chosen_role": false,
"role_dimension_saved": false,
"roles_from_db": [],
"skill_dimension_saved": false,
"skill_id": null,
"skill_tag": "new",
"skipped_reason": "skill_not_in_db_v3_proposed"
},
{
"chosen_role_id": null,
"dimension": {
"difficulty_hint": null,
"display_name": "Business Analysis Certification",
"id": null,
"rationale": "Formal business analysis credentialing and exam-based competency for practitioners who elicit, analyze, document, and validate requirements. CCBA fits here as a recognized business analysis certification rather than a tooling or technical implementation 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": null,
"dimension": {
"difficulty_hint": null,
"display_name": "Spreadsheet Analysis and Modeling",
"id": null,
"rationale": "Using spreadsheets to organize, analyze, and present data for business decisions. Excel belongs here because it is the core tool for formulas, pivots, charts, and ad hoc analysis in analyst workflows.",
"slug": "d_init_01",
"source": "llm"
},
"dimension_id": null,
"input_skill": "Excel",
"llm_role": null,
"matched_chosen_role": false,
"role_dimension_saved": false,
"roles_from_db": [],
"skill_dimension_saved": false,
"skill_id": null,
"skill_tag": "new",
"skipped_reason": "skill_not_in_db_v3_proposed"
},
{
"chosen_role_id": null,
"dimension": {
"difficulty_hint": null,
"display_name": "Functional Requirements Documents",
"id": null,
"rationale": "Covers creating, reviewing, and maintaining FRDs that define what a product or system must do from a business perspective. This fits a Business Analyst role because FRDs translate stakeholder needs into structured functional requirements 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": null,
"dimension": {
"difficulty_hint": null,
"display_name": "Domain Familiarity",
"id": null,
"rationale": "General working familiarity with a business or technical domain, including its terminology, common workflows, and key stakeholders. This fits the target skill because it signals awareness and context rather than deep specialization in a specific engineering practice.",
"slug": "d_init_01",
"source": "llm"
},
"dimension_id": null,
"input_skill": "Familiarity",
"llm_role": null,
"matched_chosen_role": false,
"role_dimension_saved": false,
"roles_from_db": [],
"skill_dimension_saved": false,
"skill_id": null,
"skill_tag": "new",
"skipped_reason": "skill_not_in_db_v3_proposed"
},
{
"chosen_role_id": null,
"dimension": {
"difficulty_hint": null,
"display_name": "Business Domain Awareness",
"id": null,
"rationale": "Understanding the business context, operating model, and terminology relevant to analysis work. For a Business Analyst, familiarity often means enough context to communicate effectively with stakeholders and interpret process or requirement discussions.",
"slug": "d_init_02",
"source": "llm"
},
"dimension_id": null,
"input_skill": "Familiarity",
"llm_role": null,
"matched_chosen_role": false,
"role_dimension_saved": false,
"roles_from_db": [],
"skill_dimension_saved": false,
"skill_id": null,
"skill_tag": "new",
"skipped_reason": "skill_not_in_db_v3_proposed"
},
{
"chosen_role_id": null,
"dimension": {
"difficulty_hint": null,
"display_name": "Domain Knowledge and Business Context",
"id": null,
"rationale": "Understanding the business domain, terminology, processes, and rules that shape analysis and decisions. This skill belongs here because a Business Analyst must know the subject matter well enough to interpret requirements and communicate accurately.",
"slug": "d_init_01",
"source": "llm"
},
"dimension_id": null,
"input_skill": "Knowledge",
"llm_role": null,
"matched_chosen_role": false,
"role_dimension_saved": false,
"roles_from_db": [],
"skill_dimension_saved": false,
"skill_id": null,
"skill_tag": "new",
"skipped_reason": "skill_not_in_db_v3_proposed"
},
{
"chosen_role_id": null,
"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. SDLC belongs here because it refers to the overall delivery lifecycle rather than a single technical specialty.",
"slug": "d_init_01",
"source": "llm"
},
"dimension_id": null,
"input_skill": "SDLC",
"llm_role": null,
"matched_chosen_role": false,
"role_dimension_saved": false,
"roles_from_db": [],
"skill_dimension_saved": false,
"skill_id": null,
"skill_tag": "new",
"skipped_reason": "skill_not_in_db_v3_proposed"
},
{
"chosen_role_id": null,
"dimension": {
"difficulty_hint": null,
"display_name": "Software as a Service",
"id": null,
"rationale": "Covers cloud-delivered software products that are accessed by subscription through a browser or thin client. This fits SaaS because the skill refers to the product delivery and operating model rather than a specific technical implementation detail.",
"slug": "d_init_01",
"source": "llm"
},
"dimension_id": null,
"input_skill": "SaaS",
"llm_role": null,
"matched_chosen_role": false,
"role_dimension_saved": false,
"roles_from_db": [],
"skill_dimension_saved": false,
"skill_id": null,
"skill_tag": "new",
"skipped_reason": "skill_not_in_db_v3_proposed"
},
{
"chosen_role_id": null,
"dimension": {
"difficulty_hint": null,
"display_name": "User Acceptance Testing",
"id": null,
"rationale": "Validating that a delivered feature meets documented business requirements, user stories, and acceptance criteria. UAT belongs here because it is the business-facing check that the solution works as intended before 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": null,
"dimension": {
"difficulty_hint": null,
"display_name": "Diagramming and Process Modeling",
"id": null,
"rationale": "Creating business and technical diagrams to communicate workflows, systems, and relationships. Visio belongs here because it is commonly used to draw process maps, 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": 17
},
"planner_output": null,
"run_id": "eb02168f-026f-4c93-8b0c-84ebc7c90426"
}
LLM Calls
Every model call made for this run, in pipeline order. Click a card to see the model's response.
Loading…