There's a specific feeling I chased into this career — the moment you change one line of code and see the world respond. That immediacy hooked me. But what kept me was something deeper: the obsession with understanding why things work, not just that they work.

I'm a Full Stack Engineer who lives on the backend side of the stack — designing systems that scale without drama, APIs that don't lie, and architectures that make sense three years later. The frontend is a means to an end; the backend is where the real decisions happen.

What drives me is system thinking. Why did this technology exist? What problem forced someone to invent it? That question shapes how I write code, how I pick tools, and how I approach every technical decision I make.

Ambitious by nature. I set a goal and I don't let go of it. My teammates would tell you I communicate clearly, work relentlessly, and always finish what I start. I'm currently building toward working on products where engineering and intelligence meet — systems that don't just process data, but understand it.