AWS DevOps Engineerll [email protected] ll

ROLES AND RESPONSIBILITIES:

• Plan, schedule, and manage all releases across product and customer projects.
• Define and maintain the release calendar, identifying dependencies and managing risks proactively.
• Partner with engineering, QA, DevOps, and product management to ensure release readiness.
• Create release documentation (notes, guides, videos) for both internal stakeholders and customers.
• Run a release review process with product leads before publishing.
• Publish releases and updates to the company website release section.
• Drive communication of release details to internal teams and customers in a clear, concise way.
• Manage post-release validation and rollback procedures when required.
• Continuously improve release management through automation, tooling, and process refinement.

IDEAL CANDIDATE:

• 3+ years of experience in Release Management, DevOps, or related roles.
• Strong knowledge of CI/CD pipelines, source control (Git), and build/deployment practices.
• Experience creating release documentation and customer-facing content (videos, notes, FAQs).
• Excellent communication and stakeholder management skills; able to translate technical changes into business impact.
• Familiarity with SaaS, iPaaS, or enterprise software environments is a strong plus.

PERKS, BENEFITS AND WORK CULTURE:

• Competitive salary package.
• Opportunity to learn from and work with senior leadership & founders.
• Build solutions for large enterprises that move from concept to real-world impact.
• Exceptional career growth pathways in a highly innovative and rapidly scaling environment.

Why this role exists

Our infrastructure footprint is growing faster than our headcount, and we believe most of that

gap should be closed by automation and AI agents — not by hiring more humans to do toil. We

need someone early in their career who treats manual work as a bug, ships scripts and agents

instead of tickets, and wants to grow into deeper ownership over the next two years.

You will not be the most senior person on the team. You will be the one who multiplies the team.

What you'll own

In your first 1 months

• Take ownership of one slice of our CI/CD pipeline and make it measurably

faster, more reliable, or cheaper. We expect a number on a dashboard to move.

• Build at least three internal automations that replace manual ops toil —

using AI agents (Claude Code, agentic CLIs, scripted LLM workflows) as your force

multiplier.

• Be the first responder for a defined set of alerts. Write the runbooks. Drive

the alert volume down.

• Support senior engineers on AI/ML infrastructure (GPU nodes, inference

services, model deployment) — observe, document, and gradually take on contained

changes under review.

By 3 months you should be

• The go-to person for at least two production systems.

• Shipping routine infrastructure changes without needing senior review.

• Treating "manual" as a code smell.

Required (we will reject without these)

• 0–3 years hands-on experience with one major cloud (AWS, GCP, or

Azure — one is fine, depth beats breadth).

• Fluent in Linux command line, bash, and at least one scripting language

(Python or Go preferred).

• Have shipped something to production that real users hit. A side project

counts; a graded coursework lab does not.

• Comfortable with Docker — you can explain what an image vs. a

container is and why it matters.

• Working knowledge of networking fundamentals: DNS, HTTP/HTTPS,

TLS, ports, basic subnets — enough to debug "it works on my machine."

• Git fluency: branches, merges, rebases, conflict resolution.

• CI/CD pipelines — you have authored or substantially modified pipelines

in GitHub Actions, GitLab CI, ArgoCD, Jenkins, or similar. Not just "I clicked Re-run."

• Kubernetes basics — kubectl for real work, can read pod logs,

understand deployments and services, can debug a CrashLoopBackOff without

panicking. You do not need to have run a cluster; you do need to have lived inside one.

• Active user of AI coding agents (Claude Code, Cursor, Copilot, agentic

CLIs, etc.). You should be able to walk us through specific tasks where they made you

faster, and specific tasks where they failed you and how you noticed. "I have tried it" is

not enough.

Bonus (real plus, not required)

• Infrastructure as Code: Terraform, Pulumi, or Ansible.

• Observability: Prometheus/Grafana, Datadog, OpenTelemetry, any APM.

• Have built or extended an LLM-based agent — a custom MCP server, a

scripted multi-step workflow, an internal tool that calls models in a loop. Anything beyond

chat-with-Claude.

• Exposure to GPU workloads, model serving (vLLM, Triton, TGI, etc.), or

ML pipelines.

What we don't care about

• Whether your degree is in CS — or whether you have a degree at all.

• Brand-name companies on your resume.

• Certifications. They are fine. They do not substitute for having shipped.

How we work

• We default to automation. If you do something manually twice, the third

time you script it or hand it to an agent.

• AI agents are part of the workflow, not a novelty. Expect interview

questions about exactly how you use them — and where you have caught them being

wrong.

• Small, reversible changes beat big-bang rollouts.

• Postmortems are blameless and written down.

• We push back on each other. If you only execute, you will be unhappy

here.

How to apply

Send:

• Your resume.

• A short note (≤200 words) describing one infra or automation problem you

solved, and how AI agents factored in — or did not, and why. We read these. Generic

notes get rejected.

Internal note — delete before posting externally

• Comp band, location policy, team name, and reporting line marked

[CONFIRM] need to be filled in before this goes external.

• The Required list is intentionally tight: CI/CD and Kubernetes basics

promoted from bonus. Expect this to filter ~80% of typical junior DevOps applicants. The

remaining pool will skew toward people who have actually shipped infra at a startup, not

bootcamp grads or pure cloud-cert holders.

• IaC, observability, agent-building, and GPU/ML serving stay as bonus.

Promoting any of these to required at 0–3 yrs collapses the pool to near-zero or forces

hiring senior people at junior comp. If you want IaC required, re-level this to mid (3–5

yrs) and raise the band.

• Screening implication: the resume screen should explicitly check for

CI/CD pipeline authorship and any K8s-touching production work. If neither is on the

resume, reject at screen. Do not waste interview slots.

• Pipeline watch: if fewer than ~15 qualified resumes after 2 weeks of

active sourcing, the first thing to relax is the AI-agent-fluency bar (move to bonus and

screen for it in interview instead). Do not relax the "shipped to production" requirement

— that is the load-bearing filter.

Skills We Require:- Dev Ops, AWS Admin, terraform, Infrastructure as a Code

SUMMARY:-

• Implement integrations requested by customers
• Deploy updates and fixes
• Provide Level 2 technical support
• Build tools to reduce occurrences of errors and improve customer experience
• Develop software to integrate with internal back-end systems
• Perform root cause analysis for production errors
• Investigate and resolve technical issues
• Develop scripts to automate visualization
• Design procedures for system troubleshooting and maintenance

Have good hands on experience on Dev Ops, AWS Admin, terraform, Infrastructure as a Code

Have knowledge on EC2, Lambda, S3, ELB, VPC, IAM, Cloud Watch, Centos, Server Hardening

Ability to understand business requirements and translate them into technical requirements

Job Description

We are looking to add DevOps Engineer to the Infra team. 

Roles & Responsibilities

What you do :

• Developing automation for the various deployments core to our business
• Documenting run books for various processes / improving knowledge bases
• Identifying technical issues, communicating and recommending solutions
• Miscellaneous support (user account, VPN, network, etc)
• Develop continuous integration / deployment strategies
• Production systems deployment/monitoring/optimization

• Management of staging/development environments

What you know :

• Ability to work with a wide variety of open source technologies and tools
• Ability to code/script (Python, Ruby, Bash)
• Experience with systems and IT operations
• Comfortable with frequent incremental code testing and deployment
• Strong grasp of automation tools (Chef, Packer, Ansible, or others)
• Experience with cloud infrastructure and bare-metal systems
• Experience optimizing infrastructure for high availability and low latencies
• Experience with instrumenting systems for monitoring and reporting purposes
• Well versed in software configuration management systems (git, others)
• Experience with cloud providers (AWS or other) and tailoring apps for cloud deployment

• Data management skills

Education :

• Degree in Computer Engineering or Computer Science
• 1-3 years of equivalent experience in DevOps roles.
• Work conducted is focused on business outcomes
• Can work in an environment with a high level of autonomy (at the individual and team level)

• Comfortable working in an open, collaborative environment, reaching across functional.

Our Offering :

• True start-up experience - no bureaucracy and a ton of tough decisions that have a real impact on the business from day one.

• The camaraderie of an amazingly talented team that is working tirelessly to build a great OS for India and surrounding markets.

Perks :

• Awesome benefits, social gatherings, etc.
• Work with intelligent, fun, and interesting people in a dynamic start-up environment.

Eligibility

B.Tech/M.Tech/B.E

Company Introduction

Established in May 2015, Indus OS is a homebred system apps company, building India’s only content and commerce platform for users to discover and consume digital content & services in the language of their choice. With a vision of digitally connecting 1 Billion Indians, Indus OS is constantly striving to adapt its existing portfolio (App Store, Minus One Screen, Keyboard, Messenger, etc) by introducing new features to enrich the user experience in their native language.
Currently, Indus OS has a user base of over 12+ Million on the back of 10+ smartphone brand partnerships with leading OEMs such as Samsung, Gionee, iTel, Micromax, Intex, Karbonn, and others. The Indus platform is available in English & 23 Indian regional languages and is intended to digitally connect the next 1 billion people in the emerging markets.