PrincipalEngineer,Infrastructure

What This Role Is Every product Manifest Global operates — Cialfo, BridgeU, Explore, Kaaiser — runs on infrastructure. The AWS platform underneath them handles the traffic from 2,000+ schools, hundreds of thousands of students, and 1,000+ university partners across 50+ countries. When it works well, nobody notices. When it doesn't, a counselor can't access a student's application, a university's outreach campaign stalls, a placement goes wrong. The infrastructure is invisible only when it's excellent. Most multi-brand technology groups at this scale have solved the infrastructure problem the obvious way: each product team builds its own, defends its own, and calls on a central team as a last resort. The result is fragmentation — duplicated systems, inconsistent reliability, and an engineering tax that compounds quietly until it starts slowing everything down. The better answer is a shared platform that product teams consume freely, that raises the engineering standard across the portfolio without requiring constant coordination, and that gets more valuable the more brands and engineers build on top of it. Manifest is building that platform. The Platform Team is the engineering group responsible for it — the paved paths, the CI/CD pipelines, the observability layer, the self-service tooling that lets a product engineer in one brand build and ship without waiting on infrastructure. The work spans the full Manifest portfolio. The leverage is real. And the person who owns the infrastructure layer is the person who decides, in practical terms, what kind of engineering organisation Manifest becomes. This role owns the AWS infrastructure platform across Manifest's family of products — and the mandate to turn it from a per-brand dependency into a shared, self-service foundation every engineering team builds on freely. What Makes This Role Different Most infrastructure roles at this scale ask you to maintain something that already exists. This one asks you to redesign someth