The interview process consists of five different phases (HR intv, Technical intv, Behavioral intv, Bar Raiser intv and Offering). The interview usually goes past the allotted time, so I suggest allocating at least double of the time set. The HR interview basically consists of an introductory session (you describing what's on your CV, which is basically done on every session), the questioning session and the ending. In the questioning session the HR will ask you common HR questions (e.g. The most challenging thing that you did in your last job, why and what did you do to overcome that), The Technical part alone can go for more than 2 hours. The questions asked beyond the introductory session are Logic/Algorithms, Basic SQL, Computer Science Fundamentals and lastly Soft Skills. For logic specifically I conveyed what I want to do first, before actually coding. Perhaps if there is anything that needs to be asked about edge cases and whatnot you should ask. The interviewer here is the lead backend developer. Within the behavioral section, beyond the introductory session, you are asked some cases testing how a Senior should behave in different situations, especially in a company where requirements can change on the fly. To be perfectly honest in this interview I sense there to be no right and wrong, as long as you can reason your answers correctly you should be able to pass. A book that can help is Pragmatic Engineer's The Software Engineer's Guidebook. Basically you need to think of yourself as somebody who uses your technical skills to solve business problems, not just somebody that codes and implements features. This section lasts for a bit past an hour and the Engineering Manager and a technical Associate VP will be interviewing you as a panel. The last interview is with the Head of Audit and Risk Management. Basically what I did at the last interview is to answer risk mitigation strategies, be it simple things such as leaving your ID on your desk unattended which may cause somebody to be able to access certain sections of the office even though they are unauthorized to do so, and also basic things that you can do to help make your deployed applications more secure. You need to explain it in a way that a non-technical associate VP can understand. This section lasts a bit past an hour. Do keep in mind that even if you pass the interview you will need to pass the probation as well, and the probation is significantly harder as you will have to onboard yourself as there is no formal technical onboarding process. If you get teammates that are constantly busy (which they usually are) you might unfortunately be out of luck.