I’m Fiodar Sazanavets, an ex-environmental scientist turned software leader. Today, I help product teams as a Fractional CTO and hands-on tech advisor, bringing a scientific, evidence-based approach to architecture, leadership, training, and delivery.
At Microsoft I’ve led and shipped complex .NET/Azure systems. At Scientific Programmer, I use the same rigor—hypothesis → experiment → measure → decide—to help clients move faster with less risk.
What I do
Fractional CTO
Strategic technical leadership without the full-time overhead—roadmaps, decision logs, and 90-day evidence cycles that tie engineering to business outcomes.Tech Stack & Architecture Advice
Pragmatic reviews and experiment-driven recommendations for .NET/Azure, resilience, performance, and cost—validated with metrics and rollback plans.Tech Leadership & Hiring
Team topology, delivery rituals, and structured hiring loops that raise the bar—complete with rubrics and an implementation playbook.Training for Software Teams
Workshops designed with learning science (spacing, retrieval practice, interleaving, deliberate practice) plus a reinforcement plan to ensure skills stick.Engineering Playbooks & Standards
Clear, adoptable standards (branching, testing, reviews, releases) with measurable acceptance criteria so quality doesn’t depend on heroics.Hands-On High-Value Engineering
Sleeves-rolled-up help on CI/CD, Azure environments, and complex technical problems—targeting improvements in DORA metrics (lead time, CFR, MTTR).
Why “Scientific Programmer”
My first career in hard science trained me to think in hypotheses, design small safe-to-fail experiments, and base decisions on data. I apply that same method to software: baseline the metrics, test the change, measure the result, then scale what works. Clients get reproducible results, not opinions.
How engagements work
Observe – baseline delivery & quality (lead time, CFR, MTTR, PR cycle time, cloud cost)
Hypothesize – define the smallest change likely to move the metric
Experiment – implement with guardrails and a clear success threshold
Measure – compare pre/post on an agreed time window
Decide – adopt, iterate, or roll back; capture in a Playbook
Every engagement includes a Decision Log and concrete artifacts your team can reuse.
Let’s talk
If you need a Fractional CTO or targeted help with architecture, leadership, training, standards, or CI/CD, I’d love to learn about your goals and share first steps.