Software Engineer, Payments Product Lead at Aptos Labs

<div class="content-intro"><p><span style="font-weight: 400;">Aptos is a people-first blockchain on a mission to help billions of people achieve universal and fair access to decentralized assets in a safe and scalable way.</span></p> <p><span style="font-weight: 400;">Founded by some of the original creators and maintainers that researched, designed, and built the Diem blockchain to serve this purpose, we have dedicated several years toward this mission. We believe the open-source Diem technology we have developed is an important foundation of a safe and scalable web3 world where everyone has more equitable opportunities to grow and access financial assets with lower fees and fewer intermediaries.  </span></p> <p><span style="font-weight: 400;">Aptos (Ohlone for "The People") encompasses our mission and ethos for why we build.</span></p></div><p><strong>About this role </strong></p> <p>Aptos is a high-performance Layer 1 designed for financial services: sub-second settlement at sub-cent cost, production reliability institutions build on, and native stablecoins including assets exclusive to the network. We are consolidating our commercial efforts into one financial services company — payments, tokenization, and trading — and payments is the first chartered business: a ring-fenced unit with its own P&L, an exclusive global settlement partnership already signed, first-party products already shipped (keyless onboarding, multisig treasury, confidential payments), and clear evidence gates at 90 days, 6 months, and 24 months.</p> <p>This role is the founding technical leader of that unit. You are hire number one of the engineering team, and the build you lead defines the business.</p> <p><strong>What you'll own</strong></p> <ul> <li><strong>The Aptos Payment API. </strong>Spec, ship, and run the single API businesses integrate against — wrapping partner infrastructure today, with an orchestration engine routing across a licensed partner network as the business earns it. You write the spec bottoms-up from partner and client requirements.</li> <li><strong>Partner-facing engineering. </strong>You are the technical face of the unit: requirements intake, integration leadership, and technical diligence with banks, EMIs, PSPs, stablecoin issuers, and e-wallet platforms. You can run those calls alone and write the requirements doc after.</li> <li><strong>The trust infrastructure. </strong>Revenue attribution and reconciliation (the system that proves which volume is ours), a single-window KYC/KYB integration, a testnet sandbox that lets any prospect try the stack before compliance onboarding, and a native-asset-only settlement policy — no bridges.&lt