Member of Technical Staff | Inference Platform
This is the employer's own posting, not a copy on a job board.
What we know
Is it still open?
Confirmed still open
Last checked 2d ago — checked against the employer's own applicant tracking system, which is the company answering directly.
We re-read the employer's own applicant tracking system and the posting was still there. That is the company answering directly.
How old is it?
Posted 18d ago
The date the source published, not the day we noticed it (2026-09-23). Last seen at its source 1h ago.
We have tracked this listing since 5 Oct 2026 (5 days). The employer's own board has carried it every time we have read it, most recently 1 hour ago.
Is it remote?
Marked remote on the employer's board
Their board carries a remote setting on this posting — a field they filled in, not wording we read. The location field names somewhere specific, which is usually where the team or the entity sits.
Who may apply?
Sao Paulo
The description states no restriction of its own. This is the source's own tag.
Skills named in the ad
Recognised terms only, from a fixed vocabulary — this is what CV matching compares against.
Carried by 1 source
-
Ashby employer's own board first seen 5d ago · last seen 1h ago
The listing
About the role
At Avra, every technical IC is a Member of Technical Staff (MTS). The title doesn't put anyone in a silo: you own systems and outcomes, not steps in a function, and you keep building depth in your area.
In this role, you'll join the Platform team to own where our models execute. Customers consume our models through large batches of millions of records and through real-time APIs, and they make business decisions on every response. You'll run governed model releases reliably and efficiently — in our cloud and on customer-hosted Kubernetes — and make inference fast, predictable, and cheap enough to serve both enterprise and mid-market customers.
What you'll do
Evolve Sophos, our online and batch inference runtime, built on Kubernetes.
Run large batch inference on ephemeral jobs, with multi-dimensional admission control (CPU, memory, GPU).
Build and extend the controller and its Kubernetes custom resources.
Optimize each model's inference engine and feature processing.
Serve graphs and data efficiently.
Own execution of training, post-training, and fine-tuning jobs, in our cloud and in customer dataplanes / on-premisse cloud.
Drive autoscaling, GPU serving, performance, and cost optimization, with telemetry for every model we run.
How we measure success
99.9% serving availability.
p95/p99 latency for online inference and throughput for batch.
Cost per prediction and per training job.
GPU utilization: paid capacity versus capacity actually used.
Training and batch jobs that finish on time and succeed without manual retries.
What we're looking for
Experience running model serving or large-scale batch compute on Kubernetes.
Experience building Kubernetes controllers or operators.
Skill at profiling and optimizing data-heavy Python pipelines.
A clear sense of cost: you treat compute efficiency as a product feature.
Production-quality code and reviews, and a willingness to operate what you build.
Nice to have
Ray, Ray Serve, or KubeRay in production.
Admission-control systems.
GPU serving and performance optimization.
Arrow, Parquet, Lance, or other columnar formats.
Shipping software to customer-hosted Kubernetes.
GCP/AWS and GKE/EKS, and financial services or regulated environments.