The entire interview process took about six weeks.

I was first given a HackerRank assessment containing ten logic questions and two coding questions. The coding session was a bit tricky. I remember I had to use a hashmap to achieve the most optimal output.

After passing the HackerRank assessment, it took a week to schedule a video call to meet with a senior recruiter. This video interview was informal and informational. The recruiter was very nice and explained the company's value. She made it clear that it is very important to the company that they hire someone compatible, not just experienced.

The first technical interview with a senior developer was scheduled two weeks after the HR informational interview, as my initial recruiter went on vacation. The technical interview was definitely easier than the HackerRank assessment. I recall having two coding questions. I didn't get them right away. I talked it through with the interviewer, planned my algorithm first, and asked if I was on the right track before writing any code. The interviewer was nice and supportive. We actually had a lot of fun discussing ways to solve the problems.

A week later, I was scheduled to meet with two technical leads for the final interview. This time, I was asked to present a piece of automation using UiPath Studio Community Edition. I prepared by watching UiPath Academy video tutorials and reviewing the open forum. I spent my entire weekend on this project because I still work full-time. It took a full weekend as I wasn't very familiar with the software, but it was user-friendly enough that I could create a fairly complex automation without deep knowledge of it.

The final interview started with me introducing myself and presenting the automation piece. Then, I was asked to write code to solve an algorithmic/semi-mathematical question. It was so long ago, I vaguely remember it involved adding numbers and then doing something with the sum. I struggled a bit with this coding, but the tech lead kindly guided me, and I was able to solve it! The first interviewer gave me immediate feedback, both positive and negative. Then, the second tech lead joined and told me a little about the team. This second tech lead was very genuine and made me feel much more relaxed after the first coding session. However, he did give me another coding question, but this time I wasn't as nervous. I asked many questions and cracked the code, literally, step by baby step. After finishing with the second tech lead, I met with the 'Boss Man.' He was super chill and nice! He asked me to show him my proudly made automation piece and told me how he's trying to build an ultimate, amazing team in NYC. This, he explained, is why they spend so much time and effort interviewing people—because they care a lot about hiring individuals with the right motive, attitude, and fit for the team.

I learned a lot throughout all the interviews and phone calls. I feel that even if I hadn't received the offer, I walked away with valuable interviewing experience and was ready to excel in future interviews. I believe that people who have had negative experiences should reflect on themselves rather than blaming the company.

However, I would say the process did take a bit longer, and you have to stay on top of your recruiter. Patience is key in this situation. I hope this review helps ease your mind. Best of luck, and I hope more amazing people join the company!

The offer comes soon after the final interview, and the VP will call to discuss the next steps.

Logic, algorithmic, and mathematics coding questions.