Zum Inhalt springenZur Fußzeile springen
  • Jobs
  • Unternehmen
  • Gehälter
  • Für Arbeitgeber

      Deine Karriere auf Höhenflug

      Erfahre, was du verdienen könntest, ergattere deinen Traumjob und tausche dich anonym über dein Berufs- und Privatleben aus.

      employer cover photo
      employer logo
      employer logo

      Amazon

      Aktiver Arbeitgeber

      Info
      Bewertungen
      Vergütung & Zusatzleistungen
      Jobs
      Interviews
      Interviews
      Ähnliche Suchanfragen: Bewertungen für Amazon | Jobs bei Amazon | Gehälter bei Amazon | Zusatzleistungen bei Amazon
      Vorstellungsgespräche bei AmazonResearch Scientist, Machine Learning – Vorstellungsgespräche bei AmazonVorstellungsgespräche bei Amazon


      Glassdoor

      • Über uns
      • Auszeichnungen
      • Blog
      • Kontakt
      • Ratgeber

      Arbeitgeber

      • Gratis Arbeitgeberkonto
      • Arbeitgeberbereich
      • Blog für Arbeitgeber

      Informationen

      • Hilfe
      • Richtlinien
      • Nutzungsbedingungen
      • Datenschutz & Anzeigenoptionen
      • Meine Daten nicht verkaufen oder weitergeben
      • Cookie-Zustimmungs-Tool

      Partner werden

      • Werbeanbieter
      App herunterladen

      • Suchen nach:
      • Unternehmen
      • Jobs
      • Standorte

      Copyright © 2008-2026. Glassdoor LLC. „Glassdoor”, „Worklife Pro”, „Bowls” und das Logo sind eingetragene Warenzeichen von Glassdoor LLC.

      Beobachtete Unternehmen

      Verschaffe dir einen Vorsprung bei Chancen und Insider-Tipps, indem du deinem Traumunternehmen folgst.

      Vorstellungsgespräch für eine Beschäftigung als Research Scientist, Machine Learning

      2. Sept. 2018
      Anonymer Bewerber im Vorstellungsgespräch
      Kein Angebot
      Neutrale Erfahrung
      Durchschnittl. Gespräch

      Bewerbung

      Ich habe mich online beworben. Der Vorgang dauerte 3 Wochen. Vorstellungsgespräch absolviert im Juli 2018 bei Amazon

      Vorstellungsgespräch

      Recruiter emailed me to set up appointment. I gave a number of blocks of time when I was available to do the interview. I didn't hear back from them and, in the mean time, a meeting was scheduled at work resulting in one of the blocks of time to no longer be available. I contacted the recruiter to inform her that one of the blocks of time were no longer available. The next day, they schedule the phone interview for precisely when my meeting occurred. I contacted and phoned the recruiter to ask if I could push the phone interview later because of a meeting that was scheduled that I couldn't miss at work. Time passed and the recruiter never contacted me. Another recruiter/HR person called me, not at the phone number I had given, but on my cell phone to tell me that they can push the phone interview later. I was somewhat surprised that a company that prides itself on logistics would be a tad bit sloppy with the logistics of setting up the phone interview. Nonetheless, the interviewer explained the structure of the interview, they ask open ended questions and I would answer them. They gave a general idea of the areas on which the questions would be asked. The interviewer spoke really really really fast and came across as trying to artificially create a pressure filled environment, which came across as very weird. The first question concerned a linked-list data structures question. It seemed strange since the position was a research position and not a software-engineering position. Easy enough, but I was still taken off guard as I was hoping for a Machine Learning question as that is my background and that is what the position concerned. I explained how one would implement a sorting algorithm, then the two alternatives for finding median based on whether you had an even or odd number of items in the linked list. They actually wanted a description of what the code would do, so I explained you implement a while loop iterating as many times as described by the indices computed for obtaining the median. The "how would you actually implement it" was a strange question as it isn't really the focus of what a researcher will solve, at least not in Machine Learning. Then the topic turned to a general design question. They asked where I would start if I were designing a robot lawn mower. I began with what I would have my team do. They interrupted me and said, what if you didn't have a team and it was just you. This process of frequently interrupting me and changing the scope or scenario occurred throughout my interview. After a point, I had lost interest in the job during the interview. Anyway, I began with requirements and how I would actually mow lawns and talk to landscapers who mow lawns to understand the environment, variations, types of equipment and issues encountered with mowing laws; that is understand the domain. Again, I was interrupted and the scope shifted to assume someone had solved all the mechanical problems and implemented the hardware platform. They were asked where would you start. OK, so I began with the sensors I would use (Camera, Lidar, etc.) and before I could start to explain sensor fusion and localization, I was interrupted and the scope was changed to cameras only. So, I explained the types of features you might extract from the camera in addition to a system of beacons to make the problem easier. They interrupted again to say what if you didn't have beacons and only cameras. OK, so I described the issues with both navigation and detecting the boundaries of the lawn to be mowed in addition to detection of objects. They interrupted me again asking where I would put the camera. I described multiple cameras, one forward facing and another with a hemispherical panoramic lens. As I continued to describe the system, they interrupted me again asking how I would recognize people. I explained you are concerned about living things in general and that a thermal camera could be added to detect warm bodies in addition to motion queues. They interrupted me again scoping the problem based on static images. I described a skeletal model. They asked my how I would literally implement it. I described at a high level a parts based model because the person might be partially occluded. They asked specifically how I would implement the parts based model. Then they changed the topic to give an example where I was on a project that did not work out as planned. I described this and they asked who made the decision. Then they asked me to give an example of a project where I had multiple alternatives from which to choose for components and what choice I made. Then they asked me if I had any questions. I asked how about a Machine Learning question? They didn't really have an answer only that the allotted time for my interview was done.

      Fragen im Vorstellungsgespräch [4]

      Frage 1

      You have a linked list of numbers, how would you return the median ? Follow up, what is the worst case performance?
      1 Antwort

      Frage 2

      If you were designing a robot lawn mower, where would you start? Various follow ups including sensors, limited to cameras, where mounted? How would you recognize people? Describe skeletal model?
      1 Antwort

      Frage 3

      Describe a project where things didn't work out as expected.
      1 Antwort

      Frage 4

      Describe a project where there were multiple alternatives from which to choose in implementing it.
      1 Antwort
      3

      Weitere Bewertungen zu Vorstellungsgesprächen als Research Scientist, Machine Learning bei Amazon

      Vorstellungsgespräch für eine Beschäftigung als Research Scientist, Machine Learning

      1. Aug. 2018
      Anonymer Bewerber im Vorstellungsgespräch
      Kein Angebot
      Negative Erfahrung
      Durchschnittl. Gespräch

      Bewerbung

      Ich habe mich online beworben. Der Vorgang dauerte 1 Tag. Vorstellungsgespräch absolviert im Juli 2018 bei Amazon

      Vorstellungsgespräch

      They were somewhat sloppy with phone interview logistics, ignoring email about available times and calling me at the wrong phone number. This somewhat killed my interest in the position. For a company who prides themselves on excellence in logistics, this surprised me. Also interesting is that their scheduling system assumed PDT and did not translate to EDT time zone. The interview was very strange. They were artificially manufacturing a pressure filled feel to the interview by talking very fast, constantly interrupting me and changing the scope and question as I answered. While English is my native language, I grew up Speaking non-American English, so the interviewer speaking really fast made it difficult at times for me to understand what they were asking. The interview material was pretty standard. There was a very specific and basic data structures question and an open ended question. The basic data-structures question on sorting a list and finding the median caught me by surprise, since in my experience it is not typical asked for a research scientist position as there are more advanced things one might expect from a research scientist. Anyway, I answered the question explaining how the sorting algorithm works but forgot what it was called. I gave them the algorithmic complexity (big-Oh) and they switched to the open ended topic. The open ended topic involved a robotic device. It took me as strange since the position was not for a Machine Learning position in robotics, rather it was for the Amazon Go group. Anyway, I began with how one must first understand the domain, as you cannot design a robot for an activity when you don't understand the variations, dynamics, etc. for said activity. Nonetheless, the interviewers were not interested in any of that. They changed the focus, interrupting, to concentrate solely on perception. I began describing the sensor package, what issues arise in the task, and justifying the sensor choices. Again they interrupted me limiting only to cameras. OK, so I described what type of features I would use and why, then they interrupted me again asking "where would you put the camera?" I answered that question and then they asked about detecting people. The best solution was a thermal camera and I answered that one is not just concerned about people, but any living thing as you wouldn't want the lawnmower to run over your dog. So they interrupted and changed the question again asking how would you detect people with a regular camera. I described a traditional approach using images. They interrupted again and asked what if the person is partially occluded. I answered that you could implement a parts based skeletal model. They asked me how, specifically I would implement it. I answered that. Then they changed the subject saying that you are discussing video and have motion information, how would you do that using static images. I described a shape based approach for computing a skeleton of the subject and effectively testing it against an idealized model based on the blob height for the foreground object. Then they asked me how would I pick up images from the camera I described earlier using features for navigation. I introduced a second camera pointing forward that had a hemisphere sense to pick up a 270-degree cone. I also described a semi autonomous version where you place beacons at the vertices of the lawn's polygon and use a harmonic function to repel the robot around obstacles. They switched topics again, this time to scenarios about when I had to make a difficult decision because a project objective couldn't be satisfied. They also asked about a time when I had many different alternatives for a project and how I decided how to proceed. The position was for Machine learning, but the bulk of the questions concerned Computer Vision and data-structures. I had even asked them, "aren't you going to ask me a Machine Learning question?" In all, it appeared they were more interested in how you would implement versus understanding how something might work and why you would chose certain approaches. It became very clear that for this position, they are more interested in Development and Implementation than Research. This is a very applied position and perhaps should be advertised as such. Nonetheless, I wish them the best of luck. If offered the job, I wouldn't have taken it as it was not the right fit. They sent me an email that they are not continuing further. The strange part was that it said that their policy is that they do not share feedback the interviewers had as to why they do not further pursue.

      Fragen im Vorstellungsgespräch [4]

      Frage 1

      If you were designing a robot lawnmower, where would you start?
      1 Antwort

      Frage 2

      You have a singly linked list, how would you find the median?
      1 Antwort

      Frage 3

      Describe a scenario where a project wasn't going to work, what did you do?
      Frage beantworten

      Frage 4

      Describe an example where you had multiple alternatives to choose from for tools/approaches for a project. How did you go forward?
      Frage beantworten

      Die besten Unternehmen in der Kategorie „Vergütung & Zusatzleistungen“ in deiner Nähe

      avatar
      Google
      4.5★Vergütung & Benefits
      avatar
      Meta
      4.6★Vergütung & Benefits
      avatar
      Amazon Web Services
      3.9★Vergütung & Benefits
      avatar
      payever
      4.1★Vergütung & Benefits

      Jobsuchen

      Erhalte personalisierte Jobempfehlungen und Updates, indem du Suchanfragen startest.