Available for projectsStockholm · CET

Full-stack developer, frontend-focused

Frontend engineer building React and Next.js apps that hold up in production.

I'm Viktor. 5+ years building for the web, from the database to the render path. Accessibility that passes an audit rather than a plugin check; currently working toward IAAP WAS certification. I use Claude and Copilot daily, and every output is reviewed and tested.

Frontend Development
HTML5 · CSS3 · Sass · Tailwind CSS · JavaScript · TypeScript · React · Redux · Next.js · Vue.js · Astro
Backend, APIs & Data
Node.js · PHP · Laravel · REST APIs · GraphQL · PostgreSQL · Supabase · Redis · Stripe
CMS & Platforms
WordPress (custom themes, ACF, headless) · Shopify · Magento
Testing & Tooling
Playwright · Vitest · React Testing Library · Git · Webpack · Vite · Docker · CI/CD · Figma · Claude · Copilot · Codex

01 - Work

In production.

A deliberately short list. Each entry is something I've designed, built, or actively ship - not a mockup. Employer and client work isn't public, so these are the projects I own end to end.

01Product · Design · Development

DomainLert

A SaaS tool that monitors a portfolio of domains and escalates alerts before any of them expire. Built solo, end to end - data model, RDAP checker, billing, marketing.

  • Next.js
  • Supabase
  • Stripe
  • RDAP

02Architecture · Development

Budkrig

A public pay-to-rank leaderboard for the Swedish market. Anyone can put a product link or an @handle on the board and pay to hold a spot - rank is decided by the amount paid, nothing else. Bids are cumulative, non-refundable, and never expire.

  • Next.js
  • TypeScript
  • PostgreSQL
  • Drizzle

03Design · Development

Skopje

A scroll-driven, surreal three.js journey through nine landmarks of central Skopje. Every monument, texture and sky is generated in code - no models or photographs ship - and the story is pre-rendered in English and Macedonian.

  • three.js
  • TypeScript
  • Vite
  • Lenis

02 - Capabilities

What I actually do

Frontend-focused, and full-stack enough to take a site or a small product from brief to production.

Frontend

Interfaces with real engineering underneath

React, Next.js (App Router) and TypeScript for product UIs and marketing sites, plus an internal Next.js application I co-built that manages 300+ WordPress websites from one place. Components that are typed, accessible and aligned with the design system - so the second and third feature ship as fast as the first.

  • React · Next.js · TypeScript
  • Design-system components
  • WCAG accessibility

WordPress

Custom themes and headless builds

Custom themes with modular, reusable ACF blocks, and headless WordPress with Next.js and React front ends, with WordPress as the content back end. Build processes, asset bundling and code splitting tuned so the front end stays fast as the site grows.

  • Custom themes, ACF blocks & plugins
  • Headless WordPress with Next.js
  • Build & performance optimization

E-commerce

Storefronts tuned for speed and conversion

Shopify and WordPress storefronts, with Magento in the background, built with an eye on the funnel: store functionality and system architecture, faster landing pages, and Core Web Vitals work validated through A/B tests.

  • Shopify & WordPress stores
  • A/B testing & conversion
  • Core Web Vitals

Backend

The practical glue

Node.js, PHP and Laravel, REST and GraphQL APIs, Supabase and Postgres schemas, Stripe billing, queues, transactional email and deployment. Enough backend to ship a product end to end - DomainLert and Budkrig both went from data model to production.

  • Supabase · Postgres · Redis
  • Payments & webhooks
  • Deployments & go-live

Quality

Tested code, shared standards

End-to-end tests in Playwright and unit and component tests in Vitest and React Testing Library. Code reviews and QA before delivery, and guiding junior developers - in distributed and in-house teams alike.

  • Playwright · Vitest · Testing Library
  • Code review & QA
  • Mentoring & delivery workflows

AI-assisted

Faster delivery, same standards

I use Claude and Copilot daily, and Codex too, to move quickly - scaffolding, refactors, boilerplate, test stubs. Every output is reviewed and tested before it ships. The tools speed up the work; they don't get to decide whether it's correct.

  • Claude · Copilot · Codex
  • Reviewed & tested, not pasted
  • Faster iteration, no shortcuts on quality

03 - How I work

A few principles

  1. Ship something usable early, then improve it in the open.
  2. The markup is the product. Semantic, accessible HTML first; enhancement second.
  3. Performance and SEO are decided while you build, not bolted on at the end.
  4. Leave the codebase clearer than you found it - for the next developer and for future me.
  5. Say what's true. No unverifiable claims, no dark patterns, no dependency you can't explain.

04 - About

Background

My route into development ran through ecommerce and content sites - places where a slow page or a broken template has an immediate, measurable cost. That's shaped how I work: I care about the render path, Core Web Vitals and the editor's afternoon as much as the visual design.

Day to day that's React, Next.js and TypeScript frontends, WordPress builds (custom themes, ACF blocks, headless) and Shopify storefronts, with Vue or Astro when the project calls for something lighter, and the backend work to tie it together: Node.js, PHP, Laravel, Supabase and Postgres. At No Sleep AB I co-built an internal Next.js application that manages 300+ WordPress websites, as one of two developers and with a focus on the frontend. I've also built and shipped a full SaaS product solo, DomainLert, from the data model to deployment - the clearest way I know to show I can own a whole thing rather than a slice of it.

I'm based in Stockholm and have worked in both distributed and in-house teams: reviewing code, running QA, guiding junior developers and shaping delivery workflows. The bar I hold every project to: it should look sharp, work for everyone, rank for what it should, and be a pleasure for the next developer to pick up.

05 - Search

SEO, done by the person who builds the site

Most SEO problems are really engineering problems - rendering, speed, structure, markup. I handle both sides, so recommendations don't get lost in a hand-off.

Crawl & index
Clean information architecture, correct canonicals and status codes, XML sitemaps, robots and render-path audits so the pages you care about are the pages that get indexed.
Core Web Vitals
LCP, CLS and INP treated as engineering problems, not a plugin toggle - image strategy, font loading, render-blocking scripts, and layout stability fixed at the source.
Structured data
Schema.org for organisations, products, articles and FAQs - validated, kept in sync with the content, and used to earn richer results.
Answer-engine readiness
Making a site legible and citable to AI answer engines: clear entities, machine-readable facts, evidence close to claims, and content structured the way a model reads it.

06 - Contact

Start a conversation

Tell me what you're building, where it's stuck, and what a good outcome looks like. I'll tell you honestly whether I'm the right fit.