Skip to content
Saber Motamedi

About

Senior engineer, solutions architect, occasional founder

I design and ship scalable .NET backends and modern web products — from greenfield platforms to architecture audits and migrations.

I design and ship scalable backend systems with Clean Architecture, CQRS, and event-driven messaging. I own problems end-to-end: domain modelling, service boundaries, data, APIs, delivery pipelines, and the diagrams and ADRs that keep systems understandable over time.

How I work

Principles, not process theatre

A handful of beliefs that have stayed true across very different stacks, sizes, and stakes.

Boring tech, sharp boundaries

Pick stable, well-understood building blocks. Spend the novelty budget on the parts that actually differentiate the product.

Domain first, framework second

Model the business in plain code. Keep frameworks at the edges so the core stays testable, portable, and resistant to fashion.

Optimize for change, not for cleverness

Most production systems live for years. Readability, observability, and clear seams beat micro-optimizations almost every time.

Architecture is a deliverable

Diagrams, ADRs, runbooks, and onboarding docs ship alongside the code. Future maintainers should understand the why, not just the what.

Performance is a feature with a budget

Latency targets and capacity envelopes are designed in early — measured, not assumed. Caching and async are tools, not reflexes.

Ship to learn

Small vertical slices, real users, fast feedback. Greenfield design that never sees production teaches you nothing.

Impact

What that has produced in production

  • Architected an 11-service SaaS platform on .NET 8 · gRPC · CQRS · Azure
  • Cut search latency from ~90 ms → <40 ms via service redesign and caching
  • Reduced deploys to <10 min with CI/CD pipelines and blue/green gates
  • Led MSSQL → PostgreSQL migration — replaced stored procedures, views, and functions with C# domain logic
  • Defined a Clean Architecture + React/shadcn reference stack adopted across multiple teams
  • Built an internal troubleshooting system that cut incident-discovery time from 20 min → 5 min
  • Automated sales-discrepancy detection, reducing resolution time to <24 h

Stack

Tools I reach for

Backend
C# · .NET · ASP.NET Core · EF Core · gRPC · REST · SignalR
Frontend
Angular · React · Next.js · Svelte · TypeScript · shadcn/ui
Data
SQL Server · PostgreSQL · MySQL · Elasticsearch · Redis
Messaging
RabbitMQ · MassTransit
Cloud & Ops
Docker · Azure · AWS · GitHub Actions · GitLab CI · Grafana · Prometheus
Architecture
Clean Architecture · Microservices · CQRS · DDD · SOA
Quality
TDD · BDD · xUnit · Postman

Writing

Recent posts

All writing

Currently

Exploring AI-assisted development workflows and refining a .NET 10 reference architecture for scale-oriented platforms.

Open to senior / architect roles globally — remote or relocation. Consulting and advisory engagements welcome.

See selected case studies

Working on a complex backend? Let's talk.

Architecture reviews, greenfield .NET delivery, audits, and fractional advisory. Tell me about your system and the constraints you're navigating.