About Watershed
Watershed is a software platform for running a world-class climate program. We measure our success in the carbon reduction achievements of our customers. We are looking for team members who love product-building, want to work hard at a mission-oriented startup, and will collaborate with us in shaping the culture of a growing team.
We have offices in San Francisco, New York and London and remote team members across the US and Europe. We hope that you’ll be interested in joining us!
The role
We are looking for a team member who is excited to do everything involved in shipping great products, including hands-on engineering, talking with customers, mastering the climate domain, and setting direction for the company. You will be joining as an early member of the team that will shape everything that comes next at Watershed. Your past experience should include a track record of building things that users love.
Watershed’s technical stack is the web frontend that our customers use, together with a backend of climate data, climate models, and plug-ins to various financial systems. We build new products in a customer-first way so you’ll be working quite a bit in React, TypeScript, CSS, Node.js, etc. There’s no need to be a prior expert in our stack — it’s more important that you’re good at picking up technologies quickly.
Some traits that are important to our company culture: customer-obsessed, outcome-oriented, and inclusive. And we’re looking for owners, so we hope you’ll help us evolve this list.
FAQ
Where does Watershed work?
We have hub offices in San Francisco, New York and London, and some remote team members in the US and EU. Most of our jobs need to be in San Francisco / New York / London, but certain jobs are open to being remote and will be specifically noted on the jobs page and in the job description.
What’s the interview process like?
It starts the same for every candidate: getting to know the team members through 1 to 2 conversations about Watershed, your experience, and your interests. Next steps can vary by role, but usual next steps are a skill or experience screen (e.g. a coding interview for an engineer, a portfolio review for a designer, deeper experience call for other roles) which leads to a virtual or in person interview panel after that if the screens go well. We prioritize transparency and lack of surprise throughout the process.
