Front-End Engineer Real-Time 3D (React / Three.js)

Posted yesterday

intelixaiDetroit (MI)

SENIORITY

Senior

Apply

About the role

Front-End Engineer – Real-Time 3D (React / Three.js) Seattle, Palo Alto, Washington DC, NYC, or Denver · $135K–$200K + EquityYou will build the 3D command-and-control interface that operators use to detect, track, and intercept hostile drones over stadiums, airports, and military bases. Your code renders the live tactical picture and fires the response.
SUMMARY: Successful candidates will have deep React and shipped Three.js/WebGL in production. This role will suit a mid-level software engineer who has already shipped real-time 3D in the browser. This role owns the operator interface on a newly formed engineering team. You render live, streaming sensor data as a real-time 3D picture in React and Three.js, and build the interactions an operator uses to act on what they see.
REQUIREMENTS: Production experience with React and TypeScript, and strong computer-science fundamentals. Write production React to a high standard, and be ready to demonstrate it in a live React coding assessment. Ability to keep complex scenes fast while their contents change constantly, and work comfortably across the browser and the services feeding it. Work through a live React coding assessment covering components, state and the DOM, alongside core data structures and algorithms. Shipped work in Three.js or WebGL.Experience rendering real-time or streaming data over websockets.
THE ROLE: You build the interface operators use to understand and act on a live tactical picture, in React and Three.js. Sensor data streams in continuously, and your work turns it into a real-time 3D scene that stays responsive as the data changes. You build direct interactions on the scene, from reclassifying a contact to handing off to the right response. You work end to end, across the React front end and the services and APIs behind it. The software runs across cloud, on-premise and edge hardware, so you see your work in real environments. You travel to deployment sites between 25% and 75% of the time, depending on the work.
SUPER NICE TO HAVE: Experience with real-time or streaming data pipelines and websockets. Geospatial, mapping or telemetry visualisation. Docker and Kubernetes. Comfort dropping into Python or Rust near the data layer. A record of passing rigorous engineering interviews, competitive programming, or open-source work in systems or data structures. Engineers from real-time data, trading, observability, mapping, geospatial or game-engine tooling backgrounds, who build in React and render live data, are welcome to apply.

Before you apply

Applying takes about a minute. These four things decide how fast it moves after that.

Your profile is current

It's what we read first. Occupations, seniority and locations matter more than a long history.

Two examples you can talk through

Not a portfolio — just two pieces of work where you can explain the decisions and what you'd change.

A number in mind

What you're on now and what would make you move. We negotiate better when we know both.

Your notice period

Employers plan around it, and it's the question that stalls offers most often.

Once you apply, someone reads it and calls you before anything reaches the employer — usually within two working days.

More like this