Questions d'entretiens chez SpaceX | Glassdoor.fr

Questions d'entretiens chez SpaceX

Dernière mise à jour : 10 sept. 2018
566 Avis sur les entretiens

Expérience

Expérience
69%
18%
13%

Obtenir un entretien

Obtenir un entretien
51%
17%
15%
10
4
2
1

Difficulté

3,4
Moyenne

Difficulté

Difficile
Moyenne
Facile

Avis sur les entretiens d'embauche

Filtrer

Trier: PopulairesDateDifficulté

Filtrer

Trier: PopulairesDateDifficulté
  1.  

    Offre acceptée
    Expérience positive
    Difficulté moyenne

    Candidature

    J'ai postulé via une autre source. Le processus a pris 3 semaines. J'ai passé une entrevue à SpaceX (Paris) en juin 2015.

    Entretien

    I contacted them by email after watching a conference from SpaceX (NVIDIA GTC 2015). I got an answer within a few days and we scheduled a phone screen for the following week. A few hours before the phone screen I got contacted by HR to get various information about my GPA and school degrees. After the phone screen I was told I would have a second interview which I got a few days later. After the final interview I was told that I would be contacted by HR. In less than a 24H, HR told my that I was accepted for the intern.

    The two interviews start by asking you to sum up your prior work experience. Then they ask you a series of questions. At the end you are given the opportunity to ask them questions.

    Questions d'entretien d'embauche

    • 1) Difference between virtual and physical memory.
      2) Give my the 3 ways to copy an object in c++
      3) Difference between rvalue and lvalue and what are move semantics   1 réponse
    • Difference between compiled and interpreted language.   1 réponse
    • Why is it bad to throw exceptions in a virtual destructor   1 réponse
    • Difference between stack and heap   1 réponse
    • What is a cudastream   1 réponse

  2.  

    Entretien de Computer Engineer

    Candidat à l'entretien anonyme - Hawthorne, CA (États-Unis)
    Pas d’offre d’emploi
    Expérience positive
    Difficulté moyenne

    Candidature

    J'ai postulé en ligne. J'ai passé une entrevue à SpaceX (Hawthorne, CA (États-Unis)) en janvier 2017.

    Entretien

    An online coding challenge
    A phone interview
    Another phone interview
    A 48 hour coding challenge
    They fly you down to Hawthorne, CA to give a presentation on your final challenge/project. You get a chance to explain how and why you did it the way you did.

    Questions d'entretien d'embauche

    • "What is the size of an integer on a 32-bit system?"   5 Réponses
  3. Utile (3)  

    Entretien de Planner

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

    Candidature

    J'ai postulé en ligne. J'ai passé une entrevue à SpaceX en juin 2017.

    Entretien

    Started with a phone interview, then a half day in person with a 20 minute presentation. I ended up talking to a few different groups that had openings that the original manager thought I could be a good fit for as well.

    Questions d'entretien d'embauche


  4. Utile (11)  

    Entretien de Software Engineer

    Candidat à l'entretien anonyme
    Pas d’offre d’emploi
    Expérience négative
    Difficulté moyenne

    Candidature

    J'ai postulé en ligne. Le processus a pris 3 jours. J'ai passé une entrevue à SpaceX en avril 2014.

    Entretien

    I applied online on the company website. I received an email almost the next day with an invite to take 45-minute multiple choice C/C++ quiz. All questions were about finding the potential error in a short snippet of code. I finished the quiz quickly and got a reply 2 days later asking me to setup a time for a phone screen....

    Then, poof ! Nothing !! No reply from HR! Silence! I checked back twice, asking what happened. And nothing!! As if I applied to a fake company! Very unprofessional and rude! Well, thankfully I am employed so I don't need to work for these clowns. My advice is not to take employment at this company too seriously.

    Questions d'entretien d'embauche

    • When is the best time to contact you. That was difficult to answer because there was nobody from HR to arrange a phone interview with. They just ignore candidates.   2 Réponses

    Réponse de SpaceX

    15 avr. 2014 – Lead Recruiter

    Thanks for your message. We are very sorry to hear you had a negative experience. I believe this may have been caused by some email issues we experienced over the last couple weeks. Sporadic email... Voir plus


  5. Utile (7)  

    Entretien de Software Engineer

    Candidat à l'entretien anonyme
    Pas d’offre d’emploi
    Expérience négative
    Difficulté moyenne

    Candidature

    J'ai postulé via un recruteur. Le processus a pris 3 semaines. J'ai passé une entrevue à SpaceX.

    Entretien

    I went through multiple phone interviews, multiple choice coding quiz, plus a 6 hour coding project test. Passed them all very well. Was ready for on-site interview and they bailed because they couldn't pay my market value. This was a sad waste of time.

    Questions d'entretien d'embauche

    • Multiple choice 'what's wrong with this code' sort of test had multiple defects in the code and the choices didn't always match the situation well. Pick the one you think they want to hear and you'll do fine.   Répondre à cette question

  6. Utile (8)  

    Entretien de Software Engineer

    Employé anonyme - Hawthorne, CA (États-Unis)
    Offre acceptée
    Expérience positive
    Entretien dificile

    Candidature

    J'ai postulé via une recommandation d'un employé. Le processus a pris +2 semaines. J'ai passé une entrevue à SpaceX (Hawthorne, CA (États-Unis)) en août 2013.

    Entretien

    Tech screen by HR, 2 technical phone interviews, 6-hour on-site interview with 5 one-on-one sessions (2 tech, 3 not) and provided lunch.

    Phone interviews are to establish proficiency and basic coding approach.
    In-person technical sessions were split: one more daily-problem oriented, the other about known algorithmic solutions.
    Non-technical interviews were personality / philosophy / social.

    Feedback time between each step was 1-2 days.

    Questions d'entretien d'embauche

    • Some questions about framework internals, not generally relevant to day-to-day.   1 réponse

  7.  

    Entretien de Software Engineer

    Candidat à l'entretien anonyme - Hawthorne, CA (États-Unis)
    Pas d’offre d’emploi
    Expérience neutre
    Entretien dificile

    Candidature

    J'ai postulé en ligne. Le processus a pris 3 semaines. J'ai passé une entrevue à SpaceX (Hawthorne, CA (États-Unis)) en juin 2013.

    Entretien

    I applied via their website. One of their recruiters responded within a couple of days. Next was a 60-minute online multiple-choice quiz covering the basics of C++, C#, and SQL. It had 14 questions, and these could easily be answered in a small fraction of the total time given. I had plenty of time to double- and triple-check my work. Then was a phone interview with their recruiter, in which he asked about some things on my resume and asked me some more technical questions centering on data structures and algorithms. He wasn't a developer himself, but it seemed like their developers had provided these questions. Then were two more phone interviews, each with a different developer on their staff. These were done with a live collabedit.com session where they asked me to develop various algorithms live while on the phone with them.

    Questions d'entretien d'embauche

    • "Write a function implementing the _________ data structure" (various kinds including Stack and Binary Tree). Followed by, "Now rewrite your work without using loops", e.g. recursively.   1 réponse
  8. Utile (7)  

    Entretien de Software Engineer

    Candidat à l'entretien anonyme - Los Angeles, CA (États-Unis)
    Pas d’offre d’emploi
    Expérience négative
    Difficulté moyenne

    Candidature

    J'ai postulé en ligne. Le processus a pris +4 semaines. J'ai passé une entrevue à SpaceX (Los Angeles, CA (États-Unis)) en août 2013.

    Entretien

    I submitted my resume and some work examples through their website. The position I applied to was focused on Python software development in support of the Avionics hardware team. A few days later I was contacted by a recruiter saying there was interest. The first step was take an online C/C++ programming test. Initially I was worried because my background is much more Python-oriented. I should not have worried. The test was stuff that any serious programmer should know.

    The second step in the process was a technical interview with the software engineer who headed up this particular software team. It's been quite a while since I've done an interview (10+ years), and the "technical" part of this interview caught me a little by surprise. I have done more homework on this topic since then and I think the questions I was asked are probably typical. I fumbled around on a few, the rest I think I gave good answers. When I was uncertain, I made sure to talk through my thought process as I tried to find a solution.

    Towards the end I got somewhat negative feedback that my work experience might be too "researchy" for the position in question.

    The third step was a week-long programming challenge assignment. The topic was not at all technical or work related. I basically had to create a simple text console application in Python given a handful of requirements. I spent sooooo much time on this task! It was frankly a lot of fun. On the last day I misjudged my time and I was not able to meet all the requirements. I feel quite strongly that the work I put into that task very clearly shows my Python programming strengths. Given the earlier doubts I think they had about, I think this (small?) error on my part gave them an easy way to tell me "thanks, but no thanks."

    The recruiter told me that the only feedback he received from the engineer about my programming test was that it was incomplete, with no further details. My application was closed.

    The entire process took about a month. Many days would go by when I thought I was waiting for them to make the next step happen. When I would get in touch with the recruiter, it would turn he was waiting for info from the engineer, who in turn thought her part was done.

    Questions d'entretien d'embauche


  9. Utile (6)  

    Entretien de Software Engineer

    Candidat à l'entretien anonyme - Colorado Springs, CO (États-Unis)
    Pas d’offre d’emploi
    Expérience négative
    Entretien facile

    Candidature

    J'ai postulé en ligne. Le processus a pris 1 jour. J'ai passé une entrevue à SpaceX (Colorado Springs, CO (États-Unis)) en avril 2012.

    Entretien

    Applied on line for a software engineer position in their simulation group. Since I work on spacecraft simulation software for a living, I thought I'd be a good match. I received a quick response after applying and was asked to complete an online C/C++ programming quiz.

    Quiz consisted of low level programming questions (pointers, memory management, etc.), and was fairly easy. After completing the quiz, I received another email from a SpaceX recruiter telling me that I did well and he'd like to set up a phone interview with me. We agreed on a date and time, and when the appointed time came... no phone call. I attempted to call the recruiter and got sent to voicemail. I also sent an email. No response. I made a few more attempts over the next several days to communicate with this person (and another recruiter at SpaceX) to no avail.

    Fortunately I'm employed and have no shortage of prospects with the more established companies in the aerospace industry, so this is more annoying than anything else.

    What a bunch of disorganized clowns this company is. Don't waste your time with SpaceX.

    Questions d'entretien d'embauche

    • Would you like to set up a phone interview?   1 réponse

  10. Utile (15)  

    Offre acceptée
    Expérience positive
    Entretien dificile

    Candidature

    J'ai postulé en personne. Le processus a pris +4 semaines. J'ai passé une entrevue à SpaceX.

    Entretien

    The interview was definitely more advanced than for any other place I have applied for. Guidance was excellent throughout the process. My recruiter always communicated with me in a timely manner and clearly described the next steps. Here is an overview:

    * Call with recruiter
    Not technical, discussion on possible fit in the company.

    * 30min quiz
    Basic technical questions, really should not be a problem if you have the experience required for the job.

    * 60min call with an engineer
    Some advanced technical questions here (in my case, OS, networking, advanced C++), not extremely hard, as most of the answers should be known at a college level if you have taken the aforementioned classes.

    * 6-hour coding test
    This is where the real stuff begins. You have to provide a standalone program that solves a problem. You are in contact via email with an engineer who can review and run tests on your code.

    The problem itself was not very hard, but it's the time pressure that makes it hard. As mentioned in another review here, I definitely recommend coming prepared, so that you can directly attack the problem. I also suggest refreshing your knowledge on data structures.

    While the test focuses on the ability to efficiently design and implement a solution, it also tests your ability to make trade-offs given the tight deadline.

    * Full day on-site interview
    In my case, I was flown in the day before, fare and hotel paid for.

    We started with a tour of the impressive facility (just this part is worth giving your best on the 6-hour test!), before moving to a 30-60min panel interview on the 6-hour test above. This panel was much more technical than I expected, with advanced questions about things that were not in the original problem (eg: how to rewrite your program given a new XYZ constraint).

    After lunch I had three 1-on-1 technical interviews followed by a discussion with the director of engineering.

    We ended the day with a dinner with some members of the team (different than the ones who interviewed me). It was a great opportunity to talk about non-work-related things like housing, etc.

    In addition of being well prepared and being able to show that you love what you do, I would recommend to show that you are curious and professional. For example, if you fail to answer a question at any stage of the interview, you should be prepared to answer it (and more on that same subject) at the next stage.

    Also, have a good night sleep before the 6-hour test and the on-site: you need to be in your best shape to put all the chances on your side.

    Questions d'entretien d'embauche

    • What does C++ 'mutable' keyword does?   1 réponse

Ne manquez pas la possibilité d'obtenir un emploi que vous adoreriez
Ajoutez un CV pour postuler facilement à des offres depuis n'importe où. Il est facile à configurer.