I had a very bad experience with the Capital One interview process. I'm not sure if this happened only to me or to others, but I wasted a lot of time following up and working on the tests.

I was contacted by a recruiter after she reviewed my LinkedIn profile. I was very interested in the role and accepted the invitation to chat. We had an initial call, and it was a decent exchange of information. She told me that she would send an email with all the details regarding the position, but she never sent any email.

I was the one who kept following up on LinkedIn, and she would respond after many attempts, and even then, only with limited information. If I asked for more details, I had to follow up again and wait for a long time. I was frustrated but thought I would give it a few more tries because I liked the role.

Finally, she responded, saying there would be a call with one of the Directors and one programming test to be taken before the phone interview and an onsite interview. I scheduled the call right away because I wasn't sure if I would get a reply if I missed that chance.

The Director called me on the scheduled date and time, and he was gauging my expertise and my work. The conversation went fine. Days passed by, but there was no reply from the recruiter. I pinged on LinkedIn again for my status. Then, after a long wait, I got a response saying I needed to take the programming test. I had to ask for feedback about the Director call. She said it went very well. I received an email about the programming test with a link to HackerRank.

This test took a long time as it was vague and required understanding the whole workflow. They had their own Linux-based platform within the HackerRank setup. We had to use the terminal to run the program. There were certain test scripts that read text instructions and produced the output. To do this outside in our local environment would have required setup and would have been tedious, so I tried doing it in the terminal itself.

The test had a time limit of 3 days, and we needed to complete it within that time. I worked on it during my leisure intervals and was able to complete it after learning a few things and was able to use them based on the test instructions. I submitted the code and communicated the same to the recruiter. I followed up several times, but there was no reply from the recruiter.

I was so frustrated because I had invested so much time in this process that I stopped following up. It's been many weeks now, and I haven't been contacted. Whether the outcome is positive or negative, the candidate needs to be informed because we invest so much of our personal time, and it needs to be respected.

This is my personal experience, so I can't comment on the actual interview process. Maybe I got the wrong recruiter. I just wanted to share this so that if you happen to have the same experience, please don't follow up like I did and waste your time.

Programming test related to a weather application.

This test includes some stubs that need to be completed and tested based on the provided instructions.

Additionally, new APIs and workflows need to be added.

The entire project is structured with a POM and also features a terminal application embedded within HackerRank, specifically for Capital One.