The Cybersecurity Experimenter Who Became a Builder: My Journey from Cybersecurity to AI
Every builder has an origin story, and mine starts with breaking things, not building them. Long before I wrote a line of production code, I was the kid poking at scanning tools, testing exploits, and pushing systems to see where they'd give. I wasn't building anything back then — I was just curious about how far I could go. Looking back, that curiosity turned out to be the best training ground I could have asked for, because it taught me something most developers only learn the hard way: every application has a weak point somewhere. That single lesson has quietly shaped everything I've built since.
Security Isn't a Checkbox. It's a Discipline.
Here's what most people get wrong about security: they treat it like a one-time task. Ship the app, run a scan, tick the box, move on. But security doesn't work that way — it's a 24x7, 365-days-a-year commitment. You don't secure a website once and forget about it. You keep watching it: the servers, the databases, the API usage, the small quiet changes that eventually become big problems.
That mindset is exactly what pushed me to build ReconX and NmapAnalyzer — tools that came directly out of wanting to turn "breaking things" into something useful. Instead of just finding weaknesses, I wanted to build the tools that help other people find them first, before someone with worse intentions does.
The Turning Point: From Manual Coding to AI-Powered Building
Somewhere along the way, I started experimenting with AI tools built directly into my code editor. It completely changed how I thought about building software. I found myself asking a question I hadn't asked before: is writing every single line by hand really the most valuable use of my time?
I'd already built plenty of projects the traditional way — ClinchWorks, NightCap-Feedback, EduSpheree — real products solving real problems. But once I saw how much faster I could move by combining my security instincts and coding foundation with AI-assisted development, something clicked. You can't always change things quickly by doing everything manually. When you know how to work with AI, you can go from idea to working product in minutes, and still apply everything you know about secure coding to make sure it actually holds up.
Solving a problem isn't the hard part. Figuring out which problem is actually worth solving — that's the real work.
I never took a formal course to get here. What I did get good at was prompting — learning how to translate my own thinking into instructions an AI system could act on and build from. That's a skill in itself, and I don't think it gets enough credit.
Diving Into Machine Learning — One Year, No Shortcuts
Eventually I asked myself a harder question: is web development alone going to be enough in the future? I didn't think so. So I shifted my focus toward Generative AI and Machine Learning, and spent close to a year experimenting, prompting, and slowly building real intuition for the field.
I already had a head start — Python was part of my academic background, and I'd used NumPy and pandas for coursework, so the syntax wasn't new. That meant I could skip past the basics and get straight into how machine learning actually works: how models learn from data, how algorithms like random forests operate, and eventually how neural networks are structured.
That year of hands-on work turned into a string of real projects:
- CloudCostAI — an AI-driven cloud cost forecasting tool
- A loan-approval classifier built on a Random Forest model
- A Resume Shortlister classification model
- A Hybrid RAG API built with FastAPI and Ollama
- A GenAI-powered stadium operations platform for the FIFA World Cup 2026 competition, focused on crowd management, navigation, and multilingual assistance
What excites me most is that this isn't a narrow path. I can work on the front end of an AI product, or go deeper into the backend — model architecture, training pipelines, research. There isn't just one lane here; there's a whole spectrum of ways to contribute, and that flexibility is part of what makes this field worth investing in.
Recognition That Came From Showing Up
None of this happened in isolation. Along the way I became a Google Student Ambassador, took on a trainee role at ToriiMinds, and earned a GitHub Copilot Certification and the Hackviser CORE cybersecurity foundations certification. I stayed active on TryHackMe and LeetCode too — not because anyone asked me to, but because staying sharp in security and problem-solving has to be a habit, not a one-time effort.
Giving Back: Rising by Lifting Others
Somewhere in this journey, my role shifted from just building for myself to helping other students find their footing. As part of my placement training work, I reviewed close to 100 student GitHub profiles to assess real job-readiness — not just what a README claims, but what the code actually shows. It was a reminder that the gap between "looks impressive" and "is actually solid" is one of the biggest things holding students back, and closing that gap is work I care about.
That's the philosophy I try to lead with: rising by lifting others. Growth means a lot more when you're helping the people around you grow too.
My Advice to Second-Year Students
If there's one thing I want students — especially those in their second year of engineering — to take away from my experience, it's this: don't wait until third year to figure out your direction.
- Start exploring early. By third year, you're expected to already know your stack. Students who start figuring things out at that point often end up scrambling.
- Watch the job market yourself. I check LinkedIn regularly to see what roles are trending, what's slowing down, and what's paying well. First-hand awareness beats secondhand advice every time.
- Don't settle for a low-value internship out of panic. A rushed internship taken just to have "something" on your resume rarely moves the needle the way people hope.
- Take control of your own learning. Explore multiple domains before you specialize. The broader your foundation, the more options you'll have later.
Where This Leaves Me
Security and AI aren't competing priorities — they're two sides of the same future. AI is growing fast, but as more of the world runs on AI-powered systems, the need for people who understand how to secure them grows right alongside it. That's the intersection I've chosen to build my path around: an AI Engineer who never stopped thinking like a security researcher. And the earlier you start thinking about both, the more prepared you'll be for what's coming.
Comments
Post a Comment