Resume Critique
-
Example. I recently cut a company's development time in half. Saving them a fortune on employee costs and getting them to market way faster. Do I brag about it? No, because I didn't do anything impressive. I just showed them that fundamental good decision making was better than picking random gibberish out of their butts. I didn't fail, but I certainly can't brag about the decisions that I made. Sure, I'm better than the people who were making the decisions before. But their decisions were failures. They aren't to be used as a serious measurement for success on my part. For me to call that a success means I have to lower my own value to a level of being totally pathetic in order for that to be impressive - that's a big price to pay, lowering my own level so that one avoidance of failure looks like "a success by my personal standards."
That's what will happen with the CV. It drags down the person in order to make one small decision warrant being considered a success. Overall, it's a huge loss for one small win. It's like totally scrapping the war in order to win one tiny battle.
-
@scottalanmiller said in Resume Critique:
@jimmy9008 said in Resume Critique:
Saying that's not good as is should never have been wrong is just bollocks. Things go wrong, showing you can make them go the correct way is important.
This doesn't make any logical sense. It doesn't show that at all. It shows that disaster was avoided. It doesn't show why or by whom. Only that the CV writer wasn't a cause of the disaster. We don't know who proposed the consolidation, why the failure was considered, who made the decision or based on what criteria. It shows nothing positive about the CV writer at all, only that they didn't sabotage the project themselves by refusing to consolidate.
No. The fact that they are saying they consolidated using hyper-v, and if they why they did it, does show that the CV writer did it. Entirely.
And yes on your other points. Saying you stopped an idiot doing something idiotic by doing the great thing you did and Ankit that idiotic thing turn in to a successful thing... Is what should be shown. Saying goodbye Hyper-V tells me nothing...
Why is Hyper-V on the CV. The why makes you go to the yes pile. The word on its own sends out to the no pile.
-
@jimmy9008 said in Resume Critique:
@scottalanmiller said in Resume Critique:
@jimmy9008 said in Resume Critique:
Saying that's not good as is should never have been wrong is just bollocks. Things go wrong, showing you can make them go the correct way is important.
This doesn't make any logical sense. It doesn't show that at all. It shows that disaster was avoided. It doesn't show why or by whom. Only that the CV writer wasn't a cause of the disaster. We don't know who proposed the consolidation, why the failure was considered, who made the decision or based on what criteria. It shows nothing positive about the CV writer at all, only that they didn't sabotage the project themselves by refusing to consolidate.
No. The fact that they are saying they consolidated using hyper-v, and if they why they did it, does show that the CV writer did it. Entirely.
It doesn't even mention or suggest that. It shows that they did the work, not that they made or influenced the decision.
-
@scottalanmiller said in Resume Critique:
Example. I recently cut a company's development time in half. Saving them a fortune on employee costs and getting them to market way faster. Do I brag about it? No, because I didn't do anything impressive. I just showed them that fundamental good decision making was better than picking random gibberish out of their butts. I didn't fail, but I certainly can't brag about the decisions that I made. Sure, I'm better than the people who were making the decisions before. But their decisions were failures. They aren't to be used as a serious measurement for success on my part. For me to call that a success means I have to lower my own value to a level of being totally pathetic in order for that to be impressive - that's a big price to pay, lowering my own level so that one avoidance of failure looks like "a success by my personal standards."
That's what will happen with the CV. It drags down the person in order to make one small decision warrant being considered a success. Overall, it's a huge loss for one small win. It's like totally scrapping the war in order to win one tiny battle.
No. Showing you changed that failure to a success saving so much cash an time is a success, and is something you should brag about.
-
@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.
-
@jimmy9008 said in Resume Critique:
No. Showing you changed that failure to a success saving so much cash an time is a success, and is something you should brag about.
I didn't make it a success. I just avoided failure. There is nothing worth bragging about there, I just followed industry baseline. It would be totally embarassing for me if I bragged about and people pointed out that all I did was the "normal starting point" for a project of that nature.
-
@scottalanmiller said in Resume Critique:
@jimmy9008 said in Resume Critique:
@scottalanmiller said in Resume Critique:
@jimmy9008 said in Resume Critique:
Saying that's not good as is should never have been wrong is just bollocks. Things go wrong, showing you can make them go the correct way is important.
This doesn't make any logical sense. It doesn't show that at all. It shows that disaster was avoided. It doesn't show why or by whom. Only that the CV writer wasn't a cause of the disaster. We don't know who proposed the consolidation, why the failure was considered, who made the decision or based on what criteria. It shows nothing positive about the CV writer at all, only that they didn't sabotage the project themselves by refusing to consolidate.
No. The fact that they are saying they consolidated using hyper-v, and if they why they did it, does show that the CV writer did it. Entirely.
It doesn't even mention or suggest that. It shows that they did the work, not that they made or influenced the decision.
That's why I'm saying 'consolidated saving X per year'. That to me says you did it. Other it's not be written.
-
If I bragged about that, I could brag about just anything.
-
@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:
Saying that's not good as is should never have been wrong is just bollocks. Things go wrong, showing you can make them go the correct way is important.
This doesn't make any logical sense. It doesn't show that at all. It shows that disaster was avoided. It doesn't show why or by whom. Only that the CV writer wasn't a cause of the disaster. We don't know who proposed the consolidation, why the failure was considered, who made the decision or based on what criteria. It shows nothing positive about the CV writer at all, only that they didn't sabotage the project themselves by refusing to consolidate.
No. The fact that they are saying they consolidated using hyper-v, and if they why they did it, does show that the CV writer did it. Entirely.
It doesn't even mention or suggest that. It shows that they did the work, not that they made or influenced the decision.
That's why I'm saying 'consolidated saving X per year'. That to me says you did it. Other it's not be written.
Still says nothing. It says that Hyper-V was used, that consolidation happened. It doesn't say why or who made decisions and the cost savigns, as we pointed out, is fake because it is against an arbitrary level of failure.
-
@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.
-
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.
