Pedro Vicente
2 min readJul 4, 2018

--

As said here: https://medium.com/code-procedure-and-rants/not-another-android-interviews-article-the-questions-3dedafa30bec

Why would I share a lot of the questions I normally use during an interview?

The answer is really simple. First of all, because when I started interviewing and being interviewed I wish I had something like this. I believe you are wondering if this doesn’t defeat the purpose of the interview, by enabling the person to study the questions. Well, I don’t believe so, for several reasons:

  1. Again using Facebook’s interview as a good example, their instructions before it pointed to several sites that have lists of questions they ask. There isn’t an “official” one but the truth is a lot of the questions that I was asked were at least similar. Did it help me? Yes, because it made me understand what type of questions they would ask me. Did this alone help me pass? Not by a long shot. Really. Not by long long shot. Below you will see that I have added quite a few of the questions I normally ask, but not the answers. Well that’s not (just) because I was lazy, it’s really because it’s made for you to search and read about it. I don’t want to give you a small answer that you can just memorize and spit out to me… guess what, I want you to learn in the process!
  2. If you are really learning by using this, it will indeed help you in the interview, but that’s not the point, the whole point is… you’re learning and improving! You now know more, awesome!
  3. Even if you can memorize and spit out stuff.. I will find and I will kill you. Just kidding, but I will definitely ask you to explain and apply each concept that you are spitting out until you confess you’re bullshiting(although all the process is point towards a good experience, if you do this it won’t be, believe me).

--

--

Pedro Vicente
Pedro Vicente

Written by Pedro Vicente

Improver | Mobile Service Lead @minderaswcraft | Feedback @ LoopGain | Communities @GDGPorto | 🔥 @ O Que Arde Cura

No responses yet