Form3 Senior Software Engineer Go interview questions

After an initial check-in call will a recruiter you get invited to take an exercise at home (writing a client for a fake API they provide). The good part is that there is no time limit for submitting the test, but the review process left me totally puzzled. After providing extensive unit and behavior test suite (especially on sad paths) with full test coverage, a perfectly working client, documentation and even a working example on how to use it all i got was a rejection with three reasons that didn’t make real sense if you take a look at the code. I spent 3 full days at reading over and over again those rejection reasons and well, they still just don’t make any sense since what they said it isn’t what’s inside the code. This is a very demanding test if you want to make it very well, and therefore it is unacceptable to get rejection on something that just doesn’t exists or is just pure personal and biased preference. I think that they use the test to see if you code like they want/expect, rather than understanding if you really can code or not and know what you are doing. At this point all I can say is that I should feel lucky I got rejected. Watch out candidates, huge risk of wasting your of time.

Initial call with internal recruiter explained the company and role, the recruiter sent a really helpful candidate pack through including details about the company, role, benefits, tech stack, interview process and FAQs. Next stage was to complete a coding task, for which you're given as much time as you need. Once submitted via GitHub, the team review your code and aim to get back to you within a week to either invite you to an interview or to decline, providing feedback on your task. The interview is made up of 3 parts, 30 minutes each with 3 different engineers, and a 4th engineer observing the whole thing. In the first part the engineer gives you an intro to Form3 and payments in general, then asks questions about your code, giving you chance to talk through what you did, why you used certain approaches, etc. In the second part the engineer asks technical questions, including networking, HTTP and security. The third part involves a simulated debugging exercise where you need to ask questions and explain how you would debug an incident. There are also questions about CI/CD, and an opportunity for you to ask questions about the role. Overall I was really impressed with the interview process, in particular the professionalism and friendliness of everyone involved. This gave me a great impression of Form3 and was a big factor in my decision to accept.