The Company
We believe general-purpose, generally-intelligent robots will be built in our lifetimes. Robots will work in our factories, move our goods, walk on our streets and eventually be in our homes. To build that future, research and deployment must work in lockstep: real-world operation must make the technology better and better technology must make deployment easier. We're looking for the thinkers, builders, and researchers who want to be part of that loop.
As an AI robotics company that deploys its inventions directly into the facilities that need them, on state-of-the-art hardware, every line of code written at Tutor has a direct impact on the global, physical economy.
Our Culture
We believe that something truly special can happen when talented, motivated people work together; at Tutor, every member of our team is empowered to have real impact in everything that they do. We're characterized by both technical excellence and next-level collaboration and respect.
About the Role
At Tutor, AI agents do most of the engineering work. They write the code, run the tests, triage CI, deploy to robots, and operate the tools the company runs on. That only works if the infrastructure underneath them is built for it: environments they can stand up, systems they can observe, tooling they can call, context they can read. We are looking for the person who will lead the team that builds and supports that infrastructure.
The people who use this infrastructure are the engineers sitting next to you, and they do not file tickets and wait. When something in the commons breaks or gets in their way, they are on it immediately, often with an agent, and they expect you and your team to be there with them. That is the culture you would be joining and leading: users who operate what they use, and a central team that makes that possible rather than standing between them and the systems.
You are responsible for the commons serving the whole. Shared infrastructure at Tutor is used by every team, and every team pulls it in its own direction. Your job is to keep it working for all of them: to decide what the center owns and what stays with the teams, to make the call when two teams need different things, and to be the accountable person when the shared layer fails.
This is a senior role with organization-wide scope, and you set the direction for the function. We expect you to be hands-on. How much you build yourself and how much you lead others will depend on who you are, and the team grows as the work requires it, with you hiring it.
What You'll Do
- Lead the team that builds the infrastructure agents run on: Environments, tooling, observability, and context, designed for agents first and for the humans directing them
- Keep the commons serving the whole: Decide what the central team owns and what each team owns, make the call when teams need different things from a shared system, and write the decisions down so they hold
- Be the accountable person when the shared layer fails: Production, CI, security, compliance. Make sure a problem reaches the right hands within the hour, and take the ones that are yours
- Work alongside the engineers who use what you build: They will be on a problem the moment it appears. Be there with them, and fix the cause rather than the report
- Build the team: Hire senior engineers, grow the team only as fast as the work requires, and set the direction for how a small team and a fleet of agents cover a large surface
What We're Looking For
- 10+ years in infrastructure, platform, or systems engineering, including several leading a team or a function: You have owned shared infrastructure that a whole engineering organization depended on
- You have built for AI agents, not only with them: You have shaped environments, tooling, or workflows so that agents could do real engineering work, and you have opinions about what that takes
- You have been accountable for production: On-call, incident response, and the postmortems that followed, somewhere downtime cost something
- You lead by making others faster: Your platform work was adopted because it helped, and the people who used it came to you first when it didn't
- Comfortable with users who are also operators: You would rather engineers fix their own problems in your systems than route everything through you, and you build so they can
- Clear in writing: The decisions and standards you write are read and followed
Nice to Have
- Robotics, hardware, or another company where infrastructure includes machines in the field
- Experience as a first platform or first security lead at a growing company
- Experience building a small, senior team rather than a large one
About Our Roles & Titles
At Tutor, we believe great engineers and researchers are defined by what they build and the impact they have — not where they sit in an org chart or what title they have. Therefore, everyone in our R&D org holds the title Member of Technical Staff (MoTS). Our job postings use standard titles so you can find us, but if you join Tutor, you'll be a MoTS — with a level that is determined through the interview process.
That also means we hire people, not slots. Work at Tutor evolves every quarter, and we set the expectation of flexibility from day one — it's common for people to start on one thing and shift to another based on where the team needs them most. A high technical bar across the board is what makes that flexibility possible: it's what allows people to contribute meaningfully whatever problem they take on.
.jpg?1711044265){kind=logo}