Who gets hired, and onto which teams
A robot folding laundry inside a San Francisco laundromat sounds like a publicity stunt until you notice the company behind it is hiring CNC machinists, embedded systems engineers, and robot operators in the same breath. That mix, mechanical trades alongside low-level firmware alongside data-annotation labor on the same org chart, is unusual for a startup less than two years out of founding, and it tells you something specific about what Weave Robotics actually is. The founders describe a company that writes its own operating system and controllers down to the drivers that physically actuate the arms, and that kind of claim only holds if the people writing the software sit ten feet from the people cutting metal for the chassis.
Weave was founded in 2024 by Kaan Dogrusoz and Evan Wineland, who came out of Y Combinator's Summer 2024 batch. The company runs a 26-person team in San Francisco, per its Y Combinator profile. The first product, a wheeled-base humanoid called Isaac, folds clothes for paying customers at laundromats and other laundry facilities across the city, with tidying in living rooms announced as the second use case. In a Humanoids Summit talk, Wineland framed the origin story this way: "we realized as the physical AI revolution was beginning that nobody was actually building a robot that we would actually be comfortable putting in our own home."
The job board tells the same vertical-integration story more concretely. Open roles on Y Combinator's job board span software engineers across cloud infrastructure, applications, and systems; robotics-specific roles covering 3D perception and SLAM, robotic systems engineering, and a triage-focused robotics systems position; embedded systems; a senior security engineer; an ML research scientist; a UI and interaction designer; a marketing lead; a robot production manager; a workplace coordinator; a CNC machinist; assembly technicians; a robotics lab technician; a robotics operations assistant; and robot operators and data annotators. Most posts list "Any (new grads ok)" as the experience floor; only the senior security engineer, marketing lead, robot production manager, and a couple of robotics engineering roles ask for three to five years. Hardware-trades and operations posts sit at the same experience threshold as the new-grad software posts.
That spread, new-grad software engineers, mid-career robotics specialists, and skilled-trades manufacturing staff on the same careers page, is the practical answer to "who gets hired here." A team that small cannot afford specialists who only do one thing. First-party board data shows robots shipping in 2025, with first deployments already running in San Francisco.
Anyone evaluating Weave should read the job list as a map of which functions the company still considers under-built. Today that map has clear weight on the build-and-deploy side: manufacturing, robotics engineering, embedded systems, and operations roles outnumber pure research postings, and the trades and technician roles carry the same urgency as the software ones.
What the board pays
| Role | Posted base salary | Source |
|---|---|---|
| ML Research Scientist | $125,000 – $165,000 | Y Combinator |
| Robotics Systems Engineer | $130,000 – $150,000 | Y Combinator |
| Robotics Lab Technician | $80,000 – $100,000 | Y Combinator |
Pull those postings together and the effective band runs roughly $89,000 to $162,000 across the three salaried roles where compensation appears, with a $150,000 median, per first-party board data. Three data points is not a compensation philosophy. The robotics systems engineer slot sits tighter at a $20,000 spread from low to high. At the bottom, the robotics lab technician anchors the floor as the only sub-$100K figure on the board.
Two other engineering slots, the senior security engineer and the software engineer positions in applications and cloud infrastructure, are listed without published compensation in the data pulled, so any candidate looking at those will need to ask directly rather than work backward from a posted range.
Two things are missing, and both matter more than the numbers that are there. First, Weave has not published equity, signing bonus, or benefits figures for any of its roles; the posted salaries are base pay only. Second, the company has not broken out compensation by team the way a larger employer would, so there is no public way to tell whether the manufacturing and operations hires are paid against the same scale as the robotics and software engineers. The board data skews heavily toward technical roles: the only three salary points anyone can verify all sit in engineering, research, or lab support.
Candidates who care about the full package should treat the posted salaries as the floor of the conversation, not the answer, and should ask specifically about equity refresh cadence, vesting terms, and benefits cost before reading too much into the median.
The interview funnel
Public information about how Weave Robotics screens, interviews, and selects candidates does not exist in any form a job seeker can actually use. No careers page describes a pipeline. No Greenhouse, Lever, or Ashby link surfaces a set of interview stages. No engineering blog post walks through the technical bar. No Glassdoor, Blind, or Levels.fyi review tells candidates what the phone screen feels like, how many rounds to expect, or what the take-home looks like. For a San Francisco robotics company hiring across ML research, systems engineering, lab operations, security, and cloud infrastructure, that silence is unusual; most peers of this size at least run a careers site or publish an engineering post describing what they test for.
What is visible is the shape of the funnel at its endpoints. The board lists active openings with a salary band running roughly $89,000 to $162,000 and a $150,000 median across three salaried roles, with Y Combinator's figures putting the top end at the $162,000 mark on the engineering postings it indexes. That tells a candidate that hiring is active and that the company pays market for the Bay Area, but not how decisions inside the process get made. The first-party data confirms the roles and the compensation range; it does not confirm whether candidates go through a recruiter screen, a hiring-manager call, a technical loop, a systems-design round, or a values interview, none of which the company has disclosed.
The absence is not because Weave is hiding a process behind a careers login wall. There is no login wall. The domain, the company's public profiles, and its job postings point to listings, not to a described methodology.
For job seekers, the practical consequence is that preparation has to be built around the role family rather than the company's stated criteria. An applicant for the ML research scientist posting has to assume a research-heavy screen, paper walkthrough, model design discussion, and coding, because that is the norm for the role in this market, not because Weave has said so. An applicant for robotics systems engineer has to assume hardware-in-the-loop debugging, controls, and real-time systems questions. The senior security engineer posting implies a security loop, threat modeling, systems-level security design, and coding, without the company confirming it. Each candidate is, in effect, reverse-engineering a process the employer has declined to publish.
Until Weave publishes interview stages, expected timelines, or a candidate rubric, the only honest move is to ask in the recruiter screen and to prepare against the standard bar for the specific role rather than against any company-specific signal.
San Francisco, full stop
Weave operates out of one city, and every open role on the board lists San Francisco, CA as the work location. The founders' own description of their early deployment footprint matches that single-city reality. In the Humanoids Summit talk, the team said it is "now actually deployed with multiple businesses across San Francisco," and described the current robot fleet as folding laundry "every day for paying customers across San Francisco" at laundromats and other laundry facilities.
Beyond that anchor, Weave has not disclosed any other offices, labs, manufacturing sites, or remote hubs. There is no public address, no second-city announcement, no mention of a Bay Area satellite facility in the materials available. The company's vertical-integration approach, writing software from the operating layer down to actuator controllers and designing the robot's arms, torso, and wheeled base in-house, implies an on-site build and test environment somewhere in San Francisco, but the company has not named it.
Candidates who cannot relocate to the Bay Area should read that uniformity carefully. There is no signal of a distributed workforce, no posted remote-eligible role, and no indication that engineering, manufacturing, or operations staff split their time across sites. The company says it works "with the workers that were already folding laundry" at customer sites, but those deployments are field operations, robots installed at laundromats and laundry-service providers, not employee workplaces.
Who actually thrives here?
The honest answer is that nobody outside Weave knows, at least not from anything the company has put into public circulation.
A 2024-founded San Francisco robotics company would, in a typical job-market reading, have left some trace of its culture by now. A Glassdoor page. A few Blind posts. A LinkedIn note from a former employee. Weave has none of that surface area. There are no public employee reviews to draw from, no interview write-ups on LeetCode-style forums, no first-hand "day in the life" threads, and no published list of attributes the company says it screens for. The candidate who wants to know what kind of person succeeds here has, at present, only the job postings themselves.
What those postings do say, indirectly, is that the hiring mix is unusually broad for a young company. Six distinct functions, manufacturing, robotics, software, operations, product, and marketing, share the salary band but presumably ask for very different things from candidates. A robotics lab technician who thrives at Weave is almost certainly not the same profile as a senior security engineer who thrives there, and the postings do not spell out which traits transfer across the floor and which do not.
For most San Francisco robotics employers of comparable size, the answer is partly findable: a candidate can read three former employees' Glassdoor reviews and learn that the company values independent project ownership, hates micromanagement, promotes from inside, or burns people out. Weave's applicants cannot do that triangulation. The company has not published a careers page that names its values. It has not posted a culture deck. It has not, as of this writing, registered enough review-site presence to generate the kind of aggregated signal a candidate could lean on.
Anyone considering a role here is making a bet on a young San Francisco robotics employer with no public track record of employee experience to confirm or deny. The salary band is legible. The location is legible. The team functions are legible from the postings. The interview process is not. The workplace facilities beyond the headquarters city are not. And the profile of the person who does well once inside is, for now, a question the public record simply does not answer.
Working in frontier tech? Zero G Talent tracks the openings: see every open Weave Robotics role, browse frontier tech jobs, the companies hiring, and the people building the field.