Staff Machine Learning Engineer - Perception

We need to output HTML fragment with sections: About the role (already present as "About The Role"), Responsibilities (What You'll Do), Requirements/Qualifications/Skills (What We're Looking For), Benefits (Benefits Summary), Pay (base salary range), Schedule (maybe mention onsite five days a week). Also maybe "Who We Are" is not a required heading; we can include as a section? The instruction: use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). We should include sections only when posting has real specific content. The posting includes "Who We Are" (intro) but not a required heading; we could include as a section maybe "About the company" but not in list; but we can include as a

before headings. Probably we should not create a heading for Who We Are unless it's needed; but we can keep it as a paragraph. We need to remove boilerplate: cookie/navigation/legal/EEO etc. There's none. We need to preserve all substantive info. We need to output only HTML fragment, no /, no markdown fences. Thus produce something like:

About the role

As a Senior Staff Machine Learning Engineer focused on Perception, you will be one of the foundational technical leaders of Atoms' AI organization....

Responsibilities

• Define and help build the technical architecture for Atoms' next-generation perception systems.
...

Requirements

• Deep expertise in machine learning and computer vision, with substantial experience building sophisticated perception systems.
...

Maybe also Skills? Could combine Requirements and Skills; but we can have Requirements and Skills separate if content distinct. The posting includes "What We're Looking For" which covers expertise, experience, etc. Could treat as Requirements. Could also add Skills: strong software engineering fundamentals, ability to remain hands-on in Python/C++, etc. But those are already in the list. We'll just have one Requirements section. Benefits: list from Benefits Summary. Pay: base salary range. Schedule: mention onsite five days a week. We need to ensure no placeholder text like "commensurate with experience". Not present. Let's extract details. From "Who We Are": paragraph(s). We'll keep as

maybe multiple. "About The Role": paragraph(s). We'll put under About the role heading. "What You'll Do": list of responsibilities. "What We're Looking For": list of requirements. "Why join us": maybe could be a section? Not in list but could be included as a paragraph under maybe "About the company"? But we can keep as a paragraph after requirements maybe under a heading "Why join us"? Not in allowed headings list but we could still include as

Why join us

if we want. The instruction says use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but says use those for those sections. Safer to stick to those headings only. So we can incorporate "Why join us" content into a paragraph under maybe "About the role" or as a separate

without heading. Probably better to keep as a paragraph after requirements. "What Else You Need To Know": includes location, onsite, salary, benefits. We'll parse. Let's extract: Location: based in our San Francisco office. Work schedule: all of our office-based teams work onsite, five days a week. Salary: base salary range $275,000 - $321,000 per year. Actual compensation determined individually. Benefits Summary: list: - Medical, Dental, Vision, Disability, and Life Insurance - Flexible Spending Account / Health Savings Account Options - 401(k) - Equity - Sick Time, Unlimited Flexible Time Off, and Paid Holidays - Paid Parental Leave - Pre-Tax Commuter Benefit Plan - Team lunch in our SoMa office every Tuesday and Thursday - Benefits Are Subject To Change At The Company's Discretion. Also note: Atoms accepts applications on an ongoing basis. (We can drop as application instruction? It's not instruction to apply but maybe minor metadata; we can drop or keep as short p. Probably drop as it's not substantive? It's about process; maybe keep as a short p under a heading? Not needed. We'll drop. Now produce HTML. We'll need to escape any special characters? Not needed. Let's craft. First paragraph: Who We Are content. We'll combine the two paragraphs from Who We Are into one

maybe. Who We Are text: "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." We'll put that as

. Then About the role heading and paragraph(s). The About The Role paragraph: "As a Senior Staff Machine Learning Engineer focused on Perception, you will be one of the foundational technical leaders of Atoms' AI organization. You will help define how our machines transform raw sensor data into rich representations of the physical world. You'll work across camera, LiDAR, radar, audio, and other sensor modalities to build perception systems capable of operating in complex, dynamic real-world environments. This is not simply a role focused on improving an existing perception stack. You will have the opportunity to help determine what that stack should become. You will work closely with AI research, robotics, autonomy, and engineering leaders to develop perception architectures that connect traditional perception capabilities with emerging approaches in world models and foundation models for physical AI. This is a deeply technical individual contributor role with significant influence over Atoms' technical direction." We'll put as

. Responsibilities: list each bullet from "What You'll Do". Let's extract: - Define and help build the technical architecture for Atoms' next-generation perception systems. - Develop machine learning systems that transform multimodal sensor inputs—including camera, LiDAR, radar, audio, and other signals—into useful representations of the physical environment. - Advance approaches to multi-sensor and multimodal fusion across complex real-world operating environments. - Design and develop deep learning architectures for problems such as detection, segmentation, tracking, classification, scene understanding, and 3D perception. - Explore how modern foundation models and world models can complement or replace components of traditional perception pipelines. - Build perception systems designed to serve downstream reasoning, planning, and action models. - Make architectural decisions spanning data, model design, training, evaluation, inference, and deployment. - Develop systems that balance model quality with the latency, efficiency, reliability, and compute constraints required for real-world machines. - Establish evaluation methodologies and metrics that accurately measure perception performance in the environments where our systems operate. - Partner closely with researchers and engineers working across world models, action models, robotics, autonomy, and ML infrastructure. - Provide technical leadership across the organization through architecture reviews, mentorship, technical direction, and hands-on engineering. - Help establish the technical bar for the growing perception organization and participate in identifying and assessing exceptional engineering and research talent. We'll put each as

. Requirements: list from "What We're Looking For". Extract: - Deep expertise in machine learning and computer vision, with substantial experience building sophisticated perception systems. - Strong understanding of modern deep learning architectures and their application to visual and multimodal perception. - Experience working with one or more real-world sensor modalities such as cameras, LiDAR, radar, audio, depth sensors, or related systems. - Experience with sensor fusion, multimodal learning, 3D perception, scene understanding, or related areas. - Strong understanding of the full ML lifecycle, including data strategy, training, model architecture, evaluation, optimization, and deployment. - Experience designing ML systems that operate under real-world latency, compute, reliability, and safety constraints. - Strong software engineering fundamentals and the ability to remain deeply hands-on in Python and/or C++. - Demonstrated ability to make consequential technical and architectural decisions in ambiguous problem spaces. - A track record of technical leadership and influencing engineering direction beyond your immediate projects or team. - Ability to communicate complex technical ideas clearly and collaborate across research and engineering disciplines. We'll put as

. Benefits: list from Benefits Summary. Extract each bullet: - Medical, Dental, Vision, Disability, and Life Insurance - Flexible Spending Account / Health Savings Account Options - 401(k) - Equity - Sick Time, Unlimited Flexible Time Off, and Paid Holidays - Paid Parental Leave - Pre-Tax Commuter Benefit Plan - Team lunch in our SoMa office every Tuesday and Thursday - Benefits Are Subject To Change At The Company's Discretion. We'll put as

. Pay: we can have a

stating base salary range. Schedule: we can have a

stating onsite five days a week, based in San Francisco office. We might also include location as part of schedule or separate. We'll create sections:

About the role

...

Responsibilities

...

Requirements

...

Benefits

...

Pay

The base salary range for this role is $275,000 - $321,000 per year. Actual compensation will be determined on an individual basis and may vary depending on experience, skills, and qualifications.

Schedule

This role is based in our San Francisco office and requires onsite work five days a week.

We might also include a brief paragraph about "Why join us" maybe as a

after Requirements before Benefits. Could add a heading "Why join us"? Not in list but could be okay. Safer to add as a

without heading. We'll place after Requirements: a

containing the "Why join us" paragraph. Why join us text: "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." We'll put as

. Now ensure we didn't include any boilerplate like "Atoms accepts applications on an ongoing basis." We'll drop. Now produce final HTML. Check for any repeated lines: none. Make sure to not include markdown fences. Let's craft final answer.