Me postulé en línea. El proceso tomó 5 semanas. Acudí a una entrevista en Teradata (Miamisburg, OH) en mar 2013
Entrevista
First I talked with the hiring manager on the phone and answered questions--typical phone screen. I interviewed onsite, in Miamisburg, and I talked to two managers. During the first interview, I was asked questions about my resume and talked about the structure of the company and the department in which I would be working. This was approximately one hour. After this, I talked to the second manager and he asked me "What will you do for the company if I hire you?' Then he asked me "If you had to take a test on Java, and the results would determine if I hire you, would you take it? I said "Yes, I will take it right now." He said, "Confidence, that's what I like to see" Then he called the other manager and told him to get the Java test. The test questions were fairly straight forward. They went something like this:
"What does the extends keyword mean and what does implements keyword mean?" "What is and interface? When would a interface be used?" Then there was a simple SQL query question. Then "What is a singleton?" "Are memory leaks possible in Java?" "What is serialization?" These are the questions I remember--there were three or four other questions.
Preguntas de entrevista [1]
Pregunta 1
I didn't expect to have to take the Java test--but most of the questions were straight-forward.
There was one question about SOAP that I did not know how to answer.
It went well. Asked questions on Java and SpringBoot and micro services. And also few DSA questions . Difficulty level is medium and the interviewer was good and patient . There are three rounds of interviews followed by hr round
I applied and was first contacted by HR with who I did a very high level interview to understand my profile. Then I actually had an interview with my future manager and was asked more technical questions and also questions linked to my motivation.
Preguntas de entrevista [1]
Pregunta 1
Explain my technical knowledge in terms of databases.