Viget Labs Interview Questions
& Process

The Viget interview process is pretty in-depth and takes a good chunk of time, around 6 weeks total for me. It was broken down into 4 main parts: first, a chat with a recruiter, then a 90-minute written task, followed by a video call where I had to do a technical project briefing, and finally, a full day of in-person interviews. The recruiter was great at letting me know what to expect and how long each part would take. I even read a blog post by Viget about their process to make sure I was on the same page. The 90-minute written exercise was tough but also pretty enjoyable, with 4 questions covering different topics to test how well I communicate and research. I felt like 90 minutes was a good amount of time to figure out how to manage my time effectively. The technical project briefing call was another fun challenge that needed some preparation. I had to present a website I'd managed, acting like I was bringing new developers up to speed on it. Two people from the accounts team asked questions, and it turned into a pretty open discussion. The all-day in-person interview had several different sessions, each looking at a specific skill. I had to QA a website, act out some client and project situations, and then had more standard interviews with various people, including the company's co-founders. Overall, the whole experience gave me a really clear picture of Viget's values and how they treat their employees. It would be great if more companies did something similar because it's a smart way to find people who not only have the right skills but also fit the company culture.

When you apply for an apprenticeship, you fill out a google form, and then are asked to complete a practice exercise. It was a lot of work on the front end, but a pretty quick turnaround (I heard back about a screening call a little over a week after I submitted my application). The recruiter was super rushed and stressed and asked if I could call them later that day. I agreed, and when I was on the call, you could tell they were stressed and had their mind elsewhere. There was also another member of the team on the call, but they didn't say much at all. The recruiter was thinking on their feet, so there were a lot of "ums" and "likes". Nothing I'd typically be nit picky about, but that paired with her evident lack of preparation and her followup, in which she said my own communication skills could use some improvement, seemed a bit "out of touch". Definitely meant well, but came across very rushed, and the folllowup questions that were asked made me feel like I wasn't being listened to.

After submitting an application via Viget's website, I communicated with their recruiter, had a phone conversation, finished a coding challenge, and went through an interview. The whole thing spanned over 8 weeks. I was really excited to potentially join Viget because I've been a fan of their blog for a while. I thought my code exercise was solid, and I felt good after the interview because we had a good discussion – I was sure I could handle most of the responsibilities listed in the job posting. Sadly, Viget didn't offer me the position. They recognized my skills but mentioned they had more experienced people in the running. Viget was professional throughout the process, and I'd still recommend applying to them. Maybe candidates should stick closer to the recommended time for the code exercise. As for Viget, perhaps they could speed things up a bit since 8 weeks felt a little long.

The apprenticeship interview process at Viget is quite thorough. After submitting an online application, there's a phone interview with a recruiter. This is followed by a technical interview where I pair programmed with a development director. The final stage involved a two-hour interview with my potential mentor (another development director) and someone from the people team. Although it can take a lot of time, I had a really good experience overall. Everyone was really nice and they were upfront about who I would be interviewing with. It was one of the toughest interview processes I've been through, but also one of the best.