Gitanjali

Product designer in Bangalore. I came to this through architecture school, which is where I learned to think about how people move through a space before deciding what to build in it.

--:-- in Bangalore. Open to new work.

Selected work

The short version: what was broken, and what you changed. Two or three sentences, enough to decide whether to read on.

Read the full case study

The short version: what was broken, and what you changed. Two or three sentences, enough to decide whether to read on.

Read the full case study

The short version: what was broken, and what you changed. Two or three sentences, enough to decide whether to read on.

Read the full case study

About

I studied architecture. That taught me to design for how people actually move and decide, not for how a plan looks on paper, and it turned out to transfer almost directly to software.

I taught myself product design and have been working in it for close to two years. Interfaces, flows, and the writing inside them, because half of any design problem turns out to be wording.

Based in Bangalore. Still early, still learning in public, and happiest on a problem nobody has tidied up yet.

Experience

Product designer, [Company]2024 — now

[Previous role]2023 — 2024

B.Arch, [School]20XX — 20XX

Full CV, PDF

All work

Project name

The one-sentence version of what changed. Lead with the outcome, not the brief — this is the line someone reads before deciding to scroll.

Client: Company
Year: 2026
Role: Product design, research
Team: Two engineers, one PM

What the screen looks like now.

The problem

Who was struggling, with what, and how you knew. Name the person and the moment. "The finance team closed the month in nine days" beats "the process was inefficient."

What you found when you looked closer, and what surprised you. If the analytics said one thing and watching people said another, this is where that goes.

Research artefact, early sketch, or the old interface.

What I did

The decision that made the difference, and the reasoning behind it. One strong idea explained properly beats six screens listed out.

What you tried that didn't work. This is the part other designers read closely, and most portfolios leave it out.

The key screen, annotated if it needs explaining.

A short line from someone who used it, or the sentence that reframed the problem for you. Name, role

What happened

The result, with a number if you have one. If you don't have numbers, say what changed in how people worked instead — that's still evidence.

What you'd do differently. Ending on a real reflection reads as confidence, not doubt.

Next project Project name

All work

Project name

The one-sentence version of what changed. Lead with the outcome, not the brief — this is the line someone reads before deciding to scroll.

Client: Company
Year: 2026
Role: Product design, research
Team: Two engineers, one PM

What the screen looks like now.

The problem

Who was struggling, with what, and how you knew. Name the person and the moment. "The finance team closed the month in nine days" beats "the process was inefficient."

What you found when you looked closer, and what surprised you. If the analytics said one thing and watching people said another, this is where that goes.

Research artefact, early sketch, or the old interface.

What I did

The decision that made the difference, and the reasoning behind it. One strong idea explained properly beats six screens listed out.

What you tried that didn't work. This is the part other designers read closely, and most portfolios leave it out.

The key screen, annotated if it needs explaining.

A short line from someone who used it, or the sentence that reframed the problem for you. Name, role

What happened

The result, with a number if you have one. If you don't have numbers, say what changed in how people worked instead — that's still evidence.

What you'd do differently. Ending on a real reflection reads as confidence, not doubt.

Next project Project name

All work

Project name

The one-sentence version of what changed. Lead with the outcome, not the brief — this is the line someone reads before deciding to scroll.

Client: Company
Year: 2026
Role: Product design, research
Team: Two engineers, one PM

What the screen looks like now.

The problem

Who was struggling, with what, and how you knew. Name the person and the moment. "The finance team closed the month in nine days" beats "the process was inefficient."

What you found when you looked closer, and what surprised you. If the analytics said one thing and watching people said another, this is where that goes.

Research artefact, early sketch, or the old interface.

What I did

The decision that made the difference, and the reasoning behind it. One strong idea explained properly beats six screens listed out.

What you tried that didn't work. This is the part other designers read closely, and most portfolios leave it out.

The key screen, annotated if it needs explaining.

A short line from someone who used it, or the sentence that reframed the problem for you. Name, role

What happened

The result, with a number if you have one. If you don't have numbers, say what changed in how people worked instead — that's still evidence.

What you'd do differently. Ending on a real reflection reads as confidence, not doubt.

Next project Project name