Site Reliability Engineer

Job Description – Application SRE (L3 Support)

Experience:

• 5–8 years (Senior-level)

Role Summary:

The Application SRE (L3) role focuses on application-level reliability, monitoring, and production support. This role acts as a bridge between Development and Support teams, ensuring faster issue resolution, proactive alerting, and stable application operations.

The role emphasizes observability, incident management, and FCAPS ownership, enabling NOC and SQT teams to respond effectively to application alerts.

Key Responsibilities:

• Act as L3 support for production applications and critical incidents
• Collaborate with Development, Support(L1/L2), QA, and DevOps teams
• Design and maintain application-level monitoring and alerts
• Ensure alerts are actionable for NOC and SQT teams
• Perform root cause analysis(RCA) and drive permanent fixes
• Maintain FCAPS practices (Fault, Configuration, Accounting, Performance, Security) at the application level
• Create and maintain run books and operational documentation
• Support release validation and post-production monitoring

• Performance Management: Diagnose and resolve High Latency queue building and Throughput degradation
• Support DR drills and validate HA mechanisms

Required Skills:

• Strong knowledge of Linux systems
• Experience with scripting (Shell, Python, or similar)
• Good understanding of databases, preferably PostgreSQL
• Good Understanding of Postman and Rest API to troubleshoot the issues
• Experience with application monitoring, alerting, and logging tools
• Experience on Tcp Dump and Wireshark to find out the network level issues and bottleneck
• Strong problem-solving and communication skills
• Hands-on AWS SysOps expertise

Nice to Have:

• Experience in SRE, Production Support, or Platform Operations
• AWS SysOps Administrator certification
• Experience supporting high-availability or customer-facing systems

Success Metrics:

• Reduction in production incidents and repeat issues
• Improved alert quality and response time
• Faster incident solution (MTTR)
• Effective enablement of NOC and SQT teams