PayPal · Primly Community

PayPal frontend engineer interview: what rounds look like and what they actually care about

frontend_fran · 4 replies

Just did the PayPal frontend engineer interview loop for a mid-senior SWE role on their checkout experience team. Sharing because most threads about PayPal interviews focus on backend, and frontend had some specific quirks.

How it broke down: one recruiter screen, one 45-min technical phone screen, then a 4-round virtual onsite.

Phone screen: they had me code a vanilla JavaScript problem. No React. Implement a debounce function from scratch, then extend it to support a leading-edge option. Caught me off guard because I defaulted to thinking they'd use a framework. Know your JS fundamentals: closures, event loop, prototype chain. That's table stakes before you even get to framework questions.

Onsite round 1: coding. Again, mostly vanilla JS / DOM manipulation. Build a simple autocomplete component without a framework. They wanted to see how I structure component state manually, handle async (fetch + debounce), and manage accessibility basics (ARIA attributes on the dropdown). They asked follow-up: how would you test this? What breaks at scale with 1000 results?

Onsite round 2: system design / architecture. Design the front-end of a payment flow (not the API, just the client architecture). They wanted: state management approach, how to handle optimistic UI for payment confirmation, error states, retry logic on failed API calls. They specifically asked about how I'd handle PCI compliance concerns on the frontend (script isolation, iframe usage for card fields). That was a nice fintech-specific twist.

Onsite round 3: performance. They showed me a demo of a slow checkout page and asked me to debug/optimize. Core Web Vitals came up. LCP, CLS, FID. Know your performance metrics, know how to use Chrome DevTools.

Onsite round 4: behavioral. Standard STAR. They asked about a time you shipped something that caused a customer-facing bug and how you handled it. Fintech company, they care about reliability.

Offer was around $175k TC for mid-senior level, remote-eligible. The frontend bar felt genuinely high, especially the vanilla JS emphasis. If you've been heads-down in React and haven't thought about the underlying platform in a while, spend a week on that before applying.

4 replies

backend_bekah

the PCI compliance question on the frontend is such a good gotcha. most frontend folks don't think about it until they're actually building a payment form and realize you can't just put a card number in a plain input. iframe sandboxing and Stripe-style embedded fields exist for a reason.

mobile_mara

vanilla JS fundamentals test in 2026, love it. half the frontend candidates i've seen tank debounce because they've only ever called lodash.debounce. writing it from scratch once is genuinely clarifying.

frontend_fran

100%. i actually wrote one from scratch the week before the interview as practice and was glad i did. the tricky part is the leading-edge variant, easy to mess up the timer reset logic.

ux_uma

the accessibility question in the autocomplete is interesting, did they have a rubric or was it more 'mention it and they nod'? asking because design/front-end a11y is something i care about and want to know if it actually influences the score