Pipeline run
1e48c84e-e05d-4e98-a8e1-12b83451729c
Client output enrichment
v2 Skill cluster · Nature of work · AI index · Tech stack maturity · Evidence · KRA descriptionNature of work
—
Tech stack maturity
Mainstream Modern
AI index (0 = no AI use, 5 = totally AI-dependent · v2.1)
0.00 / 5
· Title match
· Has AI skill
· AI skill (primary)
· AI skill (secondary)
· On AI team
· Builds AI products
vocab breakdown (legacy)
Assistants (×1):
—
Frameworks (×2):
—
Models / concepts (×3):
—
Evidence — skills matched in JD (0)
Skill cluster (0 dimension groups, role-scoped)
Status:
completed
Created: 2026-05-08T10:16:10.253737Z
Updated: 2026-05-08T10:17:59.334731Z
API 3 duration: 1264 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 dominant evidence is requirements and analysis work (BRDs, FRDs, UAT, QA, SDLC, stakeholders), which aligns much more cleanly with a Business Analyst than the DB engineering candidates.
0
New skills
0
Skill↔dim saved
0
Role↔dim saved
21
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 |
| Acceptance | new |
Business Requirements Acceptance
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 |
| Familiarity | new |
Domain Familiarity
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 |
| QA | new |
Quality Assurance Testing
d_init_01
|
— | — | — | skill_not_in_db_v3_proposed |
| SDLC | new |
Software Delivery Lifecycle
d_init_01
|
— | — | — | skill_not_in_db_v3_proposed |
| SaaS | new |
SaaS Product Delivery
d_init_01
|
— | — | — | skill_not_in_db_v3_proposed |
| SaaS | new |
Software Subscription Business Models
d_init_02
|
— | — | — | skill_not_in_db_v3_proposed |
| UAT | new |
User Acceptance Testing
d_init_01
|
— | — | — | skill_not_in_db_v3_proposed |
| Understanding | new |
Requirements and Domain Understanding
d_init_01
|
— | — | — | skill_not_in_db_v3_proposed |
| Visio | new |
Diagramming and Process Modeling
d_init_01
|
— | — | — | skill_not_in_db_v3_proposed |
| Visio | new |
Business Analysis Documentation
d_init_02
|
— | — | — | 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_documents nature=CONCEPT lifespan=EVERGREEN | |
| canonical_skill_proposed | CBAP | type=Certification subtype=business_analysis_professional_certification nature=CREDENTIAL lifespan=EVERGREEN | |
| canonical_skill_proposed | CCBA | type=Certification subtype=business_analysis_certification nature=CREDENTIAL lifespan=EVERGREEN | |
| canonical_skill_proposed | Excel | type=Tool subtype=spreadsheet_software nature=TOOL lifespan=EVERGREEN | |
| canonical_skill_proposed | FRDs | type=Concept subtype=functional_requirements_document nature=CONCEPT lifespan=EVERGREEN | |
| canonical_skill_proposed | Familiarity | type=Concept subtype=familiarity nature=CONCEPT lifespan=EVERGREEN | |
| canonical_skill_proposed | Knowledge | type=Concept subtype=general_knowledge nature=CONCEPT lifespan=EVERGREEN | |
| canonical_skill_proposed | QA | type=Methodology subtype=quality_assurance nature=METHODOLOGY lifespan=EVERGREEN | |
| canonical_skill_proposed | SDLC | type=Methodology subtype=software_development_lifecycle nature=METHODOLOGY lifespan=EVERGREEN | |
| canonical_skill_proposed | SaaS | type=Platform subtype=software_as_a_service_platform nature=PLATFORM lifespan=EVERGREEN | |
| canonical_skill_proposed | Testing | type=Methodology subtype=software_testing_methodology nature=METHODOLOGY lifespan=EVERGREEN | |
| canonical_skill_proposed | UAT | type=Methodology subtype=user_acceptance_testing nature=METHODOLOGY lifespan=EVERGREEN | |
| canonical_skill_proposed | 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 Requirements Acceptance | |
| dimension_skill_link_proposed | Acceptance ↔ Business Requirements Acceptance | |
| 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 | Domain Familiarity | |
| dimension_skill_link_proposed | Familiarity ↔ Domain Familiarity | |
| dimension_proposed | Domain Knowledge and Business Context | |
| dimension_skill_link_proposed | Knowledge ↔ Domain Knowledge and Business Context | |
| dimension_proposed | Quality Assurance Testing | |
| dimension_skill_link_proposed | QA ↔ Quality Assurance Testing | |
| dimension_proposed | Software Delivery Lifecycle | |
| dimension_skill_link_proposed | SDLC ↔ Software Delivery Lifecycle | |
| dimension_proposed | SaaS Product Delivery | |
| dimension_skill_link_proposed | SaaS ↔ SaaS Product Delivery | |
| dimension_proposed | Software Subscription Business Models | |
| dimension_skill_link_proposed | SaaS ↔ Software Subscription Business Models | |
| dimension_proposed | User Acceptance Testing | |
| dimension_skill_link_proposed | UAT ↔ User Acceptance Testing | |
| dimension_proposed | Requirements and Domain Understanding | |
| dimension_skill_link_proposed | Understanding ↔ Requirements and Domain Understanding | |
| dimension_proposed | Diagramming and Process Modeling | |
| dimension_skill_link_proposed | Visio ↔ Diagramming and Process Modeling | |
| dimension_proposed | Business Analysis Documentation | |
| dimension_skill_link_proposed | Visio ↔ Business Analysis Documentation |
API 1 — extract-from-jd click to toggle
{
"filtered_unknown_words": [
"2\u20135",
"APIs",
"Ability",
"Acceptance",
"Analyst",
"BI",
"BRDs",
"Bachelor",
"Benefits",
"Business",
"CBAP",
"CCBA",
"Career",
"Certification",
"Computer",
"Conduct",
"Description",
"Ensure",
"Excel",
"Experience",
"Exposure",
"FRDs",
"Familiarity",
"Gather",
"Health",
"Hybrid",
"Job",
"Key",
"Knowledge",
"Learning",
"Location",
"Monitor",
"Power",
"Preferred",
"QA",
"Qualifications",
"Remote",
"Required",
"Responsibilities",
"Role",
"SDLC",
"SaaS",
"Science",
"Skills",
"Support",
"Testing",
"Title",
"UAT",
"Understanding",
"User",
"Visio",
"Years",
"abilities",
"analysis",
"benefits",
"business",
"candidate",
"certification",
"commerce",
"communication",
"company",
"data",
"databases",
"degree",
"delivery",
"dependencies",
"developers",
"development",
"diagrams",
"document",
"documentation",
"domains",
"environment",
"field",
"fintech",
"gap",
"gathering",
"goals",
"growth",
"healthcare",
"insights",
"insurance",
"leaves",
"management",
"managers",
"meetings",
"methodologies",
"needs",
"opportunities",
"optimization",
"problem",
"process",
"processes",
"product",
"progress",
"project",
"reporting",
"requirement",
"requirements",
"risks",
"salary",
"site",
"skills",
"software",
"solutions",
"specifications",
"stakeholder",
"stakeholders",
"stories",
"strategies",
"teams",
"tools",
"trends",
"understanding",
"user",
"work",
"workshops"
],
"final_non_skills": [
"2\u20135",
"Ability",
"Analyst",
"Bachelor",
"Benefits",
"Business",
"Certification",
"Computer",
"Conduct",
"Description",
"Ensure",
"Experience",
"Exposure",
"Gather",
"Health",
"Hybrid",
"Job",
"Key",
"Learning",
"Location",
"Monitor",
"Power",
"Preferred",
"Qualifications",
"Remote",
"Required",
"Responsibilities",
"Role",
"Science",
"Skills",
"Support",
"Title",
"User",
"Years",
"abilities",
"candidate",
"commerce",
"company",
"degree",
"delivery",
"dependencies",
"developers",
"document",
"documentation",
"environment",
"field",
"gap",
"gathering",
"goals",
"growth",
"insurance",
"leaves",
"managers",
"meetings",
"needs",
"opportunities",
"problem",
"process",
"processes",
"product",
"progress",
"project",
"requirement",
"risks",
"salary",
"site",
"solutions",
"teams",
"work"
],
"final_skills": [
"Tableau",
"Argo Workflows",
"Power BI",
"APIs",
"Acceptance",
"BI",
"BRDs",
"CBAP",
"CCBA",
"Excel",
"FRDs",
"Familiarity",
"Knowledge",
"QA",
"SDLC",
"SaaS",
"Testing",
"UAT",
"Understanding",
"Visio",
"analysis",
"communication",
"data",
"databases",
"development",
"domains",
"fintech",
"healthcare",
"insights",
"management",
"methodologies",
"optimization",
"reporting",
"requirements",
"software",
"specifications",
"stakeholder",
"stakeholders",
"stories",
"strategies",
"tools",
"trends",
"workshops"
],
"initial_skills": [
"Tableau",
"Argo Workflows",
"Power BI"
],
"jd_role_hint": {
"display_name": "Business Analyst",
"rationale": "The excerpt is explicitly a Business Analyst JD centered on requirements gathering, process analysis, documentation, and stakeholder coordination.",
"role_archetype": "Requirements-focused analyst bridging business and technical teams to document, analyze, and translate needs into functional specifications.",
"slug": "business-analyst"
},
"llm_non_skills": [
"2\u20135",
"Ability",
"Analyst",
"Bachelor",
"Benefits",
"Business",
"Certification",
"Computer",
"Conduct",
"Description",
"Ensure",
"Experience",
"Exposure",
"Gather",
"Health",
"Hybrid",
"Job",
"Key",
"Learning",
"Location",
"Monitor",
"Power",
"Preferred",
"Qualifications",
"Remote",
"Required",
"Responsibilities",
"Role",
"Science",
"Skills",
"Support",
"Title",
"User",
"Years",
"abilities",
"candidate",
"commerce",
"company",
"degree",
"delivery",
"dependencies",
"developers",
"document",
"documentation",
"environment",
"field",
"gap",
"gathering",
"goals",
"growth",
"insurance",
"leaves",
"managers",
"meetings",
"needs",
"opportunities",
"problem",
"process",
"processes",
"product",
"progress",
"project",
"requirement",
"risks",
"salary",
"site",
"solutions",
"teams",
"work"
],
"llm_skills": [
"APIs",
"Acceptance",
"BI",
"BRDs",
"CBAP",
"CCBA",
"Excel",
"FRDs",
"Familiarity",
"Knowledge",
"QA",
"SDLC",
"SaaS",
"Testing",
"UAT",
"Understanding",
"Visio",
"analysis",
"communication",
"data",
"databases",
"development",
"domains",
"fintech",
"healthcare",
"insights",
"management",
"methodologies",
"optimization",
"reporting",
"requirements",
"software",
"specifications",
"stakeholder",
"stakeholders",
"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 dominant evidence is requirements and analysis work (BRDs, FRDs, UAT, QA, SDLC, stakeholders), which aligns much more cleanly with a Business Analyst than the DB engineering candidates.",
"role_archetype": "Requirements-focused analyst bridging business and technical teams to document, analyze, and translate business needs into functional specifications. Typically works across stakeholders, QA/UAT, and documentation-heavy workflows.",
"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, documenting, and integrating application programming interfaces across systems. This fits APIs because the skill centers on how software exposes and consumes structured endpoints and contracts.",
"slug": "d_init_01",
"source": "llm"
},
"input_skill": "APIs",
"llm_role": null,
"roles_from_db": []
},
{
"dimension": {
"difficulty_hint": null,
"display_name": "Business Requirements Acceptance",
"id": null,
"rationale": "Confirming that delivered work satisfies business needs, stakeholder expectations, and formal sign-off criteria. This is the best fit when Acceptance refers to approving a solution from a business analysis perspective rather than technical testing.",
"slug": "d_init_01",
"source": "llm"
},
"input_skill": "Acceptance",
"llm_role": null,
"roles_from_db": []
},
{
"dimension": {
"difficulty_hint": null,
"display_name": "Business Intelligence Reporting",
"id": null,
"rationale": "Covers the creation and consumption of business-facing reports, dashboards, and KPI views used to monitor performance and support decisions. BI belongs here because, in a Business Analyst context, it typically refers to turning data into actionable reporting and analysis for 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 writing and maintaining business requirements documents that define the problem, scope, stakeholders, assumptions, and acceptance criteria for a solution. BRDs belong here because they are the canonical artifact used by business analysts to translate business needs into implementable requirements.",
"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 and credentialing for business analysts. CBAP belongs here because it is a business analysis certification focused on requirements, stakeholder needs, and solution evaluation rather than a specific tool or platform.",
"slug": "d_init_01",
"source": "llm"
},
"input_skill": "CBAP",
"llm_role": null,
"roles_from_db": []
},
{
"dimension": {
"difficulty_hint": null,
"display_name": "Business Analysis Certification",
"id": null,
"rationale": "Professional certification knowledge for business analysts, including requirements elicitation, stakeholder analysis, solution assessment, and business process modeling. CCBA belongs here because it is a recognized business analysis credential rather than a tool or technical implementation skill.",
"slug": "d_init_01",
"source": "llm"
},
"input_skill": "CCBA",
"llm_role": null,
"roles_from_db": []
},
{
"dimension": {
"difficulty_hint": null,
"display_name": "Spreadsheet Analysis and Modeling",
"id": null,
"rationale": "Using spreadsheets to organize, analyze, and summarize business data for reporting and decision support. Excel belongs here because it is the primary tool for formulas, pivot-based analysis, charts, 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 requirements documents that define what a product or process must do. FRDs belong here because they capture business needs, scope, rules, and acceptance expectations in a formal requirements artifact.",
"slug": "d_init_01",
"source": "llm"
},
"input_skill": "FRDs",
"llm_role": null,
"roles_from_db": []
},
{
"dimension": {
"difficulty_hint": null,
"display_name": "Domain Familiarity",
"id": null,
"rationale": "General working familiarity with a business or technical domain, enough to understand terminology, workflows, and stakeholder needs. This fits the target skill because it signals breadth of exposure rather than deep implementation expertise.",
"slug": "d_init_01",
"source": "llm"
},
"input_skill": "Familiarity",
"llm_role": null,
"roles_from_db": []
},
{
"dimension": {
"difficulty_hint": null,
"display_name": "Domain Knowledge and Business Context",
"id": null,
"rationale": "Knowledge of the business domain, processes, terminology, and operating context used to interpret requirements and make sound decisions. For a Business Analyst, this is the core subject-matter understanding behind analysis, stakeholder communication, and solution framing.",
"slug": "d_init_01",
"source": "llm"
},
"input_skill": "Knowledge",
"llm_role": null,
"roles_from_db": []
},
{
"dimension": {
"difficulty_hint": null,
"display_name": "Quality Assurance Testing",
"id": null,
"rationale": "Validating that a product, feature, or process meets requirements through structured testing and defect checking. QA belongs here when it refers to general assurance work rather than a specific automation or platform discipline.",
"slug": "d_init_01",
"source": "llm"
},
"input_skill": "QA",
"llm_role": null,
"roles_from_db": []
},
{
"dimension": {
"difficulty_hint": null,
"display_name": "Software Delivery Lifecycle",
"id": null,
"rationale": "Covers the end-to-end process used to plan, build, test, release, and maintain software changes. SDLC belongs here because it refers to the overall lifecycle and governance of delivery work rather than a single technical practice.",
"slug": "d_init_01",
"source": "llm"
},
"input_skill": "SDLC",
"llm_role": null,
"roles_from_db": []
},
{
"dimension": {
"difficulty_hint": null,
"display_name": "SaaS Product Delivery",
"id": null,
"rationale": "Covers software delivered as a hosted subscription service, including multi-tenant product packaging, release cadence, and customer-facing service operations. SaaS belongs here because it describes the delivery model and operating context for the product rather than a specific technical component.",
"slug": "d_init_01",
"source": "llm"
},
"input_skill": "SaaS",
"llm_role": null,
"roles_from_db": []
},
{
"dimension": {
"difficulty_hint": null,
"display_name": "Software Subscription Business Models",
"id": null,
"rationale": "Covers the commercial and operational model of selling software as a recurring subscription service. This fits SaaS when the skill is used in business analysis, pricing, packaging, and customer lifecycle discussions.",
"slug": "d_init_02",
"source": "llm"
},
"input_skill": "SaaS",
"llm_role": null,
"roles_from_db": []
},
{
"dimension": {
"difficulty_hint": null,
"display_name": "User Acceptance Testing",
"id": null,
"rationale": "Validating that a delivered feature meets business requirements and is ready for user sign-off. UAT belongs here because it is the business-facing execution of acceptance scenarios before release.",
"slug": "d_init_01",
"source": "llm"
},
"input_skill": "UAT",
"llm_role": null,
"roles_from_db": []
},
{
"dimension": {
"difficulty_hint": null,
"display_name": "Requirements and Domain Understanding",
"id": null,
"rationale": "Interpreting business needs, user goals, and process context well enough to translate them into clear requirements and analysis artifacts. This fits the target skill because business analysts are often evaluated on how well they understand the problem space before proposing solutions.",
"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, swimlanes, org charts, and system diagrams for analysis and documentation.",
"slug": "d_init_01",
"source": "llm"
},
"input_skill": "Visio",
"llm_role": null,
"roles_from_db": []
},
{
"dimension": {
"difficulty_hint": null,
"display_name": "Business Analysis Documentation",
"id": null,
"rationale": "Documenting business requirements, current-state and future-state processes, and stakeholder-facing artifacts. Visio fits when used by a Business Analyst to capture process flows and support requirements communication.",
"slug": "d_init_02",
"source": "llm"
},
"input_skill": "Visio",
"llm_role": null,
"roles_from_db": []
}
],
"input_final_skills": [
"Tableau",
"Argo Workflows",
"Power BI",
"APIs",
"Acceptance",
"BI",
"BRDs",
"CBAP",
"CCBA",
"Excel",
"FRDs",
"Familiarity",
"Knowledge",
"QA",
"SDLC",
"SaaS",
"Testing",
"UAT",
"Understanding",
"Visio",
"analysis",
"communication",
"data",
"databases",
"development",
"domains",
"fintech",
"healthcare",
"insights",
"management",
"methodologies",
"optimization",
"reporting",
"requirements",
"software",
"specifications",
"stakeholder",
"stakeholders",
"stories",
"strategies",
"tools",
"trends",
"workshops"
],
"input_llm_skills": [
"APIs",
"Acceptance",
"BI",
"BRDs",
"CBAP",
"CCBA",
"Excel",
"FRDs",
"Familiarity",
"Knowledge",
"QA",
"SDLC",
"SaaS",
"Testing",
"UAT",
"Understanding",
"Visio",
"analysis",
"communication",
"data",
"databases",
"development",
"domains",
"fintech",
"healthcare",
"insights",
"management",
"methodologies",
"optimization",
"reporting",
"requirements",
"software",
"specifications",
"stakeholder",
"stakeholders",
"stories",
"strategies",
"tools",
"trends",
"workshops"
],
"new_aliases_persisted": 0,
"run_id": "1e48c84e-e05d-4e98-a8e1-12b83451729c",
"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, documenting, and integrating application programming interfaces across systems. This fits APIs because the skill centers on how software exposes and consumes structured endpoints and contracts.",
"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",
"OAuth 2.0",
"JWT",
"webhooks",
"endpoint",
"rate limiting",
"API gateway",
"microservices",
"SDK",
"versioning",
"HTTP"
]
},
"maturity": {
"confidence": 0.98,
"maturity": "well_known",
"reasoning": "APIs are a hiring-pipeline staple across backend, mobile, and platform JDs; REST/GraphQL/API design appears in large volumes of job postings and cloud vendor docs."
},
"skill_id": "apis",
"vendor_license": {
"confidence": 0.99,
"license": null,
"vendor": null,
"year_introduced": null
},
"versioning": {
"current_version": null,
"version_aliases": {},
"versioned": false
}
},
"keep_log": [],
"locked_dimensions": [
{
"description": "Designing, documenting, and integrating application programming interfaces across systems. This fits APIs because the skill centers on how software exposes and consumes structured endpoints and contracts.",
"exemplar_skills": [
"APIs",
"REST APIs",
"API design",
"endpoint integration",
"webhooks",
"service contracts"
],
"in_scope": "APIs, REST APIs, API design, endpoint integration, request and response formats, versioning, pagination, error handling, webhooks",
"name": "API Design and Integration",
"out_of_scope": "UI rendering, database schema modeling, automated API testing, infrastructure provisioning, which belong to frontend, data, testing, or platform dimensions",
"overlap_flags": [
{
"reason": "API design overlaps with endpoint testing, but this dimension focuses on defining and integrating APIs rather than validating them.",
"with_dim_id": "api-and-service-test-automation",
"with_dim_name": null,
"with_role": null
},
{
"reason": "Service architecture also covers APIs as part of broader backend decomposition and inter-service communication.",
"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",
"scripted-rest-api",
"outbound-rest-messages",
"mock-servers"
],
"requires": [
"http",
"json",
"oauth-2-0"
],
"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 the term refers to an interface class, not a knowledge unit like idempotency."
],
"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": [
{
"dimension": {
"difficulty_hint": null,
"display_name": "Business Requirements Acceptance",
"id": null,
"rationale": "Confirming that delivered work satisfies business needs, stakeholder expectations, and formal sign-off criteria. This is the best fit when Acceptance refers to approving a solution from a business analysis perspective rather than technical testing.",
"slug": "d_init_01",
"source": "llm"
},
"input_skill": "Acceptance",
"llm_role": null,
"roles_from_db": []
}
],
"input_skill": "Acceptance",
"matched_via": null,
"new_alias_persisted": false,
"new_alias_text": null,
"new_skill_meta": {
"derived": {
"category": "Concept",
"skill_nature": "CONCEPT",
"sub_category": "acceptance_concept",
"typical_lifespan": "EVERGREEN",
"version_strategy": "NOT_APPLICABLE",
"volatility": "STABLE"
},
"enrichment": {
"ambiguity": {
"ambiguity_flag": true,
"confused_with": [
"acceptance_testing"
],
"reasoning": "\u201cAcceptance\u201d is a generic term in JDs and could easily be read as acceptance testing or user acceptance testing, which is a distinct catalog skill."
},
"context_keywords": {
"context_keywords": [
"UAT",
"user acceptance testing",
"acceptance criteria",
"acceptance test",
"sign-off",
"definition of done",
"test cases",
"test plan",
"QA",
"stakeholder approval",
"validation",
"verification",
"go-live",
"release readiness",
"requirements traceability"
]
},
"maturity": {
"confidence": 0.84,
"maturity": "well_known",
"reasoning": "Acceptance is a standard concept in software and product work, commonly referenced in JDs for QA, product, and agile roles; market signal: widespread use in acceptance criteria/UAT across job postings and team practices."
},
"skill_id": "acceptance",
"vendor_license": {
"confidence": 0.99,
"license": null,
"vendor": null,
"year_introduced": null
},
"versioning": {
"current_version": null,
"version_aliases": {},
"versioned": false
}
},
"keep_log": [],
"locked_dimensions": [
{
"description": "Confirming that delivered work satisfies business needs, stakeholder expectations, and formal sign-off criteria. This is the best fit when Acceptance refers to approving a solution from a business analysis perspective rather than technical testing.",
"exemplar_skills": [
"Acceptance",
"acceptance criteria",
"business sign-off",
"stakeholder review",
"user acceptance testing"
],
"in_scope": "Acceptance, business sign-off, acceptance criteria, stakeholder review, requirement validation, UAT coordination, scope confirmation",
"name": "Business Requirements Acceptance",
"out_of_scope": "Writing automated test scripts, API contract validation, UI test framework setup, production incident response, technical deployment checks",
"overlap_flags": [
{
"reason": "Business acceptance often uses test cases, but the core focus here is stakeholder approval and requirement fit rather than test execution.",
"with_dim_id": "test-case-design-and-execution",
"with_dim_name": null,
"with_role": null
}
],
"tentative_id": "d_init_01"
}
],
"merge_log": [],
"placed": {
"name": "Acceptance",
"placement_confidence": 0.92,
"primary_dimension": "d_init_01",
"reasoning": "Deterministic JD placement: locked_dimensions has 1 dimension(s) from skill-driven dimension generation after reconciliation; primary_dimension is the first locked dim.",
"secondary_dimensions": [],
"skill_id": "acceptance"
},
"relationships": {
"child_skills": [],
"parent_skills": [],
"related_to": [
"acceptance-criteria-validation",
"acceptance-criteria-checks",
"contract-tests",
"defect-retest",
"change-requests"
],
"requires": [],
"skill_id": "acceptance",
"suppress_on_match": []
},
"skill_id": "acceptance",
"split_log": [],
"typed": {
"alternatives_considered": [
"Methodology: ruled out \u2014 acceptance is not a process or operating method like Agile or TDD.",
"SoftSkill: ruled out \u2014 although it can involve interpersonal agreement, the term itself denotes a technical/product concept."
],
"confidence": 0.78,
"name": "Acceptance",
"reasoning": "By the Concept vs Methodology rule, Acceptance is best treated as a named knowledge unit about when work is considered complete or approved, rather than a way of working.",
"skill_id": "acceptance",
"subtype": "acceptance_concept",
"type": "Concept"
},
"warnings": []
},
"source_tag": "llm",
"was_in_llm_skills": true
},
{
"aliases_in_db": [],
"canonical": null,
"dimensions": [
{
"dimension": {
"difficulty_hint": null,
"display_name": "Business Intelligence Reporting",
"id": null,
"rationale": "Covers the creation and consumption of business-facing reports, dashboards, and KPI views used to monitor performance and support decisions. BI belongs here because, in a Business Analyst context, it typically refers to turning data into actionable reporting and analysis for 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 read as other meanings like bi- or bilingual. A reasonable extractor could confuse it with the full Business Intelligence skill."
},
"context_keywords": {
"context_keywords": [
"dashboard",
"KPI",
"data warehouse",
"ETL",
"OLAP",
"reporting",
"Tableau",
"Power BI",
"Looker",
"SQL",
"dimensional modeling",
"star schema",
"data mart",
"ad hoc analysis",
"drill-down"
]
},
"maturity": {
"confidence": 0.92,
"maturity": "well_known",
"reasoning": "BI appears in many analytics/data job descriptions and is a standard enterprise reporting stack skill; vendors like Microsoft, Tableau, and Power BI continue to drive broad hiring demand."
},
"skill_id": "bi",
"vendor_license": {
"confidence": 0.99,
"license": null,
"vendor": null,
"year_introduced": null
},
"versioning": {
"current_version": null,
"version_aliases": {},
"versioned": false
}
},
"keep_log": [],
"locked_dimensions": [
{
"description": "Covers the creation and consumption of business-facing reports, dashboards, and KPI views used to monitor performance and support decisions. BI belongs here because, in a Business Analyst context, it typically refers to turning data into actionable reporting and analysis for stakeholders.",
"exemplar_skills": [
"BI",
"dashboard development",
"KPI reporting",
"executive reporting",
"ad hoc reporting",
"Power BI",
"Tableau",
"Looker"
],
"in_scope": "BI, dashboards, KPI reporting, executive scorecards, ad hoc business reports, operational reporting, self-service analytics, drill-down analysis, report distribution, Power BI, Tableau, Looker",
"name": "Business Intelligence Reporting",
"out_of_scope": "Data preparation and blending for building source datasets, data quality assessment for validating data fitness, notebook and reproducible analysis workflow for exploratory coding, streaming data processing for real-time pipelines",
"overlap_flags": [
{
"reason": "BI reporting often depends on prepared datasets, but this dimension owns the transformation and joining work.",
"with_dim_id": "data-preparation-and-blending",
"with_dim_name": null,
"with_role": null
},
{
"reason": "Analysts may use notebooks for exploration, but BI is centered on stakeholder reporting and dashboards.",
"with_dim_id": "notebook-and-reproducible-analysis-workflow",
"with_dim_name": null,
"with_role": null
}
],
"tentative_id": "d_init_01"
}
],
"merge_log": [],
"placed": {
"name": "BI",
"placement_confidence": 0.92,
"primary_dimension": "d_init_01",
"reasoning": "Deterministic JD placement: locked_dimensions has 1 dimension(s) from skill-driven dimension generation after reconciliation; primary_dimension is the first locked dim.",
"secondary_dimensions": [],
"skill_id": "bi"
},
"relationships": {
"child_skills": [],
"parent_skills": [],
"related_to": [
"dashboards"
],
"requires": [],
"skill_id": "bi",
"suppress_on_match": []
},
"skill_id": "bi",
"split_log": [],
"typed": {
"alternatives_considered": [],
"confidence": 0.93,
"name": "BI",
"reasoning": "BI is best classified as a Domain because it denotes the business intelligence problem-space and body of knowledge rather than a specific tool, platform, or methodology.",
"skill_id": "bi",
"subtype": "business_intelligence",
"type": "Domain"
},
"warnings": []
},
"source_tag": "llm",
"was_in_llm_skills": true
},
{
"aliases_in_db": [],
"canonical": null,
"dimensions": [
{
"dimension": {
"difficulty_hint": null,
"display_name": "Business Requirements Documentation",
"id": null,
"rationale": "Covers writing and maintaining business requirements documents that define the problem, scope, stakeholders, assumptions, and acceptance criteria for a solution. BRDs belong here because they are the canonical artifact used by business analysts to translate business needs into implementable requirements.",
"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_documents",
"typical_lifespan": "EVERGREEN",
"version_strategy": "NOT_APPLICABLE",
"volatility": "STABLE"
},
"enrichment": {
"ambiguity": {
"ambiguity_flag": false,
"confused_with": [],
"reasoning": "BRDs is a common business-analysis acronym for Business Requirements Documents; in JDs it is usually clear from context and not plausibly confused with another 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",
"business analysis",
"sign-off",
"requirements elicitation",
"solution design"
]
},
"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, with no vendor sunset or replacement trend."
},
"skill_id": "brds",
"vendor_license": {
"confidence": 0.99,
"license": null,
"vendor": null,
"year_introduced": null
},
"versioning": {
"current_version": null,
"version_aliases": {},
"versioned": false
}
},
"keep_log": [],
"locked_dimensions": [
{
"description": "Covers writing and maintaining business requirements documents that define the problem, scope, stakeholders, assumptions, and acceptance criteria for a solution. BRDs belong here because they are the canonical artifact used by business analysts to translate business needs into implementable requirements.",
"exemplar_skills": [
"BRDs",
"Business Requirements Documents",
"requirements elicitation",
"requirements documentation",
"scope definition",
"stakeholder analysis",
"acceptance criteria writing"
],
"in_scope": "BRDs, business requirements documents, requirements gathering, scope definition, stakeholder needs, business objectives, assumptions and constraints, acceptance criteria, functional requirements, non-functional requirements at a business level, approval workflows",
"name": "Business Requirements Documentation",
"out_of_scope": "Technical design specs, API contracts, user stories owned by agile delivery, test case execution, process modeling notation, which belong to solution design, product backlog management, or test design dimensions",
"overlap_flags": [
{
"reason": "BRDs often inform test cases, but test design is a separate validation discipline rather than requirements authoring.",
"with_dim_id": "test-case-design-and-execution",
"with_dim_name": null,
"with_role": null
},
{
"reason": "BRDs may mention integrations, but detailed service decomposition and interface design belong to architecture.",
"with_dim_id": "service-architecture-and-integration",
"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",
"catalog-items",
"rollback-readiness"
],
"requires": [],
"skill_id": "brds",
"suppress_on_match": []
},
"skill_id": "brds",
"split_log": [],
"typed": {
"alternatives_considered": [
"Format: ruled out \u2014 although a BRD is a document, the term refers to the requirements artifact/idea rather than a specific data structure or wire format",
"Methodology: ruled out \u2014 BRDs describe what to capture, not a way of working or process"
],
"confidence": 0.88,
"name": "BRDs",
"reasoning": "BRDs (business requirements documents) are a named knowledge artifact used in requirements gathering, so they fit the Concept category rather than a Methodology or Format.",
"skill_id": "brds",
"subtype": "business_requirements_documents",
"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 and credentialing for business analysts. CBAP belongs here because it is a business analysis certification focused on requirements, stakeholder needs, and solution evaluation rather than a specific tool or platform.",
"slug": "d_init_01",
"source": "llm"
},
"input_skill": "CBAP",
"llm_role": null,
"roles_from_db": []
}
],
"input_skill": "CBAP",
"matched_via": null,
"new_alias_persisted": false,
"new_alias_text": null,
"new_skill_meta": {
"derived": {
"category": "Certification",
"skill_nature": "CREDENTIAL",
"sub_category": "business_analysis_professional_certification",
"typical_lifespan": "EVERGREEN",
"version_strategy": "NOT_APPLICABLE",
"volatility": "STABLE"
},
"enrichment": {
"ambiguity": {
"ambiguity_flag": false,
"confused_with": [],
"reasoning": "CBAP is a specific certification acronym (Certified Business Analysis Professional) and is unlikely to be confused with another catalog skill in typical job descriptions."
},
"context_keywords": {
"context_keywords": [
"BABOK",
"IIBA",
"requirements elicitation",
"stakeholder analysis",
"process modeling",
"use cases",
"user stories",
"gap analysis",
"business process improvement",
"UML",
"SWOT analysis",
"traceability matrix",
"solution assessment",
"requirements management"
]
},
"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
}
},
"keep_log": [],
"locked_dimensions": [
{
"description": "Professional certification and credentialing for business analysts. CBAP belongs here because it is a business analysis certification focused on requirements, stakeholder needs, and solution evaluation rather than a specific tool or platform.",
"exemplar_skills": [
"CBAP",
"CCBA",
"ECBA",
"IIBA certification",
"business analysis certification",
"requirements elicitation",
"stakeholder analysis"
],
"in_scope": "CBAP, CCBA, ECBA, business analysis certification, IIBA certification, requirements elicitation, stakeholder analysis, business process analysis, solution assessment",
"name": "Business Analysis Certification",
"out_of_scope": "Project management certifications, software engineering certifications, agile delivery certifications, platform-specific training, test automation skills",
"overlap_flags": [
{
"reason": "Business analysts may work on service boundaries and integrations, but this dimension is about certification and BA practice rather than system architecture.",
"with_dim_id": "service-architecture-and-integration",
"with_dim_name": null,
"with_role": null
}
],
"tentative_id": "d_init_01"
}
],
"merge_log": [],
"placed": {
"name": "CBAP",
"placement_confidence": 0.92,
"primary_dimension": "d_init_01",
"reasoning": "Deterministic JD placement: locked_dimensions has 1 dimension(s) from skill-driven dimension generation after reconciliation; primary_dimension is the first locked dim.",
"secondary_dimensions": [],
"skill_id": "cbap"
},
"relationships": {
"child_skills": [],
"parent_skills": [],
"related_to": [
"risk-based-testing",
"acceptance-criteria-validation",
"acceptance-criteria-checks",
"capacity-planning",
"session-based-testing"
],
"requires": [],
"skill_id": "cbap",
"suppress_on_match": []
},
"skill_id": "cbap",
"split_log": [],
"typed": {
"alternatives_considered": [],
"confidence": 0.98,
"name": "CBAP",
"reasoning": "CBAP is a formal third-party credential, so by the Certification rule it is a certification rather than a concept or methodology.",
"skill_id": "cbap",
"subtype": "business_analysis_professional_certification",
"type": "Certification"
},
"warnings": []
},
"source_tag": "llm",
"was_in_llm_skills": true
},
{
"aliases_in_db": [],
"canonical": null,
"dimensions": [
{
"dimension": {
"difficulty_hint": null,
"display_name": "Business Analysis Certification",
"id": null,
"rationale": "Professional certification knowledge for business analysts, including requirements elicitation, stakeholder analysis, solution assessment, and business process modeling. CCBA belongs here because it is a recognized business analysis credential rather than a tool or technical implementation skill.",
"slug": "d_init_01",
"source": "llm"
},
"input_skill": "CCBA",
"llm_role": null,
"roles_from_db": []
}
],
"input_skill": "CCBA",
"matched_via": null,
"new_alias_persisted": false,
"new_alias_text": null,
"new_skill_meta": {
"derived": {
"category": "Certification",
"skill_nature": "CREDENTIAL",
"sub_category": "business_analysis_certification",
"typical_lifespan": "EVERGREEN",
"version_strategy": "NOT_APPLICABLE",
"volatility": "STABLE"
},
"enrichment": {
"ambiguity": {
"ambiguity_flag": true,
"confused_with": [
"cbap",
"pmp"
],
"reasoning": "CCBA is an acronym for a business analysis certification, but in JDs it can be mistaken for nearby cert acronyms like CBAP or even generic project certs such as PMP when listed in a qualifications block."
},
"context_keywords": {
"context_keywords": [
"BABOK",
"IIBA",
"requirements elicitation",
"stakeholder analysis",
"process modeling",
"use cases",
"user stories",
"gap analysis",
"business process improvement",
"solution assessment",
"traceability matrix",
"SWOT analysis",
"workshop facilitation",
"UAT",
"BRD"
]
},
"maturity": {
"confidence": 0.84,
"maturity": "well_known",
"reasoning": "CCBA is a widely recognized business analysis certification; it appears in many job descriptions for BA roles and is offered by IIBA as a mainstream credential alongside CBAP."
},
"skill_id": "ccba",
"vendor_license": {
"confidence": 0.92,
"license": null,
"vendor": "International Institute of Business Analysis",
"year_introduced": 2008
},
"versioning": {
"current_version": null,
"version_aliases": {},
"versioned": false
}
},
"keep_log": [],
"locked_dimensions": [
{
"description": "Professional certification knowledge for business analysts, including requirements elicitation, stakeholder analysis, solution assessment, and business process modeling. CCBA belongs here because it is a recognized business analysis credential rather than a tool or technical implementation skill.",
"exemplar_skills": [
"CCBA",
"CBAP",
"ECBA",
"business analysis certification",
"requirements elicitation",
"stakeholder analysis",
"business process modeling",
"solution assessment"
],
"in_scope": "CCBA, CBAP, ECBA, business analysis certification, requirements elicitation, stakeholder analysis, business process modeling, solution assessment, business case analysis, BABOK knowledge areas",
"name": "Business Analysis Certification",
"out_of_scope": "Software development, data analysis tooling, project management certification, UX research methods, ServiceNow platform configuration, technical testing frameworks",
"overlap_flags": [
{
"reason": "Business analysts may document service interactions, but this dimension is about certification and BA practice rather than system architecture.",
"with_dim_id": "service-architecture-and-integration",
"with_dim_name": null,
"with_role": null
}
],
"tentative_id": "d_init_01"
}
],
"merge_log": [],
"placed": {
"name": "CCBA",
"placement_confidence": 0.92,
"primary_dimension": "d_init_01",
"reasoning": "Deterministic JD placement: locked_dimensions has 1 dimension(s) from skill-driven dimension generation after reconciliation; primary_dimension is the first locked dim.",
"secondary_dimensions": [],
"skill_id": "ccba"
},
"relationships": {
"child_skills": [],
"parent_skills": [],
"related_to": [
"scorecards",
"acceptance-criteria-checks",
"acceptance-criteria-validation",
"risk-based-testing",
"charter-based-testing",
"session-based-testing"
],
"requires": [],
"skill_id": "ccba",
"suppress_on_match": []
},
"skill_id": "ccba",
"split_log": [],
"typed": {
"alternatives_considered": [],
"confidence": 0.98,
"name": "CCBA",
"reasoning": "CCBA is a formal third-party credential, so by the Certification rule it is a Certification rather than a concept or methodology.",
"skill_id": "ccba",
"subtype": "business_analysis_certification",
"type": "Certification"
},
"warnings": []
},
"source_tag": "llm",
"was_in_llm_skills": true
},
{
"aliases_in_db": [],
"canonical": null,
"dimensions": [
{
"dimension": {
"difficulty_hint": null,
"display_name": "Spreadsheet Analysis and Modeling",
"id": null,
"rationale": "Using spreadsheets to organize, analyze, and summarize business data for reporting and decision support. Excel belongs here because it is the primary tool for formulas, pivot-based analysis, charts, 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 in JDs almost always refers to Microsoft Excel spreadsheet software; the name is specific and unlikely to be confused with another catalog skill."
},
"context_keywords": {
"context_keywords": [
"pivot tables",
"VLOOKUP",
"XLOOKUP",
"INDEX MATCH",
"macros",
"VBA",
"Power Query",
"Power Pivot",
"conditional formatting",
"data validation",
"charts",
"dashboards",
"CSV",
"SUMIF",
"COUNTIF"
]
},
"maturity": {
"confidence": 0.99,
"maturity": "well_known",
"reasoning": "Excel appears in a very large share of business, finance, ops, and analyst job descriptions; Microsoft continues active development and it remains a default spreadsheet tool in hiring pipelines."
},
"skill_id": "excel",
"vendor_license": {
"confidence": 0.99,
"license": "proprietary",
"vendor": "Microsoft",
"year_introduced": 1985
},
"versioning": {
"current_version": "Microsoft 365 / Excel 2024",
"version_aliases": {
"Excel 2007": "Microsoft 365 / Excel 2024",
"Excel 2010": "Microsoft 365 / Excel 2024",
"Excel 2013": "Microsoft 365 / Excel 2024",
"Excel 2016": "Microsoft 365 / Excel 2024",
"Excel 2019": "Microsoft 365 / Excel 2024",
"Excel 2021": "Microsoft 365 / Excel 2024",
"Excel 2024": "Microsoft 365 / Excel 2024",
"Excel 365": "Microsoft 365 / Excel 2024",
"Microsoft 365 Excel": "Microsoft 365 / Excel 2024"
},
"versioned": true
}
},
"keep_log": [],
"locked_dimensions": [
{
"description": "Using spreadsheets to organize, analyze, and summarize business data for reporting and decision support. Excel belongs here because it is the primary tool for formulas, pivot-based analysis, charts, and lightweight modeling in analyst workflows.",
"exemplar_skills": [
"Excel",
"pivot tables",
"VLOOKUP",
"XLOOKUP",
"conditional formatting",
"data validation",
"what-if analysis",
"chart creation"
],
"in_scope": "Excel, formulas and functions, pivot tables, charts and graphs, conditional formatting, lookup functions, data validation, filters and sorting, what-if analysis, basic financial and business models",
"name": "Spreadsheet Analysis and Modeling",
"out_of_scope": "SQL querying and database design, statistical programming in Python or R, enterprise BI dashboarding in Power BI or Tableau, data engineering pipelines and ETL orchestration",
"overlap_flags": [
{
"reason": "Excel is often used to combine and reshape small datasets, but that dimension owns multi-source preparation and transformation logic.",
"with_dim_id": "data-preparation-and-blending",
"with_dim_name": null,
"with_role": null
},
{
"reason": "Excel can support analysis workflows, but notebooks own scripted, reproducible analytical work.",
"with_dim_id": "notebook-and-reproducible-analysis-workflow",
"with_dim_name": null,
"with_role": null
}
],
"tentative_id": "d_init_01"
}
],
"merge_log": [],
"placed": {
"name": "Excel",
"placement_confidence": 0.92,
"primary_dimension": "d_init_01",
"reasoning": "Deterministic JD placement: locked_dimensions has 1 dimension(s) from skill-driven dimension generation after reconciliation; primary_dimension is the first locked dim.",
"secondary_dimensions": [],
"skill_id": "excel"
},
"relationships": {
"child_skills": [],
"parent_skills": [],
"related_to": [
"dashboards",
"scorecards",
"summary-statistics",
"outlier-detection",
"error-analysis"
],
"requires": [],
"skill_id": "excel",
"suppress_on_match": []
},
"skill_id": "excel",
"split_log": [],
"typed": {
"alternatives_considered": [],
"confidence": 0.98,
"name": "Excel",
"reasoning": "Excel is software you operate directly as a user rather than a hosted multi-tenant environment, so by the Tool vs Platform rule it is a Tool.",
"skill_id": "excel",
"subtype": "spreadsheet_software",
"type": "Tool"
},
"warnings": []
},
"source_tag": "llm",
"was_in_llm_skills": true
},
{
"aliases_in_db": [],
"canonical": null,
"dimensions": [
{
"dimension": {
"difficulty_hint": null,
"display_name": "Functional Requirements Documentation",
"id": null,
"rationale": "Covers writing and maintaining functional requirements documents that define what a product or process must do. FRDs belong here because they capture business needs, scope, rules, and acceptance expectations in a formal requirements artifact.",
"slug": "d_init_01",
"source": "llm"
},
"input_skill": "FRDs",
"llm_role": null,
"roles_from_db": []
}
],
"input_skill": "FRDs",
"matched_via": null,
"new_alias_persisted": false,
"new_alias_text": null,
"new_skill_meta": {
"derived": {
"category": "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",
"stakeholder review",
"business rules",
"process flows",
"wireframes",
"UAT",
"sign-off",
"non-functional requirements"
]
},
"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; no vendor sunset or replacement has displaced them."
},
"skill_id": "frds",
"vendor_license": {
"confidence": 0.98,
"license": null,
"vendor": null,
"year_introduced": null
},
"versioning": {
"current_version": null,
"version_aliases": {},
"versioned": false
}
},
"keep_log": [],
"locked_dimensions": [
{
"description": "Covers writing and maintaining functional requirements documents that define what a product or process must do. FRDs belong here because they capture business needs, scope, rules, and acceptance expectations in a formal requirements artifact.",
"exemplar_skills": [
"FRDs",
"functional requirements documentation",
"requirements elicitation",
"business requirements analysis",
"acceptance criteria definition",
"scope definition"
],
"in_scope": "FRDs, functional requirements documents, business requirements capture, scope definition, process rules, acceptance criteria, requirement traceability",
"name": "Functional Requirements Documentation",
"out_of_scope": "Technical design specs, API implementation details, test execution, project planning, which belong to architecture, engineering, QA, or delivery management dimensions",
"overlap_flags": [
{
"reason": "FRDs often inform test cases, but this dimension focuses on documenting requirements rather than executing validation.",
"with_dim_id": "test-case-design-and-execution",
"with_dim_name": null,
"with_role": null
},
{
"reason": "Requirements may constrain service design, but architecture owns the technical decomposition and integration approach.",
"with_dim_id": "service-architecture-and-integration",
"with_dim_name": null,
"with_role": null
}
],
"tentative_id": "d_init_01"
}
],
"merge_log": [],
"placed": {
"name": "FRDs",
"placement_confidence": 0.92,
"primary_dimension": "d_init_01",
"reasoning": "Deterministic JD placement: locked_dimensions has 1 dimension(s) from skill-driven dimension generation after reconciliation; primary_dimension is the first locked dim.",
"secondary_dimensions": [],
"skill_id": "frds"
},
"relationships": {
"child_skills": [],
"parent_skills": [],
"related_to": [
"change-requests",
"contract-tests",
"risk-based-testing",
"runbooks",
"rollback-readiness"
],
"requires": [],
"skill_id": "frds",
"suppress_on_match": []
},
"skill_id": "frds",
"split_log": [],
"typed": {
"alternatives_considered": [
"Format: ruled out \u2014 although it is a document, the skill name refers to the requirements artifact as a concept, not a data structure or wire format.",
"Domain: ruled out \u2014 it is not a vertical industry or problem-space body of knowledge."
],
"confidence": 0.78,
"name": "FRDs",
"reasoning": "FRDs are a named knowledge unit describing requirements, so by the Concept vs Methodology rule they fit Concept rather than a tool or format.",
"skill_id": "frds",
"subtype": "functional_requirements_document",
"type": "Concept"
},
"warnings": []
},
"source_tag": "llm",
"was_in_llm_skills": true
},
{
"aliases_in_db": [],
"canonical": null,
"dimensions": [
{
"dimension": {
"difficulty_hint": null,
"display_name": "Domain Familiarity",
"id": null,
"rationale": "General working familiarity with a business or technical domain, enough to understand terminology, workflows, and stakeholder needs. This fits the target skill because it signals breadth of exposure rather than deep implementation expertise.",
"slug": "d_init_01",
"source": "llm"
},
"input_skill": "Familiarity",
"llm_role": null,
"roles_from_db": []
}
],
"input_skill": "Familiarity",
"matched_via": null,
"new_alias_persisted": false,
"new_alias_text": null,
"new_skill_meta": {
"derived": {
"category": "Concept",
"skill_nature": "CONCEPT",
"sub_category": "familiarity",
"typical_lifespan": "EVERGREEN",
"version_strategy": "NOT_APPLICABLE",
"volatility": "STABLE"
},
"enrichment": {
"ambiguity": {
"ambiguity_flag": false,
"confused_with": [],
"reasoning": "\u201cFamiliarity\u201d is a generic concept, but it is not a specific skill name likely to be confused with another catalog entry in a JD."
},
"context_keywords": {
"context_keywords": [
"working knowledge",
"hands-on experience",
"exposure to",
"awareness of",
"proficiency",
"competency",
"understanding of",
"practical experience",
"familiar with",
"knowledge of",
"experience with",
"basic understanding",
"prior exposure",
"subject matter",
"domain knowledge"
]
},
"maturity": {
"confidence": 0.86,
"maturity": "niche",
"reasoning": "\u201cFamiliarity\u201d is a generic concept, not a commonly listed skill in job descriptions; market signals are sparse compared with concrete tools/tech, so it appears only in narrow competency frameworks."
},
"skill_id": "familiarity",
"vendor_license": {
"confidence": 0.99,
"license": null,
"vendor": null,
"year_introduced": null
},
"versioning": {
"current_version": null,
"version_aliases": {},
"versioned": false
}
},
"keep_log": [],
"locked_dimensions": [
{
"description": "General working familiarity with a business or technical domain, enough to understand terminology, workflows, and stakeholder needs. This fits the target skill because it signals breadth of exposure rather than deep implementation expertise.",
"exemplar_skills": [
"Familiarity",
"Domain familiarity",
"Business domain awareness",
"Process awareness",
"Stakeholder context understanding"
],
"in_scope": "Familiarity, domain terminology, business process awareness, stakeholder context, product and workflow exposure, cross-functional communication, industry concepts",
"name": "Domain Familiarity",
"out_of_scope": "Hands-on process ownership, requirements elicitation, data analysis techniques, technical implementation, project management, subject-matter expertise",
"overlap_flags": [
{
"reason": "Domain familiarity can overlap with understanding service landscapes, but that dimension owns concrete architecture and integration patterns.",
"with_dim_id": "service-architecture-and-integration",
"with_dim_name": null,
"with_role": null
},
{
"reason": "Familiarity with data concepts may support analysis work, but this dimension owns the actual preparation and transformation skills.",
"with_dim_id": "data-preparation-and-blending",
"with_dim_name": null,
"with_role": null
}
],
"tentative_id": "d_init_01"
}
],
"merge_log": [],
"placed": {
"name": "Familiarity",
"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": "familiarity"
},
"relationships": {
"child_skills": [],
"parent_skills": [],
"related_to": [],
"requires": [],
"skill_id": "familiarity",
"suppress_on_match": []
},
"skill_id": "familiarity",
"split_log": [],
"typed": {
"alternatives_considered": [
"SoftSkill: ruled out \u2014 it is not primarily an interpersonal capability.",
"Methodology: ruled out \u2014 it does not describe a process or operating method."
],
"confidence": 0.88,
"name": "Familiarity",
"reasoning": "Familiarity is a named knowledge unit about recognition or prior exposure, so by the Concept vs Methodology rule it is a Concept rather than a way of working.",
"skill_id": "familiarity",
"subtype": "familiarity",
"type": "Concept"
},
"warnings": []
},
"source_tag": "llm",
"was_in_llm_skills": true
},
{
"aliases_in_db": [],
"canonical": null,
"dimensions": [
{
"dimension": {
"difficulty_hint": null,
"display_name": "Domain Knowledge and Business Context",
"id": null,
"rationale": "Knowledge of the business domain, processes, terminology, and operating context used to interpret requirements and make sound decisions. For a Business Analyst, this is the core subject-matter understanding behind analysis, stakeholder communication, and solution framing.",
"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",
"institutional knowledge",
"knowledge base",
"knowledge management",
"knowledge transfer",
"best practices",
"lessons learned",
"documentation",
"taxonomy",
"ontology",
"information architecture",
"expertise",
"procedures",
"playbook"
]
},
"maturity": {
"confidence": 0.93,
"maturity": "niche",
"reasoning": "\u201cKnowledge\u201d is a generic concept, not a specific engineering skill; it rarely appears as a standalone requirement in job descriptions compared with concrete tools or languages."
},
"skill_id": "knowledge",
"vendor_license": {
"confidence": 0.99,
"license": null,
"vendor": null,
"year_introduced": null
},
"versioning": {
"current_version": null,
"version_aliases": {},
"versioned": false
}
},
"keep_log": [],
"locked_dimensions": [
{
"description": "Knowledge of the business domain, processes, terminology, and operating context used to interpret requirements and make sound decisions. For a Business Analyst, this is the core subject-matter understanding behind analysis, stakeholder communication, and solution framing.",
"exemplar_skills": [
"Knowledge",
"business domain knowledge",
"process knowledge",
"business rules understanding",
"stakeholder context awareness",
"industry knowledge"
],
"in_scope": "Knowledge, business domain understanding, process knowledge, terminology, operating model, stakeholder context, regulatory context, product knowledge, business rules, workflow understanding, industry concepts",
"name": "Domain Knowledge and Business Context",
"out_of_scope": "Data quality assessment, technical platform administration, coding, testing, and infrastructure operations, which belong to specialized engineering or QA dimensions.",
"overlap_flags": [
{
"reason": "Business context can inform service boundaries and integration decisions, but the architectural design itself belongs to the service architecture dimension.",
"with_dim_id": "service-architecture-and-integration",
"with_dim_name": null,
"with_role": null
},
{
"reason": "Domain knowledge often guides how data is interpreted and combined, but the actual joining and reshaping work belongs to data preparation.",
"with_dim_id": "data-preparation-and-blending",
"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.95,
"name": "Knowledge",
"reasoning": "Knowledge is a named body of understanding rather than a system, process, or artifact, so it fits the Concept category by the Concept vs Methodology rule.",
"skill_id": "knowledge",
"subtype": "general_knowledge",
"type": "Concept"
},
"warnings": []
},
"source_tag": "llm",
"was_in_llm_skills": true
},
{
"aliases_in_db": [],
"canonical": null,
"dimensions": [
{
"dimension": {
"difficulty_hint": null,
"display_name": "Quality Assurance Testing",
"id": null,
"rationale": "Validating that a product, feature, or process meets requirements through structured testing and defect checking. QA belongs here when it refers to general assurance work rather than a specific automation or platform discipline.",
"slug": "d_init_01",
"source": "llm"
},
"input_skill": "QA",
"llm_role": null,
"roles_from_db": []
}
],
"input_skill": "QA",
"matched_via": null,
"new_alias_persisted": false,
"new_alias_text": null,
"new_skill_meta": {
"derived": {
"category": "Methodology",
"skill_nature": "METHODOLOGY",
"sub_category": "quality_assurance",
"typical_lifespan": "EVERGREEN",
"version_strategy": "NOT_APPLICABLE",
"volatility": "STABLE"
},
"enrichment": {
"ambiguity": {
"ambiguity_flag": true,
"confused_with": [
"quality_control",
"test_automation"
],
"reasoning": "\"QA\" is a common abbreviation for Quality Assurance, but in JDs it can also be used loosely for quality control or testing roles, so an extractor could confuse it with nearby catalog skills."
},
"context_keywords": {
"context_keywords": [
"test cases",
"test plan",
"test strategy",
"regression testing",
"smoke testing",
"UAT",
"defect tracking",
"bug triage",
"test automation",
"Selenium",
"JIRA",
"manual testing",
"acceptance criteria",
"traceability matrix"
]
},
"maturity": {
"confidence": 0.93,
"maturity": "well_known",
"reasoning": "QA is a standard hiring requirement across software roles; job postings commonly list test planning, manual/automated QA, and defect tracking, and it remains a core function in enterprise SDLCs."
},
"skill_id": "qa",
"vendor_license": {
"confidence": 0.99,
"license": null,
"vendor": null,
"year_introduced": null
},
"versioning": {
"current_version": null,
"version_aliases": {},
"versioned": false
}
},
"keep_log": [],
"locked_dimensions": [
{
"description": "Validating that a product, feature, or process meets requirements through structured testing and defect checking. QA belongs here when it refers to general assurance work rather than a specific automation or platform discipline.",
"exemplar_skills": [
"QA",
"manual testing",
"test case design",
"test execution",
"regression testing",
"defect verification"
],
"in_scope": "QA, manual testing, test case design, test execution, regression testing, smoke testing, acceptance testing, exploratory testing, defect verification, test evidence, test reporting",
"name": "Quality Assurance Testing",
"out_of_scope": "Automated API test suites, unit test framework code, performance/load testing, business analysis, production monitoring",
"overlap_flags": [
{
"reason": "This is the closest catalog concept for manual test design and execution, but it is not available as a reusable catalog id in the required pattern.",
"with_dim_id": "test-case-design-and-execution",
"with_dim_name": null,
"with_role": null
},
{
"reason": "QA can include backend validation, but that dimension owns automated API and service-level testing rather than general assurance work.",
"with_dim_id": "api-and-service-test-automation",
"with_dim_name": null,
"with_role": null
},
{
"reason": "QA may use test tools, but this dimension specifically covers automation frameworks and code-based test infrastructure.",
"with_dim_id": "testing-and-automation-frameworks",
"with_dim_name": null,
"with_role": null
}
],
"tentative_id": "d_init_01"
}
],
"merge_log": [],
"placed": {
"name": "QA",
"placement_confidence": 0.92,
"primary_dimension": "d_init_01",
"reasoning": "Deterministic JD placement: locked_dimensions has 1 dimension(s) from skill-driven dimension generation after reconciliation; primary_dimension is the first locked dim.",
"secondary_dimensions": [],
"skill_id": "qa"
},
"relationships": {
"child_skills": [],
"parent_skills": [],
"related_to": [
"acceptance-criteria-checks",
"acceptance-criteria-validation",
"test-case-authoring",
"risk-based-testing",
"cross-browser-testing",
"session-based-testing",
"charter-based-testing",
"defect-retest",
"health-checks"
],
"requires": [],
"skill_id": "qa",
"suppress_on_match": []
},
"skill_id": "qa",
"split_log": [],
"typed": {
"alternatives_considered": [
"Concept: ruled out \u2014 QA is an applied practice area, not a single knowledge unit.",
"SoftSkill: ruled out \u2014 QA is not primarily an interpersonal capability.",
"Domain: ruled out \u2014 QA is not a vertical or problem-space body of knowledge."
],
"confidence": 0.82,
"name": "QA",
"reasoning": "QA is best treated as a way of working focused on assuring quality, so under the Concept vs Methodology rule it fits Methodology rather than a standalone concept.",
"skill_id": "qa",
"subtype": "quality_assurance",
"type": "Methodology"
},
"warnings": []
},
"source_tag": "llm",
"was_in_llm_skills": true
},
{
"aliases_in_db": [],
"canonical": null,
"dimensions": [
{
"dimension": {
"difficulty_hint": null,
"display_name": "Software Delivery Lifecycle",
"id": null,
"rationale": "Covers the end-to-end process used to plan, build, test, release, and maintain software changes. SDLC belongs here because it refers to the overall lifecycle and governance of delivery work rather than a single technical practice.",
"slug": "d_init_01",
"source": "llm"
},
"input_skill": "SDLC",
"llm_role": null,
"roles_from_db": []
}
],
"input_skill": "SDLC",
"matched_via": null,
"new_alias_persisted": false,
"new_alias_text": null,
"new_skill_meta": {
"derived": {
"category": "Methodology",
"skill_nature": "METHODOLOGY",
"sub_category": "software_development_lifecycle",
"typical_lifespan": "EVERGREEN",
"version_strategy": "NOT_APPLICABLE",
"volatility": "STABLE"
},
"enrichment": {
"ambiguity": {
"ambiguity_flag": false,
"confused_with": [],
"reasoning": "SDLC is a standard, well-known acronym for software development lifecycle and is usually unambiguous in job descriptions."
},
"context_keywords": {
"context_keywords": [
"requirements gathering",
"design review",
"implementation",
"code review",
"testing",
"QA",
"UAT",
"deployment",
"release management",
"CI/CD",
"Agile",
"Scrum",
"waterfall",
"change management",
"defect tracking"
]
},
"maturity": {
"confidence": 0.93,
"maturity": "well_known",
"reasoning": "SDLC is a standard term in software job descriptions and enterprise process docs; it appears broadly across hiring pipelines and vendor frameworks like Agile/DevOps rather than as a niche tool."
},
"skill_id": "sdlc",
"vendor_license": {
"confidence": 0.99,
"license": null,
"vendor": null,
"year_introduced": null
},
"versioning": {
"current_version": null,
"version_aliases": {},
"versioned": false
}
},
"keep_log": [],
"locked_dimensions": [
{
"description": "Covers the end-to-end process used to plan, build, test, release, and maintain software changes. SDLC belongs here because it refers to the overall lifecycle and governance of delivery work rather than a single technical practice.",
"exemplar_skills": [
"SDLC",
"software development lifecycle",
"release management",
"change control",
"development workflow",
"requirements to deployment process"
],
"in_scope": "SDLC, requirements gathering, design, implementation, testing, release management, maintenance, change control, versioning, development workflow, delivery governance",
"name": "Software Delivery Lifecycle",
"out_of_scope": "Unit test frameworks, API test automation, environment provisioning, cloud deployment mechanics, incident response, product strategy, business analysis artifacts, which belong to more specific engineering or business dimensions",
"overlap_flags": [
{
"reason": "SDLC includes testing as one phase, but detailed test design and execution are owned by the testing dimension.",
"with_dim_id": "test-case-design-and-execution",
"with_dim_name": null,
"with_role": null
},
{
"reason": "SDLC may reference promotion across environments, but environment setup and promotion mechanics are a separate operational cluster.",
"with_dim_id": "environment-provisioning-and-promotion",
"with_dim_name": null,
"with_role": null
},
{
"reason": "SDLC can touch design and implementation, but service decomposition and integration patterns are a distinct architecture concern.",
"with_dim_id": "service-architecture-and-integration",
"with_dim_name": null,
"with_role": null
}
],
"tentative_id": "d_init_01"
}
],
"merge_log": [],
"placed": {
"name": "SDLC",
"placement_confidence": 0.92,
"primary_dimension": "d_init_01",
"reasoning": "Deterministic JD placement: locked_dimensions has 1 dimension(s) from skill-driven dimension generation after reconciliation; primary_dimension is the first locked dim.",
"secondary_dimensions": [],
"skill_id": "sdlc"
},
"relationships": {
"child_skills": [],
"parent_skills": [],
"related_to": [
"clean-architecture",
"acceptance-criteria-checks",
"acceptance-criteria-validation",
"defect-retest",
"dependency-mapping",
"dashboards",
"scorecards"
],
"requires": [],
"skill_id": "sdlc",
"suppress_on_match": []
},
"skill_id": "sdlc",
"split_log": [],
"typed": {
"alternatives_considered": [],
"confidence": 0.88,
"name": "SDLC",
"reasoning": "SDLC is best treated as a Methodology because it describes the process and phases for how software is developed and delivered, not a system shape or a knowledge unit.",
"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 Delivery",
"id": null,
"rationale": "Covers software delivered as a hosted subscription service, including multi-tenant product packaging, release cadence, and customer-facing service operations. SaaS belongs here because it describes the delivery model and operating context for the product rather than a specific technical component.",
"slug": "d_init_01",
"source": "llm"
},
"input_skill": "SaaS",
"llm_role": null,
"roles_from_db": []
},
{
"dimension": {
"difficulty_hint": null,
"display_name": "Software Subscription Business Models",
"id": null,
"rationale": "Covers the commercial and operational model of selling software as a recurring subscription service. This fits SaaS when the skill is used in business analysis, pricing, packaging, and customer lifecycle discussions.",
"slug": "d_init_02",
"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": [
"subscription billing",
"multi-tenant",
"tenant isolation",
"self-service onboarding",
"usage-based pricing",
"SAML",
"SSO",
"RBAC",
"API integrations",
"webhooks",
"customer provisioning",
"admin console",
"trial conversion",
"churn",
"renewals"
]
},
"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 Atlassian market core offerings as SaaS, indicating broad adoption."
},
"skill_id": "saas",
"vendor_license": {
"confidence": 0.88,
"license": null,
"vendor": null,
"year_introduced": 1999
},
"versioning": {
"current_version": null,
"version_aliases": {},
"versioned": false
}
},
"keep_log": [],
"locked_dimensions": [
{
"description": "Covers software delivered as a hosted subscription service, including multi-tenant product packaging, release cadence, and customer-facing service operations. SaaS belongs here because it describes the delivery model and operating context for the product rather than a specific technical component.",
"exemplar_skills": [
"SaaS",
"multi-tenant architecture",
"subscription software",
"hosted application delivery",
"tenant isolation",
"service tiers",
"usage-based billing"
],
"in_scope": "SaaS, subscription software, multi-tenant application delivery, hosted web application, tenant isolation, release management for SaaS, service tiers, usage-based entitlements, customer onboarding flows",
"name": "SaaS Product Delivery",
"out_of_scope": "on-premises software deployment, mobile app distribution, internal tooling, cloud infrastructure provisioning, API design, which belong to other platform or architecture dimensions",
"overlap_flags": [
{
"reason": "SaaS products are often built from services, but this dimension focuses on the delivery model and customer-facing operating context rather than service decomposition.",
"with_dim_id": "service-architecture-and-integration",
"with_dim_name": null,
"with_role": null
},
{
"reason": "Teams may move products into SaaS form during modernization, but that dimension covers the transition plan, not the SaaS model itself.",
"with_dim_id": "migration-and-modernization-planning",
"with_dim_name": null,
"with_role": null
}
],
"tentative_id": "d_init_01"
},
{
"description": "Covers the commercial and operational model of selling software as a recurring subscription service. This fits SaaS when the skill is used in business analysis, pricing, packaging, and customer lifecycle discussions.",
"exemplar_skills": [
"SaaS",
"subscription pricing",
"freemium model",
"trial conversion",
"seat-based licensing",
"customer retention",
"recurring revenue"
],
"in_scope": "SaaS, recurring subscriptions, annual and monthly plans, freemium models, trials, seat-based licensing, billing cycles, customer retention, churn, plan packaging",
"name": "Software Subscription Business Models",
"out_of_scope": "technical hosting architecture, API implementation, cloud security controls, which belong to engineering or platform dimensions",
"overlap_flags": [
{
"reason": "SaaS offerings may be implemented as services, but this dimension is about the commercial model rather than system integration.",
"with_dim_id": "service-architecture-and-integration",
"with_dim_name": null,
"with_role": null
}
],
"tentative_id": "d_init_02"
}
],
"merge_log": [],
"placed": {
"name": "SaaS",
"placement_confidence": 0.92,
"primary_dimension": "d_init_01",
"reasoning": "Deterministic JD placement: locked_dimensions has 2 dimension(s) from skill-driven dimension generation after reconciliation; primary_dimension is the first locked dim.",
"secondary_dimensions": [
"d_init_02"
],
"skill_id": "saas"
},
"relationships": {
"child_skills": [],
"parent_skills": [],
"related_to": [
"cloud-run",
"azure-backup",
"cspm",
"policy-as-code",
"cloud-reference-architecture"
],
"requires": [],
"skill_id": "saas",
"suppress_on_match": []
},
"skill_id": "saas",
"split_log": [],
"typed": {
"alternatives_considered": [],
"confidence": 0.9,
"name": "SaaS",
"reasoning": "By the Platform vs Tool rule, SaaS is a hosted multi-tenant environment delivered over APIs and managed services rather than software you run yourself.",
"skill_id": "saas",
"subtype": "software_as_a_service_platform",
"type": "Platform"
},
"warnings": []
},
"source_tag": "llm",
"was_in_llm_skills": true
},
{
"aliases_in_db": [],
"canonical": null,
"dimensions": [],
"input_skill": "Testing",
"matched_via": null,
"new_alias_persisted": false,
"new_alias_text": null,
"new_skill_meta": {
"derived": {
"category": "Methodology",
"skill_nature": "METHODOLOGY",
"sub_category": "software_testing_methodology",
"typical_lifespan": "EVERGREEN",
"version_strategy": "NOT_APPLICABLE",
"volatility": "STABLE"
},
"enrichment": {
"ambiguity": {
"ambiguity_flag": true,
"confused_with": [
"unit_testing",
"integration_testing",
"automated_testing",
"qa",
"test_automation"
],
"reasoning": "\"Testing\" is very broad in JDs and can refer to specific software testing disciplines or QA work rather than the generic methodology, so extractors could map it to related testing skills."
},
"context_keywords": {
"context_keywords": [
"unit testing",
"integration testing",
"test automation",
"test cases",
"test plan",
"regression testing",
"smoke testing",
"mocking",
"stubs",
"fixtures",
"assertions",
"TDD",
"BDD",
"Selenium",
"JUnit"
]
},
"maturity": {
"confidence": 0.97,
"maturity": "well_known",
"reasoning": "Software testing is a hiring-pipeline staple across JDs for QA, SDET, and backend roles; CI/CD and automation tooling have made it a standard requirement 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
}
},
"keep_log": [],
"locked_dimensions": [],
"merge_log": [
{
"a_dim_id": "d_init_01",
"a_name": "Test Case Design and Execution",
"a_role": "__skill_focal__",
"b_dim_id": "test-case-design-and-execution",
"b_name": "Test Case Design and Execution",
"b_role": "Manual Tester",
"into": "d_merge_01",
"into_name": "Manual Test Case Design and Execution",
"merged_from": [
"d_init_01",
"test-case-design-and-execution"
],
"pair_kind": "cross_role",
"reasoning": "Both dims describe the same manual QA activity: designing, reviewing, and executing human-run test cases to verify requirements, acceptance criteria, workflows, fixes, and regressions. Dim A\u2019s exemplars (manual testing, test case design, regression testing, user acceptance testing) match Dim B\u2019s core description almost exactly. The extra business-analyst framing in A does not create a distinct skill cluster; it is still the same manual test case design/execution work.",
"similarity": 0.8499528012426355
}
],
"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": [
"restore-testing",
"session-based-testing",
"risk-based-testing",
"cross-browser-testing",
"defect-retest",
"charter-based-testing",
"smoke-testing",
"fuzzing"
],
"requires": [],
"skill_id": "testing",
"suppress_on_match": []
},
"skill_id": "testing",
"split_log": [],
"typed": {
"alternatives_considered": [],
"confidence": 0.91,
"name": "Testing",
"reasoning": "By the Concept vs Methodology rule, Testing is fundamentally a way of working for validating software rather than a single knowledge unit or tool.",
"skill_id": "testing",
"subtype": "software_testing_methodology",
"type": "Methodology"
},
"warnings": [
"placement_stub_no_locked_dimensions"
]
},
"source_tag": "llm",
"was_in_llm_skills": true
},
{
"aliases_in_db": [],
"canonical": null,
"dimensions": [
{
"dimension": {
"difficulty_hint": null,
"display_name": "User Acceptance Testing",
"id": null,
"rationale": "Validating that a delivered feature meets business requirements and is ready for user sign-off. UAT belongs here because it is the business-facing execution of acceptance scenarios before release.",
"slug": "d_init_01",
"source": "llm"
},
"input_skill": "UAT",
"llm_role": null,
"roles_from_db": []
}
],
"input_skill": "UAT",
"matched_via": null,
"new_alias_persisted": false,
"new_alias_text": null,
"new_skill_meta": {
"derived": {
"category": "Methodology",
"skill_nature": "METHODOLOGY",
"sub_category": "user_acceptance_testing",
"typical_lifespan": "EVERGREEN",
"version_strategy": "NOT_APPLICABLE",
"volatility": "STABLE"
},
"enrichment": {
"ambiguity": {
"ambiguity_flag": false,
"confused_with": [],
"reasoning": "UAT in JDs almost always means User Acceptance Testing; the acronym is standard and unlikely to be mistaken for another catalog skill in typical hiring context."
},
"context_keywords": {
"context_keywords": [
"test cases",
"acceptance criteria",
"business users",
"end users",
"sign-off",
"test scripts",
"defect triage",
"test plan",
"test scenarios",
"regression testing",
"stakeholder review",
"go-live",
"test execution",
"requirements validation"
]
},
"maturity": {
"confidence": 0.86,
"maturity": "well_known",
"reasoning": "UAT is a standard QA phase in many software JDs and delivery pipelines; market listings commonly mention user acceptance testing alongside QA, test planning, and release sign-off."
},
"skill_id": "uat",
"vendor_license": {
"confidence": 0.99,
"license": null,
"vendor": null,
"year_introduced": null
},
"versioning": {
"current_version": null,
"version_aliases": {},
"versioned": false
}
},
"keep_log": [],
"locked_dimensions": [
{
"description": "Validating that a delivered feature meets business requirements and is ready for user sign-off. UAT belongs here because it is the business-facing execution of acceptance scenarios before release.",
"exemplar_skills": [
"UAT",
"user acceptance testing",
"acceptance criteria validation",
"business scenario testing",
"end-user sign-off"
],
"in_scope": "UAT, user acceptance testing, acceptance criteria validation, business scenario walkthroughs, end-user sign-off testing, defect logging from acceptance runs",
"name": "User Acceptance Testing",
"out_of_scope": "Automated unit tests, API regression suites, performance testing, production monitoring, which belong to engineering test automation or operations dimensions",
"overlap_flags": [
{
"reason": "UAT overlaps with manual test execution, but this catalog dimension is specifically for broader test case design and execution rather than business acceptance sign-off.",
"with_dim_id": "test-case-design-and-execution",
"with_dim_name": null,
"with_role": null
},
{
"reason": "UAT may validate service behavior indirectly, but automated API and service checks are owned by the backend test automation dimension.",
"with_dim_id": "api-and-service-test-automation",
"with_dim_name": null,
"with_role": null
}
],
"tentative_id": "d_init_01"
}
],
"merge_log": [],
"placed": {
"name": "UAT",
"placement_confidence": 0.92,
"primary_dimension": "d_init_01",
"reasoning": "Deterministic JD placement: locked_dimensions has 1 dimension(s) from skill-driven dimension generation after reconciliation; primary_dimension is the first locked dim.",
"secondary_dimensions": [],
"skill_id": "uat"
},
"relationships": {
"child_skills": [],
"parent_skills": [],
"related_to": [
"acceptance-criteria-checks",
"session-based-testing",
"test-case-authoring"
],
"requires": [],
"skill_id": "uat",
"suppress_on_match": []
},
"skill_id": "uat",
"split_log": [],
"typed": {
"alternatives_considered": [],
"confidence": 0.93,
"name": "UAT",
"reasoning": "UAT is a way of working in which users validate the system before release, so by the Concept vs Methodology rule it is a Methodology rather than a Concept or Tool.",
"skill_id": "uat",
"subtype": "user_acceptance_testing",
"type": "Methodology"
},
"warnings": []
},
"source_tag": "llm",
"was_in_llm_skills": true
},
{
"aliases_in_db": [],
"canonical": null,
"dimensions": [
{
"dimension": {
"difficulty_hint": null,
"display_name": "Requirements and Domain Understanding",
"id": null,
"rationale": "Interpreting business needs, user goals, and process context well enough to translate them into clear requirements and analysis artifacts. This fits the target skill because business analysts are often evaluated on how well they understand the problem space before proposing solutions.",
"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_customer_needs",
"understanding_business_requirements"
],
"reasoning": "\"Understanding\" is a generic noun in JDs and could easily be parsed as broader comprehension or as part of phrases like understanding customer needs/business requirements, rather than a distinct skill."
},
"context_keywords": {
"context_keywords": [
"requirements analysis",
"stakeholder needs",
"problem framing",
"root cause analysis",
"domain knowledge",
"business context",
"specification",
"interpretation",
"critical thinking",
"systems thinking",
"user stories",
"acceptance criteria",
"gap analysis",
"decision making"
]
},
"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
}
},
"keep_log": [],
"locked_dimensions": [
{
"description": "Interpreting business needs, user goals, and process context well enough to translate them into clear requirements and analysis artifacts. This fits the target skill because business analysts are often evaluated on how well they understand the problem space before proposing solutions.",
"exemplar_skills": [
"Understanding",
"Requirements Gathering",
"Business Process Analysis",
"Stakeholder Analysis",
"Gap Analysis",
"Use Case Analysis",
"Acceptance Criteria Definition"
],
"in_scope": "Understanding, requirements elicitation, business process analysis, stakeholder needs analysis, problem framing, current-state and future-state analysis, use cases, acceptance criteria, gap analysis",
"name": "Requirements and Domain Understanding",
"out_of_scope": "Technical implementation details, data pipeline design, UI styling, and platform administration, which belong to engineering or delivery-specific dimensions.",
"overlap_flags": [
{
"reason": "Some business analysis work touches service boundaries and integration constraints, but this dimension focuses on the business interpretation rather than system design.",
"with_dim_id": "service-architecture-and-integration",
"with_dim_name": null,
"with_role": null
},
{
"reason": "Understanding source data and reporting inputs can overlap with analysis-ready data shaping, but that dimension owns the actual transformation work.",
"with_dim_id": "data-preparation-and-blending",
"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": [],
"requires": [],
"skill_id": "understanding",
"suppress_on_match": []
},
"skill_id": "understanding",
"split_log": [],
"typed": {
"alternatives_considered": [],
"confidence": 0.97,
"name": "Understanding",
"reasoning": "Understanding is a named knowledge unit rather than a way of working, so by the Concept vs Methodology rule it is a 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, swimlanes, org charts, and system diagrams for analysis and documentation.",
"slug": "d_init_01",
"source": "llm"
},
"input_skill": "Visio",
"llm_role": null,
"roles_from_db": []
},
{
"dimension": {
"difficulty_hint": null,
"display_name": "Business Analysis Documentation",
"id": null,
"rationale": "Documenting business requirements, current-state and future-state processes, and stakeholder-facing artifacts. Visio fits when used by a Business Analyst to capture process flows and support requirements communication.",
"slug": "d_init_02",
"source": "llm"
},
"input_skill": "Visio",
"llm_role": null,
"roles_from_db": []
}
],
"input_skill": "Visio",
"matched_via": null,
"new_alias_persisted": false,
"new_alias_text": null,
"new_skill_meta": {
"derived": {
"category": "Tool",
"skill_nature": "TOOL",
"sub_category": "diagramming_tool",
"typical_lifespan": "EVERGREEN",
"version_strategy": "NOT_APPLICABLE",
"volatility": "STABLE"
},
"enrichment": {
"ambiguity": {
"ambiguity_flag": false,
"confused_with": [],
"reasoning": "Visio is a specific Microsoft diagramming tool; in typical JDs it is unlikely to be confused with another catalog skill."
},
"context_keywords": {
"context_keywords": [
"flowchart",
"swimlane",
"BPMN",
"UML",
"process map",
"network diagram",
"org chart",
"wireframe",
"data flow diagram",
"ERD",
"business process",
"workflow",
"site map",
"cross-functional diagram",
"stencil"
]
},
"maturity": {
"confidence": 0.84,
"maturity": "well_known",
"reasoning": "Common in enterprise JDs for process/network diagrams and Microsoft 365 environments; no vendor sunset, and it remains a standard diagramming tool alongside newer alternatives."
},
"skill_id": "visio",
"vendor_license": {
"confidence": 0.99,
"license": "proprietary",
"vendor": "Microsoft",
"year_introduced": 1992
},
"versioning": {
"current_version": null,
"version_aliases": {},
"versioned": false
}
},
"keep_log": [],
"locked_dimensions": [
{
"description": "Creating business and technical diagrams to communicate workflows, systems, and relationships. Visio belongs here because it is commonly used to draw process maps, swimlanes, org charts, and system diagrams for analysis and documentation.",
"exemplar_skills": [
"Visio",
"flowchart creation",
"swimlane diagramming",
"process mapping",
"org chart design",
"system diagramming"
],
"in_scope": "Visio, process maps, flowcharts, swimlane diagrams, org charts, UML-style diagrams, system context diagrams, business process modeling, wireframes, cross-functional documentation",
"name": "Diagramming and Process Modeling",
"out_of_scope": "Spreadsheet analysis, requirements elicitation notes, database design, and code-level modeling, which belong to other analysis or engineering dimensions",
"overlap_flags": [
{
"reason": "System and integration diagrams can overlap with architecture work, but this dimension focuses on communication artifacts rather than backend design decisions.",
"with_dim_id": "service-architecture-and-integration",
"with_dim_name": null,
"with_role": null
}
],
"tentative_id": "d_init_01"
},
{
"description": "Documenting business requirements, current-state and future-state processes, and stakeholder-facing artifacts. Visio fits when used by a Business Analyst to capture process flows and support requirements communication.",
"exemplar_skills": [
"Visio",
"business process documentation",
"current-state mapping",
"future-state mapping",
"requirements diagrams",
"gap analysis visuals"
],
"in_scope": "Visio, business process documentation, current-state mapping, future-state mapping, requirements diagrams, stakeholder review artifacts, gap analysis visuals, SOP diagrams",
"name": "Business Analysis Documentation",
"out_of_scope": "Formal project planning, test execution, data modeling, and software implementation details, which are owned by planning, QA, or engineering dimensions",
"overlap_flags": [
{
"reason": "Some BA diagrams may describe data movement, but this dimension is about business documentation rather than data transformation work.",
"with_dim_id": "data-preparation-and-blending",
"with_dim_name": null,
"with_role": null
}
],
"tentative_id": "d_init_02"
}
],
"merge_log": [],
"placed": {
"name": "Visio",
"placement_confidence": 0.92,
"primary_dimension": "d_init_01",
"reasoning": "Deterministic JD placement: locked_dimensions has 2 dimension(s) from skill-driven dimension generation after reconciliation; primary_dimension is the first locked dim.",
"secondary_dimensions": [
"d_init_02"
],
"skill_id": "visio"
},
"relationships": {
"child_skills": [],
"parent_skills": [],
"related_to": [],
"requires": [],
"skill_id": "visio",
"suppress_on_match": []
},
"skill_id": "visio",
"split_log": [],
"typed": {
"alternatives_considered": [],
"confidence": 0.98,
"name": "Visio",
"reasoning": "Visio is software you operate to create diagrams, so by the Tool vs Framework rule it is a Tool rather than something you build applications inside.",
"skill_id": "visio",
"subtype": "diagramming_tool",
"type": "Tool"
},
"warnings": []
},
"source_tag": "llm",
"was_in_llm_skills": true
},
{
"aliases_in_db": [],
"canonical": null,
"dimensions": [],
"input_skill": "analysis",
"matched_via": null,
"new_alias_persisted": false,
"new_alias_text": null,
"new_skill_meta": null,
"source_tag": "llm",
"was_in_llm_skills": true
},
{
"aliases_in_db": [],
"canonical": null,
"dimensions": [],
"input_skill": "communication",
"matched_via": null,
"new_alias_persisted": false,
"new_alias_text": null,
"new_skill_meta": null,
"source_tag": "llm",
"was_in_llm_skills": true
},
{
"aliases_in_db": [],
"canonical": null,
"dimensions": [],
"input_skill": "data",
"matched_via": null,
"new_alias_persisted": false,
"new_alias_text": null,
"new_skill_meta": null,
"source_tag": "llm",
"was_in_llm_skills": true
},
{
"aliases_in_db": [],
"canonical": null,
"dimensions": [],
"input_skill": "databases",
"matched_via": null,
"new_alias_persisted": false,
"new_alias_text": null,
"new_skill_meta": null,
"source_tag": "llm",
"was_in_llm_skills": true
},
{
"aliases_in_db": [],
"canonical": null,
"dimensions": [],
"input_skill": "development",
"matched_via": null,
"new_alias_persisted": false,
"new_alias_text": null,
"new_skill_meta": null,
"source_tag": "llm",
"was_in_llm_skills": true
},
{
"aliases_in_db": [],
"canonical": null,
"dimensions": [],
"input_skill": "domains",
"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": "management",
"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": "stakeholder",
"matched_via": null,
"new_alias_persisted": false,
"new_alias_text": null,
"new_skill_meta": null,
"source_tag": "llm",
"was_in_llm_skills": true
},
{
"aliases_in_db": [],
"canonical": null,
"dimensions": [],
"input_skill": "stakeholders",
"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",
"Familiarity",
"Knowledge",
"QA",
"SDLC",
"SaaS",
"Testing",
"UAT",
"Understanding",
"Visio"
]
}
API 3 — final-role-output
{
"chosen_role": {
"display_name": "Business Analyst",
"id": null,
"rationale": "The dominant evidence is requirements and analysis work (BRDs, FRDs, UAT, QA, SDLC, stakeholders), which aligns much more cleanly with a Business Analyst than the DB engineering candidates.",
"role_archetype": "Requirements-focused analyst bridging business and technical teams to document, analyze, and translate business needs into functional specifications. Typically works across stakeholders, QA/UAT, and documentation-heavy workflows.",
"slug": "business-analyst",
"source": "llm"
},
"final_input_skills": [
{
"skill": "Tableau",
"tag": "in_db"
},
{
"skill": "Argo Workflows",
"tag": "in_db"
},
{
"skill": "Power BI",
"tag": "in_db"
},
{
"skill": "APIs",
"tag": "new"
},
{
"skill": "Acceptance",
"tag": "new"
},
{
"skill": "BI",
"tag": "new"
},
{
"skill": "BRDs",
"tag": "new"
},
{
"skill": "CBAP",
"tag": "new"
},
{
"skill": "CCBA",
"tag": "new"
},
{
"skill": "Excel",
"tag": "new"
},
{
"skill": "FRDs",
"tag": "new"
},
{
"skill": "Familiarity",
"tag": "new"
},
{
"skill": "Knowledge",
"tag": "new"
},
{
"skill": "QA",
"tag": "new"
},
{
"skill": "SDLC",
"tag": "new"
},
{
"skill": "SaaS",
"tag": "new"
},
{
"skill": "Testing",
"tag": "new"
},
{
"skill": "UAT",
"tag": "new"
},
{
"skill": "Understanding",
"tag": "new"
},
{
"skill": "Visio",
"tag": "new"
},
{
"skill": "analysis",
"tag": "new"
},
{
"skill": "communication",
"tag": "new"
},
{
"skill": "data",
"tag": "new"
},
{
"skill": "databases",
"tag": "new"
},
{
"skill": "development",
"tag": "new"
},
{
"skill": "domains",
"tag": "new"
},
{
"skill": "fintech",
"tag": "new"
},
{
"skill": "healthcare",
"tag": "new"
},
{
"skill": "insights",
"tag": "new"
},
{
"skill": "management",
"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": "stakeholder",
"tag": "new"
},
{
"skill": "stakeholders",
"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, documenting, and integrating application programming interfaces across systems. This fits APIs because the skill centers on how software exposes and consumes structured endpoints and contracts.",
"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 Requirements Acceptance",
"id": null,
"rationale": "Confirming that delivered work satisfies business needs, stakeholder expectations, and formal sign-off criteria. This is the best fit when Acceptance refers to approving a solution from a business analysis perspective rather than technical testing.",
"slug": "d_init_01",
"source": "llm"
},
"dimension_id": null,
"input_skill": "Acceptance",
"llm_role": null,
"matched_chosen_role": false,
"role_dimension_saved": false,
"roles_from_db": [],
"skill_dimension_saved": false,
"skill_id": null,
"skill_tag": "new",
"skipped_reason": "skill_not_in_db_v3_proposed"
},
{
"chosen_role_id": null,
"dimension": {
"difficulty_hint": null,
"display_name": "Business Intelligence Reporting",
"id": null,
"rationale": "Covers the creation and consumption of business-facing reports, dashboards, and KPI views used to monitor performance and support decisions. BI belongs here because, in a Business Analyst context, it typically refers to turning data into actionable reporting and analysis for 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 writing and maintaining business requirements documents that define the problem, scope, stakeholders, assumptions, and acceptance criteria for a solution. BRDs belong here because they are the canonical artifact used by business analysts to translate business needs into implementable requirements.",
"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 and credentialing for business analysts. CBAP belongs here because it is a business analysis certification focused on requirements, stakeholder needs, and solution evaluation rather than a specific tool or platform.",
"slug": "d_init_01",
"source": "llm"
},
"dimension_id": null,
"input_skill": "CBAP",
"llm_role": null,
"matched_chosen_role": false,
"role_dimension_saved": false,
"roles_from_db": [],
"skill_dimension_saved": false,
"skill_id": null,
"skill_tag": "new",
"skipped_reason": "skill_not_in_db_v3_proposed"
},
{
"chosen_role_id": null,
"dimension": {
"difficulty_hint": null,
"display_name": "Business Analysis Certification",
"id": null,
"rationale": "Professional certification knowledge for business analysts, including requirements elicitation, stakeholder analysis, solution assessment, and business process modeling. CCBA belongs here because it is a recognized business analysis credential rather than a tool or technical implementation skill.",
"slug": "d_init_01",
"source": "llm"
},
"dimension_id": null,
"input_skill": "CCBA",
"llm_role": null,
"matched_chosen_role": false,
"role_dimension_saved": false,
"roles_from_db": [],
"skill_dimension_saved": false,
"skill_id": null,
"skill_tag": "new",
"skipped_reason": "skill_not_in_db_v3_proposed"
},
{
"chosen_role_id": null,
"dimension": {
"difficulty_hint": null,
"display_name": "Spreadsheet Analysis and Modeling",
"id": null,
"rationale": "Using spreadsheets to organize, analyze, and summarize business data for reporting and decision support. Excel belongs here because it is the primary tool for formulas, pivot-based analysis, charts, 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 requirements documents that define what a product or process must do. FRDs belong here because they capture business needs, scope, rules, and acceptance expectations in a formal requirements artifact.",
"slug": "d_init_01",
"source": "llm"
},
"dimension_id": null,
"input_skill": "FRDs",
"llm_role": null,
"matched_chosen_role": false,
"role_dimension_saved": false,
"roles_from_db": [],
"skill_dimension_saved": false,
"skill_id": null,
"skill_tag": "new",
"skipped_reason": "skill_not_in_db_v3_proposed"
},
{
"chosen_role_id": null,
"dimension": {
"difficulty_hint": null,
"display_name": "Domain Familiarity",
"id": null,
"rationale": "General working familiarity with a business or technical domain, enough to understand terminology, workflows, and stakeholder needs. This fits the target skill because it signals breadth of exposure rather than deep implementation expertise.",
"slug": "d_init_01",
"source": "llm"
},
"dimension_id": null,
"input_skill": "Familiarity",
"llm_role": null,
"matched_chosen_role": false,
"role_dimension_saved": false,
"roles_from_db": [],
"skill_dimension_saved": false,
"skill_id": null,
"skill_tag": "new",
"skipped_reason": "skill_not_in_db_v3_proposed"
},
{
"chosen_role_id": null,
"dimension": {
"difficulty_hint": null,
"display_name": "Domain Knowledge and Business Context",
"id": null,
"rationale": "Knowledge of the business domain, processes, terminology, and operating context used to interpret requirements and make sound decisions. For a Business Analyst, this is the core subject-matter understanding behind analysis, stakeholder communication, and solution framing.",
"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": "Quality Assurance Testing",
"id": null,
"rationale": "Validating that a product, feature, or process meets requirements through structured testing and defect checking. QA belongs here when it refers to general assurance work rather than a specific automation or platform discipline.",
"slug": "d_init_01",
"source": "llm"
},
"dimension_id": null,
"input_skill": "QA",
"llm_role": null,
"matched_chosen_role": false,
"role_dimension_saved": false,
"roles_from_db": [],
"skill_dimension_saved": false,
"skill_id": null,
"skill_tag": "new",
"skipped_reason": "skill_not_in_db_v3_proposed"
},
{
"chosen_role_id": null,
"dimension": {
"difficulty_hint": null,
"display_name": "Software Delivery Lifecycle",
"id": null,
"rationale": "Covers the end-to-end process used to plan, build, test, release, and maintain software changes. SDLC belongs here because it refers to the overall lifecycle and governance of delivery work rather than a single technical practice.",
"slug": "d_init_01",
"source": "llm"
},
"dimension_id": null,
"input_skill": "SDLC",
"llm_role": null,
"matched_chosen_role": false,
"role_dimension_saved": false,
"roles_from_db": [],
"skill_dimension_saved": false,
"skill_id": null,
"skill_tag": "new",
"skipped_reason": "skill_not_in_db_v3_proposed"
},
{
"chosen_role_id": null,
"dimension": {
"difficulty_hint": null,
"display_name": "SaaS Product Delivery",
"id": null,
"rationale": "Covers software delivered as a hosted subscription service, including multi-tenant product packaging, release cadence, and customer-facing service operations. SaaS belongs here because it describes the delivery model and operating context for the product rather than a specific technical component.",
"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": "Software Subscription Business Models",
"id": null,
"rationale": "Covers the commercial and operational model of selling software as a recurring subscription service. This fits SaaS when the skill is used in business analysis, pricing, packaging, and customer lifecycle discussions.",
"slug": "d_init_02",
"source": "llm"
},
"dimension_id": null,
"input_skill": "SaaS",
"llm_role": null,
"matched_chosen_role": false,
"role_dimension_saved": false,
"roles_from_db": [],
"skill_dimension_saved": false,
"skill_id": null,
"skill_tag": "new",
"skipped_reason": "skill_not_in_db_v3_proposed"
},
{
"chosen_role_id": null,
"dimension": {
"difficulty_hint": null,
"display_name": "User Acceptance Testing",
"id": null,
"rationale": "Validating that a delivered feature meets business requirements and is ready for user sign-off. UAT belongs here because it is the business-facing execution of acceptance scenarios before release.",
"slug": "d_init_01",
"source": "llm"
},
"dimension_id": null,
"input_skill": "UAT",
"llm_role": null,
"matched_chosen_role": false,
"role_dimension_saved": false,
"roles_from_db": [],
"skill_dimension_saved": false,
"skill_id": null,
"skill_tag": "new",
"skipped_reason": "skill_not_in_db_v3_proposed"
},
{
"chosen_role_id": null,
"dimension": {
"difficulty_hint": null,
"display_name": "Requirements and Domain Understanding",
"id": null,
"rationale": "Interpreting business needs, user goals, and process context well enough to translate them into clear requirements and analysis artifacts. This fits the target skill because business analysts are often evaluated on how well they understand the problem space before proposing solutions.",
"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, swimlanes, org charts, and system diagrams for analysis and documentation.",
"slug": "d_init_01",
"source": "llm"
},
"dimension_id": null,
"input_skill": "Visio",
"llm_role": null,
"matched_chosen_role": false,
"role_dimension_saved": false,
"roles_from_db": [],
"skill_dimension_saved": false,
"skill_id": null,
"skill_tag": "new",
"skipped_reason": "skill_not_in_db_v3_proposed"
},
{
"chosen_role_id": null,
"dimension": {
"difficulty_hint": null,
"display_name": "Business Analysis Documentation",
"id": null,
"rationale": "Documenting business requirements, current-state and future-state processes, and stakeholder-facing artifacts. Visio fits when used by a Business Analyst to capture process flows and support requirements communication.",
"slug": "d_init_02",
"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": 21
},
"planner_output": null,
"run_id": "1e48c84e-e05d-4e98-a8e1-12b83451729c"
}
LLM Calls
Every model call made for this run, in pipeline order. Click a card to see the model's response.
Loading…