LendingClub · Product & Experience

Hi! I'm Anusha.

I'm a Cognitive Science student at UC Davis with a minor in Computer Science. I got into design through an interest in how people think, make decisions, and interact with technology.

That led me to product and UX, where I enjoy working across the full process from understanding user problems to designing and testing solutions. Most recently, I was a Product Design Intern at Narb, where I worked on onboarding and the core AI experience that we shipped.

Across my work, I focus on making complex and confusing experiences feel clear and usable, especially in areas where trust and clarity really matter. That is a big reason why I'm excited about LendingClub and the opportunity to design thoughtful digital financial experiences.

Interview deck · LendingClub

Anusha Ramachandran · Product & UX

Product & Experience internship

I design for moments when complexity meets real people.

I'll walk through three projects that show how I approach design from start to finish, from understanding the problem to delivering clear, thoughtful solutions. I'll start with Nexus, my internship project at Narb where I designed the onboarding and core AI experience that was built and launched, then move to NeuraNote, where I designed a study tool grounded in cognitive science to help users better understand and retain information, and finish with FlowOps, which focuses on designing across multiple roles. Each project follows a similar structure, with key visuals included where they help tell the story.

Navigate this deck

  • Use the top tabs, or scroll—the highlight tracks where you are.
  • In each project: click a section on the left, or press ← → to step through images and sections; ↑ ↓ jumps between Intro / Nexus / NeuraNote / FlowOps / Close.
  • Click a main image to enlarge; Esc closes.
Scroll

Project walkthrough

Nexus

One answer backed by multiple models, designed to feel clear and trustworthy.

Product design · Narb internship · Shipped with engineering (Figma, Cursor, Lovable)

View full case study
Section 1 / 901 · Overview

Sections — jump to any part

01 · Overview

What Nexus is

Nexus is an AI research platform I designed at Narb during my internship. For complex technical or academic work, students already use AI, but a single response often doesn’t feel reliable. Different models can give different answers, and even in my own experience, I found myself cross-checking across tools to be sure.

  • This project focuses on helping people feel confident in their decisions by giving them a clear answer first, with more detail available if they want it.
  • Nexus does this by running multiple models in the background and combining the results into one focused response, instead of showing everything side by side.
  • The goal is simple: reduce uncertainty and give users something they can actually act on.

LendingClub connection

When confidence is low, users create their own workflows to verify results. That adds friction and breaks the experience. In products where decisions matter, trust determines whether users stay or leave.

Nexus landing page

Project walkthrough

NeuraNote

A study tool designed around how people learn, not just how they organize notes.

UX design & research · 6 weeks · Cognitive science in the interface (Figma, Lovable, Cursor)

View full case study
Section 1 / 701 · Overview

Sections — jump to any part

01 · Overview

The idea

Most note-taking tools focus on organization. NeuraNote focuses on memory, helping students capture ideas, connect them visually, and review them in a way that actually supports learning.

  • Who it’s for: Students who take a lot of notes but still struggle to remember what matters when it counts.
  • What makes it different: The product is grounded in how people learn, using concepts like retrieval practice, spaced repetition, and concept mapping instead of adding more features.

Landing page

Project walkthrough

FlowOps

A multi-role request tool designed to make ownership, progress, and next steps clear.

Product design · 2-week sprint · Enterprise workflows (Figma, Adobe CC, Cursor)

View full case study
Section 1 / 701 · Problem

Sections — jump to any part

01 · Problem

The problem

I designed FlowOps because a lot of internal tools make simple tasks feel more complicated than they should. Requests were spread across email, Slack, and spreadsheets, so it was hard to track what was going on and who was responsible.

  • What that caused: Confusion around ownership, delays in getting things done, and issues being noticed too late.
  • Who it affected: Requesters, agents, and managers were all involved in the same request, but each person needed a different view.

Before we wrap

I’d love to bring this same focus on clarity to your team.

Across these projects, a pattern for me has been taking something that feels unclear at first and shaping it into something people can move through with confidence. That's why I'm especially interested in LendingClub, because even small moments in these experiences can really impact how someone feels when they're managing their money. I'd be excited to bring that same focus on clarity and usability to your team.

View full portfolio