Hello, I'm Gary McKeever, and I

Design systems that survive business whiplash.

Over the last decade, I've gotten good at reading what the business actually needs and designing systems to support it. I make the architectural calls that keep features shipping while the platform evolves underneath to keep solutions moving forward.

Gary McKeever
Gary McKeever · Staff Software Architect

Point of view

How I Think

  1. Messy business logic is normal.

    Real systems collect exceptions, timing rules, and old decisions that still matter. Good architecture keeps that complexity contained so new edge cases add business behavior, not technical sprawl.

  2. Solve platform concerns in the platform.

    Retries, durability, coordination, and audit trails belong in the platform when they can. Business code should solve business problems, not rebuild infrastructure one feature at a time.

  3. Infrastructure is critical.

    Architecture is not just code structure; it includes deployment, runtime shape, scaling, and long-running execution. A clean codebase on the wrong runtime model is still a bad system.

  4. Simple is deliberate.

    The most robust systems usually look simple because someone did the hard planning up front. Clear boundaries, fewer moving parts, and deliberate tradeoffs make software easier to change, operate, and trust.

  5. The first version teaches you.

    Good architecture leaves room to solve the problem twice: once to learn, and once to lock it in with the real edge cases in view. The second pass should fit reality, not the assumptions that came before it.

I do some of my best work when a broad, ambiguous problem needs a clear, structured solution; I work even better under pressure.

Where It Shows Up

I led a major, high risk platform transition off an EOL foundation.

Ongoing

I led the organization-wide transition of a revenue-critical workflow platform off an end-of-life foundation and onto a supported fork. That work turned a major platform risk into a controlled path forward without disrupting the system the business depended on.

Outcome: Replaced an organization-wide EOL risk with a stable, supported transition path.

Intermediate → Senior → Staff → Architect at Moxe Health

Workflow systems, Migration planning, Production change management

I led an engineering-wide shift to a containerized developer experience.

Delivered

I led a cross-team shift from ad hoc local setups to a shared containerized development standard. It brought local development closer to deployed behavior, improved consistency across teams, and created a pattern the engineering organization adopted and kept building on.

Outcome: Drove a lasting engineering culture shift around modern, deployment-aligned local development.

Docker, Local development standards, Integration testing, Kubernetes-aligned workflows

I rebuilt a legacy MS Access ERP into a full ASP.NET solution.

Delivered

Early in my career, I rebuilt a legacy MS Access ERP into a full ASP.NET system as the sole developer, integrated it with MAS 100, and built the reporting layer around it. That work shaped how I think about architecture: software has to fit real operational behavior, not just look clean on paper.

Outcome: Built a business-critical operational system end to end and the instincts that still shape my architecture work.

C#, .NET, SQL Server, Angular, Node.js

From pharmacy counters to healthtech platform architecture, the pivots and compounding decisions that shaped how I build today.

How I Got Here

Career Education Milestone
2026

Published ASTR alpha

Shipped a playable alpha build of ASTR: a single shard persistent universe survival game.

2025

Published Ekkos

Published a scheduling platform built on resilient reminder semantics and natural-language task creation.

2021 – Present

Moxe Health

Healthcare data aggregation & platform engineering

Led enterprise modernization using strangler patterns, event-driven autoscaling, and staged decoupling. Progressed from Intermediate to Senior, then Staff, and now Architect.

Intermediate Senior Staff Architect

Distributed services, CI/CD, Cloud operations

2021

Pivoted into healthcare tech

Shifted from small-business tooling to platform-scale distributed systems.

2016 – 2021

Software Developer

Northeast Technical Services

Sole-developed a custom ERP used by ~50 staff. Built GIS portals, finance dashboards, and SAGE integrations. First full-time engineering role.

C#, .NET, SQL Server, Angular, Node.js

2015 – 2017

Pharmacy Tech · Inventory Manager

CVS Pharmacy

2014 – 2017

B.S. Computer Science + Business Minor

University of Minnesota Duluth

Software Engineering, Analysis & Design, and IT in Business. This decision shifted my trajectory into software architecture.

2011 – 2015

Team Member → Pharmacy Technician

Target Corporation

2007 – 2010

Associate of Arts

Mesabi Range Community & Technical College

2007

Eagle Scout

2007

High School Diploma

Eveleth-Gilbert High School

Still writing the next chapter.

If this is the kind of work your team needs, reach out.

I test new ideas with side projects - sometimes it is nice to not have the pressure of product constraints!

What I Build

Ekkos interface showing persistent task scheduling

Ekkos

Active build

A reminder system built around timing, state, and follow-through.

A reminder system built around timing, state, and friction reduction. It turns plain-language input into structured reminder behavior. It is also a working product for testing whether better workflow design can make small software more dependable and considerate.

React, .NET, Quartz.NET, API integrations

ASTR single-shard persistent-universe survival sandbox preview

ASTR

Published alpha

A top-down space survival sandbox built as a single-shard persistent universe with MMO-style world pressure.

ASTR is now its own published game entity: a single-shard persistent-universe survival sandbox where mining, processing, logistics, building, movement, and defense all happen in one shared world and create exposure that other players and threats can push against.

Custom game architecture, single-shard networking, persistent-world simulation, survival sandbox design

What I Work In

Languages

  • C#
  • Java
  • Python
  • Node.js
  • SQL

Frameworks

  • .NET
  • ASP.NET
  • EF Core
  • React
  • Angular
  • WPF

Data

  • PostgreSQL
  • SQL Server
  • Spark
  • Databricks

Platform

  • AWS
  • Azure
  • Docker
  • Kubernetes

Systems

  • Airflow
  • Temporal
  • Camunda
  • Unity

Contact

If you want to talk about architecture, platform modernization, or building systems that can keep moving as the business changes, get in touch.