# Oliver Pietsch — full site content Source: https://oliver-pietsch.de Frontend Engineer, Potsdam, Germany. Vue.js, Nuxt.js, TypeScript. --- ## Frontend Engineer (Vue/Nuxt/TypeScript) URL: https://oliver-pietsch.de/ Last updated: 2026-09-18 Hello, I am Oliver. I am a Frontend Engineer with eight years of experience building scalable, high-performance web applications. I work at myposter on Nuxt and Vue server-side-rendered e-commerce used by millions of customers, and I live in Potsdam, Germany, working remotely with product and engineering teams. ## What I work on My day-to-day is server-side-rendered frontend work at production scale: Nuxt 3 and Vue 3 applications with TypeScript end to end. That means caching strategies that hold up under real traffic, render paths that stay fast on a mid-range phone, and component architecture that a team can still extend two years later. I also build the backend-for-frontend layer that sits directly behind it — NestJS services with Redis caching, shaping and caching data for the frontend rather than exposing raw domain APIs. Owning a feature from that layer through to the rendered pixel is usually faster than negotiating it across two teams. ## How I work I care about the parts of engineering that are invisible when they go right: - Performance as a requirement, not a cleanup task. Measuring before optimising, and knowing which numbers actually correlate with what users feel. - Accessibility built in from the first component. Semantic markup and keyboard paths are far cheaper to get right at the start than to retrofit after launch. - Pragmatic testing. Unit tests for logic, integration tests for the parts that break, end-to-end tests for the flows that cost money if they fail — not a coverage number for its own sake. - Migrations that actually finish. Large codebase-wide changes — an ESLint 9 migration across a monorepo, a full Cypress-to-Playwright move — are mostly a sequencing and communication problem, not a technical one. ## AI-supported development AI-assisted development is part of my regular workflow, including at myposter. I keep the same review and testing standard for generated code as for handwritten code, and the architectural decisions stay on my side of the line. ## Get in touch I am open to conversations about frontend engineering work, particularly Vue and Nuxt at scale. You can reach me via email, connect on LinkedIn, or browse my code on GitHub. --- ## Experience Highlights URL: https://oliver-pietsch.de/references Last updated: 2026-09-18 Eight years of frontend engineering, most of it in Vue — from enterprise agency work through automotive e-commerce and B2B SaaS to high-traffic consumer retail. The through-line is server-side-rendered applications that stay fast and maintainable as teams and codebases grow. ## Frontend Engineer — myposter GmbH October 2024 to present · Remote Frontend engineering for myposter, a high-traffic e-commerce platform serving millions of customers. - Building server-side-rendered frontends with Nuxt 3, Vue 3 and TypeScript, where render performance directly affects conversion. - Developing NestJS backend-for-frontend services with Redis caching, shaping and caching data for the frontend rather than exposing raw domain APIs. - Full-stack feature delivery, including an order status system built end to end — backend API through to the customer-facing components. - Leading an ESLint 9 flat-config migration across the entire monorepo. - Migrating the end-to-end suite from Cypress to Playwright. - Integrating Storyblok as a headless CMS so non-engineers can ship content changes without a deploy. - Ongoing performance, SEO and accessibility work across the storefront. - Unit and end-to-end testing with Vitest and Playwright. - AI-supported development as part of the regular workflow. ## Senior Frontend Developer — CYCLE (formerly GetHenry) April 2022 to September 2024 · Berlin Led frontend development for a fleet-management SaaS platform, building Vue applications against a Laravel-backed API. - Architected new features from scratch while keeping a substantial legacy codebase running — the usual real-world constraint of building the new thing without a rewrite. - Implemented responsive interfaces for complex data visualisation, where fleet operators needed dense information to stay readable on a phone in the field. - Worked directly with product and UX to turn operational requirements into something usable. - Established testing practices and code-quality standards for the frontend team. - Mentored team members on Vue best practices and component architecture. ## Senior Frontend Developer — Customer Alliance December 2020 to February 2022 · Berlin Built Vue applications for Customer Alliance, a hospitality-industry SaaS platform. - Developed interactive dashboards presenting performance scores and trends for hotel operators. - Created data-visualisation components for review analytics, turning large volumes of guest feedback into something a hotel manager could act on. ## Frontend Developer — Mercedes-Benz March 2020 to September 2020 · Berlin Customer-facing web applications for Mercedes-Benz, across booking and e-commerce. - Built the Portuguese test-drive booking tool with Vue and GraphQL. - Developed the German online shop, including the car configurator, with Vue and TypeScript — a deeply stateful interface where every option constrains the others. - Collaborated across international teams in Germany and Portugal. ## Frontend Developer — Publicis Pixelpark April 2018 to February 2020 · Berlin Websites and intranet platforms for large corporate clients, largely in vanilla JavaScript — good grounding in what frameworks actually do for you, learned by not having one. ## Earlier - Web Developer at blitzrechner (freelance, 2017–2018) — building online calculators. A nice symmetry with what I now do in my own time: the Potsdam Mietspiegel calculator is the same problem, approached with eight more years of experience. - TYPO3 Assistant, co2online gGmbH (freelance, 2017–2018) — CMS work for a non-profit in the energy-efficiency sector. - Ausbildung: Mediengestalter für Digital und Print (2012–2015) — a design and production apprenticeship at Labor für Gestaltung Schleßelmann, Berlin. It is why I tend to notice typography and spacing, and why I can usually talk to designers in their own vocabulary. ## Education OSZ Druck- und Medientechnik Berlin — Mediengestalter für Digital und Print, 2012–2015. ## Core technical focus Vue 3, Nuxt, TypeScript, Node.js, NestJS, server-side rendering, REST APIs, CSS, web performance optimisation, accessibility, Playwright, Vitest, Cypress, CI/CD, and AI-supported development. --- ## Projects URL: https://oliver-pietsch.de/projects Last updated: 2026-09-18 Things I have built outside of client work, and — more importantly — still run. Operating something yourself for years teaches you things that shipping and handing over does not. ## Mietspiegelrechner Potsdam mietspiegelrechner-potsdam.de is a free tool that helps Potsdam tenants and landlords classify an apartment against the city's official qualified rent index (Mietspiegel). Rent indices are published as dense official tables with scoring rules attached. Working out where your flat actually falls means reading a PDF carefully and not making an arithmetic mistake. The calculator does the table lookup and the orientation-aid scoring, compares the result against the rent actually being paid, and fills out the official form. It is genuinely useful to people in a way that most side projects are not, and it is also where I try out engineering ideas without a deadline attached: - Nuxt 4 with full prerendering. Every HTML route is generated at build time, so the site is static to serve but written like an application. - A separately versioned calculation core kept at complete test coverage. The rent logic is the part that must not be wrong, so it lives in its own package with its own quality gate, independent of the UI. - Machine-readable surfaces. A documented JSON API, an OpenAPI description, an llms.txt, and a Model Context Protocol server, so AI assistants can call the calculator correctly instead of hallucinating rent figures. If someone asks an assistant about Potsdam rent levels, I would rather it fetch a real answer than invent one. - Structured data validated against what Google actually accepts, checked in CI against the built HTML rather than against intent. - Deployed from CI to a small self-hosted server, with a smoke test that boots the real build artifact and verifies every public endpoint before the deploy counts as successful. It is open source and AGPL-licensed. ## Self-hosted smart doorbell A private smart doorbell system, built and actively run: device logic, a web interface, and HomeKit integration, all self-hosted. No cloud service sees who is at my door, and it keeps working when someone else's API has an outage. ## Developer tooling for Vue and Nuxt Smaller utilities, editor integrations and workflow helpers that remove friction from day-to-day Vue and Nuxt work. These generally start as something that annoyed me twice in one week. Most of it is on GitHub. ## This site The site you are reading is a Nuxt 4 application rendered on the server, with content in Markdown parsed server-side so the parser never reaches the browser. It is deliberately small: self-hosted cookieless analytics, no external fonts, no third-party scripts, and no cookie banner - because nothing is stored in your browser, none is needed. --- ## What I do in my free time URL: https://oliver-pietsch.de/free-time Last updated: 2026-09-18 Outside of work, most of my technical time goes into two things: developer tooling around Vue and Nuxt, and a homelab that has grown well past the point of being a weekend project. ## Developer tooling Practical tooling around Vue and Nuxt — small utilities, editor integrations, and workflow helpers that remove friction. Deep dives into framework internals tend to come with this: understanding how Nuxt actually resolves and renders things makes you considerably better at debugging it at work, and the ideas usually find their way back into real projects. ## The homelab Several Raspberry Pis run a permanent self-hosted stack at home. It started as a DNS ad-blocker and turned into the thing that runs the house. ### Network and infrastructure - AdGuard Home — network-wide DNS filtering - Caddy — reverse proxy with automatic certificates - Podman — rootless containers, the whole stack's runtime - PostgreSQL — shared database for the services that need one ### Home automation - Home Assistant — the automation core - Mosquitto — MQTT broker for the devices - Matterbridge — exposing non-Matter devices to the Matter ecosystem ### Monitoring - Prometheus — metrics collection - Blackbox Exporter — endpoint probing - Loki and Promtail — log aggregation - Grafana — dashboards and alerting Running your own monitoring changes how you think about production systems. When an alert wakes you up, you get strict very quickly about which alerts deserve to exist. ## A self-hosted smart doorbell The most involved piece: a private smart doorbell, developed and actively run, connecting device logic, a web interface and HomeKit integration. Nothing leaves the house, and it keeps working during someone else's outage. ## Why bother Self-hosting is the cheapest way I know to stay honest about operations. Writing frontend code is a different discipline from keeping a service running for years, and doing the second one makes you better at the first — you stop treating deploys, certificates, backups and logs as somebody else's concern.