Designer first. Builder second. Both seriously.
I am Shreyo. I design financial products at Bright Money, and when the tool my team needs does not exist yet, I build that too.
I work on the parts of fintech that are hard to make feel good. Reporting someone's rent to a credit bureau. Selling identity protection to a person who does not think they need it. Regulation sets the rules, the stakes are somebody's actual money, and the room to be clever is small.
I stopped waiting for engineering bandwidth to test an idea. I build them instead, not as prototypes but deployed, on a URL, with a database behind them. Competitor Hub reached a production stack three days after I opened the repo and now runs the team's research cycle.
I do not think this makes me an engineer. I think it makes me a designer who wastes less time.
A short and fairly non-linear timeline.
Two Figma plugins published company-wide, and a wireframing system that takes a PRD in and returns on-system screens. Each one started as a document that had not worked.
Credit and subscription products: the rent reporting funnel, the identity protection pitch. Also design ops, which is how I ended up owning the design-status dashboard the exec team reads.
Finalist at the Taiwan International Student Design Competition, and a TEDx talk in the same year.
Typography, systems thinking, and the habit of defending a decision with a reason rather than a preference.
What I actually use, most weeks.
- Figma, deep in it daily
- Design systems and tokens
- Prototyping real branches, not happy paths
- Flow mapping and funnel analysis
- Handoff documentation people actually read
- Claude Code, my main build surface
- HTML, CSS, JavaScript, React
- PostgreSQL and schema design
- AWS: S3, RDS, EC2
- Figma plugin API
- Ask for the brief, not just the screens
- Bring compliance in early, not at approval
- Sequence before surface
- Enforce conventions with tools, not docs
- Ship, then keep it alive
Things that are true but not on the resume.
I keep a running list of competitor flows I find genuinely well made. That habit eventually turned into a product. I am opinionated about naming things, as one of my projects makes fairly obvious.
I read release notes for fun. I think that is normal. Nobody else does.
Working US hours
Design engineering