Job Opportunities API

The Public Ledger of Openings

← Back to the ledger

Staff Software Engineer

Avra
CompanyAvra
CategoryEngineering
LocationSão Paulo
RemoteRemote
EmploymentNot stated
LevelNot stated
SalaryNot stated by the employer
Posted14 May 2026
Last verified30 Jul 2026
SourceEmployer career page (ashby)
Applications are handled by the employer, not by us.Apply on the employer's site →
Description
ABOUT AVRA Avra is building relational foundation models for enterprise decision-making in Brazil. Our work focuses on graph-native models for structured, high-stakes prediction problems: credit, fraud, growth, monitoring, and other decisions where entities cannot be understood in isolation. We model companies, people, and the relationships between them as evolving networks, then adapt those representations to customer-specific prediction tasks that plug into existing decisioning systems. We work with internationally recognized research advisors, and we care about research that becomes useful in production. Our systems are already in production with large enterprise customers, supporting high-volume workflows where reliability, latency, model quality, and operational safety all matter. THE ROLE This is a senior individual contributor role for an engineer who can raise the technical quality, reliability, and architectural clarity of Avra’s platform. You will work across the systems that turn Avra’s research and data assets into production infrastructure: APIs, model serving, batch inference, customer workspaces, data contracts, model lifecycle, observability, internal tools, and customer-specific deployments. The role is not pure architecture. You will write code, review code, debug production systems, simplify designs, and help other engineers make better technical decisions. It is also not people management. Your leverage comes from technical judgment, execution quality, mentorship, and the systems you help shape. You will collaborate closely with founders, product engineering, data platform, research, and customer-facing teams. The right person can move between product constraints, infrastructure constraints, ML constraints, and enterprise customer requirements without losing sight of what should be simple, reliable, and maintainable. WHAT YOU’LL WORK ON You will help design and scale the architecture behind Avra’s platform. We do not expect you to be an expert in everything on day one, but you should bring deep expertise in at least one core technical domain and strong architectural judgment across the others. - Backend and API systems: Design high-throughput, reliable services in Go, Python and Rust. Build API surfaces that expose relational intelligence safely and clearly. - Infrastructure and cloud: Strengthen production infrastructure across Kubernetes, GCP, AWS, observability, incident response, deployment workflows, and CI/CD. - Data and ML platform: Improve the systems that connect customer data, Avra’s knowledge graph assets, model outputs, and downstream enterprise workflows. - MLOps and inference: Scale model serving and batch inference. Improve model versioning, aliases, challenger and shadow deployments, rollback, monitoring, and customer-specific deployments. - Research and graph infrastructure: Build clean interfaces around internal systems such as graph training, sampling, embeddings, and feature pipelines so research components can become reliable production capabilities. - Engineering quality: Improve testing strategy, code review standards, operational readiness, technical design quality, and the way engineers reason about tradeoffs. - Technical mentorship: Help senior and mid-level engineers grow through design reviews, pairing, code reviews, clear written feedback, and pragmatic technical leadership. THE PROBLEMS YOU’LL HELP SOLVE - How should customer-specific models, data, and deployments be isolated while sharing common platform infrastructure? - How do we make batch inference, online inference, and model versioning feel like one coherent system? - How do we expose powerful relational intelligence through simple APIs and operationally safe customer workflows? - How do we keep systems debuggable when outputs depend on customer data, graph features, embeddings, model versions, and downstream integrations? - How do we help research move faster witho
HOUSE AD991,236 openings. Erioun finds yours.Scored against your own profile, every hour.Try the radar →