"Technology evolves quickly. Responsibility does not."
I'm young. I didn't get here through a straight line, and I think that's actually the point.
Growing up, I bounced between three different worlds out of pure curiosity: medicine, engineering, and eventually technology. Nobody mapped that out for me. I just couldn't help wanting to understand how things worked and, more importantly, why they failed. That instinct never switched off.
What each field gave me was different. Medicine showed me that the gap between a system functioning and a system failing is almost always smaller than it looks from the outside. Engineering taught me to think in structures: what depends on what, what carries the load, what happens when one piece doesn't hold. When I found IT, both of those instincts finally had somewhere useful to go.
AI pulled me in first. I was fascinated by systems that could find patterns in data and make decisions faster than any human team. But I kept arriving at the same uncomfortable question: what happens when the pattern is wrong? Who catches it? Who's responsible? That question is what led me into security. Not as a pivot, but as the natural next step.
I don't just want to fix problems. I want to build systems where the problems are structurally harder to create in the first place.
I know I'm early. I'm not pretending otherwise. But with two years of hands-on experience, four active certifications, and a degree in information security underway, I'm building toward something deliberate: security architecture at the intersection of AI, risk, and human judgment.
NetRaptor is an active development project - a modular, offensive-security-grade network intelligence platform built from the ground up. The concept: a unified system that doesn't just observe a network, it understands it. Combines real-time scanning, packet-level analysis, threat correlation, and automated incident response into a single cohesive engine.
The architecture is designed around the idea that every tool should feed every other tool. Scanner output feeds the threat mapper. Log analysis informs the SIEM simulator. Incident response draws from everything. No siloed dashboards - one predator-instinct system.
Active practice on HackTheBox and TryHackMe. Every room documented - methodology, dead ends, and lessons, not just solutions.
Graded, documented, and deployed. Built across two programs - networking, embedded systems, security, and ITSM. Hover the card to see the network.
I'm open to full-time and hybrid roles in IT support, cybersecurity, and security operations. If you need someone who thinks in systems and stays in the room when things get hard, reach out.