Form3 Senior Software Engineer interview questions

- Introduction interview - Take home exercise - Interview with Three different engineers With the first one we talked about the exercise and my solution Second asked generic questions about tcp, ip, udp, rest Third came with an exercise that had to do with a live debugging infrastructure issue exercise (very edge case scenario that most people would not solve) Even if i received very positive feedback about my home exercise and my answers they rejected my application because my internet connection went off for 3 minutes and due to my communication skills without getting into detail what exactly was wrong with them. If my communication skills were so problematic it would have been very easy to spot this problem on the very first interview instead of putting me under this process just to totally waste my time.

I was contacted by a Talent Associate lady. She guided me through all phases of the interview process which I found very helpful and transparent. By looking at the job details I got really interested first of all, because of the e2e ownership philosophy and the latest tech ofc. First part of the interview process was a phone screening session about half an hour long in which I was given a high level introduction of what the company is about and what they are looking for. Also the entire interview process was explained here which consists of 3 parts, the initial screening, take home test and if successful the final interview after which you get an offer or not. In the case the solution is not successful, code review was promised to be sent which I found fair. I thought it would be also neat to get it to the pull request in this case but it's not part of the deal. Take home test is to build a client library in Go for which details are in the Readme of a Github repo publicly available. As this was the first time for me to ever write in Go I took the strategy of checking how I could do some basic things first, like (de)serialize json and organize my code in compositional style that I like. This was to try to get some understanding upfront and prevent beginner mess sneak into the solution. After I submitted the solution, it took five days to get an answer which is exactly what they said it could take. We agreed to a time-slot for the final interview that had another 3 parts. First part was high level overview of the business model and infrastructure plus code review - I found all points plausible. Second part was related to the background check and had several technical questions - was very casual. Third part was about an on-call scenario with no right or wrong answers just figuring things out. Afterwards was the time when you can ask questions if you have them. I had some as I was interested how they think and work. During the same day I received an offer which I chose to accept. The contract was promised to be prepared for the review within a few days but it came the very next morning. Overall, I think it is useful to go through material Talent Associate gives you, see if the same things are of interest to you and be ready for any kind of response.