Founding Product Designer

Who We Are

Nobody calls a logistics coordinator to say things went well. They call because a $100,000 shipment of clinical trial medication has been sitting in customs for three days and nobody can explain why. Because a biologic therapy arrived outside its temperature window and the treatment has to start over. Because the patient is waiting and nobody in the supply chain can give a straight answer about the shipment's location.

This is the problem we're solving. We're a year in, tracking over 500,000 shipments (including for Fortune 100 customers), and we've already cut manual ops effort in half. General Catalyst, Eclipse Ventures, and Virtue led the seed. The angels are all former or current operators who've spent careers tracking down shipments themselves, such as Head of Logistics at Bristol Myers Squibb, CMO of Cardinal Health, President of Novo Nordisk US, President of UPS Air, and CEO of Uber Freight. They know the market is as large as the problem is broken.

What we've built works, and the most interesting problems are still ahead of us.

Olivier, Co-founder & CEO

The Role

This is the first design hire at a company that's already in production, solving real-world problems with AI. The screens you design will run on real shipments, for real customers, and you'll see them in front of operators within weeks, not quarters.

Every person at ZoomLogi talks directly to customers, and design is no exception. We believe designers who've watched an operator work through a temperature excursion at 2am make better product decisions than designers who've read a summary of it. You'll be in customer calls regularly, because what you see there is the design brief.

You'll own design across the product, from the first sketch to the shipped interface and back again, working closely with the founding team and engineers. There's no design team to inherit and no playbook waiting for you. You'll set the bar.

What You'll Design

• The control tower. This is the core surface: multi-leg shipments, real-time status, exceptions, hundreds of shipments moving at once. An operator opens it to find the one thing that's wrong before it becomes the delay that restarts a patient's therapy. Making that legible, when every shipment has a dozen states and the screen is dense by necessity, is the whole job. Clarity here is measured in seconds saved on a call, not pixels.
• The alerting and intervention experience. When the platform detects a risk (a temperature excursion, a pre-alarm, a silent carrier), design decides whether the right person acts in time. An alert that gets ignored is worse than no alert. The hard part is signal against noise: surfacing the excursion that matters, giving the operator enough context to act without making them read, and designing the handoff between the AI and the human so neither drops the ball.
• Logiblock, our workflow builder. A node-based, no-code canvas where operators build their own logistics automations. The tension is expressive power against simplicity: powerful enough to model a real customs playbook, simple enough that an ops lead builds one without a manual. You'll own the interaction model end to end.
• AI-native surfaces. Conversational and agentic patterns layered across the product. Healthcare logistics requires every AI action to be inspectable, so design has to make the machine's reasoning legible: what it saw, what it did, why, and where a human steps in. Defining what trustworthy AI looks like inside serious operational software is mostly unsolved, and it's yours to figure out.
• The design system. We have a visual language today and the beginnings of a component set. Turning that into a real system, one dense enough for data-heavy ops screens, consistent across five product areas, and something the engineers actually build against, is ongoing work. You set the standard and hold it.

Who Thrives Here

• You have a specific recent example of something you designed, shipped, and watched real users use. And you care about what happens after it ships.
• You're comfortable with ambiguity at the problem level. The interesting work here doesn't arrive as a spec: you see something in a customer call, you figure out what to design, and you design it. If you want a PM to hand you a fully-defined problem before you start, this role will frustrate you.
• You find the domain genuinely interesting. The compliance constraints, the tension between quality and speed, the fact that what you ship moves medication to real patients: these should read as compelling design constraints, not obstacles. A designer who finds regulated, data-heavy software tedious won't do their best work here.
• You're honest about what you don't know. We debate hard, change our minds, and push on each other's work, always with the assumption that everyone in the room is trying to get it right.
• You don't think customer contact is a tax on design time. Every person here is in customer calls. The design decisions that come out of them are the ones worth making.

This role is probably not right for you if your best work is pixel-perfect polish on a single narrow surface, left alone. The surface area here is wide: control tower, workflow builder, alerting, AI, design system, all at once, as the only designer. If context-switching drains you, this will too. And if the work you're proudest of is beautiful marketing sites and consumer flows, this is dense B2B operational software, and that's a different craft.

What We're Looking For

You have 4-8 years of professional product design experience. You're strong across interaction, visual, and systems design, and you lean toward the complex end: dashboards, ops tooling, dev tools, fintech, logistics, anything data-dense. You've shipped software with real users and can show the decisions behind the work, not just the final frames. You're fluent in Figma and prototype well enough to communicate motion and interaction. You can own design end to end as the first designer, with no team to lean on. You're based in San Francisco and excited about being in the office (4 days a week).

The Team

Founded by a team of operators with deep experience in Logistics Tech & Healthcare (Ex-Uber Freight GM + Airspace CRO), joined by early engineers from the likes of Uber, Hippocratic AI, Assort Health and others. We're here to solve a real-world problem at scale, by making every critical shipment visible, predictable, and on time, so potentially life-saving therapies reliably reach the people who need them.

The Tools

Figma is home. We do a lot of low-fidelity prototyping, Google Slides included, and we'd rather explore ten rough directions than polish one too early. The product ships in React/TypeScript, so your designs land in a real component system, not a static file. LLM-driven surfaces are increasingly central to what we design.

The Interview Process

We move quickly.

• Intro call: role fit, motivation, what you've shipped
• Portfolio deep dive: walk us through one project end to end, the decisions and the tradeoffs
• Working session: a realistic design problem close to the actual work, done together
• References → Offer

Compensation & Logistics

• Base salary: $180K- $260K depending on seniority
• Equity: Above market (4-year vesting, 1-year cliff)
• Benefits: Best-in-class medical and dental (100% self, 50% dependents)
• Location: San Francisco HQ (Mission). Hybrid, 4 days/week in office.