The pay and benefits are good, vacation time is untracked, and you're unlikely to ever get heat for anything because there's very little accountability.
All I can say is that PayPal suffers from an intransigent culture of non-cooperation among development groups.
Every piece of vital development, deployment, and project management infrastructure is (GitHub, Jira, Jenkins, Slack, Node.js, and on and on) completely siloed. The team running within that silo is far more interested in keeping everyone else out than they are in cooperating for the common good of development teams.
If you ever have a suggestion or a request for a change to one of these infrastructure items, whether it's a direct necessity for one of your project requirements or just something you thought of that would benefit the development experience of everyone using it, the team running that silo will put a truly impressive amount of time and energy into preventing it from happening. They generally go down this ladder of stonewalling tactics:
I don't even know how you begin to cure a development culture this sick. I've been a software engineer professionally for over a decade, and I've never seen a development culture so obsessed with not getting things done at any cost.
The most frustrating part is that I can't even identify where it comes from. I interact with a large number of different developers from different teams in different areas of the company, and the vast majority of them are very lively and helpful. But somehow, whenever we need to make the slightest change to anything that isn't 100% directly under our control, the new team we have to interact with is invariably completely unhelpful and intransigent. I have no idea whatsoever where the root of this problem is.
The interview has three rounds: one telephonic and two face-to-face. Of these, two rounds were technical, and one was managerial. In the technical rounds, coding, SQL, Selenium, Unix, and puzzles were asked.
In April 2011, I underwent five rounds of interviews in Pune. Four of these were technical, and one was managerial. The joining location was Chennai. One interview round focused solely on data structures and algorithms. Another covered design chall
They tried to follow Amazon's interview process and failed heavily. They have a screening round, then candidates are placed into a pool of three interviews comprising two coding rounds and a design round. Initially, in all three rounds, they state
The interview has three rounds: one telephonic and two face-to-face. Of these, two rounds were technical, and one was managerial. In the technical rounds, coding, SQL, Selenium, Unix, and puzzles were asked.
In April 2011, I underwent five rounds of interviews in Pune. Four of these were technical, and one was managerial. The joining location was Chennai. One interview round focused solely on data structures and algorithms. Another covered design chall
They tried to follow Amazon's interview process and failed heavily. They have a screening round, then candidates are placed into a pool of three interviews comprising two coding rounds and a design round. Initially, in all three rounds, they state