Skip to content
Search jobs inside your AI agent. Claude, ChatGPT, Claude Code, Codex, Gemini, Cursor and Grok
Connect

Prama Innovations India Pvt. Ltd.

NewBe an early applicant

Data Operations Engineer

Posted Updated

Description

Data Operations Engineer

Role summary
The Data Operations Engineer will support the reliable, scalable, and cost-effective operation of
the team’s data platforms. The primary focus of this role is operating and improving Redshift,
Databricks, and Snowflake environments, while contributing to data lake development, database
modeling, performance tuning, and production support.
The ideal candidate is comfortable working across data engineering and platform operations.
They should be able to investigate failures, improve system performance, automate repeatable
work, and make controlled changes through established CI/CD and infrastructure-as-code
practices.


Core responsibilities
Operate and support Amazon Redshift, Databricks, Snowflake, PostgreSQL, and
MySQL platforms.
Build, maintain, and troubleshoot data lake ingestion and processing workflows.
Investigate data pipeline failures, query performance issues, capacity constraints, and
production incidents.
Develop and maintain database models, schemas, tables, views, and data movement
patterns.
Apply performance-tuning techniques across relational databases and analytical
platforms.
Monitor platform health, pipeline reliability, workload performance, storage, compute
utilization, and operational costs.
Create repeatable operational procedures, runbooks, dashboards, and validation
checks.
Implement changes through Git-based workflows, code review, automated testing, and
controlled deployments.
Support CI/CD pipelines using Jenkins and Argo CD.
Work with Kubernetes-based services and deployments when operating data platform
components.
Use Terraform to provision and manage infrastructure consistently across environments.
Use advanced AI models effectively for technical investigation, SQL and code
development, documentation, troubleshooting, automation, and operational analysis.
Validate AI-generated recommendations, code, and configurations against system
requirements, security policies, tests, and production-safe operating practices.
Collaborate with engineers and stakeholders to document dependencies, risks,
implementation details, and rollback plans.
Follow data security, privacy, access-control, and change-management practices when
handling production data.


Required technical familiarity
Data platforms and databases
PostgreSQL: SQL, schema design, indexes, transactions, locks, connections, backups,
replication concepts, and troubleshooting.
Amazon Redshift: workload management, distribution and sort strategies,
vacuum/analyze concepts, query plans, table design, concurrency, scaling, and cost
awareness.
Databricks: workspace concepts, Apache Spark fundamentals, notebooks and jobs,
Delta Lake, medallion-style data organization, cluster configuration, Unity Catalog
concepts, and pipeline troubleshooting.
Snowflake: warehouses, databases and schemas, stages, loading patterns, SQL
performance, resource utilization, access controls, and cost management.
Data lakes: object-storage layout, file formats such as Parquet, partitioning, schema
evolution, incremental processing, data quality, and replay or backfill strategies.
Data modeling: normalized and dimensional models, fact and dimension tables, keys,
grain, slowly changing dimensions, and model performance considerations.
CI/CD and infrastructure
Git: branching, pull requests, code review, merge practices, tagging, and resolving
conflicts.
Jenkins: pipeline configuration, build and deployment stages, credentials handling, test
execution, and troubleshooting failed builds.
Argo CD: GitOps principles, application synchronization, deployment health, drift
detection, rollback, and troubleshooting sync failures.
Kubernetes: core concepts including pods, deployments, services, namespaces,
configuration, secrets, logs, resource requests and limits, and rollout behavior.
Terraform: modules, variables, state, plans, applies, drift, dependency management, and
safe infrastructure changes.


Performance-tuning expectations
The engineer should be able to approach performance issues methodically by:
Establishing a baseline using query history, execution plans, workload metrics, and
resource utilization.
Identifying whether the bottleneck is caused by SQL, data layout, joins, statistics,
concurrency, compute capacity, storage, network activity, or orchestration.
Applying the smallest safe change that addresses the root cause.
Measuring the result and documenting before-and-after behavior.
Considering cost, operational risk, data correctness, and rollback options in addition to
raw execution time.


Data operations expectations
Treat production changes as controlled operational work, not ad hoc experimentation.
Validate changes in a lower environment whenever practical before production rollout.
Prefer idempotent, restartable, and observable pipelines.
Protect sensitive data and avoid exposing credentials, private keys, or personally
identifiable information in logs, code, or datasets.
Use alerts and monitoring to distinguish transient failures from systemic reliability
problems.
Document assumptions, dependencies, known limitations, and recovery steps.
Communicate status clearly during incidents and follow through on post-incident actions.

Skills

Apply

See also