Live data from Hacker News

Red flags I saw while doing technical interviews

blog.interviewing.io

31–40 of 394 posts

Re: Red flags I saw while doing technical interviews

#34

This article seems like another example of mid-level people giving advice to junior-level people. There are far more red flags you can expect from a company by asking the right questions. The article doesn't dive into any of that and reads more like a few gripes from a guy who did way too many interviews and became jaded by it. The technical interview itself is not likely to be a good indicator of what work looks lik…

I thought it was a good article and shouldn't junior level people get advice from mid-level people? That's the next stop on the ladder, after all.

Re: Red flags I saw while doing technical interviews

#35

This article seems like another example of mid-level people giving advice to junior-level people. There are far more red flags you can expect from a company by asking the right questions. The article doesn't dive into any of that and reads more like a few gripes from a guy who did way too many interviews and became jaded by it. The technical interview itself is not likely to be a good indicator of what work looks lik…

It's good to ask a manager whether they read the CIA simple sabotage manual and if they practice any of the techniques in the company.

Re: Red flags I saw while doing technical interviews

#36

Why is the font on this article so hard to read? Maybe it’s not the font, but the weight. I had a hard time reading it and stopped part way through.

Firefox reader view saved me again on this one. If you're on Firefox give it a try, makes it readable.

Re: Red flags I saw while doing technical interviews

#37

Why is the font on this article so hard to read? Maybe it’s not the font, but the weight. I had a hard time reading it and stopped part way through.

It's meant to look pretty, not be read.

Silly me... :))

Re: Red flags I saw while doing technical interviews

#38
post #5

"Not Enough Clarity about your Role" - Like the author mentions, this can definitely signify that the role is not important. The other thing I've noticed over my career is that it could be that the role involves "grunge" work (awful oncall shifts, doing backend work when you want to do only frontend, etc). Companies hide behind cool titles/department names/etc, promising whatever you want to hear to get you in.

Or you are interviewing "for the company" (e.g. Google or Facebook). While it fits their processes, it's always seemed a way to create and reinforce lock in.

"lock-in" of _____ to ____ ? Do you mean making it more difficult for the employee to eventually leave / how?

Re: Red flags I saw while doing technical interviews

#39

Why is the font on this article so hard to read? Maybe it’s not the font, but the weight. I had a hard time reading it and stopped part way through.

Also the (sub)headers are actually span tags followed by paragraph breaks, leading to a completely broken pile of text in the browser's reader view(and probably any accessibility tools).

Re: Red flags I saw while doing technical interviews

#40
post #5

"Not Enough Clarity about your Role" - Like the author mentions, this can definitely signify that the role is not important. The other thing I've noticed over my career is that it could be that the role involves "grunge" work (awful oncall shifts, doing backend work when you want to do only frontend, etc). Companies hide behind cool titles/department names/etc, promising whatever you want to hear to get you in.

IMO it's not really 'not important' as much as 'not honest'.

Someone, somewhere at that company chose to hire someone... and they know what they want them to do. Why aren't they telling me?

Here I am sitting down expecting to divulge all sorts of things / do a dance, but they can't tell me what they want...

There's all sorts of reasons to not tell anyone / corporate circumstances, but it's a really bad foot to start off with / makes me worry.

Post reply on HN