Remote job
Senior Backend Engineer, Payments
Job details
About this role
Role overview
Join the Payments team as a Senior Backend Engineer to lead complex, multi-team initiatives within a high-volume payments platform serving tens of thousands of customers. The role focuses on driving technical architecture, mentoring peers, and partnering closely with product, design, and frontend counterparts to deliver reliable, scalable services. It is a senior, hands-on position suited to an engineer who thrives on cross-functional collaboration and owns outcomes from design through production.
Responsibilities
- Design, build, and maintain scalable backend services and APIs, primarily using Golang-based microservices. - Lead architectural decisions and shape long-term system health, anticipating scaling and maintenance needs early. - Partner with product managers, designers, and frontend engineers to deliver high-impact payments features. - Participate in system design reviews, propose robust solutions, and contribute to broader engineering strategy. - Own code quality, reliability, and observability from development through production, including SLAs, SLOs, monitoring, alerting, and incident response. - Mentor peers and junior engineers, and take part in an on-call rotation with hands-on support during critical incidents.
Requirements
- 5+ years of backend engineering experience with modern languages such as Golang, Java, Python, Ruby, or C# (Golang preferred or willingness to learn). - Hands-on experience designing and building RESTful APIs and backend services. - Strong understanding of distributed systems and inter-service communication (e.g., gRPC, REST, Kafka, Redis). - Experience with relational databases and SQL. - Willingness to participate in an on-call rotation and take responsibility for production systems.
Nice to have
- Experience deploying and maintaining services in cloud environments, particularly Google Cloud Platform. - Familiarity with Docker and Kubernetes, plus observability tooling for metrics, alerts, and tracing. - Background with protobufs, gRPC, or Temporal, and prior work breaking monoliths into microservices. - A thoughtful approach to technical debt, scalability, and explaining complex systems to mixed audiences.