I applied online. The process took 4 weeks. I interviewed at CARVANA
Interview
Contacted by recruiter, pre-screen coding challenge on HackerRank, two phone interviews with lead engineers, final on-site interview. I was not asked to solve any coding problems or asked any questions about Computer Science.
Interview questions [1]
Question 1
Are you the kind of engineer who often works on projects outside of work?
Recruiter reached out on LinkedIn and move forward with the whole process:
Hiring manager round 30min
Coding round 1hr
Onsite:
Data science round
Leadership round
System design round
Product round
I applied through a recruiter. The process took 3 weeks. I interviewed at CARVANA (Phoenix, AZ) in Mar 2022
Interview
The process took 2 weeks, consisted of 1 technical interview and 1 behavioral interview via zoom, followed by a general informational meeting.
The technical interview involved a zoom meeting with two technical leads where I was asked questions involving my technical expertise. I was also tasked with a whiteboard question to display problem solving and communication skills.
The behavioral interview involved general behavioral questions to gauge personality and culture fit.
The last meeting was with a top recruiter, going over details of the company and offer letter.
Overall, a great experience!
Interview questions [2]
Question 1
General technical questions with one whiteboard question
We are so happy that you had a positive recruiting experience at Carvana... and that you took the time to share your feedback. Very much appreciated, and we look forward to working with you!
The process took 3 weeks. I interviewed at CARVANA (New York, NY)
Interview
Applied on company website and heard back the next day.
Two short phone interviews with the recruiter.
One short zoom interview with the team lead.
One long zoom interview with almost everyone in the team.
One take-home test which I had a week to do.
Overall, I liked the process. The recruiters and interviewers were on time and responsive.
I liked that I had a week to do the take home test. The test was not difficult, but had a lot of interesting edge cases. It takes time to figure out, document and write unit tests.