Clay Interview Questions
& Process

Just wanted to share my experience with Clay’s interview process, as I know some people are looking into it. I was really into it at first because the company and its message are pretty cool and different. The interview process is pretty standard: you start with an HR chat, then a take-home assignment, followed by a live workshop interview, and if you do well, you'll talk to a co-founder. I thought the take-home was good and actually useful for the role, and I put a lot of work into it. But things went downhill during the in-person workshop. The interviewers were 12 minutes late but still expected me to finish everything in the 45 minutes, so I only had about 36 minutes, and they didn't say anything about it. I get that this might happen in sales or client-facing jobs where you have to present in a specific time frame, but this wasn't a sales job. Still, I felt like I was being rushed and judged on how fast I could work, which seemed to be the main thing they cared about. The live demo felt more like a sales pitch under pressure than a real test of my problem-solving skills or the work I’d already done on the take-home. Even though I had prepared a detailed table beforehand, it felt like they didn’t even consider it. Basically, the whole process seemed to value speed over actual thinking and made me feel like they didn’t respect my time or the effort I put in. So, if you’re thinking about interviewing here, just know what they’re really looking for.

This was a really refreshing interview experience. After a quick intro call, they gave me a take-home project. It wasn't your typical boring assignment; they actually encouraged creativity, weirdness, and humor. The goal was to show off my technical skills and how I think, building something Clay users would really enjoy. I felt like I could be myself and ended up making it a mini show-and-tell, creating something useful and presenting it humorously. It's clear they value original thinking over just checking boxes. The best part was the lack of corporate stiffness; they treated me like a creative collaborator, not just a candidate. I felt inspired, not drained, afterward. My advice: don't play it safe; show your intellect and personality.

The interview process consisted of an initial recruiter screen, followed by two back-to-back coding interviews, and concluding with a system design and project deep dive interview. The entire process spanned approximately six weeks. All interactions were positive and pleasant. The recruiting team provided helpful guidance and success criteria for the final round interviews.

The interview process at Clay was quite bad and I wouldn't do it again. It started with a normal recruiter call with basic questions. Then came the take-home assignment, which was the real issue. They gave a 4-question take-home that asked about support knowledge, expecting us to learn everything from their not-so-clear help docs. One question specifically required making a table using their platform based on requirements, but without any instructions. This meant digging through lots of videos and docs, and a lot of guesswork, to set it up. I thought I nailed it, especially since it took about 3 hours. But then, just a standard rejection email two days later. If you ask candidates to spend 4 hours on a take-home, the least you can do is give feedback instead of just a rejection. It felt like they didn't respect my time, and if this is how they treat potential hires, I can only imagine how they treat current employees.