Who I Am
I got into IT because I wanted more than what I saw ahead of me as a production chef. I loved my work, but I wanted a career where I'd keep learning and solving problems instead of hitting a ceiling on where my interests could actually take me. Tech had already been my hobby for years at that point I'd been messing with desktop Linux and building my own computers since I was 13, long before I thought of pursuing IT as a career. My first attempt at making the jump was web development: I enrolled in a full-stack bootcamp through Ohio State's College of Engineering and ended up failing out of it. That taught me a rather expensive lesson; the zero to hero approach is not sustainable, nor would it have actually set me up for success in my future career. Not only did my approach to learning need to change, but my starting point in tech needed to change as well. I was better suited to the systems and infrastructure underneath the applications than to building the applications themselves. So I pivoted to traditional IT infrastructure and started building on the years of hands-on computer knowledge I already had.
From there it was mostly self-taught. I studied for the CompTIA A+ on my own, then did instructor-led Network+ training through CompTIA Tech, which gave me a real foundation in hardware, OS, networking, and troubleshooting. That eventually got me into AWS through their Work-Based Learning program on the Data Center Operations team. What was meant to be a foot in the door quickly turned into a real stretch of growth. I converted from the WBLP program into a full-time role on that team, being put on as the on-shift technician for multiple machine learning data centers within two months of my conversion date. After developing and conducting instructor-lead training for an HPC server platform, I was promoted within my role to a level 3 DCO technician. After some time I was transferred to the deployment team building out new data centers when I floated some interest in the position. I had a busy year, re-vamping the team's new-hire technical training and delivering on 15 projects quickly and with high quality, earning another promotion.
Most recently I picked up the Security+ cert, partly to keep sharpening my own foundation and partly to better understand what the security teams I work with are actually doing. At the end of the day, it's the same curiosity that had me building computers at 13; I love figuring out how things work, why they break, and what to learn next.