Software Engineer, Caching

Judi Health is an enterprise health technology company providing a comprehensive suite of solutions for employers and health plans, including:

• Judi Rx
  , a public benefit corporation delivering full-service pharmacy benefit management (PBM) solutions to self-insured employers,
• Judi Health™, which offers full-service health benefit management solutions to employers, TPAs, and health plans, and
• Judi®, the industry’s leading proprietary Enterprise Health Platform (EHP), which consolidates all claim administration-related workflows in one scalable, secure platform.

Together with our clients, we’re rebuilding trust in healthcare in the U.S. and deploying the infrastructure we need for the care we deserve. To learn more, visit (Use the "Apply for this Job" box below)..

Hybrid 3 days (offices in NYC, Denver, CO and Charlotte, NC area)

Judi Health is building the technology infrastructure our nation needs to deliver the healthcare we deserve — a domain where correctness is non‑negotiable and latency has real‑world consequences. The Architecture organization is responsible for the technical foundation the rest of the company builds on: the standards, patterns, and infrastructure primitives that engineering teams depend on to move fast and build correctly.

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. You are building for the platform and for the teams that build on it.

The platform's domain model is deeply interdependent — claims, eligibility, accumulations, and prior authorizations are coupled across multiple high-throughput workflows, and a cache that reflects an inconsistent view of that model has consequences that compound quickly. You will be directly responsible for designing invalidation architectures and consistency contracts for a domain where the tolerance for stale data varies by workflow and the cost of a wrong read is high.

One of your first major initiatives will be architecting the caching strategy for our most critical processing domain: claims adjudication. This is a deeply embedded engagement. You will work directly within the domain — reviewing and analyzing real claims data and processing workflows — to understand the caching requirements at their root. This data flows across systems throughout the platform, directly influencing critical workflows including prior authorization, reporting, and member experience.

• Design, build, and operate the caching infrastructure that serves as the data access layer for one of the most complex domain models in American healthcare
• Own the full lifecycle of cache design — from eviction policy and topology decisions to invalidation architecture and operational recovery
• Define and own the performance and correctness contracts between the caching layer and the services that depend on it
• Drive adoption of caching best practices across engineering — eliminating anti-patterns, building shared libraries, and making cache‑aware design the default
• Diagnose and resolve correctness, performance, and stability issues in the caching layer, including leading incident response and post‑incident reviews
• Set the technical bar for the caching team through design review, code review, and direct mentorship of senior engineers
• Participate in a 24/7 on‑call rotation to provide continuous operational support and rapid incident response

• 10+ years of production engineering experience, with deep specialization in distributed systems and caching infrastructure
• Production experience operating distributed caching systems — Redis, Valkey, Memcached, or Elasti Cache — at cloud scale, including cluster topology, eviction policy, replication, and failure recovery
• Deep understanding of multi‑tenancy and the operational complexity of running shared caching infrastructure across many independent workloads
• Deep understanding of cache…