Contradictory Tech Interview Feedback Experiences🤯

Photo by Nik on Unsplash

Feedback generally comes in one of two types. It’s either useful or rather irrelevant.

I would have agreed with that as a statement, right up until I’ve been subjected to the feedback given to me in recent tech interviews.

I’ve started questioning why they bother to give feedback if it has no value to anyone concerned. What’s worse is some of the feedback is contradictory and contrary in nature. 

I’m going to dredge up that feedback today and let you into some of the most perplexing comments I’ve received.

Too Strong, Too Flexible

This is a recent piece of feedback I’ve received from a technical interview.

“You have strong opinions about your own code, but were too flexible about code generally”

What’s worse in this case is I get what they mean. The issue is I presented a tech test with a couple dubious decisions. So, what is the best strategy here, should you defend your code or crumble at the first “I’m curious to know” question? I decided to go in hard and defend my decisions.

On the other hand, they asked whether I would block a pull request using network objects in the business logic. I said it depends on the team, I’m flexible — it depends. They kept pushing and I eventually said that I would block the PR but it appears that they remembered the word flexible.

The feedback they should have given: We don’t like you, and the decisions you made were wrong.

The Three Bears

I interviewed for a small startup. I decided to think of a compelling reason why I’d want to work for them (quite difficult actually, it wasn’t an exciting opportunity). I said something about having worked for massive companies and tiny companies, so working for a scaleup that is growing would be of interest to me. Imagine my surprise at the feedback:

“Has never worked in a set up quite like this, has always been in a much smaller company or much larger company”

I’ve had other variations on this feedback telling me I’ve worked in companies that don’t work in the same way they do or using exactly the same technology. I mean, if it’s precisely the same job as I’m leaving why precisely would I want to join?

The feedback they should have given: It is clear from other feedback - “couldn’t always get a sense of what they were trying to say” that they really didn’t like me.

Too Technical

I went for a technical interview and got this feedback (in the cons section):

“Their instinct was always to talk about the tech”

A technical interview for a software engineer gave me this feedback, to be clear.

The feedback they should have given: Talked too much.

Bored

“You might get bored not doing new things all the time. Also, you’re too junior.”

The classic “you’re overqualified and underqualified at the same time.” 

The feedback they should have given: We want a unicorn who can also perform magic tricks at the company picnic.

Software Engineering

“You didn’t know enough about good software engineering practices.” 

This followed a pointless discussion down a tangential tech rabbit hole. They found an area I was weak in and kept asking, asking and asking until I couldn’t answer. I don’t see what that has to do with software engineering practices honestly.

The feedback they should have given: We rate you on your weakest areas, not your strongest.

Conclusion

I’m feeling quite unemployable at the moment, that is despite having a job.

Seems strange to say, but that is the situation.

Previous
Previous

6 Essential Software Engineering Tips

Next
Next

The Tip of the Software Developer Iceberg🧊