> OPEN_POSITIONS

Open positions

We read work before we read credentials. Every application starts with links: a repo, a package, a published model, a newsletter archive. A résumé is optional context. A degree is trivia. If your best argument for the role is something we can run, read, or verify, you are already ahead.

> SECTOR_01 · LOGISTICS

2 open roles

Supply Chain Risk Engineer

Route, port and corridor risk, mapped continuously. You'll build the pipelines that turn AIS feeds, port throughput data and corridor disruption signals into risk surfaces a client can act on before the chokepoint forms.

Show us: A data pipeline you've published, a graph or geospatial model in a public repo, anything that ingests messy real-world feeds and holds up.
Stack: Python, PostGIS or similar, streaming ingestion. Familiarity with maritime or freight data is a bonus, not a gate.

Geospatial Data Engineer

The map layer under everything Sector 01 does. Tile pipelines, satellite-derived features, change detection over ports and corridors.

Show us: Published geospatial work: an open dataset you've cleaned, a raster pipeline, a contribution to GDAL, rasterio, xarray or their neighbors.

> SECTOR_02 · DEFENSE

2 open roles

OSINT Analyst-Engineer

Open-source and sensor-derived assessments, independently verified. You'll fuse public imagery, flight and vessel tracking, and structured OSINT into assessments that carry a signature: every claim traces to a source and every assessment can be reproduced.

Show us: Published analysis under your name or handle: a Bellingcat-style investigation, a tracking project, a dataset with documented provenance. We care that your methods survive scrutiny in public.
Note: US-person status matters for some engagements. Tell us where you stand; it decides which engagements we can staff you on, and nothing more.

Verification Engineer

The "independently verified" half of the sector. You'll build the signing and reproduction layer: the machinery that lets a third party check our work without trusting us.

Show us: Cryptographic tooling in public. A signing implementation, a supply-chain security contribution (Sigstore, in-toto, the SLSA ecosystem), a CVE with your name on it.

> SECTOR_03 · FINANCE

1 open role

Quantitative Risk Engineer

Exposure you can see before it moves. Counterparty, market and infrastructure risk traced end to end. You'll build models where every finding is signed and every backtest regenerates from a commit hash.

Show us: Published quant work: a backtesting harness, a calibration study, a paper or preprint, a Kaggle history with real methodology. We will read your validation logic before anything else. Purged cross-validation done correctly says more than any title.

> SECTOR_04 · CLIMATE

1 open role

Climate Risk Modeler

Weather, water and energy stress modeled against real assets, on planning horizons of a quarter or a decade. You'll take climate model output and hydrological data down to the asset level and quantify what a client should actually plan for.

Show us: Published modeling work: a hazard model, a downscaling pipeline, contributions to the CMIP, xclim or climada ecosystem, a preprint. Uncertainty quantification handled honestly is the bar; point estimates dressed as forecasts are the failure mode.

> DISPATCH · RESEARCH

1 open role

Security Analyst/Journalist

Security analysis, published under your byline. You'll own SSX360 Dispatch and the Intelligence Log write-ups: recurring, technical, and readable by both an engineer and a risk officer. What moved, what it means, what our instruments saw.

Show us: An archive and an investigation. A Substack, a blog, a column, or a thread series with sustained readership, plus at least one piece of security analysis where the sourcing holds up. Writing samples beat pitches; an audience you built beats both.
Bonus: Enough technical literacy to read a repo and quote it correctly.

How we evaluate

No cover letters. No credential screens. Published work is the application.

01
Links first. We open your repos and publications before anything else.
02
Reproduce or verify. If we can run it, we will.
03
One conversation about the work, yours and ours.
04
Paid trial task scoped to a week, on real sector problems, before any offer.

Apply

Pick a role, or leave the default if none fits and your links argue for a seat anyway. We read everything that arrives with a working link in it.

A paid trial task scoped to a week sits between the conversation and any offer, so the strongest thing you can send is work we can run today. All roles are remote-first and begin in Q4 2026.