Questions entretien Software Engineer In Test chez Google | Glassdoor.fr

Questions entretien Software Engineer In Test chez Google

Entretiens chez Google

56 Avis sur les entretiens

Expérience

Expérience
55%
31%
14%

Obtenir un entretien

Obtenir un entretien
39%
27%
18%
10
6

Difficulté

3,5
Moyenne

Difficulté

Difficile
Moyenne
Facile

 

Entretien de Software Engineer In Test

Candidat à l'entretien anonyme - Mountain View, CA (États-Unis)
Aucune offre d'embauche
Expérience négative
Difficulté moyenne

Candidature

J'ai postulé via une autre source. Le processus a pris +2 semaines. J'ai passé un entretien à Google (Mountain View, CA (États-Unis)).

Entretien

LinkedIn HR called, phone interview, then onsite interviews, HR was calling frequently to update status (good), one of the interview was just too cold, he wasn't very responsive throughout

Questions d'entretien d'embauche

Autres avis d'entretien pour Google

  1. Utile (15)  

    Entretien de Software Engineer In Test

    Candidat à l'entretien anonyme
    Offres d'embauche déclinées
    Expérience neutre
    Difficulté moyenne

    Candidature

    J'ai postulé via un recruteur. Le processus a pris +4 semaines. J'ai passé un entretien à Google.

    Entretien

    I previously interviewed at Google and was denied an offer. I was contacted about a year later by a recruiter who believed she found a role that fit me better. We skipped the phone interview, and went straight to a 3 person on site interview. I was given an offer about two weeks later.

    When they found that I had a competing offer, the recruiter starting pushing very hard for me to join. This included everything from giving me more money, having me talk to people, and even bashing the other company.

    Questions d'entretien d'embauche

    • Given a string, convert it into a palindrome with the lease number of insertions possible.   3 Réponses

    Raison du refus

    In the end, the position just sounded pretty boring. Despite my attempts to clarify my interests, they either didn't notice or didn't care.


  2. Utile (8)  

    Entretien de Software Engineer In Test

    Candidat à l'entretien anonyme
    Aucune offre d'embauche

    Candidature

    J'ai postulé via un recruteur. Le processus a pris une semaine. J'ai passé un entretien à Google.

    Entretien

    Contacted by a recruiter via linked who scheduled a technical phone interview screening within a week. The recruiter alos provided interview prep materials and links to helpful resources.
    The interview was a typical google interview - asked to answer a question on google docs. There was some background noise during the interview, I could here people playing ping pong or something.

    Advice: Schedule your interview earlier in the day.

    Questions d'entretien d'embauche

  3.  

    Entretien de Software Engineer In Test

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

    Candidature

    J'ai postulé via un établissement de l'enseignement supérieur ou universitaire.. Le processus a pris +7 mois. J'ai passé un entretien à Google en mai 2014.

    Entretien

    In October 2013, I attended a conference in Baltimore and I left my resume and contact information at the booth of Google during a career fair.

    I received an email in April 2014 from an HR in which she asked me for an informal interview/conversation over the phone. Since I'm still pursuing my B.S., the interview process will consist of a technical interview over the phone and an onsite interview if I was successful during the first round. In my conversation with the HR, we just went through all my academic background and we agreed on a date for the following technical interview.

    I had the technical interview on May 15, 2014 and it consisted on two programming questions using bit manipulation. I got to choose the programming language to use on that interview and I chose C since I have been working with it lately. However, I was fully aware that I was not knowledgeable enough with the programming language and although I tried to prepare as best as I could, I knew that my performance was going to be far from stellar.

    I managed to give decent responses for the problems, although in my second question I did not get a correct implementation. We were trying to use a Google doc to write down the question and for me, to code the answer. However, for some reason, the Google doc was extremely slow and sometimes wouldn't update at all. I tried to code my answers over a simple text editor and then paste them to the Google doc but at the end the interviewer and I gave up and I emailed my coding answers to my HR contact instead.

    A week later, I received a call from the HR with some feedback about the interview and unfortunately, I didn't make it to the second round. Overall it was a good experience and my very first technical interview. It gave me more insight into what I need to focus whenever I have opportunities like these in the future. It was a very good learning experience and both my HR contact and interviewer where very nice, professional, and detail-oriented in their attention.

    Questions d'entretien d'embauche


  4. Utile (1)  

    Entretien de Software Engineer In Test

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

    Candidature

    J'ai postulé via un recruteur. Le processus a pris +2 mois. J'ai passé un entretien à Google en mars 2014.

    Entretien

    I was contacted by a recruiter that met me on a career fair for my university. They were interested in receiving an application from me and so I decided to apply. About a month after I sent in my resume they contacted me and said they would like to setup a phone interview. The phone interview was pretty great - the lady that was interviewing me was extremely friendly and calmed my nerves. I do terribly on phone interviews because phone conversations make me nervous (no idea why). I did pretty badly and only got to the second interview question out of 3 ( I later found out from talking to her on the onsite interview day that she had 3 questions to ask me and the first 2 were just warmups). However, she liked my personality and said I walked her through my thought process very well. A few weeks later I was told that I had been invited for a series of on site interview (5). The first interview went badly as I was very nervous, but the last 4 went very well. About 2 weeks later I was contacted one final time and notified they would not be extending me an offer. I had no time to prepare/study anything for either the phone or the onsite interviews due to a heavy course load (70 hours or so of homework a week), so I feel I did well considering. If I had time to prepare/study I feel confident I would have gotten the position. Overall the experience was very positive - they communicated very clearly at all times and everyone involved in the entire process was extremely professional and friendly.

    Questions d'entretien d'embauche

    • All questions were fairly equal in difficulty - I managed to just finish solving them right as the interview with each person ended.   Répondre à cette question

  5. Utile (2)  

    Entretien de Software Engineer In Test

    Candidat à l'entretien anonyme
    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 +2 semaines. J'ai passé un entretien à Google en janvier 2014.

    Entretien

    One round phone interview. The HR helped me to set up the phone interview. It took around 45 min. The questions were not touch. At first, serveral questions about the java. And one coding question. Keep communication during the interview.

    Questions d'entretien d'embauche

    • Not difficult. It is like why can not compare two strings. And how to compare one object which initialed as a string with string. The coding quesition is to find the kth in two sorted arrays.   5 Réponses

  6. Utile (1)  

    Entretien de Software Engineer In Test

    Candidat à l'entretien anonyme
    Aucune offre d'embauche
    Difficulté moyenne

    Candidature

    J'ai postulé en ligne. Le processus a pris 2 semaines. J'ai passé un entretien à Google en avril 2014.

    Entretien

    1. HR talk about the position and ask some questions about my background.
    2. Scheduled a telephone technical interview.
    3. A technician from Washington D.C called to do the interview.

    The technician is really nice. We talked a lot about the Google working progress and environment. And he talked about major task for SET in Google.

    Questions d'entretien d'embauche

    • 1. determine the overlap.
      2. write test cases based on 1
      3. give an input stream like 1010x0x1, give all the result that transfer x into 0 or 1   1 réponse

  7. Utile (3)  

    Entretien de Software Engineer In Test

    Employé anonyme
    Offre d'embauche acceptée
    Expérience positive
    Entretien dificile

    Candidature

    J'ai postulé via une recommandation d'un employé. Le processus a pris +2 mois. J'ai passé un entretien à Google en mai 2014.

    Entretien

    I had a phone screen and then an on-site interview, which consisted of 5 1:1 technical interviews. Google tends to avoid behavioral questions and focuses mostly on coding and past project work. Getting through the hiring committee, team alignment, and SVP approval, which is all needed to generate the actual offer, takes a while, which can be problematic if you get a competing offer in the interim.

    Questions d'entretien d'embauche

    • I can't give away actual questions, but on some occasions, the answer lies in thinking outside the box and going beyond the pass/fail framework of most test cases in defining success. Sometimes whether the product or feature works or not cannot be boiled down to a simple binary.   Répondre à cette question
  8.  

    Entretien de Software Engineer In Test

    Candidat à l'entretien anonyme - Mountain View, CA (États-Unis)
    Aucune offre d'embauche
    Expérience positive
    Entretien dificile

    Candidature

    J'ai postulé en ligne. J'ai passé un entretien à Google (Mountain View, CA (États-Unis)) en avril 2014.

    Entretien

    I applied online, contacted by HR, then got 1 phone screen interview, passed that then 4 onsite interviews. after 2 weeks entered hiring committee process but got rejected at last.

    Questions d'entretien d'embauche


  9. Utile (4)  

    Entretien de Software Engineer In Test

    Candidat à l'entretien anonyme - Mountain View, CA (États-Unis)
    Aucune offre d'embauche
    Expérience positive
    Entretien dificile

    Candidature

    J'ai postulé en ligne. Le processus a pris +4 semaines. J'ai passé un entretien à Google (Mountain View, CA (États-Unis)) en mai 2014.

    Entretien

    Applied online, and was contacted by a recruiter a few days after. Had one phone interview shorty after involving coding one algorithm question in a shared Google Doc. Then invited out to Mountain View for four technical interviews over the course of one day. Everyone was very professional, and despite what I had heard, very prompt. Unfortunately, they could not give me any feedback.

    Questions d'entretien d'embauche

    • Pretty standard algorithm/data structure questions. Reading Cracking the Coding Interview helped a lot.   Répondre à cette question

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