Back to jobs

Senior ML Engineer (Client Solutions)

Pay
Pay not listedSimilar roles state $166K–$237K
Work setting
Not stated
Employment
Full-time — employment source
Employment type in the employer’s posting: FullTime
From the employer’s posting

What you’ll work on

Full posting

We are seeking an ML Engineer who builds ML systems directly inside client environments.

  • Own the full ML lifecycle: data cleaning, modeling, deployment, scheduling, monitoring, retraining

  • Build forecasting and detection models that handle late feeds, revised rows, and missing labels

  • Backtest and evaluate models, and defend precision/recall tradeoffs to end users

  • Ship usable product such as a FastAPI service, React surface, or scheduled job

  • Run discovery, working sessions, and demos with client IT and data teams

From the employer’s posting
We are seeking an ML Engineer who builds ML systems directly inside client environments. Your job starts with the client's actual data spread across multiple systems — and ends with a model running on a schedule inside their environment. You will bring a strong area of expertise, but expect to wear many hats as part of a small team — some DevOps, some infrastructure, some front end and back end — because you are the engineering face of AZX to your client.
Own the full ML delivery lifecycle: data discovery and cleaning, modeling, evaluation, deployment into the client environment, scheduling, monitoring, and retraining policy.
Build forecasting and detection models that hold up against real-world data quality issues (late feeds, revised rows, missing labels).
Backtest and evaluate models honestly enough to stake real operational decisions on them, and defend your precision/recall tradeoffs to the people who bear the cost of false alarms.
Ship enough product to make the model usable — a FastAPI service, a small React surface, a scheduled job
running discovery, working sessions with client IT/data teams, demos

Before you apply

Work authorization
Must already have the right to work in the USApplicants must be currently authorized to work in the United States on a full-time basis
Education & alternatives
- Working fluency with LLMs for the agentic edges of client work (extraction, retrieval) — depth isn't required, but honesty about your actual experience is. - Bachelor's Degree; Master's is a Plus - Domain experience in Energy, Utilities, Infrastructure, and Commercial Real Estate is a plus

About Azx

Our mission is to accelerate positive impact in critical industries through AI transformation.

In the employer’s words · Read in context

Apply at Azx

Posting record

Report an error
Status in our records
Live
First seen by us
Sep 2, 202679 days ago
Recorded sightings
52
Last seen by us
Nov 20, 2026
Employer says posted
Aug 31, 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

Pay

$166K–$237K is typical

The middle half of what similar US postings state. This one doesn’t list pay.

From 1,507 postings in the last year. Stated ranges, not salaries paid.

Time since we first saw it

Day 79

Up longer than most. Similar jobs usually come down between day 7 and day 76.

From 6,269 similar postings that came down. Coming down is not always a hire.

Azx is hiring

3 open jobs

Open jobs by the week we first saw them, last 12 weeks.

  • Its jobs tend to stay up a long time
Hiring record

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.

  • Python
  • SQL
  • TypeScript
  • AWS
  • Azure
  • Docker
  • DuckDB
  • FastAPI
  • pandas
  • Polars
  • React
  • scikit-learn
  • PostgreSQL
Where the posting names them
- Rigorous validation discipline — chronological splits, walk-forward validation, as-of correctness, and an instinct to be suspicious of a suspiciously good metric. - Enough software engineering to ship real systems: Python, SQL, tests, Docker, a scheduler, an API or app surface, and monitoring — type-strict, tested, reviewable code, even in a pod of two. - Client-facing capability and the assertion to use it — running discovery, leading demos, and pushing back early and plainly when an ask is wrong, with an alternative already in hand.
- Judgment about when ML is the wrong tool, and the willingness to say so to a client who wants AI regardless. - Practical fluency with our core stack — Python 3.12+ (pandas/polars/DuckDB, scikit-learn, statsmodels, gradient boosting), SQL/Postgres (with TimescaleDB/PostGIS for grid work), and time-series feature engineering and validation. - Comfort building the surfaces that make a model usable — FastAPI plus enough React/TypeScript to expose results — and deploying it with Docker and basic cloud tooling (Azure/AWS).
- Practical fluency with our core stack — Python 3.12+ (pandas/polars/DuckDB, scikit-learn, statsmodels, gradient boosting), SQL/Postgres (with TimescaleDB/PostGIS for grid work), and time-series feature engineering and validation. - Comfort building the surfaces that make a model usable — FastAPI plus enough React/TypeScript to expose results — and deploying it with Docker and basic cloud tooling (Azure/AWS). - Working fluency with LLMs for the agentic edges of client work (extraction, retrieval) — depth isn't required, but honesty about your actual experience is.
- Design systems that distinguish "no prediction" from "wrong prediction," so a missing answer reads differently to the end user than an incorrect one. - Ship enough product to make the model usable — a FastAPI service, a small React surface, a scheduled job — whatever "usable capability" means for that client. - Own the measurement story: agree on baselines and KPIs before deployment, instrument for monitoring, and deliver a post-deployment readout with attribution limits clearly stated.

Your next step

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

Applying through Ashby

  • No account needed. “Autofill from resume” at the top of the form fills the key fields from your file.

Already applied? Track this application

Job description

View original posting ↗

About AZX

Our mission is to accelerate positive impact in critical industries through AI transformation. We specialize in physics-informed ML and enterprise AI solutions that directly address climate and sustainability challenges.

We’re growing quickly and already work with category-leaders in real estate (CBRE), energy (LevelTen Energy), logistics (Flexe) and utilities.

We bootstrapped profitably for our first year and are now backed by leading investors focused on AI, climate and energy.

We work on challenges in clean energy, decarbonization, climate risk, energy systems, and global economics. We’re building our company for long-term success and aim to create the ultimate place to work for those passionate about AI and making a positive impact.

About This Role:

We are seeking an ML Engineer who builds ML systems directly inside client environments. Your job starts with the client's actual data spread across multiple systems — and ends with a model running on a schedule inside their environment. You will bring a strong area of expertise, but expect to wear many hats as part of a small team — some DevOps, some infrastructure, some front end and back end — because you are the engineering face of AZX to your client.

Responsibilities:

  • Own the full ML delivery lifecycle: data discovery and cleaning, modeling, evaluation, deployment into the client environment, scheduling, monitoring, and retraining policy.

  • Build forecasting and detection models that hold up against real-world data quality issues (late feeds, revised rows, missing labels).

  • Backtest and evaluate models honestly enough to stake real operational decisions on them, and defend your precision/recall tradeoffs to the people who bear the cost of false alarms.

  • Design systems that distinguish "no prediction" from "wrong prediction," so a missing answer reads differently to the end user than an incorrect one.

  • Ship enough product to make the model usable — a FastAPI service, a small React surface, a scheduled job — whatever "usable capability" means for that client.

  • Own the measurement story: agree on baselines and KPIs before deployment, instrument for monitoring, and deliver a post-deployment readout with attribution limits clearly stated.

  • Maintain client-facing engineering presence and a feedback loop into the platform team — running discovery, working sessions with client IT/data teams, demos, and surfacing the data shapes and failure modes only visible from inside client data.

Core Qualifications:

  • 5+ years of shipping applied machine learning to production — forecasting, detection/classification on time series, survival/reliability modeling, or optimization — with an evaluation you defended to someone whose job depended on it.

  • Strong data engineering skills and willingness to use them: you find, clean, join, and profile data yourself at awkward scale, without a dedicated data team.

  • Rigorous validation discipline — chronological splits, walk-forward validation, as-of correctness, and an instinct to be suspicious of a suspiciously good metric.

  • Enough software engineering to ship real systems: Python, SQL, tests, Docker, a scheduler, an API or app surface, and monitoring — type-strict, tested, reviewable code, even in a pod of two.

  • Client-facing capability and the assertion to use it — running discovery, leading demos, and pushing back early and plainly when an ask is wrong, with an alternative already in hand.

  • Judgment about when ML is the wrong tool, and the willingness to say so to a client who wants AI regardless.

  • Practical fluency with our core stack — Python 3.12+ (pandas/polars/DuckDB, scikit-learn, statsmodels, gradient boosting), SQL/Postgres (with TimescaleDB/PostGIS for grid work), and time-series feature engineering and validation.

  • Comfort building the surfaces that make a model usable — FastAPI plus enough React/TypeScript to expose results — and deploying it with Docker and basic cloud tooling (Azure/AWS).

  • Working fluency with LLMs for the agentic edges of client work (extraction, retrieval) — depth isn't required, but honesty about your actual experience is.

  • Bachelor's Degree; Master's is a Plus

  • Domain experience in Energy, Utilities, Infrastructure, and Commercial Real Estate is a plus

Why AZX!

  • Be part of a fast-growing, profitable, mission-driven company with industry-leading clients tackling the massive opportunity of AI transformation in critical industries.

  • Competitive early-stage startup compensation (based on capabilities, experience, and location)

  • Bonus eligibility

  • Health insurance with meaningful coverage for dependents

  • Flexible paid time off

  • Equity

  • Fully remote culture with a cluster of teammates in Seattle

 

Additional Information:

  • Must be able to travel 2x/year for company summits

  • Applicants must be currently authorized to work in the United States on a full-time basis.

  • We are unable to sponsor or take over sponsorship of employment visas at this time.

  • Please note that our interview process includes a written take-home assignment followed by a live two-hour technical session with our engineering team, so if that format isn't a good fit, we'd ask that you not apply

  • Please only apply to a maximum of 2 roles at a time, any applicants who apply to more then 2 roles within a 6 month period will automatically be disqualified

 

Next Steps:

If this job sounds like a great fit but you don’t check ALL of these qualification boxes, we’d still love to hear from you!

Demand for ML Engineer roles

New ML Engineer postings at the employers we follow are up 12% 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 556, the most 1,080, and the latest week had 556.
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

No pay amount identified in the saved description.

Location & working pattern

United States

- Equity - Fully remote culture with a cluster of teammates in Seattle Additional Information:
Work authorization
- Must be able to travel 2x/year for company summits - Applicants must be currently authorized to work in the United States on a full-time basis. - We are unable to sponsor or take over sponsorship of employment visas at this time. - Please note that our interview process includes a written take-home assignment followed by a live two-hour technical session with our engineering team, so if that format isn't a good fit, we'd ask that you not apply

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.