Pipeline run
1200a67e-5b56-492e-8cad-e59c72f369de
Client output enrichment
v2 Skill cluster · Nature of work · AI index · Tech stack maturity · Evidence · KRA descriptionvocab breakdown (legacy)
Signals
Post-classification
Captured for admin review
1 POST /skills/extract-from-jd
2 POST /skills/extract-details
3 POST /skills/final-role-output
Data Engineer
CASE Aslug: data-engineer · id: 2 · source: db
Exact alias hit on data-engineer (1.0) — no other alias at this confidence; skill_top absent does not contradict
Resolution:
in_db
— role exists in library; skill↔dim and role↔dim links saved when applicable.
Job description
Job Title: Sr. Data Engineer - Ontology & Knowledge Graph Specialist Department: Platform Engineering Summary We are seeking a highly skilled Data Engineer with expertise in ontology development and knowledge graph implementation. This role will be pivotal in shaping our data infrastructure and ensuring the accurate representation and integration of complex data sets. You will leverage industry best practices, including the Basic Formal Ontology (BFO) and Common Core Ontologies (CCO), to design, develop, and maintain ontologies, semantic and syntactic data models, and knowledge graphs on the Databricks Data Intelligence Platform that drive data-driven decision-making and innovation within the company. Responsibilities Ontology Development: Design and implement ontologies based on BFO and CCO principles, ensuring alignment with business requirements and industry standards. Collaborate with domain experts to capture and formalize domain knowledge into ontological structures. Develop and maintain comprehensive ontologies to model various business entities, relationships, and processes. Data Modeling Design and implement semantic and syntactic data models that adhere to ontological principles. Create data models that are scalable, flexible, and adaptable to changing business needs. Integrate data models with existing data infrastructure and applications. Knowledge Graph Implementation Design and build knowledge graphs based on ontologies and data models. Develop algorithms and tools for knowledge graph population, enrichment, and maintenance. Utilize knowledge graphs to enable advanced analytics, search, and recommendation systems. Data Quality And Governance Ensure the quality, accuracy, and consistency of ontologies, data models, and knowledge graphs. Define and implement data governance processes and standards for ontology development and maintenance. Collaboration And Communication Work closely with data scientists, software engineers, and business stakeholders to understand their data requirements and provide tailored solutions. Communicate complex technical concepts clearly and effectively to diverse audiences. Qualifications Education: Bachelor's or Master's degree in Computer Science, Data Science, or a related field. Experience 5+ years of experience in data engineering or a related role. Proven experience in ontology development using BFO and CCO or similar ontological frameworks. Strong knowledge of semantic web technologies, including RDF, OWL, SPARQL, and SHACL. Proficiency in Python, SQL, and other programming languages used for data engineering. Experience with graph databases (e.g., TigerGraph, JanusGraph) and triple stores (e.g., GraphDB, Stardog) is a plus. Desired Skills Familiarity with machine learning and natural language processing techniques. Experience with cloud-based data platforms (e.g., AWS, Azure, GCP). Experience with Databricks technologies including Spark, Delta Lake, Iceberg, Unity Catalog, UniForm, and Photon. Strong problem-solving and analytical skills. Excellent communication and interpersonal skills. To Apply Please submit your resume, cover letter, and a portfolio of your ontology or knowledge graph projects to . Skills: machine learning,databricks technologies,syntactic data models,iceberg,ontology,ontology development,create data models,rdf,utilize knowledge graphs,owl,delta lake,sparql,gcp,data engineering,python,triple stores,databricks data intelligence platform,data scientists,graphs,natural language processing techniques,shacl,ontologies,spark,knowledge graphs,cloud-based data platforms,bfo,knowledge graph implementation,data lake,photon,cco,semantic web technologies,aws,data models,janusgraph,uniform,unified data platform,common core ontologies,software engineers,graphdb,communicate complex technical concepts,integrate data models,graph,tigergraph,sql,data governance,azure,graph databases,basic formal ontology,stardog,data quality,knowledge graph population,data governance processes,data modeling
Skills from this JD
Each row merges API 1 extraction, API 2 library match / v3 orchestration (dimensions + locked dims), and API 3 persistence tags.
Skill enrichment (orchestrator / LLM)
No Stage 7 enrichment blob on this skill (orchestrator skipped enrichment).
- Category
- Concepts
- Sub-category
- general
- Skill nature
- CONCEPT
- Volatility
- MEDIUM
- Typical lifespan
- MULTI_YEAR
- Version strategy
- UNVERSIONED
Skill enrichment (orchestrator / LLM)
No Stage 7 enrichment blob on this skill (orchestrator skipped enrichment).
- Category
- Concepts
- Sub-category
- general
- Skill nature
- CONCEPT
- Volatility
- MEDIUM
- Typical lifespan
- MULTI_YEAR
- Version strategy
- UNVERSIONED
Skill enrichment (orchestrator / LLM)
No Stage 7 enrichment blob on this skill (orchestrator skipped enrichment).
- Category
- Concepts
- Sub-category
- general
- Skill nature
- CONCEPT
- Volatility
- MEDIUM
- Typical lifespan
- MULTI_YEAR
- Version strategy
- UNVERSIONED
Aliases — catalog
- domain modeling (CANONICAL) primary
- Domain Modeling (CANONICAL)
Context tags (catalog)
Stored enrichment (catalog DB)
- Category
- Methodology
- Sub-category
- Domain Modeling
- Confidence
- 0.90
- Version strategy
- NOT_APPLICABLE
Maturity reasoning: Common in software JDs under DDD/business analysis; many roles ask for domain modeling or domain-driven design, and it remains a standard design skill rather than a niche tool.
Skill profile (library / DB)
- Skill nature
- METHODOLOGY
- Volatility
- STABLE
- Typical lifespan
- EVERGREEN
- Category id
- 8
- Sub-category id
- 2831
- Extractable
- True
- Also category
- False
Dimensions (API 2 worklist)
-
Application Architecture Patterns Catalog dimension db id 293
Library dimension (catalog)
Roles linked in library: .NET Backend Developer, Python Backend Developer
-
Service Architecture and Design Patterns Catalog dimension db id 18
Library dimension (catalog)
Roles linked in library: Backend Developer, Java Backend Developer, Kotlin Backend Developer, Node.js Backend Developer, PHP Backend Developer, Ruby Backend Developer, Scala Backend Developer
API 3 link attempts (this skill)
| Dimension | Skill↔dim | Role↔dim | Outcome |
|---|---|---|---|
|
Application Architecture Patterns
application-architecture-patterns
|
— | — |
Skipped — no persistable v3 meta for new skill
skill_not_in_db_v3_proposed
|
|
Service Architecture and Design Patterns
service-architecture-and-design-patterns
|
— | — |
Skipped — no persistable v3 meta for new skill
skill_not_in_db_v3_proposed
|
Skill enrichment (orchestrator / LLM)
No Stage 7 enrichment blob on this skill (orchestrator skipped enrichment).
- Category
- Concepts
- Sub-category
- general
- Skill nature
- CONCEPT
- Volatility
- MEDIUM
- Typical lifespan
- MULTI_YEAR
- Version strategy
- UNVERSIONED
Skill enrichment (orchestrator / LLM)
No Stage 7 enrichment blob on this skill (orchestrator skipped enrichment).
- Category
- Practices
- Sub-category
- general
- Skill nature
- PRACTICE
- Volatility
- MEDIUM
- Typical lifespan
- MULTI_YEAR
- Version strategy
- UNVERSIONED
Skill enrichment (orchestrator / LLM)
No Stage 7 enrichment blob on this skill (orchestrator skipped enrichment).
- Category
- Practices
- Sub-category
- general
- Skill nature
- PRACTICE
- Volatility
- MEDIUM
- Typical lifespan
- MULTI_YEAR
- Version strategy
- UNVERSIONED
Skill enrichment (orchestrator / LLM)
No Stage 7 enrichment blob on this skill (orchestrator skipped enrichment).
- Category
- Concepts
- Sub-category
- general
- Skill nature
- CONCEPT
- Volatility
- MEDIUM
- Typical lifespan
- MULTI_YEAR
- Version strategy
- UNVERSIONED
Skill enrichment (orchestrator / LLM)
No Stage 7 enrichment blob on this skill (orchestrator skipped enrichment).
- Category
- Concepts
- Sub-category
- general
- Skill nature
- CONCEPT
- Volatility
- MEDIUM
- Typical lifespan
- MULTI_YEAR
- Version strategy
- UNVERSIONED
Skill enrichment (orchestrator / LLM)
No Stage 7 enrichment blob on this skill (orchestrator skipped enrichment).
- Category
- Concepts
- Sub-category
- general
- Skill nature
- CONCEPT
- Volatility
- MEDIUM
- Typical lifespan
- MULTI_YEAR
- Version strategy
- UNVERSIONED
Skill enrichment (orchestrator / LLM)
No Stage 7 enrichment blob on this skill (orchestrator skipped enrichment).
- Category
- Concepts
- Sub-category
- general
- Skill nature
- CONCEPT
- Volatility
- MEDIUM
- Typical lifespan
- MULTI_YEAR
- Version strategy
- UNVERSIONED
Skill enrichment (orchestrator / LLM)
No Stage 7 enrichment blob on this skill (orchestrator skipped enrichment).
- Category
- Concepts
- Sub-category
- general
- Skill nature
- CONCEPT
- Volatility
- MEDIUM
- Typical lifespan
- MULTI_YEAR
- Version strategy
- UNVERSIONED
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 |
|---|---|---|---|---|---|---|
| Data Modeling | new |
Application Architecture Patterns
application-architecture-patterns
|
— | — | Skipped — no persistable v3 meta for new skill | skill_not_in_db_v3_proposed |
| Data Modeling | new |
Service Architecture and Design Patterns
service-architecture-and-design-patterns
|
— | — | Skipped — no persistable v3 meta for new skill | skill_not_in_db_v3_proposed |
Library artifacts (this run)
| Kind | Detail | DB id |
|---|---|---|
| canonical_skill_proposed | Ontology | type=Concepts subtype=general nature=CONCEPT lifespan=MULTI_YEAR | |
| canonical_skill_proposed | BFO | type=Concepts subtype=general nature=CONCEPT lifespan=MULTI_YEAR | |
| canonical_skill_proposed | CCO | type=Concepts subtype=general nature=CONCEPT lifespan=MULTI_YEAR | |
| canonical_skill_proposed | Knowledge Graphs | type=Concepts subtype=general nature=CONCEPT lifespan=MULTI_YEAR | |
| canonical_skill_proposed | Data Governance | type=Practices subtype=general nature=PRACTICE lifespan=MULTI_YEAR | |
| canonical_skill_proposed | Data Quality | type=Practices subtype=general nature=PRACTICE lifespan=MULTI_YEAR | |
| canonical_skill_proposed | Semantic Modeling | type=Concepts subtype=general nature=CONCEPT lifespan=MULTI_YEAR | |
| canonical_skill_proposed | Syntactic Data Modeling | type=Concepts subtype=general nature=CONCEPT lifespan=MULTI_YEAR | |
| canonical_skill_proposed | Advanced Analytics | type=Concepts subtype=general nature=CONCEPT lifespan=MULTI_YEAR | |
| canonical_skill_proposed | Search | type=Concepts subtype=general nature=CONCEPT lifespan=MULTI_YEAR | |
| canonical_skill_proposed | Recommendation Systems | type=Concepts subtype=general nature=CONCEPT lifespan=MULTI_YEAR | |
| dimension_skill_link_proposed | Data Modeling ↔ Application Architecture Patterns | |
| dimension_skill_link_proposed | Data Modeling ↔ Service Architecture and Design Patterns |
nano JD Parser — gpt-4.1-nano click to toggle
Show raw JSON
{
"JD_type": "pass",
"about_company": null,
"certifications": [],
"company_name": null,
"ctc": null,
"domain": {
"primary": {
"aliases": [],
"domain": "IT Services \u0026 Consulting"
},
"secondary": null
},
"education": [
{
"level": "Bachelor\u0027s",
"qualification": "BTECH/BE/BSC/MTECH/ME/MSC - Computer Science / Data Science (or related)",
"raw": "Bachelor\u0027s or Master\u0027s degree in Computer Science, Data Science, or a related field.",
"requirement": "required"
}
],
"experience": {
"max": null,
"min": 5,
"raw": "5+ years of experience in data engineering or a related role."
},
"job_locations": [],
"role": "Sr. Data Engineer - Ontology \u0026 Knowledge Graph Specialist",
"role_aliases": [
"Data Engineer",
"Ontology Specialist",
"Knowledge Graph Engineer"
],
"role_archetype": "Data",
"roles_and_responsibilities": [
{
"bullet_count": 0,
"heading": "Responsibilities",
"heading_was_present": true,
"source_marker": {
"first_5_words": "Ontology Development: Design and implement",
"last_5_words": "to diverse audiences."
},
"text": "Ontology Development:\n\nDesign and implement ontologies based on BFO and CCO principles, ensuring alignment with business requirements and industry standards.\n\nCollaborate with domain experts to capture and formalize domain knowledge into ontological structures.\n\nDevelop and maintain comprehensive ontologies to model various business entities, relationships, and processes.\n\nData Modeling\n\nDesign and implement semantic and syntactic data models that adhere to ontological principles.\n\nCreate data models that are scalable, flexible, and adaptable to changing business needs.\n\nIntegrate data models with existing data infrastructure and applications.\n\nKnowledge Graph Implementation\n\nDesign and build knowledge graphs based on ontologies and data models.\n\nDevelop algorithms and tools for knowledge graph population, enrichment, and maintenance.\n\nUtilize knowledge graphs to enable advanced analytics, search, and recommendation systems.\n\nData Quality And Governance\n\nEnsure the quality, accuracy, and consistency of ontologies, data models, and knowledge graphs.\n\nDefine and implement data governance processes and standards for ontology development and maintenance.\n\nCollaboration And Communication\n\nWork closely with data scientists, software engineers, and business stakeholders to understand their data requirements and provide tailored solutions.\n\nCommunicate complex technical concepts clearly and effectively to diverse audiences.",
"word_count": 335
}
],
"urls": []
}
API 1 — extract-from-jd click to toggle
{
"final_skills": [
{
"is_primary": true,
"skill_name": "Ontology"
},
{
"is_primary": true,
"skill_name": "BFO"
},
{
"is_primary": true,
"skill_name": "CCO"
},
{
"is_primary": true,
"skill_name": "Data Modeling"
},
{
"is_primary": true,
"skill_name": "Knowledge Graphs"
},
{
"is_primary": true,
"skill_name": "Data Governance"
},
{
"is_primary": true,
"skill_name": "Data Quality"
},
{
"is_primary": true,
"skill_name": "Semantic Modeling"
},
{
"is_primary": true,
"skill_name": "Syntactic Data Modeling"
},
{
"is_primary": false,
"skill_name": "Advanced Analytics"
},
{
"is_primary": false,
"skill_name": "Search"
},
{
"is_primary": false,
"skill_name": "Recommendation Systems"
}
],
"jd_role": {
"display_name": "Sr. Data Engineer - Ontology \u0026 Knowledge Graph Specialist",
"rationale": null,
"role_aliases": [
"Data Engineer",
"Ontology Specialist",
"Knowledge Graph Engineer"
],
"role_archetype": "Data",
"slug": ""
},
"nano_parsed": {
"JD_type": "pass",
"about_company": null,
"certifications": [],
"company_name": null,
"ctc": null,
"domain": {
"primary": {
"aliases": [],
"domain": "IT Services \u0026 Consulting"
},
"secondary": null
},
"education": [
{
"level": "Bachelor\u0027s",
"qualification": "BTECH/BE/BSC/MTECH/ME/MSC - Computer Science / Data Science (or related)",
"raw": "Bachelor\u0027s or Master\u0027s degree in Computer Science, Data Science, or a related field.",
"requirement": "required"
}
],
"experience": {
"max": null,
"min": 5,
"raw": "5+ years of experience in data engineering or a related role."
},
"job_locations": [],
"role": "Sr. Data Engineer - Ontology \u0026 Knowledge Graph Specialist",
"role_aliases": [
"Data Engineer",
"Ontology Specialist",
"Knowledge Graph Engineer"
],
"role_archetype": "Data",
"roles_and_responsibilities": [
{
"bullet_count": 0,
"heading": "Responsibilities",
"heading_was_present": true,
"source_marker": {
"first_5_words": "Ontology Development: Design and implement",
"last_5_words": "to diverse audiences."
},
"text": "Ontology Development:\n\nDesign and implement ontologies based on BFO and CCO principles, ensuring alignment with business requirements and industry standards.\n\nCollaborate with domain experts to capture and formalize domain knowledge into ontological structures.\n\nDevelop and maintain comprehensive ontologies to model various business entities, relationships, and processes.\n\nData Modeling\n\nDesign and implement semantic and syntactic data models that adhere to ontological principles.\n\nCreate data models that are scalable, flexible, and adaptable to changing business needs.\n\nIntegrate data models with existing data infrastructure and applications.\n\nKnowledge Graph Implementation\n\nDesign and build knowledge graphs based on ontologies and data models.\n\nDevelop algorithms and tools for knowledge graph population, enrichment, and maintenance.\n\nUtilize knowledge graphs to enable advanced analytics, search, and recommendation systems.\n\nData Quality And Governance\n\nEnsure the quality, accuracy, and consistency of ontologies, data models, and knowledge graphs.\n\nDefine and implement data governance processes and standards for ontology development and maintenance.\n\nCollaboration And Communication\n\nWork closely with data scientists, software engineers, and business stakeholders to understand their data requirements and provide tailored solutions.\n\nCommunicate complex technical concepts clearly and effectively to diverse audiences.",
"word_count": 335
}
],
"urls": []
},
"rejected": false,
"rejection_reason": null,
"run_id": "1200a67e-5b56-492e-8cad-e59c72f369de",
"stage3_signals": {
"alias_found": true,
"alias_match_roles": [
{
"display_name": "Data Engineer",
"kra_matches": null,
"matched_count": null,
"matched_skills": null,
"role_id": 2,
"score": 1.0,
"slug": "data-engineer",
"total_count": null
}
],
"kra_match_roles": [
{
"display_name": "Data Engineer",
"kra_matches": [
{
"kra_text": "Works with data analysts, data scientists, and business stakeholders to define data models, ingestion schedules, and data delivery requirements.",
"sentence": "Work closely with data scientists, software engineers, and business stakeholders to understand their data requirements and provide tailored solutions.",
"similarity": 0.7046
},
{
"kra_text": "Works with data analysts, data scientists, and business stakeholders to define data models, ingestion schedules, and data delivery requirements.",
"sentence": "Integrate data models with existing data infrastructure and applications.",
"similarity": 0.603
},
{
"kra_text": "Designs dimensional models, star schemas, data vault structures, and curated data mart tables to support BI tools and self-service analytics consumption.",
"sentence": "Create data models that are scalable, flexible, and adaptable to changing business needs.",
"similarity": 0.5929
}
],
"matched_count": null,
"matched_skills": null,
"role_id": 2,
"score": 0.6335,
"slug": "data-engineer",
"total_count": null
},
{
"display_name": "Scala Backend Developer",
"kra_matches": [
{
"kra_text": "application data modeling",
"sentence": "Integrate data models with existing data infrastructure and applications.",
"similarity": 0.5416
},
{
"kra_text": "application data modeling",
"sentence": "Create data models that are scalable, flexible, and adaptable to changing business needs.",
"similarity": 0.5284
},
{
"kra_text": "application data modeling",
"sentence": "Design and implement semantic and syntactic data models that adhere to ontological principles.",
"similarity": 0.4849
}
],
"matched_count": null,
"matched_skills": null,
"role_id": 87,
"score": 0.5183,
"slug": "scala-backend-developer",
"total_count": null
},
{
"display_name": "Java Backend Developer",
"kra_matches": [
{
"kra_text": "persistence and data modeling",
"sentence": "Create data models that are scalable, flexible, and adaptable to changing business needs.",
"similarity": 0.5312
},
{
"kra_text": "persistence and data modeling",
"sentence": "Integrate data models with existing data infrastructure and applications.",
"similarity": 0.5206
},
{
"kra_text": "persistence and data modeling",
"sentence": "Design and implement semantic and syntactic data models that adhere to ontological principles.",
"similarity": 0.4977
}
],
"matched_count": null,
"matched_skills": null,
"role_id": 79,
"score": 0.5165,
"slug": "java-backend-developer",
"total_count": null
},
{
"display_name": "Node.js Backend Developer",
"kra_matches": [
{
"kra_text": "data modeling and persistence access",
"sentence": "Create data models that are scalable, flexible, and adaptable to changing business needs.",
"similarity": 0.5033
},
{
"kra_text": "data modeling and persistence access",
"sentence": "Design and implement semantic and syntactic data models that adhere to ontological principles.",
"similarity": 0.5033
},
{
"kra_text": "external system integration",
"sentence": "Integrate data models with existing data infrastructure and applications.",
"similarity": 0.4682
}
],
"matched_count": null,
"matched_skills": null,
"role_id": 82,
"score": 0.4916,
"slug": "node-backend-developer",
"total_count": null
},
{
"display_name": "Flutter Developer",
"kra_matches": [
{
"kra_text": "integrate external APIs and data sources",
"sentence": "Integrate data models with existing data infrastructure and applications.",
"similarity": 0.6173
},
{
"kra_text": "collaborate with design, product, and backend teams",
"sentence": "Work closely with data scientists, software engineers, and business stakeholders to understand their data requirements and provide tailored solutions.",
"similarity": 0.4571
},
{
"kra_text": "optimize responsiveness and performance",
"sentence": "Create data models that are scalable, flexible, and adaptable to changing business needs.",
"similarity": 0.3983
}
],
"matched_count": null,
"matched_skills": null,
"role_id": 74,
"score": 0.4909,
"slug": "flutter-developer",
"total_count": null
}
],
"skill_match_roles": []
},
"stage4_decision": {
"alias_collision_detected": false,
"case": "A",
"chosen_role": {
"display_name": "Data Engineer",
"kra_matches": null,
"matched_count": null,
"matched_skills": null,
"role_id": 2,
"score": 1.0,
"slug": "data-engineer",
"total_count": null
},
"confidence": 1.0,
"is_new_role": false,
"llm2_fired": false,
"llm2_reasoning": null,
"matched_dimensions": [],
"matched_kras": [],
"matched_skills": [],
"new_role_display_name": null,
"new_role_slug": null,
"queued": false,
"reasoning": "Exact alias hit on data-engineer (1.0) \u2014 no other alias at this confidence; skill_top absent does not contradict",
"sub_role": null
},
"stage5_updates": {
"centroid_n_after": 295,
"centroid_updated": true,
"collision_log_id": null,
"new_kra_attached": null,
"new_skills_attached": [
{
"is_primary": true,
"queue_id": 14218,
"role_display_name": "Data Engineer",
"role_slug": "data-engineer",
"skill_name": "Ontology",
"status": "pending"
},
{
"is_primary": true,
"queue_id": 14219,
"role_display_name": "Data Engineer",
"role_slug": "data-engineer",
"skill_name": "BFO",
"status": "pending"
},
{
"is_primary": true,
"queue_id": 14220,
"role_display_name": "Data Engineer",
"role_slug": "data-engineer",
"skill_name": "CCO",
"status": "pending"
},
{
"is_primary": true,
"queue_id": 14221,
"role_display_name": "Data Engineer",
"role_slug": "data-engineer",
"skill_name": "Data Modeling",
"status": "pending"
},
{
"is_primary": true,
"queue_id": 14222,
"role_display_name": "Data Engineer",
"role_slug": "data-engineer",
"skill_name": "Knowledge Graphs",
"status": "pending"
},
{
"is_primary": true,
"queue_id": 14223,
"role_display_name": "Data Engineer",
"role_slug": "data-engineer",
"skill_name": "Data Governance",
"status": "pending"
},
{
"is_primary": true,
"queue_id": 14224,
"role_display_name": "Data Engineer",
"role_slug": "data-engineer",
"skill_name": "Data Quality",
"status": "pending"
},
{
"is_primary": true,
"queue_id": 14225,
"role_display_name": "Data Engineer",
"role_slug": "data-engineer",
"skill_name": "Semantic Modeling",
"status": "pending"
},
{
"is_primary": true,
"queue_id": 14226,
"role_display_name": "Data Engineer",
"role_slug": "data-engineer",
"skill_name": "Syntactic Data Modeling",
"status": "pending"
},
{
"is_primary": false,
"queue_id": 14227,
"role_display_name": "Data Engineer",
"role_slug": "data-engineer",
"skill_name": "Advanced Analytics",
"status": "pending"
},
{
"is_primary": false,
"queue_id": 14228,
"role_display_name": "Data Engineer",
"role_slug": "data-engineer",
"skill_name": "Search",
"status": "pending"
},
{
"is_primary": false,
"queue_id": 14229,
"role_display_name": "Data Engineer",
"role_slug": "data-engineer",
"skill_name": "Recommendation Systems",
"status": "pending"
}
],
"queue_entry_id": null,
"v3_pipeline_triggered": false,
"v3_role_slug": null,
"v3_run_id": null
}
}
API 2 — extract-details
{
"alias_matches": [
{
"alias_persist_skipped_reason": "TODO: REMOVE AFTER TESTING \u2014 alias DB write disabled",
"alias_persisted": false,
"existing_alias_id": 5644,
"existing_alias_text": "Domain Modeling",
"input_term": "Data Modeling",
"matched_canonical": {
"category_id": 8,
"display_name": "domain modeling",
"id": 2379,
"is_also_category": false,
"is_extractable": true,
"skill_nature": "METHODOLOGY",
"slug": "domain-modeling",
"sub_category_id": 2831,
"typical_lifespan": "EVERGREEN",
"volatility": "STABLE"
},
"matched_via": "embedding_alias"
}
],
"candidate_roles": [
{
"display_name": ".NET Backend Developer",
"id": 83,
"rationale": null,
"role_archetype": "Engineering",
"slug": "dotnet-backend-developer",
"source": "db"
},
{
"display_name": "Python Backend Developer",
"id": 80,
"rationale": null,
"role_archetype": "Engineering",
"slug": "python-backend-developer",
"source": "db"
},
{
"display_name": "Backend Developer",
"id": 1,
"rationale": null,
"role_archetype": "A Backend Engineer designs, builds, and maintains the server-side logic and data handling that power applications and services. They focus on implementing reliable business functionality, integrating with other systems, and ensuring the backend is scalable, maintainable, and observable.",
"slug": "backend-engineer",
"source": "db"
},
{
"display_name": "Java Backend Developer",
"id": 79,
"rationale": null,
"role_archetype": "Engineering",
"slug": "java-backend-developer",
"source": "db"
},
{
"display_name": "Kotlin Backend Developer",
"id": 84,
"rationale": null,
"role_archetype": "Engineering",
"slug": "kotlin-server-backend-developer",
"source": "db"
},
{
"display_name": "Node.js Backend Developer",
"id": 82,
"rationale": null,
"role_archetype": "Engineering",
"slug": "node-backend-developer",
"source": "db"
},
{
"display_name": "PHP Backend Developer",
"id": 86,
"rationale": null,
"role_archetype": "Engineering",
"slug": "php-backend-developer",
"source": "db"
},
{
"display_name": "Ruby Backend Developer",
"id": 85,
"rationale": null,
"role_archetype": "Engineering",
"slug": "ruby-backend-developer",
"source": "db"
},
{
"display_name": "Scala Backend Developer",
"id": 87,
"rationale": null,
"role_archetype": "Engineering",
"slug": "scala-backend-developer",
"source": "db"
}
],
"chosen_role": {
"display_name": "Data Engineer",
"id": 2,
"rationale": "Exact alias hit on data-engineer (1.0) \u2014 no other alias at this confidence; skill_top absent does not contradict",
"role_archetype": null,
"slug": "data-engineer",
"source": "db"
},
"dimensions": [
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Application Architecture Patterns",
"id": 293,
"rationale": "Structural patterns for organizing Python backend code into maintainable modules, layers, and feature boundaries. This is a coherent cluster because senior backend developers are expected to refactor and shape service internals over time.",
"slug": "application-architecture-patterns",
"source": "db"
},
"input_skill": "Data Modeling",
"llm_role": null,
"roles_from_db": [
{
"display_name": ".NET Backend Developer",
"id": 83,
"rationale": null,
"role_archetype": "Engineering",
"slug": "dotnet-backend-developer",
"source": "db"
},
{
"display_name": "Python Backend Developer",
"id": 80,
"rationale": null,
"role_archetype": "Engineering",
"slug": "python-backend-developer",
"source": "db"
}
]
},
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Service Architecture and Design Patterns",
"id": 18,
"rationale": "Reusable backend design patterns used to structure service code and boundaries. Covers layering, dependency management, domain modeling, and maintainable service organization.",
"slug": "service-architecture-and-design-patterns",
"source": "db"
},
"input_skill": "Data Modeling",
"llm_role": null,
"roles_from_db": [
{
"display_name": "Backend Developer",
"id": 1,
"rationale": null,
"role_archetype": "A Backend Engineer designs, builds, and maintains the server-side logic and data handling that power applications and services. They focus on implementing reliable business functionality, integrating with other systems, and ensuring the backend is scalable, maintainable, and observable.",
"slug": "backend-engineer",
"source": "db"
},
{
"display_name": "Java Backend Developer",
"id": 79,
"rationale": null,
"role_archetype": "Engineering",
"slug": "java-backend-developer",
"source": "db"
},
{
"display_name": "Kotlin Backend Developer",
"id": 84,
"rationale": null,
"role_archetype": "Engineering",
"slug": "kotlin-server-backend-developer",
"source": "db"
},
{
"display_name": "Node.js Backend Developer",
"id": 82,
"rationale": null,
"role_archetype": "Engineering",
"slug": "node-backend-developer",
"source": "db"
},
{
"display_name": "PHP Backend Developer",
"id": 86,
"rationale": null,
"role_archetype": "Engineering",
"slug": "php-backend-developer",
"source": "db"
},
{
"display_name": "Ruby Backend Developer",
"id": 85,
"rationale": null,
"role_archetype": "Engineering",
"slug": "ruby-backend-developer",
"source": "db"
},
{
"display_name": "Scala Backend Developer",
"id": 87,
"rationale": null,
"role_archetype": "Engineering",
"slug": "scala-backend-developer",
"source": "db"
}
]
}
],
"input_final_skills": [
"Ontology",
"BFO",
"CCO",
"Data Modeling",
"Knowledge Graphs",
"Data Governance",
"Data Quality",
"Semantic Modeling",
"Syntactic Data Modeling",
"Advanced Analytics",
"Search",
"Recommendation Systems"
],
"input_llm_skills": [
"Ontology",
"BFO",
"CCO",
"Data Modeling",
"Knowledge Graphs",
"Data Governance",
"Data Quality",
"Semantic Modeling",
"Syntactic Data Modeling",
"Advanced Analytics",
"Search",
"Recommendation Systems"
],
"new_aliases_persisted": 0,
"run_id": "1200a67e-5b56-492e-8cad-e59c72f369de",
"skills_detail": [
{
"aliases_in_db": [],
"canonical": null,
"dimensions": [],
"input_skill": "Ontology",
"matched_via": null,
"new_alias_persisted": false,
"new_alias_text": null,
"new_skill_meta": {
"derived": {
"category": "Concepts",
"skill_nature": "CONCEPT",
"sub_category": "general",
"typical_lifespan": "MULTI_YEAR",
"version_strategy": "UNVERSIONED",
"volatility": "MEDIUM"
},
"enrichment": null,
"keep_log": [],
"locked_dimensions": [],
"merge_log": [],
"placed": null,
"relationships": null,
"skill_id": "ontology",
"split_log": [],
"typed": null,
"warnings": []
},
"source_tag": "llm",
"was_in_llm_skills": true
},
{
"aliases_in_db": [],
"canonical": null,
"dimensions": [],
"input_skill": "BFO",
"matched_via": null,
"new_alias_persisted": false,
"new_alias_text": null,
"new_skill_meta": {
"derived": {
"category": "Concepts",
"skill_nature": "CONCEPT",
"sub_category": "general",
"typical_lifespan": "MULTI_YEAR",
"version_strategy": "UNVERSIONED",
"volatility": "MEDIUM"
},
"enrichment": null,
"keep_log": [],
"locked_dimensions": [],
"merge_log": [],
"placed": null,
"relationships": null,
"skill_id": "bfo",
"split_log": [],
"typed": null,
"warnings": []
},
"source_tag": "llm",
"was_in_llm_skills": true
},
{
"aliases_in_db": [],
"canonical": null,
"dimensions": [],
"input_skill": "CCO",
"matched_via": null,
"new_alias_persisted": false,
"new_alias_text": null,
"new_skill_meta": {
"derived": {
"category": "Concepts",
"skill_nature": "CONCEPT",
"sub_category": "general",
"typical_lifespan": "MULTI_YEAR",
"version_strategy": "UNVERSIONED",
"volatility": "MEDIUM"
},
"enrichment": null,
"keep_log": [],
"locked_dimensions": [],
"merge_log": [],
"placed": null,
"relationships": null,
"skill_id": "cco",
"split_log": [],
"typed": null,
"warnings": []
},
"source_tag": "llm",
"was_in_llm_skills": true
},
{
"aliases_in_db": [
{
"alias_text": "domain modeling",
"alias_type": "CANONICAL",
"id": 3675,
"is_primary": true,
"match_strategy": "CASE_INSENSITIVE"
},
{
"alias_text": "Domain Modeling",
"alias_type": "CANONICAL",
"id": 5644,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
}
],
"canonical": {
"category_id": 8,
"display_name": "domain modeling",
"id": 2379,
"is_also_category": false,
"is_extractable": true,
"skill_nature": "METHODOLOGY",
"slug": "domain-modeling",
"sub_category_id": 2831,
"typical_lifespan": "EVERGREEN",
"volatility": "STABLE"
},
"dimensions": [
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Application Architecture Patterns",
"id": 293,
"rationale": "Structural patterns for organizing Python backend code into maintainable modules, layers, and feature boundaries. This is a coherent cluster because senior backend developers are expected to refactor and shape service internals over time.",
"slug": "application-architecture-patterns",
"source": "db"
},
"input_skill": "Data Modeling",
"llm_role": null,
"roles_from_db": [
{
"display_name": ".NET Backend Developer",
"id": 83,
"rationale": null,
"role_archetype": "Engineering",
"slug": "dotnet-backend-developer",
"source": "db"
},
{
"display_name": "Python Backend Developer",
"id": 80,
"rationale": null,
"role_archetype": "Engineering",
"slug": "python-backend-developer",
"source": "db"
}
]
},
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Service Architecture and Design Patterns",
"id": 18,
"rationale": "Reusable backend design patterns used to structure service code and boundaries. Covers layering, dependency management, domain modeling, and maintainable service organization.",
"slug": "service-architecture-and-design-patterns",
"source": "db"
},
"input_skill": "Data Modeling",
"llm_role": null,
"roles_from_db": [
{
"display_name": "Backend Developer",
"id": 1,
"rationale": null,
"role_archetype": "A Backend Engineer designs, builds, and maintains the server-side logic and data handling that power applications and services. They focus on implementing reliable business functionality, integrating with other systems, and ensuring the backend is scalable, maintainable, and observable.",
"slug": "backend-engineer",
"source": "db"
},
{
"display_name": "Java Backend Developer",
"id": 79,
"rationale": null,
"role_archetype": "Engineering",
"slug": "java-backend-developer",
"source": "db"
},
{
"display_name": "Kotlin Backend Developer",
"id": 84,
"rationale": null,
"role_archetype": "Engineering",
"slug": "kotlin-server-backend-developer",
"source": "db"
},
{
"display_name": "Node.js Backend Developer",
"id": 82,
"rationale": null,
"role_archetype": "Engineering",
"slug": "node-backend-developer",
"source": "db"
},
{
"display_name": "PHP Backend Developer",
"id": 86,
"rationale": null,
"role_archetype": "Engineering",
"slug": "php-backend-developer",
"source": "db"
},
{
"display_name": "Ruby Backend Developer",
"id": 85,
"rationale": null,
"role_archetype": "Engineering",
"slug": "ruby-backend-developer",
"source": "db"
},
{
"display_name": "Scala Backend Developer",
"id": 87,
"rationale": null,
"role_archetype": "Engineering",
"slug": "scala-backend-developer",
"source": "db"
}
]
}
],
"input_skill": "Data Modeling",
"matched_via": "embedding_alias",
"new_alias_persisted": false,
"new_alias_text": null,
"new_skill_meta": null,
"source_tag": "db",
"was_in_llm_skills": true
},
{
"aliases_in_db": [],
"canonical": null,
"dimensions": [],
"input_skill": "Knowledge Graphs",
"matched_via": null,
"new_alias_persisted": false,
"new_alias_text": null,
"new_skill_meta": {
"derived": {
"category": "Concepts",
"skill_nature": "CONCEPT",
"sub_category": "general",
"typical_lifespan": "MULTI_YEAR",
"version_strategy": "UNVERSIONED",
"volatility": "MEDIUM"
},
"enrichment": null,
"keep_log": [],
"locked_dimensions": [],
"merge_log": [],
"placed": null,
"relationships": null,
"skill_id": "knowledge-graphs",
"split_log": [],
"typed": null,
"warnings": []
},
"source_tag": "llm",
"was_in_llm_skills": true
},
{
"aliases_in_db": [],
"canonical": null,
"dimensions": [],
"input_skill": "Data Governance",
"matched_via": null,
"new_alias_persisted": false,
"new_alias_text": null,
"new_skill_meta": {
"derived": {
"category": "Practices",
"skill_nature": "PRACTICE",
"sub_category": "general",
"typical_lifespan": "MULTI_YEAR",
"version_strategy": "UNVERSIONED",
"volatility": "MEDIUM"
},
"enrichment": null,
"keep_log": [],
"locked_dimensions": [],
"merge_log": [],
"placed": null,
"relationships": null,
"skill_id": "data-governance",
"split_log": [],
"typed": null,
"warnings": []
},
"source_tag": "llm",
"was_in_llm_skills": true
},
{
"aliases_in_db": [],
"canonical": null,
"dimensions": [],
"input_skill": "Data Quality",
"matched_via": null,
"new_alias_persisted": false,
"new_alias_text": null,
"new_skill_meta": {
"derived": {
"category": "Practices",
"skill_nature": "PRACTICE",
"sub_category": "general",
"typical_lifespan": "MULTI_YEAR",
"version_strategy": "UNVERSIONED",
"volatility": "MEDIUM"
},
"enrichment": null,
"keep_log": [],
"locked_dimensions": [],
"merge_log": [],
"placed": null,
"relationships": null,
"skill_id": "data-quality",
"split_log": [],
"typed": null,
"warnings": []
},
"source_tag": "llm",
"was_in_llm_skills": true
},
{
"aliases_in_db": [],
"canonical": null,
"dimensions": [],
"input_skill": "Semantic Modeling",
"matched_via": null,
"new_alias_persisted": false,
"new_alias_text": null,
"new_skill_meta": {
"derived": {
"category": "Concepts",
"skill_nature": "CONCEPT",
"sub_category": "general",
"typical_lifespan": "MULTI_YEAR",
"version_strategy": "UNVERSIONED",
"volatility": "MEDIUM"
},
"enrichment": null,
"keep_log": [],
"locked_dimensions": [],
"merge_log": [],
"placed": null,
"relationships": null,
"skill_id": "semantic-modeling",
"split_log": [],
"typed": null,
"warnings": []
},
"source_tag": "llm",
"was_in_llm_skills": true
},
{
"aliases_in_db": [],
"canonical": null,
"dimensions": [],
"input_skill": "Syntactic Data Modeling",
"matched_via": null,
"new_alias_persisted": false,
"new_alias_text": null,
"new_skill_meta": {
"derived": {
"category": "Concepts",
"skill_nature": "CONCEPT",
"sub_category": "general",
"typical_lifespan": "MULTI_YEAR",
"version_strategy": "UNVERSIONED",
"volatility": "MEDIUM"
},
"enrichment": null,
"keep_log": [],
"locked_dimensions": [],
"merge_log": [],
"placed": null,
"relationships": null,
"skill_id": "syntactic-data-modeling",
"split_log": [],
"typed": null,
"warnings": []
},
"source_tag": "llm",
"was_in_llm_skills": true
},
{
"aliases_in_db": [],
"canonical": null,
"dimensions": [],
"input_skill": "Advanced Analytics",
"matched_via": null,
"new_alias_persisted": false,
"new_alias_text": null,
"new_skill_meta": {
"derived": {
"category": "Concepts",
"skill_nature": "CONCEPT",
"sub_category": "general",
"typical_lifespan": "MULTI_YEAR",
"version_strategy": "UNVERSIONED",
"volatility": "MEDIUM"
},
"enrichment": null,
"keep_log": [],
"locked_dimensions": [],
"merge_log": [],
"placed": null,
"relationships": null,
"skill_id": "advanced-analytics",
"split_log": [],
"typed": null,
"warnings": []
},
"source_tag": "llm",
"was_in_llm_skills": true
},
{
"aliases_in_db": [],
"canonical": null,
"dimensions": [],
"input_skill": "Search",
"matched_via": null,
"new_alias_persisted": false,
"new_alias_text": null,
"new_skill_meta": {
"derived": {
"category": "Concepts",
"skill_nature": "CONCEPT",
"sub_category": "general",
"typical_lifespan": "MULTI_YEAR",
"version_strategy": "UNVERSIONED",
"volatility": "MEDIUM"
},
"enrichment": null,
"keep_log": [],
"locked_dimensions": [],
"merge_log": [],
"placed": null,
"relationships": null,
"skill_id": "search",
"split_log": [],
"typed": null,
"warnings": []
},
"source_tag": "llm",
"was_in_llm_skills": true
},
{
"aliases_in_db": [],
"canonical": null,
"dimensions": [],
"input_skill": "Recommendation Systems",
"matched_via": null,
"new_alias_persisted": false,
"new_alias_text": null,
"new_skill_meta": {
"derived": {
"category": "Concepts",
"skill_nature": "CONCEPT",
"sub_category": "general",
"typical_lifespan": "MULTI_YEAR",
"version_strategy": "UNVERSIONED",
"volatility": "MEDIUM"
},
"enrichment": null,
"keep_log": [],
"locked_dimensions": [],
"merge_log": [],
"placed": null,
"relationships": null,
"skill_id": "recommendation-systems",
"split_log": [],
"typed": null,
"warnings": []
},
"source_tag": "llm",
"was_in_llm_skills": true
}
],
"unmatched_skills": [
"Ontology",
"BFO",
"CCO",
"Knowledge Graphs",
"Data Governance",
"Data Quality",
"Semantic Modeling",
"Syntactic Data Modeling",
"Advanced Analytics",
"Search",
"Recommendation Systems"
]
}
API 3 — final-role-output
{
"chosen_role": {
"display_name": "Data Engineer",
"id": 2,
"rationale": "Exact alias hit on data-engineer (1.0) \u2014 no other alias at this confidence; skill_top absent does not contradict",
"role_archetype": null,
"slug": "data-engineer",
"source": "db"
},
"chosen_role_resolution": "in_db",
"final_input_skills": [
{
"skill": "Ontology",
"tag": "new"
},
{
"skill": "BFO",
"tag": "new"
},
{
"skill": "CCO",
"tag": "new"
},
{
"skill": "Data Modeling",
"tag": "in_db"
},
{
"skill": "Knowledge Graphs",
"tag": "new"
},
{
"skill": "Data Governance",
"tag": "new"
},
{
"skill": "Data Quality",
"tag": "new"
},
{
"skill": "Semantic Modeling",
"tag": "new"
},
{
"skill": "Syntactic Data Modeling",
"tag": "new"
},
{
"skill": "Advanced Analytics",
"tag": "new"
},
{
"skill": "Search",
"tag": "new"
},
{
"skill": "Recommendation Systems",
"tag": "new"
}
],
"llm_cost_api1_usd": null,
"llm_cost_api2_usd": null,
"llm_cost_api3_usd": null,
"llm_cost_total_usd": null,
"persistence": {
"items": [
{
"chosen_role_id": 2,
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Application Architecture Patterns",
"id": 293,
"rationale": "Structural patterns for organizing Python backend code into maintainable modules, layers, and feature boundaries. This is a coherent cluster because senior backend developers are expected to refactor and shape service internals over time.",
"slug": "application-architecture-patterns",
"source": "db"
},
"dimension_id": 293,
"input_skill": "Data Modeling",
"llm_role": null,
"matched_chosen_role": false,
"outcome_line": "Skipped \u2014 no persistable v3 meta for new skill",
"role_dimension_saved": false,
"roles_from_db": [
{
"display_name": ".NET Backend Developer",
"id": 83,
"rationale": null,
"role_archetype": "Engineering",
"slug": "dotnet-backend-developer",
"source": "db"
},
{
"display_name": "Python Backend Developer",
"id": 80,
"rationale": null,
"role_archetype": "Engineering",
"slug": "python-backend-developer",
"source": "db"
}
],
"skill_dimension_saved": false,
"skill_id": null,
"skill_tag": "new",
"skipped_reason": "skill_not_in_db_v3_proposed"
},
{
"chosen_role_id": 2,
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Service Architecture and Design Patterns",
"id": 18,
"rationale": "Reusable backend design patterns used to structure service code and boundaries. Covers layering, dependency management, domain modeling, and maintainable service organization.",
"slug": "service-architecture-and-design-patterns",
"source": "db"
},
"dimension_id": 18,
"input_skill": "Data Modeling",
"llm_role": null,
"matched_chosen_role": false,
"outcome_line": "Skipped \u2014 no persistable v3 meta for new skill",
"role_dimension_saved": false,
"roles_from_db": [
{
"display_name": "Backend Developer",
"id": 1,
"rationale": null,
"role_archetype": "A Backend Engineer designs, builds, and maintains the server-side logic and data handling that power applications and services. They focus on implementing reliable business functionality, integrating with other systems, and ensuring the backend is scalable, maintainable, and observable.",
"slug": "backend-engineer",
"source": "db"
},
{
"display_name": "Java Backend Developer",
"id": 79,
"rationale": null,
"role_archetype": "Engineering",
"slug": "java-backend-developer",
"source": "db"
},
{
"display_name": "Kotlin Backend Developer",
"id": 84,
"rationale": null,
"role_archetype": "Engineering",
"slug": "kotlin-server-backend-developer",
"source": "db"
},
{
"display_name": "Node.js Backend Developer",
"id": 82,
"rationale": null,
"role_archetype": "Engineering",
"slug": "node-backend-developer",
"source": "db"
},
{
"display_name": "PHP Backend Developer",
"id": 86,
"rationale": null,
"role_archetype": "Engineering",
"slug": "php-backend-developer",
"source": "db"
},
{
"display_name": "Ruby Backend Developer",
"id": 85,
"rationale": null,
"role_archetype": "Engineering",
"slug": "ruby-backend-developer",
"source": "db"
},
{
"display_name": "Scala Backend Developer",
"id": 87,
"rationale": null,
"role_archetype": "Engineering",
"slug": "scala-backend-developer",
"source": "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": 2
},
"planner_output": null,
"run_id": "1200a67e-5b56-492e-8cad-e59c72f369de"
}
LLM Calls
Every model call made for this run, in pipeline order. Click a card to see the model's response.