I'm a vim user myself, but most of the team doesn't use it on a daily basis (but they all passed through the same interview process). The choice of using tmux/vim/AWS is based on several factors. The remote pairing environment is terribly simple to setup like this in virtually any programming language (we have a polyglot ecosystem here). Familiarity with the Linux command line is imperative for us, so that's another strong reason. Also, I want to hire real developers, people who can think software, not superusers of an specific IDE. Taking the candidate out of the comfort zone helps to reveal that.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
I'm a vim user myself, but most of the team doesn't use it on a daily basis (but they all passed through the same interview process). The choice of using tmux/vim/AWS is based on several factors. The remote pairing environment is terribly simple to setup like this in virtually any programming language (we have a polyglot ecosystem here). Familiarity with the Linux command line is imperative for us, so that's another strong reason. Also, I want to hire real developers, people who can think software, not superusers of an specific IDE. Taking the candidate out of the comfort zone helps to reveal that.