So here's the deal: I initially applied for the Software Quality Engineer II position, but got rejected. The interesting part is that they actually liked me enough to refer me for the iOS Engineer I role. So, I went through the whole Hirevue process, answering behavioral and technical questions. Then came the interviews: first, a 30-minute chat with HR, followed by an hour-long session with the Engineering Manager, a technical interview for an hour, and finally, a behavioral interview for another hour. Now, the technical interview part is where things get interesting because it really depends on the team. They might throw a LeetCode problem at you or ask you to code something related to the job you're applying for. The key here is to think out loud and explain your approach. Time was a bit tight for me, so I couldn't finish the problem entirely, but I made sure to walk them through my thinking and what I had planned. They do encourage helping you learn, but from what I've seen, they want people to have a good amount of knowledge for the role they are applying for. So, if you're applying for something, make sure you have some projects under your belt that are related to what you're applying for, this is response is more for college students since a lot of them think a degree is enough. Good luck!