Even after a good amount of hard works, I keep falling for various reasons. Here, I would like to share my interview experience, so that it would help someone who prepares

JPMorgan:- (Android Studio wasn't working with ZOOM)

Duration: 1 hour

They have given an offline coding challenge and asked me to submit the coding within 48 hours. I'm managed to complete that within 36 hours including the requirement documents, Unit test case, and better UI design with the latest android architecture components. It was so easy for me because recently I was releasing my app with all these architecture component features. if you are interested, please check my app here https://play.google.com/store/apps/details?id=com.bob.offlinediary

The online interview was scheduled for 2 weeks after I submit the code in GitLab. There is 4 member joined the call and ask me to walk through my code in Zoom call by sharing my screen. With all positive notes, I was in a peak to make it a fabulous interview... wait BOOOOMMM, my android studio wasn't opening at all. I've tried for 30 minutes and finally ask the panel to check out the code and share their screen.

Somehow, I've managed to walk through the code with their machine. However, one of the panel members was so impressed with the way I've handled the situation and given some positive feedback.

The next day, HR called me and we discussed the compensation part. It was too low, I almost reduce my expectation, but they didn't show any interest to come near to my expectations. After 3 weeks, they said that my application was put ON HOLD

Smart Sheets (REJECTED)

Duration: 1 Hour

First 30 minutes we were discussed my current project and experience and asked a few questions related to the current project. Few questions related to compiler flag, prod flavors, and security-related stuff.

The last 30 minutes was an online coding challenge. As usual, they picked one of the LC medium questions, initially, I was struggling a bit, but managed to identify the way to solve the problem within 10 minutes. Then, I wrote the code within the next 10 minutes with minor mistakes but managed to find those while I debug step to step manual debug. Overall, I've executed & shown the output within 30 minutes.

Then, we have discussed some edge cases and the interview was over. Overall, I felt that I would clear this round. But, the next day I received the email that they are not proceeding with me. REEEJJJEECCTTEED. I'm not able to identify what went wrong here.

Robinhood Android Interview (REJECTED)

Duration: 1 hour, Google Meet Online coding

One of the easiest interview and the karma played the BIG role here

One of the easiest interview and karma played the BIG role here

1. First 5 minutes are for the introduction
2. Next 15 minutes is simple Android coding question (Recursion) - Managed to complete with a small mistake, then HR provided me the hint and rectify it within 15 minutes
3. 35 minutes instant android application development. He gave me the scenario to develop the app within 35 minutes by sharing your screen in Google Meet. It's a very basic 2-page app, like passing one value to another page and do some operation, and show the result king of flow.

The BIGGEST mistake is, I have chosen to go for NavigationUI with a safe argument instead of the traditional bundle approach. I missed some configuration in gralde, so it didn't generate the code for me to send or consume the arguments between the fragments. Also, my android studio was DAMN slow and every time it took 10 minutes to compile the code.

I've completed the UI design within 5 minutes, and the safeArgument screwed me up and I managed to find the gralde configuration just before the last 5 minutes. Somehow, I put that try to compile it and the android studio eats my remaining times.

The last 5 minutes were revered for me to ask some questions to them. But, I borrowed that time show him the way to pass and consume the safeArguments in NavigationUI and I explained my implementation approach and he is fine with that too.

But, no use, they rejected me in the next day. Of course, I've not shown them out to them within 35 minutes.

Here is the take out from my experience:

1. The Android Studio will NOT run properly or FREEZE while you are sharing the screen in ZOOM or Google Meetings. So, plan accordingly. I'm NOT sure when Google developer going to fix this Android Studio saga.

2. Planning to switch back to iOS, XCode technology