🎁 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 →
Job Title: Python Software Engineer (Cloud & Generative AI) Location: Chennai Job Type: Full-Time Experience Level: Mid-Level (36+ years) About the Role Algorithm Health is seeking a Python Software Engineer with strong cloud backend experience and hands-on exposure to Generative AI technologies. In this role, you will design, build, and deploy production-grade microservices and LLM-powered features. You will bridge traditional Python backend engineering with modern AI workflowsintegrating frontier foundation models, vector databases, and Retrieval-Augmented Generation (RAG) pipelines into cloud environments. Key Responsibilities * Backend Development: Design, write, test, and maintain high-performance, asynchronous RESTful/gRPC APIs and microservices using Python frameworks (FastAPI, Flask, or Django). GenAI & LLM Integration: Implement RAG systems, prompt engineering, and agentic workflows using orchestration frameworks like LangChain, LlamaIndex, or CrewAI.Cloud Architecture: Build, containerize, and deploy Python applications on at least one major cloud platformAWS (e.g., Lambda, ECS, Bedrock, SageMaker), Azure (e.g., Azure OpenAI, App Service, AKS), or GCP (e.g., Vertex AI, Cloud Run, GKE).Data & Vector Stores: Integrate relational/NoSQL databases (PostgreSQL, MongoDB) and vector databases (Pinecone, Qdrant, ChromaDB, or PGVector) for efficient semantic search.MLOps & DevOps: Set up CI/CD pipelines (GitHub Actions, GitLab CI) and monitoring tools (LangSmith, Prometheus) to track API latency, cost efficiency, and model response quality.Code Quality & Best Practices: Write clean, modular, and well-tested code (pytest) with robust error handling and logging. Requirements & Qualifications Must-Have Skills: * 3+ years of professional backend software development using Python. Proven hands-on experience with at least one cloud platform:AWS: Lambda, ECS, S3, Bedrock, or SageMaker ORAzure: Functions, Azure OpenAI Service, App Services ORGCP: Cloud Run, Vertex AI, Cloud Functions.Solid understanding of Generative AI concepts: LLM APIs (OpenAI, Anthropic, Gemini, Llama), RAG architectures, and fine-tuning/prompt design.Experience with Vector Databases (e.g., Pinecone, Weaviate, Qdrant, or Pgvector).Proficiency with Docker and cloud deployment workflows.Strong knowledge of database design, REST API design, and asynchronous Python architecture (asyncio). Nice-to-Have Skills: * Experience with AI agent frameworks (e.g., LangGraph, AutoGen, CrewAI). .
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.