I've learned these things from own experience also and I totaly agree. Go to interviews so you can see what the market is looking for and what you need to learn, prepare for the interview at least as basic stuff, ask questions and make sure you are understood. I always try to do my best and to learn as many thing possible from the discussion. However, the feedback is very limited, and many times missing.
In the last period, 6month +, I get the feeling that the recruiters ar looking to make a list with as many "available" people as they can find and not to actualy hire. But I still enjoy going to interviews :)
It's been a little chaotic these past few months and I think they are pushed a lot to make the quota so to say. I did find out that in order to get that feedback that is totally limited or even non-existent, it's better to try and snatch the technical interviewer's Linkedin profile or email to keep in touch at the end of the talk.
Now, some of them might refuse, of course, but that's not a problem at all, every little success matters.
I then try to reach out to them directly instead of trying to go through the HR person, it's just an indirection layer that usually breaks the communication (love the work they do, but sometimes things get lost).
Without creating any pressure then (they probably have a lot on the plate too), I drop a message asking for some feedback on what can I do to improve.
Try it out and let me know if it worked for you. I'd love to hear more.
Keep the interview fun going ❤️ !
We're a place where coders share, stay up-to-date and grow their careers.
We strive for transparency and don't collect excess data.