Skip to contentSkip to footer
  • Community
  • Jobs
  • Companies
  • Salaries
  • For Employers
      Notifications

      Loading...

      Elevate your career

      Discover your earning potential, land dream jobs, and share work-life insights anonymously.

      employer cover photo
      employer logo
      employer logo

      Quizlet

      Engaged Employer

      About
      Reviews
      Pay & benefits
      Jobs
      Interviews
      Interviews
      Related searches: Quizlet reviews | Quizlet jobs | Quizlet salaries | Quizlet benefits
      Quizlet interviewsQuizlet Senior Software Engineer interviewsQuizlet interview


      Glassdoor

      • About / Press
      • Awards
      • Blog
      • Research
      • Contact Us
      • Guides

      Employers

      • Free Employer Account
      • Employer Center
      • Employers Blog

      Information

      • Help
      • Guidelines
      • Terms of Use
      • Privacy & Ad Choices
      • Do Not Sell Or Share My Information
      • Cookie Consent Tool
      • Security

      Work With Us

      • Advertisers
      • Careers
      Download the App

      • Browse by:
      • Companies
      • Jobs
      • Locations
      • Communities
      • Recent Posts

      Copyright © 2008-2026. Glassdoor LLC. "Glassdoor," "Worklife Pro," "Bowls," and logo are proprietary trademarks of Glassdoor LLC.

      Company Bowl sample

      Want the inside scoop on your own company?

      Check out your Company Bowl for anonymous work chats.

      Bowls

      Get actionable career advice tailored to you by joining more bowls.

      Followed companies

      Stay ahead in opportunities and insider tips by following your dream companies.

      Job searches

      Get personalized job recommendations and updates by starting your searches.

      Senior Software Engineer Interview

      Mar 11, 2025
      Anonymous Interview Candidate
      No offer
      Neutral experience
      Easy interview

      Application

      I applied online. I interviewed at Quizlet in Feb 2025

      Interview

      It was a rather long process, starting with a 30-minute Recruiter screen, followed a week later by a 30-minute Hiring Manager screen, followed a week later by a 3-hour two-part interview (one part System Design for 90 minutes, followed by a 30-minute break, followed by a 60-minute pull request review), followed a week later by a 2-hour two-part interview (one part behavioral/"Leadership" screen with the Head of Data Engineering, one part 60-minute practical coding problem), followed a week later by a final loop (that I didn't make it to, but looking at other reviews, would have been another multi-part/multi-hour loop). The interviewers were super friendly for the most part, and the system design, practical coding, and pull request interviews were engaging and a unique way of conducting interviews - much better than the standardized leetcode tests of other companies. The drawn-out process was one obvious concern, but I didn't find the "Leadership" interview to be a particularly well-oiled component either. The engineering leader asked the typical questions about me and particularly significant projects I worked on, and I felt good about my responses to those, but he ended with a few curveball questions that (a) didn't have anything to do with leadership (e.g. "what's the most recent thing you taught yourself" and "what's your most recent contribution to your local community") and (b) seemed to be looking for particular answers. I gave fine answers to these questions, but I could tell from his reactions that I wasn't passing his specific vibe check, and he even ended by implying I shouldn't even bother with the coding phase of my interview (of course I did that portion, but it left a really sour taste in my mouth). In my opinion, this reflected poor leadership on his part, and structuring an interview process to put a gate of his whims a full month in is not only a waste of everyone's time, but Quizlet's own money and resources. For a startup in such a precariously stagnant position, Quizlet really needs to work on innovating, accelerating, and trimming the fat; this interview process should be a prime target.

      Interview questions [1]

      Question 1

      System Design, Code Review, Behavioral Questions, Practical DSA problem in python
      Answer question
      2

      Other Senior Software Engineer Interview Reviews for Quizlet

      Senior Software Engineer Interview

      Jun 3, 2022
      Anonymous Interview Candidate
      No offer
      Positive experience
      Average interview

      Application

      I applied through a recruiter. The process took 2 weeks. I interviewed at Quizlet in Apr 2022

      Interview

      HR Screening Interview, into a round 1 algorithm technical interview (2 questions in 45 minutes), with a final round including behavioral, management, and a front end/back end technical interview. > Everyone was super friendly and they seemed to have a culture that valued helping people learn. At every technical stage of the interview process, they gave very specific and constructive feedback, better than I've received interviewing anywhere else, over all I was really impressed. Admittedly also bummed that I wasn't able to get an offer. > During the first 1 technical interview, I didn't realize they would be asking me technical questions so it caught me a bit off guard (you write your code in an online IDE and it had to compile/execute correctly, they let you choose the language). I also didn't realize until later that there were meant to be two questions, I took the entire time to finish just the one, but I think I would have been stuck on it either way. They decided to bump me down to a SDE 2 instead of a senior for the final interview, but mentioned I could be bumped back up if I did well in the final rounds. > Final rounds discussed work culture, the team structure/projects I'd be working on, and finally involved both a front end and back end interview (they didn't seem to have explicit front end/backend roles so everyone was expected to be fullstack. I'll give non specific versions of the questions below.

      Interview questions [3]

      Question 1

      Round 1 technical: I opted for Python 3, and the first question involved parsing HTML objects using some "DOM Element" library, then filtering/executing something on them according to some specific logic.
      1 Answer

      Question 2

      Round 2 Front end interview: They give you some boilerplate React code/CSS ahead of time to set up in an IDE ahead of time. When you do the actual interview, they ask you to take it an add X, Y, or Z functionality to it. Hint: It is related to how their website operates and the boilerplate code is a good indicator of what they'll ask.
      1 Answer

      Question 3

      Round 2 backend questions: You're not expected to have something that necessarily compiles here, and the question felt much more like an abstract leet code algorithmic/data structure question. After coding up my answer, the interviewer did make it a point to ask me how my code might actually perform in a real back end set up, and to consider what additional difficulties would be involved (probing my knowledge of backend work basically). Conceptually it was writing code to keep tabs on the names of "servers" that were currently allocated, to deallocate them, as well as handling some rules about how that allocation had to work.
      1 Answer
      1

      Senior Software Engineer Interview

      Jun 4, 2020
      Anonymous Interview Candidate
      San Francisco, CA
      No offer
      Neutral experience
      Average interview

      Application

      I applied online. I interviewed at Quizlet (San Francisco, CA)

      Interview

      Intro, tech screen, onsite. Tech screen is an algorithm based question should be fairly straightforward. Onsite has 2 tech screens and the remaining are behavioral. Tech screens are based on repos you'll have to prepare beforehand. Based on what I can tell: you are given the opportunity to look up things if you want to look up documentation. You'll be under the impression that it will not be considered as a negative -- don't believe it. It can be used as a sign of weak technical skill.

      Interview questions [1]

      Question 1

      Recursively do something with DOM nodes
      1 Answer
      1