GitLab Support Engineer interview questions

Recruiter found me via LinkedIn, we had a screening call and then was technical interview with the Sr. Support Engg. They just wanted to know the way you think towards resolution. The guy was a bit rude and loud which can make people nervous and didnt give me time to read the error/output by myself. He kept talking and not relaxed which was not great. Of course I told them they were good when they asked for feedback on video call but yea anyway didn't get the offer, giving people an heads-up . Here you go, there was 3 technical and 3 customer based scenario questions. Tech questions were: Apache is responding on port 80 and GitLab is not. Make a plan to fix this. GitLab gives a 500 when logging in. Fix it. Given this SSH fingerprint, find me the user's email address. Customer based: For each scenario, you may attempt to collect more information from the 'customer' if you believe you need it to reach a solution. However, more information will not be available in all cases. Assume that the customer is running GitLab on-premises and is a system administrator - they have access to the server command line (logs, process status, configuration, etc). Consider how you're representing the company and what kind of experience the customer is having. ## Scenario 1 **Customer:** I'm getting the following error when trying to load a page: `500 Whoops, something went wrong on our end`. ## Scenario 2 **Hint:** High Availability support is only available to EE Premium customers. **Customer:** Our organization has an EE Starter subscription. We're having trouble configuring GitLab for high availability. We really would like to have this resolved right away. ## Scenario 3: **Customer**: I want this issue escalated to a more senior developer, as right now I am very dissatisfied with the support received, especially your last e-mail – I feel that you are not addressing the considerable, detailed evidence I provided.