Interviewing for positions at Microsoft: Part 2
In my last post, I spent most of the time talking about preparation before the interviews. Most people really want to know what an actual interview day is like at Microsoft. Well, you always get what you ask for when you are dealing with us! I am giving you some information here about what a typical day might feel like. I hope this helps out when you are preparing for your big interview day…
The day or night before the interview
If you arrive the day or night before the interviews and have some down time, it might be a good idea to do a practice run to the interview location if you are planning on driving yourself. I did this the night before my interviews and it took the nerves out of trying to find my way around an unfamiliar city. If you don’t have time to do this, you might want to ask the concierge or front desk manager at your hotel about traffic conditions from the location you are to the location of your interviews. You can then plan how much time you will need in the morning and give yourself a few minutes extra if you run into traffic or an accident.
The other transportation option you have is using a taxi. The taxi option is really appealing to those people that know they are going to be too nervous to drive. The taxis we use are also very familiar with getting candidates to and from our building so that can take the pressure off. Gretchen mentioned that she chose this option and it was really helpful to her. However, if you are relying on another form of transportation make sure you have confirmed your transportation the day/night before you need it. The last thing you want is to have everything else prepared and then forget to confirm your taxi.
I make a big deal out of this because arriving late for your interviews can be unnerving and it can also impact the time table for the rest of the interview day. We try to reduce travel time as much as possible by providing you with accommodations close to your interview location; however it never hurts to be prepared for any potential roadblocks!
Typically, I recommend that people arrive for their interviews 15 minutes before the start time that the recruiting coordinator has indicated. This allows you time to find parking, get yourself situated and if you need to complete any paper work prior to the recruiter meeting with you. Make sure you allow for this in your travel time whether you are driving or using an alternate form of transportation.
Oh, I thought this was a given but I might as well say it anyway – get a good nights sleep! It can be tempting to check out the local sites or have dinner with your friends the night before, but you may want to hold off on doing this until after your interviews are over. I have had a lot of completely wiped out people come in for interviews because they spent the night out on the town. Consequently they haven’t preformed all that well during the course of the interviews themselves.
Interview day morning
This may sound a little motherly, but you should try to have a good breakfast the morning of your interviews. I usually recommend eating something with protein vs. high carbohydrates. I don’t know about you but if I have a huge breakfast of pancakes, I am usually toast by 11 am (no pun intended :). If you get really nervous and can’t think about eating, try to at least have a protein bar or some fruit. The one thing you probably should avoid is loading up on caffeine as this can really exacerbate any nervous feelings you have. And, I don’t know if I should say this or not, but caffeine is a diuretic and you might feel the effects of it all day.
I once had a candidate spill an entire cup of coffee on me, my computer and all my files. Hey, no biggie this happens, right? I later found out though that this was his 3rd or 4th cup of coffee that day and it was only 9 am! I figure you can guess the moral of this story.
Anyway, most of our interview days start in the morning, so eating a little something will help carry you through your first few interviews until lunch. I promise you will feel and perform better throughout the course of the day.
Arriving on campus
Okay, so you have done your dry run to campus or you have allowed extra travel time to get to the interview location. Whatever the case, you have finally arrived! The first thing you will do is walk into our building’s main lobby area and up to the receptionist’s desk. The recruiting coordinator will have indicated a recruiter that you should meet with and you should ask for this person. Depending on how early you arrive, feel free to take a seat and a few minutes to relax before meeting your recruiter. You’ll be sitting with other interview candidates at this point and it should be comforting to know there are other people feeling and experiencing the same things you are!
The recruiter will come to the lobby to pick you up at the designated time. If you find you are waiting 10-15 minutes past the time assigned for the interviews, then you should make sure the receptionist is aware of this so they can locate your recruiter.
The recruiter will take you to their office and thus begins the interview day. When I meet with candidates I use this time to cover a few different areas. First, I will let you know what you should be expecting from the interview day. I will give you the first couple of interviewers that you will be meeting with and I will also give you my contact information. Essentially, this is my time to prep you and help you be successful during the day.
I will also use this time to find out any additional information I need to know about you. For example, if we haven’t discussed compensation yet or there are other administrative details we need to get out of the way, this is the time to do it.
This is also a chance for me to interview you again. I like doing this with candidates because it helps me to inform the rest of the interviewers on the loop what they should cover during the day. It also helps get you prepared and in the mindset for the rest of the day.
After we have had our meeting, it is time for me to send you to the product team. I will walk you to the recruiting shuttle and then send you over to your next interview location. From that point forward, your day should be on autopilot. I usually monitor the progress from my office, but if you run into any problems during the day you have my contact information.
Meeting with the team
Once you get to your next destination, you’ll ask the receptionist for the first person on your interview list. You’ll typically wait in the lobby for that person just as you did for the recruiter. The will come down and meet you and walk you to their office.
The way each interview is conducted will vary depending on the person. Usually, they will take the first few minutes to introduce themselves and tell you about their job at the company. Then they will dive right in to asking you questions. As I mentioned before, they will ask a combination of technical and non-technical questions. If you have done the preparation recommended above, you should be well prepared for the questions that might be asked. However, these are some areas where you may be asked questions:
- You resume - be prepared to discuss anything you have put on your resume with examples
- Coding questions – getting up an solving a coding question on a white board
- Testing questions
- Problem solving
- Experiential based - talking about a project that you have worked on
- Situational
- Behavioral
- Technical – explaining your understanding of a particular technology
Before you start answering questions, make sure you have all the information you need. If you are unclear on the problem you are being asked to solve or unclear on the question itself; make sure to ask clarifying questions. Many times you will be given questions with ambiguous information and it is your job to make sure you have all the information you need in order to actually answer the question.
Interviewing is a two way street – always keep this in mind. You are also interviewing us to determine if this is a group, position, and company that can support your short term and long term career goals. Don’t be afraid to these types of questions!
Between each interview you will be waiting in the lobby for the next person to come and get you. You should use this time to regroup and review your performance in the last interview. Self assess where things went well and determine what you can do better in the next interview.
A special note on the lunch interview: Most of our candidates at Microsoft will have some sort of a lunch interview. These interviews are longer then the others on the loop and last for about 90 minutes. Usually the interviewer will take the first 30-45 minutes to eat lunch and ask questions that don’t require working on a white board. Usually they will take you to lunch at one of our fine cafeterias on campus or to a local restaurant. If you have certain dietary requirements, let the recruiting coordinator know in advance. It is really important to stay in your interview mindset during lunch – these are still interviews though they may feel more casual. That said, I remember not eating a whole lot during my lunch interview so you may want to bring a snack with you to eat later in the afternoon (power bar or other protein source) to boost your energy and stave off the tummy rumbles. After taking some time to eat, you most likely will return to the interviewer’s office and finish out the rest of the conversation and interview day.
After the interviews are over
The last interviewer on your loop will let you know when you are done for the day. The recruiter should have let you know in the morning whether or not they will be meeting with you at the end of the day. Either way, you will be returning to their building to retrieve your car or get your taxi.
The recruiter should also have given you a timeline for when to expect to hear back from Microsoft on whether or not you got the position. This usually takes about 5-10 business days depending on how many other candidates are interviewing for the position. I would try to get a commitment in advance on when/if you will be hearing back from the recruiter.
Gretchen has recently posted some articles titled “Après Interview”. I would highly recommend you check these out as they may be a possible result of your interview.
Now that you are done with your interview day you should try to enjoy the rest of the time that you have in Seattle. Relax, take in the sites and tastes of the area. You never know, you could end up moving here in a couple of weeks :)
33 Comments
Ry Jones said:
You didn't talk about the AA
Mark said:
Super informative! Thanks =]
Mitch Denny said:
Traffic can certainly be a problem in the Seattle area. I've never interviewed for a job up there, but I remember missing a flight to Vancouver on the way back to Australia.
I left about two hours to get to the airport (above the checkin buffer) and there was an accident on the bridge (apparently) and the flow on effects pretty much made traffic crawl.
Moral of this story - if you are interviewing at Microsoft I wouldn't use a hotel in downtown Seattle :P
Mark said:
Based on the interviews I experienced I wouldn't always recommend this, it depends on the interviewer:
Before you start answering questions, make sure you have all the information you need. If you are unclear on the problem you are being asked to solve or unclear on the question itself; make sure to ask clarifying questions.
I agree that you need to ask questions if things are unclear, this is the way I was trained, but 2 out of the 4 interviewers did not like me asking clarifying questions when I was asked puzzle questions. They would get irritated like they were in a hurry, and kept saying each interview is only an hour so we have many more questions so let’s get moving. It was nice weather that day sunny and 75 degrees I think they wanted to get outside, they kept saying it is such a nice day here today.
One of the interviewers was from South America (Columbia), who was at times hard to understand so I needed clarification and he did not like that.
What was real tacky was my last interview; I waited 20 minutes in the lobby, and was told the long wait was because my next interviewer has a broken leg from a motorcycle accident and was in pain. I was escorted up to his office which was pretty dark for most of the interview, and there he was laid out on his couch his leg in a lace up cast and talking about his pain and asking questions. His leg was partly exposed as well so it wasn’t the most pleasant to look at. This was real distracting and awkward. I felt bad for the guy, and could not believe that Microsoft would do this to him and me.
This was so unprofessional in my opinion, how can you interview someone with a broken leg and in pain. So he got on his crutches and led me back to the lobby. I pretty much figured out I wouldn't get an offer, I mean really, do they want me to take this seriously. My recruiter sent me an email stating I would not get an offer.
What a ridiculous joke. Whoever set this up should be ashamed.
Scott Allen said:
I'm always paranoid about traffic in a stange city that I invariably end up at an interview or client site about an hour before the scheduled time. I always take something useful to read, be it background information for the day ahead, or, in the case of an interview, perhaps information about the company. If I ever have an interview at Microsoft I think I'd put all of your blog entries into my PDA for review while waiting :)
Krish said:
Mark -- Probably its one of the worst situations one could ever face. The interviewer doesn't know the importance of the time he is spending with you.
But, Some how I found most of my interviewers are so kind and pretty much good in helping the candidates. Once during my phone interview, I was having cold, and the interviewer insisted me on postponing the call to next day or to give a break of two days saying the importance of the screening. I was so happy, but finally it ended that after my all screening interviews, there was H1B cap.
But in your case, I could have talked to the recruiter about the incident and explained her/him, how disgusting the situation was and asked to consider your case. Because I have read in microsoft careers page that the recruiter is the best person to contact regarding any problem you face.
Probably you could have been little bold enough to explain your situation.And ofcourse there is nothing wrong in being frank ;-)
-- Krish
"The best thing about saying truth is that, you need not prepare for it"
zoe said:
Mark - I am sorry to hear about this experience. I hope to reassure you that I think this was a fairly out of character interview that you had at Microsoft.
Though I am not completely familiar with your interview situation, I too would agree that asking calrifying questions is very important.
What I do know is that having you interview with someone that is in pain with a broken leg (sounds like it was recent) is probably not a good idea. Microsoft isn't a place that would force an interaction like this so I can only assume that it was up to this person to continue to be at work.
Regardless, I really hope that you give this feedback to the recruiter that you have been working with. This is the only way we know about these situations and then can improve the way we interview and the experience for our candidates in the future.
Take care,
Z
Mark said:
Zoe -
This was a recent interview (end of April)for a full time position, but it was via the college recruiting process and I know both you and Gretchen have stated is different than the professional.
I didn't get to see my recruiter the day of my interview, she stated that when I come back to Building 19 ask for her but she might be in meetings, so do not wait for more than 15 minutes. I will inform her of my experience. I have also received the Microsoft recruiting survey and will include this in my response.
Thanks for the info, and good job on the Blog.
Mark
Balaji said:
Hi Zoe
Just wanted to share an experience similar to Mark's that I had last year. I had interviews with 5 people and the last one was a south american and his accent was so bad, I could hardly understand what he is asking. To one of the questions, when I tried to explain, he shot back "I know that. You dont have to explain". Well, the purpose of the interview is to check if I know the information. Not to check if he does. Well, at the end of the interview, I spoke to the recruiter and suggested that MS should start giving interview process feedback questionaire to candidates. I think that would really prevent people from having bad experiences.
Just my 2 cents..
thanks
Balaji said:
Having said that, I do feel that potential candidates should treat MS just as another company and try not to have too much expectations with respect to having a pleasant experience in interviews (My mistake number one, I think). Having a realistic attitude towards the process will help. Because every process has its own flaws.
After attending the interviews I started working more in my career and it was definitely an eye-opener for me (not that I did bad in interviews, but the last interview didnt exactly go well because of the strange attitude of the interviewer). I have grown a lot in my current company in the past one year with respect to both dev skills and otherwise. So it was helpful in that aspect.
I didnt mean to sound offending, but just letting out my steam!
:-)
Rober said:
Hi Zoe
Good post , Thanks !!
I have 3 years of experience in networking and streaming protocols. What's the better way I can apply for a position?
Shall I send resume to either you or <a title="" href="http://blogs.msdn.com/jobsblog/articles/88832.aspx" >gretchen</a>?
or Should I send my resume to recruiters who recruit for networking group? If yes, Can you please give some contact ids of the recruiters?
Thanks!!
_Rob.
Kal El said:
_Rob,
LOL! There had to be one! IMHO you should invent a new protocol, market it and hope the MS buys you out! :)
Zoe & Gretchen,
great blog, v imformative. A friend of mine interviewed with MS and relayed the interview day which is similar to your article (and his interview was about 3 years ago!).
Thanks.
Rober said:
BTW my opinion is not to ask the people's contact info, rather I meant to say why not other MS recruiters also participate in this blog and let their opinion out. May be some thing like Zoe and Gretchen advertised about their recruiting events on Exchange server and Core platform group.
Probably,this way, people will come to know the exact skills needed immediately than searching all database and finding positions.
Well, doesn't it sound good ??
Thanks!!
_Rob.
gretchen said:
Balaji - I believe we do send a survey out to people after they interview. You should definitely note this. I'm sorry you had a bad experience!
Rob - I would suggest searching for particular jobs of interest on www.microsoft.com/careers and then submitting your resume. That's the best way to get your resume to the right recruiters.
Kal El - thanks!
Rob again - :) We have tried to get other recruiters to participate in this blog. In fact, when we started it, we knew we'd be the blog owners/admins but we thought we'd have frequent guest posters from recruiting. Unfortunately, no one seems quite as interested in blogging as we do. :)
Sam said:
Hi! Thanks so much for such an informative blog and lively discussion.
I have recently applied for a techno-managerial position with Microsoft's Consulting practice. (I've applied through Microsoft's Career site as well as through my freind at Microsoft). Microsoft has similar positions open in a few cities in the US. I've applied for the position in the city I live in.
Suppose Microsoft recruiters/hiring managers like me (I'm hoping they will because I believe I have all that is required for the position). But if for some reason they don't offer me the job for the position in my city and if I showed interest in the similar position in a different city, do you think Microsoft will consider my request to help me with selling my 2-years-old house at no loss to me and also help with relocation etc so I can start my job on time? Or do you think they will prefer local candidates from those other cities to save on relocation expenses?
Thanks a lot for your help and time!
gretchen said:
Hi Sam - I don't know the specifics of that job so I can't answer that question. Across the board, Microsoft does have a great relo package, but you'd have to discus the details with recruiter for the particular role. Sorry I can't be of more help!
Paul Correia said:
This email is just for information and advice only. I've got an opportunity to interview with Microsoft next week for a TAM position in the DC area supporting Federal accounts. I was wondering if you can give me the real low down on this type of position? :
For Example:
What exactly is MS looking for in candidates for these TAM positions.
How technical is the position?
What's the interview process like for this type of position? Any of the famously wild MS questions forthcoming?
What's the day to day job really like, without the recruiter spin?
What would you recommend for Interview attire?
I'm currently working as an IT Director for the City where I live. It's got decent pay but I don't want to stay in Central Texas so I'm open for moving. However, I don't want to move into a job that is strictly desktop/phone support. I just don't want to make that mistake while moving my family, so your information and insight is defintely needed.
I just can't seem to find much information about these types of positions at MS. Can you please help with some thoughts and experiences?
zoe said:
Hi Paul,
Unfortunately, we aren't that familiar with how interviews are conducted in our field offices. I am even less familiar with the TAM position.
However, I would recommend that you ask your recruiter the first four questions you listed above. Gretchen and I won't be able to help you out with these since we don't know the TAM position.
As for interview attire, check out this article: <a target="_new" href="http://blogs.msdn.com/jobsblog/archive/2004/04/01/105933.aspx">http://blogs.msdn.com/jobsblog/archive/2004/04/01/105933.aspx</a>
It talks about what you should wear and a lot of great comments from our readers.
I am not sure if you are a first time reader, but you should also check out these articles to give you a better idea of what areas Gretchen and I recruit for and know the most about.
<a target="_new" href="http://blogs.msdn.com/jobsblog/articles/110574.aspx">http://blogs.msdn.com/jobsblog/articles/110574.aspx</a>
Hope this helps!
Mike said:
I am interviewing for a Senior Software Design Engineer position in Fargo, ND... I have had my tech screen, and had my typical interview loop (four interviews with potential colleagues, finishing with the hiring manager). I now have another interview scheduled with a Senior Director. Any insight as to what I can expect from this interview, and/or why this interview might be necessary? The only logical thing I can think of is that sine my hire involves relocation costs they might need to get a higher approval?
Thanks!
Jon said:
Question for interviewing for a PM role.
What are the interviewers looking for when they say, “Design a Timer” or “Design a Alarm Clock”. I interviewed awhile back and got mixed reactions. Are they looking for class diagrams, OO Design patterns (like in the Gang of 4 book), and so on? What methodical approach should be taken? Any help here would be great.
Jon
gretchen said:
You know, I think it really depends on what variety of PM position you are interviewing for and who is interviewing you. I know what I look for but that's not always what a seasoned PM would look for.
With me, I'm looking for someone who can demonstrate they understand the trade-offs involved in product development (budget, scheduling, resources, company vision, etc) while also demonstrating superb customer focus, creativity, and a sense of priorities. The more detail, the better.
Jon said:
Gretchen
Thanks for the info. I guess the problem is figuring out what the interviewer really wants. Seems to be a variety of approaches. For design questions I was thinking on the lines of showing the relationship between objects, modeling the different events, show that the “use cases” start with the customer and so on. I also see your point of evaluating the tradeoffs and at the same time being creative. Would it better to ask the interviewer what he/she is looking for or just give everything you can. I am guessing give everything.
Thanks!
sharad said:
Hi All,
I hope this is proper place to post my interview experience. If not, I would ask administrator to move it to appropriate place on this website..
If any one is interviewing for "network org" at msft, please read through as this may be useful..
My interview at msft was unique. I had prepared for more than 2 weeks, but all was in vain.. I was interviewed for "test engineer' post in network org.
After doing some analysis this is what i figured out..
1> Don't set your expectations abt interview and don't prepare according to your expectations of interview.
In my case, having a profound networking(telecom) experience, i had prepared in quite detail abt all networking fundamentals..Since I had worked on lots of networking technologies(some of which are used by msft), I spent a lot of time on preparing networking topics. Unfortunately I figured out after the interview that msft guys are not that smart. As a matter of fact, no one even asked abt any in depth networking related questions or even discuss abt basic fundamentals of networking such as tcp/ip.. I had hoped for in depth discussion abt various topics that were mentioned in my resume.
Instead, msft interviewers asked me some operating system fundamentals, or some questions like 'how do you test a pen' etc which i personally think are stupid questions for person with 5 years of experience in testing. I understand,as msft boasts, this helps understand one's thought process. But unfortunatelly i figured out that these guys are not smart to ask some tricky questions which require in depth understanding of networking.
Having said this, I think I feel i had quite a mismatch with the interviewers. There must be few good guys at msft, but its good to know that one's chances of getting a good interviewer are very less.
2> Resume: It's nice to prepare on things that you have mentioned in your resume. I had read lot of times that msft guys really dig into one's resume. In my case, that did not happen. You will have same chances of making it even if you have not prepared on your resume.
3> Repeated question pattern.: I figured out from my friends at msft and other guys who had interviewed at msft that each interviewer has some questions he would ask any one he interviews. In my case one guy asked me the same tech questions he had asked my friend who had interviewed before me.
4> They judge you very fast.: If you can't answer a puzzle or can't figure out an algorithm, then you are 90% out. It is true. They judge you very fast. Interviewers are nice to give you tips.
5> MSFT employees live in their own world:
I could somehow feel that they don't really care or appreciate how much of good experince you have or care to show some interest in what you worked on. They will ask same stereotype questions to each of them and are not smart enough to appreciate one's experience. I felt that freshers or experienced guys are treated equally- same questions to both.
Well, this is because, people at msft have limited exposure. In my case I could figure out that inteviewer who worked on firewalls, did not have much understanding of networking layers. As I come from a telcom startup having good understanding of networking technologies, i took the opportunity to discuss the problem in detail. The guy kept on changing his question, every time i came up with an answer until i finally gave the answer he was looking for. Bottom line - your success depends on how
Michael said:
Sharad,
I think you have to keep in mind that the "interviewers" are colleagues, more than likely individuals who are performing the job you are interviewing for. I can also imagine that some of them "interview" quite often. Because of this, I think they have a set of questions that they have used over and over again because; 1. It is expedient. 2. The answers they are looking for are "known". 3. They feel the answers are representative of some quality they are looking for.
The fact that you have extensive networking experience may have no impact on whether they think you have the necessary skills for the position you were interviewing for.
I have also read (and it seems to be true based on the one set of interviews I have had) that Microsoft would be willing to pass on a good candidate rather than hire one that is not the right fit. This is not a reflection on you or your skills, but rather the culture they foster.
gretchen said:
Another reason you may find interviewers asking the same questions to multiple people is for calibration purposes. If you ask a question only once, you often aren't able to judge how someone answers it, but if you ask the question to each person, it's a good balance to see how candidates answer as compared to each other.
sharad said:
Michael & Gretchen,
I understand why they ask the same questions to all the interviewers. But I don't think this is a safe practice.It all depends on how tough questions they ask.Any college kid can reverse a linked list or explain OSI model of networking. If they were to ask these questions to some experienced person, interviewers better get into some detailed discussion rather than making it very objective question-answer session. :)
I think there are some wrong interviewing practices at MSFT.
Interviewers some times (as in my case) don't dig into resume. One inteviewer took some time during interview to read my resume. I would expect them to spend some time in preparing for inteview.
People fly over from all parts of US to interview at MSFT. Inteviewers need to understand that MSFT spends money to interview these candiates and so they better be well prepared. Also the candidates who are consultants take salary cut for a day to interview at MSFT. Microsoft is a rich company does not mean that they can interview any one they want and as they want.
I have heard that MSFT gets on average 8 condidates for onsite interview for one open position. Since all of them come from different backgrounds, "Repeated question pattern" can help them seperate good ones. But it all depends what questions they ask. I feel they need to prepared on tough questions. No wonder why good candidates fail in their interview process.
Michael said:
Sharad,
I agree their interview process is not perfect, and everyone's experience is going to be different. That said, I have been in software development for over 12 years, and have been on countless interviews. I have had one Microsoft "loop" of interviews for one position, and it is easily the most thorough 'interview' I have ever had. I interviewed with a total of seven different individuals, from potential colleagues, to the hiring manager, to a senior director. All queried me at different levels, technical, professional and personal (to the extent allowed of course). I came away with a clear understanding of the position, culture and expectations, and should I receive an offer, I feel comfortable I have enough information to make a decision.
On the flip side, I have read of other experiences such as you had. My only suggestion would be to keep plugging away, and if Microsoft continues to have postings that interest you, keep submitting your resume. Keep in mind part of the 'art' of interviewing is knowing what the goals the interviewer are, and meeting them, even if they are not your own goals, or even make sense :-) At least with one interview under your belt, you will have clearer expectations the next time around.
Best of luck!
Guillermo said:
Hi, I was interviewing for a Technical Account Manager position and wanted to know if anyone knows the type of questions they generally ask? What are they looking for?
I asked similar questions to the first guy that interviewed me and it was somewhat help. I just wanted to know if anyone out there knows typical TAM questions.
Thanks!
gotcha said:
Hello,
I have some very non-typical questions for you. Suppose you are offered a job and for various reason you refuse the offer, does it affect badly on your profile? Is it possible to interview again for the same position, say in a few months? How is the candidate treated if he/she applies again? Does the candidate have to go through the same process again?
I know these questions sound weird, but I wanted to know nonetheless.
JobsBlog said:
Guillermo - I don't specialize in TAM roles so I don't know. But maybe some readers here do! Readers?
Gotcha - Yes, you do have to go through the same process again, but turning down an offer (in a respectful and professional manner) does not reflect poorly upon your future candidacy. When you are ready to reapply, I'd suggest contacting your previous recruiter and letting him/her know you are back on the market.
Good luck!
Samantha said:
I'm having my TAM interviews with Microsoft in April. Can someone tell me about their interview experience for a TAM position? Do they ask technical questions or no? How should I prepare myself? Guillermo? Anyone?
Please advise me. Thanks!
Microsoft's JobsBlog said:
Thanks for visiting JobsBlog! We invite you to read our post archives for information about applying
Microsoft's JobsBlog said:
A long, long time ago, I wrote a post about phone screens and included some of my tips for success. Last