Full Stack Developer

Helge Drews Portfolio

Freelance Software Developer & AI Consultant, Helge Drews — AI Voice & Web Engineering

A freelance consultant site that replaces the usual portfolio project grid with a dated, quantified work-history timeline — 30+ REST endpoints on a wealth-manager backend, a 10-person team leading an international medical-device site relaunch across 5 markets — and is honest ("reference in preparation") wherever a proof point isn't ready yet instead of filling the gap with vague copy.

Next.jsTypeScriptNest.jsReactAWS

Location

Lübeck, Germany

Companies

Helge Drews — AI Voice & Web EngineeringPHAT Consulting GmbHSerafin Asset Management GmbHBergwerk.io GmbH53NorthDigital GmbHPlato AGoncampus GmbH / ILD

Credentials

  • B.Sc. Informatik, Universität zu Lübeck (2008–2017)

Skills

Next.jsTypeScriptNest.jsReactAWS

Notable

  • Technical lead of a 10-person team on an international medical-device website relaunch across 5 markets (Bergwerk.io)
  • Built a 30+ endpoint NestJS REST backend with 2FA for a wealth manager, serving 50+ users managing over €2M in assets (Serafin Asset Management)
  • 53 public repositories on GitHub (github.com/dahelg), independently confirming identity, location, and stated focus areas

What makes it work

A breakdown of the choices that make this portfolio stand out.

1

Career history as a dated timeline with one quantified line per role

The "Werdegang" section on the about page lists each job with exact start/end months, employer name, a one-sentence project description, and the tech-stack chips used there — e.g. "Senior Backend Developer, 01/2024–01/2025, Serafin Asset Management GmbH: 30+ REST endpoints, migration to a scalable Nest.js microservice architecture, two-factor authentication." Reads more like an audited changelog than a resume paragraph.

2

Anonymized but specific proof points instead of named-client name-dropping or vague praise

A dedicated "Referenzen & Beweise" section states plainly that the case studies are anonymized (client NDA), then still gives real numbers: 30+ endpoints / 2FA / 50+ users / over €2M in managed portfolio for the wealth-management backend, and a 10-person team leading an international medtech site relaunch across 5 markets with Lighthouse consistently above 92. Confidentiality doesn't become an excuse to go generic.

3

A live, checkable claim sitting right on the homepage

A three-tile stat strip reads "15+ / Jahre Softwareentwicklung", "<1s / Ladezeit dieser Seite", "0 / Cookie-Banner nötig" — the middle claim (page load time) is something the visitor is, at that exact moment, in a position to verify just by having gotten the page to render.

4

Says "not ready yet" instead of inventing a number

On the AI-consulting page, two metric tiles that would normally hold a client testimonial stat are explicitly labeled "REFERENZ IN VORBEREITUNG" (reference in preparation) rather than a placeholder figure or omitted silently. Consistent with the site's own stated positioning ("Klartext statt Fachchinesisch," "anbieterneutral") — under-claim rather than dress up an empty slot.

What Full Stack Developers can take from this

Specific, actionable tips to apply to your own portfolio — no generic advice.

  • Turn your work history into a timeline with one quantified line per role (endpoint counts, team size, user counts) instead of a paragraph of job-description prose — it reads in seconds and hits harder.

  • If NDA or confidentiality stops you from naming a client, don't drop the case study — anonymize the client and keep the real numbers (team size, scope, metrics). "Anonymized, but specific" beats both "named but vague" and "omitted entirely."

  • When a proof point genuinely isn't ready, label it as such ("case study in progress") rather than leaving a blank tile or padding it with filler copy — it reads as more credible than either.

  • If you can put a live, checkable claim on your own homepage (page load time, uptime, a real counter), do it — it's a claim your visitor can verify without leaving the page.

  • Put your GitHub and LinkedIn behind one dedicated, shareable "digital business card" page with a QR code — useful for handing off contact info in person, not just embedding icons in a footer.

Ready to build your portfolio?

Follow the Full Stack Developer roadmap — skills, projects, and timeline to get hired.

Full Stack Developer Roadmap