🎁 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 →
Role Overview At Qashio, we're transforming how businesses manage company spending. We are looking for an AI engineer who turns cutting-edge AI into software people can rely on. You care about quality, safety and doing things properly, and you are happiest owning a hard problem from first design to something running in production. Responsibilities • Own the technical architecture of our AI / LLM systems end to end - from framework and tooling choices through to deployment. • Build reusable platform components: a model gateway, permission-aware RAG, agent orchestration, secure tools/MCP connectors and internal-system integrations. • Translate security and compliance policy into technical controls for SSO/RBAC, data classification and isolation, PII, secrets, approvals and audit. • Establish evaluation, observability and release gates covering answer and retrieval quality, safety, cost, latency, reliability and drift. • Partner with product and business teams to turn priority problems into shipped, dependable solutions, with the right human oversight. • Keep the architecture modular and vendor-neutral, so we are never locked to a single framework or model provider. Qualifications and Experience • 5+ years software engineering, with strong Python and production backend/API experience and ownership of 0-to-1 systems. • Hands-on production experience with LangChain/LangGraph, OpenAI Agents SDK, Microsoft Agent Framework/Semantic Kernel or comparable agent SDKs, including durable workflows, structured outputs, tool calling and HITL. • Experience building permission-aware RAG and ingestion pipelines with LlamaIndex, Haystack or LangChain and vector stores such as pgvector, Pinecone or Qdrant, including source ACLs and data isolation. • Strong cloud-native engineering fundamentals, plus evaluation and tracing with LangSmith, Arize Phoenix, DeepEval, Ragas or equivalent, including CI/CD release gates and incident readiness. • Hands-on experience implementing guardrails with NVIDIA NeMo Guardrails, Guardrails AI, OpenAI Guardrails or equivalent, covering prompt injection, PII/data leakage, output validation and unsafe tool use. • Experience implementing fine-grained permissions and secure tools/connectors with OPA, OpenFGA, Cedar or equivalent, plus MCP, OAuth/service authentication, least-privilege scopes and approval gates. • Clear communicator who turns ambiguous problems into scoped milestones, architecture decisions, runbooks and shipped, reliable software. Nice-to-have • Experience handling sensitive data in fintech, banking or another regulated environment (GDPR, data residency, SOC 2 and/or PCI). • Experience with model gateways, multi-provider routing, LLM cost controls and tracing/evaluation platforms. • Working knowledge of TypeScript/React, internal developer platforms or multi-tenant SaaS.
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.