Backend Software Engineer

Role overview

Backend Software Engineer focused on building high-throughput backend platform capabilities and shared services used by multiple teams. The role emphasizes predictable latency, durable event processing, strong developer experience (DX), and operational ergonomics.

Responsibilities

• Design and build internal platform services and shared infrastructure used daily by hundreds of engineers (DX and operational ergonomics focus)
• Architect high-throughput, latency-sensitive backend platforms with predictable, well-bounded tail latency
• Build replayable event-processing pipelines and asynchronous job execution platforms that other teams compose
• Design and operate caching, rate-limiting, and request-shaping layers for safe scaling under bursty workloads
• Create platform abstractions, SDKs, and paved-road libraries to prevent duplicate implementations
• Establish observability, SLOs, and capacity-planning practices for platform services
• Drive multi-region, fault-tolerant, geo-distributed designs emphasizing availability, durability, and graceful degradation
• Lead incident response and run blameless post-mortems; drive durable engineering improvements
• Define and enforce platform-wide standards (API design, schema evolution, deployment, backward compatibility)
• Optimize platform performance via profiling, data-driven tuning, and throughput/cost improvements
• Partner with infrastructure, security, and SRE teams to meet reliability, compliance, and security obligations
• Mentor engineers and lead architectural discussions; produce technical design docs, decision records, and runbooks

Requirements

• BS or MS in Computer Science/Software Engineering or closely related field
• 6+ years of professional backend or platform engineering experience
• Experience building and operating internal platforms/shared services used by multiple engineering teams
• Strong hands-on distributed systems experience designing latency-sensitive, high-throughput systems

Nice-to-haves

• Not explicitly stated in the provided excerpt (e.g., specific technologies, SRE practices, or cloud stack details were not included).