Time since we first saw it
Day 18
Similar jobs usually come down between day 7 and day 76.
From 6,398 similar postings that came down. Coming down is not always a hire.
Reads like an ML Engineer role: training models and running them in production.
Bengaluru, Karnataka, India
Live, first seen by us 18 days agoOwn end-to-end deployment of AI applications on Azure — from classical ML models and Azure OpenAI Service integrations through to production release, monitoring, and iteration.
Design and implement guardrails — content filtering, prompt injection defence, PII redaction, output validation, and human-in-the-loop checkpoints for high-risk actions.
Manage the model lifecycle — model selection and routing (classical ML vs.
What You'll Do Own end-to-end deployment of AI applications on Azure — from classical ML models and Azure OpenAI Service integrations through to production release, monitoring, and iteration. Build and evaluate core ML models where GenAI isn't the right tool — classification, regression, forecasting, clustering, or recommendation problems using traditional ML techniques.
Build and evaluate core ML models where GenAI isn't the right tool — classification, regression, forecasting, clustering, or recommendation problems using traditional ML techniques. Design and implement guardrails — content filtering, prompt injection defence, PII redaction, output validation, and human-in-the-loop checkpoints for high-risk actions. Build and maintain MLOps/LLMOps pipelines — CI/CD for models and prompts, feature engineering and data pipelines, automated evaluation harnesses, versioning for models/prompts/embeddings/fine-tunes, and rollback mechanisms.
Build and maintain MLOps/LLMOps pipelines — CI/CD for models and prompts, feature engineering and data pipelines, automated evaluation harnesses, versioning for models/prompts/embeddings/fine-tunes, and rollback mechanisms. Manage the model lifecycle — model selection and routing (classical ML vs. smaller LLMs vs. frontier models by task complexity and cost), performance benchmarking, cost-per-call/cost-per-inference tracking, and deprecation/upgrade planning. Implement observability — logging, tracing, and alerting for LLM applications (token usage, latency, hallucination/error rates, user feedback loops).
Hands-on experience with standard ML libraries (scikit-learn, XGBoost / LightGBM, pandas, NumPy) and at least one deep learning framework (PyTorch or TensorFlow).
Experience with voice-based or multimodal AI applications.
Practical experience with MLOps/LLMOps tooling — CI/CD pipelines, containerization (Docker), model/prompt versioning, experiment tracking, and automated testing/evaluation frameworks.
Familiarity with enterprise AI governance frameworks and responsible AI principles.
Demonstrated experience building guardrails and safety layers in production — not just theoretical familiarity (e.g., Azure AI Content Safety, custom validation layers, jailbreak/prompt-injection mitigation).
Prior experience in AEC, GCC, or large enterprise delivery environments.
These dates show when we found the posting. Check the employer’s website to confirm it is still accepting applications.
Day 18
Similar jobs usually come down between day 7 and day 76.
From 6,398 similar postings that came down. Coming down is not always a hire.
20 open jobs
Open jobs by the week we first saw them, last 12 weeks.
Add your resume and we’ll mark which of these tools you already use, and point out anything in the posting that could rule you out.
- Demonstrated experience building guardrails and safety layers in production — not just theoretical familiarity (e.g., Azure AI Content Safety, custom validation layers, jailbreak/prompt-injection mitigation). - Solid Python engineering skills — clean, testable, production-grade code, not notebook scripts. - Experience with at least one orchestration framework: LangGraph, Semantic Kernel, LangChain, or similar.
We're looking for a Sr AI Engineer who has shipped AI products, not just prototyped them, with equal footing in core ML and modern GenAI. This role sits at the intersection of engineering rigor and product ownership, you'll build, deploy, and operate ML and LLM-powered applications on Azure, with real accountability for what happens after go-live: accuracy, cost, latency, safety, drift, and uptime. If you've only worked in notebooks or built demos that never saw production traffic, this isn't the role. If you've had to explain to a stakeholder why a model started hallucinating in week three or had to design a rollback plan for a prompt change, we want to talk to you.
What You'll Do - Own end-to-end deployment of AI applications on Azure — from classical ML models and Azure OpenAI Service integrations through to production release, monitoring, and iteration. - Build and evaluate core ML models where GenAI isn't the right tool — classification, regression, forecasting, clustering, or recommendation problems using traditional ML techniques.
- Hands-on experience with standard ML libraries (scikit-learn, XGBoost / LightGBM, pandas, NumPy) and at least one deep learning framework (PyTorch or TensorFlow). - Strong working knowledge of the Azure AI/ML stack: Azure Machine Learning, Azure OpenAI Service, Azure AI Foundry, Azure AI Search, and Azure App Service/Functions for deployment. - Practical experience with MLOps/LLMOps tooling — CI/CD pipelines, containerization (Docker), model/prompt versioning, experiment tracking, and automated testing/evaluation frameworks.
- Practical experience with MLOps/LLMOps tooling — CI/CD pipelines, containerization (Docker), model/prompt versioning, experiment tracking, and automated testing/evaluation frameworks. - Demonstrated experience building guardrails and safety layers in production — not just theoretical familiarity (e.g., Azure AI Content Safety, custom validation layers, jailbreak/prompt-injection mitigation). - Solid Python engineering skills — clean, testable, production-grade code, not notebook scripts.
- Strong working knowledge of the Azure AI/ML stack: Azure Machine Learning, Azure OpenAI Service, Azure AI Foundry, Azure AI Search, and Azure App Service/Functions for deployment. - Practical experience with MLOps/LLMOps tooling — CI/CD pipelines, containerization (Docker), model/prompt versioning, experiment tracking, and automated testing/evaluation frameworks. - Demonstrated experience building guardrails and safety layers in production — not just theoretical familiarity (e.g., Azure AI Content Safety, custom validation layers, jailbreak/prompt-injection mitigation).
- Solid grounding in core AI/ML fundamentals — supervised/unsupervised learning, model evaluation metrics, feature engineering, handling class imbalance/overfitting, and knowing when a classical ML model beats an LLM for the job. - Hands-on experience with standard ML libraries (scikit-learn, XGBoost / LightGBM, pandas, NumPy) and at least one deep learning framework (PyTorch or TensorFlow). - Strong working knowledge of the Azure AI/ML stack: Azure Machine Learning, Azure OpenAI Service, Azure AI Foundry, Azure AI Search, and Azure App Service/Functions for deployment.
Complete your application on emit.fa.ca3.oraclecloud.com. The employer’s form will show what is required.
Already applied? Track this application
We're looking for a Sr AI Engineer who has shipped AI products, not just prototyped them, with equal footing in core ML and modern GenAI. This role sits at the intersection of engineering rigor and product ownership, you'll build, deploy, and operate ML and LLM-powered applications on Azure, with real accountability for what happens after go-live: accuracy, cost, latency, safety, drift, and uptime.
If you've only worked in notebooks or built demos that never saw production traffic, this isn't the role. If you've had to explain to a stakeholder why a model started hallucinating in week three or had to design a rollback plan for a prompt change, we want to talk to you.
What You'll Do
What You Bring
Must-Have
Good to Have
What Sets Strong Candidates Apart
We're specifically screening for deployment maturity across both classical ML and GenAI, over research depth alone. In interviews, be ready to talk through:
BGV:
Employment with WSP India is subject to the successful completion of a background verification (“BGV”) check conducted by a third-party agency appointed by WSP India.
Candidates are advised to ensure that all information provided during the recruitment process — including documents uploaded — is accurate and complete, both to WSP India and its BGV partner”.
New ML Engineer postings at the employers we follow are down 4% over the last 6 weeks compared with the 6 before.
Each bar is one week of new postings. The darkest bars are the last 6 weeks.
Counted from the hiring pages we’ve followed for at least five weeks, so employers we add don’t look like growth. Updated weekly.
We file this job under ML Engineer, by the work the posting describes.
ML engineers put machine learning models into products. They write the code that trains, ships, serves and monitors models so a recommendation or prediction works for real users.
Postings ask for strong Python and software engineering, a framework such as PyTorch, cloud services, and more and more often experience with large language models.
A data scientist often works out which model to build; an ML engineer makes it run reliably in production.
The government has no code for ML engineers, so these figures are for the closest group, computer and information research scientists.
Source: US Bureau of Labor Statistics, Occupational Employment and Wage Statistics (May 2025) and Employment Projections (2025 to 2035). Occupation code 15-1221.
Selected passages from the saved posting. Check the full description for conditions and exceptions.
No pay amount identified in the saved description.
Bengaluru, Karnataka, India
Working pattern and location restrictions need checking in the full posting.
No clear work-authorization passage found. Eligibility is unconfirmed.