Remix.run Logo
▲ Aurornis 6 hours ago

It’s interesting to me that 9 hours of interview time is considered excessive by some people. Over my career I’ve done interviews that required plane flights, hotels, and multiple separate days on site.

I’ve also done interviews that were brief 30-60 minute casual discussions followed by an offer during the hiring craziness that happened in a few years in the past. Anecdotally, coworkers at those companies were a completely random range from smart and kind down to the meanest, most clueless people I ever worked with. They had high turnover both because they were always firing bad hires (hire fast only works if you also fire fast) and people were burning out from the perpetual stream of bad hires being randomly injected into the company after they talked their way through the short interview.

Looking back, the interview processes that took the longest were certainly not perfect, but the companies that had them were much better about maintaining a coherent culture and high bar for the coworkers I would get. Every new hire felt like someone amazing who I was happy to be working with.

Everyone has different priorities, but looking back I think the relatively small amount of time I invested into long interview processes (relative to the 2000 hours I work every year) was time well spent.

▲john_strinlai 6 hours ago | parent | next [-]

for me, at least, one interview process being 9 hours isn't a big deal and i agree with you that a company doing that is likely to have a more coherent culture and make smarter hiring decisions.

the problem is that when the job market isn't too hot, you might be applying to a dozens or even a hundred+ positions. if 5-10 of those all have 9 hour processes, well now you have 1-2 full weeks work of unpaid interviewing to do, which is a lot to organize, prepare for, etc.

▲Aurornis 5 hours ago | parent [-]

The only time I see people blitzing interviews and stacking 5-10 different companies interview processes is when they’re unemployed urgently trying to change jobs. In those cases it makes sense to do whatever you need to do to stack interviews.

For normal job changing, people are more selective and interview maybe a couple times per year, spread out over time. In my experience it hasn’t been hard at all to get 3 hours here and there for interviews. Tech company culture is usually forgiving about people leaving for appointments and other things so this isn’t nearly as hard as it is for some of my friends in other careers where it’s PTO every time.

I’ve also not actually seen many cases where people schedule 10 interviews at once and actually get the full interview experience at every one of them. People get rejected at earlier stages of the interview process or they start pulling out if they realize the job isn’t a good fit. It would be very rare for someone to schedule 10 interviews and actually invest the maximum time into every single one of them.

So I understand your concern, but in my observation this pattern doesn’t really happen. People have been doing much more involved interviews (travel, flights, hotels) for decades.

▲john_strinlai 5 hours ago | parent | next [-]

>In those cases it makes sense to do whatever you need to do to stack interviews.

right, people will do it, but then they'll complain on a forum about having to spend 60+ hours (with prep time) for a handful of interviews with no guarantee of a position and i think that's a fair complaint to make.

>I’ve also not actually seen many cases where people schedule 10 interviews at once and actually get the full interview experience at every one of them. People get rejected at earlier stages of the interview process or they start pulling out if they realize the job isn’t a good fit.

sure, but even if you drop out partway through the process, the prep time remains the same, you're still blocking out time and scheduling, you're still occupied for a portion of the day, etc.

>So I understand your concern, but in my observation this pattern doesn’t really happen.

i have observed it often enough with my former students (and sometimes current ones) to be understanding of the people complaining about a 9 hour interview.

▲r3trohack3r 3 hours ago | parent | next [-]

> right, people will do it, but then they'll complain on a forum about having to spend 60+ hours (with prep time) for a handful of interviews with no guarantee of a position and i think that's a fair complaint to make.

This is an acceptable filter for me on both sides of the table.

You are interviewing them as much as they are interviewing you. Where you work should be a major life decision. These are the humans and craft you’re going to spend your time with/on for 40+ hours a week for years. You aren’t going to get a glimmer of understanding of the culture, people, and work in a single 45 minute interview (short of major red flags).

If all you’re doing is looking for a job, any job, I get this sentiment - and the other side of the table needs to be looking for a butt in a seat, any butt, and then these shotgun interviews work.

But if you’re optimizing for career and quality of life, having an extended diligence process is a pro, not a con. Especially since that means the team you’re joining has passed muster in the same diligence process when they were hired.

A strong diligence process signals the company takes who they hire seriously - and that the people who work there take where they work seriously.

▲nomel 4 hours ago | parent | prev [-]

Nobody doing long interviews is doing it blindly. It's because you're already passed some reasonable level of screening that mostly resembles a regular 45 minute type interview.

▲serial_dev 5 hours ago | parent | prev [-]

And how about people who have a job that they just don’t like that much, and would love to escape.

Having 9 rounds of interviews sounds crazy excessive. Why is the 9th interview needed that you couldn’t have figured out by the 8th interview? If regular companies do that, I opt out, it’s a don that they are delusional, inefficient, incapable of making decisions and don’t respect candidates time and potentially different life circumstances (candidates might have family, full time work, hobbies, other interviews).

On the other hand, their company is quite unique, I bet they have enough applicants, so in the end it’s supply and demand, and companies in extreme demand can make their interview process as tiring as they wish…

▲cortesoft 27 minutes ago | parent | prev | next [-]

On the other hand, in my 20 year career the only real interview I did was for my first job. Every one after that was from people I worked with recruiting me to work with them somewhere, and the interview process was more about pitching me on their company.

Sometimes i wonder if I would have a better career if I was more proactive in my job searches, but I do enjoy the experience of being pursued a lot more enjoyable than pursuing.

▲ChuckMcM 3 hours ago | parent | prev | next [-]

This is very well put. There are different ways to 'pre-filter' the candidate pool, from quizzes to purity tests. What a many startups don't seem to understand is that the 'culture' is the people and what they do. So taking care in interviews tends to hire people who take care in their work. And unlike the gp comment I never felt 'bad' after a number of hours of interviews and a decline, I had a better understanding of the company, presumably they had a better understanding of me.

Reading the article though it was interesting that having a positive EBITDA was the real news here. Not a single AI company can claim that. That's a pretty big milestone.

▲Aurornis 2 hours ago | parent [-]

> There are different ways to 'pre-filter' the candidate pool

Reading the replies here, most are assuming that every candidate gets the maximum interview duration. I see a lot of arguments that if someone applies to M jobs and each requires N hours of interviews then they're spending M*N hours without knowing they'll get a job.

Usually you don't get scheduled for interviews at all unless there's a good chance that they expect you to pass the hiring bar. When you are scheduled for interviews, they don't go straight to the full gauntlet until the early interviews show promise.

So by the time someone goes through the 3 x 3 hour interviews in this example, there's probably a very good chance that they're being seriously considered as a hire.

▲ChuckMcM an hour ago | parent [-]

I agree with this. Also I empathize with the trauma a lot of tech people are going through in the current market because of my experiences in the 'chip downturn', 'dot com downturn' and the 'economic downturn in the late naughts'. So I'm seeing a lot of 'maxing' like this; "I send out 10,000 resumes and maybe get 1,000 people interested, and 100 people willing to interview me, and this takes 9 months and I've only got a few more months of 401k I can eat up ... ahhhhhhhh!" My experiences going through these sources of downturns changed me a lot, I don't see how it couldn't have.

▲QuiEgo an hour ago | parent | prev | next [-]

I remember before COVID trying to interview multiple places and time it where offers will land at the same time. I remember flying 3 times in one week (!) to make this happen. We have it easy now :).

▲Philip-J-Fry an hour ago | parent | prev | next [-]

9 hours is certainly excessive considering there's only 8 hours or less in a work day!

▲tptacek an hour ago | parent [-]

It's over several days. This used to be a pretty normal thing in hiring processes!

▲unshavedyak 6 hours ago | parent | prev | next [-]

> It’s interesting to me that 9 hours of interview time is considered excessive by some people. Over my career I’ve done interviews that required plane flights, hotels, and multiple separate days on site.

I think part of the reason is that interviews have gotten more adversarial as time has gone on. Ie less respect for the interviewee, more of a power dynamic, more careless wasted time in lazy take home assignments, etc.

I wouldn't mind 9 hour interviews to 3 companies if i knew i'd land the job. It's the 1,000 companies that many people experience that gives them pause after so much disrespect through time.

▲b112 5 hours ago | parent | next [-]

I've worked as an employee, a contractor, and owned my own firm and hired. Seen all sides.

Until the last few years, the idea of hours and hours of interviews wasn't a thing. I interviewed at IBM and was hired after two, 1 hour interviews. One of those over the phone.

I can't even envision what these interviews are all for. It feels like people attempting over the top risk management, without really scoping the risk. It feels quite disorganized.

▲nomel 4 hours ago | parent | next [-]

I firmly believe it's because someone getting fired, for poor performance, is a huge deal now.

Where I am, exposing someones poor performance is more of an exhibition in the failure of the hiring process and all involved. So, you just keep the under-performers around.

▲bcantrill 5 hours ago | parent | prev [-]

Well, bullshit actually. When I went to Sun in 1996, I was flown out for a full day of interviews (9 hours!) plus both lunch and dinner. (And this was true for more or less every company I interviewed with.)

I'm not sure why people are indexing so hard on the interviews, as we matriculate very few candidates into conversations; if you want to complain about something, complain about the written nature of our hiring process.[0]

[0] https://rfd.shared.oxide.computer/rfd/0003

▲jghn 3 hours ago | parent | next [-]

Yes, I definitely had some full day interviews back then, including travel time.

The largest difference I have found between then and now is what the interview actually consists of, not how long they last.

▲spullara 3 hours ago | parent | prev | next [-]

btw congrats on the company. i was skeptical at the time but it was never because you wouldn't attract awesome talent and make great hires. your process looks great to me.

▲bcantrill 2 hours ago | parent [-]

Thanks! And don't worry -- there were PLENTY of reasons for skepticism in 2019! We got lucky many times over, hitting on stuff that turned out to be really important in ways that we couldn't know at the time.

The hiring process is a very concrete example of that. What still blows my mind (at least a little) is that our process came directly out of one of the worst moments in my career: making an absolutely terrible hire about two years before we started Oxide. For a while after that, I wished I could go back and warn my previous self to not make the hire that would be so destructive to the organization -- but in the years at Oxide I have come to realize that that terrible hire was in fact essential for the future Oxide: it was the impetus for putting together a writing-intensive process, and there is no doubt in my mind that I had I not made this atrocious hire, I would have continued to hire the (broken) way that I had been hiring. (I described this a bit in my conversation with Gergely Orosz on hiring.[0])

Anyway: don't get me near the time machine -- I'll only screw things up.

[0] https://oxide-and-friends.transistor.fm/episodes/hiring-proc...

▲ahl 4 hours ago | parent | prev | next [-]

in Sun's defense, that was in the 1990s, before the invention of the telephone.

▲b112 an hour ago | parent | prev | next [-]

I think people are just generally grousing about Interview length, not about your company specifically. Don't worry about it. It's not aimed directly at you.

I know in my case, it's not about you directly.

▲Barbing 5 hours ago | parent | prev [-]

Thank you for caring about us.

▲bitwize 3 hours ago | parent | prev [-]

"Job interviews" in tech used to be casual conversations of a few hours. There weren't even quizzes to see if you really could program, let alone leetcode-grinding insanity.

Once a system gets gamed en masse, anti-gaming measures dominate, and ruin, the whole process. See also: ads vs. ad blockers, and the fact that you can't run a fucking email server of your own anymore without jumping through security hoops.

▲Aurornis 3 hours ago | parent [-]

> "Job interviews" in tech used to be casual conversations of a few hours. There weren't even quizzes to see if you really could program

How far back are you referring to? I'm definitely not the oldest person around here, but most of my interviews since graduating college were more than casual conversations.

The exceptions were primarily where I was coming in via a referral or they were hiring me for something that was already proven and verifiable, like open source contributions.

▲jghn 3 hours ago | parent | next [-]

When I was coming up in the 90s what I found was it was mostly conversational, sometimes with some whiteboarding although of a much more relaxed nature than contemporary whiteboarding. It was more a tool to help express your thoughts and draw pictures than writing code.

There were some companies like Microsoft who were starting to become known for being more intense, but I never came across that.

It wasn't until the mid-aughts that I started to see brain teasers, "real" whiteboarding, and other aspects that started to bleed into standard interviews.

▲spullara 3 hours ago | parent | prev [-]

my first job at a startup (first engineer after the founders) consisted of 13 hours on the phone with the CTO over a few weeks and then an in person all day interview that included traveling from Chicago to SF and a couple of dinners with the founders. this was 1996. our typical interviews after joining were all day affairs and they people almost all people that were referred in or had worked with in the past (I wasn't).

interviews at twitter back in 2010 were 6 hours and that was true even for me when we had an agreement to acquire my company pending the success of those interviews. at the time they had a lot of ex-googlers and they were setup similarly.

▲mlyle 2 hours ago | parent | prev [-]

An 8 hour interviewing day plus an hour on the front end (screen) or back end (confirm/double check some things/really meet manager) can make sense.

3x 3 hours sounds -exhausting-.

▲Aurornis 2 hours ago | parent [-]

> An 8 hour interviewing day plus an hour on the front end (screen) or back end (confirm/double check some things/really meet manager) can make sense.

> 3x 3 hours sounds -exhausting-.

I think most people would prefer 3 x 3 hour blocks.

A 3 hour block could be worked into a day without anyone batting an eye at every (tech) employer I've ever had. People go to appointments all the time.

A full 8 hour interviewing day requires taking the day off. It's also exhausting to do it all continuously.

The 3 x 3 hour structure also allows the company or candidate to end it early if it doesn't look like it's going to be a fit. I'd rather lose 3 hours and than take a vacation day, spend 8 hours somewhere, and then get rejected if they knew I wasn't a good fit after the first few hours.