Another project that shows a different side of my work was building Citi’s developer API platform.

Citi needed a dedicated site where external developers could easily understand, test, and integrate Citi’s APIs into their own products. This was the first time Citi was directly opening up its tools and capabilities to developers, so there was a lot riding on clarity, trust, and usability.

I led the visual design and overall experience, working closely with UX, product and engineering to make something that felt approachable, modern, and credible — especially for an audience that’s often skeptical of large financial institutions.

One of the biggest challenges was that APIs are inherently abstract. So instead of just listing documentation, we designed the experience around end-to-end customer journeys. Developers could actually see how Citi’s APIs would work in real-world scenarios, not just read about them.

We also built a full testing environment so developers could experiment safely before committing to an integration. And we made space to highlight success stories, so potential customers could see how other companies were already using Citi’s tools to solve real problems.

The platform launched with about sixty-seven hundred users signing up almost immediately, and we continued to add hundreds of new developers every month. More importantly, it changed how Citi engaged with developers — from a closed, enterprise-only mindset to a more open, partner-driven model.

For me, this project reinforced how much design matters in making complex, technical products feel understandable and usable, especially at scale.