My name is Alexander Ferring, I'm a 35-year-old German.

I am a lead front-end developer with a particular focus on Angular applications written in TypeScript, with experience guiding development teams and coordinating with stakeholders. I consider myself a fast learner, am fluent in English, and have a broad foundational understanding of technological context.


Core skills and technology-stack

I believe Angular serves very well in providing performant cross-platform applications that can be developed in a strongly typed and well-testable environment.
In what follows, allow me to showcase Progressive Web App (PWA) functionality, in particular the stack and patterns that I utilized:

Angular frontend

Front end written in TypeScript with standalone components, Signals, and styled using Bootstrap 5. Building on concepts such as ahead-of-time compilation, tree-shaking, server-side rendering (SSR), and Service Workers for caching, web-push, and offline support.

The Angular CLI serves as the primary bundler and task runner, with @angular/ssr providing SSR functionality and hydration.

GraphQL endpoint

GraphQL is provided by the Node server in addition to the REST-endpoints and consumed by an Apollo client implementation.

This allows the app to fetch only the exact set of properties that are actually needed for a specific render, hence avoiding over- and underfetching data. Furthermore, this neatly improves efficiency by allowing for dynamic queries, reducing roundtrips as well as costs incurred with implementing new route endpoints.

Nodejs server

Providing RESTful API / CORS routes, connecting the front end with the database, push notifications, and mail-transfer functionality. I utilize Express, Mongoose, and Nodemailer modules, to name a few.

Angular SSR is tightly coupled with the backend to bootstrap a server-side render of the Angular app. This improves Time to Interactive and First Contentful Paint, as well as improving social media, crawler, and search engine compatibility.

Docker containers

Nginx Docker components are used as reverse proxies, to auto-renew certificates, and to host the Node.js Express environment that prerenders and serves the front end.

I utilize acme-companion to auto-renew certificates and generate Nginx proxy configurations, as well as mailcow-dockerized as a containerized mail suite and transfer agent.


Performance

I encourage you to also consider this website's Google Lighthouse rating as a benchmark for PWA best practices. You may already know the Google Lighthouse Audit tools that have been built into Chrome for a while now.
To learn more about Lighthouse, please consult the Chrome docs or watch this short GIF I compiled for you.


Skills at a glance

  • Angular: Signals, Resources, SSR with hydration, NgRx, PWA & Service Workers
  • Front-End: SASS, Apollo GraphQL, Bootstrap 5, dynamic component systems
  • Back-End: GraphQL (Apollo Server), SQL, AWS including Lambda
    • JavaScript / TypeScript: Node.js Express APIs, MongoDB
    • Java: Spring Boot and Hibernate
  • DevOps: Docker (multi-stage builds), GitLab CI/CD, Nginx reverse proxy, pfSense
  • Tooling: Vitest, ts-morph for static analysis, AI-assisted development workflows
  • Prior experience: PHP (Symfony), Angular Universal, Kafka Streams, Python ML


Selected Blogs

Enabling Team Velocity

Force multipliers for small development teams: living documentation strategies, branch-aware CI/CD pipelines, developer experience automation, and pragmatic AI tool adoption.

Tooling AI

Building a Dynamic Component System in Angular

JSON-driven component composition for multi-customer configurability, covering recursive rendering, type-safe element interfaces, view-scoped state management, and the Loggable debugging pattern.

Angular AI

Scaling Angular Testing with Vitest

AnalogJS integration, reusable test utilities, and patterns for testing Angular signals and effects with Vitest.

Angular Tooling AI