Yeah, that was the page that convinced me I should try to join. But,

"A note on the technical interview: As part of our interviewing process, you may be asked to pick an issue from the GitLab CE issue tracker, and code ‘live’ with the interviewer there to talk with and collaborate with. We do this because we believe that it is the best way for you to see what the work is really like, and for our interviewer to see how you think, code, and collaborate." Actually, it's the opposite of how to find out how I think and code.

Do you have a profile on GitLab.com, GitHub or Bitbucket?

No.

What (open source) project that you built or contributed to are you particularly proud of / passionate about?

None.

Were you referred by a current GitLab team member?

No.

I once discovered that one of the most effective developers in the world would've had similar answers.

Is there an extension to hide downvotes, ungray all comments, and hide karma count? If not, I'm going to write one.

I know it's just an errant downvote, and people can feel however they want. But the information is no longer useful.

Given those answers, you really seem to clash with gitlab's culture, regardless of how good a programmer you may be.

We also hire people that never contributed to open source but that are great people and are open to our values https://about.gitlab.com/handbook/#values

Yes, thanks for correcting me!

Will you give me a real-world task and see how well I do?

Assessing a candidate is as simple (and as hard) as that. Watching someone while they code isn't useful. https://data.triplebyte.com/take-home-interviews-d7f7ea13067...

Just give me something real to work on.

We give you something real to work on but we'll be in a Google Hangout to discuss it with you: "As part of our interviewing process, you may be asked to pick an issue from the GitLab CE issue tracker, and code ‘live’ with the interviewer there to talk with and collaborate with."