Company
Actor
Annual salary
$190k – $250k/yr
Location
Mountain View, CA
Listed
39d ago
- Experience:
- 2 to 10 years
- Workplace:
- 5 days in-office in Mountain View, CA (up to 2 long-distance customer site trips per month; some weekend shop work; relocation support available)
- Equity:
- 1.5-3%
Open to people who live in the US, Canada or the UK
We can only put candidates forward for this role from those three countries for now. See the contract AI training jobs open in more countries.
On-site in Mountain View, CA.
Send us your LinkedIn and CV. If your experience fits, we'll introduce you to the recruiter filling this role.
Apply for a referral →The recruiter emails you before anything happens and may suggest other jobs that suit you better.
About this role
We are looking for a Deployed Software Engineer with 2+ years of experience to take Actor's robot models from the shop to real heavy machinery at quarries, mines and construction sites. You've worked with data and you've written code for real robots or vehicles, and you want to own hard problems end to end. With 150+ deployments live and only a small team, we need high-agency engineers who will build the data and autonomy infrastructure that makes operator-trained robot models useful in the field. This is a founding-team role in a fast, horizontal shop where everyone owns a problem.
What will you be doing?
Keeping our fleet of 150+ machine deployments healthy: debugging nodes that go down, digging through logs and working with on-site deployment staff to put out fires
Building reliable data infrastructure so no frames are lost, from machine capture and upload to the cloud, then on to labeling and model training pipelines
Managing the in-house and external labeling teams, and running evaluations on newly trained robot models
Writing robotics software that controls autonomous machines, and getting autonomy data into customer-facing portals and dashboards
Working from our Mountain View industrial shop, with up to 2 long-distance trips a month to deploy hardware and build autonomy solutions at customer sites
Common questions
How do I apply for the Deployed Software Engineer (Robotics) (US) role at Actor? +
Use the Apply for a referral button on this page to send us your LinkedIn and CV. If your experience fits, we'll introduce you to the recruiter filling this role. They'll email you to check you're interested, then put you forward for this job or others that suit you better. It's free.
What does this Actor role pay? +
The listing gives $190k – $250k/yr.
Is this role remote? +
The listing gives the location as Mountain View, CA. 5 days in-office in Mountain View, CA (up to 2 long-distance customer site trips per month; some weekend shop work; relocation support available).
Software Engineer interview prep
Questions Software Engineer interviewers often ask. They aren't taken from this listing.
How do you approach designing a system when the requirements are still likely to change?
I design around the parts of the problem I'm confident are stable, like the core data model, and keep the parts most likely to change, like specific business rules, isolated behind clear interfaces. Over-engineering flexibility everywhere just adds complexity to parts of the system that were never going to change.
What's your process for debugging an issue that only reproduces in production, not locally?
I add targeted logging around the suspected area and compare production data or configuration against my local setup, since an issue that's environment-specific usually traces back to a real difference between the two rather than a fundamentally different bug. I avoid making speculative changes without first confirming where the divergence is.
How do you decide when a piece of code needs a test versus when it's low-risk enough to skip?
I prioritize tests for logic with real business consequences if it breaks, or code that's likely to be touched again later by someone unfamiliar with it. Simple, rarely-changed glue code gets less coverage, since the cost of a thorough test there often exceeds the risk it's protecting against.
How do you evaluate a proposed technical solution's trade-offs, like performance versus maintainability?
I start from the actual constraint that matters for this specific system, whether that's genuinely performance-critical or whether maintainability is the bigger long-term cost, rather than defaulting to whichever trade-off I personally prefer. Optimizing for performance the system doesn't need just adds complexity nobody benefits from.
Related roles
Browse all referral roles
Salaried roles at startups, AI companies and established businesses, all filled by referral. One application covers every role.
See all referral roles →