The IFS guide
45 of 46 topics written. The rest show their plan from the topic map.
This guide prepares you for your first weeks as Principal Product Manager, IDP & Agentic AI at IFS [posting: pm]. Each topic explains its subject from the ground up. A few ranked materials follow, for when you want to go deeper.
What this guide is, and what it isn't
- It explains. You can follow every topic without opening a material. An earlier study plan listed 201 sources, and you read 2, so the text here does the work.
- It's a snapshot from before your first day. It holds public knowledge and what the hiring process revealed. Nothing you learn inside IFS after you start comes back into it.
- It isn't IFS documentation. Where nobody outside IFS knows the answer, a topic says so and links an open question. The open questions page collects all of them for your first weeks.
- It isn't interview preparation. It scripts nothing for you to say.
Every fact about IFS carries a tag that says where it came from.
- [posting: pm] is a job posting, here your own.
- [public] is a public page, linked.
- [inference] is this guide's reasoning from facts the text names.
- [unverified] is a single weak source, never stated as fact.
How the ranks work
Every topic, section and material has one of four ranks. The rank says how much of your time it deserves.
| Rank | A topic or a section | A material, and what you do with it |
|---|---|---|
| Critical | The seat can't be done well without it in the first 30 days | Read or watch it in full. It gives something this guide can't |
| High | Needed to follow core conversations, or needed within 90 days | Skim it, 10 to 15 minutes |
| Medium | Useful background that helps you read other topics | Skim it faster, about 5 minutes |
| Context | Orientation and completeness. You can skip a context section without losing the thread | Optional. Open it when you need it |
No section ranks above its topic. Critical materials are few, and each one says what it gives that the text doesn't. High and medium materials differ by how much a skim pays, not by when you read them.
How to read it
This guide has three tiers. Each tier page quotes your own definition of it.
- Base is the platform you're optimising, and the company around it.
- Practical is the practice of fixing it: methods, research, frameworks and metrics.
- Modern is what today's tools change about the problem and about the solutions.
Each tier page opens with a map of its topics. Below this text, "Where to start" gives the reading order: the critical topics first, with the few high topics they build on. The other high topics follow, then the medium ones.
Every topic page runs in the same order: why it matters in the seat, a short version, the explanation, and what is known and unknown at IFS. Where practitioners disagree, it takes a position and gives the case against. The materials and what this guide couldn't verify close the page.
Private blocks
Some facts come from your hiring conversations and the material you received for them. People shared them with you as a candidate, so they're private. Each one sits in a private block that stays closed until you open it.
- A closed block shows only its label. The label names the subject, never the fact, so a page can be open where someone else sees the screen.
- "Open all private facts" opens every block on a page, and closes them again.
- Search doesn't look inside private blocks, and a closed block prints its label only.
- Every page still reads with its blocks closed.
Where to start
Read the critical topics first, in this order. Each step leans on the one before it.
1The seat and the map
2Events, then what a team has to do
3Identity, frameworks, platforms
4The discipline, the role, the first weeks
5Frameworks, measurement, friction, economics
6Moving teams
7Influence
8AI-assisted development, then agents as users of the platform
Then the other high topics 14
- B03IFS Cloud: the heritage product and its stack
- B05How IFS builds software: organisation, teams, practice
- B07Containers, Kubernetes and AKS
- B08From commit to production: CI/CD, GitOps, infrastructure as code
- B10Kafka and Redpanda: how the event backbone works
- B18From deployed to in customers' hands
- P07Deciding with small numbers
- P13Self-service and the ticket queue
- M02Spec-driven development and agentic engineering practice
- M03What AI-native products need from a platform
- M06AI-assisted migration and modernisation
- M07AI inside the developer platform
- M09Measuring AI's effect on engineering
- M10Your own AI workflow in the seat
Then the medium topics 11
- B02IFS: the business the platform serves
- B04IFS's AI products and bets
- B12Event contracts: schemas, compatibility and catalogues
- B14The rest of the stack: Go, PostgreSQL, React
- B15Observability and reliability
- B19Why vendors re-platform: legacy modernisation
- P14Guardrails: reliability, security and tenancy under delivery pressure
- P15Platform adoption in the wild: cases and failure modes
- P17Leading change across an engineering organisation
- M04Governing agents on a multi-tenant platform
- M08The platform engineering toolset in 2026
The three tiers
How long it takes
Reading time is words divided by 220 a minute. Written topics are counted. Planned topics are estimated at the middle of their size, so the totals change as topics are written. The sizes are S, 800 to 1,500 words; M, 1,500 to 2,500; L, 2,500 to 3,500; and XL, 3,500 to 4,500, for a few exceptions.
| Tier | Topics | Written | Written, reading time | All topics |
|---|---|---|---|---|
| Base | 19 | 18 | 3 h 40 min | about 3 h 49 min |
| Practical | 17 | 17 | 3 h 46 min | 3 h 46 min |
| Modern | 10 | 10 | 1 h 58 min | 1 h 58 min |
| All tiers | 46 | 45 | 9 h 24 min | about 9 h 33 min |
| Topic rank | Topics | Written | Written, reading time | All topics |
|---|---|---|---|---|
| Critical | 17 | 17 | 4 h 9 min | 4 h 9 min |
| High | 18 | 18 | 3 h 34 min | 3 h 34 min |
| Medium | 11 | 10 | 1 h 41 min | about 1 h 50 min |
| Materials in written topics | Count | Listed time | What you do | Your time |
|---|---|---|---|---|
| Critical | 7 | 1 h 28 min | Read in full | 1 h 28 min |
| High | 91 | 38 h 36 min | Skim, 10 to 15 min | up to 18 h 42 min |
| Medium | 89 | 22 h 47 min | Skim, about 5 min | up to 7 h 18 min |
| Context | 31 | 10 h 45 min | Open when needed | Optional |