🎁 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 →
Were a remote, product-focused startup building AI- and algorithm-driven systems, and were looking for a strong Backend Django Engineer who loves clean data models, well-designed APIs, and clever algorithms. Youll own core backend features end-to-end: from modeling the data to implementing the logic and exposing it through fast, reliable services that ship to users quickly, working with a small distributed team across several countries. $100 bonus: After successfully completing a second assessment. To receive the first assessment, please submit your resume to this job application. If your resume is approved, youll receive the assessments afterwards. What Youll Do Design and implement backend services and APIs using Python + Django (and DRF or similar). Model and evolve our domain in the database with clean, well-structured schemas and relationships. Implement algorithmic/AI logic in the backend (e.g., scoring, ranking, routing, decision rules). Write pragmatic, production-ready code thats easy to reason about and iterate on. Optimize for correctness and performance: efficient queries, smart indexing, and lean responses. Work with the team to turn product ideas into concrete technical designs and endpoints. Help shape how we build things: patterns, conventions, and how we ship and iterate as we grow. What Were Looking For Strong experience building backend applications with Python + Django. Solid understanding of relational data modeling and SQL (we use PostgreSQL). Comfortable designing and building RESTful APIs (bonus if youve used DRF or similar frameworks). Experience working on non-trivial business logic or algorithms (e.g., decision flows, scoring rules, optimization logic). Good instincts around performance: understanding query behavior, avoiding obvious pitfalls, and using caching when it counts. A startup mindset: comfortable with ambiguity, moving fast, and iterating based on real-world feedback. Ability to work independently in a remote environment and communicate clearly. Bonus Points For Experience in startups, side projects, or hackathons where youve had to ship scrappy solutions fast. Background in algorithms, optimization, or data-heavy systems. Experience with Google Cloud Platform (GCP) in production. Familiarity with Redis (caching, queues) and PostgreSQL at some scale. Exposure to containers and orchestration (Docker, Kubernetes) and/or serverless on GCP. This role is a central piece of our backend roadmap, and were aiming to fill it quickly once we meet the right person. If it resonates with you, go ahead and apply now. Send us your resume to start the assessment process (and get a chance at the $100 bonus). Apply To this Job Company : Spotter Salary : Full-time .
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.