Recruiter reached out. Got me to interview for SWE for shopping content project. First, did a phone screen with one of the engineers. It's a medium level LC question. Got it done almost perfectly. For the onsite, there were 4 sessions, 2 system design and 2 coding. and finally a chat with their hiring manager. * First system design Some data modelling relevant to the shopping content, and the second part is designing a processing pipeline * Second system design Sort of a deeper dive of the processing pipeline in the first session. It's clear they have a direction they want to go, and just wait for you to say the right word, which IMO defeats the purpose of system design interviews. Case in point: I described the load shedding strategy to use, but was completely ignored by the interviewer, and in the end, he explained the strategy is "heuristics" which is exactly what I explained, and only I didn't mention heuristics by name. * First coding Another LC-medium type (I'd say on the easier side of medium). Finished it with time to go, and chatted with the interviewer on how I'd change the algorithm if the requirements were changed. It was a pleasant chat. * Second coding LC-medium (slightly hard) problem, but it boiled down to implementing a pretty well-known data structure. Finished it perfectly with time to spare. Another pretty pleasant session. * Chat with Eng Manager Nussin' to say All in all, I enjoyed the sessions with the engineers, even though there were some hiccups in system design sessions, I still enjoyed the process. I'm usually not great at LeetCode questions, but I'm pleasantly surprised by my coding session performance. My advice to Pinterest: respect candidates' time.

It was fast and had 3 interviews after screening one. Basic programming, but data wrangling was harder as the person interviewing had more experience than the previous ones and it showed