<style> .film__track { height: auto !important; } .film__stage { position: static !important; height: auto !important; /* Ohne diese Zeile ist der Rückfall LEER: container-type: size bemisst die Bühne nicht mehr nach ihrem Inhalt, und overflow: hidden schneidet alles weg. */ container-type: normal !important; } .film__poster { position: absolute !important; } .film__content [data-film-anchor] { position: static !important; transform: none !important; opacity: 1 !important; margin: 2.5rem clamp(1rem, 5vw, 4rem) !important; max-width: 34rem; } </style>
← Back to About

Verified Qualification

Software Developer · Backend Development

The half of a website nobody ever sees: what happens after someone clicks "send". That is exactly where it is decided whether an enquiry arrives or quietly disappears.

Issued by Developer Akademie GmbH AZAV-accredited training providerFebruary 2025

View certificate (PDF) (Software Developer · Backend Development, opens in a new tab)

The record

Issuer
Developer Akademie GmbH
Issued
Focus
Web applications focus · Backend Development

Competencies

  • Backend Development
  • REST APIs
  • Database Design
  • Deployment

Technologies

  • Python
  • Django
  • PostgreSQL
  • SQL
  • Redis
  • Linux
  • Docker
  • Cloud

What the certificate states

It was issued by Developer Akademie GmbH, an AZAV-accredited training provider, in February 2025, with a web applications focus. The document lists backend development, REST APIs, database design and deployment as competencies, and Python, Django, PostgreSQL, SQL, Redis, Linux, Docker and cloud as technologies. It exists as a PDF and can be viewed on this page.

When a website needs a backend

Many do not. A site that explains your offer and leads to a phone call works without one — and is faster and cheaper to run that way. A backend is needed as soon as your website has to remember something: appointments that are taken. Enquiries that have a status. Customer data that should still be correct tomorrow. Drawing that line honestly is the first backend decision, and it usually saves you the most money.

What it changes during the build

A data model that reflects how your business actually works, rather than a form someone bends into shape later. Interfaces that let your website talk to your point of sale, your calendar or your accounting without anyone retyping numbers. And storage locations chosen on purpose: enquiry data does not sit in the public web directory, it sits where a visitor cannot reach it.

How you can check it on this site

The appointment system on this site is not a bought-in calendar service, it is built in-house: free slots, request, confirmation email with a calendar entry and a cancellation link — on our own servers, without your data passing through someone else's booking portal.

What this means for your project

  • Your data lives in a structure that fits your business — not one that happened to fall out of a form.
  • Existing systems are connected instead of maintained twice.
  • Enquiries and bookings are validated on the server, not only in the sender's browser.
  • Whatever is stored sits outside the publicly reachable directory.

Other certificates

Should your website do more than explain?

Describe the routine that costs you time today. I will tell you whether it needs a backend — and if it does not, I will say that too.

Project inquiry