icvc.framer.website/about:iulia

To: whoever's on the other side of this

I'm a product designer who cares about the full picture. The logic of a flow, the structure of a system, or the details of a component nobody will notice until it's wrong. I build things that hold up under real use, and that moment when something finally works the way it should is still what drives me.

Next, I want to join a team where design gets built alongside the code, by people who care about both.

I'm a product designer who cares about the full picture. The logic of a flow, the structure of a system, or the details of a component nobody will notice until it's wrong. I build things that hold up under real use, and that moment when something finally works the way it should is still what drives me.

Next, I want to join a team where design gets built alongside the code, by people who care about both.

WHAT I FOCUS ON
WHAT I FOCUS ON
design systems
Deciding what a component should do, what it shouldn't, and what to call it.
complex workflows
Multi-step tools where the edge cases outnumber the happy path.
design to dev
Specs an engineer can build from without a follow-up call.
accessibility
Contrast, focus order, and keyboard paths, settled while the design can still change.
design systems
Deciding what a component should do, what it shouldn't, and what to call it.
complex workflows
Multi-step tools where the edge cases outnumber the happy path.
design to dev
Specs an engineer can build from without a follow-up call.
accessibility
Contrast, focus order, and keyboard paths, settled while the design can still change.
HOW I WORK
HOW I WORK

The most interesting design problems are system problems that surface through the interface, where user needs, business constraints, and technical reality all push against each other.

I like working inside that tension. A lot of it happens in conversations, untangling those forces early so the team ends up building the right thing. My process follows the same logic: I explore wide and fast with AI, then slow down for the calls that need real judgment.

The most interesting design problems are system problems that surface through the interface, where user needs, business constraints, and technical reality all push against each other.

I like working inside that tension. A lot of it happens in conversations, untangling those forces early so the team ends up building the right thing. My process follows the same logic: I explore wide and fast with AI, then slow down for the calls that need real judgment.

WHAT'S NEXT
WHAT'S NEXT

The direction I'm building toward is design engineering: sitting inside the code, shaping implementation directly, and keeping AI agents reliable in production.

Reckon is one of the first products I'm taking through that full loop myself. The engineering side is where most of my learning is going right now.

The direction I'm building toward is design engineering: sitting inside the code, shaping implementation directly, and keeping AI agents reliable in production.

Reckon is one of the first products I'm taking through that full loop myself. The engineering side is where most of my learning is going right now.

PERI
THX FOR VISITING!
tap to say hi to Peri
~/about>log
readingThe Path to Senior PD
playingNivalis Nights
learningFrontend Development
workingReckon: Phase C (Capture flow)
~/about>
// PERI.SYS v2.0: a pixel pet wired to a terminal. She idles, the log reports what I'm up to.

Create a free website with Framer, the website builder loved by startups, designers and agencies.