🎁 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 →
ABOUT DAWERONE DawerOne is an AI-native venture office and consulting practice that helps growing companies build, modernize, and scale technology products without unnecessary process or complexity. ROLE OVERVIEW This is a contract position to start, with the opportunity to increase scope over the first few months and transition to a full-time position if it is a strong fit for both sides. We are seeking a Senior Backend Engineer to work on a client product, building and maintaining its backend with a strong focus on Python, AWS Lambda, APIs, and integrations with external AI services. You will be responsible for building production backend services, integrating third-party AI APIs, handling failures and edge cases, and ensuring the system is reliable, observable, and cost-effective. KEY RESPONSIBILITIES BACKEND DEVELOPMENT Build and maintain production backend services using Python. Develop and maintain APIs that support the applications core functionality. Build and maintain AWS Lambda services and supporting AWS infrastructure. Design clean, maintainable backend components and integrations. Implement business logic, data processing, and service-to-service communication. Debug and resolve backend issues across development and production environments. Improve backend performance, reliability, and maintainability as the product evolves. AI AND THIRD-PARTY INTEGRATION Integrate external AI services for transcription, language models, and scoring. Build reliable API clients and service integrations rather than tightly coupling vendor-specific logic throughout the application. Handle API authentication, request/response validation, timeouts, retries, rate limits, and failures. Account for unexpected or malformed responses from external providers. Design appropriate fallback and failure-handling behavior when an external service is unavailable. Monitor AI API usage and help control token consumption and vendor costs. Keep integrations maintainable as external vendors change their APIs and capabilities. Understand the practical differences between deterministic application logic and nondeterministic AI-powered services. INFRASTRUCTURE AND ENVIRONMENTS Stand up a staging environment and a real deployment pipeline where none exists. Establish IAM fundamentals: named users, least privilege, no root usage. Build environment configuration and secret management that holds up across development, staging, and production. RELIABILITY & OBSERVABILITY Build backend services that remain stable when external dependencies are slow or unavailable. Implement appropriate timeouts, retries, error handling, and graceful failure behavior. Add useful logging, metrics, and monitoring to backend services and AI integrations. Investigate production failures and identify whether the root cause is in our application, infrastructure, authentication, test data, or an external dependency. Identify reliability issues before they become recurring production problems. Balance reliability and engineering effort without over-engineering a relatively straightforward system. TESTING & ENGINEERING QUALITY Write automated unit, integration, and API tests for backend functionality. Test both successful and failure scenarios, particularly around external service integrations. Validate API responses, error conditions, authentication, data handling, and business logic. Build reusable test utilities and fixtures where appropriate. Use automated testing as part of normal backend development rather than treating testing as a separate QA function. Integrate tests into the development and CI/CD workflow. Use AI coding tools responsibly to accelerate development, debugging, documentation, and test creation while reviewing generated code before it reaches production. API & INTEGRATION ENGINEERING Design and maintain REST APIs and service interfaces. Work with third-party APIs and SDKs. Handle authentication mechanisms such as API keys, OAuth, and service credentials where required. Validate external inputs and protect the application from unexpected or invalid data. Design integrations that are observable and easy to troubleshoot. Ensure data is passed correctly between backend services and external platforms. DELIVERY AND COLLABORATION Read an undocumented system and reconstruct what it is actually doing, as the first real task on it. Work alongside a dedicated QA engineer to define what a safe release requires on the backend. Report plainly on what is fragile, what is fixed, and what a proposed change will cost to build. REQUIRED QUALIFICATIONS 5+ years of professional backend software engineering experience. Strong experience building production applications with Python. Hands-on experience with AWS Lambda and serverless backend development. Strong experience designing and .
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.