Shrey Patel

Designing the connective tissue

UI Designer · Frontend Developer · UX Architect

I make digitalsystems feelconsidered.

I’m Shrey, a product-minded software engineer and UX researcher who enjoys turning complex problems into simple, polished experiences—from the first interface to the systems underneath.

Software Engineer @ Wells Fargo

Frontend interfaces•Product systems•User research

Selected work

Products with a clear point of view.

A small selection of systems where interface thinking and engineering have to work together.

Operational care, in view

01 — Product system2025

DardiBook

Clinic management platform

A digital workspace that brings authentication, real-time collaboration, operational state, and subscription experiences into one calmer clinical workflow.

Next.jsFirebaseLiveblocksRazorpay

Package discovery, in context

03 — Developer toolPortfolio project

Istine Package Manager

React Native package manager

A React Native package-management application built with the NPM Registry API and Firebase. It includes package-specific communication groups, favourites, dynamic theming, notifications, advertising, and quizzes covering NPM, React, and Angular.

React NativeNPM Registry APIFirebase
04 — GenAI experiencePortfolio project

FliplookAI

GenAI fashion assistant

A GenAI-powered fashion assistant built with React, Node.js, and Python deep learning. It analyzes user history and preferences to deliver personalized outfit suggestions and customized fashion recommendations.

ReactNode.jsPythonDeep learning

Style signals, made personal

Shared costs, clearly tracked

05 — Personal finance toolPortfolio project

Bill Splitter

Shared expense tracker

A React Native and Firebase application for tracking group expenses. It records who owes whom, keeps trip-level totals, and includes an in-app payment feature to make settlement more convenient.

React NativeFirebase

Practice

The work behind the work.

I work best in the space between a messy problem and a usable system. That means thinking through flows, asking sharper questions, shaping the interface, and staying close enough to implementation that the details hold up.

Flow
Signal / decision / responseSystem note 01
Detail is part of the system.

01

Interface design

Making complex workflows clear, calm, and easy to navigate.

02

UX architecture

Mapping decisions, edge cases, and information before they become interface debt.

03

Frontend craft

Translating systems into responsive, resilient interfaces with considered detail.

04

Research mindset

Watching for assumptions, asking why, and letting real constraints shape the answer.

01

Android technologies

React Native · Expo

02

Backend technologies

Node.js · Express.js · MongoDB · Django

03

Frontend technologies

HTML · CSS · React.js

04

Programming languages

C · C++ · JavaScript · Python

05

Other stacks

Git & GitHub · Bootstrap · Figma · Canva · Tailwind

Achievements and participation

Learning in public.

Community leadership, technical gatherings, and challenges that expanded how I build, collaborate, and keep learning.

Google Developer Student Clubs program mark

GDSC Lead

Google Developer Student Club · 2022 — 2023

Editorial placeholder for INAE–SERB Youth Conclave

INAE–SERB Youth Conclave

IIT Jodhpur · 2022

Editorial placeholder for DotSlash 5.0

DotSlash 5.0

SVNIT Surat · Participation

Editorial placeholder for Learn to Earn Cloud Challenge

Learn to Earn Cloud Challenge

Google Cloud · 2021

ISTE SC MANIT’s Codathon

ISTE Student Chapter, MANIT · Participation

About

A little about me.

Bangalore, India

2+ years of experience

I studied Computer Science and Engineering at SVNIT Surat and now work as a Software Developer at Wells Fargo. I care about what software does under the hood—and how it feels in the hands of the person using it.

My work has taken me across frontend development, backend engineering, databases, and risk technology. I particularly enjoy problems where the answer is not obvious: understanding the constraints, breaking the work down, and shaping an experience that can scale.

Now

Software Developer

Wells Fargo

Education

B.Tech, CSE

SVNIT Surat

Focus

Product systems

Interface to data

Experience

A factual, understated snapshot of the work I do and the systems I want to keep learning from.

Wells Fargo

Software Developer · Market Risk

2024 — Present

Contributing to applications and services that support quantitative risk-management and risk-adjustment workflows. The work stretches across frontend, backend, data, and the technical decisions that connect them.

  • Crafting interface architecture with React and TypeScript.
  • Designing Java and Spring services around real operational constraints.
  • Working across SQL data flows, business logic, and user-facing product details.

Wells Fargo

Software Developer Intern

May 2023 — July 2023

Developed an NLP-based tool to address inconsistent metadata element names across platforms including Collibra and EMH. The tool analyzed business data-element descriptions to generate related technical data elements and presented results with confidence scores.

  • Developed an NLP model for inconsistent metadata element names across Collibra and EMH.
  • Built analysis of business data-element descriptions to generate related technical data elements.
  • Implemented a user-friendly interface for data-element inputs, generated outputs, and confidence scores.

Surabhi.io

Software Developer Intern

Sept 2022 — Feb 2023

Contributed to SURABHI.io, a Social Commerce application from Deep-Tech Computing Private Limited that helps local businesses around the world.

  • Worked on the Django web application.
  • Worked on the React Native mobile application.

ZolutionTech

React Native Intern

Feb 2022 — March 2022

Implemented React Native components and integrated third-party libraries for the application experience.

  • Implemented a range of React Native components.
  • Integrated third-party libraries including navigation and NativeBase.
  • Collaborated with quality developers, designers, and fellow interns.

Engineering philosophy

How I think
about software.

A few principles I return to when systems, screens, or product decisions get more complex.

01

Keep it simple.

Complexity should solve a real problem. If it does not, it is probably just complexity.

02

Build for the person using it.

Technical decisions matter, but software ultimately exists to make someone’s work or life better.

03

Understand before optimizing.

Measure, find the bottleneck, then make it faster—with a reason for every change.

04

Make it maintainable.

The best decision survives the next six months, including the person who has to maintain it.