🎁 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 →
Own your future: Our culture isn't something people join, it's something they build and shape. We believe that every person deserves to be heard and empowered. If you're on the fence about whether you're a fit, we say go for it. Let’s build something great together. Must Have: Strong commercial experience with Ruby (Rails) and React. Hands-on experience building and maintaining microservice-based systems — not just working inside a single service. Ability to trace how data flows between services: message queues / event streams, third-party integrations, data warehouses. Proactive ownership: looks beyond the assigned ticket, understands the project as a system and how neighboring services fit together. Comfortable in a fast-paced environment — able to context-switch across several tickets and keep progress moving when one is blocked. Able to ask the right questions and surface risks or gaps early rather than waiting for direction. Upper-intermediate+ level of English. Nice to Have: Direct experience with Kafka (or another event-streaming platform: RabbitMQ, SQS/SNS, Pub/Sub). Experience with Snowflake or a comparable analytical data warehouse (BigQuery, Redshift). Experience integrating and debugging external/third-party APIs at scale. Experience with observability tooling for cross-service debugging (distributed tracing, centralized logging). Exposure to service decomposition or migrating a monolith to microservices. Key Responsibilities: Design, build, and maintain full-stack applications, including backend services, APIs, and user-facing web interfaces. Develop backend systems using Ruby on Rails; build responsive user interfaces using JavaScript/TypeScript. Ensure high performance, security, scalability, and maintainability across the entire application stack. Collaborate closely with other developers, designers, and product teams to deliver end-to-end solutions. Provide guidance and advice to other team members. Conduct code reviews and provide guidance to system architecture and technical design across backend and frontend. Continuously improving development processes, system performance, and developer experience across the stack. Maintaining technical communication with the client, particularly with their technical counterparts, and contributing to architecture-related discussions and decisions.
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.