Product Designer

Requirements

• 5+ years designing B2B or SaaS products
• Experience with data‑heavy UX patterns (tables, filters, dashboards)
• Strong systems thinking. You’re not just designing a screen, you’re designing flows. Each one needs to be documented so engineers don’t have to guess
• Solid grounding in cognitive psychology and UX heuristics. You can explain why a design decision reduces friction, not just that it does
• Ability to advocate for design decisions in cross‑functional discussions with PMs, engineers, and stakeholders. You can defend a position with reasoning, adjust it with new data, and know the difference
• Someone who raises the bar around them sharing references, giving sharp feedback on work in progress, and making the team better
• Comfort with ambiguity. Early‑stage product areas won’t have a spec. You’ll need to drive the framing, not wait for it
• Fluent in Figma
• English working fluency. Our product, documentation, and most team communication happens in English

What the job involves

• We build software for factory floors. Our users are ops managers, supply chain planners, and production leads, people who don’t have time for confusing UX when a line is down. We’re looking for a designer who takes that seriously
• Pelico is a SaaS platform for industrial operations teams. We help manufacturers get ahead of supply disruptions, manage customer order risk, and coordinate resolution across siloed teams, before a problem becomes a shutdown
• The design problems here are genuinely hard. A single customer order can involve dozens of components, multiple suppliers, overlapping work orders, and five people who each hold a piece of the picture. Your job is to make that navigable, to design interfaces that help someone understand a situation in 30 seconds and act on it confidently
• There’s no established playbook for this kind of software. Industrial ops tooling is a decade behind which means real room to define what good looks like, not just iterate on what already exists
• Own end‑to‑end design for core product areas. From problem framing to shipped feature, in close collaboration with PMs and engineers
• Design complex operational views. Supply chain looks simple from the outside; it isn’t. There are real domain challenges to understand, and the design work reflects that complexity
• Run user research and testing directly with industrial customers. On‑site when possible. We don’t wait for research opportunities to be handed to us. The best designers here create the conditions for good research themselves
• Contribute to and challenge our design system
• Push back when a feature spec isn’t ready to be designed. We’d rather slow down early than redo everything post‑development
• What the next 18 months look like:
• In the short term, you’ll go deep on one or two core product areas, building enough domain knowledge to design with real conviction, not just good instincts
• Over time, you’ll become a reference point for design quality across the team, the person engineers and PMs come to early, not after decisions are already made
• We’re also actively building AI‑assisted workflows into how the design team operates. If that area interests you, there’s room to shape it