Resume Critique
-
Under "Network Engineer"...
Nothing in the description is even close to being either in networking, or engineering. It's wrong on both axis. This heading alone would cause me to bin a resume that I saw like this. Make sure the role name matches the workload, at least within reason. The tasks listed are admin / support side, not eng / design side. And they are desktop and infrastructure, not network.
These two parts you need to consider mentioning at all:
"Provided Helpdesk support via phone and email, created and completed tickets.
Manage projects to improve client support and customer service."If you want to mention the helpdesk aspect, then merge that into the short, original description line. But I see no need to bring it up. The second part is project management and not part of IT at all. Unless you want to focus on moving over to PM instead of IT, I'd not point out that you were spending time involved in other things that makes it appear that while IT was your focus, it wasn't full time. This suggests, since it was big enough to be on your resume description, that a minimum of 10% of your time wasn't in IT at this job; but rather just processing paperwork and files TPS reports.
-
Fix this... "Systems Administrator
With over 10 years’ experience, strong technical ability, problem solving and customer service skills"First, nothing in your history supports System Administrator, it's not a role you've ever held, nor do you have any accreditation behind it, like certs. It's fine as a goal, but why label yourself as something (that's not normal to do to begin with) so specific, that you specifically have not done?
Second, the description is too long and big, you can trim it to better effect: "10+ Years of Strong Technical Ability, Problem Solving, and Customer Service"
Just dropping extra words keeps it to one line, and faster to read.
-
Skills: Cloud Technologies...
None of those are cloud. Office 365 and G Suite are just applications that you use, yes they are hosted and they may or may not use cloud under the hood, but their use of cloud tech (if they do so) isn't applicable to you, you aren't using or managing it. You are just using a website.
Saying you used cloud there would be similar to say that I ate an apple today, and that apple was picked by a farmer using a tractor, so I have skills in tractor management. I don't actually know that a tractor was used, it is only a guess. But whether it was or not, my benefiting from the farmer using a tractor doesn't mean I've gained skills in doing so.
And Nextcloud is just a normal application, it is not related to cloud in any way. It's not related to cloud computing, nor is it "over the Internet", it's just an application like anything else.
-
I know you have cloud computing experience in using public clouds, I'm surprised that none of that has been mentioned.
-
Designed, deployed, and maintained networks in the United States, Canada, and Mexico.
Administered hosts, servers, laptops, printers, switches, phones, smartphones.
Deployed software updates, security patches and firmware upgrades.
Designed, deployed, and maintained backups and replication using Veeam Backup & Replication
I think that we can tighten this up a lot...
Designed and administered complete networks in the US, Canada, and Mexico including core infrastructure and end user compute devices including security, patching, configuration, backup, and disaster recovery planning.
Half the length, 500% of the impact.
-
@scottalanmiller said in Resume Critique:
What are "lean on time IT services"? Whom did you lean on while doing it?
I'm assuming that this means something, but it sounds super funny when you see it on a resume. I can't figure out what work you did as a Field Tech, only that it was leaning on something.If you were just a cog in a company practising Lean, then I don't think you need to mention it on your resume.
If you were required to have a solid understanding of Lean (and have the ability to help a company use Lean), then maybe move it to something like a Skills section
-
Definitely drop the college part if you don't have a degree. There is no value by saying you took some college classes.
-
The wording in general is very confusing. I feel like you are stretching for space. Concentrate on relevant skills. The points mentioned are repetitive, long, and boring. They also don't really describe what you did very well. I know you've worked on some cool projects. Why not describe the best of what you do.
-
@irj said in Resume Critique:
Definitely drop the college part if you don't have a degree. There is no value by saying you took some college classes.
Especially as nearly every high school kid gets college classes as part of high school today. My sixteen year old nieces all have college classes already.
-
@black3dynamite Thanks for your feedback! I have removed that job completely
-
@aaronstuder said in Resume Critique:
@black3dynamite Thanks for your feedback! I have removed that job completely
Why remove it, it added depth?
-
@kelly Thanks for your feedback! When you say bland what do you mean? Should I try a different format? Font? Layout?
I have removed all but the last 3 jobs, they make up the majority of my experience anyways
I'll work on wording, and providing more specific details.
-
@aaronstuder said in Resume Critique:
@kelly Thanks for your feedback! When you say bland what do you mean? Should I try a different format? Font? Layout?
I have removed all but the last 3 jobs, they make up the majority of my experience anyways
I'll work on wording, and providing more specific details.
I would caution against that. Your early jobs establish your timeline, and middle ones avoid gaps. It's rare that you want to remove a job in your field. I've been in IT 30 years (as of next year) and still have my first job in 1989 on there, because it shows when I started.
-
The only thing I would add is that if you are submitting your resume to someone that has a HR filter, you might want to word stuff like Point of Sale (POS) so that if they search for either search term, your resume gets a hit. A tech person knows all the server versions between Server 2016 and 2008R2, but a non tech that is told "we have Server 2012R2, so show me resumes that have experience with that" might miss your resume because it doesn't come up in the search...
-
@scottalanmiller Added the the jobs back in.
-
@kelly Good Points! I'll work on that
-
@scottalanmiller said in Resume Critique:
Under "Network Engineer"...
Nothing in the description is even close to being either in networking, or engineering. It's wrong on both axis. This heading alone would cause me to bin a resume that I saw like this. Make sure the role name matches the workload, at least within reason. The tasks listed are admin / support side, not eng / design side. And they are desktop and infrastructure, not network.
I understand what your saying, but what can I do about it? That is the title that was given me by the employer. Even if I could change it, what would I make it?
-
@aaronstuder said in Resume Critique:
@scottalanmiller said in Resume Critique:
Under "Network Engineer"...
Nothing in the description is even close to being either in networking, or engineering. It's wrong on both axis. This heading alone would cause me to bin a resume that I saw like this. Make sure the role name matches the workload, at least within reason. The tasks listed are admin / support side, not eng / design side. And they are desktop and infrastructure, not network.
I understand what your saying, but what can I do about it? That is the title that was given me by the employer. Even if I could change it, what would I make it?
I'm not sure that I follow. You never put your title on a resume, you put your role. Your role is not network engineer, not even slightly. What they called you is not applicable to a resume, ever. They could call you "Bob the Tech Janitor" and you still just put your role on a resume.
You always put what you actually were, nothing else. Anything else is lying. Even if they called you a Network Engineer, since you weren't one, putting what they called you is a total fabrication. It looks like you were a normal generalist, so any normal generalist title will do.
-
@aaronstuder said in Resume Critique:
@scottalanmiller Added the the jobs back in.
The one time you might take jobs out is if they are overlapping (two jobs at once) and one is not impressive enough to bother including.
Like you are a Senior IT Engineer my day, but moonlight doing L1 helpdesk for extra scratch. Don't tell anyone about the moonlighting.
-
@scottalanmiller said in Resume Critique:
It looks like you were a normal generalist, so any normal generalist title will do.
It was a MSP,. I went on site to customer's site and completed tasks as needed. Everything from helpdesk to complete network setups. How would you describe this role?
