I applied to a few PayPal positions before Christmas, and two of my applications got recruiter calls.
One of them was for a Fraud DS role and moved to interviews fast. The interviewer was someone from the same team based in India, and the interview was at 10:30pm Eastern. They asked about fraud, statistics, SQL, and Python.
The second round was with the hiring manager, also based in India, at around 10:45pm Eastern. We talked about what the job actually involves, then went into a fraud case.
The thing is, I don't have any fraud-related experience, and I hadn't interviewed in a long time, so I performed pretty badly. On top of that, communication wasn't very smooth because of the language barrier. But somehow both rounds passed, and now I'm scheduling the final round with the director...
I'm wondering if they're just bringing in a weak candidate like me to pad the pool, or if there's some gap they're desperate to fill. Does anyone with experience have any pointers?
Here are some of the interview questions.
Round 1
Types of fraud, how ATO (account takeover) usually happens, first-party vs. third-party fraud, how to measure a fraud model's effectiveness, how you'd design a fraud strategy from scratch, and some questions about p-values.
The SQL was pretty simple — he'd describe a scenario and I'd talk through roughly how I'd write the code. One needed HAVING, and another seemed to need a window function.
For Python, they asked about the difference between list and tuple.
Round 2 was a case. They screen-shared a one-page document — roughly, the current model's fraud loss is high, only 40% of fraud is being caught, and a large chunk of the fraud is coming from emerging regions, plus a few other characteristics. The resources you can leverage are limited, and if precision goes up to 2% then complaints will increase — how would you approach the strategy?
Discussion
Loading comments…