I'm a third-year biomedical engineering student, but at my core I'm a researcher. I build communities, help people, and take the lead when something needs doing. That started before I had a name for it. In middle school I joined a humanitarian club and saw, up close, what people were going through, and how much difference real help could make. High school is where I found what I actually wanted: to point my technical skills at biology.
That combination, wanting to help people and having a technical skill set, is why I keep taking on different kinds of projects. My pattern from the start has been taking things from zero to one. I come up with the idea, start a team, and keep it moving. A project stops being interesting to me for one of two reasons. Either I don't see potential in it, or I realize it isn't my problem to solve, not because I can't do it, but because someone who has actually lived through the problem can solve it better than I can.
In five years, the biggest thing I want to have done is start automating research. I've always wanted to see what people are capable of once a barrier is gone, and research has one of the biggest barriers there is. Removing it, so people can look into and learn about anything they're curious about, is the goal behind almost everything I do. At RISE for Health, that means helping people learn about healthcare and helping them find each other and be heard. At Project90, it means leading a team toward something with a real impact, something people can walk away with for themselves.
The throughline in all of it is that I want to enable people. I believe there are a lot of paths to building something big, and I want to build mine by helping others and making an impact through technical work nobody else has done yet. I think that's what research can do, what entrepreneurship can do, and what leadership can do. To me, that's what being part of a community means.
Newsletter on Substack
