- Jan 21, 2005
- 6,023
- 0
- 0
Originally posted by: Tizyler
I feel like im not telling much about myself in the summary section. I've been using computers my whole life... I've been building computers since I was like 13. I have been doing networking for like 6 years, and I've used every piece of software under the sun.
How do I convey that to them?
I'm in a pretty good position to judge this as I am a senior network engineer/manager and I have evaluated resumes and been directly involved in hiring networking candidates. That being said, all of this is of course my opinion and the people at the companies you are applying for may feel differently.Originally posted by: Tizyler
I feel like im not telling much about myself in the summary section. I've been using computers my whole life... I've been building computers since I was like 13. I have been doing networking for like 6 years, and I've used every piece of software under the sun.
How do I convey that to them?
I completely disagree with this. While knowing how to build a PC won't directly help you configure IOS, there are certain core skills involving hardware and troubleshooting that underlie just about every type of computing platform. Need to upgrade router memory? Pretty much identical to the same operation on a PC. Troubleshooting is all about systematically exploring/testing likely causes, and someone who knows how to troubleshoot PC issues well is likely to carry a good troubleshooting methodology into other areas. All else being equal, I'd much rather have an entry level network engineer who has gotten his/her "hands dirty" in a PC rather than one with only theoretical knowledge of hardware.Originally posted by: Elbryn
in my opinion the past computer hardware stuff doesnt really apply to a network engineer. its not that applicable to say you can seat a cpu or troubleshoot a bad disk drive when the job you want is comprised of configuring routers from a telnet session.
Originally posted by: Pheran
I'm in a pretty good position to judge this as I am a senior network engineer/manager and I have evaluated resumes and been directly involved in hiring networking candidates. That being said, all of this is of course my opinion and the people at the companies you are applying for may feel differently.Originally posted by: Tizyler
I feel like im not telling much about myself in the summary section. I've been using computers my whole life... I've been building computers since I was like 13. I have been doing networking for like 6 years, and I've used every piece of software under the sun.
How do I convey that to them?
First, what the heck is SQA? I'm guessing the QA part stands for quality assurance, but I have no idea about the S. Don't assume that other organizations know what acronyms from your company mean. Ditto for PBT - I'm guessing that means Provider Backbone Transport but I had to Google it.
You've only been in your current position for ~10 months and the previous one lasted only 5 months. This is going to raise some red flags, so be prepared to talk about it. Employers assume that it will take you months to get fully up to speed in a technical position - someone who leaves in a year is not worth investing the time in.
If you actually have a degree, you need to modify your education section to state what it is (e.g. BS, associate, etc.), but if you didn't finish one it's OK as is. As it stands, this resume means to me that you do not have one.
Honestly, I don't care about your volunteer experience.
You're right that your resume fails to convey pre-job experience. Without really knowing what you've done, I can't tell you what to put on there. Something like "Built PCs from component parts" is one possibility or "Years of experience building PC hardware".
Good luck in your job search.
I don't know if this is the norm anymore. I think 2 pages is now, but that obviously depends on how much experience you have. I just applied for a job where the VP asked me to make mine as long as possible because the President loves seeing all experiences.Originally posted by: hopeless74
keeping it to one page is good