Application Maintainer
Hiring an Application Maintainer to manage applications across data centres and cloud, scale horizontally and vertically, and hold a 99.9% uptime SLA.
We are looking for an Application Maintainer to keep our production estate healthy. Our applications run across multiple data centres and cloud providers, and this role is about keeping them available, predictable and within the 99.9% uptime commitment we make to customers.
The work is a mix of operational ownership and engineering. You will scale services horizontally and vertically as demand shifts, tune what is slow, automate what is repetitive, and be the person who understands why a system behaves the way it does at three in the morning.
What you will do
- Own the day-to-day health of production applications deployed across on-premise data centres and cloud environments.
- Meet and defend a 99.9% uptime SLA, tracking availability, latency and error budgets against it.
- Plan and execute horizontal and vertical scaling, including capacity forecasting ahead of demand.
- Monitor systems end to end and build alerting that catches real problems without drowning the team in noise.
- Lead incident response: triage, mitigate, restore service, then run a blameless post-mortem and close the follow-ups.
- Apply patches, security updates and dependency upgrades with minimal disruption.
- Automate routine operations through scripting and infrastructure as code.
- Maintain backup, failover and disaster recovery procedures, and test them rather than assuming they work.
- Keep runbooks, architecture notes and escalation paths current.
- Work with development teams on release readiness, deployment safety and production feedback.
What we are looking for
- Experience maintaining business-critical applications in production across data centre and cloud environments.
- Solid Linux administration, networking fundamentals and troubleshooting under pressure.
- Hands-on work with at least one major cloud platform such as AWS, Azure or Google Cloud.
- Containers and orchestration: Docker and Kubernetes, including scaling and rollout strategies.
- Monitoring and observability tooling such as Prometheus, Grafana, the ELK stack or equivalents.
- Scripting in Bash, Python or similar, plus infrastructure as code with Terraform, Ansible or comparable tools.
- Database operations including backups, replication, failover and query performance basics.
- CI/CD pipelines and safe deployment patterns such as blue-green or canary releases.
- Familiarity with SLA, SLO and error budget practice, and comfort participating in an on-call rotation.
Nice to have
- Load balancing, CDN and multi-region traffic management.
- Security hardening, vulnerability management and compliance work.
- Cost optimisation across cloud and hosted infrastructure.
- Cloud or Kubernetes certification.
How to apply
Send your resume with a short note about an outage you handled: what broke, how you restored service, and what you changed so it did not happen again.
Queries raised before signature
Everything worth knowing about Application Maintainer.
01What does an Application Maintainer do here?
You keep production applications running across our data centres and cloud environments, scale them as load changes, respond to incidents and hold the 99.9% uptime commitment.
02What uptime target does this role own?
A 99.9% availability SLA, which allows roughly 43 minutes of downtime per month.
03Is on-call part of the job?
Yes. On-call is shared across a rotation so the load is spread rather than landing on one person.
04Which cloud platforms will I work with?
Applications run across AWS, Azure and Google Cloud alongside on-premise data centres. Depth in one platform and willingness to learn the others works fine.
05Do I need Kubernetes experience?
Yes, practical experience with containers and orchestration matters because scaling and deployment work runs through them.
06Is this a development role or an operations role?
Both. You maintain and operate systems, and you write automation, tooling and infrastructure code to do it well.
07What is the difference between horizontal and vertical scaling here?
Horizontal scaling adds more instances behind a load balancer. Vertical scaling adds CPU, memory or storage to existing ones. You decide which fits the workload and the cost picture.
08What monitoring stack do you use?
Prometheus and Grafana for metrics, centralised log aggregation, and alerting tied to service level objectives.
09Will I handle security patching?
Yes. Patching, dependency upgrades and vulnerability remediation are part of keeping the estate healthy.
10Is remote work possible?
The role can be performed remotely where the on-call rotation and data centre access requirements allow. Discuss it during the interview.
11What does the interview process look like?
An introductory call, a technical discussion on systems and troubleshooting, a practical incident or scaling scenario, and a final conversation with the engineering lead.
12How do you handle post-incident reviews?
Blameless post-mortems focused on the system rather than the individual, with action items tracked to completion.
Sign off and we start
Tell us what you are trying to build. You will hear back from an engineer, not a sales desk.
- For
- e10 Infotech Private Limited
- Office
- Mumbai, Maharashtra
- Established
- 2011
- Direct line
- +91 86574 40720