Careers at Multiply Labs: Teams, Pay and How to Get Hired

Who gets hired and onto which teams

The biomanufacturing bottleneck is a physics problem, not a staffing problem. Factory floors producing advanced cell therapies belong to a different era of medicine. The people who can rebuild them span disciplines. Multiply Labs hires where robotics meets GMP-grade biology, and the team structure mirrors that collision.

The careers page lists seven functional categories: Advanced Software R&D, Engineering Leadership, Hardware, Quality, Robotics Software, System Software, and a General Interest bucket. The eight live roles on the Zero G Talent board collapse into four clusters that reveal hiring priority. Software infrastructure and leadership anchor one cluster: VP Software Engineering, Robotics & System and Staff Infrastructure Engineer, both in San Francisco. Robotics research and deployment form a second: Senior / Staff Robotics Research Scientist - Dexterous & Mobile Manipulation in San Francisco and Robotics Engineer in Milan, Pavia, and Turin. Manufacturing and quality systems make a third: NPI Manufacturing Engineer and Staff Quality Systems & Compliance Engineer, both in San Francisco. A single science role, Scientist II in San Francisco, rounds out the fourth. An Open Applications posting catches outliers.

The distribution follows the roadmap. A $75 million Series B, according to Multiply Labs' careers page, led by NantWorks, with participation from AstraZeneca and Lingotto, funds simultaneous advances in motion planning for sterile manipulation, real-time sensor orchestration under 21 CFR Part 11, and hardware that survives cleanroom validation. Collaborations with AstraZeneca, Legend Biotech, and Kyverna Therapeutics mean every hire works on code or hardware that touches a partner's process. Founders Alice Melocchi, Joe Wilson, Fred Parietti, and Tiffany Kuo structured the organization so a robotics researcher in San Francisco and a manufacturing engineer in Milan share a release cadence. The salary band across six salaried roles runs $103,000 to $275,000 with a $198,000 median. Senior individual contributors in robotics and software command the top of the band; quality and manufacturing roles sit lower but carry regulatory authority.

Geography mirrors the split. San Francisco hosts leadership, software, research science, manufacturing, and quality. The Milan-Pavia-Turin corridor hosts the Robotics Engineer role. The company calls itself "roboticists, scientists, and engineers rebuilding biomanufacturing from scratch" and seeks "builders who want hard problems and real stakes." That framing filters for people who have shipped physical systems under regulatory constraints, not just simulated them.

What it pays

Multiply Labs does not publish base-salary bands on its careers page or job postings. The six salaried postings there span that band. That band is narrower than the $177,000-to-$500,000 range Business Insider found for OpenAI's robotics push (a different company, stage, and capital structure) but fits the Bay Area robotics-engineering market for a Series B team backed by NantWorks, AstraZeneca, and Lingotto.

The live postings show the range. The VP Software Engineering role tops the band at $250,000–$320,000. The Staff Infrastructure Engineer at $175,000–$230,000. The Senior/Staff Robotics Research Scientist at $160,000–$210,000 demands specialized motion-planning and manipulation expertise.

The Staff Quality Systems & Compliance Engineer reflects the regulatory weight of GMP-grade automation. The Scientist II role is the entry point for the wet-lab side. The NPI Manufacturing Engineer shows the widest band, capturing early-career support up to senior engineers owning the transfer from prototype to validated production line.

Two postings list no base band: the role there, and the Open Applications posting in San Francisco.

Third-party aggregates roughly corroborate the board. Salary.com places a Multiply Labs Software Engineer at $126K–$145K, average $136K, between the Scientist II and Staff Infrastructure Engineer bands, plausible for a mid-level generalist. Glassdoor shows 14 salaries across nine titles, too thin to break out by level. Neither source distinguishes equity.

If you're interviewing for a staff-or-above engineering track in San Francisco, expect a base offer of $175,000–$320,000; quality, compliance, and NPI roles cluster at $90,000–$185,000; wet-lab scientists start around $115,000. The $198,000 median — derived from posted bands, not self-reported surveys — is the most useful anchor.

How the hiring process works and what gets candidates through it

Multiply Labs runs a three-round process spanning three to five weeks, sometimes stretching to six. The company doesn't publish the stages; they come from candidate reports on interview guides and community boards. Round one tests the stack: Python, distributed systems, and multi-agent scheduling. Round two tests architectural thinking and practical engineering: candidates describe systems they've built, how they handled failure modes, how they reason about reliability when software touches physical actuators. Round three is a hands-on assessment mirroring active team problems: live coding, a timed take-home, deep-dive discussions with future teammates.

PracHub's editorial advice based on candidate reports states: "During live coding or system design, talk through your thought process. We care as much about how you arrive at a solution as the solution itself."

The criteria are explicit about what they don't require: robotics experience. The company values strong software engineering fundamentals above all and provides domain context. It requires evidence of designing resilient, maintainable, scalable systems, not just code that "works." Curiosity about the software-hardware boundary differentiates. The environment is mission-driven, fast-paced, highly collaborative, with a high bar for excellence and a preference for impact over rigid hours.

Community interview guides emphasize specific preparation. Refresh distributed systems and algorithmic design for several weeks. Be ready to discuss constraint satisfaction, throughput optimization, discrete-event simulation, state synchronization, and fault tolerance testing. During live coding, narrate your reasoning. In system design, emphasize edge-case handling and failure recovery. Ask questions that reveal owner-level thinking: how the team balances speed with quality, what architectural challenges keep them up. Demonstrate you can context-switch between high-level orchestration and low-level debugging. The founders built a culture where the supply chain team comes from Formula 1 and the simulation stack runs on Nvidia Isaac Sim. That pedigree sets a high bar for precision and iteration.

Where the work happens

Multiply Labs operates from two primary sites: a San Francisco headquarters that doubles as a robotic pharmaceutical manufacturing facility, and an Italian subsidiary in Turin built to produce the robotic clusters. The company also stations engineers at customer facilities where Clusters deploy, sites belonging to partners such as AstraZeneca and Legend Biotech.

The San Francisco headquarters sits at 1426 Minnesota Street in Dogpatch, listed on the company's visit page. Third-party directories still reference an earlier 1040 Mariposa Street address. The Minnesota Street facility houses engineering teams developing the Cluster platform, a closed, GMP-ready system that automates biologic manufacturing by orchestrating robotic arms around validated instruments from Thermo Fisher Scientific, Cytiva, and Wilson Wolf. The site runs manufacturing demonstrations and process development, generating electronic records and sensor data that feed the software stack. All San Francisco roles — Staff Infrastructure Engineer, NPI Manufacturing Engineer, Staff Quality Systems & Compliance Engineer, VP Software Engineering, Senior/Staff Robotics Research Scientist, and Scientist II — concentrate here.

Multiply Labs Italia launched in Turin in May 2026 with a mandate to build manufacturing capacity for robotic clusters serving pharmaceutical customers. The company appointed Enrico Racca — formerly head of supply chain and manufacturing for Scuderia Ferrari Formula 1 — as founding general manager. The Robotics Engineer role lists "Milan/Pavia/Turin," suggesting the operation spans the Lombardy-Piedmont corridor. The subsidiary handles production-scale assembly and integration of Cluster hardware: robotic arms, enclosures, control systems.

This split mirrors the commercial model: San Francisco develops the platform (software, control systems, process integration, regulatory strategy) while Turin manufactures the physical units that ship to customer sites. The Clusters then operate inside partners' own GMP facilities (AstraZeneca and Legend Biotech both purchase Multiply Labs' robots and operate them at their own facilities, Hoodline reported), meaning Multiply Labs engineers also spend time on-site for deployment, validation, and ongoing support. The instrument-agnostic design, which connects to partners' already-validated equipment inside a closed automated environment, means the San Francisco facility maintains a representative instrument set for integration testing, while Turin's line produces Clusters that slot into varied customer floor plans and utility configurations.

The two-site structure is recent (the Italian entity didn't exist until mid-2026), and headcount remains modest, around 40 employees across two offices, BuiltInSF lists. The physical separation of platform development from hardware manufacturing reflects a deliberate scaling decision. The Series B buys time to prove robotic systems can become a manufacturing business, where robots, not lab technicians, carry the weight of producing medicine's most expensive treatments. Turin is where that manufacturing business gets built.

Who thrives here

The people who last at Multiply Labs share a specific profile: they treat the clean room as a first-class engineering constraint. The company's modular robotic platform compresses the work of ten laboratories into a closet-sized cell, each arm executing thousands of distinct tasks across a two-week manufacturing run — 5,000 to 6,000 individual steps by the founders' count — where a single error scraps a patient's therapy. That reality selects for engineers who have internalized GMP discipline before they ever join. The board's own postings make it explicit: a Staff Quality Systems & Compliance Engineer sits alongside Robotics Engineers and NPI Manufacturing Engineers, and the VP of Software Engineering owns "Robotics & System" as a combined remit.

Founders' accounts reinforce the filter. Fred Parietti said the company exists because "we found it inconceivable that these medicines would scale… being made by hand as if it was an artisan shop." Alice Melocchi brought the manufacturing pain point; Parietti brought the robotics obsession. Early hires translated that frustration into a "super modular" system: pharma partners swap modules around robotic arms as processes change, while software builds a learning pipeline that ingests video demonstrations from scientists and outputs control policies via imitation learning and foundation-model fine-tuning. Nadia Kreciglowa, Head of Robotics Software, evaluated collaborative arms against that spec and called Universal Robots "the clear winner."

Employee accounts from partner sites echo the same traits. Thermo Fisher, Cytiva, Stanford Medicine, and UCSF collaborate on pilot runs. The NPI Manufacturing Engineer role exists because new product introduction here is a contact sport between mechanical tolerances, sterility assurance, and software release cycles. The Scientist II role sits inside the same organization, not a separate R&D silo, so wet-lab fluency is expected even from robotics hires.

The compensation band reflects the scarcity of that hybrid profile. A Senior/Staff Robotics Research Scientist in dexterous and mobile manipulation must publish in top venues and ship code running on hardware bolted to ceiling rails in a clean room. The Staff Infrastructure Engineer builds the compute and data fabric letting the learning pipeline iterate across dozens of deployed systems. The VP Software Engineering owns the architecture that makes "videos in, control policy out" reliable at scale. None of these roles tolerate specialists who stop at their discipline boundary.

Retention bears this out. The company has raised over $100 million since 2016, including the $75 million Series B, capital funding long development cycles, not quick pivots. The AstraZeneca agreement to evaluate GMP-ready systems for commercial-scale manufacturing makes the next 18 months a gauntlet of regulatory and technical milestones. Engineers who stay view that gauntlet as the job, not an interruption. They prototype Friday, qualify Monday, document both before lunch.

Working in frontier tech? Zero G Talent tracks the openings: see every open Multiply Labs role, browse frontier tech jobs, the companies hiring, and the people building the field.