SteveO86 wrote: » So the company I work for is looking for an architect, we've had quite a few people come in for the position. So far it's been pretty amusing, and I've even had one interviewee get a little snippy with me and my co-worker. (I'm not applying for this position just doing the interview with our director..) This position is suppose to be above me, a pure technical position no management. So do you think it's too much to ask that I expect this architect to be smarter then me? I mean he is suppose to be someone I can turn to instead of me banging my head against the desk till I figure something out.. I really feel like I'm asking pretty basic questions to.. 1. What routing protocol do you run to a service provider. 2. Name me few BGP path attributes 3. Why do we break OSPF up into areas. 4. Give me a few OSPF area types. 5. What's the purpose of IKE Phase1 and 2 (Those are just few, and I'll go a big more in depth into those) Basic stuff, the problem is I've had people come in that can barely answer 2 of those questions correctly. (and a few of them mentioned they passed their CCIE-Written) But should I be expecting too much for an architect type position? I'd really like to think an architect should be able to run circles around me and teach me something.... (I'm expecting to have a deep broad knowledge of OSPF, BGP, IPSec, and routing in general.)
jamesp1983 wrote: » A decent architect should be able to easily answer those questions with little effort. Ask him more in depth questions about technologies that your company considers important. I had a preliminary phone screen with a recruiter from a large ISP who asked me what the well-known mandatory BGP attributes were. That was within 3 minutes of talking to me. It was for a high level network engineer position. Make sure you really dig into him/her.
NOC-Ninja wrote: » Break time from lab. Let me take a stab on this. 1. What routing protocol do you run to a service provider. BGP 2. Name me few BGP path attributes I remember: weight as path local pre MED 3. Why do we break OSPF up into areas. To help lessen the load on the routers due to ospf calculation 4. Give me a few OSPF area types. backbone stub totally stub nssa 5. What's the purpose of IKE Phase1 and 2 I dont remember but I know its about key and authentication. I have to read it again.
SteveO86 wrote: » I just throw in the IKE question to break up the routing. (That and we work with a lot of VPNs) - I'm looking for something broad like ISAKMP key exchange in Phase 1 and IPSec SA negotiation in phase 2.. For 3 I'm either looking for what you said or to cut down on OSPF LSA's, this question will usually spawn a few others.
NOC-Ninja wrote: » ohh those types 1 to 7. I was about to ask you before if you were talking about LSA's. Ill probably fail you interview.lol
SteveO86 wrote: » Nah, your answers would have been accepted, on top of the answers I'm also looking for an understanding of the technologies. I wouldn't go that in depth unless the interviewee was overly arrogant. (Which has happened). I do like your idea of the open ended questions.. I might have to implement that somehow. Of course I'm not the only one that has to give the thumbs up, I just provide the technical side of the interview
NOC-Ninja wrote: » lol Yeah. I recommend those open ended questions because I went through them. It changed me in a good way. After going through an open ended questions, I start asking myself if I really knew the technology and if I deserved my certs. I had to re read again and really understand it. Now, I always ask myself every time i read a subject, " explain to me how (stp,ospf,bgp,eigrp,etc) works?". From there, I can really tell which one is my weakness and I read again and wipe my weakness. Like most of us here, I do this because I love learning and I would personally be disappointed to myself if i missed 1 question, like your IKE. lol
reaper81 wrote: » Using OSPF areas to lessen load on routers is not really a valid reason any longer. They can easily handle the load. I know service providers that run an entire network in area 0 (200+ routers). You can say what you want about the design but it works.