Careers

Come build

the map.

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

Engineer lit by a magenta graph on a screen, a server rack behind her
4

roles open, Portside or remote. Pay shown on every one.

§1   Open roles

Pick your part of the map.

Every role shows its pay range, and every applicant gets a reply from a person. Sample ranges.

Identity research engineerRemote  $128,000 to $156,000

What you will do

  • Read trust policies across AWS, Entra ID and Google Cloud
  • Write the rules that turn them into hops
  • Keep up when a provider changes how a role works

What you bring

  • Three years in cloud identity or security
  • Comfort with IAM policy at the line level
  • Clear, short writing
Reports to Hana Mori

Pipeline research engineerPortside or remote  $124,000 to $150,000

What you will do

  • Follow tokens from GitHub Actions and GitLab CI
  • Map what each deploy role can reach
  • Write the smallest change that breaks a path

What you bring

  • Three years of CI or platform work
  • Working Terraform
  • Patience with detail
Reports to Minh Tran

Customer engineerPortside or remote  $118,000 to $142,000

What you will do

  • Stay on hand while a first map runs
  • Read the map through with the team
  • Write first pull requests in Terraform

What you bring

  • Three years in cloud engineering
  • Calm in a shared channel
  • Plain writing for people outside security
Reports to Arjun Nair

Product designerPortside  $112,000 to $136,000

What you will do

  • Decide what the map shows first
  • Sit in on first-map calls every week
  • Remove more than you add

What you bring

  • Four years of product design
  • A data-heavy product you can talk through
  • Curiosity about how clouds fit together
Reports to Temi Adeyemi
Engineer's hands at a keyboard in front of a dark identity graph, a hardware security key on the desk
§2   How we work together

Half the jobis explaining.

Plain words

If a path needs a glossary, it goes back. The person reading the map may not be the person who built the cloud.

Read, never write

We only ever hold read-only access. Changes go through a pull request that the customer merges.

Two sets of eyes

A second engineer checks every new rule before it reaches a customer map.

Say what you do not know

In a customer channel, "I have not confirmed that yet" is a good answer.

§3   Benefits

1 in 5

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%

Sample figures.
§4   How we hire

Twelve days,start to offer.

Day 0

Apply

A short email and one piece of your writing. No cover letter needed.

Day 2

Talk

Thirty minutes with an engineer from the team you would join.

Day 5

Lab

One paid day on a sample cloud we built, with a short write-up at the end.

Day 9

Read-out

You walk two of us through what you found, as you would with a customer.

No puzzles

No whiteboard riddles and no unpaid homework. You do the work we actually do, at a day rate.

Day 12

Offer

A written offer, or written feedback you can use.

Two cloud engineers at a dark wall display, one pointing at a magenta branch of a storage graph
Day 1

You sit in on a first map in week one.

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