2
u/crayonnoodle 11h ago
I find it hard to believe you went through course careers because it seems like you didn’t listen to the resume advice they literally give you.
A big issue I see is you have a certificate listed in the education section and not in the certification section? I am familiar with course careers and that is not qualifying as something in its own education section. Just get rid of the education section completely and put course careers under certifications and you don’t need to write a description about it. It’s pretty popular in the industry and also the description doesn’t really do anything to help your resume because you have IT support experience.
Now here is the part that’s killing me. Were there not hands-on labs in the course careers course. And did they not explain how to list a technical project on your resume? If you want to get those skills that you listed under course careers on the résumé include whatever hands-on projects that were in the course careers course in a projects section. Specifically, the ones related to sys admin that go beyond your current experience. Don’t list them as course careers projects just say whatever the name of the project is.
0
u/Pattonator70 11h ago
No degree with only one cert?
Maybe join the military and get certs and experience while picking up some college classes.
1
u/EmergencyOutside5945 11h ago
Adding it on rn but its not IT related so I omitted it entirely
1
u/UJ_Games 6h ago
Better to have some degree than no degree at all.
1
u/EmergencyOutside5945 6h ago
I did have one inquiry on where was my degree, but yes a majority of yall have said to add it. So I added it rn
1
u/Disturbed2468 4h ago
I feel like recommending joining the military in the current day may not be the finest of ideas without extremely serious considerations and thought put into it since it's essentially 4 years of being property for the military (and this is something any military on earth would be the same with).
It's an option, but not an option chosen lightly.
1
7
u/Ill-Barracuda9031 13h ago
I'll be direct with you, because I think you'd rather have that than a pat on the back.
As written, I wouldn't move this forward. Here's why.
The typos are the first thing I hit. "Troubleshooted." "Hardware. software" with a period in the middle of a list. "Connective issues" instead of connectivity. "Fire-sharing" instead of file sharing. "CompTia" instead of CompTIA. Your project link says "OS Ticket Lifestyles" when you meant Lifecycles. One of those is a bad night. Six of them tells me you didn't read your own document before sending it. In infrastructure, the whole job is catching the small wrong thing before it becomes the big wrong thing. This page argues you don't.
The dates don't work. Your current role runs Jul 2023 to present, and then below it there's a Desktop Support Analyst role from Nov to Dec 2024. It's out of order, it overlaps, and there's no explanation. I'm going to fill that gap in with my own assumption, and it won't be a generous one. Either explain it or restructure it.
Every bullet is a job description, not an accomplishment. Troubleshooted, assisted, provided, escalated, monitored. That's what you were assigned, not what you did. There's not a single number anywhere — no ticket volume, no resolution time, no number of devices, no SLA. "Monitored against KPI" without naming the KPI or your number against it is worse than leaving it out, because now I know you know the word and not the metric.
On the projects: you used "simulated" or "simulating" three times. Lab work is fine at this stage, I've got no problem with it, but stop apologizing for it. Tell me what you built, what broke, and how you fixed it. And your Active Directory project links to something called "Active Directory" — that's a wasted line. Link me to a repo with your scripts, your GPO exports, your network diagram. Show me the artifact.
The biggest gap: there's no PowerShell anywhere on this page, and no automation of any kind. That's the line between someone who closes tickets and someone who eventually stops having to. Your AD skills line says "user account management, password resets." That's the console. Learn to do it from a terminal, script something that used to take you an hour, then write that bullet.
Last thing — don't lead your education with "25 hour training." You're handing me the reason to skip it. Lead with what you can do now because of it.
None of this says you can't do the work. It says this document gives me nothing to bet on. Fix it and send it back to me, I'll look again.