HomeLocationCologne

Full-stack engineer for Cologne

Four reference projects, built from the interface down to the database — remotely, with the meetings on site. How far it is from here to Cologne is right below.

Base
Bergisch Gladbach
Region
NRW
Around
4 places

Bergisch Gladbachconnected toCologne

Who turns up: the same person on all twenty-six location pages
Who turns up — the same everywhere4:5

Relation to Cologne

Built remotely. On site where the trip earned itself.

Cologne is on my doorstep — Bergisch Gladbach is half an hour away. The four projects on this page were built from there: interface, backend, database and cloud, handed over by one person.

Under way: regional train, laptop open, editor darkAI-generated
The stretch itself — the part no location page shows21:9
The hour in between: work on the train, coffee beside itAI-generated
The hour in between is working time16:9

Reference projects

Four systems that were built, one from each of the four areas I work in. Behind every title is the case study: the situation, the build, and the numbers afterwards.

The pipeline, triggered from inside the client team: build, test, migrate, deploy — all greenAI-generated

01Cloud & Deployment

SnipeFlip

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

The repository after the handover: transferred to the client, history intactAI-generated

02Full-stack development

AI profile generator

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

Claude Python pgvector React

The acceptance run, started from the client account: 24 of 24 passedAI-generated

03AI integration

RecroBot

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

Node Claude Twilio PostgreSQL

The sync overview in production: 2,500 records, 0 errorsAI-generated

04System integration

ERP integration

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 work

Three proof points

The same three numbers as everywhere else on this site — checkable, with the material they come from beside them. Being in Cologne changes none of it.

On site and remote

This is how these projects ran: on site for workshops and acceptance sessions, built remotely, with weekly demos on real code — the distance to Cologne changes none of it.

On site: a workshop at the client’s own tableAI-generated
On site: the thing that supposedly never happens16:10
Remote: a call and a shared editor — one working mode, not a wordAI-generated
Remote: a working session, not a buzzword16:10

Common questions

6 questions that actually come up about a project in Cologne — answered the way they would be answered in conversation.

Is there on-site work in Cologne too?
Yes. Bergisch Gladbach is half an hour from the centre of Cologne, and that is how the projects ran: on site for workshops, acceptance sessions and handovers, built remotely, with weekly demos on real code.
What are the projects here built with?
Next.js, React and TypeScript on the front end, Node and Python on the back end, PostgreSQL with pgvector as the database, Docker and AWS in operation. The complete list is in each case study, line by line.
Can any of the projects be seen live?
SnipeFlip runs publicly at snipeflip.com. The other three ran inside client systems — what may be shown from them is in the respective case study, together with the number the project was measured by.
Do you work alone or with a team?
Alone, and that is the point: in all four projects interface, backend, database and cloud came from the same person, so there was no handover between trades for knowledge to fall through. On the AI profile generator, team leadership came with it — from three developers to twelve in three months.
Where does the data sit when AI is involved?
Hosting in the EU is the default, usually AWS Frankfurt or Hetzner. Where a language model is wired in, the handover document states which model sees which data, what is logged, and what never leaves the building.
Where do the numbers on this page come from?
Each comes out of the project it was measured in: 2,500 operations a day at SnipeFlip, three minutes per profile instead of forty-five, a team from three to twelve, zero errors after the ERP switch. How it was measured is in the case study each time.

Nearby

These places are within reach of Cologne. Where one of them has a page of its own, the name leads there.

A steel truss bridge over the Rhine in haze, the towers of the city as shadows behind itAI-generated
The place itself, and the area around it. For the work, the journey is the only difference.21:9
What the distance actually is: the regional train pulling inAI-generated
What the distance is16:9
How the radius was decided: a pencil circle on a paper mapAI-generated
How the radius was decided16:9

Other locations

Twenty-five more pages, none of them from a template.

25 cities in 6 countries. Each page names the distance, the way the work runs and the questions actually asked there — and none of them is here because a search engine expects it.

The same page three times: English, German, SerbianAI-generated
Three languages, one source21:9
Three clocks, three time zones, one calendarAI-generated
Three time zones in one day’s plan16:9
The border as a document: an invoice across it, reverse chargeAI-generated
A border, actually crossed16:9
Twenty-six printed pages on the steel table — no two the sameAI-generated
All twenty-six, printed out — the proof that none exists twice21:9

Contact

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.