Senior Systems Engineer, Platform Requirements & Interfaces (US)
Atoms • San Francisco Bay Area
Company
Atoms
Annual salary
$182k – $240k/yr
Location
San Francisco Bay Area
Listed
18d ago
- Experience:
- 5+ years
- Workplace:
- 5 days in-office in SoMa, San Francisco
- 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 Bay Area.
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 Engineer, Platform Requirements & Interfaces with 5+ years of experience to own the requirements, interfaces, and verification plan for the autonomous vehicle platforms Atoms is bringing up across its Transport and Mining divisions. This is a priority (P0) hire. We need someone who has done hands-on AV hardware work with lidar, radar, cameras and vehicle networks like CAN, and who now wants to work at the planning and verification level. You will make sure the people doing hands-on work are building and testing the right things, at the right time, against the right requirements. The role sits inside an engineering-first company where engineers make the key calls, and it puts you on live autonomous systems integrated into OEM vehicles from Toyota, Hyundai, Komatsu and others.
What will you be doing?
- Writing and owning the system requirements and interface control documents (ICDs) for new vehicle platforms: sensors, compute, power, and vehicle networks such as CAN and Automotive Ethernet.
- Planning the integration and test work so the hands-on integration and test engineers know what to do, when to do it, and what it has to verify against.
- Reviewing and analyzing vehicle test results with the test team and deciding whether the vehicle system passes or fails. You will be checking the vehicle platform itself, not the autonomy software's behavior.
- Tracking verification coverage against the requirements, and working with the functional safety lead so testing meets ISO 26262-style safety requirements.
- Spending about 80, 90% of your time on documentation, planning and analysis, and the rest in the garage or running tests on vehicles when needed.
Common questions
How do I apply for the Senior Systems Engineer, Platform Requirements & Interfaces (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 $182k – $240k/yr.
Is this role remote? +
The listing gives the location as San Francisco Bay Area. 5 days in-office in SoMa, San Francisco.
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 →