The benefits are okay, probably the only real positive when comparing a big company like this to a sweet little startup where you'll be given fun and interesting challenges, and where people speak in human languages and not in acronyms and corp-speak.
The salary is fair* (it was good but now it's stagnant; they suspended salary increases and bonuses).
It's changing a lot with all the off-shoring and the ever-worsening work conditions, which have triggered an exodus of the best and brightest, but still there are some genuinely decent co-workers (mixed in with some genuinely not-so-decent butt-kissers).
Managers, their sycophants, and those outside of the technology organizations look like they have a pretty good time. When reading other reviews, pay attention to job titles, and you'll see how most engineers skew towards the unhappy side of the scale, and those in other organizations seem to be far more content with PayPal employment. Also, if you're considering this place for your next employer, read the eBay reviews as well; they are the company that owns us, and their culture is fast encroaching on ours.
*You can look up the salaries, and those not in California will probably consider them very high. But the cost of living here is pretty brutal, so those of you scoping this place out for a possible move would be well advised to look into how expensive this area is.
Fire each other. Seriously, it's absolutely sad how much management we have, and how completely ineffectual a vast majority of our "leadership" actually is. Ask ANY current employee how often they see managers doing anything other than meeting with other managers, then coming back with further ways to over-complicate the work flows and frustrate the individual contributors.
Upgrade the playgrounds, stages, feature pools, and network.
Upgrade the tools we use, making functionality, speed, and ease of use primary considerations, not metric gathering as is the current rule.
Simplify the release process.
Stop changing the release process every release.
Size projects better. We push too much with too many bugs, not because we code or QA badly, but because there's not enough time for people to do a craftsman-like job. We have a "rush everything" strategy, which results in too many live site bugs, too many emergency bug fixes, and too many emergency feature requests. Changing the live site shouldn't be such a casual activity.
Take a look at the scheduling that's being done, and re-done, then modified, then re-modified, and ask yourself why we plan like this. We spend inordinate amounts of time doing crazy stuff, which takes away from our primary duties, which suffer like crazy because we play games like this.
Consider not off-shoring so many of our jobs.
Get over the obsession with automation. I know you fantasize about having scripts that don't draw salaries instead of engineers who do. But look at the reality of what you're pouring into this ineffectual tactic. Automation is a nice supplemental strategy, on a limited scale.
Extremely slow. Even after an interview goes very well and the manager gives positive feedback, they take months to move to the next step. Suddenly, process changes, and they want to do another round of interviews. Don't waste your time here.
We need some Lead QA to lead the team in Singapore and San Jose.
We need some Lead QA to lead the team in Singapore and San Jose.
The process included one written test, followed by two technical rounds and one manager round, all conducted on the same day. However, the interview process is based on performance in the written test.
Extremely slow. Even after an interview goes very well and the manager gives positive feedback, they take months to move to the next step. Suddenly, process changes, and they want to do another round of interviews. Don't waste your time here.
We need some Lead QA to lead the team in Singapore and San Jose.
We need some Lead QA to lead the team in Singapore and San Jose.
The process included one written test, followed by two technical rounds and one manager round, all conducted on the same day. However, the interview process is based on performance in the written test.