Remote Open C2C - 12 Yrs Above Latest - Site Reliability Engineer (SRE) - Observability & Monitoring
adrikj...@gmail.com
Send Resumes Adrik Jordan adrik....@grtcorp.com
Remote Open C2C - 12 Yrs Above Latest - Site Reliability Engineer (SRE) – Observability & Monitoring
Mandatory Java Development Background
Interview Screening process
- GRT Internal L1 Interview – Java Coding Test – 1.5 hrs Interview Duration
- GRT Internal L2 Interview [Consultant working in the Project] – 30 Mins Interview Duration
- Implementation Company L1 Interview – 1 hr interview duration
- End Client – L1 Interview - 1 hr interview Duration
Site Reliability Engineer (SRE) – Observability & Monitoring
About the Role
We are seeking a Site Reliability Engineer (SRE) with strong expertise in observability, monitoring, and distributed tracing to join our SRE team. The ideal candidate will help us design, build, and scale an observability framework that provides end-to-end visibility into our systems and applications. A strong focus will be places on OpenTelemetry, as we continue to standardize our telemetry pipeline across logs, metrics, and traces.
Responsibilities
- Design, implement, and maintain observability solutions using OpenTelemetry, Prometheus, Grafana, AppDynamics, and Splunk.
- Build and manage telemetry pipelines (metrics, logs, traces) ensuring reliable data collection, transformation, and export.
- Lead initiatives to improve incident detection, response, and post-incident analysis with a strong emphasis on RCA (Root Cause Analysis).
- Define and maintain SLIs, SLOs, and error budgets to measure and improve system reliability.
- Partner with development and operations teams to instrument applications and services for better monitoring and tracing coverage.
- Develop dashboards, alerts, and visualizations to provide actionable insights into system health and performance.
- Contribute to automation and self-healing practices that improve uptime and reduce operational toil.
- Stay current with trends in observability and advocate best practices across the engineering organization.
Requirements
- 7+ years of SRE/ Devops/ Cloud/ Infrastructure engineering experience with a focus on monitoring and observability.
- Strong communication skills with the ability to articulate technical requirements and explain benefits of observability clearly to development teams.
- Experience working in an area that requires strong business knowledge and the ability to pull together business parters and development teams to perform RCA across distributed systems.
- Experience implementing an Observability Framework at an organization.
- Hands-on experience with OpenTelemetry SDKs, collectors, and exporters.
- Proficiency with observability stacks such as Prometheus, Grafana, Loki, Tempo, Elastic Stack, or Splunk Observability (Splunk/AppDynamics).
- Strong knowledge on cloud platforms (GCP, or Azure).
- Hand-on experience on container orchestration using Kubernetes (OCP, GKE, AKS)
- Familiarity with CI/CD pipelines like (Jenkins and Github actions), infrastructure as code (Terraform/Ansible/ARM/CloudFormation).
- Experience provisioning infrastructure and capacity planning.
- Hands-on skills in programming languages like Java, and Python.
Talent Acquisition Specialist
+1 860 506 5032 (O)
https://www.linkedin.com/in/aadrickj/
If you’d no longer like to receive emails from me, simply reply with Unsubscribe in the subject line or Click to Unsubscribe or Opt-Out
Respecting your privacy is paramount to us, and we sincerely apologize for any inconvenience caused by any unsolicited message. Although we strive to contact only those who have explicitly opted in to hear from GRT Corp, it appears we may have reached you in error. If you did not grant permission—or if you simply prefer not to receive further correspondence—please let us know and we will permanently remove your address from our mailing records without delay. We value the trust you place in us, we never share your contact information with third parties, and process all opt-out requests promptly—typically within 48hrs. Thank you for your understanding, and please accept our apologies once again for any disruption this message may have caused.