Questions entretien Data Scientist chez Adobe | Glassdoor.fr

Questions entretien Data Scientist chez Adobe

Entretiens chez Adobe

16 Avis sur les entretiens

Expérience

Expérience
56%
19%
25%

Obtenir un entretien

Obtenir un entretien
26%
27%
20%
20
7

Difficulté

3,4
Moyenne

Difficulté

Difficile
Moyenne
Facile

Utile (1)  

Entretien de Data Scientist

Candidat à l'entretien anonyme
Aucune offre d'embauche
Expérience négative
Difficulté moyenne

Entretien

A recruiter contacted me regarding an opening in the Emeryville office, he was very polite and nice and scheduled a phone screening with the hiring manager. The hiring manager called, he didn't know which candidate he was speaking with! He kept asking open-ended questions and hung up as soon as I finished answering the last question and they didn't get back to me to give me any feedback as to whether they decided to move forward or not.

Questions d'entretien d'embauche

Autres avis d'entretien pour Adobe

  1.  

    Entretien de Data Science

    Candidat à l'entretien anonyme
    Offre déclinée
    Expérience neutre
    Entretien facile

    Candidature

    J'ai postulé via une recommandation d'un employé. J'ai passé un entretien à Adobe.

    Entretien

    two rounds interview. The first one is coding and second one is machine learning related problems + probability (100 coins, one of them is double head, compute the probability of getting a double head if when flipping a coin the turnout is head, explain plainly why the probability is doubled)

    Questions d'entretien d'embauche


  2. Utile (3)  

    Entretien de Data Scientist

    Candidat à l'entretien anonyme
    Offre déclinée
    Expérience négative
    Entretien dificile

    Candidature

    J'ai postulé via un recruteur. J'ai passé un entretien à Adobe en janvier 2019.

    Entretien

    After a chat with recruiter, we had two phone interviews, then the onsite.

    Recruiters were nice people, but they give ZERO information about what the interview is gonna be about. They say "it's gonna be a mix of technical and case study," but that's pretty much it. I'm not sure if it's the company policy to hide such info from the candidates (in that case, I cannot fault recruiters) or not, but I've never seen a company where recruiters were this clueless about the interview structure. They pretty much threw out the onsite interview time and 6 interviewers I'll be meeting like only few days before the onsite interview (it was just hey~ u'll have interview from X AM to Y PM, and these 6 people are names of your interviewers type of e-mail, zero info about who's gonna ask what types of questions), but since it overlaps with lunch time, I expected the one of the interviews would be lunch interview, but there was none. The recruiter didn't bother to tell me that, so I was hungry throughout the interview process.

    The gap between two phone interviews and onsite interview was gigantic. I don't know if it was just me or that's the general case with Adobe data scientist interview. In the first phone interview, I was given a very easy question that can be solved via hash map, and the second phone interview was super basic ML and case study that involves t-test.

    However, the onsite interview was MUCH MUCH more technical. They asked graduate-level stat questions (something in the ballpark of sketching the steps of PLS and stating conditions for convergence of Newton's method or not), and the case study questions were SUPER SPECIFIC to what that team was doing.

    Overall, 4 of 6 interviewers were nice people, but the other 2 were not, especially the last one. One told me that I don't look good, and I told him "sorry, I'm a bit hungry," and then he was like "you should've eaten some food during lunch interview, who was your lunch interviewer?" I told him they didn't include lunch interview, then he went on to boasting about he once had a time when he didn't get any sleep and food and still did fine on the interview and got an offer: it was pretty obvious that he was insinuating I should do the same. And then he went on to saying my job experience doesn't seem to match the level of position I was applying, so I should seriously consider taking a level down, so I was like "eh.. ok."

    However, it was really the last one that threw me off. From the beginning, he had this "why the hell should I be here" face, and then quickly introduced himself (starting from where he went for his undergrad, which I was not even curious about) and then didn't even ask me to introduce myself. That's fine, but then he took out a piece of paper, which seemed to be my resume, and then said the same thing that the other not-so-nice guy said: my job experience doesn't seem to match the level of position that I applied.

    First, I didn't apply to that position. Recruiter contacted me through linkedin and then sent me the position and asked me to apply for it, which I did. It was kinda annoying to hear the same thing twice, especially from a seemingly rude man, but I said ok.

    Then he asked a super specific case study question, to which I gave my best guess, but then he laughed (not for long, but for a very brief period), and gave me one hell of a condescending look and said "no," and then moved on to next question.

    Usually, when I interview someone, if they don't answer correctly first time, I give them some hints and give them another chance. This guy just scoffed and then moved on to next question.

    Then the interview was over. I went to airport, super-hungry, ate two hamburgers and then flew to my home. A week later, miraculously (I thought I was done after the last interview), I somehow got an offer, but as expected, a level below what I applied for, and the offer was very bad (considering tax, price level, even lower than what I'm currently making), and on top of that, my interview experience was far from good. I politely rejected the offer.

    Questions d'entretien d'embauche

    • I signed NDA, so I cannot state the exact questions. Since the phone interviews were super easy, I'll give questions similar to what the onsite questions were like:

      1) Sketch the proof for convergence of K-means algorithm
      2) State how AUC will change depending on the threshold
      3) Derive the MLE for linear regression and show how you would use it.   1 réponse
  3.  

    Entretien de Data Science

    Candidat à l'entretien anonyme - San Jose, CA (États-Unis)
    Aucune offre d'embauche
    Expérience négative
    Entretien dificile

    Candidature

    J'ai postulé via un recruteur. Le processus a pris 2 semaines. J'ai passé un entretien à Adobe (San Jose, CA (États-Unis)) en janvier 2019.

    Entretien

    Contacted by recruiter on hiring platform. Suitable role for my profile. Asked for availability for 45 min phone interview for the following week. But, the recruiter scheduled the interview for the very next day without checking my availability - I thought that was ridiculous.

    The interview itself was not very smooth and too demanding for a first round phone screen.

    Questions d'entretien d'embauche


  4. Utile (1)  

    Entretien de Data Scientist

    Candidat à l'entretien anonyme
    Aucune offre d'embauche
    Expérience négative
    Entretien dificile

    Candidature

    J'ai postulé via un recruteur. Le processus a pris une semaine. J'ai passé un entretien à Adobe en janvier 2018.

    Entretien

    HR scheduled two phone interviews, both of them were either delayed or cancelled. It was the worst experience I've ever had in my life. I was asked only one hard level leetcode question in the first coding interview and I was informed rejected after the absence of my second interviewer. It was completely wasting my time (waiting for the missing interviewer) and I highly doubt the structure of their interview setup (what's the point of judging data science knowledge by a single hard leetcode problem?) They could have hired an SE if that's what they wanted.

    Questions d'entretien d'embauche

    • Similar to the basic calculator problem in leetcode.   2 Réponses

  5. Utile (3)  

    Entretien de Data Scientist

    Employé anonyme - San Jose, CA (États-Unis)
    Offre acceptée
    Expérience positive
    Difficulté moyenne

    Candidature

    J'ai postulé via une recommandation d'un employé. J'ai passé un entretien à Adobe (San Jose, CA (États-Unis)) en juillet 2017.

    Entretien

    A friend referred me for the position. The recruiter set up two phone screens. One for Statistics and one for coding. Got the invitation for onsite the next week. I interviewed at San Jose.

    Questions d'entretien d'embauche

    • Create confidence intervals for finite sampled population   2 Réponses
    • Logistic Regression vs Collaborative Filtering for Large Scale Categorical Variable output regression with a large number of features   1 réponse

  6. Utile (3)  

    Entretien de Data Scientist

    Candidat à l'entretien anonyme - San Jose, CA (États-Unis)
    Aucune offre d'embauche
    Expérience positive
    Difficulté moyenne

    Candidature

    J'ai postulé via une recommandation d'un employé. J'ai passé un entretien à Adobe (San Jose, CA (États-Unis)) en mai 2017.

    Entretien

    I had an interview with four interviewees in a row for 30 mins each. It was on-site 1-1 interview. They were very kind and chill! Definitely, working environment looks awesome.

    Questions d'entretien d'embauche

    • Explain about correlation colored plot and make a story about a plot drawn on a white board. Also, technical questions were about data structure in Python/R and modeling experiences.   Répondre à cette question

  7.  

    Entretien de Data Scientist

    Candidat à l'entretien anonyme - Minneapolis, MN (États-Unis)
    Aucune offre d'embauche
    Expérience positive
    Difficulté moyenne

    Candidature

    J'ai postulé via un établissement de l'enseignement supérieur ou universitaire.. Le processus a pris 3 semaines. J'ai passé un entretien à Adobe (Minneapolis, MN (États-Unis)) en avril 2017.

    Entretien

    Initial interview was a phone call, was more of non-technical. In a weeks time had 45 min technical interview on Coderpad which went well. I was then given a take home test.

    Questions d'entretien d'embauche

  8. Utile (1)  

    Entretien de Data Scientist

    Employé anonyme
    Offre acceptée
    Expérience positive
    Difficulté moyenne

    Candidature

    J'ai postulé via un établissement de l'enseignement supérieur ou universitaire.. Le processus a pris 2 semaines. J'ai passé un entretien à Adobe en février 2017.

    Entretien

    I was recommended by a company member. The member talks to me first and asks me some backgrounds. Then he said to me that he would contact me in a week. After one week, two research data scientists contact me and ask me some technical questions including my research topics, statistics, and coding techniques. The process is technical but I think they care more about research ability.

    Questions d'entretien d'embauche

    • Q1: tell about your research topics and what is the difference between your methods and classic methods   1 réponse
    • Q2: What kind of coding language you use in handling large-scale dataset.   1 réponse

  9.  

    Entretien de Data Science

    Employé anonyme
    Offre acceptée
    Expérience positive
    Difficulté moyenne

    Candidature

    J'ai postulé via une recommandation d'un employé. J'ai passé un entretien à Adobe en février 2017.

    Entretien

    Got referred through a friend at Adobe. There were 2 rounds of interviews:
    1) Programming round: Questions that involved arrays, dynamic programming, memoization etc. It was mostly about the pseudo code and not about the actual code.
    2) Probability, Statistics and general ML round: Started with basic questions about distributions. Then some questions about linear regression, logistic regression etc.

    Questions d'entretien d'embauche

    • How to calculate the most frequently occurring entry on huge data over different severs?   1 réponse

Ne manquez aucun emploi que vous aimez
Ajoutez un CV pour postuler facilement à des offres depuis n'importe où. C'est simple à configurer.