Real, anonymous reports from people who interviewed for Software Engineer at Clever, newest first and distilled into what to expect across the loop.
My biggest takeaway from Clever was how harsh the HackerRank-style screen felt. I ran into a strict time limit for each prompt—timeouts that were too short for what the questions demanded. It wasn’t like I could think through the problem slowly; I had to read, type every character manually with no copy/paste, and still debug under pressure.
I got contacted by a senior tech recruiter shortly after applying, and they sent an online assessment link with a short deadline. I replied quickly because I was unexpectedly traveling, explained the timing issue, and asked for an extension. The recruiter sent a new link, but that link had its own expiry window, and when I tried to access it on time—and also tried the original and reminder links—the assessment wouldn’t load or show as available.
Candidates should expect a rigorous online assessment that involves coding challenges with strict time limits and no external resources allowed. The assessment is designed to test not just coding ability but also debugging skills under pressure.
The initial recruiter interaction can vary, with some candidates experiencing delays or issues with assessment links, leading to frustration. It's important to communicate clearly and promptly with recruiters regarding any issues encountered during the application process.
Technical interviews typically focus on system design, API integration, and practical coding tasks that reflect real engineering work. Candidates should be prepared to explain their thought processes and reasoning during these sessions.
Behavioral interviews assess collaboration and alignment with company values, often using structured questions about past experiences. Candidates should prepare to discuss specific examples that highlight their teamwork and problem-solving skills.
The interview process is generally organized and linear, often consisting of multiple rounds including a recruiter screen, technical interviews, and a final wrap-up with a hiring manager or CTO. Candidates should be ready for a comprehensive evaluation across different areas.
Candidates report a generally positive and professional tone throughout the interview process, even if they do not receive an offer. It's important to approach the experience as a learning opportunity, regardless of the outcome.
