Senior Product Designer

• Several years shipping real B2B products that people use, ideally SaaS with complex data or workflows - and you can show your work and what happened after launch.
• A maker: you prototype instead of debating, you can build a working version of your ideas (HTML/CSS/JS, React, or whatever you use), and you treat AI tools as part of your kit.
• Strong craft: interaction and visual design that is sharp, fast, and considered, on dense and complex UI.
• Product thinker: you care about whether the thing works for the user and the business, and you use data and customer conversations to decide - not opinions in meetings.
• Opinionated and easy to work with: you say what you think, explain your reasoning briefly, change your mind when the evidence says so, and move on.
• Happy in ambiguity and small teams: no one will hand you a brief. You will find the problem, scope it, and go.
• Curious about AI, sales, and how outbound actually works - and you want to build in that space.
• Fluent English.

We are hiring a Senior Product Designer who builds. Not a specialist who hands off polished specs, but a maker who takes an idea from a rough problem to something real in users' hands - and keeps iterating until it works.

At Enginy, design is not a stage in a process. It is how we figure out what to build. You will pick up ambiguous, high-impact problems, sketch, prototype, test, ship, and measure. You will work directly with engineers and founders - in the product, not in a deck about the product. You will have the autonomy to make calls and the responsibility to own the outcome.

Problem → prototype → ship → learn → repeat

• Own initiatives end to end. Take at least one major product bet from "we think there's a problem here" to shipped and measured. You frame it, design it, build the prototype, ship it with the squad, and read the results.
• Prototype in whatever gets the answer fastest. Figma, code, AI tools, a Loom to five users. You test ideas with real prospects and real data before we commit engineering time to them.
• Design the whole thing. Journeys, flows, edge cases, empty states, data-heavy UI, the AI moments where the product does the work. Screens are the output, not the job.
• Ship with engineering. You are comfortable in the codebase, in PRs, and in the details of how things actually get built. You would rather fix it than file a ticket.
• Evolve the design system as a tool for shipping faster, not as an artefact to maintain.
• Raise the bar. Push the quality of what we ship, share what you learn, and grow through doing.