SHELL RECHARGE · ENGINEERING STORY
Building a Frontend Platform for Shell Recharge
Scaling frontend architecture across a growing ecosystem of EV products.
- ROLE
- Lead Frontend Engineer
- TIMELINE
- 2020–2026
- FOCUS
- Frontend Architecture • Angular • React • Technical Leadership • Product Development
THE CHALLENGE
As electric vehicle adoption accelerated, Shell Recharge expanded from individual charging experiences into a broader ecosystem supporting fleet operators, commercial customers, and everyday drivers.
The frontend needed to support multiple products serving different audiences while remaining consistent, performant, and maintainable as engineering teams and business priorities evolved.
The challenge wasn't simply delivering features. It was creating an architectural foundation that allowed products to grow independently while presenting a cohesive experience to customers.
MY ROLE
As Lead Frontend Engineer, I helped shape frontend architecture across several customer-facing products while remaining deeply involved in implementation.
My work spanned architectural planning, technical leadership, mentoring engineers, collaborating with product and design, and delivering major features used by both fleet managers and EV drivers.
Throughout the platform's evolution, I focused on creating systems that would support long-term product growth rather than solving only today's requirements.
BUILDING THE PLATFORM
Rather than thinking of each application as an isolated project, we treated the frontend as an evolving platform.
That meant balancing immediate product delivery with investments in architecture, shared components, and engineering practices that would continue paying dividends as the organization expanded.
As new products emerged, consistency became just as important as speed. Shared patterns reduced duplication, improved maintainability, and helped multiple engineering teams deliver cohesive user experiences.
PRODUCT SPOTLIGHT
Fleet Manager
Fleet operators rely on software to monitor vehicles, manage charging infrastructure, and make operational decisions that directly affect business efficiency.
The application needed to present large amounts of operational data while remaining approachable for users making decisions throughout the day.
I helped develop and evolve the frontend architecture, working closely with product and design teams to create interfaces that balanced powerful functionality with clarity and usability.
Driver Portal
The Driver Portal presented a very different set of challenges.
Rather than managing fleets, drivers needed quick access to charging information, account management, and everyday tasks through an interface optimized for speed and simplicity.
Building both products reinforced an important lesson: good frontend architecture isn't only about sharing code. It's about supporting different user needs while maintaining a consistent experience across an entire product ecosystem.
ENGINEERING DECISIONS
Several architectural decisions shaped the long-term direction of the platform.
One of the most significant was adopting Module Federation to support independently deployable frontend applications while preserving a cohesive user experience.
This approach allowed engineering teams to work more autonomously, simplified deployment workflows, and created a foundation that could evolve alongside the business.
Equally important was establishing frontend patterns that emphasized maintainability, performance, accessibility, and developer experience as first-class concerns rather than afterthoughts.
IMPACT
The resulting platform enabled multiple products to evolve more efficiently while delivering consistent experiences across different customer audiences.
Beyond shipping features, the architectural investments helped engineering teams move more confidently, reduce duplication, and support the continued growth of Shell Recharge's frontend ecosystem.
WHAT I LEARNED
Working on Shell Recharge reinforced that architecture is ultimately about enabling people.
The best technical decisions aren't necessarily the most sophisticated—they're the ones that help teams build better products over many years.
That perspective continues to shape how I approach frontend engineering today: create systems that simplify complexity, empower engineers, and allow products to evolve without sacrificing the customer experience.