Product Manager, Orchestration Platform

Felix Technologies•San Francisco, CA

2d•Remote

About The Position

Félix is hiring a senior product manager to lead its orchestration platform, the core infrastructure that runs remittance transactions end to end. The platform manages long-running, stateful workflows involving routing, compliance checks, partner calls, payouts, reconciliation, retries, and compensation when steps fail. Remittance is the platform’s first product, and the company intends for future products to use this layer rather than build their own transaction orchestration. The role defines the platform’s scope, guarantees, and non-goals; determines which capabilities should be platform primitives versus product-specific; and sequences the changes needed to onboard a second product. It also shapes the interfaces, semantics, documentation, onboarding, and observability that engineering teams use to build on and operate the platform. The Product Manager owns the platform engineering team’s roadmap and success metrics, balancing remittance reliability with platform investment. They represent the platform to operations, compliance, and finance, and partner with the engineering lead on architecture decisions with product implications. The role is remote currently, with a future transition to a hybrid setup.

Requirements

At least 5 years of product management experience, including at least 3 years owning a platform, infrastructure, API, or backend product primarily used by other engineering teams; equivalent competencies will also be considered.
Experience shipping a product other teams built on and understanding the consequences of its abstractions, including concrete examples of what did not work as intended; equivalent competencies will also be considered.
Strong grounding in distributed-systems concepts, including asynchronous processing, eventual consistency, at-least-once delivery, idempotency, compensation versus rollback, and failure modes of long-running workflows; equivalent competencies will also be considered.
Ability to participate as a peer in design conversations with senior engineers; equivalent competencies will also be considered.
Experience in payments, remittance, banking, ledger, or transaction processing, with sufficient understanding of settlement, reconciliation, payout partners, and compliance screening to identify where domain-specific logic ends; equivalent competencies will also be considered.
Exceptional written communication, with the ability to create specs and contracts that others can rely on; equivalent competencies will also be considered.
Comfort working directly with data, including querying, reading dashboards, and investigating anomalies without an intermediary; equivalent competencies will also be considered.
A track record of saying no to powerful internal stakeholders and being right often enough that they continued to rely on the person.

Nice To Haves

Hands-on product experience with a workflow or durable-execution engine such as Temporal, Cadence, Step Functions, Camunda, or an in-house equivalent.
Experience owning platform reliability outcomes, not just features.

Responsibilities

Define the orchestration platform’s boundaries, guarantees, and non-goals.
Decide which capabilities are platform primitives and which belong in consuming products.
Sequence the core platform changes required before a second product can onboard, and define the remittance migration approach as the platform evolves.
Define the contracts teams build against, including workflow interfaces, idempotency, retry and compensation semantics, timeouts, state visibility, and SLAs.
Develop the documentation, onboarding, and observability tooling that make the platform self-serve and operable.
Run the platform engineering team’s roadmap, balancing remittance reliability against platform investment.
Own platform success metrics, including workflow success rates, time-to-completion, manual intervention rate, time to resolve stuck workflows, and time-to-integrate.
Represent the platform to operations, compliance, and finance.
Partner with the engineering lead on architecture decisions with product consequences.