Software Engineer applicants have rated the interview process at Clever with 2.7 out of 5 (where 5 is the highest level of difficulty) and assessed their interview experience as 48% positive. To compare, the company-average is 43.9% positive. This is according to Glassdoor user ratings.
Candidates applying for Software Engineer roles take an average of 23 days to get hired, when considering 29 user submitted interviews for this role. To compare, the hiring process at Clever overall takes an average of 23 days.
Common stages of the interview process at Clever as a Software Engineer according to 29 Glassdoor interviews include:
Phone interview: 40%
Skills test: 17%
One on one interview: 15%
Presentation: 12%
Group panel interview: 10%
Personality test: 4%
Drug test: 2%
Here are the most commonly searched roles for interview reports -
I applied online. The process took 4 weeks. I interviewed at Clever
Interview
First I applied online. The application has a question that requires a little research and experiments on its open API. I was asked to write a program and report its result in the application. I believe the problem is here to weed out the applicants who are not dedicated enough. A few days later I got a call from a recruiter. We talked about my background and the company, and scheduled a technical screening. The technical screening is a peer programming of me and one of their engineers. The problem is not hard, but some coding details and edge cases might be tricky. We started with building the simple and naive solution, and progressed to improve it, until we found the optimal. The interview went OK and the next round was a take-home coding challenge. I was given a week to do it. The coding challenge asked for code (solution) and a design doc (as detailed as possible). The problem comes with sample data, whose size is really small. Given the small size of the sample data, the problem is relatively easy. However, a question asked me to write about the scalability aspects of my proposed solution -- how my solution would perform when the input data size scaled up. My solution was rejected. The recruiter told me that the engineers said I wasn't using the tool in the right way, even though my solution demonstrated strong correctness.
Interview questions [1]
Question 1
The scalability of a solution that could involve a database (relational, NoSQL, ...)
The time constraint on the Hackerrank screen is just not realistic and doesn't reflect what developers even do with real work. I don't understand why companies choose to screen like this. Each question has a 5-22 minute timeout and it is barely enough time to read the prompt and understand it. You have to type every character for your solution, since no copy/paste is allowed. They are not hard problems, but you are expected to come up with them cold, debug them extremely fast with hidden test cases, and not use Google or any other resources. I don't know a single dev who codes like this in the real world.
Just another company that relies on a blunt tool to filter.
Interview questions [1]
Question 1
Hackerrank screen questions with a very fast time limit.
I applied for a role and was contacted the following Monday by a Senior Tech Recruiter, who sent me a link to an online assessment with a 5-day deadline. I replied promptly to explain that I was unexpectedly traveling and wouldn’t be able to complete it until early the following week, and I requested an extension through end of day Tuesday.
The recruiter then sent a new link, but this one was set to expire on Tuesday morning. On Monday afternoon, I tried to access the assessment using the new link (as well as the original link and the reminder email link), and in all cases the assessment was unavailable to me. I immediately emailed the recruiter to let her know the link wasn’t working.
I heard nothing back. Instead, the next day I received an automated email stating that my time was up and my application had been closed for failure to complete the assessment. I followed up again, explaining that the link they provided was not valid at the time I was scheduled to take the test.
The only response I received was a canned message saying that they had already granted an extension, that the extended link had expired “for a second time,” and that the assessment window was now permanently closed and could not be reactivated. There was no acknowledgment that the link had been inaccessible when I tried to use it, nor any attempt to troubleshoot or reschedule.
Ridiculous, clumsy, disrespectful.
Interview questions [1]
Question 1
When is the best time to send you a broken link and then ignore your attempts to resolve this issue?
I applied and heard nothing for several months. A recruiter emailed me inviting me to chat about my application several months after I applied. I had a 30 minute call with the recruiter. It was not at all conversational. Recruiter seemed very rote, scripted, and robotic, and did not inspire excitement about the company. After the call, the recruiter ghosted me.