Current state
I separate completed, active, planned, private, and externally blocked work so a roadmap item never reads like a shipped feature.
A little context
I'm completing Ontario Tech University's Networking and IT Security degree, with graduation expected in April 2028. My work moves between configuring routed and switched networks, examining how security controls fail, and building software that makes technical evidence understandable to the person operating it.
I learn best by building and verifying. A Cisco lab makes a failed route observable through interface state, routing tables, packet captures, and end-to-end tests. A security application turns broad terms such as identity, authorization, integrity, replay protection, or recovery into decisions that have to survive malformed input and interrupted workflows.
I co-founded SSIK with my Ontario Tech classmate Ghayas Sher. We share its consulting, security, privacy, and stakeholder responsibilities, while I independently built its public website and private SSIK Intelligence V1 platform. I also handle Google Workspace, account continuity, website-team coordination, hosting, and deployment for a developing nonprofit while preparing for CompTIA Security+ and expanding a Proxmox home lab.
I am looking for co-op work where I can contribute to real infrastructure and learn from experienced operators. Network operations, security operations, systems administration, infrastructure security, and security-focused development all fit the direction of the work collected here.
I use this portfolio as an ongoing record rather than a polished snapshot that hides the process. Completed work includes measurements and verification; active work includes its present boundary and next step; private work explains architecture without exposing confidential material; and older projects stay useful when they show where a skill started.
That also means correcting the record when something changes. Product outcomes, project status, deployment links, limitations, and responsibilities should agree across the resume, room, AFFAN_OS, GitHub, and the long-form pages. I would rather describe a smaller verified result accurately than make a broad claim that I cannot explain in an interview.