Splunk Observability Engineer with Immediate joining
BengaluruOn-siteSenior
Applicants who checked fit first are 3.1× more likely to hear back
Before you apply
The post's words + ASAI's dataOn-site in Bengaluru.
OK with that?Senior level, usually 5-8 years.
You have them?No pay range in the post.
Not a repost. 171 of Wipro's last 3455 posts were reposts; 1060 of its 3216 open roles are here.
224 Data Engineer roles posted in Bengaluru this week, 1,430 open. See them →
Skills listed in the post · tap the ones you have · 0 of 8
You almost certainly match several of these already.
This post sets 2 stated bars and lists 8 skills. Tap where you stand - nothing is saved, no account needed.
ASAI checks this on every job for you, automatically, so you apply where you fit.
Fit Breakdown
ExampleHow an ASAI match score looks. Yours is built from your resume, not a guess.
Your score for this role already exists - sign in to view it
ASAI compared this JD against 41 signals - skills, seniority, domain, stack overlap etc. Add a resume and it unlocks in about 30 seconds.
Always free · no credit card · 1 tap with Google
Tools on this job
60-Day PassStarts free · 60-Day Pass ₹149 for 60 days, GST included
Free account, no card needed.
The job post
516 words · from Wipro's careers siteJob Description
Role Purpose
The purpose of this role is to support delivery through development and deployment of tools.
͏
Title: Splunk Observability
Total years of experience: 6 years to 10 years
Location: Anywhere in India
Role: Observability (O11y) Engineer (Enterprise Observability Platform)
We are building a next‑generation Enterprise Observability Platform using Splunk Enterprise, ITSI, and Splunk Observability Cloud (O11y) for our clients. We are seeking a Splunk O11Y- Observability Engineer to lead the design, deployment, and enablement of observability capabilities across applications, infrastructure, and cloud environments.
This role focuses on instrumentation, telemetry pipeline engineering, service modeling, APM rollout, and onboarding new teams into the observability ecosystem. The engineer will work closely with application owners, SRE, DevOps, and platform engineering teams to deliver full‑stack visibility and accelerate observability adoption.
Key Responsibilities
Observability Architecture & Implementation
- Design and implement observability solutions using Splunk Observability Cloud (APM, Infrastructure Monitoring, RUM, Log Observer).
- Build and optimize OpenTelemetry (OTel) collector pipelines for metrics, traces, and logs.
- Define instrumentation strategies for applications (auto‑instrumentation, SDKs, agents).
- Develop service maps, dependency graphs, and distributed tracing configurations.
͏
Application & Service Onboarding
- Partner with application teams to onboard services into O11y and ITSI.
- Define SLIs/SLOs, KPIs, and service health indicators.
- Build dashboards, detectors, alerts, and anomaly detection rules tailored to each service.
- Ensure consistent tagging, metadata, and observability standards across teams.
ITSI & Splunk Core Integration
- Implement ITSI service models, KPIs, correlation searches, and glass tables.
- Integrate O11y telemetry with Splunk Enterprise and ITSI for unified service health.
- Collaborate with Splunk Core SMEs to align ingestion, retention, and data modeling.
Telemetry Pipeline Engineering
- Deploy and configure OTel collectors across VMs, containers, Kubernetes, and cloud services.
- Implement processors, exporters, and routing logic for efficient telemetry flow.
- Optimize pipelines for performance, cost, and reliability.
Enablement & Best Practices
- Develop onboarding guides, instrumentation patterns, and observability standards.
- Conduct workshops, demos, and training sessions for engineering teams.
- Provide architectural guidance on observability adoption across the enterprise.
Cross‑Functional Collaboration
- Work with SRE, DevOps, Cloud, and Application teams to embed observability into CI/CD and deployment workflows.
- Support modernization initiatives such as microservices, Kubernetes, and cloud migrations.
- Influence platform roadmap and observability strategy.
Required Skills & Experience
Technical Skills
- Hands‑on experience implementing Splunk Observability Cloud (APM, Infra Monitoring, RUM, Log Observer).
- Strong understanding of OpenTelemetry (collectors, processors, exporters, instrumentation).
- Experience with distributed tracing, span analysis, and service dependency mapping.
- Familiarity with Splunk Enterprise and ITSI for integrated observability use cases.
- Strong Linux/Unix skills and scripting (Python, Bash).
- Experience with Kubernetes, Docker, and cloud platforms (AWS, and Azure).
Implementation & Architecture Skills
- Experience designing observability solutions for microservices, APIs, and distributed systems.
- Ability to guide teams through instrumentation and telemetry onboarding.
- Strong understanding of SLIs/SLOs, service health scoring, and reliability engineering.
Soft Skills
- Excellent communication and stakeholder‑facing skills.
- Ability to lead workshops and influence engineering teams.
- Strong documentation and architectural thinking.
Preferred Qualifications
- Splunk Observability or OTel certifications.
- Experience with Prometheus, Grafana, Datadog, New Relic, or similar tools.
- Familiarity with Terraform, Ansible, GitOps, or CI/CD pipelines.
- Experience in large enterprise, utilities, financial, or public sector environments.
͏
Free · no signup
Get tomorrow's jobs before you have to search
