Site Reliability Engineer I, Paze

About the Role

At Early Warning, we’ve powered and protected the U.S. financial system for over thirty years with cutting-edge solutions like Zelle®, Paze®, and so much more. As a trusted name in payments, we partner with thousands of institutions to increase access to financial services and protect transactions for hundreds of millions of consumers and small businesses. Early Warning follows a hybrid work model.

The Site Reliability Engineer I applies software engineering and systems engineering practices to improve the reliability, resilience, scalability, and operational health of production services. The role partners with Software Engineering and other technology teams to ensure reliability, observability, recoverability, performance, and operational readiness are engineered into systems throughout their lifecycle. At the Engineer I level, the engineer develops technical breadth while working with more experienced engineers to understand system behavior, automate operational work, and improve service health.

Key Responsibilities

• Use software engineering, automation, and DevOps principles and practices to continually improve how services are built, tested, deployed, observed, operated, and recovered.
• Use data, evidence, experimentation, and rigorous engineering analysis appropriate to the level to identify reliability risks, test assumptions, and guide technical decisions.
• Define, implement, or improve SLIs, SLOs, error budgets, and other service-health measures appropriate to the scope of responsibility.
• Improve observability through metrics, logging, tracing, monitoring, alerting, dashboards, and service-health instrumentation.
• Drive continuous improvement across CI/CD, observability, deployment practices, Infrastructure as Code, automation, testing, incident response, capacity management, resilience, and operational readiness.
• Identify recurring or systemic production issues and translate operational experience into improvements in code, architecture, automation, tooling, and engineering practices.
• Partner with Software Engineering teams to incorporate reliability, resiliency, scalability, performance, observability, recoverability, and operational readiness throughout the development lifecycle.
• Participate in or lead incident response, troubleshooting, service restoration, and blameless post-incident learning appropriate to the level.
• Participates in an on-call rotation for supported production services, responding to incidents, alerts and service degradation in accordance with established procedures and escalation paths.
• Reduce operational toil and unnecessary manual intervention through software, automation, reusable patterns, and better engineering practices.

Leveling Intent

Engineer I is an entry or early-career SRE role. The engineer performs meaningful reliability engineering work while developing technical breadth, production experience, and independence. Force multiplication begins at this level through knowledge sharing, documentation, automation, and reusable improvements that benefit the immediate team.

Level Expectations

• Contributes as a force multiplier within the immediate team by sharing knowledge, improving documentation, and creating reusable automation and solutions that help others work more effectively.
• Demonstrates software engineering, systems thinking, troubleshooting, and production reliability capabilities appropriate to the level.
• Applies evidence-driven reasoning and technical rigor to distinguish observed facts from assumptions and make defensible engineering recommendations.
• Shares knowledge and contributes to sustainable engineering capability rather than creating dependency on individual expertise.
• Works primarily within established patterns with guidance from more experienced engineers.
• Demonstrates increasing independence in routine troubleshooting, automation, and engineering changes.

Requirements & Tech Stack

• Experience with software development or scripting using one or more modern programming languages.
• Experience with software engineering principles, distributed systems, production troubleshooting, automation, and observability appropriate to the level.
• Experience with public cloud technologies and architectures, preferably AWS, along with infrastructure, networking, Linux/Unix, and modern application architectures appropriate to the level.
• Demonstrated analytical, problem-solving, communication, and collaboration skills appropriate to the scope of the role.
• Relevant internship, co-op, academic, laboratory, open-source, or other substantive hands-on engineering experience may be considered when evaluating candidates early in their careers.

Preferred Qualifications

• Hands-on experience with AWS is preferred, or comparable experience with another major cloud platform such as Microsoft Azure, Google Cloud Platform (GCP), or Oracle Cloud Infrastructure (OCI).
• Experience developing, deploying, operating, or improving highly available production software or distributed systems.
• Experience with CI/CD, Infrastructure as Code, containers or orchestration, observability, monitoring, alerting, and software-delivery automation.
• Experience with SLIs, SLOs, error budgets, incident management, performance analysis, capacity management, resilience testing, disaster recovery, or operational readiness appropriate to the level.
• Experience creating reusable automation, tooling, platforms, patterns, or practices that improve engineering effectiveness.
• Bachelor's degree in Computer Science, Software Engineering, Computer Engineering, Information Systems, or a related technical field, or equivalent practical experience.

Qualifications

• Typically 0–2 years of relevant professional experience in Software Engineering, Site Reliability Engineering, Systems Engineering, Cloud/Platform Engineering, DevOps, Infrastructure Engineering, Architecture where applicable, or a comparable technical discipline.