🎁 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 →
This is the standout listing today for anyone who has been asking for remote backend work. Imply is the company built around Apache Druid, the real time analytics database, and Lumi is its managed product. The role is genuinely low level: building ingestion plugins that get data into Lumi, writing new functions and expressions for querying it, and working on making the query engine itself performant. That is database internals work, which is rare at three years of experience. The bar is modest and clearly stated at at least three years as a backend developer with working knowledge of distributed systems, in Java, Go, C or C++. Past experience with the internals of a database is listed only as bonus points, so this is a way into that specialism rather than a role demanding you already have it. Who it is for: REQUIREMENTS, AS PUBLISHED - At least 3 years of experience working as a backend developer. - Working knowledge of distributed systems. - Experience with one or more of Java, Go, C, C++ or similar. - A bachelor's degree in computer science, engineering or a related field, or equivalent experience. BONUS POINTS - Past experience working on the internals of a database. WHAT THE JOB ACTUALLY IS DAY TO DAY Building scalable and performant ingestion plugins to get data into Lumi. Building new functions and expressions to query that data. Working on making the query engine highly performant. Supporting the team through code and design reviews. Being on call for escalations relating to the ecosystem team. REMOTE AND BENEFITS DETAIL The role is listed as remote with the location given as Bengaluru, and the posting carries an LI-Remote tag. Imply lists an employer matched provident fund contribution, private medical insurance, paid time off, a phone and internet allowance, and home office equipment reimbursement, the last two of which are meaningful signals that remote is genuinely supported rather than tolerated. AN ENCOURAGEMENT THE EMPLOYER PUTS IN WRITING The posting notes that studies show some groups are less likely to apply unless they meet every qualification, and says directly that if you are excited about the role but your experience does not align perfectly with every requirement, you should apply anyway. LOCATION AND WORKING PATTERN Remote, with Bengaluru given as the location. Confirm the exact arrangement in writing during the process. HONEST FIT GUIDANCE Three years for query engine work is an unusually low bar for that depth, and the codebase question is worth raising: Apache Druid is open source, so you can read the project before you apply and arrive with informed questions. On call is part of the role and is stated up front. .
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.