Sr. Software Engineer, Backend (Risk & Compliance)
Company: Synctera
Location: United States (Remote)
Salary: $160,000 - $248,000 a year
Type: Full-time
Remote: Yes
Posted: 2026-04-16
About this role
## What We're Doing
At Synctera, we’re powering the future of FinTech. We help companies create new revenue streams and enhance their value proposition with FinTech apps and embedded banking products. With APIs, compliance support, and bank partners in one end-to-end Banking as a Service platform, Synctera is the fastest and easiest way to build, launch, and scale bank accounts, debit cards, charge cards, lending, and more. We help banks increase deposits and non-interest income by expanding their footprint through FinTech and embedded finance partnerships. The Synctera Platform enables banks to manage their program through a fully compliant, scalable solution.
We are looking for interesting, curious, wickedly smart people who are ready to jump in and run with our fast-growing team. If you want to have fun at work, collaborate with some of the sharpest people in the industry, grow the FinTech and Banking as a Service ecosystem, and love to win, read on!
## How We Build
At Synctera, engineers play a hands-on role in building and evolving our core platform. With smaller teams and fewer layers, engineers have real ownership over their work, move quickly from idea to execution, and contribute directly to technical decisions that matter.
You’ll work on systems that must be reliable, secure, and scalable, while helping shape how the platform continues to grow and mature. It’s an environment designed for engineers who enjoy meaningful impact, autonomy, and solving complex problems in a regulated, real-world context.
## Our Stack
Our platform is built in Go (for backend services) and React with Typescript (for the Synctera Console, our frontend). We’re built on top of Google Cloud Platform and typically use Postgres (Cloud SQL), Redis (Cloud Memorystore), and Pub/Sub as our core application stack, with OpenAPI specifications being used to both document our API and be the foundation for inter-service communication.
Our infrastructure is predominantly Kube...