🎁 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 →
Summary of role: The Backend Developer is a delivery-focused specialist responsible for building, extending, and maintaining backend services, APIs, and data integrations within an established cloud-native platform. They work under the technical direction of onshore senior engineers and principals, contributing high-quality backend code at scale. Key responsibilities: Build and maintain backend services and APIs in line with existing architectural patterns and standards. Implement business logic, data access layers, and integrations with internal and external systems. Develop and enhance RESTful APIs, following defined contracts and API standards. Write clean, maintainable, well-tested code, adhering to agreed engineering best practices. Contribute unit and integration tests to ensure functional correctness and regression safety. Support feature delivery by implementing backend components from pre-defined designs and tickets. Participate in code reviews, addressing feedback and continuously improving code quality. Troubleshoot backend issues using logs and diagnostics, escalating complex design concerns to onshore leads. Work within an Agile/Scrum team, contributing to sprint delivery and estimations for assigned work. Follow established security, performance, and reliability guidelines when implementing backend changes. Skills & experience required: Core backend engineering 36+ years of backend development experience. Strong experience with Python or equivalent backend frameworks. Solid understanding of REST API development, request/response models, and error handling. Experience working in microservices-based architectures. Cloud & infrastructure awareness Hands-on experience deploying or running services on GCP or another hyperscaler. Familiarity with managed databases (e.g. Cloud SQL, PostgreSQL). Understanding of containerised workloads (Docker) and serverless/container platforms (e.g. Cloud Run or Kubernetes). Data & integration Strong SQL skills, including schema usage, query optimisation, and data consistency. Experience integrating with external systems via APIs or messaging. Awareness of data validation, idempotency, and failure handling patterns. Quality & delivery Experience writing unit and integration tests for backend services. Familiarity with CI/CD pipelines and version control (Git-based workflows). Comfortable working from clear requirements, tickets, and technical guidance provided by onshore leads. Ways of working Experience working as part of a distributed or offshore delivery team. Able to communicate progress, blockers, and risks clearly to onshore counterparts. Willingness to follow established standards rather than redefine architecture. .
Here's where they are and how to stand out in your next interview.
24.795Jobs
9.577IN
74%EN
That number includes positions in India (9,577), Poland (3,429), the United States (1,753), Singapore (787), and Brazil (779). If you're looking to move or work remotely, check which countries match your goals — then filter WorkMundi by location to see what's actually hiring near you.
Most developer ads you'll see are written in English: 18,397 of the 24,795. That doesn't tell you whether the job itself requires you to speak English or work in English daily, so read each posting carefully. Don't assume the language of the ad matches the language of the team.
The employers posting the most developer roles are Link Group (369 jobs), Upvanta (257), jobgether (226), and OfferZen (212). If you're applying to any of these, research their hiring patterns. They move fast and post often, which means they're either scaling hard or replacing people who didn't fit.
In your interview, expect this: 'Walk me through the last time you had to debug something that took you more than an hour. What was it, what did you try first, and what would you do differently?' Hiring managers ask this to see if you think systematically or just try random fixes. Have a real example ready with specifics.