Senior fullstack engineer for web apps that are hard to change.
I've spent eight years building web apps across the stack, with React, Next.js and TypeScript on the front and Node, NestJS and Postgres behind them. A lot of that time went into codebases where shipping had slowed down. At Spotted Zebra I built the component library that made new features about a quarter faster to ship, and before that I spent five years refactoring enterprise systems without rewriting them.
hi@mirza-alispahic.com. A couple of lines is enough, and I reply within a day or two.
Advisory, a fixed-scope build, or the right full-time role.
- faster feature deliverycomponent library built from scratch at Spotted Zebra
- ~25%
- performance won backrefactoring legacy React and Node codebases
- ~30%
- uptime maintainedhigh-availability REST APIs
- 99.9%
- technical interviews runhiring and mentoring across two companies
- 30+
8+ years · Sarajevo · CET · replies within two days
Where I can help
Legacy codebases
Refactoring tired React and Node codebases. Clearing out the tech debt and getting performance back without a full rewrite.
Vibe-coded rescues
Your AI-built MVP works, but nobody can safely change it. I add the structure, tests and security it skipped, without losing the speed that got you here.
Component libraries
UI and design systems that get shared across apps and teams, so the next feature is quicker to ship and everything stays consistent.
APIs & data layers
GraphQL and REST schemas with the Postgres models behind them, built for systems that need to stay up and stay easy to work on.
Data-heavy UIs
Dashboards, complex tables and long lists that stay fast once real data shows up, not just in the demo.
AI features
LLM features built into real products: streaming UIs, the prompt and data plumbing behind them, and the boring parts like cost control and handling failures. Personality Ascend runs on this.
Selected Work
CheckoutGuard
2026Live product · built solo
Checkout monitoring for ecommerce stores. An AI agent learns a store's checkout once, then plain Playwright replays that path on a schedule and alerts when it stops completing. When the store changes and the saved path breaks, it relearns the path on its own. It never places an order.
Atlantbh
2018 — 2023Software Engineer · Fullstack
Five years of fullstack work on enterprise platforms, where I went from junior to senior. I built services, REST APIs and data layers behind systems that held 99.9% uptime, wrote React components that other projects reused, and left a lot of legacy code better than I found it.
Working with me
Advisory
A senior brain on call
- Architecture and code review
- API and schema design sessions
- Performance audits with a written plan
- Async first, a few hours when you need them
Project work
Fixed scope, or embedded with your team
- One engineer takes it from the data model to the UI
- React / Next.js on the front, Node / NestJS / Postgres behind it
- Daily overlap with US / UK / EU hours
Full-time
For the right role
- Long-term ownership of features across the stack
- Front-end architecture, API design and the Postgres models behind them
- Mentoring and hiring, with 30+ technical interviews behind me
No forms and no calendars. Just email me a couple of lines about what you're building and we'll take it from there.
Experience
Spotted Zebra
2023 — nowSenior Frontend Engineer · Remote
I own the front-end architecture of a data-heavy workforce platform, which covers the component library, the Apollo data flows and performance.
- Built the UI component library from scratch. New features ship about a quarter faster and the product looks consistent again.
- Led the technical-debt paydown, refactoring core parts of the codebase for speed and maintainability.
- Mentored junior engineers and ran technical interviews as the team grew.
Atlantbh
2018 — 2023Software Engineer · Fullstack
Five years of fullstack work on enterprise platforms, going from junior to senior.
- Built and maintained REST APIs behind high-availability systems holding 99.9% uptime.
- Modernized legacy codebases and got performance back without full rewrites.
- Created reusable React components shared across projects and teams.
- Mentored engineers, ran knowledge-sharing sessions and 30+ technical interviews.
Stack
The tools I reach for mostFrontend
Backend
Testing & infra
Writing
How to Avoid Big Vercel Bills
How hosting costs creep up on you, and how to catch them early.
Quick Accessibility Wins for Modern Web Apps
Small, practical fixes that make interfaces work for everyone.
Improving Next.js Page Transitions
Moving between pages without the jarring reload.
Next.js — Fetch with Query Parameters
A short reference for something simple that's easy to get wrong.
FAQ
Questions people actually ask- Frontend or backend?
- Both. My work has always split fairly evenly between the two, and I usually own a feature end to end rather than half of it.
- Can I see your work at Spotted Zebra?
- Most of it is under NDA, which is why the screenshots here stop at the public site. I can walk through the architecture and decisions on a call, and references are available on request.
- What timezones do you cover?
- I'm in Sarajevo, on CET, and I work async first. My mornings overlap fully with the UK and EU, and my afternoons with the US East Coast.
- How fast do you reply?
- Within a day or two. Email goes straight to me, not to a form service, and I read all of it.
06 — Contact
Let's talk.
Got a project in mind, a tricky frontend or API problem, or just want to compare notes? Email is the best way to reach me. I read everything myself and usually reply within a day or two.
Sarajevo · CET · working remotely with US / UK / EU teams · references available on request