Liliia Orlenko
Senior / Lead Product Designer & Design Engineer

A hands-on designer working across product design, product strategy, and frontend implementation.

liliia.orlenko@gmail.com

Complexity, made to feel simple.

I'm an AI-native design engineer. Years in fintech and SaaS taught me to make feature-rich products feel calm and obvious. Working AI-native now lets me dive deeper into product strategy and system design.

Stack
Claude Claude Code Cursor GitHub Figma Adobe Creative Suite Maze Miro Dovetail Hotjar
Open to work
Ready to start immediately
Stockholm, onsite or hybrid
Fully remote across the EU and US
Targeting
Healthtech Climate tech Civic tech Lifestyle & everyday tools Complex system products
Interesting project? Contact me ↗
2025 — 2026View case ↗
EARN'M
Design Leadership · AI Automation
Led design across the product and set up AI-assisted design work across marketing, business, and engineering, backed by a shared system and Storybook.
3 Teams running on AI-assisted design functions: marketing, business, engineering
2 Design systems built, plus a shared Storybook
2021 — 2024View case ↗
Safe.Global
Senior Product Designer · Berlin (Hybrid)
A multi-signature wallet holding billions in digital assets. I made a complex, security-critical product feel manageable for very different kinds of users.
+9% Onboarding completion after lightweight UX test
+13% Executed transactions post-flow redesign
1,000+ Design system Figma copies within month one
2019 — 2021View case ↗
McMakler
Product Designer · Berlin · Full-time
A research-led redesign of the internal tools a German real-estate team used daily, plus a stronger design and research culture along the way.
18→32% User satisfaction across the platform
75% First-round design approval rate
Highlights
01
Safe design system, 1,000+ Figma copies in month one
Built for external contributors who would never talk to me
↗ 02
Challenged business decisions for better adoption
EARN'M. Pushed on subscription pricing and other calls that shape whether people stick with the product.
↗ 03
Proposed a research sprint that was not in the McMakler brief
One week. 75% first-round approval followed.
↗ 04
Storybook shifted design reviews from pixels to problems
EARN'M. Developer owns components. I own the decisions.
↗ 05
Alla was sunset three months after launch
McMakler. Low adoption is a research problem. I document that too.
↗
Approach
Systems over screens
A system's real job is to help teams work together. It gives marketing, business, and engineering a shared way to build with design instead of each team going its own way.
Research before production
The most useful things I learn come from being in the room while someone does their job, not from asking them to describe it afterward.
Accountable for outcomes
I write down what worked and what didn't. Recording the failures matters as much as the wins, because that's how a team learns and stops repeating the same mistakes.
AI-augmented, not AI-replaced
Claude Code, Cursor, and Figma Make are part of my daily work. They shift the balance between thinking and production, without replacing the thinking.