Observability Engineer / Senior Observability Engineer (New Relic, Azure)-6-8 Years-Immediate

Hi,

Greetings for the day!!!

We have an excellent opportunity for Observability Engineer / Senior Observability Engineer (New Relic, Azure) with one of my esteemed client for Bangalore/Hyderabad location

Role: Observability Engineer / Senior Observability Engineer (New Relic, Azure)

Experience: 6+ Years

Location: Bangalore/Hyderabad - Hybrid 3 days in a Week WFO

Immediate Joiners Only

Excellent Communication Skills

Note: Candidates must be able to attend an in-person discussion at any of our client locations.

Key requirement: The candidate should have hands-on experience in implementing and managing observability solutions using New Relic, not just using observability tools for monitoring and alert consumption.

The role requires practical expertise in designing, deploying, and optimizing observability capabilities.

In addition to New Relic experience, the JD includes requirements for:

Terraform knowledge

Basic Azure cloud knowledge

Other relevant observability and platform engineering skills outlined in the attached JD

JD:

We are seeking an experienced Observability Engineer (6–8 years) with strong hands-on implementation expertise in New Relic to design, build, and operate end-to-end observability

across applications and cloud infrastructure.

The role focuses on APM, Distributed Tracing, Synthetic Monitoring, RUM, dashboards, alerting, NRQL, and integrations with ITSM/DevOps tooling such as ServiceNow and Jira.

Experience with secondary

observability platforms (Dynatrace, Datadog, etc.) is a plus.

You will also contribute to automation using Terraform and CI/CD, and support Azure-native observability using Azure

Monitor, KQL, Logic Apps, and related services. Familiarity with SRE

concepts including SLI/SLO/SLA, error budgets, and reliability reporting is required.

Goal Build and continuously improve a scalable, automated observability platform and practices that improve system reliability, reduce MTTR, and enable data-driven operations and engineering decisions.

Key Responsibilities

New Relic Implementation & Operations (Primary)

 Implement and maintain New Relic Observability across services and environments (dev/test/prod).

 Configure and tune:

 APM instrumentation (language agents, configuration standards, naming conventions).

 Distributed tracing (trace propagation, sampling, service maps).

 RUM for user experience monitoring and frontend performance insights.

 Synthetic monitoring (availability, API tests, scripted monitors, private locations if applicable).

 Build and maintain dashboards for engineering, operations, and leadership views (service health, golden signals, business KPIs).

 Design and manage alerts: policies, conditions, incident preferences, noise reduction, correlation, and runbook links.

 Write and optimize NRQL queries for metrics/logs/traces, SLOs, anomaly detection, and reporting.

Integrations & Incident Management

 Integrate New Relic with service management and collaboration tools:

 ServiceNow (incident creation, enrichment, assignment rules, CMDB/service mapping where applicable).

 Jira (ticket automation for reliability workstreams, defects, and problem records).

 Support on-call and incident response by improving alert quality, investigation workflows, and post-incident learnings (RCA support).

Azure Cloud Observability

 Implement and operate Azure observability capabilities, including:

 Azure Monitor, Log Analytics, and diagnostic settings.

 KQL queries for operational dashboards and investigations.

 Logic Apps for workflow automation and alert routing/notifications.

 Ensure cloud telemetry completeness for workloads running in Azure (VMs, AKS, App Services, Functions—based on your environment).

Automation (Terraform + CI/CD)

 Use Terraform to codify observability configurations where feasible (dashboards, alert policies, monitoring resources, cloud settings).

 Build/maintain CI/CD pipelines to automate deployment of monitoring-as-code and reduce manual configuration drift.

 Maintain version control, peer review practices, and environment promotion (dev → prod).

Reliability Engineering (SRE Concepts)

 Define and implement service reliability metrics: SLI, SLO, SLA, and error budgets.

 Partner with engineering teams to set measurable reliability objectives and drive continuous improvement.

 Produce reliability reporting (trends, burn rates, availability/performance posture) and support governance reviews.

R…