Couple of IT interview questions..

rz30 said:
I can pick up this network stuff in 20 mins, coders should be payed 10 x what network guys are being paid.
Click to expand...

That shows you have no idea what you are talking about. A networking job is a lot more in depth than plugging in a network cable and checking google loads OK. Configuration of network switches, routers and IPT is as indepth as your coding. Except for we have a lot of responsibility for what we do which counts for a lot.
 
Last edited:
Trifid said:
That shows you have no idea what you are talking about. A networking job is a lot more in depth than plugging in a network cable and checking google loads OK. Configuration of network switches, routers and IPT is as indepth as your coding. Except for we have a lot of responsibility for what we do which counts for a lot.
Click to expand...

Serioulsy though once you learn it that's it..........?

LANS, MANS, WANS and GANS
Chosing the right cables and plugging them in
Switching on the router
Assigning IP's to each PC on the network if manual assiging is needed
Setting up the firewall
Monitoring the logs(might be a different role)
Sorting out any potential issues, dead router or dead router, maybe even some conflicts here and there, chuck router out, order a new one.
* managing email, anti spam and virus protection; * LOL
analysing and resolving faults, ranging from a major system crash to a forgotten password
Most of the monitoring an engineer does is with software.
Peer-to-peer, Hybrid combinations and server/client sytems
Understanding protocols

You tell me where it gets complicated?
 
rz30 said:
Serioulsy though once you learn it that's it..........?

LANS, MANS, WANS and GANS
Chosing the right cables and plugging them in
Switching on the router
Assigning IP's to each PC on the network if manual assiging is needed
Setting up the firewall
Monitoring the logs(might be a different role)
Sorting out any potential issues, dead router or dead router, maybe even some conflicts here and there, chuck router out, order a new one.
* managing email, anti spam and virus protection; * LOL
analysing and resolving faults, ranging from a major system crash to a forgotten password
Most of the monitoring an engineer does is with software.
Peer-to-peer, Hybrid combinations and server/client sytems
Understanding protocols

You tell me where it gets complicated?
Click to expand...

see your opening post for evidence
 
Red and White said:
see your opening post for evidence
Click to expand...

Point being that beacuase of this post i have now learned a fair amount over the last few hours. I think i have a good vision of the whole thing, yes i can learn a lot of things yet but i could pick this all up properly by reading and on the job experience with a month or two.

Also i should thank those who contributed as it has been very useful for me to realise the level i am actually at.
 
rz30 said:
You tell me where it gets complicated?
Click to expand...

Ok, you go learn the ins and outs of EVERY config for every scenario, for every peice of Cisco CatOS and IOS hardware, learn how to use the various levels of encapsulation, encryption, trunking, VLANs, and then know how to troubleshoot all of the above, without reference.

But wait, you probably couldn't even make a console cable. Let alone get into enable mode of the CLI. God help you if you had to drop to ROMMON mode to reset the memory register where the encrypted secret password is stored.

YOU WON'T GET ANYWHERE WITH YOUR ATTITUDE. WHAT YOU SEE AS NETWORKING, A TRUE NETWORKING GURU SEES AS PLAYSCHOOL. ITS LIKE SAYING YOU WOULD MAKE AN AWESOME ASTRO PHYSICIST AFTER GETTING A GRADE E GSCE IN PHYSICS.
 
Last edited:
rz30 said:
Point being that beacuase of this post i have now learned a fair amount over the last few hours. I think i have a good vision of the whole thing, yes i can learn a lot of things yet but i could pick this all up properly by reading and on the job experience with a month or two.

Also i should thank those who contributed as it has been very useful for me to realise the level i am actually at.
Click to expand...

im sorry but you have already proved you are clueless about networking and after a couple of hours of reading you are belittling the job. youve got no chance in that interview mate. good luck though.
 
rz30 said:
You tell me where it gets complicated?
Click to expand...

This thread has reached epic lol. Answer the question I put to you a page back then, it really is a basic question. The things that you mentioned are barely scratching the surface.

Im happy to explain the answer to you tomorrow. Search for VLSM if you want a hint.

Like the chap above said. Your attitude could do with some improvement.
 
paradigm said:
Ok, you go learn the ins and outs of EVERY config for every scenario, for every peice of Cisco CatOS and IOS hardware, learn how to use the various levels of encapsulation, encryption, trunking, VLANs, and then know how to troubleshoot all of the above, without reference.

But wait, you probably couldn't even make a console cable. Let alone get into enable mode of the CLI. God help you if you had to drop to ROMMON mode to reset the memory register where the encrypted secret password is stored.

YOU WON'T GET ANYWHERE WITH YOUR ATTITUDE. WHAT YOU SEE AS NETWORKING, A TRUE NETWORKING GURU SEES AS PLAYSCHOOL. ITS LIKE SAYING YOU WOULD MAKE AN AWESOME ASTRO PHYSICIST AFTER GETTING A GRADE E GSCE IN PHYSICS.
Click to expand...


I have a degree in Physics from Glasgow Uni and it is a hell of a lot of intense than networking, i do admit that although i had the talent i definately could have attended a few more lectures than i did.

Nevertheless, WHY can you not use reference, is it some kind of competition that you can't have a laptop of some kind of PDA on hand, i understand that there will be a lot of configuration involved but the job is not one of memory skill rather it's a manual labour job like that of an electrian or plumber.
 
rz30 said:
I have a degree in Physics from Glasgow Uni and it is a hell of a lot of intense than networking, i do admit that although i had the talent i definately could have attended a few more lectures than i did.

Nevertheless, WHY can you not use reference, is it some kind of competition that you can't have a laptop of some kind of PDA on hand, i understand that there will be a lot of configuration involved but the job is not one of memory skill rather it's a manual labour job like that of an electrian or plumber.
Click to expand...

lol, this is wind up right.
 
Ok, if your business critical internet connection has just dropped, for an unknown reason, and every 15 minutes of downtime is tens of thousands of pounds lost, you don't have TIME to research, you just need to KNOW.

Until you HAVE SEEN the depth of configuration of enterprise level hardware, you simply will not be able to comprehend just how downright complex it is. I assume you think that all routers have config webpages? Have you ever even used a telnet or terminal session before? Do you know about hardware flow control? Do you even have a slight clue to the architecture of a cisco based networking solution? If I threw a PIX at you and asked you to set up access-lists, would you even know what I meant, let alone know how to do it? NO.

And as someone quite rightly stated early on in the thread, having a paper based degree (even in the subject that you wish to work in) does NOT qualify you for the real world.

If you think you can become a competant enterprise level network technician (yes, technician, the lowest of the low, not an admin, not an architect, not anything special in any way shape or form) in a few hours, followed by a few months "hands on" then you are a retard.

If you came to interview at our place, I wouldn't have even entertained the entire interview, you'd have been shown the door.
 
Last edited:
rz30 you are looking at networking from a home user, singular subnet range – as previously stated this is ‘playschool’ for the majority of us network guys.

Try implement a secure, multi-vendor, MPLS VPN solution for a large corporate enterprise. This will usually span locations varying from hundreds of remote sites to multiple data centres - then see how far you get.

Networking, like any field is as complex as the user makes it. Comparing the ‘ease’ of implementation to say, programming is just plain stupidity.

I could botch out “Hello World!” in probably every language under the sun after 5 minutes research.. try get me to produce something more useful and it will take a lot more research. The same applys to the network field.

You seem rather naive, and at best childish in your behaviour in this thread.
 
rz30 said:
Serioulsy though once you learn it that's it..........?

LANS, MANS, WANS and GANS
Chosing the right cables and plugging them in
Switching on the router
Assigning IP's to each PC on the network if manual assiging is needed
Setting up the firewall - Just one step? THis is probably the hardest part.
Monitoring the logs(might be a different role)
Sorting out any potential issues, dead router or dead router, maybe even some conflicts here and there, chuck router out, order a new one.
* managing email, anti spam and virus protection; * LOL
analysing and resolving faults, ranging from a major system crash to a forgotten password
Most of the monitoring an engineer does is with software.
Peer-to-peer, Hybrid combinations and server/client sytems
Understanding protocols

You tell me where it gets complicated?
Click to expand...

How about setting up some DNS for all your hosts?
How about setting up a network booted boot loader with a list of OS install CDs?
How about a WSUS/caching proxy of linux repos?
And that's just stuff for hosts.

Networking is huge, it takes years to get good at just one aspect.
 
Last edited:
rz30 said:
I have a degree in Physics from Glasgow Uni and it is a hell of a lot of intense than networking, i do admit that although i had the talent i definately could have attended a few more lectures than i did.
Click to expand...

So highly educated but with such poor spelling :eek:
 
stop right there. The op probably has had enough of you lot spurting off over thread. Just like to say to the op that alittle research is needed before interviews like this but does not mean you won't get the job just because you might fail to answer some questions. Do alittle researchfor your questions and tell us the answerers maybe?
 
BigglesPiP said:
How about setting up some DNS for all your hosts?

Networking is huge, it takes years to get good at just one aspect.
Click to expand...

He also only "switched on" the router. I assume its one of those magical corporate routers that manage to set themselves up.

optitech-uk said:
stop right there. The op probably has had enough of you lot spurting off over thread. Just like to say to the op that alittle research is needed before interviews like this but does not mean you won't get the job just because you might fail to answer some questions. Do alittle researchfor your questions and tell us the answerers maybe?
Click to expand...

Stop right where? We are defending our profession from belittlement from someone who refuses to get a clue. The fact of the matter is that he doesn't realise that IT IS over his head.
 
paradigm said:
And as someone quite rightly stated early on in the thread, having a paper based degree (even in the subject that you wish to work in) does NOT qualify you for the real world.

.
Click to expand...

I don't disagree with that at all, you can pass a degree if you know how cram study correctly. You will have some lab experience but as you said no real world experience. There was a fair mix of people in my class and a lot depends on your enthusiasm, to be honest i started off doing Chemical Physics but got kicked out of Chemistry as i never went to any labs and didn't want to leave Uni so i stuck in with Physics, wish i had done computing now though.

Nevertheless this is not a high end position i am going for it's to get my 'foot in the door' and give me some kind of income/experience.
 
You must log in or register to reply here.
Back
Top Bottom