You and the process

With a person
Anna, in-house recruiter
9 years hiring engineers
30 minutes with a real recruiter
They read your CV with you, on a call, and say where the offers are being lost.
Didn’t find what you were looking for? Tell us what to build
IFS

Principal Product Designer, AI Experiences

  • Hybrid
  • 6+ years

Salary

Not stated

AI summary

For members

The whole posting in a few lines. Sign up to read it here and on every role you open.

Sign Up to Read

Description

You'll be designing for people whose work actually matters: maintenance engineers, field service technicians, operations planners working in environments where the software either helps or gets in the way. The stakes are real and the problems are hard, which is exactly what makes this role interesting.

At IFS, product design means owning the full problem, not just the screens. You'll work in a cross-functional squad alongside engineers and product managers, with the scope and support to do the work properly. From problem framing through to something shipped and measured.

But the deeper question is harder than that. The industries IFS serves (field service, asset management, manufacturing, supply chain) are changing faster than the software that runs them. By 2030, we're not confident the interface paradigms we rely on today will still be the right ones. AI, ambient computing, voice, autonomous systems: any of these could fundamentally change how an operations planner or a field engineer interacts with software, or whether they interact with it at all.

That's not a problem we've solved. It's the problem you'd be working on.

Responsibilities

  • Product Design
  • Own design for defined feature areas end-to-end — from problem framing through to production-ready Figma files, with a clear rationale for every decision
  • Work in a cross-functional squad with engineers and PMs, making real decisions rather than executing on someone else's brief
  • Present design thinking to stakeholders with confidence — handling pushback with evidence, not just conviction
  • Discovery & Research
  • Plan and run user interviews, JTBD analysis, and journey mapping independently — turning findings into clear design direction, not just a readout
  • Track quantitative signals alongside qualitative insight, and use both to drive iteration
  • AI & Emerging Technology
  • Design AI-driven features with a clear understanding of where AI helps and where it introduces risk — prompts, fallbacks, and human-in-the-loop moments included
  • Bring a genuine perspective on how the interfaces we're building today might become obsolete — and what should replace them
  • Design Systems & Quality
  • Contribute to the IFS design system by proposing reusable components and patterns rather than designing one-offs
  • Apply WCAG 2.1+ accessibility standards from the start, and design for edge cases, error states, and real-world data — not just the happy path
  • You'll know it's working when your work ships, holds up in the field, and raises the bar for the next thing. Concretely: task success rates improve, UX-related support tickets drop, and the squad reaches for your work as a reference rather than a starting point.

Requirements

  • You may be a good fit if you:
  • You have at least eight years of end-to-end product design experience — from discovery through to shipped product — and you can point to work that reflects real ownership, not just execution
  • You're comfortable running your own research: planning the study, conducting interviews, synthesising findings, and turning them into a clear design direction
  • You know how to work in a cross-functional squad — making real decisions alongside engineers and PMs, not waiting to be handed a brief
  • You know Figma well and have the visual craft to back your thinking up
  • You treat accessibility as a design constraint from the start, not a checklist at the end
  • You've thought seriously about what AI means for the interfaces you build — not just as a feature to add, but as something that changes the fundamental design problem
  • You measure your work — task success rates, support ticket volume, adoption — and use those signals to drive the next iteration
  • Strong candidates may also have:
  • Experience shipping AI-driven features — prompts, fallbacks, human-in-the-loop moments — not just awareness of the concepts
  • Familiarity with design tokens, contribution models, and what it means to design for a system rather than a screen
  • Some exposure to quantitative signals: task success rates, funnel data, or A/B results — and a habit of using them
  • Additional Information
  • We embrace flexibility and hybrid work opportunities to support diverse needs and lifestyles, while also valuing inclusive workplace experiences. By fostering a sense of community, we drive innovation, strengthen connections, and nurture belonging. Our commitment ensures you can work in a way that suits you best, while also engaging with colleagues to share ideas and build meaningful relationships.
  • Company Description
  • We’re rebuilding IFS around AI, and we’re looking for a designer who has already shipped it — not someone who has read about it. That’s the first thing we’ll look for, so please lead with it.
  • You’d be designing for maintenance engineers, field service technicians and operations planners: people whose work depends on the software either helping or getting in the way. The stakes are real and the problems are hard, which is exactly what makes this interesting.
  • The deeper question is harder. The industries we serve — field service, asset management, manufacturing, supply chain — are changing faster than the software that runs them. By 2030 we’re not confident the interface paradigms we rely on today will still be the right ones. AI, ambient computing, voice, autonomous systems: any of these could change how an operations planner or a field engineer works, or whether they interact with software at all. That’s not a problem we’ve solved. It’s the problem you’d be working on.
  • What we need to see
  • Four things. We read every application against them.
  • AI you’ve shipped, recently. You’ve designed AI features that went into production in roughly the last two years, and you can show us. Assistive, generative or agentic all count. What we want to understand is what the AI actually did for the user, and how you handled it being wrong — confidence thresholds, fallbacks, review steps, correction paths, what someone sees on a bad output, how you evaluated it with real users. Listing “AI”, “LLM” or “prompt engineering” as skills won’t tell us anything. Neither will a chat panel with nothing said about what happens when the model gets it wrong.
  • Scope beyond one product. You’ve set direction that crossed more than one product or team, over a year or more, that other designers then worked inside. Work that outlasted the project. Problems you chose rather than were handed. Things you decided not to build, and why. We read the scope, not the job title — titles differ everywhere, and plenty of people titled Senior are operating at this level.
  • You run your own research. You plan the study, do the interviews, synthesise it and turn it into design direction. Tell us about one you ran and what changed because of it.
  • You own outcomes, not screens. End to end, from framing the problem to something shipped and measured. Name the numbers you moved — task success, support ticket volume, adoption — and a decision you argued for and won.
  • Your portfolio
  • Please include a link, and a password if it needs one. We will look at it, and for this role it carries real weight.
  • What helps us: work we can find quickly, presented with care, where it’s clear what you made. Show us the finished thing, not only the process behind it. What doesn’t help: a site that takes a long time to load, or one where we have to scroll past a lot of material to reach the actual work.
  • If you don’t have a portfolio site, send work samples. Plenty of strong people apply without one and we’d rather see the work than lose you over a link.
  • IFS is a billion-dollar revenue company with 7000+ employees on all continents. We deliver award-winning enterprise software solutions through the use of embedded digital innovation and a single cloud-based platform to help businesses be their best when it really matters–at the Moment of Service.
  • At IFS, we're flexible, we're innovative, and we're focused not only on how we can engage with our customers, but on how we can make a real change and have a worldwide impact. We help solve some of society's greatest challenges, fostering a better future through our agility, collaboration, and trust.
  • We celebrate diversity and accept that there are so many different perspectives in this world. As a truly international company serving people from around the globe, we realize that our success is tantamount to the respect we have for those different points of view.
  • By joining our team, you will have the opportunity to be part of a global, diverse environment; you will be joining a winning team with a commitment to sustainability; and a company where we get things done so that you can make a positive impact on the world.
  • We're looking for innovative and original thinkers to work in an environment where you can MakeYourMoment so that we can help others make theirs.
  • If you want to change the status quo, we'll help you make your moment. Join Team Purple. Join IFS.

Where you’d work

Part of the week in the office

You can work from

  • United Kingdom

About the company

IFS

  • Industry: SaaS

Office in United Kingdom

Also hiring in London, United Kingdom, United States, Madrid, Spain and 8 more places

10 of their 42 open roles are remote

Your chances

We've checked whether it's still hiring and how crowded it is.

  • 19 checks run
  • 0 red flags

Still hiring?

13 checks

No red flags

How crowded?

6 checks

No red flags

Fits Me

How well does this role fit you?

Answer a few questions or drop your CV, and every role gets a fit score with the reasons, this one first.

  • Your field
  • Level
  • Stack
  • Work model
  • Salary floor
  • Must-haves
Details13 facts · Role, Location, Compensation, Employment, Company
Tech stack
  • Figma
  • User research
Seniority
Principal
Type
Full-time
Industry
SaaS
Specialty
Product
Region
United Kingdom
Show 7 more factsShow less

Role

Category
Design
Specialty
Product
Seniority
Principal
Experience
6+ years
Tech stack
  • Figma
  • User research

Location

Work model
Hybrid
Region
United Kingdom
Office
  • United Kingdom
Remote from
  • United Kingdom

Compensation

Salary
Salary by agreement
Pay period
Annual

Employment

Type
Full-time

Company

Industry
SaaS

Something wrong with this vacancy?

Similar vacancies

Share this vacancy

What's wrong with it?

The employer never sees who reported.

Reason