The first interview is just somebody selling you the company. The second interview was technical and very tricky.

They have a GitLab handbook of how they conduct interviews that they encourage you to read, but if the interviewer has not read it, it won't do you any good. It is a really awkward interview at times. You will not get any feedback as to what is expected from you.

You will ask questions and will not get a response, then get an unrelated question. At some point, the interviewer plays an uncooperative client, but he won't really explain what the dynamic of the exercise is.

The other part of the interview is to make a merge request using GitLab. You should review the code, but he won't really tell you what the code is supposed to do or what he wants you to fix.

If this is a C# interview for the fuzz testing position, I will give you a clue: He wants you to implement dependency injection on a poorly implemented repository pattern. He will also ask you how to manage exceptions, but with very vague instructions.