Evgenii ShmoishSenior UX Designer

I design the software that experts live in all day.

10 years in UX design, 8 in enterprise software. I design interfaces, build working tools and use research and usage data to guide improvements.

Helsinki, Finland · Native German and Russian · Professional English

EmailLinkedInFigma

FA Solutions4 years (present)

Bringing clients into product decisions

As FA’s first UX designer, I established research, prototyping and validation across four product teams.

  • Client involvement. I introduced interviews, prototype reviews and usability testing with clients across five countries, so their needs could shape decisions before development.
  • A process from discovery to delivery. I brought structure to the work: gathering requirements, exploring ideas, validating designs and handing them over to development.
  • Shared UI. I established a design system and reusable components to help teams build consistent interfaces.

FA’s platform covers portfolio and fund management, trading, compliance, reporting, and a client portal.

80+ client organisations · 15 feature areas

FA Solutions ↗
KALO · Kalorimeta4 years

A shared design foundation for a platform renewal

During a major platform transition, I introduced research and prototyping practices and built a design system across enterprise, mobile and consumer applications.

  • Discovery and validation. I gathered requirements, interviewed users and tested interactive prototypes to shape applications before development.
  • Design system. I built the component library and design system for the new applications, connecting design decisions with frontend implementation.
  • Cross-team delivery. I coordinated three designers and a frontend developer group to carry those patterns through implementation.

Metering and billing for housing. Public digital services include the customer portal, resident portal and KALO Home consumption app.

50+ locations across Germany

KALO ↗

I make complex problems
clear enough to solve together.

I connect customer conversations with the evidence a company can collect. Working prototypes help us test a direction; usage data helps us decide what to improve.

  1. 01UnderstandWhat is happening?
  2. 02Make it clearDo we see the same thing?
  3. 03ExploreWhat could work here?
  4. 04DecideWhat do we need to test?
  5. 05LearnDid it help people?

What we learn changes what we do next.

  1. 01

    Understand the problem behind the request.

    I first establish what the company can already observe: usage data, funnels, monitoring and customer feedback. I combine that evidence with client conversations to identify where people struggle and what needs investigation.

    For example: a drop in completion is a starting point. I investigate whether people misunderstand a step, encounter an error or wait too long.

  2. 02

    Make it clear enough to think together.

    I turn findings into sketches, diagrams and working prototypes. Teams and clients can explore the idea, question assumptions and correct my understanding.

    The picture is useful when people can think with it.

  3. 03

    Find options that fit the real product.

    I explore solutions within the existing product and design system. With developers, I compare effort, constraints and trade-offs. With clients, I look for needs beyond the original request. A rough sketch or a working prototype makes those conversations concrete.

    One client’s request can reveal a need shared by many.

    An example of how I explore ideas How I work with agents
  4. 04

    Find the evidence a decision needs.

    I turn an observation into a testable hypothesis and agree what success would look like. I choose the method to fit the question and the available tools: usability tests, funnel analysis or A/B testing when traffic supports it.

    For example: if unclear instructions might cause people to abandon a form, I test clearer wording and check completion alongside errors.

  5. 05

    Use the results to choose the next change.

    After release, I review completion, drop-offs and errors with the data the company has. I combine the numbers with user feedback to decide what to keep, adjust or investigate next. A change in a metric alone does not explain its cause.

    For example: if completion improves but errors remain, I investigate the affected step before extending the change to other flows.

I build agent tools
for thinking together.

I build tools that teams use to explore product decisions together. Product knowledge, reusable components and automated checks give the work a consistent foundation.

  1. TrustShared understanding
  2. EngineeringReliable foundations
  3. ProductA useful tool

What we learn improves the context, code and tools.

Shared documentation and domain knowledge give agents context. Strict TypeScript, reusable components and automated checks guide how they build.

The outcome can be a prototype, a research wiki or a testing tool. The problem determines the form.

Teams already prototype with my agents.

  1. RequirementsTickets & questions
  2. Working prototypeBuilt in the meeting
  3. Team discussionTry, question, refine

I built agents that use product documentation, existing interfaces and UX guidance to turn tickets into working prototypes. Teams use them during discussions to try alternatives and clarify requirements.

I use shared components and strict TypeScript so the prototypes reflect the frontend we work with. I review the generated code and the behaviour it produces.

Agents support a designer, who presents a working interface to a group of people.

I own the decisions
and the result.

I frame the problem, choose what to build and review both the interface and its implementation. I present the result to teams and clients, then use their feedback to guide the next iteration.

The question decides which tool I use.

I choose the form that helps people respond: a sketch to clarify an idea, or a working prototype to try a task.

  1. The screen as a wobbly pencil wireframe on paper: a list, a detail pane, a crossed image box and a button.
    SketchesPaper and whiteboards help me explain a thought while it is still easy to change.
  2. The same screen in marker on a whiteboard, with two sticky notes on it. One note asks a question.
    WorkshopsI bring the people who know the problem together to question and clarify it.
  3. The same screen as a clean high‑fidelity Figma frame with a frame name above it and pale fills.
    FigmaDetailed prototypes let people respond to the layout, content and behavior of a proposed interface.
  4. The same screen built in React in a browser: rows of real data, a chart in the detail pane, and a pointer on the one highlighted button.
    ReactWorking prototypes let people try realistic tasks with realistic data, including interactions a static screen cannot show.
  5. The same screen being built by an agent: the list stands, the detail pane is a petrol dashed edge still open, and a prompt line with a cursor sits below.
    AgentsI can build interactive drafts during a discussion, test ideas sooner and iterate faster.

5 published plugins.
Designed and built by me.

I take recurring problems from my design work through design, implementation and publication. My 5 Figma plugins cover website import, typography, data grids and images.

Web Import Master

Bring a website into Figma as an editable document.

Web Import Master demo video

I designed and built a Chrome extension to capture a page in the browser, and a Figma plugin to rebuild it as an editable document.

I chose a local workflow: no sign-up or upload, with support for pages already open behind a login. The published extension, plugin and demo show the working result.

PluginChrome extensionDocs

Four more tools, each built around one recurring task.

  • Text Styles Manager demo video
    Text Styles ManagerCreates a typography system and applies it to the whole document, variables included.
  • Data Grid Master demo video
    Data Grid MasterTurns a spreadsheet into a data grid built from your own components.
  • Mask Master demo video
    Mask MasterImage masking with adjustable threshold controls.
  • Image to Vector Master demo video
    Image to Vector MasterConverts raster images to editable vectors.

All plugins on my Figma profile

Curiosity has always
made me build things.

  1. At 4

    My father built a customized Sinclair computer for me. I still remember it vividly.

  2. At 14

    I made my first software tools to make my video games more interesting.

  3. At 18

    I explored the internet and built small websites for friends.

  4. At 24

    I studied communication design. My final project became my first startup.

  5. At 35

    I discovered agents as a way to turn more of my ideas into working experiments.

Outside of work, I lift, cook
and stay curious.

  • BodyHeavy weightlifting and time outdoors in nature.
  • MindScience, philosophy and psychology. My favorite channels are Veritasium, Kurzgesagt and Be Smart.
  • HandsGood food and cooking. Woodcraft, drawing and painting.

evgenii.s@posteo.deLinkedIn