USA remote
Data Architect
About this role
Why you: We are looking for someone who can design a data platform and then help build it. This is not a whiteboard only role. You will own the architecture, and you will also write pipelines, models, and code alongside the team. If this is you, and you wonder what it would be like to work at Pythian, reach out to us and find out! Intrigued to see what a life is like at Pythian? Check out #pythianlife on LinkedIn and follow @loveyourdata on Instagram! Not the right job for you? Check out what other great jobs Pythian has open around the world! Pythian Careers What you will be doing: Own the end to end architecture: ingestion, lakehouse and warehouse layers, transformation, modeling, and delivery to reporting and analytics tools.
Build it. Write and deploy pipelines, Spark and SQL transformations, and data models, and review the code the rest of the team writes. Design lakehouse architectures on Databricks or Fabric, including medallion layering, Delta table design, and the semantic layer that sits on top. Make the platform call and defend it. Databricks, Fabric, or a mix, based on the client's workloads, existing licensing, skills, and cost profile.
Set up governance and access control using Unity Catalog, Purview, or the equivalent, and apply it consistently rather than bolting it on at the end. Design and build ingestion from a wide range of sources: databases, SaaS applications, APIs, files, and legacy systems that were never meant to be integrated. What we need from you: Eight or more years in data engineering, with at least three years owning architecture and design decisions.
Proven hands on delivery. You should be able to point at platforms you designed and also built. Deep hands on experience with Databricks or Microsoft Fabric, and working knowledge of the other. Comfortable explaining where each one fits and where it does not. Strong Spark and SQL. Solid Python or an equivalent language used in production data work. Experience with Delta Lake, medallion architecture, and lakehouse patterns in production, not just in a demo.
Power BI, including how the semantic model is built and where it should live. Solid dimensional and semantic modeling skills. You should have opinions about where business logic belongs and be able to explain why. Working knowledge of data governance: classification, lineage, cataloging, and access control. CI/CD, version control, and testing practices applied to data work, not just to application code. What sets you apart from other applicants: Azure Government or GCC High delivery experience.