First round is a meeting with HR where they go over your CV to see if you'd be a good fit for their requirements.
The second round is one of these silly LeetCode/HackerRank technical tests where half the interview is trying to figure out what on earth the problem is even asking. The answer involves string manipulation, use of hashmaps and some basic maths.
However, this round is not a good judge of a software engineer. It's a pointless task with no real application in the real world. Why on earth would financial portfolio data be stored in an array of space separated strings? Eg "GOOG 10". Database ORMs, object orientation and dictionaries exist for a reason. I spent a good portion of the interview explaining how this data really should have been stored and didn't finish the solution on time because of this.
Talking to the interviewer was like speaking to a brick wall too. No friendly discussion, barely a greeting when I joined the call and frequently racing to find something to correct you on. If the working environment is anything like this then I dodged a bullet.
Find discrepancies between a day zero and day one portfolio based on a transactions log.
The following metrics were computed from 7 interview experiences for the Addepar Software Engineer role in United Kingdom.
Addepar's interview process for their Software Engineer roles in the United Kingdom is extremely selective, failing the vast majority of engineers.
Candidates reported having very negative feelings for Addepar's Software Engineer interview process in United Kingdom.