Director, Principal Engineer - Marketing Technologies

ROLE SUMMARY

Pfizer’s Biopharma, Patient and Centre for Digital Innovation (BPC) team are responsible for the creation, configuration, launch, and support of all externally facing digital (web, mobile, omni-channel, & device) products, platforms, services, and experiences, servicing all external customer types at Pfizer.

In addition, they are accountable for our Marketing Technology (Martech) stack inclusive of Digital Platforms, Digital Channel Enablement, Content Integration, and Marketing/Marketer Tools and for driving Digital Enablement within Pfizer. 

Within this team, Engineering Leadership is a critical element of the team composition.  The Director, Principal Engineer - Marketing Technology Solutions role is a leadership role that ensures the engineering standards and principles that underpin our Digital operating model are applied and refined.  

This role is a key technical and people leader position within the Martech Platforms team which will be responsible for providing expert guidance and direction in the design, development, and implementation of complex Marketing Technology systems and solutions. 

This role plays a pivotal role in defining architectural standards, ensuring global scalability, and designing technical roadmaps.  The role will ensure reliability and performance of systems, while also mentoring and coaching other engineers to foster their professional development. 

Collaborating closely with other key cross-functional teams, they help translate business requirements into technical solutions, drive innovation through research and experimentation, and resolve intricate technical challenges with their problem-solving skills. 

With a blend of technical expertise, leadership, and strategic vision, principal engineers drive technical excellence, innovation, and success within the Pfizer Digital.

The commercial effectiveness of the solutions delivered in this role are equally as important as the standard of the engineering we use to build the solutions.  This role will be a key influencer in the design of marketing technology solutions for Pfizer.

ROLE RESPONSIBILITIES 

Typically, this role consists of leading one or more teams of engineers to deliver and implement technical solutions, following your design approach to meet your assigned program objectives and KPIs. You will also collaborate closely and often with Chief Marketing Office (CMO) Leads, Digital Leads, and Product Owners, to ensure that technical decisions and their implementation align with broader strategic priorities.

You represent engineering in program and stakeholder meetings, as such you’ll need to be able to think on your feet: provide consultation, identify risks based on a variety of factors, and rely on your past experiences to identify potential solutions and develop ballpark estimates.

In many situations you will be working with technology that is new to Pfizer and requires you to learn quickly, be able to read and understand documentation, and architect robust and scalable solutions that align with our business objectives.

Using influence more than authority, you will lead teams of engineers on the implementation of the solution. Individual members of the team are responsible for delivering on their commitments, but the team supports each other. The team pride themselves on the quality of their code, our delivery practices and breadth of our test coverage. You will be expected to document your work.

Key responsibilities for a Principal Engineer are listed below:

Technical Leadership 

• Serve as the top technical authority on projects, making decisions on technology choices, design approaches, solution architecture and implementation.
• Lead and oversee the entire lifecycle excellence of engineering projects, ensuring alignment with architectural vision and adherence to best practices.
• Responsible for maintaining good code quality by promoting and ensuring secure code hygiene.
• Responsible for guiding the correct configuration of SaaS solutions to ensure security and compliance.
• Build a team able to manage change. Take appropriate risks to achieve the desired results, balancing risks to stability and current norms versus the need for constant change, improvement, and simplification.
• Facilitate the conversation between Enterprise Architects, Business Architects, Vendors and Developers, by providing technical clarity on solution(s) to build and code to write, move content from ideation into delivery to move from concept to reality.

Cross-Team Collaboration

• Act as a translator between business stakeholders and technical engineers, to ensure that technical, security and privacy considerations are represented in strategic discussions and business objectives