The short version
Compliance software is one of the last categories in fintech where design has never been the priority. We think the people who use these tools every day deserve better, and we want someone to build it with us.
What Bits does
We build compliance infrastructure for regulated financial institutions in the Nordics. KYC, KYB, transaction monitoring. Our users are compliance officers at banks, PSPs and fintechs. They spend their whole working day inside tools like ours, which is exactly why the craft matters so much here. In July 2027, the EU's new anti-money-laundering regulation (AMLR) starts to apply: one directly applicable rulebook replacing today's patchwork of national rules. Every institution in scope has to be able to show that its procedures follow the regulation — documented, running, and provable, down to individual decisions.
The product is dense, stateful and full of edge cases. Design quality is the difference between a compliance officer trusting the system and working around it.
The role
We work in small, tightly knit project teams where design and engineering explore ideas together, prototype together, and ship together. You will be part of projects from the first sketch to the release, working closely with our founders, engineers and compliance experts.
You own product surfaces end to end. Problem, prototype, production.
You prototype in code. Figma is where you think. The repo is where you decide.
You own the design system as a living thing in Storybook. Use code and Figma to make it right.
You sit with engineering, compliance, and customers. Our users are generous with feedback and genuinely want the product to be great. You will never wonder whether your work matters to someone.
AI-native, in the practical sense
Everyone can generate an interface now. That is not the skill. The skill is knowing which one is right, and being able to tell the difference fast, in a domain where plausible-but-wrong is a regulatory problem rather than a bad user experience. We expect you to be fluent with Claude Code, Cursor, Figma MCP or whatever else earns its place in your workflow, and to use these tools to raise the ceiling of what you personally ship.
Who this is for
We care about four things.
Taste. You can look at an interface and say what is wrong with it and why, precisely. You have opinions about density, about defaults, about when a modal is a cop-out. You care about speed and polish, and you push back kindly but clearly when something doesn't feel right.
Shipping. You have put things in front of real users under your own name and iterated on them. Live URLs beat case studies. A small component library on GitHub beats a deck. A short post explaining a decision you made and would defend beats both.
Systems. You think in components, states and behaviour rather than screens. You know which things should be reusable and which should stay one-offs.
Curiosity about hard, complex problems. The interesting work here is making a complex legal process legible and auditable. You are comfortable helping to shape the problem, not just implementing a solution someone else has specified.
Depth matters more than years, and more than whether you have carried this title before. Designers who learned to ship, and frontend engineers with real visual judgment, are both the right shape. Experience from a startup or a company with a genuinely high design bar is a strong plus.
What this is not
Not a team lead role. Not brand and campaign work. Not six months of discovery. You carry the design craft here, in a company with a real external deadline in front of it, and with a team around you that cares about the same things you do.
Practical
How to apply
Please use our application form. We look forward to hearing from you!
Check My Fit
