Portfolio — Remote · US

 

Principal Software Engineer

I design and build durable systems — from the metal up to the moment a person taps “go.”

Scroll

01—About

I build software that stays quiet in production and obvious in hindsight.

Currently

Principal Software Engineer
Remote · US

I’m a principal engineer who likes the unglamorous parts: the data model that ages well, the deploy that never wakes anyone at 3am, the interface that feels obvious in hindsight. Two decades in, I still measure my work by how quiet it is in production.

I work end to end — architecture, infrastructure, and the last mile of polish where software stops feeling like software. I care about teams as much as systems, and about leaving things better documented than I found them.

02—Selected Work

A few things I’ve shipped.

Featured

A Platform, Named Later

This is placeholder copy sized like a real entry so the layout reads true before you add case studies. Swap in a real title, a two-sentence summary, a cover image, and links. The row scales gracefully as you add more.

  • architecture
  • platform
  • typescript
Source
01

An Infrastructure Story

Another placeholder entry. Describe the problem, the constraint, and the outcome in a sentence or two. Add a cover image via PROJECT_EXTRAS and a case-study link when the write-up exists.

  • infrastructure
  • ci/cd
  • observability
Source
02

Something Small & Sharp

Not every project is a platform. Use entries like this for the sharp little tools — the CLI, the library, the internal thing everyone quietly relied on.

  • tooling
  • dx
Source

03—Approach

How I think about the work.

  • 01

    Boring on purpose

    The best systems are quiet. I optimize for the change you’ll make in a year, not the demo you’ll give tomorrow — proven tools, clear seams, and failure modes you can reason about half-asleep.

  • 02

    From the metal up

    I’m comfortable across the whole stack — kernels of infrastructure to pixels of interface. Owning the full path is how you make the parts actually fit.

  • 03

    Craft is a contract

    Type, spacing, latency, error copy — the details users can’t name are the ones they feel. Polish isn’t decoration; it’s a promise that the invisible parts were built with the same care.

  • 04

    Leave a trail

    Good work outlives the person who did it. I write things down, name things well, and hand off systems the next engineer can grow into without an oral history.

04—Contact

Let’s build something durable.

hello@brianoney.dev