Backend Engineer at Scanner
San Francisco, CA
—
Jul 25, 2026
San Francisco, CA
Jul 26, 2026
What this job asks for AI summary
A backend engineering role at an early-stage security data platform, focused on building product features and infrastructure for large-scale log search. Day-to-day work spans ingestion pipelines that pull log streams from cloud and SaaS sources, outbound integrations, and tooling that supports AI-driven investigations — all operating against hundreds of terabytes to petabytes of data daily. The stack is primarily Rust, with AWS services including Lambda, ECS, and S3.
Mid level · 3+ years · San Francisco-Oakland-Berkeley, CA · Full-time
“or” means any one of them counts — you don't need all of them.
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 4,300 people in the San Francisco-Oakland-Berkeley, CA area plausibly meet what this posting asks for (software developers). range 3,250–5,600
Applicant volume Heavy — This req sits in a large pool with little in its requirements to thin it, and auto-apply tools fire at everything in the occupation. Applying early and leading with the rare skills below is what gets read.
Most people in this occupation already list these. Still required — just not what gets you shortlisted.
What the occupation pays Median $190,744 (middle half $167,095–$224,501).
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 (6)
The role is titled 'Backend Engineer' with no level modifier; advertised seniority is Unspecified. The 3-year minimum and scope (feature delivery on a small early-stage team) support a Mid-level classification.
The backend language requirement lists Rust, Go, C/C++, Java, or Swift as acceptable options with a stated willingness to ramp into Rust — captured as a single required skill with alternatives rather than separate entries.
General familiarity with 'databases, database internals, and data pipelines/warehouses' is a stated requirement but names no specific technology beyond MySQL (which appears only in the stack narrative); 'databases' is captured as a required skill and MySQL as preferred from the stack section.
All technologies beyond the language and database familiarity requirements (Svelte, TypeScript, AWS Lambda, S3, MySQL, Amazon ECS, Pulumi) appear exclusively in the 'Our Tech Stack' narrative section and are marked preferred accordingly.
No compensation figures are stated beyond 'competitive salary, meaningful equity, and comprehensive benefits'; no numeric range to extract.
The posting says 'hybrid-friendly with regular in-person collaboration in San Francisco,' so remote=false.
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.