DevOps + Java

Job Title : Senior DevOps Engineer

Experience : 5+ Years

Location : Gurgaon, Sector 39

About the Role :

We are seeking an experienced Senior DevOps Engineer to lead our DevOps practices, manage a small team, and build functional, scalable systems that enhance customer experience. You will be responsible for deployments, automation, troubleshooting, integrations, monitoring, and team mentoring while ensuring secure and efficient operations.

Mandatory Skills :

Linux Administration, Shell Scripting, CI/CD (Jenkins), Git/GitHub, Docker, Kubernetes, AWS, Ansible, Database Administration (MariaDB/MySQL/MongoDB), Apache httpd/Tomcat, HAProxy, Nagios, Keepalived, Monitoring/Logging/Alerting, and On-premise Server Management.

Key Responsibilities :

• Implement and manage integrations as per business and customer needs.
• Deploy product updates, fixes, and enhancements.
• Provide Level 2 technical support and resolve production issues.
• Build tools to reduce errors and improve system performance.
• Develop scripts and automation for CI/CD, monitoring, and visualization.
• Perform root cause analysis of incidents and implement long-term fixes.
• Ensure robust monitoring, logging, and alerting systems are in place.
• Manage on-premise servers and ensure smooth deployments.
• Collaborate with development teams for system integration.
• Mentor and guide a team of 3 to 4 engineers.

Required Qualifications & Experience :

• Bachelor’s degree in Computer Science, Software Engineering, IT, or related field (Master’s preferred).
• 5+ years of experience in DevOps engineering with team management exposure.
• Strong expertise in:
• Linux Administration & Shell Scripting
• CI/CD pipelines (Jenkins or similar)
• Git/GitHub, branching, and code repository standards
• Docker, Kubernetes, AWS, Ansible
• Database administration (MariaDB, MySQL, MongoDB)
• Web servers (Apache httpd, Apache Tomcat)
• Networking & Load Balancing tools (HAProxy, Keepalived)
• Monitoring & alerting tools (Nagios, logging frameworks)
• On-premise server management
• Strong debugging, automation, and system troubleshooting skills.
• Knowledge of security best practices including data encryption.

Personal Attributes :

• Excellent problem-solving and analytical skills.
• Strong communication and leadership abilities.
• Detail-oriented with a focus on reliability and performance.
• Ability to mentor juniors and collaborate with cross-functional teams.
• Keen interest in emerging DevOps and cloud trends.

We are looking for very hands-on DevOps engineers with 3 to 6 years of experience. The person will be part of a team that is responsible for designing & implementing automation from scratch for medium to large scale cloud infrastructure and providing 24x7 services to our North American / European customers. This also includes ensuring ~100% uptime for almost 50+ internal sites. The person is expected to deliver with both high speed and high quality as well as work for 40 hours per week (~6.5 hours per day, 6 days per week) in shifts that will rotate every month.

This person MUST have:

• B.E Computer Science or equivalent

• 2+ Years of hands-on experience troubleshooting/setting up of the Linux environment, who can write shell scripts for any given requirement.

• 1+ Years of hands-on experience setting up/configuring AWS or GCP services from SCRATCH and maintaining them.

• 1+ Years of hands-on experience setting up/configuring Kubernetes & EKS and ensuring high availability of container orchestration.

• 1+ Years of hands-on experience setting up CICD from SCRATCH in Jenkins & Gitlab.

• Experience configuring/maintaining one monitoring tool.

• Excellent verbal & written communication skills.

• Candidates with certifications - AWS, GCP, CKA, etc will be preferred

• Hands-on experience with databases (Cassandra, MongoDB, MySQL, RDS).

Experience:

• Min 3 years of experience as DevOps automation engineer buildingg, running, and maintaining production sites.

• Not looking for candidates who have experience only as L1/L2 or Build & Deploy.
  
  

Location: Remotely, anywhere in India.

Timings:

• The person is expected to deliver with both high speed and high quality as well as work for 40 hours per week (~6.5 hours per day, 6 days per week) in shifts that will rotate every month.
  
  

Position:

• Full time/Direct

• We have great benefits such as PF, medical insurance, 12 annual company holidays, 12 PTO leaves per year, annual increments, Diwali bonus, spot bonuses and other incentives etc.

• We dont believe in locking in people with large notice periods.  You will stay here because you love the company.  We have only a 15 days notice period.

JOB DETAILS:

* Job Title: Specialist I - DevOps Engineering

* Industry: Global Digital Transformation Solutions Provider

* Salary: Best in Industry

* Experience: 7-10 years

* Location: Bengaluru (Bangalore), Chennai, Hyderabad, Kochi (Cochin), Noida, Pune, Thiruvananthapuram

Job Description

Job Summary:

As a DevOps Engineer focused on Perforce to GitHub migration, you will be responsible for executing seamless and large-scale source control migrations. You must be proficient with GitHub Enterprise and Perforce, possess strong scripting skills (Python/Shell), and have a deep understanding of version control concepts.

The ideal candidate is a self-starter, a problem-solver, and thrives on challenges while ensuring smooth transitions with minimal disruption to development workflows.

Key Responsibilities:

• Analyze and prepare Perforce repositories — clean workspaces, merge streams, and remove unnecessary files.
• Handle large files efficiently using Git Large File Storage (LFS) for files exceeding GitHub’s 100MB size limit.
• Use git-p4 fusion (Python-based tool) to clone and migrate Perforce repositories incrementally, ensuring data integrity.
• Define migration scope — determine how much history to migrate and plan the repository structure.
• Manage branch renaming and repository organization for optimized post-migration workflows.
• Collaborate with development teams to determine migration points and finalize migration strategies.
• Troubleshoot issues related to file sizes, Python compatibility, network connectivity, or permissions during migration.

Required Qualifications:

• Strong knowledge of Git/GitHub and preferably Perforce (Helix Core) — understanding of differences, workflows, and integrations.
• Hands-on experience with P4-Fusion.
• Familiarity with cloud platforms (AWS, Azure) and containerization technologies (Docker, Kubernetes).
• Proficiency in migration tools such as git-p4 fusion — installation, configuration, and troubleshooting.
• Ability to identify and manage large files using Git LFS to meet GitHub repository size limits.
• Strong scripting skills in Python and Shell for automating migration and restructuring tasks.
• Experience in planning and executing source control migrations — defining scope, branch mapping, history retention, and permission translation.
• Familiarity with CI/CD pipeline integration to validate workflows post-migration.
• Understanding of source code management (SCM) best practices, including version history and repository organization in GitHub.
• Excellent communication and collaboration skills for cross-team coordination and migration planning.
• Proven practical experience in repository migration, large file management, and history preservation during Perforce to GitHub transitions.

Skills: Github, Kubernetes, Perforce, Perforce (Helix Core), Devops Tools

Must-Haves

Git/GitHub (advanced), Perforce (Helix Core) (advanced), Python/Shell scripting (strong), P4-Fusion (hands-on experience), Git LFS (proficient)

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.

Must Have -

a. Background working with Startups

b. Good knowledge of Kubernetes & Docker

c. Background working in Azure

What you’ll be doing

• Ensure that our applications and environments are stable, scalable, secure and performing as expected.
• Proactively engage and work in alignment with cross-functional colleagues to understand their requirements, contributing to and providing suitable supporting solutions.
• Develop and introduce systems to aid and facilitate rapid growth including implementation of deployment policies, designing and implementing new procedures, configuration management and planning of patches and for capacity upgrades
• Observability: ensure suitable levels of monitoring and alerting are in place to keep engineers aware of issues.
• Establish runbooks and procedures to keep outages to a minimum. Jump in before users notice that things are off track, then automate it for the future.
• Automate everything so that nothing is ever done manually in production.
• Identify and mitigate reliability and security risks. Make sure we are prepared for peak times,
• DDoS attacks and fat fingers.
• Troubleshoot issues across the whole stack - software, applications and network.
• Manage individual project priorities, deadlines, and deliverables as part of a self-organizing team.
• Learn and unlearn every day by exchanging knowledge and new insights, conducting constructive code reviews, and participating in retrospectives.

Requirements

• 2+ years extensive experience of Linux server administration include patching, packaging (rpm), performance tuning, networking, user management, and security.
• 2+ years of implementing systems that are highly available, secure, scalable, and self-healingon Azure cloud platform
• Strong understanding of networking, especially in cloud environments along with a good understanding of CICD.
• Prior experience implementing industry standard security best practices, including those recommended by Azure
• Proficiency with Bash, and any high-level scripting language.
• Basic working knowledge of observability stacks like ELK, prometheus, grafana, Signoz etc
• Proficiency with Infrastructure as Code and Infrastructure Testing, preferably using Pulumi/Terraform.
• Hands-on experience in building and administering VMs and Containers using tools such as Docker/Kubernetes.
• Excellent communication skills, spoken as well as written, with a demonstrated ability to articulate technical problems and projects to all stakeholders.

• As a DevOps Engineer, you need to have strong experience in CI/CD pipelines.
• Setup development, testing, automation tools, and IT infrastructure
• Defining and setting development, test, release, update, and support processes for DevOps operation
• Selecting and deploying appropriate CI/CD tools
• Deploy and maintain CI/CD pipelines across multiple environments (Mobile, Web API’s & AIML)

• 3+ years of experience as DevOps Engineer and strong working knowledge in CI/CD pipelines
• Experience administering and deploying development CI/CD using Git, BitBucket, CodeCommit, Jira, Jenkins, Maven, Gradle, etc
• Strong knowledge in Linux-based infrastructures and AWS/Azure/GCP environment
• Working knowledge on AWS (IAM, EC2, VPC, ELB, ALB, Autoscaling, Lambda, etc)
• Experience with Docker containerization and clustering (Kubernetes/ECS)
• Experience on Android source(AOSP) clone, build, and automation ecosystems
• Knowledge of scripting languages such as Python, Shell, Groovy, Bash, etc
• Familiar with Android ROM development and build process
• Knowledge of Agile Software Development methodologies

1. GCP Cloud experience mandatory
2. CICD - Azure DevOps
3. IaC tools – Terraform
4. Experience with IAM / Access Management within cloud
5. Networking / Firewalls
6. Kubernetes / Helm / Istio

Mandatory Requirement/ Preference:

1.PowerBuild technology experience with minimum 8+ years

1. Excellent command on ASP.NET, Angular5/6/7/any version, MVC, Sql Server.
2. Should have strong debugging skills on Developer Tools of the browser and Working with Cross Browser UI

4.Working knowledge of the Microsoft Windows Platform and Microsoft Office applications.

1. Detailed technical knowledge of Angular any version, C#.Net (Visual Studio) development tools.
2. Experience with DevExpress components desirable.
3. Experience with DATA along with DevOps and GitHub.
4. ANgularJS is different to Angular. AngularJS experience is not relevant to us