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?
-
@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.
-
@coliver said in Resume Critique:
@scottalanmiller said in Resume Critique:
first job in 1989
I always forget how old most of you are.
Get off my lawn.
-
@coliver said in Resume Critique:
@scottalanmiller said in Resume Critique:
first job in 1989
I always forget how old most of you are.
I'm 33. The late end of a young person. What age can I start calling myself middle aged?
-
@wirestyle22 said in Resume Critique:
@coliver said in Resume Critique:
@scottalanmiller said in Resume Critique:
first job in 1989
I always forget how old most of you are.
I'm 33. The late end of a young person. What age can I start calling myself middle aged?
38 I believe is the average middle age.
-
58, while not exactly in the twilight years is certainly at the dinner table.
I thought that age was just a number.
-
@coliver said in Resume Critique:
@wirestyle22 said in Resume Critique:
@coliver said in Resume Critique:
@scottalanmiller said in Resume Critique:
first job in 1989
I always forget how old most of you are.
I'm 33. The late end of a young person. What age can I start calling myself middle aged?
38 I believe is the average middle age.
Whew. That's longer than I thought I had
-
@coliver said in Resume Critique:
@scottalanmiller said in Resume Critique:
first job in 1989
I always forget how old most of you are.
Ya I was 2 at that time.
-
@stacksofplates said in Resume Critique:
@coliver said in Resume Critique:
@scottalanmiller said in Resume Critique:
first job in 1989
I always forget how old most of you are.
Ya I was 2 at that time.
Haha that would have been the year I was born.
-
Y'all can just shut up now.. I was in 10th Grade.
-
@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.
The blandness of it was from the text, not the visuals. As a hiring manager layouts never made much difference except if they were terrible.
-
@scottalanmiller said in Resume Critique:
@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.
I'm not sure that is true. If a potential employer calls your current/previous employer they will provide the listed title when asking for verification of employment. If it doesn't match the one you have on record you will seem like more of a liar in that case.
-
@kelly said in Resume Critique:
@scottalanmiller said in Resume Critique:
@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.
I'm not sure that is true. If a potential employer calls your current/previous employer they will provide the listed title when asking for verification of employment. If it doesn't match the one you have on record you will seem like more of a liar in that case.
No, it does not. Because your former employer is legally bound not to lie about you. If they claim you did a job that you did not do, you can sue them. If they give a false title to do so, you can still sue them.
There is only one truth, you can only be a liar if you don't tell the truth but tell something else instead.
Companies are free to make up any title they want, but they cannot lie about the job you did. If the company trying to hire you calls and asks what your title was, rather than what you did, then they are idiots beyond belief and only hurting themselves for no reason. But in the real world, has anyone ever had an employer call and ask for a title and not care about the job that was done? I do these interviews on the employer side all of the time, and never once has someone asked me a title.
-
@scottalanmiller said in Resume Critique:
@kelly said in Resume Critique:
@scottalanmiller said in Resume Critique:
@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.
I'm not sure that is true. If a potential employer calls your current/previous employer they will provide the listed title when asking for verification of employment. If it doesn't match the one you have on record you will seem like more of a liar in that case.
No, it does not. Because your former employer is legally bound not to lie about you. If they claim you did a job that you did not do, you can sue them. If they give a false title to do so, you can still sue them.
There is only one truth, you can only be a liar if you don't tell the truth but tell something else instead.
Companies are free to make up any title they want, but they cannot lie about the job you did. If the company trying to hire you calls and asks what your title was, rather than what you did, then they are idiots beyond belief and only hurting themselves for no reason. But in the real world, has anyone ever had an employer call and ask for a title and not care about the job that was done? I do these interviews on the employer side all of the time, and never once has someone asked me a title.
Employment verification has nothing to do with the work you did. It is a communication between HR people verifying that the information on your resume reflects the records of the other company. For example, "Was Kelly employed by your company as an IT Manager (title) from <date> to <date>?" At this stage they do not care about the work that you actually did. This is simply a verification of employment and the title applied. If, however, there is a discrepancy between the title provided on the resume and the records of the prior company then there will be a loss of trust.
