Experience

Aspira

Building the next generation of software for state-park operations, reservations, and guest experiences.

Role: Senior Software Engineer
When: Sep 2024 – Present
Where: Remote

The role

What I was there to do

Aspira is rebuilding a broad, decades-old parks platform as a modern operating system for state-park administrators. I work across product modeling, platform architecture, delivery systems, and the engineering practices that help a growing TypeScript monorepo stay understandable.

Selected impact

Work that moved things forward

01
Translated on-site state-park requirements into designs for versioned, conditional, and shareable reservation rules while pressure-testing the surrounding configuration and taxonomy models.
02
Cut typecheck time from 82 seconds to 4 seconds with remote caching, then led an 11-point CI/CD initiative and traced minute-long tests to dependency-injection barrel re-exports.
03
Redesigned Slack alarms, eliminated false-positive capacity alerts, added structured query logs, hardened load-balancer headers, and added safeguards around migrations and N+1 queries.
04
Set standards for documentation, code review, and AI context quality while piloting next-generation TypeScript, linting, and formatting tools.
05
Founded and continue to lead an AI guild with 5–10 regular attendees focused on agent models, reusable skills, and better codebase context.

A closer look

The work behind the bullets

Product systems

Turning park policy into software

State parks are full of rules that look simple until they interact: seasons, inventory, customer eligibility, check-in windows, occupancy, and the taxonomy administrators use to describe what they offer. My work has often started at that boundary between real operational policy and a model engineers can safely evolve.

I have designed and reviewed approaches for configurable reservation rules, limitations, business configuration, and the newer taxonomy model. The through-line is making powerful systems legible to the administrators who have to use them—not merely elegant to the engineers who build them.

Engineering systems

Making the monorepo faster and safer

As the codebase grew past ten applications and packages, I introduced and operated monorepo tooling, added remote caching, and investigated the dependency patterns behind slow builds and tests. That work reduced one typecheck path from 82 seconds to 4 seconds and became the foundation for a broader CI/CD improvement program.

I was also the first engineer through a rotating DevOps role. I used the opportunity to improve alarms, logs, load-balancer behavior, database safeguards, and the feedback loops engineers rely on when production behaves differently from a laptop.

Team practice

Better context for people and agents

I care about the quality of the context surrounding the code: design documents, review standards, observability, and the instructions we give increasingly capable coding agents. In 2026, I started a twice-monthly AI guild where engineers compare tools and turn useful workflows into reusable skills.

Toolkit

Technologies in the mix

TypeScript
AWS
SST
CDK
Aurora PostgreSQL
DynamoDB
OpenSearch
Nx
Apollo GraphQL
New Relic