context
Joining as the first engineer means the pipeline is the first feature
Fuerte is building a mobile app for healthcare professionals to find each other and schedule events. When I joined there was no codebase, which meant the early decisions were about how fast the team could move, not about what to build.
I owned the React Native app end to end — architecture, release process, and most of the surface area.
delivery
Shipping to production with no manual steps and no downtime
The bottleneck early on was never writing features, it was the distance between "it works on my machine" and "it's live". I built a CI/CD pipeline on GitHub Actions and the AWS CLI that runs E2E tests and deploys to production without anyone babysitting it.
That work came before most of the product work, deliberately. Iteration speed compounds; a feature does not.
realtime
Instant feedback was the difference between one session and a habit
In-app messaging, event updates, and user-to-user interactions run over Pusher WebSockets. The first version polled, and it was fine — technically. But an app where your action lands a few seconds later feels broken in a way that is hard to argue with, and people stopped coming back.
observability
You cannot fix what you cannot see
LogRocket and Sentry are what make same-day fixes possible. A session replay next to a stack trace turns most bug reports from a conversation into a five-minute change.