Read on Twitter
Been interviewing candidates for senior android roles for a while now, here at Tinder. Here’s are some thoughts and learnings —
Not going to be company specific 1/n
https://abs.twimg.com/emoji/v2/... draggable="false" alt="🧵" title="collectie" aria-label="Emoji: collectie">
Not going to be company specific 1/n
Majority of the candidates want to solve the problem right away, as soon as they see it. This is basic human nature but the people who didn’t take this approach most of the time did really well. Let’s talk about why I feel this hurts you as a candidate
Jumping on to a problem before clearly understanding it, is considered a https://abs.twimg.com/emoji/v2/... draggable="false" alt="🚩" title="Driehoekige vlag op stok" aria-label="Emoji: Driehoekige vlag op stok"> especially for IC3 and above candidates. This is because at these roles you are expected to start owning and delivering projects without any hand holding.
If you don’t demonstrate this behavior. You’ve already set the tone for the interview. Which is — I will be moving on a different path and I might have to be brought back on track every now and then. This is not good!
Here is what you can do otherwise —
1. Once you understand the problem. Explain it to the interviewer and confirm if you got it right.
2. Now ask about the boundaries, you don’t want to make instagram in 40 mins if all they asked you was to design a feed with pictures.
1. Once you understand the problem. Explain it to the interviewer and confirm if you got it right.
2. Now ask about the boundaries, you don’t want to make instagram in 40 mins if all they asked you was to design a feed with pictures.
3. Now ask the interviewer what’s the best way to proceed with a solution - Discussion? PsuedoCode? or Implementation
4. Next, ask them if they’d like you to test any components (UI, Domain etc.) Even if there’s no time to write tests, at least verbally tell how it’ll be done
4. Next, ask them if they’d like you to test any components (UI, Domain etc.) Even if there’s no time to write tests, at least verbally tell how it’ll be done
5. Finally, ask about anything that you missed that they’d like you to talk about/demonstrate/touch upon in the interview.
All this should not take more than 5-10 mins and will help you a lot during the interview — consider than an investmenthttps://abs.twimg.com/emoji/v2/... draggable="false" alt="😉" title="Knipogend gezicht" aria-label="Emoji: Knipogend gezicht">
All this should not take more than 5-10 mins and will help you a lot during the interview — consider than an investment
Now I personally always like to start with a discussion and don’t try to write anything unless the interviewer is happy with a possible solution and I have finished bouncing all my ideas to them!
By doing this YOU are driving the interview and this one of the best things you can do for yourself in this situation.
This is purely a psychological trick — if you know you are in the driving seat, you’ll usually be more comfortable and confident.
This is purely a psychological trick — if you know you are in the driving seat, you’ll usually be more comfortable and confident.
Always remember, a good interviewer wants to help you succeed no matter what.
All of the things mentioned above are what you can hone with some practice. This is not about your technical skills, it’s about your soft skills and they sink our boat more often than we think they do
All of the things mentioned above are what you can hone with some practice. This is not about your technical skills, it’s about your soft skills and they sink our boat more often than we think they do
Will likely polish this and write a more through blog on this later!
Thanks for readinghttps://abs.twimg.com/emoji/v2/... draggable="false" alt="☺️" title="Lachend gezicht" aria-label="Emoji: Lachend gezicht">
Thanks for reading
