← Back to Job Board

AI Platform Engineer

Supabase

Official advert: Supabase · jobs.ashbyhq.com

Remote, open to applicants in Kenya. An international employer - before you accept, check whether you would be an employee or a contractor, the pay currency, and how tax is handled.

remote · fulltime

Posted 18 Nov 2026

Apply

About

Supabase is hiring an AI Platform Engineer to build the execution, evaluation and governance layers for its internal AI systems. The role owns the agent platform and infrastructure end to end, including production agents, evaluation gates, governance controls, platform tooling and production measurement.

How to apply

Create a free account to apply

Sign up and add a short profile, then see how to apply and open the official advert. We'll track every application for you, alert you to jobs like this one, and you'll apply faster next time.

About two minutes, and you come straight back to this job. Cazini never charges to apply.

Responsibilities

  • Ship the agent platform to production. An event-triggered queue, a headless model-agnostic runtime (choosing the runtime is an open decision you will close), durable state that survives a failed run, a human review gate, atomic rollback, and complete run logging in the warehouse.
  • Own the evaluation layer, and switch on the gate that depends on it. Golden suites with behavioral assertions rather than intuition, judge criteria with a written rubric, safety cases that must pass on every run, and a CI gate that blocks a regression from merging. This is the precondition for every
  • Build and register the agent portfolio. Reporting, drafting, linting, triage and question-answering agents across the executive, team-lead and individual-contributor layers, plus a meta layer that observes the platform and improves it.
  • Enforce governance in code. Risk tiers the pipeline actually enforces, least-privilege credentials per agent, tool-permission gates, a decision audit log, and autonomy classes where the dangerous class has no code path rather than a warning label. Nothing runs without a registered owner, tier, tool
  • Design how the system contacts people. A hard interruption budget per person, message bundling instead of a stream of pings, and a structure that gives something useful before it asks for anything. Adoption depends on this more than on any other single design choice.
  • Own the platform tooling. The compiler and validator, inventory integrity, and the paths that distribute context and capabilities into the repositories and chat surfaces where work happens.
  • Compute the operating measures from production data. A pipeline from raw system activity through to a computed maturity grade per team, defensible enough that a team can dispute the result and be answered with the query rather than an opinion.
  • Instrument the platform's own return. A ledger that logs the work each agent absorbs and computes the monthly figure, so the value of the system is a measurement rather than a claim.

Qualifications

  • Have shipped production LLM agent systems that other people depended on. Not demos, not internal showcases. Systems with operational history, real users and at least one incident you can talk through. Prompt engineering on its own does not clear this bar.
  • Design evaluations, not spot checks. You build golden sets, write behavioral assertions, define judge rubrics, set pass thresholds and gate CI on the result. You can explain why "we reviewed a bunch of outputs and they looked good" is not evaluation.
  • Have done deep API work against the systems work actually lives in, and have authored MCP servers. You know the specific failure modes of those APIs, not just that they exist.
  • Own infrastructure end to end in Python on GCP, with a cloud warehouse and infrastructure as code. You provision, deploy, monitor and roll back your own systems, and you close architecture decisions rather than routing them onward.
  • Have taste about how software contacts humans. You treat every notification as spending a limited amount of trust.
  • Public work in this space. An open-source agent framework, an MCP server, an evaluation harness, or writing on agent reliability that other practitioners cite.
  • LLM observability and cost instrumentation. Tracing agent runs, attributing spend per run, and building the queries that turn raw logs into a report someone acts on.
  • You have built an internal platform that non-engineers adopted voluntarily, and can describe what you changed after watching them use it.

Similar jobs

Get new it jobs by email

Free, one email a day at most, unsubscribe any time.