Robotics Forward Deployed Engineer

The Role

We're looking for a technically credible, customer‑oriented engineer to own a portfolio of customer sites running Tutor robots in production. You'll be the primary partner for each of your sites — the person their operations, engineering, and maintenance teams call first when something matters — and you'll be accountable for the operational and technical success of those deployments over time.

This isn't a traditional customer success role, and it isn't core product engineering. You won't own the product roadmap or build new robotic capabilities — that's R&D. But you will write code: the scripts, tooling, dashboards, and playbook logic that turn today's manual interventions into things that run themselves. The point of the job is to make your sites need you less over time, and to solve the hard, multi‑factor problems that no playbook covers yet.

You'll develop deep working knowledge of how our robots actually behave in the real world, diagnose issues across software, mechanical, and process dimensions, and partner with engineering to drive the deeper fixes — bringing the field context, prioritization, and validation that makes those fixes right.

The role is also genuinely relationship‑driven. The customers in your portfolio will know you, trust you, and rely on you. You'll spend real time on‑site at your facilities, remote time on diagnosis, tuning, and building, and ongoing time partnering with your customers' engineering and operations leaders. Your insights from the field will directly shape our product roadmap. This role sits at the intersection of robotics, operations, and customer partnership — and the right person is energized by all three.

• Own a portfolio of customer sites end‑to‑end: be the primary technical partner for each, build deep trust with their operations, engineering, and maintenance teams, and be accountable for the operational and technical success of those deployments.
• Automate yourself out of the repetitive work. Convert recurring manual interventions into tooling, scripts, and playbooks that your customers and our remote team can run without you. The fleet grows; your manual workload shouldn't. This is the core of the job, not a side effect.
• Develop deep working knowledge of our robot systems — software, hardware, and operational characteristics — sufficient to diagnose issues credibly and build real solutions at the boundary of the product.
• Diagnose and resolve ambiguous, multi‑factor issues in real‑world environments — across software configuration, mechanical adjustment, process change, and root‑cause analysis — and own the ones with no playbook yet.
• Partner with engineering on the deeper fixes: package high‑confidence cases with repro conditions, logs, and a likely root cause, and bring field validation rather than just a complaint.
• Track the health and performance of your fleet — uptime, reliability, throughput, customer satisfaction — and act proactively on early signals.
• Be the voice of your customers in our internal roadmap conversations; translate field reality into structured product insight.
• Partner with Account Executives on expansion conversations, where operational success creates natural openings for growth.

You clear a real technical floor, and then we select hard on judgment and people skills. Both halves matter; the second is what we weight most.

The technical floor (pass/fail):

• 3–7+ years in a technical, ideally customer‑facing role: applications/field engineering, robotics deployment, solutions engineering, technical account management, or similar.
• Technical depth in at least one of: robotics, industrial automation, controls, mechatronics, manufacturing systems, or warehouse/logistics technology.
• Comfortable working hands‑on with both software and physical systems in messy operational environments. You can read logs and telemetry, reason about a system you didn't build, and write the scripts/tooling to automate a manual process — you don't need to have built the robot from scratch.

What we actually rank on:

• Thrives in ambiguity — can take a vague, half‑described, multi‑factor problem with no clear owner and drive it to…