Perguntas de entrevista da empresa Moov Financial

1. Initial Phone Screen 2. Background interview with two engineering managers. Talk mostly about projects you work on, the impact you have, certain decisions you were responsible for, etc. 3. Code-review practicum - Basic N-Tier CRUD app written in Go. A very basic understanding of Go is all that is needed. Being able to run a basic Go web-api on your local machine probably scores some points. - Given roughly 10 test cases that are failing. Asked to essentially walk through them 1 by 1, fixing the bugs. The bugs are mainly focused around basic REST project architecture, some very basic SQL. I felt the interview went pretty well. I was trying to make sure that I went slow and explained my thought process. This may have hurt me, as I was given feedback that it seemed like I was struggling with the reference architecture. I wasn't at all. It's the type of project I've worked in countless times throughout my career. It would be a good idea to brush up on general REST concepts. I wasn't expected to have status codes memorized, however it appeared not knowing them may have hurt me. I was also put off by the fact that I was given feedback on not having a strong understanding of "REST" standards... when REST isn't a standard. It has general best practices, and everyone takes their own liberties and brings their own opinions in terms of administering them. Regardless, I felt like I had good conversation around the concepts, but perhaps wasn't given points for not taking a hard stance one way or another... not sure. Overall, I really like the interview format. Admittedly, I'm just a little bummed because despite having no professional experience in Go, I felt like outside of one gotcha, I really didn't struggle at all. Long story short, I like Moov and I like the company. It's just a bummer when you feel like something is a good fit, but ultimately don't receive an offer. Such is life.