🎁 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 →
Lead Java Backend Engineer Kafka, Spring Boot, Production Support (70% Support/Development 30% Lead level Activities) Location: Remote (India) Shift: 3:00 PM 12:00 AM IST (Overlap support with PST Client) Will require to provide on-call shared support as needed Engagement: Full time employment with Samay India Availability: Looking for candidates who can join in 30 days or less We're looking for a Senior Backend Java Engineer to serve as an Integration Lead for our squad a technical and squad leader, not just an experienced individual contributor. This role will focus on maintaining and optimizing integrations to Oracle Retail Cloud MFCS, and is suited for someone who prevents incidents before they happen, drives permanent fixes, makes sound escalation calls, and reasons about failure modes across systems, not just within a single application. What You'll Do Lead technical direction and standards for the squad, guiding other engineers on design and implementation decisions Maintain and optimize integrations to Oracle Retail Cloud MFCS Architect and troubleshoot integrations across multiple systems, not just within one service Take ownership during production incidents, leading resolution and driving root cause analysis through to permanent fixes Establish and improve engineering standards, code quality practices, and operational controls across the team Design and build backend services using Java and Spring, with strong database and SQL expertise Bring cloud and DevOps understanding to inform architecture and operational decisions Proactively identify and close gaps in operational hygiene, going beyond incident remediation to implement features and controls that improve software quality over time What You'll Bring Strong expertise in Java, Spring Boot, and Kafka (Expertise in Kafka is a must) Advanced integration architecture experience across distributed systems Strong SQL and database knowledge Solid understanding of cloud platforms and DevOps practices Demonstrated experience leading through production incidents, not just participating in them Ability to reason about cross-system design and troubleshoot issues that span multiple services A track record of driving standards and mentoring engineers, not just accumulating tool knowledge Knowledge of MFCS APIs and integration points is desirable/preferred What Sets This Role Apart We're looking for someone who thinks several steps ahead: someone who can point to concrete examples of preventing incidents rather than just fixing them, and who has implemented real improvements to operational hygiene, whether that's better monitoring, stronger testing practices, or controls that catch problems before they reach production. Please do share me the below information to submit your resume to the client .
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.