Resume Review
-
Tighten this up. More like...
- Admin for AD and GPO on Windows Server 2003 - 2012 R2 and CentOS mixed domain with ~270 workstations.
See if you can make that one line. Don't sell DNS and DHCP with AD and GPO. Different levels of complexity, don't try to brag about DHCP, it belittles the good stuff.
-
About a word too long to be a one liner. I will work on it.
Makes sense regarding DHCP and DNS.
Thinking about it, its incorrect for me to use GPO. I should be using GP. I made that change.
Any advantages/disadvantages to using/not using acronyms. ie.. AD vs Active Directory?
-
@unwiseapple said in Resume Review:
About a word too long to be a one liner. I will work on it.
Makes sense regarding DHCP and DNS.
Thinking about it, its incorrect for me to use GPO. I should be using GP. I made that change.
Any advantages/disadvantages to using/not using acronyms. ie.. AD vs Active Directory?
Yes, GP is better.
AD is short and very well known. I think that it is fine.
-
Sounds good.
Have a question regarding fonts, any in particular nicer on the eyes? I tend to use times new roman but wonder if there is something better.
-
Times New Roman and Georgia are pretty good.
-
Sounds good, I will probably stick to Times New Roman then. Size 12 is common correct?
Anyone else with any recommendations?
-
I think anything 10 - 12 is normal.
-
Yup, 12pt is good. Whatever gives you one full page without spilling over.
-
Recent changes:
To
To make it a one liner on Times New Roman Size 11.
Any recommendations on how to make the following a one liner?
I also have changed the heading with my name and info from 4 lines to 2 as it just seems like a lot of wasted space up top.
-
@unwiseapple said in Resume Review:
Recent changes:
To
To make it a one liner on Times New Roman Size 11.
Any recommendations on how to make the following a one liner?
I also have changed the heading with my name and info from 4 lines to 2 as it just seems like a lot of wasted space up top.
"Developed bash script that manages email to comply with document retention policy." That still gets the point across and would only be one line.
-
@stacksofplates Yup that works thanks!
@scottalanmiller Heres my attempt on making the following a one liner
To
I don't state the versions of CentOS, so why should i for Windows Server. Is there any value lost by removing the version numbers?
-
@unwiseapple said in Resume Review:
@stacksofplates Yup that works thanks!
@scottalanmiller Heres my attempt on making the following a one liner
To
I don't state the versions of CentOS, so why should i for Windows Server. Is there any value lost by removing the version numbers?
As long as you state the versions in your skill list, remove them here.
-
@scottalanmiller I do sate the version down below on my technology summary.
If anyone could help me shorten this, that would be fantastic. Im about 2ish words too long. Its currently just barely 3 lines and i would like it down to 2.
If i remove department and VMware it fits on two lines, but would love to hear some opinions.
-
@unwiseapple said in Resume Review:
@scottalanmiller I do sate the version down below on my technology summary.
If anyone could help me shorten this, that would be fantastic. Im about 2ish words too long. Its currently just barely 3 lines and i would like it down to 2.
If i remove department and VMware it fits on two lines, but would love to hear some opinions.
Is "virtualized" something that you want to include? It doesn't really take any effort to move existing tools into a VM. Is that worth noting on a resume? If you include ESXi in there at all, it will be implied. If even that is needed.
-
@StrongBad It expanded their ability to test the software because i introduced virtualization. They went from 6 or so physical machines to 100+ VM's. It helped find bugs in the software, duplicate client environments to debug issues reported by our clients and much more. This improved the quality of the product. So i do find it valuable to list, as no one before me thought to do so.
-
@unwiseapple said in Resume Review:
@StrongBad It expanded their ability to test the software because i introduced virtualization. They went from 6 or so physical machines to 100+ VM's. It helped find bugs in the software, duplicate client environments to debug issues reported by our clients and much more. This improved the quality of the product. So i do find it valuable to list, as no one before me thought to do so.
That's valuable "to the company" sure, but only because they were doing it poorly before. But is it something that reflects your value to the next company?
-
I would hope so, as others have looked at this for years and didn't think to virtualize it. It is a process that i directly greatly improved, among others in the company.
-
@unwiseapple said in Resume Review:
I would hope so, as others have looked at this for years and didn't think to virtualize it. It is a process that i directly greatly improved, among others in the company.
Based on the assumption that the next company will also not be aware that everything should be virtualized? I don't think that this conveys the value that you think that it does.
Let me see if I can make an analogy. It's like working at a trucking firm and you figure out that you can lengthen the lifespan of the engines in the trucks my replacing the oil filter regularly. You don't put that on your resume. It doesn't showcase your value, it just tells future employers how badly the last place you were, was. Not something that you want them to be aware of, because you want them to think that you excelled in a good, challenging environment. Not that you excelled by getting them up to a normal baseline. You want the last job to sound good, raise yourself up by raising them up, not be knocking them down.
