Senior Machine Learning Engineer at Coderio
Uruguay
—
Aug 17, 2026
Uruguay
Sep 25, 2026
What this job asks for AI summary
A senior MLOps engineer role at a remote-first software consultancy, responsible for architecting and operating end-to-end machine learning pipelines from development through production. The position bridges data science and software engineering — covering ML lifecycle automation, cloud cost and performance evaluation, and cross-functional collaboration with data engineers and scientists. Suits an experienced practitioner comfortable owning both the infrastructure and the deployment side of ML systems.
Senior level · Remote · Contract
Quick apply — this platform usually takes a CV and a few fields.
We read this from the posting text with AI. Skim the description below before ruling yourself out.
How this req sits in the market our data
Roughly 1,650 people nationally plausibly meet what this posting asks for (network and computer systems administrators). range 690–2,500
Applicant volume Moderate — A normal amount of company. The rare requirements below are what will separate a shortlisted application from the rest.
Rare in this occupation — lead with these, and say what you built with them.
Most people in this occupation already list these. Still required — just not what gets you shortlisted.
What the occupation pays Median $101,310 (middle half $79,725–$129,425).
Estimated from BLS employment for this occupation and area, per-skill prevalence across our listing corpus, and published wage benchmarks — as of Aug 20, 2026. It is a model, not a headcount.
Why we read it this way (7)
SOC classification is genuinely ambiguous for an MLOps role. The posting emphasizes operating and automating the ML lifecycle (pipeline management, deployment, cloud infrastructure) — closer to 15-1244 — but also calls for architecting and developing ML solutions end-to-end, which pulls toward 15-1252 Software Developers. 15-1244 was chosen because the primary framing is operational ownership of the ML lifecycle rather than building new software products, but reasonable classifiers could disagree.
The tooling block is introduced with 'strong knowledge in (or similar to)', meaning the specific tools are interchangeable with equivalents. However, because they appear under the hard Requirements section, the capability they represent is a gate; the 'or similar' qualifier only signals substitutability of the named tool, not optionality of the skill itself.
No compensation figures are stated anywhere in the posting.
The posting describes a 'long-term contract engagement' under Benefits, which signals a Contract engagement type rather than full-time employment.
A Bachelor's degree in CS/software engineering is listed, but the posting explicitly accepts 'proven equivalent experience' as a substitute, so no formal degree is hard-required.
Domain experience in payments or financial systems is listed under 'Nice to Have' and is therefore preferred, not required — it was omitted from the skills list as it names no specific technology or tool.
Posting is for a contract engagement — the market benchmarks below price full-time roles, so read the comp comparison with that in mind.
Read the full posting
The employer publishes the full description on their own site — read it there ↗. Or sign in to read it here — it's free, and it also lets you track this application.