Live data from Hacker News

Red flags I saw while doing technical interviews

blog.interviewing.io

11–20 of 394 posts

Re: Red flags I saw while doing technical interviews

#11

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.

In my experience it's because people test their websites only on Mac + Chrome, where thin fonts look fine. Case in point, this website is hard to read on FF + Linux but it's much better on Mac + Chrome.

Re: Red flags I saw while doing technical interviews

#12
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 like at the company, and without experiencing the other side of things these red flags become 'things that rubbed me the wrong way.'

Questions you ask are what dig up the red flags. Who am I replacing and why did they leave? What's the largest obstacle the engineering team is trying to overcome? How do you (the manager) manage your team differently? Is there anything you as a manager would like to improve at?

90% of workplace satisfaction can be attributed to (or sabotaged by) one's direct manager. Make sure you'll appreciate their style.

Re: Red flags I saw while doing technical interviews

#13
post #10
post #6

I can identify with the red flag where they try to pressure you to accept the offer in a short period. This is also called an exploding offer. I had a place do that to me and I ended up turning the opportunity down.

On the other hand, there often needs to be a time limit, or else they will be too late to make an offer to the runner-up (when the leader turns it down). I am not sure what a 'reasonable period' is.

That only applies when the company needs to fill a specific position. Specific positions that need a particular person are a minority of SWE roles. In fact it is bad management to let your team get in a situation where there are individual hyper-specialized roles with no knowledge shared.

Re: Red flags I saw while doing technical interviews

#15
post #4

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.

font-weight: 300 is a bit light. Bump it up to 500!

Dear website creators: Just leave it alone. The default font width is just fine!

Re: Red flags I saw while doing technical interviews

#18
post #6

I can identify with the red flag where they try to pressure you to accept the offer in a short period. This is also called an exploding offer. I had a place do that to me and I ended up turning the opportunity down.

It can be a problem for companies too — candidates accepting an exploding offer and then leaving after a month when another offer comes through can be a rational approach. The first place just gets left off the resume.

Re: Red flags I saw while doing technical interviews

#19

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…

there's a link at the bottom of the post to a list of questions you can ask: https://blog.alinelerner.com/how-to-interview-your-interview...

hope that helps.

Post reply on HN