> Markdown version of [/jobs/ext/3841138-staff-software-engineer-caching](https://www.wearedevelopers.com/jobs/ext/3841138-staff-software-engineer-caching). Every page supports `.md` or `Accept: text/markdown`. Links point to the HTML versions so they work for humans too. Agent guide: [/agents.md](https://www.wearedevelopers.com/agents.md).

---

# Staff Software Engineer, Caching

- **Company:** Judi Health
- **Location:** Charlotte, NC, United States
- **Experience:** Expert
- **Contract:** Permanent contract
- **Skills:** Amazon Web Services, C++ (Programming Language), Cloud Computing, Code Review, Databases, Data Structures, Distributed Systems, Python (Programming Language), Memcached, Redis, Data Access Layer, Distributed Caching, Data Streaming, Caching, Change Data Capture, Database Replication
- **Published:** October 20, 2026
- **Apply:** https://www.juju.com/job/23_139D40E3FDDB6708E9DD2C8C42A25644

## About the Role

senior engineersParticipate in a 24/7 on-call rotation to provide continuous operational support and rapid incident responseRequired Qualifications:10+ years of production engineering experience, with deep specialization in distributed systems and caching infrastructureProduction experience operating distributed caching systems, such as Redis / Valkey or, Memcached, at cloud scale, including cluster topology, eviction policy, replication, and failure recoveryExperience with multi-tenancy and the operational complexity of running shared caching infrastructure across many independent workloadsDeep understanding of cache consistency and the failure modes that emerge at scale, such as thundering herd, hot key saturation, cache leasing, and dual-write consistency problems, and the judgment to choose the right invalidation strategy for a given workloadFluency with cache replacement algorithms beyond LRU (e.g., LFU, ARC, and probabilistic eviction) and the tradeoffs of multi-tier architectures
when an in-process layer belongs alongside a shared distributed cacheExperience in cloud-native environments where redundancy, resource efficiency, and resiliency are first-class requirements, not afterthoughtsA track record of leading cross-team technical initiatives - driving decisions through influence and producing documentation that holds up over timeStrong written and verbal communication - you produce architectural guidance that the broader engineering organization depends onComfortable operating with ambiguity - at this level, you will be handed problems, not plans, and are expected to identify the right approach and drive it from first principles to productionStrong experience supporting 24/7 production on-call rotations, including responding to alerts and resolving incidents outside of standard business hoursPreferred Qualifications:Experience in healthcare, pharmacy benefits, or other regulated industriesWorking familiarity with probabilistic data structures
and when they belong in a caching architecture over standard key-value patternsExperience with caching in real-time transactional processing domains - payments, financial services, insurance, or healthcare - where data correctness and timeliness have measurable downstream consequencesFamiliarity with database replication and change data capture as mechanisms for cache invalidation and maintaining consistency with the source of truthSystems-level programming experience in Rust, Go, or C/C++, particularly for performance-critical infrastructure componentsProficiency in Python for infrastructure tooling, automation, or service developmentExperience with AWS / GCP for managed caching, database, and streaming servicesOpen-source contributions, technical publications, or conference presentations in distributed systems or infrastructureNothing in this position description restricts management's right to assign or reassign duties and responsibilities to this job at any

## Description

The Architecture organization is responsible for the technical foundation the rest of the company builds on: the standards, patterns, and infrastructure that engineering teams use to move fast and build efficiently.
The Caching team sits within Architecture's Core Platform function, owning the data access layer across the entire platform.As a Staff Engineer in Architecture, your influence extends beyond what you ship directly.
The standards you set, the patterns you establish, and the decisions you document become the reference point for how caching is approached across the organization.Claims processing, eligibility, accumulations, and prior authorizations drive highly interconnected, high-volume workflows where maintaining a consistent view of data across the platform is a significant architectural challenge.
Decisions around caching, invalidation, and state propagation directly impact both performance and correctness, particularly where the cost of a stale or incorrect read is high.
You will be directly responsible for defining consistency contracts, designing invalidation patterns, and balancing correctness and performance across a domain with varying tolerance for stale data.One of your first major initiatives will be architecting the caching strategy for our most critical domain: claims adjudication.
This is a deeply embedded engagement.
You will work directly within the domain by reviewing and analyzing real claims data and processing workflows to understand the caching and consistency requirements.
This data flows across systems throughout the platform, directly influencing critical workflows including prior authorization, reporting, and member experience.Position Responsibilities:Design, build, and operate the caching infrastructure that serves as the data access layer for one of the most complex domain models in American healthcareOwn the full lifecycle of cache design, from eviction policy and service topology to invalidation architecture and operational recoveryDefine and own the performance and correctness contracts between the caching layer and the services that depend on itDrive adoption of caching best practices across engineering, eliminating anti-patterns, building shared libraries, and making cache-aware design the defaultDiagnose and resolve correctness, performance, and stability issues in the caching layer, including leading incident response and post-incident reviewsSet the technical bar for the caching team through design review, code review, and direct mentorship of