Job Details

Director Of Product (AI-Native)

We are not hiring a Director to run a product organization the old way. We are hiring an operator who has already started running one the new way, and is ready to teach others to do the same.

Location: Remote, anywhere in the USA (Las Vegas, NV strongly preferred)

Company: Seeking.com (Reflex Media)

Department: Product

Reports To: Founder and CEO

Type: Full-Time, Salaried

Compensation: $200,000 to $280,000 base annually, plus performance bonus. The top of the range is reserved for candidates who can show prior Director-level outcomes and a working agentic operating model already in production use. Compensation is structured around impact, not prior title.

About Seeking

Seeking.com is the world's largest premium dating platform. Founded and led by an MIT alumnus, headquartered in Las Vegas, and operating as a hybrid-remote organization, we sit at the intersection of technology, consumer psychology, and product design at the highest level.

Our business is as much data science and artificial intelligence as it is human understanding. We create at the forefronts of psychology, economics, art, fashion, cinematography, and the science of human connection. Our mission is to help people foster genuine relationships and find love.

We think bigger than dating. We believe social platforms have a responsibility to help people build stronger, more positive relationships, with others and with themselves. We are rethinking how social networks can be redesigned to advance human connection and, ultimately, advance humanity as a whole. If that sounds ambitious, it is. We need people who are drawn to ambition, not intimidated by it.

The Role

Product leadership is changing fast. The traditional Director of Product who writes briefs, runs OKR cycles, and coordinates a team of ten through Jira is finished. We are not hiring against that model.

We are hiring a Director who is already operating in the new model. The kind of leader who can take a product idea on Monday morning and have a working, tested prototype by Friday afternoon, because Claude, Claude Code, MCP-based agent workflows, and a self-deployed agent fleet are extensions of how they think. The kind of leader who can do every layer of product work themselves: market research, competitive analysis, customer insight synthesis, product vision, prototype, UX design, software architecture thinking, cost and impact tradeoffs, spec writing. Then hand a clean, testable specification to a development team using Claude Code to build, test, QA, and ship.

This is not a Director role in the sense of managing many people. It is a Director role in the sense of setting the standard, owning the outcomes, and raising the next generation of operators who can work this way.

You will own Seeking's product. The strategy, the roadmap, the experiments, the design language, the prioritization, the bar for quality. You will lead a small team of Associates and mid-level Product hires, not because you need them to get the work done, but because we want you to develop them into operators who can work at your level. As you prove the model, your mandate expands. Over time, we expect this role to grow into oversight of product and engineering together, because the line between the two is getting thinner every quarter.

Why This Role Is Different

• You will not be a manager pretending to do product. You will personally lead the most important product bets. Wireframes, specs, prototypes, written experiments, instrumentation plans, design reviews. You are the craftsman, not the editor.
• You will operate at agent-augmented velocity. If you have not already built personal workflows that deploy agents to take work off your plate, this is not the role for you. If you have, you will find a company that understands what that means and gives you the room to prove it at scale.
• Your impact will be visible in weeks, not quarters. Seeking is a profitable, established platform with millions of users. Strategic bets you set in your first thirty days will be in front of real members the same month.
• You will set the bar for an entire function. Every product hire after you will be measured against the standard you set. Every Associate will learn how to work by watching you.
• The mandate grows with the proof. Show us this operating model works at the Director level, and the next quarter you are overseeing more than product. Show us you can develop talent, and we will let you build a function the way you would build it from scratch.

Who We Are Looking For

This is a role for a specific kind of leader. Read carefully before applying.

• You have led product before, and you want to lead in a new way. You have held Senior PM, Principal PM, Group PM, Head of Product, or Director roles. You have shipped product at scale. You can point to features and businesses you led and the specific outcomes you drove. What changed is that you have stopped doing the work the old way and you are looking for a company that will let you operate at the level you actually work at now.
• You are agent-native, not AI-curious. You use Claude, Claude Code, MCP servers, and similar tools every single day. You already have a portfolio of custom skills. You have set up your own agent workflows. You have a clear point of view on what agents should own and what you should keep in your own hands. You can show us the workflows, not just talk about them.
• You do the whole stack of product work yourself. Market research, competitive analysis, customer insight synthesis, product vision, prototyping in Figma or in code, UX design, software architecture, cost-impact tradeoffs, specification writing, instrumentation planning. You do all of it. You enjoy all of it. You believe that doing it yourself is what makes a leader trustworthy.
• You develop other people. People who have worked under you can name specific ways you made them better. You see developing other operators as a craft, not a tax. You want to build a team that thinks and ships the way you do.
• You are an obsessive UX thinker. You can articulate why a button feels wrong, why a flow loses users at step three, and why a competitor's onboarding lands harder than yours. You have strong opinions about how a premium consumer product should feel and you can defend them.
• You are technical. You can read code, run SQL, sketch a schema, reason about an API, and think clearly about software architecture. You do not need to write production code, but you need to specify it well enough that engineers want to work from your specs.
• You think in systems. You do not see a feature. You see the user motivation, the data event, the downstream retention impact, the support burden, the architectural cost, and three ways the same problem could be solved better.
• You have business instincts. Conversion, LTV, retention, monetization, payback period. You think about all of it without prompting. You understand a product has to work for the user and for the business or it does not exist for long.
• You are hungry, still. You have done the job. You could keep doing it the old way for years. You do not want to. You want to operate at a level the rest of your industry has not figured out yet.

What You Will Do

Your work spans strategy, execution, and people. In any given week, expect to:

Product Strategy and Roadmap

• Own and defend the Seeking product roadmap across web and native mobile.
• Translate business strategy into a sequenced, testable set of product bets.
• Set North Star and input metrics, and hold the line on them.
• Make difficult prioritization calls and explain your reasoning to the CEO and engineering leadership.
• Run quarterly planning and shape company-level product investment decisions.

Doing the Work, Not Just Briefing It

• Personally lead the highest-impact product bets from concept through launch.
• Conduct market research, competitive analysis, and customer insight synthesis.
• Design and prototype features in Framer, Stitch, Claude Design or code before they touch the engineering backlog.
• Use agent-assisted environments to produce real, testable artifacts inside a single sitting.
• Write specifications, user stories, and acceptance criteria so clean that engineers using Claude Code can build directly from them.

Experimentation and Data

• Design, run, and interpret A/B tests on growth, engagement, retention, and