Senior Product Manager

About the company

Tapcheck provides an earned-wage-access mobile platform that integrates with payroll and HR systems to enable hourly employees to access earned pay advances at no cost to employers.

About this role

This is a remote-friendly role. Ideally, candidates will sit in the following states: AL, AZ, CA, CO, DC, DE, FL, GA, ID, IL, LA, MA, MO, NC, NH, NJ, NV, NY, OR, OH, PA, RI, SC, TX, VA, WA, WI. About the Job Tapcheck moves real money to hourly workers every day — across bank rails and card rails, inside cutoff windows, at volumes that grow every quarter. The rails work. What's still being built is the platform underneath them: a payments layer designed as services, with clean contracts, defined SLAs, and the ability to absorb the next rail, the next product line, and the next order of magnitude without being rewritten. We're hiring a Senior Product Manager who knows payments at the settlement level and builds like a platform engineer thinks. You'll own money movement end to end — bank payment types, the payroll card program, and payout experiences — and you'll build it as reusable infrastructure that other teams consume through APIs rather than one-off integrations. This is a hands-on seat. You'll write the requirements yourself, work embedded with engineering through delivery, and stay accountable through production validation. You'll also work with real ambiguity. Documentation is incomplete, a lot of current state lives in people's heads, and problems arrive as a recurring symptom rather than a scoped request. You'll be expected to decide with partial information, write down what you assumed, and move — not wait for someone to hand you clarity. And because nothing here ships without Finance, Legal, Payment Operations, Engineering, and often an external partner agreeing, you'll need to build that alignment yourself, ahead of the meeting rather than in it. Nobody in this seat succeeds on authority; they succeed on being consistently right in writing and easy to say yes to. If you have under-the-hood knowledge of how funds actually settle, you obsess over failure paths because that's where payment systems break, and you'd rather build the service properly than ship the feature twice — this is the seat. What You'll Do Own money movement end to end - Bank payment types: Same-Day ACH, RTP, wires, push-to-card — including returns, rejections, retries, cutoff windows, settlement confirmation, and reconciliation - The payroll card program: issuing, BIN eligibility, cardholder lifecycle, network compliance, processor configuration - Employer and worker payout surfaces, including file upload, funding windows, and failure handling - Routing and waterfall logic — the tradeoffs between speed, cost, and settlement certainty that decide whether a rail is trustworthy Build it as a platform - Design payments capability as services with explicit API and data contracts, so new rails, products, and partners plug in rather than requiring rework - Define the abstractions that keep the platform rail-agnostic — so adding a rail is a configuration and integration exercise, not a re-architecture - Define and own the SLAs and performance benchmarks payment services run against, and build the observability to prove them - Design for multi-tenant scale, backward compatibility, and clean migration paths where changes have blast radius across consuming teams Write and deliver - Produce the detailed requirements yourself: PRDs, user stories, acceptance criteria, state and error handling, field-level mapping, technical scoping - Work embedded with engineering day to day — discovery, refinement, sprint planning, standup, demos — answering questions in the moment rather than next cycle - Direct augmented engineering capacity: define work precisely enough for distributed teams to build correctly, sequence it, review what comes back, hold the bar - Carry work through production validation. Read the logs, query the data, walk the flow, confirm the fix held Test, measure, and prove it - Define success metrics and guardrails before you build, not after - Run real experiments where they apply — payout selection, funding flows, card activation, error and retry messaging, default rail selection — with honest sample sizing and honest readouts, including the ones that don't go your way - Use staged rollout as the instrument where experimentation isn't safe: canary and percentage releases, holdback cohorts, pre-declared guardrail metrics, and rollback criteria agreed in advance - Know the difference between the two, and be able to explain to a stakeholder why a given change gets one and not the other - Build the analytics and instrumentation you need to answer questions yourself instead of filing a request Bring order to ambiguity - Take problems that arrive as a symptom, a complaint, or a recurring incident and turn them into scoped, sequenced, owned work - Decide with incomplete information, state your assumptions plainly, and revisit them when evidence changes - Distinguish reversible decisions from irreversible ones and spend your rigor accordingly - Reverse-engineer current state where documentation is thin, and leave it better documented than you found it Build alignment across the company and with partners - Get to yes with Engineering, Payment Operations, Finance, Legal and Compliance, Customer Success, and Business Development — pre-wiring decisions with the people who have to live with them rather than surfacing them cold in a meeting - Write the document that makes the decision easy: options, tradeoffs, a clear recommendation, and what you need from each party - Negotiate contested ownership boundaries in good faith, and make the seams explicit so they stop being relitigated - Manage the product relationship with sponsor bank, processor, card network, and data aggregator counterparts - Write clearly enough that the CEO, CFO, and GC can make decisions from what you put in front of them Design for resilience - Treat edge cases and failure scenarios as first-class design work, not error states bolted on at the end - Build compliance, auditabi