> Markdown version of [/jobs/ext/4649367-staff-frontend-engineer-systems](https://www.wearedevelopers.com/jobs/ext/4649367-staff-frontend-engineer-systems). Every page supports `.md` or `Accept: text/markdown`. Links point to the HTML versions so they work for humans too. Agent guide: [/agents.md](https://www.wearedevelopers.com/agents.md).

---

# Staff Frontend Engineer, Systems

- **Company:** Sift
- **Location:** Long Beach, CA, United States
- **Experience:** Expert
- **Salary:** $200,000 - $250,000
- **Contract:** Permanent contract
- **Skills:** Application Programming Interfaces (APIs), Artificial Intelligence, Apache HTTP Server, Systems Engineering, Data Files, Serialization, Programming Tools, File Systems, Protocol Buffers, Design of User Interfaces, Human-Computer Interaction, Performance Tuning, Scientific Computating, Software Construction, TypeScript, Web Applications, WebGL, Parquet, Data Processing, Multithreading, ReactJS, Caching, Data Management, Front End Software Development, Data Pipelines
- **Published:** November 9, 2026
- **Apply:** https://www.careerbuilder.com/job-details/staff-frontend-engineer-systems-marina-del-rey-ca--d60c277c-34c8-41b0-9759-8a1e51abdd16

## About the Role

User Interface/Experience (UI/UX), Systems Engineering, Telemetry, Artificial Intelligence (AI), Data Sets, Apache, Internet Application, Data Management, File Systems, Caching, * 7+ years building software for the web, with meaningful experience pushing browsers beyond their comfort zone, whether that's performance optimization, binary data processing, GPU rendering, multi-threaded architectures, or something else that required understanding the platform deeply

 * Strong TypeScript skills and comfort working in a React codebase, but your value isn't in knowing React APIs. It's in knowing when React is the wrong tool for the job and what to reach for instead
 * Systems-level intuition: you think about memory layout, thread coordination, caching strategies, and data serialization formats, not just component hierarchies
 * Experience building for correctness under constraint. You've worked on software where bugs have real consequences, or you've built systems where data fidelity and performance couldn't be traded off against each other

Bonus Points:

 * Experience with GPU-accelerated rendering in the browser (WebGL, WebGPU, Canvas 2D optimizations) or technical visualization at scale (D3, ECharts, custom renderers)
 * Hands-on work with binary data formats (Arrow, Parquet, protobuf, FlatBuffers) or columnar data processing
 * Background in Web Workers, SharedArrayBuffer, OPFS, or other browser threading/storage APIs- Experience in domains where data correctness is non-negotiable: aerospace, scientific computing, medical devices, financial systems, or similar
 * Projects where you had to build infrastructure that didn't exist yet, like custom caching layers, data processing pipelines, rendering engines, or developer tools