Senior Frontend-Focused Engineer. Ascend.

The first phase was migration. The public-facing site was a basic WordPress installation. The new version needed to be a Next.js platform that could carry the brand, support the concierge workflow, and grow without rebuilding. I owned the migration. By the end of the first phase the site had moved cleanly and the foundation was in place for everything that followed.

What followed was nine phases of work across one year. Four hundred and thirty five Jira tickets. The number is real and the work behind it is real. Onboarding flows for new clients. Internal portals for the concierge team. Notification systems. Search interfaces. Admin tools. A trip pricing layer. A document generator for itineraries. Each phase was its own product effort with its own design pass, its own backend integration, its own deployment plan.

Two features I owned end to end. The Trips Workspace is a Notion-style table the concierge team uses to plan client trips. Each row is a trip, each column is a planning dimension (flights, hotels, ground transport, dining, experiences, costs, notes), and the workspace lets the team see and edit a trip's full state in one view. The Ascend Analytics dashboard is the other. It is the layer the leadership team uses to understand how the operation is performing, drawn from the platform's own data, designed to surface what the team actually needs to act on, not what is easy to chart.

The role has been frontend-focused but never frontend-only. I write the BFF endpoints my screens depend on. I configure the observability and analytics layer. I manage the deployments and the CI/CD pipelines across Vercel. I get pulled into product roadmap conversations because the team needs an engineering voice that sees the workflow end to end, not just the screen. That kind of contribution is how I have stayed valuable on a team operating eight time zones away from me.