Time since we first saw it
Day 20
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.
Work setup in the employer’s posting: TELECOMMUTEFrom the employer’s posting
These dates show when we found the posting. Check the employer’s website to confirm it is still accepting applications.
Day 20
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.
892 open jobs
Open jobs by the week we first saw them, last 12 weeks.
Hiring recordAdd 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.
We are seeking a Generative AI Engineer to own how the platform's language models are improved — from fine-tuning and evaluation to deployment. You will partner with Back-End engineers who handle the serving infrastructure, and collaborate with Data Analysts and business stakeholders who define what a "good" recommendation actually looks like. Responsibilities Run supervised fine-tuning and parameter-efficient adaptation (LoRA/QLoRA, adapters) and preference-based alignment (DPO, ORPO, RLHF-style methods) to shape tone, output structure, and domain reasoning for retail next-best-action and content-compliance tasks Own the dataset lifecycle — sourcing and curating examples from platform data and expert feedback, designing annotation and review workflows, deduplication, and decontamination against eval sets Generate and filter synthetic data, and version every dataset used in training Reduce cost and latency through distillation into smaller models, quantization, batching and caching strategy, and model routing — while holding quality above an agreed threshold Package and deploy tuned models on Vertex AI (or equivalent), and manage model and prompt versioning Monitor drift and quality decay in production, and define the retraining trigger and rollback path Implement and tune safety, scope, and PII controls appropriate to enterprise commercial data, including refusal behavior and output validation Partner with commercial teams to convert qualitative expectations ("this recommendation reads wrong") into training signal and measurable eval criteria Requirements 5+ years of hands-on experience with Large Language Models (LLM) fine-tuning — SFT and PEFT/LoRA at minimum, ideally preference optimization (DPO or similar) At least 1 year of relevant leadership experience Proficiency in Hugging Face Transformers/PEFT/TRL, Axolotl, or Unsloth, or managed tuning on Vertex AI / Bedrock / OpenAI Understanding of training mechanics, including tokenization, context length and packing, and learning-rate and hyperparameter choices Knowledge of catastrophic forgetting, overfitting on small domain sets, and GPU/TPU memory constraints Expertise in LLM evaluation — designing eval sets and metrics for generative tasks, with healthy skepticism about benchmark scores that don't reflect user outcomes Skills in data curation with strong instinct for dataset quality over quantity — labeling guidelines, inter-annotator agreement, and leakage control Familiarity with synthetic data pitfalls and filtering strategies Background in LLMOps, including model and prompt versioning, drift monitoring, and retraining lifecycle management Competency in Google Cloud Platform (Vertex AI, GCS, Cloud Run) and Git-based workflows Sufficient Python skills to work in notebooks, training scripts, and eval pipelines, and to adapt existing framework code Excellent command of written and spoken English (B2+ level) Nice to have Experience with Reinforcement Learning from Human Feedback (RLHF) and preference-based alignment methods Familiarity with distillation and quantization techniques (GPTQ, AWQ, GGUF, bitsandbytes) and their quality cost Understanding of inference stacks such as vLLM, TGI, and Vertex AI endpoints, including streaming and latency/throughput implications Knowledge of LLM security, including safety guardrails, scope controls, and PII handling for enterprise commercial data
Complete your application on careers.epam.com. The employer’s form will show what is required.
Already applied? Track this application
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.
Location not supplied.
Working pattern and location restrictions need checking in the full posting.
No clear work-authorization passage found. Eligibility is unconfirmed.