Michael Thomas
Home .NET Games

.NET Backend Engineer


Azure • AWS

Automation • Operational ownership • Cross-team delivery

I work on production .NET services that process live data, focusing on automation and building safe, repeatable recovery/cleanup tooling.

LinkedIn GitHub
.NET 8 Minimal APIs Azure messaging Cosmos DB Automation Debugging / Logging

What I’m Looking For

I’m looking for backend roles building production .NET services where I can contribute across features, automation, and operational tooling. I’m comfortable switching between tasks as needed to keep delivery moving.

How I Work

Automation

I try to remove repeated manual work by building simple tools and scripts the team can reuse.

Debugging

When an issue is hard to reproduce, I add targeted logging so investigation is based on evidence rather than guesses.

Production-safe changes

I prefer repeatable recovery and cleanup steps so fixes are safer to run and less stressful in production.

Documentation + knowledge transfer

I write short playbooks and notes so common support tasks are easier for others to pick up.

Core Skills

Backend: C#, .NET 8, ASP.NET Core (Minimal APIs), Console apps

Cloud: Azure (Cosmos DB, Service Bus, Event Hubs, Key Vault) • AWS (general usage)

Data & messaging: event-driven processing, reprocessing/backfills, reliability-focused tooling

Automation: Bash, PowerShell, operational tooling

Observability / debugging: Grafana, logging, incident triage support

Delivery: CI/CD practices, containers (Docker), basic Kubernetes exposure

Workflow: Visual Studio, SSMS (Azure), ClickUp, Guru

Bettormetrics — Highlights

Startup environment with strong production ownership. Work described at a high level.

  • Linker platform: unified multi-provider streams into a single source of truth across fixtures/markets/selections.
  • Retrospective Linker Service: automated failed linking recovery, saving ~1–2 hours per incident; reused in other workflows.
  • Production recovery tooling: built production-ready cleanup and validation tooling to detect and correct linking/data integrity issues.
  • Automation utilities: built scripts and internal tools to reduce operational workload and accelerate incident response.
  • Platform maintenance: migrated services to the latest Cosmos DB SDK and validated compatibility across dependent systems.
  • Knowledge transfer: captured institutional knowledge and converted it into documentation and operational playbooks (Guru).

More than happy to expand on any of these in an interview.

Socials

github

linkedin