Back to jobs

[VMT] Platform AI Software Engineer

Buenos Aires, Buenos Aires, Argentina

Live, first seen by us 77 days ago
Pay
Pay not listed
Work setting
On-site — work setting source
Work setup in the employer’s posting: On-site
From the employer’s posting
Employment
Full-time — employment source
Employment type in the employer’s posting: Full-time
From the employer’s posting

What you’ll work on

Full posting
  • Build and extend the evaluation harnesses that gate prompt changes and model migrations.

From the employer’s posting
Investigate agent misbehavior reported from real customer plants and turn each case into a diagnosis, a fix, and a regression test. Build and extend the evaluation harnesses that gate prompt changes and model migrations. Add reliability mechanisms to the agent: assumption surfacing, grounding checks, output-quality reviewers.

What you’ll bring

All qualifications

Core experience

  • Strong Python in large, shared, evolving backend codebases: you will work daily in code you didn't write, alongside people committing to it every day.
  • Experience with charting/plotting pipelines (matplotlib or similar) feeding a UI.
Qualification wording
Strong Python in large, shared, evolving backend codebases: you will work daily in code you didn't write, alongside people committing to it every day.
Experience with charting/plotting pipelines (matplotlib or similar) feeding a UI.
Apply at Software Mind

Posting record

Report an error
Status in our records
Live
First seen by us
Sep 5, 202677 days ago
Recorded sightings
119
Last seen by us
Nov 21, 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 77

Up longer than most. Similar jobs usually come down between day 1 and day 15.

Well past Software Mind’s usual: its jobs come down by about day 7.

From 1,371 similar postings that came down, and 55 of Software Mind’s. Coming down is not always a hire.

Software Mind is hiring

6 open jobs

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

  • Hiring at a steady pace
  • Takes jobs down quickly
  • 17% of open jobs were reposted
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
  • Azure
  • GCP
  • Matplotlib
Where the posting names them
Our client builds an AI copilot for process engineers in oil refineries and chemical plants: a natural-language interface where engineers ask questions about live plant data — equipment, sensor tags, process trends — and get grounded, chart-backed answers. The users are experienced engineers who are rightly skeptical of AI: in this domain, a fabricated number or a silent wrong assumption has real cost. The product wins or loses on whether the agent can be trusted. This role owns the trust layer of that agent inside a large, active Python codebase. It is not feature work with an LLM endpoint bolted on. The work is the mechanics of agent reliability: making the agent say "I don't know" instead of inventing, surfacing every assumption it makes so the user can correct it, grounding every claim in actual data, holding output quality through model migrations, and keeping latency acceptable while doing all of the above. To make the day-to-day concrete, this is what the engineer currently in this seat shipped in the last four months (all of it flag-gated, in small PRs, reviewed async daily by a team spread across the US and Australia):
Expectations - the experience you need - Strong Python in large, shared, evolving backend codebases: you will work daily in code you didn't write, alongside people committing to it every day. - You have shipped an LLM-based feature to production AND built an evaluation that changed a real decision (a model choice, a prompt rollback, a killed feature).
Nice to have - GCP (Vertex AI in particular); AWS/Azure acceptable. - Observability tooling (tracing, structured logging, latency percentiles you actually watched).
- Observability tooling (tracing, structured logging, latency percentiles you actually watched). - Experience with charting/plotting pipelines (matplotlib or similar) feeding a UI. - Industrial, process, or time-series data domain experience.

Your next step

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

Applying through SmartRecruiters

  • Uploading your resume fills in the application form for you, so check what it filled before you send.

Already applied? Track this application

Job description

View original posting ↗

Job Description

Project - the aim you'll have

Our client builds an AI copilot for process engineers in oil refineries and chemical plants: a natural-language interface where engineers ask questions about live plant data — equipment, sensor tags, process trends — and get grounded, chart-backed answers. The users are experienced engineers who are rightly skeptical of AI: in this domain, a fabricated number or a silent wrong assumption has real cost. The product wins or loses on whether the agent can be trusted.

This role owns the trust layer of that agent inside a large, active Python codebase. It is not feature work with an LLM endpoint bolted on. The work is the mechanics of agent reliability: making the agent say "I don't know" instead of inventing, surfacing every assumption it makes so the user can correct it, grounding every claim in actual data, holding output quality through model migrations, and keeping latency acceptable while doing all of the above.

To make the day-to-day concrete, this is what the engineer currently in this seat shipped in the last four months (all of it flag-gated, in small PRs, reviewed async daily by a team spread across the US and Australia):

- An assumption auditor: detects the silent assumptions the agent makes when answering (which equipment, which time window), validates them via multi-draw consensus, and surfaces them in the UI as correctable chips — the engineer can fix an assumption and rerun the analysis.
- A grounding auditor that catches reports fabricated from empty data feeds before they reach the user.
- An adversarial reviewer sidecar that critiques generated charts for correctness before display.
- Successive frontier-model evaluations (loop behavior, directive adherence, regression on a replay harness) that decided when to flip the product's default model — including, twice, deciding NOT to flip.
- Hardening of a plant-exploration tool against hallucinating structure that the data does not support.
- A latency fix: a narration side-loop was inflating query response times; capped it and made it best-effort.
- A concurrency fix making a shared data-reset path atomic, eliminating intermittent production read errors.

If reading that list is more interesting to you than building another CRUD feature, this role is for you.

Qualifications

Expectations - the experience you need

  • Strong Python in large, shared, evolving backend codebases: you will work daily in code you didn't write, alongside people committing to it every day.
  • You have shipped an LLM-based feature to production AND built an evaluation that changed a real decision (a model choice, a prompt rollback, a killed feature).
  • Production debugging from symptom to confirmed root cause: latency spikes, concurrency errors, failures that produce no log line.
  • Prompt work treated as engineering: measured adherence, regression testing against a fixed case set — not vibes.
  • Comfort with feature-flag discipline and staged rollouts (default-off, soak, flip), small PRs, and mostly-async collaboration across US and Australia time zones.
  • High autonomy: problems arrive ambiguous ("the agent feels slow", "the engineers don't trust the numbers") and you turn them into scoped, verifiable fixes without waiting for a spec.
  • Direct, precise written English.

Nice to have

  • GCP (Vertex AI in particular); AWS/Azure acceptable.
  • Observability tooling (tracing, structured logging, latency percentiles you actually watched).
  • Experience with charting/plotting pipelines (matplotlib or similar) feeding a UI.
  • Industrial, process, or time-series data domain experience.
  • Heavy AI-tooling development workflow (Claude Code or similar) — the team works this way.

What you will do 

  • Investigate agent misbehavior reported from real customer plants and turn each case into a diagnosis, a fix, and a regression test.
  • Build and extend the evaluation harnesses that gate prompt changes and model migrations.
  • Add reliability mechanisms to the agent: assumption surfacing, grounding checks, output-quality reviewers.
  • Diagnose and resolve cross-cutting performance and concurrency issues.
  • Raise code quality in the areas you touch, within the team's review conventions.

Our Benefits 

  • Educational resources
  • Flexible schedule and Work From Anywhere
  • Referral Program
  • Supportive and chill atmosphere

We are accepting applications from LATAM countries
 

Company Description

We are Software Mind, an awesome team of engineers who are ready to ramp up any top-notch company’s projects! Our aim? To always be one step ahead. Become part of a multicultural company in constant growth with an excellent work environment certified by Great Place To Work!

Demand for AI Engineer roles

New AI Engineer postings at the employers we follow are up 340% over the last 6 weeks compared with the 6 before.

Weekly new AI Engineer postings at the same employers, from the week of August 17 to the week of November 9. The fewest in a week was 78, the most 803, and the latest week had 438.
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 AI Engineer, by the work the posting describes.

AI engineers build products on top of AI models that already exist, most often large language models: they connect a model to a company's data and tools and ship the assistants, agents and search features people use.

Postings ask for strong Python or TypeScript, experience with model APIs, retrieval and agent frameworks, and ways to test whether the model's answers are good enough.

An ML engineer trains and serves models; an AI engineer usually starts from a model someone else trained and builds the product around it, though titles often mix the two.

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

Buenos Aires, Buenos Aires, Argentina

Working pattern and location restrictions need checking in the full posting.

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.