Candidatei-me online. O processo levou 1 semana. Fiz uma entrevista na empresa GitLab.
Entrevista
Pretty much like described on their website. They sent out a technical assessment with blocks of code and questions around it, then asked to look at the merge requests and provide feedback. After looking at their code base and tests, I'm relieved not to get the role as it looks a hot mess. Also, the questions on the assessment felt like they were expecting someone to come up with the solutions to all their problems before even getting hired or having a full understanding of their solution.
When there are too many UI tests and too few unit tests, this is known as..
A: A Muffin Top
B: An Ice Cream Cone
C: An Hourglass
D: A Pyramid
E: Other: (write in)
Choose a bug from the list of open GitLab Issues and triage it by answering the questions below:
Can you reproduce the issue ?
How would you troubleshoot it ?
What do you think are the likely culprits in code that are responsible?
What debug information or instrumentation would help?
Choose an open Merge Request from the list of open GitLab Merge Requests and answer the questions below:
What feedback do you have on the code?
What do you look at to determine that this is a good change to make?
What information, if any, is missing from this MR?
According to you, what are the worst and best Rails testing practices? Given the GitLab codebase, can you come up with specific (as boring as possible) solutions that could improve this situation?