Cloud Operations Engineer
Job description
About the role
This role manages and monitors Neo4j cloud infrastructure to maximize application and infrastructure uptime. The engineer responds to production incidents and collaborates directly with customers to resolve issues. The role operates within a global Cloud Managed Services workflow.
Software engineers turn product ideas into working code. Engineers work in small teams, review each other's work, and ship in small batches. Most teams follow agile practices such as sprints and daily standups. Engineers also write tests, fix bugs, and improve performance. The field values clear communication as much as technical skill. Engineers spend part of every week on planning, code review, and debugging, not just writing new code. The ability to explain a technical decision in plain words separates strong engineers from the rest.
Key facts
What you'll do
Incident response is handled through on-call rotation, and necessary support is provided for customer cases affecting Neo4j cloud infrastructure availability.
Outside business hours, the team manages the Neo4j database infrastructure, handles escalations, and resolves issues for cloud-hosted environments.
Incidents, procedures, and outcomes of customer communications are documented, and contributions are made to the Cloud Managed Services knowledge base.
Troubleshooting is performed across clusters that span multiple servers, data centers, and regions, and across public clouds such as AWS, Azure, and Google Cloud, as well as virtual and bare metal environments.
Requirements
A minimum of 5 years of cloud infrastructure administration experience is required.
A degree in Computer Science or a Computing Systems equivalent is required; a background in math is advantageous.
Proficiency in Linux environments at command level is required.
Experience with RedHat, CentOS, or Amazon Linux is required.
Experience with at least one of the major cloud providers (AWS, GCP, Azure) is required.
Experience with Ansible, Terraform, and Kubernetes is desirable.
Experience with Nagios and Prometheus is desirable.
Familiarity with Linux and Windows diagnostics and tuning is advantageous.
Neo4j Certified Professional certification is desirable.
Proficiency in Microsoft Office Applications such as Outlook, Word, and Excel is required.
Strong attention to detail, teamwork, verbal communication skills, and performance in a fast-paced, high-energy, multi-tasking environment are required.
Practical notes
The role requires remote work from India with participation in an on-call rotation and occasional off-hours support.
Travel is not mentioned; the position is cloud infrastructure focused across multiple platforms.
Typical interview steps
Hiring for engineering roles usually starts with a recruiter screen, followed by one or two technical rounds. Candidates often solve a coding problem, discuss past projects, and answer system design questions. Some loops include a take-home task. Final rounds typically cover team fit and give candidates a chance to ask questions. Interviewers look for how you break down an unfamiliar problem, not just whether you reach the answer. Practicing a few problems aloud and reviewing your own past projects are the best preparation.
Good to know
Graph databases power relationship-focused data and enable explainable AI.
The role uses graph platforms and cloud infrastructure tools to manage scalable environments.
Automation, monitoring, and diagnostics are central to operations in this field.
Collaboration across engineering and customer-facing teams is common in product-driven technology organizations.
Career growth
Engineering careers usually progress from individual contributor to senior, staff, and principal levels. Some engineers move into management and lead teams of five to twenty people. Others stay on the technical track. Growth follows demonstrated impact, not tenure alone. A typical engineering ladder has clear levels with defined expectations for scope, quality, and mentorship. Moving up usually requires owning outcomes end to end rather than completing assigned tickets.