About Altitude

Stablecoins crossed $300 billion in circulation. Real businesses now use them for cross-border settlements, contractor payments, treasury operations.

The fintech playbook assumed rails were fixed - you couldn't change ACH or SWIFT, only build better interfaces on top. Stablecoins change the rails themselves, creating an opening for a new generation of financial products.

Altitude is what we're building to capture it. Business accounts on stablecoin rails: global accounts, cross-border payments, cards, invoicing, yield. Over 500 businesses use it today. Built by Squads (Squads Multisig secures $15B+ on Solana). Backed by Haun, Multicoin, Solana, Coinbase, Electric Capital, Placeholder and others.

More on the thesis here.

The Role

You'll translate compliance policies into technical reality. The MLRO sets the rules; you make them work inside the product. This means configuring KYB workflows, building vendor integrations, designing escalation paths, and ensuring our compliance orchestration layer actually functions across multiple PSPs and providers.

What You'll Do

• Configure and optimize KYB workflows across Sumsub and other identity vendors

• Build the operational layer that routes customers through the right compliance checks based on risk profile, jurisdiction, and product access

• Design and implement transaction monitoring workflows

• Create SOPs for compliance operations, RFI handling, escalation protocols, case management

• Work with engineering to spec compliance requirements for new features and markets

• Manage vendor relationships operationally

• Identify friction in onboarding legitimate businesses and fix it without compromising controls

What We're Looking For

• Experience configuring compliance/identity vendors (Sumsub, Persona, similar)

• Ability to translate policy into technical workflows

• SQL or equivalent data skills - you'll need to pull reports, analyze rejection patterns, spot process failures

• Systems thinking: how do changes in one workflow affect downstream processes?

• Prior fintech or payments operations experience strongly preferred

• Comfort with complexity, we work with multiple PSPs, each with different requirements

Not a Fit If

• You're purely policy-oriented without technical implementation experience

• You can't context-switch between vendor configurations, process design, and data analysis

• You need engineering to build everything for you