Job Opportunities API

What This Role Is There are 1,000-plus universities across 100-plus countries trying to reach the right students, and almost none of them can tell you, with any confidence, why a given student converted. They can tell you volume. They can tell you which fair or campaign brought in the most leads. What they can rarely tell you is why a recommendation worked, or what a counselor, an applicant, or an admissions team actually needed to see in that moment to make a good decision faster. That gap between data and understanding is a design problem before it is anything else. Explore exists to close it. Launched in 2025 onto a network that already spans a thousand-plus university partners, it is an AI-powered outreach and intelligence platform still being built in public — the infrastructure is real, but the product experience that makes that infrastructure legible, trustworthy, and genuinely useful to the humans using it is still being written. That is not a caveat. It is the opportunity. Design at Explore sits at the exact point where product ambition meets human comprehension. Every dashboard, every recommendation surface, every workflow a university administrator or a counselor touches is either building trust in the system or quietly eroding it. There is no legacy interface to inherit and no established pattern library to lean on uncritically — the structures, the flows, and the design language itself are still being defined, and this role has a direct hand in defining them. You will own the design craft behind Explore's product experience — the systems, the flows, and the day-to-day partnership with product and engineering that turns a data platform into something universities actually want to open every day. What Makes This Role Different Most product design roles at this level ask you to execute inside a design system someone else already built. This one asks you to help build it. Explore's product surface — from university-facing dashboards to the outreach and intelligence tooling underneath them — is young enough that foundational decisions about structure, pattern, and interaction model are still live, and the person in this seat will shape a meaningful share of them. The Manifest ecosystem gives that work a head start no standalone competitor has. Explore's design language does not need to be invented in a vacuum — Cialfo and BridgeU have already spent years learning what counselors, school staff, and students actually need from an interface under real operational pressure, and Kaaiser's counseling experience adds a further layer of insight into how people make high-stakes education decisions. You inherit that pattern knowledge and get to decide what actually transfers to a university-facing, AI-native product, and what doesn't. This is also, deliberately, a build-stage role rather than a maintenance one. The decisions made in Explore's product design over the next year or two will be the ones later designers inherit as convention. Joining now means those foundational calls are still yours to make. What You Own The Explore product design language Own the design system and pattern library that Explore's product surfaces are built on, and keep it current as the product evolves Define interaction models for genuinely new problems — AI-driven outreach and intelligence tooling that does not have an obvious off-the-shelf pattern to borrow Translate what works in Cialfo's and BridgeU's counselor-facing experience into what a university-facing AI platform actually needs Product delivery, end to end Partner with product managers and engineers from early concept through shipped code on every major release, not just at the handoff points Turn ambiguous hypotheses about what universities need into concrete, testable product experiences Ensure design decisions are documented well enough that engineering can build against them with minimal back-and-forth Research and validat