About

05
About

Based in Eindhoven. Who I am, where I've worked, and what I bring to your project.

Who I am

I'm Stanimir Nikolov. Full-Stag Digital is my studio in Eindhoven, Netherlands: web apps, online stores, and booking sites, built end to end.

The longer story

I started Full-Stag Digital to work the other way round: understand a business before writing a line of code, and say so plainly when a project isn't worth building.

That is why every engagement begins with investigation, not implementation, and why I would rather talk you out of the wrong build than deliver it well.

My background spans custom software, SaaS platforms, legacy systems, e-commerce, and frontend architecture. It taught me that technologies change far faster than good engineering principles: clear ownership, understandable systems, careful planning, and honest communication.

Today I build web applications, internal tools, booking systems, online stores, and business websites, modernise existing software, and help businesses work out what they actually need before investing in it.

I deliberately keep the studio small, so every project stays with the person who discussed it with you: fewer misunderstandings, and direct accountability from first conversation to finished result.

At a glance

Based in
Eindhoven, Netherlands
Studying
Software engineering, Fontys ICT, Eindhoven.
Availability
Open for enquiries.
Languages
Bulgarian (native), English (fluent, Cambridge C1 Advanced), and Dutch (elementary).See the C1 Advanced certificate

Education

  1. 2017 –

    Software engineering, Fontys ICT, Eindhoven

    Since September 2017.

  2. 2024

    Digital Experience Design minor certificate, Fontys ICT

    Minor certificate, completed 2024.

  3. 2016

    Certificate in Advanced English, University of Cambridge

    Cambridge CAE, 2016.

  4. 2012–2017

    E-commerce, High School of Commerce "Knyaz Simeon Tarnovski", Bulgaria

    Secondary education, 2012 to 2017.

Software experience

  1. 2023–2024

    Appsemble

    Software Engineer Intern, then part-time Junior Software Engineer (September 2023 to July 2024). SaaS platform features; GUI and code editor rework for responsiveness across devices; usability improvements; systematic bug elimination.

  2. 2024–2025

    ART-IE, Interreg Vlaanderen-Nederland

    EU-funded federated learning platform (September 2024 to June 2025). Refactoring a complex legacy codebase: Go, Cassandra, microservices, with a data-privacy focus.

Range

  1. 2021–2022

    Prodrive Technologies, Son en Breugel

    Cleanroom technician and circuit-assembly technician: building printed circuit boards under contamination-controlled conditions. Precision hardware work that shows the range I bring to a problem.

Technologies & Tools

  • Frontend

    Vue / Nuxt (SSR)

    Building fast, accessible interfaces and server-rendered applications for business software and public sites.

    Primary

  • Backend

    Hono (TypeScript monolith)

    APIs, business logic, integrations, authentication, and the architecture that holds an application together.

    Primary

  • Language

    TypeScript, typed end-to-end

    One typed language across the front end and the back end, so the pieces of a system can't quietly disagree.

    Primary

  • Data

    Prisma

    Database modelling, migrations, and type-safe access to your data.

    Advanced

  • Infra

    Cloudflare

    Hosting, DNS, security, caching, and edge delivery.

    Working proficiency

  • Security & QA

    OWASP ZAP, Burp Suite, SonarQube, Snyk

    Catching common security issues early, automating quality checks, and keeping a codebase maintainable as it grows.

    Working proficiency

I work in React as well; Vue and Nuxt are my default.

How I work with you

  • A paid feasibility report, a fraction of the build, before you commit to it. source: How I work · step 03
  • A fixed quote after it. source: How I work · step 04
  • New ideas mid-build don't quietly inflate the bill: they're planned into the next version, as your decision. source: stated commitment, no ledger exists yet

What I hold to

Good software is decided long before anyone writes code: in whether the problem is understood, the expectations are clear, someone owns the difficult decisions, and honest advice outranks commercial pressure.

My job is to reduce uncertainty before reducing complexity: understand the problem first, explain trade-offs plainly, document decisions, and recommend against unnecessary work when that is the better answer.

Every commitment I make should be observable. If I can't explain why I recommend something, or show how it benefits your business, I reconsider it.

I build software another developer should be able to understand after me. Documentation, standard technologies, and client ownership aren't extras; they're part of the product.

Tell me what you want to build. I'll find the way that fits your business.

The first conversation is free and in plain words. Then a paid feasibility report gives you the direction, the honest cost, and the right way forward, so you commit with confidence. source: How I work · step 03