Cloudflare
Distributed Systems Engineer
Remote Engineering role with clear candidate location fit.
PostedRecently added
Eligible countries1 accepted country
Seniority signalOpen level
Work settingRemote
Accepted candidate locations
India
Role overview
Distributed Systems Engineer
Requirements and responsibilities
Readable role content extracted into sections for faster review.
Responsibilities
- 3+ years of professional experience designing, building, and operating production distributed systems at scale.
- Strong 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.
- Solid grasp of distributed systems fundamentals, including:
- Consistency and consensus models (strong, sequential, eventual; Paxos / Raft at a conceptual level).
- Replication, sharding, and partitioning strategies, and their tradeoffs against availability and latency.
- Failure modes: partial failure, network partitions, split brain, clock skew, and how these show up in real systems.
- Idempotency, retries, backpressure, timeouts, circuit breakers, and rate limiting as first-class design concerns.
- Health checking, failure detection, leader election, and graceful degradation.
- Observability: metrics, logs, and tracing as design inputs, not afterthoughts.
- Practical experience with API design (REST or gRPC), relational databases, and asynchronous messaging or event streaming systems, with a clear understanding of transactional and consistency boundaries.
- Comfortable with AI-assisted development tooling, with the judgment to use it to accelerate work while remaining accountable for correctness, security, and design quality
- Track record of production ownership: on-call, incident response, post-mortems, and continuous investment in reliability and performance.
- Strong written and verbal communication skills; ability to write clear design documents and collaborate effectively across time zones.
Details
- Consistency and consensus models (strong, sequential, eventual; Paxos / Raft at a conceptual level).
- Replication, sharding, and partitioning strategies, and their tradeoffs against availability and latency.
- Failure modes: partial failure, network partitions, split brain, clock skew, and how these show up in real systems.
- Idempotency, retries, backpressure, timeouts, circuit breakers, and rate limiting as first-class design concerns.
- Health checking, failure detection, leader election, and graceful degradation.
- Observability: metrics, logs, and tracing as design inputs, not afterthoughts.
Responsibilities
- Experience building compliance-driven, security-sensitive, or multi-region systems.
- Familiarity with cryptography basics — envelope encryption, key management, HSMs, or PKI.
- Exposure to edge, CDN, or L4/L7 proxy platforms, or to large-scale globally distributed storage or key-value systems.
- Experience contributing to or driving multi-team, multi-quarter engineering programs with cross-functional dependencies across platform, security, and product teams.
Similar roles
Keep a backup shortlist.
Stack
Use these tags to compare similar remote roles.
Location eligibility
Candidates should apply only when their profile country is listed here.
Your profileCountry not setSign in to check your country against this role.
Hiring flow
WithMira shows the role, then sends candidates to the company application.
1Check role fit, stack, and location eligibility in WithMira.
2Open the company application page from the tracked apply link.
3Save the role or subscribe for similar opportunities before leaving.