Lmao do people get that? The only thing I’ve ever gotten after final round lately have been ghosted or a useless generic rejection email. Even when a recruiter is involved, they don’t seem to get that sort of information.
I usually don’t get direct feedback. But if you’re even slightly socially conscious you can usually pick up clues by not having great answers to interview questions. Seeing their face or hearing their voice express some involuntary emotion that says, “ah he doesn’t know this.”
I usually pick up the hints, read between the lines, and study up on those things, whatever they may be.
As a hiring manager, it's risky to give detailed information because it could be used for a lawsuit, and there's no direct benefit to the company. My company still does give feedback because it's the right thing to do, but there is a reason why most companies shy away.
i ask everytime I get rejected, you do sometimes get some info. But i think its almost always useless because the next interview you do will be graded some other random arbitrary standard. sometimes it is helpful though, or if there is a trend.
I always ask for it directly. I usually get some clues, but nothing deep. I've never been ghosted after an in person interview (except by Tawkify matchmakers, but that's another story lol)
Well its a mix of things. I struggle with "live coding", y'know fight,flight, or freeze? I freeze up. So on that front I think I need to do two things:
1. Slow down and ask for a few minutes to collect myself. "I'm not in this context, do you mind if I have a minute to organize my thoughts". And then do a little "whiteboard" in my notebook or something. Some people might say to verbalize your thinking process and I agree but there shouldn't be anything wrong with taking a few minutes. (I mean, this doesn't even necessarily test for how I'd do on the job because I'm at least competent at coding)
2. Practice more situations. Any time I struggle with a problem after the interview I make sure I understand that tech. Right now I'm studying up on class components and websockets. (Two technologies I either don't really see anymore: we use functional components on my latest projects or stuff you set and forget)
I think #2 is part of what people mean when they say that interviewing prepares you for the next one.
- Some places that I get far with I've literally reached out afterward and asked for pointers. One piece of feedback I've gotten is, "We didn't get a good sense of what drives you." which, that's fair. I think of software engineering as more of a technician => "I have the skills to solve your problems" and not so much, "My passion is building the front-end for X,Y,Z business" I mean, I'd obviously like to find work with meaning but I'm not driven by that meaning. I don't think we'd ask our plumber to show their passion for the work (Not that they can't have that) but instead we're more concerned with, "Are you competent?" - That's something I need to work on for sure.
- Lastly, I've learned that an interview is for both parties. The person interviewing me is also representative of the company. The last two interviews I had a bad feeling about the fit post interview and I think I should have reached out and rescinded my interest because our values didn't align.
Most of the time though, I check all the boxes and don't even make it to interview stage so its hard to really glean anything useful most of the time. Could it be a bad market? Is it because the only box I don't check is having a CS degree? (I have a bachelors but not in CS) Is it my experience is too varied? Who knows. Best I can do is to keep at it.