Resume Critique
-
You can't get away from the arbitrary failure component. That is the critical piece here. Along with not knowing if the disaster avoidance was the employee or a manager.
-
@scottalanmiller said in Resume Critique:
If I bragged about that, I could brag about just anything.
If it's released to the job, you probably should.Its better than bragging get about nothing and listing a word.
-
@jimmy9008 said in Resume Critique:
@scottalanmiller said in Resume Critique:
@jimmy9008 said in Resume Critique:
Why is Hyper-V on the CV.
To show experience that is likely of value to the employer reading the CV.
That does not show experience. It's a word. Saying why you used HyperV. What is did. How it improved or solved something good... That shows the experience.
A word is experience on a CV. The CV is a list of experience. Hyper-V is the thing with which there is experience. It's the only piece of your description that related to experience. The rest talks about the business' needs or other people's decisions and their experience, but not the CV writers and is just filler.
-
@jimmy9008 said in Resume Critique:
@scottalanmiller said in Resume Critique:
If I bragged about that, I could brag about just anything.
If it's released to the job, you probably should.Its better than bragging get about nothing and listing a word.
As a hiring manager, I don't agree. I want to know what is useful to me and factual, not opinion and only useful to someone else.
-
@scottalanmiller said in Resume Critique:
You can't get away from the arbitrary failure component. That is the critical piece here. Along with not knowing if the disaster avoidance was the employee or a manager.
Then put that information in the CV. On that one line. Putting on your CV means you did it. Otherwise it should not be on the CV. I want to know what you did. Not what soembody else did.
-
Examples:
- Implemented Hyper-V, no GUI, on four physical hosts, version 2016 - factual experience
- Implemented Hyper-V saving 100,000 semolians - opinion, not factual
-
@scottalanmiller said in Resume Critique:
@jimmy9008 said in Resume Critique:
@scottalanmiller said in Resume Critique:
If I bragged about that, I could brag about just anything.
If it's released to the job, you probably should.Its better than bragging get about nothing and listing a word.
As a hiring manager, I don't agree. I want to know what is useful to me and factual, not opinion and only useful to someone else.
Knowing a prospect is able to stop failure is surely useful. If rather hire somebody that can show an history of preventing failure over one that never has.
-
@jimmy9008 said in Resume Critique:
@scottalanmiller said in Resume Critique:
You can't get away from the arbitrary failure component. That is the critical piece here. Along with not knowing if the disaster avoidance was the employee or a manager.
Then put that information in the CV. On that one line. Putting on your CV means you did it. Otherwise it should not be on the CV. I want to know what you did. Not what soembody else did.
Right. And Hyper-V is what he did. Savings $100K, both in the creation of the cost, and in the fixing of the cost, were someone else.
-
@scottalanmiller said in Resume Critique:
Examples:
- Implemented Hyper-V, no GUI, on four physical hosts, version 2016 - factual experience
- Implemented Hyper-V saving 100,000 semolians - opinion, not factual
No. Factual. Are you saying they lied?
-
@jimmy9008 said in Resume Critique:
@scottalanmiller said in Resume Critique:
@jimmy9008 said in Resume Critique:
@scottalanmiller said in Resume Critique:
If I bragged about that, I could brag about just anything.
If it's released to the job, you probably should.Its better than bragging get about nothing and listing a word.
As a hiring manager, I don't agree. I want to know what is useful to me and factual, not opinion and only useful to someone else.
Knowing a prospect is able to stop failure is surely useful. If rather hire somebody that can show an history of preventing failure over one that never has.
No, because that is almost entirely dependent on the person created the failure and being willing to avoid it, it tells us almost nothing about the candidate. Or in this case, as there isn't even a suggestion that they influenced the decision, it tells us absolutely nothing. But does tell us that they don't know how to convey meaningful information - a major business concern with IT people.
-
@scottalanmiller said in Resume Critique:
@jimmy9008 said in Resume Critique:
@scottalanmiller said in Resume Critique:
You can't get away from the arbitrary failure component. That is the critical piece here. Along with not knowing if the disaster avoidance was the employee or a manager.
Then put that information in the CV. On that one line. Putting on your CV means you did it. Otherwise it should not be on the CV. I want to know what you did. Not what soembody else did.
Right. And Hyper-V is what he did. Savings $100K, both in the creation of the cost, and in the fixing of the cost, were someone else.
Not necessarily. If you read my post I'm saying to say why he use HyperV and gave a possible example why. If it was 'because I was told to'... That's pretty crap.
-
@jimmy9008 said in Resume Critique:
@scottalanmiller said in Resume Critique:
Examples:
- Implemented Hyper-V, no GUI, on four physical hosts, version 2016 - factual experience
- Implemented Hyper-V saving 100,000 semolians - opinion, not factual
No. Factual. Are you saying they lied?
Absolutely, I'm saying that to call avoiding failure a success, we just lie. There is no meaning to saying $100K was saved. It's BS. It requries a ridiculous failure (taxi / wall) to be considered as viable, and then a claim of savings by not arbitrarily screwing the company.
-
@jimmy9008 said in Resume Critique:
@scottalanmiller said in Resume Critique:
@jimmy9008 said in Resume Critique:
@scottalanmiller said in Resume Critique:
You can't get away from the arbitrary failure component. That is the critical piece here. Along with not knowing if the disaster avoidance was the employee or a manager.
Then put that information in the CV. On that one line. Putting on your CV means you did it. Otherwise it should not be on the CV. I want to know what you did. Not what soembody else did.
Right. And Hyper-V is what he did. Savings $100K, both in the creation of the cost, and in the fixing of the cost, were someone else.
Not necessarily. If you read my post I'm saying to say why he use HyperV and gave a possible example why. If it was 'because I was told to'... That's pretty crap.
But the failure was because he was told to, right? Or is he saying that HE was going to screw up and not consolidate, but stopped himself?
-
@scottalanmiller said in Resume Critique:
@jimmy9008 said in Resume Critique:
@scottalanmiller said in Resume Critique:
@jimmy9008 said in Resume Critique:
@scottalanmiller said in Resume Critique:
If I bragged about that, I could brag about just anything.
If it's released to the job, you probably should.Its better than bragging get about nothing and listing a word.
As a hiring manager, I don't agree. I want to know what is useful to me and factual, not opinion and only useful to someone else.
Knowing a prospect is able to stop failure is surely useful. If rather hire somebody that can show an history of preventing failure over one that never has.
No, because that is almost entirely dependent on the person created the failure and being willing to avoid it, it tells us almost nothing about the candidate. Or in this case, as there isn't even a suggestion that they influenced the decision, it tells us absolutely nothing. But does tell us that they don't know how to convey meaningful information - a major business concern with IT people.
No. Disagree still. It does show it as they have said it. It shows they are not a 'yes man's and can change a project for the better.
-
Cost savings of decisions, across the board, is a BS process. It cannot be calcluated meaningfully and is always just opinion. It's useful when a third party audits internally with neutral goals to attempt to determine decision value. But to an outside party it is completely meaningless.
-
@jimmy9008 said in Resume Critique:
@scottalanmiller said in Resume Critique:
@jimmy9008 said in Resume Critique:
@scottalanmiller said in Resume Critique:
@jimmy9008 said in Resume Critique:
@scottalanmiller said in Resume Critique:
If I bragged about that, I could brag about just anything.
If it's released to the job, you probably should.Its better than bragging get about nothing and listing a word.
As a hiring manager, I don't agree. I want to know what is useful to me and factual, not opinion and only useful to someone else.
Knowing a prospect is able to stop failure is surely useful. If rather hire somebody that can show an history of preventing failure over one that never has.
No, because that is almost entirely dependent on the person created the failure and being willing to avoid it, it tells us almost nothing about the candidate. Or in this case, as there isn't even a suggestion that they influenced the decision, it tells us absolutely nothing. But does tell us that they don't know how to convey meaningful information - a major business concern with IT people.
No. Disagree still. It does show it as they have said it. It shows they are not a 'yes man's and can change a project for the better.
We don't know that, because we don't know who created the failure, or who corrected it, or why. It just tells us nothing in that regard.
-
@scottalanmiller said in Resume Critique:
@jimmy9008 said in Resume Critique:
@scottalanmiller said in Resume Critique:
@jimmy9008 said in Resume Critique:
@scottalanmiller said in Resume Critique:
You can't get away from the arbitrary failure component. That is the critical piece here. Along with not knowing if the disaster avoidance was the employee or a manager.
Then put that information in the CV. On that one line. Putting on your CV means you did it. Otherwise it should not be on the CV. I want to know what you did. Not what soembody else did.
Right. And Hyper-V is what he did. Savings $100K, both in the creation of the cost, and in the fixing of the cost, were someone else.
Not necessarily. If you read my post I'm saying to say why he use HyperV and gave a possible example why. If it was 'because I was told to'... That's pretty crap.
But the failure was because he was told to, right? Or is he saying that HE was going to screw up and not consolidate, but stopped himself?
No. He stopped not consolidation by doing consolidation.
-
@jimmy9008 said in Resume Critique:
@scottalanmiller said in Resume Critique:
@jimmy9008 said in Resume Critique:
@scottalanmiller said in Resume Critique:
@jimmy9008 said in Resume Critique:
@scottalanmiller said in Resume Critique:
You can't get away from the arbitrary failure component. That is the critical piece here. Along with not knowing if the disaster avoidance was the employee or a manager.
Then put that information in the CV. On that one line. Putting on your CV means you did it. Otherwise it should not be on the CV. I want to know what you did. Not what soembody else did.
Right. And Hyper-V is what he did. Savings $100K, both in the creation of the cost, and in the fixing of the cost, were someone else.
Not necessarily. If you read my post I'm saying to say why he use HyperV and gave a possible example why. If it was 'because I was told to'... That's pretty crap.
But the failure was because he was told to, right? Or is he saying that HE was going to screw up and not consolidate, but stopped himself?
No. He stopped not consolidation by doing consolidation.
Sure, but that's meaningless. He stopped failure by not failing.
-
@scottalanmiller said in Resume Critique:
@jimmy9008 said in Resume Critique:
@scottalanmiller said in Resume Critique:
@jimmy9008 said in Resume Critique:
@scottalanmiller said in Resume Critique:
@jimmy9008 said in Resume Critique:
@scottalanmiller said in Resume Critique:
You can't get away from the arbitrary failure component. That is the critical piece here. Along with not knowing if the disaster avoidance was the employee or a manager.
Then put that information in the CV. On that one line. Putting on your CV means you did it. Otherwise it should not be on the CV. I want to know what you did. Not what soembody else did.
Right. And Hyper-V is what he did. Savings $100K, both in the creation of the cost, and in the fixing of the cost, were someone else.
Not necessarily. If you read my post I'm saying to say why he use HyperV and gave a possible example why. If it was 'because I was told to'... That's pretty crap.
But the failure was because he was told to, right? Or is he saying that HE was going to screw up and not consolidate, but stopped himself?
No. He stopped not consolidation by doing consolidation.
Sure, but that's meaningless. He stopped failure by not failing.
Yes. And not failing is something to brag about.
-
@jimmy9008 said in Resume Critique:
@scottalanmiller said in Resume Critique:
@jimmy9008 said in Resume Critique:
@scottalanmiller said in Resume Critique:
@jimmy9008 said in Resume Critique:
@scottalanmiller said in Resume Critique:
You can't get away from the arbitrary failure component. That is the critical piece here. Along with not knowing if the disaster avoidance was the employee or a manager.
Then put that information in the CV. On that one line. Putting on your CV means you did it. Otherwise it should not be on the CV. I want to know what you did. Not what soembody else did.
Right. And Hyper-V is what he did. Savings $100K, both in the creation of the cost, and in the fixing of the cost, were someone else.
Not necessarily. If you read my post I'm saying to say why he use HyperV and gave a possible example why. If it was 'because I was told to'... That's pretty crap.
But the failure was because he was told to, right? Or is he saying that HE was going to screw up and not consolidate, but stopped himself?
No. He stopped not consolidation by doing consolidation.
Was it his failure and he changed his mind? Did he talk the CEO out of it? Was it really considered honestly? Was the good idea always the leading option and he just didn't get in the way? Was he the one talked out of doing the wrong thing?
