Senior Frontend Engineer at Weave
CA
$175,000–$225,000from the description
Jul 1, 2026
CA
Jul 21, 2026
What this job asks for AI summary
A senior frontend role focused on building a collaborative document editing platform for drug development workflows. The core technical challenge is architecting real-time, multiplayer document editing — including conflict resolution and presence features — using React and TypeScript. The position suits an experienced engineer with strong product instincts who has worked in small, early-stage environments and is comfortable driving technical decisions independently.
Senior level · 5+ 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 5,600 people in the San Francisco-Oakland-Berkeley, CA area plausibly meet what this posting asks for (software developers). range 2,900–7,200
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). This posting is about at that midpoint.
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 5+ years requirement is stated at the role level tied to React and TypeScript together ('5+ years of production experience building modern web applications with React, TypeScript…'), so it is captured as both overall years minimum and on those individual skills.
Real-time collaborative editing (CRDTs, presence indicators, conflict resolution) is described as a core ownership area under 'What You'll Own' with architectural responsibility, making it a hard gate rather than a nice-to-have; CRDTs is the concrete named concept extracted.
Rich text editor experience (Slate, ProseMirror) and real-time collaboration libraries (Yjs, Liveblocks) appear explicitly under 'Nice to Have' and are marked preferred accordingly.
The role is hybrid in San Francisco (Tue/Wed/Thu in-office, Mon/Fri remote) — it is NOT fully remote.
AI-augmented tooling (Cursor, Claude) is called out as a required working style, but these are framed as workflow accelerators rather than gateable technical skills; no specific tool is hard-required, so they are omitted from the skills list to avoid inflating hard gates.
Startup experience (<50 people) is listed as a required attribute but names no specific technology, so it is not captured as a skill.
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.