DEV Community

Discussion on: Reasons I've Been Rejected For Software Engineering Roles

Collapse
 
barmatat profile image
Dmitry Spasibenko

@jgaskins , how did it happen that you could collect so many rejection reasons? I never even got one which could make any sense. In my case a "standard" rejection answer is a copy-pasted bullshit...

Collapse
 
jgaskins profile image
Jamie Gaskins • Edited

Most of my rejection letters have been, as well. But after 15 years and a whole lot of rejections, it’s possible to get a few relatively straight answers. If I’ve been rejected for 50 roles, for example (no idea what the real number is, but it could be higher), I’ve probably had to ask 48 of them for feedback (this part is important because almost no company volunteers that info), 35 of them have given it (the rest may have a no-feedback policy or they’ve decided not to respond), and only 10 have given a straight answer.

Collapse
 
barmatat profile image
Dmitry Spasibenko • Edited

Thanks. Last fall I've just come through of the process so I can share some numbers. For some short period of time I've been involved in about 50 interviews, which turned into ~20 on-sites. I did not pay much attention to pre-onsite process (screenings and different phone calls), cause the reasons of not going forward could be different and they are not interested to me so much. I was more interested in the on-sites rejection results, which in my case were 1/2 of the total number (~10). I always explicitly asked for the feedback. I got zero answers that could give me an understanding of the rejection. Nobody told me the reason. Zero. That is probably one of the weird things in the whole process.

Some comments have been hidden by the post's author - find out more