ML Engineer Jobs in Energy: Demand, Pay & Skills
Part of Plutarch’s ongoing analysis of skill demand in energy hiring — last updated 16 November 2026, based on 84 tracked postings.
As of 16 November 2026, Plutarch tracked 84 unique open ML Engineer postings at energy employers. 16 postings disclosed annual pay, with a United States median of USD 188,000.
Demand for ML Engineers is concentrated in the United States, with meaningful activity in India and the United Kingdom and smaller pockets elsewhere. Most titles carry no stated seniority, but a large share explicitly call for senior, lead, principal, staff or manager level experience, indicating competition is weighted toward experienced practitioners rather than entry-level hires. Entry-level and intern-labeled titles form a small minority, and executive-labeled titles are effectively absent.
AI-written summary, 29 October 2026. The figures below are counted from the postings and updated weekly.
Seniority
Only 6 of 84 titles are early career. 32 are senior or above, and 46 state no level.
- Early career 6
- Senior, lead, staff or manager 32
- Level not stated in title 46
Where
The United States has 32 of 84 postings (38%). 21 are in other countries or state none.
- United States 32
- India 12
- United Kingdom 9
- Canada 6
- Australia 4
- Other or not stated 21
Disclosed pay by country · annual
Half of the 16 United States postings that state pay sit above USD 188,000.
| Country | Lowest to highest employer midpoint | Median | Postings stating pay |
|---|---|---|---|
| United States | USD 106,000–275,000 | USD 188,000 | 16 of 30 |
Directional, not conclusive. Each figure is the midpoint of a salary range an employer disclosed in a public job posting, derived from public market sources and rounded to the nearest thousand. Samples are small, so a country appears only when at least 5 open postings disclose annual pay. At these sample sizes, do not compare one role’s median against another’s — the difference between them is smaller than the error on either.
How many employers state pay
United States postings state pay in 21 of 30. In India and Australia, none of 16 do.
| Country | Postings we could read that state pay |
|---|---|
| United States | 21 of 30 |
| India | 0 of 12 |
| United Kingdom | 3 of 9 |
| Canada | 2 of 6 |
| Australia | 0 of 4 |
Counted from the same open postings as above, leaving out postings whose text we could not read for pay. A posting that states pay per hour or per month counts here, but not in the annual figures above. Pay disclosure tracks local pay-transparency law more closely than employer policy, so a low rate is not evidence that employers here pay less.
Who is hiring
No employer leads. S&P Global and Siemens Energy have 5 postings each, about 6% of the market. 51 postings are at other employers.
| Employer | Open postings |
|---|---|
| S&P Global | 5 |
| Siemens Energy | 5 |
| Neara | 4 |
| tem | 3 |
| Crusoe | 2 |
| ETAP | 2 |
| Hitachi Energy | 2 |
| Kpler | 2 |
| Maersk | 2 |
| Mariana Minerals | 2 |
| Occidental Petroleum Corporation | 2 |
| SES | 2 |
| Other employers | 51 |
How these roles are titled
The titles employers use for this role, most repeated first. Titles shown without a count appeared once.
- Machine Learning Engineer · 12 postings
- AI/ML Engineer · 4 postings
- Senior Machine Learning Engineer · 2 postings
- Staff Machine Learning Engineer · 2 postings
- Advisor IT Systems - AI/ML Ops
- AI /ML Solutions Engineer
- AI & MLOps Engineer
- AI and Machine Learning Engineer (2 Year Fixed Term Contract)
- AI Operations Intern
- AI Platform Engineering & Operations Manager
- AI/Machine Learning Engineer
- AI/Machine Learning Engineering Intern
- AI/ML Engineering Intern
- AI/ML Process Engineering Intern (Spring 2027)
- Associate AI/ML Engineer
What employers ask for
Skills and tools named in the text of 81 open postings we could read in full, most named first.
Python is named in 81% of the postings we read, and Machine learning in 79%.
| Skill or tool | Postings naming it | Employers |
|---|---|---|
| Python | 66 of 81 | 47 |
| Machine learning | 64 of 81 | 44 |
| PyTorch | 38 of 81 | 28 |
| MLOps | 37 of 81 | 31 |
| AWS | 36 of 81 | 25 |
| LLMs | 34 of 81 | 23 |
| Azure | 32 of 81 | 25 |
| CI/CD | 28 of 81 | 25 |
| SQL | 27 of 81 | 24 |
| Docker | 26 of 81 | 20 |
| Statistics | 22 of 81 | 18 |
| Git | 21 of 81 | 19 |
| Deep learning | 21 of 81 | 16 |
| Generative AI | 21 of 81 | 15 |
| Kubernetes | 21 of 81 | 15 |
A skill counts when the posting names it anywhere — requirements, role description or the employer’s own introduction. A skill is shown only when at least 3 postings from at least two employers name it. Postings whose full text we did not read are left out of these counts rather than counted as asking for nothing.
Patterns in the job titles
- MLOps and machine learning infrastructure/operations
- Applied and production-focused machine learning engineering
- AI/ML engineering combined roles
- Platform-focused machine learning engineering
Roles that ask for the same skills
Data Scientist postings have the most skills in common with these: Python is named in 81% of these postings and 85% of theirs.
- Data Scientist — both name Python (81% here, 85% there), Machine learning (79% here, 70% there), SQL (33% here, 57% there), Azure (40% here, 29% there), Statistics (27% here, 70% there) · compare side by side
- AI Engineer — both name Python (81% here, 68% there), LLMs (42% here, 61% there), Azure (40% here, 41% there), AWS (44% here, 30% there), CI/CD (35% here, 30% there) · compare side by side
- Generative & Agentic AI Specialist — both name Python (81% here, 60% there), LLMs (42% here, 64% there), CI/CD (35% here, 36% there), Azure (40% here, 31% there), Machine learning (79% here, 29% there) · compare side by side
Shares are of the open postings we could read in full for each role. This compares what employers ask for in the two roles; it does not count how many people hold those skills or say that one role can do the other.
ML Engineer job description template
An outline to start from. The requirements are the skills energy employers most often name for this role, with how often each is named — not a model's guess.
Already have a draft? Paste it for a hiring-feasibility brief and a sharpened version. For the credential line, see which credentials the law requires, and where.
What the postings suggest about filling this role
The high proportion of titles demanding senior, lead, staff or principal-level skills suggests sourcing will skew toward a smaller, more experienced and more contested talent pool, making those roles comparatively harder to fill. The sizeable set of unspecified-level titles and modest junior and intern presence offers somewhat easier entry points, but overall difficulty leans higher given the concentration of advanced-level requirements.
AI-written, 29 October 2026. Read from employer demand only. These sources show what employers advertise, not how many people are available to hire, so this is a reading of the vacancies rather than a measure of scarcity.
Show these figures on your own website or newsletter
For recruitment agencies, careers sites, hiring blogs and newsletters: add a small card that shows how many ML Engineer roles energy employers have open and the skills they ask for most. It is useful beside a job advert or a market update, to show candidates and clients the demand. The card updates itself each week, and it names Plutarch as the source.
To add it, paste this code into your page's HTML, or send it to whoever manages your website.
Grade a job description — free, no sign-up
Paste a job description. We point out wording that may mislead candidates, whether it needs a credential, and how it compares with what energy employers ask for.Open the full grader.
This page sums up every open posting for this role. Your role is one job description, with its own requirements, location and pay.
Paste it to get a hiring-feasibility brief: whether the role can be filled, at what price, and who else could do it — every figure labelled by what it rests on.
Check your role — two briefs freeCounts are unique open postings seen in the last three weeks, taken from the named employers’ own published job postings; a vacancy posted in several places is counted once. Employers are named because they published these postings publicly themselves. The written summary is AI-generated from those postings and contains no figures and no employer names. Posting figures are direct counts; pay figures are the median and range of the salaries those employers disclosed. Terms of use.