Skip to content
MF

Chapter Six. The year at altitude. 2025 to present.

The standard is the obstacle. Not the geography.

435

Jira tickets

9

Phases of work

10+

Major features

15k km

From the office

Ascend plans private trips for wealthy clients. Austin, Texas. They needed an engineer who could move at the speed of a small US startup while carrying the kind of feature ownership that usually comes from a much more established team. I started in April 2025 from October City, fully remote, fifteen thousand kilometers from the office.

  1. 01WordPress to Next.js migration
  2. 02Public platform foundation
  3. 03Client onboarding
  4. 04Concierge internal portals
  5. 05Notifications and search
  6. 06Admin tooling
  7. 07Trip pricing layer
  8. 08Itinerary document generator
  9. 09Trips Workspace and Analytics

The first phase was a migration: the public site was a basic WordPress installation, and it needed to become a Next.js platform that could carry the brand, support the concierge workflow, and grow without another rebuild. I owned it end to end. By the end of the phase the site had moved cleanly, and more importantly the foundation was shaped for everything that followed, because a migration is not about moving the old thing. It is about choosing what the next three years get built on.

What followed was nine phases of work in one year. Four hundred thirty five Jira tickets. I lead with the number because numbers like it get used to obscure the work, and I want to be exact instead. Onboarding flows for new clients. Internal portals for the concierge team. Notifications. Search. Admin tools. A trip pricing layer. A document generator for itineraries. Each phase its own product effort: its design pass, its backend integration, its deployment plan, its week where it was the only thing that mattered.

Self-owned. One.

The Trips Workspace.

A Notion-style table where each row is a trip and each column is a planning dimension. One view holding the full state of a trip, where the team already lived.

Self-owned. Two.

The Ascend Analytics dashboard.

The layer leadership reads the operation through. Surfaces what the team needs to act on, not what is easy to chart.

Two features I owned completely. The Trips Workspace is a Notion-style table the concierge team plans client trips in. Each row a trip. Each column a planning dimension: flights, hotels, ground transport, dining, experiences, costs, notes. One view holding the full state of a trip, because that is where the team already lived. The Ascend Analytics dashboard is the other: the layer leadership uses to understand how the operation performs, drawn from the platform's own data, designed to surface what the team needs to act on, not what is easy to chart.

The role says frontend but was never frontend-only. I write the BFF endpoints my screens depend on. I run the observability and analytics layer. I manage deployments and CI/CD across Vercel. I sit in roadmap conversations because the team needs an engineering voice that sees the workflow end to end. That is how I have stayed valuable on a team operating eight time zones away: the distance is irrelevant if the standard is met. The year proved the thing I needed proved. I can land features at the speed and the standard a US startup expects, from October City, indefinitely.

The stack at the time.

  • TypeScript
  • Next.js
  • React
  • TailwindCSS
  • shadcn/ui
  • Node.js
  • Vercel
  • Supabase
  • PostgreSQL
  • PostHog
  • Django
  • Zod
  • React Hook Form

The geography is not the obstacle. The standard is. Meet it from anywhere, and the distance stops mattering.