App
All the jobs I failed to get
61–70 of 180 posts
Re: All the jobs I failed to get
#62I remember getting rejected by Google because I completely blanked on a binary search question. All my other rounds were great, but you can’t miss the search question at the search company.
Re: All the jobs I failed to get
#63GoDaddy rejected me a year after I applied and only realized it when a recruiter was trying to input me into their system. I took great pride in informing her that a) I made more than their proposed offer and b) I’d never work for a company who couldn’t operate with basic human decency in their recruiting process. Because of that experience, I make it a point that every single candidate deserves a yes or no response…
> GoDaddy rejected me a year after I applied and only realized it when a recruiter was trying to input me into their system.
I don't understand this bit. Did the recruiter input your info in their system and then the system send you a rejection email?
Re: All the jobs I failed to get
#64GoDaddy rejected me a year after I applied and only realized it when a recruiter was trying to input me into their system. I took great pride in informing her that a) I made more than their proposed offer and b) I’d never work for a company who couldn’t operate with basic human decency in their recruiting process. Because of that experience, I make it a point that every single candidate deserves a yes or no response…
> I took great pride in informing her that a) I made more than their proposed offer and b) I’d never work for a company who couldn’t operate with basic human decency in their recruiting process. I used to work in tech recruiting. I guarantee you 100%, no one cares. As a candidate your only option is to move on or write a bad glassdoor if you are so inclined and move on.
I'm on the interviewer's side of the table and we absolutely do care.
Re: All the jobs I failed to get
#65The last time I got rejected was after the final interview. The recruiter scheduled a call to talk with me without letting me know they had an offer. I could only have imagined they'd be making an offer. He thanked me for the time and told me why they decided to reject me, and that they'd likely reconsider me in six months. I'd rather receive an email telling upfront I was rejected instead (still would be happy to sc…
I’ve gotten three of these calls in the last 6 months. I learned after the first one not to get too excited and grown to appreciate actually getting feedback.
I can’t stand the interviews where you invest a significant amount of time and get zero feedback. I realize they often don’t want to share everything but give me something so I have some direction for improvement.
Re: All the jobs I failed to get
#66My final interview with AWS for a Sr PdM role went so poorly that they told me I had to wait 12 months to apply again. I feel like that’s some sort of accomplishment on its own.
Re: All the jobs I failed to get
#67GoDaddy rejected me a year after I applied and only realized it when a recruiter was trying to input me into their system. I took great pride in informing her that a) I made more than their proposed offer and b) I’d never work for a company who couldn’t operate with basic human decency in their recruiting process. Because of that experience, I make it a point that every single candidate deserves a yes or no response…
> I took great pride in informing her that a) I made more than their proposed offer and b) I’d never work for a company who couldn’t operate with basic human decency in their recruiting process. I used to work in tech recruiting. I guarantee you 100%, no one cares. As a candidate your only option is to move on or write a bad glassdoor if you are so inclined and move on.
Candidates talk. If we hear that a company has a terrible recruiting process, we'll generally avoid it. This is especially true of qualified candidates who are heavily recruited. You'll send an email or a LinkedIn message to a candidate and get one of the suggested "No, thanks" replies or outright silence.
So if you don't care, you should.
Re: All the jobs I failed to get
#68GoDaddy rejected me a year after I applied and only realized it when a recruiter was trying to input me into their system. I took great pride in informing her that a) I made more than their proposed offer and b) I’d never work for a company who couldn’t operate with basic human decency in their recruiting process. Because of that experience, I make it a point that every single candidate deserves a yes or no response…
> I took great pride in informing her that a) I made more than their proposed offer and b) I’d never work for a company who couldn’t operate with basic human decency in their recruiting process. I used to work in tech recruiting. I guarantee you 100%, no one cares. As a candidate your only option is to move on or write a bad glassdoor if you are so inclined and move on.
> I used to work in tech recruiting. I guarantee you 100%, no one cares.
Yes, everyone noticed.
Re: All the jobs I failed to get
#69I had a first interview for Product Manager for Google about a week ago and got the reject couple of days back. The recruiter said it was close. I played back the interview in my head and realized I could have been more methodical in my answers. Finally, just decided to let go. In the end its just a footnote.
> The recruiter said it was close. Is this something a recruiter might ever not say?
For an in-house recruiter, yes. They generally say that because they want you to interview again in the future. I don’t think they would waste their time if it wasn’t close.
Head hunters on the other hand will generally say anything to get you to keep interviewing.
Re: All the jobs I failed to get
#70Earlier quoted context omitted.
But is that a skill that is required for lots of positions?
Recursion is a fundemntal part of programming, beyond the self-taught junior yes I would absolutely expect every programmer to be able to do it. You learn it in highschool level programming classes & first semester intro to CS college courses. Even if they won't specifically need to use recursion in their next job it marks them as someone not serious or about programming.
I'd argue that not being able to program in C marks someone as not serious about programming, but that's mostly because I know and like C.