01
Started the platform as the sole engineer, defining its architecture and building the initial product, integration, cloud, and delivery foundations before two external engineers joined.
Sanitized case study
BAUHAUS · Enterprise configurators
Connecting complex supplier configurators to one maintainable product platform.
Scope shared publicly
I started this platform as its sole engineer; two external engineers joined later as delivery expanded. This page intentionally omits internal topology, business-sensitive data, and unsupported performance claims.
The challenge
Many external systems, one customer experience.
Product configurators often come from different suppliers, with different integration models and delivery constraints. The engineering work is not just embedding another tool: it is creating a platform boundary that supports consistent customer journeys while remaining operable and maintainable for the teams behind it.
My ownership
From the first architecture decisions through production delivery.
02
Built and evolved cloud-native services using TypeScript, Node.js, NestJS, React, GCP, and Firestore.
03
Developed Terraform infrastructure and GitHub Actions workflows to make environments and releases repeatable.
04
Designed APIs and integration patterns for supplier configurators, working across product, UX, and vendor teams to turn requirements into production software.
High-level delivery model
A conceptual view of the responsibilities involved—not a representation of BAUHAUS's internal production architecture.
Customer experience
React-based configurator journeys across BAUHAUS digital channels
Integration services
TypeScript and NestJS services connecting platform and supplier workflows
Managed cloud foundation
GCP and Firestore services provisioned and evolved through Terraform
Delivery system
GitHub Actions workflows supporting consistent build and release processes
Engineering decisions
What the platform choices needed to support.
Create a stable integration boundary
Supplier configurators vary in behavior and lifecycle. Keeping those differences behind a defined integration layer helps the customer-facing experience remain consistent.
Treat infrastructure as product code
Terraform makes cloud changes reviewable and repeatable, reducing reliance on undocumented manual configuration.
Automate the delivery path
GitHub Actions turns build and release steps into shared workflows that the engineering team can understand and improve together.
Keep product and platform work connected
The integration succeeds only when technical decisions account for UX, product requirements, vendor constraints, and production operations at the same time.
The result I can stand behind
A clearer integration model and a more repeatable delivery path.
The work established shared platform patterns for supplier integrations, cloud infrastructure, and automated delivery without relying on unverified percentage claims.