Case Study
Siemens EDA — Building a Multi-Region AWS Platform and Full-Stack Customer Experience Portal
Siemens EDA
Electronic Design Automation — a Siemens Digital Industries Software business
Role
AWS Solutions Architect & Full-Stack Technical Lead
Period
November 2023 – September 2025
Duration
22 months
Reporting Line
Worked alongside the permanent VP and Senior Manager
Industry
Electronic Design Automation
The Situation
Siemens EDA — the business unit behind industry-standard chip design tools — was launching a new B2B SaaS Customer Experience Portal to unify a sprawling collection of disconnected systems. Customers and internal teams were navigating multiple applications to do work that should have been seamless.
They needed the platform built correctly the first time: multi-account AWS infrastructure, a full-stack TypeScript application, CI/CD with quality gates, and observability — not a slide deck and a handoff.
Why Bring Me In
Siemens needed a senior AWS cloud and product engineer embedded in the build — someone who could design the landing zone, write the infrastructure-as-code, own the application architecture (Next.js, NestJS, AppSync), and stand up the pipelines that made 99.99% uptime possible. Discovering architectural gaps in production wasn't an option.
What I Built
- •
Built the entire AWS footprint from zero. No AWS accounts existed when I arrived. Designed the multi-account strategy, VPC topology, network segmentation, multi-AZ patterns, and environment promotion (dev / staging / production). Established Terraform as the IaC standard with reusable modules across all environments.
- •
Architected the full-stack product. Microservices on ECS Fargate with a Next.js frontend, NestJS backends, AppSync GraphQL API layer, RDS Aurora and DocumentDB polyglot persistence, and EventBridge / Step Functions / Lambda for serverless workflows.
- •
Owned CI/CD and DevSecOps as defaults. GitHub Actions with blue-green deployments; Vitest, Playwright, SonarQube, Tenable, and Aqua quality gates; observability via CloudWatch and OpenSearch.
- •
Guided the engineering teams through the build. Conducted architecture reviews, established patterns for GraphQL and serverless event processing, and mentored engineers on AWS service selection and cloud-native trade-offs — so the platform could be sustained after I left.
- •
Introduced AI coding assistants (Claude) into the development workflow, accelerating TypeScript and infrastructure velocity, and evaluated Bedrock integration points for customer-experience personalization.
Business Outcomes
- •
99.99% uptime on the mission-critical Customer Experience Portal
- •
75% faster deployment cycles through CI/CD and quality gate automation
- •
30% infrastructure cost reduction through architecture discipline and FinOps
- •
60% improvement in code quality through standards, reviews, and automated gates
- •
40% acceleration in feature delivery velocity via reusable component library
What I Left Behind
- •
A complete production-ready AWS footprint, fully managed via Terraform
- •
Full-stack TypeScript architecture (Next.js, NestJS, AppSync) with documented service boundaries
- •
CI/CD pipelines with automated quality gates and blue-green deployments
- •
Observability runbooks and patterns the internal team could operate without me