I build software by asking why it should exist before asking how to build it. NYU CS grad, fast learner, and someone who cares about turning information into understanding, not just shipping features.
I didn't get into engineering because I wanted to write code. I got into it because I kept asking why things worked the way they did, and whether they could work better for people. My work usually starts with a question: not what can I build, but why should it exist?
That curiosity has led me to build tools that give context to data. Helping someone know exactly when to leave for an airport pickup, or understand what a currency conversion actually means in everyday life. I'm drawn to projects that sit at the intersection of systems and people, where the goal isn't just efficiency but clarity and purpose.
For me, the best solutions come from blending analytics, design, and empathy. Building technology is about turning information into understanding and making complexity feel a little more human.