Judi Health Staff Software Engineer, Performance at Judi Health responsible for platform performance under load. Lead diagnostics and improvements on database architecture for claims processing and adjudication systems.
Responsibilities
Apply deep Postgres expertise to diagnose production performance problems by interpreting query plans, analyzing usage patterns, and evaluating how cluster configuration and architectural decisions shape system behavior at scale, then own the path from root cause to production remediation
Evaluate and implement cluster topology changes and drive the architectural transformations, including the migration from synchronous to asynchronous I/O patterns, that take the platform's throughput to the next order of magnitude
Build the benchmarking and regression-detection infrastructure that gives engineering teams a database performance signal, before changes reach production
Define and own performance contracts for the database layer: latency targets, throughput expectations, and the SLA boundaries that upstream services build against
Lead query and schema reviews for high-risk changes; own incident response for performance-related degradations and drive post-incident findings into engineering improvements
Mentor and develop senior engineers on Postgres internals, query analysis, execution plan interpretation, and the performance implications of schema decisions at scale
Participate in a 24/7 on-call rotation to provide continuous operational support and rapid incident response
Qualification
Deep fluency in PostgreSQL internals
Required
10+ years of production engineering experience, with deep specialization in PostgreSQL performance and transactional systems at scale
Deep fluency in PostgreSQL internals: MVCC, autovacuum behavior, query planner statistics, locking semantics, and the interaction between transaction patterns and long-running queries
Demonstrated ability to diagnose and remediate production database performance problems in regulated or correctness-critical environments where performance improvements cannot compromise data integrity
Experience designing and building performance benchmarking and regression-detection systems — including CI-integrated performance gates and observability pipelines — that give engineering teams pre-production visibility into database performance across the stack
Experience evaluating and implementing cluster topology changes: connection pooling configuration, read replica strategy, partitioning/sharding approaches, and PostgreSQL - parameter tuning for high-concurrency transactional workloads
A track record of leading cross-team technical initiatives — driving decisions through influence and producing documentation that holds up over time
Strong written and verbal communication — you produce architectural guidance that the broader engineering organization depends on
Comfortable 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 production
Strong experience supporting 24/7 production on-call rotations, including responding to alerts and resolving incidents outside of standard business hours
Preferred
Direct experience with Aurora PostgreSQL at scale, including familiarity with the operational constraints of a managed PostgreSQL deployment: connection limits, storage autoscaling behavior, I/O throughput ceilings, extensions, and the performance characteristics of Aurora's distributed storage layer
Hands-on experience with connection pooling middleware, particularly the operational tradeoffs between pooling modes (session, transaction, statement) in high-concurrency transactional workloads; e.g. PgBouncer, PgDog, or equivalent
Experience with asynchronous Python I/O patterns (asyncio, asyncpg, or equivalent) and the architectural migration from synchronous to asynchronous database interaction
Familiarity with horizontal scale strategies for transactional PostgreSQL workloads, including logical and physical sharding approaches and the tradeoffs they introduce for data model complexity and query routing
Familiarity with the boundary between OLTP and OLAP workloads, and the ability to recognize when analytical query patterns are better served by a purpose-built system than optimized on the transactional cluster
Systems-level programming experience in Rust, Go, or C/C++. While the primary focus of this role is database optimization, you'll be actively involved in application development, and the ability to work at lower levels of the stack when performance demands it is a meaningful advantage
Background in pharmacy benefit management, claims adjudication, healthcare data systems, or other regulated, correctness-first transactional environments