Skip to content
EK
About

Engineer and designer, drawn to the craft of calm, precise software.

I build products end-to-end — from data models to design systems to the last two pixels of a button. I care about performance, accessibility, and the feeling of a product that respects the person using it.

Story

A quick tour of how I got here.

I started out curious about how things work on the web — view-source, dev tools, a text editor, and too many side projects. Over time, curiosity turned into craft: I learned how to ship, how to maintain, and how to think about software as a system rather than a pile of files.

These days I spend most of my time on product engineering — the slice of work where design and implementation are the same activity. I'm happiest when I can move between a Figma frame, a database schema, and a production rollout without losing the plot.

Outside of work, I write on my blog, tinker with design systems, and quietly obsess over typography.

Experience

Where I've worked.

  1. Current
    2024 — Present
    Prishtina, Kosovo

    Fullstack Engineer

    Building scalable web applications and shaping frontend architecture for a digital health platform. Contribute to core product surfaces, establish engineering conventions, and invest in accessibility and performance.

    ReactTypeScriptNext.jsNode.jsPostgreSQL
  2. 2022 — 2024
    Remote

    Freelance Developer

    Upwork & independent clients

    Delivered custom web products for clients worldwide — e-commerce, dashboards, SaaS tools. Owned projects end-to-end from discovery to deployment.

    ReactVue.jsNode.jsMongoDBAWS
Toolbox

What I work with.

Languages
  • TypeScript
  • JavaScript
  • Python
  • Go
  • SQL
Frameworks
  • Next.js
  • React
  • Node.js
  • NestJS
  • Tailwind CSS
Tools
  • PostgreSQL
  • Redis
  • Docker
  • AWS
  • Vercel
  • Figma
Interests
  • Design systems
  • Developer experience
  • AI tooling
  • Performance
Beliefs

How I think about product.

  • Taste is a force multiplier.

    Details are not decoration. They are how a product signals that someone cared.

  • Speed is a feature.

    Latency is UX. Keep the thinking in the product, not the spinner.

  • Accessibility is the baseline.

    If it isn't usable with a keyboard, a screen reader, and a slow connection, it isn't done.

  • Systems beat heroics.

    Components, tokens, and conventions compound. Write software that still makes sense in a year.