Ask us about:
- PayPal APIs
- PayPal OSS
- Mobile Payments Integrations
- Working at PayPal
- NVP/SOAP API SDKs
- PayPal REST SDKs
Message from the host 💬
Hello Hashnode folks! We're super excited to be here for this AMA session 😀
The host team is a broad representation of engineering, professional services and management at PayPal, so we can tackle pretty much any question you throw at us.
We're more than happy to discuss our engineering practices, open source work, mistakes from the past and lessons learned, corporate culture at PayPal, "day-in-the-life" questions, our diversity and inclusivity initiatives and more!
Only a couple of topics are off-limits (Legal said so...). We can't give any forward looking statements on company performance, and obviously we can't give away "secret sauce" information.
Looking forward to answering everyone's questions!
-The PayPal Team.
Hi PayPal Devs! It's amazing to see you all going live publicly for the first time (I guess) 😀
How does PayPal write test cases? I mean one single mistake and you can end up having huge loss! 👀
Without going into the details, if you can just explain briefly what goes under the hood, it will be really helpful.
Thank you PayPal folks for doing this AMA. I have three questions.
My first question is very fanboyish. I am a huge fan of Peter Theil and would love to know if any of you have had a chance to interact with him. I know he left the company long back, but does he ever visit the PayPal offices still?
What's your favorite thing about working at PayPal?
If I were to choose a payment solution today for my app, should I use PayPal or Braintree? How are the two products differents given that both are from the same team?
I always had a question when building a software. How do you bring reliability in projects which are very critical like money transaction or things like spacecrafts? There is no(or very less) room to make mistakes. So how do you at PayPal do fault tolerance and ensure that system is consistent no matter what happens.
Hello Paypal Devs . With no disrespect or malice meant at all, a large percentage of the development community would agree that Paypal's documentation just makes working with Paypal API close to impossible. It's such a pain. Stripe ( Forgive me mentioning this ) dominates the market for payment gateway integrations right now, not because they have better programmers, or better software, but the ease of integration of their API service, and how awesome and organized their documentation is .
Yallz are devs and you must have heard developers hate soo much on the paypal api and documentation.
Why has this not changed over the years ? Is there any particular reason why this has not been updated over the years ? or why this complain has not been taken into consideration ?
Thank you so much , hope to get a satisfying response.
Hey paypal devs.. I was a massive advocate of you guys up until stripe came along with a super easy payment api, since then I haven't really used anything else. Just want to know since they came on the scene what kind of board stroke improvements you have made to win back developers :) Sorry if its sensitive but will really help us busy devs read into more details later on and make the switch again :)
are you guys practicing much of the reactive principles when architecting system, are the feelings all positive? I have worked on a few microservice based systems and i don't think there really is a way to totally isolate any direct inter-service dependancy or am i missing a trick :)