Most CVs are boring.
This one didn't have to be.

I'm Lorenz.

I'm a Full Stack Software Engineer.

Instead of bullet points and buzzwords, this is a short, commented walk-through of how I build software and solve problems.

AI-infused content ahead!

Prefer a classic CV? Download the PDF.

Choose your guide

Sound on recommended

Scientist

Italian Chef

Robot

Your browser can't play the audio. Switch to Firefox or Chrome for the full experience.

How I Got Here

I didn't choose Computer Science as a career move. I picked it out of curiosity. I liked taking systems apart and understanding how they worked.

So after my Abitur, the decision felt natural.

University added depth, but also contrast. I built a strong theoretical foundation, yet much of the teaching lagged behind how software is actually built and used today. My energy went up when I was creating, experimenting, and testing ideas against reality, and dropped whenever learning lost its connection to the real world.

- more details -

University taught me that I don't do my best work in purely academic setups. Too often, memorization mattered more than understanding. My motivation didn't fade because it was hard; it faded because it felt disconnected from why I chose this field.

During my Master's, that tension became impossible to ignore. My first thesis topic, polyp recognition and report generation in gastrointestinal images, had to be abandoned due to insufficient dataset consistency from the University Hospital Würzburg. Frustrating, but a real lesson in how research can fail for reasons entirely unrelated to skill or effort.

For my second topic, I worked on interactive segmentation of 3D medical data, breaking down complex images (CT, MRI, ultrasound, PET, microscopy) into meaningful, usable structures, and placed first in an international challenge. We published our work on the iMedSTAM model.

In the end, the delays and long writing cycles took their toll. I realized my strengths lie in building and iterating on concrete problems, not in academic writing phases.

I decided not to finish the thesis — not as a failure, but as a form of clarity.

Things I've Built, Broken, and Fixed

Most of my projects started with the same frustration: this shouldn't be this hard. I kept running into powerful systems that got in their own way, so I built alternatives that let people focus on the actual problem.

VPNBOX: Secure Networking Without the Headaches (Jan 2018 - Dec 2022)

VPNBOX set out to make VPN routers usable by anyone. Set up in minutes, no ongoing maintenance, and support every device: from laptops to TVs, consoles, and smart hardware that never heard of VPNs.

We replaced fragile setups with a plug-and-play system built on Ubuntu Core that updates itself without breaking. We shipped native WireGuard support early, long before it became mainstream.

The result was a system that stayed out of the way. Advanced networking stopped feeling intimidating, even for users who had never touched a VPN before.

Screenshots

Snapolly: Frictionless User Feedback (2023)

Most feedback tools try to shout — pop-ups, annoying overlays, interruptions. Snapolly went the opposite way.

A quiet, on-page questionnaire builder that only engages when users choose to interact. No pressure. No disruption.

Collecting feedback stopped feeling like a chore and started feeling natural.

Search Analytics Node: SEO Data Where It Belongs (Aug 2024 - Present)

Working with Google Search Console data usually meant CSV exports, row limits, and manual stitching. The Search Analytics Node removes that friction.

As an open-source KNIME extension, it pulls Search Console data directly into analytics workflows. Users can fetch an unlimited number of rows per query and break down the data by page, query, country, or device.

The result: faster analysis, fewer errors, and less time fighting files than insights.

Website Article in Website Boosting magazine

University of Würzburg: Modeling an Alveolus (Aug 2022 - May 2023)

My first paid role at the university focused on modeling an alveolus, the tiny air sacs in our lungs. Translating biological assumptions from different papers into 3D simulations quickly taught me how fragile models become when their assumptions go unchallenged.

University of Würzburg: Interactive Research Tools (Feb 2023 - Aug 2024)

In my second role, I built interactive web applications that made research data explorable instead of static. Rather than dumping results into chats or PDFs, the goal was to let people play with the data.

Letter of Recommendation by Prof. Dr. Goran Glavaš

My ToolBox

I don't collect tools like trophies. I use them as instruments: pick the right one, learn it, move on.

I focus on understanding systems, knowing where to look, and adapting quickly to new situations.

JavaScript is my home base. I'm most comfortable building full-stack systems where frontend, backend, and infrastructure fit together cleanly.

- more details -

You'll often find me jumping between documentation, source code, and small experiments until things click. That's how I stay flexible. I don't try to remember everything. I focus on knowing where to look and how to think once I'm there.

AI tools are part of that workflow as well. I use them as thinking partners: code reviews, exploring alternatives, or stress-testing ideas. Not as a replacement for understanding.

JavaScript remains my home base. Runtime-wise, I gravitated toward Deno early and never really looked back. The ecosystem feels cleaner, more opinionated, and closer to how I like it.

Earlier, during my VPNBOX days, I wrote more Bash than I care to admit and spent a lot of time configuring GNU/Linux systems and networking. That hands-on work taught me how systems actually behave under real conditions.

Most of my experience so far has been in full-stack web development — building APIs, designing UIs, and making sure the whole system feels solid. What matters to me isn't how many tools I've touched, but knowing when and why to use them, and staying curious.

What I care about (more than grades)

I care about usefulness, freedom, and whether something works in the real world.

I'm drawn to thoughtful systems and teams with good energy. I value learning over buzzwords and curiosity over credentials.

- more details -

I do my best work in teams with trust, clarity, and low politics.

Away from the desk, I move — a lot: cycling, rowing, running. Physical activity helps me think and reset.

I value flexibility and early clarity, including room for open-source work or side projects. Clarity beats awkward conversations later.

Let's talk.

I enjoy building things that actually get used and improving what's already there. If this resonates, I'd love to talk and see where it could lead, ideally in person.