
Webroot Interview Questions
& Process
Real candidates share what happened, how many rounds they had,
and how the experience turned out.
Based on 41 interview experiences · FREE TO READ
Which role are you interviewing for?
20 roles · 41 reportsCandidate interview experiences
First-hand accounts from people who interviewed at Webroot.
UX Designer
I applied online and heard back from a recruiter a couple weeks later for an initial phone screen. After that, I had a phone interview with the hiring manager that seemed to go well. About a month later, which made me think they'd moved on, the recruiter reached out again to schedule an on-site interview. The on-site lasted 2 hours and I met with the hiring manager, marketing manager, and members from the design and dev teams. I felt good about how those interactions went, and then waited for the next steps. It took 3 weeks to get feedback, which was basically a 'thanks, but no thanks' because they had hired someone else.
- Can you describe your design process?
- What design tools are you proficient with?
- How have you managed interactions with marketing and development teams in the past?
Software QA Engineer
The whole interview process took about a week. First, a recruiter from the company reached out, and we had a phone call that went pretty well. Then, I was invited for an onsite interview later that week. The onsite was mainly about discussing my previous work on projects and answering some technical questions. They seemed happy with my background and were initially going to extend an offer. But then, surprisingly, after another week, my consultant let me know they had put the offer on hold without giving any reason, which was quite strange.
- Can you discuss your past project experiences?
- Tell me about your past project experiences.
- Describe your past project experiences.
Anonymous
A third-party recruiter handled the initial screening and scheduling. The whole process felt messy and unprofessional. I had a 30-minute phone interview, and then they set up an in-person interview. The recruiter sent a calendar invite for one hour, but the panel interview with people from different departments actually lasted about three hours. I had researched the company beforehand and saw online that Carbonite's recent acquisition had made people worried about product support, potential shutdown, and future updates. When I brought this up, they seemed confused and didn't believe me. Honestly, the company didn't impress me. Most people I talked to seemed really unenthusiastic. It felt like the company had a lot of internal problems and might face big issues soon.
- What programming languages are you proficient in?
Manager
The interview process was quite intensive, involving 13 separate interviews over 9+ hours. Although I enjoyed the discussions, it was disappointing to be rejected due to salary expectations, especially after investing so much time without prior indication of this being an issue. The recruiter's involvement added some ups and downs to the experience. Despite the outcome, the comprehensive nature of the interviews is effective for assessing answer consistency and potential rapport with the team.
- What skills would you contribute if hired?
Webroot Interview Questions
Quoted word for word from Webroot interview reports.
“What's the length of the TCP header when no options are set?”
Read reports →“What is Cloud Testing?”
Read reports →“What are the major differences between C, C++ and Java?”
Read reports →“What is Performance Testing?”
Read reports →“What are your favorite vocabulary words?”
Read report →“What is your expected timeframe for responding to social media comments?”
Read report →“Can you analyze this large script for code?”
Read report →“Tell me about RESTful Services.”
Read report →“What UX problems do you see with this product?”
Read report →Formats, difficulty and experience
Across all 41 Webroot interview reports.