Site Reliability Engineering Lead

OnePay is a consumer fintech platform providing banking, savings, credit, lending, investing, crypto, and embedded financial services. The Site Reliability Engineering Lead will lead a senior SRE team while remaining hands-on with production code, automation, observability, incident response, service ownership, and reliability engineering across the organization.

Responsibilities:

• Lead a senior SRE team. Bring planning, clarity, and career growth to a small, strong team, and focus them on high-leverage reliability work over manual, ticket-driven response
• Stay hands-on. Write production code, and build automation, tooling, and golden paths yourself. Contribute to your team's codebase, do design and code review, and set the technical bar by example
• Define service ownership, alerting, dashboards, runbooks, and deploy and rollback safety, and run regular service-health reviews for the systems your team supports
• Stay in the incident loop. Run incident command when needed, drive verified remediation, and prevent recurrence. Help build self-service incident tooling and runbook automation so reliability scales without heroics
• Build sustainable on-call. Design durable coverage through staffing, handoffs, and automation rather than open-ended volunteer hours
• Partner across engineering. Work with service teams and engineering leaders to raise reliability standards, holding clear boundaries between SRE enablement and service-team ownership

Requirements:

• You still code today. Strong software engineering foundation, and you write production-quality code in a modern language such as Python or Go. You are comfortable being assessed on your coding
• Real reliability depth for production systems and services at scale, ideally in a consumer, fintech, or other high-availability environment
• You built your foundation at a high-bar, high-scale engineering organization with a strong engineering culture
• Recent people leadership. You have managed a small engineering team within roughly the last few years and want to keep leading while staying technical
• Genuinely hands-on with observability, alerting, safe deploys, automation, and incident command. You build these things, not just specify them
• Calm, credible communication with your team, partner teams, and during live incidents