I had a phone screen and then an on-site interview. The phone screen was pretty basic, with experience and behavioral related questions.
The on-site interview was a full day with three people interviewing. The first two were very technical and asked me questions about Informatica, SQL joins, optimization, and Perl scripts. It wasn't that hard, but not too easy either.
The last person was a manager and asked more about behavioral and coordination-related questions.
Write a script to remove duplicates from a file, identify outliers, replace them with a default value, and load the data into MySQL.
Which is the most cost-efficient transformation in Informatica, and what would you use instead to perform the same job more efficiently?
What is a "screw" in Teradata, how do you identify it, and how do you tune queries affected by it?
The following metrics were computed from 7 interview experiences for the PayPal Software Engineer III role in San Jose, California.
PayPal's interview process for their Software Engineer III roles in San Jose, California is incredibly easy as the vast majority of engineers get an offer after going through it.
Candidates reported having very good feelings for PayPal's Software Engineer III interview process in San Jose, California.