The operating system
behind the research.

Invisible work, visible impact.

Research Operations gets described as a behind-the-scenes function, and it is true: there is an enormous amount of invisible work in making research run. But calling it backstage misses what the role actually is. ReOps builds the rails that research strategy runs on. Researchers own the craft and the telling of it; ops builds the rails that carry it. It is the role that designs recruitment pipelines that bring in exactly the right participants while the team keeps its velocity. The role running constant experimentation so researchers stay at the frontier of AI workflows without carrying the tooling burden themselves. The role that builds the infrastructure insights travel on, from repositories to rituals. And quietly, persistently, the role that shapes the culture of the team doing all of it.

What it asks of you.

This role requires someone who values connection: strong relationships across the whole organization, well beyond research, because anything this team pushes out has to land and be received by people who trust the person bringing it. It requires a deep care for the human on the other side of the product, whether that is a dater opening an app or, in a b2b world, the employers and employees running their working lives on a platform. And it demands a double vision: caring intensely about the small, nuanced details that let an insight have impact, while stepping back to see the greater product development lifecycle and the ecosystem the work lives in.

That layering is why I love this work: strategy, creativity, innovation, and connection, all in one role.