Director, Commercial Data Products

Business Introduction
At GSK, we have bold ambitions for patients, aiming to positively impact the health of 2.5 billion people by the end of the decade. Our R&D focuses on discovering and delivering vaccines and medicines, combining our understanding of the immune system with cutting-edge technology to transform people’s lives. GSK fosters a culture ambitious for patients, accountable for impact, and committed to doing the right thing, making sure that we focus our efforts on accelerating significant assets that meet patients’ needs and have the highest probability of success. We’re uniting science, technology, and talent to get ahead of disease together.
Find out more:
Our approach to R&D

Position Summary

Are you a data leader who wants to build and manage enterprise data products on which a major pharmaceutical business bases its commercial decisions — while staying hands-on in the data model, the code standards, and the roadmap? If yes, this Director, Commercial Data Products role could be an ideal opportunity to explore.

This role owns key enterprise data products, including products in the Commercial Activity and Customer & Account domains that people and AI use directly to answer their own questions quickly, consistently, and with confidence. Success in this role requires strong partnership across GSK, including with engineering teams that ingest and prepare data, analytics teams, commercial and field operations, tech partners, and master data and data governance teams.

The role establishes or refines the data model and product roadmap and is accountable for the quality, reliability, documentation, and versioning of the products. Accountability does not stop at the pipeline: the role owns the SLAs, published definitions, and catalog documentation through which products reach their users, and their adoption.

This is a hands-on product owner role, not a request-management role, partnering with an engineering team to build and maintain the products, leading a team of contractors, and setting the engineering bar by example: version-controlled, peer-reviewed, tested, and documented code. Business functions retain ownership of what metrics and rules mean; this role encodes, versions, and certifies them.

Key Responsibilities

This role will provide YOU the opportunity to lead key activities to progress YOUR career. These responsibilities include some of the following:

• Own a set of key enterprise data products in the Commercial Activity and Customer & Account domains — for example, Customer Interactions, Sales & Performance, Customer 360 — setting product vision, scope, SLAs, versioning, and the standard against which each is certified, and driving adoption while retiring previous data products.
• Own the product roadmap: gather and prioritize stakeholder requirements, negotiate scope and trade-offs directly with the business, and make firm commitments with clear delivery timelines agreed against published capacity. Represent the domains in regular demand review meetings and publish roadmaps, backlogs, and release notes so consumers can see what is coming and when.
• Own the data models for the products in the domains — conceptual, logical, and physical (Erwin or equivalent) — designing for reuse and for the hard problems in commercial data: effective-dating, data restatements, HCP/HCO hierarchies and affiliations, and consistent keys across masters and products.

• Partner closely with the matrixed engineering team that builds and maintains the products on Databricks, following enterprise platform standards. Own what gets built, in what order, and to what definition of done.

• Champion engineering best practices across everyone who contributes, including contractors — Git-based version control, pull requests with peer review, automated tests alongside models, CI/CD, and everything-as-code — and review designs and code with the depth to be a credible partner to engineers, contributing hands-on when the work demands it.

• Lead a team of contractors supporting the domains — setting priorities, quality standards, and expectations, and ensuring knowledge is documented and retained — while influencing engineering and stewardship partners who contribute to the products without direct reporting lines.

• Own the key source relationships feeding the domains (for example syndicated sales data and CRM data) alongside source data stewards, writing the contents-and-format specification for each source; consume the certified Customer Master as the foundation for 360 products and provide requirements on identity rules, hierarchies, and affiliations.

• Encode, version, and certify business definitions and rules supplied by named business owners — never defining what a metric means, and not certifying without a named owner — and certify each product as AI-ready (permitted use cleared, semantics documented, lineage complete), with catalog entries and documentation good enough for teams and AI agents to self-serve.

…