Resume Critique
-
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?
-
@aaronstuder said in Resume Critique:
@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?
It sounds like you did a little bit of everything for the majority percentage of your time, so IT Generalist or IT Practitioner... maybe there is something better.
-
@aaronstuder said in Resume Critique:
@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?
Yup, in house or out sourced, the tasks are generalists and exactly what we'd expect in an SMB IT role. Nothing weird, so a general role name that reflects that. Loads of choices, and you can expose that you were external or not, up to you.
-
Think of it this way, a potential employer doesn't care about how you were paid (W2/1099/volunteer), they care about your experience and what you can do for them.
-
@scottalanmiller said in Resume Critique:
first job in 1989
I always forget how old most of you are.
