Product Operations

Weave was founded to build the robots we’d want to have in our own home. We believe the next generation of robotics will transform everyday life by enabling people to do more and to reclaim time to spend on what’s important.

We also believe robots are in a sense like any other product: to matter, they have to ship. Our robots are already operating in real homes and businesses, giving us the opportunity to rapidly improve from real-world experience. With a growing team, strong customer demand, and capital for expansion, we’re entering an exciting stage of growth—and we’re looking for people with exceptional talent and standards to help bring home robotics to millions of households.

Successful deployments define real robotics companies. Weave went from first design concept to paying customer shipment in 6 months and has since deployed robots across California in homes and (publicly traded) businesses. We’re looking for our first Product Operations hire to own internal and external deployment success, before, during, and after. In this role you’ll be customers’ first contact and work directly with manufacturing, engineering, data collections, field operations, and sales. You’ll be the glue between them all: owning many deployments at once, sweating every logistical detail, and doing whatever else is required to make sure every robot gets deployed successfully and used to its fullest.

• Own deployments: Drive deployments from signed customer through go-live and ongoing operation, coordinating site readiness, hardware availability, configuration, logistics, training, support, and internal dependencies. At any moment, you know what’s blocking each deployment and who needs to do what next.

• Drive customer requirements: Understand customers’ real workflows, configure robot tasks around them, and coordinate the integrations and operational changes required to make the product useful in practice.

• Be the point person: Own the customer relationship after handoff from Sales, responding quickly when something goes wrong and coordinating Field Operations, Engineering, Manufacturing, or whoever else is needed through resolution.

• Clear the compliance path. Own site safety assessments for business customers including HARAs end to end, and work through building and site requirements, customer policy constraints, and whatever regulatory requirements apply, so nothing blocks go-live.

• Build the operating system: Create the checklists, trackers, dashboards, escalation paths, and automations that let us manage an order of magnitude more deployments without an order of magnitude more overhead.

• Inform the roadmap: See what breaks at new sites before anyone else and turn field observations into crisp bug reports, product requirements, and priorities for the teams that can fix them.

• Build data-collection environments: Partner with Data Operations to set up and configure spaces for internal data collection, evaluations, and other operational deployments.

• 3+ years in operations for a technical product, ideally hardware, and ideally at least once while going from 0 to 1.

• Range: Comfortable demoing to a homeowner in the morning, negotiating a business deployment in the afternoon, and answering tickets and coordinating repairs in between.

• Exceptional operational command: You can run many deployments and workstreams simultaneously without dropping details—maintaining clear owners, dependencies, deadlines, risks, and next actions while priorities change around you.

• Clear, precise communication: You turn messy situations into concise status, decisions, and next steps, whether communicating with customers, engineers, operators, or executives.

• Process instinct: You naturally turn repeated work into checklists, SOPs, dashboards, tooling, and automation—and you are prepared to justify any additional process you propose.

• Technical fluency: Comfortable learning how a complex hardware/software product works, demonstrating it credibly, gathering useful diagnostics, and distinguishing a configuration or operational problem from something that needs engineering.

• Bias toward action: When a deployment needs something outside your job description, you solve it. You’re comfortable operating with incomplete information and figuring out the path as you go.

• Robotics, IoT, or consumer-hardware experience on the support side.

• Early-stage company experience owning a customer function from scratch.

• Past founder experience: you know what it means to do whatever is required to ship.

• Support automation experience: macros, triage rules, or LLM-assisted workflows you built.