AWS Data Engineer - Databricks<\/b> <\/div> Hybrid \u2013 Indianapolis, IN <\/b> <\/div> <\/div> About the Role<\/b> <\/div> <\/div> We are seeking a Data Engineer with 3\u20135 years of experience working specifically within the pharma industry to join a pharma-focused data team. This is a senior-flavored engineering role that combines hands-on pipeline and platform work with significant business-facing responsibility \u2014 including translating business needs into technical specs, presenting to executive-level stakeholders, and helping stand up new data domains from the ground up. You will design, build, and govern the data infrastructure that powers analytics and reporting across the business, while also acting as a trusted technical partner to non-technical stakeholders. <\/div> <\/div> Key Responsibilities<\/b> <\/div> Design, build, and maintain scalable ETL/ELT pipelines (batch and streaming) using Databricks, AWS, and related orchestration tools <\/div><\/li> Write and optimize advanced SQL, and build data transformations in Python or Scala <\/div><\/li> Integrate external data sources via APIs and manage pipeline orchestration (Airflow, Databricks Workflows, AWS Glue) <\/div><\/li> Apply data quality, governance, cataloging, and lineage practices aligned with regulated-industry standards <\/div><\/li> Work within GxP-regulated data environments and apply awareness of data privacy/compliance considerations (e.g., 21 CFR Part 11, GDPR where applicable) <\/div><\/li> Partner with business stakeholders across the pharma value chain (R&D, Manufacturing & Quality, Commercial, Drug Development) to gather and translate requirements into technical specifications <\/div><\/li> Present technical work and data strategy to executive-level audiences <\/div><\/li> Prioritize high-impact data initiatives and proactively identify and avoid duplicated data efforts <\/div><\/li> Support change management and adoption of new data solutions across business teams <\/div><\/li> Help stand up new data domains from scratch (green-field build), not just maintain existing ones <\/div><\/li><\/ul> <\/div><\/span> Requirements<\/h3> Required Qualifications<\/b> <\/div> Data Engineering & Pipelines<\/b> <\/div> ETL/ELT development (batch and streaming) <\/div><\/li> Advanced SQL (joins, window functions, query optimization) <\/div><\/li> Python or Scala for data transformation <\/div><\/li> Data pipeline orchestration (Airflow, Databricks Workflows, AWS Glue) <\/div><\/li> API integration for external data source ingestion <\/div><\/li><\/ul> Platforms & Tools<\/b> <\/div> Databricks (Delta Lake, Unity Catalog, Genie) <\/div><\/li> Cloud platforms \u2014 AWS (S3, Glue, Athena) and/or Azure/GCP equivalents <\/div><\/li> Data warehousing concepts (dimensional modeling, star schema) <\/div><\/li> BI/visualization tools (Tableau, Power BI, or similar) to understand downstream consumption <\/div><\/li><\/ul> Data Quality & Governance<\/b> <\/div> Data profiling and cleansing techniques <\/div><\/li> Metadata management and data cataloging <\/div><\/li> Master data management (MDM) principles <\/div><\/li> Data lineage tracking <\/div><\/li> Data governance frameworks (especially regulated-industry standards) <\/div><\/li><\/ul> Pharma / Life Sciences Domain Knowledge<\/b> <\/div> Familiarity with GxP-regulated data environments <\/div><\/li> Understanding of the pharma value chain (R&D, Manufacturing & Quality, Commercial, Drug Development) <\/div><\/li> Awareness of data privacy/compliance considerations (21 CFR Part 11, GDPR where applicable) <\/div><\/li> Knowledge of common pharma data domains (clinical, manufacturing, quality, commercial) <\/div><\/li><\/ul> Stakeholder Management<\/b> <\/div> Requirements gathering and translation (business need → technical spec) <\/div><\/li> Cross-functional communication (Business ↔ IT) <\/div><\/li> Executive-level presentation skills (given EC visibility) <\/div><\/li> Change management / adoption support <\/div><\/li><\/ul> Analytical & Strategic Thinking<\/b> <\/div> Prioritization frameworks (identifying high-impact vs. low-value data asks) <\/div><\/li> Cost-avoidance mindset (spotting duplication before it happens) <\/div><\/li> Ability to work with ambiguity and evolving priorities <\/div><\/li><\/ul> Project & Program Skills<\/b> <\/div> Agile/Scrum familiarity <\/div><\/li> Documentation discipline (data dictionaries, source-to-target mappings) <\/div><\/li> Vendor/partner coordination (if external data sources are involved) <\/div><\/li><\/ul> Nice-to-Have Differentiators <\/div> Prior consulting or client-facing delivery experience <\/div><\/li> Experience standing up new data domains from scratch (green-field vs. maintenance) <\/div><\/li> Familiarity with AI/GenAI-enabled analytics tools <\/div><\/li><\/ul><\/span>

Timing