🎁 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 role is for one of the Weekday's clients Min Experience: 1 years Location: Chennai, Bangalore, Hyderabad JobType: full-time We are looking for a skilled Backend / Software / Platform Engineer to help build and scale robust, high-performance backend systems for modern products. This role is ideal for engineers who enjoy working close to core infrastructure, distributed systems, and event-driven architectures. You will play a key role in designing reliable services that power mission-critical applications in a fast-moving startup or SaaS environment. Key Responsibilities - Design, build, and maintain scalable backend services using Go or Java, following clean architecture and best engineering practices. - Develop and operate event-driven systems using Kafka, including producers, consumers, and stream-based workflows. - Own the full lifecycle of backend componentsfrom design and development to deployment, monitoring, and optimization. - Collaborate with product managers, architects, and fellow engineers to translate business requirements into reliable backend solutions. - Improve system performance, reliability, and scalability by identifying bottlenecks and implementing efficient solutions. - Write clean, maintainable, and well-tested code with a strong focus on quality and long-term sustainability. - Participate in code reviews and technical discussions to uphold engineering standards and share knowledge across the team. - Contribute to platform stability through observability, logging, and proactive incident resolution. - Support continuous improvement by refining APIs, improving data flows, and strengthening system integrations. What Makes You a Great Fit - 15 years of hands-on experience building backend or platform systems in production environments. - Strong proficiency in Go or Java, with a solid understanding of backend design patterns and concurrency concepts. - Practical experience with Kafka and asynchronous, message-driven architectures. - Positive understanding of distributed systems, microservices, and backend scalability challenges. - Comfort working with databases, APIs, and backend integrations, even in evolving or ambiguous problem spaces. - A strong engineering mindsetcurious, detail-oriented, and driven to build reliable systems rather than quick fixes. - Ability to work effectively in a startup or SaaS setting where ownership, speed, and adaptability matter. - Clear communication skills and a collaborative attitude when working with cross-functional teams. - Passion for backend engineering and platform development, with no reliance on frontend, QA, or ML work to define your impact. .
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.