Senior Software Engineer, AI-Augmented Development

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. The Role Something has changed. A year ago you wrote code by hand — and you were good at it. Then you started using Claude Code, Cursor, or similar tools and realized the game had fundamentally shifted. Now LLMs write the vast majority of your code, and you're producing more, better software than ever before. You didn't just try these tools — you went all in. We're looking for a senior software engineer who has lived through this transition and come out the other side more productive, not less rigorous. Someone who understands that AI-augmented development isn't about generating slop — it's about a skilled engineer leveraging a force multiplier to ship things that used to take a team of five. At Tutor, you'll build the distributed infrastructure, cloud services, user interfaces, and developer tooling that power intelligent robots in real factories. Your code ships to real robots that pick real things in real warehouses — not another SaaS dashboard. You'll work across the stack — backend services, frontends, CI/CD, ML pipelines, data systems — wherever the highest-leverage work is on any given day. Robotics experience is not required. Strong engineering judgment is. But if you've ever wanted to watch a robot do something because of code you wrote that morning, this is the job. What You'll Do Architect and build core software systems across backend services, cloud infrastructure, internal tools, and user-facing applications Ship fast by combining your own engineering expertise with LLM-based development workflows — and help the rest of the team do the same Own problems end-to-end: scope them, build them, deploy them, and keep them running in production Work directly with robotics engineers, ML engineers, and operations to understand what's needed and deliver it See your work come to life on physical robots — debug a deployment in the morning, watch it run on the factory floor in the afternoon Identify and eliminate bottlenecks in how the team builds, tests, and deploys software You You were a strong software engineer before LLMs entered the picture. You have deep fundamentals — you understand systems design, debugging, performance, and how to write code that doesn't fall over in production. You've gone deep on AI-augmented development. Claude Code, Cursor, Copilot, aider — you've used one or more of these tools extensively and have strong opinions about how to use them well. You can articulate what works, what doesn't, and why a human in the loop still matters. You are pragmatic and fast. You'd rather ship something that works today than design the perfect abstraction for next quarter. You have good instincts for when to be careful and when to move. You are multidisciplinary. You don't hide behind a title. If the highest-value thing to do is write a React frontend, set up a Kubernetes cluster, or debug a data pipeline, you do it. You have 5+ years of professional software engineering experience, with meaningful work in Python. You are excited about working on-site with a small, intense team building physical products that operate in the real world. You think robots are cool — and you want to be the reason they get cooler. 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.

{
  "content_hash": "50473be877f5892f303f3de0658fd4f17c95b59d22f5f7d00e39b867e3e0244f",
  "source_hash": "759c60b3a16482f8318e6a596265ee45130c1c154278518bdac383e892bdba14",
  "last_changed_at": "2026-06-02T10:45:38.487Z",
  "active_status": "active"
}

{
  "language": "en",
  "location": {
    "raw": "Watertown, MA",
    "city": "Watertown",
    "region": "MA",
    "country": "United States",
    "is_remote": false,
    "confidence": 0.9
  },
  "salary_max": 190000,
  "salary_min": 140000,
  "inferred_at": "2026-06-18T07:57:31.247Z",
  "launch_scope": {
    "reason": "english_us_canada",
    "included": true,
    "language": "en",
    "location": {
      "raw": "Watertown, MA",
      "city": "Watertown",
      "region": "MA",
      "country": "United States",
      "is_remote": false,
      "confidence": 0.9
    },
    "countries": [
      "United States"
    ]
  },
  "remote_policy": null,
  "salary_period": "year",
  "workplace_type": "on_site",
  "salary_currency": "USD"
}

{}

{
  "lists": [
    {
      "text": "What You'll Do",
      "content": "\n<li>Architect and build core software systems across backend services, cloud infrastructure, internal tools, and user-facing applications</li>\n<li>Ship fast by combining your own engineering expertise with LLM-based development workflows — and help the rest of the team do the same</li>\n<li>Own problems end-to-end: scope them, build them, deploy them, and keep them running in production</li>\n<li>Work directly with robotics engineers, ML engineers, and operations to understand what's needed and deliver it</li>\n<li>See your work come to life on physical robots — debug a deployment in the morning, watch it run on the factory floor in the afternoon</li>\n<li>Identify and eliminate bottlenecks in how the team builds, tests, and deploys software</li>\n"
    },
    {
      "text": "You",
      "content": "\n<li>You were a strong software engineer before LLMs entered the picture. You have deep fundamentals — you understand systems design, debugging, performance, and how to write code that doesn't fall over in production.</li>\n<li>You've gone deep on AI-augmented development. Claude Code, Cursor, Copilot, aider — you've used one or more of these tools extensively and have strong opinions about how to use them well. You can articulate what works, what doesn't, and why a human in the loop still matters.</li>\n<li>You are pragmatic and fast. You'd rather ship something that works today than design the perfect abstraction for next quarter. You have good instincts for when to be careful and when to move.</li>\n<li>You are multidisciplinary. You don't hide behind a title. If the highest-value thing to do is write a React frontend, set up a Kubernetes cluster, or debug a data pipeline, you do it.</li>\n<li>You have 5+ years of professional software engineering experience, with meaningful work in Python.</li>\n<li>You are excited about working on-site with a small, intense team building physical products that operate in the real world. You think robots are cool — and you want to be the reason they get cooler.</li>\n"
    },
    {
      "text": "About Our Roles & Titles",
      "content": "<div>\n<p>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&amp;D org holds the title <strong>Member of Technical Staff (MoTS)</strong>. 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.</p>\n<p>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.</p>\n</div>"
    }
  ],
  "country": "US",
  "createdAt": 1773162474160,
  "updatedAt": null,
  "categories": {
    "team": "R&D - Software",
    "location": "Watertown, MA",
    "commitment": "Full-time",
    "allLocations": [
      "Watertown, MA"
    ]
  },
  "salaryRange": {
    "max": 190000,
    "min": 140000,
    "currency": "USD",
    "interval": "per-year-salary"
  },
  "workplaceType": "onsite"
}