Pipeline run
200ba776-f813-4560-a97e-2e1cdf5da0ce
Client output enrichment
v2 Skill cluster · Nature of work · AI index · Tech stack maturity · Evidence · KRA descriptionNature of work
—
Tech stack maturity
Mainstream Modern
AI index (0 = no AI use, 5 = totally AI-dependent · v2.1)
0.00 / 5
· Title match
· Has AI skill
· AI skill (primary)
· AI skill (secondary)
· On AI team
· Builds AI products
vocab breakdown (legacy)
Assistants (×1):
—
Frameworks (×2):
—
Models / concepts (×3):
—
Evidence — skills matched in JD (0)
Skill cluster (0 dimension groups, role-scoped)
Status:
completed
Created: 2026-05-08T07:30:00.454418Z
Updated: 2026-05-08T07:31:53.430319Z
API 3 duration: 875 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
Most evidence points to business analysis and requirements work, with BI/reporting as supporting signals rather than a pure data or MLOps role.
0
New skills
0
Skill↔dim saved
0
Role↔dim saved
14
Skipped
Job description
Business Analyst Job Description Job Title: Business Analyst Experience: 2–5 Years Location: Remote / Hybrid / On-site About the Role We are looking for a Business Analyst to bridge the gap between business needs and technical solutions. The ideal candidate will work closely with stakeholders, product teams, and developers to gather requirements, analyze business processes, and support successful project delivery. Key Responsibilities Gather, analyze, and document business requirements from stakeholders Translate business needs into functional specifications and user stories Work with cross-functional teams including developers, QA, and product managers Conduct requirement workshops, stakeholder meetings, and process analysis Create BRDs, FRDs, workflows, process diagrams, and reports Analyze data to identify trends, opportunities, and business insights Support UAT (User Acceptance Testing) and validate delivered solutions Monitor project progress and help manage risks and dependencies Improve existing business processes and recommend optimization strategies Ensure solutions align with business goals and operational needs Required Skills Strong understanding of business analysis methodologies Experience with requirement gathering and documentation Knowledge of Agile/Scrum methodologies Excellent communication and stakeholder management skills Strong analytical and problem-solving abilities Experience with tools like JIRA, Confluence, Excel, Visio, or Power BI Ability to create reports, dashboards, and process flows Understanding of SDLC and software development processes Preferred Qualifications Bachelor’s degree in Business, Computer Science, IT, or related field Experience working with technical and non-technical teams Familiarity with SQL, data analysis, or reporting tools is a plus Certification such as CBAP, CCBA, or Agile certification is preferred Nice to Have Experience in fintech, healthcare, e-commerce, or SaaS domains Exposure to BI tools like Tableau or Power BI Basic understanding of APIs and databases Benefits Competitive salary Flexible work environment Health insurance Learning and development opportunities Career growth and mentorship Paid leaves and company benefits
history_view bundle (older API). Showing raw API payloads below.
All API 3 persistence rows
Same grid as the skill-extractor “Persistence items” table: one row per (skill × dimension) work item.
| Skill | Tag | Dimension | Skill↔dim | Role↔dim | Outcome | Notes |
|---|---|---|---|---|---|---|
| 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 |
Application Programming Interfaces
d_init_01
|
— | — | — | skill_not_in_db_v3_proposed |
| BI | new |
Business Intelligence
d_init_01
|
— | — | — | skill_not_in_db_v3_proposed |
| CBAP | new |
Business Analysis Certification
d_init_01
|
— | — | — | skill_not_in_db_v3_proposed |
| CCBA | new |
Business Analysis Certification
d_init_01
|
— | — | — | skill_not_in_db_v3_proposed |
| Excel | new |
Spreadsheet Analysis and Modeling
d_init_01
|
— | — | — | skill_not_in_db_v3_proposed |
| FRDs | new |
Functional Requirements Documentation
d_init_01
|
— | — | — | skill_not_in_db_v3_proposed |
| Familiarity | new |
Domain and Process 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 |
| SDLC | new |
Software Development Lifecycle
d_init_01
|
— | — | — | skill_not_in_db_v3_proposed |
| SaaS | new |
Software as a Service
d_init_01
|
— | — | — | skill_not_in_db_v3_proposed |
| Visio | new |
Process and Workflow Diagramming
d_init_01
|
— | — | — | skill_not_in_db_v3_proposed |
Library artifacts (this run)
| Kind | Detail | DB id |
|---|---|---|
| canonical_skill_proposed | APIs | type=Protocol subtype=application_programming_interfaces nature=PROTOCOL lifespan=EVERGREEN | |
| canonical_skill_proposed | Acceptance | type=Concept subtype=acceptance_concept nature=CONCEPT lifespan=EVERGREEN | |
| canonical_skill_proposed | BI | type=Domain subtype=business_intelligence nature=CONCEPT lifespan=EVERGREEN | |
| canonical_skill_proposed | CBAP | type=Certification subtype=business_analysis_professional_certification nature=CREDENTIAL lifespan=EVERGREEN | |
| canonical_skill_proposed | CCBA | type=Certification subtype=business_analysis_certification nature=CREDENTIAL lifespan=EVERGREEN | |
| canonical_skill_proposed | Excel | type=Tool subtype=spreadsheet_software nature=TOOL lifespan=EVERGREEN | |
| canonical_skill_proposed | FRDs | type=Concept subtype=functional_requirements_document nature=CONCEPT lifespan=EVERGREEN | |
| canonical_skill_proposed | Familiarity | type=Concept subtype=familiarity nature=CONCEPT lifespan=EVERGREEN | |
| canonical_skill_proposed | Knowledge | type=Concept subtype=general_knowledge nature=CONCEPT lifespan=EVERGREEN | |
| canonical_skill_proposed | QA | type=SoftSkill subtype=quality_assurance nature=PRACTICE lifespan=EVERGREEN | |
| canonical_skill_proposed | SDLC | type=Methodology subtype=software_development_lifecycle nature=METHODOLOGY lifespan=EVERGREEN | |
| canonical_skill_proposed | SaaS | type=Platform subtype=software_as_a_service_platform nature=PLATFORM lifespan=EVERGREEN | |
| canonical_skill_proposed | Testing | type=Methodology subtype=software_testing_methodology nature=METHODOLOGY lifespan=EVERGREEN | |
| canonical_skill_proposed | UAT | type=Methodology subtype=user_acceptance_testing nature=METHODOLOGY lifespan=EVERGREEN | |
| canonical_skill_proposed | Visio | type=Tool subtype=diagramming_tool nature=TOOL lifespan=EVERGREEN | |
| dimension_proposed | Application Programming Interfaces | |
| dimension_skill_link_proposed | APIs ↔ Application Programming Interfaces | |
| dimension_proposed | Business Intelligence | |
| dimension_skill_link_proposed | BI ↔ Business Intelligence | |
| dimension_proposed | Business Analysis Certification | |
| dimension_skill_link_proposed | CBAP ↔ Business Analysis Certification | |
| dimension_proposed | Business Analysis Certification | |
| dimension_skill_link_proposed | CCBA ↔ Business Analysis Certification | |
| dimension_proposed | Spreadsheet Analysis and Modeling | |
| dimension_skill_link_proposed | Excel ↔ Spreadsheet Analysis and Modeling | |
| dimension_proposed | Functional Requirements Documentation | |
| dimension_skill_link_proposed | FRDs ↔ Functional Requirements Documentation | |
| dimension_proposed | Domain and Process Familiarity | |
| dimension_skill_link_proposed | Familiarity ↔ Domain and Process Familiarity | |
| dimension_proposed | Domain Knowledge and Business Context | |
| dimension_skill_link_proposed | Knowledge ↔ Domain Knowledge and Business Context | |
| dimension_proposed | Software Development Lifecycle | |
| dimension_skill_link_proposed | SDLC ↔ Software Development Lifecycle | |
| dimension_proposed | Software as a Service | |
| dimension_skill_link_proposed | SaaS ↔ Software as a Service | |
| dimension_proposed | Process and Workflow Diagramming | |
| dimension_skill_link_proposed | Visio ↔ Process and Workflow Diagramming |
API 1 — extract-from-jd click to toggle
{
"filtered_unknown_words": [
"2\u20135",
"APIs",
"Ability",
"Acceptance",
"Analyst",
"BI",
"BRDs",
"Bachelor",
"Benefits",
"Business",
"CBAP",
"CCBA",
"Career",
"Certification",
"Computer",
"Conduct",
"Description",
"Ensure",
"Excel",
"Experience",
"Exposure",
"FRDs",
"Familiarity",
"Gather",
"Health",
"Hybrid",
"Job",
"Key",
"Knowledge",
"Learning",
"Location",
"Monitor",
"Power",
"Preferred",
"QA",
"Qualifications",
"Remote",
"Required",
"Responsibilities",
"Role",
"SDLC",
"SaaS",
"Science",
"Skills",
"Support",
"Testing",
"Title",
"UAT",
"Understanding",
"User",
"Visio",
"Years",
"abilities",
"analysis",
"benefits",
"business",
"candidate",
"certification",
"commerce",
"communication",
"company",
"data",
"databases",
"degree",
"delivery",
"dependencies",
"developers",
"development",
"diagrams",
"document",
"documentation",
"domains",
"environment",
"field",
"fintech",
"gap",
"gathering",
"goals",
"growth",
"healthcare",
"insights",
"insurance",
"leaves",
"management",
"managers",
"meetings",
"methodologies",
"needs",
"opportunities",
"optimization",
"problem",
"process",
"processes",
"product",
"progress",
"project",
"reporting",
"requirement",
"requirements",
"risks",
"salary",
"site",
"skills",
"software",
"solutions",
"specifications",
"stakeholder",
"stakeholders",
"stories",
"strategies",
"teams",
"tools",
"trends",
"understanding",
"user",
"work",
"workshops"
],
"final_non_skills": [
"2\u20135",
"Ability",
"Analyst",
"BRDs",
"Bachelor",
"Benefits",
"Business",
"Certification",
"Computer",
"Conduct",
"Description",
"Ensure",
"Experience",
"Exposure",
"Gather",
"Health",
"Hybrid",
"Job",
"Key",
"Learning",
"Location",
"Monitor",
"Power",
"Preferred",
"Qualifications",
"Remote",
"Required",
"Responsibilities",
"Role",
"Science",
"Skills",
"Support",
"Title",
"Understanding",
"User",
"Years",
"abilities",
"candidate",
"commerce",
"company",
"degree",
"delivery",
"dependencies",
"developers",
"development",
"diagrams",
"document",
"domains",
"environment",
"field",
"gap",
"gathering",
"goals",
"growth",
"insurance",
"leaves",
"management",
"managers",
"meetings",
"needs",
"opportunities",
"problem",
"process",
"processes",
"product",
"progress",
"project",
"requirement",
"risks",
"salary",
"site",
"solutions",
"stakeholder",
"stakeholders",
"strategies",
"teams",
"tools",
"work"
],
"final_skills": [
"Tableau",
"Argo Workflows",
"Power BI",
"APIs",
"Acceptance",
"BI",
"CBAP",
"CCBA",
"Excel",
"FRDs",
"Familiarity",
"Knowledge",
"QA",
"SDLC",
"SaaS",
"Testing",
"UAT",
"Visio",
"analysis",
"communication",
"data",
"databases",
"documentation",
"fintech",
"healthcare",
"insights",
"methodologies",
"optimization",
"reporting",
"requirements",
"software",
"specifications",
"stories",
"trends",
"workshops"
],
"initial_skills": [
"Tableau",
"Argo Workflows",
"Power BI"
],
"jd_role_hint": {
"display_name": "Business Analyst",
"rationale": "The excerpt explicitly describes a Business Analyst role centered on requirements, workflows, stakeholders, and delivery support.",
"role_archetype": "Business analysis professional focused on requirements gathering, process analysis, stakeholder communication, and translating business needs into functional specifications.",
"slug": "business-analyst"
},
"llm_non_skills": [
"2\u20135",
"Ability",
"Analyst",
"BRDs",
"Bachelor",
"Benefits",
"Business",
"Certification",
"Computer",
"Conduct",
"Description",
"Ensure",
"Experience",
"Exposure",
"Gather",
"Health",
"Hybrid",
"Job",
"Key",
"Learning",
"Location",
"Monitor",
"Power",
"Preferred",
"Qualifications",
"Remote",
"Required",
"Responsibilities",
"Role",
"Science",
"Skills",
"Support",
"Title",
"Understanding",
"User",
"Years",
"abilities",
"candidate",
"commerce",
"company",
"degree",
"delivery",
"dependencies",
"developers",
"development",
"diagrams",
"document",
"domains",
"environment",
"field",
"gap",
"gathering",
"goals",
"growth",
"insurance",
"leaves",
"management",
"managers",
"meetings",
"needs",
"opportunities",
"problem",
"process",
"processes",
"product",
"progress",
"project",
"requirement",
"risks",
"salary",
"site",
"solutions",
"stakeholder",
"stakeholders",
"strategies",
"teams",
"tools",
"work"
],
"llm_skills": [
"APIs",
"Acceptance",
"BI",
"CBAP",
"CCBA",
"Excel",
"FRDs",
"Familiarity",
"Knowledge",
"QA",
"SDLC",
"SaaS",
"Testing",
"UAT",
"Visio",
"analysis",
"communication",
"data",
"databases",
"documentation",
"fintech",
"healthcare",
"insights",
"methodologies",
"optimization",
"reporting",
"requirements",
"software",
"specifications",
"stories",
"trends",
"workshops"
],
"run_id": null,
"unknown_words": [
"2\u20135",
"APIs",
"Ability",
"Acceptance",
"Analyst",
"BI",
"BRDs",
"Bachelor",
"Benefits",
"Business",
"CBAP",
"CCBA",
"Career",
"Certification",
"Computer",
"Conduct",
"Description",
"Ensure",
"Excel",
"Experience",
"Exposure",
"FRDs",
"Familiarity",
"Gather",
"Health",
"Hybrid",
"Job",
"Key",
"Knowledge",
"Learning",
"Location",
"Monitor",
"Power",
"Preferred",
"QA",
"Qualifications",
"Remote",
"Required",
"Responsibilities",
"Role",
"SDLC",
"SaaS",
"Science",
"Skills",
"Support",
"Testing",
"Title",
"UAT",
"Understanding",
"User",
"Visio",
"Years",
"abilities",
"analysis",
"benefits",
"business",
"candidate",
"certification",
"commerce",
"communication",
"company",
"data",
"databases",
"degree",
"delivery",
"dependencies",
"developers",
"development",
"diagrams",
"document",
"documentation",
"domains",
"environment",
"field",
"fintech",
"gap",
"gathering",
"goals",
"growth",
"healthcare",
"insights",
"insurance",
"leaves",
"management",
"managers",
"meetings",
"methodologies",
"needs",
"opportunities",
"optimization",
"problem",
"process",
"processes",
"product",
"progress",
"project",
"reporting",
"requirement",
"requirements",
"risks",
"salary",
"site",
"skills",
"software",
"solutions",
"specifications",
"stakeholder",
"stakeholders",
"stories",
"strategies",
"teams",
"tools",
"trends",
"understanding",
"user",
"work",
"workshops"
]
}
API 2 — extract-details
{
"alias_matches": [],
"candidate_roles": [
{
"display_name": "Data Analyst",
"id": 20,
"rationale": null,
"role_archetype": null,
"slug": "data-analyst",
"source": "db"
},
{
"display_name": "Data Engineer",
"id": 6,
"rationale": null,
"role_archetype": null,
"slug": "data-engineer",
"source": "db"
},
{
"display_name": "MLOps Engineer",
"id": 5,
"rationale": null,
"role_archetype": null,
"slug": "mlops-engineer",
"source": "db"
}
],
"chosen_role": {
"display_name": "Business Analyst",
"id": null,
"rationale": "Most evidence points to business analysis and requirements work, with BI/reporting as supporting signals rather than a pure data or MLOps role.",
"role_archetype": "Business analysis professional focused on requirements gathering, process analysis, stakeholder communication, and translating business needs into functional specifications.",
"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": "Application Programming Interfaces",
"id": null,
"rationale": "Designing, consuming, and documenting software interfaces that let systems exchange data and actions. APIs belong here because they define the contract used by applications, services, and external platforms.",
"slug": "d_init_01",
"source": "llm"
},
"input_skill": "APIs",
"llm_role": null,
"roles_from_db": []
},
{
"dimension": {
"difficulty_hint": null,
"display_name": "Business Intelligence",
"id": null,
"rationale": "Covers the use of data to create reports, dashboards, and decision-support views for business stakeholders. BI fits here because it commonly refers to the discipline of turning operational data into accessible analysis and performance monitoring.",
"slug": "d_init_01",
"source": "llm"
},
"input_skill": "BI",
"llm_role": null,
"roles_from_db": []
},
{
"dimension": {
"difficulty_hint": null,
"display_name": "Business Analysis Certification",
"id": null,
"rationale": "Professional certification knowledge for business analysts, including the CBAP credential and the BABOK-based practices it represents. This belongs here because CBAP is a certification focused on business analysis competencies, techniques, and professional standards rather than a software tool or technical method.",
"slug": "d_init_01",
"source": "llm"
},
"input_skill": "CBAP",
"llm_role": null,
"roles_from_db": []
},
{
"dimension": {
"difficulty_hint": null,
"display_name": "Business Analysis Certification",
"id": null,
"rationale": "Formal business analysis credentialing and exam-based competency in requirements, stakeholder analysis, and solution evaluation. CCBA belongs here because it is a recognized business analysis certification rather than a technical skill or tool.",
"slug": "d_init_01",
"source": "llm"
},
"input_skill": "CCBA",
"llm_role": null,
"roles_from_db": []
},
{
"dimension": {
"difficulty_hint": null,
"display_name": "Spreadsheet Analysis and Modeling",
"id": null,
"rationale": "Using spreadsheets to organize, analyze, and present data for business decisions. Excel belongs here because it is the core tool for tabular analysis, formulas, pivoting, and lightweight modeling in analyst workflows.",
"slug": "d_init_01",
"source": "llm"
},
"input_skill": "Excel",
"llm_role": null,
"roles_from_db": []
},
{
"dimension": {
"difficulty_hint": null,
"display_name": "Functional Requirements Documentation",
"id": null,
"rationale": "Covers writing and maintaining functional requirement documents that define what a product or system should do. FRDs belong here because they capture business needs, scope, behaviors, and acceptance expectations in a structured requirements artifact.",
"slug": "d_init_01",
"source": "llm"
},
"input_skill": "FRDs",
"llm_role": null,
"roles_from_db": []
},
{
"dimension": {
"difficulty_hint": null,
"display_name": "Domain and Process Familiarity",
"id": null,
"rationale": "General working familiarity with a business domain, product area, or process flow. For a Business Analyst, this captures being conversant enough to understand terminology, stakeholders, and how work gets done without implying deep technical specialization.",
"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": "Understanding the subject-matter area, business processes, and terminology needed to interpret requirements and make sound analysis decisions. For a Business Analyst, knowledge is the foundation for eliciting, validating, and communicating what the business actually needs.",
"slug": "d_init_01",
"source": "llm"
},
"input_skill": "Knowledge",
"llm_role": null,
"roles_from_db": []
},
{
"dimension": {
"difficulty_hint": null,
"display_name": "Software Development Lifecycle",
"id": null,
"rationale": "Covers the end-to-end process for planning, building, testing, releasing, and maintaining software. SDLC belongs here because it refers to the overall lifecycle framework rather than a single technical implementation area.",
"slug": "d_init_01",
"source": "llm"
},
"input_skill": "SDLC",
"llm_role": null,
"roles_from_db": []
},
{
"dimension": {
"difficulty_hint": null,
"display_name": "Software as a Service",
"id": null,
"rationale": "Covers the SaaS product and delivery model: subscription-based software delivered over the internet, typically managed by a vendor and accessed through a browser or thin client. This fits the target skill because SaaS is the core business and deployment model being referenced.",
"slug": "d_init_01",
"source": "llm"
},
"input_skill": "SaaS",
"llm_role": null,
"roles_from_db": []
},
{
"dimension": {
"difficulty_hint": null,
"display_name": "Process and Workflow Diagramming",
"id": null,
"rationale": "Creating business and technical diagrams that map processes, workflows, handoffs, and system interactions. Visio belongs here because it is commonly used to document flows, swimlanes, and operational procedures for analysis and communication.",
"slug": "d_init_01",
"source": "llm"
},
"input_skill": "Visio",
"llm_role": null,
"roles_from_db": []
}
],
"input_final_skills": [
"Tableau",
"Argo Workflows",
"Power BI",
"APIs",
"Acceptance",
"BI",
"CBAP",
"CCBA",
"Excel",
"FRDs",
"Familiarity",
"Knowledge",
"QA",
"SDLC",
"SaaS",
"Testing",
"UAT",
"Visio",
"analysis",
"communication",
"data",
"databases",
"documentation",
"fintech",
"healthcare",
"insights",
"methodologies",
"optimization",
"reporting",
"requirements",
"software",
"specifications",
"stories",
"trends",
"workshops"
],
"input_llm_skills": [
"APIs",
"Acceptance",
"BI",
"CBAP",
"CCBA",
"Excel",
"FRDs",
"Familiarity",
"Knowledge",
"QA",
"SDLC",
"SaaS",
"Testing",
"UAT",
"Visio",
"analysis",
"communication",
"data",
"databases",
"documentation",
"fintech",
"healthcare",
"insights",
"methodologies",
"optimization",
"reporting",
"requirements",
"software",
"specifications",
"stories",
"trends",
"workshops"
],
"new_aliases_persisted": 0,
"run_id": "200ba776-f813-4560-a97e-2e1cdf5da0ce",
"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": "Application Programming Interfaces",
"id": null,
"rationale": "Designing, consuming, and documenting software interfaces that let systems exchange data and actions. APIs belong here because they define the contract used by applications, services, and external platforms.",
"slug": "d_init_01",
"source": "llm"
},
"input_skill": "APIs",
"llm_role": null,
"roles_from_db": []
}
],
"input_skill": "APIs",
"matched_via": null,
"new_alias_persisted": false,
"new_alias_text": null,
"new_skill_meta": {
"derived": {
"category": "Protocol",
"skill_nature": "PROTOCOL",
"sub_category": "application_programming_interfaces",
"typical_lifespan": "EVERGREEN",
"version_strategy": "NOT_APPLICABLE",
"volatility": "STABLE"
},
"enrichment": {
"ambiguity": {
"ambiguity_flag": false,
"confused_with": [],
"reasoning": "APIs is a standard, well-scoped term in JDs and usually refers to application programming interfaces; it is not typically confused with a different catalog skill."
},
"context_keywords": {
"context_keywords": [
"REST",
"GraphQL",
"OpenAPI",
"Swagger",
"JSON",
"OAuth 2.0",
"webhooks",
"endpoint",
"rate limiting",
"API gateway",
"microservices",
"SDK",
"versioning",
"HTTP",
"Postman"
]
},
"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
}
},
"locked_dimensions": [
{
"description": "Designing, consuming, and documenting software interfaces that let systems exchange data and actions. APIs belong here because they define the contract used by applications, services, and external platforms.",
"exemplar_skills": [
"APIs",
"REST APIs",
"GraphQL APIs",
"SOAP APIs",
"Webhook integration",
"API versioning"
],
"in_scope": "APIs, REST APIs, GraphQL APIs, SOAP APIs, webhook endpoints, request and response payloads, API versioning, pagination, error handling",
"name": "Application Programming Interfaces",
"out_of_scope": "Authentication flows, session handling, UI component wiring, database schema design, network routing, batch ETL pipelines, which are owned by other dimensions",
"overlap_flags": [
{
"reason": "If this catalog dimension exists elsewhere, it would cover the broader integration context around APIs and service contracts.",
"with_dim_id": "service-architecture-and-integration",
"with_dim_name": null,
"with_role": null
},
{
"reason": "Both involve external interfaces, but tool use is specific to model-driven action invocation rather than general software APIs.",
"with_dim_id": "tool-use-and-function-calling",
"with_dim_name": null,
"with_role": null
}
],
"tentative_id": "d_init_01"
}
],
"merge_log": [],
"placed": {
"name": "APIs",
"placement_confidence": 0.92,
"primary_dimension": "d_init_01",
"reasoning": "Deterministic JD placement: locked_dimensions has 1 dimension(s) from skill-driven dimension generation after reconciliation; primary_dimension is the first locked dim.",
"secondary_dimensions": [],
"skill_id": "apis"
},
"relationships": {
"child_skills": [],
"parent_skills": [],
"related_to": [
"rest-apis",
"grpc",
"http",
"json",
"oauth-2-0",
"private-endpoints",
"acls",
"scripted-rest-api",
"outbound-rest-messages",
"mock-servers"
],
"requires": [],
"skill_id": "apis",
"suppress_on_match": []
},
"skill_id": "apis",
"split_log": [],
"typed": {
"alternatives_considered": [
"Concept: ruled out \u2014 APIs are not just a knowledge unit; they define an interaction interface.",
"Standard: ruled out \u2014 while some APIs follow standards, the term itself refers to an interface/protocol, not an industry specification."
],
"confidence": 0.93,
"name": "APIs",
"reasoning": "By the Protocol rule, APIs are the communication contract between systems rather than software you run or a hosted environment.",
"skill_id": "apis",
"subtype": "application_programming_interfaces",
"type": "Protocol"
},
"warnings": []
},
"source_tag": "llm",
"was_in_llm_skills": true
},
{
"aliases_in_db": [],
"canonical": null,
"dimensions": [],
"input_skill": "Acceptance",
"matched_via": null,
"new_alias_persisted": false,
"new_alias_text": null,
"new_skill_meta": {
"derived": {
"category": "Concept",
"skill_nature": "CONCEPT",
"sub_category": "acceptance_concept",
"typical_lifespan": "EVERGREEN",
"version_strategy": "NOT_APPLICABLE",
"volatility": "STABLE"
},
"enrichment": {
"ambiguity": {
"ambiguity_flag": true,
"confused_with": [
"acceptance_testing",
"user_acceptance_testing",
"acceptance_criteria"
],
"reasoning": "\u201cAcceptance\u201d is a generic term in JDs and could refer to acceptance testing, user acceptance testing, or acceptance criteria rather than the standalone concept."
},
"context_keywords": {
"context_keywords": [
"UAT",
"user acceptance testing",
"acceptance criteria",
"acceptance test",
"sign-off",
"go-live",
"test cases",
"requirements traceability",
"definition of done",
"validation",
"verification",
"stakeholder approval",
"release readiness",
"quality assurance"
]
},
"maturity": {
"confidence": 0.86,
"maturity": "niche",
"reasoning": "Job postings rarely list \"Acceptance\" as a standalone skill; it appears mainly in QA/UAT or Agile contexts rather than as a hiring-pipeline staple."
},
"skill_id": "acceptance",
"vendor_license": {
"confidence": 0.99,
"license": null,
"vendor": null,
"year_introduced": null
},
"versioning": {
"current_version": null,
"version_aliases": {},
"versioned": false
}
},
"locked_dimensions": [],
"merge_log": [
{
"into": "d_merge_01",
"into_name": "Requirements and Acceptance Validation",
"merged_from": [
"d_init_01",
"requirements-and-acceptance-validation"
],
"reasoning": "Both dims describe the same skill: validating delivered behavior against requirements, user stories, and acceptance criteria. Dim A adds BA-oriented framing (requirements traceability, UAT support, sign-off readiness) and exemplars like \"Acceptance\" and \"user story acceptance.\" Dim B says the same thing in testing-oriented language and even notes manual testing starts from understanding intended behavior. The overlap is substantive, not just lexical, so this is one cluster across roles."
}
],
"placed": {
"name": "Acceptance",
"placement_confidence": 0.0,
"primary_dimension": "d_init_00",
"reasoning": "Stub placement: no locked_dimensions after Stage 2/3; downstream containment and enrichment use placeholders only.",
"secondary_dimensions": [],
"skill_id": "acceptance"
},
"relationships": {
"child_skills": [],
"parent_skills": [],
"related_to": [
"acceptance-criteria-validation",
"acceptance-criteria-checks",
"change-requests",
"contract-tests",
"defect-retest"
],
"requires": [],
"skill_id": "acceptance",
"suppress_on_match": []
},
"skill_id": "acceptance",
"split_log": [],
"typed": {
"alternatives_considered": [
"Methodology: ruled out \u2014 acceptance is not a process or workflow like Agile or TDD.",
"SoftSkill: ruled out \u2014 this is not an interpersonal capability."
],
"confidence": 0.78,
"name": "Acceptance",
"reasoning": "By the Concept vs Methodology rule, Acceptance is best treated as a named knowledge unit about agreeing that criteria or requirements are met, rather than a way of working.",
"skill_id": "acceptance",
"subtype": "acceptance_concept",
"type": "Concept"
},
"warnings": [
"placement_stub_no_locked_dimensions"
]
},
"source_tag": "llm",
"was_in_llm_skills": true
},
{
"aliases_in_db": [],
"canonical": null,
"dimensions": [
{
"dimension": {
"difficulty_hint": null,
"display_name": "Business Intelligence",
"id": null,
"rationale": "Covers the use of data to create reports, dashboards, and decision-support views for business stakeholders. BI fits here because it commonly refers to the discipline of turning operational data into accessible analysis and performance monitoring.",
"slug": "d_init_01",
"source": "llm"
},
"input_skill": "BI",
"llm_role": null,
"roles_from_db": []
}
],
"input_skill": "BI",
"matched_via": null,
"new_alias_persisted": false,
"new_alias_text": null,
"new_skill_meta": {
"derived": {
"category": "Domain",
"skill_nature": "CONCEPT",
"sub_category": "business_intelligence",
"typical_lifespan": "EVERGREEN",
"version_strategy": "NOT_APPLICABLE",
"volatility": "STABLE"
},
"enrichment": {
"ambiguity": {
"ambiguity_flag": true,
"confused_with": [
"business_intelligence"
],
"reasoning": "\"BI\" is a common abbreviation for Business Intelligence, but in JDs it can also be used generically for business/BI tooling or reporting contexts, making it easy to conflate with the full business_intelligence skill."
},
"context_keywords": {
"context_keywords": [
"dashboard",
"KPI",
"data warehouse",
"ETL",
"OLAP",
"reporting",
"Tableau",
"Power BI",
"Looker",
"SQL",
"semantic layer",
"ad hoc analysis",
"data modeling",
"star schema",
"drill-down"
]
},
"maturity": {
"confidence": 0.88,
"maturity": "well_known",
"reasoning": "BI is a common hiring keyword across analytics and data roles; job boards regularly list Tableau/Power BI/Looker BI experience, showing broad market demand rather than niche use."
},
"skill_id": "bi",
"vendor_license": {
"confidence": 0.99,
"license": null,
"vendor": null,
"year_introduced": null
},
"versioning": {
"current_version": null,
"version_aliases": {},
"versioned": false
}
},
"locked_dimensions": [
{
"description": "Covers the use of data to create reports, dashboards, and decision-support views for business stakeholders. BI fits here because it commonly refers to the discipline of turning operational data into accessible analysis and performance monitoring.",
"exemplar_skills": [
"BI",
"business intelligence",
"dashboard design",
"reporting",
"KPI analysis",
"self-service analytics",
"OLAP"
],
"in_scope": "BI, business intelligence, reporting, dashboards, KPI tracking, ad hoc analysis, OLAP, semantic layers, self-service analytics",
"name": "Business Intelligence",
"out_of_scope": "data engineering pipelines, machine learning model development, statistical hypothesis testing, data quality auditing, which belong to other dimensions",
"overlap_flags": [
{
"reason": "BI often includes dashboard/report creation, but this catalog dimension is narrower and platform-oriented.",
"with_dim_id": "reporting-and-dashboard-configuration",
"with_dim_name": null,
"with_role": null
},
{
"reason": "BI work may use basic statistics, but the core skill is business-facing reporting and insight delivery.",
"with_dim_id": "statistical-reasoning-for-analysis",
"with_dim_name": null,
"with_role": null
}
],
"tentative_id": "d_init_01"
}
],
"merge_log": [],
"placed": {
"name": "BI",
"placement_confidence": 0.92,
"primary_dimension": "d_init_01",
"reasoning": "Deterministic JD placement: locked_dimensions has 1 dimension(s) from skill-driven dimension generation after reconciliation; primary_dimension is the first locked dim.",
"secondary_dimensions": [],
"skill_id": "bi"
},
"relationships": {
"child_skills": [],
"parent_skills": [],
"related_to": [
"dashboards"
],
"requires": [],
"skill_id": "bi",
"suppress_on_match": []
},
"skill_id": "bi",
"split_log": [],
"typed": {
"alternatives_considered": [],
"confidence": 0.93,
"name": "BI",
"reasoning": "BI is fundamentally a business intelligence problem-space, so by the Domain rule it is a vertical/body of knowledge rather than a tool, platform, or methodology.",
"skill_id": "bi",
"subtype": "business_intelligence",
"type": "Domain"
},
"warnings": []
},
"source_tag": "llm",
"was_in_llm_skills": true
},
{
"aliases_in_db": [],
"canonical": null,
"dimensions": [
{
"dimension": {
"difficulty_hint": null,
"display_name": "Business Analysis Certification",
"id": null,
"rationale": "Professional certification knowledge for business analysts, including the CBAP credential and the BABOK-based practices it represents. This belongs here because CBAP is a certification focused on business analysis competencies, techniques, and professional standards rather than a software tool or technical method.",
"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",
"traceability matrix",
"business process improvement",
"solution assessment",
"SWOT analysis",
"MoSCoW",
"UML",
"workshops"
]
},
"maturity": {
"confidence": 0.84,
"maturity": "well_known",
"reasoning": "CBAP is a widely recognized business analysis certification and appears regularly in job descriptions for senior BA roles; IIBA continues to maintain and promote it as a standard credential."
},
"skill_id": "cbap",
"vendor_license": {
"confidence": 0.95,
"license": null,
"vendor": "International Institute of Business Analysis",
"year_introduced": 2006
},
"versioning": {
"current_version": null,
"version_aliases": {},
"versioned": false
}
},
"locked_dimensions": [
{
"description": "Professional certification knowledge for business analysts, including the CBAP credential and the BABOK-based practices it represents. This belongs here because CBAP is a certification focused on business analysis competencies, techniques, and professional standards rather than a software tool or technical method.",
"exemplar_skills": [
"CBAP",
"BABOK Guide",
"CCBA",
"ECBA",
"business analysis planning and monitoring",
"elicitation and collaboration",
"requirements lifecycle management",
"strategy analysis",
"solution evaluation"
],
"in_scope": "CBAP, CCBA, ECBA, BABOK Guide, business analysis planning and monitoring, elicitation and collaboration, requirements lifecycle management, strategy analysis, solution evaluation",
"name": "Business Analysis Certification",
"out_of_scope": "Software development, data analysis methods, project management certification, product management, technical architecture review, QA test execution",
"overlap_flags": [
{
"reason": "Both involve requirements, but this dimension is about professional business analysis certification and practice, while the catalog dimension is about validating implemented behavior against requirements.",
"with_dim_id": "requirements-and-acceptance-validation",
"with_dim_name": null,
"with_role": null
}
],
"tentative_id": "d_init_01"
}
],
"merge_log": [],
"placed": {
"name": "CBAP",
"placement_confidence": 0.92,
"primary_dimension": "d_init_01",
"reasoning": "Deterministic JD placement: locked_dimensions has 1 dimension(s) from skill-driven dimension generation after reconciliation; primary_dimension is the first locked dim.",
"secondary_dimensions": [],
"skill_id": "cbap"
},
"relationships": {
"child_skills": [],
"parent_skills": [],
"related_to": [
"risk-based-testing",
"acceptance-criteria-validation",
"acceptance-criteria-checks",
"capacity-planning",
"session-based-testing"
],
"requires": [],
"skill_id": "cbap",
"suppress_on_match": []
},
"skill_id": "cbap",
"split_log": [],
"typed": {
"alternatives_considered": [],
"confidence": 0.98,
"name": "CBAP",
"reasoning": "CBAP is a formal third-party credential, so by the Certification rule it is a certification rather than a concept or methodology.",
"skill_id": "cbap",
"subtype": "business_analysis_professional_certification",
"type": "Certification"
},
"warnings": []
},
"source_tag": "llm",
"was_in_llm_skills": true
},
{
"aliases_in_db": [],
"canonical": null,
"dimensions": [
{
"dimension": {
"difficulty_hint": null,
"display_name": "Business Analysis Certification",
"id": null,
"rationale": "Formal business analysis credentialing and exam-based competency in requirements, stakeholder analysis, and solution evaluation. CCBA belongs here because it is a recognized business analysis certification rather than a technical skill or tool.",
"slug": "d_init_01",
"source": "llm"
},
"input_skill": "CCBA",
"llm_role": null,
"roles_from_db": []
}
],
"input_skill": "CCBA",
"matched_via": null,
"new_alias_persisted": false,
"new_alias_text": null,
"new_skill_meta": {
"derived": {
"category": "Certification",
"skill_nature": "CREDENTIAL",
"sub_category": "business_analysis_certification",
"typical_lifespan": "EVERGREEN",
"version_strategy": "NOT_APPLICABLE",
"volatility": "STABLE"
},
"enrichment": {
"ambiguity": {
"ambiguity_flag": true,
"confused_with": [
"cbap"
],
"reasoning": "CCBA is a business analysis certification acronym and can be mistaken for the closely related CBAP certification in job descriptions, especially when abbreviations are listed without expansion."
},
"context_keywords": {
"context_keywords": [
"BABOK",
"IIBA",
"business analysis",
"requirements elicitation",
"stakeholder analysis",
"process modeling",
"use cases",
"user stories",
"gap analysis",
"traceability matrix",
"solution assessment",
"requirements management",
"workshop facilitation",
"UML",
"SWOT analysis"
]
},
"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.95,
"license": null,
"vendor": "International Institute of Business Analysis",
"year_introduced": 2008
},
"versioning": {
"current_version": null,
"version_aliases": {},
"versioned": false
}
},
"locked_dimensions": [
{
"description": "Formal business analysis credentialing and exam-based competency in requirements, stakeholder analysis, and solution evaluation. CCBA belongs here because it is a recognized business analysis certification rather than a technical skill or tool.",
"exemplar_skills": [
"CCBA",
"CBAP",
"ECBA",
"BABOK",
"business analysis certification",
"requirements elicitation",
"stakeholder analysis"
],
"in_scope": "CCBA, CBAP, ECBA, business analysis certification, BABOK knowledge areas, requirements elicitation, stakeholder analysis, solution assessment, business process analysis",
"name": "Business Analysis Certification",
"out_of_scope": "requirements-and-acceptance-validation, project management certification, agile delivery methods, technical system analysis, data analysis tools, which belong to separate practice or technical dimensions",
"overlap_flags": [
{
"reason": "Both touch requirements, but CCBA is a credential covering broader business analysis practice rather than validation of implemented behavior.",
"with_dim_id": "requirements-and-acceptance-validation",
"with_dim_name": null,
"with_role": null
}
],
"tentative_id": "d_init_01"
}
],
"merge_log": [],
"placed": {
"name": "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 fits Certification rather than a concept or methodology.",
"skill_id": "ccba",
"subtype": "business_analysis_certification",
"type": "Certification"
},
"warnings": []
},
"source_tag": "llm",
"was_in_llm_skills": true
},
{
"aliases_in_db": [],
"canonical": null,
"dimensions": [
{
"dimension": {
"difficulty_hint": null,
"display_name": "Spreadsheet Analysis and Modeling",
"id": null,
"rationale": "Using spreadsheets to organize, analyze, and present data for business decisions. Excel belongs here because it is the core tool for tabular analysis, formulas, pivoting, and lightweight modeling in analyst workflows.",
"slug": "d_init_01",
"source": "llm"
},
"input_skill": "Excel",
"llm_role": null,
"roles_from_db": []
}
],
"input_skill": "Excel",
"matched_via": null,
"new_alias_persisted": false,
"new_alias_text": null,
"new_skill_meta": {
"derived": {
"category": "Tool",
"skill_nature": "TOOL",
"sub_category": "spreadsheet_software",
"typical_lifespan": "EVERGREEN",
"version_strategy": "SEPARATE_ENTITY",
"volatility": "STABLE"
},
"enrichment": {
"ambiguity": {
"ambiguity_flag": false,
"confused_with": [],
"reasoning": "Excel is a well-known spreadsheet application and, in typical JDs, is unlikely to be confused with another catalog skill."
},
"context_keywords": {
"context_keywords": [
"pivot tables",
"VLOOKUP",
"XLOOKUP",
"SUMIF",
"INDEX MATCH",
"macros",
"VBA",
"Power Query",
"Power Pivot",
"data validation",
"conditional formatting",
"charts",
"dashboards",
"CSV",
"financial modeling"
]
},
"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 support and it remains a standard spreadsheet tool rather than a sunset product."
},
"skill_id": "excel",
"vendor_license": {
"confidence": 0.99,
"license": "proprietary",
"vendor": "Microsoft",
"year_introduced": 1985
},
"versioning": {
"current_version": "Microsoft 365 / Excel 2024",
"version_aliases": {
"Excel 2010": "Microsoft 365 / Excel 2024",
"Excel 2013": "Microsoft 365 / Excel 2024",
"Excel 2016": "Microsoft 365 / Excel 2024",
"Excel 2019": "Microsoft 365 / Excel 2024",
"Excel 2021": "Microsoft 365 / Excel 2024",
"Excel 2024": "Microsoft 365 / Excel 2024",
"Excel 365": "Microsoft 365 / Excel 2024",
"Microsoft 365 Excel": "Microsoft 365 / Excel 2024"
},
"versioned": true
}
},
"locked_dimensions": [
{
"description": "Using spreadsheets to organize, analyze, and present data for business decisions. Excel belongs here because it is the core tool for tabular analysis, formulas, pivoting, and lightweight modeling in analyst workflows.",
"exemplar_skills": [
"Excel",
"Pivot Tables",
"VLOOKUP",
"XLOOKUP",
"Conditional Formatting",
"Data Cleaning in Excel",
"What-If Analysis",
"Excel Charts"
],
"in_scope": "Excel, formulas and functions, pivot tables, charts and graphs, data cleaning in spreadsheets, lookup functions, conditional formatting, what-if analysis, basic dashboards, workbook organization",
"name": "Spreadsheet Analysis and Modeling",
"out_of_scope": "SQL querying and database design, statistical inference and experiment design, BI platform dashboarding, programming-language automation, data governance and access policy",
"overlap_flags": [
{
"reason": "Excel is often used for descriptive analysis, but statistical interpretation and inference belong to the statistics dimension.",
"with_dim_id": "statistical-reasoning-for-analysis",
"with_dim_name": null,
"with_role": null
},
{
"reason": "Excel can produce reports and dashboards, but platform-specific dashboard configuration is a separate cluster.",
"with_dim_id": "reporting-and-dashboard-configuration",
"with_dim_name": null,
"with_role": null
}
],
"tentative_id": "d_init_01"
}
],
"merge_log": [],
"placed": {
"name": "Excel",
"placement_confidence": 0.92,
"primary_dimension": "d_init_01",
"reasoning": "Deterministic JD placement: locked_dimensions has 1 dimension(s) from skill-driven dimension generation after reconciliation; primary_dimension is the first locked dim.",
"secondary_dimensions": [],
"skill_id": "excel"
},
"relationships": {
"child_skills": [],
"parent_skills": [],
"related_to": [
"dashboards",
"summary-statistics",
"scorecards",
"runbooks"
],
"requires": [],
"skill_id": "excel",
"suppress_on_match": []
},
"skill_id": "excel",
"split_log": [],
"typed": {
"alternatives_considered": [],
"confidence": 0.98,
"name": "Excel",
"reasoning": "Excel is software you operate directly as a user rather than a hosted multi-tenant environment or a code package, so under the Tool vs Framework and Platform vs Tool rules it is a Tool.",
"skill_id": "excel",
"subtype": "spreadsheet_software",
"type": "Tool"
},
"warnings": []
},
"source_tag": "llm",
"was_in_llm_skills": true
},
{
"aliases_in_db": [],
"canonical": null,
"dimensions": [
{
"dimension": {
"difficulty_hint": null,
"display_name": "Functional Requirements Documentation",
"id": null,
"rationale": "Covers writing and maintaining functional requirement documents that define what a product or system should do. FRDs belong here because they capture business needs, scope, behaviors, and acceptance expectations in a structured 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 common alternate skill name in the catalog."
},
"context_keywords": {
"context_keywords": [
"BRD",
"PRD",
"use cases",
"user stories",
"acceptance criteria",
"requirements traceability",
"scope definition",
"functional specification",
"business rules",
"wireframes",
"process flows",
"stakeholder review",
"sign-off",
"change requests",
"requirements gathering"
]
},
"maturity": {
"confidence": 0.86,
"maturity": "well_known",
"reasoning": "Functional requirements documents are a standard artifact in software and systems JDs/SDLCs, commonly requested alongside BRDs/PRDs and used across enterprise delivery teams."
},
"skill_id": "frds",
"vendor_license": {
"confidence": 0.98,
"license": null,
"vendor": null,
"year_introduced": null
},
"versioning": {
"current_version": null,
"version_aliases": {},
"versioned": false
}
},
"locked_dimensions": [
{
"description": "Covers writing and maintaining functional requirement documents that define what a product or system should do. FRDs belong here because they capture business needs, scope, behaviors, and acceptance expectations in a structured requirements artifact.",
"exemplar_skills": [
"FRDs",
"functional requirements documentation",
"business requirements gathering",
"requirements specification",
"acceptance criteria definition",
"scope definition"
],
"in_scope": "FRDs, functional requirements documents, business requirements, feature scope definition, user needs capture, acceptance criteria, requirement traceability",
"name": "Functional Requirements Documentation",
"out_of_scope": "technical design specs, API implementation details, test execution, project scheduling, data modeling, which belong to architecture, engineering, QA, or planning dimensions",
"overlap_flags": [
{
"reason": "FRDs often feed validation work, but this dimension is about authoring requirements rather than checking implementation against them.",
"with_dim_id": "requirements-and-acceptance-validation",
"with_dim_name": null,
"with_role": null
}
],
"tentative_id": "d_init_01"
}
],
"merge_log": [],
"placed": {
"name": "FRDs",
"placement_confidence": 0.92,
"primary_dimension": "d_init_01",
"reasoning": "Deterministic JD placement: locked_dimensions has 1 dimension(s) from skill-driven dimension generation after reconciliation; primary_dimension is the first locked dim.",
"secondary_dimensions": [],
"skill_id": "frds"
},
"relationships": {
"child_skills": [],
"parent_skills": [],
"related_to": [
"change-requests",
"contract-tests",
"runbooks"
],
"requires": [],
"skill_id": "frds",
"suppress_on_match": []
},
"skill_id": "frds",
"split_log": [],
"typed": {
"alternatives_considered": [
"Standard: ruled out \u2014 FRDs are not an industry-defined specification.",
"Format: ruled out \u2014 FRDs describe content, but the term refers to the document concept rather than a wire/data format.",
"Methodology: ruled out \u2014 FRDs are a deliverable, not a way of working."
],
"confidence": 0.78,
"name": "FRDs",
"reasoning": "FRDs are a named knowledge artifact describing requirements, so by the Concept vs Methodology rule they fit best as a concept rather than a process or software artifact.",
"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 and Process Familiarity",
"id": null,
"rationale": "General working familiarity with a business domain, product area, or process flow. For a Business Analyst, this captures being conversant enough to understand terminology, stakeholders, and how work gets done without implying deep technical specialization.",
"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 term, but it is not a likely extractor collision with a distinct catalog skill in typical JDs."
},
"context_keywords": {
"context_keywords": [
"working knowledge",
"hands-on experience",
"exposure to",
"awareness of",
"proficiency in",
"understanding of",
"practical experience",
"familiar with",
"basic knowledge",
"prior experience",
"subject matter",
"domain knowledge",
"operational knowledge",
"working familiarity",
"experience with"
]
},
"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 stacks, 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
}
},
"locked_dimensions": [
{
"description": "General working familiarity with a business domain, product area, or process flow. For a Business Analyst, this captures being conversant enough to understand terminology, stakeholders, and how work gets done without implying deep technical specialization.",
"exemplar_skills": [
"Familiarity",
"Business domain familiarity",
"Process familiarity",
"Product familiarity",
"Terminology awareness"
],
"in_scope": "Familiarity, business domain familiarity, process familiarity, product familiarity, stakeholder context, terminology awareness, workflow awareness",
"name": "Domain and Process Familiarity",
"out_of_scope": "Requirements elicitation, process mapping, data analysis, technical implementation, system configuration",
"overlap_flags": [
{
"reason": "A BA\u0027s familiarity often supports validating requirements, but this dimension is about knowing the domain rather than checking acceptance criteria.",
"with_dim_id": "requirements-and-acceptance-validation",
"with_dim_name": null,
"with_role": null
},
{
"reason": "If familiarity is specifically with system interactions or integration points, it may overlap with architecture knowledge rather than general domain awareness.",
"with_dim_id": "service-architecture-and-integration",
"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": [],
"confidence": 0.93,
"name": "Familiarity",
"reasoning": "Familiarity is a named knowledge unit about recognition or prior exposure, so by the Concept vs Methodology rule it is a Concept rather than a way of working.",
"skill_id": "familiarity",
"subtype": "familiarity",
"type": "Concept"
},
"warnings": []
},
"source_tag": "llm",
"was_in_llm_skills": true
},
{
"aliases_in_db": [],
"canonical": null,
"dimensions": [
{
"dimension": {
"difficulty_hint": null,
"display_name": "Domain Knowledge and Business Context",
"id": null,
"rationale": "Understanding the subject-matter area, business processes, and terminology needed to interpret requirements and make sound analysis decisions. For a Business Analyst, knowledge is the foundation for eliciting, validating, and communicating what the business actually needs.",
"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 easily mean knowledge management, knowledge graphs, or knowledge base work rather than the generic concept."
},
"context_keywords": {
"context_keywords": [
"domain expertise",
"subject matter expert",
"SME",
"institutional knowledge",
"knowledge base",
"knowledge management",
"knowledge transfer",
"lessons learned",
"best practices",
"documentation",
"taxonomy",
"ontology",
"information architecture",
"expertise",
"troubleshooting"
]
},
"maturity": {
"confidence": 0.93,
"maturity": "niche",
"reasoning": "\u201cKnowledge\u201d is a generic concept, not a named engineering skill; JD searches rarely list it as a standalone requirement, unlike 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
}
},
"locked_dimensions": [
{
"description": "Understanding the subject-matter area, business processes, and terminology needed to interpret requirements and make sound analysis decisions. For a Business Analyst, knowledge is the foundation for eliciting, validating, and communicating what the business actually needs.",
"exemplar_skills": [
"Knowledge",
"Business domain knowledge",
"Process knowledge",
"Industry terminology",
"Business rules",
"Stakeholder context"
],
"in_scope": "Knowledge, business domain knowledge, process knowledge, product knowledge, industry terminology, stakeholder context, operational workflows, policy awareness, regulatory context, business rules",
"name": "Domain Knowledge and Business Context",
"out_of_scope": "Requirements elicitation techniques, user story writing, and acceptance criteria belong to requirements-and-acceptance-validation; data profiling and dataset fitness belong to data-quality-assessment; statistical inference belongs to statistical-reasoning-for-analysis",
"overlap_flags": [
{
"reason": "Business knowledge often informs requirements work, but the dimension here is the underlying domain understanding rather than validation of documented requirements.",
"with_dim_id": "requirements-and-acceptance-validation",
"with_dim_name": null,
"with_role": null
},
{
"reason": "In analytics-heavy BA work, knowledge can overlap with understanding data meaning, but data fitness and bias checks are owned by data quality assessment.",
"with_dim_id": "data-quality-assessment",
"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.98,
"name": "Knowledge",
"reasoning": "Knowledge is a named knowledge unit rather than a way of working, so by the Concept vs Methodology rule it fits Concept.",
"skill_id": "knowledge",
"subtype": "general_knowledge",
"type": "Concept"
},
"warnings": []
},
"source_tag": "llm",
"was_in_llm_skills": true
},
{
"aliases_in_db": [],
"canonical": null,
"dimensions": [],
"input_skill": "QA",
"matched_via": null,
"new_alias_persisted": false,
"new_alias_text": null,
"new_skill_meta": {
"derived": {
"category": "SoftSkill",
"skill_nature": "PRACTICE",
"sub_category": "quality_assurance",
"typical_lifespan": "EVERGREEN",
"version_strategy": "NOT_APPLICABLE",
"volatility": "STABLE"
},
"enrichment": {
"ambiguity": {
"ambiguity_flag": true,
"confused_with": [
"quality_assurance"
],
"reasoning": "\"QA\" is a common abbreviation for quality assurance, but in JDs it can also mean quality analyst or testing-related roles; the catalog likely has the full quality_assurance skill, making this abbreviation potentially conflated."
},
"context_keywords": {
"context_keywords": [
"test cases",
"test plans",
"regression testing",
"defect tracking",
"bug triage",
"UAT",
"test automation",
"Selenium",
"JIRA",
"manual testing",
"acceptance criteria",
"test scripts",
"traceability matrix",
"smoke testing",
"QA process"
]
},
"maturity": {
"confidence": 0.93,
"maturity": "well_known",
"reasoning": "QA is a standard hiring-pipeline requirement across software JDs, with frequent mentions of test planning, defect tracking, and regression testing; it remains broadly adopted rather than niche or sunsetted."
},
"skill_id": "qa",
"vendor_license": {
"confidence": 0.99,
"license": null,
"vendor": null,
"year_introduced": null
},
"versioning": {
"current_version": null,
"version_aliases": {},
"versioned": false
}
},
"locked_dimensions": [],
"merge_log": [
{
"into": "d_merge_01",
"into_name": "Requirements and Acceptance Validation",
"merged_from": [
"d_init_01",
"requirements-and-acceptance-validation"
],
"reasoning": "Both dims define the same skill cluster: checking delivered work against requirements, user stories, and acceptance criteria. Dim A\u2019s exemplars (QA, acceptance testing, requirements validation, user story verification, defect verification, UAT support) match Dim B\u2019s description of verifying implemented behavior against documented requirements. The extra exclusions in A only narrow scope; they do not create a distinct cluster. Cross-role similarity is therefore a true duplicate, not a false positive."
}
],
"placed": {
"name": "QA",
"placement_confidence": 0.0,
"primary_dimension": "d_init_00",
"reasoning": "Stub placement: no locked_dimensions after Stage 2/3; downstream containment and enrichment use placeholders only.",
"secondary_dimensions": [],
"skill_id": "qa"
},
"relationships": {
"child_skills": [],
"parent_skills": [],
"related_to": [
"acceptance-criteria-checks",
"acceptance-criteria-validation",
"test-case-authoring",
"defect-retest",
"risk-based-testing",
"cross-browser-testing",
"session-based-testing",
"charter-based-testing"
],
"requires": [],
"skill_id": "qa",
"suppress_on_match": []
},
"skill_id": "qa",
"split_log": [],
"typed": {
"alternatives_considered": [
"Methodology: ruled out \u2014 QA is a broad practice area, but the term alone does not specify a concrete process like TDD or Scrum.",
"Concept: ruled out \u2014 QA is more an operational capability/practice than a single knowledge unit.",
"Domain: ruled out \u2014 QA is not a vertical or industry problem-space."
],
"confidence": 0.78,
"name": "QA",
"reasoning": "QA is best treated as a SoftSkill here because, in this context, it refers to the human practice of quality assurance and review rather than a specific tool, framework, or formal methodology.",
"skill_id": "qa",
"subtype": "quality_assurance",
"type": "SoftSkill"
},
"warnings": [
"placement_stub_no_locked_dimensions"
]
},
"source_tag": "llm",
"was_in_llm_skills": true
},
{
"aliases_in_db": [],
"canonical": null,
"dimensions": [
{
"dimension": {
"difficulty_hint": null,
"display_name": "Software Development Lifecycle",
"id": null,
"rationale": "Covers the end-to-end process for planning, building, testing, releasing, and maintaining software. SDLC belongs here because it refers to the overall lifecycle framework rather than a single technical implementation area.",
"slug": "d_init_01",
"source": "llm"
},
"input_skill": "SDLC",
"llm_role": null,
"roles_from_db": []
}
],
"input_skill": "SDLC",
"matched_via": null,
"new_alias_persisted": false,
"new_alias_text": null,
"new_skill_meta": {
"derived": {
"category": "Methodology",
"skill_nature": "METHODOLOGY",
"sub_category": "software_development_lifecycle",
"typical_lifespan": "EVERGREEN",
"version_strategy": "NOT_APPLICABLE",
"volatility": "STABLE"
},
"enrichment": {
"ambiguity": {
"ambiguity_flag": false,
"confused_with": [],
"reasoning": "SDLC is a standard, well-known acronym for software development lifecycle and is usually unambiguous in job descriptions."
},
"context_keywords": {
"context_keywords": [
"requirements gathering",
"design review",
"implementation",
"code review",
"testing",
"QA",
"UAT",
"deployment",
"release management",
"change management",
"Agile",
"Scrum",
"waterfall",
"CI/CD",
"DevOps"
]
},
"maturity": {
"confidence": 0.93,
"maturity": "well_known",
"reasoning": "SDLC is a standard term in software engineering job descriptions and vendor training/certifications; it underpins common frameworks like Agile, DevOps, and Waterfall rather than being a niche tool."
},
"skill_id": "sdlc",
"vendor_license": {
"confidence": 0.99,
"license": null,
"vendor": null,
"year_introduced": null
},
"versioning": {
"current_version": null,
"version_aliases": {},
"versioned": false
}
},
"locked_dimensions": [
{
"description": "Covers the end-to-end process for planning, building, testing, releasing, and maintaining software. SDLC belongs here because it refers to the overall lifecycle framework rather than a single technical implementation area.",
"exemplar_skills": [
"SDLC",
"software development lifecycle",
"requirements gathering",
"code review",
"release planning",
"change management"
],
"in_scope": "SDLC, software development lifecycle, requirements, design, implementation, testing, release, maintenance, change management, version control workflow, code review, deployment planning",
"name": "Software Development Lifecycle",
"out_of_scope": "Requirements and Acceptance Validation, frontend testing, backend coding, release tooling specifics, project management methods, which are owned by more specialized dimensions",
"overlap_flags": [
{
"reason": "SDLC often includes validation activities, but that catalog dimension is specifically about checking implemented behavior against requirements.",
"with_dim_id": "requirements-and-acceptance-validation",
"with_dim_name": null,
"with_role": null
},
{
"reason": "SDLC includes release as a phase, but that dimension owns the concrete build and packaging mechanics.",
"with_dim_id": "build-configuration-and-release",
"with_dim_name": null,
"with_role": null
}
],
"tentative_id": "d_init_01"
}
],
"merge_log": [],
"placed": {
"name": "SDLC",
"placement_confidence": 0.92,
"primary_dimension": "d_init_01",
"reasoning": "Deterministic JD placement: locked_dimensions has 1 dimension(s) from skill-driven dimension generation after reconciliation; primary_dimension is the first locked dim.",
"secondary_dimensions": [],
"skill_id": "sdlc"
},
"relationships": {
"child_skills": [],
"parent_skills": [],
"related_to": [
"clean-architecture",
"acceptance-criteria-checks",
"acceptance-criteria-validation",
"dependency-mapping",
"defect-retest"
],
"requires": [],
"skill_id": "sdlc",
"suppress_on_match": []
},
"skill_id": "sdlc",
"split_log": [],
"typed": {
"alternatives_considered": [],
"confidence": 0.88,
"name": "SDLC",
"reasoning": "SDLC is best treated as a Methodology because it describes the process and phases for how software is developed and delivered, matching the Concept vs Methodology rule.",
"skill_id": "sdlc",
"subtype": "software_development_lifecycle",
"type": "Methodology"
},
"warnings": []
},
"source_tag": "llm",
"was_in_llm_skills": true
},
{
"aliases_in_db": [],
"canonical": null,
"dimensions": [
{
"dimension": {
"difficulty_hint": null,
"display_name": "Software as a Service",
"id": null,
"rationale": "Covers the SaaS product and delivery model: subscription-based software delivered over the internet, typically managed by a vendor and accessed through a browser or thin client. This fits the target skill because SaaS is the core business and deployment model being referenced.",
"slug": "d_init_01",
"source": "llm"
},
"input_skill": "SaaS",
"llm_role": null,
"roles_from_db": []
}
],
"input_skill": "SaaS",
"matched_via": null,
"new_alias_persisted": false,
"new_alias_text": null,
"new_skill_meta": {
"derived": {
"category": "Platform",
"skill_nature": "PLATFORM",
"sub_category": "software_as_a_service_platform",
"typical_lifespan": "EVERGREEN",
"version_strategy": "NOT_APPLICABLE",
"volatility": "STABLE"
},
"enrichment": {
"ambiguity": {
"ambiguity_flag": false,
"confused_with": [],
"reasoning": "SaaS is a standard, well-scoped term for software-as-a-service platforms in JDs; it is unlikely to be mistaken for a different catalog skill."
},
"context_keywords": {
"context_keywords": [
"multi-tenant",
"subscription billing",
"tenant isolation",
"self-service onboarding",
"usage-based pricing",
"SAML",
"SSO",
"RBAC",
"API integration",
"webhooks",
"provisioning",
"SLAs",
"customer portal",
"trial conversion",
"churn"
]
},
"maturity": {
"confidence": 0.96,
"maturity": "well_known",
"reasoning": "SaaS is a standard cloud delivery model and appears broadly across job descriptions for product, platform, and DevOps roles; major vendors like Salesforce, Microsoft, and Google market SaaS as a core offering."
},
"skill_id": "saas",
"vendor_license": {
"confidence": 0.78,
"license": "proprietary",
"vendor": "Salesforce",
"year_introduced": 1999
},
"versioning": {
"current_version": null,
"version_aliases": {},
"versioned": false
}
},
"locked_dimensions": [
{
"description": "Covers the SaaS product and delivery model: subscription-based software delivered over the internet, typically managed by a vendor and accessed through a browser or thin client. This fits the target skill because SaaS is the core business and deployment model being referenced.",
"exemplar_skills": [
"SaaS",
"multi-tenant SaaS",
"subscription software",
"web-based software delivery",
"customer tenant isolation",
"SaaS onboarding"
],
"in_scope": "SaaS, subscription software, multi-tenant application delivery, web-delivered software, vendor-hosted application access, recurring billing model, customer tenant isolation, SaaS onboarding, SaaS feature packaging",
"name": "Software as a Service",
"out_of_scope": "On-premises software deployment, desktop application licensing, infrastructure provisioning, API integration details, which belong to other product or engineering dimensions",
"overlap_flags": [
{
"reason": "SaaS products are often built on cloud services, but this dimension is about the business delivery model rather than choosing infrastructure primitives.",
"with_dim_id": "cloud-platform-service-selection",
"with_dim_name": null,
"with_role": null
},
{
"reason": "SaaS implementations commonly use service-oriented backends, but architecture patterns are a separate concern from the SaaS model itself.",
"with_dim_id": "service-architecture-and-integration",
"with_dim_name": null,
"with_role": null
}
],
"tentative_id": "d_init_01"
}
],
"merge_log": [],
"placed": {
"name": "SaaS",
"placement_confidence": 0.92,
"primary_dimension": "d_init_01",
"reasoning": "Deterministic JD placement: locked_dimensions has 1 dimension(s) from skill-driven dimension generation after reconciliation; primary_dimension is the first locked dim.",
"secondary_dimensions": [],
"skill_id": "saas"
},
"relationships": {
"child_skills": [],
"parent_skills": [],
"related_to": [
"cloud-run",
"azure-backup",
"cspm",
"policy-as-code",
"cloud-reference-architecture"
],
"requires": [],
"skill_id": "saas",
"suppress_on_match": []
},
"skill_id": "saas",
"split_log": [],
"typed": {
"alternatives_considered": [
"Service: ruled out \u2014 SaaS is the broader hosted environment, not a specific managed capability inside another platform.",
"Tool: ruled out \u2014 SaaS is not software you operate locally; it is delivered as a hosted platform."
],
"confidence": 0.93,
"name": "SaaS",
"reasoning": "By the Platform vs Tool rule, SaaS is a hosted multi-tenant environment delivered over APIs and managed 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",
"test_automation"
],
"reasoning": "\u201cTesting\u201d is a broad umbrella term in JDs and could refer to several specific testing methodologies in the catalog, especially unit, integration, or automated testing."
},
"context_keywords": {
"context_keywords": [
"unit testing",
"integration testing",
"test automation",
"test cases",
"test coverage",
"regression testing",
"smoke testing",
"mocking",
"stubs",
"fixtures",
"assertions",
"TDD",
"BDD",
"JUnit",
"pytest"
]
},
"maturity": {
"confidence": 0.98,
"maturity": "well_known",
"reasoning": "Software testing is a standard requirement in most engineering JDs and appears across QA, SDET, and developer roles; major frameworks and CI pipelines routinely include unit/integration testing."
},
"skill_id": "testing",
"vendor_license": {
"confidence": 0.99,
"license": null,
"vendor": null,
"year_introduced": null
},
"versioning": {
"current_version": null,
"version_aliases": {},
"versioned": false
}
},
"locked_dimensions": [],
"merge_log": [
{
"into": "d_merge_01",
"into_name": "Requirements and Acceptance Validation",
"merged_from": [
"d_init_01",
"requirements-and-acceptance-validation"
],
"reasoning": "Both dims define the same cluster: checking implemented behavior against requirements, user stories, and acceptance criteria. Dim A\u2019s exemplars like \"requirements validation,\" \"acceptance criteria verification,\" and \"user acceptance testing\" match Dim B\u2019s description of checking behavior against documented requirements. The cross-role difference is only wording; no distinct skill set appears."
}
],
"placed": {
"name": "Testing",
"placement_confidence": 0.0,
"primary_dimension": "d_init_00",
"reasoning": "Stub placement: no locked_dimensions after Stage 2/3; downstream containment and enrichment use placeholders only.",
"secondary_dimensions": [],
"skill_id": "testing"
},
"relationships": {
"child_skills": [],
"parent_skills": [],
"related_to": [
"risk-based-testing",
"session-based-testing",
"cross-browser-testing",
"smoke-testing",
"fuzzing",
"contract-tests",
"charter-based-testing"
],
"requires": [],
"skill_id": "testing",
"suppress_on_match": []
},
"skill_id": "testing",
"split_log": [],
"typed": {
"alternatives_considered": [
"Concept: ruled out \u2014 while testing has conceptual aspects, the skill name here refers to the practice/process of testing."
],
"confidence": 0.91,
"name": "Testing",
"reasoning": "By the Concept vs Methodology rule, Testing is fundamentally a way of working for validating software behavior 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": [],
"input_skill": "UAT",
"matched_via": null,
"new_alias_persisted": false,
"new_alias_text": null,
"new_skill_meta": {
"derived": {
"category": "Methodology",
"skill_nature": "METHODOLOGY",
"sub_category": "user_acceptance_testing",
"typical_lifespan": "EVERGREEN",
"version_strategy": "NOT_APPLICABLE",
"volatility": "STABLE"
},
"enrichment": {
"ambiguity": {
"ambiguity_flag": false,
"confused_with": [],
"reasoning": "UAT in JDs almost always means User Acceptance Testing; the acronym is standard and unlikely to be mistaken for another catalog skill in typical hiring context."
},
"context_keywords": {
"context_keywords": [
"test cases",
"test scripts",
"acceptance criteria",
"business users",
"end users",
"sign-off",
"defect triage",
"test plan",
"test scenarios",
"regression testing",
"stakeholder review",
"go-live",
"user stories",
"test environment",
"issue log"
]
},
"maturity": {
"confidence": 0.86,
"maturity": "well_known",
"reasoning": "UAT appears routinely in QA/BA job descriptions and enterprise release checklists as a standard pre-production signoff step, with no vendor sunset or replacement trend."
},
"skill_id": "uat",
"vendor_license": {
"confidence": 0.99,
"license": null,
"vendor": null,
"year_introduced": null
},
"versioning": {
"current_version": null,
"version_aliases": {},
"versioned": false
}
},
"locked_dimensions": [],
"merge_log": [
{
"into": "d_merge_01",
"into_name": "Requirements and Acceptance Validation (UAT)",
"merged_from": [
"d_init_01",
"requirements-and-acceptance-validation"
],
"reasoning": "Both dimensions describe the same conceptual cluster: validating delivered behavior against documented requirements, user stories, and acceptance criteria. Dim A explicitly includes UAT, acceptance criteria validation, requirements traceability, business scenario walkthroughs, and release sign-off readiness; Dim B says essentially the same thing in broader terms, including checking implemented behavior against requirements, user stories, and acceptance criteria. The exemplar skills in A (UAT, user acceptance testing, requirements validation, release sign-off) all fit B\u2019s description, and B adds no distinct skill anchor beyond the same acceptance/requirements check. The cross-role similarity is a wording overlap, not a role-specific distinction."
}
],
"placed": {
"name": "UAT",
"placement_confidence": 0.0,
"primary_dimension": "d_init_00",
"reasoning": "Stub placement: no locked_dimensions after Stage 2/3; downstream containment and enrichment use placeholders only.",
"secondary_dimensions": [],
"skill_id": "uat"
},
"relationships": {
"child_skills": [],
"parent_skills": [],
"related_to": [
"acceptance-criteria-checks",
"session-based-testing",
"test-case-authoring"
],
"requires": [],
"skill_id": "uat",
"suppress_on_match": []
},
"skill_id": "uat",
"split_log": [],
"typed": {
"alternatives_considered": [],
"confidence": 0.93,
"name": "UAT",
"reasoning": "UAT is a way of working for validating software with end users, so by the Concept vs Methodology rule it is a Methodology rather than a tool or concept.",
"skill_id": "uat",
"subtype": "user_acceptance_testing",
"type": "Methodology"
},
"warnings": [
"placement_stub_no_locked_dimensions"
]
},
"source_tag": "llm",
"was_in_llm_skills": true
},
{
"aliases_in_db": [],
"canonical": null,
"dimensions": [
{
"dimension": {
"difficulty_hint": null,
"display_name": "Process and Workflow Diagramming",
"id": null,
"rationale": "Creating business and technical diagrams that map processes, workflows, handoffs, and system interactions. Visio belongs here because it is commonly used to document flows, swimlanes, and operational procedures for analysis and communication.",
"slug": "d_init_01",
"source": "llm"
},
"input_skill": "Visio",
"llm_role": null,
"roles_from_db": []
}
],
"input_skill": "Visio",
"matched_via": null,
"new_alias_persisted": false,
"new_alias_text": null,
"new_skill_meta": {
"derived": {
"category": "Tool",
"skill_nature": "TOOL",
"sub_category": "diagramming_tool",
"typical_lifespan": "EVERGREEN",
"version_strategy": "NOT_APPLICABLE",
"volatility": "STABLE"
},
"enrichment": {
"ambiguity": {
"ambiguity_flag": false,
"confused_with": [],
"reasoning": "Visio is a specific Microsoft diagramming tool; in typical JDs it is unlikely to be confused with another catalog skill."
},
"context_keywords": {
"context_keywords": [
"process flow",
"swimlane",
"flowchart",
"org chart",
"BPMN",
"UML",
"network diagram",
"data flow diagram",
"wireframe",
"site map",
"floor plan",
"cross-functional",
"business process",
"workflow",
"diagram templates"
]
},
"maturity": {
"confidence": 0.86,
"maturity": "well_known",
"reasoning": "Common in enterprise JDs for process/network diagrams and Microsoft 365 stack roles; no vendor sunset and still broadly supported in hiring pipelines."
},
"skill_id": "visio",
"vendor_license": {
"confidence": 0.99,
"license": "proprietary",
"vendor": "Microsoft",
"year_introduced": 1992
},
"versioning": {
"current_version": null,
"version_aliases": {},
"versioned": false
}
},
"locked_dimensions": [
{
"description": "Creating business and technical diagrams that map processes, workflows, handoffs, and system interactions. Visio belongs here because it is commonly used to document flows, swimlanes, and operational procedures for analysis and communication.",
"exemplar_skills": [
"Visio",
"flowcharting",
"swimlane diagrams",
"process mapping",
"workflow diagramming",
"BPMN modeling"
],
"in_scope": "Visio, flowcharts, swimlane diagrams, BPMN-style process maps, cross-functional workflow diagrams, decision trees, process documentation",
"name": "Process and Workflow Diagramming",
"out_of_scope": "Database schema design, software code implementation, project scheduling, presentation slides, which belong to other dimensions such as data modeling, programming, or business communication",
"overlap_flags": [
{
"reason": "Process diagrams are often created to clarify requirements and validate intended behavior with stakeholders.",
"with_dim_id": "requirements-and-acceptance-validation",
"with_dim_name": null,
"with_role": null
},
{
"reason": "Visio is also used for technical diagrams such as network topology and infrastructure documentation.",
"with_dim_id": "network-documentation-and-standards",
"with_dim_name": null,
"with_role": null
}
],
"tentative_id": "d_init_01"
}
],
"merge_log": [],
"placed": {
"name": "Visio",
"placement_confidence": 0.92,
"primary_dimension": "d_init_01",
"reasoning": "Deterministic JD placement: locked_dimensions has 1 dimension(s) from skill-driven dimension generation after reconciliation; primary_dimension is the first locked dim.",
"secondary_dimensions": [],
"skill_id": "visio"
},
"relationships": {
"child_skills": [],
"parent_skills": [],
"related_to": [],
"requires": [],
"skill_id": "visio",
"suppress_on_match": []
},
"skill_id": "visio",
"split_log": [],
"typed": {
"alternatives_considered": [],
"confidence": 0.98,
"name": "Visio",
"reasoning": "Visio is software you operate to create diagrams, so by the Tool vs Framework rule it is a Tool rather than something you build applications inside.",
"skill_id": "visio",
"subtype": "diagramming_tool",
"type": "Tool"
},
"warnings": []
},
"source_tag": "llm",
"was_in_llm_skills": true
},
{
"aliases_in_db": [],
"canonical": null,
"dimensions": [],
"input_skill": "analysis",
"matched_via": null,
"new_alias_persisted": false,
"new_alias_text": null,
"new_skill_meta": null,
"source_tag": "llm",
"was_in_llm_skills": true
},
{
"aliases_in_db": [],
"canonical": null,
"dimensions": [],
"input_skill": "communication",
"matched_via": null,
"new_alias_persisted": false,
"new_alias_text": null,
"new_skill_meta": null,
"source_tag": "llm",
"was_in_llm_skills": true
},
{
"aliases_in_db": [],
"canonical": null,
"dimensions": [],
"input_skill": "data",
"matched_via": null,
"new_alias_persisted": false,
"new_alias_text": null,
"new_skill_meta": null,
"source_tag": "llm",
"was_in_llm_skills": true
},
{
"aliases_in_db": [],
"canonical": null,
"dimensions": [],
"input_skill": "databases",
"matched_via": null,
"new_alias_persisted": false,
"new_alias_text": null,
"new_skill_meta": null,
"source_tag": "llm",
"was_in_llm_skills": true
},
{
"aliases_in_db": [],
"canonical": null,
"dimensions": [],
"input_skill": "documentation",
"matched_via": null,
"new_alias_persisted": false,
"new_alias_text": null,
"new_skill_meta": null,
"source_tag": "llm",
"was_in_llm_skills": true
},
{
"aliases_in_db": [],
"canonical": null,
"dimensions": [],
"input_skill": "fintech",
"matched_via": null,
"new_alias_persisted": false,
"new_alias_text": null,
"new_skill_meta": null,
"source_tag": "llm",
"was_in_llm_skills": true
},
{
"aliases_in_db": [],
"canonical": null,
"dimensions": [],
"input_skill": "healthcare",
"matched_via": null,
"new_alias_persisted": false,
"new_alias_text": null,
"new_skill_meta": null,
"source_tag": "llm",
"was_in_llm_skills": true
},
{
"aliases_in_db": [],
"canonical": null,
"dimensions": [],
"input_skill": "insights",
"matched_via": null,
"new_alias_persisted": false,
"new_alias_text": null,
"new_skill_meta": null,
"source_tag": "llm",
"was_in_llm_skills": true
},
{
"aliases_in_db": [],
"canonical": null,
"dimensions": [],
"input_skill": "methodologies",
"matched_via": null,
"new_alias_persisted": false,
"new_alias_text": null,
"new_skill_meta": null,
"source_tag": "llm",
"was_in_llm_skills": true
},
{
"aliases_in_db": [],
"canonical": null,
"dimensions": [],
"input_skill": "optimization",
"matched_via": null,
"new_alias_persisted": false,
"new_alias_text": null,
"new_skill_meta": null,
"source_tag": "llm",
"was_in_llm_skills": true
},
{
"aliases_in_db": [],
"canonical": null,
"dimensions": [],
"input_skill": "reporting",
"matched_via": null,
"new_alias_persisted": false,
"new_alias_text": null,
"new_skill_meta": null,
"source_tag": "llm",
"was_in_llm_skills": true
},
{
"aliases_in_db": [],
"canonical": null,
"dimensions": [],
"input_skill": "requirements",
"matched_via": null,
"new_alias_persisted": false,
"new_alias_text": null,
"new_skill_meta": null,
"source_tag": "llm",
"was_in_llm_skills": true
},
{
"aliases_in_db": [],
"canonical": null,
"dimensions": [],
"input_skill": "software",
"matched_via": null,
"new_alias_persisted": false,
"new_alias_text": null,
"new_skill_meta": null,
"source_tag": "llm",
"was_in_llm_skills": true
},
{
"aliases_in_db": [],
"canonical": null,
"dimensions": [],
"input_skill": "specifications",
"matched_via": null,
"new_alias_persisted": false,
"new_alias_text": null,
"new_skill_meta": null,
"source_tag": "llm",
"was_in_llm_skills": true
},
{
"aliases_in_db": [],
"canonical": null,
"dimensions": [],
"input_skill": "stories",
"matched_via": null,
"new_alias_persisted": false,
"new_alias_text": null,
"new_skill_meta": null,
"source_tag": "llm",
"was_in_llm_skills": true
},
{
"aliases_in_db": [],
"canonical": null,
"dimensions": [],
"input_skill": "trends",
"matched_via": null,
"new_alias_persisted": false,
"new_alias_text": null,
"new_skill_meta": null,
"source_tag": "llm",
"was_in_llm_skills": true
},
{
"aliases_in_db": [],
"canonical": null,
"dimensions": [],
"input_skill": "workshops",
"matched_via": null,
"new_alias_persisted": false,
"new_alias_text": null,
"new_skill_meta": null,
"source_tag": "llm",
"was_in_llm_skills": true
}
],
"unmatched_skills": [
"APIs",
"Acceptance",
"BI",
"CBAP",
"CCBA",
"Excel",
"FRDs",
"Familiarity",
"Knowledge",
"QA",
"SDLC",
"SaaS",
"Testing",
"UAT",
"Visio"
]
}
API 3 — final-role-output
{
"chosen_role": {
"display_name": "Business Analyst",
"id": null,
"rationale": "Most evidence points to business analysis and requirements work, with BI/reporting as supporting signals rather than a pure data or MLOps role.",
"role_archetype": "Business analysis professional focused on requirements gathering, process analysis, stakeholder communication, and translating business needs into functional specifications.",
"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": "CBAP",
"tag": "new"
},
{
"skill": "CCBA",
"tag": "new"
},
{
"skill": "Excel",
"tag": "new"
},
{
"skill": "FRDs",
"tag": "new"
},
{
"skill": "Familiarity",
"tag": "new"
},
{
"skill": "Knowledge",
"tag": "new"
},
{
"skill": "QA",
"tag": "new"
},
{
"skill": "SDLC",
"tag": "new"
},
{
"skill": "SaaS",
"tag": "new"
},
{
"skill": "Testing",
"tag": "new"
},
{
"skill": "UAT",
"tag": "new"
},
{
"skill": "Visio",
"tag": "new"
},
{
"skill": "analysis",
"tag": "new"
},
{
"skill": "communication",
"tag": "new"
},
{
"skill": "data",
"tag": "new"
},
{
"skill": "databases",
"tag": "new"
},
{
"skill": "documentation",
"tag": "new"
},
{
"skill": "fintech",
"tag": "new"
},
{
"skill": "healthcare",
"tag": "new"
},
{
"skill": "insights",
"tag": "new"
},
{
"skill": "methodologies",
"tag": "new"
},
{
"skill": "optimization",
"tag": "new"
},
{
"skill": "reporting",
"tag": "new"
},
{
"skill": "requirements",
"tag": "new"
},
{
"skill": "software",
"tag": "new"
},
{
"skill": "specifications",
"tag": "new"
},
{
"skill": "stories",
"tag": "new"
},
{
"skill": "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": "Application Programming Interfaces",
"id": null,
"rationale": "Designing, consuming, and documenting software interfaces that let systems exchange data and actions. APIs belong here because they define the contract used by applications, services, and external platforms.",
"slug": "d_init_01",
"source": "llm"
},
"dimension_id": null,
"input_skill": "APIs",
"llm_role": null,
"matched_chosen_role": false,
"role_dimension_saved": false,
"roles_from_db": [],
"skill_dimension_saved": false,
"skill_id": null,
"skill_tag": "new",
"skipped_reason": "skill_not_in_db_v3_proposed"
},
{
"chosen_role_id": null,
"dimension": {
"difficulty_hint": null,
"display_name": "Business Intelligence",
"id": null,
"rationale": "Covers the use of data to create reports, dashboards, and decision-support views for business stakeholders. BI fits here because it commonly refers to the discipline of turning operational data into accessible analysis and performance monitoring.",
"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 Analysis Certification",
"id": null,
"rationale": "Professional certification knowledge for business analysts, including the CBAP credential and the BABOK-based practices it represents. This belongs here because CBAP is a certification focused on business analysis competencies, techniques, and professional standards rather than a software tool or technical method.",
"slug": "d_init_01",
"source": "llm"
},
"dimension_id": null,
"input_skill": "CBAP",
"llm_role": null,
"matched_chosen_role": false,
"role_dimension_saved": false,
"roles_from_db": [],
"skill_dimension_saved": false,
"skill_id": null,
"skill_tag": "new",
"skipped_reason": "skill_not_in_db_v3_proposed"
},
{
"chosen_role_id": null,
"dimension": {
"difficulty_hint": null,
"display_name": "Business Analysis Certification",
"id": null,
"rationale": "Formal business analysis credentialing and exam-based competency in requirements, stakeholder analysis, and solution evaluation. CCBA belongs here because it is a recognized business analysis certification rather than a technical skill or tool.",
"slug": "d_init_01",
"source": "llm"
},
"dimension_id": null,
"input_skill": "CCBA",
"llm_role": null,
"matched_chosen_role": false,
"role_dimension_saved": false,
"roles_from_db": [],
"skill_dimension_saved": false,
"skill_id": null,
"skill_tag": "new",
"skipped_reason": "skill_not_in_db_v3_proposed"
},
{
"chosen_role_id": null,
"dimension": {
"difficulty_hint": null,
"display_name": "Spreadsheet Analysis and Modeling",
"id": null,
"rationale": "Using spreadsheets to organize, analyze, and present data for business decisions. Excel belongs here because it is the core tool for tabular analysis, formulas, pivoting, and lightweight modeling in analyst workflows.",
"slug": "d_init_01",
"source": "llm"
},
"dimension_id": null,
"input_skill": "Excel",
"llm_role": null,
"matched_chosen_role": false,
"role_dimension_saved": false,
"roles_from_db": [],
"skill_dimension_saved": false,
"skill_id": null,
"skill_tag": "new",
"skipped_reason": "skill_not_in_db_v3_proposed"
},
{
"chosen_role_id": null,
"dimension": {
"difficulty_hint": null,
"display_name": "Functional Requirements Documentation",
"id": null,
"rationale": "Covers writing and maintaining functional requirement documents that define what a product or system should do. FRDs belong here because they capture business needs, scope, behaviors, and acceptance expectations in a structured 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 and Process Familiarity",
"id": null,
"rationale": "General working familiarity with a business domain, product area, or process flow. For a Business Analyst, this captures being conversant enough to understand terminology, stakeholders, and how work gets done without implying deep technical specialization.",
"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": "Understanding the subject-matter area, business processes, and terminology needed to interpret requirements and make sound analysis decisions. For a Business Analyst, knowledge is the foundation for eliciting, validating, and communicating what the business actually needs.",
"slug": "d_init_01",
"source": "llm"
},
"dimension_id": null,
"input_skill": "Knowledge",
"llm_role": null,
"matched_chosen_role": false,
"role_dimension_saved": false,
"roles_from_db": [],
"skill_dimension_saved": false,
"skill_id": null,
"skill_tag": "new",
"skipped_reason": "skill_not_in_db_v3_proposed"
},
{
"chosen_role_id": null,
"dimension": {
"difficulty_hint": null,
"display_name": "Software Development Lifecycle",
"id": null,
"rationale": "Covers the end-to-end process for planning, building, testing, releasing, and maintaining software. SDLC belongs here because it refers to the overall lifecycle framework rather than a single technical implementation area.",
"slug": "d_init_01",
"source": "llm"
},
"dimension_id": null,
"input_skill": "SDLC",
"llm_role": null,
"matched_chosen_role": false,
"role_dimension_saved": false,
"roles_from_db": [],
"skill_dimension_saved": false,
"skill_id": null,
"skill_tag": "new",
"skipped_reason": "skill_not_in_db_v3_proposed"
},
{
"chosen_role_id": null,
"dimension": {
"difficulty_hint": null,
"display_name": "Software as a Service",
"id": null,
"rationale": "Covers the SaaS product and delivery model: subscription-based software delivered over the internet, typically managed by a vendor and accessed through a browser or thin client. This fits the target skill because SaaS is the core business and deployment model being referenced.",
"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": "Process and Workflow Diagramming",
"id": null,
"rationale": "Creating business and technical diagrams that map processes, workflows, handoffs, and system interactions. Visio belongs here because it is commonly used to document flows, swimlanes, and operational procedures for analysis and communication.",
"slug": "d_init_01",
"source": "llm"
},
"dimension_id": null,
"input_skill": "Visio",
"llm_role": null,
"matched_chosen_role": false,
"role_dimension_saved": false,
"roles_from_db": [],
"skill_dimension_saved": false,
"skill_id": null,
"skill_tag": "new",
"skipped_reason": "skill_not_in_db_v3_proposed"
}
],
"new_skills_created": 0,
"role_dimension_saved": 0,
"skill_dimension_saved": 0,
"skipped": 14
},
"planner_output": null,
"run_id": "200ba776-f813-4560-a97e-2e1cdf5da0ce"
}
LLM Calls
Every model call made for this run, in pipeline order. Click a card to see the model's response.
Loading…