Applied online. Had a phone call with a recruiter. I was given a coding exercise to complete in a week. After that, I was invited to an onsite interview.

The first phone call was non-technical. The assigned coding exercise was very exciting, and you can complete it in a language of your choice. After this, I was invited to an onsite interview. I also had a phone call to prep me for the onsite interview.

At the onsite interview, I had 3 rounds of interviews (1 hour each). The first one was a technical conversation. During this conversation, I explained my code for the take-home coding exercise. We talked about my interests, skills, and what I was hoping to get from the internship. We also talked about the projects on my resume. It was a great conversation, and I really enjoyed learning about the company. I thought I did quite well on this part.

The next thing was a design exercise. I collaborated with the engineer in designing a simple board game. I enjoyed the exercise, and she was very helpful whenever I got stuck. After the exercise, we talked about her interests and more about the company. I enjoyed this section too, and from my own assessment, I did quite well on it.

The third round was a refactoring exercise (they prefer you to do this part in Ruby, Python, or Node.js). I did this exercise in Java and managed to do about 3/4 of the problem quite well, and I could not finish due to time.

They did a great job showcasing the company to me, and I loved the place. Everyone was smart and humble, a quality that is hard to find in engineering.

After the interview, they told me that they would give me a decision within a week. After this, there was radio silence, and I did not hear back anything for 2 weeks. I reached out to the recruiter, and I was told that they were not continuing with my candidacy.

Advice: The company says you can complete the exercises in any language, but from my own assessment, they prefer Ruby. Also, make sure you do everything perfectly! It seems one small mistake or uncompleted section will entirely ruin your chances. If you do not hear back after your onsite, it is most likely that you did not make it.

Take-home coding exercise: Build a REST API (you can use any language).

Onsite:

1. Technical conversation
2. Design exercise
3. Refactoring exercise (Even though they say you can use any language, do this part in Ruby if you can)