Skip to content
Marco Middeldorff — Software Developer Cologne, Germany · Remote or hybrid Path /en/about

About

I build backend systems that run quietly in production.

01

Person

I am a software developer in Cologne and work mostly on the server side: data models, APIs, background processes and the infrastructure all of it runs on. For about two years I have been the lead developer of an ERP system that a client uses to run its day-to-day business.

I taught myself to program, without a degree and without formal training. That is why I care about my work being verifiable: through readable code, documented decisions and systems that run quietly in production.

Outside of work I build my own projects: a platform for virtual airlines, an air traffic control simulation in German airspace, a personal voice assistant and an iOS app for shopping lists.

02

Career

2 positions
  1. 2024 – present

    Software developer, permanent position

    at HAL Media GmbH · Home office

    Lead developer of an ERP system built on Laravel, Vue and MySQL: integration with a workflow system, billing, routes, frontend and deployment with Docker and GitLab CI.

  2. 2022 – 2024

    Software developer, permanent position

    at Cyrano Kommunikation GmbH · Home office

    Development of web applications for clients in the pharmacy sector, with Laravel, PHP and MySQL. New features and bug fixes across several client projects, setting up deployment processes with GitHub Actions and Docker. Worked in Scrum in a cross-functional team, in close coordination with project management and internal stakeholders.

Résumé

On request

Full résumé with employers and references by email.

Request →
03

Stack

In daily use

3.1 Backend

  • —PHP, Laravel
  • —MySQL, PostgreSQL
  • —Redis, Queues, Horizon
  • —REST-APIs, Webhooks

3.2 Infrastructure

  • —Docker
  • —GitLab CI/CD
  • —GitHub Actions
  • —Coolify

3.3 Frontend

  • —Vue, TypeScript
  • —React
  • —Inertia
  • —Tailwind CSS

Also in personal projects: C# / Unity · WPF · Swift / SwiftUI

04

Working style

I start with the data model, not the framework. I record decisions in writing so they are still traceable a year from now. I prefer small changes that can be rolled out and rolled back without downtime. And when something goes wrong in production, I want to understand why — not just that it works again.