Frontend Engineer

About Sift

Sift is the data infrastructure platform for hardware engineering teams. Sift turns high-frequency telemetry into engineering insights for mission-critical systems. Teams use Sift to build and operate rockets, satellites, autonomous vehicles, energy systems, defense platforms, and more.

Founded by former SpaceX engineers who built the tools behind Dragon and Starlink, Sift is building the data infrastructure to herald the AI era for physical systems.

In This Role, You'll:

• Design and optimize data pipelines that run entirely in the browser: Web Workers processing Apache Arrow binary data, persistent caching in the Origin Private File System, and multi-layer invalidation strategies that keep the UI responsive while handling datasets that would crash most web apps.

• Build interactive visualizations for time-series telemetry, FFT frequency analysis, geographic mapping, and scatter plots, and many more, each with distinct performance profiles and correctness constraints. When your users are debugging flight hardware, a rendering inaccuracy is a mission-critical problem, not a cosmetic one.

• Solve performance problems that frameworks can't: bypassing React's render cycle for 60fps interactions, coordinating worker thread pools, managing memory across large binary buffers, and making architectural decisions about what belongs on the main thread vs. off it.

• Architect composable UI systems for technical users who need full data fidelity. Not simplified dashboards, but tools that expose the real complexity of hardware telemetry with zeptosecond level timestamp precision - Work across the stack boundary. Collaborate with backend engineers on API design, binary serialization formats, and query semantics for structured data endpoints.

The Skillset You'll Bring:

• 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