Team Enablement
I help teams adopt ways of working that keep delivering long-term.
- Reviews, standards, mentoring
- DX: tooling, build/test setup, strong defaults
- Technical decisions documented and easy to find
Tech Lead · Web Platforms · Team Enablement
I make scalable web platforms reliably deliverable.
Architecture decisions that won't hurt later, plus teams that can execute them. Focus: Developer Experience, Quality, Performance.
Who I am
I'm a software engineer focused on web platforms in e-commerce and SaaS, with 10+ years of experience building product and platform systems, both in teams and independently.
I enjoy working on systems that need to live for a long time: clear boundaries, strong defaults, minimal magic. In teams, I focus on enablement: solid reviews, transparent decisions, and tooling nobody hates.
I've taken ownership early, even without a formal lead title: introducing standards, driving refactorings, and establishing observability with OpenTelemetry so issues are found faster and releases become more reliable.
What I deliver
Platform Architecture
Structures that scale without every change becoming painful.
- Modular architecture, clear boundaries
- API design, versioning, migration strategies
- Monorepo/Nx, reusable libraries
Quality & Observability
Problems become visible early and releases stay controlled.
- OpenTelemetry tracing, logging, monitoring
- Testing strategy and CI/CD as defaults, not “later” projects
- Performance budgets and pragmatic optimization
Stack (selection)
- TypeScript · Angular · NestJS · Node.js
- SSR · REST · SSE · TypeORM
- Docker · Pipelines · Deployments
Projects
A lightweight TypeScript application based on Three.js featuring realistic scaling, orbital paths, custom GLSL shaders, subtle cinematic effects, and additional information about the planets.
A browser-based UI to make LM Studio comfortably accessible within a local network. Focus: clean system architecture, tool use, and advanced workflows.
How I work
1. Goals & Constraints
I clarify scope, risks, and what “done” means before we debate architecture.
2. Decisions you can find later
Trade-offs documented briefly, so the team doesn't repeat the same debate.
3. Enablement over heroics
Standards, reviews, and tooling so the team can deliver without a bottleneck.
4. Operations as part of the product
Tracing, logs, and tests aren't “later”, they're prerequisites for reliable releases.
Technical principles
Some principles that guide my work:
- Boring tech unless there's a measurable win against it.
- Observability is part of the product.
- Clear commitments matter more than vague promises.
Contact
I'm open to roles in technical leadership and software architecture, as well as selected consulting projects.