Technical Product Manager

TECHNICAL PRODUCT MANAGER

Product | Full-Time, Salaried | Reports to Head of Product
Company Seeking.com (Reflex Media)
Location Remote, anywhere in the USA
Compensation $145,000 to $190,000 base

Travel Required for team weeks, engineering deep dives, and quarterly planning in Las Vegas
About the Role

Seeking.com is the world's largest premium dating platform, founded and led by an MIT alumnus and headquartered in Las Vegas. We are a technical company. Our product is built on a set of microservices, internal tools, and third-party integrations that our engineering, moderation, support, and finance teams operate every day. Making that machine easy to understand and easy to run is the difference between a product team that ships and one that fights fires.

We are hiring the Technical Product Manager who owns the platform layer underneath the Seeking core experience. Our internal tools, our payments system, our content moderation stack, and the microservices behind them. This is the person who reads the code, walks the flow, sits with the engineers, and turns a tangled system into a clean one.

This role may also be a fit for candidates whose current title is Technical Product Manager, Platform PM, Infrastructure PM, API PM, Payments PM, Product Engineer with a systems bent, or Software Engineer who has moved into product ownership. If your day-to-day is turning technical complexity into simple, well-documented, well-instrumented systems, you should apply regardless of your current title.

This is the role for the Technical PM who is an expert at simplification, at organization, and at making complex systems easier to understand and easier to manage. If your instinct in a review is to add scope, this is not your role. If your instinct is to cut, clarify, and document, keep reading.
What You'll Own
Platform and Internal Systems Ownership

- Own the roadmap for the internal tools and microservices that support Seeking, including support and moderation tools, automated content moderation systems, the internal payments system, and the technical services that connect them.

- Treat every internal system as its own product, with a defined user, a metric, and a documented interface.

- Set quarterly OKRs for your surface and define both leading and lagging KPIs for every Key Result you own.

Simplification, Documentation, and Order

- Take systems that are messy and make them clean. Rename, restructure, deprecate, and consolidate until a new engineer can be productive on day two.

- Own the technical documentation for the surfaces you cover in Confluence. Diagrams, data flows, API contracts, runbooks. If it is not documented, it is not shipped.

- Write specs, user stories, and acceptance criteria clean enough that an engineer using Claude Code can build directly from them.

Doing the Work, Not Just Briefing It

- Prototype endpoints, admin screens, and internal tools yourself before they hit the engineering backlog. Postman, a Figma flow, a working prototype in code, or a Claude Code or Cursor session that produces a testable artifact.

- Write SQL against the production data warehouse, read the code, and walk the calls yourself. Do not ask an engineer to answer a question you can answer.

- Use agent-assisted environments to produce real, testable artifacts inside a single sitting.

Collaboration Across Teams

- Serve as the primary translator between the engineering team and the non-technical teams (support, moderation, marketing, finance) who depend on these systems.

- Ensure technical feasibility on every proposal and drive prioritization of what actually gets built.

- Communicate updates, tradeoffs, and risks to stakeholders in plain, direct language.

Payments and Moderation

- Own the internal payments system as its own product. Understand the flow end-to-end: authorization, capture, settlement, reconciliation, refunds, chargebacks, tokenization, and PCI scope.

- Own the moderation and support tooling that keeps