A small team of engineers. You read real maps with customers, ship small changes and log off on time.

roles open, Portside or remote. Pay shown on every one.
Every role shows its pay range, and every applicant gets a reply from a person. Sample ranges.
What you will do
What you bring
What you will do
What you bring
What you will do
What you bring
What you will do
What you bring

If a path needs a glossary, it goes back. The person reading the map may not be the person who built the cloud.
We only ever hold read-only access. Changes go through a pull request that the customer merges.
A second engineer checks every new rule before it reaches a customer map.
In a customer channel, "I have not confirmed that yet" is a good answer.
working days is yours for research. Publish it, ship it or bin it. Nobody books a customer call that day.
Annual leave | 30 days |
Learning budget, each year | $4,000 |
Exam fees, retakes included | Paid |
Conferences, each year | 2 |
Out-of-hours pages | 0 |
Health cover, family included | 100% |
A short email and one piece of your writing. No cover letter needed.
Thirty minutes with an engineer from the team you would join.
One paid day on a sample cloud we built, with a short write-up at the end.
You walk two of us through what you found, as you would with a customer.
No whiteboard riddles and no unpaid homework. You do the work we actually do, at a day rate.
A written offer, or written feedback you can use.

Not on the list above? Send us something you built or wrote. We read all of them.