Skip to content

About Eduardo

My Story

I’m a Senior Software Engineer at Prudential. I build design systems and products that scale. I also founded Velton, which builds custom software that small businesses own.

Getting Started at NJCU and Smarttwigs

At New Jersey City University, I built a pathfinding visualizer so I could see where an algorithm looked before it found a route. At Smarttwigs, I learned REST by writing the service behind the leaderboard in Props, a mobile app. Later, while interning at PGIM, I ran NJCU’s software development club and hosted its first frontend bootcamp. Teaching showed me how much I enjoy helping other engineers grow.

Building PInnacle at PGIM

As an intern, I wrote Angular components and services for PGIM’s internal apps. Later I led our department’s move to React. That’s where I got into design systems.

PInnacle’s library grew to 50+ components across 20 internal apps. Teams could start a full-stack project in under five minutes. I also led delivery of 15+ applications built with React, .NET, and SQL. On one critical API endpoint, we cut the response time in half.

I wrote Storybook examples and onboarding guides that helped new engineers get up to speed in about a week instead of four. With several teams using the library, we had to make sure a fix for one app wouldn’t break another. PInnacle served our department. I also proposed modernizing a broader design system and later worked with a colleague on a proposal for a company-wide application platform.

Design Systems at Prudential

On Prudential’s Design System, I build accessible React and TypeScript components and write examples that show engineers how to use them. I also write skills and plugins for Claude Code to help it follow our conventions when it makes changes to the library.

I also build products that scale. When screens that do similar work load their data in different ways, knowing how one works doesn’t help much with the next, so I refactor them to follow one consistent pattern.

What I Build Outside Work

I made Yni Anniversary so my girlfriend could unwrap a little 3D world on our one-year anniversary. My order-entry dashboard needed almost the opposite: a form that got out of the way and a server that wouldn’t accept an invalid order.

I organized the code for both projects the same way: I kept components with the features that used them, put shared controls in one place, and tested what someone could actually do in the app. I did the same with my market-data dashboard and this portfolio, even though the dashboards use Vite and this site uses Next.js.

A conversation about what people were building with AI got me thinking about businesses around me: a party-rental business, a produce business, the places I shop. A rental owner knows what it means for an item to be booked. They shouldn’t also have to figure out how to build and test a reservation system, keep it up to date, or hand it off to someone else.

That’s why I founded Velton. I want small businesses to get software built on a solid foundation, software they can keep using and changing long after the first version ships.

What’s Next

Next, I want Velton’s first apps running for real businesses, and a public site that explains Velton without a tour from me.

The first two are a party-rental business and a produce business. A reservation and a produce sale aren’t the same problem. I want to learn what each one needs, then see which parts of the engineering can serve both.