1. Email with tech questions, essay style.
2. Hangout interview with hiring manager.
3. Work on an issue in their codebase.
4. Give references to HR and phone call with VP.

In theory, GitLab uses a manual that dictates their interview process, timing, and handoffs. In practice, it was much slower, required emails to restart the process, and tied me up in a lengthy code process. They gave me positive feedback, only to eventually turn me down with the reasoning that they needed someone who wasn't a junior, which is something they should know from the start. It's hard not to ascribe negative intentions to that.

Perhaps they were trying to give me a chance, but surely they could have realized before six weeks that the level they were wanting was not a junior.

Describe the request/response cycle in relation to GitLab code.

Describe each part of the MVC cycle, with emphasis on concerns and services.