5 ms·
My favorite part of their story is how they changed the interview process to not be terrible and built a dashboard to quantify it: https://about.gitlab.com/blog
by alexfromapex 4y ago
My favorite part of their story is how they changed the interview process to not be terrible and built a dashboard to quantify it: https://about.gitlab.com/blog/2020/03/19/the-trouble-with-technical-interviews/ https://about.gitlab.com/blog/2020/03/19/the-trouble-with-te...
- VoidWhisperer 4y agoUnfortunately the dashboard seems to be very broken now :(
- inyorgroove 4y agoI've interviewed with them twice (2016 & 2022), didn't receive any feed back other than a generic decline e-mail. And this was despite promises to the contrary from recruiters, I was ghosted when I asked for it too. I even recall teaching the interviewer some javascript quirk during a coding challenge the first time and solved whatever silly brain teaser question that was asked, with test cases too! Yet zero feedback as to why I was not going to move past that first technical challenge. Disappointing really. EDIT: More on topic, I did really enjoy the MR based technical interview way more than the common coding challenge.
- Traubenfuchs 4y agoSo your personal experience with the processes of $BIG_CORP don't live up to the fairy tails $BIG_CORP spins in their blogs, talks and other public relations material? I am shocked, shocked!
- inyorgroove 4y agoThey try to paint this feedback as a big difference about themselves is the only reason I brought it up.
- bamboozled 4y agoInterviewed with them once, it was a while back, more than 2 year, but it was the worst interview I can remember. They asked me to clone a rather large repo as part of the interview, I cloned it but it was slow, the dude just blamed it all on my internet and my geographic location. Like kept going on about it through the awkward slow clone. I think I wrapped it up early. I ws cloning other repos of similar size and much faster speeds that day.