Maximilian Lindig

I build the HMI SDK that Porsche infotainment engineers use to bring in-car experiences to life — in Kotlin and Jetpack Compose. My measure of success: a developer should be able to hover a function and know exactly what to do. No docs tab open, no Slack message needed. Just intuitive, well-documented, modular APIs that get out of the way.

I also sit between the development and design worlds — evaluating feasibility, translating intent, and finding the path from great idea to shippable feature. Having worked as a designer myself, I know what's worth fighting for and what's worth adapting. I'd rather find a way than close the door.

Four years of working across teams, clients, and disciplines — from optimizing landing pages to building full web applications. When AI started generating a lot of noise, I focused on finding the signal: real, practical value for clients, not trend-chasing.

I mentored junior designers, introduced tools like Webflow to move faster without piling on developer dependencies, and spent a lot of time helping design and development teams actually understand each other. The best work happened in those gaps.

A car enthusiast's dream. I designed UI components and animations within BMW's corporate identity and independently built a plant-wide web application in Oracle APEX — from research and planning through to deployment. My first real taste of what it means to own something end to end.

Helped digitalize parts of the university: a web app prototype for always-on access to course materials, and a safety instruction video produced start to finish — research, scripting, filming, editing, voiceover.

Designed a touch-based HMI concept for industrial extrusion machines, built through iterative weekly feedback with employees across departments. Later took on the full digital brand identity and UI system for their MES product NEXXT365 — logo, color system, UI components, and product page — growing it feature by feature as the product evolved.

Where design and code met for me properly for the first time. The curriculum spanned both worlds: software engineering with Java, databases, and RESTful services on one side, and UX design, motion graphics, and interaction design on the other. It's where I stopped choosing and realized I didn't have to.

Foundations that still inform how I think about systems and constraints. Two years of electrical engineering, programming, CAD, and FEM before I switched tracks — but the engineer's mindset of understanding systems end-to-end never left.

STEM specialization. Three months of soldering circuits and working with active and passive components. Three months of sawing, turning, milling, and CNC programming. Got my hands dirty early, and learned that building things with your hands teaches you things a screen never will.