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

      Klaviyo

      Engaged Employer

      About
      Reviews
      Pay & benefits
      Jobs
      Interviews
      Interviews
      Related searches: Klaviyo reviews | Klaviyo jobs | Klaviyo salaries | Klaviyo benefits | Klaviyo conversations
      Klaviyo interviewsKlaviyo Senior Full Stack Software Engineer interviewsKlaviyo 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 Full Stack Software Engineer Interview

      Sep 18, 2023
      Anonymous Interview Candidate
      Boston, MA
      No offer
      Neutral experience
      Difficult interview

      Application

      I applied online. The process took 4 weeks. I interviewed at Klaviyo (Boston, MA) in Aug 2023

      Interview

      It was OK but very disorganized. One of my interviewers was late and somehow recruiting didn't know people were on PTO. Some of the interviewers were also distracted with other things, which makes me think they are very stressed out. The interview process was way too long. I applied for the role through LinkedIn and was contacted by a recruiter. I haven't done front-end developing in like 3 years, so very rusty there. I told the recruiter that I am probably more suited for a backend role but she insist on this role. The hiring manager also went on PTO for 2 weeks right when my onsite was suppose to happen, so I had to schedule the onsite after that (while I was on vacation). One of interviewers for my onsite was 15minutes late. There was a 1 hr phone call with the recruiter, 45mins with hiring manager, 1 hour coding collab with two engineers, and finally an onsite that consisted of 5 different interviews. The 5 interviews were - 1. With the hiring manager 2. React list interview 3. System design 4. Leadership interview (this was actually a technical interview on requirements and my interviewer was 15 mins late). 5. PM interview The feedback I got was I did bad on the front end and the system design. I'm not too surprised about the feedback on the front end React stuff but was surprised about the system design part. I suggested better designs even before they asked the questions, which may have been bad on my part. I think there was some things I could've communicated better. I think the person interviewing never heard of blue green deployment in AWS RDS, but I could've explained the concept to him better. From the feedback, it seemed either he either didn't understand what i was saying (could be my fault) or maybe I stepped on his toes a bit. One of the interviewers was also doing something else the entire time. It was great practice though, so thanks to the interviewers who actually paid attention. I did learn a lot from this experience. The recruiter was a bit mean saying the overall feedback was not positive but was honest, which I really appreciate. I'm not sure why they continued the rest of the interview if it was that bad. To be fair, the hiring manager and the product manager (she was a replacement because the PM for the team I was interviewing for was on PTO somehow) I met were both pretty cool people. They were very passionate about the product, which I liked. The lead engineer seemed like a good guy too because he was very engaged but I think I may have stepped on his toes (the other engineer didn't say anything and let him take lead) I would probably interview with them again with a different recruiter if I was given the opportunity since I got good experience from it. Depends if they enforce the work in office or not (the people in the interview I asked about that either never heard about it or were confused for some reason).

      Interview questions [1]

      Question 1

      1. Talk about the design of a system you are working on. I don't know if this is where I did bad but maybe try to focus on how the system is designed. 2. Fix the given React code and format it so that it looks like what they want. Practice cssing components in a certain way with flex, etc. Flex in their code was one of the things causing problems because of the inline property. 3. Basically they have a diagram of a process that records users checking out a cart and different processes that will send an email to a user if the cart is not checked out for a period of time. Each cart checkout is recorded in a SQL table. Each of these processes are hosted in a single EC2 instance. The four different processes are 1. The vendor checkout cart is written to a table 2. The checkout cart is completed and written to a table. 3. There is another process that will retrieve the cart id's from the vendor for carts that have completed checkouts and update them. 4. There is another process that will check if carts sat too long and an email should be sent to a user. They asked what happens if the EC2 instance fails, if there is a planned DB outage, if the call is rate limited. 4. They explained to me how the data pipeline needs to use the same framework because multiple teams have created their own data pipelines and created their own frameworks, so the validation is not consistent across all pipelines. This interview was a bit different actually because they wanted requirements for internal developers vs for customers. What would the UI look like, etc. 5. Talked to a PM (the one that is suppose to hire me is out on PTO somehow). She asked me about what to do in situations like if the feature could not be implemented, etc. She was great to talk with.
      Answer question
      4