↳
I was honest about the situation, and hope it didn't hurt my chances.
↳
This was not a difficult one, but it was unexpected. I took this question to be less of a trick question, and more of a question to make one think. Perhaps it is a similar interview question to the common "What's your greatest weakness", but I felt that it was a better approach to learning about a candidate, as the answer stands to communicate far more than the actual question demands. Menos
↳
I did some research and prepared the presentation before going on-site.
↳
Make sure that expectations are aligned across all stakeholders.
↳
A Scrum Master is focused on removing blockers to maximize velocity while a PM has budget oversight, baselines, and other responsibilities outside of ensuring day-to-day project traction. Menos
↳
How to deal with memory leak issue in an embedded system.
↳
Candidate was qualified. Candidate demanded AFTER the offer was made to 'work from home' at least one day per week. We told the candidate this job required all hands on deck in the office. Candidate was adamant about working from home to the point of annoyance, extremely pushy as the candidate lost his/her position in a downsized company and was pushing to land this job.. Candidate simply got greedy with expectations from a small start up. Menos
↳
I created a multiple page storyboard for an application that has real potential.
↳
I answered honestly and truthfully which was easy because these core values are something I really wanted to believe in. Menos
↳
I cited a project where the deliverables were split into 2-week segments. Although not exactly Scrum, since for the early stages code wasn't testable, it did allow for the project to be broken up into manageable chunks. Menos