I’ll give you my thoughts as someone who’s sat in as part of the tech interview portion. And I don’t want what’s below to discourage you as you are seeking that internship which will be great to add and really fill that thing out. An internship should grant you a lot of leniency during the interviews. But I’ll give you my thoughts ignoring that fact, more like what you’d expect once you’re done with the internship and your resume was sent to me for consideration.
What is it you want to do in IT? Generally, I’d say you want to sort of customize the resume to highlight what they might be looking for. For example, for your windows domain section, you list Active Directory and Powershell. Did you add to anything? Create anything? Because if your powershell is just ‘Get-ADUser’ that’s not all that impressive. Writing a script that manages something in AD is. If you can apply something like that and sort of pull out “deployed multiple users” and “updated a GPO”… because both of those things as worded is BAU. It would be weird if you listed “Deployed multiple user accounts in all the wrong OU’s”. You say in their appropriate OUs… how was that determined? What was special for the website, what did it do, what was it’s purpose? You list it but there’s no details so I’d be left to assume you wrote a “Hello World” basic HTML with <html><body><h1>Hello World</h1>… with CSS changing the background to a solid color. What exactly did the bash script do? Why a script and not just a shell command?
You will absolutely need to be ready to fully explain any of these. How did an ArrayList determine the difficulty? (For example). How did you organize the OUs and GPOs? How did you manage the AD server? What was your DR plan and how did you test it? How did you set up the firewall and what authentication was in place for SSH? Were your linux machines on the domain or just the windows machines?
I also see nothing about git or other version control system and that would immediately concern me. You list a few tools (ufw, cron, cerbot) but nothing like VSCode or IntelliJ, GitLab or GitHub. Or whatever tools you used. But again, add/remove things from your resume that best fit the roll you’re applying too. If it’s more programming, stress that more and the administration less (but don’t completely remove it, just work on emphasis). Was any of this a capstone project? Did you participate in any competitions (like Business Professionals of America… but Canadian) or really any competitions? What sets you apart from your classmates for a position at any company (internship or full employment). Also, this might be hit or miss with people, but it might be worth considering dropping the fast food all together from this and add an object about what your seeking from an internship. If asked about no experience, you can just say you have no prior relevant working experience in IT and that’s what your looking to gain from the internship. Because most managers I’ve worked with, would just look right past it since it has none of the keywords they’re looking for and I as the technical person, simply don’t care.
Right now, you have no real world experience with this, just a bit of homework. Highlight what the purpose was of these sections, looping back, what was the purpose of the web site? What did the SSH have to do with the website that you set up HTTPS on? What were you backing up and why? Speaking just for internship, you may want to highlight your certs first and not your irrelevant fast food experience.
Anywho, hope this helps. Getting that first foot in the door can be difficult, but once in and you start networking (not the technical kind, the interpersonal kind) it gets a lot easier. And as a tip, when you first get in a place, that’s the single best time to shine as that’ll propel your career. I don’t mean like do a bunch of free work. But I’ve seen people lose their jobs because they would party every night and then give low effort (or sleep) on the job. Play video games, at the job… taking an absolute excessive amount of smoke breaks (where any given hour they’re at their desk for 15ish minutes)… or do the absolute bare minimum. Express interest in projects (if you actually are), be honest, deliver a product you’d want if you were the customer.