Profile

Robin Winkelewski

Founder & Principal Engineer · RootVector

I design and build business-critical infrastructure, platforms, and production AI systems. I stay with the work from target architecture through implementation to stable operations, so the trade-offs are tested in a running system, not handed over as slides.

Background

Experience behind the judgment.

  1. SAPOct 2018 — May 2023

    Platform change at enterprise scale.

    I led cloud migrations of central development platforms that teams across the company depended on. That work made reversibility, validation, and the cutover itself architecture concerns, not afterthoughts.

  2. SysElevenJun 2023 — Oct 2025

    Security constraints as design inputs.

    At SysEleven I designed secure cloud architecture for public-sector and defence workloads, from the implementation blueprint to certification support. The lesson was broader than compliance: constraints belong in the first architecture conversation.

  3. RootVectorNov 2025 — now

    One accountable line from decision to operation.

    RootVector brings those perspectives together across infrastructure, platforms, and production AI. I work directly with the people responsible for the system and implement the architecture with them, so it meets operational reality. RootVector's own GPU and Kubernetes platform runs the booking and call flow on this site.

Principles

The judgment I bring.

The hard part is rarely drawing a technically valid system. It is choosing the system your business and team can still own when conditions change.

Operating consequences first

A design is incomplete until ownership, failure modes, upgrades, observability, and an exit path are clear.

Constraints before products

Workload placement and tooling follow data, risk, cost, and team capability, not a partner tier or whatever is fashionable.

Direct and explicit

You work with me from scoping through delivery. Decisions, evidence, and unresolved risks are written down so your team can challenge them.

Next step

Thirty minutes. One decision.

In 30 minutes, we can examine the setup, architecture, or risk that needs a decision and identify the most useful next step.

See how engagements start
Book 30 minutes

30-minute working session. No pitch, no commitment.