AboutExperienceWorkContact
Available for new roles

ProductDesignLeader

12 years shaping fintech products, building design orgs from zero, and turning complex B2B systems into experiences that ship and scale.

12+
Years
13
Team size
400+
Components
€300M
Raised
UX ArchitectureDesign SystemsTeam BuildingFintechAI WorkflowsProduct StrategyCross-domain UXB2B SaaS UX ArchitectureDesign SystemsTeam BuildingFintechAI WorkflowsProduct StrategyCross-domain UXB2B SaaS
About
Strategy meets
execution

I work at the intersection of strategy and craft — turning cross-domain complexity into scalable UX architecture, aligning product & engineering around clear decisions, and shipping systems that hold up over time.

Built design functions from scratch twice, shaped product direction across payments, accounting, lending, and AI-powered workflows.

UX Architecture
Cross-domain systems
Design Systems
400+ components
Team Leadership
0 → 13 twice
AI Workflows
Shipped to prod
Product Strategy
CPO-level planning
Fintech Domain
12 years deep
Career
Where I've
made impact
Finom
2019 — 2026
Head of Product Design
European neobank for SME. 100K+ clients, €300M+ raised (General Catalyst, Northzone). Unified cross-domain UX architecture. Launched AI CFO, Cards, Accounting, E-invoicing, Credit. Scaled design system to 400+ components. Built org from 0 to 13.
Modulbank
2014 — 2019
Head of Product Design
Digital banking for SME. Built design function from scratch. Launched Lending, Deposits, Acquiring, POS terminals. Designed complex banking flows.
Unicloud Labs
2012 — 2014
Product Designer
Web products. UX/UI, prototyping, close collaboration with engineering.
Selected work
Case
Studies
01
Fintech · 2019–2026
Finom
Head of Product Design
Multi-product European neobank. Full case study: design infrastructure, AI features, reconciliation, team building.
02
Fintech · 2014–2019
ModulBank
Head of Product Design
Digital banking from zero. Complex banking flows, lending, acquiring.
03
Mobile
NeClub
Product Designer
Mobile product — UX, interaction design, end-to-end delivery.
04
Mobile
Easy Anatomy
Product Designer
Educational mobile app — complex medical data made accessible.
Get in touch
Let's build
something great

Open for leadership & senior IC product design roles

dinar@galimov.netLinkedIn ↗Telegram ↗
Head of Product Design · 2019–2026
Finom

European fintech for SMBs: multi-banking, payments, cards, accounting and AI-assistant in one product. 100K+ clients across 5 EU countries, €300M+ raised, 500+ employees.

100K+
Clients
€300M+
Raised
500+
Employees
5
EU Markets
01

Context & Role

Finom — European fintech for small and medium businesses: multi-banking, payments, cards, accounting and AI-assistant in one product. Key markets: France, Germany, Netherlands, Italy, Spain.

I joined Finom at an early stage when there was no design function. For the first months I was the only designer: simultaneously shipping key product tasks and establishing quality standards that the growing team would build upon.

🎯
Focus

Quality infrastructure — principles, patterns, and culture that enabled the team to consistently deliver strong design at scale.

My Role — Head of Product Design

🏗️
Built from zero

Design organization from first decisions and processes to a full team.

👥
Hiring & growth

At peak — 13 designers (8 product, 5 marketing) with parallel responsibility.

⚙️
Operating model

Involved at task framing, concept, and design review stages. Domain designers carried solutions to production.

Hands-on

Visual language integrity, UI quality, and design system evolution across product and brand.

02

What "Building Design from Zero" Means

When I joined, there was no design as a system: no unified UI principles, no design system, no clear workflow with product, engineering, and QA. Meanwhile, the product was evolving fast, and fintech doesn't forgive errors or inconsistency.

" Speed without system creates debt. System without speed doesn't survive in a startup. I built processes to accelerate delivery and protect quality at scale.

Four Layers of Infrastructure

01
Design System & UI Standards
Unified product language
  • Defined visual language and foundational UI principles
  • Created and evolved the component and pattern library
  • Established consistency and accessibility standards so domains don't diverge
📄 UI principles + key patterns (navigation, forms, tables, empty states)
02
Documentation & Artifacts
Fast onboarding, predictable handoff
  • Built file structure and formatting rules for quick navigation
  • Standardized artifacts: specs, states, edge cases, annotations
  • Organized versioning and solution reuse
📄 Spec page template + "ready for dev" checklist
03
Product Workflow
Transparent decisions, less chaos
  • Fixed design entry points: discovery → framing → UI → dev prep
  • Reviews check quality and systemness, not individual taste
  • Supported domain designers bringing initiatives to production
📄 Design review format (criteria, expected inputs, definition of done)
04
Engineering & QA Integration
Quality reaches production
  • Built handoff practices so design is implemented without loss
  • Embedded UI quality checks: what, when, and who's responsible
  • Design ↔ engineering ↔ QA rules to reduce rework
📄 UI QA checklist + discrepancy tracking
📌
Main result

Domain designers could autonomously complete projects, and my role shifted to system quality, direction, and review.

03

Team: How I Built It

I built an environment where quality and speed scale together. Started alone, for several months handled all design myself. As the company grew, assembled the team: led search, selection, onboarding, and development.

8
Product Design

Domain designers assigned to verticals, leading initiatives end-to-end.

+
5
Marketing Design

Brand communications, growth, and marketing surfaces.

=
13
Unified Team

One design system and one visual language for product and brand.

Culture & Ways of Working

  • Regular design reviews with transparent quality criteria: principles, systemness, accessibility, consistency.
  • Standardized artifacts and documentation so decisions read the same across design, product, and engineering.
  • Maintained hands-on standards: UI details, visual integrity, and system evolution remained my responsibility.
🤝
Team Goal

Domain autonomy without quality erosion: local team speed + unified user experience.

04

Product Impact

At Finom I influenced results through UX architecture, patterns, and execution quality that withstood product and team growth. My focus — turning complex fintech scenarios into solutions that can be repeated, evolved, and shipped without losing integrity.

Involvement Model

Framing

Turn ideas into clear problems, scenarios, and success criteria aligned between product, design, and engineering.

Architecture

Formulate UX models and system patterns before the team goes into UI details.

Review

Maintain execution level and consistency so decisions don't depend on individual "taste".

Cross-domain

Take on the riskiest zones — where one scenario passes through multiple domains, roles, and states.

Strongest Impact Areas

  • Cash flows and reconciliation: invoicing (including e-invoicing), document recognition, linking transactions to documents and exception management.
  • AI as new interface: assistant concept and AI Accounting (in production) — from UX architecture to key user scenario.
  • Unified product experience: dashboard as control center, navigation rules and experience architecture across domains.
  • High-stakes banking: cards and credit — clarity of conditions, statuses, risks, and consequences.
🏁
Core Strength

Connecting product strategy, UX architecture, and delivery quality so the team could rapidly ship complex fintech scenarios without experience erosion.

05

Mini-case: AI in Product

I used AI not as a "feature" but as a way to change interaction with the fintech product. Two manifestations: AI Accounting (production, Germany) and AI Assistant (concept, in development).

● Live

AI Accounting

Production · Germany · 2024–2025

Context: SMB accounting often looks like constant "background debt": deadlines, scattered documents, unclear categories, endless clarifications. We built an experience that removes routine and partially takes over the bookkeeper role where automation is possible.

My contribution: UX and architecture design at the early stage. Making the process clear and manageable: so the user sees what to do next, why it matters, and what the result will be.

Key Value

  • Removed routine and part of bookkeeper functions: the client can independently prepare and submit tax reports without depending on a bookkeeper.
  • Lowered the accounting entry barrier: the user doesn't need to know rules and nuances to start working correctly.

Key Decisions

1
AI categorization "by default"

User uploads a document, system fills categories and suggests results for review.

2
AI as coordinator

Collects missing context and asks clarifying questions on its own.

3
Reporting calendar

Deadlines, obligations, and statuses in one place with reminders.

4
Weekly loop

Once a week — a short action list for documents and categories where automation isn't confident.

5
Draft-first reports

Report forms as a draft that just needs review and submission.

Upload → auto-categorize → weekly tasks → draft report → review & submit
◌ Concept

AI Assistant

In development · 2025–2026

Context: As Finom grew, users found it harder to locate features and solve individual problems. This increased support load and heightened questions about pricing transparency.

Idea: Create an "intent-first" entry point — a layer that knows product context and the specific business, guiding toward task resolution in plain language.

My contribution: Designed the concept and UX architecture as a cross-product layer: scenarios, responsibility boundaries, and trust patterns.

Key Decisions

  • Not "support chat" but an agent: proactively tracks business situation and suggests actions.
  • Completes tasks in dialogue: guides through the process and executes steps right in chat.
  • Trust patterns: errors, uncertainty, result explanation, checkpoints (when confirmation is needed).
  • Escalation: in complex cases — soft handoff to live support.
06

Mini-case: Reconciliation

I designed the unified cash flow management experience: from receiving money through invoices to closing transactions with documents. Not just "store documents" — keep the financial picture under control.

Key Decisions

🔗
Automatic matching

Clear logic (including by amount) and explainable rules.

✏️
Manual override

Override links and correct results when automation is wrong.

⚠️
Exceptions first

UX for cases where the match is non-obvious or data is insufficient — as a default scenario.

Document → Transaction → Status → Action (auto / manual resolution)
07

Results & Reflection

When I joined, the design function didn't exist. Today Finom is a multi-product fintech with multiple domains and dedicated AI initiatives.

Organization Level

  • Built the design organization and a reproducible delivery process.
  • Created and evolved a unified visual language and design system for consistency at scale.
  • Established design ↔ engineering ↔ QA integration, reducing implementation losses and accelerating the cycle.

Product Level

  • Systematized UX for complex SMB fintech scenarios, making them simpler and more predictable.
  • Laid the AI foundation: AI Accounting reached production, the assistant formed the base for the intent-layer.
" At scale, systems win — principles, patterns, and processes that make quality reproducible.

What I'd Do Differently

  • Establish unified guardrails for cross-product navigation and layout earlier to reduce divergence between domains.
  • Embed UX quality measurement into the regular cycle earlier: support contact reasons, time-to-task, recurring errors.
Case Study · Head of Product Design · 2014–2019
ModulBank

Business bank and digital banking platform for SME. Pioneering digital-first banking for small business.

What I Did

  • Built design function from scratch: team, processes, standards.
  • Designed complex banking flows: payments, accounts, transaction management.
  • Key launches: Lending, Deposits, Acquiring, POS terminals.
  • Established scalable design practices for rapid company growth.
💡 First experience building a design organization from zero — lessons I later applied and scaled at Finom.
Case Study · Mobile Product
NeClub

Mobile product for a social/community platform.

End-to-end UX/UI, user research, interaction design, prototyping and usability testing.

Case Study · Mobile Product
Easy Anatomy

Educational mobile app making complex medical anatomy accessible.

Intuitive information architecture, interactive learning flows, and mobile-first design approach.