Couple of IT interview questions..

Ok it is time for a read.

OK just remember that every minute your customer is down he's losing £100,000 in revenue and your companies SLA's promise him resolution in < 5 mins ;)

To be serious for second we've all got to start somewhere and we all knew nothing at one time or another but it's best to have a little humilty, I'll leave the "how do you reconverge a fully meshed MPLS network with 180 LSP's" for another day!
 
Last edited:
A basic job with IT will not require this level of knowledge. FAIL

Oh shut up will you. You FAIL more than anyone in the thread, including the OP.

Like I said last time (that you conveniently ignored), this was all to PROVE A POINT. To show the OP that he didn't indeed "know everything" and could "learn in a couple of hours".

Nowhere did ANYONE say he needed this knowledge for his interview.

The OP has finally taken this onboard and gone off for a good read. So it served its purpose.
 
A basic job with IT will not require this level of knowledge. FAIL

Rubbish, if he's goes in a first line support the simple question posed above shouldn't be too hard, if he was going for a first line network support job and he couldn't answer the above he wouldn't get a job in my company (ISP)

First line support have to be able to quickly identify problems and either solve them are pass them onto 2nd/3rd line quickly.

My question could be solved by any first line engineer that knows their mustard.
 
Last edited:
Rubbish, if he's goes in a first line support the simple question posed above shouldn't be too hard, if he was going for a first line network support job and he couldn't answer the above he wouldn't get a job in my company (ISP)

First line support have to be able to quickly identify problems and either solve them are pass them onto 2nd/3rd line quickly.

My question could be solved by any first line engineer that knows their mustard.

The ops first post in this thread asked 2 simple questions and everyone as usual jumped down throats. AS PER.
 
So I guess you ignored me again then? Yes he asked two simple questions, but he also stated a lot of crap and showed a huge attitude problem. This is why people jumped down his throat, no other reason.
 
The op doesn't need to know half the stuff posted here. But he needs to be aware of it. Home networking isn't the be all and end all.

For the interview a few tips:
1. Stop BSing. Admit you don't know something if you don't. Someone posted above something similar saying some dude got hired as he was more honest than another candidate, even if he had less aparent knowledge.

2. It can hardly be your fault if you don't have experience of enterprise level hard ware and configurations, not everyone can afford £100,000 of equipment to play with. ignorance isn't nessacarily a bad thing - it can be fixed.

3. Show to the prospective interviewer that in the areas of knowledge you do have (be that home networking as it may), that you are fully competent.

4. There are basic things that you should however know, regardless. I fear that the op may not have these even. In that case probably should do a course of some sort, or read that book as posted above.

5. Most folk applying for these positions are enthusiastic and passionate enough to already have multiple PCs/ networks, odd equipment, linux boxes/ windows machines and have a few years experience even if it is messing about/playing around at home setting up network services etc. I don't think the OP has done much more than DOWLOAD MOVIES, LOL! using a torrent client, chosen based on it's ease of installation.

6. I would say good luck :)
 
This has become a fantasic thread on the basic requirements for an network engineer.

I will check back in a couple of months to update my progress.

On another note, my degree was really just a waste of time, unless of course i go in for teaching which is still a possibilty.
 
This has become a fantasic thread on the basic requirements for an network engineer.

I will check back in a couple of months to update my progress.

On another note, my degree was really just a waste of time, unless of course i go in for teaching which is still a possibilty.

how much starting you looking for?

hahaha I'll employ you just for the humor!!!!!!
 
First thing you check is that the cabling is properly connected from router to the wall(terminology check).

Second check your password and username are correct.

You should also have some software from the routers manufactures that run you through the setup. (am assuming this has all been done)

Thirdly see if the ISP is assiging you an IP address if it isnt i would likely say the problem is at the ISP end.

If it is then you want to check that your firewall is not blocking the conection.
twfoxcatjcd0.jpg
 
I can pick up this network stuff in 20 mins, coders should be payed 10 x what network guys are being paid.

I wish :)

What you have learned about networks so far is the equivilant of making a bad notepad clone and dropping a few words like class and inheritance.

I'm no network engineer but I have the common sense to know the field is far more complicated than plugging in a netgear and mapping a few ports. That may be all you ever need but if your employed as a network admin for a decent size company your going to need more, a lot more.
 
Here's a very easy test question for you, you have server on a subnet behind a router, the server is able to ping the router but not able to ping anything on the internet. The server is able to ping other machines in the subnet and visa versa. Even thought the ACL's are open nothing from the internet can connect to the server even though the webserver is running.

Q. What would be the first thing you would check?

HEADRAT

A. The answer to the question is that the the server does not have it's default route set, so it can ping other machines in it's IP range as they are on the same logical/physical network (directly connected if you like). Because it doesn't have a default gateway it doesn't know to forward outgoing packets to the router, the router will inspect the outgoing packets and forward them on dependant on it's routing table.

HEADRAT
 
When I got broadband installed I plugged in my modem to the wall and then into my PC.

It all auto-configured itself and I can browse the net.

I need to apply for a job in networking now because I'm so pro.
 
What you should have distinguished between is larger enterprise networks using a variety of Cisco hardware/software and smaller office, Windows based, networks using standard routers, hubs or switches and software firewalls.
 
What you should have distinguished between is larger enterprise networks using a variety of Cisco hardware/software and smaller office, Windows based, networks using standard routers, hubs or switches and software firewalls.

Actually, the lack of a default gateway setting would have given the same effect regardless of networking kit and scale of enterprise.

However, the fact that he listed ACLs to me would have meant enterprise grade kit.
 
So you've read a few things on the web and now you think you understand them, I've just read a couple of interesting articles on brain surgery doesn't make me a brain surgeon does it!

Here's a very easy test question for you, you have server on a subnet behind a router, the server is able to ping the router but not able to ping anything on the internet. The server is able to ping other machines in the subnet and visa versa. Even thought the ACL's are open nothing from the internet can connect to the server even though the webserver is running.

Q. What would be the first thing you would check?

HEADRAT

Sounds to me like there aren't any routing table entries configured for that particular subnet?

Sorry. :p Just testing my very rusty CCNA knowledge!

Edit: Gah, just noticed the answer is above. Damn me for not reading the whole thread first!
 
Last edited:
Back
Top Bottom