Join the team bringing autonomy to the built world

At Bedrock, we're moving AI out of the lab and onto real job sites. Our team includes veterans who helped launch Waymo, scaled Segment to a $3.2B acquisition, and grew Uber Freight to $5B in revenue. We retrofit the heavy equipment contractors already own, starting with excavators, so experienced crews can safely take on more projects and deliver more of the critical infrastructure our society needs.

In August 2026, Bedrock-equipped excavators began doing fully autonomous, paid work on live commercial job sites. We've more than doubled our customer base since 2025, and our machines now work with contractors across the South, Midwest, and Mid-Atlantic

In October 2026, we raised a $600M Series C co-led by CapitalG and Emergence Capital, bringing our total funding to nearly $1B. We're using it to put more autonomous machines to work, build the field and operations teams behind every deployment, and expand into new machine types and job-site tasks.

This is where algorithms meet steel-toed boots. You'll work alongside construction veterans and world-class engineers to solve physical-world problems that simulations can't touch. If you're ready to do meaningful work on hard problems, we'd love to have you join us.

About the Role & Team

As Bedrock scales deployments nationwide, every machine has to be reliably built, provisioned, calibrated, updated, monitored, and kept healthy. Fleet Engineering builds the platforms and internal tools that teams across the company use to manage our growing fleet of autonomous machines.

You'll spend the summer designing, building, and shipping a critical internal tool end to end, one we'll continue using after you leave. Along the way, you'll work with teams across engineering and operations, and see firsthand what it takes to run robots in production.

What You'll Do

• Understand, design, and build an internal tool that addresses a key challenge in the robot lifecycle, and define what "done" means
• Interview the people who'll actually use the tool and translate their pain into requirements
• Build the tool end to end: data, backend, and interfaces, working with cross-functional teams to unblock yourself
• Instrument usage so you can tell whether it's helping
• Iterate fast on real feedback from real operators, traveling to the field if needed
• Document and hand off so what you build survives past the summer

What We're Looking For

Required