Sounds like a great company raising money for the right reasons.<p>Oxide continues to be one of the most inspiring companies in the space, I was just encouraging someone to apply there yesterday. :)
Still waiting for their 10 inch homelab mini oxide servers
I know they'll never do this but, by god, I would line up so fast for a mini oxide that I can homelab out of.
I mean, most of the code is open source. With enough enthusiasm and skill, you could probably make a reasonable home-lab out of that code, and some second hand hardware. And yeah, it would not be _hardware-software-co-design_, but it would be better than nothing, plus you will -- for a brief shining moment -- be the only person on planet earth (who is not formally affiliated with Oxide) who has an Oxide home-lab.<p>You could be a hero. A legend. The internet might even write poems and sing songs about you.
Before I joined Oxide I did a little fan-boying (as one does) and put together home lab components as best I could. You _could_ tie 3+ mini-PCs together and wrangle omicron into some semblance of working that way. But it would not be pretty.<p>However! You absolutely can use non-simulated Omicron: <a href="https://github.com/oxidecomputer/omicron/blob/main/docs/how-to-run.adoc" rel="nofollow">https://github.com/oxidecomputer/omicron/blob/main/docs/how-...</a><p>You'll get a single node control plane that's mostly workable, and be able to spin up VMs all day with it. That's what I did. Additionally, if you want to play with microcontrollers you can install Hubris onto STM32H753ZI dev boards! I have one connected to my TrueNAS server over UART and USBTTY for sensors, power management, and console.
Honestly, right now I'm pretty happy with my Nomad and heterogeneous hardware setup of cobbled together compute. But it's honestly not a bad side project idea.
I went hunting but it seems this isn’t even rumoured.<p>I want something like a Synology for the drives, but with something like a Mac Mini for the computer. Ubuntu or similar.<p>I’ll keep dreaming.
Oh hell yes. Throw us a bone @bcantrill
NixOS is the perfect homelab solution. You don't really want an overengineered VM monstrocity - that stuff is only needed to work around coporate process insanities.
They have one of the best hiring processes in the game. Just all around great people who care.
I was interested in applying to Oxide a few months back. They ask candidates who reach interviews to provide at least 9 hours of availability, normally arranged as three separate 3-hour blocks. Each block contains three 1-hour interview slots, so the standard schedule is effectively nine one-hour conversations. Not including the follow ups.<p>I got another great offer after just 1 interview that I took, so I never went through their process, but it looks very exhausting to me. Being rejected after investing so much time must also feel awful.
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.<p>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.<p>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.<p>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.
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.<p>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.
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.<p>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 <i>all</i> 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.<p>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.<p>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.<p>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.
><i>In those cases it makes sense to do whatever you need to do to stack interviews.</i><p>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.<p>><i>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.</i><p>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.<p>><i>So I understand your concern, but in my observation this pattern doesn’t really happen.</i><p>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.<p>This is an acceptable filter for me on both sides of the table.<p>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).<p>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.<p>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.<p>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.<p>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).<p>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
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.<p>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.
> There are different ways to 'pre-filter' the candidate pool<p>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.<p>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.<p>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.
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.
> 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.<p>I've never been flown somewhere for a multi-day process. 5-hours or less of actual interview time on those for me. The lead-up was usually 3-or-fewer 1hr calls.<p>Yeah, the travel eats up some other time, but that's different than being grilled for 3 hours straight on three separate days.<p>I agree with the "that seems overly excessive" position.<p>I'm very curious what marginal signal they think they get from hours 6-9.
> 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.<p>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.<p>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.
"Job interviews" in tech used to be casual conversations of a few hours. There weren't even quizzes to see if you <i>really could</i> program, let alone leetcode-grinding insanity.<p>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.
> "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<p>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.<p>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.
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.<p>There were some companies like Microsoft who were starting to become known for being more intense, but I never came across that.<p>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.
I'm to understand that Microsoft was one of the companies that had more relaxed interviews in the early 90s, and then took a turn for the more intensive in the mid-90s.<p>Perhaps the turning point was Jim McCarthy's "beware of a guy in a room", which he meant both figuratively and literally, leading to a transition away from solo or shared offices or even cubicles for software engineers and toward open-plan arrangements. I think that his wisdom led first Microsoft, then the rest of the industry, to treat software engineers not as the darling whiz kids they were in the past, but more a cohort to be closely watched and controlled, as the company is risking a lot on them.
My first job in 2004 was a pretty casual conversation. My next few through the 00s were basically the same tbh.
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).<p>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.
I've worked as an employee, a contractor, and owned my own firm and hired. Seen all sides.<p>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.<p>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.
IBM - well, that tells us all :) seriously though, you may be referencing the dot com era, when a warm body was all that sufficed
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.)<p>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]<p>[0] <a href="https://rfd.shared.oxide.computer/rfd/0003" rel="nofollow">https://rfd.shared.oxide.computer/rfd/0003</a>
Yes, I definitely had some full day interviews back then, including travel time.<p>The largest difference I have found between then and now is what the interview actually consists of, not how long they last.
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.
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.<p>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])<p>Anyway: don't get me near the time machine -- I'll only screw things up.<p>[0] <a href="https://oxide-and-friends.transistor.fm/episodes/hiring-processes-with-gergely-orosz" rel="nofollow">https://oxide-and-friends.transistor.fm/episodes/hiring-proc...</a>
in Sun's defense, that was in the 1990s, before the invention of the telephone.
Thank you for caring about us.
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.<p>I know in my case, it's not about you directly.
I firmly believe it's because someone getting fired, for poor performance, is a huge deal now.<p>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.
My experience more closely matches yours, but I've also done the multiple rounds of painful interviews.<p>I do find that the latter can be explained by care and concern, and also by organization chaos and poor boundaries. It's hard to tell until you're in them, but I try to avoid the latter whenever I can.<p>As another commenter mentioned - I now respect companies that take their time in hiring. The last thing I want is to jump on with some company that will hire anyone. But there is an element of respect - if you're just duplicating questions and wasting my time? GTFO here.
Back in the days of ZIRP and you could get a job just by showing up it wasn't so bad. Nowadays I certainly wouldn't bother unless it was for a dream job.
9 hours is certainly excessive considering there's only 8 hours or less in a work day!
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 :).
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.<p>3x 3 hours sounds -exhausting-.
> 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.<p>> 3x 3 hours sounds -exhausting-.<p>I think most people would prefer 3 x 3 hour blocks.<p>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.<p>A full 8 hour interviewing day requires taking the day off. It's also exhausting to do it all continuously.<p>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.
How many of those extended processes ended in a <i>no</i>?
IME those kinds of interviews are a waste for the applicant because you have to do your 5-10 minute elevator pitch and 10-15 minute dive into your experience 9 separate times. It’s terribly exhausting.<p>On the other hand I like meeting a lot of people that I’d be working with. It’s nice to start day 1 knowing who people are.
In our interviews, the interviewer has read the applicant's detailed written materials, and the candidate has received the interviewer's materials from when they applied. So there is no elevator pitch, no walking through resume, no getting to know you. Just a conversation.<p>We also advance very few candidates to interviews and hire a surprisingly large proportion of those who interview, so it's not like you're doing all this interviewing for the usual slim chance of being hired. The written materials are the primary filter.<p>Hiring process RFD: <a href="https://rfd.shared.oxide.computer/rfd/0003" rel="nofollow">https://rfd.shared.oxide.computer/rfd/0003</a>
Yep, I had two interview processes that did this... 8 times, at the same time.
Both said no after 8 interviews because of one person in the process who didn't like me, everyone else supposedly were on board.<p>It genuinely took me another year to even consider applying to another job it was so demoralizing.
You are going to potentially spend a major portion of your life there - so it isn't that weird to set aside a full day to get to know them.<p>In my experience with this format it isn't like you are coding for 9 hours. It starts with soft HR stuff, ends with a sales pitch to you, and most of the middle is just pleasant conversation with interesting people.
> You are going to potentially spend a major portion of your life there - so it isn't that weird to set aside a full day to get to know them.<p>Right, but you're not just doing it with them, you're potentially doing it with lots of companies you're applying to. It would be untenable to devote that much time to every prospect. Oxide can only do it because most other companies don't.<p>There are lots of axes on which to judge a company so I wouldn't write off Oxide for this alone, but it doesn't speak well of their respect for their candidates' time.
When I worked at Oxide, you only get to the interview part if you’re extremely close to an offer. Like, down to one or two candidates out of hundreds.
There's been several mentions of disrespecting the candidate's time in this conversation. Is the expected value of that time investment not worth it? You're trying to land a job. It seems like it would be, even if you have ten such companies.
The reason companies have that many interview hours spread across multiple slots is that then have fallout over the funnel.<p>They don’t have every candidate scheduled for the entire time of all the rounds. If you don’t pass earlier rounds, they’re not going to waste time (yours and theirs) hauling you through more rounds of interviews.<p>If you make it to the end of all of those scheduled interviews, there’s probably a very good chance you’re getting an offer.
I understand that, but it's still possible to devote up to 9 hours to this and get nothing in return. And maybe not just possible, but likely. We don't know how eagerly their pipeline rejects candidates. Every candidate has to take that gamble.<p>9 hours just seems excessive. Other companies have "funnel" hiring processes like this and still manage to do it in 3 hours instead of 9.
A full day is a lot unless you get compensated or something for it I feel. In today's world it is a lot of ask. I could also not be spending any time there, in which case that day is wasted. Imagine if all interviews of all your applications took a full day… probably burn off half your PTO just interviewing…
[dead]
I personally don't mind the multiple interview slots or 9 hours of conversations. It's fair since it takes their team members an equivalent amount of time (though it's split across team members, each team member is likely interviewing many others as well).<p>My blocker has been the initial written answers to the questions. I've had the questions half-answered for nearly a year now. I want to do it properly (sans AI) but other things come up and I question the EV of spending the time, especially since I'm not a strong writer in the first place※.<p>For Oxide, it makes sense to demand a strong writer due to their culture, so even if technically qualified I might not be a good fit, assuming I even get an interview.<p>※ - I write unambiguously, but use point form whenever possible and am not great at naturally writing concisely.
Sans AI is definitely the way to go if you plan to submit!<p>As for the materials, they play a part in the conversation stage, and even if you get hired and interview others hoping to join. Every interviewer reads the materials of the candidate, and we send the interviewer's original materials to the candidate. It's not nearly as tedious as some of these comments are making it out to be (and believe me, I've been through the "ten elevator pitches" gauntlet in my career).<p>tbh, I really enjoyed filling out my Oxide materials. They got me thinking and taking stock of my wins and motivations, not just the crap we throw on resumes to attract the eye.
> It's fair since it takes their team members an equivalent amount of time<p>Well, they're being paid to do that. That's part of the unfairness. The other part is the time is bounded on the employer side. On the prospective employee side, it's unbounded - you're interviewing until you get a job somewhere.
Right...so best interview process in the game for employers, not so much employees.
It's also an investment of their time into you. I assume some candidates get cut after the first or second block, in which case keep in mind the further you make it, the more invested they are in you as a prospective hire.<p>It's important to remember the interview process isn't just one way. That's 9 hours you get to interview <i>them</i> (which I would personally love to help inform my decision) and you can always walk away early if it doesn't look like it will be a good fit.<p>I'd go even further if I could, and work on a little test project with the team to feel this out. Despite everyone's best intentions during a hiring process, neither of you know for certain how it'll go until you're in the trenches together.
As someone who has dealt with both sides (interviewing and working with those that pass the interview), I really wish a long interview, like this, was standard. 45 minutes is not enough, unless it's easy to fire people.
I agree, 9 of one hour interviews is exhausting just imagining it. In my company, 3-4 steps of 1h each that spans over days were already stressed. Guess I’m too old for that kind of companies
Dont you want to spend more than 1 hour getting to know the company you might spend the next 5-10 years of your life with?
> Being rejected after investing so much time must also feel awful.<p>I did an interview process that was 6 hours, one hour per <i>week</i>, then flew me in for a 6 hour on-site. They decided not to take me at that point and provided no reason.
At least you know what the time commitment is up front. Not true of every company.
Nine hours is crazy
I feel like this topic comes up <i>every single time</i> interview processes are discussed. Lots of people complaining "that process is too onerous! How do they expect me to invest that much time! In person coding problems are worthless!" And I don't necessarily disagree with that, but I do wonder what a lot of folks then expect a good process would look like while still allowing the employer enough information to make a decision.<p>Oxide can obviously impose a 9 hour interview process because they're a good enough company that lots of smart, motivated people want to work there and thus good candidates are willing to endure that process. Lesser companies obviously can't impose that process because there aren't enough good candidates willing to endure it.<p>My main point being, different strokes for different folks. If you think that process is too long, great, find a company with a less time consuming process. But Oxide's process obviously seems to work well for them, so I think it's pointless to complain about it (note I don't really think that's what you are doing, but a bunch of reply comments certainly are).
Joel Spolsky said it 20+ years ago: The primary goal of the hiring process is to <i>avoid</i> bad hires, even if you need to turn away potentially excellent hires. If you want to hire insanely good people, there is no alternative to a very onerous process.
This is the same argument that says YouTube can play 3 unskippable ads, TVs can scan and collect data on all devices in your LAN, because they're a private company and can do what they want, and if you don't like it, just don't buy it. Well in that case, I can also smoke in front of kids, because I am a free agent and there's no laws saying I can't.
Except that analogy has absolutely nothing to do with what I posted.<p>First, some potential candidates (I'll raise my hand) actually <i>prefer</i> a rigorous, onerous hiring process. I prefer to work with people who put a lot of thought and investigation into their technology, and who demand a high bar for their colleagues. I'm not just talking about "length for the sake of length" interviews or irrelevant brain teasers, but I want to know a prospective employer is putting a lot of thought and work into who they hire. One of the biggest red flags for me is if the hiring process is just a bunch of "shoot the shit" interviews.
[flagged]
I read their "we will respond to every application, even if it has to be a brief non-specific rejection" and thought that sounded like a great policy that I wish more companies would follow. It's been 6 months now and I never heard anything from them, so that's a little disappointing.
I don't know how they possibly read all these in full. They are quite voluminous: 1-3 work samples, 1 analysis sample, 1-3 writing samples, 1 presentation sample, and then 8 open-ended long-form questions. The instructions often say to give as much detail as possible, and they are very clear that this is the main way they filter candidates, so I'm guessing serious applications are quite long.<p>At some point, there becomes a mathematical impossibility of too many pages of applications for too few evaluators who also have to do the rest of their jobs. Either they don't get quite that many applications, or the initial evaluations must be based on some incomplete reading (looking just at the resume, reading a subsection, skimming, or randomly discarding), or the backlog keeps growing.<p>Fwiw I also applied and the auto-reply said I should expect to wait 4-6 weeks, which has recently passed without hearing back. The application is a ton of work, and I don't mind doing it with a significant chance of being considered, but I think it's a normal reaction to be devastated if you put all that time and energy into crafting your materials, which manifest all your experience, behavior, and personality, and it turned out nobody read them. I still have a little hope, but I'm sorry you never got a response.
No they don’t.<p>They waste very large amounts of candidate time on an essay like assignment before you get to talk to someone.<p>Truth be told they already know from your resume if you’d be worth interviewing. That’s enough , and maybe a OA.<p>The best process I’ve experienced, was a quick conversion with a few technical questions, then I can start as a contractor. If it works out it works, if it doesn’t that’s ok too.<p>No need for me to write a long paper, when HR probably took one look at my resume and sent out a rejection.
Looks really cool. I like that kind of process. But the gap between my current skills(mostly application and Data engineering) and the hardware and performance engineering guys they want is large.<p>Sometimes a company comes along that one what's to join even if its outside my wheel house. Do they have an intern/mentorship program for generalists that one can join that could turn into a FTE?
I just heard about this company for the first time. the energy does feel inspiring
Yes they seem to be doing everything right so far. Inspiring and exciting.
What is their product exactly? It’s a server that is cheaper for some reason?
the product is a podcast the server is just merch
B2B/Enterprise datacenter software. Alternative to VMware and the likes. None of their core products are open to the average Joe afaik. There was a post about that sometime back on here.
Enterprise software and hardware, built from the ground up. Definitely not just a VMware alternative, though the end product is virtual instances of course.<p>We're building racks over here! And all our software is open source.
Its a bit strange thing to say, their software is QUITE LITERALLY OPEN TO EVERYBODY. Its literally all Open Source.<p>Their product is a bunch of servers in a rack designed to run that open source software.<p>But you can run most of their software yourself.
It's a server that is more expensive for some reason.
Username checks out.
It's the full hardware/firmware stack up to and including VM hypervisor. A complete rack solution, but it's the tailored firmware and integrated hypervisor, networking that sets it apart from another OEM that sells you a full rack solution. Afaik.
Love the photo caption "FIGURE 1. US BEING AS EXCITED AS YOU CAN BE PAYING TAXES".<p>Oxide are so good at comms.
But maybe not great at finance?<p>Why are they paying taxes if they have a huge order backlog. Expand your production capability. Amazon famously had no profits on paper for many years because of their relentless expansion.
Oxide doesn't have the same type of capex opportunities that Amazon had. Amazon had a massive physical footprint to build. Oxide contracts with other companies to produce the actual boards. Most of the inventory of components they have are held in their contractor facilities. So they don't have extra warehouses to build. They could change course and adopt more in-house production. However, I think doing that during the sale of their first model would be unwise.
> Why are they paying taxes<p>"Paying our taxes" in this kind of context is nearly always shorthand for "filling out our tax returns". That part usually takes a substantial hunk of time. The actual payment process is typically writing a check or entering credit card info, which just takes a few seconds.
Well, in this case it was actually literally paying our taxes. (In the photo, Steve is about to initiate a wire to the IRS.) At our size, it's not a check -- and certainly not a credit card.<p>As to why we're paying taxes: while tax minimization is certainly a thing (and we have taken advantage of things like R&D tax credits), we're paying taxes because we're profitable.
>we're paying taxes because we're profitable.<p>I guess the question is why not invest those profits to further expand when there are already a backlog of orders to fill.<p>But on the other hand Huge Congrats being a profitable company! Hardware business is insanely brutal, and having the backlog is great to hear. AMD being investor I hope you guys get Zen 6c and Zen 7c earlier in the future.
Hah, well, I stand corrected. And also, huge congratulations on profitability!
Can I just say how unfathomably based you guys are re:<p>"Compensation
Everyone at Oxide makes $275,000 USD, regardless of location."
As someone who has applied less than 6 weeks ago, this is great news. I can't wait to hear back!
Maybe they're not trying to be great at the tax avoidance game.
The post is about how they don't have the capital to safely expand production capacity, which is why they're raising more.
And yet that seems like a caption Bryan could have written…
How is oxide trendy and IBM systems z/i are seen as archaic? Isnt that essentially what they sell “cloud” on prem? Seriously wondering what are the major differences in market, is it just that Oxide is targeting modern software stacks?
Oxide is so cool, I just wish the hiring process was a little less crazy. I spent such an incredible amount of time on my application just to not hear anything for months until I got the rejection.
I think that hiring process is what makes that entire team great and hum in such harmony. At the very least, going through that rigorous writing process helps you prepare for other applications or prepare materials for future applications with other companies. Hiring is hard. I have heard Bryan Cantrill say something that has also been true in my experience, along the lines of: Some of my biggest career mistakes were related to hiring.
The company is not very big and has a lot of very talented people.
The vibe is probably similar to what big tech used to be in the early 2000s<p>I'm pretty sure most people getting in are not getting in through classic website application, but by word of mouth, or knowing somebody who's in etc.<p>It's the type of company where you probably know before applying if you belong or not.
I looked at applying there way back in 2020 and bounced off the application because it seemed like more work than I had time for.
Awesome company, awesome products. I wish they pushed AI less in their socials, like we get it computers and servers means ai workloads. It just devalues their whole image in my opinion. Hope you all do continue to do awesome things and don't become evil.
I'm surprised they didn't go the debt route, trade finance could cover their customer orders. I know they are risk averse in case companies back out of orders, but bringing on more shareholders is its own form of risk.<p>Is something else going on here, are they locking in orders from AMD and other suppliers beyond their current order backlog?
Debt can bankrupt you, equity can’t. They’re concerned the meme companies will collapse, cancel their orders and then kill them. Then mr bezos will turn up and liquidate their assets.<p>Or… they could just take on equity investment at no risk.
This is a crazy take. If you can raise on good terms (or better) then it almost always beats debt. Debt can make it a lot harder to raise or take on more debt in the future.<p>They're profitable, they are going to get the best terms possible at this moment.
But if they're just scaling inventory, debt makes way more sense because they payoff is almost instant as soon as they fulfill the order to the customer. I agree the math is hazier when you're talking about massive capex, growing headcount, or other longer-horizon capital commitments. But if they just need to buy inputs to sell output to complete an order backlog, selling a portion of the company seems odd.
The people running the company are people who lived through the tech crash, and saw how quickly the entire economy around them can evaporate. At Sun, only slightly exaggerating, they went from flying high and controlling a market segment, to seeing all the demand evaporate and customers vanish, leaving the company holding the bag on just massive piles of inventory, basically in a day.<p>When you sell shovels, even slight downturns are massively exaggerated because the shovels can be resold, and if some of their customers go under, it's not just that demand that goes away, it's all the demand that can be satisfied by their customers purchasing second hand servers from the bankruptcies instead.<p>No-one can really say how long this bubble will last. Might pop tomorrow, might be a decade. But if Oxide funds inventory on debt, and the bubble pops, they go with it. Whereas if they fund on equity, and it pops, they will come out the other side just fine. The cost of this is that the old stockholders have a slightly lower upside.
They can likely fund the purchase orders for 10% while they grow. Sounds cheaper than giving away a percent of all future profits. This is very common.
That would mean they would be growing <i>slower</i>. Being common is irrelevant.<p>Raising a Series D is an attempt to <i>permanently</i> increase the velocity of their enterprise. The change in the cap table is negligible if they succeed.<p>Raising debt right now would be a massive unforced error given they were able to shore up half a billion dollars in funding. If the funding well were dry then it'd be a different story, but that's not the case.<p>Can you imagine if they raised $445M of debt?
blog mentions the use of debt facilities, there's a smart mix of both debt and equity
I found myself confused about what they actually do. They sell you a server rack + software stack that you keep on-prem? The comparison between traditional cloud vs. on-prem vs. oxide is vaguely worded and I can't figure out if their hardware is physically stored on-prem or not.<p>Maybe I'm just tired!
Funny I was about to ask the same question. Went to look at the products they offer and was confused why HN gets pumped up all the time with anything oxide do :) End of the day looks like a great product that has great comms team.
Yup, it’s a rack+software. My understanding is that you get all the convenience of the cloud, but the hardware is yours
They aimed to bring the ease of scaling workloads and infrastructure-as-code workflows from the cloud to the on-prem data center, and did so by owning the stack from cold boot all the way up.
yes, goes on the customer premises, or their colocation facility of choice
its not going to go anywhere
with agentic coding lock in @ AWS and Google Cloud is evaporating fast<p>a few days ago I migrated a non-trivial firestore app to sqlite<p>10x less latency (10x requests / second)<p>migration took a few minutes (+ 2 days of prep)<p>just a few months ago that would have been infeasible or at least nerve wracking
SQLite isn’t equivalent to something like aurora.
It's all software in the end. If you plan ahead, it is hard to be completely locked in. I worked for a company, where we had build a data transformation pipeline, and we had GCP and AWS credits, and wanted to use both of them. We built a minimal, high-level library that could be mapped onto both PubSub and SQS (we were transforming the WARC files from the internet archive, in preparation for data analysis). Once we built this, and worked around the near-criminally incompetent design of SQS (e.g. PubSub does compression, batching, and does not send duplicate messages, while you need to all that yourself for SQS), we were able to use both clouds (for free) at the same time, and we were not locked in at all.<p>In fact, we had a call with some people who worked at GCP, and I (naively, and excitedly) mentioned that our design is simple/minimal and cloud-portable. A miasma of awkwardness fell upon the conversation, and I realized that the reason that the GCP people were so keen to speak to us, was that they were anticipating, that once we used up the credits, that they would then get regular recurring revenue from the company.<p>Most cloud companies are in the business of locking you in via very convenient APIs, that would be costly to migrate off of, if you did not abstract them away to begin with (naturally, the egress costs cannot be abstracted away, but those were not much of a problem in our case, because our output-data was very small compared to the input-data).<p>There is an expression in my native language: he who lacks virtue in the head, has virtue in the legs.
I just looked into their product, WOW that is cool. Wish them the best
FYI previous discussion of the series D <a href="https://news.ycombinator.com/item?id=49174407">https://news.ycombinator.com/item?id=49174407</a>
Maybe the most thoughtful fundraising announcement I’ve seen. Focusing on all the right stuff.
if these guys just capture 1% of spend that's on AWS, Azure & Google Cloud they will still be very big.
Excellent podcast, still not sure about their stack. No GPU support is a hard sell these days.
> No GPU support is a hard sell these days.<p>No GPU support is a hard sell for people who latch onto buzzwords and media narratives without actually understanding technology. CPUs are not going anywhere.
> No GPU support is a hard sell these days.<p>you still need pure compute when doing the agentic ai dance.<p>you certainly need gpu for inference purposes, but everything else (harnesses, tools, mcps and the actual software) still runs on regular cpus with regular ram and storing data on regular disks.
This is literally a post about how no GPU clearly isn't a hard sell.
Really cool company! Checking out the state of the product I would have expected to see a gpu / tpu server there. Is this on the roadmap?
I was watching some Oxide videos recently and I think this one answers that question: <a href="https://youtu.be/n2ze5RCy3TM?t=928" rel="nofollow">https://youtu.be/n2ze5RCy3TM?t=928</a><p>Timestamped to "the differentiator" (15:45) and "what are you guys doing about GPU?".
we have an FAQ Friday on this: <a href="https://oxide.computer/faq-friday/what-is-oxides-thinking-around-gpus" rel="nofollow">https://oxide.computer/faq-friday/what-is-oxides-thinking-ar...</a>
Right? Bryan, go put a GPU in there, integrate it in a noncrazy way with firmware and software that just works, and go make a killing!
There is little standardization in the GPU world and the technology deprecates quickly.<p>They could certainly pick a previous-generation GPU architecture, and get it integrated their way with Rust drivers and whatever else their technology fetishism is, it wouldn't matter because ultimately people want to run software, and right now all the AI software is targeting NVIDIA SDK as a first-class citizen, and AMD SDK as a distant second-class citizen.<p>So their story is partially correct: get our systems for general purpose and buy GPUs for the rest. It's just that it kind of self-defeats their entire raison d'etre, which is to have a single highly-integrated vendor. Now turns out you still need to deal with the messy world of GPU computing.
Commenting about the unique compensation to ruin someone’s bingo card :)
> Well, yes, it is: most startups don’t pay income tax because most startups aren’t profitable! Indeed, startups seek investment because they have costs long before they have revenue, let alone gross profit — let alone income. This is by design: profitability is a lagging indicator of product/market fit (the adventure in venture capital is investing long before the business has materialized!).<p>Venture Capital is one of the greatest engines of growth, and fitting for the vast majority of early stage tech companies, it is interesting to see how changes in business economics may result in niche, differing capital structures. Eg. Companies which sell RL envs have vastly different economics than a food delivery app.
sovereign compute is the only way out of tiranny
Also time for the quarterly reminder that On the Metal / Oxide and Friends is an excellent podcast if you're into Rust and/or EE. Bryan and co. do such a good job keeping the technical discussions entertaining. Seems like an awesome place to work, too.
With series B,C and now D, makes one wonder; will there be any shares left for the original team?
A confusing thing about fundraising and dilution is that the new shares don’t take away value from existing shareholders.<p>If each share is worth $1 at the valuation used in the raise, then an investor adding $100 million gets 100 million shares for it. The shares aren’t taken away from anyone, they're issued in exchange for the capital.<p>So ideally the dilution is neutral to the <i>value</i> of the equity. In practice this is highly variable because the valuations are fuzzy numbers used for the raise, but you get the idea.<p>If a company can get the same growth without raising, that would be better because the proportional ownership stays higher. However, the reason companies give equity in exchange for capital is that they need the cash for growth and can’t get it on better terms anywhere else.
That's always struck me as a very idealistic way of looking at dilution.<p>Another way to look at it, is that it's partly locking in the value of those shares at the time of dilution, effectively reducing the variance of the future value of the existing shares.<p>As a thought experiment:<p>If you're holding a lottery ticket that you bought, and someone comes along, says they're going to buy 1,000 lottery tickets, but promises to share any winnings with you pro-rata. You don't really have a choice to say no.<p>You'd probably be really annoyed, if your ticket is a winning ticket, you split the jackpot and don't even get a life-changing amount of money back for it. If any of theirs wins, you likewise get a modest amount, but you weren't bothered about losing £1.<p>It's an expectation neutral thought experiment, but reducing variance isn't always wanted!
> You'd probably be really annoyed, if your ticket is a winning ticket, you split the jackpot and don't even get a life-changing amount of money back for it. If any of theirs wins, you likewise get a modest amount, but you weren't bothered about losing £1<p>Your lottery comparison isn’t logical. I think you’re just repeating the same misunderstanding I was trying to dispel above.<p>If you want to force the analogy, you would have to imagine a lottery where your win and the investor’s wins are tied together. Either you both win or you both lose. But to make the analogy actually work, you’d have to imagine a lottery where their ticket purchase increase the winnings proportionally.<p>So in this bad forced lottery analogy, you would have a smaller number of the overall tickets, but the same odds of winning as before and the payout would be the same as before.<p>You’re making the common mistake of assuming that the company could get the same outcome without taking investment money. It’s common to imagine getting that your 0.1% of a sweet $1 billion IPO without ever getting diluted along the way, but getting a company to that IPO point requires a lot of cash. If a company is lucky enough to have all the cash flow they need to get there then they can do it all without dilution. Most companies need to raise some cash to get there, though.<p>So raising the money actually lowers your variance of getting a large payout, because the cash is what enables the growth to that liquidity event.
Here's a good way to think about this.<p>If I have a business and I raise $10M at a $100M valuation for 10% of the company, the people giving me the money really value the business at $90M, their addition of the $10M into the business brings the valuation to $100M.<p>It's not always exactly like that, 1 for 1, but that's the gist. Without the capital, the business is not worth as much as the valuation at the time of the raise.
But as an existing shareholder you have the right to buy in to the new shares to maintain your percentage if you want to.
But that's not how shares work. And companies aren't lotteries.<p>In your example, the additional 1,000 lottery tickets might add nothing whatsoever to the value of the winning lottery ticket in your hand. It's just not a good metaphor. That's not how buying shares in a company works. Investors don't invest using bearer instruments of totally unknown value. They invest using cash. Cash always adds the value of the cash. That's intrinsic to it being cash.<p>A much better way to think about it is that you have something in your hand that's worth X dollars and has Y shares. If somebody were to give you X dollars in investment in exchange for Y additionally issued shares, then at the end of that operation the company, by definition, would be worth $2x, and your Y shares would be exactly half of that value, meaning that you start with X and you end with X.<p>As mentioned, knowing exactly what the company is worth in dollars is a little tricky, but that's the premise, and it completely makes sense.<p>Back to your lottery ticket example: let’s say you had a company with assets consisting solely of a winning scratch-off lottery ticket worth $1,000, and then you agreed to sell half the company to an investor who contributed $1,000 in cash. At the end of the exercise you would have a company worth exactly $2,000 (the company's assets include the lottery ticket and the new $1,000 of invested cash) and you would own exactly half of it.<p>If you have a unique skill at buying scratch-off lottery tickets and can turn that $1,000 in cash into more than $1,000 in lottery tickets, then you and the investor win from the transaction. That's what the investor is betting on.<p>If you can't get those results then the investors shouldn't invest in you and you shouldn't seek investment.
> In your example, the additional 1,000 lottery tickets might add nothing whatsoever to the value of the winning lottery ticket in your hand<p>They add greatly to your expected chance of winning, given you have pooled winnings.
New shares take away from existing shareholders in every circumstance except one: that the money raised is invested in a way that durably grows the business in excess of the dilution.<p>Every story where a company sold for an amount that wiped out employee equity (for example every Bending Spoons acquisition) is because they raised too much and it never materialized into (sufficient) growth.
Similarly, printing more of a nation's currency does not increase inflation.
They’re raising from a position of strength for capital they don’t need. As far as I know, they haven’t published their valuation, but it is very possible they’re giving up little equity. Plus, giving up some equity to meet customer demand is generally a good idea as more revenue means higher valuation.
Forbes has our valuation, at $6b: <a href="https://www.forbes.com/sites/rashishrivastava/2026/10/09/this-6-billion-company-is-betting-companies-want-to-own-their-computing-infrastructure/" rel="nofollow">https://www.forbes.com/sites/rashishrivastava/2026/10/09/thi...</a>
Isn't the correct vehicle when in such a position called a "loan"?
Taking on debt is MUCH faster and easier way for all shareholders in a startup to end up with $0.<p>Loans are a lot better when you're in a more stable scenario - lower growth and/or lower risk of implosion due to just being more established.<p>As well as Oxide is doing, startups are still volatile and taking on debt that might need to restructure or be defaulted can create a lot worse outcome for shareholders than just "we diluted and then stopped growing as much".
depends on market conditions and visibility on future revenue. And current balance sheet, cost of debt vs cost of equity.
Not necessarily, no. That’s just one option with its own risks and tradeoff
Why do you think there wouldn’t be? They are just different prices.
Couldn't happen to a better bunch of people.<p>I used to think that Oxide's business model sucks in the face of the hyperscalers. When AWS/GCP/Azure "just works" and is generally reliable and cheap, why would I go through the trouble of buying my own computers? Well the past 5 years have been a constant decline towards more concentration of power, lack of care for their customers, and degradation in quality in general. AI is of course accelerating this decline - selling de-slopped products is now a huge competitive advantage. All the best luck to Oxide.
Having one of these in a colo is on my bucket list. Would love to just tinker with one to see how they work.
Probably I'm blind.. is there any form of imprint on their page? An address?
may the Sun never set
That's enough that they can drive down to Central Computers and grab a 32GB stick.
- Series B in Jul 2025 $100M<p>- Series C in Feb 2026 $200M<p>- Series D now $445M<p>I expect the next round soon :)
I still don't get Oxide's offering. Anyone care to give me the skinny?
I wrote this back in 2022 when I worked there, and it's still fundamentally relevant today: <a href="https://news.ycombinator.com/item?id=30678324">https://news.ycombinator.com/item?id=30678324</a>
Server racks which are vertically integrated and provide great cooling, are quiet, and fully vertically integrated software (including bootloaders, hypervisor, etc. -- no BIOS!).<p>This includes everything from the rack itself to the PDU/switch/BMC, to the actual server blade and its chassis.<p>All presented in a nice package to give you a on-prem cloud-like experience.
I think this blog covers it pretty well:<p><a href="https://oxide.computer/blog/the-cloud-computer" rel="nofollow">https://oxide.computer/blog/the-cloud-computer</a><p>Basically they sell a pre-assembled rack of compute, storage and networking with their own open source management software to build on-premise clouds.
They are selling you a rack of computers instead of a single computer, with well integrated high speed connection, storage, power, and cooling.
Expensive servers but with no GPU.
Looks like a mainframe computer and their selling point is that the operating system is open source.<p>I have no idea why you'd buy that over any of the more established players that have a proven track record of being able to support these multi-million dollar machines for many years.
I'd argue there's not that great of a track record, legacy vendors are being legally forced to provide better support for their closed-source systems in the EU because it generally isn't very good. Also you're usually buying hardware and software that weren't designed together which comes with many sharp edges we're solving for.
Why are you answering if you have not looked into it very much?<p>Its not really like a mainframe at all. Mainframe usually have extreme hardware availability focus with the goal of extreme uptime. This is the opposite of what Oxide offers.<p>And their OS being open source is far from the primary thing they advertise.
[flagged]
Always happy to see Oxide growing. The way their company is run is pretty close to how I think all engineering orgs should run.<p>Hoping they hire for a position in my area of expertise some day!
awesome job to the whole team. Congrats Bryan and everyone!
$445M is a lot of money.
Congrats to the Oxide team!
I'm interested in exploring what it would be like to use them but... there's no pricing page? I don't even know where to begin.
Is this the new IBM?
hopefully they are.<p>IBM is more than 100 years old and has brought us a lot of innovations of the modern era.<p>To give a trivial example the relational model for databases was theorized by F. Codd while working at IBM Research (see <a href="https://en.wikipedia.org/wiki/A_Relational_Model_of_Data_for_Large_Shared_Data_Banks" rel="nofollow">https://en.wikipedia.org/wiki/A_Relational_Model_of_Data_for...</a> for further details)<p>IBM still does a bunch of stuff, mainly in the research area. They just don't sell netvista/aptiva computers and ibm laptops since like 2005 or so. They still develop and sell mainframes though.
I really wish they had a SOHO offering, would love to run this with NextCloud and personal projects from home.
Congrats!
Excellent news! It's wonderful to see a great company succeeding.
A legit business? Raising legit money?? In this economy???<p>Wake me up please
Congrats! Now it does get tricky - because once you tempt investors with a profit they start worrying about your spending and expect you to keep a profit.
[dead]
[dead]