Aller au contenuAller au pied de page
  • Emplois
  • Entreprises
  • Salaires
  • Pour les employeurs

      Boostez votre carrière

      Découvrez votre salaire potentiel, décrochez des emplois de rêve et partagez vos témoignages de manière anonyme.

      employer cover photo
      employer logo
      employer logo

      Whatnot

      Employeur impliqué

      À propos
      Avis
      Salaires et avantages
      Emplois
      Entretiens
      Entretiens
      Recherches associées: Avis sur Whatnot | Offres d’emploi chez Whatnot | Salaires chez Whatnot | Avantages sociaux chez Whatnot
      Entretiens chez WhatnotEntretiens d’embauche pour Data Engineer chez WhatnotEntretien chez Whatnot


      Glassdoor

      • À propos
      • Récompenses
      • Blog
      • Nous contacter
      • Guides

      Employeurs

      • Compte employeur gratuit
      • Centre employeur
      • Blog pour les employeurs

      Informations

      • Aide
      • Règles de la communauté
      • Conditions d'utilisation
      • Confidentialité et choix publicitaires
      • Ne pas vendre ni partager mes informations
      • Outil de consentement aux cookies

      Travailler avec nous

      • Annonceurs
      • Carrières
      Télécharger l'application

      • Parcourir par :
      • Entreprises
      • Emplois
      • Lieux

      Copyright © 2008-2026. Glassdoor LLC. « Glassdoor », son logo, « Worklife Pro » et « Bowls » sont des marques déposées de Glassdoor LLC.

      Entreprises suivies

      Tenez-vous au courant des dernières opportunités et profitez de conseils d’initiés en suivant les entreprises de vos rêves.

      Recherche d’emplois

      Obtenez des recommandations et des mises à jour personnalisées en démarrant vos recherches.

      Entretien pour Data Engineer

      10 avr. 2023
      Employé (anonyme)
      Offre acceptée
      Expérience positive
      Entretien difficile

      Candidature

      J'ai postulé via une autre source. J'ai passé un entretien chez Whatnot en mars 2023

      Entretien

      - First call with the recruiter to go over the interview process, and salary expectations - Programming Interview Questions - System Design Interview - Product Sense interview - Final round behavioral with a leadership team member

      Questions d'entretien [1]

      Question 1

      - Design a business critical pipeline that can ingest data from an external vendor server
      Répondre à cette question

      Autres retours d’entretien d’embauche pour un poste comme Data Engineer chez Whatnot

      Entretien pour Data Engineer

      30 juin 2023
      Employé (anonyme)
      Lansing, MI
      Offre acceptée
      Expérience positive
      Entretien moyen

      Candidature

      J'ai postulé via la recommandation d'un employé. Le processus a pris 6 semaines. J'ai passé un entretien chez Whatnot (Lansing, MI) en juin 2023

      Entretien

      The interview process consisted in the following meetings: - initial contact with recruiter - briefing about first interview rounds (coding challenge, system design) - interview with team lead - coding challenge - system design - briefing about next rounds of interviews (product knowledge, soft skills) - product knowledge interview - soft skills interview - feedback and briefing about subsequent interview round (data pipeline design) - data pipeline design - offer and negotiation

      Questions d'entretien [3]

      Question 1

      Design and implement code to build a user action tree from application logs.
      1 réponse

      Question 2

      Design an API to serve livestream rankings to the client application.
      1 réponse

      Question 3

      Design a data pipeline to ingest a JSON file into the data warehouse, daily.
      1 réponse

      Entretien pour Data Engineer

      14 juill. 2023
      Candidat à l'entretien anonyme
      Aucune offre
      Expérience positive
      Entretien facile

      Candidature

      J'ai postulé en ligne. Le processus a pris 4 semaines. J'ai passé un entretien chez Whatnot en juin 2023

      Entretien

      NOTE: As per HR, there are only two levels in Software: Software Engineer, and Principal Software Engineer. I applied online. Following rounds: [x] 30 minutes with Hiring Manager [x] ≈1 hour coding interview. [x] ≈1 hour design interview. [x] 30 minutes product sense ----- Got the rejection email here, but they had 2 more rounds ---- [x] Behavioral [x] Conclusive round with Hiring Manager. The first round with Hiring Manager was more informal, just going into my past experience and details about the job vacancy. The coding round is Easy, this is simply a log-parsing and does not require prior LeetCode practice. The design round is where I got knocked out (I think). The problem statement is fairly simple: "Design a REST api for ML model" (using LucidSpark drawing tool). But the expectations weren't that obvious. The interview isn't being conducted as a standard design interview, and instead I should have read more about the interviewer's background and focus on those areas instead. I see that another candidate received a positive offer during the same time window when I interviewed. S/he used a slide deck (instead of using LucidSpark) for the design round. That's a better idea, instead of letting the interviewer drive that round, this would have given me more control over the discussion. Product sense: Like a regular product-sense interviews. What can you improve, or a feature, how would you measure the success of your proposed ideas, etc. Overall, my experience was positive. Assuming that I am right about the Design Interview results being the cause of rejection, I still think that I should have prepared better. Not the design part, the human-interview part. They're a startup, and the interviewers may have their own quirks, better prepare thoroughly. Anyway, it was a sad day; I really needed this job and I feel that I could've passed their evaluation criteria. Good luck to all other folks interviewing with them, this company has a good opportunity ahead of them if they play their cards right.

      Questions d'entretien [3]

      Question 1

      Coding: Write a function that parses user action logs. (Answer is easy once you understand the what is being logged. Solution uses Trie)
      Répondre à cette question

      Question 2

      Design: An API to serve livestream rankings to the client application.
      Répondre à cette question

      Question 3

      Product Sense: Is generic, but would mostly be around what to improve/add on Whatnot app/service.
      Répondre à cette question