Senior Software Engineer at Bastion

<h1><strong>About Bastion</strong></h1><p style="min-height:1.5em">Bastion builds regulated financial infrastructure for modern businesses. Bastion's full stack product suite covers stablecoin issuance, custodial wallet infrastructure, and global asset conversion rails, with the flexibility to deploy individual capabilities or combine them end-to-end. </p><p style="min-height:1.5em">Bastion's regulated foundation underpins a compliance-first approach to risk management, ensuring the integrity and security of all financial activity within its systems. Bastion holds the appropriate licenses for its own operations, but can also act as a service provider, offering compliance and financial operations support under our customers’ licenses.</p><h1>Overview</h1><p style="min-height:1.5em">We are looking for a Senior Software Engineer to join our engineering team and build the core infrastructure that powers our stablecoin platform. In this role, you'll design and ship services that handle custody, transfers, issuance, and compliance workflows—systems that process real money and require exceptional reliability and security.</p><p style="min-height:1.5em">You'll work within one of our product verticals (Custody, On/Off Ramps, Issuance, or Shared Services), collaborating closely with product managers, compliance, and other engineers. Our teams are small and cross-functional, which means your work ships fast and has direct impact on customers and partners.</p><p style="min-height:1.5em">This is an opportunity to build financial infrastructure at a 30+ person company where ownership is real. We expect engineers to take initiative. Whether that's shipping features, improving observability, or strengthening the codebase. If you want to work on hard problems in a regulated domain where your contributions matter immediately, we'd love to talk.</p><p style="min-height:1.5em"></p><h1><strong>Work to Be Done</strong></h1><p style="min-height:1.5em">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.</p><p style="min-height:1.5em">We are a startup, so the pace is fast and the specific work will change. You need to be okay with that.</p><p style="min-height:1.5em">If you think this is something you can handle, we will be excited to speak with you.</p><p style="min-height:1.5em">We are building out our engineering hub in New York City, and this role is based our of our SoHo office. We work in a hybrid-but-flexible way (no set days in the office, come in when you think its effective, travel when you like) - most of us are in 2-3 days a week. </p><p style="min-height:1.5em"></p><h3>First 30 days: Learn the rails, ship confidently</h3><ul style="min-height:1.5em"><li><p style="min-height:1.5em">Ramp on service architecture, CI/CD, observability, and engineering conventions</p></li><li><p style="min-height:1.5em">Ship a small feature slice or quality-of-life improvement in one service</p></li><li><p styl