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 positive 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 an