Staff Software Engineer, Bank

SoFi SoFi · Fintech · Seattle, WA · Engineering

Staff Software Engineer to be the technical backbone of SoFi's new commercial banking product. This role involves owning the technical architecture for core systems like payment orchestration, client onboarding, API Gateway, and real-time settlement. The engineer will design and implement the SoFi Exchange Network (SEN), a 24/7/365 closed-loop payment network. Responsibilities include setting technical standards, driving architectural decisions, mentoring engineers, and ensuring production readiness for systems handling institutional money.

What you'd actually do

  1. Own the technical architecture for Commercial Banking's core systems — payment orchestration, client onboarding workflows, API Gateway, real-time settlement, and the services that power the client-facing experience.
  2. Design and implement the SoFi Exchange Network (SEN) — a real-time, 24/7/365 closed-loop payment network enabling instant settlement between SoFi commercial clients.
  3. Build the client onboarding orchestrator: a stateful workflow engine that provisions entities, bank accounts, entitlements, payment rails, limits, and pricing — with retry, rollback, and idempotency guarantees.
  4. Design enterprise-grade identity, RBAC, and maker/checker approval systems that support complex organizational structures with scoped account access, per-rail permissions, and configurable payment limits.
  5. Define API contracts that institutional clients will integrate against — getting the abstractions, error models, and versioning right from day one.

Skills

Required

  • 7+ years of software engineering experience
  • sustained track record of technical leadership on complex, production-critical systems
  • Deep distributed systems expertise
  • Hands-on mastery of JVM-based stacks (Kotlin or Java, Spring Boot)
  • modern infrastructure (Kubernetes, AWS/GCP, Terraform, CI/CD pipelines)
  • Strong API design sensibility
  • Experience with stateful workflow systems

What the JD emphasized

  • production-critical systems
  • correctness is non-negotiable
  • reliability and correctness that institutional clients demand
  • every transaction must be accounted for
  • every failure mode handled