[giantg2]

That's not my experience.

I'm consistently told that communication is my strong point, that I'm good at interpreting statements into wanted functionality, and that my professional opinions are very thorough and well-thought out.

I'm told I'm slow. When I do code screens, usually in a language that I have limited experience in due to my diverse background in technologies, I don't get the job because others are faster.

[28304283409234]

I feel you pain. And whenever I do get hired, after 6 months, I have a deeper understanding of the architecture than most of those "fast" coders.

I'm a diesel. But that's not what gets you through jobinterviews nowadays.

[dieselgate]

Appreciate the diesel analogy!

[warrenm]

>I'm a diesel

Low RPM, loads of torque?

I'd hire that!

[MattGaiser]

Especially since you tend to interview for your next role. You don’t earn it through good job performance.

Beyond learning new technical skills, how I perform in my current role probably will not impact what comes next.

I’m considered by many to be a clear writer. I would happily trade that skill for leetcode.

[Wiseacre]

Ah the never ending difference between what employers say they want and what they actually want.

[giantg2]

It's not even reading between the lines. I ace my behavioral and/or conceptual sections. Then I fail the code screen for being too slow. I know they want fast people - they all do. That just leaves people like me in a shitty position, questioning what I should do with my professional life since the first 10 years have been a waste.

[wnolens]

This is my experience too.