Director of Product

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.

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.

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

• 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.

• 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.

• Design, run, and interpret A/B tests on growth, engagement, retention, and monetization.
• Instrument every feature with the data layer in mind from day one.
• Use product analytics tools (Mixpanel, Posthog, or similar) to drive every meaningful decision.
• Bring evidence, not opinions, to every roadmap conversation.

• Coach a small team of Product Associates and mid‑level Product hires through real work.
• Hire the next wave of Product talent against the standard you set.
• Define the playbook that lets Seeking train and retain operators who work this way.
• Create the conditions for your team to outperform their previous best.

• Build, refine, and document the agent workflows that let your team produce at scale.
• Codify your operating system so others can adopt it.
• Evaluate new tools the moment they emerge and integrate the ones that earn their place.
• Push the boundary of what a small product team can deliver in a quarter.

• As you prove the model, expand into oversight of product engineering.
• Help us define what the modern, agent‑augmented product and engineering function looks like at Seeking.
• Shape company‑wide adoption of agentic AI inside product development.

• Seven or more years in product. With meaningful time in Senior PM, Principal PM, Group PM, Head of Product, or Director roles. Title‑flexible, track record is what we care about.
• Referenceable shipping history. Specific features or products you led, with specific outcomes. If you cannot name the metric you moved and by how much, this is not the role for you.
• History of developing other product people. People who reported to you, worked…