Should you work at Mind Robotics?
Probably, if you want hardware from prototype to production and will be on-site. Mind Robotics raised a $500M Series A, is hiring 31 roles, and puts engineers on physical hardware across the full lifecycle rather than in simulation — with non-traditional backgrounds explicitly accepted in several postings. All 31 roles are on-site, 29 of them in Palo Alto; the company says outright it will not provide structure or direction, processes are expected to change including ones you wrote, and we hold no verified employee reviews.
Read from 31 live roles, 31 full job descriptions and 1 funding round. No employee reviews, no ratings.
Good fit if
- The company is funded and has a named first deployment site, so the work has a concrete near-term target rather than only research goals.
- Many roles are described as first-of-their-kind or foundational, so early hires define the function rather than inherit it.
- Hardware roles cover the full lifecycle from prototype to production, not just design.
- Engineering roles are explicitly hands-on with physical hardware rather than simulation- or spec-only.
Think twice if
- Comfort with ambiguity and speed is a stated requirement across engineering postings, not an optional trait — candidates who prefer defined scope may not fit the screen.
- The company explicitly says it will not provide structure or direction; self-starting is a hiring filter.
- Some roles are individual contributor with no team to manage or inherit, despite senior scope.
- Processes are expected to change frequently, including ones you authored.
We can't tell you
- What managers are actually like day to day
- Attrition, tenure or promotion rates
- Whether the pace is sustainable
- Equity terms — no posting states them
What it pays
No active roles publish a salary range.
0 of 31 roles post a range
No role here publishes a salary range.
Where you'd sit
Of 31 roles that specify a setup.
Who they're hiring
31 live roles across 4 teams.
What the job descriptions ask of you
A reading of how 31 postings are worded — not a score, and not comparable between companies.
Pace Fast
Speed and urgency are stated requirements across engineering, supply chain, and program roles.
“You thrive in ambiguity, default to urgency, and have the drive to build — not just maintain”
Autonomy Self-directed
Postings repeatedly ask for people who act without being directed.
“figure out what needs to exist, build it, and move on to the next thing -- without waiting to be told what that is”
Structure Ambiguous
Postings describe absent playbooks and expect the hire to create structure rather than follow it.
“the playbook doesn't exist yet"; "you create structure from ambiguity”
Ownership End-to-end
Roles are framed as end-to-end ownership of a domain or stack.
“Own the tactile sensor stack electrically"; "Own the monthly and quarterly close process end-to-end”
Collaboration Cross-functional
Most roles sit at the boundary between hardware, firmware, software, and ML teams.
“Serve as the primary connective layer between the hardware engineering, software/ML, and data operations teams”
The upside
Stated by Mind Robotics in its own postings.
The company is funded and has a named first deployment site, so the work has a concrete near-term target rather than only research goals.
“$615M raised from Eclipse, Accel, and Andreessen Horowitz... Our first robots go into Rivian's plant this year.”
Many roles are described as first-of-their-kind or foundational, so early hires define the function rather than inherit it.
“This is a founding program management role"; "You will be the first dedicated finance hire”
Hardware roles cover the full lifecycle from prototype to production, not just design.
“bring up, characterize, and scale custom sensor hardware from initial benchtop debug all the way to high-volume manufacturing”
Engineering roles are explicitly hands-on with physical hardware rather than simulation- or spec-only.
“Comfortable instrumenting, testing, and debugging thermal performance on real hardware.”
Cross-functional exposure across disciplines is built into most engineering roles.
“Collaborate cross-functionally with mechanical, firmware, controls, and ML teams to translate raw transducer signals into calibrated, usable manipulation feedback.”
The company states it accepts non-traditional backgrounds and project-based experience in place of formal credentials in several roles.
“5+ years of experience (or equivalent \"hard tech\" projects) designing sensor electronics”
The trade-offs
Also from the postings — not complaints from employees.
Comfort with ambiguity and speed is a stated requirement across engineering postings, not an optional trait — candidates who prefer defined scope may not fit the screen.
“You are comfortable with ambiguity, move fast, and have an \"engineering curiosity\"”
The company explicitly says it will not provide structure or direction; self-starting is a hiring filter.
“You don't need structure to be productive"; "figure out what needs to happen and make it happen, with minimal direction”
Some roles are individual contributor with no team to manage or inherit, despite senior scope.
“This is not a role for someone who wants to inherit a mature function or manage a team on day one.”
Processes are expected to change frequently, including ones you authored.
“Thrives in an early, fast-moving environment where the process you wrote last month gets rewritten this month.”
Certain roles require on-site presence, irregular hours, and travel.
“On-site... Flexibility across shifts including occasional nights and weekends... Travel up to ~20%”
One role is based at a customer site away from headquarters, with remote support rather than co-located teammates.
“be our hands and eyes onsite at a key customer in Normal, IL”
Employee sentiment
No data yetWe hold no verified employee reviews for this company. Sentiment appears here only when it comes from verified employees — never from product or customer ratings, which measure something else.