Skip to content

Rich Majewski

Senior / Staff-level systems, platform, and reliability engineer.

I build deterministic tooling, failure-aware systems, and reproducible infrastructure, with a focus on Rust, Linux, observability, and operational rigor.

Most of my work sits at the intersection of systems engineering, platform reliability, and technical product building, especially the kind of work where recovery, maintainability, and clear operating boundaries matter over time.

Professional Snapshot

  • 15+ years operating at Senior/Staff level in platform, systems, and reliability engineering
  • Owned and operated production environments at multi-thousand node scale
  • Reduced alert volume from 100–200/day to fewer than 10/day through SLO-driven observability and system design
  • Designed and maintained private-cloud infrastructure (SDDC) as a primary operator
  • Built deterministic tooling and pipelines focused on reproducibility, failure handling, and operational clarity
  • Background spans three decades of infrastructure evolution, which has shaped a strong bias toward durable, failure-aware system design

What I Do

  • Platform and infrastructure engineering
  • Site reliability / production engineering
  • Systems tooling and Rust-based infrastructure software
  • Reproducible build and CI/CD systems
  • Failure-aware architecture, observability, and recovery design

What I’m Looking For

I tend to be most effective at the Staff level, where the work is centered more on systems and operating models than on short-term firefighting.

I’m generally focused on roles involving:

  • Platform and infrastructure engineering
  • Site reliability / production engineering
  • Systems and tooling (Rust, Linux, internal platforms)

The work I usually gravitate toward includes:

  • designing systems that reduce or eliminate recurring failure modes
  • reducing operational noise through better architecture and observability
  • building internal platforms and tooling that improve engineering effectiveness

I do my best work in environments that value:

  • clear system boundaries and contracts
  • long-term system health alongside delivery
  • ownership at the system level, not just the ticket or service level

Writing

I write occasionally about systems design, reliability, deterministic tooling, and engineering tradeoffs.

This section will stay curated rather than high-volume. I’m more interested in writing things worth revisiting than feeding a content treadmill.