Live data from Hacker News

If You Want This Job, We Must Interview You Forever

newyorker.com

331–340 of 415 posts

Re: If You Want This Job, We Must Interview You Forever

#332

Whenever these posts come up, there's a certain amount of hubris to be found. For those programmers who didn't jump through the hoops for a good gpa and now refuse to jump through hoops for a job, what exactly are you willing to do?

...get actual work done?

Re: If You Want This Job, We Must Interview You Forever

#333

I’ve been interviewing for 8 months. Getting to many final rounds, 1 lowballed offer, 1 rescinded offer, and it’s playing a mental toll. Today, I got a rejection that went along the lines of “everyone loved you and there was absolutely 0 negative feedback, but we just found a better fit.” I almost broke down, but hid behind a facade of positivity because the long weekend was starting and my kids can’t afford a bummed…

It's amazing how from one interview or technical test to the next, you can feel a worthless human being or a god amongst your peer.

Re: If You Want This Job, We Must Interview You Forever

#334
post #113

Earlier quoted context omitted.

If they said in the interview they’re very comfortable with Vue.js and Postgres, and then you find out after a few weeks that actually they barely know Vue or Postgres, they actually come from a React/SQLite background, they’ve overpromised. Rather than ensuring every bullet point on their resume is factual through six interviews I’ve found it’s better to assume they’re honest and as capable as advertised, interview…

Find me an engineer who knows both vue.js and Postgres and they’re worth their pound of salt. And, if you’re differentiating against React and SQLite - e.g. they’re not familiar with JSONB style queries or CTEs, but instead have some alternative, par familiarity with another db… and the same level of sophistication with an FE stack - e.g usage of useRef vs forwardRef… and you cut them loose… well, they’ll probably be…

Hello, please deliver the salt.

Of course "knows" is not that precise. Postgresql is vast and complex.

Re: If You Want This Job, We Must Interview You Forever

#335
post #199

Earlier quoted context omitted.

This is why propbation periods exist. It’s a chance for the employee or employer to back out.

Probationary periods are good for companies, but they're horrible for early stage engineers. They don't know how to take it, and they probably don't have a lot of money saved up. I think if companies decide to fire someone after a probationary period they should give them a $1,000 bonus or something to carry them over. That engineer has given up other opportunities and maybe moved or made changes in their life. Not e…

In France if you're let go during the probation period you're entitled to unemployment (if you have accrued the rights).

Re: If You Want This Job, We Must Interview You Forever

#336

Earlier quoted context omitted.

I disagree. > the employer can easily weather In a large business maybe, but more often than not in a large business you're a number and you're gonna pass probation regardless. In a smaller business, the cost of recruitment process can be huge, it's not just 1 hour interview and you're done as an employer. It's hours of reviewing CVs, contacting people, arranging times, conducting interviews, weening people out, disr…

> In a smaller business, the cost of recruitment process can be huge, it's not just 1 hour interview and you're done as an employer. It's hours of reviewing CVs, contacting people, arranging times, conducting interviews, weening people out, disruption to your primary job role, etc etc. That's a huge cost and drain on the business. Not as life-changing to the business as it is to the employee. > At the same time I've…

> And yet, that did not cause the business to pay the current employees less, or downstaff, did it?

> After all, if the financial implication did not involve cutting costs down just to survive, then it is not comparable to an individual, who literally has to spend less money and cut out existing costs just to survive.

I’m not sure you understand. It still costs the company.

It was the employees decision to leave because he decided he didn’t want to do the work he was hired to do.

Should the company say “oh no problem we will just pay you because we have some money in the bank right at this very moment in time”?

Re: If You Want This Job, We Must Interview You Forever

#337
post #180

Earlier quoted context omitted.

This is why I just interview endlessly. At least one a week. You need to develop a callus to interviewing. Find the time for it by rubber stamping a few code reviews. It gets boring after a while. Just a very repetitive process after 100 or so.

Do you do the full loop with each company? How do you select the companies? Do you feel bad if they’re smaller ones and you’re not serious about it?

Yes. I usually target hybrid roles in a place I am unwilling to live like New York as many are explicitly for practice. And I generally do not interview for smaller companies as the process is usually wacky. I was once asked to argue for forcing a company on Linux, Mac, or Windows for a dev role.

Re: If You Want This Job, We Must Interview You Forever

#338

Earlier quoted context omitted.

This is why I just interview endlessly. At least one a week. You need to develop a callus to interviewing. Find the time for it by rubber stamping a few code reviews. It gets boring after a while. Just a very repetitive process after 100 or so.

Once you interview and turn them down then will they interview you again? Doesn't that close a lot of doors?

My solution to this is to book many of my interviews in places where I am unwilling to live, like New York. So whether or not I am burning bridges, it does not matter because I would not accept many of those roles anyway.

Re: If You Want This Job, We Must Interview You Forever

#339
post #69

Earlier quoted context omitted.

I found it funny that a week ago I got an email from a Google recruiter, offering me to enter their interviewing machinery. I bluntly told him that I rejected the offer because of the horror stories regarding 5-7 interviews in Google. The recruiter's reply was that it was ok of this was not an appropriate time for me , and that we would stay in touch. How can they be so dense? Of course it may be that they are also j…

Google interviews sound awful if I'm being honest. The last recruiter I spoke with said it involved a technical test and phone interview, after which they'd see what teams had openings and that it would be 3-4 2+ hour interviews per team before an offer was made if I was a fit. Who has the time for this?

That's pretty much standard for almost every startup and non faang company I interviewed in Canada / US
Post reply on HN