Skip to content

Senior QA Engineer

Engineering software quality through code, automation and architecture.

I build automated testing systems and software with a focus on reliability, maintainability and fast feedback.

  • Playwright
  • TypeScript
  • API Testing
  • E2E
  • CI/CD
  • Test Architecture
quality.flowillustrative

The product under test —
web app and its APIs.

Selected Work

Selected Engineering Work

Real repositories spanning quality automation, product engineering and frontend architecture.

pipeline.runpassing
  1. 1API✓
  2. 2Test Architecture✓
  3. 3Playwright✓
  4. 4CI/CD✓
FEATURED

01QA Engineering / Test Automation

QA Automation Framework

A Playwright + TypeScript framework for API and Web testing on shared infrastructure, configuration-driven and extensible across regions.

PlaywrightTypeScriptNode.jsZodFakerdotenvGitHub Actions
Mon
Checkup
Tue
Consult
Follow-up
Wed
Lab
Thu
Surgery prep
Fri
Checkup
Review

02Full-Stack Application / Product Engineering

Medical Appointment Management System

A medical practice management app with a weekly scheduler, conflict detection, Google Calendar integration and offline fallback.

ReactTypeScriptViteTailwind CSSshadcn/ui+5
41.6086° N, 21.7453° E

03Frontend Engineering / Interactive Experience

Interactive Map of Macedonia

Macedonia Explorer — a geospatial app for discovering monuments, cities, nature, camping and recreation across Macedonia.

ReactTypeScriptViteTailwind CSSshadcn/ui+5

Philosophy

How I think about quality

Read more
  1. 01

    Quality is engineered

    Quality isn't added at the end of development. It is designed in — through requirements, architecture and the feedback loops a team builds around its code.

  2. 02

    Automate the right layer

    Not every scenario belongs in E2E. Validate logic and contracts at the API, and reserve the browser for the journeys real users take.

  3. 03

    Tests are software

    A test suite needs architecture, maintainability and sensible abstractions — page objects, fixtures, factories and clear responsibilities.

  4. 04

    Fast feedback matters

    Automation is only valuable if developers trust it. Quick runs, readable failures and a place in the CI pipeline make tests worth having.

Currently focused on

Automated testing systems that give teams fast and reliable feedback.

My background in frontend engineering shapes how I approach QA: I care about architecture, maintainability and the developer experience of the test suite itself.

  • →Playwright
  • →TypeScript
  • →API automation
  • →E2E testing
  • →CI/CD
  • →Scalable test architecture

Engineering Journey

Understanding how software is built makes it easier to understand how it should be tested.

  1. 01

    Frontend Engineering

    Building interfaces and learning how users actually break them.

  2. 02

    UI / Product Development

    Shipping product features end to end, from component to API.

  3. 03

    QA Leadership

    Owning quality across teams, processes and releases.

  4. 04

    Automation Engineering

    Turning test knowledge into code, frameworks and pipelines.

  5. 05

    Senior QA Engineering

    Designing test architecture that helps teams ship with confidence.

Values

Things I care about

  • →Readable tests that explain intent
  • →Clear boundaries between test intent and mechanics
  • →Validating data at the edges
  • →Test data that is isolated and generated
  • →Failures that are easy to debug
  • →Interfaces that keep working when the network doesn't

Technology

Tools I work with

QA & Automation

PlaywrightTypeScriptAPI TestingPostmanNewmanCucumber / Gherkin

Frontend

ReactNext.jsTypeScriptJavaScriptHTMLCSS / Sass

Engineering

GitCI/CDAzure DevOpsGitHub ActionsDocker

Testing Concepts

E2EAPI TestingIntegration TestingRegression TestingTest ArchitecturePage ObjectsFixturesTest Data Management

Let's build better software.

Open to conversations about QA automation, test architecture and engineering roles.

Get in touch