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.
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.
>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.
> 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.
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.
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…
I guess oxide gets away with it because they have the podcast and lots of people know a lot about the company and are pretty sure they want to work there. It's like would you do a nine hour interview to find out if you can go on a date with some random person from a dating app, no, but would you spend 9 hours with someone that you see potential to be your future wife or husband when there's mutual interest? Yes
while .local is reserved, it's reserved for mDNS, and should be avoided on things like active directory. using an internal subdomain of a registered public domain is best practice. .internal is also okay.
Then why hasn't there been a gTLD reserved for local use? The only ones that are reserved are .local and .home.arpa. .local is out, since it is entirely for use with mDNS / Bonjour.
That leaves .home.arpa, which is very awkward and only a thing since 2018 (my home network's use of .lan definitely predates this). Especially as a non US citizen. It also seemed so far that .lan was the "unofficial" gTLD to be used, since much software like OpenWRT was already using it anyway.
Either way: making .lan internet routable seems entirely unhinged to me. LAN has always been the acronym for Local Area Network. Why would anyone sane think that it is a good idea to make this into a gTLD that can be internet routable? The only way I see forward to do this justice, is to only allow RFC 1918 and IPv6 addresses that are within the assigned prefix for your router.
This seems like a worse version of allowing .zip to be a gTLD. Remember the idea of downloading something from https://github.com/[...]@evil.zip?
> Then why hasn't there been a gTLD reserved for local use?
.qm to .qz and .xa to .xz have always been implicitly reserved as TLDs that will never be globally-routable [0] [1], but these aren't exactly the most intuitive names so it's unsurprising that nobody uses them.
(".internal" as mentioned by the sibling comment [2] is the best choice these days, but its definition is somewhat recent.)
(note: i hope .lan does not get approved, but people have to understand that they are rolling dice when using unreserved names)
edit: fucking wild that this is downvoted into negatives. press the wiki link and read the first line if you don't believe me. in fact, i will quote it: "The name internal is reserved by ICANN "
The only ones rolling dice here is anyone attempting to use the .lan TLD for public services, given that OpenWrt (and by extension most GL.iNet products) will not publicly resolve .lan under their default configuration.
Pihole here will still serve .lan internal domains. Anyone that registers .lan globally are the ones guilty of using a culturally busy domain that was unreserved before.
In time we'll see articles like "Don't register a .lan domain if you want people to visit your site"
Eh, maybe someone spinning up a brand new environment using it in 2026 should have known better. But you don't have to go that far back to reach a point where the current list of gTLDs would make .lan feel safe.
While you're not wrong, I suspect that .lan sees more real world usage than .local
It may not be an official standard, but it does have some weight as a de-facto standard.
I've tried briefly to try and find some numbers to back that up, but can't find much beyond apple's bonjour vs consumer routers - although I've seen companies with AD domains using .lan as well. (Although, I've also seen companies using 1.0.0.0/8 for their internal addressing...)
it definitely gets used, and i hope that the application is denied, but i also hope this is another wake up call for people that pick unreserved domains.
Wake up to what? The fact ICANN have failed in their governance responsibilities by not encoding a widely used defacto private namespace into the reserved namespace RFC and considering delegating it publicly?
whether you consider this a failure of ICANN or not is completely beside the point.
if you choose to use an unreserved domain, you are choosing to accept the risk of something like this happening. take ownership of your choices. "but other people use it" is not a great defense.
It's a default on OpenWRT and Ubiquiti devices. I don't think consumers should be blamed nor suffer because they didn't know their pricey Ubiquiti router was using a de facto but not officially reserved TLD. you can blame Ubiquiti i guess, but once upon a time there were no reserved TLDs and it was the job of ICANN to deny new ones that had widespread understanding not to be internet routable, so it's not like there's no precedent for Ubiquiti's behavior either.
>If that was the only thing that “living off grid” meant, then you’d be right. But it’s being used in this case as a shorthand for many things that don’t involve power grids.
to your original point, though, none of those "many things" is solipsism or total isolation.
>In January 2025, Cleo was revealed by internet sleuths
this type of sleuthing, when someone is not doing any harm, is typically quite off-putting. if someone is contributing good to the world but trying to maintain some anonymity, it's really rude to try and "out" them.
however, i guess reshetnikov didn't care too much about being exposed as the person behind the name, considering:
>"On 8 February 2025, Reshetnikov posted a Base64-encoded message on his Stack Exchange profile that, when decoded, read "Creator of Cleo"."
reply