Initial call and then "pair" programming. Put pair in quotes cause really it's not paired programming and instead the engineer from Monzo just sits there giving little bits of input every now and then. Personally absolutely hate doing technical programming interviews like this had too many bad experiences that it's honestly put me off doing them. Don't understand why in our industry we have to have such complicated interview processes compared to others. Would of much preferred to do a take home test if given the opportunity. Given only 45 minutes to code up an in memory ledger so obviously put on the spot to solve a problem. The interviewer fed back that the code was complicated and had lots of repetition but I wasn't really trying to solve a beautiful code challenge. Reviewing my code now it only has two bits of repetition which I repeatably said this wasn't ideal and would like to redo it but given the limited amount of time I had to focus on trying to make it feature complete. As I progressed through the problem I realised and communicated that my code isn't ideal but I can't exactly just go back and rewrite everything to make it better which the interviewer even said not to bother. So to complain about my complicated and repeated code I feel is a bit cheeky/rude I'd like to ask Monzo if they put there engineers under such time pressures to solve technical interviews? If not then why do it for interviews? Why is this an accepted way of interviewing for our industry?
