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 the platform safe and the members supported, including our LLM-based message moderation pipeline.
• Track the metrics that matter: transaction success rate, decline rate by gateway, latency, ticket time-to-resolution, moderation SLA.

Data-Driven Decision-Making

• Instrument every feature with the data layer in mind from day one, using Amplitude, Mixpanel, Firebase, or comparable.
• Analyze data to measure the success of every technical change you ship, and follow up with the fix or the deprecation.
• Propose data-driven improvements to the systems you own, and back them with the numbers.

Required Qualifications

• Engineering degree. Bachelor's in Computer Science, Software Engineering, Electrical Engineering, or a related technical field. A business degree on its own does not qualify. If you did not train as an engineer, this is not the role for you.
• Three to six years in a technical product role, ideally with an engineering background as an individual contributor before moving into product.
• Working knowledge of system architecture, REST APIs, microservices, and database design. You can read the code, sketch the data flow on a whiteboard, and explain the tradeoffs in an integration.
• SQL fluency. You can write, read, and debug non-trivial queries against a production warehouse without help.
• Referenceable shipping history in technical product work. At least one platform, API, or internal system you personally owned end-to-end, with the metric you moved and by how much.
• Daily, fluent use of agentic AI tools (Claude, Claude Code, Cursor, MCP-based workflows, or comparable). You will be asked to demonstrate this in the interview.
• Simplification instinct. Show us a system you took over that was messy and left cleaner. Fewer moving parts, better documentation, a metric that improved because of the cleanup.
• Outstanding written communication. Specs, PRDs, runbooks, decision docs. Your writing should be a competitive advantage, and it should be shorter than the reader expects.
• Presentation skill. You can walk a room through a complex system in ten minutes without losing anyone. Direct answers, no meandering. If a simple question gets a ten-minute answer, this is not the role for you.
• Fluency in the operating stack. Confluence for documentation, Jira for shipping, Monday for cross-team scheduling. You can operate the stack without needing a project manager to do it for you.

Preferred Qualifications

• Hands-on background as a software engineer before moving into product, ideally in backend, platform, or infrastructure.
• Working experience with payments on a technical level: systems, flow, entities, PCI scope, and reconciliation.
• Working experience with support ticketing and content moderation systems, including LLM-based moderation pipelines.
• Cloud fluency (AWS preferred), including a working understanding of DevOps practices and deployment pipelines.
• Prior experience in dating, social, marketplace, subscription, or other consumer-focused product categories.
• Public work we can look at: a technical portfolio, an open-source contribution, a spec you wrote, a system you diagrammed, or an agent toolkit you have shared.
• Master's degree in Engineering, Computer Science, or a related field.