Back to jobs

Senior Machine Learning Engineer

Pay
$150,000–300,000 · BasePay period needs review. Location-specific pay — pay source
Pay and Benefits The annual US base salary range for this role, and other engineering roles, is $150,000 – $300,000. This salary range is broad in order to accommodate a wide range of candidates; the interview process will narrow it down based on a number of factors, including your experience, qualifications, and location. We offer equity compensation and top-tier medical, dental, and vision benefits.
Read the full posting
Work setting
Not stated
Employment
Full-time — employment source
Employment type in the employer’s posting: FULL_TIME
From the employer’s posting

What you’ll work on

Full posting
  • Design, train, evaluate and ship the models behind the revenue-optimization product

  • Own the full model lifecycle from feature definition to production deployment and online evaluation

  • Work with Product and publishers to decide what to optimize and sequence the roadmap

  • Set ML direction and raise the bar for the ML effort, mentoring future hires

From the employer’s posting
design, train, evaluate, and ship the models that power the revenue-optimization product
You'll own the full lifecycle, from feature definition through production deployment and online evaluation
You'll work directly with Product and with publishers to understand what's actually worth optimizing for and sequence the roadmap accordingly
you'll be the person setting direction, raising the bar, and — as the function grows — helping us hire and mentor additional ML engineers

What you’ll bring

All qualifications

Core experience

  • Hands-on experience training and deploying traditional ML models
  • Has shipped ML into a production request path under a latency SLO
  • Has owned offline-to-online feature parity and training/serving consistency
  • Has run experiments measuring real revenue impact
  • Willing to read and contribute to Golang production serving code
Qualification wording
We’re looking for someone with hands-on experience actually training and deploying traditional machine-learning models
You've shipped ML into a production request path.
You've owned the offline-to-online feature parity problem.
You've run real experiments measuring real revenue impact.
you should be willing to learn enough to read production serving code

About CloudX

At CloudX we’re building a new supply-side advertising platform for mobile publishers.

In the employer’s words · Read in context

Apply at CloudX

Posting record

Report an error

Open 5 monthsWe first saw this posting 173 days ago and it is still up. Roles open this long are often slow to fill or kept open to collect applications.

Status in our records
Live
First seen by us
Jun 2, 2026173 days ago
Recorded sightings
80
Last seen by us
Nov 21, 2026

These dates show when we found the posting. Check the employer’s website to confirm it is still accepting applications.

How this job compares

Time since we first saw it

Day 173

Up longer than most. 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.

See how this role fits your experience

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.

  • Go
  • Python
  • AWS
  • ClickHouse
  • Datadog
  • Kubernetes
  • LightGBM
  • XGBoost
Where the posting names them
- You've run real experiments measuring real revenue impact. You understand the difference between "the model log-likelihood improved" and "the business made more money," and you can describe a time those disagreed and what you did about it. - You can get comfortable outside Python. You tell us what you need for the models, but the rest of our services are mostly Golang. You don't need to be a Go engineer, but you should be willing to learn enough to read production serving code, flag where it diverges from training, and contribute fixes when it does. - Hands-on expertise: in case we weren’t clear enough already, this is a hands-on position. You may have managed or led ML teams at points in your career, but you still code regularly and are interested in continuing to do so. You've owned large projects end-to-end and know how to work well with others.
- Auction and bidding model experience: hands-on experience with contextual bandits, reinforcement learning, Thompson sampling, or other approaches that fit the explore/exploit structure of auction pricing. Familiarity with the RTB literature or systems like Meta's Pearl is a strong positive. - Stack experience: we're running in AWS, our inference is ONNX-based, we currently train with XGBoost (and are evaluating LightGBM), we use ClickHouse for analytics, Kubernetes for training orchestration, and Datadog for observability. All of this is v0; we'd be happy to speak with you if you have strong opinions about the right tools for the job. In general, we’re looking for people with grit, passion, and talent. If you’re not sure if this role is an exact fit, we encourage you to apply. Many members of our team have had interesting career paths and we relish the chance to work with extraordinary individuals.
You will be our first dedicated ML hire and you will be directly responsible for delivering this vision. We’re looking for someone with hands-on experience actually training and deploying traditional machine-learning models. Think: Thompson sampling, generalized policy learning, LightGBM. Your key responsibilities will be: - Machine Learning Engineering: design, train, evaluate, and ship the models that power the revenue-optimization product. You'll own the full lifecycle, from feature definition through production deployment and online evaluation. You'll make the architectural calls — what models, what training framework, what serving approach — and you'll write the code to make them real.

Your next step

Complete your application on jobs.gem.com. The employer’s form will show what is required.

Already applied? Track this application

Job description

View original posting ↗

Senior Machine Learning Engineer

About CloudX


At CloudX we’re building a new supply-side advertising platform for mobile publishers. We’re convinced that an AI-native product will significantly advance the state of the art in mobile advertising; we recently raised a $30M Series A in order to bring this dream to life. We have a long history of innovation in this space — our founding team previously built MoPub (sold to Twitter for $350M) and MAX (acquired by AppLovin). Our new platform combines real technical improvements like verifiably fair auctions with a truly AI-native product experience to give publishers unprecedented control over their ad monetization strategy.


About The Team


Our Engineering team is distributed and remote — spanning UTC-8 to UTC+6, with core working hours of roughly the US Eastern business day. We have a strong ownership culture and are heavily collaborative, relying primarily on asynchronous, written, communication for coordination. We ship daily and believe that fast CI and good test coverage is the best way to remain productive as we scale. We’re small and high trust; we optimize for rapid iteration and experimentation. Everyone has access to the latest AI tools, but rather than generating vibe-slop we use them pragmatically to build better products. We are lucky to work closely with our talented Product and Business teams to make sure we’re building the right things. It’s a true early-stage startup with lots of important work to go around.

What you'll do


We are looking for a Senior Machine Learning Engineer to own one of the most important product bets we're making: replacing the narrow set of manual knobs our publishers use to drive revenue — per-line-item floors, bidder targeting, waterfall ordering — with ML-driven systems that optimize life-time customer value automatically. Our long-term vision is for CloudX to be the simplest ad monetization platform; customers express their basic constraints and desired ad setups, and our machine learning algorithms and agents work together to make suggestions and work within those constraints in order to maximize LTV.

You will be our first dedicated ML hire and you will be directly responsible for delivering this vision.

We’re looking for someone with hands-on experience actually training and deploying traditional machine-learning models. Think: Thompson sampling, generalized policy learning, LightGBM. Your key responsibilities will be:

  • Machine Learning Engineering: design, train, evaluate, and ship the models that power the revenue-optimization product. You'll own the full lifecycle, from feature definition through production deployment and online evaluation. You'll make the architectural calls — what models, what training framework, what serving approach — and you'll write the code to make them real.
  • Product Ownership: the "make me more money" button is a multi-year product surface, starting with floor pricing, extending into waterfall and bidder-order optimization, and eventually joint optimization across the full set of publisher controls. You'll work directly with Product and with publishers to understand what's actually worth optimizing for and sequence the roadmap accordingly.
  • Technical Leadership: lead by example to build out the ML discipline at CloudX. Today, several engineers across backend and infra contribute to the ML effort as part of their broader work; you'll be the person setting direction, raising the bar, and — as the function grows — helping us hire and mentor additional ML engineers.

Who you are


We're looking for someone who has done this before. The skill we are hiring for is specifically the ability to take an ML system from "theoretically promising" to "demonstrably moving real revenue in production", and we'd like to see concrete evidence of that in your past work. We encourage you to apply if you meet these requirements:

  • You've shipped ML into a production request path. Not a batch job, not a notebook, not a dashboard. A model serving real traffic under a latency SLO, where getting it wrong costs money. You can talk about a specific system you built, the lift you measured, and how you measured it.
  • You've owned the offline-to-online feature parity problem. You've seen training/serving skew, you've written (or reviewed) the featurizer that runs in both places, and you have a view on how to keep them consistent as the system evolves.
  • You've run real experiments measuring real revenue impact. You understand the difference between "the model log-likelihood improved" and "the business made more money," and you can describe a time those disagreed and what you did about it.
  • You can get comfortable outside Python. You tell us what you need for the models, but the rest of our services are mostly Golang. You don't need to be a Go engineer, but you should be willing to learn enough to read production serving code, flag where it diverges from training, and contribute fixes when it does.
  • Hands-on expertise: in case we weren’t clear enough already, this is a hands-on position. You may have managed or led ML teams at points in your career, but you still code regularly and are interested in continuing to do so. You've owned large projects end-to-end and know how to work well with others.
  • Strong written communication skills: you are used to writing about, speaking about, and generally communicating complex technical subject matter both to other engineers and to non-engineers.
  • Early-stage mentality: you understand that success at a startup involves grit and determination. You have good taste when it comes to trading off speed vs. perfection. You know when to cut corners but aren't afraid to advocate for rigor when you believe it's necessary.
  • AI forward: you are actively experimenting with or using AI as part of your software engineering practice. You don't send vibe-coded slop to your teammates to review, but you use AI appropriately to achieve great results.
  • High ownership: you care a lot about your work and when you ship a product, you make sure it continues to solve problems for the customer. You care a lot about the customer, the overall business, and are constantly trying to help achieve success — with or without code.


While not strictly required, we're particularly interested in candidates with:

  • Adtech experience: you've worked in adtech — SSP, DSP, ad exchange, RTB — and have a good understanding of the broader ecosystem and market. Equivalent experience from other low-latency, revenue-objective ML domains (search ranking, recsys, marketplace pricing for rides/delivery/lodging, or quant execution) is a real substitute and we'll treat it as such.
  • Auction and bidding model experience: hands-on experience with contextual bandits, reinforcement learning, Thompson sampling, or other approaches that fit the explore/exploit structure of auction pricing. Familiarity with the RTB literature or systems like Meta's Pearl is a strong positive.
  • Stack experience: we're running in AWS, our inference is ONNX-based, we currently train with XGBoost (and are evaluating LightGBM), we use ClickHouse for analytics, Kubernetes for training orchestration, and Datadog for observability. All of this is v0; we'd be happy to speak with you if you have strong opinions about the right tools for the job.

In general, we’re looking for people with grit, passion, and talent. If you’re not sure if this role is an exact fit, we encourage you to apply. Many members of our team have had interesting career paths and we relish the chance to work with extraordinary individuals.

Pay and Benefits


The annual US base salary range for this role, and other engineering roles, is $150,000 – $300,000. This salary range is broad in order to accommodate a wide range of candidates; the interview process will narrow it down based on a number of factors, including your experience, qualifications, and location.

We offer equity compensation and top-tier medical, dental, and vision benefits.

We also have a generous hardware budget for a computer, monitor, and other core equipment necessary to work effectively on a remote team.

We care about the quality of your work more than the specific hours you spend getting it done, and try to minimize the number of synchronous meetings in favor of greater flexibility. There is no in-office requirement.

Demand for ML Engineer roles

New ML Engineer postings at the employers we follow are down 4% over the last 6 weeks compared with the 6 before.

Weekly new ML Engineer postings at the same employers, from the week of August 17 to the week of November 9. The fewest in a week was 508, the most 899, and the latest week had 508.
August 17Last week

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.

About the role

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.

US government figures for computer and information research scientists

Median yearly pay, May 2025
$140,300
Expected change, 2025 to 2035
21.8% more jobsagainst 3.5% for all jobs

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.

Source details

View original posting ↗

Source notes

Source excerpts

Selected passages from the saved posting. Check the full description for conditions and exceptions.

Pay
Pay and Benefits The annual US base salary range for this role, and other engineering roles, is $150,000 – $300,000. This salary range is broad in order to accommodate a wide range of candidates; the interview process will narrow it down based on a number of factors, including your experience, qualifications, and location. We offer equity compensation and top-tier medical, dental, and vision benefits.
Location & working pattern

Global

About The Team Our Engineering team is distributed and remote — spanning UTC-8 to UTC+6, with core working hours of roughly the US Eastern business day. We have a strong ownership culture and are heavily collaborative, relying primarily on asynchronous, written, communication for coordination. We ship daily and believe that fast CI and good test coverage is the best way to remain productive as we scale. We’re small and high trust; we optimize for rapid iteration and experimentation. Everyone has access to the latest AI tools, but rather than generating vibe-slop we use them pragmatically to build better products. We are lucky to work closely with our talented Product and Business teams to make sure we’re building the right things. It’s a true early-stage startup with lots of important work to go around. What you'll do
More source context
We offer equity compensation and top-tier medical, dental, and vision benefits. We also have a generous hardware budget for a computer, monitor, and other core equipment necessary to work effectively on a remote team. We care about the quality of your work more than the specific hours you spend getting it done, and try to minimize the number of synchronous meetings in favor of greater flexibility. There is no in-office requirement.
Work authorization

No clear work-authorization passage found. Eligibility is unconfirmed.

Find answers in the posting

AI
How answers work

AI selects complete passages from this posting. Check them for conditions and exceptions.

Uses this posting and your question. No profile needed.