Experience: Production support, Java, monitoring tools
Job Description & Details
"Site Reliability Engineering is at the heart of modern digital services, ensuring systems stay up and performant 24/7. With businesses increasingly moving to cloud\u2011native architectures, skilled SREs are in high demand. This six\u2011month onsite role in Phoenix offers a fast\u2011track chance to apply your production\u2011support expertise in a banking\u2011focused environment.\n\n# Job Summary\nWe are seeking a hands\u2011on Site Reliability Engineer to monitor system health, troubleshoot production incidents, and drive automation across our cloud\u2011based services. The role involves building alerts, dashboards, and collaborating with development teams to improve reliability while participating in on\u2011call rotations.\n\n# Top 3 Critical Skills Table\n| Skill | Why it's critical | Mastery Level |\n|---|---|---|\n| Core Java | Foundation for building and debugging services in Spring Boot | Senior |\n| Monitoring (Splunk/Kibana/Grafana) | Provides real\u2011time visibility and rapid incident response | Senior |\n| Cloud Platforms (AWS/Azure/GCP) | Enables scalability, reliability, and automation in production | Senior |\n\n# Interview Preparation\n1. **How do you design an alerting strategy to minimize noise while ensuring critical incidents are caught?**\n *What the interviewer is looking for:* Understanding of threshold setting, severity levels, and use of tools like Splunk or Grafana.\n2. **Explain a time you performed a root\u2011cause analysis on a production outage. What steps did you take?**\n *What the interviewer is looking for:* Structured troubleshooting methodology, documentation, and collaboration with dev teams.\n3. **Describe how you would implement a CI/CD pipeline for a Spring Boot microservice.**\n *What the interviewer is looking for:* Familiarity with build tools, automated testing, and deployment orchestration.\n4. **What are the key differences between L1 and L2 support, and how do you transition an issue between them?**\n *What the interviewer is looking for:* Clear delineation of responsibilities, escalation procedures, and communication skills.\n5. **How would you automate the creation of monitoring dashboards for a new service in Grafana?**\n *What the interviewer is looking for:* Use of templating, API integration, and infrastructure\u2011as\u2011code concepts.\n\n# Resume Optimization\n- Site Reliability Engineer\n- Production Support\n- Core Java\n- Splunk\n- Kibana\n- Grafana\n- PostgreSQL\n- MongoDB\n- ServiceNow\n- CI/CD\n\n# Application Strategy\nWhen reaching out to the recruiter, send a concise email that starts with a friendly greeting, attaches your updated resume, and clearly maps your experience to the role. Highlight your top skills\u2014such as Core Java, monitoring with Splunk/Kibana/Grafana, and cloud automation\u2014and reference any relevant projects where you reduced downtime or automated incident response. Mention that you\u2019re eager to discuss how your background aligns with the team\u2019s reliability goals.\n\n# Career Roadmap\n| Current Role | Typical Experience | Core Focus | Next Position |\n|---|---|---|---|\n| Site Reliability Engineer | 2\u20114 years | Incident response, automation, monitoring | Senior Site Reliability Engineer |\n| Senior Site Reliability Engineer | 4\u20117 years | Architecture, large\u2011scale reliability, mentorship | SRE Lead / Reliability Architect |\n| SRE Lead / Reliability Architect | 7+ years | Strategy, cross\u2011team leadership, budgeting | Director of Reliability Engineering |\n"