Skip to content

Associate, AI Engineering

For international applicants

From the posting

Visa

Sponsorship not stated in the posting.

This employer holds a UK work-visa sponsor licence. Ask the employer before you apply.

Visa salary

Can’t check: no salary in the posting

  • UK Skilled Worker threshold: £41,700 a year, or the going rate for the occupation, if higher. Ask the employer for the salary before you rely on sponsorship.
  • May still qualify: non-STEM PhD holders (90% of the going rate) (£37,500).
  • May still qualify: new entrants (under 26, students, graduates), STEM PhD holders or immigration salary list jobs (£33,400).

Indicative, not legal advice. UK Skilled Worker figure in force since 22 Jul 2025, checked 18 Oct 2026. Official source

Your work rights

Description (EN)

This is an early-career engineering job where your work ends up in front of the leadership of a global company. You'll build AI tools for Pfizer's Office of the Chief Executive Officer (OCEO), which sets the company's strategy, looks after its communications and global health investments, and runs the CEO's own office. You'll take ideas from a first conversation to something senior colleagues rely on.


You'll work directly with the people who had the ideas. Many of them aren't engineers, and you'll often be the one sitting next to them while the idea turns into something real. You'll be building with current AI models and tools from your first week, with a senior engineering lead guiding you, and you'll own solutions yourself as you get more experienced.

There are two of these jobs, in a team of five, and you'd report to the Senior Director, AI Innovation and Delivery. It suits someone who likes learning in the open, wants to see what their work actually does, and is as happy helping a colleague build something as building it alone.

 

Role Responsibilities

  • Pair with the people who have ideas Work alongside colleagues who bring an idea in, especially if it's their first time. Help them shape it and test it, be straight about what it will take to make it production-grade, and make sure they know what they own once it's live. Next time, they should need you a bit less.
  • Build and harden Build features, integrations and fixes from the briefs the Product Lead agrees with originators. You'll use AI coding tools, and your work gets reviewed. Some ideas you'll help build from scratch; others start as a prototype that you turn into a production-grade solution. Before writing anything new, check whether it already exists.
  • Test and evaluate Write the tests and evaluation cases that show whether something works. Run them before release and keep them running after. Watch how solutions behave in real use, find where they get things wrong, and turn what you find into fixes or new tests.
  • Help run what we build Take your share of the day-to-day running: keeping an eye on quality and cost, dealing with issues, applying platform updates, keeping releases tidy. If something looks off, flag it early instead of quietly working around it.
  • Learn it, then own it Get to know the solutions the team runs, including work handed over by outside partners, well enough to change them with confidence. As you get more experienced, you'll take ownership of particular ones.
  • Document as you go Keep how-to guides, decision notes and runbooks up to date, and write them so people outside the team can follow them too. It's what keeps a solution working after the people who built it have moved on.

Role Behaviours

  • Help people build Leave each person you work with more capable than before. A pairing session went well if they can do more on their own afterwards.
  • Ask early Ask questions and raise problems as soon as they come up, whether it's the code, the data or getting access to it. A question on day one costs far less than a mistake found at release.
  • Reuse first Look for a component, pattern or platform feature that already does the job. Writing something new needs a reason.
  • Test what you ship A change isn't finished until you've shown it works on real examples. Keep that evidence where others can see it.
  • Write it down Note what you built and why, in plain words a colleague outside the team can follow. If you're the only one who can explain it, it's not done yet.



  
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!

To learn more about acceptable and prohibited uses of AI during the recruitment process, please review our candidate AI-use guidelines available on Pfizer Careers.

 

 

Information & Business Tech

Walton Oaks, United KingdomOpen in maps ↗

Never pay a recruiter for a job offer or a visa promise. Check the original posting and employer identity before sharing documents. Pay any legitimate government visa fees only through official channels.

Working in United Kingdom

Possible country route: Skilled Worker. A licensed sponsor, certificate of sponsorship and an eligible role are needed. Salary and English requirements depend on the application.

Outside the UK: usually 3 weeks after submitting the application, identity and documents. Sponsor preparation and appointments are additional.

What to check before applying
  1. Verify the sponsor. Confirm the employer can issue a certificate of sponsorship for this role.
  2. Check current requirements. Use GOV.UK for the salary, English, fees and maintenance rules.
  3. Complete the application. Prepare documents and the identity check; do not book relocation against a guaranteed date.
Official immigration guidance ↗

Reviewed 2026-10-14. Country routes are context, not a confirmation that this vacancy or your passport qualifies.

About the employer

PfizerPosted on the employer’s careers page · pfizer.wd1.myworkdayjobs.comLicensed sponsor (UK) — employer-level; what this means

Get similar jobs with visa sponsorshipIT & software jobs in the United Kingdom with visa sponsorship

By tapping “Email me jobs like these” you agree to our Terms and confirm you've read the Privacy Policy.

Once a week. We first email you a link to confirm; nothing is sent until you open it. One-click unsubscribe. Already have an account? Sign in

Similar vacancies

N8n · today
Head of Product Design

Berlin Office; Romania; Estonia; Netherlands; Hungary; Portugal; France; Poland; Germany; Austria; Finland; London Office; Albania; Ireland; Bulgaria; Denmark; Belgium; United Kingdom; Spain; Sweden (Remote) · Full-time · Lead · Creative & media

€125–272k/year (assumed)

Country limits listed

More IT & software jobs with visa sponsorship in the United Kingdom (123) →