Senior Frontend Engineer (Full-Stack Capable) at Orkes
In Office - Santa Clara, CA
$180,000–$240,000from the description
Aug 2, 2026
In Office - Santa Clara, CA
Sep 24, 2026
What this job asks for AI summary
This in-office Senior Frontend Engineer role at an AI workflow orchestration platform involves owning the architecture of a visual workflow builder (canvas/node-graph editor) and control-plane tooling used by enterprise clients and internal teams. The position requires deep React/TypeScript expertise, strong UX judgment, and the ability to shape frontend strategy across teams. Some backend exposure — particularly around API contracts and microservices — is expected.
Senior level · 7+ years · San Jose-Sunnyvale-Santa Clara, 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 2,400 people in the San Jose-Sunnyvale-Santa Clara, CA area plausibly meet what this posting asks for (software developers). range 1,800–3,100
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 $217,796 (middle half $177,469–$231,052). 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 Aug 4, 2026. It is a model, not a headcount.
Why we read it this way (5)
The '7+ years' figure is tied to the frontend architect requirement in the Must-haves section and is treated as the overall experience gate, not a per-technology demand.
The posting lists 'AI-coding experience' as a must-have but this names no specific tool or platform — it describes a working style rather than a concrete technology, so it is omitted from the skills list per extraction rules.
The must-haves also reference building complex UI (IDEs, node-graph/canvas editors, data-dense dashboards) and owning API contracts into microservices — these are scope/experience descriptors rather than named technologies and are therefore not emitted as skills.
Nice-to-haves include dev-tooling background (e.g. IDEs like Cursor or VS Code, low-code/no-code, graph-node tools) — these are framed as background context rather than named discrete technologies, so only the concrete named tools (Next.js, Java, Spring Boot, D3/Recharts/Tremor) are captured as preferred skills.
Compensation includes equity in addition to the stated base salary range, but the equity amount is unspecified.
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.