grab interview
https://www.linkedin.com/pulse/grab-wants-you-tamim-shahriar
Now, if you are interested in the backend engineering position, read below. Or share this article to friends who might be interested.
Well, you don't really need to read it. It's just my humble attempt to ensure that we are not missing a great candidate like you because you didn't spend some time to prepare for the interview. At first you have to take an online coding test. It will test your coding skills along with basic data structures and algorithms skills. If you are not in touch with programming problem solving for years, you should spend some time to practice solving some easy-medium level problems in your favourite online judge (hackerrank, codility, uva, topcoder etc.). In our onsite interviews, we also spend 60-70% time on coding questions. You need to have solid CS concepts including (but not limited to) data structures, algorithms, operating systems, databases, and networking. We don't expect you to solve hard problems in 30-40 minutes, but given any kind of problem (easy / medium / hard), we want you to attack the problem. Don't jump into coding right away. Things you should remember :
- Think about it. Please ask questions to the interviewer. Make sure you understand the problem.
- Question and clarify your assumptions.
- Write some test cases (other than those given by the interviewer). Think and discuss if those are correct.
- Write the simplest solution, unless the interviewer gives you a constraint about run-time / memory complexity.
- If you are stuck with a problem, stand up and use the whiteboard. The interviewer should help you with hints. Try to understand those and apply them in your solution. Once you are clear, get back to coding.
If you are experienced in software engineering, try to prove it in your code. Let me give you an example. Maybe you are asked to write a function that takes two numbers and returns the result of division of first number by the second one. You can see three types of answers here and you will know the difference :
You will be asked software design questions. If not in round 1, in round 2 or 3 for sure. Think about the problem. Try to solve it from customer's point of view. Don't think about whether you will use sql or no-sql. Just design a solution that can be implemented using different varieties of technology. Then propose those you are mostly familiar with. Discuss with the interviewer.
- Don't forget the basic learnings from your operating systems, networking and databases course. Let me name a few things: thread, process, race condition, deadlock, tcp/ip, database indexing, range query, transaction.
So we are looking for you, if, you -
love solving even the really hard problems! come with a solid knowledge on CS fundamentals know what clean, functional code and design looks like can communicate really well in all aspects are a good listener If you have read this far, feel free to try Grab. You will enjoy it here - guaranteed! We want you.