Director, AI Applications Engineering Lead in Surrey

Director, AI Applications Engineering Lead in Surrey

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

At a Glance

  • Tasks: Lead the development of AI tools for Pfizer's executive team and enhance their decision-making.
  • Company: Join Pfizer, a leader in healthcare innovation with a commitment to patient-centric solutions.
  • Benefits: Enjoy a hybrid work model, competitive salary, and a culture that values flexibility and diversity.
  • Other info: Be part of a dynamic team that fosters creativity and supports your professional growth.
  • Why this job: Make a real impact by transforming ideas into reliable AI solutions that improve patient outcomes.
  • Qualifications: Proven experience in software engineering and a passion for building dependable AI applications.

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

You'd be building AI tools for the people who run Pfizer. The Office of the Chief Executive Officer (OCEO) sets the company's strategy, looks after its communications and global health investments, and runs the CEO's own office. So the people using what you build are the CEO's team and the most senior leaders in the company, and they need it to be right as well as quick.

Most of the job is getting early ideas into production. Some turn up as an idea and nothing more, and you design and build from scratch. Others arrive as a prototype or a pilot that proves the point but isn't secure, reliable or supportable yet, and you can't measure whether it's working. Either way you end up with something colleagues can depend on, built with current AI techniques on Pfizer's enterprise AI platforms.

It's a hands-on Director role in a small, senior team that moves fast and owns its own architecture. You'll work hand in hand with the Director, Product Lead: they decide what's worth building and why, you decide how, and neither job works without the other. You'll also work with two Engineering Associates, and they'll pick up most of their standards from watching how you work. If you want hard technical problems, and you'd like to be part of creating a team culture as well as software, it's a good fit.

Role Responsibilities:

  • Get ideas into production: When an idea has earned it, you take it all the way. If nothing's been built yet, you design and build it with the person who came up with it. If there's a prototype or a pilot, you work out what it does well and where it falls down. Then you harden it for real use: security, data handling, testing, monitoring, cost control, and a named owner.
  • Own the architecture: You own the technical design of everything the team builds and keep it hanging together, so each new piece adds to a shared set of components instead of sitting on its own.
  • Write and review code: You'll write and review code most days. AI tools do most of the implementation. You keep the architecture and the reviews in your own hands.
  • Refine the agentic software factory: The team builds with an agentic software factory. Every piece of work goes through the same steps: specify, plan, build, review, ship.
  • Work with the platform teams: You're the technical contact for Pfizer's enterprise AI platform teams. You pick up their new capabilities as they land and tell them what OCEO needs.
  • Get things approved: Solutions go through the Architecture Review Board, the Security Review and the AI Review Board, and you help with the privacy and risk assessments.
  • Take over partner work: Sometimes external partners or colleagues build something and hand it over. You agree up front what a good handover looks like, check it before you accept it, and fix the gaps.
  • Run it in production: Once it's live, you run it: monitoring, evaluation results, cost, incidents, rollback.
  • Build with the people who had the idea: Work with the colleagues who bring ideas in, so they know what they're taking on when it goes live.

Qualifications:

  • Finish the job: A prototype that went down well in a demo is where the work starts. You hold it to the standard that makes it dependable.
  • Start from what's there: Use the platforms and the components the team already has. Writing something new needs a reason.
  • Look at the real thing: Read the code, the data and the logs before you form a view.
  • Think about who runs it next: Write it so someone who wasn't in the room can run it.
  • Ask before you touch other teams' systems: Other teams' systems and data are theirs to grant.
  • Make approvals leave a trail: Where you can, design things so the record of who approved what comes out of the work itself.

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.

Digital Transformation Strategy: One bold way we are achieving our purpose is through our company wide digital transformation strategy.

Flexibility: We aim to create a trusting, flexible workplace culture which encourages employees to achieve work life harmony.

Equal Employment Opportunity: We believe that a diverse and inclusive workforce is crucial to building a successful business.

DisAbility Confident: We are proud to be a Disability Confident Employer and we encourage you to put your best self forward.

Director, AI Applications Engineering Lead in Surrey 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 Applications Engineering Lead in Surrey

✨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 Applications Engineering Lead in Surrey

AI Tool Development
Architecture Design
Code Writing and Review
Software Development Lifecycle
Data Handling
Security Assessment
Monitoring and Evaluation

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.