Case Study
How this project was designed and delivered
Overview
Fusion is a data platform designed for pharmaceutical teams that need to curate, transform, and explore very large, highly regulated datasets. It brings ETL pipelines, standardized data models, and interactive dashboards into a single product so analysts, scientists, and commercial teams can all work from the same, trusted source of truth.
Problem
Pharma organizations typically pull data from multiple vendors, clinical systems, and internal tools. These feeds often arrive in different formats and update cadences, making it hard to build reliable reports or run cross-cutting analyses. Legacy solutions were slow to change, hard to extend, and made it difficult to safely evolve the UI for different user groups without breaking existing workflows.
My Role
I worked as a frontend engineer on the Fusion platform, focusing on the micro-frontend layer that powers the web UI. I helped design and implement React-based shells and feature modules that could be independently deployed using Webpack Module Federation, while still sharing core design system components and utilities across teams.
Solution
We adopted a micro-frontend architecture where the core Fusion shell handled navigation, authentication, and layout, and individual product areas (data catalog, pipeline monitoring, dashboards, admin tools) were implemented as separate React micro-frontends. I implemented key parts of the shared layout, routing integration, and design system bindings, and worked on data-heavy views for exploring curated datasets and monitoring ETL health. The architecture allowed teams to iterate independently while still feeling like a single cohesive app.
Outcome
Fusion gave pharma stakeholders a unified, self-service place to work with curated data instead of relying on ad-hoc exports and siloed tools. The micro-frontend approach reduced coordination overhead between teams, shortened release cycles for new features, and made it possible to onboard additional modules and data domains without rewriting the core application.
This write-up focuses on the product problem, my role, and the key architectural decisions behind the implementation, highlighting how design, engineering and UX came together.
It is intentionally high level and technology-agnostic so it can be read easily by both engineers and non-technical stakeholders.