Pipeline run
5ea778e2-d522-4b40-9a49-2c1c35e5d410
Client output enrichment
v2 Skill cluster · Nature of work · AI index · Tech stack maturity · Evidence · KRA description
role baseline loaded
sources · ai_index: jd · nature_of_work: no_kras · tech_stack_maturity: jd
Nature 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-08T07:42:27.330366Z
Updated: 2026-05-08T07:44:21.024787Z
API 3 duration: 703 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 Engineer
slug: data-engineer · id: 6 · source: db
The strongest repeated DB evidence is for Data Engineer across workflow orchestration and the broader technical/API dimension, while reporting tools only support Data Analyst.
0
New skills
0
Skill↔dim saved
0
Role↔dim saved
17
Skipped
Job description
Business Analyst Job Description Job Title: Business Analyst Experience: 2–5 Years Location: Remote / Hybrid / On-site About the Role We are looking for a Business Analyst to bridge the gap between business needs and technical solutions. The ideal candidate will work closely with stakeholders, product teams, and developers to gather requirements, analyze business processes, and support successful project delivery. Key Responsibilities Gather, analyze, and document business requirements from stakeholders Translate business needs into functional specifications and user stories Work with cross-functional teams including developers, QA, and product managers Conduct requirement workshops, stakeholder meetings, and process analysis Create BRDs, FRDs, workflows, process diagrams, and reports Analyze data to identify trends, opportunities, and business insights Support UAT (User Acceptance Testing) and validate delivered solutions Monitor project progress and help manage risks and dependencies Improve existing business processes and recommend optimization strategies Ensure solutions align with business goals and operational needs Required Skills Strong understanding of business analysis methodologies Experience with requirement gathering and documentation Knowledge of Agile/Scrum methodologies Excellent communication and stakeholder management skills Strong analytical and problem-solving abilities Experience with tools like JIRA, Confluence, Excel, Visio, or Power BI Ability to create reports, dashboards, and process flows Understanding of SDLC and software development processes Preferred Qualifications Bachelor’s degree in Business, Computer Science, IT, or related field Experience working with technical and non-technical teams Familiarity with SQL, data analysis, or reporting tools is a plus Certification such as CBAP, CCBA, or Agile certification is preferred Nice to Have Experience in fintech, healthcare, e-commerce, or SaaS domains Exposure to BI tools like Tableau or Power BI Basic understanding of APIs and databases Benefits Competitive salary Flexible work environment Health insurance Learning and development opportunities Career growth and mentorship Paid leaves and company benefits
history_view bundle (older API). Showing raw API payloads below.
All API 3 persistence rows
Same grid as the skill-extractor “Persistence items” table: one row per (skill × dimension) work item.
| Skill | Tag | Dimension | Skill↔dim | Role↔dim | Outcome | Notes |
|---|---|---|---|---|---|---|
| Tableau | in_db |
Reporting and Dashboard Development
reporting-and-dashboard-development
|
— | — | — | TODO: REMOVE AFTER TESTING — api3_writes_enabled=False (writes disabled) |
| Argo Workflows | in_db |
Workflow Orchestration Systems
workflow-orchestration-systems
|
— | — | — | TODO: REMOVE AFTER TESTING — api3_writes_enabled=False (writes disabled) |
| Power BI | in_db |
Reporting and Dashboard Development
reporting-and-dashboard-development
|
— | — | — | TODO: REMOVE AFTER TESTING — api3_writes_enabled=False (writes disabled) |
| APIs | new |
API Design and Integration
d_init_01
|
— | — | — | skill_not_in_db_v3_proposed |
| BI | new |
Business Intelligence
d_init_01
|
— | — | — | skill_not_in_db_v3_proposed |
| BRDs | new |
Business Requirements Documents
d_init_01
|
— | — | — | skill_not_in_db_v3_proposed |
| CBAP | new |
Business Analysis Certification
d_init_01
|
— | — | — | skill_not_in_db_v3_proposed |
| CCBA | new |
Business Analysis Certification
d_init_01
|
— | — | — | skill_not_in_db_v3_proposed |
| Excel | new |
Spreadsheet Analysis and Modeling
d_init_01
|
— | — | — | skill_not_in_db_v3_proposed |
| FRDs | new |
Functional Requirements Documents
d_init_01
|
— | — | — | skill_not_in_db_v3_proposed |
| Familiarity | new |
Domain Familiarity
d_init_01
|
— | — | — | skill_not_in_db_v3_proposed |
| Knowledge | new |
Knowledge Representation
d_init_01
|
— | — | — | skill_not_in_db_v3_proposed |
| SDLC | new |
Software Development Lifecycle
d_init_01
|
— | — | — | skill_not_in_db_v3_proposed |
| SaaS | new |
SaaS Product Delivery
d_init_01
|
— | — | — | skill_not_in_db_v3_proposed |
| Testing | new |
General Software Testing
d_init_01
|
— | — | — | skill_not_in_db_v3_proposed |
| Understanding | new |
Conceptual Understanding
d_init_01
|
— | — | — | skill_not_in_db_v3_proposed |
| Visio | new |
Diagramming and Process Modeling
d_init_01
|
— | — | — | skill_not_in_db_v3_proposed |
Library artifacts (this run)
| Kind | Detail | DB id |
|---|---|---|
| canonical_skill_proposed | APIs | type=Protocol subtype=application_programming_interfaces nature=PROTOCOL lifespan=EVERGREEN | |
| canonical_skill_proposed | Acceptance | type=Concept subtype=acceptance_concept nature=CONCEPT lifespan=EVERGREEN | |
| canonical_skill_proposed | BI | type=Domain subtype=business_intelligence nature=CONCEPT lifespan=EVERGREEN | |
| canonical_skill_proposed | BRDs | type=Concept subtype=business_requirements_documents nature=CONCEPT lifespan=EVERGREEN | |
| canonical_skill_proposed | CBAP | type=Certification subtype=business_analysis_professional_certification nature=CREDENTIAL lifespan=EVERGREEN | |
| canonical_skill_proposed | CCBA | type=Certification subtype=business_analysis_certification nature=CREDENTIAL lifespan=EVERGREEN | |
| canonical_skill_proposed | Excel | type=Tool subtype=spreadsheet_software nature=TOOL lifespan=EVERGREEN | |
| canonical_skill_proposed | FRDs | type=Concept subtype=functional_requirements_document nature=CONCEPT lifespan=EVERGREEN | |
| canonical_skill_proposed | Familiarity | type=SoftSkill subtype=familiarity nature=PRACTICE 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 | Understanding | type=Concept subtype=comprehension nature=CONCEPT lifespan=EVERGREEN | |
| canonical_skill_proposed | Visio | type=Tool subtype=diagramming_tool nature=TOOL lifespan=EVERGREEN | |
| dimension_proposed | API Design and Integration | |
| dimension_skill_link_proposed | APIs ↔ API Design and Integration | |
| dimension_proposed | Business Intelligence | |
| dimension_skill_link_proposed | BI ↔ Business Intelligence | |
| dimension_proposed | Business Requirements Documents | |
| dimension_skill_link_proposed | BRDs ↔ Business Requirements Documents | |
| dimension_proposed | Business Analysis Certification | |
| dimension_skill_link_proposed | CBAP ↔ Business Analysis Certification | |
| dimension_proposed | Business Analysis Certification | |
| dimension_skill_link_proposed | CCBA ↔ Business Analysis Certification | |
| dimension_proposed | Spreadsheet Analysis and Modeling | |
| dimension_skill_link_proposed | Excel ↔ Spreadsheet Analysis and Modeling | |
| dimension_proposed | Functional Requirements Documents | |
| dimension_skill_link_proposed | FRDs ↔ Functional Requirements Documents | |
| dimension_proposed | Domain Familiarity | |
| dimension_skill_link_proposed | Familiarity ↔ Domain Familiarity | |
| dimension_proposed | Knowledge Representation | |
| dimension_skill_link_proposed | Knowledge ↔ Knowledge Representation | |
| dimension_proposed | Software Development Lifecycle | |
| dimension_skill_link_proposed | SDLC ↔ Software Development Lifecycle | |
| dimension_proposed | SaaS Product Delivery | |
| dimension_skill_link_proposed | SaaS ↔ SaaS Product Delivery | |
| dimension_proposed | General Software Testing | |
| dimension_skill_link_proposed | Testing ↔ General Software Testing | |
| dimension_proposed | Conceptual Understanding | |
| dimension_skill_link_proposed | Understanding ↔ Conceptual Understanding | |
| dimension_proposed | Diagramming and Process Modeling | |
| dimension_skill_link_proposed | Visio ↔ Diagramming and Process Modeling |
API 1 — extract-from-jd click to toggle
{
"filtered_unknown_words": [
"2\u20135",
"APIs",
"Ability",
"Acceptance",
"Analyst",
"BI",
"BRDs",
"Bachelor",
"Benefits",
"Business",
"CBAP",
"CCBA",
"Career",
"Certification",
"Computer",
"Conduct",
"Description",
"Ensure",
"Excel",
"Experience",
"Exposure",
"FRDs",
"Familiarity",
"Gather",
"Health",
"Hybrid",
"Job",
"Key",
"Knowledge",
"Learning",
"Location",
"Monitor",
"Power",
"Preferred",
"QA",
"Qualifications",
"Remote",
"Required",
"Responsibilities",
"Role",
"SDLC",
"SaaS",
"Science",
"Skills",
"Support",
"Testing",
"Title",
"UAT",
"Understanding",
"User",
"Visio",
"Years",
"abilities",
"analysis",
"benefits",
"business",
"candidate",
"certification",
"commerce",
"communication",
"company",
"data",
"databases",
"degree",
"delivery",
"dependencies",
"developers",
"development",
"diagrams",
"document",
"documentation",
"domains",
"environment",
"field",
"fintech",
"gap",
"gathering",
"goals",
"growth",
"healthcare",
"insights",
"insurance",
"leaves",
"management",
"managers",
"meetings",
"methodologies",
"needs",
"opportunities",
"optimization",
"problem",
"process",
"processes",
"product",
"progress",
"project",
"reporting",
"requirement",
"requirements",
"risks",
"salary",
"site",
"skills",
"software",
"solutions",
"specifications",
"stakeholder",
"stakeholders",
"stories",
"strategies",
"teams",
"tools",
"trends",
"understanding",
"user",
"work",
"workshops"
],
"final_non_skills": [
"2\u20135",
"Ability",
"Analyst",
"Bachelor",
"Benefits",
"Business",
"Certification",
"Computer",
"Conduct",
"Description",
"Ensure",
"Experience",
"Exposure",
"Gather",
"Health",
"Hybrid",
"Job",
"Key",
"Learning",
"Location",
"Monitor",
"Power",
"Preferred",
"Qualifications",
"Remote",
"Required",
"Responsibilities",
"Role",
"Science",
"Skills",
"Support",
"Title",
"Years",
"abilities",
"candidate",
"commerce",
"communication",
"company",
"degree",
"delivery",
"dependencies",
"developers",
"development",
"diagrams",
"document",
"domains",
"environment",
"field",
"gap",
"gathering",
"goals",
"growth",
"insights",
"insurance",
"leaves",
"management",
"managers",
"meetings",
"methodologies",
"needs",
"opportunities",
"problem",
"process",
"processes",
"product",
"progress",
"project",
"requirement",
"risks",
"salary",
"site",
"solutions",
"stakeholder",
"stakeholders",
"strategies",
"teams",
"work"
],
"final_skills": [
"Tableau",
"Argo Workflows",
"Power BI",
"APIs",
"Acceptance",
"BI",
"BRDs",
"CBAP",
"CCBA",
"Excel",
"FRDs",
"Familiarity",
"Knowledge",
"QA",
"SDLC",
"SaaS",
"Testing",
"UAT",
"Understanding",
"Visio",
"analysis",
"data",
"databases",
"documentation",
"fintech",
"healthcare",
"optimization",
"reporting",
"requirements",
"software",
"specifications",
"stories",
"tools",
"trends",
"workshops"
],
"initial_skills": [
"Tableau",
"Argo Workflows",
"Power BI"
],
"jd_role_hint": null,
"llm_non_skills": [
"2\u20135",
"Ability",
"Analyst",
"Bachelor",
"Benefits",
"Business",
"Certification",
"Computer",
"Conduct",
"Description",
"Ensure",
"Experience",
"Exposure",
"Gather",
"Health",
"Hybrid",
"Job",
"Key",
"Learning",
"Location",
"Monitor",
"Power",
"Preferred",
"Qualifications",
"Remote",
"Required",
"Responsibilities",
"Role",
"Science",
"Skills",
"Support",
"Title",
"Years",
"abilities",
"candidate",
"commerce",
"communication",
"company",
"degree",
"delivery",
"dependencies",
"developers",
"development",
"diagrams",
"document",
"domains",
"environment",
"field",
"gap",
"gathering",
"goals",
"growth",
"insights",
"insurance",
"leaves",
"management",
"managers",
"meetings",
"methodologies",
"needs",
"opportunities",
"problem",
"process",
"processes",
"product",
"progress",
"project",
"requirement",
"risks",
"salary",
"site",
"solutions",
"stakeholder",
"stakeholders",
"strategies",
"teams",
"work"
],
"llm_skills": [
"APIs",
"Acceptance",
"BI",
"BRDs",
"CBAP",
"CCBA",
"Excel",
"FRDs",
"Familiarity",
"Knowledge",
"QA",
"SDLC",
"SaaS",
"Testing",
"UAT",
"Understanding",
"Visio",
"analysis",
"data",
"databases",
"documentation",
"fintech",
"healthcare",
"optimization",
"reporting",
"requirements",
"software",
"specifications",
"stories",
"tools",
"trends",
"understanding",
"workshops"
],
"run_id": null,
"unknown_words": [
"2\u20135",
"APIs",
"Ability",
"Acceptance",
"Analyst",
"BI",
"BRDs",
"Bachelor",
"Benefits",
"Business",
"CBAP",
"CCBA",
"Career",
"Certification",
"Computer",
"Conduct",
"Description",
"Ensure",
"Excel",
"Experience",
"Exposure",
"FRDs",
"Familiarity",
"Gather",
"Health",
"Hybrid",
"Job",
"Key",
"Knowledge",
"Learning",
"Location",
"Monitor",
"Power",
"Preferred",
"QA",
"Qualifications",
"Remote",
"Required",
"Responsibilities",
"Role",
"SDLC",
"SaaS",
"Science",
"Skills",
"Support",
"Testing",
"Title",
"UAT",
"Understanding",
"User",
"Visio",
"Years",
"abilities",
"analysis",
"benefits",
"business",
"candidate",
"certification",
"commerce",
"communication",
"company",
"data",
"databases",
"degree",
"delivery",
"dependencies",
"developers",
"development",
"diagrams",
"document",
"documentation",
"domains",
"environment",
"field",
"fintech",
"gap",
"gathering",
"goals",
"growth",
"healthcare",
"insights",
"insurance",
"leaves",
"management",
"managers",
"meetings",
"methodologies",
"needs",
"opportunities",
"optimization",
"problem",
"process",
"processes",
"product",
"progress",
"project",
"reporting",
"requirement",
"requirements",
"risks",
"salary",
"site",
"skills",
"software",
"solutions",
"specifications",
"stakeholder",
"stakeholders",
"stories",
"strategies",
"teams",
"tools",
"trends",
"understanding",
"user",
"work",
"workshops"
]
}
API 2 — extract-details
{
"alias_matches": [],
"candidate_roles": [
{
"display_name": "Data Analyst",
"id": 20,
"rationale": null,
"role_archetype": null,
"slug": "data-analyst",
"source": "db"
},
{
"display_name": "Data Engineer",
"id": 6,
"rationale": null,
"role_archetype": null,
"slug": "data-engineer",
"source": "db"
},
{
"display_name": "MLOps Engineer",
"id": 5,
"rationale": null,
"role_archetype": null,
"slug": "mlops-engineer",
"source": "db"
}
],
"chosen_role": {
"display_name": "Data Engineer",
"id": 6,
"rationale": "The strongest repeated DB evidence is for Data Engineer across workflow orchestration and the broader technical/API dimension, while reporting tools only support Data Analyst.",
"role_archetype": null,
"slug": "data-engineer",
"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": "Tableau",
"llm_role": null,
"roles_from_db": [
{
"display_name": "Data Analyst",
"id": 20,
"rationale": null,
"role_archetype": null,
"slug": "data-analyst",
"source": "db"
}
]
},
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Workflow Orchestration Systems",
"id": 64,
"rationale": "Operational orchestration of ML jobs, dependencies, and handoffs across training, validation, deployment, and retraining. This is a useful split from training pipelines because it emphasizes the scheduler and control plane.",
"slug": "workflow-orchestration-systems",
"source": "db"
},
"input_skill": "Argo Workflows",
"llm_role": null,
"roles_from_db": [
{
"display_name": "Data Engineer",
"id": 6,
"rationale": null,
"role_archetype": null,
"slug": "data-engineer",
"source": "db"
},
{
"display_name": "MLOps Engineer",
"id": 5,
"rationale": null,
"role_archetype": null,
"slug": "mlops-engineer",
"source": "db"
}
]
},
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Reporting and Dashboard Development",
"id": 295,
"rationale": "Building recurring reports and dashboards that track performance over time and across segments. This is a distinct cluster because the analyst must package metrics into reusable views for stakeholders.",
"slug": "reporting-and-dashboard-development",
"source": "db"
},
"input_skill": "Power BI",
"llm_role": null,
"roles_from_db": [
{
"display_name": "Data Analyst",
"id": 20,
"rationale": null,
"role_archetype": null,
"slug": "data-analyst",
"source": "db"
}
]
},
{
"dimension": {
"difficulty_hint": null,
"display_name": "API Design and Integration",
"id": null,
"rationale": "Designing, documenting, and consuming application programming interfaces as stable contracts between systems. This fits APIs because the skill centers on defining endpoints, payloads, and integration behavior across services and clients.",
"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 belongs here because it commonly refers to the discipline and tooling used to analyze and present operational and strategic metrics.",
"slug": "d_init_01",
"source": "llm"
},
"input_skill": "BI",
"llm_role": null,
"roles_from_db": []
},
{
"dimension": {
"difficulty_hint": null,
"display_name": "Business Requirements Documents",
"id": null,
"rationale": "Covers creating and maintaining BRDs that capture business goals, scope, stakeholders, constraints, and acceptance expectations. This skill belongs here because BRDs are the primary artifact for translating business needs into structured requirements.",
"slug": "d_init_01",
"source": "llm"
},
"input_skill": "BRDs",
"llm_role": null,
"roles_from_db": []
},
{
"dimension": {
"difficulty_hint": null,
"display_name": "Business Analysis Certification",
"id": null,
"rationale": "Professional certification knowledge for business analysts, including the CBAP credential and the competencies it validates. This belongs here because CBAP is itself a business analysis certification rather than a technical implementation skill.",
"slug": "d_init_01",
"source": "llm"
},
"input_skill": "CBAP",
"llm_role": null,
"roles_from_db": []
},
{
"dimension": {
"difficulty_hint": null,
"display_name": "Business Analysis Certification",
"id": null,
"rationale": "Business analysis credentials and the knowledge areas they validate, including requirements elicitation, stakeholder analysis, process modeling, and solution evaluation. CCBA fits here as a recognized business analysis certification rather than a technical implementation skill.",
"slug": "d_init_01",
"source": "llm"
},
"input_skill": "CCBA",
"llm_role": null,
"roles_from_db": []
},
{
"dimension": {
"difficulty_hint": null,
"display_name": "Spreadsheet Analysis and Modeling",
"id": null,
"rationale": "Using Excel to organize, analyze, and model tabular data for reporting and decision support. This covers formulas, pivots, charts, and workbook structure because Excel is the primary spreadsheet tool for these tasks.",
"slug": "d_init_01",
"source": "llm"
},
"input_skill": "Excel",
"llm_role": null,
"roles_from_db": []
},
{
"dimension": {
"difficulty_hint": null,
"display_name": "Functional Requirements Documents",
"id": null,
"rationale": "Covers creating, reviewing, and using FRDs that define product behavior, scope, constraints, and acceptance expectations. FRDs belong here because the skill refers to formal requirement artifacts rather than implementation or testing work.",
"slug": "d_init_01",
"source": "llm"
},
"input_skill": "FRDs",
"llm_role": null,
"roles_from_db": []
},
{
"dimension": {
"difficulty_hint": null,
"display_name": "Domain Familiarity",
"id": null,
"rationale": "General familiarity with a technical domain, stack, or workflow. This fits when the skill indicates awareness or exposure rather than deep implementation ability.",
"slug": "d_init_01",
"source": "llm"
},
"input_skill": "Familiarity",
"llm_role": null,
"roles_from_db": []
},
{
"dimension": {
"difficulty_hint": null,
"display_name": "Knowledge Representation",
"id": null,
"rationale": "Represents structured knowledge used by AI systems to store, retrieve, and reason over facts, concepts, and relationships. The target skill fits here because it refers to the knowledge layer itself rather than a specific model or retrieval mechanism.",
"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 of planning, building, testing, releasing, and maintaining software. SDLC belongs here because it refers to the overall lifecycle framework rather than a single technical subskill.",
"slug": "d_init_01",
"source": "llm"
},
"input_skill": "SDLC",
"llm_role": null,
"roles_from_db": []
},
{
"dimension": {
"difficulty_hint": null,
"display_name": "SaaS Product Delivery",
"id": null,
"rationale": "Covers building, packaging, and operating software delivered as a hosted subscription service. SaaS belongs here because it refers to the delivery model and the product/operational concerns that make a service usable by many customers over time.",
"slug": "d_init_01",
"source": "llm"
},
"input_skill": "SaaS",
"llm_role": null,
"roles_from_db": []
},
{
"dimension": {
"difficulty_hint": null,
"display_name": "General Software Testing",
"id": null,
"rationale": "Testing practices used to verify that software behaves as intended across manual and automated checks. This is the best fit for the standalone skill \"Testing\" when no narrower layer such as frontend, backend, or acceptance validation is specified.",
"slug": "d_init_01",
"source": "llm"
},
"input_skill": "Testing",
"llm_role": null,
"roles_from_db": []
},
{
"dimension": {
"difficulty_hint": null,
"display_name": "Conceptual Understanding",
"id": null,
"rationale": "Broad comprehension of a domain, system, or process well enough to explain how it works and why it behaves a certain way. This skill is too generic to map cleanly to a narrower catalog dimension, so it is treated as a standalone conceptual dimension.",
"slug": "d_init_01",
"source": "llm"
},
"input_skill": "Understanding",
"llm_role": null,
"roles_from_db": []
},
{
"dimension": {
"difficulty_hint": null,
"display_name": "Diagramming and Process Modeling",
"id": null,
"rationale": "Creating clear visual diagrams for systems, workflows, and business processes. Visio belongs here because it is a general-purpose diagramming tool used to model flows, relationships, and structured documentation.",
"slug": "d_init_01",
"source": "llm"
},
"input_skill": "Visio",
"llm_role": null,
"roles_from_db": []
}
],
"input_final_skills": [
"Tableau",
"Argo Workflows",
"Power BI",
"APIs",
"Acceptance",
"BI",
"BRDs",
"CBAP",
"CCBA",
"Excel",
"FRDs",
"Familiarity",
"Knowledge",
"QA",
"SDLC",
"SaaS",
"Testing",
"UAT",
"Understanding",
"Visio",
"analysis",
"data",
"databases",
"documentation",
"fintech",
"healthcare",
"optimization",
"reporting",
"requirements",
"software",
"specifications",
"stories",
"tools",
"trends",
"workshops"
],
"input_llm_skills": [
"APIs",
"Acceptance",
"BI",
"BRDs",
"CBAP",
"CCBA",
"Excel",
"FRDs",
"Familiarity",
"Knowledge",
"QA",
"SDLC",
"SaaS",
"Testing",
"UAT",
"Understanding",
"Visio",
"analysis",
"data",
"databases",
"documentation",
"fintech",
"healthcare",
"optimization",
"reporting",
"requirements",
"software",
"specifications",
"stories",
"tools",
"trends",
"workshops"
],
"new_aliases_persisted": 0,
"run_id": "5ea778e2-d522-4b40-9a49-2c1c35e5d410",
"skills_detail": [
{
"aliases_in_db": [
{
"alias_text": "Tableau",
"alias_type": "CANONICAL",
"id": 2534,
"is_primary": true,
"match_strategy": "CASE_INSENSITIVE"
}
],
"canonical": {
"category_id": 11,
"display_name": "Tableau",
"id": 1883,
"is_also_category": false,
"is_extractable": true,
"skill_nature": "TOOL",
"slug": "tableau",
"sub_category_id": 1618,
"typical_lifespan": "EVERGREEN",
"volatility": "STABLE"
},
"dimensions": [
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Reporting and Dashboard Development",
"id": 295,
"rationale": "Building recurring reports and dashboards that track performance over time and across segments. This is a distinct cluster because the analyst must package metrics into reusable views for stakeholders.",
"slug": "reporting-and-dashboard-development",
"source": "db"
},
"input_skill": "Tableau",
"llm_role": null,
"roles_from_db": [
{
"display_name": "Data Analyst",
"id": 20,
"rationale": null,
"role_archetype": null,
"slug": "data-analyst",
"source": "db"
}
]
}
],
"input_skill": "Tableau",
"matched_via": "alias",
"new_alias_persisted": false,
"new_alias_text": null,
"new_skill_meta": null,
"source_tag": "db",
"was_in_llm_skills": false
},
{
"aliases_in_db": [
{
"alias_text": "Argo Workflows",
"alias_type": "CANONICAL",
"id": 595,
"is_primary": true,
"match_strategy": "CASE_INSENSITIVE"
}
],
"canonical": {
"category_id": 11,
"display_name": "Argo Workflows",
"id": 380,
"is_also_category": false,
"is_extractable": true,
"skill_nature": "TOOL",
"slug": "argo-workflows",
"sub_category_id": 335,
"typical_lifespan": "EVERGREEN",
"volatility": "EMERGING"
},
"dimensions": [
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Workflow Orchestration Systems",
"id": 64,
"rationale": "Operational orchestration of ML jobs, dependencies, and handoffs across training, validation, deployment, and retraining. This is a useful split from training pipelines because it emphasizes the scheduler and control plane.",
"slug": "workflow-orchestration-systems",
"source": "db"
},
"input_skill": "Argo Workflows",
"llm_role": null,
"roles_from_db": [
{
"display_name": "Data Engineer",
"id": 6,
"rationale": null,
"role_archetype": null,
"slug": "data-engineer",
"source": "db"
},
{
"display_name": "MLOps Engineer",
"id": 5,
"rationale": null,
"role_archetype": null,
"slug": "mlops-engineer",
"source": "db"
}
]
}
],
"input_skill": "Argo Workflows",
"matched_via": "alias",
"new_alias_persisted": false,
"new_alias_text": null,
"new_skill_meta": null,
"source_tag": "db",
"was_in_llm_skills": false
},
{
"aliases_in_db": [
{
"alias_text": "Power BI",
"alias_type": "CANONICAL",
"id": 2535,
"is_primary": true,
"match_strategy": "CASE_INSENSITIVE"
}
],
"canonical": {
"category_id": 11,
"display_name": "Power BI",
"id": 1884,
"is_also_category": false,
"is_extractable": true,
"skill_nature": "TOOL",
"slug": "power-bi",
"sub_category_id": 1618,
"typical_lifespan": "EVERGREEN",
"volatility": "STABLE"
},
"dimensions": [
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Reporting and Dashboard Development",
"id": 295,
"rationale": "Building recurring reports and dashboards that track performance over time and across segments. This is a distinct cluster because the analyst must package metrics into reusable views for stakeholders.",
"slug": "reporting-and-dashboard-development",
"source": "db"
},
"input_skill": "Power BI",
"llm_role": null,
"roles_from_db": [
{
"display_name": "Data Analyst",
"id": 20,
"rationale": null,
"role_archetype": null,
"slug": "data-analyst",
"source": "db"
}
]
}
],
"input_skill": "Power BI",
"matched_via": "alias",
"new_alias_persisted": false,
"new_alias_text": null,
"new_skill_meta": null,
"source_tag": "db",
"was_in_llm_skills": false
},
{
"aliases_in_db": [],
"canonical": null,
"dimensions": [
{
"dimension": {
"difficulty_hint": null,
"display_name": "API Design and Integration",
"id": null,
"rationale": "Designing, documenting, and consuming application programming interfaces as stable contracts between systems. This fits APIs because the skill centers on defining endpoints, payloads, and integration behavior across services and clients.",
"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",
"endpoints",
"API gateway",
"rate limiting",
"versioning",
"SDK",
"microservices",
"gRPC",
"Postman"
]
},
"maturity": {
"confidence": 0.98,
"maturity": "well_known",
"reasoning": "APIs are a hiring-pipeline staple across backend, mobile, and platform roles; job postings routinely list REST/GraphQL API design and integration as core requirements, and major cloud/vendor docs center on API-first development."
},
"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, documenting, and consuming application programming interfaces as stable contracts between systems. This fits APIs because the skill centers on defining endpoints, payloads, and integration behavior across services and clients.",
"exemplar_skills": [
"APIs",
"REST API design",
"GraphQL",
"API versioning",
"service contracts",
"endpoint design"
],
"in_scope": "APIs, REST APIs, GraphQL APIs, RPC interfaces, endpoint design, request/response schemas, versioning, pagination, error handling, idempotency",
"name": "API Design and Integration",
"out_of_scope": "Client-side UI state, authentication session handling, database schema design, message queue internals, these belong to other dimensions",
"overlap_flags": [
{
"reason": "API work often sits inside broader service architecture, but this dimension is narrower and centered on the interface contract itself.",
"with_dim_id": "service-architecture-and-integration",
"with_dim_name": null,
"with_role": null
},
{
"reason": "Both involve callable interfaces, but that dimension is specific to AI tool 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",
"mock-servers"
],
"requires": [],
"skill_id": "apis",
"suppress_on_match": []
},
"skill_id": "apis",
"split_log": [],
"typed": {
"alternatives_considered": [],
"confidence": 0.91,
"name": "APIs",
"reasoning": "APIs are best treated as a communication interface standard between systems, so under the Protocol vs Standard distinction they fit Protocol rather than a tool or platform.",
"skill_id": "apis",
"subtype": "application_programming_interfaces",
"type": "Protocol"
},
"warnings": []
},
"source_tag": "llm",
"was_in_llm_skills": true
},
{
"aliases_in_db": [],
"canonical": null,
"dimensions": [],
"input_skill": "Acceptance",
"matched_via": null,
"new_alias_persisted": false,
"new_alias_text": null,
"new_skill_meta": {
"derived": {
"category": "Concept",
"skill_nature": "CONCEPT",
"sub_category": "acceptance_concept",
"typical_lifespan": "EVERGREEN",
"version_strategy": "NOT_APPLICABLE",
"volatility": "STABLE"
},
"enrichment": {
"ambiguity": {
"ambiguity_flag": 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",
"definition of done",
"test cases",
"requirements validation",
"stakeholder approval",
"quality assurance",
"release readiness",
"verification",
"validation",
"test plan"
]
},
"maturity": {
"confidence": 0.78,
"maturity": "niche",
"reasoning": "Acceptance is a specialized QA/UAT concept; job postings usually mention it only in test/BA roles, while broader market demand centers on automation tools and frameworks rather than the concept itself."
},
"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": "Dim A and Dim B describe the same conceptual cluster: validating implemented behavior against documented requirements, user stories, and acceptance criteria. The descriptions are effectively identical, and the exemplar skills in Dim A \u2014 especially \"Acceptance criteria review,\" \"User story validation,\" \"Requirements traceability,\" and \"UAT support\" \u2014 all fit the same release/sign-off verification activity described in Dim B. Dim B adds only a clarifying sentence about manual testing starting from product expectations, which does not introduce a distinct skill boundary. There is no evidence of a broader umbrella that should be split, and no meaningful distinction between the two dimensions beyond wording."
}
],
"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",
"defect-retest",
"contract-tests",
"change-requests"
],
"requires": [],
"skill_id": "acceptance",
"suppress_on_match": []
},
"skill_id": "acceptance",
"split_log": [],
"typed": {
"alternatives_considered": [
"Methodology: ruled out \u2014 acceptance is not a way of working like Agile or TDD.",
"SoftSkill: ruled out \u2014 although acceptance can involve interpersonal agreement, the skill name most fundamentally refers to a project/requirements concept."
],
"confidence": 0.78,
"name": "Acceptance",
"reasoning": "By the Concept vs Methodology rule, Acceptance here is best treated as a named knowledge unit about when work is considered complete or approved, rather than a process or tool.",
"skill_id": "acceptance",
"subtype": "acceptance_concept",
"type": "Concept"
},
"warnings": [
"placement_stub_no_locked_dimensions"
]
},
"source_tag": "llm",
"was_in_llm_skills": true
},
{
"aliases_in_db": [],
"canonical": null,
"dimensions": [
{
"dimension": {
"difficulty_hint": null,
"display_name": "Business Intelligence",
"id": null,
"rationale": "Covers the use of data to create reports, dashboards, and decision-support views for business stakeholders. BI belongs here because it commonly refers to the discipline and tooling used to analyze and present operational and strategic metrics.",
"slug": "d_init_01",
"source": "llm"
},
"input_skill": "BI",
"llm_role": null,
"roles_from_db": []
}
],
"input_skill": "BI",
"matched_via": null,
"new_alias_persisted": false,
"new_alias_text": null,
"new_skill_meta": {
"derived": {
"category": "Domain",
"skill_nature": "CONCEPT",
"sub_category": "business_intelligence",
"typical_lifespan": "EVERGREEN",
"version_strategy": "NOT_APPLICABLE",
"volatility": "STABLE"
},
"enrichment": {
"ambiguity": {
"ambiguity_flag": true,
"confused_with": [
"business_intelligence"
],
"reasoning": "\"BI\" is a common abbreviation for business intelligence, but in JDs it can also be read as other acronyms/phrases. A reasonable extractor could confuse it with the fuller business_intelligence skill entry."
},
"context_keywords": {
"context_keywords": [
"dashboards",
"data warehouse",
"ETL",
"OLAP",
"KPI",
"reporting",
"data modeling",
"SQL",
"Tableau",
"Power BI",
"Looker",
"SSRS",
"ad hoc analysis",
"semantic layer",
"star schema"
]
},
"maturity": {
"confidence": 0.92,
"maturity": "well_known",
"reasoning": "BI appears in many job descriptions across analyst, data, and reporting roles; vendors like Microsoft, Tableau, and Power BI have large enterprise adoption, making it a common hiring-pipeline skill."
},
"skill_id": "bi",
"vendor_license": {
"confidence": 0.98,
"license": null,
"vendor": null,
"year_introduced": null
},
"versioning": {
"current_version": null,
"version_aliases": {},
"versioned": false
}
},
"locked_dimensions": [
{
"description": "Covers the use of data to create reports, dashboards, and decision-support views for business stakeholders. BI belongs here because it commonly refers to the discipline and tooling used to analyze and present operational and strategic metrics.",
"exemplar_skills": [
"BI",
"business intelligence",
"dashboard creation",
"KPI reporting",
"ad hoc reporting",
"OLAP analysis",
"self-service analytics"
],
"in_scope": "BI, dashboards, KPI reporting, ad hoc analysis, OLAP, semantic layers, self-service analytics, executive scorecards, report development, data visualization for business users",
"name": "Business Intelligence",
"out_of_scope": "Data engineering pipelines, machine learning model training, statistical experimentation, database administration, these belong to other dimensions focused on data movement, modeling, or platform operations",
"overlap_flags": [
{
"reason": "BI often includes building dashboards and reports, but this catalog dimension is narrower and platform-specific.",
"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 rather than statistical inference.",
"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",
"r"
],
"requires": [],
"skill_id": "bi",
"suppress_on_match": []
},
"skill_id": "bi",
"split_log": [],
"typed": {
"alternatives_considered": [],
"confidence": 0.93,
"name": "BI",
"reasoning": "BI is best classified as a Domain because it denotes the business intelligence problem-space and body of knowledge rather than a specific tool, language, or methodology.",
"skill_id": "bi",
"subtype": "business_intelligence",
"type": "Domain"
},
"warnings": []
},
"source_tag": "llm",
"was_in_llm_skills": true
},
{
"aliases_in_db": [],
"canonical": null,
"dimensions": [
{
"dimension": {
"difficulty_hint": null,
"display_name": "Business Requirements Documents",
"id": null,
"rationale": "Covers creating and maintaining BRDs that capture business goals, scope, stakeholders, constraints, and acceptance expectations. This skill belongs here because BRDs are the primary artifact for translating business needs into structured requirements.",
"slug": "d_init_01",
"source": "llm"
},
"input_skill": "BRDs",
"llm_role": null,
"roles_from_db": []
}
],
"input_skill": "BRDs",
"matched_via": null,
"new_alias_persisted": false,
"new_alias_text": null,
"new_skill_meta": {
"derived": {
"category": "Concept",
"skill_nature": "CONCEPT",
"sub_category": "business_requirements_documents",
"typical_lifespan": "EVERGREEN",
"version_strategy": "NOT_APPLICABLE",
"volatility": "STABLE"
},
"enrichment": {
"ambiguity": {
"ambiguity_flag": false,
"confused_with": [],
"reasoning": "BRDs is a common business-analysis acronym for Business Requirements Documents; in JDs it is usually clear from context and not likely confused with another catalog skill."
},
"context_keywords": {
"context_keywords": [
"requirements gathering",
"stakeholder interviews",
"functional requirements",
"non-functional requirements",
"use cases",
"user stories",
"scope definition",
"acceptance criteria",
"process flows",
"gap analysis",
"business analysis",
"traceability matrix",
"sign-off",
"requirements elicitation",
"solution design"
]
},
"maturity": {
"confidence": 0.86,
"maturity": "well_known",
"reasoning": "BRDs are a standard artifact in business analysis and product roles; job postings commonly ask for business requirements documentation or BRD experience, especially in enterprise and consulting environments."
},
"skill_id": "brds",
"vendor_license": {
"confidence": 0.99,
"license": null,
"vendor": null,
"year_introduced": null
},
"versioning": {
"current_version": null,
"version_aliases": {},
"versioned": false
}
},
"locked_dimensions": [
{
"description": "Covers creating and maintaining BRDs that capture business goals, scope, stakeholders, constraints, and acceptance expectations. This skill belongs here because BRDs are the primary artifact for translating business needs into structured requirements.",
"exemplar_skills": [
"BRDs",
"writing business requirements documents",
"requirements gathering",
"stakeholder analysis",
"scope definition",
"acceptance criteria definition"
],
"in_scope": "BRDs, business requirements documents, requirement gathering, stakeholder interviews, scope definition, business objectives, assumptions, constraints, acceptance criteria, requirement traceability",
"name": "Business Requirements Documents",
"out_of_scope": "Technical design specs, solution architecture, API contracts, which belong to implementation and architecture dimensions; test execution and validation, which belong to requirements-and-acceptance-validation; product roadmaps and prioritization, which belong to product planning",
"overlap_flags": [
{
"reason": "BRDs often feed acceptance validation, but this dimension is about documenting business needs rather than checking implemented behavior.",
"with_dim_id": "requirements-and-acceptance-validation",
"with_dim_name": null,
"with_role": null
},
{
"reason": "BRDs may influence solution design, but architecture owns the technical decomposition and integration choices.",
"with_dim_id": "service-architecture-and-integration",
"with_dim_name": null,
"with_role": null
}
],
"tentative_id": "d_init_01"
}
],
"merge_log": [],
"placed": {
"name": "BRDs",
"placement_confidence": 0.92,
"primary_dimension": "d_init_01",
"reasoning": "Deterministic JD placement: locked_dimensions has 1 dimension(s) from skill-driven dimension generation after reconciliation; primary_dimension is the first locked dim.",
"secondary_dimensions": [],
"skill_id": "brds"
},
"relationships": {
"child_skills": [],
"parent_skills": [],
"related_to": [
"runbooks",
"order-guides",
"catalog-items"
],
"requires": [],
"skill_id": "brds",
"suppress_on_match": []
},
"skill_id": "brds",
"split_log": [],
"typed": {
"alternatives_considered": [],
"confidence": 0.88,
"name": "BRDs",
"reasoning": "BRDs (business requirements documents) are a named knowledge artifact used in requirements gathering, so they fit the Concept category rather than a Methodology or Format.",
"skill_id": "brds",
"subtype": "business_requirements_documents",
"type": "Concept"
},
"warnings": []
},
"source_tag": "llm",
"was_in_llm_skills": true
},
{
"aliases_in_db": [],
"canonical": null,
"dimensions": [
{
"dimension": {
"difficulty_hint": null,
"display_name": "Business Analysis Certification",
"id": null,
"rationale": "Professional certification knowledge for business analysts, including the CBAP credential and the competencies it validates. This belongs here because CBAP is itself a business analysis certification rather than a technical implementation skill.",
"slug": "d_init_01",
"source": "llm"
},
"input_skill": "CBAP",
"llm_role": null,
"roles_from_db": []
}
],
"input_skill": "CBAP",
"matched_via": null,
"new_alias_persisted": false,
"new_alias_text": null,
"new_skill_meta": {
"derived": {
"category": "Certification",
"skill_nature": "CREDENTIAL",
"sub_category": "business_analysis_professional_certification",
"typical_lifespan": "EVERGREEN",
"version_strategy": "NOT_APPLICABLE",
"volatility": "STABLE"
},
"enrichment": {
"ambiguity": {
"ambiguity_flag": false,
"confused_with": [],
"reasoning": "CBAP is a specific certification acronym (Certified Business Analysis Professional) and is unlikely to be mistaken for another catalog skill in typical job descriptions."
},
"context_keywords": {
"context_keywords": [
"BABOK",
"IIBA",
"requirements elicitation",
"stakeholder analysis",
"process modeling",
"use cases",
"user stories",
"gap analysis",
"business process improvement",
"traceability matrix",
"SWOT analysis",
"workshops",
"UML",
"BRD",
"functional requirements"
]
},
"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
}
},
"locked_dimensions": [
{
"description": "Professional certification knowledge for business analysts, including the CBAP credential and the competencies it validates. This belongs here because CBAP is itself a business analysis certification rather than a technical implementation skill.",
"exemplar_skills": [
"CBAP",
"CCBA",
"ECBA",
"BABOK",
"requirements elicitation",
"stakeholder analysis",
"solution assessment"
],
"in_scope": "CBAP, CCBA, ECBA, business analysis certification prep, BABOK knowledge areas, requirements elicitation, stakeholder analysis, solution assessment",
"name": "Business Analysis Certification",
"out_of_scope": "requirements-and-acceptance-validation, project management certification, product management methods, software testing, process automation, technical architecture design",
"overlap_flags": [
{
"reason": "Business analysis certifications often cover validating requirements, but that dimension is about checking implemented behavior rather than certification knowledge.",
"with_dim_id": "requirements-and-acceptance-validation",
"with_dim_name": null,
"with_role": null
}
],
"tentative_id": "d_init_01"
}
],
"merge_log": [],
"placed": {
"name": "CBAP",
"placement_confidence": 0.92,
"primary_dimension": "d_init_01",
"reasoning": "Deterministic JD placement: locked_dimensions has 1 dimension(s) from skill-driven dimension generation after reconciliation; primary_dimension is the first locked dim.",
"secondary_dimensions": [],
"skill_id": "cbap"
},
"relationships": {
"child_skills": [],
"parent_skills": [],
"related_to": [
"risk-based-testing",
"acceptance-criteria-validation",
"acceptance-criteria-checks",
"capacity-planning",
"session-based-testing"
],
"requires": [],
"skill_id": "cbap",
"suppress_on_match": []
},
"skill_id": "cbap",
"split_log": [],
"typed": {
"alternatives_considered": [],
"confidence": 0.98,
"name": "CBAP",
"reasoning": "CBAP is a formal third-party credential, so by the Certification rule it is 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": "Business analysis credentials and the knowledge areas they validate, including requirements elicitation, stakeholder analysis, process modeling, and solution evaluation. CCBA fits here as a recognized business analysis certification rather than a technical implementation skill.",
"slug": "d_init_01",
"source": "llm"
},
"input_skill": "CCBA",
"llm_role": null,
"roles_from_db": []
}
],
"input_skill": "CCBA",
"matched_via": null,
"new_alias_persisted": false,
"new_alias_text": null,
"new_skill_meta": {
"derived": {
"category": "Certification",
"skill_nature": "CREDENTIAL",
"sub_category": "business_analysis_certification",
"typical_lifespan": "EVERGREEN",
"version_strategy": "NOT_APPLICABLE",
"volatility": "STABLE"
},
"enrichment": {
"ambiguity": {
"ambiguity_flag": true,
"confused_with": [
"cbap"
],
"reasoning": "CCBA is a business analysis certification acronym and could be mistaken for the closely related CBAP certification in JDs, 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",
"elicitation techniques",
"requirements management",
"UML",
"SWOT analysis"
]
},
"maturity": {
"confidence": 0.78,
"maturity": "well_known",
"reasoning": "CCBA is a widely recognized business analysis certification; job postings for business analyst roles commonly list IIBA/CCBA alongside CBAP as preferred credentials, indicating steady hiring-pipeline demand."
},
"skill_id": "ccba",
"vendor_license": {
"confidence": 0.93,
"license": null,
"vendor": "International Institute of Business Analysis",
"year_introduced": 2008
},
"versioning": {
"current_version": null,
"version_aliases": {},
"versioned": false
}
},
"locked_dimensions": [
{
"description": "Business analysis credentials and the knowledge areas they validate, including requirements elicitation, stakeholder analysis, process modeling, and solution evaluation. CCBA fits here as a recognized business analysis certification rather than a technical implementation skill.",
"exemplar_skills": [
"CCBA",
"CBAP",
"ECBA",
"BABOK",
"business analysis certification",
"requirements elicitation",
"stakeholder analysis",
"process modeling"
],
"in_scope": "CCBA, CBAP, ECBA, business analysis certification, requirements elicitation, stakeholder analysis, process modeling, solution assessment, BABOK knowledge areas",
"name": "Business Analysis Certification",
"out_of_scope": "Software testing execution, product management strategy, project scheduling, technical system design, data analysis methods; those belong to separate delivery, product, or analytics dimensions",
"overlap_flags": [
{
"reason": "Both touch requirements, but CCBA is about business analysis competency and certification rather than validating implemented behavior.",
"with_dim_id": "requirements-and-acceptance-validation",
"with_dim_name": null,
"with_role": null
}
],
"tentative_id": "d_init_01"
}
],
"merge_log": [],
"placed": {
"name": "CCBA",
"placement_confidence": 0.92,
"primary_dimension": "d_init_01",
"reasoning": "Deterministic JD placement: locked_dimensions has 1 dimension(s) from skill-driven dimension generation after reconciliation; primary_dimension is the first locked dim.",
"secondary_dimensions": [],
"skill_id": "ccba"
},
"relationships": {
"child_skills": [],
"parent_skills": [],
"related_to": [
"scorecards",
"acceptance-criteria-checks",
"acceptance-criteria-validation",
"risk-based-testing",
"charter-based-testing",
"session-based-testing"
],
"requires": [],
"skill_id": "ccba",
"suppress_on_match": []
},
"skill_id": "ccba",
"split_log": [],
"typed": {
"alternatives_considered": [],
"confidence": 0.98,
"name": "CCBA",
"reasoning": "CCBA is a formal third-party credential, so by the Certification rule it is a Certification rather than a concept or methodology.",
"skill_id": "ccba",
"subtype": "business_analysis_certification",
"type": "Certification"
},
"warnings": []
},
"source_tag": "llm",
"was_in_llm_skills": true
},
{
"aliases_in_db": [],
"canonical": null,
"dimensions": [
{
"dimension": {
"difficulty_hint": null,
"display_name": "Spreadsheet Analysis and Modeling",
"id": null,
"rationale": "Using Excel to organize, analyze, and model tabular data for reporting and decision support. This covers formulas, pivots, charts, and workbook structure because Excel is the primary spreadsheet tool for these tasks.",
"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 with a clear JD meaning; typical job descriptions are unlikely to confuse it with another catalog skill."
},
"context_keywords": {
"context_keywords": [
"PivotTables",
"VLOOKUP",
"XLOOKUP",
"INDEX-MATCH",
"Power Query",
"Power Pivot",
"macros",
"VBA",
"data validation",
"conditional formatting",
"charts",
"dashboards",
"SUMIFS",
"COUNTIFS",
"CSV"
]
},
"maturity": {
"confidence": 0.99,
"maturity": "well_known",
"reasoning": "Excel appears in a very large share of business, finance, ops, and analyst job descriptions, and Microsoft continues active support and feature releases via Microsoft 365."
},
"skill_id": "excel",
"vendor_license": {
"confidence": 0.99,
"license": "proprietary",
"vendor": "Microsoft",
"year_introduced": 1985
},
"versioning": {
"current_version": "Microsoft 365 / Excel 2024",
"version_aliases": {
"Excel 2007": "Microsoft 365 / Excel 2024",
"Excel 2010": "Microsoft 365 / Excel 2024",
"Excel 2013": "Microsoft 365 / Excel 2024",
"Excel 2016": "Microsoft 365 / Excel 2024",
"Excel 2019": "Microsoft 365 / Excel 2024",
"Excel 2021": "Microsoft 365 / Excel 2024",
"Excel 2024": "Microsoft 365 / Excel 2024",
"Excel 365": "Microsoft 365 / Excel 2024",
"Microsoft 365 Excel": "Microsoft 365 / Excel 2024"
},
"versioned": true
}
},
"locked_dimensions": [
{
"description": "Using Excel to organize, analyze, and model tabular data for reporting and decision support. This covers formulas, pivots, charts, and workbook structure because Excel is the primary spreadsheet tool for these tasks.",
"exemplar_skills": [
"Excel",
"Microsoft Excel",
"pivot tables in Excel",
"Excel formulas",
"Excel charts",
"Excel data validation",
"Excel lookup functions"
],
"in_scope": "Excel, formulas, functions, pivot tables, charts, conditional formatting, data validation, workbook design, named ranges, lookup functions, what-if analysis",
"name": "Spreadsheet Analysis and Modeling",
"out_of_scope": "SQL querying and database design, statistical inference and experiment design, BI dashboard platforms, programming languages for automation, cloud data pipelines",
"overlap_flags": [
{
"reason": "Excel is often used for basic statistical summaries, but deeper statistical interpretation belongs to statistical reasoning.",
"with_dim_id": "statistical-reasoning-for-analysis",
"with_dim_name": null,
"with_role": null
},
{
"reason": "Excel can produce reports and dashboards, but platform-specific dashboard configuration is a separate skill cluster.",
"with_dim_id": "reporting-and-dashboard-configuration",
"with_dim_name": null,
"with_role": null
}
],
"tentative_id": "d_init_01"
}
],
"merge_log": [],
"placed": {
"name": "Excel",
"placement_confidence": 0.92,
"primary_dimension": "d_init_01",
"reasoning": "Deterministic JD placement: locked_dimensions has 1 dimension(s) from skill-driven dimension generation after reconciliation; primary_dimension is the first locked dim.",
"secondary_dimensions": [],
"skill_id": "excel"
},
"relationships": {
"child_skills": [],
"parent_skills": [],
"related_to": [
"dashboards",
"scorecards",
"summary-statistics",
"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 environment or code package, so by the Tool vs Framework rule it is a Tool.",
"skill_id": "excel",
"subtype": "spreadsheet_software",
"type": "Tool"
},
"warnings": []
},
"source_tag": "llm",
"was_in_llm_skills": true
},
{
"aliases_in_db": [],
"canonical": null,
"dimensions": [
{
"dimension": {
"difficulty_hint": null,
"display_name": "Functional Requirements Documents",
"id": null,
"rationale": "Covers creating, reviewing, and using FRDs that define product behavior, scope, constraints, and acceptance expectations. FRDs belong here because the skill refers to formal requirement artifacts rather than implementation or testing work.",
"slug": "d_init_01",
"source": "llm"
},
"input_skill": "FRDs",
"llm_role": null,
"roles_from_db": []
}
],
"input_skill": "FRDs",
"matched_via": null,
"new_alias_persisted": false,
"new_alias_text": null,
"new_skill_meta": {
"derived": {
"category": "Concept",
"skill_nature": "CONCEPT",
"sub_category": "functional_requirements_document",
"typical_lifespan": "EVERGREEN",
"version_strategy": "NOT_APPLICABLE",
"volatility": "STABLE"
},
"enrichment": {
"ambiguity": {
"ambiguity_flag": false,
"confused_with": [],
"reasoning": "FRDs is a fairly specific requirements-document acronym; in typical JDs it would be read as functional requirements documents, not a different catalog skill."
},
"context_keywords": {
"context_keywords": [
"BRD",
"PRD",
"use cases",
"user stories",
"acceptance criteria",
"requirements traceability",
"scope definition",
"functional specification",
"business requirements",
"stakeholder review",
"sign-off",
"process flows",
"wireframes",
"UAT",
"change requests"
]
},
"maturity": {
"confidence": 0.86,
"maturity": "well_known",
"reasoning": "Functional requirements documents are a standard artifact in software and systems JDs/SDLCs, commonly requested for business analysts, product, and systems roles; no vendor sunset or replacement has displaced them."
},
"skill_id": "frds",
"vendor_license": {
"confidence": 0.98,
"license": null,
"vendor": null,
"year_introduced": null
},
"versioning": {
"current_version": null,
"version_aliases": {},
"versioned": false
}
},
"locked_dimensions": [
{
"description": "Covers creating, reviewing, and using FRDs that define product behavior, scope, constraints, and acceptance expectations. FRDs belong here because the skill refers to formal requirement artifacts rather than implementation or testing work.",
"exemplar_skills": [
"FRDs",
"functional requirements documentation",
"requirements specification writing",
"business requirements analysis",
"acceptance criteria definition"
],
"in_scope": "FRDs, functional requirements documents, requirement specifications, business rules, user-visible behaviors, scope definitions, acceptance criteria, FRD review",
"name": "Functional Requirements Documents",
"out_of_scope": "test cases, test execution, code implementation, API design, project planning, which belong to testing, engineering, or delivery dimensions",
"overlap_flags": [
{
"reason": "FRDs often feed validation work, but this dimension is about authoring the requirement artifact itself rather than checking implementation against it.",
"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",
"risk-based-testing",
"runbooks",
"rollback-readiness"
],
"requires": [],
"skill_id": "frds",
"suppress_on_match": []
},
"skill_id": "frds",
"split_log": [],
"typed": {
"alternatives_considered": [
"Format: ruled out \u2014 although documents have structure, FRDs are primarily a requirements artifact rather than a data structure or wire format.",
"Domain: ruled out \u2014 FRDs are not an industry or problem-space body of knowledge."
],
"confidence": 0.78,
"name": "FRDs",
"reasoning": "FRDs are a named knowledge artifact describing requirements, so by the Concept vs Methodology rule they fit best as a concept rather than a tool or format.",
"skill_id": "frds",
"subtype": "functional_requirements_document",
"type": "Concept"
},
"warnings": []
},
"source_tag": "llm",
"was_in_llm_skills": true
},
{
"aliases_in_db": [],
"canonical": null,
"dimensions": [
{
"dimension": {
"difficulty_hint": null,
"display_name": "Domain Familiarity",
"id": null,
"rationale": "General familiarity with a technical domain, stack, or workflow. This fits when the skill indicates awareness or exposure rather than deep implementation ability.",
"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": "SoftSkill",
"skill_nature": "PRACTICE",
"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 soft-skill term, but it is not a specific technical skill name likely to be confused with another catalog entry in a JD."
},
"context_keywords": {
"context_keywords": [
"domain knowledge",
"working knowledge",
"exposure",
"hands-on experience",
"awareness",
"proficiency",
"acquaintance",
"understanding",
"prior experience",
"subject matter",
"on-the-job",
"practical experience",
"baseline knowledge",
"familiarity with",
"knowledge of"
]
},
"maturity": {
"confidence": 0.86,
"maturity": "niche",
"reasoning": "\u201cFamiliarity\u201d is a generic soft-skill label, not a standardized hiring keyword; JD searches usually specify concrete tools or competencies instead, so market signal is low-volume and inconsistent."
},
"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 familiarity with a technical domain, stack, or workflow. This fits when the skill indicates awareness or exposure rather than deep implementation ability.",
"exemplar_skills": [
"Familiarity",
"Working knowledge",
"Awareness of concepts",
"Exposure to the stack",
"Basic understanding"
],
"in_scope": "Familiarity, working knowledge, awareness of concepts, exposure to tools and workflows, basic recognition of terminology, introductory understanding of domain practices",
"name": "Domain Familiarity",
"out_of_scope": "Deep implementation expertise, architecture design, debugging, or hands-on coding; those belong in specific technical dimensions such as programming, service architecture, or testing",
"overlap_flags": [
{
"reason": "Familiarity can be a shallow indicator of backend architecture exposure, but deeper service design belongs there.",
"with_dim_id": "service-architecture-and-integration",
"with_dim_name": null,
"with_role": null
},
{
"reason": "Familiarity may refer to language exposure, while actual coding proficiency belongs in the language-specific dimension.",
"with_dim_id": "programming-languages-for-backend-systems",
"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.88,
"name": "Familiarity",
"reasoning": "Familiarity is a non-technical interpersonal/working capability rather than a technical artifact, so it best fits the SoftSkill category.",
"skill_id": "familiarity",
"subtype": "familiarity",
"type": "SoftSkill"
},
"warnings": []
},
"source_tag": "llm",
"was_in_llm_skills": true
},
{
"aliases_in_db": [],
"canonical": null,
"dimensions": [
{
"dimension": {
"difficulty_hint": null,
"display_name": "Knowledge Representation",
"id": null,
"rationale": "Represents structured knowledge used by AI systems to store, retrieve, and reason over facts, concepts, and relationships. The target skill fits here because it refers to the knowledge layer itself rather than a specific model or retrieval mechanism.",
"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 generic term in JDs and could easily refer to knowledge management, knowledge graphs, or a knowledge base rather than a distinct skill concept."
},
"context_keywords": {
"context_keywords": [
"domain expertise",
"subject matter expert",
"best practices",
"business acumen",
"institutional knowledge",
"knowledge base",
"knowledge management",
"knowledge transfer",
"lessons learned",
"documentation",
"training materials",
"onboarding",
"process knowledge",
"expertise",
"reference materials"
]
},
"maturity": {
"confidence": 0.94,
"maturity": "niche",
"reasoning": "\u201cKnowledge\u201d is a generic concept, not a specific engineering skill; it rarely appears as a standalone JD requirement, unlike concrete tools or languages. Market signal is effectively near-zero direct hiring demand."
},
"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": "Represents structured knowledge used by AI systems to store, retrieve, and reason over facts, concepts, and relationships. The target skill fits here because it refers to the knowledge layer itself rather than a specific model or retrieval mechanism.",
"exemplar_skills": [
"Knowledge",
"Knowledge graphs",
"Ontologies",
"Taxonomies",
"Semantic networks",
"Knowledge bases"
],
"in_scope": "Knowledge, knowledge graphs, ontologies, taxonomies, semantic networks, entity relationships, symbolic facts, structured domain knowledge, knowledge bases, schema design for knowledge",
"name": "Knowledge Representation",
"out_of_scope": "Vector embeddings and similarity search, document retrieval pipelines, prompt engineering, model training, database administration",
"overlap_flags": [
{
"reason": "Knowledge systems may be exposed through services, but the dimension here is the knowledge model itself rather than service integration.",
"with_dim_id": "service-architecture-and-integration",
"with_dim_name": null,
"with_role": null
},
{
"reason": "Models can use knowledge via tools, but tool invocation is a separate capability from representing knowledge.",
"with_dim_id": "tool-use-and-function-calling",
"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 or a system shape, so under 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": "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 roles; a catalog extractor could confuse this soft-skill label with the more explicit quality_assurance skill."
},
"context_keywords": {
"context_keywords": [
"test cases",
"test plans",
"regression testing",
"defect tracking",
"bug triage",
"UAT",
"test automation",
"Selenium",
"JIRA",
"manual testing",
"acceptance criteria",
"traceability matrix",
"smoke testing",
"test scripts",
"quality metrics"
]
},
"maturity": {
"confidence": 0.96,
"maturity": "well_known",
"reasoning": "QA is a standard hiring requirement across software JDs, with broad demand for test planning, defect tracking, and automation; it appears in large volumes on job boards and ATS filters."
},
"skill_id": "qa",
"vendor_license": {
"confidence": 0.99,
"license": null,
"vendor": null,
"year_introduced": null
},
"versioning": {
"current_version": null,
"version_aliases": {},
"versioned": false
}
},
"locked_dimensions": [],
"merge_log": [
{
"into": "d_merge_01",
"into_name": "Requirements and Acceptance Validation",
"merged_from": [
"d_init_01",
"requirements-and-acceptance-validation"
],
"reasoning": "Dim A and Dim B describe the same conceptual cluster with nearly identical wording and scope: both are about checking implemented behavior against documented requirements, user stories, and acceptance criteria. Dim A\u2019s exemplars (QA, acceptance testing, manual testing, exploratory testing, regression validation) all fit exactly within Dim B\u2019s description of manual verification against what the product is supposed to do. There is no evidence of a narrower sub-split or a distinct adjacent skill area; the cosine similarity is high because the definitions are effectively duplicates, not merely overlapping neighbors."
}
],
"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": [
"Methodology: ruled out \u2014 QA is broader than a specific process like TDD or Scrum.",
"Concept: ruled out \u2014 it is not primarily a theory or principle, but an operational practice area."
],
"confidence": 0.67,
"name": "QA",
"reasoning": "QA is best treated as a quality-assurance practice/role-related capability rather than a software artifact, and under the Concept vs Methodology rule it fits a way of working more than a knowledge unit.",
"skill_id": "qa",
"subtype": "quality_assurance",
"type": "SoftSkill"
},
"warnings": [
"placement_stub_no_locked_dimensions"
]
},
"source_tag": "llm",
"was_in_llm_skills": true
},
{
"aliases_in_db": [],
"canonical": null,
"dimensions": [
{
"dimension": {
"difficulty_hint": null,
"display_name": "Software Development Lifecycle",
"id": null,
"rationale": "Covers the end-to-end process of planning, building, testing, releasing, and maintaining software. SDLC belongs here because it refers to the overall lifecycle framework rather than a single technical subskill.",
"slug": "d_init_01",
"source": "llm"
},
"input_skill": "SDLC",
"llm_role": null,
"roles_from_db": []
}
],
"input_skill": "SDLC",
"matched_via": null,
"new_alias_persisted": false,
"new_alias_text": null,
"new_skill_meta": {
"derived": {
"category": "Methodology",
"skill_nature": "METHODOLOGY",
"sub_category": "software_development_lifecycle",
"typical_lifespan": "EVERGREEN",
"version_strategy": "NOT_APPLICABLE",
"volatility": "STABLE"
},
"enrichment": {
"ambiguity": {
"ambiguity_flag": false,
"confused_with": [],
"reasoning": "SDLC is a standard, well-established 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",
"release management",
"deployment",
"CI/CD",
"Agile",
"Scrum",
"waterfall",
"change management",
"defect tracking"
]
},
"maturity": {
"confidence": 0.93,
"maturity": "well_known",
"reasoning": "SDLC is a standard term in software job descriptions and enterprise process docs, with widespread use across Agile, Waterfall, and DevOps hiring pipelines."
},
"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 of planning, building, testing, releasing, and maintaining software. SDLC belongs here because it refers to the overall lifecycle framework rather than a single technical subskill.",
"exemplar_skills": [
"SDLC",
"software development lifecycle",
"requirements analysis",
"code review",
"release management",
"change control"
],
"in_scope": "SDLC, requirements gathering, design, implementation, code review, testing, release management, maintenance, change control, versioning, deployment planning",
"name": "Software Development Lifecycle",
"out_of_scope": "Specific test automation frameworks, CI/CD tooling, application architecture patterns, incident response, database administration, which are owned by more specialized dimensions",
"overlap_flags": [
{
"reason": "SDLC often includes validation activities, but that catalog dimension focuses specifically on checking implemented behavior against acceptance criteria.",
"with_dim_id": "requirements-and-acceptance-validation",
"with_dim_name": null,
"with_role": null
},
{
"reason": "SDLC can include release steps, but that dimension is narrower and focused on producing shippable iOS builds.",
"with_dim_id": "build-configuration-and-release",
"with_dim_name": null,
"with_role": null
}
],
"tentative_id": "d_init_01"
}
],
"merge_log": [],
"placed": {
"name": "SDLC",
"placement_confidence": 0.92,
"primary_dimension": "d_init_01",
"reasoning": "Deterministic JD placement: locked_dimensions has 1 dimension(s) from skill-driven dimension generation after reconciliation; primary_dimension is the first locked dim.",
"secondary_dimensions": [],
"skill_id": "sdlc"
},
"relationships": {
"child_skills": [],
"parent_skills": [],
"related_to": [
"clean-architecture",
"acceptance-criteria-checks",
"acceptance-criteria-validation",
"defect-retest",
"dependency-mapping",
"dashboards",
"scorecards"
],
"requires": [],
"skill_id": "sdlc",
"suppress_on_match": []
},
"skill_id": "sdlc",
"split_log": [],
"typed": {
"alternatives_considered": [
"Concept: ruled out \u2014 SDLC is not just a knowledge unit but a way of working.",
"Architecture: ruled out \u2014 it does not describe a system shape or structural pattern."
],
"confidence": 0.88,
"name": "SDLC",
"reasoning": "SDLC is best treated as a Methodology because it describes the process and phases for how software is developed and delivered, matching the Concept vs Methodology rule.",
"skill_id": "sdlc",
"subtype": "software_development_lifecycle",
"type": "Methodology"
},
"warnings": []
},
"source_tag": "llm",
"was_in_llm_skills": true
},
{
"aliases_in_db": [],
"canonical": null,
"dimensions": [
{
"dimension": {
"difficulty_hint": null,
"display_name": "SaaS Product Delivery",
"id": null,
"rationale": "Covers building, packaging, and operating software delivered as a hosted subscription service. SaaS belongs here because it refers to the delivery model and the product/operational concerns that make a service usable by many customers over time.",
"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",
"web app",
"cloud-hosted",
"SAML",
"SSO",
"RBAC",
"usage-based pricing",
"customer provisioning",
"admin console",
"API integrations",
"trial conversion",
"churn"
]
},
"maturity": {
"confidence": 0.96,
"maturity": "well_known",
"reasoning": "SaaS is a standard deployment model across most software JDs and vendor ecosystems; cloud job postings routinely list building or integrating SaaS products, and major vendors like Salesforce, Microsoft 365, and ServiceNow anchor the market."
},
"skill_id": "saas",
"vendor_license": {
"confidence": 0.88,
"license": null,
"vendor": null,
"year_introduced": 1999
},
"versioning": {
"current_version": null,
"version_aliases": {},
"versioned": false
}
},
"locked_dimensions": [
{
"description": "Covers building, packaging, and operating software delivered as a hosted subscription service. SaaS belongs here because it refers to the delivery model and the product/operational concerns that make a service usable by many customers over time.",
"exemplar_skills": [
"SaaS",
"multi-tenant architecture",
"subscription software",
"hosted application delivery",
"tenant isolation",
"customer onboarding"
],
"in_scope": "SaaS, multi-tenant application delivery, subscription software, hosted web application, tenant isolation, customer onboarding, service availability, usage-based access, admin consoles, release management for hosted products",
"name": "SaaS Product Delivery",
"out_of_scope": "On-premises software deployment, mobile app distribution, internal developer tooling, data warehouse analytics, which belong to other product or platform dimensions",
"overlap_flags": [
{
"reason": "SaaS products are often implemented as services, but this dimension is about the delivery model and tenant/customer operation rather than service decomposition.",
"with_dim_id": "service-architecture-and-integration",
"with_dim_name": null,
"with_role": null
},
{
"reason": "SaaS solutions frequently rely on cloud services, but selecting infrastructure is distinct from the SaaS product model itself.",
"with_dim_id": "cloud-platform-service-selection",
"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",
"cspm",
"policy-as-code",
"cloud-reference-architecture"
],
"requires": [],
"skill_id": "saas",
"suppress_on_match": []
},
"skill_id": "saas",
"split_log": [],
"typed": {
"alternatives_considered": [],
"confidence": 0.9,
"name": "SaaS",
"reasoning": "By the Platform vs Tool rule, SaaS is a hosted multi-tenant environment delivered over APIs and managed services rather than software you run yourself.",
"skill_id": "saas",
"subtype": "software_as_a_service_platform",
"type": "Platform"
},
"warnings": []
},
"source_tag": "llm",
"was_in_llm_skills": true
},
{
"aliases_in_db": [],
"canonical": null,
"dimensions": [
{
"dimension": {
"difficulty_hint": null,
"display_name": "General Software Testing",
"id": null,
"rationale": "Testing practices used to verify that software behaves as intended across manual and automated checks. This is the best fit for the standalone skill \"Testing\" when no narrower layer such as frontend, backend, or acceptance validation is specified.",
"slug": "d_init_01",
"source": "llm"
},
"input_skill": "Testing",
"llm_role": null,
"roles_from_db": []
}
],
"input_skill": "Testing",
"matched_via": null,
"new_alias_persisted": false,
"new_alias_text": null,
"new_skill_meta": {
"derived": {
"category": "Methodology",
"skill_nature": "METHODOLOGY",
"sub_category": "software_testing_methodology",
"typical_lifespan": "EVERGREEN",
"version_strategy": "NOT_APPLICABLE",
"volatility": "STABLE"
},
"enrichment": {
"ambiguity": {
"ambiguity_flag": false,
"confused_with": [],
"reasoning": "In JDs, \"testing\" usually clearly means software testing methodology. It\u2019s broad, but not typically confused with a distinct catalog skill in a way that would mislead extraction."
},
"context_keywords": {
"context_keywords": [
"unit testing",
"integration testing",
"test automation",
"regression testing",
"smoke testing",
"test cases",
"test suite",
"mocking",
"stubbing",
"assertions",
"TDD",
"BDD",
"pytest",
"JUnit",
"Selenium"
]
},
"maturity": {
"confidence": 0.97,
"maturity": "well_known",
"reasoning": "Software testing is a standard requirement in most engineering JDs and appears across QA, SDET, and developer roles; CI/CD tooling and frameworks like pytest, JUnit, and Playwright reinforce broad market adoption."
},
"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": [
{
"description": "Testing practices used to verify that software behaves as intended across manual and automated checks. This is the best fit for the standalone skill \"Testing\" when no narrower layer such as frontend, backend, or acceptance validation is specified.",
"exemplar_skills": [
"Testing",
"manual testing",
"exploratory testing",
"regression testing",
"smoke testing",
"test case design"
],
"in_scope": "Testing, test planning, test case design, manual testing, exploratory testing, regression testing, smoke testing, sanity testing, Testing of software behavior",
"name": "General Software Testing",
"out_of_scope": "Frontend component testing, backend unit test implementation, acceptance criteria validation, performance testing, security testing, which belong to more specialized quality dimensions",
"overlap_flags": [
{
"reason": "If the skill refers specifically to UI, component, or end-to-end browser testing, that catalog dimension is a better fit.",
"with_dim_id": "frontend-testing-and-quality",
"with_dim_name": null,
"with_role": null
},
{
"reason": "If the skill is about checking implemented behavior against user stories or acceptance criteria, that dimension may be more precise.",
"with_dim_id": "requirements-and-acceptance-validation",
"with_dim_name": null,
"with_role": null
}
],
"tentative_id": "d_init_01"
}
],
"merge_log": [],
"placed": {
"name": "Testing",
"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": "testing"
},
"relationships": {
"child_skills": [],
"parent_skills": [],
"related_to": [
"risk-based-testing",
"session-based-testing",
"cross-browser-testing",
"smoke-testing",
"fuzzing",
"charter-based-testing"
],
"requires": [],
"skill_id": "testing",
"suppress_on_match": []
},
"skill_id": "testing",
"split_log": [],
"typed": {
"alternatives_considered": [],
"confidence": 0.91,
"name": "Testing",
"reasoning": "Testing is fundamentally a way of working for validating software behavior, so by the Concept vs Methodology rule it fits Methodology rather than a tool or concept.",
"skill_id": "testing",
"subtype": "software_testing_methodology",
"type": "Methodology"
},
"warnings": []
},
"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 not typically confused with another catalog skill."
},
"context_keywords": {
"context_keywords": [
"test cases",
"acceptance criteria",
"business users",
"end users",
"test scripts",
"sign-off",
"test plan",
"defect triage",
"test scenarios",
"regression testing",
"stakeholder review",
"go-live",
"test execution",
"requirements validation"
]
},
"maturity": {
"confidence": 0.86,
"maturity": "well_known",
"reasoning": "UAT appears routinely in QA/BA job descriptions and enterprise delivery checklists as a standard pre-release gate for user sign-off, indicating broad hiring-market familiarity."
},
"skill_id": "uat",
"vendor_license": {
"confidence": 0.99,
"license": null,
"vendor": null,
"year_introduced": null
},
"versioning": {
"current_version": null,
"version_aliases": {},
"versioned": false
}
},
"locked_dimensions": [],
"merge_log": [
{
"into": "d_merge_01",
"into_name": "Requirements and Acceptance Validation",
"merged_from": [
"d_init_01",
"requirements-and-acceptance-validation"
],
"reasoning": "Both dimensions describe the same cluster: validating delivered behavior against requirements, user stories, and acceptance criteria. Dim A explicitly includes UAT, acceptance criteria verification, requirements traceability, stakeholder review, and end-user validation. Dim B says essentially the same thing\u2014checking implemented behavior matches documented requirements and acceptance criteria\u2014and its manual-testing framing aligns with A\u2019s UAT/sign-off focus. There is no distinct skill boundary here."
}
],
"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": "Conceptual Understanding",
"id": null,
"rationale": "Broad comprehension of a domain, system, or process well enough to explain how it works and why it behaves a certain way. This skill is too generic to map cleanly to a narrower catalog dimension, so it is treated as a standalone conceptual dimension.",
"slug": "d_init_01",
"source": "llm"
},
"input_skill": "Understanding",
"llm_role": null,
"roles_from_db": []
}
],
"input_skill": "Understanding",
"matched_via": null,
"new_alias_persisted": false,
"new_alias_text": null,
"new_skill_meta": {
"derived": {
"category": "Concept",
"skill_nature": "CONCEPT",
"sub_category": "comprehension",
"typical_lifespan": "EVERGREEN",
"version_strategy": "NOT_APPLICABLE",
"volatility": "STABLE"
},
"enrichment": {
"ambiguity": {
"ambiguity_flag": true,
"confused_with": [
"understanding_requirements",
"understanding_customer_needs"
],
"reasoning": "\"Understanding\" is a generic noun in JDs and could easily refer to related catalog concepts like understanding requirements or customer needs rather than a distinct skill."
},
"context_keywords": {
"context_keywords": [
"requirements analysis",
"stakeholder needs",
"problem framing",
"domain knowledge",
"root cause analysis",
"user stories",
"acceptance criteria",
"specification",
"gap analysis",
"critical thinking",
"systems thinking",
"inference",
"interpretation",
"ambiguity",
"contextual reasoning"
]
},
"maturity": {
"confidence": 0.93,
"maturity": "well_known",
"reasoning": "Broadly expected in job descriptions across engineering roles; comprehension/understanding is a baseline interview and performance criterion rather than a niche tool skill."
},
"skill_id": "understanding",
"vendor_license": {
"confidence": 0.99,
"license": null,
"vendor": null,
"year_introduced": null
},
"versioning": {
"current_version": null,
"version_aliases": {},
"versioned": false
}
},
"locked_dimensions": [
{
"description": "Broad comprehension of a domain, system, or process well enough to explain how it works and why it behaves a certain way. This skill is too generic to map cleanly to a narrower catalog dimension, so it is treated as a standalone conceptual dimension.",
"exemplar_skills": [
"Understanding",
"Conceptual understanding",
"Domain understanding",
"System understanding",
"Grasping requirements",
"Interpreting behavior"
],
"in_scope": "Understanding, conceptual understanding, domain understanding, system understanding, grasping requirements, interpreting behavior, explaining relationships, recognizing dependencies, understanding tradeoffs",
"name": "Conceptual Understanding",
"out_of_scope": "Deep implementation skills, debugging and crash analysis, architecture design, statistical analysis, or operational procedures; those belong to more specific engineering dimensions.",
"overlap_flags": [
{
"reason": "Understanding can support checking requirements, but that dimension is about verifying implemented behavior against acceptance criteria.",
"with_dim_id": "requirements-and-acceptance-validation",
"with_dim_name": null,
"with_role": null
},
{
"reason": "Understanding may apply to backend systems, but this dimension is specifically about service decomposition and integration patterns.",
"with_dim_id": "service-architecture-and-integration",
"with_dim_name": null,
"with_role": null
}
],
"tentative_id": "d_init_01"
}
],
"merge_log": [],
"placed": {
"name": "Understanding",
"placement_confidence": 0.92,
"primary_dimension": "d_init_01",
"reasoning": "Deterministic JD placement: locked_dimensions has 1 dimension(s) from skill-driven dimension generation after reconciliation; primary_dimension is the first locked dim.",
"secondary_dimensions": [],
"skill_id": "understanding"
},
"relationships": {
"child_skills": [],
"parent_skills": [],
"related_to": [],
"requires": [],
"skill_id": "understanding",
"suppress_on_match": []
},
"skill_id": "understanding",
"split_log": [],
"typed": {
"alternatives_considered": [],
"confidence": 0.97,
"name": "Understanding",
"reasoning": "Understanding is a named knowledge unit rather than a way of working, so by the Concept vs Methodology rule it fits Concept.",
"skill_id": "understanding",
"subtype": "comprehension",
"type": "Concept"
},
"warnings": []
},
"source_tag": "llm",
"was_in_llm_skills": true
},
{
"aliases_in_db": [],
"canonical": null,
"dimensions": [
{
"dimension": {
"difficulty_hint": null,
"display_name": "Diagramming and Process Modeling",
"id": null,
"rationale": "Creating clear visual diagrams for systems, workflows, and business processes. Visio belongs here because it is a general-purpose diagramming tool used to model flows, relationships, and structured documentation.",
"slug": "d_init_01",
"source": "llm"
},
"input_skill": "Visio",
"llm_role": null,
"roles_from_db": []
}
],
"input_skill": "Visio",
"matched_via": null,
"new_alias_persisted": false,
"new_alias_text": null,
"new_skill_meta": {
"derived": {
"category": "Tool",
"skill_nature": "TOOL",
"sub_category": "diagramming_tool",
"typical_lifespan": "EVERGREEN",
"version_strategy": "NOT_APPLICABLE",
"volatility": "STABLE"
},
"enrichment": {
"ambiguity": {
"ambiguity_flag": false,
"confused_with": [],
"reasoning": "Visio is a specific Microsoft diagramming tool; in typical JDs it is unlikely to be confused with another catalog skill."
},
"context_keywords": {
"context_keywords": [
"process flow",
"swimlane",
"workflow diagram",
"org chart",
"network diagram",
"UML",
"BPMN",
"data flow diagram",
"floor plan",
"cross-functional flowchart",
"stencil",
"shapes",
"connector",
"blueprint",
"schematic"
]
},
"maturity": {
"confidence": 0.86,
"maturity": "well_known",
"reasoning": "Common in enterprise JDs for process/network diagrams and Microsoft 365 environments; Microsoft continues to support and market Visio rather than sunset it."
},
"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 clear visual diagrams for systems, workflows, and business processes. Visio belongs here because it is a general-purpose diagramming tool used to model flows, relationships, and structured documentation.",
"exemplar_skills": [
"Visio",
"flowchart creation",
"process mapping",
"swimlane diagramming",
"UML diagramming"
],
"in_scope": "Visio, flowcharts, process maps, swimlane diagrams, org charts, block diagrams, UML sketches, BPMN diagrams, system diagrams",
"name": "Diagramming and Process Modeling",
"out_of_scope": "Hands-on implementation of software, network device configuration, and formal architecture review, which belong to engineering or domain-specific design dimensions.",
"overlap_flags": [
{
"reason": "Visio is frequently used for network and infrastructure diagrams, so some usage overlaps with documentation standards for technical environments.",
"with_dim_id": "network-documentation-and-standards",
"with_dim_name": null,
"with_role": null
},
{
"reason": "Visio diagrams can support security architecture review, but the analytical review work itself is a separate dimension.",
"with_dim_id": "security-architecture-review",
"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 run to create diagrams, so by the Tool vs Framework rule it is a Tool rather than a Framework or Platform.",
"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": "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": "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": "tools",
"matched_via": null,
"new_alias_persisted": false,
"new_alias_text": null,
"new_skill_meta": null,
"source_tag": "llm",
"was_in_llm_skills": true
},
{
"aliases_in_db": [],
"canonical": null,
"dimensions": [],
"input_skill": "trends",
"matched_via": null,
"new_alias_persisted": false,
"new_alias_text": null,
"new_skill_meta": null,
"source_tag": "llm",
"was_in_llm_skills": true
},
{
"aliases_in_db": [],
"canonical": null,
"dimensions": [],
"input_skill": "workshops",
"matched_via": null,
"new_alias_persisted": false,
"new_alias_text": null,
"new_skill_meta": null,
"source_tag": "llm",
"was_in_llm_skills": true
}
],
"unmatched_skills": [
"APIs",
"Acceptance",
"BI",
"BRDs",
"CBAP",
"CCBA",
"Excel",
"FRDs",
"Familiarity",
"Knowledge",
"QA",
"SDLC",
"SaaS",
"Testing",
"UAT",
"Understanding",
"Visio"
]
}
API 3 — final-role-output
{
"chosen_role": {
"display_name": "Data Engineer",
"id": 6,
"rationale": "The strongest repeated DB evidence is for Data Engineer across workflow orchestration and the broader technical/API dimension, while reporting tools only support Data Analyst.",
"role_archetype": null,
"slug": "data-engineer",
"source": "db"
},
"final_input_skills": [
{
"skill": "Tableau",
"tag": "in_db"
},
{
"skill": "Argo Workflows",
"tag": "in_db"
},
{
"skill": "Power BI",
"tag": "in_db"
},
{
"skill": "APIs",
"tag": "new"
},
{
"skill": "Acceptance",
"tag": "new"
},
{
"skill": "BI",
"tag": "new"
},
{
"skill": "BRDs",
"tag": "new"
},
{
"skill": "CBAP",
"tag": "new"
},
{
"skill": "CCBA",
"tag": "new"
},
{
"skill": "Excel",
"tag": "new"
},
{
"skill": "FRDs",
"tag": "new"
},
{
"skill": "Familiarity",
"tag": "new"
},
{
"skill": "Knowledge",
"tag": "new"
},
{
"skill": "QA",
"tag": "new"
},
{
"skill": "SDLC",
"tag": "new"
},
{
"skill": "SaaS",
"tag": "new"
},
{
"skill": "Testing",
"tag": "new"
},
{
"skill": "UAT",
"tag": "new"
},
{
"skill": "Understanding",
"tag": "new"
},
{
"skill": "Visio",
"tag": "new"
},
{
"skill": "analysis",
"tag": "new"
},
{
"skill": "data",
"tag": "new"
},
{
"skill": "databases",
"tag": "new"
},
{
"skill": "documentation",
"tag": "new"
},
{
"skill": "fintech",
"tag": "new"
},
{
"skill": "healthcare",
"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": "tools",
"tag": "new"
},
{
"skill": "trends",
"tag": "new"
},
{
"skill": "workshops",
"tag": "new"
}
],
"persistence": {
"items": [
{
"chosen_role_id": 6,
"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": 6,
"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": true,
"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": 6,
"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": 6,
"dimension": {
"difficulty_hint": null,
"display_name": "API Design and Integration",
"id": null,
"rationale": "Designing, documenting, and consuming application programming interfaces as stable contracts between systems. This fits APIs because the skill centers on defining endpoints, payloads, and integration behavior across services and clients.",
"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": 6,
"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 belongs here because it commonly refers to the discipline and tooling used to analyze and present operational and strategic metrics.",
"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": 6,
"dimension": {
"difficulty_hint": null,
"display_name": "Business Requirements Documents",
"id": null,
"rationale": "Covers creating and maintaining BRDs that capture business goals, scope, stakeholders, constraints, and acceptance expectations. This skill belongs here because BRDs are the primary artifact for translating business needs into structured requirements.",
"slug": "d_init_01",
"source": "llm"
},
"dimension_id": null,
"input_skill": "BRDs",
"llm_role": null,
"matched_chosen_role": false,
"role_dimension_saved": false,
"roles_from_db": [],
"skill_dimension_saved": false,
"skill_id": null,
"skill_tag": "new",
"skipped_reason": "skill_not_in_db_v3_proposed"
},
{
"chosen_role_id": 6,
"dimension": {
"difficulty_hint": null,
"display_name": "Business Analysis Certification",
"id": null,
"rationale": "Professional certification knowledge for business analysts, including the CBAP credential and the competencies it validates. This belongs here because CBAP is itself a business analysis certification rather than a technical implementation skill.",
"slug": "d_init_01",
"source": "llm"
},
"dimension_id": null,
"input_skill": "CBAP",
"llm_role": null,
"matched_chosen_role": false,
"role_dimension_saved": false,
"roles_from_db": [],
"skill_dimension_saved": false,
"skill_id": null,
"skill_tag": "new",
"skipped_reason": "skill_not_in_db_v3_proposed"
},
{
"chosen_role_id": 6,
"dimension": {
"difficulty_hint": null,
"display_name": "Business Analysis Certification",
"id": null,
"rationale": "Business analysis credentials and the knowledge areas they validate, including requirements elicitation, stakeholder analysis, process modeling, and solution evaluation. CCBA fits here as a recognized business analysis certification rather than a technical implementation skill.",
"slug": "d_init_01",
"source": "llm"
},
"dimension_id": null,
"input_skill": "CCBA",
"llm_role": null,
"matched_chosen_role": false,
"role_dimension_saved": false,
"roles_from_db": [],
"skill_dimension_saved": false,
"skill_id": null,
"skill_tag": "new",
"skipped_reason": "skill_not_in_db_v3_proposed"
},
{
"chosen_role_id": 6,
"dimension": {
"difficulty_hint": null,
"display_name": "Spreadsheet Analysis and Modeling",
"id": null,
"rationale": "Using Excel to organize, analyze, and model tabular data for reporting and decision support. This covers formulas, pivots, charts, and workbook structure because Excel is the primary spreadsheet tool for these tasks.",
"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": 6,
"dimension": {
"difficulty_hint": null,
"display_name": "Functional Requirements Documents",
"id": null,
"rationale": "Covers creating, reviewing, and using FRDs that define product behavior, scope, constraints, and acceptance expectations. FRDs belong here because the skill refers to formal requirement artifacts rather than implementation or testing work.",
"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": 6,
"dimension": {
"difficulty_hint": null,
"display_name": "Domain Familiarity",
"id": null,
"rationale": "General familiarity with a technical domain, stack, or workflow. This fits when the skill indicates awareness or exposure rather than deep implementation ability.",
"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": 6,
"dimension": {
"difficulty_hint": null,
"display_name": "Knowledge Representation",
"id": null,
"rationale": "Represents structured knowledge used by AI systems to store, retrieve, and reason over facts, concepts, and relationships. The target skill fits here because it refers to the knowledge layer itself rather than a specific model or retrieval mechanism.",
"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": 6,
"dimension": {
"difficulty_hint": null,
"display_name": "Software Development Lifecycle",
"id": null,
"rationale": "Covers the end-to-end process of planning, building, testing, releasing, and maintaining software. SDLC belongs here because it refers to the overall lifecycle framework rather than a single technical subskill.",
"slug": "d_init_01",
"source": "llm"
},
"dimension_id": null,
"input_skill": "SDLC",
"llm_role": null,
"matched_chosen_role": false,
"role_dimension_saved": false,
"roles_from_db": [],
"skill_dimension_saved": false,
"skill_id": null,
"skill_tag": "new",
"skipped_reason": "skill_not_in_db_v3_proposed"
},
{
"chosen_role_id": 6,
"dimension": {
"difficulty_hint": null,
"display_name": "SaaS Product Delivery",
"id": null,
"rationale": "Covers building, packaging, and operating software delivered as a hosted subscription service. SaaS belongs here because it refers to the delivery model and the product/operational concerns that make a service usable by many customers over time.",
"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": 6,
"dimension": {
"difficulty_hint": null,
"display_name": "General Software Testing",
"id": null,
"rationale": "Testing practices used to verify that software behaves as intended across manual and automated checks. This is the best fit for the standalone skill \"Testing\" when no narrower layer such as frontend, backend, or acceptance validation is specified.",
"slug": "d_init_01",
"source": "llm"
},
"dimension_id": null,
"input_skill": "Testing",
"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": 6,
"dimension": {
"difficulty_hint": null,
"display_name": "Conceptual Understanding",
"id": null,
"rationale": "Broad comprehension of a domain, system, or process well enough to explain how it works and why it behaves a certain way. This skill is too generic to map cleanly to a narrower catalog dimension, so it is treated as a standalone conceptual dimension.",
"slug": "d_init_01",
"source": "llm"
},
"dimension_id": null,
"input_skill": "Understanding",
"llm_role": null,
"matched_chosen_role": false,
"role_dimension_saved": false,
"roles_from_db": [],
"skill_dimension_saved": false,
"skill_id": null,
"skill_tag": "new",
"skipped_reason": "skill_not_in_db_v3_proposed"
},
{
"chosen_role_id": 6,
"dimension": {
"difficulty_hint": null,
"display_name": "Diagramming and Process Modeling",
"id": null,
"rationale": "Creating clear visual diagrams for systems, workflows, and business processes. Visio belongs here because it is a general-purpose diagramming tool used to model flows, relationships, and structured documentation.",
"slug": "d_init_01",
"source": "llm"
},
"dimension_id": null,
"input_skill": "Visio",
"llm_role": null,
"matched_chosen_role": false,
"role_dimension_saved": false,
"roles_from_db": [],
"skill_dimension_saved": false,
"skill_id": null,
"skill_tag": "new",
"skipped_reason": "skill_not_in_db_v3_proposed"
}
],
"new_skills_created": 0,
"role_dimension_saved": 0,
"skill_dimension_saved": 0,
"skipped": 17
},
"planner_output": null,
"run_id": "5ea778e2-d522-4b40-9a49-2c1c35e5d410"
}
LLM Calls
Every model call made for this run, in pipeline order. Click a card to see the model's response.
Loading…