Asking the interviewer to take time out of their lives to give you feedback is a proposition with iffy chances of success. I have to say that I lucked out when I interviewed with a fellow who turned out to be one of the top five Devops experts in NYC. The technical interview was a complete bust for me but he was touched and impressed that I had the guts to ask him what I needed to know in order to be successful as a Devops. He actually spent more time going over that than in actually interviewing me :) I carry the lessons he taught me that day with me every single day.

No, it doesn't hurt to ask. But if you know you busted it, you are best off asking right away rather than ask a few days later, when your interviewer's mind is focused on other viable candidates or on the next stage interviews. Look at this way way, the prospective candidates could be part of the firm's future. As far as the interviewer is concerned, your failed candidacy is part of a past that's dead and gone. And your asking a few days later the interviewer what went wrong is like you being a revenant in a bad zombie movie - You wait two weeks before you ask and it's a miracle if the interviewer remembers that you at one time existed :)

Frankly, you are better off asking at the interview what it takes to be successful at the position offered in the firm than what you did wrong. Knowing what it takes to be successful in that position will enable you to figure out on you own where you went short anyway. And asking where you went wrong rightly or wrongly creates the impression that lack confidence in your abilities. No matter how badly you screw up, never doubt yourself :) Fix what you need to fix, learn what you need to learn, do what you need to do but never doubt yourself.

And when you ask for feedback, be genuine, earnest and sincere about it. Ideally, you'll connect with the interviewer on a personal level and you'll get the feedback you need. In my case, my earnestness and sincerity connected with the Devops expert's passion for what he was doing - The feedback that I got from the Devops expert was priceless.

Asking the interviewer to take time out of their lives to give you feedback is a proposition with iffy chances of success. I have to say that I lucked out when I interviewed with a fellow who turned out to be one of the top five Devops experts in NYC. The technical interview was a complete bust for me but he was touched and impressed that I had the guts to ask him what I needed to know in order to be successful as a Devops. He actually spent more time going over that than in actually interviewing me :) I carry the lessons he taught me that day with me every single day.

No, it doesn't hurt to ask. But if you know you busted it, you are best off asking right away rather than ask a few days later, when your interviewer's mind is focused on other viable candidates or on the next stage interviews. Look at this way, the prospective candidates could be part of the firm's future. As far as the interviewer is concerned, your failed candidacy is part of a past that's dead and gone. And your asking a few days later the interviewer what went wrong is like you being a revenant in a bad zombie movie - You wait two weeks before you ask and it's a miracle if the interviewer remembers that you at one time existed :)

Frankly, you are better off asking at the interview what it takes to be successful at the position offered in the firm than what you did wrong. Knowing what it takes to be successful in that position will enable you to figure out on you own where you went short anyway. And asking where you went wrong rightly or wrongly creates the impression that lack confidence in your abilities. No matter how badly you screw up, never doubt yourself :) Fix what you need to fix, learn what you need to learn, do what you need to do but never doubt yourself.

And when you ask for feedback, be genuine, earnest and sincere about it. Ideally, you'll connect with the interviewer on a personal level and you'll get the feedback you need. In my case, my earnestness and sincerity connected with the Devops expert's passion for what he was doing - The feedback that I got from the Devops expert was priceless.

Asking the interviewer to take time out of their lives to give you feedback is a proposition with iffy chances of success. I have to say that I lucked out when I interviewed with a fellow who turned out to be one of the top five Devops experts in NYC. The technical interview was a complete bust for me but he was touched and impressed that I had the guts to ask him what I needed to know in order to be successful as a Devops. He actually spent more time going over that than in actually interviewing me :) I carry the lessons he taught me that day with me every single day.

No, it doesn't hurt to ask. But if you know you busted it, you are best off asking right away rather than ask a few days later, when your interviewer's mind is focused on other viable candidates or on the next stage interviews. Look at this way way, the prospective candidates could be part of the firm's future. As far as the interviewer is concerned, your failed candidacy is part of a past that's dead and gone. And your asking a few days later the interviewer what went wrong is like you being a revenant in a bad zombie movie - You wait two weeks before you ask and it's a miracle if the interviewer remembers that you at one time existed :)

Frankly, you are better off asking at the interview what it takes to be successful at the position offered in the firm than what you did wrong. Knowing what it takes to be successful in that position will enable you to figure out on you own where you went short anyway. And asking where you went wrong rightly or wrongly creates the impression that lack confidence in your abilities. No matter how badly you screw up, never doubt yourself :) Fix what you need to fix, learn what you need to learn, do what you need to do but never doubt yourself.

And when you ask for feedback, be genuine, earnest and sincere about it. Ideally, you'll connect with the interviewer on a personal level and you'll get the feedback you need - The feedback that I got from the Devops expert was priceless.

Asking the interviewer to take time out of their lives to give you feedback is a proposition with iffy chances of success. I have to say that I lucked out when I interviewed with a fellow who turned out to be one of the top five Devops experts in NYC. The technical interview was a complete bust for me but he was touched and impressed that I had the guts to ask him what I needed to know in order to be successful as a Devops. He actually spent more time going over that than in actually interviewing me :) I carry the lessons he taught me that day with me every single day.

No, it doesn't hurt to ask. But if you know you busted it, you are best off asking right away rather than ask a few days later, when your interviewer's mind is focused on other viable candidates or on the next stage interviews. Look at this way way, the prospective candidates could be part of the firm's future. As far as the interviewer is concerned, your failed candidacy is part of a past that's dead and gone. And your asking a few days later the interviewer what went wrong is like you being a revenant in a bad zombie movie - You wait two weeks before you ask and it's a miracle if the interviewer remembers that you at one time existed :)

Frankly, you are better off asking at the interview what it takes to be successful at the position offered in the firm than what you did wrong. Knowing what it takes to be successful in that position will enable you to figure out on you own where you went short anyway. And asking where you went wrong rightly or wrongly creates the impression that lack confidence in your abilities. No matter how badly you screw up, never doubt yourself :) Fix what you need to fix, learn what you need to learn, do what you need to do but never doubt yourself.

And when you ask for feedback, be genuine, earnest and sincere about it. Ideally, you'll connect with the interviewer on a personal level and you'll get the feedback you need. In my case, my earnestness and sincerity connected with the Devops expert's passion for what he was doing - The feedback that I got from the Devops expert was priceless.