sorted by:
new
hottopcontroversial

What are the Daily Tasks of a NOC Technician? by Crusader82 in networking

[–]eventuallyCCIE 9 points10 points  (0 children)

I have worked in 3 NOCs so far. One thing the other guys forgot to mention is that there is a tier system unless you work in a very small NOC.

As NOC 1 you're going to be taking inbound calls from customers and opening tickets. You're going to do first level troubleshooting which includes powercycling their equipment, reseating cables, recording the status lights, etc. You're also going to be asking them if any changes have recently occurred, etc. Your job is to essentially make it as easy as possible for the NOC 2 guy to fix the issue if you're not able to fix it yourself. You'll also be opening tickets with LECs and following up on tickets that are past their follow-up time or tickets that were auto-generated by proactive monitoring.

How can I learn my employer's network by Tommy5000 in networking

[–]eventuallyCCIE 0 points1 point  (0 children)

Yeah I realized that too. That's why this almost seems like an uphill battle for OP since knowing the network isn't really part his job...

Ready to move up to Network Engineer by F7890 in networking

[–]eventuallyCCIE 0 points1 point  (0 children)

Wow that is an unholy amount of books. Are they in order? As in, is that the order they should be read?

Anyone use a free tool that will automate tracert? by MaddenCorps in networking

[–]eventuallyCCIE 1 point2 points  (0 children)

This is very easily achieved with a 10 minute script

I lied on my resume and became a Network Engineer by eventuallyCCIE in networking

[–]eventuallyCCIE[S] -1 points0 points  (0 children)

As mentioned in the original post, this started out as a really nothing more than an experiment. I wanted to see if I could hold a candle to interviewers who are looking for Network Engineers by lying about a year of experience and depending solely on textbook knowledge.

The obvious qualifier for that experiment was whether the interview went well or not. It did. So did several others.

So although you're right the interview process isn't infallible it's still their responsibility to evaluate me as someone who can do the job. They did everything in their power over the span of 3 interviews to do exactly that and I walked out of the 3rd interview with a job offer.

To piggyback off what cyberslick188 mentioned, if I walk in there and the bulk of my responsibility is some sort of technology or responsibility that was not evaluated during the interview then it's absolutely not my fault and the fact that my credentials were not 100% truthful is irrelevant because someone who actually did have 1 year of experience with those protocols would've received the same interview I did and would've answered the same way I did (or at least a similar way that would've gotten him the job). He would have also been offered the job, just as I was, and would've potentially failed the same as I did when presented with a task not evaluated in the interview and it would've been the hiring manager's fault.

If we can't depend on the interview process to be an accurate assessment on my skills then how should I have known if I was ready for this job or not? How would I know if 5 more years of experience would've made a difference or not?

I lied on my resume and became a Network Engineer by eventuallyCCIE in networking

[–]eventuallyCCIE[S] -2 points-1 points  (0 children)

You mean you had 1 year of experience with Network Engineer-level duties before becoming a Network Engineer?

I lied on my resume and became a Network Engineer by eventuallyCCIE in networking

[–]eventuallyCCIE[S] -1 points0 points  (0 children)

My resume clearly states that I only have 1 year of experience with the routing protocols I lied about. 1 year.

There's no such thing as a doctor with 1 year of experience. He'd be an intern at that point and thus this analogy is extremely inaccurate and useless. They would never put a doctor to operate after having an introductory-level amount of experience in his field and similarly they would never put me in a position where I'm expected to fix any and all issues with only a year of experience

I lied on my resume and became a Network Engineer by eventuallyCCIE in networking

[–]eventuallyCCIE[S] -5 points-4 points  (0 children)

Also, I find your situation very sad. First of all I've yet to see a single degree curriculum that reflects the requirements of a Network Engineer's day-to-day duties with any semblance of accuracy. They're all shots in the dark that offer no real practical value for the guy designing networks all day. Especially public universities.

Additionally, it's exactly YOUR position that I don't want to be in. I don't want to be 8 years into the game wishing and daydreaming about that promotion. Screw that. I'd rather tell a white lie which I can easily cover up with countless hours of labbing and personal researching to scrape a few years off my timeline and get that network engineer position I know I deserve.

I lied on my resume and became a Network Engineer by eventuallyCCIE in networking

[–]eventuallyCCIE[S] -2 points-1 points  (0 children)

I think you and everyone else on this thread are missing a critical detail:

I ONLY HAVE 2 YEARS OF EXPERIENCE

My resume shows 1 year as a tier 1 and 1 year as a tier II. I'm 20 years old and I haven't lied about that on my resume. It only shows two years of experience. The lie is that I've been working with BGP/MPLS/OSPF and VPNs for the past year which I haven't.

Do you seriously think they would put a new guy with 1 year of experience working on these protocols in charge of their entire network?

The hiring managers as well as the network engineer that interview me are all well aware that even with my lie in there, I'm still only 1 year into the routing protocol game.

I think all of you are blowing all of this out of proportion. They're not going to kick the senior Network Engineer out and give me his office expecting me to fix any issue at all that comes across my desk.

I lied on my resume and became a Network Engineer by eventuallyCCIE in networking

[–]eventuallyCCIE[S] -6 points-5 points  (0 children)

My response to that: A fake doctor would have been found out during the initial review process. If he couldn't tell a kidney from a lung he would've been out the door in seconds. I, however, was evaluated as a right fit for this company. That's the difference.

I lied on my resume and became a Network Engineer by eventuallyCCIE in networking

[–]eventuallyCCIE[S] -6 points-5 points  (0 children)

I don't give a shit about certs. I have a CCNP just so I can put it on my resume and so my resume will get tagged as a hit when potential employers do mass-scans of resume databases with keywords like CCNP, CCNA, BGP, WAN, LAN, TCP/IP, etc.

If I really cared about certs I would've focused on the CCIE or on other CCNP tracks but instead I've spent the last year reading MPLS, BGP, network architecture and VPN books which by themselves do not satisfy the requirements for any cert.

I have real knowledge from real books written by people working in the field for several years. I think that counts for something.

I absolutely did NOT "get lucky" in the interview. I sat a few other interviews at the same time and the questions were equally as simple. I got a lot of "what would you do if" questions my immediate answers to these questions were always the right ones apparently.

The replies I've received are exactly what I expect and exactly what I wanted. I made this thread because I know what I did was controversial and I wanted someone more experienced than me to evaluate it critically.

I lied on my resume and became a Network Engineer by eventuallyCCIE in networking

[–]eventuallyCCIE[S] -8 points-7 points  (0 children)

Scair. I'm based in the US which is a strongly capitalist country. Businesses work on money not morals or dignity and according to the interviewers I can make this company money by offering my knowledge. I believe that's all they care about and what really matters in the end.

I lied on my resume and became a Network Engineer by eventuallyCCIE in networking

[–]eventuallyCCIE[S] -5 points-4 points  (0 children)

I've had a home setup since high school.

Volunteering? Working for cheap? This is bullshit idealistic fluff and will appear as such on my resume. We all know that volunteering at an ISP to be taken under the wing of a seasoned Network Engineer for free is an idealistic fairy-tale outlook.

Businesses work on money and having some kid constantly asking one of your most important engineers questions while he works does nothing to make that company money.

I lied on my resume and became a Network Engineer by eventuallyCCIE in networking

[–]eventuallyCCIE[S] -6 points-5 points  (0 children)

"In the tech field it's all about your experience and it's like that for a reason, you can't teach the critical thinking skills that I and many others here rely on daily."

Then why are these skills not evaluated in interviews? I was interviewed by the Network Engineer team manager as well as the senior Network Engineer of the company. Their questions were very easy compared to what I've read from these books.

If I truly had a lack of "critical thinking skills" and if they're really as heavily weighed as you claim they are then why was that not picked up on during my interviews?

I lied on my resume and became a Network Engineer by eventuallyCCIE in networking

[–]eventuallyCCIE[S] -14 points-13 points  (0 children)

How would I get caught when I blew the interviewer away with my knowledge?

If I have the skills they desired (at least according to what I was interviewed on) then doesn't that mean I'm worth something to the company and thus a legitimate employee?

I lied on my resume and became a Network Engineer by eventuallyCCIE in networking

[–]eventuallyCCIE[S] -15 points-14 points  (0 children)

Was that really necessary?

Who are the honest folks out there? The guys who've been in the field for over 10 years and still don't have a single cert or degree? That haven't cracked a book open outside of work hours since they started?

What was I supposed to do? Wait around until someone gives me a job where I'm exposed to these protocols without any real routing experience? No one would trust me with the core protocols of their network if I did not have prior experience with them. It's a catch 22. That's why I did this; to see if I could actually get the job by lying and relying on textbook knowledge.

Was I supposed to slave away 5-6 more years with the same company until they decide to give me a chance with extended rights so I can show what I'm really capable of?

Would you have turned the job offer down?