3 ms·
Got feedback, "you didn't really know anything about Ruby on Rails". I was a Rails developer at the time, but no questions were asked about Rails during the int
by nobleach 7y ago
Got feedback, "you didn't really know anything about Ruby on Rails". I was a Rails developer at the time, but no questions were asked about Rails during the interview (asked me nothing but JavaScript). I mentioned that to the recruiter, but when a recruiter is calling you to tell you that you didn't get the job, that's not the time to lodge a protest. Since this was an internal recruiter for the company, I thanked him kindly for actually calling me instead of sending an email. That was a solid move in my opinion.
- mbreedlove 7y agoI applied and interviewed for an Angular position a few years ago. I was interviewed by a consultant doing work for the company while they built up their engineering team. He absolutely grilled me about .NET intricacies, including some of my favorites, "Where is the .NET GAC stored on the filesystem?" and "Why is n-tier better than MVC?". Not surprising, they declined to move forward citing my inexperience working with .NET enterprise architecture. I could have told you them that from beginning and saved everyone a few hours.
- flukus 7y ago.net + angular seems to be popular around here and I've been on the other side of that, knowing .net but rejected for not knowing angular (but plenty of experience with other frameworks). The only time I've received real feedback was for a ruby job with a small project interview. Apparently I wasn't doing TDD because the tests and fixes were in the same commit. At least that kind of feedback let's you know you've dodged a bullet.