Senior Software Engineer

About Bastion

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.


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.

Overview

We are looking for a Backend 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're remote-first, async-by-default, and 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.

We have an office in NYC with a very flexible hybrid working environment, but are also open to remote employees in the US.


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.

First 30 days: Learn the rails, ship confidently

• Ramp on service layout, CI/CD, observability, engineering conventions and practices
• Ship a small feature slice or quality-of-life improvement in one service
• Add tests, dashboards, or runbook notes for the areas you touch
• 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 issuance-readiness
• Lead a medium-scope project: eg. 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/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 problems you might work on

• Designing stable, evolvable APIs for custody, transfers, or issuance without breaking downstream clients
• Building idempotent job flows for high-throughput transfers with strong audit trails
• Hardening key operations using hardware-backed isolation and robust key policies
• Improving p95 latency through query tuning, caching, or backpressure strategies

Our typical stack

• Languages: Go and TypeScript/Node.js; some services in Rust as needed
• Service patterns: gRPC and REST; GraphQL/tRPC at the edge for frontend BFFs
• Data and async processing: Postgres, Redis, Kakfa
• Workflow Management: Temporal
• Infra: AWS, containers, Kubernetes, Terraform; hardware-backed key isolation with Nitro Enclaves for sensitive operations
• Observability and ops: Datadog, Grafana, Sentry, Incident.io

Bastion provides equal employment opportunities to all employees and applicants for employment and prohibits discrimination and harassment of any type without regard to race, color, religion, age, sex, national origin, disability status, genetics, protected veteran status, sexual orientation, gender identity or expression, or any other characteristic protected by federal, state or local laws. This policy applies to all terms and conditions of employment, including recruiting, hiring, and placement. Bastion participates in E-Verify to authorize eligibility of employment in the United States.