Questions entretien Test Engineer chez Motorola Solutions | Glassdoor.fr

Questions entretien Test Engineer chez Motorola Solutions

Entretiens chez Motorola Solutions

5 Avis sur les entretiens

Expérience

Expérience
80%
0%
20%

Obtenir un entretien

Obtenir un entretien
60%
20%
20%

Difficulté

3,5
Moyenne

Difficulté

Difficile
Moyenne
Facile

Utile (3)  

Entretien de Test Engineer

Employé anonyme - Schaumburg, IL (États-Unis)
Offre d'embauche acceptée
Expérience positive

Candidature

J'ai postulé en ligne. Le processus a pris 5 semaines. J'ai passé un entretien à Motorola Solutions (Schaumburg, IL (États-Unis)) en mai 2016.

Entretien

The interview process was good so far.The process took 4 weeks till now. I am Scheduled for in person next week for next week. I was asked for more of technical questions so far with few behavioral questions.Any suggestions or comments that could help are appreciated.

Questions d'entretien d'embauche

Autres avis d'entretien pour Motorola Solutions

  1. Utile (6)  

    Entretien de Test Engineer

    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 +5 semaines. J'ai passé un entretien à Motorola Solutions en janvier 2015.

    Entretien

    I was contacted by a recruiter in which they gave me a 13 question questionnaire to fill out, in which I had already filled out months ago for the same position whereas I believe the other recruiter never even submitted me. At the time, it took me about 7 hours to do, the recruiters both thought it was a quick and easy thing that'll take like an hour or two. The questionnaire is 13 long answer questions, asking for tables and detailed plans, in some cases. After the recruiter this time actually submitted me to the manager to look it over, about a month later they requested an interview. I arrived at their Holtsville, NY location and walked in to a room with three women, two managers and one team lead. The interview started out very standard, as one manager asked me to take a couple of minutes to describe my background, education, and work experience. Then the lady said something odd but it was not totally out of nowhere, she said do I know what kind of position this is and what its for. Seemed a little arrogant to me, but I quickly realize she is saying this because it's a testing role and not a development role. They moved onto going over my questionnaire, and then the interview went downhill very quickly. Out of the 5 questions I sat there to go over, I got every single one wrong. They gave me paper and explained the questions again and made me redo them. This was highly unusual in my opinion, it's not like some kind of makeup test, it's an interview. They received this questionnaire in advance from the recruiter, and THEY were the ones that requested I come in for an interview. If I got all or almost all of the questions wrong on this questionnaire that they deemed so important, why even bother setting this interview up? Redoing the questions was extremely nerve wracking and they expected me to understand these questions (that I didn't understand in the first place, apparently) right away after explaining and giving me "hints." I will say again, what is this, a study group? The team lead was going over a programming question which was actually very simple but I didn't give a proper example (I gave an example of an in scope variable instead of out of scope) so then she wanted EVERY example that would fit into what I already wrote, but she wasn't listening to what I had to say unless I said everything in the proper order of her line of thought. They were shooting me hypotheticals like what if you took out a word how would you get an out of scope error. I don't know what they were really getting at with these questions, since it wasn't a programming job and I learned in college to how to properly program, not how to generate errors. That just seems like useless knowledge. They were at the sixth or seventh question I believe (they had me reading them to the group, I don't know why) and this was the icing on the cake. There was a question to write a test plan, which I've heard of before but I've never actually written one. They started off saying it was clear I've never written a test plan, which was true, but they didn't know why I didn't look it up. The team lead goes on and repeats several times that she doesn't understand why I didn't search on the web for a test plan and copy one of the templates, implying I was too stupid or incapable of doing such a thing. This was the last straw, I apparently had no acceptable answers on the questionnaire they were going over, they had me redoing the questions, and now they were straight up insulting me! I stood up, thanked them for their time, and walked out. I don't think they even said a word in rebuttal. So far, it's been my worst interview experience of all time.

    Questions d'entretien d'embauche

    • How many gallons of gasoline is used by New York City each week?   2 Réponses

  2.  

    Entretien de Test Engineer

    Employé anonyme - Schaumburg, IL (États-Unis)
    Offre d'embauche acceptée
    Expérience positive
    Difficulté moyenne

    Candidature

    J'ai postulé via une recommandation d'un employé. Le processus a pris 2 jours. J'ai passé un entretien à Motorola Solutions (Schaumburg, IL (États-Unis)) en août 2012.

    Entretien

    I had a brief meeting with a manager in the test organization. I then interviewed with two senior testers. The questions were typical and job related. There were no off the wall "what kind of tree would you be" questions. The interviewers provided clear, understandable answers to all of my questions.

    Questions d'entretien d'embauche

  3. Utile (1)  

    Entretien de Test Engineer

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

    Candidature

    J'ai postulé via une recommandation d'un employé. Le processus a pris 2 semaines. J'ai passé un entretien à Motorola Solutions (San Jose, CA (États-Unis)) en juin 2010.

    Entretien

    Interview process involved Phone screening followed by onsite interview. Interview process was smooth with quick , the whole process took 2 weeks. The interview questions were regular engineering questions, with moderate difficulty level. Knowledge of networking protocols, test tools, scripting experience and test methodologies was expected.

    Questions d'entretien d'embauche


  4. Utile (2)  

    Entretien de Test Engineer

    Employé anonyme - Kraków (Pologne)
    Offre d'embauche acceptée
    Expérience positive
    Difficulté moyenne

    Candidature

    J'ai postulé via une recommandation d'un employé. Le processus a pris 2 jours. J'ai passé un entretien à Motorola Solutions (Kraków (Pologne)) en avril 2016.

    Entretien

    It was very quick, i applied, and the day after that i've gotten a call to schedule an interview.
    After interview i've got call the next day with an offer.
    The people i have been in contact with were very helpful and pleasant.
    Managers and Technical Officers were very friendly and our talk was in a friendly enviroment.

    Questions d'entretien d'embauche

    • Technical questions, some hr questions, and standard ones about why do you want to work here, and some questions about projects i have been part of.   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.