write a review
back | Posted on November 28, 2007 at 09:26 AM for Solaris Networking | |||||||||
|
Number of Interviewers:
8
Total Hours Interviewed: 8 Interview Comments: Wow was this unnecessarily long. I met one of the developers at the career fair, and was called for a phone interview, which lasted for about an hour. Then, I received an email asking me to come on-site. Most of the on-site interviewers were very nice and polite. Towards the end of the day I got to meet the manager of the team, and he wasn't so nice. He questioned why I was there, my lack of experience with networking, etc. He lightened up at the end though - I think he was just trying to give me a hard time. Overall though, the position seemed interesting but the place seemed dead. Not sure if I would have wanted to come there every single day. My biggest complaint was that the darn thing lasted for 8 hours! I did not expect that at all. Pretty much every person I spoke to asked me the same questions (and I returned the favor), so I have no clue why it's a day-long affair. One of the guys who interviewed me said that they used to last two days. I have no idea why. First came the phone interview, where I talked to two (really cool) guys. They asked me all sorts of good stuff. We covered IPC, memory management, synchronous/asynchronous IO, system calls, etc - all that fun OS stuff. They seemed happy with my answers and I was called for an on-site interview. On-site, the interviewers just kept coming one after another. There were so many questions (lots of repeats) that I can't even begin to enumerate them here. Most had to do with (duh) networking. When I came in, I was given around 5 questions on paper. Some of them were quite easy: 1. find the bug in the code 2. find the deadlock 3. sketch the calls between a client/server (i.e. socket(), accept(), listen(), etc.) Others were easy and not memorable. In any case, you're given about 15-20 minutes to figure all this out and write it on paper, which was enough time. Then came the barrage of conference calls. Each person asked the standard questions about my resume, my work experience, my classwork, and a very few tech questions. One non-tech question I was asked was to figure out the depth of a barrel at a distance using only pebbles. There's no right/wrong answer here - just wants to know how you think. Most of the other interviewers kept asking the same questions about my resume, etc. The interview wasn't really that hard - it was just ridiculously long. I was there for 8 hours - the last person took pity and just asked me one question, after which she said 'You must be exhausted - do you have any questions for me?' No - ok thanks. This was at around 5pm! Know your networking stuff, know your resume very well, and be ready to talk through any problem-solving activities they may ask. The phone interview was probably the toughest part, so you should know all the OS concepts and be ready to chat about them! Finally, I was asked questions about Solaris - my experience with it, etc. Should definitely read up on it a bit - take a look at their OpenSolaris project - was asked quite a few questions on that. A good chunk of their source code is up there - go through it and see if there's something you can pick out to talk about. They will ask. |
||||||||
| Posted on November 28, 2007 at 09:56 AM for Engineer for Project Blackbox | |||||||||
|
Number of Interviewers:
4
Total Hours Interviewed: 4 Interview Comments: I was just contacted by a recruiter who set up the interview - they already had my resume. I wasn't terribly interested in this position since it was a hybrid between engineering and support. The role was not well defined at all since it was a new group, but the project did receive some publicity on ZDNN (the 'data center in a box' project). I didn't seem particularly interested in the position (didn't even send thank you letters) and we parted ways. I wasn't really asked any technical questions for this position. The position/my responsibilities weren't clear at all, but they did manage to ask me questions about my work & class experience, and go through my resume. Overall, don't stress about this interview. They were pretty casual and I felt right at home! Like I said, the interview was pretty easy. Be ready to talk about your experience, your goals, etc. Nothing technical really. |
||||||||