03Hiring process

Five steps.
No funnel.

Our process is short and direct. One application, a conversation, a technical deep-dive, an onsite, and a decision. We aim to move from first contact to offer in four to six weeks, faster when schedules allow. You will always hear back — yes or no, with a reason.

03.1The steps
01Application

You send a direct, technical message — what you've built, what you want to build, and why here. No cover-letter theater. We read every one.

~Days
02Conversation

A 30-minute call with a team member. We tell you what we're building; you tell us what you're looking for. Both sides check fit.

~1 week
03Technical deep-dive

A working session with the team — on real problems, not brainteasers. For engineering roles this is often a practical exercise with our stack or hardware.

~1–2 weeks
04Onsite

A day at the lab in Los Angeles. You meet the people, see the hardware, and we dig into how you think and work together.

~1 week
05Decision

We move fast once we know. You hear a clear yes or no, with honest feedback, usually within a few days of the onsite.

~Days
03.2What we look for
    You have built and shipped real things — hardware, software, or systems that left the bench.
    You reason from first principles and are comfortable being wrong in public.
    You take ownership past your title and care about the outcome, not the credit.
    You want to work on hard problems with a long horizon and no shortcut.
03.3Tips for your application

Be specific

Tell us what you actually did on a project, not the project's marketing. Details beat adjectives.

Show the work

Links to repos, write-ups, builds, or field footage are welcome and read carefully.

Tell us why

Why this, why now. We want people who chose us on purpose.

Ask us anything

The conversation is two-way. We expect you to interview us too.

Ready when you are.

Start with a role, or send an open application. Either way, a person reads it.