Iterable Software Engineer interview questions

I was approached by a recruiter from the company, the entire interview process consisted of seven rounds. The first round was a technical phone screen. The virtual onsite consisted of 5 rounds (4 rounds on the 1st day and 1 round on the 2nd day - this was more so a q&a session with the hiring manager). Throughout the interview process, everyone I spoke to was very nice and courteous. The interview was very well organized and the recruiter I was working with was extremely helpful with prepping me before the virtual onsite!

Pretty grueling interview process that spanned the course of 5 days with multiple different people, including 3-hour-long sessions of live coding. Interview started off pretty typical: Recruiter phone screen then an interview with a manager. Then ended with some live coding, and finally a presentation to a panel on some project/code you've worked on. Frankly the 3 hours of live coding felt gratuitous and by the end of it, I was completely drained and barely even wanted the job anymore. The issue with the live coding is that it left little to no time to ask the engineers you're interviewing with any questions about the role, because you'll need near the full hour to complete the programs. In my opinion, I got the point across that I was competent with the first coding session and when I entered the second and third, I really didn't care if I got the job or not because it started to feel more like billable work, rather than a test of my skillset. The presentation to the panel came immediately after the third live coding session. It was less difficult, but coming off of the previous session, I was tired and just wanted the whole process to be over. If I had advice to the company, either ditch the live coding sessions and give candidates a 1-hour take-home assignment and then have a conversation about that in the interviews, which will also give the opportunity for the candidate to get to know the engineers better. Or if you really want to keep the live coding (which I feel like they shouldn't because live coding is antiquated and doesn't actually depict how someone is going to be in a real-world scenario), limit it to 1 hour. 3 sessions is extremely obnoxious. Overall, I passed the interview, but in the future, if a company ever told me that this was their interview process, I would immediately withdrawal my application and save myself the trouble