UX/UI Designer & Developer · 8+ yrs Worldwide

Pavel Evtushenko.

I turn messy ideas into clean pages and flows, then build them so they actually ship.

Pavel Evtushenko, portrait
Scroll
01

Who I am

I'm a UX/UI designer and developer with 8+ years in the field. Most of my work is for small businesses and startups where I own the whole path, from early sketches to the live site. That usually means UX and UI in Figma, and when it makes sense, building the thing in Framer or Webflow myself so it reaches production faster and keeps its quality along the way.

Background

I started out designing apps, which taught me to think in flows, states, and real device constraints. These days I lean more toward web, because it gives small teams a better return on their budget and I find it a more interesting space to work in right now.

Style

I do my best work with teams that like clarity and straight answers. If you want a designer who talks to you like a person and keeps the project moving, we'll get along.

02

How I work

Short loops, small deliverables, and more questions up front than you probably expect. I'd rather catch a misalignment in week one than in week four. Progress stays visible, decisions get written down, and nothing I design is going to fall apart the moment someone tries to build it. On the build, I use AI-assisted tools like Claude Code where they genuinely speed things up, so production moves faster and more of the time goes to the decisions that actually need judgment.

  • Short loops, small deliverables
  • Lots of questions early on
  • Designs built with the handoff in mind
  • AI-assisted build where it speeds things up
  • Direct feedback in both directions
  • Transparent about where we are
03

Principles I keep

P.1

Clarity first

I simplify before I decorate. A clean structure beats a pretty one that confuses people.

P.2

Structure matters

Good hierarchy and readable layouts do more work than any effect or gradient.

P.3

Design that earns its keep

The work has to support what you're trying to do. Looking good is not the same as working well.

P.4

Short loops

I move fast with small, concrete options so feedback stays focused.

P.5

Clean handoff

Organized files, consistent components, decisions written down. No guessing when the build starts.

P.6

Honest timelines

I'd rather say "that's two weeks" and deliver in ten days than oversell it.

P.7

Built for small teams

I'm used to tight budgets and the reality of needing to launch something, not ship it to a drawer.

P.8

Easy to work with

I reply, I stick to what I said, I don't waste your time.

Have a project in mind?

Let's start