SRE Lead

Calling all innovators – find your future at Fiserv. We’re Fiserv, a global leader in Fintech and payments, and we move money and information in a way that moves the world. We connect financial institutions, corporations, merchants, and consumers to one another millions of times a day – quickly, reliably, and securely. Any time you swipe your credit card, pay through a mobile app, or withdraw money from the bank, we’re involved. If you want to make an impact on a global scale, come make a difference at Fiserv. Job Title SRE Lead About your role: At Fiserv, we are modernising a high-volume global payment processing platform — migrating from a legacy monolithic PL/SQL core to a cloud-native, event-driven microservices architecture on AWS. This is a ground-up build across different business domains. Confluent Cloud for event streaming, Aurora PostgreSQL for persistence, EKS (Kubernetes) for compute, and a modern Java/Quarkus stack throughout. As a Site Reliability Engineer, you will own the production readiness and operational health of the new platform as services go live. You will ensure that what we build is observable, resilient, and operable — bridging the gap between engineering teams building services and the reality of running a payment platform that processes millions of transactions daily. You will define what production-ready means, ensure teams meet that bar, and build the tooling and practices that keep the platform healthy. This is a particularly critical role during modernisation — new microservices will go live alongside the legacy system, with traffic migrating incrementally via feature flags and canary deployments (Argo Rollouts). You will ensure we can operate both with confidence, understand system behavior under load, and detect and respond to issues before they impact clients. What you’ll do: Define and own production readiness standards — what every service must have before going live: observability, SLOs, runbooks, resource limits, graceful degradation and policy compliance. Build and maintain observability — owning the Dynatrace APM deployment, Splunk log pipelines via Fluent Bit, and Prometheus metrics across the platform. Ensuring distributed tracing, structured logging, and dashboards give clear visibility into system health across the event-driven pipeline. Define and implement SLIs/SLOs — working with engineering teams and stakeholders to define meaningful service level indicators and objectives, and building the measurement infrastructure. Own incident response practices — defining how we detect, respond to, and learn from production issues. Building the culture of blameless post-mortems and reliability improvement. Drive resilience engineering — chaos testing, failover validation, load testing, and ensuring the platform degrades gracefully under stress rather than failing catastrophically. Support engineering teams on operability — reviewing designs for operational concerns, advising on retry strategies, timeout tuning, circuit breaker configuration, and back-pressure handling. Manage the transition from legacy to new — ensuring we can operate both systems during migration, with clear visibility into traffic routing, parity, and system behaviour during cutovers. Automate operational toil — building tooling that reduces manual intervention, improves deployment confidence, and makes the platform easier to operate at scale. Capacity planning — understanding traffic patterns, growth trajectories, and ensuring the platform is provisioned appropriately for both normal and peak load. Experience you’ll need to have: Experience in SRE, production engineering, or operations for high-volume distributed systems — you have kept critical systems running and improved their reliability. Strong hands-on skills with observability platforms — distributed tracing (OpenTelemetry), metrics (Prometheus/Grafana or equivalent), structured logging, and APM tools (Dynatrace, Datadog, or similar). Experience defining and measuring SLIs/SLOs and using them to drive engineering decisions. Understanding of resilience patterns in distributed systems — circuit breakers, retries, timeouts, bulkheads, back-pressure — and how to validate they work. Experience with load and performance testing — defining realistic scenarios, running at scale, and interpreting results to identify bottlenecks. Comfort with cloud infrastructure — AWS services, Kubernetes, container orchestration, and infrastructure-as-code. Experience with event-driven systems — Kafka, message-based architectures, and the operational challenges they bring (lag monitoring, consumer group management, partition rebalancing). A mindset of enabling engineering teams rather than gatekeeping — you set standards and build tooling, not approve deployments. Experience that would be great to have: Strong hands-on experience with Dynatrace or equivalent APM — distributed tracing, anomaly detection, SLO tracking, and alerting. Dynatrace experience is a strong advantage. Familiarity with payments, financial services, or high-volume transactional domains is a plus but not essential. Exposure to incident management tooling, on-call practices, or chaos engineering frameworks is beneficial. Thank you for considering employment with Fiserv. Please: Apply using your legal name Complete the step-by-step profile and attach your resume (either is acceptable, both are preferable). Our commitment to Diversity and Inclusion: Fiserv is proud to be an Equal Opportunity Employer. All qualified applicants will receive consideration for employment without regard to race, color, religion, national origin, gender, gender identity, sexual orientation, age, disability, protected veteran status, or any other category protected by law. Note to agencies: Fiserv does not accept resume submissions from agencies outside of existing agreements. Please do not send resumes to Fiserv associates. Fiserv is not responsible for any fees associated with unsolicited resume submissions. Warning about fake job posts: Please be aware of fraudulent job postings that are not affiliated with Fiserv. Fraudulent job postings may be used by cyber criminals to target your personally identifiable information and/or to steal money or financial information. Any communications from a Fiserv representative will come from a legitimate Fiserv email address.