Staff Software Engineer

In this Staff Engineer role, you will define the technical direction for high-throughput, low-latency payment systems and ensure reliability at scale. You will act as a force multiplier across multiple teams, shaping architecture and elevating engineering standards. The work centers on building resilient, observable systems that can handle growth while maintaining correctness. You’ll collaborate with product and platform teams to align delivery with a single technical direction and drive meaningful, incremental improvements.

• hybrid working model
• recognition for impact
• high-autonomy culture
• ownership and fewer blockers
• meaningful challenges
• opportunity for growth

• Define service boundaries, data models, and integration patterns for scalable, high-throughput systems
• Design for resilience with redundancy, graceful degradation, backpressure, idempotency, and recovery
• Set non-functional requirements (availability, latency, throughput, durability, recovery)
• Lead major technical decisions end-to-end from framing to production rollout and decommissioning
• Improve observability, monitoring, capacity planning, load testing, and incident response
• Raise engineering bar via reviews, mentorship, and pairing to grow senior engineers
• Collaborate with product, platform, and other engineering teams to maintain a unified technical direction
• Make pragmatic build-vs-buy and refactor-vs-rewrite trade-offs and communicate them to stakeholders

• Significant experience building and operating distributed backend systems in production
• Proven design experience for high throughput and low latency
• Deep understanding of resilience patterns (idempotency, backoff, circuit breaking, queueing)
• Strong proficiency in either .NET or Java
• Experience with event-driven/streaming architectures and scalable data stores (relational and non-relational)
• Hands-on cloud development (AWS & Azure), containers, orchestration, infrastructure as code
• Experience owning production systems on call and driving observability and incident response
• Experience leading migrations or re-architectures of live systems with no data loss
• Excellent communication skills for technical trade-offs to engineers and non-technical audiences
• Nice-to-haves: payments domain experience, multi-region/active-active architectures, mentoring engineers

• strong communication
• ownership
• influence without authority
• distributed backend systems
• high throughput and low latency design
• resilience patterns (idempotency, retries, backoff, circuit breaking)