DEVOPS Engineer (Observability Migration (Splunk → Datadog))
- Source: LinkedIn
- Metasys Technologies
- Remote
- Hyderabad
- Mid level
Job Description
DEVOPS Engineer (Observability Migration (Splunk → Datadog))
Remote
Notice Period: 30 Days
Key Responsibilities
Observability Migration (Splunk → Datadog)
- Execute discovery across the Splunk estate: data sources, ingestion paths (Universal/Heavy Forwarders, HEC, Firehose, syslog), volumes, props/transforms logic, content usage, and downstream consumers
- Deploy and manage Datadog Agents at scale (EKS/Kubernetes via Helm, EC2/on-prem via config management) alongside existing Splunk forwarders in a dual-run model
- Configure Datadog Observability Pipelines where required (in-network masking via Sensitive Data Scanner, filtering, routing)
- Design and enforce the tagging taxonomy, RBAC/Teams model, log index tiers (hot/Flex/Archive), and cost guardrails
- Migrate content: dashboards, monitors, and SIEM detections — using conversion accelerators, rebuilding complex SPL as Datadog queries/log-based metrics, deploying everything as Terraform (Datadog provider)
- Build validation tooling comparing platforms (volume, quality, alert behavior) and run evidence-gated, per-account cutovers with tested rollback
Azure DevOps Migration (instance → instance)
- Inventory and migrate ADO projects across organizations/instances: repos, boards/work items (with history), pipelines, artifacts, service connections, variable groups, and permissions
- Use and evaluate migration tooling (Azure DevOps Data Migration Tool, ADO REST APIs, third-party utilities); script gap-filling migrations via PowerShell/Python against the ADO API
- Re-establish pipeline integrity post-migration: service connections, agent pools, secrets (Key Vault integration), and approvals/policies
- Plan cutover with freeze windows, validation checklists, and rollback for in-flight work
GitHub & GitOps
- Migrate repositories to GitHub (Enterprise/Cloud) preserving history, branches, tags, and where feasible PR metadata; map ADO/legacy permissions to GitHub teams and CODEOWNERS
- Stand up GitHub Actions CI/CD (or integrate with existing pipelines), reusable workflows, environments, and OIDC-based cloud authentication
- Implement GitOps delivery patterns: infrastructure and platform configuration as code (Terraform), PR-based change management, drift detection, and automated deployment via Actions/Argo CD/Flux (as applicable)
- Define branch protection, secret scanning, and repository governance standards
Required Skills & Experience
- 6+ years in DevOps/Platform/SRE roles with at least one large-scale platform migration delivered end-to-end
- Observability hands-on Splunk administration (SPL, forwarder architecture, props/transforms, HEC) and Datadog (Agent, log pipelines, monitors, APM basics); understanding of OpenTelemetry
- IaC strong Terraform (modules, state management, provider ecosystems — Datadog provider a plus)
- Azure DevOps deep familiarity with projects, boards, YAML pipelines, and the ADO REST API; prior org-to-org migration experience strongly preferred
- GitHub Actions, branch protection, GitHub API/CLI, enterprise administration; GitOps tooling (Argo CD/Flux) experience valued
- Automation proficient in Python and/or PowerShell for API-driven tooling; Bash; config management (Ansible/Chef/Helm)
- Cloud AWS (EKS, EC2, Kinesis Firehose, S3, IAM) — Azure familiarity a plus
- Comfortable with change management, evidence-based cutover practices, and writing runbooks/rollback procedures
Skills
- splunk
- datadog
- Kubernetes
- helm
- guardrails
- Terraform
- microsoft-azure
- azure-devops
- powershell
- Python
- vault
- Github
- github-actions
- drift
- argo
- argo-cd
- opentelemetry
- yaml
- Ansible
- amazon-web-services
- amazon-eks
- amazon-ec2
- amazon-kinesis
- amazon-kinesis-firehose
- amazon-s3
- aws-iam
You missed this one - but you don't have to keep missing out. Try Club members get matched with open opportunities before they're gone, so you're always first in line, never last.
