> Markdown version of [/jobs/ext/4589447-data-operations-analyst](https://www.wearedevelopers.com/jobs/ext/4589447-data-operations-analyst). Every page supports `.md` or `Accept: text/markdown`. Links point to the HTML versions so they work for humans too. Agent guide: [/agents.md](https://www.wearedevelopers.com/agents.md).

---

# Data Operations Analyst

- **Company:** TEKSYSTEMS INC.
- **Location:** Miamisburg, OH, United States (Remote available)
- **Experience:** Experienced
- **Salary:** $104,000 - $124,800
- **Contract:** Temporary contract
- **Skills:** Java (Programming Language), Application Programming Interfaces (APIs), Microsoft Azure, Databases, Data Infrastructure, Extract Transform Load (ETL), Distributed Data Store, Entity Framework, Github, Kusto Query Language, DataOps, Software Deployment, Software Engineering, SQL Databases, Workflow Management Systems, Diagnostic Tools, Data Ingestion, Grafana, Kubernetes, Low Latency, Cosmos DB
- **Published:** November 5, 2026
- **Apply:** https://www.careercircle.com/jobs/all/all/usa/oh/miamisburg/4090ade1-3fb8-43dd-8c24-44b2426e46e7

## About the Role

3+ years in production application support, data platform operations, ETL operations, or related technical operations.

Hands-on production Azure Cosmos DB support, including monitoring and troubleshooting ingestion failures, RU

consumption, HTTP 429 throttling, and recovery procedures.

Production ETL/data ingestion operations, including batch workflows, job failures, retries, recovery, and

upstream/downstream dependencies.

Understanding of distributed data-processing behavior, including throughput constraints, throttling, retries, and error

handling.

Experience using dashboards, application logs, and diagnostic tools to investigate production incidents.

Familiarity with incident triage, escalation, production change controls, and operational documentation.

Strong communication, organization, and troubleshooting judgment; ability to work independently within approved

operational procedures.

Skills

Operations analysis, Azure Cosmos DB, ETL, High-volume or business-critical Cosmos DB ingestion experience.

Experience supporting Java-based enterprise or batch applications, including analysis of exceptions and runtime errors.

Grafana, Grafana IRM, GitHub Issues, GitHub Actions, or comparable monitoring and workflow tools.

Azure, AKS, ADLS, Kubernetes, SQL, or KQL familiarity; deep platform engineering knowledge is not required.

Experience with approved production deployments and geographically distributed support teams., Individual compensation offered for this position within this range will depend on many factors, including qualifications, skills, relevant experience, job knowledge, geographic location, internal equity, and other pertinent job-related factors.

## Description

Github
Tooling
Grafana
Fallback
Dashboard
Operations
Leadership
Kubernetes
Nearshoring
Communication
Change Control
Data Ingestion
API Throttling
Microsoft Azure
Azure Cosmos DB
Diagnostic Tools
Technical Support
Incident Response
Business Valuation
Workflow Management
Software Development
Full Stack Development
Distributed Data Store
Business Transformation
Authorization (Computing)
SQL (Programming Language)
Product Family Engineering
Java (Programming Language)
Extract Transform Load (ETL)
Continuous Improvement Process
Troubleshooting (Problem Solving)
Activities Of Daily Living (ADLs), We are seeking an experienced Data Platform Operations Analyst to support production operations across the Entity

Database (EDB) platform: Vault, KEL, large-scale data ingestion, ETL processing, Azure Cosmos DB, and downstream entity

data services.

The role focuses on monitoring, incident response, troubleshooting, and approved operational recovery, with particular

emphasis on production Cosmos DB ingestion and ETL workflows. Working with the EDB Operations Functional Lead

and engineering teams, the analyst will use established tooling and runbooks to keep services operating reliably and

escalate issues requiring deeper engineering expertise.

This is an L1 production operations role, not a software development or infrastructure engineering position.

Key Responsibilities

Production Monitoring & Incident Response

Monitor Vault, KEL, Cosmos DB, and ingestion pipelines using Grafana and engineering-provided tools; perform routine

daily health checks.

Identify stalled or failed jobs and investigate application errors, Cosmos RU usage, HTTP 429 throttling, latency, and

ingestion failures.

Respond to Grafana IRM incidents: triage, document, execute approved recovery procedures, and escalate when

necessary.

Support major and critical incidents under engineering or Ops leadership, including execution of explicitly directed

recovery steps.

Operational Execution

Execute authorized retries, workflow restarts, dataset promotions, and other clearly defined production service requests.

Deploy approved application images through established pipelines and perform post-deployment health checks.

Track operational work through GitHub Issues, Grafana IRM, and existing auditable execution records; follow change

and authorization controls.

Coordination & Continuous Improvement

Coordinate routine incidents with Vault engineering, KEL engineering, SRE, and the Operations Functional Lead; provide

concise internal status updates.

Maintain incident notes, daily operational summaries, and follow-the-sun regional handoffs.

Identify recurring failures and trends; escalate findings and create actionable GitHub Issues for engineering.

Maintain operational checklists, troubleshooting guides, and known-issue documentation. Engineering approves changes

to technical recovery procedures., US fallback: If a suitable nearshore hire cannot be found, candidates in Dayton and surrounding areas, including Cincinnati

and Columbus, may be considered for a hybrid role with required Dayton office attendance.

The analyst participates in a 24/5 global follow-the-sun model across the Americas, India, and East Asia, plus rotating

weekend on-call during US business hours for major and critical incidents routed through Grafana IRM. Routine noncritical

issues generally wait for staffed weekday operations.

Operational autonomy expands through competency-based onboarding: from monitoring and guided execution to

independent routine recovery and limited, engineering-directed advanced operations. Engineering retains technical