So, I've been in contact with a Microsoft recruiter since 2007, and have been waiting for my chance at an interview. Now that I've got Nortel on my resume, Microsoft has offered to have me come in for an interview. Typically I do very well in interviews, so I'm excited for the opportunity.
Newby, maybe your dad could give me a good word! :P
My dad's on his way out. I doubt that. That, and you're in line with MyndFyre for the same reason. :P
For what position are you interviewing for?
Skywing, I'm unaware of anything more specific than just Software Development Engineer. They've spoken to me about several of their projects that they've got going on, inlcuding something called Photosynth, as well as Silverlight. I doubt I'd be put on either of those projects since they're both well off the ground. I won't really know much more until this upcoming Thursday when I go into their office.
Newby, hehe I was just kidding. I've been plugging away at this recruiter for about a year. I know I'll do fine. :)
Quote from: warz on October 31, 2008, 10:11:33 PM
Skywing, I'm unaware of anything more specific than just Software Development Engineer. They've spoken to me about several of their projects that they've got going on, inlcuding something called Photosynth, as well as Silverlight. I doubt I'd be put on either of those projects since they're both well off the ground. I won't really know much more until this upcoming Thursday when I go into their office.
Newby, hehe I was just kidding. I've been plugging away at this recruiter for about a year. I know I'll do fine. :)
so i herd u liek mudkip?
i've got no clue what mudkip is :p
warz: Which team, or do you not know?
Well, like I said - I don't know, yet. I'm sure by this upcoming Thursday I'll know everything.
My friend is flying up to Washington to interview for an internship position this weekend. I'm not sure if she'll be in contact, but I'll definitely be asking her how it went if she is.
I think Microsoft is one of the companies that sticks interviewees with moderately tough algorithms problems. I'm guessing you've been reading up on these sorts of things, but here's a good example:
You have a car with an empty tank that you can move to any point on a circular track with no effort. Gas cans which have an arbitrary amount of gas in each can (e.g., one can have 1 gallon, another can have 100 gallons) are placed around the track in arbitrary positions. The total amount of gas in all the cans is just enough to get you all the way around the track. Give an algorithm to find the point at which you can start your car such that you'll make it one lap.
The naive algorithm is O(n^2). There's a fairly clever solution that allows you to get it in O(n).
This was a question that was asked by Microsoft a few years ago. An alumni of the CS department here who now works at MS was asked that during his interview, apparently. I wasn't sure I recognized his name, but if I remember correctly, he also interned there for a summer or two before he graduated.
Quote from: Sidoh on November 01, 2008, 04:04:24 AM
My friend is flying up to Washington to interview for an internship position this weekend. I'm not sure if she'll be in contact, but I'll definitely be asking her how it went if she is.
I think Microsoft is one of the companies that sticks interviewees with moderately tough algorithms problems. I'm guessing you've been reading up on these sorts of things, but here's a good example:
You have a car with an empty tank that you can move to any point on a circular track with no effort. Gas cans which have an arbitrary amount of gas in each can (e.g., one can have 1 gallon, another can have 100 gallons) are placed around the track in arbitrary positions. The total amount of gas in all the cans is just enough to get you all the way around the track. Give an algorithm to find the point at which you can start your car such that you'll make it one lap.
The naive algorithm is O(n^2). There's a fairly clever solution that allows you to get it in O(n).
This was a question that was asked by Microsoft a few years ago. An alumni of the CS department here who now works at MS was asked that during his interview, apparently. I wasn't sure I recognized his name, but if I remember correctly, he also interned there for a summer or two before he graduated.
Aha, the classic Interview 2.0 (http://thedailywtf.com/Articles/Riddle-Me-An-Interview.aspx)!
The kinds of questions like the one I gave are a testament to how strong your problem solving/algorithmic skills are, which is vitally important in a number of roles at companies like MS. The ones in the article you linked seem like useless "think outside the box" questions. I've heard that some interviewers ask these kinds of questions, but at an info session with Google about a month ago, they said the interviewers were no longer allowed to ask those kinds of questions.
I don't at all think that question is useless.
Well, whether or not that question is useful strongly depends on the job. I definitely couldn't solve it, and I'm awful at coming up with "good" algorithms. But, how often does that come up in day to do development? Generally, if you use anything but a simple algorithm, your code ends up more confusing without, in most cases, gaining anything.
Obviously that isn't true in every case, just like you said, but eh? :)
I like useless "think outside the box" questions better, since I generally already know the answer to all the common ones. :)
Quote from: iago on November 01, 2008, 03:17:43 PM
Well, whether or not that question is useful strongly depends on the job. I definitely couldn't solve it, and I'm awful at coming up with "good" algorithms. But, how often does that come up in day to do development? Generally, if you use anything but a simple algorithm, your code ends up more confusing without, in most cases, gaining anything.
I think I pretty much said the same thing in the first sentence. If you're just going to be a code monkey, then strong algorithmic skills probably aren't that important. If you're working on something like compilers, operating systems, data mining, parallel programming, pattern analysis, anything mathy, etc, your algorithmic skills and familiarity with data structures is going to make or break the interview.
I call BS on the "simple algorithm" statement. Naive algorithms are often disgustingly worse than cleverer solutions. This is true even in obscure problems that probably haven't manifested themselves enough to be written about. If you're working with small samples, then it clearly doesn't matter. However, when you're working with huge datasets (and there are plenty of jobs where this is the case), it's obvious that implementing naive algorithm after naive algorithm is going to produce a really crappy, slow product.
This is an aside, but: I enjoy finding algorithms for tough problems much more than implementing solutions. :)
I've been through an interview just like this for Nortel. They ask questions that you don't quite expect to hear. I did very well at the Nortel one, though, because I was able to talk my way through the problem. That's all they want to figure out during these interviews. They want to see if a) you'll fit in with the team, b) you're able to do the job. The answer to these interview questions are going to make or break you during the interview if you're able to think out loud, and if possible draw what you're thinking on a white board, or something.
I prefer these "interview 2.0"s over other interviews because I think they're more my style. I'm much better at mapping my way to a conclusion than I am at coming up with algorithms on the spot.
Being able to code an algorithm, or whatever you're both stressing, isn't necesarilly of high importance during an interview if you can convey the theory behind the algorithm, or just explain what it'd do. Psuedocode is typically fine during these, and from the people I've spoken to that recently interviewed have told me that that's the case with Microsoft, also. It's Microsoft - they understand there's infinite amounts of references online, they're not going to expect you to be a human computer, but they'd like to know that you can use one to find the answers you're looking for.
edit: The thing that can be stressful about MS interviews is that they're not scheduled. You go to one person, and talk for awhile, and then get a 10 minute break, during this break they discuss if they think you have any weaknesses, or whatever, if the next interviewer will try to find out if this is true or not. Your interview can end early if they don't think you're a fit, or it could go on for 4-5 different interviewers if you're doing well. :)
Quote from: warz on November 01, 2008, 03:35:37 PM
I've been through an interview just like this for Nortel. They ask questions that you don't quite expect to hear. I did very well at the Nortel one, though, because I was able to talk my way through the problem. That's all they want to figure out during these interviews. They want to see if a) you'll fit in with the team, b) you're able to do the job. The answer to these interview questions are going to make or break you during the interview if you're able to think out loud, and if possible draw what you're thinking on a white board, or something.
I prefer these "interview 2.0"s over other interviews because I think they're more my style. I'm much better at mapping my way to a conclusion than I am at coming up with algorithms on the spot.
Being able to code an algorithm, or whatever you're both stressing, isn't necesarilly of high importance during an interview if you can convey the theory behind the algorithm, or just explain what it'd do. Psuedocode is typically fine during these, and from the people I've spoken to that recently interviewed have told me that that's the case with Microsoft, also. It's Microsoft - they understand there's infinite amounts of references online, they're not going to expect you to be a human computer, but they'd like to know that you can use one to find the answers you're looking for.
edit: The thing that can be stressful about MS interviews is that they're not scheduled. You go to one person, and talk for awhile, and then get a 10 minute break, during this break they discuss if they think you have any weaknesses, or whatever, if the next interviewer will try to find out if this is true or not. Your interview can end early if they don't think you're a fit, or it could go on for 4-5 different interviewers if you're doing well. :)
We were "stressing" over the importance of problem solving skills. I don't think we were talking about the importance of how good you are at implementing an algorithm.
Sounds like a fun time. Good luck on the interview.
I think I'll probably apply to Microsoft when they start accepting applications for summer interns (again). The aforementioned friend who's interviewing this weekend is trying for an internship too, but apparently they accept applications in the fall and in the spring. I already have three applications into other places (NASA, DoD, Lockheed Martin), and I think I'll probably apply to Google when they open up applications.
What's your reason for being interested in Microsoft, warz? I mean I've definitely heard great things, but is there something specific that really attracts you to a job there? I'm still kind of deciding where I want to work this summer (and I'm by no means assuming I'll be accepted to all the places I apply, lol).
Quote from: Sidoh on November 01, 2008, 03:34:13 PM
I think I pretty much said the same thing in the first sentence. If you're just going to be a code monkey, then strong algorithmic skills probably aren't that important. If you're working on something like compilers, operating systems, data mining, parallel programming, pattern analysis, anything mathy, etc, your algorithmic skills and familiarity with data structures is going to make or break the interview.
And I agree, but at the same time the majority of developers probably aren't working on those, at least, not right off the bat (and by 'operating systems', I'm assuming you mean the deep kernel stuff, not, say, the shutdown menu).
Quote from: Sidoh on November 01, 2008, 03:34:13 PM
I call BS on the "simple algorithm" statement. Naive algorithms are often disgustingly worse than cleverer solutions. This is true even in obscure problems that probably haven't manifested themselves enough to be written about. If you're working with small samples, then it clearly doesn't matter. However, when you're working with huge datasets (and there are plenty of jobs where this is the case), it's obvious that implementing naive algorithm after naive algorithm is going to produce a really crappy, slow product.
And I call shenanigans on you! :P
In all my years of programming, I've never had to write a "clever algorithm", except for schoolwork. I'm not saying that you never use them, for example in the cases you mentioned at the top, but those definitely aren't the norm anywhere. Another place they're useful is in a GIS solution (since I'm working with one of those at the moment, it's ont he top of my mind). But yeah, certainly not common in general.
Also, in terms of making a crappy/slow product, their interviewing obviously isn't working ;)
Quote from: Sidoh on November 01, 2008, 03:34:13 PM
This is an aside, but: I enjoy finding algorithms for tough problems much more than implementing solutions. :)
Nerd! :P
Quote from: iago on November 01, 2008, 03:55:15 PM
And I call shenanigans on you! :P
In all my years of programming, I've never had to write a "clever algorithm", except for schoolwork. I'm not saying that you never use them, for example in the cases you mentioned at the top, but those definitely aren't the norm anywhere. Another place they're useful is in a GIS solution (since I'm working with one of those at the moment, it's ont he top of my mind). But yeah, certainly not common in general.
Also, in terms of making a crappy/slow product, their interviewing obviously isn't working ;)
I guess I should clarify -- In ALL of the jobs I'm interested in working, algorithmic/problem solving skills will be critical. :)
Honestly, I think there are far more jobs where making use of clever algorithms is hugely beneficial or necessary than you're saying.
Quote from: iago on November 01, 2008, 03:55:15 PM
Nerd! :P
Code monkeying is boring. Seriously. :(
@warz: in case you miss it, I had a question for you on the previous page
Quote from: Sidoh on November 01, 2008, 03:54:07 PM
I think I'll probably apply to Microsoft when they start accepting applications for summer interns (again). The aforementioned friend who's interviewing this weekend is trying for an internship too, but apparently they accept applications in the fall and in the spring. I already have three applications into other places (NASA, DoD, Lockheed Martin), and I think I'll probably apply to Google when they open up applications.
What's your reason for being interested in Microsoft, warz? I mean I've definitely heard great things, but is there something specific that really attracts you to a job there? I'm still kind of deciding where I want to work this summer (and I'm by no means assuming I'll be accepted to all the places I apply, lol).
Well, aside from the fact that it's Microsoft, it's probably a more enthusiastic environment because the software you could potentially be working on has the chance to be used by millions of people. Their office is also much closer to where I live, so it'd make commuting a whole lot shorter. Microsoft was also the first place I was in contact with, but I was too late for their first round of application turn-ins. Yeah, they accept applications in the fall and spring, and probably any other time if you match an open position. Besides, Microsoft is one of those career companies if you want it to be. Would I rather work at Google? Ofcourse, their office setup and stuff sounds like a blast but they're impossible to get ahold of. I've sent in several resumes, and have applied to multiple positions over time. I've never received a response about any of them. If I was finished with college I'd probably be applying mainly to gaming companies on the west coast, because I think I'd just enjoy going to work too much. :P
I know several people that work at Lockheed Martin, actually. They say they enjoy it, but most of the stuff they work on they can't talk about. haha.
Quote from: warz on November 01, 2008, 04:35:09 PM
Quote from: Sidoh on November 01, 2008, 03:54:07 PM
I think I'll probably apply to Microsoft when they start accepting applications for summer interns (again). The aforementioned friend who's interviewing this weekend is trying for an internship too, but apparently they accept applications in the fall and in the spring. I already have three applications into other places (NASA, DoD, Lockheed Martin), and I think I'll probably apply to Google when they open up applications.
What's your reason for being interested in Microsoft, warz? I mean I've definitely heard great things, but is there something specific that really attracts you to a job there? I'm still kind of deciding where I want to work this summer (and I'm by no means assuming I'll be accepted to all the places I apply, lol).
Well, aside from the fact that it's Microsoft, it's probably a more enthusiastic environment because the software you could potentially be working on has the chance to be used by millions of people. Their office is also much closer to where I live, so it'd make commuting a whole lot shorter. Microsoft was also the first place I was in contact with, but I was too late for their first round of application turn-ins. Yeah, they accept applications in the fall and spring, and probably any other time if you match an open position. Besides, Microsoft is one of those career companies if you want it to be. Would I rather work at Google? Ofcourse, their office setup and stuff sounds like a blast but they're impossible to get ahold of. I've sent in several resumes, and have applied to multiple positions over time. I've never received a response about any of them. If I was finished with college I'd probably be applying mainly to gaming companies on the west coast, because I think I'd just enjoy going to work too much. :P
Ah, cool. Yeah, those are the answers I kind of expected. They're definitely awesome reasons -- reasons I'd want to work there as well. I'm not sure what the deal is with Google. I've met several people who graduated from here who now work for them. I'm not sure if it's a matter of getting to know someone in the office where the job you're applying for is or something, but I don't know. They said they get over 1000 applications for internships a year or something. It was a little disheartening, lol.
lol, gaming companies would be pretty cool. I would imagine working on something like WoW would be really fun for a lot of the same reasons you mentioned you'd like to work at MS.
Quote from: warz on November 01, 2008, 04:35:09 PM
I know several people that work at Lockheed Martin, actually. They say they enjoy it, but most of the stuff they work on they can't talk about. haha.
I worked at LM last summer. It was pretty awesome. The office I worked at was really small (200ish people), though, and all of their projects involved logistics, which I didn't find especially interesting (although there were some really cool approaches to some of the hard problems they were faced with). The one I put as my "first choice" is here in Colorado and is much bigger and I think is involved with what I'd consider more interesting projects. All my work was "unclassified", but I definitely put my signature at the end of a long NDA, lol. I think most people who work there get security clearances at some point; it's just not so useful for them to get them for interns (I think they cost the government in excess of $30,000 or something?). The job I applied for at the DoD requires a security clearance, though, lol.
Quote from: Sidoh on November 01, 2008, 04:48:53 PM
Quote from: warz on November 01, 2008, 04:35:09 PM
Quote from: Sidoh on November 01, 2008, 03:54:07 PM
I think I'll probably apply to Microsoft when they start accepting applications for summer interns (again). The aforementioned friend who's interviewing this weekend is trying for an internship too, but apparently they accept applications in the fall and in the spring. I already have three applications into other places (NASA, DoD, Lockheed Martin), and I think I'll probably apply to Google when they open up applications.
What's your reason for being interested in Microsoft, warz? I mean I've definitely heard great things, but is there something specific that really attracts you to a job there? I'm still kind of deciding where I want to work this summer (and I'm by no means assuming I'll be accepted to all the places I apply, lol).
Well, aside from the fact that it's Microsoft, it's probably a more enthusiastic environment because the software you could potentially be working on has the chance to be used by millions of people. Their office is also much closer to where I live, so it'd make commuting a whole lot shorter. Microsoft was also the first place I was in contact with, but I was too late for their first round of application turn-ins. Yeah, they accept applications in the fall and spring, and probably any other time if you match an open position. Besides, Microsoft is one of those career companies if you want it to be. Would I rather work at Google? Ofcourse, their office setup and stuff sounds like a blast but they're impossible to get ahold of. I've sent in several resumes, and have applied to multiple positions over time. I've never received a response about any of them. If I was finished with college I'd probably be applying mainly to gaming companies on the west coast, because I think I'd just enjoy going to work too much. :P
Ah, cool. Yeah, those are the answers I kind of expected. They're definitely awesome reasons -- reasons I'd want to work there as well. I'm not sure what the deal is with Google. I've met several people who graduated from here who now work for them. I'm not sure if it's a matter of getting to know someone in the office where the job you're applying for is or something, but I don't know. They said they get over 1000 applications for internships a year or something. It was a little disheartening, lol.
lol, gaming companies would be pretty cool. I would imagine working on something like WoW would be really fun for a lot of the same reasons you mentioned you'd like to work at MS.
Quote from: warz on November 01, 2008, 04:35:09 PM
I know several people that work at Lockheed Martin, actually. They say they enjoy it, but most of the stuff they work on they can't talk about. haha.
I worked at LM last summer. It was pretty awesome. The office I worked at was really small (200ish people), though, and all of their projects involved logistics, which I didn't find especially interesting (although there were some really cool approaches to some of the hard problems they were faced with). The one I put as my "first choice" is here in Colorado and is much bigger and I think is involved with what I'd consider more interesting projects. All my work was "unclassified", but I definitely put my signature at the end of a long NDA, lol. I think most people who work there get security clearances at some point; it's just not so useful for them to get them for interns (I think they cost the government in excess of $30,000 or something?). The job I applied for at the DoD requires a security clearance, though, lol.
I'd be careful with those; some of the employee agreements out there in the world are pretty nasty, to the effect of claiming ownership of any ideas you come up with both inside or outside of work.
Quote from: Skywing on November 01, 2008, 05:14:39 PM
I'd be careful with those; some of the employee agreements out there in the world are pretty nasty, to the effect of claiming ownership of any ideas you come up with both inside or outside of work.
Heh, definitely. I'm pretty sure theirs is pretty nasty, but when talking to people, it sounded like it was only to allow them to "cover all their bases". Regardless, that was definitely one of the things that made me very uncomfortable about working there. I like owning my ideas. :(
It was just an internship, though, so now my ideas are mine again! :D
Nortel had me sign something like that - they own any ideas I come up with at work. lol.
Quote from: Skywing on November 01, 2008, 05:14:39 PM
I'd be careful with those; some of the employee agreements out there in the world are pretty nasty, to the effect of claiming ownership of any ideas you come up with both inside or outside of work.
Symantec was like that, that's one of the main reasons I left.
My current job (Government of Manitoba) didn't require any kind of IP agreement, or even an NDA. All I had to sign was a conflict of interest thing.
(I think an NDA is implied by the nature of my work, though, but it's not official)
Quote from: Sidoh on November 01, 2008, 05:18:36 PM
Quote from: Skywing on November 01, 2008, 05:14:39 PM
I'd be careful with those; some of the employee agreements out there in the world are pretty nasty, to the effect of claiming ownership of any ideas you come up with both inside or outside of work.
Heh, definitely. I'm pretty sure theirs is pretty nasty, but when talking to people, it sounded like it was only to allow them to "cover all their bases". Regardless, that was definitely one of the things that made me very uncomfortable about working there. I like owning my ideas. :(
It was just an internship, though, so now my ideas are mine again! :D
I was more meaning Lockheed Martin and other companies that do defense-related work.
Quote from: Skywing on November 01, 2008, 08:19:56 PM
Quote from: Sidoh on November 01, 2008, 05:18:36 PM
Quote from: Skywing on November 01, 2008, 05:14:39 PM
I'd be careful with those; some of the employee agreements out there in the world are pretty nasty, to the effect of claiming ownership of any ideas you come up with both inside or outside of work.
Heh, definitely. I'm pretty sure theirs is pretty nasty, but when talking to people, it sounded like it was only to allow them to "cover all their bases". Regardless, that was definitely one of the things that made me very uncomfortable about working there. I like owning my ideas. :(
It was just an internship, though, so now my ideas are mine again! :D
I was more meaning Lockheed Martin and other companies that do defense-related work.
Heh, yeah.
Not that this makes it any more excusable, but I was working in an IRAD department, so the NDA is really the only way they can protect "trade secrets". People working on contracts typically have security clearances, which I'm sure have all other kinds of obligations of secrecy.
I guess my friend got an offer. Man, they pay well. $5,400/month for an internship? Damn.
That's nice. It's less than what I make at Nortel, though. =( I should also note that taxes suck.
Quote from: warz on November 05, 2008, 07:14:27 PM
That's nice. It's less than what I make at Nortel, though. =( I should also note that taxes suck.
It's a summer internship and she has no work experience, lol
Quote from: Sidoh on November 05, 2008, 07:16:12 PM
Quote from: warz on November 05, 2008, 07:14:27 PM
That's nice. It's less than what I make at Nortel, though. =( I should also note that taxes suck.
It's a summer internship and she has no work experience, lol
You may be surprised then to learn that that is the average pay for these kinds of jobs. I haven't talked to an employee of a non internet startup programming company that makes less than this average. It's a tough job if you think about it. You're constantly doing critical thinking, problem solving, working with teams constantly... you're never done. You're staring at a monitor all day, and have the humming of computers making you go insane subconciously. They're not going to find anyone willing to do this after all the schooling for much less. ;) These companies know that, too, and they've got no problem paying the price.
Guess it depends where you are.... We pay our interns ~$12/hr. :P
Hm. My co-op will be at least $14/hr, but I'm shooting for the $18 range.
Quote from: MyndFyre on November 06, 2008, 12:56:05 AM
Guess it depends where you are.... We pay our interns ~$12/hr. :P
Our students get $19/hour, and aren't worked very hard. Plus, they get to hang out with me, that's an extra bonus! :)
Quote from: warz on November 05, 2008, 11:05:24 PM
Quote from: Sidoh on November 05, 2008, 07:16:12 PM
Quote from: warz on November 05, 2008, 07:14:27 PM
That's nice. It's less than what I make at Nortel, though. =( I should also note that taxes suck.
It's a summer internship and she has no work experience, lol
You may be surprised then to learn that that is the average pay for these kinds of jobs. I haven't talked to an employee of a non internet startup programming company that makes less than this average. It's a tough job if you think about it. You're constantly doing critical thinking, problem solving, working with teams constantly... you're never done. You're staring at a monitor all day, and have the humming of computers making you go insane subconciously. They're not going to find anyone willing to do this after all the schooling for much less. ;) These companies know that, too, and they've got no problem paying the price.
heh, true. I think I was only getting paid like $3,000/month at LM. However, they did give me $900/month for living costs. The other interns were paid better because they were further in school (even though I was probably among the most competent of them, heh). I've heard Google and Microsoft pay the best for internships (out of the commonly discussed companies, of course). However, I still think I'd prefer working at the DoD. I think they pay ~$25/hour, which is pretty good.
Quote from: rabbit on November 06, 2008, 09:05:12 AM
Hm. My co-op will be at least $14/hr, but I'm shooting for the $18 range.
Yeah, go as high as you can! Or work for Microsoft and get paid $33.75/hour...
I wonder if that's a "salary". That'd be kind of lame. Hourly work is awesome. Overtime pay kicks ass! :D
Quote from: iago on November 06, 2008, 10:05:17 AM
Quote from: MyndFyre on November 06, 2008, 12:56:05 AM
Guess it depends where you are.... We pay our interns ~$12/hr. :P
Our students get $19/hour, and aren't worked very hard. Plus, they get to hang out with me, that's an extra bonus! :)
Sweet! Do you convert them to RPG playing vegans? :D
Drink getting slaves. :)
Well, I just got finished with the interview. I think everything went very well. They didn't ask any difficult questions, really. I was expecting questions like "can you explain polymorphism to us" and stuff - didn't get any of those. There was one tricky question that asked me to code up a method that'll plot coordinates on a graph, and I think the purpose was to end up with portions of a circle, but not the entire circle? I couldn't understand the interviewer too well because he had a heavy indian accent, and initially I thought he wanted me to graph out the arm of a clock as it rotates around the circle. So I started thinking out loud on how to do that, and he stopped me and said "no i mean like parts of the circle", so I kept asking questions trying to clarify by we kind of hit a language barrier wall, maybe. I don't think he was explaining the question very well... because I still don't know what he really wanted me to do.
Other than that one question I think I blew the interview away. Now I just wait for a response! :P
I asked about their teams, too, and he said there's so many and that they don't determine which one you'll be on until you get to that point in the interview process. He said I'll be shown the different teams, though, and I'll be able to choose.
Cool! Hope you get an offer.
My friend decided on the Outlook team, I guess. She got offers from Outlook/Word, which were the only two she interviewed for. You're gonna have to give her a hard time for me if you end up working near her.
Well, unlike your friend, Sidoh, they seem to be taking their sweet time sending me a response. :P
Your friend said she got a response the Monday following her interview, which was on Thursday. Sounds like her interview was a lot shorter than mine, and much much easier. Her coding question involved something as simple as looping through a char array and counting the number of occurences of 'a', or some other letter.
It probably doesn't help that my recruiter is on vacation until Thursday. I'm about to start pulling my hair out over here. :P
Quote from: warz on November 11, 2008, 10:32:08 PM
Well, unlike your friend, Sidoh, they seem to be taking their sweet time sending me a response. :P
Your friend said she got a response the Monday following her interview, which was on Thursday. Sounds like her interview was a lot shorter than mine, and much much easier. Her coding question involved something as simple as looping through a char array and counting the number of occurences of 'a', or some other letter.
It probably doesn't help that my recruiter is on vacation until Thursday. I'm about to start pulling my hair out over here. :P
Like I said, she's interviewing for an internship position. I assume you're applying for fulltime? The interview probably should be a lot more rigorous.
That was the phone interview, I think. The real interview had more involved questions, from what I heard. They weren't like super hard, but definitely harder than that question.
Well, I always just figure stuff like this is karma for me going into spy-mode and destroying rosethorn's clans back in the day on bnet. Oh, and joining +D+ with the sole purpose of stealing one of Spht's friend's cross-bow on Diablo 2 - which I did. That kind of stuff.