Taro Logo

QA/Development Engineer Interview Experience - Redwood City, California

October 1, 2012
Neutral ExperienceNo Offer

Process

Met Informatica at the EECS career fair and was contacted shortly after by the recruiter for campus interview. Interviewer was not interested much in my resume. Immediately they started firing technical questions at me. Some on data structures, some on concurrency, and locks. Made it through the campus interview and was contacted after about a week and a half for an on-site interview in Redwood City.

Recruiter replied very slowly about the details of the on-site interview. Eventually was contacted by someone else to schedule it. The on-site interview was even more technical. The questions are not too bad, but there are just a lot. By the end of the four 1-hr interviews, I got a headache. Treated me to lunch. It seemed like a very nice company, nice people. But definitely one of the most difficult interviews I have had.

Questions

Some questions:

Implement a reader-writer lock.

Explain the way Java's memory allocation works (stack, heap, etc).

Swap two ints without using a tmp.

Sort a linked list.

Reverse a linked list.

Analyze the complexity of a program.

How to make a program more efficient.

Length of longest palindrome in a string.

Was this helpful?

Interview Statistics

The following metrics were computed from 1 interview experience for the Informatica QA/Development Engineer role in Redwood City, California.

Success Rate

0%
Pass Rate

Informatica's interview process for their QA/Development Engineer roles in Redwood City, California is extremely selective, failing the vast majority of engineers.

Experience Rating

Positive0%
Neutral100%
Negative0%

Candidates reported having mixed feelings for Informatica's QA/Development Engineer interview process in Redwood City, California.

Informatica Work Experiences