About Bastion

Bastion provides the regulated infrastructure businesses need to hold, move, and issue stablecoins. Our platform combines custodial wallets, global payment orchestration, and stablecoin issuance. Customers can use each product independently or connect them into a single end-to-end flow. We operate through our own regulated entities, with compliance and risk controls built directly into the platform. We can also support customers operating under their own licenses with the compliance and financial operations required to run their programs.

Overview

We are looking for a Product Manager to own our Shared Services vertical, the set of foundational capabilities that every other product area at Bastion depends on. You'll turn ambiguous, compliance-heavy problems into clear, sequenced, shippable work. You'll own the roadmap, requirements, compliance checkpoints, quality bar, and stakeholder communication for a vertical that gates customer commitments across the platform. Shared Services sits where product, engineering, and compliance meet. Much of the work centers on the controls and obligations that make stablecoin infrastructure trustworthy: identity and due-diligence flows, third-party risk controls, regulatory reporting, and the policies that govern how money moves. This is a high-leverage IC role with real ownership from week one. It may be up-leveled to Senior PM depending on the candidate and interview performance. We are open to candidates anywhere in the United States, with an advantage for those in (or willing to relocate or travel often to) New York City. No prior experience working with stablecoins is required. We have a preference for prior experience with fintech, compliance, or risk.

Work to Be Done

Instead of a list of requirements, we want to give you a directional look into the first 30, 90, and 180 days on the job. We are a startup, so the pace is fast and the specific work will change. People who thrive here are finding ways to contribute in their first week, and fully productive in their third month. If you think this is something you can handle, we will be excited to speak with you.

First 30 days: Learn the vertical AND take work off the table

• Map the Shared Services surface area: the foundational capabilities other verticals depend on, their current state, and where delivery risk is concentrated
• Meet your partners in Engineering, Compliance, and GTM; learn the escalation paths and how Shared Services work gates commitments elsewhere
• Take ownership of requirements for at least one active compliance-critical workstream and turn it into clear, sequenced, engineer-ready specs
• Stand up a lightweight triage cadence so incoming requirements and issues stop piling up
• Ship or unblock visible progress on at least one customer-gating milestone
• Outcomes

- A clear picture of the Shared Services roadmap and how its items gate customer commitments - Partners know what you own and how to route work to you - At least one workstream materially advanced through sharper requirements and sequencing

By 90 days: Own the roadmap and run the cadence

• Own the Shared Services roadmap end to end: themes, sequencing, milestones, and compliance checkpoints aligned to company priorities
• Run a predictable operating rhythm (planning, triage, risk tracking, and stakeholder updates) that Engineering and Compliance can rely on
• Drive requirements and delivery across several concurrent regulated workstreams, holding the quality bar on each
• Partner with Compliance to define and track checkpoints that keep flows defensible without stalling delivery
• Keep stakeholders across verticals current on status, risks, and tradeoffs for the items that gate their commitments
• Outcomes

- Shared Services has a clear, sequenced roadmap with defined compliance checkpoints - Delivery runs on a predictable cadence with proactive risk management - Measurable progress on the workstreams that gate customer commitments

By 180 days: Scale the vertical's reliability

• Sustain delivery across several regulated workstreams with the quality bar consistently met
• Build the instrumentation and feedback loops that make prioritization and compliance tracking repeatable rather than ad hoc
• Institutionalize the requirements, triage, and checkpoint practices so the vertical runs consistently as load grows
• Anticipate upcoming regulatory and customer obligations and get ahead of them in the roadmap
• Find ways to reduce recurring load on Engineering through better sequencing and reusable capability
• Outcomes

- Shared Services operates with repeatable processes and clear decision-making - Compliance checkpoints and quality bars are documented and consistently applied - Clear, measurable reduction in delivery ambiguity for the teams that depend on the vertical

Some challenges you might tackle

• Turning open-ended compliance obligations (identity and due-diligence flows, third-party risk controls, regulatory reporting, travel-rule requirements) into clear, shippable product work
• Sequencing a heavily loaded vertical so the highest-gating items land first
• Reasoning clearly about stablecoin infrastructure (issuance, custody, settlement, and on-chain movement) to make sound product tradeoffs
• Keeping a reliable triage and requirements cadence under a heavy, shifting workload
• Creating clarity from ambiguity when obligations are incomplete or customer needs conflict