Live data from Hacker News

Red flags I saw while doing technical interviews

blog.interviewing.io

51–60 of 394 posts

Re: Red flags I saw while doing technical interviews

#51
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.

I know a lot of people who have “accepted” exploding offers but then just keep interviewing and will try to renegotiate or just reneg if they get a better one.

Re: Red flags I saw while doing technical interviews

#52
post #2

I was hoping this was red flags from the interviewer side. Yeah I'm hoping a blog will give me some feedback.

Aren't "red flags" from the interviewer side pretty obvious? Most interviews are just noise with very little signal.

Some basic red flags:

* Poor ability to self-reflect or demonstrate that they've learned things from their experiences

* Lack of or otherwise poor critical thinking

* Inability to communicate

* Inability to display core competency in the skills required for the job, especially when challenged (I don't do "adversarial" interviewing, but I do throw a lot of spanners into their answers to see if they can vary their approach)

* Inability to demonstrate handling challenges and negative experiences constructively

* Poor decorum - "putting your hands at 10 and 2 on the wheel." There's not always one single thing that becomes a red flag, but things like badmouthing 3rd parties, airing of grievances, extreme arrogance, and so on. The proverbial "Would I like to work with this person?"

Re: Red flags I saw while doing technical interviews

#53
post #43

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 because default MacOS configuration is artificial systemwide bold(ing?) of all fonts. So developers create a lighter font than needed and then on MacOS it mostly ok (disregarding the fact that it is not a native bold font but processed one) but on other OSes it is this light grey mess.

As I understand it, macOS uses grayscale antialiasing by default, while Windows and Linux use subpixel hinting. To make up for the artificial thinning that occurs with grayscale antialiasing, it also uses something called "font smoothing" which makes everything look a little bolder.

Re: Red flags I saw while doing technical interviews

#54

The "Not Enough Clarity about your Role" issue has killed Google with so many potentially outstanding employees. For years and years you wouldn't interview with your team, or even be told what team you would be joining. It is slightly better now, but you still don't interview with your specific team until very, very late in the process, if you even do. One of the worst things about interviewing at the big G.

Part of that is because of the expectation at Google that you will just move around. You don't really hire specifically into a given team, and that could be disconcerting, for sure. But you are also given enough respect by the company to assume that as a competent SWE you should be able to move around fairly easily to almost any team in the company.

When I started (9 years ago) it was stated during onboarding that you would be expected to move every two years or so. That's probably softened a bit, but it's still a part of the culture.

So even if you don't love where you're initially slotted, nobody is going to frown excessively when you transfer elsewhere after getting past your noogler phase.

I've found it frustrating to interview at other places and get blank stares when I ask about how team mobility works within the company, what happens when the team is restructured, etc.

Re: Red flags I saw while doing technical interviews

#55

Role clarity is a huge one in my book. I've turned down numerous offers because when I asked what the specifics of my day to day job were going to be, the answers weren't clear. From the secret FAANG that likes to pretend what they are doing is defense contractor level top secret, and even after your hired you might not know what your actually working on, to the big companies where its clear the hiring manager only h…

Of the big tech companies, I've worked at Facebook, Google, & Apple. I've still not quite cracked what's different about Apple culturally that they seem to be more immune to this problem. The only main difference I can spot is I don't recall ever encountering a PM at Apple. To do planning engineers would propose improvements, new features, etc. These were bubbled up. Then executives would be responsible for building…

Would echo your sentiment that the role of project manager, product owner or whatever they're calling it these days needs to be rethought. In my org we literally have a squadron of these individuals which leads to bickering and an in-cohesive product experience.

Re: Red flags I saw while doing technical interviews

#56
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.

There is no reason to not be honest about these types of things (unless of course you're doing something shady). If you want to fill the position quickly, you should say so. Now, of course, as a candidate if I heard that I would jack up my compensation numbers, but again, if you want to fill the seat quickly that's how it works.

Re: Red flags I saw while doing technical interviews

#58
> If through all the different stages of the interview process, you experience a consistent lack of interest or low morale from your interviewers, you might want to pay attention

This is good advice. I certainly have a different perspective of a number of companies, where my outlook of those companies has changed are after witnessing this. It was easy to pass on those companies.

Re: Red flags I saw while doing technical interviews

#60
I generally agree with the points, but have a few places of disagreement:

> Your interviewer is only open to solving the problem ONE way

If this is someone you'll be working closely with, it's a yellow flag, but the common complaint you read here about algorithmic interviews not being the best way to evaluate someone for a job, this really just tells you how good this person is at either that problem or interviewing.

> Consistent lack of interest or low morale from interviewers

Normally, I'd agree fully, and as an interviewer, I go in with a sales hat on over my technical hat. During covid, I have no idea how to read low morale.

> based in Palo Alto...a six-figure offer definitely didn’t seem like a bad start

This is table stakes for a software engineer in the Bay Area, now. Not sure why it was worth adding.

Post reply on HN