Back to Jobs

Data Architect / Engineer – with Fabric (Graph + Ontology)

Not Disclosed

Job Description & Details

Graph‑based data architectures are reshaping how companies extract insights from complex relationships, making expertise in knowledge graphs a hot commodity. This role offers a chance to design next‑gen repositories that power AI‑driven applications, while collaborating with a tight‑knit data team in Tampa. If you thrive on building scalable graph pipelines and ontologies, this contract could be your next big impact.

Job Summary

We are seeking a seasoned Data Architect/Engineer to design and implement scalable graph‑centric data solutions, build knowledge graphs, and create robust ETL/ELT pipelines. The role demands deep expertise in graph databases, ontology modeling (OWL), and .NET/Python development, while ensuring performance, security, and governance across the platform.

Top 3 Critical Skills Table

Skill Why it's critical Mastery Level
Graph Databases (Neo4j, Amazon Neptune, TigerGraph) Core storage/query engine for highly connected data essential to knowledge graphs Senior
Cypher / Gremlin / SPARQL Enables complex traversals and inference across the ontology layer Senior
Data Modeling & ETL for Graphs (relational & NoSQL) Guarantees performant pipelines and data integrity when moving data into graph structures Senior

Interview Preparation

  1. Explain how you would model a many‑to‑many relationship in Neo4j versus a relational database.
    What the interviewer is looking for: Understanding of graph node/relationship design, benefits over join tables, and performance considerations.
  2. Describe the differences between Cypher, Gremlin, and SPARQL and when you would choose each.
    What the interviewer is looking for: Knowledge of query language syntax, execution models, and suitability for property graphs vs RDF stores.
  3. Walk us through an end‑to‑end ETL pipeline that ingests relational data into a knowledge graph.
    What the interviewer is looking for: Ability to map schemas, handle data cleansing, use tools (e.g., Python, .NET), and ensure idempotency.
  4. How do you implement ontology versioning and ensure backward compatibility in an OWL‑based system?
    What the interviewer is looking for: Familiarity with ontology lifecycle, version control strategies, and impact on downstream queries.
  5. What security and governance measures would you embed in a graph data platform on Azure?
    What the interviewer is looking for: Insight into role‑based access, encryption, audit logging, and compliance best practices.

Resume Optimization

  • Graph Databases
  • Neo4j
  • Cypher
  • SPARQL
  • Ontology (OWL)
  • Knowledge Graph
  • ETL pipelines
  • .NET development
  • Python programming
  • Data Modeling

Application Strategy

When reaching out to the recruiter, send a concise email that opens with a friendly greeting, attaches your updated resume, and clearly highlights your top matching skills. Make sure to mention related skills you possess, such as Graph Databases, Cypher/SPARQL, and .NET development, and reference any projects where you built knowledge graphs or ETL pipelines for graph environments.

Career Roadmap

Current Role Typical Experience Core Focus Next Position
Data Architect / Engineer 6‑8 years Graph architecture, ontology, ETL pipelines Senior Data Architect (8‑12 years)
Senior Data Architect 8‑12 years Strategy, cross‑team leadership, large‑scale graph platforms Data Platform Lead / Director (12+ years)
Data Platform Lead / Director 12+ years Enterprise‑wide data strategy, governance, innovation VP of Data Engineering / Chief Data Officer