Vercel Recruiter Interview Questions
& Process

Candidate had a poor experience and had to follow up multiple times. The assessment via MeritFirst was the WORST (weird/bad user interface, requiring specific systems to simply take a test, & also repetitive). The actual subject matter was easy, but they need to reconsider how they are treating and selecting top applicants. Highly recommend that you do not interview with Vercel. They are reposting/boosting this role and it's doubtful they aren't finding qualified candidates. Since candidate experience was not top of mind, you will not have a good time here. As a current RC, if a company cannot give you a great candidate experience to the owners of candidate experience, what does that tell you?

The application started with 3 required essay questions online. Immediately after, I got another writing task due in 2 days. This task asked for my best outbound recruiting message and info on 5 of my best hires, including LinkedIn profiles, which felt like a privacy issue. Both the application and the assignment took over an hour. Two days after sending it, I got a generic rejection without feedback. I asked for feedback since I spent so much time on it, but never heard back. I wish there was more transparency or some idea of how my work was judged. The process felt more like a transaction than I expected from a company that claims to care a lot about developer experience and brand. ADVICE TO VERCEL: If you want candidates to spend a lot of time on take-home work, please give personalized feedback, even if it's short. If you can't give feedback, change the application process so the time spent is fair to the effort you put into your replies.

This was one of the most bloated and unnecessarily grueling interview processes I’ve experienced in nearly two decades of tech recruiting. The total process included: 1. Recruiter screen 2. Hiring manager interview 3. Take-home assignment #1 4. Technical recruiter interview 5. Brief intake meeting with an engineering director 6. Take-home sourcing assignment #2 7. Values interview 8. TA leadership interview 9. Follow-up to review the sourcing assignment with Engineering director. 10. Wrap up with Hiring Manager And still, a VP round pending That’s 11 steps (with assignments) for a sourcing/recruiting role - not an executive position. The lack of respect for candidate time was glaring. The sourcing assignment was a setup for confusion. I was told explicitly not to over-index on the tech stack - to prioritize candidates who ship and contribute, not just keyword-heavy LinkedIn profiles. I did exactly that: sourced directly from GitHub, handpicked contributors, and mapped to real-world product impact. But somehow, this wasn’t what they were looking for. I also shared that I use AI tools to streamline GitHub vetting (without sacrificing depth),which is apparently a problem? The final straw was the implication that a repeated candidate in GitHub searches somehow means I found them with a keyword search on Linkedin(?) At that point, I realized I was wasting my time.