
Staff, Data Engineer
Philadelphia, PAJobSeen 4 days agoSeen in employer's feed 4 days ago
Most applications go out cold — see where you stand first. No sign-up to start.
Watch jobs like this. New roles like this one near Philadelphia, PA, by email.
Don't just apply. Show up ready.
Olive works from this exact posting.
At a glance
Olive lists jobs from US employers, including remote roles you can work from the United States.
Job overview
The Staff Data Engineer owns and evolves GSK’s governed context layer and serves as EAI’s internal authority on data architecture for AI. The role defines the standards, frameworks, and guardrails used by digital workers to engineer and operate pipelines, shapes AI data infrastructure and governance, and develops senior engineers. It partners with engineering and domain teams to build shared, reliable data capabilities for production AI systems.
Skills & qualifications
Skills
Qualifications
Full job description
Enterprise AI (EAI) builds the data foundations that GSK's AI systems depend on. In our operating model, digital workers do the hands-on data engineering. They generate pipelines, test and deploy them, monitor them in production and remediate failures. Our engineers design the system those digital workers operate in. At the centre of that system is a governed context layer. It makes data, meaning, permissions and history retrievable at the moment they are needed, and sits above our data platforms and beneath every experience and agent built on them. The Staff Data Engineer is accountable for implementing and evolving the governed context layer that humans and digital workers use across EAI, and is EAI's internal authority on data architecture for AI. 1. Owns the governed context layer as the shared foundation every human and digital worker in EAI relies on, accountable for its architecture, implementation and evolution. 2. Defines the system digital workers engineer within through the standards, frameworks, contracts and guardrails that let them build and operate pipelines safely, consistently and at scale. 3. Raises the standard of data engineering for AI across EAI through the architecture, governance and engineering practices others adopt, and through the senior engineers the role develops. Key Responsibilities: Context & Semantics 1. Implement and evolve the governed context layer as a product: one layer across enterprise knowledge, structured data, business vocabulary and modelled ontologies, queried by humans and digital workers at run time. 2. Build the capabilities the layer depends on: reliable cataloguing across structured and unstructured data, AI-assisted metadata enrichment, context design for each use case, secure agent access over standard protocols such as MCP, and routing across sources. 3. Make certified meaning machine-readable so that every number a digital worker returns resolves to one governed definition, with clear ownership and lineage. Agent-Operated Data Engineering 1. Define the architecture standards and shared frameworks that digital workers use to generate, test, deploy and monitor pipelines, reducing the integration cost of each new AI initiative. 2. Set the operating model for agent-generated engineering work: what digital workers do autonomously, what requires human approval, how quality is evaluated and how incidents escalate. Lead the incidents digital workers cannot resolve, from detection to permanent resolution. AI Data Infrastructure & Lifecycle 1. Shape EAI's AI data infrastructure strategy across feature engineering, vector and retrieval infrastructure, streaming data flows and evaluation data design, building shared components that multiple AI initiatives depend on in production. 2. Define EAI's MLOps data practices: versioning, lineage, drift monitoring, evaluation dataset governance and model data lifecycle management, extended to the context and evaluation data that digital workers rely on. Governance & Responsible Data 1. Define EAI's responsible data governance standards for AI pipelines, covering privacy, consent, PII, auditability and bias controls, and encode them in the governed context layer so humans and digital workers apply them by default. 2. Shape data quality and lineage at scale across multiple data domains, with measurable outcomes in error rates, downstream AI performance and audit readiness. Platform & Infrastructure 1. Design EAI's data platform architecture with infrastructure as code throughout and platform-as-product thinking, so new data and AI projects start quickly and consistently. 2. Build shared platform components that AI initiatives, engineering teams and digital workers depend on in production, and own their reliability, performance, cost and security. Standards & Technical Leadership 1. **Define data engineering standards * for code, documentation and review, written to be followed by humans and digital workers alike, and drive their adoption across EAI. 2. Develop senior engineers towards greater architectural independence, and partner with forward deployed engineers (FDEs), ML engineers, platform engineers and domain experts on the data requirements of production AI systems. Why You? Basic Qualification We are seeking professionals with the following required skills and qualifications to help us achieve our goals: 1. Bachelor's degree in Computer Science, Data Engineering or a related field, or equivalent practical experience. 2. 10+ years of data engineering experience, including experience defining data architecture for production AI or machine learning (ML) systems. 3. Experience building data infrastructure for AI systems, including feature stores, vector databases, retrieval architectures, streaming data pipelines and evaluation datasets. 4. Experience building context, metadata or semantic infrastructure used by AI systems, such as data catalogues, business glossaries, knowledge graphs or ontologies, exposed to AI agents through protocols such as Model Context Protocol (MCP). 5. Experience designing and operating AI agents or large language model (LLM)-powered systems within data workflows, including evaluation, guardrails and human-in-the-loop controls. 6. Experience defining data quality, lineage and governance standards for AI pipelines across multiple data domains, including privacy, consent, personally identifiable information (PII) handling and auditability. 7. Experience with cloud data platforms and infrastructure as code, including experience setting engineering standards. Preferred Qualification If you have the following characteristics, it would be a plus: Prior Staff, Principal or equivalent experience in an organisation operating a non-trivial data platform for AI. Experience in a regulated industry, such as life sciences, where data integrity and auditability are mandatory. Public technical contributions, such as talks, writing or open source, on data architecture for AI, context engineering or agent-operated data engineering. Experience defining pipeline architecture standards for use across enterprise AI and multiple AI initiatives Experience implementing and evolving governed context and semantic layers used by people and AI systems at run time. Knowledge of data architecture for AI, including feature engineering, vector infrastructure, streaming and evaluation data design. Experience with versioning, lineage, evaluati
How this job compares
Set against the 2,854 open Data Engineering jobs on Olive Jobs, counted November 1, 2026.
- Pay
- This postingNot listed
- Pennsylvania median$105–208K/yr71 salary ranges
- US median$48–58/hr88 hourly ranges
- Openings
- Olive Jobs lists 92 open Data Engineering jobs in Pennsylvania and 2,854 across the US. 7% of them nationwide are listed as remote or flexible.
- Experience
- This posting asks for at least 10 years of experience — more than three in four Data Engineering postings that state a minimum ask for (median 5 years, across 2,428 postings).
- Education
- 1,033 of the 2,854 open Data Engineering jobs (36%) ask for a bachelor's degree or higher.
Counted across the open, public US postings on Olive Jobs on November 1, 2026. Pay medians are the middle values of the low ends and of the high ends of postings that list both ends of a range in the same cadence (a yearly salary or an hourly rate); a range's midpoint is halfway between its ends. Pay and experience figures resting on fewer than 20 postings are left out.
You've read the whole posting — now see how you match it.




