> Markdown version of [/jobs/ext/4787702-lead-data-engineer-architect](https://www.wearedevelopers.com/jobs/ext/4787702-lead-data-engineer-architect). Every page supports `.md` or `Accept: text/markdown`. Links point to the HTML versions so they work for humans too. Agent guide: [/agents.md](https://www.wearedevelopers.com/agents.md). --- # Lead Data Engineer / Architect - **Company:** Sidram Technologies - **Location:** Cary, NC, United States - **Experience:** Expert - **Contract:** Permanent contract - **Skills:** LangGraph Framework, Artificial Intelligence, Automation of Tests, Microsoft Azure, Code Review, Computer Programming, Continuous Integration, Information Engineering, Data Profiling, Database Design, Graph Database, Information Retrieval, Python (Programming Language), Metadata, Neo4j, Performance Tuning, Posix, Role-Based Access Control, OpenAI, Standard Sql, Azure Data Lake, Scala (Programming Language), Software Engineering, SPARQL, SQL Databases, Data Streaming, Scripting, Azure Data Factory, Retrieval-Augmented Generation, Prompt Engineering, Apache Spark, Llamaindex, Generative AI, Data Lakes, Pyspark, Production Code, Data Management, Machine Learning Operations, Terraform, Data Pipelines, Key Vault, Databricks, Programming Languages - **Published:** November 19, 2026 - **Apply:** https://www.careerbuilder.com/job-details/lead-data-engineer-architect-cary-nc--0b433985-c98e-4ff2-be63-be32f7c97ab3 ## About the Role Leadership, Software Engineering, Technical/Engineering Design, Python Programming/Scripting Language, Artificial Intelligence (AI), Scala Programming Language, Code Reviews, Identify Issues, Data Management, Database Design, This is a senior hands-on leadership role. You will own the end-to-end technical design of the data and AI layers, build the reference implementations your engineers work from, and ship production-grade Python, Scala, and PySpark code every week. If you have not written or reviewed production code in the past year, this is not the right fit., Programming & Data Engineering 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. Strong SQL and data modelling - dimensional and normalised; schema design and data contract definition. Databricks expertise - Delta Lake, Unity Catalog, Jobs & Workflows, cluster and pool management, performance tuning, Model Serving. Azure data stack - ADLS Gen2 (zone design, ACLs, lifecycle), Azure Data Factory (parameterized / metadata-driven frameworks, error handling), Azure Event Hubs. AI & Machine Learning 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. Evaluation discipline - golden datasets, regression suites, accuracy and hallucination tracking, human-in-the-loop feedback loops; you measure AI quality, not assert it. Hands-on experience with LangChain, LlamaIndex, or LangGraph, plus at least one provider stack (Azure OpenAI, OpenAI, or Databricks Model Serving). Metadata-driven thinking - schema inference, data profiling, lineage, catalogs, and configuration-driven frameworks that onboard the next source without new code. Architecture & Governance 12 18 years of total experience in data engineering, data platform delivery, or related disciplines. Proven delivery of a medallion / lakehouse architecture at enterprise scale - not just familiarity with the concept. Azure security and governance - Entra ID, managed identities, RBAC, POSIX ACLs on ADLS Gen2, Key Vault, private endpoints, and PII handling. CI/CD and infrastructure as code - Azure DevOps, Terraform, Databricks Asset Bundles, and automated testing of data pipelines. Clear technical writing and the ability to present and defend a design to both engineers and non-technical stakeholders. STRONGLY PREFERRED Knowledge graphs and ontologies: RDF/SPARQL, property graphs (Neo4j), or graph modelling over a lakehouse. Text-to-SQL or semantic-layer-backed natural-language query systems at enterprise scale, including access control and ambiguity handling. ML-based anomaly detection on time-series or transactional financial data. Financial services or insurance domain knowledge: finance close, general ledger, subledger, reconciliation, or actuarial data.