“How can this policy change the future of security at our company?” The manager asks, directing his question at me. Standing at the helm of the room, I am not surprised they would ask such a question. While not a part of their ranks, over the course of 4 months, my firm had been tasked with improving the overall security baseline of this establishment. Their systems were at least a generation outdated relative to the latest security systems and practices available today. It was no wonder they had experienced a record-breaking data breach that cost them more than eight figures in damages. “Simple. Your personnel were never properly trained to recognize modern intrusion techniques. By pairing a zero-trust policy with continuous training, we reinforce your defenses at the behavioral level.” After finishing my response, I could only look at the past ten years as if leading up to this moment. As a blooming teen, I witnessed the boom of LLM and AI technologies. It was luck, but I had recently been introduced to the world of cybersecurity. So, I decided to dedicate myself to becoming an expert specializing in securing AI-systems and protecting against malicious AI-powered tools. So, I completed my computer engineering degree at Texas A&M with a concentration in cybersecurity, funded in part through the Department of War Cyber Scholarship Program. Along the way I had earned my Security+ certificate and stacked that towards CySA+ and eventually OSCP. Then I had taken steps to expand a digital product business I had made, where I self-published Security+ study guides on Gumroad, and grew that into a full certification-prep product line. Eventually, I open-sourced and expanded my LLM-based phishing analyzer, built on the Claude API, turning my initial research project into a viable tool for everyday users. After graduating, I moved to work as a security engineer at the intersection of AI and defense, such as SOC operations and AI red-teaming, learning how enterprises failed to implement AI safely and ethically before I sold them solutions. Along the way, I published research on LLM vulnerabilities, such as prompt injection, data exfiltration, and model manipulation using frameworks like OWASP’s LLM top ten and MITRE ATLAS. As my personal product revenue increased, I reinvested that revenue and my salary into a founder’s fund co-founded with a team from my TAMU and industry network. Eventually after a few years, I founded my firm: an AI security company of 10-20 engineers, serving mid-sized businesses and defense contractors, organizations deploying AI without the budget for enterprise security teams. We offered automated AI threat assessment tools, a direct descendant of my phishing analyzer with direct red-team consulting. My vision was never a far-off dream but an expansion of steps I had already taken towards a future that, ten years earlier, had seemed just beyond my doorstep. I never planned merely to secure businesses and organizations; I planned to build a future where ordinary people would not fear the compromise of their personal data and could live without worry.

One of the earliest memories I can look back on is the inside of a remote-controlled car I took apart. I remember all the electrical components that fascinated me. I didn't understand what I was looking at, but as a seven-year-old who'd just figured out how to use a screwdriver, I liked seeing what was going on inside. That habit of pulling things apart to understand them never left me. By the time I reached secondary school and started designing small mechanical systems, I had stopped asking just "How does this work?" and started asking, "How could this work better, and who could that help?" Computer engineering was my answer to that second question, a degree that lets me turn curiosity into solutions that actually reach people. My path here wasn't a smooth ride. Growing up across London, Atlanta, Dallas, Houston, and Nigeria meant constantly rebuilding myself: a new environment meant a new school, which meant new social codes and expectations. But that repeated adjustment taught me an adaptability I couldn't have learned by staying in one place. In NJROTC, I remember the countless hours of drills we practiced under the hot sun under adverse conditions, and the work ethic that was built stayed with me long after. Debate and poetry gave me a different skill: the ability to take a complicated idea and make it land with someone who's never thought about it before. My academic work in Nigeria, across math, physics, chemistry, and literature, grounded all of it in discipline. Taken together, these experiences taught me that what matters most isn't any single subject but the discipline of learning itself and the responsibility to use it for something beyond yourself. And discipline is what pulled me specifically toward cybersecurity within computer engineering. I remember when a friend of mine showed me how he'd gotten into a school security system. While I disapproved of what he'd done, the fact that a simple understanding of computers gave him that much access stuck with me; it was the first time I really understood how much power sits behind ordinary systems and how much responsibility comes with knowing how to work them. I plan to pair my degree with a cybersecurity minor and use that combination to work at the intersection of AI and security, fields where the cost of getting security wrong will only grow as more of daily life runs on autonomous systems. Long-term, I want to work with companies, nonprofits, and local governments to build technology that's not just secure but accessible and sustainable for the communities that need it most. I'm also a second-generation college student, which means I've watched what it takes to get here. I remember the late nights my parents spent working so that my siblings and I could have opportunities they didn't. That's part of why this scholarship matters to me beyond the dollar amount. It would let me spend less time worrying about how to afford tuition and more time actually building toward the work I want to do: work that pays that sacrifice forward. I'm not chasing a credential. I'm building toward being a specific kind of engineer, one who understands that the systems we secure are only as valuable as the people they serve and who's willing to do the unglamorous work of getting the fundamentals right so that others can trust the technology in their lives to be secure and private. This scholarship would be an investment in that work and proof to those who sacrificed for me that I intend to make it count.

Before I knew what a library or books were, I understood what it felt like to yearn for them. Jealous of my older brother’s ability to read, I begged my parents for countless hours to take me to our local library. Once inside, I treated every visit like an adventure I never wanted to end. Even now as a computer engineering student, I find room to read where I can, five minutes between classes, or a chapter before bed. The library was my nurturing home for imagination and creativity. And three books in particular have played a large part in my being. When the angel Gabriel came to the prophet Muhammad, peace be upon him, he told him, “Read, in the name of your lord." Spoken from chapter 96 of the Holy Quran, this book has been my guiding light throughout life. Not a book I finished once, but one I return to constantly, with insights from every new opening. Throughout my efforts to memorize it, the Quran taught me that learning is not a phase but a lifelong obligation and that knowledge carries the responsibility of being learned, shared, and used. What you learn, you owe to others, and that very principle shapes how I approach everything, from my studies to my community service. It is why I spent countless hours volunteering, teaching, and learning for library programs, giving back to places that gave me so much. If reading is a habit, then learning about habits from The Power of Habits by Charles Duhigg changed how I understood human behavior and processes. Learning about cue-routine-reward loops taught me that outcomes are rarely products of motivation but the result of systems. I built systems and structured daily routines that have helped me maintain a 3.7 GPA whilst training simultaneously in cybersecurity, coding, and AI. It has shaped my career interest in cybersecurity: security failures are almost never technical but human habits exploited at scale. Understanding why people make themselves vulnerable was an insight that led to my own research project, an AI-based email phishing analyzer, studying how systems are used to exploit and protect predictable human behavior. Thirdly, The 21 Irrefutable Laws of Leadership by John C. Maxwell taught me how leadership is influence earned through service, not titles, and people are the backbone of every company, organization, system, or collaborative goal. As a school prefect and thorough debater, I learned to put those laws into practice. Listening first, developing others and measuring success by what the team accomplishes rather than what I can do alone has shaped my ambitions: I don’t just want to work in AI security; I want to eventually lead teams that make emerging technology safer for everyone. Together, these books gave me a foundation that only the library made possible: picking a book off the shelf and learning faith and purpose from the Holy Quran, systems thinking from Duhigg, and people-first leadership from Maxwell. My goals reflect all three lessons: earning my Security+ certification, pursuing the DoD Cyber Scholarship, and building a career protecting people in an AI-driven world. I’ve even started creating free and low-cost study guides for others looking to get started in the cybersecurity space. Barbara Cain’s story resonates with me deeply: she made a difference in the lives of young readers, and I want my learning to make a difference in the lives of young learners. The library gave me a place to imagine who I could become. Books gave me the map. I intend to keep reading and to keep passing what I learn forward.

I had just scored 0.5 out of 10 on my first math exam in Nigeria. After just transferring to a Lagos boarding school after years in the United States, I was convinced that the move alone would make me grow. It didn't. I sat staring at the equations I couldn't understand and questions that looked foreign, and finally I heard myself say what I'd been afraid to admit: maybe I'm just not built for this. But then I thought of the proprietor of this school. He founded the school himself, born in a village of fewer than a thousand people and raised without the resources most people consider the minimum requirements for success. He didn't inherit an institution or stumble into his position. He built it, classroom by classroom, from a life that had every reason to stay small. By the time I met him, his school was competing in robotics, producing strong exam results, and doing it all in a corner hidden from the world. He had a way of dropping lines that didn't sound like speeches. They sounded like lessons he'd already lived through. The one that pulled me back that day: "If all you have is effort, then you have no choice but to give it your all." He never said talent was irrelevant. He said it was optional. Effort wasn't. I didn't understand that fully until I held that math paper. But when I did, something shifted. I stopped asking whether I belonged and started asking what I hadn't done yet. I realized I'd never truly studied. Not deliberately, not consistently. I didn't have the right textbooks. I hadn't connected with a single classmate who could help me. These weren't excuses; they were a checklist to be crossed out. So, I built a routine. I studied every subject with an intensity I never knew I had. I joined clubs such as robotics, debate, and poetry. Not because I was confident but because he'd shown me that confidence is a result, not a prerequisite. I made friendships that turned into study partnerships and lifelong relations. I showed up, imperfect and persistent, every single day. Two years later, I graduated from the top three of my entire set. I passed my WAEC and GCE exams with flying colors; most importantly, I dominated the math class that once intimidated me. What the proprietor gave me wasn't a scholarship or a curriculum. It was a framework for how to move through difficulty without falling back. He proved, through his own life, that where you start is not the ceiling. He modeled the exact discipline he preached, which made it impossible to dismiss as just motivation-speak. I came to that school thinking the environment would change me. He taught me that I had to change myself and that the only tool guaranteed to everyone, regardless of background, is effort applied without exception. That belief is the reason I pursued computer engineering. That man is the reason I believe I'll finish it.

One of the earliest memories I can look back on is the inside of a remote-controlled car I took apart. I remember all the electrical components that fascinated me. I didn't really understand what I was looking at, but as a seven-year-old who'd just figured out how to use a screwdriver, I liked seeing what was going on inside. That habit of pulling things apart to understand them never left me. By the time I reached secondary school and started designing small mechanical systems, I had stopped asking just "How does this work?" and started asking, "How could this work better, and who could that help?" Computer engineering was my answer to that second question, a degree that lets me turn curiosity into solutions that actually reach people. My path here wasn't a smooth ride. Growing up across London, Atlanta, Dallas, Houston, and Nigeria meant constantly rebuilding myself: a new environment, a new school, new social codes, and new expectations. But that repeated adjustment taught me an adaptability I couldn't have learned by staying in one place. In NJROTC, I remember the countless hours of drills we practiced under adverse conditions, and the work ethic that built them stayed with me long after. Debate and poetry gave me a different skill: the ability to take a complicated idea and make it land with someone who's never thought about it before. My academic work in Nigeria, across math, physics, chemistry, and literature, grounded all of it in discipline. Taken together, these experiences taught me that what matters most isn't any single subject but the discipline of learning itself and the responsibility to use it for something beyond yourself. That responsibility and discipline is what pulled me specifically toward cybersecurity within computer engineering. I remember when a friend of mine showed me how he'd gotten into a school security system. While I disapproved of what he'd done, the fact that a simple understanding of computers gave him that much access stuck with me, it was the first time I really understood how much power sits behind ordinary systems, and how much responsibility comes with knowing how to work them. I plan to pair my degree with a cybersecurity minor and use that combination to work at the intersection of AI, robotics, and security, fields where the cost of getting security wrong will only grow as more of daily life runs on autonomous systems. Long-term, I want to work with companies, nonprofits, and local governments to build technology that's not just secure, but accessible and sustainable for the communities that need it most. I'm also a second-generation college student, which means I've watched, up close, what it takes to get here. I remember the late nights my parents spent studying or working so that my siblings and I could have opportunities they didn't. That's part of why this scholarship matters to me beyond the dollar amount. It would let me spend less time worrying about how to afford tuition, an internship, or a study abroad opportunity and more time actually building toward the work I want to do: work that pays that sacrifice forward. I'm not chasing a credential. I'm building toward being a specific kind of engineer, one who understands that the systems we secure are only as valuable as the people they serve and who's willing to do the unglamorous work of getting the fundamentals right so that others can trust the technology in their lives to be secure and private. This scholarship would be an investment in that work, and I intend to make it count.

Aron Ralston spent five days trapped between a rock and a hard place in the depths of the Blue John Canyon, forced to break his own arm and amputate it to survive. What haunted me the most since I heard his story wasn’t the amputation but the fact that no one knew where he was. No signal, no way to call for help, and no way for the people who loved him to know he was ever in trouble. If not for his drastic actions, Aron Ralston could have become another missing individual and statistic. I’d feared this story since I was a kid but never expected it to become the reason my team won an A+. Sitting in the back row of my engineering graphics class, I read the prompt on the screen: “Create a project that implements sustainability, power solutions, and technology for the betterment of humanity." I was stuck staring between a paper and a prompt, just the same way Ralston once stared down a boulder. Drifting back into his story, I wondered what if he had never been disconnected in the first place? I pitched the idea to my team of four, and we agreed immediately. Combining our backgrounds in embedded systems, 3D modeling, electrical engineering, and mechanical design, we built the S.O.S Pack, an all-in-one survival backpack designed to keep outdoor adventurers connected to help, even off the grid. It featured GPS satellite location tracking, an efficient battery management system, solar charging, mechanical energy generation for all-day power, advanced cooling, and an emergency beacon, all for under $200. We weren’t just building a device; we were building the thing that could have changed Ralston’s five days into five hours, and we wanted it to be a peace of mind any hiker could afford. No device is ready until it’s been tested where it will be used. So, we spent a week camping, pushing it as we could. The battery drained faster than we’d envisioned; a cloudy, rainy stretch cut out solar input to nearly nothing. One especially rough night, a wiring fault in our battery management system sparked and nearly took out our whole setup. We then spent the next morning re-routing the circuit and added a fuse we should have included from the start. Every failure forced a redesign, and redesign made us better engineers and closer teammates. By the time we presented, with the kinks worked out, we walked away with an A+. That week taught me something I didn’t expect from a class project: that the systems I design and build aren’t just a test of technical expertise but the things people can depend on when it matters most. It’s part of why I've leaned so hard into cybersecurity since. Whether it’s a beacon that must work in a canyon or a network that has hold under attack, the goal is always the same. Build something reliable enough that someone else’s worst day doesn’t have to be their last one. Ralston survived because of his own resilience. He could have survived on someone else’s. I want to spend my career building the tools that mean the next person never has to test theirs the same way.