I was surprised at how narrow the interviews were. May be it was because the position was not very senior but I was expecting a much wider set of technical subjects to be discussed. Except for the personality questions the probing was very tactical in nature looking at the existing knowledge. There were no questions regarding strategy, only one or two product-level ones, no open questions, etc. It felt like the goal was to find a droid, not at all what I was expecting for an architect position.
I was surprised at how narrow the interviews were. May be it was because the position was not very senior but I was expecting a much wider set of technical subjects to be discussed for an architect position. Except for the personality questions the probing was very tactical in nature looking at the existing knowledge. There were very few questions pertaining to strategy, HW/SW integration, very few open-ended questions, etc.
Have you seen what our competitors are doing in this space?
What's the most important thing when you're editing? Why do you want this job? What are your strengths? What's your ideal work environment? What are your goals?
Have you ever had to promote or sell your own work? If yes, please provide an example. If no, describe a project you worked on and how you would sell it to a client.
Tell us a little about yourself. Why are you interested in working onboard?
What experience do you have in sales/retail?
What is a Switch and what does it do.
Where do you see yourself in 5yrs?
Porque queres trabajar en el nicho Gaming de YT?
Viewing 2421 - 2430 interview questions