Resume
-
-
@WrCombs hardware is ONE word, not two.
-
Drop the prior experience bit.
-
-
-
@WrCombs Didn't you spend the better part of a week troubleshooting a WiFi related printing issue?
I don't like that first real line there "Responsibilities Include; Remote System Administration,. . . ." it's a bit to wordy and is poorly grouped together.
Take a look at the example I posted.
-
@DustinB3403 said in Resume:
@WrCombs Didn't you spend the better part of a week troubleshooting a WiFi related printing issue?
I don't like that first real line there "Responsibilities Include; Remote System Administration,. . . ." it's a bit to wordy and is poorly grouped together.
Take a look at the example I posted.
Must be missing something.
Cause it look Similar. -
@DustinB3403 said in Resume:
@WrCombs Didn't you spend the better part of a week troubleshooting a WiFi related printing issue?
I've done a lot of things that are all summed up Hardware maintenance, problem resolution .
-
-
I almost feel like I should read this from the end to the beginning.
you can read backwards ? that's a skill I haven't possessed yet.
-
Thinking I'm going to take the "Technologies Used . . . " part out of the work experience. It's redundant since it's 2 places at once.
-
I'm going to Start over. Build one from Scratch.
-
I almost feel like I should read this from the end to the beginning.
you can read backwards ? that's a skill I haven't possessed yet.
What I am saying is that maybe you can create an area called Qualifications or something and talk about your projects and training first. It would be different than how I have mine setup below, but maybe the same idea. Where you steer the resume reader before you list your job experience
-
Drop High School section. Nobody cares about that. Its assumed if no education is listed you have a HS diploma
Absolutely. Never advertise something no legit hiring manager would care about. It's fine to not have a college degree, but don't like make a whole section to point it out, lol.
-
@Dashrender said in Resume:
@DustinB3403 said in Resume:
Part Time Clerk
This section isn't relevant to what you're applying for, I would almost drop the entire section and simply replace it with something along the lines of "Prior work experience is not in my target field. Will answer questions if requested about it"
This is a good point.
You're also young enough that only having the single job being listed likely isn't going to be an issue.
This is the bigger factor, if other experience is really good (manager, engineer, teacher) then yo u list it to show overall experience. If it is clerking part time, people know that you have to pay the bills before you enter your field and don't care to read about it. Err on the side of lean.
-
@Dashrender said in Resume:
More like this
That's how Curtis would write it, jajajaja.
(Note, Curtis from another community, not from here.)
-
@Dashrender said in Resume:
More like this
So he does system support
I am sure he has touched windows server before on the job
I am sure he has worked with backups, even if its just using a SaaS solution
Also if he is using VPN to connect to remote sights then he is managing the connection in a sense
Remember, he's 23. No one expects him to be like Tim Berners-Lee.
Well, but at 23 some of us were a decade into our careers and already into senior roles. I got my first director position (100+ reports, including other directors) at 23. It's a tough age because some people are just starting, others are pretty far along, depending on where they started. @valentina was GM, a director-like position at 22, for example.
So in some ways, you have to say that the expectations are low based on age, but you also have to consider that he could have loads of experience by that age, too.
-
@Dashrender said in Resume:
Not very likely - the sell windows 10 as a server solution (likely illegally)
It's legal to sell it. It's illegal to deploy it. The "illegal" is on the customer, not on the vendor. The shady is on the vendor.
-
@DustinB3403 said in Resume:
@WrCombs Didn't you spend the better part of a week troubleshooting a WiFi related printing issue?
I've done a lot of things that are all summed up Hardware maintenance, problem resolution .
Break these out into projects rather than the basic things they are if it'll better explain the experience you gained from them.
-
Example
Client project required in depth network troubleshooting to resolve a critical point of sale issue, final issue was dead router, resolution required setup of new network stack.
Something like that is better than "it died and needed to be replaced"
