🎁 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 →
Job Description What You're Walking Into The backend is a distributed microservice architecture with 15+ independent services, each owning its own database and deployment lifecycle, communicating via Redis Pub/Sub. The platform handles high-concurrency event scenarios where large audiences arrive in short windows. Real-time systems, messaging, presence, socket connections, live session state, these are at the core of what we run. The architecture is already built. The algorithms are already designed. Your job is to understand them deeply and move fast inside them. Some of what you'll be working in: Hybrid message persistence systems that layer Redis and MongoDB with deliberate handoff logic, designed for speed at scale and correctness under pressure Socket infrastructure that manages live connections across sessions with large concurrent user counts A tagging-based permission system that governs access across the entire platform Streaming pipelines, event-driven data propagation, and time-series instrumentation GCP infrastructure running on Kubernetes with independent service scaling When we go live for a major event, all services are running simultaneously. If something breaks, you need to identify which service, triage fast, and push a patch while the event is live. That's the job. What We're Looking For We are not hiring for coding speed. We are hiring for architectural fluency: the ability to look at a system design you didn't write, understand it completely, and work inside it at full confidence. You're the right person if: You can read an existing architecture, its data flow, its edge cases, its failure modes, and within a short period, own it You've worked on systems where real-time correctness mattered: messaging, presence, live state, concurrent writes You think in terms of service boundaries, failure isolation, and propagation and not just functions and endpoints You're decisive under pressure and comfortable making judgment calls when it's live and something is wrong You've operated in or adjacent to a high-availability production environment and you know what that actually feels like Technically, you should be solid in: Node.js at the backend, services, APIs, async patterns Redis beyond caching: Pub/Sub, data structures, in-memory state patterns MongoDB: schema design, querying, write patterns under load WebSockets and real-time connection management Kubernetes and containerized deployment on GCP or equivalent cloud Microservice architecture: service design, inter-service communication, independent deployability React on the frontend, you should be comfortable there when needed Required Skills ['Python', 'Javascript', 'MongoDB', 'Kubernetes', 'Nodejs'] Additional Information NA .
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.