Time since we first saw it
Day 3
Early. 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.
Location not stated
Actively hiring, first seen by us 3 days agoTurn team modelling proposals into reproducible training and fine-tuning experiments and report findings
Own accuracy, latency and cost tradeoffs via quantization, pruning, distillation and ONNX/TensorRT export
Design ML pipelines over petabyte-scale satellite archives that handle missing tiles and sensor drift
Prepare models and artifacts for deployment on KServe and Triton with the Platform team
Monitor post-deployment model drift and drive retraining decisions
Take the team's modelling proposals, turn them into well-run, reproducible training/fine-tuning experiments
Drive quantization (INT8/FP16), pruning, distillation, and ONNX/TensorRT export
Design ML pipelines that survive real data — petabyte-scale satellite archives, missing tiles, sensor drift, inconsistent projections
Prepare models for production and support their deployment on KServe / Triton alongside the Platform team
Instrument for drift, set thresholds, and drive the retraining decision
- Mandatory: Experience running experiments to a defined hypothesis with minimal supervision — and reporting findings others could act on. - Bachelor's degree in Computer Science, IT, Statistics, or a related field; non-IT degrees with strong relevant experience are acceptable. Must-have skills:
Actively hiringFirst seen by us 3 days ago, still listed, and not a repost of an earlier posting.
These dates show when we found the posting. Check the employer’s website to confirm it is still accepting applications.
Day 3
Early. 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.
10 open jobs
Open jobs by the week we first saw them, last 12 weeks.
Hiring recordAdd 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.
- Feature & Data Pipelines: Scalable pipelines over raster/vector geospatial formats; comfortable with Rasterio/GDAL, tiling strategies, and the failure modes of remote sensing data. - Python & Engineering Practice: Clean, tested, maintainable code. You write ML code other engineers can pick up. - Containerization & Cloud: Confident with Docker and AWS (S3, EC2, ECR); you can reason about GPU instance selection and the cost of your own training runs.
- Python & Engineering Practice: Clean, tested, maintainable code. You write ML code other engineers can pick up. - Containerization & Cloud: Confident with Docker and AWS (S3, EC2, ECR); you can reason about GPU instance selection and the cost of your own training runs. - Serving Infrastructure: Familiarity with KServe, Triton, or an equivalent model-serving stack — enough to understand how your model will be served and to work effectively with the team that runs it.
- Experimentation & Versioning: MLflow (or equivalent) used properly — reproducible experiments, a model registry others can trust, and lineage from data to deployed artifact. - Kubernetes (User Level): Submitting GPU jobs, reading pod logs, reasoning about resource requests and limits. Good-to-have:
- Serving Infrastructure: Familiarity with KServe, Triton, or an equivalent model-serving stack — enough to understand how your model will be served and to work effectively with the team that runs it. - Experimentation & Versioning: MLflow (or equivalent) used properly — reproducible experiments, a model registry others can trust, and lineage from data to deployed artifact. - Kubernetes (User Level): Submitting GPU jobs, reading pod logs, reasoning about resource requests and limits.
- 4–7 years of relevant experience as a Machine Learning Engineer or in an applied research/engineering role. - Mandatory: Deep hands-on PyTorch expertise — custom datasets, distributed/multi-GPU training, mixed precision, and inference optimization. You can read a PyTorch profiler trace and act on it. - Mandatory: Multiple models shipped to production and kept in production, with evidence of measured latency/throughput improvements.
Complete your application on satsure.keka.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.
Location not supplied.
- Optimization Fluency: Quantization, distillation, ONNX/TensorRT, and batching/concurrency tuning at the serving layer. You can quantify what each technique bought you. - Feature & Data Pipelines: Scalable pipelines over raster/vector geospatial formats; comfortable with Rasterio/GDAL, tiling strategies, and the failure modes of remote sensing data. - Python & Engineering Practice: Clean, tested, maintainable code. You write ML code other engineers can pick up.
Good-to-have: - Background in geospatial or remote sensing ML (satellite imagery, SAR, multispectral, time-series of Earth observation data). - Kernel-level bottleneck analysis and the ability to quantify what it bought you.
No clear work-authorization passage found. Eligibility is unconfirmed.