Job Description
Position : Lead Data Engineer (Hands-On)
\n
Location : Cary, NC (On-site / Hybrid)
\n
Duration : Full Time
\n
\n
Experience: 12–18 Years of Experience
\n
\n
Data Platform Architecture & Engineering
\n
Own the end-to-end lakehouse architecture: Bronze / Silver / Gold layer contracts, zone layout on ADLS Gen2, Delta Lake table design, partitioning, schema evolution, and retention strategy.
\n
Design and build metadata-driven, parameterized ingestion frameworks that onboard new data sources without bespoke pipeline code for every feed.
\n
Write canonical PySpark and Scala Spark transformation jobs that serve as the team reference; set coding and testing standards, review pull requests, and debug production incidents.
\n
Design for scale and cost: tune Spark clusters and pools, apply partition pruning and caching strategies, and set cost guardrails as data volumes grow.
\n
Build and automate CI/CD for Databricks and ADF pipelines in Azure DevOps using Databricks Asset Bundles and Terraform; maintain platform observability with Azure Monitor and Log Analytics.
\n
Design repeatable patterns for batch files, database extracts, CDC feeds, and streaming ingestion using Azure Event Hubs / Kafka and Spark Structured Streaming.
\n
AI-Augmented Ingestion & Canonical Mapping
\n
Design and build the AI-augmented metadata ingestion framework that auto-generates bridge documents, DML statements, canonical table definitions, and control metadata from source schemas.
\n
Build AI-assisted source-to-canonical attribute mapping: schema reasoning, data profiling, confidence scoring, and a human review / approval gate before any mapping reaches production.
\n
Generate file-level and record-level validation rules from historical data and metadata analysis, feeding a configurable, rules-engine-backed data quality framework.
\n
AI-Driven Data Quality, Anomaly Detection & Testing
\n
\n
Semantic Layer & Conversational Data Access
\n
\n
Governance, Architecture Reviews & Team Leadership
\n
\n
\n
MUST-HAVE SKILLS & EXPERIENCE
\n
Programming & Data Engineering
\n
Expert - level proficiency in Python, Scala, and PySpark, with a strong track record of designing and delivering production-ready, modular, and well-tested solutions; developing and troubleshooting Spark workloads; and optimizing large-scale batch and streaming data pipelines using Delta Lake and Spark technologies.
\n
Strong SQL and data modelling — dimensional and normalised; schema design and data contract definition.
\n
Databricks expertise — Delta Lake, Unity Catalog, Jobs & Workflows, cluster and pool management, performance tuning, Model Serving.
\n
Azure data stack — ADLS Gen2 (zone design, ACLs, lifecycle), Azure Data Factory (parameterized / metadata-driven frameworks, error handling), Azure Event Hubs.
\n
AI & Machine Learning
\n
3+ years designing and shipping LLM-based systems in production: RAG pipelines, agentic / tool-calling workflows, structured output, chunking and embedding strategy, vector and hybrid retrieval, and prompt engineering.
\n
Evaluation discipline — golden datasets, regression suites, accuracy and hallucination tracking, human-in-the-loop feedback loops; you measure AI quality, not assert it.
\n
Hands-on experience with LangChain, LlamaIndex, or LangGraph, plus at least one provider stack (Azure OpenAI, OpenAI, or Databricks Model Serving).
\n
Metadata-driven thinking — schema inference, data profiling, lineage, catalogs, and configuration-driven frameworks that onboard the next source without new code.
\n
Architecture & Governance
\n
12–18 years of total experience in data engineering, data platform delivery, or related disciplines.
\n
Proven delivery of a medallion / lakehouse architecture at enterprise scale — not just familiarity with the concept.
\n
Azure security and governance — Entra ID, managed identities, RBAC, POSIX ACLs on ADLS Gen2, Key Vault, private endpoints, and PII handling.
\n
CI/CD and infrastructure as code — Azure DevOps, Terraform, Databricks Asset Bundles, and automated testing of data pipelines.
\n
Clear technical writing and the ability to present and defend a design to both engineers and non-technical stakeholders.
\n
\n
STRONGLY PREFERRED
\n
Knowledge graphs and ontologies: RDF/SPARQL, property graphs (Neo4j), or graph modelling over a lakehouse.
\n
Text-to-SQL or semantic-layer-backed natural-language query systems at enterprise scale, including access control and ambiguity handling.
\n
ML-based anomaly detection on time-series or transactional financial data.
\n
Financial services or insurance domain knowledge: finance close, general ledger, subledger, reconciliation, or actuarial data.
\n
LLMOps and MLOps: model versioning, prompt versioning, cost governance, and observability tooling.
\n
Databricks Data Engineer Professional, Azure DP-203 / DP-700, or AZ-305 certification.
\n
dbt, Great Expectations, or similar data-quality and transformation tooling.
\n
Workday, Prism, or Accounting Center exposure.