Context
EF Ultimate Break is the young-adult group travel brand of EF Education First — a $11B education and travel company operating in 100+ countries. Ultimate Break runs 175+ guided international trips across 65+ destinations for travelers aged roughly 18 to 35, with a booking experience that has to handle low-deposit reservations, payment plans, group coordination, private custom tours, and a marketing surface large enough to rank for serious travel search terms.
When I joined the project, I was the sole frontend engineer, working alongside a team of several backend engineers. The engagement ran roughly a year and a half — enough time to own the customer-facing web platform end to end, from the browsing experience through the booking flow.
What I Did
End-to-end ownership of the customer-facing site. I built and maintained the web platform across its full surface area: the marketing and about pages, the destination and trip browsing experience, the trip detail views, the deals and promotions flows, and the full multi-step booking and checkout. If a user could interact with it on the site, I owned the frontend for it.
Booking and checkout. The checkout was the most involved part of the platform. Booking a trip isn’t a simple cart transaction — it involves trip selection, date and flight options, rooming preferences, add-ons, deposit handling, payment plan setup, traveler information for each passenger, and terms-and-conditions flows that vary by destination. Every piece of state had to be persisted, validated, and recoverable; travelers rarely finish a booking in one sitting, and losing their progress was unacceptable.
Custom content management system. I built a custom CMS from the ground up so that the marketing and operations teams could manage trip details, itineraries, pricing, imagery, destinations, and promotional content without engineering involvement. The CMS had to serve a catalog that spanned dozens of trips and hundreds of pages, and had to feed a public site where content changes shipped constantly.
SEO as a first-class engineering concern. For a travel brand of this scale, SEO is not a marketing concern you hand off — it’s an engineering invariant. Every browsing and trip page had to render with production-grade metadata, structured data, canonical URLs, and fast initial paint for search crawlers and users alike. Every change to the catalog had to maintain those invariants without manual intervention. Much of my work was making sure the platform ranked for the long-tail travel queries that drove organic acquisition, across destinations, trip styles, and travel types.
Collaboration with backend and stakeholders. As the solo frontend engineer, I was the interface between the backend team and every product, design, and marketing stakeholder shaping the experience. Translating business requirements into the right technical shape — and pushing back when the requested shape was going to hurt us — was as much of the job as writing code.
Technical Details
The stack was Angular.js on the frontend and C# with EF Core on the backend. Angular.js was already aging by this point, and working in it at scale across a site this large required discipline — clear module boundaries, consistent state patterns, and careful management of digest cycles on pages that rendered large catalogs. The custom CMS had to integrate cleanly with the C#/EF Core content model and produce pages that met the performance bar SEO demanded.
The engineering problems weren’t exotic — they were hard because of the combination: a large catalog, a complex booking flow, an SEO-critical public surface, a custom CMS, and a single frontend engineer owning all of it.
Outcome
Delivered a complete customer-facing rebuild of the Ultimate Break web platform — browsing, booking, CMS, and everything in between. The platform served as the production customer experience during my engagement. It has since been completely rebuilt by the company, but the architecture and shipped experience carried the brand through the period I owned it.