Resume Update
-
@EddieJennings said in Resume Update:
@scottalanmiller said in Resume Update:
I feel it is weird that you list Windows versions, but not other versions.
I debate listing versions. Upon thinking about it, at least in the Windows world, versions don't really matter. Let's say I'm 100% n00b and green and only had Server 2019 in my lab. If I had a job with non-current Windows server, I could find my way around. Also, further thinking about it, it seems doubtful that hiring managers are really looking for a specialist in non-current versions of Windows server -- or if they are, the question becomes "why are you having to hang on to these legacy systems? Does your company have a plan for migrating to current?"
I am curious about the Linux side of the world, but I suppose the same idea applies. If all of my experience has been with CentOS 7 and 8, I could probably function if I was in an environment with 6.x, though there would be some learning involved.
I used to list versions, and now I don't. But if you list them, list them all.
-
New draft coming tomorrow evening. Still have a few more tweaks to do before I present a second draft.
-
@Dashrender said in Resume Update:
@EddieJennings said in Resume Update:
y around. Also, further thinking about it, it seems doubtful that hiring managers are really looking for a specialist in non-
oh - what a wonderful world you and Scott live in
Ha! Unless there's some kind of position where the main project is to move off of some legacy OS, I'd be wary of a position advertising "Need Windows Server 2012 R2 specialist"
-
@Dashrender said in Resume Update:
@EddieJennings said in Resume Update:
y around. Also, further thinking about it, it seems doubtful that hiring managers are really looking for a specialist in non-
oh - what a wonderful world you and Scott live in
Do I need to remind you that employment is a choice?
@EddieJennings is making a valid argument that he doesnt want to work for someone like that.
Also, if your potential employer turns out to be bad, you can leave. This isn't India where you are bound to your employer until they release you. You can leave anytime and work for anyone else.
-
Yeah I agree with @scottalanmiller This promotion does not look much like a promotion.
I would maybe call one
IT System Administratorand the otherIT System Administrator III understand these arent your official titles, but you need to do something to show an actual promotion, because otherwise its just too confusing.
Remember, they dont call your company to verify until after you sign the offer. Put whatever title you want as long as it accurately reflects your responsibilities. Verification is done after hiring, and 99% chance they wont care since they have interviewed you and know your actual skills. If it ever comes up (it wont), you just tell them that is how you showed your promotion on your resume. The official titles made it difficult. That is a perfectly reasonable explanation that anyone would understand.
-
I think you should skip versions completely. It's just too much detail and if you have been doing it long enough it looks ridiculous.
For example, experience with Windows 2.03, 3.0, 3.1, WFW 3.11, NT3.1, 95, NT3.5, 98, NT4, Me, 2000, XP, 2003, 2008, 7, 2012, 8, 2016, 10, 2019. Probably missed a few.
-
@EddieJennings said in Resume Update:
This gets to the issue of a functional title contrasted against a employer-given title.
Always use true (functional) not fake (given) title. Never repeat a lie, it's still lying when you know it isn't true. And don't repeat gibberish as if you accept it. Given titles are of no relevance as they are meaningless. If you ever use them, you need to make a point of pointing out that you are just repeating a title.
Absolutely no one hiring you has ever wanted to know the given title, only your role and responsibilities.
-
@Pete-S said in Resume Update:
I think you should skip versions completely. It's just too much detail and if you have been doing it long enough it looks ridiculous.
For example, experience with Windows 2.03, 3.0, 3.1, WFW 3.11, NT3.1, 95, NT3.5, 98, NT4, Me, 2000, XP, 2003, 2008, 7, 2012, 8, 2016, 10, 2019. Probably missed a few.
I think that I agree with this. The only reason that I hesitate is because someone with all Windows since NT4 has a much bigger scope than someone who has only seen 2019.
-
@scottalanmiller said in Resume Update:
@Pete-S said in Resume Update:
I think you should skip versions completely. It's just too much detail and if you have been doing it long enough it looks ridiculous.
For example, experience with Windows 2.03, 3.0, 3.1, WFW 3.11, NT3.1, 95, NT3.5, 98, NT4, Me, 2000, XP, 2003, 2008, 7, 2012, 8, 2016, 10, 2019. Probably missed a few.
I think that I agree with this. The only reason that I hesitate is because someone with all Windows since NT4 has a much bigger scope than someone who has only seen 2019.
That's one reason why I like something along the lines of "Windows Server 2003 - 2019" or perhaps "Windows Server 2003 - Current."
-
@EddieJennings said in Resume Update:
@Dashrender said in Resume Update:
@EddieJennings said in Resume Update:
y around. Also, further thinking about it, it seems doubtful that hiring managers are really looking for a specialist in non-
oh - what a wonderful world you and Scott live in
Ha! Unless there's some kind of position where the main project is to move off of some legacy OS, I'd be wary of a position advertising "Need Windows Server 2012 R2 specialist"
Definitely. Although 2012 R2 is only six years old and loads of places need to support it till they update. I'd be wary, but the big gap is between 2012 and 2012 R2.
-
@EddieJennings said in Resume Update:
This was another piece with which I struggled, and I think I just needed to get this on paper so I can see it, think it through, and re-write into something better. I agree this ought to be listed as a "Side Project" kind of thing. In addition, I can make mention of the lab, which would seem to be less odd.
The few times I make purchases for the lab, I expense that to the LLC, since the function of the lab is to improve my skills to use in the projects I do as the LLC (and to better me as an IT Professional) -- this point though, is likely worthy of a thread all of its own.Yes. Having a lab is a huge deal and a great idea to have on your resume. You likely want to talk about it even more. But just not as if it was a job. It's a personal growth lab, which is perfect, it just has to be presented as such.
-
@EddieJennings said in Resume Update:
@scottalanmiller said in Resume Update:
@Pete-S said in Resume Update:
I think you should skip versions completely. It's just too much detail and if you have been doing it long enough it looks ridiculous.
For example, experience with Windows 2.03, 3.0, 3.1, WFW 3.11, NT3.1, 95, NT3.5, 98, NT4, Me, 2000, XP, 2003, 2008, 7, 2012, 8, 2016, 10, 2019. Probably missed a few.
I think that I agree with this. The only reason that I hesitate is because someone with all Windows since NT4 has a much bigger scope than someone who has only seen 2019.
That's one reason why I like something along the lines of "Windows Server 2003 - 2019" or perhaps "Windows Server 2003 - Current."
You could also put years. 10+ years experience Windows Server.
It's more common to find "years of experience" than have use version X in job ads.
-
@Pete-S said in Resume Update:
You could also put years. 10+ years experience Windows Server.
It's more common to find "years of experience" than have use version X in job ads.
I'm in a situation where I don't have 10+ years of experience with Windows Server, but I've had to support 2003 to current.
-
Here is draft 2. For this draft there are still a few things that I know needs some editing.
First are my "Skills used" line. In both of my IT positions, especially the latter, I've had the opportunity to touch several technologies. My goal is to show this variety, yet balance the annoyance of reading a long list of things. Another thing that seems odd is listing something like "Windows Server" as a skill. Windows Server is a product, so the skill would be what you do with the product (deploy, configure, troubleshoot) -- perhaps I'm discovering my answer as I type this
Looks like a third draft will be coming soon.Second is my current company. Several months ago (perhaps a year ago), On High created PruittHealth Connect, Inc., which from what I understand contains basically all of what was IT within PruittHealth. So technically during my span of two and a half years, I've worked for two distinct companies.
The question becomes how to articulate this on the resume. I chose listing it as is because my paychecks come from PruittHealth Connect; however, its not possible for me to have worked for my entire time with PruittHealth Connect, since it didn't exist when I started with Pruitt Health.
-
@EddieJennings said in Resume Update:
Here is draft 2. For this draft there are still a few things that I know needs some editing.
First are my "Skills used" line. In both of my IT positions, especially the latter, I've had the opportunity to touch several technologies. My goal is to show this variety, yet balance the annoyance of reading a long list of things. Another thing that seems odd is listing something like "Windows Server" as a skill. Windows Server is a product, so the skill would be what you do with the product (deploy, configure, troubleshoot) -- perhaps I'm discovering my answer as I type this
Looks like a third draft will be coming soon.Second is my current company. Several months ago (perhaps a year ago), On High created PruittHealth Connect, Inc., which from what I understand contains basically all of what was IT within PruittHealth. So technically during my span of two and a half years, I've worked for two distinct companies.
The question becomes how to articulate this on the resume. I chose listing it as is because my paychecks come from PruittHealth Connect; however, its not possible for me to have worked for my entire time with PruittHealth Connect, since it didn't exist when I started with Pruitt Health.
This revision looks a lot better. IMHO skip the month thing. Who cares what month you got what certificate or graduated. Same with your work experience. Who cares if you started i January or June? Just write the year. Quick glance shows you have 7 years of work experience in IT. Does it really matter if it turns out that it is actually 7.3 years or perhaps only 6.6 years?
Same thing with the company. Keep it like it is.
-
System Administrator II (September 2019 – Present)
System Administrator I(February 2018 – September 2019)I still don't like this. These are still not your role, they are clearly meaningless titles. They have no purpose as they have no meaning. So they are filler. The only acceptable thing here would be "system administrator" if that's the job you did. Having a number after it means absolutely, 100% nothing. Listing two lines with two numbers also means nothing. It doesn't even tell us if you were promoted, demoted, or just a title change.
Put yourself in the shoes of someone else reading this... they cannot glean anything from this. So why is it there?
-
Rebuilt System Center Configuration Manager testing environment
I would not list this. Remember, don't list mundane or trivial things. Not only does it come across as filler, but it implies that you perceive this as important and trivializes other parts of your resume.
-
@EddieJennings It's ntg.co not ntg.com
-
@scottalanmiller said in Resume Update:
@EddieJennings It's ntg.co not ntg.com
Yep. Missed an auto-correct.
-
@Pete-S said in Resume Update:
This revision looks a lot better. IMHO skip the month thing.
Overall yeah, way better. I generally agree about the month thing, but I like when it shows that there is or isn't an employment gap. But that's not a big deal with how few leaps are here. But I'd definitely remove it for anything else.
