Skip to contentSkip to footer

Leadership Development Interview Questions

Salaries
Interviews

8,620 leadership development interview questions shared by candidates

I cannot discuss the questions as they were a part of the NDA I signed. I can tell there was a huge emphasis on the design in my interview. The interviewers(All of them) started by an open-ended question, to which I asked many many more clarifying questions to understand the scope of the problem and come up with possible assumptions under which I operated and produced pseudo-code and wrote code. I was interviewed by a mid level Software Engineer to begin with, then another mid-level Software Engineer, then by a Manager and finally by a Team Lead with 6 years of experience in GOOG. I was particularly interested in this interview as he seemed to come with experience working at a company that dealt with code security. A stark difference between my previous interviews(Please see below I have had more interviews at GOOG before) and this was that I was being asked to clarify the design on purpose and being prevented from writing code and given very little time to write code. This felt very strange to me. Either the interviewers were new to the process or were doing so on purpose, I couldn't tell. I got a real sense that they liked me during the interview with the messages they were trying to send me in terms of the conversation they were trying to engage me in....giving instant feedback and making me feel very comfortable during the process(Initially). But there was a time when they were just giving a requirement tracing it back and the problem space was very complex and AMBIGUOUS(Several moments during the interview were racking my brain quite a bit and there was significant pressure put....all a part of the GOOG interview).....I wade through the requirements and tried chopping off the constraints a bit and gave justification as appropriate. I wrote code in almost all the interviews except the ones that involved design and only design into the depth. All my interviews on the final interview were more than an hour and 15 mins, the lunch interview was short and just a casual overview of GOOG with the person who passed my resume, she isn't from the background I come from. I was again stumped why they were asking me to have lunch on campus with this person, I guessed that they probably wanted to see how I interacted with a plethora of people with different job descriptions on campus. This was very surprising part of the interview. I could tell that the interviewers were very keen on trying to sell GOOG to me, the workplace, their shipping cycles, their code review strategy, who they get new projects and how they share space with Mountain View office and collaborate and work. Finally I was escorted by a Team Lead and we seemed to continue the discussion as a continuation to the questions asked in the interview process. They were very engaging design discussions and I got a sense that this was a company I could look up to.
avatar

Software Engineering Leadership Position

Interviewed at Google

4.4★
Feb 23, 2016

I cannot discuss the questions as they were a part of the NDA I signed. I can tell there was a huge emphasis on the design in my interview. The interviewers(All of them) started by an open-ended question, to which I asked many many more clarifying questions to understand the scope of the problem and come up with possible assumptions under which I operated and produced pseudo-code and wrote code. I was interviewed by a mid level Software Engineer to begin with, then another mid-level Software Engineer, then by a Manager and finally by a Team Lead with 6 years of experience in GOOG. I was particularly interested in this interview as he seemed to come with experience working at a company that dealt with code security. A stark difference between my previous interviews(Please see below I have had more interviews at GOOG before) and this was that I was being asked to clarify the design on purpose and being prevented from writing code and given very little time to write code. This felt very strange to me. Either the interviewers were new to the process or were doing so on purpose, I couldn't tell. I got a real sense that they liked me during the interview with the messages they were trying to send me in terms of the conversation they were trying to engage me in....giving instant feedback and making me feel very comfortable during the process(Initially). But there was a time when they were just giving a requirement tracing it back and the problem space was very complex and AMBIGUOUS(Several moments during the interview were racking my brain quite a bit and there was significant pressure put....all a part of the GOOG interview).....I wade through the requirements and tried chopping off the constraints a bit and gave justification as appropriate. I wrote code in almost all the interviews except the ones that involved design and only design into the depth. All my interviews on the final interview were more than an hour and 15 mins, the lunch interview was short and just a casual overview of GOOG with the person who passed my resume, she isn't from the background I come from. I was again stumped why they were asking me to have lunch on campus with this person, I guessed that they probably wanted to see how I interacted with a plethora of people with different job descriptions on campus. This was very surprising part of the interview. I could tell that the interviewers were very keen on trying to sell GOOG to me, the workplace, their shipping cycles, their code review strategy, who they get new projects and how they share space with Mountain View office and collaborate and work. Finally I was escorted by a Team Lead and we seemed to continue the discussion as a continuation to the questions asked in the interview process. They were very engaging design discussions and I got a sense that this was a company I could look up to.

Viewing 231 - 240 interview questions

Glassdoor has 8,620 interview questions and reports from Leadership development interviews. Prepare for your interview. Get hired. Love your job.