🎁 Before you apply, rehearse this interview. Create your free WorkMundi account and get an Interview Training on HelpsYouSpeak — no cost, no card. I want my training →
About the Role We are looking for an engineer who enjoys understanding how systems behave in real production, not just writing features. This role is responsible for maintaining reliability, stability, and smooth functioning of our live platform running on Google Cloud. You will act as the first technical owner of production systems monitoring services, investigating alerts, resolving issues, and performing controlled configuration and operational changes. This role works closely with backend developers, QA, and infrastructure teams to prevent incidents and reduce downtime. This is not a call-center support role and not a pure development role it is a hands-on technical position focused on debugging, incident handling, and system operations. Tech Stack - Google Cloud Platform (Compute, Logging, Monitoring) - Java (Spring Boot based microservices) - MongoDB - Apache Kafka (event-driven architecture) - Redis cache - Linux servers Key Responsibilities Production Monitoring & Alert Handling - Monitor application health, latency, errors, consumer lag, database connections, and resource utilization - Acknowledge and investigate monitoring alerts - Perform first-level troubleshooting and stabilize services - Identify whether issue is infra, application, database, or messaging related Incident Response - Participate in on-call rotation - Diagnose production incidents and restore services with minimal downtime - Safely restart services, scale instances, or rollback deployments when required - Communicate incident status to stakeholders Technical Support & Operational Changes - Handle technical support tickets requiring engineering understanding - Update configurations and feature flags - Manage scheduled jobs / cron triggers - Trigger or replay events in Kafka - Assist in minor Java configuration/code fixes when needed - Coordinate production releases Database & Messaging Operations - Investigate MongoDB performance issues and slow queries - Monitor and resolve Kafka consumer lag and stuck messages - Manage Redis cache behavior (TTL, eviction, connection issues) Logs & RCA - Analyze logs and metrics to determine root cause of issues - Prepare basic Root Cause Analysis (RCA) reports - Suggest preventive actions to reduce recurring incidents Required Skills Core Technical Skills - Good understanding of Linux commands and server behavior - Experience analyzing application logs and debugging runtime issues - Basic Java knowledge (stack trace reading, configuration changes, rebuild & deploy) - Practical experience with MongoDB (indexes, connections, slow queries) - Understanding of Kafka concepts (consumer, offset, lag, partitions) - Basic Redis knowledge (caching behavior, TTL) Cloud & Tools - Hands-on experience with any cloud platform (GCP preferred / AWS acceptable) - Experience using monitoring tools (GCP Monitoring, Prometheus, Grafana, ELK, or similar) - Understanding of REST APIs and HTTP status codes What We Expect From You - Ability to investigate problems logically rather than randomly restarting services - Comfort working with live production systems - Willingness to participate in on-call support - Strong ownership mindset and attention to detail - Good communication during incidents Good to Have - Experience in e-commerce, fintech, logistics, or high-traffic systems - Exposure to CI/CD pipelines and deployments - Basic scripting (Shell or Python) - Experience writing RCA documents Experience 3 6 years of relevant experience in production support, application support, SRE, DevOps operations, or similar roles. Why Join Us - Direct exposure to real distributed systems - Hands-on production debugging experience - Chance to learn system architecture deeply - Close interaction with development and platform teams Important Note This role involves handling live production systems and occasional on-call responsibilities. Candidates interested only in feature development or pure infrastructure automation may not find this role suitable. .
Here's how to pick the right one and stand out in your application.
144.883Jobs
31.687IN
81%EN
That number is real. WorkMundi's database shows 144,883 open engineer roles across the world. India has the most with 31,687 jobs, followed by the United States with 30,084. If you just finished reading one job ad and felt paralyzed by choice, you're not alone—but this scale is actually an advantage. It means you can afford to be selective.
Start by geography and language. The majority of engineer ads—117,837 of them—have the job posting text written in English. Use that as one filter, but remember: the ad text language tells you nothing about whether the role actually requires you to speak English day-to-day. Read the job description carefully. Then check which countries have the volume you're targeting. Singapore, Poland, and Australia round out the top five after India and the US.
Next, learn who's hiring. Accenture has posted 2,801 engineer roles. andurilindustries, speechify, and jobgether are also actively recruiting. If you're applying to one of these names, research their hiring patterns and interview style before you apply. That homework pays off.
When you interview, expect the question every engineer hears: 'Tell me about a time you had to debug a problem that wasn't in your job description.' Have a specific story ready—not a general one. Name the tools, the deadline pressure, and what you learned. Hiring managers listen for whether you see problem-solving as part of the role itself, not a favour.