Senior Systems Integration Engineer (Hardware-in-the-Loop) (US)
Atoms • San Francisco, CA
Company
Atoms
Annual salary
$180k – $230k/yr
Location
San Francisco, CA
Listed
18d ago
- Experience:
- 4 to 6 years
- Workplace:
- 5 days in-office, SoMa, San Francisco (former Cruise HQ)
- Equity:
- Competitive 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.
On-site in San Francisco, 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 Senior Systems Integration Engineer with 4+ years of experience to build and own the hardware-in-the-loop (HIL) benches that test our autonomy stack off-vehicle. We want a hands-on, lab-first builder who has built and debugged test benches for AV or robotics systems and has worked directly with lidar, radar and cameras. An EE background is preferred. As Atoms Transport scales autonomy into existing OEM vehicles, you will make sure every software change is proven on a reliable, production-grade bench before it reaches the fleet.
What will you be doing?
- Designing, building and commissioning HIL test racks that bring together compute, vehicle interfaces, harnesses, wiring and sensors, from the first architecture to a finished, documented bench.
- Owning the benches end to end once they are running, and keeping them stable inside CI/CD. Your main measure of success is bench uptime.
- Simulating the vehicle systems that are not on the bench (CAN, CAN FD and Automotive Ethernet traffic, power and drive-by-wire states) and replaying recorded sensor data so that on-road events become repeatable bench tests.
- Leading root-cause debugging of system-level failures across lidar, radar, cameras, sensor timing, harnessing and compute, then turning what you find into design fixes.
- Continually improving bench tooling and automation, and writing clear documentation so the autonomy, embedded and vehicle teams can use and troubleshoot the benches on their own.
Common questions
How do I apply for the Senior Systems Integration Engineer (Hardware-in-the-Loop) (US) role at Atoms? +
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 Atoms role pay? +
The listing gives $180k – $230k/yr.
Is this role remote? +
The listing gives the location as San Francisco, CA. 5 days in-office, SoMa, San Francisco (former Cruise HQ).
Systems Engineer interview prep
Questions Systems Engineer interviewers often ask. They aren't taken from this listing.
How do you decide between round-robin and least-connections load balancing for a given service?
I use round-robin when requests are roughly uniform in processing time, and least-connections when request duration varies significantly, since round-robin can overload a server handling several slow requests while it keeps receiving new ones at the same rate as faster servers.
What's your process for diagnosing intermittent network latency that only occurs under peak load?
I check for saturation on specific links or interfaces during the peak window using monitoring data, rather than testing during off-peak hours when the issue won't reproduce. I also look at whether the latency correlates with a specific service or is spread across the network, which points to either an application issue or a capacity issue.
How do you approach capacity planning for network infrastructure that needs to support future growth?
I project growth based on historical trend data combined with known upcoming initiatives, and I build in headroom above the projection since infrastructure upgrades often have long lead times. I avoid provisioning purely for current load, since that leaves no margin for unexpected spikes or faster-than-projected growth.
What steps do you take to ensure a load balancer configuration change doesn't cause an outage during deployment?
I test the configuration change in a staging environment that mirrors production traffic patterns first, and I roll out changes gradually, shifting a small percentage of traffic before a full cutover. I also keep the previous configuration ready to roll back to quickly if something unexpected happens.
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 →