Verisign Interview Questions
& Process

I had 4 interviews total. I got selected at the career fair on my campus. The first interview was at the career fair, and it was just about my resume and past experiences. The second interview was two days later, also in person. Two people interviewed me, and they asked technical questions like 'How can you optimize performance?' and 'What are REST APIs?', plus more questions about my resume and experience. The third round was online via Webex. It was a panel interview with 5 interviewers, and it was mostly behavioral questions with 2-3 technical resume questions. They asked about Google Firebase from my resume and one or two other resume questions, but the main focus was behavioral. The last round was also a panel interview, this time with 3 people, and it was entirely technical. They started with technical questions about Springboot and then gave me an easy-medium LeetCode problem.

The first round was pretty straightforward, with easy LeetCode-style problems and a review of my resume. The second round was a bit more challenging, involving easy to medium LeetCode questions. Overall, the interview process wasn't overly tough, but it did take a long time.

I applied on Verisign's website and then got an email from the recruiter with 6 questions for a written interview. I sent back my 3-page response. Then I had my first round with 2 peers over WebEx for about 30 minutes, which went a bit longer. Round 2 was with the hiring manager and another peer, also over WebEx, for about 60 minutes. The recruiter mentioned a third round with another team member, but that didn't happen. Later, the recruiter texted to say I wasn't moving forward, but the hiring manager would keep me in mind for other jobs. They mentioned Verisign doesn't have much room for growth and is stuck in old ways, and someone made an inappropriate comment about my looks. We also had some scheduling issues, and they offered a weekend interview, which I declined.

The interview, lasting from 12pm to 4pm, began with a lunch at a restaurant in Reston Town Center with the interviewer, from 12pm to 1pm. Afterward, we returned for a timed practical test. Before starting the practical, they asked a few questions. They observed my work by connecting a computer to a TV, and no Googling was allowed. While they were friendly during lunch, it wasn't an indicator of an offer. They intensely questioned me during the practical with difficult questions. Knowledge of design patterns and algorithms was highly valued. The interviewers were described as nerdy and awkward, leading to a lot of uncomfortable silence. Candidates should be prepared and know algorithms, design patterns, Python, and MongoDB. They are also known to be unresponsive to calls or emails if you don't qualify.