Resume Critique
-
I heard somewhere to put your title, then the role that actually applies in brackets beside it
-
@flaxking said in Resume Critique:
I heard somewhere to put your title, then the role that actually applies in brackets beside it
But thinking about that now... Is that kind of like calling your previous employer a liar in your resume?
-
@flaxking said in Resume Critique:
I heard somewhere to put your title, then the role that actually applies in brackets beside it
Doing both is fine, but I see no benefit to putting the title. Only makes for clutter and confusion.
-
@flaxking said in Resume Critique:
@flaxking said in Resume Critique:
I heard somewhere to put your title, then the role that actually applies in brackets beside it
But thinking about that now... Is that kind of like calling your previous employer a liar in your resume?
Yeah, which is likely not best to do. You want your resume to be clear and concise. It is the one thing that has to sell you out on its own without you there for explanation. It's job is to get your foot in the door, then in an interview you can talk about whatever you need.
-
@scottalanmiller said in Resume Critique:
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.
So if my role is IT Manager, should I put IT Manager, ever thought my boss technically has that title?
-
@aaronstuder said in Resume Critique:
@scottalanmiller said in Resume Critique:
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.
So if my role is IT Manager, should I put IT Manager, ever thought my boss technically has that title?
No because that is lying. You should describe your duties, without a falsified title.
-
@dustinb3403 That's what I thought, but @scottalanmiller seems to state otherwise.
-
It will be a lie if you say your title is something it's not. Your title is what your employer says it is. It doesn't have to match what you do, your duties.
You put your Employer and your title there. Then you can list your role if you want, and responsibilities.
-
@aaronstuder said in Resume Critique:
@dustinb3403 That's what I thought, but @scottalanmiller seems to state otherwise.
Yea. . . . but I wouldn't put CTO on my resume if it wasn't true, even if I was in charge of everything technology related for an org.
Put your titled as it is, and then state what you actually did.
"Systems Administrator"
- Managed a team of 5
- Updated Servers
- managed and developed BDR plan
But don't lie about it.
-
@aaronstuder said in Resume Critique:
@scottalanmiller said in Resume Critique:
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.
So if my role is IT Manager, should I put IT Manager, ever thought my boss technically has that title?
No, your TITLE is IT Manager, not your role. You do put your role, being the thing that you do. You only put a title if it matches your role (in which case it is still the role that you are putting), or if you clarify that it is a title and not actually what you did.
Example: Title "President of hte Universe", Role: janitor
-
@aaronstuder said in Resume Critique:
@dustinb3403 That's what I thought, but @scottalanmiller seems to state otherwise.
No, I'm crystal clear. You never lie. You always put what is honest.
-
@obsolesce said in Resume Critique:
You put your Employer and your title there. Then you can list your role if you want, and responsibilities.
No, resumes get rules, not titles. Putting a title on a resume as if it is a role is lying. There is no place on a resume for titles. That's not a thing.
-
@scottalanmiller Thanks for clarifying
-
@dustinb3403 said in Resume Critique:
@aaronstuder said in Resume Critique:
@dustinb3403 That's what I thought, but @scottalanmiller seems to state otherwise.
Yea. . . . but I wouldn't put CTO on my resume if it wasn't true, even if I was in charge of everything technology related for an org.
Put your titled as it is, and then state what you actually did.
"Systems Administrator"
- Managed a team of 5
- Updated Servers
- managed and developed BDR plan
But don't lie about it.
You HAVE to state that it is a false title if you want to put it there. Never put a false title and list responsibilities as if that makes the false title okay. If you feel compelled to list titles in addition to your role, then clarify that it is a title.
Role: System Admin
Title: Lord of the Universe
Responsibilities: "things that had been be system admin tasks" -
@scottalanmiller now I am more confused. lmao
-
If you list a title and then responsibilities that don't match it, this makes you either look dishonest, or far more likely, just confused. As if you didn't realize that your responsibilities didn't match the role.
If you put "System Admin", then list non-system admin tasks, it tells someone reading the resume that something is wrong - and that either you didn't catch it (which is a huge flag) or you knew and hoped they wouldn't catch it (also a big flag.)
-
@aaronstuder said in Resume Critique:
@scottalanmiller now I am more confused. lmao
Two rules:
- Always list roles, not titles.
- Always be honest.
That's it. So simple.
-
@scottalanmiller said in Resume Critique:
@dustinb3403 said in Resume Critique:
@aaronstuder said in Resume Critique:
@dustinb3403 That's what I thought, but @scottalanmiller seems to state otherwise.
Yea. . . . but I wouldn't put CTO on my resume if it wasn't true, even if I was in charge of everything technology related for an org.
Put your titled as it is, and then state what you actually did.
"Systems Administrator"
- Managed a team of 5
- Updated Servers
- managed and developed BDR plan
But don't lie about it.
You HAVE to state that it is a false title if you want to put it there. Never put a false title and list responsibilities as if that makes the false title okay. If you feel compelled to list titles in addition to your role, then clarify that it is a title.
Role: System Admin
Title: Lord of the Universe
Responsibilities: "things that had been be system admin tasks"But you are then left to identify the "role" where as 99.999% of jobs give a title, and then a random list of responsibilities. And if you are in NY, job descriptions that end with "duties as described" also means you could be doing janitorial one day, and electrical the next.
The title, even if worthless is an honest describer for the position you held. (even if it doesn't align with your role(s).)
-
@dustinb3403 said in Resume Critique:
@scottalanmiller said in Resume Critique:
@dustinb3403 said in Resume Critique:
@aaronstuder said in Resume Critique:
@dustinb3403 That's what I thought, but @scottalanmiller seems to state otherwise.
Yea. . . . but I wouldn't put CTO on my resume if it wasn't true, even if I was in charge of everything technology related for an org.
Put your titled as it is, and then state what you actually did.
"Systems Administrator"
- Managed a team of 5
- Updated Servers
- managed and developed BDR plan
But don't lie about it.
You HAVE to state that it is a false title if you want to put it there. Never put a false title and list responsibilities as if that makes the false title okay. If you feel compelled to list titles in addition to your role, then clarify that it is a title.
Role: System Admin
Title: Lord of the Universe
Responsibilities: "things that had been be system admin tasks"But you are then left to identify the "role" where as 99.999% of jobs give a title
You always have to identify your role. That's just part of writing a resume. Nearly all jobs give titles, and almost always they are fake.
-
@scottalanmiller said in Resume Critique:
@dustinb3403 said in Resume Critique:
@scottalanmiller said in Resume Critique:
@dustinb3403 said in Resume Critique:
@aaronstuder said in Resume Critique:
@dustinb3403 That's what I thought, but @scottalanmiller seems to state otherwise.
Yea. . . . but I wouldn't put CTO on my resume if it wasn't true, even if I was in charge of everything technology related for an org.
Put your titled as it is, and then state what you actually did.
"Systems Administrator"
- Managed a team of 5
- Updated Servers
- managed and developed BDR plan
But don't lie about it.
You HAVE to state that it is a false title if you want to put it there. Never put a false title and list responsibilities as if that makes the false title okay. If you feel compelled to list titles in addition to your role, then clarify that it is a title.
Role: System Admin
Title: Lord of the Universe
Responsibilities: "things that had been be system admin tasks"But you are then left to identify the "role" where as 99.999% of jobs give a title
You always have to identify your role. That's just part of writing a resume. Nearly all jobs give titles, and almost always they are fake.
This I haven't disagreed with.
