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/

Main example

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

116102
banditoitaliano•

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.

84
SynapticStaticOPIt's never the network.•

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.

8
EgglorrI am the Monarch of IP•

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.

37
IamMarcJacobs•

100% this. Hiring people only look at that front / first page

25
frickensweet•

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.

7

If less is more, imagine how much more, more is. - Fraiser Crane

4
CloudNetworkingIO•

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 :)

2
tgconns•

One page is all you need. Summarize only the most necessary ones and fit it into one page.

3
pmormr•

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.

2†
YouMadeItDoWhat•

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...

1
CloudNetworkingIO•

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.

1
SynapticStaticOPIt's never the network.•

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.

1
Syde80•

Just completely remove old jobs that are way in the past or not relevant to the position you are applying for.

1
runrep•

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

3
penislovereater•

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.

2
banditoitaliano•

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.

2
supnul•

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

2
banditoitaliano•

Yep, that too. Another good reason to trim things off the resume that you aren’t really an “expert” in.

1
[deleted]•

[deleted]

1
curmudgeonlylion•

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.

-11
Det_J_MillerCCNP, CWNA•

If you are hiring senior technical staff on a 1-2 page summary resume then you arent doing things right IMO.

That's what interviews are for.

17
curmudgeonlylion•

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.

-6
EleventeenCandlesCCNP, CCDP, EIEIO•

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.

4
SynapticStaticOPIt's never the network.•

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.

2
EleventeenCandlesCCNP, CCDP, EIEIO•

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.

2
curmudgeonlylion•

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.

-1
slyphicHigher Ed NetAdmin•

Do I summarize revamping a UCS to HCI infrastrcture for a client in a single bullet point?

Literally yes.

4
EleventeenCandlesCCNP, CCDP, EIEIO•

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.

2
projectself•

two pages at most. page one, who you are - skills, publications, patents, certifications, etc. page two - what you have done. experience with a paragraph explaining what you did..

On both pages, the key is to write about the job you want - not the job you have already done. write those descriptions and such as tho you are describing the job you want to be doing, and using your past experience to confirm / prove you can do it.

The resume is a forward looking document, using history to explain why you are a fit. not a history book explaining what you used to be.

61
dnietz•

the key is to write about the job you want - not the job you have already done. write those descriptions and such as tho you are describing the job you want to be doing, and using your past experience to confirm / prove you can do it.

The resume is a forward looking document, using history to explain why you are a fit. not a history book explaining what you used to be.

Best advice here.

I have a family member that is a high up exec at a large tech company. I had him look at my resume and chat with me specifically for career advice. He told me the same thing you just said.

10
EvilSubnetMask•

Seconded. This really is the best advice anyone ever gave me. Keep it short and sweet and write about the job you want to have. No one is typically excited to read a novel of your past exploits, use them to show you can do the job you are applying for. As someone who has read through lots of resumes over the years, I find that anything over 2 pages is generally excessive and shows you don't know how to be brief. Sounds like from @OP's edit that they went this route. Good luck looking for your new job!

2
bccruiser•

I love this. Helping my bro with his resume and I couldn't put my finger on it, but I think this is it. I don't want to read about what you did for some other company, what are you going to do for MY company.

3
Lurk3rrCCNP•

If it’s not too much trouble, would you mind PM’ing me an example of such a resume? Mine is definitely not in this style and I would like to fix that.

1
captain_dylan_hunt•

Delete every "WAS a lead xyz." It should be "Lead dog washer for abc." Not "was lead dog washer".

I would think you need the Skills near the top, for the few that actually READ resumes.

Now days, search engines index off key words and resumes get sent to recruiters and HR departments.

15
Cheeze_ItDRINK-IE, ANGRY-IE, LINKSYS-IE•

Now days, search engines index off key words and resumes get sent to recruiters and HR departments.

This is the key to understand.

Understand what the searchers are parsing your resume for. Put those keywords in there. You'll get your resume seen more.

5
AJAlabsCMNO•

I look for the skills either at the top or at the end. Nowhere else. And as a hiring manager, yes, please keep it to one page.

If you really want to stand out. Make sure to include a cover letter.

2

So you don't have time to read more than a page of resume but you want to read a whole page of cover letter too?

1
AJAlabsCMNO•

I find the cover letter of more value. I get more of your personality and written communication skills from your cover letter. Your resume simply needs to let me know that you’re qualified for the position and I should bring you in for an interview.

1

I put a lot of personality in my resume because I'm not qualified for any position. It was a fairly effective move (got a lot more responses since). Was told no-one ever actually reads cover letters.

1
RandomTrashMob•

Going to parrot the others here.

​

​

FIVE PAGES IS WAY TOO MUCH. 2 tops. Remove skills that don't apply directly to the job you're applying for. Sorry, but you'll have to make adjustments to your resume for each job.

Someone else mentioned keeping your 5 pages as reference, and I agree! Keep those pages with your skills. This should let you plug in related skills for each job you're applying for.

​

There are plenty of templates online (or just on word) that will get you in the right direction. Something simple and clean always works best.

14
rroberts3439•

IT Manager with 30 employees and I'm always interviewing and looking at resume's. Comments are mine alone.

5 pages is a big no. Frankly more than 2 is a no to me. Make me want to learn more about you. I'm not likely to read more than 60-90 seconds worth at the first shot. I may read more before the interview. Make it easy for someone to find the info while glancing.

The white space is a total waste of space. It's kind of annoying to be honest. So I personally would make it more compact. Tell a get to know me short story with your best stuff and leave the rest for later.

Again, I could be completely wrong. Just my thoughts.

​

Good luck!!

8
morganinc•

Right! I think as much as we want someone who is technically savvy we also want someone personable and easy to get along with. If a resume seems stiff and unimaginative, then they might be as well.

3
curmudgeonlylion•

5 pages is a big no. Frankly more than 2 is a no to me. Make me want to learn more about you. I'm not likely to read more than 60-90 seconds worth at the first shot. I may read more before the interview. Make it easy for someone to find the info while glancing.

Then you wont get someone like me with 20 years experience.

-5
slyphicHigher Ed NetAdmin•

Then you wont get someone like me with 20 years experience.

Exactly. They'll get someone with 20 years of experience, and an ability to summarize and prioritize information, instead of going on Grampa Simpson monologues

19
curmudgeonlylion•

Haha. Fine. I get plenty of work.

0
rroberts3439•

If you can't summarize your experience in 2 pages and expand during the interview then ok. Being able to communicate efficiently is an important skill.

5
LittleWanger•

I agree with the others. 1 or 2 pages at most.

What part of the world are you in? I see plenty of demand for skilled engineers in the UK

7
SynapticStaticOPIt's never the network.•

West coast US, but I'd happily move to the UK. :)

3
LittleWanger•

Loads of vacancies in bay area, but I would never work there . Cost of living is insane

5
SynapticStaticOPIt's never the network.•

Same here. I was offered a job 2x my recent job to go to the bay area, but passed on it because of the CoL as well as commute times, etc. I would've had to live out in Livermore to get to a decent CoL (This was several years ago), and the commute was like 90+ minutes each way.

Maybe I'm dumb, but I value those hours more than they can pay me. Most recent commute was 5 minutes, so I'm kind of spoiled. :)

4
OrcwinCCNA / VCP-NV•

I've done 90-120 minute commutes for the last four years. It's too much, it really wears you out.

2
[deleted]•

[deleted]

1
regmeyster•

yeah I used to live out in Southern CA where my commute was an hour each way, if I was lucky, and the horrendous CoL. We moved to Fresno, and yes, I know really not much to do out here but found a nice job, bought a house that still allows me to splurge on other things, and my commute is 30min w/traffic.

1
snokyguy•

20 minute to basically anywhere in Des Moines Iowa and plenty of IT jobs

1
k6usy•

Reasons why I live in Fresno and have a 15 commute.

1
[deleted]•

[deleted]

1
StoopidZoidberg•
4
DarrenRoskowBut did you ask nicely for the packets? •

That is a good example of tailoring to the target as well. Unless you are a recent grad or applying in academia, Education should come after experience if it is even relevant to include for the role.

1
tristanrhodes•

As a person who has been on a handful of hiring committees, I have a few suggestions.

First, less is more. When I have to read through dozens of resumes on top of my normal duties, I always appreciate a resume that is concise and targeted to the job being applied for. This means you can leave out any extra skills that aren't listed on the job application (unless ther are related).

Yes, I like the summary of skills at the top.

I agree that you should look for another resume template that doesn't have such a huge indent. For instance, your name should go at the top and then you can slide everything over. You might want to try using some fancy free software to format a resume:

https://zapier.com/blog/resume-building-tools/

3
SynapticStaticOPIt's never the network.•

What about the letter soup stuff? Unfortunately I end up with a bunch of skills like "OSPF, IPSec, MSTP, etc". Is that something you'd want to see up top? that is one thing I'm really struggling with is how to present that.

Also, could I send you a revised resume? Rebuilding it from scratch tonight with all the input here, and getting rid of what I now realize is a ton of fluff.

2
packetloss99•

In my country there is no much joy for network engineers... so 2 years ago I decided to move to virtualization and cloud. It was a good decision

3
brok3nh3lix•

how did you make that jump?

1
MoreheiMake your own flair•

By virtualizing network devices...and that's only half of a joke. Cloud & co is nice but despite the name aren't walking on thin air.

1
packetloss99•

Sorry for my late reply. I was working in NOC team and I loved it, but from where I come from, there was a lot of interest for cloud engineering/architecture. seems like many of big companies are moving their infrastructure on cloud services like AWS or Azure, and there were lot of job opportunities. For network admins/engineers, there aren't many choices and salary is not as it should be.

1
internet_eq_epicCCNA•

I just recently got hired on as a network engineer in the edu space, but of course that doesn't mean what I have to say is absolutely correct.

First, I think 5 pages is way too long. I took some care to keep mine at 2 pages, and while it was difficult, I feel like it keeps me focused on things that really matter to the potential employer.

I keep my layout and design extremely simple. The image you shared of your style is wasting a lot of space on the left side, which in turn forces text to wrap more often, lengthening the overall look (specifically look, not content) and making it difficult to read.

I start with a 2-line header with my name, email, phone, and address. Then after a horizontal separater for the header, I have sections like "Skills", "Work Experience", etc. (the bulk of my resume is these two sections).

The skills section is literally just a list of bullet points. Reasons why I think I am better suited for the job than anyone else. These include technical and non-technical skills. For example, one bullet point I have is (roughly) "Strong understanding of network security". This is a very general point, so I follow it up with a couple that are more specific, mentioning how I have experience with firewalls, VPNs, PKI, etc.. I think (hope) this shows I have a good overall understanding of a topic while not sacrificing on specific technical details and hopefully getting past some automated filters. Again, non-technical skills are important as well, so don't forget to include at least a couple of those.

I try to keep each bullet point just one line in length, but a few do wrap to a second line. Two lines is the max. Anything more than that and I should either exclude some info, or separate it into another bullet point somehow.

For my "Work Experience" section, I have a small header for each job, followed by some bullet points that (I hope) support the skills I claim to have. These are mostly actions, things I am actually doing on a day to day basis. Again, each point is no more than one to two lines max, with most being just one line.

I actually have a few separate documents where I keep just "skills", just "work experience", etc., this way I can fill them up with all the bullet points I want. If I remove something from the actual resume for length reasons, I'm not deleting it forever, just from that copy of the resume. It also saves me having to think too hard to come up with a resume that matches the job I'm applying for.

As far as references go (and I honestly don't know if this is a good choice or not), I've always either just had "References available upon request" or just didn't include any mention of references. I have references ready to go if/when I need them, but I've never felt the need to include them directly on a resume.

Finally, I'm not afraid to play with the font size if I want to lengthen/shorten the overall resume. Obviously, don't go crazy big or tiny, but I think a couple points off 12 is acceptable. Just keep the thing consistent. Currently, my entire resume (headings and all) is 11 point font size.

I realize this is a bit lengthy and some of it repeats what others have said, but I hope it helps nonetheless.

3
j-devCCNP RS•

I read a few resume books last year in preparation for a job search and these are the major sections, in order. Not everyone will agree on the performance profile, but the rest of the stuff is solid. My old company interviewed so many guys with 2-page resumes that I'd say it doesn't hurt you at all, as long as you put the important stuff near the top.

​

Sections:

  1. Performance profile: a two-sentence elevator pitch stating what makes you special.
  2. Core skills: This is where you put all those keywords: Platforms you've worked with, protocols you're proficient at, certs you have, and other stuff (programming langugages, US citizen (for jobs that require it), languages you're fluent in
  3. Project highlights: These are terse bullet points indicating projects you've led or played a very active role in. Don't BS this, as it's very likely to get you specific questions.
  4. Education
  5. Professional experience: Use the active voice and direct language. No fluff or unnecessary words. Can use present tense for current job and past tense for previous jobs.

Some people might put their education all the way at the bottom, especially if they've been out of college a long time. Since my education section is very short, I put it on top of professional experience so it doesn't get overlooked.

If your resume is too long, cut out irrelevant jobs and duties. You can always link to your LinkedIn for people who want a more exhaustive job history, which they won't care for during the initial screening.

2
opackersgoCCNP R+S | Aruba ACMP | CCNA W•

I’m going through a similar thing, I applied to 6 places and got second interviews everywhere and offers from most. I’m a mid level engineer, around senior engineer/consultant level.

I’d be happy to send you a sanitised version of mine tonight if you’d like?

2
[deleted]•

[deleted]

1
SynapticStaticOPIt's never the network.•

Oh absolutely, that would be amazing!

1
ayoung807•

Education section, skills section, projects section. Try to keep it to 1-2 pages

2
airroc925•

As a hiring manager in the Bay Area, I am going with the masses here trim it down to two pages please..... take your references and trim it down to the most recent no more then 1 page.

Use the rest of the relavent information in a well drafted cover letter or present it during the interview.

2
karma1991•

There's a site called novoresume.com that guides you through creating a well rounded resume. You should check it out, the UX is pretty good.

2
SynapticStaticOPIt's never the network.•

Will do, thank you.

1
morganinc•

So much boring here in the comments, remember no one wants to read a boring resume. Make it short yes, but make it sweet as well. Make the first paragraph or two on about you, how awesome you are and why any organization would be blessed to have you.

2
LordShadow_Cinci•

I'm a CTO level manager. 5 pages will not get looked at on my desk, ever. If you have 20 years experience, then maybe a second page, but the comments here about 1 page are SPOT ON.

Looking For each position, list no more than 3 bullet points that cater to the position you're applying for. Anything more is to much to sift through, and tells me you can't communicate well in writing, which is a key requirement in our shop.
The rest of the info? Put it in your LinkedIn Profile, and put the link to your linked in on the resume. Use that info to draw from when you're tailoring your resume to the position and company you're applying for.

2†
Gesha24•

There's nothing special about resume writing for network engineers, so you could have easily gone to the subreddits that focus on it and read up there.

You are writing resume to get through HR and convince hiring manager to give you a call. Once you got that call - it has served its purpose. HR needs keywords - so make sure they are present. Hiring manager needs to understand what you have been doing in the last few years.

Resume length - I've seen great 5-page ones and terrible 1-pagers. I personally will not discard resume based on its length, but you can see that others will do that. So I use this knowledge when I apply somewhere and make sure that my resume is at least 3 pages long - based on my experience, I do get more calls with shorter resume, but I don't want to work for any of those places. So I keep resume long to filter them out.

I would not include references in the resume. If you are asked - provide them, otherwise don't worry. And be extremely careful with formatting - not insignificant amount of companies use some software that goes through your resume and tries to rearrange it to their desired format. If your resume is in anything but the most basic format, it's extremely likely there will be a hot mess at the output of that system. You are not applying for a creative designer position, pretty looking resume is not likely to win you any extra points.

2
rodimustso•

BGP if you actually know it. I think it was Keith Barker who interviewed someone who runs their own IT consultancy company. Anyway, the person explained how they will really dig and dig deep into the person to find out if they really know the stuff they say then know. BGP was the example that he used detailing it with examples of the route selection with transitive vs non-transitive attributes.

You only really need 1 page to answer the two main questions of what do you know and what is your experience? If they're interested in you they'll ask for your references, throw 1 page of education on the 2nd page. BUT more than any of that the person interviewed stated that the BIGGEST thing that gets your resume thrown out is poor grammar, spelling, punctuation with the reasoning that "If you can't put your time into this why should I give you my time". Paraphrasing but yea. If you can find the video go watch it before you work on your resume again. Might have also been Network Chuck.

2
SynapticStaticOPIt's never the network.•

I know the basics. I've done basic configurations for eBGP as well as iBGP, but mostly on Juniper platforms. Also have a general idea of route selection process. To be fair, I don't know it inside and out, but on the other hand the one book I had on it was 1200 pages. :)

1
rodimustso•

Learn some more of it, its my favorite routing protocol by far. A lot of multi site enterprises I've seen don't even use OSPF or EIGRP either or very little if at all. There's been some funky shit that happened where I work when the ISP screws something up and your network starts learning a few million routeing prefixes. Knowing BGP is what fixes an entire shutdown like that.

1
non-stick-rob•

be assured that interviewers will have skipped along many many cv's. i like to leave them short of info, just to get them asking. i use words like "Full" and "Comprehensive" knowledge of "CCnaqlteapot" I dont find need to waste time or pad things out to say i know how to write a query. they see through it and they dont have time for it.

also the longer your cv, the longer it takes to read over. imagine this post, but TL;DR at the top

2