Cloudflare07/21/2026

Senior Distributed Systems Engineer

Salary not specified

MARKET

15,208 ₽median for this role

System Analyst · 16 jobs with disclosed pay

5,680half of the offers: 9,479–16,547100,000

The employer didn't disclose pay — compare with the market yourself.

In-Office

Responsibilities

01Design, build, and operate backend services that enforce regional boundaries on where customer data is stored, processed, and decrypted, across a globally distributed edge network
02Contribute to end-to-end feature delivery — write technical designs and RFCs, implement services and libraries, add tests and observability, drive rollout, and own the resulting systems in production
03Partner with engineers on adjacent platforms, cryptography, networking, data, and product teams to integrate residency guarantees into new and existing surfaces without regressing performance or reliability for other customers
04Reason carefully about failure modes, consistency, and blast radius; design systems that fail closed for compliance while degrading gracefully for availability, and make these tradeoffs explicit in design docs
05Participate in on-call for your services, lead incident response and post-mortems, and continually invest in reliability, capacity planning, and cost
06Raise the engineering bar through code review, mentorship, and clear written communication; contribute to the team's engineering standards and tooling

015+ years of professional experience designing, building, and operating production distributed systems at scale
02Strong proficiency in at least one system or backend language such as Go, Rust, or C/C++, and a willingness to work in others as the codebase demands
03Solid grasp of distributed systems fundamentals, including: Consistency and consensus models (strong, sequential, eventual; Paxos / Raft at a conceptual level)
04Replication, sharding, and partitioning strategies, and their tradeoffs against availability and latency
05Failure modes: partial failure, network partitions, split brain, clock skew, and how these show up in real systems
06Idempotency, retries, backpressure, timeouts, circuit breakers, and rate limiting as first-class design concerns
07Health checking, failure detection, leader election, and graceful deg