Credit Application Refresh

PayPal Credit UK

The TLDR Version

User problem — what real friction the user was hitting

Business stakes — what was at risk if it didn't get solved or got solved wrong

My role — your specific contribution in a cross-functional setting

Outcome — what changed (metrics or qualitative signals)

The LDR Version

Overview

One short paragraph: what the product was, who used it, and what state it was in when the project started.

  • judgment calls, especially where compliance, risk, legal, or commercial pressure pulled against user clarity

  • how messy (regulatory language, legacy flows, conflicting stakeholder asks) got usable for the end user

  • who pushed back, where the disagreements were, how they got resolved

Iterations and dead ends

What you tried that didn't work and why. This is the section hiring managers probe hardest in interviews, so it earns its own real estate.

Annotated before/after screens live here as the primary visual. Show v1 / v2 / v3 with brief notes on the move from each version to the next. The visual does its real job: showing movement between versions, not just the final state.