Time since we first saw it
Day 107
Up longer than most. Similar jobs usually come down between day 7 and day 76.
From 6,389 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.
Listed location: RemoteRead the full posting
Open 3 monthsWe first saw this posting 107 days ago and it is still up. Roles open this long are often slow to fill or kept open to collect applications.
These dates show when we found the posting. Check the employer’s website to confirm it is still accepting applications.
Day 107
Up longer than most. Similar jobs usually come down between day 7 and day 76.
From 6,389 similar postings that came down. Coming down is not always a hire.
1 open job
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.
- Not a DevOps role. You need to be fluent in deployment and able to get a service into production, but full-time platform ownership sits elsewhere. Your center of gravity is AI system design. If your GenAI experience is mostly notebooks and proofs of concept that never carried real traffic, this is not the role. What you'll own AI system architecture. Design the systems behind content generation, business intelligence, recommendations, and agentic workflows — including where the boundary sits between what a model decides and what deterministic code decides. Create reusable patterns, prompts, evaluation flows, and orchestration layers that hold up across products rather than being rebuilt per feature. Agentic workflows. Lead the design of agents that reason, call tools and APIs, manage state, checkpoint, and hand tasks off cleanly. Build the guardrails that keep them grounded and predictable — the hard part is not making an agent act, it's making it fail safely and legibly when it's wrong. Retrieval and model strategy. Design RAG pipelines end to end: chunking, embeddings, metadata, reranking, and retrieval evaluation that actually measures whether the right context arrived. Own model selection across ecosystems on the axes that matter — cost, latency, accuracy, reliability — and define the fallback and model-switching behavior for when a provider degrades. Evaluation and quality. Stand up the evaluation frameworks that decide whether an AI output ships: output quality, edit ratio, hallucination rate, schema adherence, latency, failure rate, inference cost. Build regression testing so a prompt or model change can't silently break production. Turn “the output feels off” into a measured threshold. Production readiness. Partner with engineering and platform teams so systems are deployable, observable, and maintainable. Package services (Python, FastAPI/Flask, Docker) when it's the fastest path, and diagnose the production failure modes specific to AI — rate limits, cost spikes, model failures, degraded output — rather than escalating them blind. Technical leadership. Mentor GenAI engineers, review designs and prompts and workflows and evals, and translate product requirements into architecture with measurable acceptance criteria. Communicate the tradeoffs to engineers and to leadership in language each can act on. What we're looking for Required- 5+ years in engineering, AI, ML, or data-product work; 3+ years hands-on with GenAI / LLM systems
- Hands-on with at least one agentic framework (LangGraph, CrewAI, AutoGen, Semantic Kernel, or equivalent) and the underlying concepts — memory, state, tool integration, failure handling — well enough to move across frameworks - Strong Python; comfortable with REST APIs, Docker, a cloud platform, and basic CI/CD - Demonstrated evaluation work: regression testing, hallucination checks, schema validation, output scoring — you can define metrics for quality, reliability, cost, and business impact
- Multimodal work across text, image, audio, or video - Kubernetes or serverless deployment - Evaluation/observability tooling — LangSmith, MLflow, Weights & Biases, or equivalent
- Kubernetes or serverless deployment - Evaluation/observability tooling — LangSmith, MLflow, Weights & Biases, or equivalent - Marketing technology, SMB intelligence, or content-automation domain experience
Complete your application on buzzboard.applytojob.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.
Remote
- Not a role for someone whose GenAI track record is demos that never took production traffic What we offer- Fully remote - A production GenAI foundation already carrying real volume — you scale it, you don't start from zero
More relevant text appears in the full description.
No clear work-authorization passage found. Eligibility is unconfirmed.