I really donât understand why most companies do such a bad job interviewing mobile devs (Google included). If your interview doesnât involve working with a real app and the SDK, what are you doing? Just because you can leetcode doesnât mean you know anything about mobile dev, and experienced mobile devs certainly arenât used to working outside of the SDK and libraries available to them
I passed complete loop for snap but decided not to join(in hindsight that was correct otherwise i would have laid off) Here is my take, system design heavy, expect some leetcode style as well as Android question including live pair coding in hacker rank, followed by behavior.
Was sys design more like designing a popular app?
Depends, for me it was designing different feature, I had 2 system design round in total, e.g collab edit
Depends on level. Canât say for certain, but based on your YOE youâll probably have 2 leetcode rounds, then two mobile sys design rounds. Usually itâs specific to mobile, i.e. design X feature. You can take it where you want it since youâre probably a senior candidate. Talk about frameworks, knowledge of what Android components to use, design patterns, testability, etc. I found my sys portions to be code light, but ymmv depending on interviewer.
Didn't they laid off mobile devs recently. Can't find rationale behind this. May be those were let go based on performance đ±
Save yourself the trouble and stay at Amazon where you may be able to keep your job.
Tech Industry
5h
722
Women, help me understand why this is inspirational
Working Parents
Yesterday
1054
What do you think is wrong with a kid who got rejected by 9 colleges?
Cars
Yesterday
751
Do you really feel special in your Tesla?
India
Yesterday
1099
Modi is a legend, will be remembered for centuries to come
World Conflicts
Yesterday
1373
Why people waste their time behind Israel Palestine issues?
Depends on interviewer, but it tends to be a very Android/mobile-centric problem, and you solve it with those constraints and best practices in mind. It would be in a normal online code share tool, so it's not going to compile but you're free to best-guess the Android SDK / java.io APIs as long as logically the solution makes sense.