Pipeline run
eba3651b-b31d-4619-a45a-afdc2e1373f0
Client output enrichment
v2 Skill cluster · Nature of work · AI index · Tech stack maturity · Evidence · KRA descriptionNature of work
no kras
Vague JD — no KRAs present to derive a specific nature of work.
Tech stack maturity
Mainstream Modern
AI index (0 = no AI use, 5 = totally AI-dependent · v2.1)
0.00 / 5
· Title match
· Has AI skill
· AI skill (primary)
· AI skill (secondary)
· On AI team
· Builds AI products
vocab breakdown (legacy)
Assistants (×1):
—
Frameworks (×2):
—
Models / concepts (×3):
—
Evidence — skills matched in JD (0)
Skill cluster (0 dimension groups, role-scoped)
Status:
completed
Created: 2026-05-08T10:36:46.513858Z
Updated: 2026-05-08T10:38:41.976871Z
API 3 duration: 906 ms
Flow
Current 3-step pipeline
1 POST /skills/extract-from-jd
2 POST /skills/extract-details
3 POST /skills/final-role-output
Role
Chosen role & resolution
Data Analyst
slug: data-analyst · id: 20 · source: db
The strongest dimension is reporting and dashboard development, which maps directly to Data Analyst and outweighs the smaller workflow-orchestration signal.
0
New skills
0
Skill↔dim saved
0
Role↔dim saved
13
Skipped
Job description
Business Analyst Job Description Job Title: Business Analyst Experience: 2–5 Years Location: Remote / Hybrid / On-site About the Role We are looking for a Business Analyst to bridge the gap between business needs and technical solutions. The ideal candidate will work closely with stakeholders, product teams, and developers to gather requirements, analyze business processes, and support successful project delivery. Key Responsibilities Gather, analyze, and document business requirements from stakeholders Translate business needs into functional specifications and user stories Work with cross-functional teams including developers, QA, and product managers Conduct requirement workshops, stakeholder meetings, and process analysis Create BRDs, FRDs, workflows, process diagrams, and reports Analyze data to identify trends, opportunities, and business insights Support UAT (User Acceptance Testing) and validate delivered solutions Monitor project progress and help manage risks and dependencies Improve existing business processes and recommend optimization strategies Ensure solutions align with business goals and operational needs Required Skills Strong understanding of business analysis methodologies Experience with requirement gathering and documentation Knowledge of Agile/Scrum methodologies Excellent communication and stakeholder management skills Strong analytical and problem-solving abilities Experience with tools like JIRA, Confluence, Excel, Visio, or Power BI Ability to create reports, dashboards, and process flows Understanding of SDLC and software development processes Preferred Qualifications Bachelor’s degree in Business, Computer Science, IT, or related field Experience working with technical and non-technical teams Familiarity with SQL, data analysis, or reporting tools is a plus Certification such as CBAP, CCBA, or Agile certification is preferred Nice to Have Experience in fintech, healthcare, e-commerce, or SaaS domains Exposure to BI tools like Tableau or Power BI Basic understanding of APIs and databases Benefits Competitive salary Flexible work environment Health insurance Learning and development opportunities Career growth and mentorship Paid leaves and company benefits
history_view bundle (older API). Showing raw API payloads below.
All API 3 persistence rows
Same grid as the skill-extractor “Persistence items” table: one row per (skill × dimension) work item.
| Skill | Tag | Dimension | Skill↔dim | Role↔dim | Outcome | Notes |
|---|---|---|---|---|---|---|
| Power BI | in_db |
Reporting and Dashboard Development
reporting-and-dashboard-development
|
— | — | — | TODO: REMOVE AFTER TESTING — api3_writes_enabled=False (writes disabled) |
| Tableau | in_db |
Reporting and Dashboard Development
reporting-and-dashboard-development
|
— | — | — | TODO: REMOVE AFTER TESTING — api3_writes_enabled=False (writes disabled) |
| Argo Workflows | in_db |
Workflow Orchestration Systems
workflow-orchestration-systems
|
— | — | — | TODO: REMOVE AFTER TESTING — api3_writes_enabled=False (writes disabled) |
| APIs | new |
API Design and Contracts
d_init_01
|
— | — | — | skill_not_in_db_v3_proposed |
| CBAP | new |
Business Analysis Certification
d_init_01
|
— | — | — | skill_not_in_db_v3_proposed |
| CCBA | new |
Business Analysis Certification
d_init_01
|
— | — | — | skill_not_in_db_v3_proposed |
| Excel | new |
Spreadsheet Analysis and Reporting
d_init_01
|
— | — | — | skill_not_in_db_v3_proposed |
| FRDs | new |
Functional Requirements Documents
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 Delivery Lifecycle
d_init_01
|
— | — | — | skill_not_in_db_v3_proposed |
| SaaS | new |
Software as a Service
d_init_01
|
— | — | — | skill_not_in_db_v3_proposed |
| UAT | new |
User Acceptance Testing
d_init_01
|
— | — | — | skill_not_in_db_v3_proposed |
| Visio | new |
Diagramming and Process Modeling
d_init_01
|
— | — | — | skill_not_in_db_v3_proposed |
Library artifacts (this run)
| Kind | Detail | DB id |
|---|---|---|
| canonical_skill_proposed | APIs | type=Protocol subtype=application_programming_interfaces nature=PROTOCOL lifespan=EVERGREEN | |
| canonical_skill_proposed | CBAP | type=Certification subtype=business_analysis_professional_certification nature=CREDENTIAL lifespan=EVERGREEN | |
| canonical_skill_proposed | CCBA | type=Certification subtype=business_analysis_certification nature=CREDENTIAL lifespan=EVERGREEN | |
| canonical_skill_proposed | Excel | type=Tool subtype=spreadsheet_software nature=TOOL lifespan=EVERGREEN | |
| canonical_skill_proposed | FRDs | type=Domain subtype=functional_requirements_documents nature=CONCEPT lifespan=EVERGREEN | |
| canonical_skill_proposed | Knowledge | type=Concept subtype=general_knowledge nature=CONCEPT lifespan=EVERGREEN | |
| canonical_skill_proposed | QA | type=Domain subtype=quality_assurance nature=CONCEPT lifespan=EVERGREEN | |
| canonical_skill_proposed | SDLC | type=Methodology subtype=software_development_lifecycle nature=METHODOLOGY lifespan=EVERGREEN | |
| canonical_skill_proposed | SaaS | type=Platform subtype=software_as_a_service_platform nature=PLATFORM lifespan=EVERGREEN | |
| canonical_skill_proposed | UAT | type=Methodology subtype=user_acceptance_testing nature=METHODOLOGY lifespan=EVERGREEN | |
| canonical_skill_proposed | Visio | type=Tool subtype=diagramming_tool nature=TOOL lifespan=EVERGREEN | |
| dimension_proposed | API Design and Contracts | |
| dimension_skill_link_proposed | APIs ↔ API Design and Contracts | |
| dimension_proposed | Business Analysis Certification | |
| dimension_skill_link_proposed | CBAP ↔ Business Analysis Certification | |
| dimension_proposed | Business Analysis Certification | |
| dimension_skill_link_proposed | CCBA ↔ Business Analysis Certification | |
| dimension_proposed | Spreadsheet Analysis and Reporting | |
| dimension_skill_link_proposed | Excel ↔ Spreadsheet Analysis and Reporting | |
| dimension_proposed | Functional Requirements Documents | |
| dimension_skill_link_proposed | FRDs ↔ Functional Requirements Documents | |
| dimension_proposed | Domain Knowledge and Business Context | |
| dimension_skill_link_proposed | Knowledge ↔ Domain Knowledge and Business Context | |
| dimension_proposed | Software Delivery Lifecycle | |
| dimension_skill_link_proposed | SDLC ↔ Software Delivery Lifecycle | |
| dimension_proposed | Software as a Service | |
| dimension_skill_link_proposed | SaaS ↔ Software as a Service | |
| dimension_proposed | User Acceptance Testing | |
| dimension_skill_link_proposed | UAT ↔ User Acceptance Testing | |
| dimension_proposed | Diagramming and Process Modeling | |
| dimension_skill_link_proposed | Visio ↔ Diagramming and Process Modeling |
API 1 — extract-from-jd click to toggle
{
"filtered_unknown_words": [
"2\u20135",
"APIs",
"Ability",
"Acceptance",
"Analyst",
"BI",
"BRDs",
"Bachelor",
"Benefits",
"Business",
"CBAP",
"CCBA",
"Career",
"Certification",
"Computer",
"Conduct",
"Description",
"Ensure",
"Excel",
"Experience",
"Exposure",
"FRDs",
"Familiarity",
"Gather",
"Health",
"Hybrid",
"Job",
"Key",
"Knowledge",
"Learning",
"Location",
"Monitor",
"Power",
"Preferred",
"QA",
"Qualifications",
"Remote",
"Required",
"Responsibilities",
"Role",
"SDLC",
"SaaS",
"Science",
"Skills",
"Support",
"Testing",
"Title",
"UAT",
"Understanding",
"User",
"Visio",
"Years",
"abilities",
"analysis",
"benefits",
"business",
"candidate",
"certification",
"commerce",
"communication",
"company",
"data",
"databases",
"degree",
"delivery",
"dependencies",
"developers",
"development",
"diagrams",
"document",
"documentation",
"domains",
"environment",
"field",
"fintech",
"gap",
"gathering",
"goals",
"growth",
"healthcare",
"insights",
"insurance",
"leaves",
"management",
"managers",
"meetings",
"methodologies",
"needs",
"opportunities",
"optimization",
"problem",
"process",
"processes",
"product",
"progress",
"project",
"reporting",
"requirement",
"requirements",
"risks",
"salary",
"site",
"skills",
"software",
"solutions",
"specifications",
"stakeholder",
"stakeholders",
"stories",
"strategies",
"teams",
"tools",
"trends",
"understanding",
"user",
"work",
"workshops"
],
"final_non_skills": [
"2\u20135",
"Ability",
"Acceptance",
"Analyst",
"BI",
"BRDs",
"Bachelor",
"Benefits",
"Business",
"Certification",
"Computer",
"Conduct",
"Description",
"Ensure",
"Experience",
"Exposure",
"Familiarity",
"Gather",
"Health",
"Hybrid",
"Job",
"Key",
"Learning",
"Location",
"Monitor",
"Power",
"Preferred",
"Qualifications",
"Remote",
"Required",
"Responsibilities",
"Role",
"Science",
"Skills",
"Support",
"Testing",
"Title",
"Understanding",
"User",
"Years",
"abilities",
"analysis",
"candidate",
"commerce",
"communication",
"company",
"data",
"databases",
"degree",
"delivery",
"dependencies",
"developers",
"development",
"diagrams",
"document",
"documentation",
"domains",
"environment",
"field",
"fintech",
"gap",
"gathering",
"goals",
"growth",
"healthcare",
"insights",
"insurance",
"leaves",
"management",
"managers",
"meetings",
"methodologies",
"needs",
"opportunities",
"optimization",
"problem",
"process",
"processes",
"product",
"progress",
"project",
"reporting",
"requirement",
"requirements",
"risks",
"salary",
"site",
"software",
"solutions",
"specifications",
"stakeholder",
"stakeholders",
"stories",
"strategies",
"teams",
"tools",
"trends",
"work",
"workshops"
],
"final_skills": [
"Power BI",
"Tableau",
"Argo Workflows",
"APIs",
"CBAP",
"CCBA",
"Excel",
"FRDs",
"Knowledge",
"QA",
"SDLC",
"SaaS",
"UAT",
"Visio"
],
"initial_skills": [
"Power BI",
"Tableau",
"Argo Workflows"
],
"jd_role_hint": {
"display_name": "Business Analyst",
"rationale": "The excerpt centers on gathering and documenting requirements, translating needs into specifications, and working with stakeholders and developers.",
"role_archetype": "Requirements-focused analyst who bridges business and technical teams, documents processes, and supports delivery/testing.",
"slug": "business-analyst"
},
"llm_non_skills": [
"2\u20135",
"Ability",
"Acceptance",
"Analyst",
"BI",
"BRDs",
"Bachelor",
"Benefits",
"Business",
"Certification",
"Computer",
"Conduct",
"Description",
"Ensure",
"Experience",
"Exposure",
"Familiarity",
"Gather",
"Health",
"Hybrid",
"Job",
"Key",
"Learning",
"Location",
"Monitor",
"Power",
"Preferred",
"Qualifications",
"Remote",
"Required",
"Responsibilities",
"Role",
"Science",
"Skills",
"Support",
"Testing",
"Title",
"Understanding",
"User",
"Years",
"abilities",
"analysis",
"candidate",
"commerce",
"communication",
"company",
"data",
"databases",
"degree",
"delivery",
"dependencies",
"developers",
"development",
"diagrams",
"document",
"documentation",
"domains",
"environment",
"field",
"fintech",
"gap",
"gathering",
"goals",
"growth",
"healthcare",
"insights",
"insurance",
"leaves",
"management",
"managers",
"meetings",
"methodologies",
"needs",
"opportunities",
"optimization",
"problem",
"process",
"processes",
"product",
"progress",
"project",
"reporting",
"requirement",
"requirements",
"risks",
"salary",
"site",
"software",
"solutions",
"specifications",
"stakeholder",
"stakeholders",
"stories",
"strategies",
"teams",
"tools",
"trends",
"work",
"workshops"
],
"llm_skills": [
"APIs",
"CBAP",
"CCBA",
"Excel",
"FRDs",
"Knowledge",
"QA",
"SDLC",
"SaaS",
"UAT",
"Visio"
],
"run_id": null,
"unknown_words": [
"2\u20135",
"APIs",
"Ability",
"Acceptance",
"Analyst",
"BI",
"BRDs",
"Bachelor",
"Benefits",
"Business",
"CBAP",
"CCBA",
"Career",
"Certification",
"Computer",
"Conduct",
"Description",
"Ensure",
"Excel",
"Experience",
"Exposure",
"FRDs",
"Familiarity",
"Gather",
"Health",
"Hybrid",
"Job",
"Key",
"Knowledge",
"Learning",
"Location",
"Monitor",
"Power",
"Preferred",
"QA",
"Qualifications",
"Remote",
"Required",
"Responsibilities",
"Role",
"SDLC",
"SaaS",
"Science",
"Skills",
"Support",
"Testing",
"Title",
"UAT",
"Understanding",
"User",
"Visio",
"Years",
"abilities",
"analysis",
"benefits",
"business",
"candidate",
"certification",
"commerce",
"communication",
"company",
"data",
"databases",
"degree",
"delivery",
"dependencies",
"developers",
"development",
"diagrams",
"document",
"documentation",
"domains",
"environment",
"field",
"fintech",
"gap",
"gathering",
"goals",
"growth",
"healthcare",
"insights",
"insurance",
"leaves",
"management",
"managers",
"meetings",
"methodologies",
"needs",
"opportunities",
"optimization",
"problem",
"process",
"processes",
"product",
"progress",
"project",
"reporting",
"requirement",
"requirements",
"risks",
"salary",
"site",
"skills",
"software",
"solutions",
"specifications",
"stakeholder",
"stakeholders",
"stories",
"strategies",
"teams",
"tools",
"trends",
"understanding",
"user",
"work",
"workshops"
]
}
API 2 — extract-details
{
"alias_matches": [],
"candidate_roles": [
{
"display_name": "Data Analyst",
"id": 20,
"rationale": null,
"role_archetype": null,
"slug": "data-analyst",
"source": "db"
},
{
"display_name": "Data Engineer",
"id": 6,
"rationale": null,
"role_archetype": null,
"slug": "data-engineer",
"source": "db"
},
{
"display_name": "MLOps Engineer",
"id": 5,
"rationale": null,
"role_archetype": null,
"slug": "mlops-engineer",
"source": "db"
}
],
"chosen_role": {
"display_name": "Data Analyst",
"id": 20,
"rationale": "The strongest dimension is reporting and dashboard development, which maps directly to Data Analyst and outweighs the smaller workflow-orchestration signal.",
"role_archetype": null,
"slug": "data-analyst",
"source": "db"
},
"dimensions": [
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Reporting and Dashboard Development",
"id": 295,
"rationale": "Building recurring reports and dashboards that track performance over time and across segments. This is a distinct cluster because the analyst must package metrics into reusable views for stakeholders.",
"slug": "reporting-and-dashboard-development",
"source": "db"
},
"input_skill": "Power BI",
"llm_role": null,
"roles_from_db": [
{
"display_name": "Data Analyst",
"id": 20,
"rationale": null,
"role_archetype": null,
"slug": "data-analyst",
"source": "db"
}
]
},
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Reporting and Dashboard Development",
"id": 295,
"rationale": "Building recurring reports and dashboards that track performance over time and across segments. This is a distinct cluster because the analyst must package metrics into reusable views for stakeholders.",
"slug": "reporting-and-dashboard-development",
"source": "db"
},
"input_skill": "Tableau",
"llm_role": null,
"roles_from_db": [
{
"display_name": "Data Analyst",
"id": 20,
"rationale": null,
"role_archetype": null,
"slug": "data-analyst",
"source": "db"
}
]
},
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Workflow Orchestration Systems",
"id": 64,
"rationale": "Operational orchestration of ML jobs, dependencies, and handoffs across training, validation, deployment, and retraining. This is a useful split from training pipelines because it emphasizes the scheduler and control plane.",
"slug": "workflow-orchestration-systems",
"source": "db"
},
"input_skill": "Argo Workflows",
"llm_role": null,
"roles_from_db": [
{
"display_name": "Data Engineer",
"id": 6,
"rationale": null,
"role_archetype": null,
"slug": "data-engineer",
"source": "db"
},
{
"display_name": "MLOps Engineer",
"id": 5,
"rationale": null,
"role_archetype": null,
"slug": "mlops-engineer",
"source": "db"
}
]
},
{
"dimension": {
"difficulty_hint": null,
"display_name": "API Design and Contracts",
"id": null,
"rationale": "Covers the structure, semantics, and lifecycle of application programming interfaces, including how consumers understand and use them. APIs belong here when the focus is on defining stable, clear, and evolvable interfaces.",
"slug": "d_init_01",
"source": "llm"
},
"input_skill": "APIs",
"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 body of knowledge and related competency areas. This fits CBAP because it is itself a business analysis certification rather than a technical tool or platform skill.",
"slug": "d_init_01",
"source": "llm"
},
"input_skill": "CBAP",
"llm_role": null,
"roles_from_db": []
},
{
"dimension": {
"difficulty_hint": null,
"display_name": "Business Analysis Certification",
"id": null,
"rationale": "Formal business analysis credentialing and professional standards for analysts. CCBA belongs here because it is a recognized certification focused on business analysis knowledge, practices, and competency validation.",
"slug": "d_init_01",
"source": "llm"
},
"input_skill": "CCBA",
"llm_role": null,
"roles_from_db": []
},
{
"dimension": {
"difficulty_hint": null,
"display_name": "Spreadsheet Analysis and Reporting",
"id": null,
"rationale": "Using Excel to organize, analyze, and present business data in spreadsheet form. This fits a Business Analyst because Excel is commonly used for ad hoc analysis, reporting, and lightweight modeling.",
"slug": "d_init_01",
"source": "llm"
},
"input_skill": "Excel",
"llm_role": null,
"roles_from_db": []
},
{
"dimension": {
"difficulty_hint": null,
"display_name": "Functional Requirements Documents",
"id": null,
"rationale": "Covers writing, reviewing, and maintaining FRDs that translate business needs into clear functional scope, rules, and acceptance criteria. This fits a Business Analyst role because FRDs are a core artifact for defining what a solution must do before delivery begins.",
"slug": "d_init_01",
"source": "llm"
},
"input_skill": "FRDs",
"llm_role": null,
"roles_from_db": []
},
{
"dimension": {
"difficulty_hint": null,
"display_name": "Domain Knowledge and Business Context",
"id": null,
"rationale": "Covers understanding the business domain, processes, terminology, and rules needed to analyze requirements and make sound decisions. For a Business Analyst, this skill is the broad knowledge base that lets them interpret stakeholder needs and translate them into workable solutions.",
"slug": "d_init_01",
"source": "llm"
},
"input_skill": "Knowledge",
"llm_role": null,
"roles_from_db": []
},
{
"dimension": {
"difficulty_hint": null,
"display_name": "Software Delivery Lifecycle",
"id": null,
"rationale": "Covers the end-to-end process used to plan, build, test, release, and maintain software products. SDLC belongs here because it refers to the overall lifecycle framework rather than a single technical practice.",
"slug": "d_init_01",
"source": "llm"
},
"input_skill": "SDLC",
"llm_role": null,
"roles_from_db": []
},
{
"dimension": {
"difficulty_hint": null,
"display_name": "Software as a Service",
"id": null,
"rationale": "Covers the product and delivery model where software is hosted centrally and consumed over the internet by subscription or usage-based access. This fits SaaS because the skill refers to the service model itself, not a specific technical implementation area.",
"slug": "d_init_01",
"source": "llm"
},
"input_skill": "SaaS",
"llm_role": null,
"roles_from_db": []
},
{
"dimension": {
"difficulty_hint": null,
"display_name": "User Acceptance Testing",
"id": null,
"rationale": "Validation of a feature or change by business users against agreed acceptance criteria before release. UAT belongs here because it is a manual, requirement-driven test phase focused on confirming the solution meets user and business needs.",
"slug": "d_init_01",
"source": "llm"
},
"input_skill": "UAT",
"llm_role": null,
"roles_from_db": []
},
{
"dimension": {
"difficulty_hint": null,
"display_name": "Diagramming and Process Modeling",
"id": null,
"rationale": "Covers creating business and technical diagrams to communicate workflows, systems, and relationships. Visio belongs here because it is commonly used by business analysts to document processes, swimlanes, org charts, and system maps.",
"slug": "d_init_01",
"source": "llm"
},
"input_skill": "Visio",
"llm_role": null,
"roles_from_db": []
}
],
"input_final_skills": [
"Power BI",
"Tableau",
"Argo Workflows",
"APIs",
"CBAP",
"CCBA",
"Excel",
"FRDs",
"Knowledge",
"QA",
"SDLC",
"SaaS",
"UAT",
"Visio"
],
"input_llm_skills": [
"APIs",
"CBAP",
"CCBA",
"Excel",
"FRDs",
"Knowledge",
"QA",
"SDLC",
"SaaS",
"UAT",
"Visio"
],
"new_aliases_persisted": 0,
"run_id": "eba3651b-b31d-4619-a45a-afdc2e1373f0",
"skills_detail": [
{
"aliases_in_db": [
{
"alias_text": "Power BI",
"alias_type": "CANONICAL",
"id": 2535,
"is_primary": true,
"match_strategy": "CASE_INSENSITIVE"
}
],
"canonical": {
"category_id": 11,
"display_name": "Power BI",
"id": 1884,
"is_also_category": false,
"is_extractable": true,
"skill_nature": "TOOL",
"slug": "power-bi",
"sub_category_id": 1618,
"typical_lifespan": "EVERGREEN",
"volatility": "STABLE"
},
"dimensions": [
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Reporting and Dashboard Development",
"id": 295,
"rationale": "Building recurring reports and dashboards that track performance over time and across segments. This is a distinct cluster because the analyst must package metrics into reusable views for stakeholders.",
"slug": "reporting-and-dashboard-development",
"source": "db"
},
"input_skill": "Power BI",
"llm_role": null,
"roles_from_db": [
{
"display_name": "Data Analyst",
"id": 20,
"rationale": null,
"role_archetype": null,
"slug": "data-analyst",
"source": "db"
}
]
}
],
"input_skill": "Power BI",
"matched_via": "alias",
"new_alias_persisted": false,
"new_alias_text": null,
"new_skill_meta": null,
"source_tag": "db",
"was_in_llm_skills": false
},
{
"aliases_in_db": [
{
"alias_text": "Tableau",
"alias_type": "CANONICAL",
"id": 2534,
"is_primary": true,
"match_strategy": "CASE_INSENSITIVE"
}
],
"canonical": {
"category_id": 11,
"display_name": "Tableau",
"id": 1883,
"is_also_category": false,
"is_extractable": true,
"skill_nature": "TOOL",
"slug": "tableau",
"sub_category_id": 1618,
"typical_lifespan": "EVERGREEN",
"volatility": "STABLE"
},
"dimensions": [
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Reporting and Dashboard Development",
"id": 295,
"rationale": "Building recurring reports and dashboards that track performance over time and across segments. This is a distinct cluster because the analyst must package metrics into reusable views for stakeholders.",
"slug": "reporting-and-dashboard-development",
"source": "db"
},
"input_skill": "Tableau",
"llm_role": null,
"roles_from_db": [
{
"display_name": "Data Analyst",
"id": 20,
"rationale": null,
"role_archetype": null,
"slug": "data-analyst",
"source": "db"
}
]
}
],
"input_skill": "Tableau",
"matched_via": "alias",
"new_alias_persisted": false,
"new_alias_text": null,
"new_skill_meta": null,
"source_tag": "db",
"was_in_llm_skills": false
},
{
"aliases_in_db": [
{
"alias_text": "Argo Workflows",
"alias_type": "CANONICAL",
"id": 595,
"is_primary": true,
"match_strategy": "CASE_INSENSITIVE"
}
],
"canonical": {
"category_id": 11,
"display_name": "Argo Workflows",
"id": 380,
"is_also_category": false,
"is_extractable": true,
"skill_nature": "TOOL",
"slug": "argo-workflows",
"sub_category_id": 335,
"typical_lifespan": "EVERGREEN",
"volatility": "EMERGING"
},
"dimensions": [
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Workflow Orchestration Systems",
"id": 64,
"rationale": "Operational orchestration of ML jobs, dependencies, and handoffs across training, validation, deployment, and retraining. This is a useful split from training pipelines because it emphasizes the scheduler and control plane.",
"slug": "workflow-orchestration-systems",
"source": "db"
},
"input_skill": "Argo Workflows",
"llm_role": null,
"roles_from_db": [
{
"display_name": "Data Engineer",
"id": 6,
"rationale": null,
"role_archetype": null,
"slug": "data-engineer",
"source": "db"
},
{
"display_name": "MLOps Engineer",
"id": 5,
"rationale": null,
"role_archetype": null,
"slug": "mlops-engineer",
"source": "db"
}
]
}
],
"input_skill": "Argo Workflows",
"matched_via": "alias",
"new_alias_persisted": false,
"new_alias_text": null,
"new_skill_meta": null,
"source_tag": "db",
"was_in_llm_skills": false
},
{
"aliases_in_db": [],
"canonical": null,
"dimensions": [
{
"dimension": {
"difficulty_hint": null,
"display_name": "API Design and Contracts",
"id": null,
"rationale": "Covers the structure, semantics, and lifecycle of application programming interfaces, including how consumers understand and use them. APIs belong here when the focus is on defining stable, clear, and evolvable interfaces.",
"slug": "d_init_01",
"source": "llm"
},
"input_skill": "APIs",
"llm_role": null,
"roles_from_db": []
}
],
"input_skill": "APIs",
"matched_via": null,
"new_alias_persisted": false,
"new_alias_text": null,
"new_skill_meta": {
"derived": {
"category": "Protocol",
"skill_nature": "PROTOCOL",
"sub_category": "application_programming_interfaces",
"typical_lifespan": "EVERGREEN",
"version_strategy": "NOT_APPLICABLE",
"volatility": "STABLE"
},
"enrichment": {
"ambiguity": {
"ambiguity_flag": false,
"confused_with": [],
"reasoning": "APIs is a standard, well-scoped term in JDs and usually refers to application programming interfaces; it is not typically confused with a different catalog skill."
},
"context_keywords": {
"context_keywords": [
"REST",
"GraphQL",
"OpenAPI",
"Swagger",
"JSON",
"XML",
"OAuth 2.0",
"API gateway",
"endpoint",
"webhooks",
"rate limiting",
"versioning",
"SDK",
"microservices",
"HTTP"
]
},
"maturity": {
"confidence": 0.98,
"maturity": "well_known",
"reasoning": "APIs are a hiring-pipeline staple across backend, mobile, and platform JDs; REST/GraphQL/API design appears in large-volume job postings and vendor docs from AWS, Google, and Microsoft."
},
"skill_id": "apis",
"vendor_license": {
"confidence": 0.99,
"license": null,
"vendor": null,
"year_introduced": null
},
"versioning": {
"current_version": null,
"version_aliases": {},
"versioned": false
}
},
"keep_log": [],
"locked_dimensions": [
{
"description": "Covers the structure, semantics, and lifecycle of application programming interfaces, including how consumers understand and use them. APIs belong here when the focus is on defining stable, clear, and evolvable interfaces.",
"exemplar_skills": [
"APIs",
"API design",
"REST APIs",
"request/response schemas",
"API contracts",
"versioning",
"idempotency"
],
"in_scope": "APIs, REST resource design, request and response schemas, contract definitions, pagination, filtering, error models, versioning, idempotency",
"name": "API Design and Contracts",
"out_of_scope": "Automated API testing, backend service orchestration, authentication session state, network protocol debugging, UI integration details",
"overlap_flags": [
{
"reason": "API design is often part of service integration work, but this dimension centers on the interface contract itself.",
"with_dim_id": "service-architecture-and-integration",
"with_dim_name": null,
"with_role": null
},
{
"reason": "Well-designed APIs are frequently tested, but this dimension excludes the automation and validation layer.",
"with_dim_id": "api-and-service-test-automation",
"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": [
"rest-apis",
"scripted-rest-api",
"outbound-rest-messages"
],
"parent_skills": [],
"related_to": [
"grpc",
"private-endpoints",
"acls",
"mock-servers"
],
"requires": [
"http",
"json",
"oauth-2-0"
],
"skill_id": "apis",
"suppress_on_match": []
},
"skill_id": "apis",
"split_log": [],
"typed": {
"alternatives_considered": [],
"confidence": 0.93,
"name": "APIs",
"reasoning": "APIs are a communication interface standard between software systems, so by the Protocol rule they fit best as a protocol-like interface rather than a tool or platform.",
"skill_id": "apis",
"subtype": "application_programming_interfaces",
"type": "Protocol"
},
"warnings": []
},
"source_tag": "llm",
"was_in_llm_skills": true
},
{
"aliases_in_db": [],
"canonical": null,
"dimensions": [
{
"dimension": {
"difficulty_hint": null,
"display_name": "Business Analysis Certification",
"id": null,
"rationale": "Professional certification knowledge for business analysts, including the CBAP body of knowledge and related competency areas. This fits CBAP because it is itself a business analysis certification rather than a technical tool or platform skill.",
"slug": "d_init_01",
"source": "llm"
},
"input_skill": "CBAP",
"llm_role": null,
"roles_from_db": []
}
],
"input_skill": "CBAP",
"matched_via": null,
"new_alias_persisted": false,
"new_alias_text": null,
"new_skill_meta": {
"derived": {
"category": "Certification",
"skill_nature": "CREDENTIAL",
"sub_category": "business_analysis_professional_certification",
"typical_lifespan": "EVERGREEN",
"version_strategy": "NOT_APPLICABLE",
"volatility": "STABLE"
},
"enrichment": {
"ambiguity": {
"ambiguity_flag": false,
"confused_with": [],
"reasoning": "CBAP is a specific certification acronym (Certified Business Analysis Professional) and is unlikely to be reasonably confused with another catalog skill in typical job descriptions."
},
"context_keywords": {
"context_keywords": [
"BABOK",
"IIBA",
"requirements elicitation",
"stakeholder analysis",
"process modeling",
"use cases",
"user stories",
"gap analysis",
"traceability matrix",
"business process improvement",
"functional requirements",
"UML",
"workshops",
"facilitation",
"SWOT analysis"
]
},
"maturity": {
"confidence": 0.84,
"maturity": "well_known",
"reasoning": "CBAP is a widely recognized business analysis certification and appears frequently in job descriptions for senior BA roles, especially in enterprise and consulting hiring pipelines."
},
"skill_id": "cbap",
"vendor_license": {
"confidence": 0.97,
"license": null,
"vendor": "International Institute of Business Analysis",
"year_introduced": 2006
},
"versioning": {
"current_version": null,
"version_aliases": {},
"versioned": false
}
},
"keep_log": [],
"locked_dimensions": [
{
"description": "Professional certification knowledge for business analysts, including the CBAP body of knowledge and related competency areas. This fits CBAP because it is itself a business analysis certification rather than a technical tool or platform skill.",
"exemplar_skills": [
"CBAP",
"BABOK",
"business analysis certification",
"requirements elicitation",
"stakeholder analysis",
"business process analysis"
],
"in_scope": "CBAP, business analysis certification prep, BABOK knowledge areas, requirements elicitation, stakeholder analysis, solution assessment, business process analysis",
"name": "Business Analysis Certification",
"out_of_scope": "project management certification, product management strategy, software testing execution, data analysis tooling, enterprise architecture design",
"overlap_flags": [
{
"reason": "Business analysts may support acceptance criteria and validation, but CBAP is broader than test design and execution.",
"with_dim_id": "test-case-design-and-execution",
"with_dim_name": null,
"with_role": "Manual Tester"
}
],
"tentative_id": "d_init_01"
}
],
"merge_log": [],
"placed": {
"name": "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": [
"acceptance-criteria-validation",
"acceptance-criteria-checks",
"risk-based-testing",
"capacity-planning",
"session-based-testing"
],
"requires": [],
"skill_id": "cbap",
"suppress_on_match": []
},
"skill_id": "cbap",
"split_log": [],
"typed": {
"alternatives_considered": [],
"confidence": 0.98,
"name": "CBAP",
"reasoning": "CBAP is a formal third-party credential, so by the Certification rule it is not a concept or methodology.",
"skill_id": "cbap",
"subtype": "business_analysis_professional_certification",
"type": "Certification"
},
"warnings": []
},
"source_tag": "llm",
"was_in_llm_skills": true
},
{
"aliases_in_db": [],
"canonical": null,
"dimensions": [
{
"dimension": {
"difficulty_hint": null,
"display_name": "Business Analysis Certification",
"id": null,
"rationale": "Formal business analysis credentialing and professional standards for analysts. CCBA belongs here because it is a recognized certification focused on business analysis knowledge, practices, and competency validation.",
"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": false,
"confused_with": [],
"reasoning": "CCBA is a specific business analysis certification acronym and is usually clear in job descriptions; it is unlikely to be confused with another catalog skill in typical JD context."
},
"context_keywords": {
"context_keywords": [
"BABOK",
"IIBA",
"requirements elicitation",
"stakeholder analysis",
"process modeling",
"use cases",
"user stories",
"gap analysis",
"business process improvement",
"solution assessment",
"traceability matrix",
"SWOT analysis",
"UML",
"workshops",
"acceptance criteria"
]
},
"maturity": {
"confidence": 0.84,
"maturity": "well_known",
"reasoning": "CCBA is a widely recognized business analysis certification and appears regularly in job descriptions for BA/PM roles, alongside IIBA/CBAP requirements."
},
"skill_id": "ccba",
"vendor_license": {
"confidence": 0.92,
"license": null,
"vendor": "International Institute of Business Analysis",
"year_introduced": 2008
},
"versioning": {
"current_version": null,
"version_aliases": {},
"versioned": false
}
},
"keep_log": [],
"locked_dimensions": [
{
"description": "Formal business analysis credentialing and professional standards for analysts. CCBA belongs here because it is a recognized certification focused on business analysis knowledge, practices, and competency validation.",
"exemplar_skills": [
"CCBA",
"CBAP",
"ECBA",
"IIBA certification",
"business analysis certification"
],
"in_scope": "CCBA, business analysis certification, IIBA certification, CBAP, ECBA, business analysis body of knowledge, requirements elicitation, stakeholder analysis, solution assessment, business process analysis",
"name": "Business Analysis Certification",
"out_of_scope": "Requirements gathering as a day-to-day project activity, process modeling techniques, product management methods, project management certifications, platform-specific implementation skills",
"overlap_flags": [
{
"reason": "Business analysts may work on service boundaries and integrations, but this dimension is about the certification itself rather than architecture design.",
"with_dim_id": "service-architecture-and-integration",
"with_dim_name": null,
"with_role": null
}
],
"tentative_id": "d_init_01"
}
],
"merge_log": [],
"placed": {
"name": "CCBA",
"placement_confidence": 0.92,
"primary_dimension": "d_init_01",
"reasoning": "Deterministic JD placement: locked_dimensions has 1 dimension(s) from skill-driven dimension generation after reconciliation; primary_dimension is the first locked dim.",
"secondary_dimensions": [],
"skill_id": "ccba"
},
"relationships": {
"child_skills": [],
"parent_skills": [],
"related_to": [
"scorecards",
"acceptance-criteria-checks",
"acceptance-criteria-validation",
"risk-based-testing",
"charter-based-testing",
"session-based-testing"
],
"requires": [],
"skill_id": "ccba",
"suppress_on_match": []
},
"skill_id": "ccba",
"split_log": [],
"typed": {
"alternatives_considered": [],
"confidence": 0.98,
"name": "CCBA",
"reasoning": "CCBA is a formal third-party credential, so by the Certification rule it is a Certification rather than a concept or methodology.",
"skill_id": "ccba",
"subtype": "business_analysis_certification",
"type": "Certification"
},
"warnings": []
},
"source_tag": "llm",
"was_in_llm_skills": true
},
{
"aliases_in_db": [],
"canonical": null,
"dimensions": [
{
"dimension": {
"difficulty_hint": null,
"display_name": "Spreadsheet Analysis and Reporting",
"id": null,
"rationale": "Using Excel to organize, analyze, and present business data in spreadsheet form. This fits a Business Analyst because Excel is commonly used for ad hoc analysis, reporting, and lightweight modeling.",
"slug": "d_init_01",
"source": "llm"
},
"input_skill": "Excel",
"llm_role": null,
"roles_from_db": []
}
],
"input_skill": "Excel",
"matched_via": null,
"new_alias_persisted": false,
"new_alias_text": null,
"new_skill_meta": {
"derived": {
"category": "Tool",
"skill_nature": "TOOL",
"sub_category": "spreadsheet_software",
"typical_lifespan": "EVERGREEN",
"version_strategy": "SEPARATE_ENTITY",
"volatility": "STABLE"
},
"enrichment": {
"ambiguity": {
"ambiguity_flag": false,
"confused_with": [],
"reasoning": "\"Excel\" in JDs almost always refers to Microsoft Excel spreadsheet software; the name is specific enough that a reasonable extractor would not confuse it 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 development and it remains a default spreadsheet tool in hiring pipelines."
},
"skill_id": "excel",
"vendor_license": {
"confidence": 0.99,
"license": "proprietary",
"vendor": "Microsoft",
"year_introduced": 1985
},
"versioning": {
"current_version": "Microsoft 365 / Excel 2024",
"version_aliases": {
"Excel 2007": "Excel 2007",
"Excel 2010": "Excel 2010",
"Excel 2013": "Excel 2013",
"Excel 2016": "Excel 2016",
"Excel 2019": "Excel 2019",
"Excel 2021": "Excel 2021",
"Excel 2024": "Microsoft 365 / Excel 2024",
"Excel 365": "Microsoft 365 / Excel 2024",
"Microsoft 365 Excel": "Microsoft 365 / Excel 2024"
},
"versioned": true
}
},
"keep_log": [],
"locked_dimensions": [
{
"description": "Using Excel to organize, analyze, and present business data in spreadsheet form. This fits a Business Analyst because Excel is commonly used for ad hoc analysis, reporting, and lightweight modeling.",
"exemplar_skills": [
"Excel",
"Pivot Tables",
"VLOOKUP",
"XLOOKUP",
"Conditional Formatting",
"Excel Charts",
"Data Validation"
],
"in_scope": "Excel, formulas and functions, pivot tables, charts and dashboards, filters and sorting, conditional formatting, data validation, lookup functions, what-if analysis, basic reporting templates",
"name": "Spreadsheet Analysis and Reporting",
"out_of_scope": "SQL querying and database modeling, statistical programming in Python or R, enterprise BI platform development, spreadsheet macro engineering and VBA automation",
"overlap_flags": [
{
"reason": "Excel is often used to combine and reshape source data, but that dimension owns the broader transformation and blending workflow.",
"with_dim_id": "data-preparation-and-blending",
"with_dim_name": null,
"with_role": null
},
{
"reason": "Excel can support analysis workflows, but notebooks own scripted, reproducible analytical work.",
"with_dim_id": "notebook-and-reproducible-analysis-workflow",
"with_dim_name": null,
"with_role": null
}
],
"tentative_id": "d_init_01"
}
],
"merge_log": [],
"placed": {
"name": "Excel",
"placement_confidence": 0.92,
"primary_dimension": "d_init_01",
"reasoning": "Deterministic JD placement: locked_dimensions has 1 dimension(s) from skill-driven dimension generation after reconciliation; primary_dimension is the first locked dim.",
"secondary_dimensions": [],
"skill_id": "excel"
},
"relationships": {
"child_skills": [],
"parent_skills": [],
"related_to": [
"python",
"javascript",
"sqlite",
"powershell",
"r",
"bash",
"dashboards",
"summary-statistics",
"scorecards"
],
"requires": [],
"skill_id": "excel",
"suppress_on_match": []
},
"skill_id": "excel",
"split_log": [],
"typed": {
"alternatives_considered": [],
"confidence": 0.98,
"name": "Excel",
"reasoning": "Excel is software you operate directly as a user rather than a hosted multi-tenant environment, so by the Tool vs Platform rule it is a Tool.",
"skill_id": "excel",
"subtype": "spreadsheet_software",
"type": "Tool"
},
"warnings": []
},
"source_tag": "llm",
"was_in_llm_skills": true
},
{
"aliases_in_db": [],
"canonical": null,
"dimensions": [
{
"dimension": {
"difficulty_hint": null,
"display_name": "Functional Requirements Documents",
"id": null,
"rationale": "Covers writing, reviewing, and maintaining FRDs that translate business needs into clear functional scope, rules, and acceptance criteria. This fits a Business Analyst role because FRDs are a core artifact for defining what a solution must do before delivery begins.",
"slug": "d_init_01",
"source": "llm"
},
"input_skill": "FRDs",
"llm_role": null,
"roles_from_db": []
}
],
"input_skill": "FRDs",
"matched_via": null,
"new_alias_persisted": false,
"new_alias_text": null,
"new_skill_meta": {
"derived": {
"category": "Domain",
"skill_nature": "CONCEPT",
"sub_category": "functional_requirements_documents",
"typical_lifespan": "EVERGREEN",
"version_strategy": "NOT_APPLICABLE",
"volatility": "STABLE"
},
"enrichment": {
"ambiguity": {
"ambiguity_flag": false,
"confused_with": [],
"reasoning": "FRDs is a fairly specific plural abbreviation for Functional Requirements Documents; in JDs it is unlikely to be mistaken for another catalog skill."
},
"context_keywords": {
"context_keywords": [
"BRD",
"PRD",
"use cases",
"user stories",
"acceptance criteria",
"functional specification",
"requirements traceability",
"stakeholder interviews",
"process flows",
"wireframes",
"UAT",
"scope definition",
"business rules",
"gap analysis",
"sign-off"
]
},
"maturity": {
"confidence": 0.78,
"maturity": "well_known",
"reasoning": "Functional requirements documents are a standard artifact in many product and systems roles; JD searches commonly mention writing/owning FRDs alongside PRDs and BRDs, indicating broad hiring-pipeline use."
},
"skill_id": "frds",
"vendor_license": {
"confidence": 0.98,
"license": null,
"vendor": null,
"year_introduced": null
},
"versioning": {
"current_version": null,
"version_aliases": {},
"versioned": false
}
},
"keep_log": [],
"locked_dimensions": [
{
"description": "Covers writing, reviewing, and maintaining FRDs that translate business needs into clear functional scope, rules, and acceptance criteria. This fits a Business Analyst role because FRDs are a core artifact for defining what a solution must do before delivery begins.",
"exemplar_skills": [
"FRDs",
"functional requirements documentation",
"requirements elicitation",
"business requirements analysis",
"acceptance criteria definition",
"use case writing"
],
"in_scope": "FRDs, functional requirements documents, business requirements translation, scope definition, use cases, user stories, acceptance criteria, process rules, requirement traceability",
"name": "Functional Requirements Documents",
"out_of_scope": "Technical design specifications, solution architecture, API implementation details, test execution, and project scheduling, which belong to engineering, architecture, QA, or delivery planning dimensions.",
"overlap_flags": [
{
"reason": "FRDs often feed test design, but this dimension owns the requirement artifact itself rather than test authoring.",
"with_dim_id": "test-case-design-and-execution",
"with_dim_name": null,
"with_role": "Manual Tester"
},
{
"reason": "FRDs may mention integrations, but detailed service decomposition and interface design belong to architecture.",
"with_dim_id": "service-architecture-and-integration",
"with_dim_name": null,
"with_role": null
}
],
"tentative_id": "d_init_01"
}
],
"merge_log": [],
"placed": {
"name": "FRDs",
"placement_confidence": 0.92,
"primary_dimension": "d_init_01",
"reasoning": "Deterministic JD placement: locked_dimensions has 1 dimension(s) from skill-driven dimension generation after reconciliation; primary_dimension is the first locked dim.",
"secondary_dimensions": [],
"skill_id": "frds"
},
"relationships": {
"child_skills": [],
"parent_skills": [],
"related_to": [
"change-requests",
"contract-tests",
"risk-based-testing",
"runbooks",
"rollback-readiness"
],
"requires": [],
"skill_id": "frds",
"suppress_on_match": []
},
"skill_id": "frds",
"split_log": [],
"typed": {
"alternatives_considered": [
"Concept: ruled out \u2014 this is more of an artifact/document category than a standalone knowledge unit.",
"Standard: ruled out \u2014 FRDs are not an industry-defined specification.",
"Methodology: ruled out \u2014 it describes a document type, not a way of working."
],
"confidence": 0.67,
"name": "FRDs",
"reasoning": "FRDs refers to functional requirements documents, which are a body of knowledge/artifact category rather than software or a process, so the best fit is Domain by the Concept vs Methodology and tool/framework rules.",
"skill_id": "frds",
"subtype": "functional_requirements_documents",
"type": "Domain"
},
"warnings": []
},
"source_tag": "llm",
"was_in_llm_skills": true
},
{
"aliases_in_db": [],
"canonical": null,
"dimensions": [
{
"dimension": {
"difficulty_hint": null,
"display_name": "Domain Knowledge and Business Context",
"id": null,
"rationale": "Covers understanding the business domain, processes, terminology, and rules needed to analyze requirements and make sound decisions. For a Business Analyst, this skill is the broad knowledge base that lets them interpret stakeholder needs and translate them into workable solutions.",
"slug": "d_init_01",
"source": "llm"
},
"input_skill": "Knowledge",
"llm_role": null,
"roles_from_db": []
}
],
"input_skill": "Knowledge",
"matched_via": null,
"new_alias_persisted": false,
"new_alias_text": null,
"new_skill_meta": {
"derived": {
"category": "Concept",
"skill_nature": "CONCEPT",
"sub_category": "general_knowledge",
"typical_lifespan": "EVERGREEN",
"version_strategy": "NOT_APPLICABLE",
"volatility": "STABLE"
},
"enrichment": {
"ambiguity": {
"ambiguity_flag": true,
"confused_with": [
"knowledge_management",
"knowledge_graph",
"knowledge_base"
],
"reasoning": "\"Knowledge\" is a very broad concept and in JDs could refer to knowledge management, knowledge graphs, or a knowledge base rather than the generic concept."
},
"context_keywords": {
"context_keywords": [
"domain expertise",
"subject matter expert",
"institutional knowledge",
"knowledge base",
"knowledge management",
"knowledge transfer",
"best practices",
"lessons learned",
"documentation",
"taxonomy",
"ontology",
"information architecture",
"expert judgment",
"decision support",
"organizational memory"
]
},
"maturity": {
"confidence": 0.86,
"maturity": "well_known",
"reasoning": "General knowledge is a baseline requirement in most job descriptions and hiring screens across roles, making it broadly expected rather than specialized."
},
"skill_id": "knowledge",
"vendor_license": {
"confidence": 0.99,
"license": null,
"vendor": null,
"year_introduced": null
},
"versioning": {
"current_version": null,
"version_aliases": {},
"versioned": false
}
},
"keep_log": [],
"locked_dimensions": [
{
"description": "Covers understanding the business domain, processes, terminology, and rules needed to analyze requirements and make sound decisions. For a Business Analyst, this skill is the broad knowledge base that lets them interpret stakeholder needs and translate them into workable solutions.",
"exemplar_skills": [
"Knowledge",
"business domain knowledge",
"process knowledge",
"stakeholder understanding",
"product knowledge",
"regulatory awareness"
],
"in_scope": "Knowledge, business domain understanding, process knowledge, stakeholder context, terminology, policies, operating rules, regulatory awareness, product knowledge",
"name": "Domain Knowledge and Business Context",
"out_of_scope": "Requirements elicitation techniques, process modeling notation, data analysis methods, project management, technical implementation details",
"overlap_flags": [
{
"reason": "Some business knowledge overlaps with service boundaries and integration constraints, but that dimension owns the technical architecture view.",
"with_dim_id": "service-architecture-and-integration",
"with_dim_name": null,
"with_role": null
},
{
"reason": "Business context can inform data interpretation, but that dimension owns the mechanics of combining and shaping data.",
"with_dim_id": "data-preparation-and-blending",
"with_dim_name": null,
"with_role": null
}
],
"tentative_id": "d_init_01"
}
],
"merge_log": [],
"placed": {
"name": "Knowledge",
"placement_confidence": 0.92,
"primary_dimension": "d_init_01",
"reasoning": "Deterministic JD placement: locked_dimensions has 1 dimension(s) from skill-driven dimension generation after reconciliation; primary_dimension is the first locked dim.",
"secondary_dimensions": [],
"skill_id": "knowledge"
},
"relationships": {
"child_skills": [],
"parent_skills": [],
"related_to": [],
"requires": [],
"skill_id": "knowledge",
"suppress_on_match": []
},
"skill_id": "knowledge",
"split_log": [],
"typed": {
"alternatives_considered": [],
"confidence": 0.98,
"name": "Knowledge",
"reasoning": "This is a named knowledge unit rather than a way of working or a system shape, so by the Concept vs Methodology and Architecture vs Concept rules 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": "Domain",
"skill_nature": "CONCEPT",
"sub_category": "quality_assurance",
"typical_lifespan": "EVERGREEN",
"version_strategy": "NOT_APPLICABLE",
"volatility": "STABLE"
},
"enrichment": {
"ambiguity": {
"ambiguity_flag": true,
"confused_with": [
"quality_assurance_engineering",
"quality_control"
],
"reasoning": "\"QA\" is a common abbreviation for quality assurance, but in JDs it can also mean quality control or QA engineering/testing roles; a reasonable extractor could map it to adjacent catalog skills."
},
"context_keywords": {
"context_keywords": [
"test cases",
"test plans",
"test automation",
"regression testing",
"smoke testing",
"UAT",
"bug tracking",
"defect lifecycle",
"Selenium",
"JUnit",
"pytest",
"CI/CD",
"acceptance criteria",
"test scripts",
"traceability matrix"
]
},
"maturity": {
"confidence": 0.95,
"maturity": "well_known",
"reasoning": "QA is a standard hiring requirement across software JDs, with broad demand for test planning, automation, and regression coverage; it appears routinely alongside Selenium/Cypress and CI pipelines in job postings."
},
"skill_id": "qa",
"vendor_license": {
"confidence": 0.99,
"license": null,
"vendor": null,
"year_introduced": null
},
"versioning": {
"current_version": null,
"version_aliases": {},
"versioned": false
}
},
"keep_log": [],
"locked_dimensions": [],
"merge_log": [
{
"a_dim_id": "d_init_01",
"a_name": "Test Case Design and Execution",
"a_role": "__skill_focal__",
"b_dim_id": "test-case-design-and-execution",
"b_name": "Test Case Design and Execution",
"b_role": "Manual Tester",
"into": "d_merge_01",
"into_name": "Manual Test Case Design, Execution, and Validation",
"merged_from": [
"d_init_01",
"test-case-design-and-execution"
],
"pair_kind": "cross_role",
"reasoning": "Both dims describe the same manual QA/test-case workflow: creating, reviewing, and executing human-run tests against requirements and acceptance criteria, then logging defects and evidence. Dim A includes manual test cases, regression testing, exploratory testing, defect logging, test evidence, and UAT support; Dim B says the same core discipline for features, fixes, and regressions, turning requirements into repeatable checks. The exemplar skills in A (manual testing, test case design, test execution, regression testing, UAT, defect tracking) align directly with B\u0027s description, so this is a wording overlap, not distinct clusters.",
"similarity": 0.8235757615279269
}
],
"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",
"health-checks"
],
"requires": [],
"skill_id": "qa",
"suppress_on_match": []
},
"skill_id": "qa",
"split_log": [],
"typed": {
"alternatives_considered": [],
"confidence": 0.9,
"name": "QA",
"reasoning": "QA is best treated as a Domain because it denotes the quality assurance problem-space/body of knowledge rather than a specific tool, framework, or methodology.",
"skill_id": "qa",
"subtype": "quality_assurance",
"type": "Domain"
},
"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 Delivery Lifecycle",
"id": null,
"rationale": "Covers the end-to-end process used to plan, build, test, release, and maintain software products. SDLC belongs here because it refers to the overall lifecycle framework rather than a single technical practice.",
"slug": "d_init_01",
"source": "llm"
},
"input_skill": "SDLC",
"llm_role": null,
"roles_from_db": []
}
],
"input_skill": "SDLC",
"matched_via": null,
"new_alias_persisted": false,
"new_alias_text": null,
"new_skill_meta": {
"derived": {
"category": "Methodology",
"skill_nature": "METHODOLOGY",
"sub_category": "software_development_lifecycle",
"typical_lifespan": "EVERGREEN",
"version_strategy": "NOT_APPLICABLE",
"volatility": "STABLE"
},
"enrichment": {
"ambiguity": {
"ambiguity_flag": false,
"confused_with": [],
"reasoning": "SDLC is a standard, well-known acronym for software development lifecycle and is usually unambiguous in job descriptions."
},
"context_keywords": {
"context_keywords": [
"requirements gathering",
"design review",
"implementation",
"code review",
"testing",
"QA",
"UAT",
"deployment",
"release management",
"change management",
"Agile",
"Scrum",
"waterfall",
"CI/CD",
"version control"
]
},
"maturity": {
"confidence": 0.93,
"maturity": "well_known",
"reasoning": "SDLC is a standard term in software job descriptions and enterprise process docs; it underpins common frameworks like Agile, Scrum, and DevOps 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
}
},
"keep_log": [],
"locked_dimensions": [
{
"description": "Covers the end-to-end process used to plan, build, test, release, and maintain software products. SDLC belongs here because it refers to the overall lifecycle framework rather than a single technical practice.",
"exemplar_skills": [
"SDLC",
"software development lifecycle",
"requirements analysis",
"release management",
"change management",
"defect lifecycle",
"software maintenance"
],
"in_scope": "SDLC, requirements gathering, design, implementation, testing, release management, maintenance, change control, versioning, defect tracking, documentation, agile SDLC, waterfall SDLC",
"name": "Software Delivery Lifecycle",
"out_of_scope": "Specific manual test design and execution, automated API test frameworks, environment provisioning, deployment tooling, production monitoring, which belong to more specialized delivery or operations dimensions",
"overlap_flags": [
{
"reason": "SDLC includes testing as a phase, but this catalog dimension is specifically about designing and executing test cases.",
"with_dim_id": "test-case-design-and-execution",
"with_dim_name": null,
"with_role": "Manual Tester"
},
{
"reason": "SDLC may reference environment stages, but this dimension owns the mechanics of creating and promoting environments.",
"with_dim_id": "environment-provisioning-and-promotion",
"with_dim_name": null,
"with_role": null
},
{
"reason": "SDLC can touch design and implementation, but architecture and integration are a separate technical concern.",
"with_dim_id": "service-architecture-and-integration",
"with_dim_name": null,
"with_role": null
}
],
"tentative_id": "d_init_01"
}
],
"merge_log": [],
"placed": {
"name": "SDLC",
"placement_confidence": 0.92,
"primary_dimension": "d_init_01",
"reasoning": "Deterministic JD placement: locked_dimensions has 1 dimension(s) from skill-driven dimension generation after reconciliation; primary_dimension is the first locked dim.",
"secondary_dimensions": [],
"skill_id": "sdlc"
},
"relationships": {
"child_skills": [],
"parent_skills": [],
"related_to": [
"acceptance-criteria-checks",
"acceptance-criteria-validation",
"defect-retest",
"dependency-mapping",
"dashboards",
"scorecards"
],
"requires": [],
"skill_id": "sdlc",
"suppress_on_match": []
},
"skill_id": "sdlc",
"split_log": [],
"typed": {
"alternatives_considered": [],
"confidence": 0.88,
"name": "SDLC",
"reasoning": "SDLC is best treated as a Methodology because it describes the process and phases for how software is developed and delivered, matching the Concept vs Methodology rule.",
"skill_id": "sdlc",
"subtype": "software_development_lifecycle",
"type": "Methodology"
},
"warnings": []
},
"source_tag": "llm",
"was_in_llm_skills": true
},
{
"aliases_in_db": [],
"canonical": null,
"dimensions": [
{
"dimension": {
"difficulty_hint": null,
"display_name": "Software as a Service",
"id": null,
"rationale": "Covers the product and delivery model where software is hosted centrally and consumed over the internet by subscription or usage-based access. This fits SaaS because the skill refers to the service model itself, not a specific technical implementation area.",
"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-established term for software as a service; in JDs it is usually unambiguous and not easily mistaken for a different catalog skill."
},
"context_keywords": {
"context_keywords": [
"multi-tenant",
"subscription billing",
"tenant isolation",
"self-service onboarding",
"usage-based pricing",
"provisioning",
"SAML",
"SSO",
"RBAC",
"API integrations",
"webhooks",
"SLAs",
"churn",
"customer success",
"feature flags"
]
},
"maturity": {
"confidence": 0.96,
"maturity": "well_known",
"reasoning": "SaaS is a standard deployment model in job postings across product, sales, and engineering roles; major vendors like Salesforce, Microsoft, and Google market SaaS offerings broadly, indicating mainstream adoption."
},
"skill_id": "saas",
"vendor_license": {
"confidence": 0.78,
"license": null,
"vendor": "Salesforce",
"year_introduced": 1999
},
"versioning": {
"current_version": null,
"version_aliases": {},
"versioned": false
}
},
"keep_log": [],
"locked_dimensions": [
{
"description": "Covers the product and delivery model where software is hosted centrally and consumed over the internet by subscription or usage-based access. This fits SaaS because the skill refers to the service model itself, not a specific technical implementation area.",
"exemplar_skills": [
"SaaS",
"multi-tenant application design",
"subscription software",
"hosted software delivery",
"tenant provisioning",
"software subscription models"
],
"in_scope": "SaaS, subscription software, multi-tenant hosted applications, web-delivered software, tenant onboarding, usage-based access, service tiers, customer provisioning, SaaS product packaging",
"name": "Software as a Service",
"out_of_scope": "On-premises software deployment, container orchestration, cloud security controls, API integration patterns, which belong to infrastructure or application architecture dimensions",
"overlap_flags": [
{
"reason": "SaaS products are often built from services, but this dimension is about the delivery model rather than backend service decomposition.",
"with_dim_id": "service-architecture-and-integration",
"with_dim_name": null,
"with_role": null
},
{
"reason": "SaaS operations may involve environment management, but that dimension focuses on delivery environments rather than the SaaS business/service model.",
"with_dim_id": "environment-provisioning-and-promotion",
"with_dim_name": null,
"with_role": null
}
],
"tentative_id": "d_init_01"
}
],
"merge_log": [],
"placed": {
"name": "SaaS",
"placement_confidence": 0.92,
"primary_dimension": "d_init_01",
"reasoning": "Deterministic JD placement: locked_dimensions has 1 dimension(s) from skill-driven dimension generation after reconciliation; primary_dimension is the first locked dim.",
"secondary_dimensions": [],
"skill_id": "saas"
},
"relationships": {
"child_skills": [],
"parent_skills": [],
"related_to": [
"cloud-run",
"azure-backup",
"cspm",
"policy-as-code",
"cloud-reference-architecture"
],
"requires": [],
"skill_id": "saas",
"suppress_on_match": []
},
"skill_id": "saas",
"split_log": [],
"typed": {
"alternatives_considered": [],
"confidence": 0.93,
"name": "SaaS",
"reasoning": "By the Platform vs Tool rule, SaaS is a hosted multi-tenant environment delivered over APIs and managed services rather than software you run yourself.",
"skill_id": "saas",
"subtype": "software_as_a_service_platform",
"type": "Platform"
},
"warnings": []
},
"source_tag": "llm",
"was_in_llm_skills": true
},
{
"aliases_in_db": [],
"canonical": null,
"dimensions": [
{
"dimension": {
"difficulty_hint": null,
"display_name": "User Acceptance Testing",
"id": null,
"rationale": "Validation of a feature or change by business users against agreed acceptance criteria before release. UAT belongs here because it is a manual, requirement-driven test phase focused on confirming the solution meets user and business needs.",
"slug": "d_init_01",
"source": "llm"
},
"input_skill": "UAT",
"llm_role": null,
"roles_from_db": []
}
],
"input_skill": "UAT",
"matched_via": null,
"new_alias_persisted": false,
"new_alias_text": null,
"new_skill_meta": {
"derived": {
"category": "Methodology",
"skill_nature": "METHODOLOGY",
"sub_category": "user_acceptance_testing",
"typical_lifespan": "EVERGREEN",
"version_strategy": "NOT_APPLICABLE",
"volatility": "STABLE"
},
"enrichment": {
"ambiguity": {
"ambiguity_flag": false,
"confused_with": [],
"reasoning": "UAT in JDs almost always means User Acceptance Testing; the acronym is standard and not typically confused with another catalog skill."
},
"context_keywords": {
"context_keywords": [
"test cases",
"acceptance criteria",
"test scripts",
"business users",
"end users",
"sign-off",
"defect triage",
"test scenarios",
"test plan",
"go-live",
"regression testing",
"stakeholder review",
"test environment",
"requirements validation",
"smoke testing"
]
},
"maturity": {
"confidence": 0.86,
"maturity": "well_known",
"reasoning": "UAT appears in many QA/test analyst job descriptions and is a standard pre-release signoff step in enterprise software delivery, especially alongside Agile/DevOps pipelines."
},
"skill_id": "uat",
"vendor_license": {
"confidence": 0.99,
"license": null,
"vendor": null,
"year_introduced": null
},
"versioning": {
"current_version": null,
"version_aliases": {},
"versioned": false
}
},
"keep_log": [],
"locked_dimensions": [
{
"description": "Validation of a feature or change by business users against agreed acceptance criteria before release. UAT belongs here because it is a manual, requirement-driven test phase focused on confirming the solution meets user and business needs.",
"exemplar_skills": [
"UAT",
"user acceptance testing",
"acceptance criteria validation",
"business user sign-off",
"scenario-based manual testing",
"release readiness testing"
],
"in_scope": "UAT, user acceptance testing, acceptance criteria validation, business user sign-off, scenario-based manual testing, release readiness checks, defect logging from acceptance runs",
"name": "User Acceptance Testing",
"out_of_scope": "Automated unit tests, API regression suites, performance testing, production monitoring, which belong to engineering test automation, service testing, or operations dimensions",
"overlap_flags": [
{
"reason": "UAT is a form of manual test execution, but this dimension is specifically about business acceptance rather than general test case work.",
"with_dim_id": "test-case-design-and-execution",
"with_dim_name": null,
"with_role": "Manual Tester"
},
{
"reason": "UAT may include validating backend flows, but the dimension is centered on business acceptance rather than automated service-level verification.",
"with_dim_id": "api-and-service-test-automation",
"with_dim_name": null,
"with_role": null
},
{
"reason": "Some teams automate acceptance checks, but UAT itself is primarily a manual business validation activity.",
"with_dim_id": "testing-and-automation-frameworks",
"with_dim_name": null,
"with_role": null
}
],
"tentative_id": "d_init_01"
}
],
"merge_log": [],
"placed": {
"name": "UAT",
"placement_confidence": 0.92,
"primary_dimension": "d_init_01",
"reasoning": "Deterministic JD placement: locked_dimensions has 1 dimension(s) from skill-driven dimension generation after reconciliation; primary_dimension is the first locked dim.",
"secondary_dimensions": [],
"skill_id": "uat"
},
"relationships": {
"child_skills": [],
"parent_skills": [],
"related_to": [
"acceptance-criteria-checks",
"session-based-testing",
"test-case-authoring"
],
"requires": [],
"skill_id": "uat",
"suppress_on_match": []
},
"skill_id": "uat",
"split_log": [],
"typed": {
"alternatives_considered": [],
"confidence": 0.93,
"name": "UAT",
"reasoning": "UAT is a way of working for validating software with users before release, so by the Concept vs Methodology rule it is a Methodology rather than a tool or concept.",
"skill_id": "uat",
"subtype": "user_acceptance_testing",
"type": "Methodology"
},
"warnings": []
},
"source_tag": "llm",
"was_in_llm_skills": true
},
{
"aliases_in_db": [],
"canonical": null,
"dimensions": [
{
"dimension": {
"difficulty_hint": null,
"display_name": "Diagramming and Process Modeling",
"id": null,
"rationale": "Covers creating business and technical diagrams to communicate workflows, systems, and relationships. Visio belongs here because it is commonly used by business analysts to document processes, swimlanes, org charts, and system maps.",
"slug": "d_init_01",
"source": "llm"
},
"input_skill": "Visio",
"llm_role": null,
"roles_from_db": []
}
],
"input_skill": "Visio",
"matched_via": null,
"new_alias_persisted": false,
"new_alias_text": null,
"new_skill_meta": {
"derived": {
"category": "Tool",
"skill_nature": "TOOL",
"sub_category": "diagramming_tool",
"typical_lifespan": "EVERGREEN",
"version_strategy": "NOT_APPLICABLE",
"volatility": "STABLE"
},
"enrichment": {
"ambiguity": {
"ambiguity_flag": false,
"confused_with": [],
"reasoning": "Visio is a specific Microsoft diagramming tool; in typical JDs it is unlikely to be confused with another catalog skill."
},
"context_keywords": {
"context_keywords": [
"process flow",
"swimlane",
"BPMN",
"UML",
"network diagram",
"org chart",
"floor plan",
"workflow",
"data flow",
"system architecture",
"ERD",
"cross-functional",
"stencil",
"shapes",
"blueprint"
]
},
"maturity": {
"confidence": 0.86,
"maturity": "well_known",
"reasoning": "Common in enterprise JDs for process/network diagrams and Microsoft 365 ecosystems; no vendor sunset, and it remains a standard diagramming tool alongside Lucidchart/draw.io."
},
"skill_id": "visio",
"vendor_license": {
"confidence": 0.99,
"license": "proprietary",
"vendor": "Microsoft",
"year_introduced": 1992
},
"versioning": {
"current_version": null,
"version_aliases": {},
"versioned": false
}
},
"keep_log": [],
"locked_dimensions": [
{
"description": "Covers creating business and technical diagrams to communicate workflows, systems, and relationships. Visio belongs here because it is commonly used by business analysts to document processes, swimlanes, org charts, and system maps.",
"exemplar_skills": [
"Visio",
"process mapping",
"swimlane diagramming",
"BPMN diagramming",
"workflow modeling",
"org chart creation"
],
"in_scope": "Visio, process flow diagrams, swimlane diagrams, BPMN sketches, org charts, system context diagrams, workflow mapping, data flow diagrams, UML-style sketches",
"name": "Diagramming and Process Modeling",
"out_of_scope": "Requirements elicitation, stakeholder interviews, business case writing, detailed solution architecture, which belong to analysis or architecture dimensions rather than diagram production",
"overlap_flags": [
{
"reason": "System and integration diagrams can overlap with solution architecture documentation, though the focus here is on visual modeling rather than architecture design.",
"with_dim_id": "service-architecture-and-integration",
"with_dim_name": null,
"with_role": null
}
],
"tentative_id": "d_init_01"
}
],
"merge_log": [],
"placed": {
"name": "Visio",
"placement_confidence": 0.92,
"primary_dimension": "d_init_01",
"reasoning": "Deterministic JD placement: locked_dimensions has 1 dimension(s) from skill-driven dimension generation after reconciliation; primary_dimension is the first locked dim.",
"secondary_dimensions": [],
"skill_id": "visio"
},
"relationships": {
"child_skills": [],
"parent_skills": [],
"related_to": [],
"requires": [],
"skill_id": "visio",
"suppress_on_match": []
},
"skill_id": "visio",
"split_log": [],
"typed": {
"alternatives_considered": [],
"confidence": 0.98,
"name": "Visio",
"reasoning": "Visio is software you operate to create diagrams, so by the Tool vs Framework rule it is a Tool rather than something you build applications inside.",
"skill_id": "visio",
"subtype": "diagramming_tool",
"type": "Tool"
},
"warnings": []
},
"source_tag": "llm",
"was_in_llm_skills": true
}
],
"unmatched_skills": [
"APIs",
"CBAP",
"CCBA",
"Excel",
"FRDs",
"Knowledge",
"QA",
"SDLC",
"SaaS",
"UAT",
"Visio"
]
}
API 3 — final-role-output
{
"chosen_role": {
"display_name": "Data Analyst",
"id": 20,
"rationale": "The strongest dimension is reporting and dashboard development, which maps directly to Data Analyst and outweighs the smaller workflow-orchestration signal.",
"role_archetype": null,
"slug": "data-analyst",
"source": "db"
},
"final_input_skills": [
{
"skill": "Power BI",
"tag": "in_db"
},
{
"skill": "Tableau",
"tag": "in_db"
},
{
"skill": "Argo Workflows",
"tag": "in_db"
},
{
"skill": "APIs",
"tag": "new"
},
{
"skill": "CBAP",
"tag": "new"
},
{
"skill": "CCBA",
"tag": "new"
},
{
"skill": "Excel",
"tag": "new"
},
{
"skill": "FRDs",
"tag": "new"
},
{
"skill": "Knowledge",
"tag": "new"
},
{
"skill": "QA",
"tag": "new"
},
{
"skill": "SDLC",
"tag": "new"
},
{
"skill": "SaaS",
"tag": "new"
},
{
"skill": "UAT",
"tag": "new"
},
{
"skill": "Visio",
"tag": "new"
}
],
"persistence": {
"items": [
{
"chosen_role_id": 20,
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Reporting and Dashboard Development",
"id": 295,
"rationale": "Building recurring reports and dashboards that track performance over time and across segments. This is a distinct cluster because the analyst must package metrics into reusable views for stakeholders.",
"slug": "reporting-and-dashboard-development",
"source": "db"
},
"dimension_id": 295,
"input_skill": "Power BI",
"llm_role": null,
"matched_chosen_role": true,
"role_dimension_saved": false,
"roles_from_db": [
{
"display_name": "Data Analyst",
"id": 20,
"rationale": null,
"role_archetype": null,
"slug": "data-analyst",
"source": "db"
}
],
"skill_dimension_saved": false,
"skill_id": 1884,
"skill_tag": "in_db",
"skipped_reason": "TODO: REMOVE AFTER TESTING \u2014 api3_writes_enabled=False (writes disabled)"
},
{
"chosen_role_id": 20,
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Reporting and Dashboard Development",
"id": 295,
"rationale": "Building recurring reports and dashboards that track performance over time and across segments. This is a distinct cluster because the analyst must package metrics into reusable views for stakeholders.",
"slug": "reporting-and-dashboard-development",
"source": "db"
},
"dimension_id": 295,
"input_skill": "Tableau",
"llm_role": null,
"matched_chosen_role": true,
"role_dimension_saved": false,
"roles_from_db": [
{
"display_name": "Data Analyst",
"id": 20,
"rationale": null,
"role_archetype": null,
"slug": "data-analyst",
"source": "db"
}
],
"skill_dimension_saved": false,
"skill_id": 1883,
"skill_tag": "in_db",
"skipped_reason": "TODO: REMOVE AFTER TESTING \u2014 api3_writes_enabled=False (writes disabled)"
},
{
"chosen_role_id": 20,
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Workflow Orchestration Systems",
"id": 64,
"rationale": "Operational orchestration of ML jobs, dependencies, and handoffs across training, validation, deployment, and retraining. This is a useful split from training pipelines because it emphasizes the scheduler and control plane.",
"slug": "workflow-orchestration-systems",
"source": "db"
},
"dimension_id": 64,
"input_skill": "Argo Workflows",
"llm_role": null,
"matched_chosen_role": false,
"role_dimension_saved": false,
"roles_from_db": [
{
"display_name": "Data Engineer",
"id": 6,
"rationale": null,
"role_archetype": null,
"slug": "data-engineer",
"source": "db"
},
{
"display_name": "MLOps Engineer",
"id": 5,
"rationale": null,
"role_archetype": null,
"slug": "mlops-engineer",
"source": "db"
}
],
"skill_dimension_saved": false,
"skill_id": 380,
"skill_tag": "in_db",
"skipped_reason": "TODO: REMOVE AFTER TESTING \u2014 api3_writes_enabled=False (writes disabled)"
},
{
"chosen_role_id": 20,
"dimension": {
"difficulty_hint": null,
"display_name": "API Design and Contracts",
"id": null,
"rationale": "Covers the structure, semantics, and lifecycle of application programming interfaces, including how consumers understand and use them. APIs belong here when the focus is on defining stable, clear, and evolvable interfaces.",
"slug": "d_init_01",
"source": "llm"
},
"dimension_id": null,
"input_skill": "APIs",
"llm_role": null,
"matched_chosen_role": false,
"role_dimension_saved": false,
"roles_from_db": [],
"skill_dimension_saved": false,
"skill_id": null,
"skill_tag": "new",
"skipped_reason": "skill_not_in_db_v3_proposed"
},
{
"chosen_role_id": 20,
"dimension": {
"difficulty_hint": null,
"display_name": "Business Analysis Certification",
"id": null,
"rationale": "Professional certification knowledge for business analysts, including the CBAP body of knowledge and related competency areas. This fits CBAP because it is itself a business analysis certification rather than a technical tool or platform skill.",
"slug": "d_init_01",
"source": "llm"
},
"dimension_id": null,
"input_skill": "CBAP",
"llm_role": null,
"matched_chosen_role": false,
"role_dimension_saved": false,
"roles_from_db": [],
"skill_dimension_saved": false,
"skill_id": null,
"skill_tag": "new",
"skipped_reason": "skill_not_in_db_v3_proposed"
},
{
"chosen_role_id": 20,
"dimension": {
"difficulty_hint": null,
"display_name": "Business Analysis Certification",
"id": null,
"rationale": "Formal business analysis credentialing and professional standards for analysts. CCBA belongs here because it is a recognized certification focused on business analysis knowledge, practices, and competency validation.",
"slug": "d_init_01",
"source": "llm"
},
"dimension_id": null,
"input_skill": "CCBA",
"llm_role": null,
"matched_chosen_role": false,
"role_dimension_saved": false,
"roles_from_db": [],
"skill_dimension_saved": false,
"skill_id": null,
"skill_tag": "new",
"skipped_reason": "skill_not_in_db_v3_proposed"
},
{
"chosen_role_id": 20,
"dimension": {
"difficulty_hint": null,
"display_name": "Spreadsheet Analysis and Reporting",
"id": null,
"rationale": "Using Excel to organize, analyze, and present business data in spreadsheet form. This fits a Business Analyst because Excel is commonly used for ad hoc analysis, reporting, and lightweight modeling.",
"slug": "d_init_01",
"source": "llm"
},
"dimension_id": null,
"input_skill": "Excel",
"llm_role": null,
"matched_chosen_role": false,
"role_dimension_saved": false,
"roles_from_db": [],
"skill_dimension_saved": false,
"skill_id": null,
"skill_tag": "new",
"skipped_reason": "skill_not_in_db_v3_proposed"
},
{
"chosen_role_id": 20,
"dimension": {
"difficulty_hint": null,
"display_name": "Functional Requirements Documents",
"id": null,
"rationale": "Covers writing, reviewing, and maintaining FRDs that translate business needs into clear functional scope, rules, and acceptance criteria. This fits a Business Analyst role because FRDs are a core artifact for defining what a solution must do before delivery begins.",
"slug": "d_init_01",
"source": "llm"
},
"dimension_id": null,
"input_skill": "FRDs",
"llm_role": null,
"matched_chosen_role": false,
"role_dimension_saved": false,
"roles_from_db": [],
"skill_dimension_saved": false,
"skill_id": null,
"skill_tag": "new",
"skipped_reason": "skill_not_in_db_v3_proposed"
},
{
"chosen_role_id": 20,
"dimension": {
"difficulty_hint": null,
"display_name": "Domain Knowledge and Business Context",
"id": null,
"rationale": "Covers understanding the business domain, processes, terminology, and rules needed to analyze requirements and make sound decisions. For a Business Analyst, this skill is the broad knowledge base that lets them interpret stakeholder needs and translate them into workable solutions.",
"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": 20,
"dimension": {
"difficulty_hint": null,
"display_name": "Software Delivery Lifecycle",
"id": null,
"rationale": "Covers the end-to-end process used to plan, build, test, release, and maintain software products. SDLC belongs here because it refers to the overall lifecycle framework rather than a single technical practice.",
"slug": "d_init_01",
"source": "llm"
},
"dimension_id": null,
"input_skill": "SDLC",
"llm_role": null,
"matched_chosen_role": false,
"role_dimension_saved": false,
"roles_from_db": [],
"skill_dimension_saved": false,
"skill_id": null,
"skill_tag": "new",
"skipped_reason": "skill_not_in_db_v3_proposed"
},
{
"chosen_role_id": 20,
"dimension": {
"difficulty_hint": null,
"display_name": "Software as a Service",
"id": null,
"rationale": "Covers the product and delivery model where software is hosted centrally and consumed over the internet by subscription or usage-based access. This fits SaaS because the skill refers to the service model itself, not a specific technical implementation area.",
"slug": "d_init_01",
"source": "llm"
},
"dimension_id": null,
"input_skill": "SaaS",
"llm_role": null,
"matched_chosen_role": false,
"role_dimension_saved": false,
"roles_from_db": [],
"skill_dimension_saved": false,
"skill_id": null,
"skill_tag": "new",
"skipped_reason": "skill_not_in_db_v3_proposed"
},
{
"chosen_role_id": 20,
"dimension": {
"difficulty_hint": null,
"display_name": "User Acceptance Testing",
"id": null,
"rationale": "Validation of a feature or change by business users against agreed acceptance criteria before release. UAT belongs here because it is a manual, requirement-driven test phase focused on confirming the solution meets user and business needs.",
"slug": "d_init_01",
"source": "llm"
},
"dimension_id": null,
"input_skill": "UAT",
"llm_role": null,
"matched_chosen_role": false,
"role_dimension_saved": false,
"roles_from_db": [],
"skill_dimension_saved": false,
"skill_id": null,
"skill_tag": "new",
"skipped_reason": "skill_not_in_db_v3_proposed"
},
{
"chosen_role_id": 20,
"dimension": {
"difficulty_hint": null,
"display_name": "Diagramming and Process Modeling",
"id": null,
"rationale": "Covers creating business and technical diagrams to communicate workflows, systems, and relationships. Visio belongs here because it is commonly used by business analysts to document processes, swimlanes, org charts, and system maps.",
"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": 13
},
"planner_output": null,
"run_id": "eba3651b-b31d-4619-a45a-afdc2e1373f0"
}
LLM Calls
Every model call made for this run, in pipeline order. Click a card to see the model's response.
Loading…