Hyrum Butler

Full-stack software engineer | Greater Kansas City Area

I build and modernize full-stack software across .NET and React.

I have 5+ years building enterprise web applications with C#, ASP.NET Core, React, TypeScript, SQL, and Azure. The work has included CMS modernization, member-facing systems, authentication services, and Salesforce integrations, with an emphasis on maintainability, clear tradeoffs, and software that still works when the happy path ends.

I am currently looking for my next software engineering role.

See selected work Get in touch Download resume

01 | Selected work

Work that shows how I think

The technologies matter, but the decisions around them matter more.

Current independent project | Source available

Ocean Intelligence

A full-stack vessel research application that turns historical AIS observations and public registry records into an explorable research workflow.

View the source on GitHub
Ocean Intelligence search controls and a result list of vessels observed within the selected area and date range.
Ocean Intelligence vessel research view for JUST HANGIN' showing filtered results, sampled historical AIS presence, identity history, and Global Fishing Watch attribution.
Research view

Uncertain maritime data becomes an organized research view. Search results lead into a structured vessel dossier with Global Fishing Watch attribution and clear data caveats. Historical AIS observations indicate past presence in the searched area, not a live vessel position.

The problem

Maritime data is incomplete, sometimes conflicting, rate-limited, and easy to overstate. The application needs to make useful evidence understandable without presenting historical observations as live or verified truth.

What I built

A React and TypeScript interface backed by an ASP.NET Core API. The backend owns authenticated Global Fishing Watch requests, validation, caching, concurrency control, rate limiting, and safe error mapping. The frontend supports cancellable searches, cached vessel details, keyboard-accessible selection, and a structured research dossier.

The engineering choices

The system keeps its public contracts separate from upstream response models and preserves attribution and data caveats in the interface. It deliberately uses native fetch and local React state, with no database, map library, or authentication until a real product need justifies them.

Engineering evidence

  1. Application-owned API contracts stay separate from upstream Global Fishing Watch response models.
  2. The access token and all Global Fishing Watch communication remain on the ASP.NET Core backend.
  3. Caching, request cancellation, concurrency coordination, and rate limiting protect upstream access and user interactions.
  4. Problem Details and xUnit coverage exercise validation, mapping, upstream failures, caching, and irregular registry data.
  1. 01 React interface
  2. 02 ASP.NET Core API
  3. 03 Global Fishing Watch

React 19 | TypeScript | ASP.NET Core | .NET 10 | xUnit | Global Fishing Watch API

Current independent project | Source available

Warple

A manually launched, tray-resident desktop companion with animated behavior, physics-based movement, dragging, throwing, climbing, and a transparent desktop overlay.

View the source on GitHub

Browser to native

React mounts a Phaser scene while Tauri and Rust own native lifecycle, display geometry, tray behavior, and narrow desktop integration.

Security boundary

Versioned, validated, data-only companion profiles cannot execute code, choose arbitrary paths, or grant themselves permissions.

Delivery evidence

JavaScript and Rust tests, compiler and lint checks, dependency auditing, build validation, and Windows installer generation keep the release path honest.

  1. 01 React Mounts the application surface
  2. 02 Phaser + Matter.js Own animation, behavior, movement, and physics
  3. 03 Tauri + Rust Own native lifecycle and desktop integration

Tauri | React | TypeScript | Phaser | Matter.js | Rust

Warple began as a re-architecture of WindowPet. Its current Blooky definition and artwork remain credited placeholder material, not original Warple artwork or the project's permanent identity.

Recent production work

Selected examples from production systems, without the corporate victory lap.

01

Content platform modernization

Contributed to key parts of a transition from a traditional Sitefinity CMS to a headless Next.js 15 and Storyblok architecture while continuing to ship production features.

02

Member-facing systems

Built an end-to-end member dashboard with 12+ integrated modules covering certifications, company rosters, demographics, and support services. Connected Salesforce and Pardot workflows with role-aware access and CSV/XLSX exports.

03

Search and identity integrations

Built an accessible Mapbox GL certification search for desktop and touch kiosks, and contributed to a .NET 8 authentication service using Salesforce OpenID Connect, claims, and role-based authorization.

02 | Experience

A practical path through modern and legacy systems

AVIXA

-

Full-stack Software Developer

Built and modernized member-facing web applications across React, Next.js, TypeScript, Node.js, Sitefinity, Storyblok, Salesforce integrations, and .NET.

Remotasks

-

AI Trainer

Evaluated software-engineering and language-model outputs, then provided structured feedback to improve correctness, intent alignment, and reliability.

RTS Labs

-

Software Engineer

Maintained React applications and legacy Ruby on Rails systems, built a recruiting-focused single-page application, and contributed to API and database modernization for property-rental software.

03 | Approach

Understand the system. Make the tradeoff. Leave it better.

I like to understand a system before changing it, but production work rarely waits for perfect context. My job is to find the important information, make a clear decision, and ship something that fits the system around it.

01

Orient first

Learn the shape of the product, its constraints, and the people who depend on it before choosing a solution.

02

Prefer the smallest useful change

Solve the actual problem without building a platform for hypothetical future requirements.

03

Design for the unhappy path

Loading, failure, stale data, conflicting records, and maintenance are part of the product, not cleanup for later.

04

Communicate the tradeoff

Make decisions understandable to technical and non-technical collaborators so the work can be trusted and maintained.

Field note

Working toolkit

Frontend systems
React, TypeScript, JavaScript, Next.js, Vue.js, accessible HTML, CSS, and SCSS
Backend and integrations
C#, .NET, ASP.NET Core, Node.js, Express, REST APIs, SQL, Salesforce, and OpenID Connect
Platforms and delivery
Storyblok, Sitefinity, Azure, Git, automated testing, Agile delivery, and AI-assisted development

04 | About

A crooked route into software

My route into software was not direct. I studied political science, worked in international trade, and took programming courses while driving trucks and later a tour bus. That background left me comfortable learning unfamiliar systems, talking with different kinds of people, and caring whether a tool works in the real world.

Away from a keyboard, I am usually happier outside: hiking, camping, or building something with my hands. The Sandbox is where the less restrained experiments live.

05 | Contact

Looking for the next useful problem

I am currently looking for my next software engineering role. If you need someone who can work across the stack, learn an existing system, and make it easier to live with, I would like to hear from you.