PayPal interview notes, page 3 of 10

“I started with the obvious stuff, velocity checks and rule-based thresholds, but then kind of froze when they pushed on how I'd actually set those thresholds.” The rest of the author's notes on Data Scientist interview at PayPal, Technical Phone Screen round, covers how they worked through the question, what the panel pushed back on, and what they would do differently.

“I froze a little because it's broad enough that you could go in a dozen directions.” The rest of the author's notes on Software Engineer interview at PayPal, Technical Phone Screen round, covers how they worked through the question, what the panel pushed back on, and what they would do differently.

“This felt manageable at first and then kept expanding.” The rest of the author's notes on Data Scientist interview at PayPal, Technical Phone Screen round, covers how they worked through the question, what the panel pushed back on, and what they would do differently.

“Pretty standard warm-up.” The rest of the author's notes on Data Scientist interview at PayPal, Technical Phone Screen round, covers how they worked through the question, what the panel pushed back on, and what they would do differently.

“Classic union-find or DFS problem.” The rest of the author's notes on Software Engineer interview at PayPal, Technical Phone Screen round, covers how they worked through the question, what the panel pushed back on, and what they would do differently.

“Felt fine building the frequency dict with a for-loop, that part came naturally.” The rest of the author's notes on Data Scientist interview at PayPal, Technical Phone Screen round, covers how they worked through the question, what the panel pushed back on, and what they would do differently.

“Started fine with the naive loop version but then they asked me to compress it further and I kind of stalled on the one-liner.” The rest of the author's notes on Data Scientist interview at PayPal, Technical Phone Screen round, covers how they worked through the question, what the panel pushed back on, and what they would do differently.

“I started with Valgrind/Memcheck since that's the one I've actually used in production and felt confident talking through.” The rest of the author's notes on Software Engineer interview at PayPal, Technical Phone Screen round, covers how they worked through the question, what the panel pushed back on, and what they would do differently.

“I covered mutability fine and even threw in a quick code snippet showing you can't reassign a tuple element.” The rest of the author's notes on Data Scientist interview at PayPal, Technical Phone Screen round, covers how they worked through the question, what the panel pushed back on, and what they would do differently.

“Went fine, covered running totals, ranking rows within partitions, lag/lead for time-series comparisons.” The rest of the author's notes on Data Scientist interview at PayPal, Technical Phone Screen round, covers how they worked through the question, what the panel pushed back on, and what they would do differently.