Aleksandar Tasevski | Product Designer

Experience

Startups

Leah · Panther · H4

Started in R&D, working on ideas and prototypes across social networks, touch interfaces, and smartphone operating systems — all emerging fields at the time. Then a career built entirely in hard B2B domains: video infrastructure, knowledge management, legal contract workflows, global payroll compliance, enterprise agentic AI. A different industry every few years, always complex. That range is not accidental — it is what happens when you can be trusted with problems that matter.

"Aleksandar has a very strong product mindset, actively participates in all phases of the product lifecycle, and is capable to quickly adapt to new tools, processes, and requirements. He was an integral part of helping us ship two products, and hit the ground running on his first day." – Sanja Zakovska, Head of Product at Panther

"Aleksandar is a thoughtful product practitioner. His design skills are excellent and he is efficient. More importantly he has a great blend of empathy and collaboration skills to get to know users and work with other stakeholders to deliver value for the user that is aligned with the business goals." – Rob Fagg, Head of Product at H4

Collaborations

Adobe · Grammarly · Figma

The work I was shipping on my own eventually opened doors I hadn't knocked on. Adobe funded it through multiple grants, provided early API access ahead of their platform launches, and featured my plugins at their keynotes. Grammarly brought me in to consult on embedding their product into designer workflows. Figma invited me into the early access program for Slides plugins and featured the work in their public launch to millions of users.

Adobe Partnership Grammarly Integration Figma Early Access

Independent

Mighty Tools

I run a small portfolio of products I design, build, and ship entirely on my own. In recent years mostly plugins — for Figma, Adobe Express, and Canva. Three platforms, three different APIs, three different review processes. I know what each one requires to get built, approved, and used at scale.

Adobe Fund for Design 300k+ Users 1k+ Paying Customers

How I Work

01. I start with why.

I start by defining the problem before touching a design tool. Why this feature, who it serves, and what success looks like come first. I read support tickets, watch user sessions, and talk to customers until the problem is clear enough to own.
02. I think in systems.

I think in systems, not screens. Every decision affects users, engineering, and business outcomes, so I design with all three in view. I map flows, pressure-test edge cases, and work through constraints so the solution holds up in real use, not just in demos.
03. I obsess over craft.

Nothing I put on screen is random. Spacing, hierarchy, color, motion — each is a deliberate decision. I've spent years studying products I admire to understand exactly why they work, and that is what tells me when to follow a rule and when to break it.
04. I ship with the team.

I join standups, read the backlog, and speak the language of engineering, marketing, and business. I care about what the team ships, not just my part of it. That means flagging problems early, staying until it ships, and documenting decisions so nothing's lost.
05. I follow the signal.

A tool is only as good as the thinking behind it. I do not follow hype. I know where AI helps and where it does not. I treat its output as working material, not finished work, and I stay fully accountable for product decisions and final quality.

If this sounds like the mindset you need on your team, let's talk.