Head of Product - Banking (Full Time)
Cosmos Labs
| Company | Cosmos Labs |
| Category | Product |
| Location | New York HQ |
| Remote | On-site (inferred) |
| Employment | Not stated |
| Level | Director |
| Salary | Not stated by the employer |
| Posted | 10 Jun 2026 |
| Last verified | 9 Aug 2026 |
| Source | Employer ATS (greenhouse) |
Description
About Cosmos Labs
Cosmos is seeking a Head of Product to lead the design and development of our Tokenized Deposits platform. Cosmos is the most popular open source DLT stack globally, and powers blockchains for financial leaders like Wells Fargo, Figure Markets, and 200+ others. Now, our team is building a groundbreaking tokenized deposit product built on top of trusted technology, with the aim to arm mid-sized and regional banks with modern DLT capabilities.
We are looking for an expert with deep, hands-on product experience in banking infrastructure, core banking software (e.g. FISERV/Jack Henry), order management platforms, and who also has a working knowledge of the operational dimensions of financial services businesses such as compliance, audit, and tax. You will report directly to the CEO, who is leading this initiative.
Role Overview
You will own the product strategy and execution for a tokenization product that enables financial institutions to interact seamlessly with tokenized assets, without requiring changes to their existing core banking systems. You will have massive ownership and responsibility - you will be able to design the product roadmap and lead it to commercial success.
Specifically, in this role, you will:
Define and evolve product requirements (PRDs), including detailed API specifications, reconciliation flows, and integration patterns
Partner with engineering and design to take the product from prototype to production
Work closely with our Head of Engineering and Co-CEO to craft our canonical product roadmap
Work with bank customers to validate and refine the product in real-world environments
Lead product ideation and translate concepts into tangible improvements across demos and production systems
Navigate internal and external stakeholders to drive adoption and successful implementation
Key Responsibilities
Tokenization Product Ownership
Own the tokenization product direction end-to-end.
Make the hard product design calls: write-back vs. omnibus model, batch vs. webhook sync, how to handle the two-phase finality gap between core posting and on-chain confirmation. On-prem versus cloud-native deployments.
Keep the product honest. For example, if something doesn't survive contact with a real bank's implementation requirements, kill it and replace it with something that does.
Report to key stakeholders and work closely with all departments to ship and build momentum around the product.
Be the voice of the customer in the room, and use your experience to design a product that will be impressive but believable
Bring the “banking perspective,” based on your years of experience integrating software at banks, or for banks
Customer Discovery
Run at least 2 hours per week of direct conversations with target banks, channel/distribution partners and payment fintechs.
Use these conversations to validate or kill product assumptions. Your job is to close the gap between what we think banks need and what they'll actually sign for.
Do not wait for banking adoption to improve the product - banks are slow to adopt, yet expect finished products. You are responsible for the second goal.
Bank-to-Blockchain Translation
Turn bank-side realities into engineering design inputs. Examples: How does a Hogan batch file land? What does a Reg CC hold look like when you need to mirror it on-chain? Why will the compliance team reject a direct write-back API?
Work side-by-side with the engineering team to scope PoCs, define adapter interfaces, and make sure the on-chain token logic maps correctly to real deposit operations — holds, memo posting, suspense, float.
Design Partner Acquisition
Co-own the path to key milestones with the Chief Commercial Officer.
Work backwards from the criteria a customer requires to commit: regulatory confidence, core system compatibility, robust reconciliation guarantees, and a credible consort