Senior Software Engineer

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 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. 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. 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. 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. You need to be okay with that. If you think this is something you can handle, we will be excited to speak with you. 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. FIRST 30 DAYS: LEARN THE RAILS, SHIP CONFIDENTLY - Ramp on service architecture, CI/CD, observability, and engineering conventions - Ship a small feature slice or quality-of-life improvement in one service - Add tests, dashboards, or runbook notes for the areas you touch - Build relationships with your vertical team and cross-functional partners - Outcomes - Multiple safe production deploys with follow-up verification - You can run core services locally and trace requests through logs/metrics - Updated documentation and/or PRs that improve onboarding in your area BY 90 DAYS: OWN A SERVICE SURFACE AND RAISE THE BAR - Take ownership of a service or capability across our product, with an eye toward production-readiness - Lead a medium-scope project: updating an API contract, implementing a partner integration, or improving robustness of a critical path - Strengthen reliability with better logging, tracing, alerts, and failure handling - Outcomes - A delivered feature or refactor that improves a product metric, SLO, or developer ergonomics - You're a go-to person for your service domain BY 180 DAYS: DRIVE CROSS-SERVICE IMPACT - Lead a cross-service initiative, such as an API versioning plan, a data model migration, or a compliance-driven workflow change - Shape technical direction with design docs and mentoring - Partner with product and compliance to make pragmatic, regulation-aware tradeoffs - Outcomes - A multi-sprint delivery that simplifies the system and unlocks product velocity - Clear before/after reliability or performance improvements - Documentation and designs that help others ship faster and safer SOME CHALLENGES YOU MIGHT TACKLE - Designing stable, evolvable APIs for custody, transfers, or issuance without breaking downstream clients - Building idempotent job flows for high-throughput transf…