I think you will hear a slightly different story from each one of us about how the typical working day looks :) I lead a small team. We all have staggered working hours since we all have different kinds of personal commitments. But we do have core hours at office that overlaps during when we have a stand-up to sync up on our day-to-day tasks as well as any dependencies that blocks us. As a manager I try to keep my team as much out of meetings as possible, so they can have some peace at their desk to work on exciting stuff. Our product and design teams sit right by us. SO we do have regular brainstorming sessions which covers a variety of things: from what goes into an immediate release to a long term vision for the team :))

We have a team pioneering GraphQL for one of our Paypal Checkout products. GraphQL is being used on node.js as an orchestrator (mid-tier service) for one of our mobile SDK clients. It is yet to be released, but so far consuming it has been great!! The developer on this project is not online today. But I will definitely bring to his attention, to answer your question in more detail. Cheers!!!

I agree with Kent. Even within Paypal, you may hear differing opinions from developers. Today node.js reigns the front tier. But I have heard murmurs, GO is being experimented for some midtier services.

I love how easy their integrations are. Although I'm not sure about their Risk detection and support system. Paypal has a pretty solid system in place for that.

Hey Shahid, Thanks for your interest in Paypal. I think the answer to the question below might answer your's as well. https://hashnode.com/ama/with-paypal-developers-cj793fn2q007usrwu2qcazocb#cj7cdgoyr0084nrwta2lpplb1

Hey Dylan, Thanks for your question. I used to be a part of the core node.js team as well in the past. To reiterate on what Lenny said We wanted to move away from building heavy in-house infrastructure around web app development and try out newer technologies. Earlier Java was used heavily in web-tier. Today, Node.js predominately dominates the web-tier. While we have small mid-tier orchestration services in node.js, Java is still used predominantly in the mid-tier. With node.js we have been able to extend expertise of our webdevs to full stack from just being on the client side. Node.js also enabled us to experiment to much more savvier front end and native technologies. NPM ecosystem was a big win to enable tearing down silos within teams and share work across :)) Here is a talk I gave at Intuit as part of Kraken team which focusses on our decision to move to node :) https://www.youtube.com/watch?v=YNtY5ObDJ8c So far it has been a big win...

Hello. Thanks for your question. You are right. We do invest considerable time of developers into testing. For front tier we do not have dedicated testing teams. Developers are expected to write and maintain tests for their code. For node.js, we use some awesome open sourced modules on npm like jest, tape, mocha, jasmine(and many many more). Teams have their own freedom to explore on this front. For functional testing in browser, we have our own opensourced framework nemo.js ( https://github.com/paypal/nemo ). I've seen some teams use Phantom.js. We do have full fledged Quality Assurance teams for testing Service infrastructures and full end-to-end testing of a product. We have specific environment setups for pre-build developer checks, Build check before release, and we have a Sandbox environment that mimics Production code to test without having to move money from our account and buying stuff online in the name of testing ;) :p

Hello :wave: Core Paypal's stack is potentially slightly different than the subsidiaries and acquired companies. At Paypal, for the web-tier we completely moved to node.js in the past 3-4 years. In the client, we have quite some freedom to explore frameworks of our choice (Angular, React, ... even the old timer Backbone in a few cases). For mobile native, the Paypal App uses swift on iOS and Java-Android. For one of our checkout SDKs (which is an effort I am leading currently), we have been exploring using react-native. In the mid-tier we mostly write Java services. A few orchestration services use node.js as well. There are even a few legacy systems using C++. For analytics, we use PIG for mining flat data alongside Hadoop and SQL scripts for db sourced data. For a big company, we take pride in moving fast to explore newer technologies. At the same time, as a big company, it takes time to deprecate older stacks due to the humongous effort involved :))