I didn't particularly like the interview process. It started off with a meet and greet with a recruiter followed by an intro call with a high level member of the team. He was a pretty relaxed guy and I enjoyed talking to him. Next was the system design round. This round was pretty fun too. We went through a practical problem with minimized complexity and they asked to design the data model. The interesting thing I noticed is a very high focus on writing raw sql queries. I don't know many people in industry that know sql that intimately, but it seems like a strange thing to test since querying can just be done using google on the fly. The next interview was just an interview about my background and previous projects and once again I was asked a lot about my database experience. I was asked if I was asked specifically about the complex queries I had written, again a strange thing because I usually just lookup the raw query based on what I want to do and forget about it. It's rare that I remember all the times I did a specific crossjoin or groupby on my old team. The coding round came next and the interviewer really wanted me to do it independently without talking to him lmao. I received a doc from the company with an api key and organization id and was told to make a series of http requests. The tech part of this interview wasn't too bad but the api definitely expects you to assume a lot about specific treasury management terms. I spent a lot of time fidgeting around with figuring out what the data even meant and what I was supposed to do. Half way through the interview the interviewer asked me if I knew what these terms meant, and he began to explain what exactly the requests were looking for. I was able to complete the task after that in the last 20 minutes. Last interview was with a customer service manager about team collaboration and that was pretty casual conversation.