DevOps Engineer

We’re hiring: Distributed Systems Engineer – High-Performance Caching
At ApexCache, we’re building caching infrastructure for applications that need fast response times without putting unnecessary load on their origin systems.
We’re looking for a Distributed Systems Engineer to work on the core of the platform.
This is a hands-on engineering role. You’ll be dealing with caching, concurrency, performance, distributed systems and the problems that show up when traffic increases.
What you’ll work on
Design and improve high-performance caching components
Work on cache lookup, storage, eviction and expiration
Build and improve request coalescing / SingleFlight mechanisms
Work on origin protection and prevent unnecessary requests reaching backend services
Handle concurrent requests and race conditions
Improve cache hit rates and reduce latency
Profile services and identify CPU, memory, I/O and network bottlenecks
Design systems that continue to behave well under high traffic
Work on failure handling, retries and recovery
Benchmark changes and compare performance before and after optimization
Work with APIs, networking and cloud infrastructure
Improve observability through metrics, logging and tracing
Review designs and code with the rest of the engineering team
What we’re looking for
You should have solid experience with backend or systems engineering and be comfortable understanding how things work below the API level.
Experience with some of the following would be useful:
Distributed systems
Caching systems
Rust, Go, C++, Java or similar languages
Multithreading and concurrency
Databases and storage systems
HTTP and networking
Linux
Performance profiling
Load and stress testing
Cloud infrastructure
Monitoring and observability
You don't need to have worked specifically on a caching product before.
If you've worked on Redis, Memcached, CDNs, API gateways, databases, message queues, distributed services or other high-throughput systems, that experience is relevant.
What would make this role interesting
A lot of the work here isn't just about adding another feature.
It's about questions like:
Why did latency increase when traffic doubled?
Why did the origin suddenly receive thousands of requests for the same resource?
What happens when multiple requests arrive for the same uncached object at exactly the same time?
How do we keep performance predictable when the system is under pressure?
Where is the actual bottleneck — application code, CPU, memory, network, storage or the origin?
If you enjoy working through these kinds of problems, you'll probably enjoy this role.
Location: Remote / Global
We’re open to engineers from different backgrounds and locations.
If you're working on distributed systems, backend infrastructure, Rust, performance engineering or caching and this sounds interesting, get in touch.
And if you know someone who would be a good fit, tag them below.
We’ll also be sharing more technical details about what we're building at ApexCache.
#Hiring #DistributedSystems #Caching #Rust #BackendEngineering #SystemsEngineering #PerformanceEngineering #Infrastructure #SoftwareEngineering #RemoteJobs

Work arrangement
No