Product Designer

120Water is a mission-driven SaaS company that provides water data and compliance software to government agencies and utilities. The Product Designer owns end-to-end design for product modules, including user research, workflows, interaction and visual design, and engineering handoff. The role also supports UX practices and the company’s internal UI language.

Responsibilities:

• Own the design of one or two modules at a time, from the first problem framing through to the shipped screen and the follow-up fixes
• Talk to users. Sit in on customer calls, run short interviews, watch Pendo session replays, and turn what you see into concrete design changes. Dead clicks and rage clicks are a brief, not a mystery
• Build flows and prototypes using a combination of Figma and AI tools that engineers can build from without guessing. Cover the empty states, the error states and the loading states, not only the happy path
• Write the words on the screen. Labels, empty states, confirmation dialogs and error messages are part of the design, and you own the first draft
• Review engineering work before release and flag where the build drifted from the design, with a clear call on what blocks the release and what can ship as a follow-up
• Present your work in critique and in product reviews. Explain the tradeoffs you made and take feedback without defending the pixels

Requirements:

• 3 to 5 years designing B2B or enterprise software that shipped, with at least one or two major features you can walk us through from research to release and tell us what you got wrong
• Fluency in Figma: components, variants, auto layout and prototypes
• Willingness to expand fluency to the MCP server and how it can grow into a component library
• Experience working inside an established design system and extending it with care. You know when to reuse, when to adapt and when to raise your hand
• Hands-on research habits. You have run user interviews or usability sessions yourself and changed a design because of what you heard
• Comfort with dense, data-heavy interfaces: tables, filters, maps, forms with 40 fields and workflows that span days
• Clear writing. You can draft microcopy, a design rationale and a handoff note that an engineer in another time zone can act on
• A working relationship with engineers. You understand enough about how front-end code gets built to design things that can be built well, and you ask when you do not
• Judgment about scope. You can tell the difference between the change a user needs this quarter and the redesign they would enjoy next year, and you ship the first one
• You have designed for regulated industries, utilities, GIS or field operations, or for users who work outdoors on a phone with gloves on
• You have used Pendo or a similar analytics and session replay tool to find problems before users reported them
• You have helped roll a new design language across an existing product, including the awkward middle period where old and new screens sit side by side
• You have designed mapping or spatial interfaces