Laid off - Resume advice for a Network Engineer?
Hey guys,
I know there's /r/'s specifically for resumes, etc. But I wanted a more focused opinion from people within specifically the network engineer/network security/etc world. I've updated my resume, but for some reason that I just can't put my finger on, it just feels... Wrong.
I know there's some management types that post/lurk on here, and I was really hoping to get some feedback/criticism on my resume.
So far it's a whopping 5+ pages, with over a page of just references, a good chunk of them senior people like directors, etc.
For instance, are hiring managers going to prefer something like what this post suggests: https://www.reddit.com/r/jobs/comments/7y8k6p/im_an_exrecruiter_for_some_of_the_top_companies/
Or something like this: My Current Resume
I feel like the whitespace on the left is too much.
The other thing I was reading is to put the "alphabet soup" at the top, but is that really something that hiring managers/etc are going to care about? I mean, if I put "Skills: BGP, OSPF, EIGRP..." is that something someone will actually want to see at the top?
Thanks!
Edit: Thanks for all the help. Just to clarify, the references section alone is 2ish pages, if I put it to "on request" we're down to more like 3 - still fat to be trimmed for sure. Definitely taking in the advice, and is very much appreciated. Keep it coming. :)
The alphabet soup - is that something people really want to see at the top? It's kind of frustrating in some ways that IT, especially highly specialized fields like mine are just a bunch of acronyms.
Edit 2: Got it down to one page finally after a few hours. I think I'm pretty happy with it too. If anyone wants to critique it more (I very much appreciate the criticism by the way), let me know and I'll re-sanitize it.
Thanks again to everyone who posted here, I love you guys.
Posted Jul 18, 2019, 8:15 PM UTC · edited
5 pages? Ouch... I've done plenty of hiring for network / security roles and honestly your resume gets about 15-30 seconds of quick scrolling and browsing to tell me if you're worth bringing in for an interview or not. 5 pages is WAY too long. 2 pages is ok, 1 is better as long as you aren't sacrificing necessary info to get past the idiotic word filter known as HR.
Should I just trim down the previous jobs to a few bullet points? I don't want to lose what I've done there, but I agree that this many pages is just way too much.
I've never submitted a resume that's longer than a single page (plus a cover letter of course). I'm one of those "less is more" type people and I think employers appreciate that.
100% this. Hiring people only look at that front / first page
For context: I’m the person you phone screen with / am the first person you interview with if your trying to join my team. I’m not a lead, just one of the members who’s been there the longest. My team is also for server administration
When I get a resume I read any skills you’ve decided to highlight and usually your current job summary. Maybe your second and third if it’s relevant. Most of my questions will be about your current job. I want to hear about what your doing now, cool technical projects, and I want to know you know what your talking about. I’ll pick something on your resume, ask you to explain it then question things based off your Answer. Your made a python script to help deploy switches? How’s it work? I don’t need exact commands but the basic structure. Then I’ll probably ask what you do when it fails / how you do error handling. Then I’ll ask some basic networking questions / server admin questions.
Five pages is way to long for a resume. I care about what you know but can you really talk in detail about what you were doing 10 years ago? Is it even relevant to the position your applying for? Unfortunately the resume is the way in and you need a bunch of buzzwords to wow HR, but do your best to do that with your current roles. My company is using today’s tech, I don’t care if you can configure RIP and frame relay.
Edit: this is not a direct response to you, but I am a big fan of the one page resume and this felt like it fit here.
Second edit: there’s two - three more pairs of interviewers that come after me. They will both understand if your BSing your tech but also are evaluating team fit / communication skills.
If less is more, imagine how much more, more is. - Fraiser Crane
I had a recruiter once tell me my CV was too short, to which I replied "but you called me" :) and eventually got offered the position :)
One page is all you need. Summarize only the most necessary ones and fit it into one page.
Mine is currently 2 pages and a little extra.
The first page is half technical skills and half for interesting projects. Technical skills being 5-10 bullets like "Extensive experience with campus LAN and WAN design". Interesting projects being 5-6 bullets like "Lead a team that reimaged over 1200 computers in 6 days following a virus outbreak at a large client with no usable pre-existing imaging infrastructure".
The second page is a more traditional job history with brief bullet points for responsibilities. The extra is side work, soft skills, hobbies, certifications, and references (depending).
I feel this strikes a nice balance between 1pg but incomplete and 5 pages chronologically detailed. If the person cares about the job history, it's there pretty complete and you can talk about it. If somebody is scanning things and wants to know high level skills a few things you've pulled off? Boom, first page above the fold. Also pure gold for interview prep. If you highlight interesting projects in your interesting projects section, they'll want to know more. It instantly directs the conversation towards centerpieces that you think are cool, knowledgeable, and excited about.
The big drawback to this format is you end up needing to refactor it quite a bit for the role (rearrange bullets/sections, change the technologies you highlight, change your stories). Also, I probably wouldn't put technical skills front and center for a management role.
Yes, you can keep the more verbose copy as backup material to present to prospective employers should they ask. I stop reading resumes after page #1...if you haven't caught my attention by then, one of the 1000 or so other ones in the stack will...
If it helps, I keep removing jobs from my CV as they become irrelevant, e.g. who cares I did XYZ 15 years ago? The technical knowledge from that long ago is not applicable any more.
I would, but my first job was from '98-2013, so if I take it out I feel like there's this giant gap. I left it in, but pared it down to two bullet points.
Just completely remove old jobs that are way in the past or not relevant to the position you are applying for.
i got told by a recruiter a few weeks back that i should rewrite it as it was 'far too short', then they sent me an example that was 8 pages long o_O
This isn't a strict rule, but it's important that it is easy to read, easy to skim, and is relevant to the position you are applying for.
I've seen shitty one pagers where people have just crammed in stuff that should have been cut, and made it harder to read and pick out the relevant things. And sometimes more pages is better, if they are necessary and actually add.
The important thing to remember about resumes (in most cases) their purpose is to get you an interview, not to get you the job.
But there's no magical bullets in job hunting, what some find very attractive others will find a huge turn off.
You’re right, there are definitely no strict rules, and it’s always nice to have the detail to dig in during an interview and a nice concise summary for an initial application. Unfortunately HR tends to make that difficult at most companies that I’ve had experience with.
Also, if your claiming that much.. you better know it.. if someone starts claiming C++ experience extensively in the past.. i start asking questions to see how much they are willing to bullshit
Yep, that too. Another good reason to trim things off the resume that you aren’t really an “expert” in.
[deleted]
I'm at 20-ish years experience in multiple industries and on multiple vendors, platforms, and environments. There's NO way I can summarize my 20 years in 2 pages.
EDIT: I do alot of contract consulting work. I've had a number of 3-6 month engagements with clients in the past 4 years, with wide variety of tech and roles/responsibilities. Its simply not possible to sumamrize doing a 6 month HCI implementation for a client in one bullet point. If someone is going to throw my CV away based purely on length then fine. I get plenty of work and my billable rate says I'm doing something right. ;)
1-2 page Summaries are for your cover letter and how experience in your CV can relate to what the employer/client is looking for.
My most recent couple of contracts/employers get the first 1.5-2 pages, and then I water down the older stuff until I'm simply referencing clients/employers and my title there. Ive done a large mix of contract consulting and full time employee gigs.
If you are hiring senior technical staff on a 1-2 page summary resume then you arent doing things right IMO. Juniors or recent grads? Sure, 1-2 pages are plenty.
That's what interviews are for.
Haha. See my comment in this thread about my experiences being interviewed. When the people I am being interviewed by are clueless I immediately take a pass.
Getting past the HR keyword filter is step 1. Most HR activities could be replaced with a set of regex filters.
5 page resumes go directly to the trash. If you can’t outline your relevant (to the position) qualifications in 2 pages, I’m not interested. I do not care about old hardware or tech you used to work on, it’s not relevant. Similarly, I don’t care that you were a noc tech 18 years ago. It’s not revenant because you’re applying for a senior level job. I do care about other senior jobs you have held, so keep it to.
Personally I hate long resumes because they highlight a deficit in communication skills.
Ouch, this is a harsh reality, but something I think I needed to hear. I think a lot of us, especially who've been in the field for a couple decades forgets that noone cares about all the old esoteric stuff we did.
Working on re-wording my older stuff and paring it down to the bare essentials.
I really hate long resumes too, it feels too much like word vomit. I guess when you don't trim out the old stuff, it just sort of builds up like a gross cancer.
I apologize if it seemed harsh. I've been doing IT for several decades as well, and it took me a while to realize that nobody cares about my experience with NT 4.0 domains or OS/2. The hiring manager only really cares if I have the needed skills and experience to do the job at hand.
As a contractor/consultant, I get a good many 3-6 month gigs, so the skills and tech from them are very relevant. Do I summarize revamping a UCS to HCI infrastrcture for a client in a single bullet point?
Given your attitude I wouldnt want to work for you anyways.
Literally yes.
You've completely missed the point. It is critical to tailor your experience to what is relevant to the position you're applying for. If you're applying for a job converting UCS to HCI, then include that experience. If you're applying for a job moving from HCI to Azure, it's not relevant.
I don't consider you not wanting to work for me a loss in any way. Hell, I wouldn't want to work WITH you in any capacity, especially as your boss. If you can't be bothered to improve your communication, you're a liability not an asset.