Company
Saildrone
Annual salary
$144k – $300k/yr
Location
Alameda, CA
Listed
50d ago
- Experience:
- 5+ years
- Workplace:
- Hybrid in Alameda, CA, Saildrone's manufacturing and R&D headquarters. Expect regular on-site collaboration with the autonomy and simulation teams.
- Equity:
- Equity
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.
Hybrid in Alameda, 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.
What you'll do
- Build and maintain production-quality simulation, replay, resimulation, and evaluation infrastructure for Saildrone's autonomous maritime systems
- Connect recorded vehicle data, simulated environments, and production autonomy software into repeatable, automated test workflows
- Develop open-loop and closed-loop testing frameworks for validating autonomous behavior at scale
- Design quantitative metrics, evaluation pipelines, and regression tests that catch issues before they reach the field
- Turn real-world failures and edge cases into repeatable scenarios and automated tests, closing the loop between operations and development
- Analyze logs, telemetry, simulation results, and test failures to identify root causes and drive fixes
- Partner with simulation users across teams to understand pain points in scenario definitions and maintenance, then propose and implement solutions
- Integrate simulation and evaluation tooling into the software development lifecycle and CI/CD pipelines
What you need
- We need a strong C++ software engineer with experience building simulation, replay, or robotics testing infrastructure for autonomous systems. You should be comfortable working across the full stack of simulation tooling, from scenario generation to evaluation pipelines, and have a track record of building production-quality infrastructure that other engineers rely on daily. Bonus points if you have hands-on experience with autonomous vehicles, robotics, or aerospace systems.
Common questions
How do I apply for the Software Engineer, Simulation & Evaluation (US) role at Saildrone? +
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 Saildrone role pay? +
The listing gives $144k – $300k/yr.
Is this role remote? +
The listing gives the location as Alameda, CA. Hybrid in Alameda, CA, Saildrone's manufacturing and R&D headquarters. Expect regular on-site collaboration with the autonomy and simulation teams.
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 →