Technical Lead – Site Reliability Engineering
Generate a McCoy IQ challenge in 30 seconds.
See how candidates think and approach the work this role demands, before the phone screen. We'll build a video challenge from this posting, and you can edit or share it before it goes live.
Key details
Job Description
Before you apply to a job, select your language preference from the options available at the top right of this page.
Explore your next opportunity at a Fortune Global 500 organization. Envision innovative possibilities, experience our rewarding culture, and work with talented teams that help you become better every day. We know what it takes to lead UPS into tomorrow—people with a unique combination of skill + passion. If you have the qualities and drive to lead yourself or teams, there are roles ready to cultivate your skills and take you to the next level.
Job Description:
Role Summary
The Technical Lead provides technical leadership for the SRE organization by driving architecture decisions, operational excellence, observability, and automation. This individual serves as the highest technical authority within the engineering team.
Responsibilities
- Define operational standards, engineering best practices, and runbooks.
- Lead critical production incidents and complex troubleshooting efforts.
- Design and implement reliability improvements across applications and infrastructure.
- Drive self-healing systems and automation initiatives.
- Establish observability standards using metrics, logs, and distributed tracing.
- Mentor engineers and QA team members.
- Drive adoption of AI-powered engineering and operational tooling.
- Collaborate with development teams on production readiness and operational improvements.
Required Skills
- 11+ years of backend engineering and production support experience.
- Strong Java development experience.
- Deep expertise in distributed systems and event-driven architectures.
- Experience with Azure/GCP cloud platforms.
- Strong knowledge of messaging systems (AMQ, MQ, Kafka, etc.).
- Expertise with Couchbase, PostgreSQL, and cloud databases.
- Experience with observability tools such as Grafana and Splunk.
- Strong scripting and automation skills (Python preferred).
As part of the Site Reliability Engineering (SRE) organization, every team member plays a critical role in maintaining the reliability and availability of our production systems.
This role supports a 24x7 production environment supporting business-critical applications.
All engineers are expected to participate in an on-call support rotation, including evenings, weekends, and public holidays as scheduled.
During on-call periods, you will be expected to respond to production incidents within defined response time objectives, troubleshoot issues, and work collaboratively to restore service as quickly as possible.
Candidates should be comfortable diagnosing complex production issues across applications, cloud infrastructure, databases, messaging systems, and integrations.
Participation in post-incident reviews, root cause analysis (RCA), and implementation of permanent corrective actions is an essential part of the role.
Team members are expected to continuously improve operational processes through automation, monitoring enhancements, and proactive reliability improvements to reduce recurring incidents.
Flexibility to collaborate with globally distributed teams, including occasional overlap with US business hours, is expected to support production operations and major releases.
A strong sense of ownership, accountability, and customer focus is essential, as ensuring platform stability and business continuity is a shared responsibility across the entire team.
Employee Type:
UPS is committed to providing a workplace free of discrimination, harassment, and retaliation.
Audit details(provenance, verification trail, raw fields)
Core fields
ups:R26022379Provenance
wd5|hcmportal|SearchVerification trail
This posting hasn't been probed by our closure verifier yet. Stream C runs on a rolling schedule against postings approaching the close-decision threshold.
See how we measure for definitions, or our corrections log for known issues. Found something wrong? Flag a correction.
