...of a Fintech designer involves constant interaction with numbers and people.

A Day In the life

…of a Fintech designer involves constant interaction with numbers and people.

Data Visualization

Data visualization is usually numbers heavy, because you spend a relatively small amount of your time figuring out the right presentation. The bulk of your time is spent tweaking the presentation to gracefully accommodate all possible data scenarios.

Interaction Design

Inevitably individual UI interactions become their own mini projects. This is because the data configuration behind the interaction has to be defined. More often than not, you will need to put on your data scientist hat, flesh out requirements, and configure usable information in order to get to get the UI functioning and delightful.


Prototyping is all about feedback from people. However, try to include rough financial concepts so that your stakeholders can better engage and help you envision the end result.


Requirements are always fairly number heavy because there is usually analytical work that has to be done. However, you get to interface with lots of people when you gather, vet and define requirements. Requirements are similar to “universal joints”. They transfer information from one silo to another. This makes them great conversation pieces because everyone owns them and feels comfortable collaborating.


Research falls dead center in the Numbers/People interaction universe. Half of your time is spent talking to people about what they do and what they need or might need. The other half of your time is spent looking up terms, investigating financial concepts, and sometimes learning the basic math behind a particular topic.