They have top-notch benefits and pay.
First, under no circumstances work here if you are in QA. You are not even a human being if you are in QA.
The whole company looks down on QA as some sort of second-class citizen that they want to get rid of as soon as possible, and the executives will say it to your face if they don't know you're in QA.
It's a bad place for development, too.
They have a bunch of proprietary technologies they use, and learning those is a gigantic waste of time.
First, you're learning to use badly written code, poorly designed user interfaces, and toolsets that can only be described as antediluvian.
It's madness.
The technologies you are learning to work with are used by no other company in the world because it's proprietary.
When I was there, they had their own version of cloud services for internal use. It was terrible, and you need to be using an industry-standard platform like AWS or Azure if you want career growth outside eBay.
It is a great place to be a manager.
Managers are given a whole different level of treatment than regular employees, and they generally don't get laid off in the rounds of layoffs that occur once or twice a year.
Every technology and tool that is proprietary and not absolutely specific to eBay's business, throw out and replace with industry-standard tools and code. If you don't think QA people are worth less than nothing and you think that any of them are valuable employees, you've consistently done the opposite to the point where eBay is notorious for being abusive to QA staff.
An online coding test was followed by an onsite interview. The hiring manager introduced himself via email and arranged the online coding test, which was conducted using a shared Google Doc. The interviewer seemed new to interviewing and appeared uns
I had a one-hour phone interview with a Senior Engineer. She asked me to speak about one of my projects and then moved on to a coding challenge. I walked her through how I would solve the question using O(n) time and O(n) space, but she wanted me t
The interview process involved an initial phone screen with a recruiter, followed by a 1:1 coding round with a software engineer, and then a panel interview. The interviewers were nice. I cleared the coding round and was selected for the final inter
An online coding test was followed by an onsite interview. The hiring manager introduced himself via email and arranged the online coding test, which was conducted using a shared Google Doc. The interviewer seemed new to interviewing and appeared uns
I had a one-hour phone interview with a Senior Engineer. She asked me to speak about one of my projects and then moved on to a coding challenge. I walked her through how I would solve the question using O(n) time and O(n) space, but she wanted me t
The interview process involved an initial phone screen with a recruiter, followed by a 1:1 coding round with a software engineer, and then a panel interview. The interviewers were nice. I cleared the coding round and was selected for the final inter