Aleksandar Tasevski

Background

+3

I 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, Panther

Recognition

The work I was shipping on my own eventually opened doors I had not 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 launch to millions of users.

Adobe PartnershipGrammarly IntegrationFigma Early Access

Ventures

I run my own portfolio of products I design, build, and ship myself. 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 Design300k+ Users1k+ Paying Customers

"Aleksandar is a thoughtful product practitioner. He has a great blend of empathy and collaboration skills to get to know users and work with other stakeholders to deliver value that is aligned with the business goals." Rob Fagg — Head of Product, H4

• 
  I start with why.

  Before touching a design tool I define the problem. Why this feature, who it serves, and what success looks like — these come first. I read support tickets, watch user sessions, and talk to customers until the problem is clear enough to own.

• 
  I think in systems.

  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 controlled demos.

• 
  I obsess over craft.

  Nothing I put on screen is random. Spacing, hierarchy, colour, motion — each is a deliberate decision. I have 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.

• 
  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 and staying until it ships.

• 
  I write for alignment.

  Design rationale, tradeoffs, and options get documented — so decisions are not dependent on meetings or individual memory. It gives engineers, PMs, and designers a shared reference across the full lifecycle of a feature, not just at the moment things were agreed.

• 
  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.