Tuesday, October 22, 2013

PLACEMENT MADE EASIER (IT companies)

This site  describes the basic and the necessary tools which is to be required for clearing the interview procedures in leading IT companies 

1. MICROSOFT INTERVIEW:

                
                     Microsoft wants smart people. People who are passionate about technology. We probably won't be tested on the ins and the outs of C++, but we will be expected to write code on the board. We will have short interview with a recruiter where he or she will give you a sample question. Recruiter is usually there to prepare us, not to and not to grill us on technical questions. Recruiter can be our biggest advocate even making us to re-interview if we stumble in the first interview. They have ability to fight for us to get us hired or not.
                    Unlike many companies, where we meet our interviewers in a conference room, we'll meet Microsoft interviewers in their office. This will become a great time to look around and get a feel about the culture followed in office.  
                     When we complete our interview with a team, we must talk with the hiring manager. Now that's a great sign. It means that we have passed the interviews with the particular team. But it also depends on the hiring manager decision. 


2. AMAZON INTERVIEW:

                      

                      Amazon's recruiting process begins with one or two phone screens in which we interview with a specific team. The engineer who interviews us will ask us to write simple codes and read it aloud on the phone. They will ask a broad set of questions to explore in what area of technology we are interested in. So be careful to show interest in a particular area of interest and thereby be the best in it. 
                       Next, we fly to Seattle to attend four or five interview with one or two teams which have selected us based on the resume and the phone interviews. We will have to code on the whiteboard and in some cases, some interviewers will stress other skills. Interviewers are assigned a specific area to probe and may seem very different from each other. They cannot see other feedback until they have submitted their own and also they are discouraged from discussing it until the hiring meeting.We will meet the recruiter by the end of the day.
                          Once our interviewers have entered their feedback, they will meet to discuss it. They will be the people making the hiring decision. Amazon's recruiters are excellent at following up with candidates but occasionally there are delays. 


3. THE GOOGLE INTERVIEW:

                            
                         There are many scary stories floating around with the Google interviews, but it is not so true. The interview is not mostly different from Microsoft's or Amazon's interview. Google  HR can be little disorganized and so it is recommended to be proactive in communication. A Google engineer performs the first phone screen, and thereby it is time to expect tough technical questions. On your on-site interview, you will interview with four to six people, one of whom will be a lunch interviewer. Interviewer feedback is usually kept confidential with other interviewers so it is assured that we meet each interview with a blank slate. Our lunch interviewer does not submit feedback and so it is a great time to ask honest questions.
                         Written feedback is submitted to a hiring committee of engineers for deciding the hiring and non- hiring operation. Feedback is typically broken down into four categories 1 .   Analytic ability 2. Coding 3 .Experience and 4. Communication. And we will get a score from 1.0 to 4.0.
                           A hiring committee wants to see one interviewer who is enthusiastic endorser. It is recommended to have a score of more than 2.5 to assure getting placed. Google hiring process is slow. In such cases ask recruiter politely about the update. 


4. THE APPLE INTERVIEW:

                         
                   Apple interview process has a minimum bureaucracy. The interviewers will be looking for a excellent technical skills, but a passion for the position and the company is also very important. While it is not a prerequisite or com pulsation to be a Mac user, you should at least be familiar with the system. The interview process typically begins with a phone screen to get a basic sense of your skills, followed up by a series of technical phone screens with team members. 
                   Once you are invited on campus, you will typically be greeted by the recruiter who provides an overview of the process. You will then have 6 to 8 interviews with member of the team for which you are interviewing, as well as key people with whom your team works. Get ready to code on a white board and make sure that all of your thoughts are being communicated properly. Lunch is with your potential future manager and appears more casual, but remember it is still an interview. Each interviewer is usually focused on different area and they are being discouraged in sharing their feedback. 
                   Towards the end of the day , your interviewer will compare notes and if everyone feels you are a viable candidate, you will interview with the director and the VP of the organisation. This decision is rather informal, you will make it only if a good sign is shown. The decision also happens behind the scenes and if we don't pass, you will simply be escorted out if the building. 
                    If you made it to the director and VP interviews, all of your interviewers will gather in a conference room to give an official declaration of getting placed. 


5. THE YAHOO INTERVIEW:

                                  
                    While Yahoo tends to recruit at the top leading 10-20 colleges, other candidates can also get interviewed through Yahoo's job board or in some cases by getting an internal reference. You will typically interview with 6-7 people on the same team for 45 minutes each. Each interviewer will have an area of focus. For example, one interviewer will focus on database, while other interviewer will focus on the computer architecture.
                    Interviews will be composed as follows:

1. 5 minutes: General conversation, Tell me about yourself, your            projects etc.
2. 20 minutes: Coding question
3. 20 minutes: System design
                     These questions will highly depend on the previous experience and for freshers it concentrates on the area of interest. 
                     At the end of the day, you will likely meet the program manager or someone else for a general conversation like product demos, concern about the company. At the same time your interviewer will discuss about the interviews faced and finally comes to a decision. The hiring manager has the ultimate say and will weigh the positive feedback against the negative.












No comments:

Post a Comment