Back to jobs

Machine Learning Engineer - 2

Pay
Pay not listed
Work setting
Not stated
Employment
Not stated

What you’ll work on

Full posting
  • Turn 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

From the employer’s posting
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
Education & alternatives
- 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:
Apply at SatSure Analytics India

Posting record

Report an error

Actively hiringFirst seen by us 3 days ago, still listed, and not a repost of an earlier posting.

Status in our records
Live
First seen by us
Nov 18, 20263 days ago
Recorded sightings
5
Last seen by us
Nov 22, 2026
Employer says posted
Jul 24, 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 3

Early. 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.

SatSure Analytics India is hiring

10 open jobs

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

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
  • AWS
  • Docker
  • Kubernetes
  • MLflow
  • S3
  • PyTorch
Where the posting names them
- 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.

Your next step

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

Already applied? Track this application

Job description

View original posting ↗

SatSure is a global Earth intelligence company headquartered in India. Founded in  2017, SatSure owns the full Earth observation data value chain – from the upstream payload infrastructure to the foundational deep-tech and AI layers, to the downstream decision intelligence solutions. We work with private companies and government bodies across Agri-tech, Agri-banking, forestry, critical infrastructure, and aviation.  Through our subsidiary KaleidEO, SatSure is building multispectral payloads for high-definition space imagery with edge computing capabilities, powering both sovereign and commercial applications.

Role:

We are looking for a Machine Learning Engineer II to own a model workstream end-to-end — not a single model, but the family of models behind a product line, and the decisions that keep them accurate, fast, and affordable in production. You will be handed goals and ideas, not finished solutions: you decide how to run the experiments to test them, own the optimization and serving strategy, and defend your choices with benchmarks and clear findings. This is a hands-on role. You will still write the training loop and read the Triton logs.

Responsibilities:
  • Experiment Execution & Reporting: Own how a workstream's ideas get tested. Take the team's modelling proposals, turn them into well-run, reproducible training/fine-tuning experiments, monitor them, and report rigorous findings that decide what ships. You make pragmatic implementation choices; the research direction comes from Data Science.
  • Model Optimization: Own the accuracy/latency/cost tradeoff for your models in production. Drive quantization (INT8/FP16), pruning, distillation, and ONNX/TensorRT export; profile GPU utilization and eliminate the bottleneck rather than guessing at it.
  • Pipelines at Scale: Design ML pipelines that survive real data — petabyte-scale satellite archives, missing tiles, sensor drift, inconsistent projections. Make them reproducible and cheap to re-run.
  • Productionization: Prepare models for production and support their deployment on KServe / Triton alongside the Platform team. You should understand how modern serving frameworks work and what they demand of a model — batch sizing, concurrency, autoscaling behaviour, and failure modes under load — and hand over artifacts that account for them.
  • Evaluation & Benchmarking: Define what "good" means before training starts — offline metrics, production SLOs, and the acceptance criteria a model must meet to ship.
  • Monitoring & Drift: Own post-deployment model health. Instrument for drift, set thresholds, and drive the retraining decision rather than waiting to be told.
  • Technical Mentorship: Review code, models, and experiment design from MLEs/Data Scientists. Raise the floor of the team's engineering practice.
Qualification:
  • 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.
  • Mandatory: Hands-on experience training, fine-tuning, debugging, optimizing, and productionizing modern deep-learning architectures, including CNNs, vision transformers, and vision foundation models such as DINO- and SAM-style models. You are comfortable reading unfamiliar model implementations, adapting them to new use cases, and improving their training efficiency, inference performance, and production reliability.
  • 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:
  • ML Engineering Depth: You have debugged the training instability, found the data leak, and traced the production regression back to a preprocessing change. You know where models break in the real world.
  • Training at Scale: Confident running distributed / multi-GPU training and fine-tuning jobs efficiently and reproducibly, and instrumenting them so the findings are trustworthy.
  • 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.
  • 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:
  • 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.
  • CI/CD for ML — automated training triggers, evaluation gates, and progressive rollout of models.
  • CUDA-level debugging and custom kernel awareness.
  • Experience with distributed training frameworks and large-scale data loading optimization.
  • Exposure to cost optimization for GPU workloads (spot strategy, right-sizing, inference cost per prediction).
Competencies:
  • Ownership: You own the outcome, not the artifact. If the model is slow in production, you drive the diagnosis and the fix with whoever owns the infrastructure it runs on.
  • Judgement: You know how to run an idea cheaply enough to get a signal fast, and when a negative result is conclusive. You do not over-engineer.
  • Scientific Rigor: Hypothesis-driven experimentation with results others can reproduce from your tracking and write-ups alone.
  • Collaboration & Influence: You can explain a tradeoff to a Data Scientist, a Platform engineer, and a domain expert — and get all three to agree on a path.
  • Mentorship: You make the engineers around you better through review, pairing, and clear technical writing.
Interview Process:
  • Intro call
  • Take-home assessment (focus on model training, optimization & deployment)
  • Interview rounds (ideally up to 3 rounds, including a deep dive on a model you have shipped and an ML system design discussion)
  • Culture round / HR round

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

No pay amount identified in the saved description.

Location & working pattern

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.
More source context
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.
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.