Pipeline run
715d9dea-c810-4ad6-8f2c-4aa329fa7829
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-08T06:57:58.131724Z
Updated: 2026-05-08T06:59:59.050939Z
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 clustered evidence is requirements/documentation/analysis work, with dashboarding and workflow tooling as secondary signals, which aligns best with a Business Analyst umbrella.
0
New skills
0
Skill↔dim saved
0
Role↔dim saved
16
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 Reporting
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 Documentation
d_init_01
|
— | — | — | skill_not_in_db_v3_proposed |
| Gather | new |
Requirements Gathering
d_init_01
|
— | — | — | 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 |
SaaS Product Concepts
d_init_01
|
— | — | — | skill_not_in_db_v3_proposed |
| Understanding | new |
Analytical Comprehension
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 | Gather | type=Tool subtype=data_collection_tool nature=TOOL 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=testing_methodology nature=METHODOLOGY lifespan=EVERGREEN | |
| canonical_skill_proposed | UAT | type=Methodology subtype=user_acceptance_testing nature=METHODOLOGY lifespan=EVERGREEN | |
| canonical_skill_proposed | Understanding | type=Concept subtype=comprehension nature=CONCEPT lifespan=EVERGREEN | |
| canonical_skill_proposed | Visio | type=Tool subtype=diagramming_tool nature=TOOL lifespan=EVERGREEN | |
| dimension_proposed | API Design and Integration | |
| dimension_skill_link_proposed | APIs ↔ API Design and Integration | |
| dimension_proposed | Business Intelligence Reporting | |
| dimension_skill_link_proposed | BI ↔ Business Intelligence Reporting | |
| 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 Documentation | |
| dimension_skill_link_proposed | FRDs ↔ Functional Requirements Documentation | |
| dimension_proposed | Requirements Gathering | |
| dimension_skill_link_proposed | Gather ↔ Requirements Gathering | |
| 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 | SaaS Product Concepts | |
| dimension_skill_link_proposed | SaaS ↔ SaaS Product Concepts | |
| dimension_proposed | Analytical Comprehension | |
| dimension_skill_link_proposed | Understanding ↔ Analytical Comprehension | |
| 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",
"Familiarity",
"Health",
"Hybrid",
"Job",
"Key",
"Learning",
"Location",
"Monitor",
"Power",
"Preferred",
"Qualifications",
"Remote",
"Required",
"Responsibilities",
"Role",
"Science",
"Skills",
"Support",
"Title",
"Years",
"abilities",
"candidate",
"commerce",
"company",
"degree",
"delivery",
"dependencies",
"developers",
"development",
"diagrams",
"document",
"domains",
"environment",
"field",
"gap",
"gathering",
"goals",
"growth",
"insurance",
"leaves",
"management",
"managers",
"meetings",
"needs",
"opportunities",
"problem",
"process",
"processes",
"product",
"progress",
"project",
"requirement",
"risks",
"salary",
"site",
"solutions",
"stakeholder",
"stakeholders",
"teams",
"work"
],
"final_skills": [
"Tableau",
"Argo Workflows",
"Power BI",
"APIs",
"Acceptance",
"BI",
"BRDs",
"CBAP",
"CCBA",
"Excel",
"FRDs",
"Gather",
"Knowledge",
"QA",
"SDLC",
"SaaS",
"Testing",
"UAT",
"Understanding",
"Visio",
"analysis",
"communication",
"data",
"databases",
"documentation",
"fintech",
"healthcare",
"insights",
"methodologies",
"optimization",
"reporting",
"requirements",
"software",
"specifications",
"stories",
"strategies",
"tools",
"trends",
"workshops"
],
"initial_skills": [
"Tableau",
"Argo Workflows",
"Power BI"
],
"jd_role_hint": {
"display_name": "Business Analyst",
"rationale": "The excerpt explicitly describes a Business Analyst role focused on requirements, stakeholder collaboration, documentation, and process analysis.",
"role_archetype": "Analyzes business needs, gathers requirements, and translates them into functional specifications and process improvements.",
"slug": "business-analyst"
},
"llm_non_skills": [
"2\u20135",
"Ability",
"Analyst",
"Bachelor",
"Benefits",
"Business",
"Certification",
"Computer",
"Conduct",
"Description",
"Ensure",
"Experience",
"Exposure",
"Familiarity",
"Health",
"Hybrid",
"Job",
"Key",
"Learning",
"Location",
"Monitor",
"Power",
"Preferred",
"Qualifications",
"Remote",
"Required",
"Responsibilities",
"Role",
"Science",
"Skills",
"Support",
"Title",
"Years",
"abilities",
"candidate",
"commerce",
"company",
"degree",
"delivery",
"dependencies",
"developers",
"development",
"diagrams",
"document",
"domains",
"environment",
"field",
"gap",
"gathering",
"goals",
"growth",
"insurance",
"leaves",
"management",
"managers",
"meetings",
"needs",
"opportunities",
"problem",
"process",
"processes",
"product",
"progress",
"project",
"requirement",
"risks",
"salary",
"site",
"solutions",
"stakeholder",
"stakeholders",
"teams",
"work"
],
"llm_skills": [
"APIs",
"Acceptance",
"BI",
"BRDs",
"CBAP",
"CCBA",
"Excel",
"FRDs",
"Gather",
"Knowledge",
"QA",
"SDLC",
"SaaS",
"Testing",
"UAT",
"Understanding",
"Visio",
"analysis",
"communication",
"data",
"databases",
"documentation",
"fintech",
"healthcare",
"insights",
"methodologies",
"optimization",
"reporting",
"requirements",
"software",
"specifications",
"stories",
"strategies",
"tools",
"trends",
"understanding",
"workshops"
],
"run_id": null,
"unknown_words": [
"2\u20135",
"APIs",
"Ability",
"Acceptance",
"Analyst",
"BI",
"BRDs",
"Bachelor",
"Benefits",
"Business",
"CBAP",
"CCBA",
"Career",
"Certification",
"Computer",
"Conduct",
"Description",
"Ensure",
"Excel",
"Experience",
"Exposure",
"FRDs",
"Familiarity",
"Gather",
"Health",
"Hybrid",
"Job",
"Key",
"Knowledge",
"Learning",
"Location",
"Monitor",
"Power",
"Preferred",
"QA",
"Qualifications",
"Remote",
"Required",
"Responsibilities",
"Role",
"SDLC",
"SaaS",
"Science",
"Skills",
"Support",
"Testing",
"Title",
"UAT",
"Understanding",
"User",
"Visio",
"Years",
"abilities",
"analysis",
"benefits",
"business",
"candidate",
"certification",
"commerce",
"communication",
"company",
"data",
"databases",
"degree",
"delivery",
"dependencies",
"developers",
"development",
"diagrams",
"document",
"documentation",
"domains",
"environment",
"field",
"fintech",
"gap",
"gathering",
"goals",
"growth",
"healthcare",
"insights",
"insurance",
"leaves",
"management",
"managers",
"meetings",
"methodologies",
"needs",
"opportunities",
"optimization",
"problem",
"process",
"processes",
"product",
"progress",
"project",
"reporting",
"requirement",
"requirements",
"risks",
"salary",
"site",
"skills",
"software",
"solutions",
"specifications",
"stakeholder",
"stakeholders",
"stories",
"strategies",
"teams",
"tools",
"trends",
"understanding",
"user",
"work",
"workshops"
]
}
API 2 — extract-details
{
"alias_matches": [],
"candidate_roles": [
{
"display_name": "Data 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 clustered evidence is requirements/documentation/analysis work, with dashboarding and workflow tooling as secondary signals, which aligns best with a Business Analyst umbrella.",
"role_archetype": "Analyzes business needs, gathers requirements, and translates them into functional specifications and process improvements. Often bridges stakeholders, documentation, and testing across business and technical teams.",
"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 and consuming application programming interfaces for system-to-system communication. This fits APIs because the skill centers on defining contracts, exchanging data, and connecting business processes across services.",
"slug": "d_init_01",
"source": "llm"
},
"input_skill": "APIs",
"llm_role": null,
"roles_from_db": []
},
{
"dimension": {
"difficulty_hint": null,
"display_name": "Business Intelligence Reporting",
"id": null,
"rationale": "Covers the creation and use of business-facing reports, dashboards, and KPI views that help teams monitor performance and make decisions. BI belongs here because it commonly refers to the reporting and analytics layer used by business analysts and stakeholders.",
"slug": "d_init_01",
"source": "llm"
},
"input_skill": "BI",
"llm_role": null,
"roles_from_db": []
},
{
"dimension": {
"difficulty_hint": null,
"display_name": "Business Requirements Documentation",
"id": null,
"rationale": "Covers creating and maintaining BRDs that capture business goals, scope, assumptions, constraints, and approval-ready requirements. This skill belongs here because BRDs are the standard artifact for translating stakeholder needs into a structured business specification.",
"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, including formal methods, terminology, and competency areas validated by credentialing bodies. CBAP belongs here because it is a business analysis certification rather than a technical implementation skill.",
"slug": "d_init_01",
"source": "llm"
},
"input_skill": "CBAP",
"llm_role": null,
"roles_from_db": []
},
{
"dimension": {
"difficulty_hint": null,
"display_name": "Business Analysis Certification",
"id": null,
"rationale": "Formal business analysis credentialing and professional standards for analysts. CCBA belongs here because it is a recognized certification focused on business analysis competency, techniques, and practice.",
"slug": "d_init_01",
"source": "llm"
},
"input_skill": "CCBA",
"llm_role": null,
"roles_from_db": []
},
{
"dimension": {
"difficulty_hint": null,
"display_name": "Spreadsheet Analysis and Modeling",
"id": null,
"rationale": "Using spreadsheet software to organize, analyze, and present business data. Excel belongs here because it is the primary tool for tabular analysis, formulas, pivoting, and lightweight modeling 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 Documentation",
"id": null,
"rationale": "Covers writing and maintaining functional requirement documents that define what a product or process must do. FRDs belong here because they capture business needs, scope, rules, and expected behavior in a structured specification.",
"slug": "d_init_01",
"source": "llm"
},
"input_skill": "FRDs",
"llm_role": null,
"roles_from_db": []
},
{
"dimension": {
"difficulty_hint": null,
"display_name": "Requirements Gathering",
"id": null,
"rationale": "Collecting, clarifying, and documenting business needs from stakeholders so teams can define scope and priorities. The skill Gather fits here because it commonly refers to eliciting information, questions, and constraints before analysis or delivery.",
"slug": "d_init_01",
"source": "llm"
},
"input_skill": "Gather",
"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, rules, and operating context behind requirements and analysis. For a Business Analyst, this skill helps interpret stakeholder needs, map processes, and make correct decisions in the right business context.",
"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 subskill.",
"slug": "d_init_01",
"source": "llm"
},
"input_skill": "SDLC",
"llm_role": null,
"roles_from_db": []
},
{
"dimension": {
"difficulty_hint": null,
"display_name": "SaaS Product Concepts",
"id": null,
"rationale": "Covers software delivered as a subscription service over the web, including tenant-based delivery, subscription packaging, and product capabilities common to SaaS offerings. SaaS fits here because it names the delivery and business model rather than a specific technical implementation.",
"slug": "d_init_01",
"source": "llm"
},
"input_skill": "SaaS",
"llm_role": null,
"roles_from_db": []
},
{
"dimension": {
"difficulty_hint": null,
"display_name": "Analytical Comprehension",
"id": null,
"rationale": "Ability to read, interpret, and make sense of information, requirements, and domain context. This skill belongs here because it is a foundational cognitive capability used to understand problems before analysis, design, or validation work begins.",
"slug": "d_init_01",
"source": "llm"
},
"input_skill": "Understanding",
"llm_role": null,
"roles_from_db": []
},
{
"dimension": {
"difficulty_hint": null,
"display_name": "Diagramming and Process Modeling",
"id": null,
"rationale": "Creating business and technical diagrams to communicate workflows, systems, and relationships. Visio belongs here because it is commonly used to draw process maps, org charts, network diagrams, and other structured visual artifacts 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",
"Gather",
"Knowledge",
"QA",
"SDLC",
"SaaS",
"Testing",
"UAT",
"Understanding",
"Visio",
"analysis",
"communication",
"data",
"databases",
"documentation",
"fintech",
"healthcare",
"insights",
"methodologies",
"optimization",
"reporting",
"requirements",
"software",
"specifications",
"stories",
"strategies",
"tools",
"trends",
"workshops"
],
"input_llm_skills": [
"APIs",
"Acceptance",
"BI",
"BRDs",
"CBAP",
"CCBA",
"Excel",
"FRDs",
"Gather",
"Knowledge",
"QA",
"SDLC",
"SaaS",
"Testing",
"UAT",
"Understanding",
"Visio",
"analysis",
"communication",
"data",
"databases",
"documentation",
"fintech",
"healthcare",
"insights",
"methodologies",
"optimization",
"reporting",
"requirements",
"software",
"specifications",
"stories",
"strategies",
"tools",
"trends",
"workshops"
],
"new_aliases_persisted": 0,
"run_id": "715d9dea-c810-4ad6-8f2c-4aa329fa7829",
"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 and consuming application programming interfaces for system-to-system communication. This fits APIs because the skill centers on defining contracts, exchanging data, and connecting business processes across services.",
"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",
"API gateway",
"endpoint",
"webhooks",
"rate limiting",
"versioning",
"SDK",
"microservices",
"HTTP"
]
},
"maturity": {
"confidence": 0.98,
"maturity": "well_known",
"reasoning": "APIs are a hiring-pipeline staple across backend, mobile, and platform JDs; REST/GraphQL/OpenAPI appear in large volumes and are foundational in cloud vendor docs and SDK ecosystems."
},
"skill_id": "apis",
"vendor_license": {
"confidence": 0.99,
"license": null,
"vendor": null,
"year_introduced": null
},
"versioning": {
"current_version": null,
"version_aliases": {},
"versioned": false
}
},
"locked_dimensions": [
{
"description": "Designing and consuming application programming interfaces for system-to-system communication. This fits APIs because the skill centers on defining contracts, exchanging data, and connecting business processes across services.",
"exemplar_skills": [
"APIs",
"REST APIs",
"endpoint design",
"API versioning",
"webhooks",
"service contracts",
"integration patterns"
],
"in_scope": "APIs, REST APIs, endpoint design, request and response formats, API versioning, webhooks, integration patterns, service contracts",
"name": "API Design and Integration",
"out_of_scope": "UI navigation, mobile screen behavior, database administration, authentication session management, those belong to other dimensions",
"overlap_flags": [
{
"reason": "This concept overlaps with service decomposition and inter-service communication, but the catalog does not provide a reusable API-specific dimension.",
"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",
"private-endpoints",
"acls",
"scripted-rest-api",
"outbound-rest-messages",
"mock-servers"
],
"requires": [],
"skill_id": "apis",
"suppress_on_match": []
},
"skill_id": "apis",
"split_log": [],
"typed": {
"alternatives_considered": [
"Standard: ruled out \u2014 APIs are usually an interface mechanism rather than an industry-defined compliance specification.",
"Concept: ruled out \u2014 this is a concrete interface category, not just a knowledge unit."
],
"confidence": 0.88,
"name": "APIs",
"reasoning": "APIs are best treated as a communication interface standard between systems, so under the Protocol vs Standard distinction they fit Protocol 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": false,
"confused_with": [],
"reasoning": "\u201cAcceptance\u201d is a common concept, but in typical JDs it is usually clear from context (e.g., acceptance testing, acceptance criteria). It is not a short acronym or vendor/product name likely to be mistaken for a different catalog skill."
},
"context_keywords": {
"context_keywords": [
"UAT",
"user acceptance testing",
"acceptance criteria",
"acceptance test",
"sign-off",
"go-live",
"definition of done",
"test cases",
"requirements validation",
"stakeholder approval",
"QA",
"regression testing",
"test plan",
"release readiness"
]
},
"maturity": {
"confidence": 0.86,
"maturity": "well_known",
"reasoning": "Acceptance is a standard software/testing concept; it appears broadly in job descriptions for QA, product, and agile roles, especially in terms like acceptance criteria and user acceptance testing (UAT)."
},
"skill_id": "acceptance",
"vendor_license": {
"confidence": 0.99,
"license": null,
"vendor": null,
"year_introduced": null
},
"versioning": {
"current_version": null,
"version_aliases": {},
"versioned": false
}
},
"locked_dimensions": [],
"merge_log": [
{
"into": "d_merge_01",
"into_name": "Requirements and Acceptance Validation",
"merged_from": [
"d_init_01",
"requirements-and-acceptance-validation"
],
"reasoning": "Both dims define the same skill: validating delivered behavior against requirements, user stories, and acceptance criteria. Dim A adds UAT support, defect confirmation, sign-off readiness, and business rule verification; Dim B says the same core thing and frames it as manual testing. The exemplar skills in A (Acceptance, Requirements validation, Acceptance criteria review, User acceptance testing, Sign-off readiness) all fit B exactly, so this is one cluster, not two."
}
],
"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",
"change-requests",
"contract-tests",
"defect-retest"
],
"requires": [],
"skill_id": "acceptance",
"suppress_on_match": []
},
"skill_id": "acceptance",
"split_log": [],
"typed": {
"alternatives_considered": [
"Methodology: ruled out \u2014 acceptance is not a process like Agile or TDD.",
"SoftSkill: ruled out \u2014 although the word can imply interpersonal acceptance, this skill name is more commonly a technical/product knowledge concept."
],
"confidence": 0.78,
"name": "Acceptance",
"reasoning": "By the Concept vs Methodology rule, Acceptance is best treated as a named knowledge unit about agreeing that requirements or work are acceptable, rather than a way of working or a tool.",
"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 Reporting",
"id": null,
"rationale": "Covers the creation and use of business-facing reports, dashboards, and KPI views that help teams monitor performance and make decisions. BI belongs here because it commonly refers to the reporting and analytics layer used by business analysts and stakeholders.",
"slug": "d_init_01",
"source": "llm"
},
"input_skill": "BI",
"llm_role": null,
"roles_from_db": []
}
],
"input_skill": "BI",
"matched_via": null,
"new_alias_persisted": false,
"new_alias_text": null,
"new_skill_meta": {
"derived": {
"category": "Domain",
"skill_nature": "CONCEPT",
"sub_category": "business_intelligence",
"typical_lifespan": "EVERGREEN",
"version_strategy": "NOT_APPLICABLE",
"volatility": "STABLE"
},
"enrichment": {
"ambiguity": {
"ambiguity_flag": true,
"confused_with": [
"business_intelligence"
],
"reasoning": "\"BI\" is a common abbreviation for Business Intelligence, but in JDs it can also be used generically for business/BI tooling or reporting contexts, making it easy to conflate with the fuller Business Intelligence skill entry."
},
"context_keywords": {
"context_keywords": [
"dashboard",
"KPI",
"data warehouse",
"ETL",
"OLAP",
"reporting",
"Tableau",
"Power BI",
"Looker",
"SQL",
"semantic layer",
"ad hoc analysis",
"data modeling",
"star schema",
"dimensional modeling"
]
},
"maturity": {
"confidence": 0.9,
"maturity": "well_known",
"reasoning": "BI is a common hiring keyword across analytics and data roles; job postings routinely ask for Power BI/Tableau/Looker, and major vendors continue active product investment, indicating broad market adoption."
},
"skill_id": "bi",
"vendor_license": {
"confidence": 0.98,
"license": null,
"vendor": null,
"year_introduced": null
},
"versioning": {
"current_version": null,
"version_aliases": {},
"versioned": false
}
},
"locked_dimensions": [
{
"description": "Covers the creation and use of business-facing reports, dashboards, and KPI views that help teams monitor performance and make decisions. BI belongs here because it commonly refers to the reporting and analytics layer used by business analysts and stakeholders.",
"exemplar_skills": [
"BI",
"dashboard creation",
"KPI reporting",
"report development",
"self-service analytics",
"ad hoc reporting",
"executive scorecards"
],
"in_scope": "BI, dashboards, KPI reporting, operational reports, executive scorecards, ad hoc analysis, self-service analytics, report design, metric definitions, drill-down views",
"name": "Business Intelligence Reporting",
"out_of_scope": "data engineering pipelines, statistical inference, experiment design, database administration, data governance, visualization platform administration",
"overlap_flags": [
{
"reason": "BI often uses the same reporting and dashboard artifacts, but this dimension is platform/configuration-focused rather than business-intelligence oriented.",
"with_dim_id": "reporting-and-dashboard-configuration",
"with_dim_name": null,
"with_role": null
},
{
"reason": "BI work may involve interpreting metrics, but deeper statistical analysis belongs in the analysis 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.96,
"name": "BI",
"reasoning": "BI is fundamentally a business intelligence problem-space, so by the Domain rule it is a vertical/body of knowledge rather than a tool or methodology.",
"skill_id": "bi",
"subtype": "business_intelligence",
"type": "Domain"
},
"warnings": []
},
"source_tag": "llm",
"was_in_llm_skills": true
},
{
"aliases_in_db": [],
"canonical": null,
"dimensions": [
{
"dimension": {
"difficulty_hint": null,
"display_name": "Business Requirements Documentation",
"id": null,
"rationale": "Covers creating and maintaining BRDs that capture business goals, scope, assumptions, constraints, and approval-ready requirements. This skill belongs here because BRDs are the standard artifact for translating stakeholder needs into a structured business specification.",
"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 clear from context and not easily mistaken for a different catalog skill."
},
"context_keywords": {
"context_keywords": [
"requirements gathering",
"stakeholder interviews",
"scope definition",
"functional requirements",
"non-functional requirements",
"use cases",
"user stories",
"acceptance criteria",
"process flows",
"gap analysis",
"traceability matrix",
"sign-off",
"business analysis",
"solution design",
"requirements elicitation"
]
},
"maturity": {
"confidence": 0.86,
"maturity": "well_known",
"reasoning": "BRDs are a standard artifact in business analysis and product roles; job descriptions commonly ask for requirements gathering and business requirements documentation, and they remain a common deliverable in enterprise SDLCs."
},
"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 approval-ready requirements. This skill belongs here because BRDs are the standard artifact for translating stakeholder needs into a structured business specification.",
"exemplar_skills": [
"BRDs",
"Business Requirements Documents",
"Requirements Documentation",
"Scope Definition",
"Stakeholder Requirements Gathering",
"Requirements Traceability",
"Business Analysis Documentation"
],
"in_scope": "BRDs, business requirements documents, scope statements, business objectives, stakeholder needs, assumptions and constraints, high-level requirements, approval workflows, requirement traceability",
"name": "Business Requirements Documentation",
"out_of_scope": "User stories and acceptance criteria, which belong to requirements and acceptance validation; technical design specs and solution architecture, which belong to architecture and engineering design; test cases and QA execution, which belong to validation and testing",
"overlap_flags": [
{
"reason": "BRDs often feed downstream acceptance criteria, but the BRD itself is the upstream business specification rather than validation of implemented behavior.",
"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 in requirements gathering, so they fit Concept rather than Methodology or Format.",
"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, including formal methods, terminology, and competency areas validated by credentialing bodies. CBAP belongs here because it is a business analysis certification rather than a technical implementation skill.",
"slug": "d_init_01",
"source": "llm"
},
"input_skill": "CBAP",
"llm_role": null,
"roles_from_db": []
}
],
"input_skill": "CBAP",
"matched_via": null,
"new_alias_persisted": false,
"new_alias_text": null,
"new_skill_meta": {
"derived": {
"category": "Certification",
"skill_nature": "CREDENTIAL",
"sub_category": "business_analysis_professional_certification",
"typical_lifespan": "EVERGREEN",
"version_strategy": "NOT_APPLICABLE",
"volatility": "STABLE"
},
"enrichment": {
"ambiguity": {
"ambiguity_flag": false,
"confused_with": [],
"reasoning": "CBAP is a specific certification acronym (Certified Business Analysis Professional) and is unlikely to be reasonably confused with another catalog skill in typical job descriptions."
},
"context_keywords": {
"context_keywords": [
"BABOK",
"IIBA",
"requirements elicitation",
"stakeholder analysis",
"process modeling",
"use cases",
"user stories",
"gap analysis",
"business process improvement",
"UML",
"SWOT analysis",
"traceability matrix",
"functional requirements",
"workshops",
"facilitation"
]
},
"maturity": {
"confidence": 0.84,
"maturity": "well_known",
"reasoning": "CBAP appears frequently in business analyst job descriptions and certification requirements, especially in enterprise BA roles; IIBA continues to maintain and promote it as a standard credential."
},
"skill_id": "cbap",
"vendor_license": {
"confidence": 0.97,
"license": null,
"vendor": "International Institute of Business Analysis",
"year_introduced": 2006
},
"versioning": {
"current_version": null,
"version_aliases": {},
"versioned": false
}
},
"locked_dimensions": [
{
"description": "Professional certification knowledge for business analysts, including formal methods, terminology, and competency areas validated by credentialing bodies. CBAP belongs here because it is a business analysis certification rather than a technical implementation skill.",
"exemplar_skills": [
"CBAP",
"CCBA",
"ECBA",
"BABOK",
"business analysis certification prep",
"business analysis competencies"
],
"in_scope": "CBAP, CCBA, ECBA, business analysis certification prep, BABOK knowledge areas, business analysis competencies, certification exam study",
"name": "Business Analysis Certification",
"out_of_scope": "requirements elicitation techniques, user story writing, process modeling notation, stakeholder analysis practice, project management certification",
"overlap_flags": [
{
"reason": "Business analysis certifications often cover requirements work, but this dimension is about the credential and exam domain rather than validating implemented requirements.",
"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 not a concept or methodology but a certification.",
"skill_id": "cbap",
"subtype": "business_analysis_professional_certification",
"type": "Certification"
},
"warnings": []
},
"source_tag": "llm",
"was_in_llm_skills": true
},
{
"aliases_in_db": [],
"canonical": null,
"dimensions": [
{
"dimension": {
"difficulty_hint": null,
"display_name": "Business Analysis Certification",
"id": null,
"rationale": "Formal business analysis credentialing and professional standards for analysts. CCBA belongs here because it is a recognized certification focused on business analysis competency, techniques, and practice.",
"slug": "d_init_01",
"source": "llm"
},
"input_skill": "CCBA",
"llm_role": null,
"roles_from_db": []
}
],
"input_skill": "CCBA",
"matched_via": null,
"new_alias_persisted": false,
"new_alias_text": null,
"new_skill_meta": {
"derived": {
"category": "Certification",
"skill_nature": "CREDENTIAL",
"sub_category": "business_analysis_certification",
"typical_lifespan": "EVERGREEN",
"version_strategy": "NOT_APPLICABLE",
"volatility": "STABLE"
},
"enrichment": {
"ambiguity": {
"ambiguity_flag": true,
"confused_with": [
"cbap"
],
"reasoning": "CCBA is a business analysis certification acronym and can be mistaken for the closely related CBAP certification in job descriptions, especially when abbreviations are listed without expansion."
},
"context_keywords": {
"context_keywords": [
"BABOK",
"IIBA",
"business analysis",
"requirements elicitation",
"requirements management",
"stakeholder analysis",
"process modeling",
"use cases",
"user stories",
"gap analysis",
"traceability matrix",
"solution assessment",
"elicitation techniques",
"SWOT analysis",
"MoSCoW"
]
},
"maturity": {
"confidence": 0.84,
"maturity": "well_known",
"reasoning": "CCBA is a widely recognized business analysis certification; it appears in many job descriptions for BA roles and is offered by IIBA as a mainstream credential alongside CBAP."
},
"skill_id": "ccba",
"vendor_license": {
"confidence": 0.92,
"license": null,
"vendor": "International Institute of Business Analysis",
"year_introduced": 2008
},
"versioning": {
"current_version": null,
"version_aliases": {},
"versioned": false
}
},
"locked_dimensions": [
{
"description": "Formal business analysis credentialing and professional standards for analysts. CCBA belongs here because it is a recognized certification focused on business analysis competency, techniques, and practice.",
"exemplar_skills": [
"CCBA",
"CBAP",
"ECBA",
"IIBA certification",
"business analysis certification",
"requirements elicitation",
"stakeholder analysis"
],
"in_scope": "CCBA, CBAP, ECBA, business analysis certification, IIBA certification, business analysis competency, requirements elicitation, stakeholder analysis, process modeling",
"name": "Business Analysis Certification",
"out_of_scope": "requirements gathering as a day-to-day practice, acceptance testing, product management, project management, data analysis, software development, which belong to other role or delivery dimensions",
"overlap_flags": [
{
"reason": "Both touch requirements, but this dimension is about formal certification and professional standards rather than validating implemented behavior.",
"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": [],
"requires": [],
"skill_id": "ccba",
"suppress_on_match": []
},
"skill_id": "ccba",
"split_log": [],
"typed": {
"alternatives_considered": [],
"confidence": 0.99,
"name": "CCBA",
"reasoning": "CCBA is a formal third-party credential, so by the Certification rule it is a Certification rather than a concept or methodology.",
"skill_id": "ccba",
"subtype": "business_analysis_certification",
"type": "Certification"
},
"warnings": []
},
"source_tag": "llm",
"was_in_llm_skills": true
},
{
"aliases_in_db": [],
"canonical": null,
"dimensions": [
{
"dimension": {
"difficulty_hint": null,
"display_name": "Spreadsheet Analysis and Modeling",
"id": null,
"rationale": "Using spreadsheet software to organize, analyze, and present business data. Excel belongs here because it is the primary tool for tabular analysis, formulas, pivoting, and lightweight modeling 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 is a well-known spreadsheet application and, in typical JDs, is unlikely to be confused with a different catalog skill."
},
"context_keywords": {
"context_keywords": [
"PivotTables",
"VLOOKUP",
"XLOOKUP",
"INDEX-MATCH",
"Power Query",
"Power Pivot",
"macros",
"VBA",
"conditional formatting",
"data validation",
"charts",
"dashboards",
"SUMIFS",
"COUNTIFS",
"CSV"
]
},
"maturity": {
"confidence": 0.98,
"maturity": "well_known",
"reasoning": "Excel appears in a very large share of business, finance, ops, and analyst job descriptions; Microsoft continues active support and it remains a standard spreadsheet tool rather than a sunset product."
},
"skill_id": "excel",
"vendor_license": {
"confidence": 0.99,
"license": "proprietary",
"vendor": "Microsoft",
"year_introduced": 1985
},
"versioning": {
"current_version": "Microsoft 365 / Excel 2024",
"version_aliases": {
"Excel 2007": "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 spreadsheet software to organize, analyze, and present business data. Excel belongs here because it is the primary tool for tabular analysis, formulas, pivoting, and lightweight modeling in analyst workflows.",
"exemplar_skills": [
"Excel",
"Pivot Tables",
"VLOOKUP",
"XLOOKUP",
"Conditional Formatting",
"What-If Analysis",
"Data Validation"
],
"in_scope": "Excel, formulas and functions, pivot tables, charts, filters and sorting, conditional formatting, lookup functions, data validation, what-if analysis, basic financial and operational models",
"name": "Spreadsheet Analysis and Modeling",
"out_of_scope": "Statistical inference and hypothesis testing, BI dashboard platforms, database querying, programming-language automation, data engineering pipelines",
"overlap_flags": [
{
"reason": "Excel is often used for basic analysis, but deeper statistical interpretation belongs in the statistics dimension.",
"with_dim_id": "statistical-reasoning-for-analysis",
"with_dim_name": null,
"with_role": null
},
{
"reason": "Excel can produce reports and dashboards, but platform-specific dashboard configuration is a separate 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"
],
"requires": [],
"skill_id": "excel",
"suppress_on_match": []
},
"skill_id": "excel",
"split_log": [],
"typed": {
"alternatives_considered": [],
"confidence": 0.98,
"name": "Excel",
"reasoning": "Excel is software you operate directly as a user rather than a hosted environment or code package, so under the Tool vs Framework rule it is a Tool.",
"skill_id": "excel",
"subtype": "spreadsheet_software",
"type": "Tool"
},
"warnings": []
},
"source_tag": "llm",
"was_in_llm_skills": true
},
{
"aliases_in_db": [],
"canonical": null,
"dimensions": [
{
"dimension": {
"difficulty_hint": null,
"display_name": "Functional Requirements Documentation",
"id": null,
"rationale": "Covers writing and maintaining functional requirement documents that define what a product or process must do. FRDs belong here because they capture business needs, scope, rules, and expected behavior in a structured specification.",
"slug": "d_init_01",
"source": "llm"
},
"input_skill": "FRDs",
"llm_role": null,
"roles_from_db": []
}
],
"input_skill": "FRDs",
"matched_via": null,
"new_alias_persisted": false,
"new_alias_text": null,
"new_skill_meta": {
"derived": {
"category": "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 different catalog skill."
},
"context_keywords": {
"context_keywords": [
"BRD",
"PRD",
"use cases",
"user stories",
"acceptance criteria",
"functional specification",
"requirements traceability",
"scope definition",
"business rules",
"process flows",
"wireframes",
"stakeholder review",
"sign-off",
"change requests",
"UAT"
]
},
"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 writing and maintaining functional requirement documents that define what a product or process must do. FRDs belong here because they capture business needs, scope, rules, and expected behavior in a structured specification.",
"exemplar_skills": [
"FRDs",
"functional requirements documentation",
"business requirements gathering",
"use case writing",
"acceptance criteria definition",
"process mapping"
],
"in_scope": "FRDs, functional requirements documents, business rules, scope statements, use cases, acceptance criteria, process flows, requirement traceability",
"name": "Functional Requirements Documentation",
"out_of_scope": "Technical design specs, API implementation details, test execution, and release planning, which belong to engineering design, validation, or delivery dimensions.",
"overlap_flags": [
{
"reason": "FRDs often feed acceptance validation, but this dimension is about authoring the 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 are primarily a requirements artifact rather than a data structure or wire format.",
"Domain: ruled out \u2014 FRDs are not an industry or problem-space body of knowledge."
],
"confidence": 0.78,
"name": "FRDs",
"reasoning": "FRDs are a named knowledge artifact describing requirements, so by the Concept vs Methodology rule they are best treated as a 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": "Requirements Gathering",
"id": null,
"rationale": "Collecting, clarifying, and documenting business needs from stakeholders so teams can define scope and priorities. The skill Gather fits here because it commonly refers to eliciting information, questions, and constraints before analysis or delivery.",
"slug": "d_init_01",
"source": "llm"
},
"input_skill": "Gather",
"llm_role": null,
"roles_from_db": []
}
],
"input_skill": "Gather",
"matched_via": null,
"new_alias_persisted": false,
"new_alias_text": null,
"new_skill_meta": {
"derived": {
"category": "Tool",
"skill_nature": "TOOL",
"sub_category": "data_collection_tool",
"typical_lifespan": "EVERGREEN",
"version_strategy": "NOT_APPLICABLE",
"volatility": "STABLE"
},
"enrichment": {
"ambiguity": {
"ambiguity_flag": true,
"confused_with": [
"gathering"
],
"reasoning": "\u201cGather\u201d is a generic verb and can be mistaken for the related catalog skill \u201cgathering\u201d in JDs, especially when listed as a tool/process name rather than a product."
},
"context_keywords": {
"context_keywords": [
"survey design",
"questionnaire",
"respondent",
"sampling",
"fieldwork",
"data collection",
"interview guide",
"focus group",
"panel management",
"crosstab",
"response rate",
"skip logic",
"quota",
"data capture",
"research instrument"
]
},
"maturity": {
"confidence": 0.78,
"maturity": "niche",
"reasoning": "Low JD volume and limited ecosystem adoption; Gather appears mainly in specialized data-collection workflows rather than broad engineering stacks, with far fewer listings than mainstream tools."
},
"skill_id": "gather",
"vendor_license": {
"confidence": 0.86,
"license": "mit",
"vendor": "pytest-dev",
"year_introduced": 2004
},
"versioning": {
"current_version": null,
"version_aliases": {},
"versioned": false
}
},
"locked_dimensions": [
{
"description": "Collecting, clarifying, and documenting business needs from stakeholders so teams can define scope and priorities. The skill Gather fits here because it commonly refers to eliciting information, questions, and constraints before analysis or delivery.",
"exemplar_skills": [
"Gather",
"requirements gathering",
"requirements elicitation",
"stakeholder interviews",
"workshop facilitation",
"needs assessment",
"business rules capture"
],
"in_scope": "Gather, requirements elicitation, stakeholder interviews, workshops, surveys, process discovery, needs assessment, scope clarification, business rules capture, user story drafting, acceptance criteria discovery",
"name": "Requirements Gathering",
"out_of_scope": "Requirements validation against delivered work, test case execution, data profiling, project planning, solution design, which belong to validation, testing, analytics, or architecture dimensions",
"overlap_flags": [
{
"reason": "Both involve requirements, but this dimension is about discovering and documenting needs rather than checking implemented behavior.",
"with_dim_id": "requirements-and-acceptance-validation",
"with_dim_name": null,
"with_role": null
}
],
"tentative_id": "d_init_01"
}
],
"merge_log": [],
"placed": {
"name": "Gather",
"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": "gather"
},
"relationships": {
"child_skills": [],
"parent_skills": [],
"related_to": [],
"requires": [],
"skill_id": "gather",
"suppress_on_match": []
},
"skill_id": "gather",
"split_log": [],
"typed": {
"alternatives_considered": [
"Framework: ruled out \u2014 it is not a codebase you build applications inside.",
"Platform: ruled out \u2014 it is not a hosted multi-tenant environment with APIs.",
"Concept: ruled out \u2014 it is a concrete piece of software, not a knowledge unit."
],
"confidence": 0.78,
"name": "Gather",
"reasoning": "Gather is best classified as a Tool because it is software you operate directly rather than a hosted platform, library, or framework.",
"skill_id": "gather",
"subtype": "data_collection_tool",
"type": "Tool"
},
"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, rules, and operating context behind requirements and analysis. For a Business Analyst, this skill helps interpret stakeholder needs, map processes, and make correct decisions in the right business context.",
"slug": "d_init_01",
"source": "llm"
},
"input_skill": "Knowledge",
"llm_role": null,
"roles_from_db": []
}
],
"input_skill": "Knowledge",
"matched_via": null,
"new_alias_persisted": false,
"new_alias_text": null,
"new_skill_meta": {
"derived": {
"category": "Concept",
"skill_nature": "CONCEPT",
"sub_category": "general_knowledge",
"typical_lifespan": "EVERGREEN",
"version_strategy": "NOT_APPLICABLE",
"volatility": "STABLE"
},
"enrichment": {
"ambiguity": {
"ambiguity_flag": true,
"confused_with": [
"knowledge_management",
"knowledge_graph",
"knowledge_base"
],
"reasoning": "\"Knowledge\" is a very broad concept and in JDs could refer to knowledge management, knowledge graphs, or a knowledge base rather than the generic concept."
},
"context_keywords": {
"context_keywords": [
"domain expertise",
"subject matter expert",
"SME",
"institutional knowledge",
"knowledge base",
"knowledge management",
"knowledge transfer",
"taxonomy",
"ontology",
"information architecture",
"documentation",
"wiki",
"lessons learned",
"best practices",
"expertise"
]
},
"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 or measurable hiring keyword compared with concrete tools/stack terms."
},
"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, rules, and operating context behind requirements and analysis. For a Business Analyst, this skill helps interpret stakeholder needs, map processes, and make correct decisions in the right business context.",
"exemplar_skills": [
"Knowledge",
"business domain knowledge",
"subject-matter expertise",
"industry terminology",
"business rules understanding"
],
"in_scope": "Knowledge, business domain knowledge, industry terminology, business rules, process context, stakeholder context, product context, regulatory context, operational context, subject-matter understanding",
"name": "Domain Knowledge and Business Context",
"out_of_scope": "Requirements elicitation and documentation, process modeling, data analysis, project planning, which belong to separate analysis or delivery dimensions",
"overlap_flags": [
{
"reason": "Business knowledge often informs requirement interpretation, but this dimension is about validating behavior against stated requirements rather than knowing the domain.",
"with_dim_id": "requirements-and-acceptance-validation",
"with_dim_name": null,
"with_role": null
},
{
"reason": "Some business knowledge overlaps with data stewardship and policy awareness, but governance focuses on controlling data access and handling.",
"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 knowledge unit rather than a way of working, so by the Concept vs Methodology rule it fits Concept.",
"skill_id": "knowledge",
"subtype": "general_knowledge",
"type": "Concept"
},
"warnings": []
},
"source_tag": "llm",
"was_in_llm_skills": true
},
{
"aliases_in_db": [],
"canonical": null,
"dimensions": [],
"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; the catalog likely has the full quality assurance skill, so an extractor could conflate the abbreviation with that entry."
},
"context_keywords": {
"context_keywords": [
"test cases",
"test plans",
"regression testing",
"UAT",
"bug tracking",
"defect triage",
"test automation",
"manual testing",
"acceptance criteria",
"test scripts",
"JIRA",
"Selenium",
"smoke testing",
"traceability matrix"
]
},
"maturity": {
"confidence": 0.95,
"maturity": "well_known",
"reasoning": "QA appears in a large share of software job descriptions and is a standard hiring requirement across product teams, with dedicated QA/test engineer roles and widespread use of test automation in CI/CD."
},
"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, Acceptance, and User Story Validation",
"merged_from": [
"d_init_01",
"requirements-and-acceptance-validation"
],
"reasoning": "Dim A and Dim B describe the same conceptual cluster: validating delivered/implemented behavior against documented requirements, user stories, and acceptance criteria. The descriptions are nearly identical in substance, and the exemplar skills in A \u2014 \"QA\", \"requirements validation\", \"acceptance testing\", \"user story verification\", and \"UAT support\" \u2014 all map directly to the same activity described in B. The small wording difference between \"delivered work\" and \"implemented behavior\" does not create a distinct skill boundary; both refer to checking that what was built matches what was specified. Because B has no additional scope beyond the same validation activity, this is not a case for SPLIT or KEEP_SEPARATE."
},
{
"into": "d_merge_02",
"into_name": "Frontend Testing and Quality Assurance",
"merged_from": [
"d_init_02",
"frontend-testing-and-quality"
],
"reasoning": "Both dims target the same frontend quality cluster. A covers QA, UI/component testing, end-to-end/regression testing, browser compatibility, and user-flow test cases; B covers the same UI behavior and component correctness plus unit/integration testing for frontend code. The difference is breadth and wording, not a distinct skill boundary, so MERGE is appropriate."
}
],
"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 and is commonly used as an operational practice/discipline rather than a named methodology.",
"Concept: ruled out \u2014 QA is not primarily a theoretical knowledge unit but an applied practice focused on ensuring quality."
],
"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 subskill.",
"slug": "d_init_01",
"source": "llm"
},
"input_skill": "SDLC",
"llm_role": null,
"roles_from_db": []
}
],
"input_skill": "SDLC",
"matched_via": null,
"new_alias_persisted": false,
"new_alias_text": null,
"new_skill_meta": {
"derived": {
"category": "Methodology",
"skill_nature": "METHODOLOGY",
"sub_category": "software_development_lifecycle",
"typical_lifespan": "EVERGREEN",
"version_strategy": "NOT_APPLICABLE",
"volatility": "STABLE"
},
"enrichment": {
"ambiguity": {
"ambiguity_flag": false,
"confused_with": [],
"reasoning": "SDLC is a standard, well-known acronym for software development lifecycle and is usually unambiguous in job descriptions."
},
"context_keywords": {
"context_keywords": [
"requirements gathering",
"design review",
"implementation",
"code review",
"testing",
"QA",
"UAT",
"deployment",
"release management",
"change management",
"Agile",
"Scrum",
"waterfall",
"CI/CD",
"version control"
]
},
"maturity": {
"confidence": 0.96,
"maturity": "well_known",
"reasoning": "SDLC is a standard term in software job descriptions and engineering interviews, with widespread use across Agile, Waterfall, and DevOps process docs; it is not tied to a sunset technology."
},
"skill_id": "sdlc",
"vendor_license": {
"confidence": 0.99,
"license": null,
"vendor": null,
"year_introduced": null
},
"versioning": {
"current_version": null,
"version_aliases": {},
"versioned": false
}
},
"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 subskill.",
"exemplar_skills": [
"SDLC",
"software development lifecycle",
"software delivery lifecycle",
"requirements gathering",
"release management",
"change control"
],
"in_scope": "SDLC, requirements gathering, design, implementation, testing, release management, maintenance, change control, versioning, development process, delivery lifecycle",
"name": "Software Development Lifecycle",
"out_of_scope": "Specific test case design and execution, which belongs to requirements-and-acceptance-validation; 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 testing and acceptance, but that catalog dimension is specifically about validating implemented behavior against requirements.",
"with_dim_id": "requirements-and-acceptance-validation",
"with_dim_name": null,
"with_role": null
},
{
"reason": "SDLC can include release activities, but that dimension is narrower and focused on build/signing/packaging mechanics.",
"with_dim_id": "build-configuration-and-release",
"with_dim_name": null,
"with_role": null
},
{
"reason": "SDLC includes maintenance, but incident response is a distinct operational recovery discipline.",
"with_dim_id": "incident-response-and-remediation",
"with_dim_name": null,
"with_role": null
}
],
"tentative_id": "d_init_01"
}
],
"merge_log": [],
"placed": {
"name": "SDLC",
"placement_confidence": 0.92,
"primary_dimension": "d_init_01",
"reasoning": "Deterministic JD placement: locked_dimensions has 1 dimension(s) from skill-driven dimension generation after reconciliation; primary_dimension is the first locked dim.",
"secondary_dimensions": [],
"skill_id": "sdlc"
},
"relationships": {
"child_skills": [],
"parent_skills": [],
"related_to": [
"acceptance-criteria-checks",
"acceptance-criteria-validation",
"defect-retest",
"dependency-mapping",
"dashboards",
"scorecards"
],
"requires": [],
"skill_id": "sdlc",
"suppress_on_match": []
},
"skill_id": "sdlc",
"split_log": [],
"typed": {
"alternatives_considered": [],
"confidence": 0.88,
"name": "SDLC",
"reasoning": "SDLC is best treated as a Methodology because it describes the process and phases for how software is developed and delivered, matching the Concept vs Methodology rule.",
"skill_id": "sdlc",
"subtype": "software_development_lifecycle",
"type": "Methodology"
},
"warnings": []
},
"source_tag": "llm",
"was_in_llm_skills": true
},
{
"aliases_in_db": [],
"canonical": null,
"dimensions": [
{
"dimension": {
"difficulty_hint": null,
"display_name": "SaaS Product Concepts",
"id": null,
"rationale": "Covers software delivered as a subscription service over the web, including tenant-based delivery, subscription packaging, and product capabilities common to SaaS offerings. SaaS fits here because it names the delivery and business model rather than a specific technical implementation.",
"slug": "d_init_01",
"source": "llm"
},
"input_skill": "SaaS",
"llm_role": null,
"roles_from_db": []
}
],
"input_skill": "SaaS",
"matched_via": null,
"new_alias_persisted": false,
"new_alias_text": null,
"new_skill_meta": {
"derived": {
"category": "Platform",
"skill_nature": "PLATFORM",
"sub_category": "software_as_a_service_platform",
"typical_lifespan": "EVERGREEN",
"version_strategy": "NOT_APPLICABLE",
"volatility": "STABLE"
},
"enrichment": {
"ambiguity": {
"ambiguity_flag": false,
"confused_with": [],
"reasoning": "SaaS is a standard, well-scoped term for software-as-a-service platforms; in JDs it is unlikely to be mistaken for a different catalog skill."
},
"context_keywords": {
"context_keywords": [
"multi-tenant",
"subscription billing",
"tenant isolation",
"self-service onboarding",
"usage-based pricing",
"provisioning",
"SAML",
"SSO",
"RBAC",
"API integrations",
"webhooks",
"SLAs",
"churn",
"customer lifecycle",
"feature flags"
]
},
"maturity": {
"confidence": 0.96,
"maturity": "well_known",
"reasoning": "SaaS is a standard deployment model in job postings across product, sales, and engineering roles; major vendors like Salesforce, Microsoft, and Google market SaaS offerings broadly, indicating mainstream adoption."
},
"skill_id": "saas",
"vendor_license": {
"confidence": 0.88,
"license": null,
"vendor": null,
"year_introduced": 1999
},
"versioning": {
"current_version": null,
"version_aliases": {},
"versioned": false
}
},
"locked_dimensions": [
{
"description": "Covers software delivered as a subscription service over the web, including tenant-based delivery, subscription packaging, and product capabilities common to SaaS offerings. SaaS fits here because it names the delivery and business model rather than a specific technical implementation.",
"exemplar_skills": [
"SaaS",
"software as a service",
"subscription software",
"multi-tenant SaaS",
"web-based product delivery",
"SaaS onboarding"
],
"in_scope": "SaaS, software as a service, subscription software, multi-tenant product delivery, web-delivered application access, usage-based plans, seat-based licensing, customer onboarding for SaaS, SaaS feature packaging",
"name": "SaaS Product Concepts",
"out_of_scope": "Cloud infrastructure provisioning, backend service implementation, identity configuration, billing system implementation, which belong to platform, engineering, or operations dimensions",
"overlap_flags": [
{
"reason": "SaaS solutions are frequently hosted on cloud platforms, but hosting choice is separate from the SaaS business/product model.",
"with_dim_id": "cloud-platform-service-selection",
"with_dim_name": null,
"with_role": null
}
],
"tentative_id": "d_init_01"
}
],
"merge_log": [
{
"into": "d_merge_01",
"into_name": "Service Architecture and Integration",
"merged_from": [
"d_init_02",
"service-architecture-and-integration"
],
"reasoning": "Both dims describe the same backend/system-design cluster: service-based architecture plus integration across internal/external dependencies. A\u2019s exemplars (service architecture, API integration, microservices, tenant-aware architecture, external system integration) match B\u2019s description of decomposing services and coordinating calls safely. A\u2019s SaaS note is just a contextual example of the same architecture, not a separate skill cluster."
}
],
"placed": {
"name": "SaaS",
"placement_confidence": 0.92,
"primary_dimension": "d_init_01",
"reasoning": "Deterministic JD placement: locked_dimensions has 1 dimension(s) from skill-driven dimension generation after reconciliation; primary_dimension is the first locked dim.",
"secondary_dimensions": [],
"skill_id": "saas"
},
"relationships": {
"child_skills": [],
"parent_skills": [],
"related_to": [
"cloud-run",
"cspm",
"policy-as-code",
"cloud-reference-architecture"
],
"requires": [],
"skill_id": "saas",
"suppress_on_match": []
},
"skill_id": "saas",
"split_log": [],
"typed": {
"alternatives_considered": [
"Service: ruled out \u2014 SaaS is the broader hosted environment rather than a specific managed capability inside another platform."
],
"confidence": 0.93,
"name": "SaaS",
"reasoning": "By the Platform vs Tool rule, SaaS is a hosted multi-tenant environment delivered over APIs and managed by the provider, so it is fundamentally a Platform.",
"skill_id": "saas",
"subtype": "software_as_a_service_platform",
"type": "Platform"
},
"warnings": []
},
"source_tag": "llm",
"was_in_llm_skills": true
},
{
"aliases_in_db": [],
"canonical": null,
"dimensions": [],
"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": "testing_methodology",
"typical_lifespan": "EVERGREEN",
"version_strategy": "NOT_APPLICABLE",
"volatility": "STABLE"
},
"enrichment": {
"ambiguity": {
"ambiguity_flag": true,
"confused_with": [
"unit_testing",
"integration_testing",
"software_testing"
],
"reasoning": "\"Testing\" is very broad in JDs and can refer to specific testing methodologies like unit or integration testing, or general software testing rather than this exact catalog entry."
},
"context_keywords": {
"context_keywords": [
"unit testing",
"integration testing",
"test automation",
"test cases",
"regression testing",
"smoke testing",
"mocking",
"assertions",
"test coverage",
"TDD",
"BDD",
"JUnit",
"pytest",
"Selenium",
"CI/CD"
]
},
"maturity": {
"confidence": 0.97,
"maturity": "well_known",
"reasoning": "Testing is a standard requirement in most software JDs and appears across GitHub/CI tooling ecosystems; it\u2019s a hiring-pipeline staple 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": [
{
"into": "d_merge_01",
"into_name": "Requirements and Acceptance Validation",
"merged_from": [
"d_init_01",
"requirements-and-acceptance-validation"
],
"reasoning": "Dim A and Dim B are the same conceptual cluster: both define manual validation of implemented behavior against documented requirements, user stories, and acceptance criteria. The descriptions are nearly identical, and Dim A\u2019s exemplars like Acceptance Testing, User Acceptance Testing, Requirements Validation, and Business Rule Validation match Dim B\u2019s stated focus on understanding whether the product does what it is supposed to do. The in-scope items in A (testing, acceptance testing, user story validation, requirements traceability, UAT support, checklist-based verification, defect logging) all belong to the same business-analysis validation activity described in B. There is no evidence of a broader umbrella that should be split, and no distinct skill boundary between them."
}
],
"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",
"cross-browser-testing",
"smoke-testing",
"fuzzing",
"charter-based-testing",
"session-based-testing",
"restore-testing",
"defect-retest",
"acceptance-criteria-validation",
"test-case-authoring",
"health-checks",
"contract-tests"
],
"requires": [],
"skill_id": "testing",
"suppress_on_match": []
},
"skill_id": "testing",
"split_log": [],
"typed": {
"alternatives_considered": [],
"confidence": 0.93,
"name": "Testing",
"reasoning": "Testing is fundamentally a way of working for validating software behavior, so by the Concept vs Methodology rule it fits Methodology rather than a tool or concept.",
"skill_id": "testing",
"subtype": "testing_methodology",
"type": "Methodology"
},
"warnings": [
"placement_stub_no_locked_dimensions"
]
},
"source_tag": "llm",
"was_in_llm_skills": true
},
{
"aliases_in_db": [],
"canonical": null,
"dimensions": [],
"input_skill": "UAT",
"matched_via": null,
"new_alias_persisted": false,
"new_alias_text": null,
"new_skill_meta": {
"derived": {
"category": "Methodology",
"skill_nature": "METHODOLOGY",
"sub_category": "user_acceptance_testing",
"typical_lifespan": "EVERGREEN",
"version_strategy": "NOT_APPLICABLE",
"volatility": "STABLE"
},
"enrichment": {
"ambiguity": {
"ambiguity_flag": false,
"confused_with": [],
"reasoning": "UAT in JDs almost always means User Acceptance Testing; the acronym is standard and unlikely to be mistaken for another catalog skill in typical hiring context."
},
"context_keywords": {
"context_keywords": [
"test cases",
"acceptance criteria",
"business users",
"end users",
"test scripts",
"sign-off",
"test plan",
"defect triage",
"test scenarios",
"regression testing",
"stakeholder review",
"go-live",
"test environment",
"UAT cycle",
"requirements validation"
]
},
"maturity": {
"confidence": 0.86,
"maturity": "well_known",
"reasoning": "UAT appears routinely in QA/BA job descriptions and enterprise delivery checklists as a standard pre-release signoff step; it is broadly adopted rather than a niche tool."
},
"skill_id": "uat",
"vendor_license": {
"confidence": 0.99,
"license": null,
"vendor": null,
"year_introduced": null
},
"versioning": {
"current_version": null,
"version_aliases": {},
"versioned": false
}
},
"locked_dimensions": [],
"merge_log": [
{
"into": "d_merge_01",
"into_name": "Requirements and Acceptance Validation",
"merged_from": [
"d_init_01",
"requirements-and-acceptance-validation"
],
"reasoning": "Dim A and Dim B describe the same conceptual cluster: validating delivered functionality against documented requirements, user stories, and acceptance criteria. Both descriptions center on checking implemented behavior against what was specified, and both explicitly include UAT/user acceptance testing and acceptance criteria validation as core examples. Dim A\u2019s exemplars (UAT, business sign-off testing, stakeholder walkthroughs, defect confirmation against requirements) are all direct instances of the same business-facing verification described in Dim B (\u201cchecking that implemented behavior matches documented requirements, user stories, and acceptance criteria\u201d). The cross-role label does not indicate a different skill here; the wording is nearly identical and the substance is the same."
}
],
"placed": {
"name": "UAT",
"placement_confidence": 0.0,
"primary_dimension": "d_init_00",
"reasoning": "Stub placement: no locked_dimensions after Stage 2/3; downstream containment and enrichment use placeholders only.",
"secondary_dimensions": [],
"skill_id": "uat"
},
"relationships": {
"child_skills": [],
"parent_skills": [],
"related_to": [
"acceptance-criteria-checks",
"session-based-testing",
"test-case-authoring"
],
"requires": [],
"skill_id": "uat",
"suppress_on_match": []
},
"skill_id": "uat",
"split_log": [],
"typed": {
"alternatives_considered": [],
"confidence": 0.93,
"name": "UAT",
"reasoning": "UAT is a way of working 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": [
"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": "Analytical Comprehension",
"id": null,
"rationale": "Ability to read, interpret, and make sense of information, requirements, and domain context. This skill belongs here because it is a foundational cognitive capability used to understand problems before analysis, design, or validation work begins.",
"slug": "d_init_01",
"source": "llm"
},
"input_skill": "Understanding",
"llm_role": null,
"roles_from_db": []
}
],
"input_skill": "Understanding",
"matched_via": null,
"new_alias_persisted": false,
"new_alias_text": null,
"new_skill_meta": {
"derived": {
"category": "Concept",
"skill_nature": "CONCEPT",
"sub_category": "comprehension",
"typical_lifespan": "EVERGREEN",
"version_strategy": "NOT_APPLICABLE",
"volatility": "STABLE"
},
"enrichment": {
"ambiguity": {
"ambiguity_flag": true,
"confused_with": [
"understanding_user_needs",
"understanding_business_requirements"
],
"reasoning": "\"Understanding\" is a generic noun, not a specific skill name. In JDs it could easily be read as user needs or business requirements understanding, among other comprehension-related skills."
},
"context_keywords": {
"context_keywords": [
"requirements analysis",
"problem decomposition",
"root cause analysis",
"stakeholder needs",
"domain knowledge",
"specification",
"interpretation",
"critical thinking",
"requirements gathering",
"gap analysis",
"user stories",
"acceptance criteria",
"decision making",
"ambiguity",
"context awareness"
]
},
"maturity": {
"confidence": 0.93,
"maturity": "well_known",
"reasoning": "Broadly expected in job descriptions across engineering roles; comprehension/understanding is a baseline interview and performance criterion rather than a niche tool skill."
},
"skill_id": "understanding",
"vendor_license": {
"confidence": 0.99,
"license": null,
"vendor": null,
"year_introduced": null
},
"versioning": {
"current_version": null,
"version_aliases": {},
"versioned": false
}
},
"locked_dimensions": [
{
"description": "Ability to read, interpret, and make sense of information, requirements, and domain context. This skill belongs here because it is a foundational cognitive capability used to understand problems before analysis, design, or validation work begins.",
"exemplar_skills": [
"Understanding",
"Requirements comprehension",
"Business process understanding",
"Stakeholder intent interpretation",
"Domain knowledge acquisition"
],
"in_scope": "Understanding, reading requirements, interpreting business rules, grasping domain terminology, following process descriptions, interpreting stakeholder intent, comprehension of documents and workflows",
"name": "Analytical Comprehension",
"out_of_scope": "Requirements and Acceptance Validation, statistical analysis, data quality checks, system design decisions, implementation coding, testing execution",
"overlap_flags": [
{
"reason": "Understanding often supports validation of requirements, but validation is about checking implemented behavior against criteria rather than comprehension itself.",
"with_dim_id": "requirements-and-acceptance-validation",
"with_dim_name": null,
"with_role": null
}
],
"tentative_id": "d_init_01"
}
],
"merge_log": [],
"placed": {
"name": "Understanding",
"placement_confidence": 0.92,
"primary_dimension": "d_init_01",
"reasoning": "Deterministic JD placement: locked_dimensions has 1 dimension(s) from skill-driven dimension generation after reconciliation; primary_dimension is the first locked dim.",
"secondary_dimensions": [],
"skill_id": "understanding"
},
"relationships": {
"child_skills": [],
"parent_skills": [],
"related_to": [
"error-analysis",
"threat-modeling",
"acceptance-criteria-validation",
"acceptance-criteria-checks",
"dependency-mapping"
],
"requires": [],
"skill_id": "understanding",
"suppress_on_match": []
},
"skill_id": "understanding",
"split_log": [],
"typed": {
"alternatives_considered": [],
"confidence": 0.93,
"name": "Understanding",
"reasoning": "Understanding is a named knowledge unit rather than a way of working, so by the Concept vs Methodology rule it fits Concept.",
"skill_id": "understanding",
"subtype": "comprehension",
"type": "Concept"
},
"warnings": []
},
"source_tag": "llm",
"was_in_llm_skills": true
},
{
"aliases_in_db": [],
"canonical": null,
"dimensions": [
{
"dimension": {
"difficulty_hint": null,
"display_name": "Diagramming and Process Modeling",
"id": null,
"rationale": "Creating business and technical diagrams to communicate workflows, systems, and relationships. Visio belongs here because it is commonly used to draw process maps, org charts, network diagrams, and other structured visual artifacts for analysis and documentation.",
"slug": "d_init_01",
"source": "llm"
},
"input_skill": "Visio",
"llm_role": null,
"roles_from_db": []
}
],
"input_skill": "Visio",
"matched_via": null,
"new_alias_persisted": false,
"new_alias_text": null,
"new_skill_meta": {
"derived": {
"category": "Tool",
"skill_nature": "TOOL",
"sub_category": "diagramming_tool",
"typical_lifespan": "EVERGREEN",
"version_strategy": "NOT_APPLICABLE",
"volatility": "STABLE"
},
"enrichment": {
"ambiguity": {
"ambiguity_flag": false,
"confused_with": [],
"reasoning": "Visio is a well-known Microsoft diagramming tool with a distinctive name; in typical JDs it is unlikely to be confused with another catalog skill."
},
"context_keywords": {
"context_keywords": [
"flowchart",
"swimlane",
"process map",
"BPMN",
"UML",
"network diagram",
"org chart",
"data flow diagram",
"wireframe",
"site map",
"value stream map",
"cross-functional diagram",
"business process",
"workflow",
"stencil"
]
},
"maturity": {
"confidence": 0.84,
"maturity": "well_known",
"reasoning": "Common in enterprise JDs for process/network diagrams and Microsoft 365 ecosystems; no vendor sunset, and it remains a standard diagramming tool alongside newer alternatives."
},
"skill_id": "visio",
"vendor_license": {
"confidence": 0.99,
"license": "proprietary",
"vendor": "Microsoft",
"year_introduced": 1992
},
"versioning": {
"current_version": null,
"version_aliases": {},
"versioned": false
}
},
"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, org charts, network diagrams, and other structured visual artifacts for analysis and documentation.",
"exemplar_skills": [
"Visio",
"process mapping",
"swimlane diagramming",
"org chart creation",
"network diagramming",
"workflow modeling"
],
"in_scope": "Visio, process flow diagrams, swimlane diagrams, BPMN-style process maps, org charts, network diagrams, floor plans, UML sketches, data flow diagrams, documentation diagrams",
"name": "Diagramming and Process Modeling",
"out_of_scope": "Requirements elicitation and stakeholder interviews, formal business analysis methods, presentation slide design, code-level UML modeling, project scheduling tools",
"overlap_flags": [
{
"reason": "Network diagrams created in Visio can overlap with network documentation, but this dimension is broader and focused on diagramming as a communication skill.",
"with_dim_id": "network-documentation-and-standards",
"with_dim_name": null,
"with_role": null
},
{
"reason": "Business analysts may use Visio to document requirements, but validation of implemented behavior belongs to the requirements validation dimension.",
"with_dim_id": "requirements-and-acceptance-validation",
"with_dim_name": null,
"with_role": null
}
],
"tentative_id": "d_init_01"
}
],
"merge_log": [],
"placed": {
"name": "Visio",
"placement_confidence": 0.92,
"primary_dimension": "d_init_01",
"reasoning": "Deterministic JD placement: locked_dimensions has 1 dimension(s) from skill-driven dimension generation after reconciliation; primary_dimension is the first locked dim.",
"secondary_dimensions": [],
"skill_id": "visio"
},
"relationships": {
"child_skills": [],
"parent_skills": [],
"related_to": [
"navgraph",
"dashboards",
"session-charters",
"scorecards",
"threat-modeling",
"mvvm",
"portal-pages",
"portal-navigation"
],
"requires": [],
"skill_id": "visio",
"suppress_on_match": []
},
"skill_id": "visio",
"split_log": [],
"typed": {
"alternatives_considered": [],
"confidence": 0.98,
"name": "Visio",
"reasoning": "Visio is software you run to create diagrams, so by the Tool vs Framework rule it is a Tool rather than something you build applications inside.",
"skill_id": "visio",
"subtype": "diagramming_tool",
"type": "Tool"
},
"warnings": []
},
"source_tag": "llm",
"was_in_llm_skills": true
},
{
"aliases_in_db": [],
"canonical": null,
"dimensions": [],
"input_skill": "analysis",
"matched_via": null,
"new_alias_persisted": false,
"new_alias_text": null,
"new_skill_meta": null,
"source_tag": "llm",
"was_in_llm_skills": true
},
{
"aliases_in_db": [],
"canonical": null,
"dimensions": [],
"input_skill": "communication",
"matched_via": null,
"new_alias_persisted": false,
"new_alias_text": null,
"new_skill_meta": null,
"source_tag": "llm",
"was_in_llm_skills": true
},
{
"aliases_in_db": [],
"canonical": null,
"dimensions": [],
"input_skill": "data",
"matched_via": null,
"new_alias_persisted": false,
"new_alias_text": null,
"new_skill_meta": null,
"source_tag": "llm",
"was_in_llm_skills": true
},
{
"aliases_in_db": [],
"canonical": null,
"dimensions": [],
"input_skill": "databases",
"matched_via": null,
"new_alias_persisted": false,
"new_alias_text": null,
"new_skill_meta": null,
"source_tag": "llm",
"was_in_llm_skills": true
},
{
"aliases_in_db": [],
"canonical": null,
"dimensions": [],
"input_skill": "documentation",
"matched_via": null,
"new_alias_persisted": false,
"new_alias_text": null,
"new_skill_meta": null,
"source_tag": "llm",
"was_in_llm_skills": true
},
{
"aliases_in_db": [],
"canonical": null,
"dimensions": [],
"input_skill": "fintech",
"matched_via": null,
"new_alias_persisted": false,
"new_alias_text": null,
"new_skill_meta": null,
"source_tag": "llm",
"was_in_llm_skills": true
},
{
"aliases_in_db": [],
"canonical": null,
"dimensions": [],
"input_skill": "healthcare",
"matched_via": null,
"new_alias_persisted": false,
"new_alias_text": null,
"new_skill_meta": null,
"source_tag": "llm",
"was_in_llm_skills": true
},
{
"aliases_in_db": [],
"canonical": null,
"dimensions": [],
"input_skill": "insights",
"matched_via": null,
"new_alias_persisted": false,
"new_alias_text": null,
"new_skill_meta": null,
"source_tag": "llm",
"was_in_llm_skills": true
},
{
"aliases_in_db": [],
"canonical": null,
"dimensions": [],
"input_skill": "methodologies",
"matched_via": null,
"new_alias_persisted": false,
"new_alias_text": null,
"new_skill_meta": null,
"source_tag": "llm",
"was_in_llm_skills": true
},
{
"aliases_in_db": [],
"canonical": null,
"dimensions": [],
"input_skill": "optimization",
"matched_via": null,
"new_alias_persisted": false,
"new_alias_text": null,
"new_skill_meta": null,
"source_tag": "llm",
"was_in_llm_skills": true
},
{
"aliases_in_db": [],
"canonical": null,
"dimensions": [],
"input_skill": "reporting",
"matched_via": null,
"new_alias_persisted": false,
"new_alias_text": null,
"new_skill_meta": null,
"source_tag": "llm",
"was_in_llm_skills": true
},
{
"aliases_in_db": [],
"canonical": null,
"dimensions": [],
"input_skill": "requirements",
"matched_via": null,
"new_alias_persisted": false,
"new_alias_text": null,
"new_skill_meta": null,
"source_tag": "llm",
"was_in_llm_skills": true
},
{
"aliases_in_db": [],
"canonical": null,
"dimensions": [],
"input_skill": "software",
"matched_via": null,
"new_alias_persisted": false,
"new_alias_text": null,
"new_skill_meta": null,
"source_tag": "llm",
"was_in_llm_skills": true
},
{
"aliases_in_db": [],
"canonical": null,
"dimensions": [],
"input_skill": "specifications",
"matched_via": null,
"new_alias_persisted": false,
"new_alias_text": null,
"new_skill_meta": null,
"source_tag": "llm",
"was_in_llm_skills": true
},
{
"aliases_in_db": [],
"canonical": null,
"dimensions": [],
"input_skill": "stories",
"matched_via": null,
"new_alias_persisted": false,
"new_alias_text": null,
"new_skill_meta": null,
"source_tag": "llm",
"was_in_llm_skills": true
},
{
"aliases_in_db": [],
"canonical": null,
"dimensions": [],
"input_skill": "strategies",
"matched_via": null,
"new_alias_persisted": false,
"new_alias_text": null,
"new_skill_meta": null,
"source_tag": "llm",
"was_in_llm_skills": true
},
{
"aliases_in_db": [],
"canonical": null,
"dimensions": [],
"input_skill": "tools",
"matched_via": null,
"new_alias_persisted": false,
"new_alias_text": null,
"new_skill_meta": null,
"source_tag": "llm",
"was_in_llm_skills": true
},
{
"aliases_in_db": [],
"canonical": null,
"dimensions": [],
"input_skill": "trends",
"matched_via": null,
"new_alias_persisted": false,
"new_alias_text": null,
"new_skill_meta": null,
"source_tag": "llm",
"was_in_llm_skills": true
},
{
"aliases_in_db": [],
"canonical": null,
"dimensions": [],
"input_skill": "workshops",
"matched_via": null,
"new_alias_persisted": false,
"new_alias_text": null,
"new_skill_meta": null,
"source_tag": "llm",
"was_in_llm_skills": true
}
],
"unmatched_skills": [
"APIs",
"Acceptance",
"BI",
"BRDs",
"CBAP",
"CCBA",
"Excel",
"FRDs",
"Gather",
"Knowledge",
"QA",
"SDLC",
"SaaS",
"Testing",
"UAT",
"Understanding",
"Visio"
]
}
API 3 — final-role-output
{
"chosen_role": {
"display_name": "Business Analyst",
"id": null,
"rationale": "The strongest clustered evidence is requirements/documentation/analysis work, with dashboarding and workflow tooling as secondary signals, which aligns best with a Business Analyst umbrella.",
"role_archetype": "Analyzes business needs, gathers requirements, and translates them into functional specifications and process improvements. Often bridges stakeholders, documentation, and testing across business and technical teams.",
"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": "Gather",
"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": "Understanding",
"tag": "new"
},
{
"skill": "Visio",
"tag": "new"
},
{
"skill": "analysis",
"tag": "new"
},
{
"skill": "communication",
"tag": "new"
},
{
"skill": "data",
"tag": "new"
},
{
"skill": "databases",
"tag": "new"
},
{
"skill": "documentation",
"tag": "new"
},
{
"skill": "fintech",
"tag": "new"
},
{
"skill": "healthcare",
"tag": "new"
},
{
"skill": "insights",
"tag": "new"
},
{
"skill": "methodologies",
"tag": "new"
},
{
"skill": "optimization",
"tag": "new"
},
{
"skill": "reporting",
"tag": "new"
},
{
"skill": "requirements",
"tag": "new"
},
{
"skill": "software",
"tag": "new"
},
{
"skill": "specifications",
"tag": "new"
},
{
"skill": "stories",
"tag": "new"
},
{
"skill": "strategies",
"tag": "new"
},
{
"skill": "tools",
"tag": "new"
},
{
"skill": "trends",
"tag": "new"
},
{
"skill": "workshops",
"tag": "new"
}
],
"persistence": {
"items": [
{
"chosen_role_id": 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 and consuming application programming interfaces for system-to-system communication. This fits APIs because the skill centers on defining contracts, exchanging data, and connecting business processes across services.",
"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 Reporting",
"id": null,
"rationale": "Covers the creation and use of business-facing reports, dashboards, and KPI views that help teams monitor performance and make decisions. BI belongs here because it commonly refers to the reporting and analytics layer used by business analysts and stakeholders.",
"slug": "d_init_01",
"source": "llm"
},
"dimension_id": null,
"input_skill": "BI",
"llm_role": null,
"matched_chosen_role": false,
"role_dimension_saved": false,
"roles_from_db": [],
"skill_dimension_saved": false,
"skill_id": null,
"skill_tag": "new",
"skipped_reason": "skill_not_in_db_v3_proposed"
},
{
"chosen_role_id": null,
"dimension": {
"difficulty_hint": null,
"display_name": "Business Requirements Documentation",
"id": null,
"rationale": "Covers creating and maintaining BRDs that capture business goals, scope, assumptions, constraints, and approval-ready requirements. This skill belongs here because BRDs are the standard artifact for translating stakeholder needs into a structured business specification.",
"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, including formal methods, terminology, and competency areas validated by credentialing bodies. CBAP belongs here because it is a business analysis certification rather than a technical implementation skill.",
"slug": "d_init_01",
"source": "llm"
},
"dimension_id": null,
"input_skill": "CBAP",
"llm_role": null,
"matched_chosen_role": false,
"role_dimension_saved": false,
"roles_from_db": [],
"skill_dimension_saved": false,
"skill_id": null,
"skill_tag": "new",
"skipped_reason": "skill_not_in_db_v3_proposed"
},
{
"chosen_role_id": null,
"dimension": {
"difficulty_hint": null,
"display_name": "Business Analysis Certification",
"id": null,
"rationale": "Formal business analysis credentialing and professional standards for analysts. CCBA belongs here because it is a recognized certification focused on business analysis competency, techniques, and practice.",
"slug": "d_init_01",
"source": "llm"
},
"dimension_id": null,
"input_skill": "CCBA",
"llm_role": null,
"matched_chosen_role": false,
"role_dimension_saved": false,
"roles_from_db": [],
"skill_dimension_saved": false,
"skill_id": null,
"skill_tag": "new",
"skipped_reason": "skill_not_in_db_v3_proposed"
},
{
"chosen_role_id": null,
"dimension": {
"difficulty_hint": null,
"display_name": "Spreadsheet Analysis and Modeling",
"id": null,
"rationale": "Using spreadsheet software to organize, analyze, and present business data. Excel belongs here because it is the primary tool for tabular analysis, formulas, pivoting, and lightweight modeling 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 Documentation",
"id": null,
"rationale": "Covers writing and maintaining functional requirement documents that define what a product or process must do. FRDs belong here because they capture business needs, scope, rules, and expected behavior in a structured specification.",
"slug": "d_init_01",
"source": "llm"
},
"dimension_id": null,
"input_skill": "FRDs",
"llm_role": null,
"matched_chosen_role": false,
"role_dimension_saved": false,
"roles_from_db": [],
"skill_dimension_saved": false,
"skill_id": null,
"skill_tag": "new",
"skipped_reason": "skill_not_in_db_v3_proposed"
},
{
"chosen_role_id": null,
"dimension": {
"difficulty_hint": null,
"display_name": "Requirements Gathering",
"id": null,
"rationale": "Collecting, clarifying, and documenting business needs from stakeholders so teams can define scope and priorities. The skill Gather fits here because it commonly refers to eliciting information, questions, and constraints before analysis or delivery.",
"slug": "d_init_01",
"source": "llm"
},
"dimension_id": null,
"input_skill": "Gather",
"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, rules, and operating context behind requirements and analysis. For a Business Analyst, this skill helps interpret stakeholder needs, map processes, and make correct decisions in the right business context.",
"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 subskill.",
"slug": "d_init_01",
"source": "llm"
},
"dimension_id": null,
"input_skill": "SDLC",
"llm_role": null,
"matched_chosen_role": false,
"role_dimension_saved": false,
"roles_from_db": [],
"skill_dimension_saved": false,
"skill_id": null,
"skill_tag": "new",
"skipped_reason": "skill_not_in_db_v3_proposed"
},
{
"chosen_role_id": null,
"dimension": {
"difficulty_hint": null,
"display_name": "SaaS Product Concepts",
"id": null,
"rationale": "Covers software delivered as a subscription service over the web, including tenant-based delivery, subscription packaging, and product capabilities common to SaaS offerings. SaaS fits here because it names the delivery and business model rather than a specific technical implementation.",
"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": "Analytical Comprehension",
"id": null,
"rationale": "Ability to read, interpret, and make sense of information, requirements, and domain context. This skill belongs here because it is a foundational cognitive capability used to understand problems before analysis, design, or validation work begins.",
"slug": "d_init_01",
"source": "llm"
},
"dimension_id": null,
"input_skill": "Understanding",
"llm_role": null,
"matched_chosen_role": false,
"role_dimension_saved": false,
"roles_from_db": [],
"skill_dimension_saved": false,
"skill_id": null,
"skill_tag": "new",
"skipped_reason": "skill_not_in_db_v3_proposed"
},
{
"chosen_role_id": 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, org charts, network diagrams, and other structured visual artifacts 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": 16
},
"planner_output": null,
"run_id": "715d9dea-c810-4ad6-8f2c-4aa329fa7829"
}
LLM Calls
Every model call made for this run, in pipeline order. Click a card to see the model's response.
Loading…