Open Roles ℹ️ Our Hiring Process F.A.Qs Selected Blog Posts📽️  Product videos

About Us

At iterative.ai, we build open-source tools for machine learning DVC (10k+ ⭐  on GitHub), CML (3k+ ⭐ on GitHub), and enterprise-grade data infrastructure solutions. We also offer a team collaboration SaaS solution - Studio. We're a well-funded (Series A), remote-first team (50+ employees) on a mission to solve the complexities of managing datasets, ML infrastructure, ML models lifecycle, and other ML & data-centric workflows.

We value great collaboration and communication skills, both among internal teams and in how we interact with our users. We take care to balance and be responsive to the needs of our open source community as well as our enterprise customers.

Check us out in other places:

🖥 Website 📂  Docs 👾: GitHub 🖊  Blog ⏯️  YouTube 💬 Discord

👩‍💻 Culture - We take care of our people

ℹ️ Our Hiring Process

We will go over the process with you in the Introductory call to make sure it is clear and you know what to expect.

Here is the full interview process you can expect - It’s our go-to for most positions:

  1. 🤙  Introductory call [~1h]
  2. 👨‍🏫  Tech call with a team member [~45m]
  3. 👩🏾‍💻  Take-home coding task [real-world, asynchronous] - We pay for your time! See this FAQ.
  4. 🦾  Task summary / retro call [Optional, ~1h]
  5. ✏️ Offer

👏 Perks & Benefits

Open Roles

F.A.Qs

How do I get in touch / where to apply?

We were doing the “email us to this address” for a while now. But it was hard to keep up with all the approaches. Please see application link in the job description and use those - they will direct you to application form which will go into our systems so we won’t miss your application

Where are you located?

We are a fully distributed startup. This means, that while we have our HQ registered in San Francisco, CA - the engineers and members are working from their homes (or… wherever!) all around the globe 🌏.. Our office is virtual - our GitHub, Slack, Notion, etc.

We are going to some length to build our virtual community (donut meetings, virtual-coffees, friendly-chats, etc) - and, of course, are trying to organize real-world meetups when we can (company wide and otherwise), but our day-to-day interactions will always be remote-first and asynchronous-first.

If you really like working in a physical office, and meeting your co-workers daily - maybe this will not be the best fit for you, it’s not for everyone!

What is the day-to-day routine like (a.k.a how many meeting will I have to attend)?

As a 100% remote company, our practices and culture are to match - asynchronous communication first.

Most of our engineers have very light meeting loads and the general approach is to leave most of your schedule open and flexible for you to decide.