Senior Product Designer

SENIOR PRODUCT DESIGNER @ SECFIX Location: Remote (EMEA) · CET/CEST time zone Hi — I'm Grigory, co-founder and CTO at Secfix. How do you feel about owning a feature from the first customer conversation to the version that's live in production — writing the spec yourself, pairing closely with engineers through the build, and overseeing your design shipped in production exactly the way you designed it? If that sounds like the right shape of the job — designer who owns, not designer who hands off — read on. I've spent most of my career believing the best designers aren't the ones with the prettiest Figma files. They're the ones who can frame a problem, write a spec, sit with engineers through the build, and own that what shipped is what they designed. Our founding product designer, Ghada https://www.linkedin.com/in/ghadashebl/, has been doing exactly that since we started. The engineering team has doubled, and we're shipping faster than we ever have. We're hiring the third designer because there's more good work to do than two people can handle — and we'd rather ship faster than slow down. WHY SECFIX EXISTS Over 1.78 million SMBs in Europe need to comply with security frameworks — ISO 27001, GDPR, TISAX, SOC 2 — just to sell to enterprise customers. The process is manual, painful, and takes over a year. We automated it. Our platform integrates with a company's full tech stack — AWS, Azure AD, Jira, GitLab, GCP, and more — automatically extracts compliance evidence, and guides teams to certification in weeks instead of months. Our fastest customer was certified in 4 weeks instead of the industry-standard 12+ months. We've raised €17M in total (€12M Series A), backed by Alstin Capital, Neosfer (Commerzbank), and Bayern Capital. We're on a profitable trajectory, growing fast, and building the team that will take us to European market leadership. This space is not threatened by AI; it's amplified by it. Compliance requires deep domain expertise combined with automation. Our new AI product (CISO AI) is just getting started, and there's a huge amount of product design work ahead: agentic workflows, intelligent evidence collection, context-aware policy generation, and more. WHAT WE BELIEVE Compliance software has historically been built like the audit it automates — heavy, defensive, ugly. We're building something else. The customer is a real person trying to ship audit-ready evidence on a Friday afternoon. The product should respect their time, automate the boring parts, and make the rest feel calm. Quality is the product. Most of our category competes on feature lists. We compete on craft. A clear empty state, a sync that doesn't lie, a settings page that holds together at eleven permission tiers — these are the things customers feel before they can name them. Design at Secfix is not what wraps the product. It's most of what makes it work. WHAT THE ROLE IS We expect strong design skills, strong product thinking, and the ability to hold your own in a technical discussion. You work in a small team — usually with one or two engineers — and pair closely from the first prototype through to production. You own the project from beginning to end. Alongside the features you ship, you do three things that make everyone else faster: - Maintain the components and patterns that make design fast. - Own how the team ships. We have no PMs. You write the specs, run the ticketing workflow, keep engineers unblocked. - Build the tools and skills — Cursor rules, design QA skills, prompt templates — that let engineers do good design work without you in the room. The leverage is doing all four well. Doing only one is the wrong shape. HOW WE WORK - No PMs. Designers and engineers run product. You talk to customers, frame the problem, write the spec, decide what ships. - Small temporary teams. You plus one or two engineers per project. Whoever is closest to the problem leads. - Design leads the logic; engineering tests feasibility. You bring the V1. Engineers push back on what's expensive or risky, and start ahead with system design. They help spot edge cases. You adjust it fast. We get from v1 to v4 in a matter of hours or a few days. - Prototype-grade, not wireframes. Real components, real states, real copy. Sometimes an LLM-built prototype before Figma. The component library stays current because the speed of design depends on it. - Handoff is the beginning, not the end. You're in the engineering channel. You review the PR. You verify on production. Staging QA is the first gate, not the last. - In-sync culture with a thoughtful comms mindset. Loom for reviews, Notion for specs, quick loops in Gather where written comms don’t cut it, all happening in the same time zone. Teammates are reviewing things quickly. Engineers and designers spend under two hours in weekly meetings. - AI is part of the craft. We use Claude to pressure-test ideas, draft specs, surface edge cases, and write test cases. Not to skip thinking. THE FIRST THREE MONTHS - Month 1. Ship your first design to production. Get into the codebase, the customer language, the way we write specs. Sit on customer calls. - Month 2. Own a full feature end-to-end. Customer conversations, problem framing, Figma, spec, engineer pairing, PR review, production verification. - Month 3 and beyond. Push the design system forward. Start building the tools and skills that make engineers faster at design. Improve the product design process. The bar is yours to defend. WHO YOU ARE - 8+ years designing B2B SaaS desktop applications as Staff/Principal Product Designer or similar. Dense interfaces — tables, filters, permissions, settings pages. - You've been the only designer, or one of two or three, in companies under 50 people at least once before. You know how to set the bar without a design org behind you. - Your portfolio is "I," not "we." You can name the engineer you paired with on each feature, the design decision you defended through the build, and what happened when the feature reached users. - You communicate clearly and concisely in English: in Slack, in docs and on a call. - You're fast in Figma with or without AI. You’re already in a serious relationship with LLMs. - You treat engineering feasibility as input, not a constraint. When an engineer says "three weeks, here's why," you find the version that's 80% as good and ships next week. - You're comfortable doing product work without the PM title. - You hear feedback and come back the next day with something better. You don't spend the hour in between defending the version that's already outdated.