Recruitment is the work

LinkedIn doesn't find frequency hearers.

We built two recruitment instruments to surface the engineers, architects, and pattern recognizers we cannot find any other way. They test how you think — not what you've memorized. Score doesn't matter. Signal does.

61 puzzles
12 layers / shells
2 instruments
possible solutions

Why puzzle games

Resumes filter for what's been done. Puzzles surface how you think.

01

The right people don't apply

People we want already have jobs. They don't browse open roles. They don't update LinkedIn. They are the kind of pattern recognizers who, when shown an interesting problem, can't not think about it.

02

Resumes encode the wrong signal

Years at FAANG, framework name-drops, certifications. None of it predicts whether you can hold a six-axis mental model of a problem and find the move that resolves all six axes at once. We test that directly.

03

Two instruments, two signal types

PULSE rewards architects and mathematicians — outside-in pattern decomposition. Prime Radiant rewards orchestrators and systems engineers — tracing signal through a hierarchy. Most strong candidates do well at one. Exceptional ones at both.

04

The score is a side effect

We read the path: which puzzles you opened first, where you backtracked, what you tried before what worked. Tier matters less than trajectory. How you fail is more revealing than how you succeed.

The two instruments

Pick one. Or both. The signal is what you build inside them.

Who we hire

Builders. Pattern recognizers. People who can't not think about it.

We are a small team building a substantial system. Force OS is 248K lines of Rust written from scratch. STARHELM, SEAHELM, WATCHMAN, AOW, RESONANCE — five product surfaces in active production. We need people who carry their own weight, ship their own ideas, and read pattern across domains.

Frequency hearers

You read continuous-spectrum signal natively — in code, in systems, in conversations, in waveforms. You see ten things and feel which three matter.

System thinkers

You hold six axes of a problem in your head and find the move that resolves multiple at once. Not a planner — a pattern composer.

Builders, not narrators

You ship. You run things in production. You read your own logs at 2am. You don't write design docs about why the design doc should be written.

Multi-domain

Audio engineering. Naval doctrine. Federal procurement. Cryptography. Genetics. Geomagnetism. The cross-domain reader is the most valuable engineer at FORCE.

No passengers

Innovate ruthlessly. Move at war speed. Ship, don't show. The four values are load-bearing, not decorative.

Cleared or clearable

Force ships into cleared enclaves. We can sponsor clearance for the right person. US persons preferred for defense work.

The hiring frame

Roles, not slots.

We hire people, then shape roles around them. The roles below are direction, not job descriptions. If you finish either instrument and have a take on which one fits you, that's the start of the conversation.

Rust systems engineer

Force OS core, fleet orchestration runtime, deterministic replay, multi-model pipelines. You write the substrate the agents run on.

Strong on Prime Radiant

AI architect / researcher

RESONANCE — universal spectral tokenizer, cross-domain transfer architecture, frequency-domain foundation model. Pre-tokenization perception across 5 spectra.

Strong on PULSE

Defense product engineer

STARHELM, SEAHELM, AOW. C2 surfaces, protocol adapters, attribution engines, edge enclave deployments. Cleared or clearable.

Strong on either

Frontend / Dioxus / UE5

Force OS operator surface, UE5 command theater, public-facing recruitment surfaces. Visual systems that hold dense information without losing taste.

Strong on PULSE