Time since we first saw it
Day 20
Up longer than most. Similar jobs usually come down between day 1 and day 15.
From 1,376 similar postings that came down. Coming down is not always a hire.
Work setup in the employer’s posting: TELECOMMUTEFrom the employer’s posting
What You'll Get A brand-new discipline within EPAM where you shape the approach rather than follow an existing playbook Focus on engineering work without 24/7 on-call responsibilities Sponsored certification and training programs (Anthropic/Claude, Databricks, AI & Data Observability learning paths) Exposure to multiple clients and a direct route into presales and solution engineering Responsibilities Add AI telemetry to production LLM, RAG, and agentic applications using OpenTelemetry and APM-native AI monitoring tools Deploy distributed tracing across multi-model chains, agent workflows, and retrieval-augmented generation pipelines to identify systemic latency and failure points Establish and track AI-native SLIs and SLOs, including time to first token (TTFT), throughput, error and refusal rates, cost per request, semantic drift, hallucination boundaries, and contextual accuracy Implement structured semantic logging and prompt/response monitoring to support quality analysis Create and maintain evaluation loops for output quality and safety using golden sets, LLM-as-a-judge methods, and Ragas/DeepEval-style frameworks, integrating them into CI/CD and runtime environments Monitor token-based cloud spend, model API rate limits, and quota usage while driving AI cost optimization efforts Set up AI gateways to manage API load balancing, failover, and fallback models across multiple LLM providers Build guardrails covering prompt injection and jailbreak filtering, output compliance, and bias and safety constraints Develop detection, triage, restoration, and problem management workflows for AI incidents, incorporating autonomous AI agents into root cause analysis to parse logs, generate hypotheses, and correlate state changes Enable rollback, canary, and fail-safe patterns for model, prompt, and configuration releases, while maintaining reproducibility through versioning of data, code, prompts, and models Develop practice accelerators, reference architectures, and internal training materials, and contribute to presales activities and client assessments Requirements 4+ years of experience in SRE, DevOps, platform, or observability engineering, with hands-on exposure to production AI/ML or LLM workloads Strong grasp of SRE fundamentals, including Golden Signals, SLI/SLO definition, error budgets and burn rate, incident lifecycle, and ITIL basics Strong Python skills for building instrumentation, automation, and evaluation tools Hands-on experience with OpenTelemetry and at least one APM/observability platform such as New Relic, Datadog, Grafana LGTM stack, Splunk, or Elastic Production experience with at least one cloud platform (Azure preferred, AWS or GCP also acceptable) and Kubernetes Solid understanding of LLM application architecture, including prompts, embeddings and vector stores, RAG, and agent orchestration tools like LangChain/LangGraph or similar Awareness of MLOps concepts, including model lifecycle (training vs.
inference), model endpoints, containerization, and deployment/rollback patterns Experience with Infrastructure as Code using Terraform, along with CI/CD tools such as Azure DevOps, GitLab CI, or GitHub Actions B2+ English proficiency, since the role involves direct client interaction and requires clear technical communication in both writing and speech Nice to have Familiarity with AI-specific observability and evaluation tools such as Traceloop/OpenLLMetry, Langfuse, Arize Phoenix, Ragas, DeepEval, or MLflow Experience with distributed inference serving at scale, including vLLM, KServe, Ray Serve, Kubernetes-native LLM orchestration, and GPU capacity planning Knowledge of AI security practices, including the OWASP LLM Top 10, prompt injection defense, and guardrail frameworks like NeMo Guardrails or Llama Guard Experience with Databricks (including Mosaic AI/MLflow) or Azure AI Foundry Relevant certifications such as Anthropic Claude, Azure AI Engineer, AWS ML Specialty, or Databricks GenAI Background in FinOps for AI workloads, particularly token and GPU cost modeling Experience in Data Reliability Engineering, covering data quality and pipeline SLOs, since AI reliability depends on data reliability Prior mentoring or team lead experience
These dates show when we found the posting. Check the employer’s website to confirm it is still accepting applications.
Day 20
Up longer than most. Similar jobs usually come down between day 1 and day 15.
From 1,376 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 recordCheck the employer’s posting for the current role and application details.
Already applied? Track this application
Yes. We’ve followed 2 other Senior AI Reliability Engineer jobs there since November 2026. All 2 are still up.
New AI Engineer postings at the employers we follow are up 340% 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 AI Engineer, by the work the posting describes.
AI engineers build products on top of AI models that already exist, most often large language models: they connect a model to a company's data and tools and ship the assistants, agents and search features people use.
Postings ask for strong Python or TypeScript, experience with model APIs, retrieval and agent frameworks, and ways to test whether the model's answers are good enough.
An ML engineer trains and serves models; an AI engineer usually starts from a model someone else trained and builds the product around it, though titles often mix the two.
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.
We couldn’t identify enough role detail in this saved description to support an AI answer. Read the full posting