Director, AI Product Lead in Guildford

Director, AI Product Lead in Guildford

Guildford Full-Time 99000 - 121000 £ / year (est.) Hybrid
Pfizer

At a Glance

  • Tasks: Lead AI product development and transform innovative ideas into impactful solutions.
  • Company: Join Pfizer, a leader in global health with a commitment to innovation.
  • Benefits: Enjoy a hybrid work environment, competitive salary, and a culture of flexibility.
  • Other info: Be part of a diverse team dedicated to empowering each other and driving change.
  • Why this job: Make a real difference in healthcare by shaping AI strategies that improve patient outcomes.
  • Qualifications: Strong problem-solving skills and experience in product management or AI.

The predicted salary is between 99000 - 121000 £ per year.

This job is about bringing AI ideas to life right at the centre of Pfizer. The Office of the Chief Executive Officer (OCEO) shapes the company's strategy, how it talks to the world and where it invests in global health, and it runs the CEO's own office. The ideas you take forward end up in that work. It might be the briefing the CEO reads before meeting another company's chief executive, the signals behind a strategic call, or a message tested before Pfizer says it in public. It's rare for product work to sit this close to the decisions.

Ideas come in all shapes. Often it's just something a colleague has thought of. Sometimes it's a prototype they built with an AI assistant, or a pilot an outside partner ran. You decide which ones are worth doing, and you take the good ones all the way to something properly supported, governed and used by the people it was for.

The team is small and senior, five people in all. Your closest partner is the Director, Engineering Lead. You own what gets built and why, they own how it's built, and most of the big calls you'll make together. You'll work with the leaders of OCEO's four groups: Strategy and Consulting, Corporate Communications, Global Health Investments and Executive Operations. You get a real say over what the team builds and what it leaves alone, and you'll need the evidence and the standing to say no. We're here to help OCEO build for itself rather than to take orders. Success looks like an Office that builds on shared capabilities, where whoever had the idea stays with it until it ships.

Role Responsibilities:

  • Meet the person with the idea early. In the first few days, sit down with whoever brought the idea in and turn it into a short brief they sign off. It says what should change, for whom, and how we'll know it worked, so we start from an outcome and not a feature list. The originator stays with the idea until release, and it's your job to make sure that actually happens.
  • Decide what's worth doing. Ideas turn up as a few lines in a chat, a prototype or a pilot. You weigh what each would be worth, how much work it would take to make it production-grade, and whether anyone would really use it. Back the ones that earn it. Reshape the ones that are nearly there. Stop the rest early, and be open about why, so the team's time goes where it counts.
  • Own the ROI definition. For every use case, you define what return on investment (ROI) means for the AI agents behind it: what they cost to build and run, what they should give back, and how we'll know. Get it agreed with the originator before work starts. The team uses it to decide what to back, and OCEO uses it to judge whether the work paid off.
  • Look for the cheapest way. Before anyone designs anything, check what already exists in OCEO and on Pfizer's enterprise platforms. A lot of ideas are best served by reusing or extending something we already have, and a new build has to justify itself. The hard part is holding that line when a senior stakeholder would rather have a tool of their own.
  • Own the spec. You own the specification and review stages of how the team builds. Write briefs and acceptance criteria tight enough for an AI-assisted build to work from. When the work comes back, judge it against the outcome in the brief, not the wording of the ticket. Loose specs make for loose products.
  • Work with the groups. You'll work with the leads of the four groups and their teams, and with the colleagues who own each solution once it's live. Keep expectations honest about what's actually coming, agree how originators get credit for the time they put in, and raise friction early instead of at release.
  • Make sure people use it. Plan adoption with each group, find local champions, and help colleagues do more for themselves next time. That way OCEO gets a bit more capable with every idea, and the know-how doesn't all sit with the team.
  • Measure what changes. Once work starts, track each use case against its ROI definition and report regularly: which ideas came in and from whom, how many made it to production, how widely they're used, and what changed for the people using them. You're the one who can say, with evidence, whether something landed.
  • Keep track of what we learn. Record decisions as you make them. After each piece of work, write up what it taught us about the problem and the group, so the next idea doesn't start from scratch.

Qualifications:

  • Help, don't just deliver. Treat each idea as a chance to make the person behind it more capable, not an order to fill. Keep asking how they could do more of this themselves next time. We judge success by what OCEO gets done. How much the team builds isn't the point.
  • Stay on the real problem. Keep the work pointed at what the originator actually needs, which isn't always the first thing they asked for. If the evidence says the problem is something else, tell them early and rework it together. Delivering the wrong brief perfectly helps nobody.
  • Reuse first. Look at what's there before you design anything. A new build needs a reason. OCEO moves faster by building on what it has than by lining up new tools.
  • Say no, and say why. Turn down or stop work that doesn't serve the outcome, even when the person asking is senior. Give the reason every time and offer a cheaper route if there is one. That's usually what keeps the relationship intact.
  • Be in the room. Make product calls with the engineers, while it's still cheap to change course. Be in the working sessions yourself rather than reviewing what comes out of them from a distance.
  • Write decisions down. Briefs, priority calls and scope cuts go in decision records, not in your head. It's a light daily habit, a few lines when you make the call, so the group leads and the rest of the team can follow your thinking without having to ask.
  • Done means the outcome happened. Agree what should change before you start, and hold the team to it. Calling something done means you can point to the outcome, not just that the work has stopped.

Work Location Assignment: Hybrid

Purpose: Breakthroughs that change patients' lives... At Pfizer we are a patient centric company, guided by our four values: courage, joy, equity and excellence. Our breakthrough culture lends itself to our dedication to transforming millions of lives.

Digital Transformation Strategy: One bold way we are achieving our purpose is through our company wide digital transformation strategy. We are leading the way in adopting new data, modelling and automated solutions to further digitize and accelerate drug discovery and development with the aim of enhancing health outcomes and the patient experience.

Flexibility: We aim to create a trusting, flexible workplace culture which encourages employees to achieve work life harmony, attracts talent and enables everyone to be their best working self. Let’s start the conversation!

Equal Employment Opportunity: We believe that a diverse and inclusive workforce is crucial to building a successful business. As an employer, Pfizer is committed to celebrating this, in all its forms – allowing for us to be as diverse as the patients and communities we serve. Together, we continue to build a culture that encourages, supports and empowers our employees.

DisAbility Confident: We are proud to be a Disability Confident Employer and we encourage you to put your best self forward with the knowledge and trust that we will make any reasonable adjustments necessary to support your application and future career. Our mission is unleashing the power of our people, especially those with unique superpowers. Your journey with Pfizer starts here!

Director, AI Product Lead in Guildford employer: Pfizer

At Pfizer, we pride ourselves on being an exceptional employer, offering a dynamic and inclusive work culture that prioritises employee well-being and professional growth. Our hybrid work model fosters flexibility, allowing you to balance your personal and professional life while contributing to groundbreaking advancements in healthcare. With a commitment to diversity and a focus on empowering our employees, you'll find meaningful opportunities to make a real impact in the lives of patients around the world.

Pfizer

Contact Details:

Pfizer Recruitment Team

StudySmarter Expert Advice🤫

We think this is how you could land Director, AI Product Lead in Guildford

✨Join Local Tech Meetups

Get out there and mingle with fellow developers by joining local tech meetups. It’s a fantastic way to meet people who might be working at Pfizer or know someone who does. Plus, you can pick up some trendy tech skills and trends while you're at it!

✨Contribute to Open Source Projects

Show off your coding chops by jumping into open-source projects. Not only does this give you practical experience, but it also gets you noticed in the dev community. You'll create a killer portfolio that speaks volumes about your skills to Pfizer.

✨Tap into Online Developer Communities

Don’t underestimate the power of online developer communities like GitHub, Stack Overflow, and even Reddit. Participate in discussions, share your projects, and build your visibility. We can often find opportunities through these channels that can lead to a full-time gig at companies like Pfizer.

✨Explore Job Boards Specifically for Tech Roles

Keep your eyes peeled on job boards that focus on tech roles. Sites like TechCareers or Stack Overflow Jobs can often have listings for companies like Pfizer that might not show up on broader job sites. Make it a habit to check these regularly, and don’t hesitate to apply directly through our website!

We think you need these skills to ace Director, AI Product Lead in Guildford

AI Product Management
Strategic Thinking
Stakeholder Engagement
ROI Definition
Specification Writing
Project Oversight
Data Analysis

Some tips for your application 🫡

Show off your coding skills:When applying for a software engineering role, it's super important to showcase your coding skills. Make sure your CV includes your tech stack, any relevant programming languages you’re comfortable with, and examples of projects you've worked on. If you have a GitHub profile, link it up! We love to see code in action.

Tailor your portfolio:For a full-time role, we’d expect to see some solid examples of your work in your portfolio. Make sure to include at least two or three projects that highlight your problem-solving skills and your ability to work with different technologies. Focus on the projects that are most relevant to the position at Pfizer.

Craft a killer cover letter:Your cover letter is your chance to stand out—make it personal! Explain why you want to work at Pfizer and how your skills align with the role. Show us your passion for software development. We dig enthusiastic candidates who understand the value of collaboration and continuous learning!

Be clear and concise:When it comes to writing your CV and cover letter, clarity is key. Avoid jargon that could confuse us and stick to simple, direct language. Highlight your achievements with quantifiable results where possible, and keep everything easy to read. A well-organised application goes a long way!

How to prepare for a job interview at Pfizer

✨Brush Up on Your Coding Skills

For a full-time software engineering role, it's crucial that we stay sharp with our coding abilities. Expect technical questions that might involve solving problems on the spot or discussing algorithms. Practise on platforms like LeetCode or HackerRank to get comfortable with the types of questions that often come up.

✨Know Your Tools and Frameworks

Make sure we’re well-acquainted with the tools and technologies listed in the job description. Familiarise ourselves with any specific frameworks or programming languages mentioned. If Pfizer uses React or Node.js, for instance, be ready to discuss how we’ve used them in previous projects or coursework.

✨Showcase Your Projects

Bring along a portfolio that highlights our best work. This could be code samples, GitHub repositories, or any side projects we’ve built. Make sure we can talk through our thought process for each project, especially the challenges we faced and how we solved them—this shows our problem-solving skills in action.

✨Prepare for Behavioural Questions

While technical skills are key, full-time positions also require cultural fit. Be ready to discuss our previous experiences and how we handle teamwork, conflict, and deadlines. Brush up on the STAR method—Situation, Task, Action, Result—to clearly articulate our past experiences when discussing how we've contributed to a team.