Hey everyone. I’m not someone who memorized bullet points; I prefer to just walk into the room and start talking about how my brain actually works when I'm solving problems. My background is a bit messy, which is actually good because it means I don't get stuck on neat but useless rules. I had to learn to code on my own, which meant debugging my own mistakes until a Tuesday afternoon when I finally understood recursion. It didn't make sense at first, but that's okay if it's actually useful later. I don't work in a big tech company with a fancy cafeteria; I work on small projects like fixing a website that just won't load or figuring out why a historical event isn't showing up in a database. Those are real problems. One of my key responsibilities was building a system to track public health data during a major event. We needed to update stats every 15 minutes, and the old method of emailing people was a disaster. We built a simple Python script that did the math for us automatically. We reduced response time from three days to just one minute. That's not magic, I know. I wrote the code and tested it a dozen times before anyone else could use it. It was frustrating at first, but once it worked, the rest of the team could focus on the bigger picture instead of writing boilerplate code. I also talk about data in terms of what people actually see, not just how it looks on a screen. One time, I had to explain why a new policy was failing without making it sound like a government blunder. I pulled up the numbers and showed the timeline where the numbers went up and down, then explained that the initial assumption about user behavior was wrong because the data showed the opposite. That explanation was clear and direct. Personally, I like to think of myself as an engineer first and a writer second. Sometimes I get too caught up in the technical details and forget to read the whole thing from the bottom up. I find that helpful when I'm explaining something to someone new because it forces me to slow down and really understand the core idea first. I also love storytelling because it helps me remember the details. We used to do things together, literally together, sharing our drafts and rewriting them over several weeks. It wasn't about having the perfect proposal; it was about finding the version that felt true to us. I've worked in different places and seen different tools. Sometimes I use Excel to track inventory, sometimes I write code in Rust or Python, and at other times I build apps using React. The common thread is always the same: I want to build something that actually works and helps people. I hate companies that hire people just to polish their resumes or follow a rigid process. That's not what skills are for, and I'm not interested in that either. I want to solve problems, learn, and create value. In short, I'm someone who gets excited about new challenges and tries to find the clever solution even when the path looks blocked. I handle pressure well because I've learned to focus on what matters for the next hour rather than worrying about the whole project right now. I'm ready to take on anything that needs to be built, fixed, or improved.