Backend Engineer at Arena Intelligence, Inc.
CA
—
Jul 15, 2026
CA
Jul 21, 2026
What this job asks for AI summary
A backend engineering role focused on building the application layer of an AI evaluation platform — specifically the APIs, data systems, and enterprise-grade services (billing, multi-tenancy, authentication, RBAC) that sit above the core infrastructure. The work ranges from greenfield API design to scaling existing pipelines, and suits an experienced backend engineer comfortable with product-facing systems and ambiguous, fast-moving startup environments.
Senior level · 5+ years · Remote · Full-time
“or” means any one of them counts — you don't need all of them.
Posted 2 times — it's one opening, so apply once.
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 24,900 people nationally plausibly meet what this posting asks for (software developers). range 14,900–37,300
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.
What the occupation pays Median $138,970 (middle half $107,524–$175,762).
Estimated from BLS employment for this occupation and area, per-skill prevalence across our listing corpus, and published wage benchmarks — as of Jul 28, 2026. It is a model, not a headcount.
Why we read it this way (7)
Go is listed as the preferred backend language ('Go preferred') under the requirements section — it is a hard gate with the understanding that strong proficiency in a comparable modern backend language may be considered; no explicit alternatives are named in the JD.
PostgreSQL is called out by name as a hard requirement ('comfortable modeling, querying, and scaling Postgres'); Redis and message queues appear in the same sentence but framed as situational tools ('you know when to reach for'), so they are treated as preferred context rather than gates.
REST/API design is implicit throughout the requirements section as the core deliverable; no specific API framework is named.
RBAC, SSO, audit logs, and multi-tenancy appear under the 'Nice to Have' section, as does billing infrastructure (Stripe, Metronome, Orb) — all marked preferred accordingly.
LLM provider APIs (OpenAI, Anthropic, Google) and the modern AI stack (vLLM, LiteLLM, LangChain) are explicitly listed under 'Nice to Have'; vLLM is used as the primary name with LiteLLM and LangChain as alternatives since they appear together as a category.
No compensation figures are provided beyond a general statement that pay is competitive and location-dependent; no range is quoted.
Caller marked this a fully-remote role — scored against the national candidate pool.
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.