Careers

Help data teams trust their data.

We are about 40 people, we ship every week, and we have four open roles. These roles are examples for this demonstration site and are not real vacancies.

Open roles

Senior Backend Engineer, Ingestion

Engineering Remote, between UTC minus 8 and UTC plus 2 Full time $165,000 to $205,000 plus equity

Build the services that read run events and warehouse metadata from our customers' systems, reliably and cheaply.

Read the full description

The role

Ingestion reads about 90 million run events a month from orchestrators, transformation tools and warehouses, and turns them into one consistent timeline. You will own parts of that path: collectors, queues, normalisation and the guarantees we give about ordering and duplicates.

What you will do

Design and ship collectors for new systems, from reading an API to handling its failure modes.
Make the event pipeline idempotent, observable and cheap to run as volume doubles.
Work with the lineage and alerting teams on the contracts between them.
Join the on-call rotation, which averages two pages a month.

What we are looking for

Five or more years building backend services, with Go or Rust in production.
Experience with queues or streaming systems and a clear view on exactly-once claims.
Comfort with SQL and with the warehouse and orchestration tools our customers use.
Clear written communication. We work asynchronously and write things down.

How to apply

Send a short note and a link to something you built to jobs@saas.phoenixcodes.org, with the role title in the subject. A person reads every application, and we reply within five working days.

Staff Frontend Engineer, Product

Engineering Remote, between UTC minus 8 and UTC plus 2 Full time $180,000 to $220,000 plus equity

Lead the front end of an application that draws large graphs and dense tables without feeling heavy.

Read the full description

The role

The Tidewater app shows pipelines, lineage graphs with thousands of nodes, and timelines with years of runs. It has to stay fast, accessible and calm. You will set the direction for how we build it.

What you will do

Own the architecture of the web app: data fetching, rendering large graphs, and the component system.
Raise the bar on accessibility and performance, with budgets that run in CI.
Pair with design on interaction details that make dense information readable.
Mentor engineers across the front end and review the work that matters most.

What we are looking for

Eight or more years in front end work, with TypeScript and React at scale.
Experience with canvas or SVG rendering, virtualised lists or graph layouts.
A habit of measuring: you reach for a profile before you reach for a fix.
Experience leading without a title, through writing and example.

How to apply

Send a short note and a link to something you built to jobs@saas.phoenixcodes.org, with the role title in the subject. A person reads every application, and we reply within five working days.

Solutions Engineer

Customer Remote, United States or Canada Full time $140,000 to $175,000 plus commission

Help data teams see their own pipelines in Tidewater during a demo, then through their first week.

Read the full description

The role

You are the technical person on calls with prospective customers. You connect a demo workspace to a messy sample warehouse, listen to the problem the team has, and show the shortest path from that problem to a useful alert.

What you will do

Run product demos and technical evaluations for data platform teams.
Answer security and architecture questions, with help from our security team.
Write scripts and sample configuration that make evaluations quicker.
Feed what you hear back to product and engineering every week.

What we are looking for

Three or more years as a data engineer, analytics engineer or solutions engineer.
Working knowledge of Airflow or Dagster, dbt and at least one cloud warehouse.
The ability to explain a technical idea to a data lead and to a finance director.
Honesty about what the product does not do yet.

How to apply

Send a short note and a link to something you built to jobs@saas.phoenixcodes.org, with the role title in the subject. A person reads every application, and we reply within five working days.

Technical Writer, Documentation

Documentation Remote, anywhere in Europe or the Americas Full time $120,000 to $150,000 plus equity

Own the quickstart, the concepts guide and the API reference that thousands of engineers read each month.

Read the full description

The role

Our documentation is part of the product. Most people meet Tidewater first through the quickstart, and most support questions are answered by a page. You will make those pages accurate, short and kind to read.

What you will do

Keep the quickstart working: you run it on a clean machine every release.
Write and edit guides, the concepts page and the API reference with the engineers who built the feature.
Review pull requests that change behaviour and ask for the matching documentation.
Look at search queries and support threads, and fix the pages that fail people.

What we are looking for

Three or more years writing developer documentation.
Enough engineering skill to run the code you document and read an OpenAPI file.
A plain, specific style, and opinions about examples.
Experience with docs as code: Markdown, Git and review.

How to apply

Send a short note and two writing samples to jobs@saas.phoenixcodes.org, with the role title in the subject. A person reads every application, and we reply within five working days.

Working here

What it is like.

Remote first

No office to be near. Core hours overlap four hours a day, and the rest is yours.

Time off that is used

25 days of leave, a company-wide week off in late December, and managers who take theirs.

Written down

Decisions live in short documents, so people in every time zone can read, comment and decide.

Looked after

Health cover, a learning budget and a home office budget, the same for every employee.

Do not see your role?

We read every note. Tell us what you would build and why, and we will keep it for when a role opens.

Write to us Read the blog