Varsity Tutors Software Engineer Interview Questions
& Process

So, I noticed the work environment seems a bit micromanaged, or at least it felt that way during the interviews. I went through three rounds initially, which included a coding challenge and then two more rounds that were a mix of technical and soft skills. Then, out of the blue, the CTO decided to do another round, calling it the 'final' one. It started with a super quick and kinda cold intro, and then another coding challenge. This time, I didn't quite make the cut, and honestly, I never heard back from HR after trying to follow up. Pretty much got ghosted.

A recruiter from Varsity Tutors reached out on LinkedIn and sent a convenient calendar link. After an initial phone screen, I had an hour-long meeting with the hiring manager. This involved behavioral questions, learning about the company, and a short coding task where I had to look at some code and then rewrite it, explaining it as if to a junior engineer. I then advanced to a multi-interview 'loop' with three interviews. The first two were with senior developers and focused on technical aspects and deeper dives into my resume. The first of these had one simple technical question, and the second had two more straightforward technical questions. I could use any programming language for these. The final interview was with a VP and consisted of standard behavioral questions. The entire process felt very fair and straightforward, with great communication from the recruiters.

I saw the role on LinkedIn and was interested because I like the education industry. The culture seemed like a fit, but I'm not sure how I feel after the interviews. First, I spoke with a friendly technical recruiter who assured me they don't use those tricky puzzles. Then, I met with the manager or director(?), who was also nice and suggested I could improve my rusty SQL, which I thought was fair since I've done that kind of work before. Many tech companies, unlike this one, focus too much on specific skills and ignore broader experience. After that, I had an interview with a tech lead, who also had a background in mechanical engineering before moving into software, just like me. He asked behavioral questions, which I think I handled well. Then came a fairly simple coding problem that I did okay on, though I didn't go over the most pythonic way to solve it because he cut it short to get to my questions. I suspect mentioning I spend 5 hours a week teaching data science might have raised a red flag, though he didn't say so.