ironquill.tech/board

$ cat jobs/cloud-database-engineer-leidos-5a71bbc48a36.json

Cloud Database Engineer

Leidos·Worldwide·Flexible / Remote·mid
Apply on themuse → Get AI match score →
Description The Behavioral Health and Readiness Division at Leidos Health & Services Sector is looking for a Cloud Database Engineer to help with developing secure and high-performing data solutions for our Navy customer (the Warfighter Performance Department at the Naval Health Research Center in San Diego, CA). Our program is a long-established sleep and fatigue lab with a substantial accumulated dataset. We conduct funded research studies as well as non-research data collections and analyses that provide commands with near-real-time insight into warfighter readiness to inform operational decisions. Our data spans wearable, survey, and metadata sources across multiple active studies involving U.S. Navy and Marine Corps personnel. We have established space, compute, S3 storage, Databricks, Qlik Sense, and GitLab in the Advana IL5 environment. We are seeking a team member to design and build - in close collaboration with our team - a maintainable, extensible data platform that ingests, validates, transforms, and exposes our data for analysis and reporting. The ideal candidate brings strong technical leadership, hands-on database development skills, and the ability to collaborate across teams to deliver innovative, efficient, and highly usable data Systems. Primary Responsibilities: Build a production data platform on Advana (Databricks + S3 medallion architecture) that supports current and future studies. Deliver a system the team can maintain and extend independently after handoff - particularly the ability to onboard new wearable vendors using a documented, repeatable pattern. Build iteratively and live, with the lab using each feature or pipeline as it is ready. Engage hands-on with our existing data and stakeholders to propose and iterate on a medallion architecture (bronze/silver/gold), naming conventions, partitioning, and schema-evolution strategy. Bronze layer shall preserve raw, unmutated vendor payloads as a hard requirement. After major pipeline updates,