Technical Lead - Autonomy Evaluation

We need to output HTML fragment with sections: About the role, Responsibilities (What You'll Do), Requirements (What We're Looking For), Benefits (Benefits Summary), Pay (base salary range). Possibly Schedule? Not present. Also maybe "Why join us" could be part of About the role? But we only include sections when posting has real specific content. "Why join us" is prose, could be part of About the role? But we already have About the role heading; we could include that prose under About the role? The instruction: use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we need to map content accordingly. We have: - About The Role: paragraph describing role. - What You'll Do: list of duties (Metrics, Log replay and scoring, Regression and benchmarking, Test coverage and data mining, Execution at scale, Engineering practices, Technical standard). Should be a list. - What We're Looking For: list of qualifications (Bachelor's degree..., 2+ years..., Ownership..., Experience designing..., Hands-on experience..., Experience running..., Experience with evaluation dataset..., Working command of applied statistics..., Working understanding..., Experience on an autonomous vehicle..., Working experience with robotics middleware..., Experience handling sensor data..., Proficiency in Python...). Should be a list. - Why join us: could be part of About the role? But we already have About the role heading; maybe we can include that as a paragraph under About the role after the initial description. However the instruction says "About the role" heading for section headings. So we can put the initial paragraph under About the role, and then maybe "Why join us" could be another section? Not in list. Could treat as part of About the role as well. - Benefits Summary: list of benefits. - Pay: base salary range. - Schedule: not present, so omit. - Also location: "This role is based in our San Francisco office location." plus "all of our office-based teams work onsite, five days a week." That's schedule info? It's about work schedule (onsite five days a week). Could be considered Schedule. The instruction says include Schedule section only if posting actually states them. It does state "all of our office-based teams work onsite, five days a week." That's schedule info. So we can include a Schedule section with that. But we need to avoid boilerplate like EEO etc. Not present. We must not repeat job title as heading. Not include Job ID. We must preserve all substantive information; do not invent or summarize away detail. We need to output only HTML fragment, no /, no markdown fences. Thus produce something like:

About the role

Atoms is building the machines that power the next era of progress.... (the initial paragraph about who we are? Actually "Who We Are" is separate; but About the role should contain the description under "About The Role". The "Who We Are" is company overview; maybe we can include that as part of About the role? The instruction says About the role heading for section headings (e.g. About the role...). The posting has a section "About The Role". So we should put the content under that heading: the paragraph starting "We are seeking a Technical Lead for Autonomy Evaluation..." plus maybe also the "Why join us"? But "Why join us" is separate later. However we could also include "Why join us" as a separate section? Not in allowed headings. Could treat as part of About the role as well, but that might mix. Better to follow the posting: About the role includes the description of the role. Then we have Responsibilities (What You'll Do). Then Requirements (What We're Looking For). Then Benefits. Then Pay. Then Schedule (onsite five days a week). The "Who We Are" could be omitted? It's substantive info about company; but not under any heading. Could we include it as a paragraph before any heading? The instruction says output only HTML fragment; we can include a leading

for company overview. It's not a heading, but it's okay. The instruction didn't forbid extra paragraphs outside headings. It said use

for section headings (e.g. About the role...). Use

• for any list... and

  for prose. So we can have a

  for company overview before the headings. Thus:

  Atoms is building the machines that power the next era of progress....

  Then

  About the role

  with the role description paragraph. Then

  Responsibilities

  with
  • each duty. Then

    Requirements

    with
    • each qualification. Then

      Benefits

      with
      • each benefit. Then

        Pay

        with

        base salary range. Then

        Schedule

        with

        about onsite five days a week. We must not include filler like "commensurate with experience". Not present. Check that we preserve all substantive information: company overview, role description, responsibilities list, requirements list, benefits list, pay, schedule. Also "Why join us" paragraph? That is substantive; we might lose it if we omit. Should we incorporate it somewhere? Could add as another paragraph under About the role after the role description, or as its own section? Since not in allowed headings, we could add a

        after About the role before Responsibilities, maybe as part of About the role. The instruction: "Prefer a few substantive sections over many thin ones." So we could merge "Why join us" into About the role as additional prose. That would preserve it. Thus About the role section will have two paragraphs: first the role description, second the "Why join us" paragraph. Now check for any other substantive info: "Atoms accepts applications on an ongoing basis." That's application instruction; we should remove per instruction: "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions." So drop that line. Also "Ready to join us as we serve those who serve others?" is also application encouragement; remove. Now ensure we don't repeat job title. Now produce HTML. Let's craft:

        Atoms is building the machines that power the next era of progress. Over the last decade, software has transformed the digital world. But the physical world, where food is made, minerals are mined, goods are moved, and industries are run, remains far less intelligent, far less efficient, and far more constrained. We’re changing that. Atoms builds Physical AI— real-world robots for the industries that move civilization forward, starting with food, mining, and transport. Our systems are designed to understand, predict, and control the real world with precision, turning complex physical operations into something more reliable, more scalable, and more productive. This work requires more than robotics. It requires deep integration across hardware, software, AI, operations, manufacturing, and real estate. We don’t just build machines in a lab. We deploy them into real environments, operate them, learn from them, and improve them until they work at scale. We are roboticists, engineers, operators, and builders. We believe the next great technology companies will not only transform information, but the physical systems that shape everyday life. If you want to work on hard problems with real-world impact, join us.

        About the role

        We are seeking a Technical Lead for Autonomy Evaluation to own the metrics our autonomy releases are judged on and the log replay and evaluation platform that computes them. In this role, you will take evaluation from recorded logs, to scored regression suites running on every candidate release, to the report a release passes before it reaches a vehicle, developing how replay, scoring, metrics, and test coverage come together into one platform engineers use every day. You will do this across on-road vehicles, and you will build the evaluation infrastructure that lets each new software release, sensor configuration, and platform be assessed seamlessly.

        At Atoms, you’ll work on one of the defining challenges of our time—bringing automation into the physical world to drive real, lasting impact. We exist to uncover valuable unknown truths and turn them into progress, which means constantly pushing beyond what’s known and building what doesn’t yet exist. The work is ambitious and often challenging, but it’s grounded in a shared sense of purpose and a team committed to seeing it through together. Our work only matters if it serves others, and we know that meaningful progress depends on the trust of the people we serve and the strength of our team—so we invest in both, creating an environment where you can do your best work and grow.

        Responsibilities

        • Metrics. Own the safety and behavior metrics a release is judged on, including collision and near-miss measures, trajectory agreement against ground truth, and comfort, and the go/no-go release criteria built on them.
        • Log replay and scoring. Own the pipeline that converts recorded logs into scored test cases, covering open-loop and closed-loop evaluation of perception, localization, and planning against ground truth.
        • Regression and benchmarking. Own the system that benchmarks new software against old across the log corpus for every candidate release, including evaluation dataset design, regression detection, and triage of a regressed case to an owner.
        • Test coverage and data mining. Own how the corpus is mined for the long tail of rare and important events, including sampling strategy, selection of logs by expected value per replay-hour, and coverage of scenario classes the corpus does not yet contain.
        • Execution at scale. Own deterministic and reproducible execution of evaluation, run identity, traceability of every result to a software version, and cost per replay-hour as a tracked number.
        • Engineering practices. Set the practices for metric definitions, test design, code review, and the write-up of evaluation results.
        • Technical standard. Mentor the engineers who join the function, set the technical bar for their work, and participate in hiring.

        Requirements

        • Bachelor's degree in Computer Science, Robotics, Electrical Engineering, Statistics, or a related field with 8+ years of relevant experience.
        • 2+ years as a technical lead or engineering manager for an evaluation, validation, or test team.
        • Ownership of an offline or system-level evaluation system for an autonomous vehicle or robotics program, or a comparable large-scale ML model evaluation system in production, with accountability for the metrics and for the release decisions made on them.
        • Experience designing safety or behavior metrics for an autonomous system and defending them to engineering and executive audiences.
        • Hands-on experience building log replay at scale, including scoring against ground truth in open-loop and closed-loop evaluation.
        • Experience running evaluation pipelines on GPU clusters or comparable large-scale compute on a recurring cadence, with responsibility for reproducibility, throughput, and compute cost.
        • Experience with evaluation dataset design, benchmarking, and regression detection across software or model versions.
        • Working command of applied statistics for system validation, including statistical uncertainty, sampling, rare-event analysis, and the data volume a given claim requires.
        • Working understanding of autonomous systems end to end, including sensing, perception, localization, planning, and controls.
        • Experience on an autonomous vehicle or robotics platform.
        • Working experience with a robotics middleware and its logging and replay tooling.
        • Experience handling autonomous driving or robotics sensor data across multiple modalities and timestamps, including camera, LiDAR, and radar.
        • Proficiency in Python and the ability to read, navigate, and debug existing C++ codebases.

        Benefits

        • Medical, Dental, Vision, Disability, and Life Insurance
        • Flexible Spending Account / Health Savings Account Options