Senior Product Designer

Jana Gonsenicova

I can hand over working software, not just a spec. From research to merged pull requests, I design and ship time-tracking products across web, desktop, and mobile at Toggl.

I design for complexity users shouldn’t have to see. The underneath still need to account for what can happen, and what happens next.

I map the rules before I draw the screen: what can happen, what happens next, and where those states collide. The interface comes after the logic.

I explore in , then converge and strip.

I don’t explore in isolation. I bring developers in right during exploration and pull in PMs and customer-facing teams when their context can change the answer. When something is easier to understand in code, I build it there.

Where it helps, I hand over working software, not a spec: a with the behaviour specified across states.

It runs in the production codebase and the team’s own design system, with the loading, empty, error and edge states in place. When the team works from frames, it comes back into Figma as static screens for review and handoff. I use AI tooling, MCPs and skills to work directly in the codebase; everything I open goes through the same review as anyone else’s. Some of it merges directly; the rest engineers build from and cite in their own pull requests.

I trust over taste, including my own.

The method follows the question: production usage, surveys, interviews, usability testing, churn data. When the evidence disagrees with my solution, the solution changes.

This site is my own build.
The commits are real