1st Interview: Question: Tell me about your current project (focus on Project Management Stuff, Agile/Waterfall, explain the project at higher level still cover key information related to project management ex. for agile scrum talk abt u got the project and how executed it, include agile scrum keywords, search on youtube on agile scrum and u will get lot of videos) Q:What -if scenarios, project is being delayed, developer is not as productive...read Project Management books and u will get all these...basically stick to script dont elaborate much but cover key stuff...what they are looking for in Project Management side interviews is you have worked in that kind of environment and your communication has to be crisp dont go back and forth.... Q: What type of challenge u get most i.e..scope change/ schedule change or budget change Q: how u exert pressure if things r not working - ans: thru reports and escalate higher up in the chain Q: wud u go for a deveoper who delivers poor quality or go with developer who delivers good quality but delays - ans: go with one who delivers good quality and 1) take into account his/her behavioral pattern during planning 2) exert pressure to get things done Q: read some project management book for sure to get idea on what is key Q: read on risk management as u need to cover it as part of what u have done Interview 2: Technical, what i learned for interviewer is ALL program manager positions at AMAZON require SDE-1 level of knowledge...what it means that interviewer should be able to represent developer community correctly at various meetings. Q1) find substring from a string 2) build an elevator - show analytical bend of mind, ask lot of clarifying questions, dont forget to start with requirements, he took a level up and asked to create classes for elevator system 3) build restaurant reservation system: dont talk abt coding but show lot of analytical skills, asked me to create a data model but before that i walked thru user scenarios and understood detailed rquirement, ask lot of clarifying questions 4) capacity related, again lot of analytical and think on your feet type questions also understand from interviewer and answer as u go along I think i got rejected mainly because interviewer's initial perception that i may not be as technical as they would like...as my project management interview went really well 5) he also asked some pming questions on what-if analysis, who is accountable if project/program not delivered, obviously PM is the one throat to choke and he agreed Good experience
