>"my greatest weakness is that I work too darned hard"

>>16785110

i say im obsessive. which is actually true. if something gets in my system it doesnt get out til its done and i will sit there for 12+ hours a day and forget to eat just to make sure its done and done right.

>>16785124
>>16785115

Some variation of "I work too hard" seems hackneyed.

My honest weakness is that I get bored and complacent after mastering something, that would obviously be a horrible thing to say though. Can anyone think of a positive way to spin it?

"I'm allergic to to technical debt. Sometimes I get carried away paying it back."

This is NOT a non-flaw. It can slow a project down, sometimes greatly, and particularly when you're maintaining a legacy codebase. But in general, even when your solutions don't work out in the short term, they can pay off in the long term, and good managers know how to leverage that. If only they can keep you pointed in the right direction.

>>16785163

>seems hackneyed

its a job interview. most any positive spin you give to your weakness will be hackneyed.

>my honest weakness is that i get bored and complacent after mastering something

that may be honest, but its far worse than giving a hackneyed response.

>can anyone think of a positive way to spin it

sure
>i get bored with compacency. once i master something i NEED to go on to the next level and do it bigger and better

>>16785179

I like it. Thanks.

>>16785191
This is really good advice. My sister works in HR and told me about this answer pretty much, she worded it differently though.

Be prepared to back it up, give examples and sell it. The first time I used it on a bunch of asses who told me it was an easy way out and I needed a different answer. Didn't want to work for them anyway.

If you are feeling ballsy, a variation of:

I am a straight talker, some people have a problem with that. So if someone asks me a bullshit question, I will point out it's bullshit.

... like now.

>>16785163
>I get bored and complacent after mastering something

That's just "I work too hard" wearing a funny hat.
You are saying you are so fucking good at everything you do you need to be challenged constantly.

>>16786055
Protip: this is not a question where you're supposed to be honest. It's like "tell me about a time you experienced failure" - You're supposed to tell them how you learned from an obstacle, not a time that your fucked up and it sucked.

You can be honest with your response, but definitely follow up with some kind of "but i recognize this as an area of improvement, so I'm trying to compensate for it".

I, for example, am naturally messy. Like, super dosorganized. However, since I know that I'm disorganized, I make a conscious effort to try to be as organized as possible. I have to try harder at it than other people who are naturally orderly, but I still do my best

>>16785110
Do NOT try the call-a-strength-a-weakness ploy (like I work too hard). They know that trick.

Instead, choose a real weakness that has little or nothing to do with the job. For example, if you will be mainly working on your own, say something like "I'm not assertive enough at meetings" or "I'm sometimes shy with customers"

Not OP here, but would

>I am never too happy with the end result of my work, because I know I could have done better and didn't.

work?

>>16786152
That just makes you sound kind of lazy, or like you do subpar work.

Being unsatisfied because you strive for perfection is one thing, but "I could have done better and didn't" makes it sound like you didn't try as hard as you should have. You're framing it wrong.