Open to senior product design roles · Skopje / remote EU

I design the parts of products nobody screenshots.

Design systems, rule engines, workflow platforms, dashboards — the structural layer of complex B2B products. And lately: products I design, architect, and ship myself.

§ 01

Selected work

2020 — 2026 · 4 OF 4

01 CUT RELATED SUPPORT TICKETS BY 40%

Complimentary Tickets

A wizard for two very different users — CS agents comping hundreds, organizers comping five. Three steps: recipients, ticket types, per-item assignment. Shipped at Events.com.

Read case study →

02 TARGETING LOGIC UNMATCHED IN THE INDUSTRY

Bonus Configuration System

A composable rule engine for casino operators — behavioral, temporal, financial, and account-state conditions, nested to any depth. Legible at five levels.

Read case study →

03 VALIDATED WITH REAL ORGANIZERS

Event Dashboard

A dashboard that reshapes itself around what the event needs — pre-event, during, post-event. Phase-aware layout, tested with real event organizers.

Read case study →

04 3 SYSTEMS · 1,000+ TOKEN REPLACEMENTS · 150+ PAGES

Design Systems Practice

Three systems, five years, one maturing architecture — culminating in a full dark-theme migration on a two-layer token model. The newest system is under NDA, shown schematically.

Read case study →

APPENDIX A

Also worth seeing

SHIPPED · UPPED EVENTS

The Token Payment System

Several US states require alcohol at events to flow through a centralized point of sale — Michigan's sell-at-cost rule effectively mandates a token economy: attendees buy tokens from the operator, then redeem them at vendor stalls. The solution wasn't novel. Making it work cleanly across a three-surface platform was.

I led design across all three surfaces: dual fiat / token pricing on every item in the admin panel, tokens as a first-class wallet with a pre-arrival purchase flow in the attendee app, and token transactions alongside cash and card at the point of sale, on custom event hardware. Shipped and used at real events. The point: one decision at the admin level cascades into every downstream surface — cross-product design at its clearest.

Admin panel — item creation with dual fiat and token pricing — FIG. A1 — Admin panel: dual pricing on every item — a fiat value and a token value. One decision with cascading effects across three surfaces.

Attendee app — tokens as a first-class wallet — FIG. A2 — Attendee app: tokens as a first-class wallet concept, with a dedicated purchase flow before arriving at the venue.

Point of sale — token transactions alongside cash and card — FIG. A3 — Point of sale: token transactions alongside cash and card on Upped's custom event hardware.

Token management — operator overview of issuance, redemption, reconciliation — FIG. A4 — Token management: operator overview of issuance, redemption, and reconciliation.

§ 02

Products I've built

DESIGNED · ARCHITECTED · SHIPPED

I design the product and make every decision that shapes it — data model, auth, infrastructure, scoring logic, sync strategy. Claude Code executes the implementation under my direction: the decisions are mine, the typing is delegated. My specialty has always been the structural layer of software; directing AI at that layer is what it looks like now. These products are the proof, not the claim.

P.01 Ran the 2026 World Cup · Complete

World Cup Picks

A prediction league that ran the full 2026 FIFA World Cup in production — group stage through the final, 48 teams, real users, live match data syncing daily. Built solo.

The completed tournament is the point: the app survived a live competition end to end, including knockout reseeding under real fixture data.

It started as Kruševo Picks, an NBA bracket app for friends built on Firebase — the World Cup version is its full rebuild on a proper Postgres backend.

Open the app — final standings live ↗

Decisions I owned

Supabase / Postgres · Google Auth
Hybrid data pipeline — API-Football + ESPN
Three daily cron jobs
Reseeding knockout bracket
Conviction-bonus scoring — 2 / 4 / 6 / 8 / 10
Golden Boot side game
Netlify hosting

World Cup Picks final standings — league leaderboard with conviction bonuses — FIG. P1.1 — Final standings: league leader and conviction deltas

World Cup Picks scoring breakdown — group rankings, knockouts, conviction bonus, Golden Boot — FIG. P1.2 — Where the points came from: rankings, knockouts, conviction, Golden Boot

P.02 In development · Phase A complete

RentBase

A two-sided trust-record app for landlords and tenants — a verifiable rental history both sides can stand behind. React, TypeScript, Supabase, Capacitor.

Trust products live or die on data integrity, so the integrity guarantees live in the database, not in app code.

Before any code: a documented multi-lens spec audit runs across every core flow — the review rigor of a full team, packaged as protocol.

Decisions I owned

Client-minted UUIDs
Immutable audit trail — append only
Roles enforced in Postgres RLS, not app code
Local-first · outbox sync pattern
Capacitor for Android · PWA for iOS
Multi-lens spec audit before build

CLIENT — LOCAL-FIRST

UUIDs minted on the device · fully functional offline

OUTBOX — queued writes, replayed on reconnect

SUPABASE / POSTGRES

Row-level security enforces roles · append-only audit trail

SAME RULES FOR EVERY SURFACE

SURFACES

Capacitor — Android · PWA — iOS

FIG. P2.1 — Sync & trust architecture (schematic)

P.03 In active development

LiftLog

A couples-oriented fitness PWA for gym beginners — two people training together, one shared record. Supabase, Netlify, PWA.

Problems I'm designing

Injury contraindication warnings inside exercise selection
Shared-accountability layer for training partners
Adaptive calorie / TDEE logic

LiftLog Today view — workout session card with coaching cues — FIG. P3.1 — Today view: session card with coaching cues

§ 03

About

SKOPJE, NORTH MACEDONIA

I'm Jovan. I'm a product designer based in Skopje.

Before design, I taught languages for six years. Useful preparation, without being the story.

I came to design through Brainster Academy and have spent the five years since across event platforms, casino operations, wallets, and design systems at scale — mostly solo or as lead designer. All of it is the structural layer of products other people use to run their businesses.

Outside work I'm a father, a husband, and a basketball fan.

Capabilities

Design systems
Tokens & theming
Light / dark migration
Admin & operator UIs
Workflow design
Rule engines & configuration UX
Design → eng handoff
Figma libraries
Information architecture
AI-directed development — Claude Code / Claude Design