Product Engineering Lead

Manifest Global empowers in building companies that connect the world towards growth, prosperity, and innovation. Our portfolio includes trailblazer brands such as Cialfo, BridgeU, Explore, Kaaiser, EduGo, and Flow AI and which are dedicated to expanding global student mobility by serving their respective stakeholders in the ecosystem.

Our Mission

To create a world where every student, regardless of their ethnicity, nationality, socio-economic status, and learning preference, gets equal access to higher education through our world-class network of portfolio brands; a network that globally connects community stakeholders that provide the finest resources and support material, anywhere in the world and at any time.

What This Role Is

Every year, millions of students make a decision that sets the direction of their lives: where to study, what to study, and which country they will build a career in. That decision runs through a counselor's office, a university's admissions funnel, a family's conversation with an advisor, and a visa timeline — and almost none of the signal from one step reaches the next. Manifest exists to connect that journey, and it does it through products that each serve one part of it exceptionally well.

This role owns one of those parts at a time. As a Product Engineering Lead, you take full technical ownership of a single business platform, accountable for one thing above all: making the user that platform serves successful at what they are trying to do. You go deep on that user — their workflow, their friction, what "success" actually means for them — and you build the product that delivers it.

This is a hands-on individual contributor seat. The engineers building on your platform report to you — none or a handful today, growing as the platform does. Your leverage comes from how completely you understand one stakeholder, how good the product you build for them becomes, and how well you bring the rest of the business along with you.

You report to the Engineering Manager. You are assessed on two things: the delivery of the platform you're leading and the product-outcome metrics aligned to it — the measures of whether the user you serve is genuinely more successful. Both move together, and both are how your performance is judged.

You do this inside a larger system. Manifest is several products becoming one connected whole, with a shared intelligence layer running underneath. You don't own that layer or the architecture that spans the platforms — but you understand the portfolio deeply, you know how your platform connects to the others, and you build in a way that draws on the shared layer and feeds signal back into it. Your focus is narrow by design. Your awareness of the whole is not.

One thing you do not do is build your own plumbing. Auth, notifications, reporting and integrations come from the shared layer. Infrastructure and quality come from their own lines. Your accountability is for using them rather than quietly working around them.

How the Role Grows

You own one platform, and you own it for as long as it is yours to build. Growth here is not a move sideways — it is the platform getting bigger underneath you. The seat starts at one engineer or none, and as the platform earns investment, engineers are added under you rather than beside you; the model is deliberately built so that going from one person to five needs the lead to have grown into it, not a new manager above it. Past that there is a real choice rather than a ladder. Some people go deeper on the IC track toward staff, where the scope stops being one platform and becomes the systems every platform is built on. Others find they want the wider org and move toward engineering management. We would rather you choose honestly than default. The one thing not on the table is drifting out of the code.

What Makes This Role Different

Most lead engineer roles ask you to work through a backlog. This one asks you to own an outcome for a specific user and build whatever it takes to get there — including the quality of it and what happens to it in production, and including the AI-native product that user has never had before.

The leverage is the Manifest ecosystem. You are not building for your user from scratch and in isolation. You have a shared intelligence layer to build on, signal from across the portfolio to draw on, and a company that is AI-native from first principles. That means you can build recommendations, workflows, and agentic experiences for your platform that a standalone product in that space could never see well enough to build.

The timing is the argument. Across Manifest's platforms, AI is at the point where it stops being a feature and becomes the way the product works. The person who defines that for a given user, now, sets the direction for years.

What's Hard — And Why It's Worth It

The best engineers we know are drawn to the hard version of a problem, not the safe one. So here's the honest shape of it.

You go deep on one platform — often as its only engineer — but you build on a shared layer with its own gravity and other platforms pulling on it. Getting what your user needs sometimes means making your case against someone else's, and not always winning. That friction isn't noise. It's what forces the sharpest thinking you'll do here, and the lead who learns to fight for their user while strengthening the whole becomes the rarest kind of operator this company has.

The business leader who runs your platform knows their market cold and has their own conviction about the roadmap. Sometimes your data will say they're wrong. The moment you tell them that — in the language of their own business — and come out with their trust intact is the moment you stop being an engineer who executes and become one leaders actually follow.

And depending on the platform, you may inherit it mid-stride: someone else's half-built roadmap, live commitments, a team already in motion. Decid