Trip checkout looked simple from the outside. Underneath it was a queue-driven workflow across Stripe, Rails, and a slow external CRM that needed to fail visibly instead of silently.

Atlas Obscura's API needed to be more than a set of Rails controllers. It needed predictable errors, sane account-linking rules, and tests the app team could trust.

A small profile feature turned into a nice full-stack problem: query the right countries, render a reusable stamp component, and expose the same data to the app.

The interesting part of app work in a mature Rails codebase isn't the endpoint. It's the combination of API contracts, moderation tools, and product logic that keeps mobile and web aligned.

A deep dive into my 2.5-year experience as a Software Engineer at Atlas Obscura, where I contributed to building and maintaining the digital platform that showcases the world's most fascinating places.