Full-stack engineer · Bergisch Gladbach

From UI to cloud.

Interface, backend, database, cloud — in one pair of hands. Four systems built show how. Employment or project: write to me.

NEXT.JS REACT TYPESCRIPT TAILWIND POSTGRESQL PYTHON

See the projects Get in touch

Damjan Savić in the hangar, arms folded, laughing into the camera — Damjan Savić4:5

Introduction

Location: Bergisch Gladbach, remote across the DACH region
Terms: Employment directly
Reply: Within one working day, by e-mail

More about me

Reference projects

Four systems, four numbers. The case study says where each one comes from.

SnipeFlip live: deal table with operations arriving by the minute — AI-generated content21:9

01 / 04Sneaker deals · Automation

2,500

operations per day · one VPS

Deal tracking that handles 2,500 operations a day

Watch several marketplaces at once, score every find, push the hits straight to a phone — without anyone keeping tabs open.

Python PostgreSQL Docker Telegram Nginx

AI exposé generator: PDF preview on the left, generation log on the right — AI-generated content21:9

02 / 04Recruiting · AI

3 min

per proposal · was 45

Exposés that write themselves in three minutes

Applications and CVs become a finished candidate profile — Claude writes the copy, the pipeline sets the document.

Claude Python pgvector React

RecRobot: recruiting pipeline from 148 contacted to 9 hires — AI-generated content21:9

03 / 04Recruiting · Automation

3 → 12

developers in three months

The bot that quadrupled a development team

Sourcing, pre-qualification and scheduling automated — nine hires in one quarter, all of them still there.

Node Claude Twilio PostgreSQL

ERP and shop hold the same record: SKU, stock and price in sync — AI-generated content21:9

04 / 04Fashion · ERP ↔ shop

manual imports since go-live

Three systems, one set of data — without handwork

Apparel Magic and the shop keep stock, prices and orders in sync; every discrepancy lands in the log instead of an inbox.

TB.One Apparel Magic MariaDB Node

See all projects

How I work

Projects fail on the handovers, not on the technology.

Between two providers a ticket waits longer than it takes to build.

The same ticket · two line-ups#4812 · inventory

InterfaceAPIDatabaseCloud

Three providershandover · waiting11 days

One person1 day

The same chain. The difference is the handovers.2 seams

Architecture

Four layers, one person answerable.

At the whiteboard in the hangar, the 96 on his back, halfway through drawing the four layers — The diagram is drawn on the whiteboard before it becomes codeArchitecture

01Interface
What reaches the browser. Server Components render on the server; clients only load genuinely interactive parts.
React Next.js Tailwind
Next.js in detail
02API
The layer that enforces rules. One strict typed contract per endpoint; wrong fields break builds, not production.
TypeScript Node Python
TypeScript in detail
03Database
Where the data sits and how fast it comes back. Migrations are versioned, indexes measured rather than assumed.
PostgreSQL pgvector HNSW
PostgreSQL in detail
04Cloud
What happens after you click merge. Build, test, and deploy. No manual steps in between, and rollbacks in one.
AWS S3 Docker CI/CD
Snipeflip case study

The objection

One person is a single point of failure — the objection is fair. So it is built to be handed over:

Handover: Repository, runbook and access — fully documented
Stack: Standard tools, nothing proprietary
Replacement: Any developer can take over immediately

9 articles

Built first, then filmed, then written down.

Every video has its article to read — with the commands, and the places where it got stuck.

0111/08/2026 · 5 min read

Half a minute, and you know more.

Half a minute on what I work on and how. If a question is left, write to me — an answer within one working day.

Get in touch

Or write directly:info@damjan-savic.com