3 ms·
I just had this experience a week ago. I've worked with C# commercially but for the past 4 - 5 years I've been working with TypeScript mostly. There was a fun
by ThalesX 2y ago
I just had this experience a week ago. I've worked with C# commercially but for the past 4 - 5 years I've been working with TypeScript mostly.
There was a fun HR girl that sent me a message how she found my profile compelling and we should schedule an interview. I said why not. After 45 minutes of asking me all sorts of questions, she asks if I have experience with .NET 5.
I went on to tell her that for the past years I haven't worked with .NET (though this was obvious from my CV) but have worked across multiple stacks, heavy TypeScript which shares a type system and the same creator bla bla. Then she asks but have you worked with .NET 5? I told her I worked with .NET Core for personal projects, but when I was working in .NET there was no .NET 5. And she stopped it there. "I'm sorry but I don't want to waste your time, they are looking for someone with .NET 5 experience."
Honestly, it's so stupid. I have more than a decade of experience working with software, been founding engineer, CTO, not shabby at DS&A. I can't imagine what kind of company would let their talent pool be so limited by such a factor. Unless you're doing some heavy .NET voodoo, but this wasn't the case.
- knallfrosch 2y agoThe trick is to say that you do have .NET 5 experience. That 25 yo female recruiter hired for looks won't be able to stop you. You'll then get an invite to the technical interview where you can talk to people who actually know whether C+ exists.
- ryandrake 2y agoYea, it's gotten to the point where you just have to say "YES" to every obvious gatekeeping/filtering question. Whatever it takes to get to the next gate. Out of 10 written job requirements, only 1, maybe 2 are actual dealbreakers. If the job really requires specifically .NET 5, then the technical interviews will grill you on it, and you'd fail for the right reasons.