Ashwarya Subhluxmi

What they show

A design leader at Credit Karma who runs design for the marketplace, a $3B business spanning Personal Loans, Insurance, Home Loans, Auto Loans and Cards, reaching 140M+ members. Scope is stated plainly: team pods across those verticals, plus vision, strategy, hiring and executive partnership. Three dated case studies, each written as something she led: a 2025–26 agentic AI product for debt consolidation, the first of its kind at the company; an end-to-end Personal Loans marketplace redesign (2022–24) that grew loan originations 300%; and the mobile-first CK Tax redesign (2019–20) that made it the most-downloaded tax app. Twelve years across Intuit, Quicken, SAP, Oracle, Synopsys and LendingClub sit underneath.

Why it works at this level

Her thesis line, 'I build the picture, the team, and the product, in that order,' is the whole leadership argument in eleven words, and the case studies are arranged to prove it: each one names the strategic framing first, the team second, and the shipped thing last. The scope statement does what most Director sites skip, listing the verticals and the business size so a reader knows what she's accountable for before reading a word of process. The dated case studies also show a trajectory, from a product redesign to a vertical to the company's first agentic product, which is what a hiring committee wants to see at the Director-to-VP step. And the numbers are business numbers (originations, app ranking, revenue), not design-process numbers.

What to steal

Write your thesis as a sequence, not a value: what you do first, second, third. State scope as the business you're accountable for, in dollars or users and in named verticals, before you describe any project. Date your case studies and order them so the reader can see you taking on more each time.

What I'd change

One thing I'd push on. Every site here is good; this is the note I'd send the author.

The site describes her as a 'design leader' without the actual title, and the leadership activities (hiring, pods, exec partnership) are listed rather than shown. One short story about building or restructuring the pod model, with the team before and after, would turn the scope statement into evidence.