Johannes Neutze

Scope: greenfield internal workflow platform built with Strategy & Operations | 150k+ merchants across 25+ countries | shipped to 100% of merchant-facing account managers in Finland and Denmark, with a phased plan behind it for the remaining markets Bootstrapped the greenfield engineering function in close partnership with Strategy & Operations, resolving an initial four-month hiring stall by redesigning the talent profile. • Hold the architecture boundary at workshop level against a vendor-first ownership

Scope: newly integrated team of 5 engineers following acquisition, scaling into a new product domain | held as concurrent scope alongside Merchant CRM Stepped in at the VP of Engineering's request to drive post-merger integration, establish engineering cadences, and unblock execution. • Moved the team from onboarding into delivery by breaking an oversized product vision into milestone-based scope it could execute — handed over with the following milestone defined and scoped, and stand-ups, weekly planning,

Scope: assigned as DRI for the merchant and venue migration workstream, plus the merchant-app device stream | matrix team of 4 senior and staff engineers reporting into other organizations | thirteen-workstream integration of Tazz, a newly acquired Romanian delivery company • Rejected a faster bulk migration in favor of routing 5k+ merchants and 12k+ venues through the existing onboarding flow — slower, but it preserved every legal, regulatory, and data-quality check rather than rebuilding them under time

Scope: 6 engineers across Flutter and backend (Kotlin, Scala) | the merchant order and grocery-picking workflows 150k+ merchants across 25+ countries and 1k+ cities depend on to trade | run from inside real restaurants on regular on-site visits with product, design and operations Hired 10+ engineers across the tenure, and coached a senior engineer to Staff after a promotion-cycle miss. • Recovered crash-free sessions within roughly four months after a mid-2024 regression, by rebuilding crash triage. Introd

Scope: 5-engineer platform team across DevOps, iOS and Android, inside Client Engineering | the CI/CD, release tooling and developer productivity systems all 10+ mobile teams depended on, for apps serving 20M+ monthly active users | team rebuilt after its Android and iOS core members left Built and carried the promotion case for a mid-level DevOps engineer into senior, in a job family too new to have a leveling rubric. • Acted as Incident Commander for mobile through Cyber Week, shipping via a two-stream b

Scope: mobile team built from zero to 3 engineers | a next-generation Digital Health Application | engineering process governed under MDR class I medical device regulation, architecture and engineering process defined from scratch across successive product leaders • Set product direction the team could build against by running structured goal- and impact-mapping workshops that brought psychologists, product, and engineering to a shared plan — recognized by the CEO. • Turned DiGA and Medical Device Regulati

Scope: sole Android engineer | Looping, a family and group calendar with hundreds of thousands of users | legacy Java codebase modernized toward Kotlin without a rewrite or a delivery freeze • Chose incremental sidecar migration over a full rewrite, keeping product delivery running throughout. Introduced Kotlin, Jetpack, MVVM, CI/CD, and observability to the legacy stack, plus backend-driven UI foundations and adapter-based calendar integration — so legacy logic no longer forced client-side rewrites. • Ran

Scope: Rider Transmission — mobile, backend and QA engineers owning the rider operational experience through the foodora/foodpanda brand merger | architecture owned for both the software and the data model | from November 2017 also the Mobile Logistics chapter, two applications across two product teams, grown from 2 to 4 engineers as an externally built rider-shift application came in-house • Introduced a backend-for-frontend layer to decouple the mobile app from backend complexity, letting the team build

Scope: first mobile engineer in courier logistics at foodora | the courier app, rebuilt for production scale | workflow patterns later used in 20+ countries • Rebuilt the app natively with abstraction layers and current libraries rather than carrying on the inherited Appcelerator Titanium stack from an acquired company — the cross-platform shortcut had already produced a maintainability trap, so not repeating it was the explicit design constraint. • Treated couriers as customers rather than internal users:

Scope: founding team of 4, pre-acquisition | first Android courier app and the operations tooling around it volo was acquired by Rocket Internet and rebranded foodora in April 2015, then acquired by Delivery Hero that September — one continuous employment through both. • Shipped the first Android courier app, and invented a Raspberry Pi and thermal-printer order-intake box for restaurants — chosen over the more obvious tablet interface because restaurants pass paper tickets straight into kitchen workflows.

Owned the data-extraction pipelines that turned partner requirements into working queries against Experteer's job database, keeping partner-facing exports current. • Partners paid for access to job data matching their own criteria, so pipeline reliability carried commercial stakes rather than only internal ones — my first exposure to owning something a customer was actually paying for.

Built reporting and campaign tracking for PAYBACK's main affiliate websites in the Adobe Omniture Suite, for marketing managers and external partners assessing subpage and campaign performance. • Worked as an analyst rather than a report generator — surfacing the numbers and trends that let a marketing manager decide something, and later onboarding external partners onto the tool directly.

Bartender and waiter in a busy premium spa, with direct customer responsibility where service consistency was visible to customers and colleagues alike. • Trained and onboarded new interns at the Champagne pool bar — the earliest version of the thing I now do full-time.

Master's thesis: Analysis of Android Cracking Tools and Investigations in Countermeasures for Developers Analyse von Android Crackingtools und Untersuchung geeigneter Gegenmaßnahmen für Entwickler (Chair of Operating Systems) Modules: - Software Engineering - Distributed Systems - Formal Methods a

Bachelor's Thesis: Implementation of a HomeMatic simulator using Android Implementierung eines HomeMatic Simulators unter Android (Chair of Operating Systems) Minor in business studies