Staff Product Designer

Paybis has been moving money between crypto and traditional finance since 2014. We’re self-funded — no investor clock, no funding-round theatre — headquartered in Riga, with ~200 people across Europe, Ukraine and the US. 8.6M+ customers in 180+ countries and $5.5B in lifetime transaction volume have gone through our rails, at 4.1/5 across 32,000+ Trustpilot reviews.

We hold a MiCA CASP authorisation and a Payment Institution (PSD2) licence in Latvia — one of a small group of companies in Europe holding both at once — plus FinCEN MSB registration in the US. In a market where most crypto products are one regulatory decision away from disappearing, that’s the moat: we’re licensed to operate in daylight.

You’ll work next to our Product Design Lead and existing designers, share a design system with them, and give and take critique. Discovery, direction, interaction design, visual craft, prototypes, handoff, design QA after release — all of it is one person’s job, and that person is you.

You’ll partner directly with B2B product managers, engineers, the compliance and legal teams, and the partner-facing side of the business. You’ll spend time in front of actual partners, because enterprise UX can’t be inferred from analytics alone. Ownership here means the outcome, not the output: you are accountable for how the work performs after it ships, not for having handed over a file.

• Partner Portal. Redesign it from a feature list into a product: partner onboarding and KYB, integration and theming setup, transaction monitoring, analytics and reporting, account and team management. This is the single highest-impact surface you’ll touch.
• Corporate Account. Take corporate wallet, OTC and treasury workflows from concept to shipped product — dashboards, balances across chains, payouts, approvals, limits, dense data made readable.
• On/Off Ramp. Design the embedded ramp and swap experience partners put in front of their own users: high-conversion checkout, payment method selection, and a white-label system that stays coherent whoever’s brand it’s wearing.
• Compliance UX. Turn KYB, KYC, travel rule and MiCA requirements into flows people can actually complete. Regulatory constraint is a design material here, not an obstacle to route around.
• Enterprise patterns. Establish how complex B2B interfaces work at Paybis — data tables, filtering, empty and error states, permissions, notifications, transactional email — and extend our design system to carry them.
• Corporate website. Own paybis.com end to end: the Business and Corporate sections, landing pages for new products and markets, the Personal/Business audience switch, localised variants, and the page system underneath. This is a primary surface, not a side task — it is the first thing a prospective partner sees.

• Contribute to targeted improvements on the consumer web and mobile apps: onboarding, checkout conversion, and closing the gap between web and native.
• Keep the consumer and business sides coherent where they share a design system, without pretending an enterprise dashboard and a retail buy flow are the same problem.

This split is deliberate and we intend to hold it. B2B is where the volume, the growth and the design debt are.

• Month 1–2. Audit the B2B surface end to end, the corporate website included. Talk to partners, PMs, compliance and support. Come back with a prioritised, evidenced view of what’s broken, what it costs us, and what you’d do first — and start on the highest-impact piece while you’re still forming the rest. We expect hypotheses with numbers attached, not a list of observations.
• Month 3–4. Ship the first meaningful redesign inside the Partner Portal. Establish the enterprise patterns and design system additions it needs, so the second and third projects go faster than the first. In parallel, put a design direction and a reusable page system under paybis.com.
• Month 5–6. Corporate account design direction is shipped or in development. Integration and KYB onboarding are measurably easier to complete. The corporate website ships against a real page system instead of one-off layouts. Engineers stop asking what a state should do, because the specs answer it.

We measure this in shipped work and moved metrics — partner activation, integration time-to-live, conversion, support volume — not in strategy decks.

• 8+ years designing digital products end to end, with substantial time at senior, staff or principal level. Shipped work that real users depend on, not concepts.
• Depth in complex B2B, enterprise or infrastructure products. Dashboards, admin and partner-facing tools, data-heavy workflows, configuration, permissions. You’ve made something genuinely complicated feel obvious.
• Fintech, payments, crypto or another regulated domain. You understand compliance-first design, trust and security signals, transaction flows, and what “we can’t ship that, legally” means before legal has to say it.
• Full autonomy and ownership. You own the entire design process and its result — problem definition, direction, execution, handoff, and how the thing performs once it is live. You operate without a brief, decide under ambiguity, sequence your own work, and never wait for a design lead to unblock you or to check the work.
• Strong UI craft — non-negotiable. This one is a hard requirement, not a preference. Typography, layout, grid, hierarchy, density, colour and state design: your screens should look finished, not approximately right. Sharp UX judgement sits on top of that craft, never instead of it. High-fidelity prototyping — motion, state, interaction — to communicate intent and to test it.
• Design systems as a practitioner. You’ve built and extended systems with tokens, components and variants at expert level in Figma, and kept them healthy while the product moved.
• Data-informed practice. Qualitative research and quantitative signals, experimentation, and honesty about what the numbers do and don’t say.
• Proactive, not reactive. You arrive with hypotheses instead of waiting for tickets: you spot the opportunity, frame it, name the metric it should move, and push it onto the roadmap yourself. Every proposal comes with the number it is meant to shift and how you will know whether it did.
• Direct, clear communication in English. You write well, present decisions without decoration, disagree productively with PMs and engineers, and change your mind when the argument is better than yours.
• Thoughtful use of AI in your workflow — for exploration, iteration and validation — with the judgement to know where it helps and where it produces plausible nonsense.



What your portfolio needs to show: at least one deep case study on a complex B2B or enterprise product — the constraints you worked under, the decisions you made, what shipped, and what it changed. We’d rather see one hard problem told honestly than ten polished screens. We also want to see web work: a corporate or marketing site you designed end to end. And we will look hard at the UI itself — craft is judged from the screens, not from the write-up around them.

• Experience with white-label or embeddable products, where your design has to survive someone else’s brand and someone else’s implementation.
• Native mobile at scale (iOS/Android), shipped to millions of users.
• Multi-market and multi-language design across different regulatory environments.
• Familiarity with front-end constraints: you can read the code, talk to engineers in their terms, and design something that can actually be built.
• Published writing, conference talks or other design community involvement — useful, not required.

• Full ownership of a product area that matters.
• No design management overhead. No reports, no hiring plans, no performance cycles. You design.
• Direct access to decisions. You report to the Product Design Lead and work alongside product, engineering and executive leadership — design input is expected before the roadmap is set, not after.
• A self-funded, profitable company. 12 years in business, no investor timeline forcing product decisions, no runway anxiety.
• One of the more interesting product landscapes in European fintech — regulated crypto infrastructure, enterprise B2B, consumer scale, and real compliance constraints to design against.
• Remote-first with genuine flexibility, async by default, quarterly in-person sessions in Riga.
• Medical insurance, professional development and conference budget, corporate English classes, modern tooling.

• HR Screen
• Hiring manager screening with Lead Product Designer (45–60 min) — portfolio review, a first look at UI craft, product thinking, fintech and crypto context alignment.
• Design assignment — a real or anonymised Paybis B2B challenge, worked through together.
• Feedback session after design assessment (45–60 min)
• Culture fit (30-40 min)
• Reference check