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.
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.
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.
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…
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.
> 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.
> 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.
"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.
> "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.
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.
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.
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.
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.
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]
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
If most companies take that much time before giving you a rejection or not, then job hunting would require quitting your current job to make sufficient time for it. With ten companies you’d need to organize something like 3-4 weeks of vacation.
The reason companies have that many interview hours spread across multiple slots is that then have fallout over the funnel.
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.
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.
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.
You do know: we are telling you. We advance very few candidates to interviews and hire a surprisingly large proportion of those who interview. The written materials are the primary filter.
No, I did not know when I posted that comment. steveklabnik's comment was posted concurrently with mine, and I did not feel the need to scour the whole thread in case there happened to be an answer to this specific question from an Oxide employee. But thank you for the data point.
No worries. It has actually always been my impression that Oxide does good work, even if I may think your hiring process is a bit on the onerous side. Keep up the good work!
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…
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).
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※.
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.
※ - 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!
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).
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
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.
> Being rejected after investing so much time must also feel awful.
I did an interview process that was 6 hours, one hour per week, then flew me in for a 6 hour on-site. They decided not to take me at that point and provided no reason.
Is it not good for exceptionally talented employees who want to work with other employees who are also great at their job and good communication skills?
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 feel like this topic comes up every single time 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.
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.
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).
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.
That’s not how it works. Interviews are like a funnel. If you don’t pass the first interview they don’t schedule you for all of the other hours just to keep going. You get dropped from the pipeline.
When a company says they have 9 hours of interview time, that’s usually the maximum time if you make it through all the rounds. If you get that far, you’re highly likely to get an offer.
You would also be surprised at how many people will actually do 10-20 long interview rounds to try to maximize their chances for the best job.
There are almost two different bubbles of candidates: Those who refuse to do anything more than a couple quick calls, and those who will rearrange their life to spend days putting in work for each job they want. I think that’s fine and everyone should do what works for them, but if you think 9 hours of interviewing is going to turn candidates away from a company like Oxide you’d be very surprised to see the quantity and caliber of applicants who line up for jobs like this.
I think you also might need to adjust your expectations now that AI interview cheating is getting out of control. A lot of companies are moving back to on-site interviews. I’d happily do 3 x 3 hour video calls more than flying and staying at hotels and renting cars to get to an office in another city just to interview.
Agree. Shotgunning 100 applications a month is not a strategy for finding a good job. It says "I don't care where I work, or what the job is, here's my generic resume, please just hire me." And maybe you're that desperate, but IMO you'll get better returns spending more time on fewer/better opportunities.
Not saying we are or aren't looking for that kind of candidate, but I _will_ say that we're very keen on the motivation to join Oxide at all, and the role you're applying for specifically.
You get worse biases by favoring people that don't value their time IMO. Not too mention it doesn't favor working people with other obligations that can't afford to give away an entire shift to interview for a job they might not get.
A hundred roles a month and call backs on 10% of them? That's A) and insane number of applications and B) a really high call back rate.
I'm on the market right now due to a layoff and I have an agent that reviews linkedin every morning and cross references levels.fyi for role leveling and salary and then assess fit to my resume. I get around 5-10 _possible_ positions per day and with human judgement that's usually down to 0-2, averaging about 0.5 per day.
I hear back from probably close to 10% but that's with a highly targeted approach, not just spamming my resume everywhere. And my pipeline is freaking full. It's a full time job doing prep and participating in all the interviews.
The only interview so far that's been a huge time sink has been anthropic's. But that's because I chose it. Their take home I have the option to use between 2 and 8 hours and I used the full 8 hours because I'm highly motivated and the position is well fit to my career history.
That's a loaded question. How about just saying it for what it is. Are you willing to spend 9 hours today (not counting the other interviews you have to do for other companies) for a X% probability of getting a job at company A which you like Y amount.
If X and Y are large enough sure. Most of the time X is hidden and Y is hard to gauge.
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.
They waste very large amounts of candidate time on an essay like assignment before you get to talk to someone.
Truth be told they already know from your resume if you’d be worth interviewing. That’s enough , and maybe a OA.
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.
No need for me to write a long paper, when HR probably took one look at my resume and sent out a rejection.
Oxide's process involves submitting writing with various questions about you, what you've done, and what you're looking for in your career. The process of doing so inherently means reflecting on the answers to those questions, and so some people find it a useful exercise.
But that should be done later in the process. I'd rather an LLM auto-reject my application vs spending 5 hours on a writing exercise.
Think about, I apply to a minimum of 5 jobs per day. If I need to spend 5 hours for each application I'm spending 25 hours a day on job applications. Obviously this isn't possible.
I think that you are (naturally) approaching it from your side, and they're (naturally) approaching it from theirs, and it sounds like it's not a fit. That's a successful outcome for a hiring process.
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.
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?
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.
We're building racks over here! And all our software is open source.
Change "something" to "a computer" and you got it!
It's a big ass computer (technically many computers in a rack) that gives you a cloud provider style API to manage on-premises infrastructure. Plug it in, connect to the web console or API, and provision yourself some sweet sweet virtual machines, disks, and VPCs.
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.
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.
"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.
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.
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.
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.
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.
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.
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 slower. Being common is irrelevant.
Raising a Series D is an attempt to permanently increase the velocity of their enterprise. The change in the cap table is negligible if they succeed.
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.
They said they are profitable aside from funding purchase orders, they don't need capital to fund growth. If they said they raised in order to grow faster and that they were not profitable then I would agree with you.
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.
> 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!).
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.
We're racking hardware right now to move off the cloud providers and but it's just a (small tens-of-millions-of-dollars) test run to start so we didn't want to complicate things by learning anything Oxide-specific, but they are certainly on the radar as the vendor for a larger rollout.
With the major issues with the big cloud providers these days as well as high costs, I’d say there’s a decent shot. Their investors certainly think so.
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.
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.
you still need pure compute when doing the agentic ai dance.
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.
A confusing thing about fundraising and dilution is that the new shares don’t take away value from existing shareholders.
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.
So ideally the dilution is neutral to the value of the equity. In practice this is highly variable because the valuations are fuzzy numbers used for the raise, but you get the idea.
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.
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.
As a thought experiment:
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.
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.
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
Your lottery comparison isn’t logical. I think you’re just repeating the same misunderstanding I was trying to dispel above.
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.
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.
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.
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.
But that's not how shares work. And companies aren't lotteries.
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.
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.
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.
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.
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.
If you can't get those results then the investors shouldn't invest in you and you shouldn't seek investment.
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.
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.
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.
Taking on debt is MUCH faster and easier way for all shareholders in a startup to end up with $0.
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.
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".
Server racks which are vertically integrated and provide great cooling, are quiet, and fully vertically integrated software (including bootloaders, hypervisor, etc. -- no BIOS!).
This includes everything from the rack itself to the PDU/switch/BMC, to the actual server blade and its chassis.
All presented in a nice package to give you a on-prem cloud-like experience.
you buy one or more of the data-centre-rack-sized computers, hook em up to each other / your datacentre network, and you now have essentially a cloud services platform like AWS/Azure, in your own datacentre, under your control, with full visibility of what every part of the platform is doing (hypervisor, underlying bare metal kernel, firmware, bootloader, etc), because it's ALL open source, written from the ground up by them
Looks like a mainframe computer and their selling point is that the operating system is open source.
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.
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.
You can still be heavily cash flow negative while being Net Income positive. It's actually one of the big use cases for VC money; you have a flywheel of revenue but not enough cash to pay to service that revenue and actually get cash.
Well they are not, but this is a startup that's actually buying/creating computer hardware and the most expensive and competitive time in history to source it.
The economics are going to look different than all the sloppified enterprise SaaS startups that charge crazy amounts for a crappy data lake product on S3.
Previously, they’ve stated that they raised merely to give customers confidence that they are in it for the long haul. You don’t want to buy racks from a company that won’t be around tomorrow. Raising money is likely being used to create a war chest, with some amount of it being used to grow the team and operations, to fill demand, and support their customers. Those functions have to grow sustainably, but the demand also signals to investors that it’s working, and continued investment is a good move.
In reality, it could very well be investors just saying “we’re so happy with how things are going, we want more, take our money!!!”
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.
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.
Exactly, no pricing page. Not worth my time to get involved in contract negotiation as a dev when all I want to know is if it's even feasible to try out.
Sounds like a great company raising money for the right reasons.
Oxide continues to be one of the most inspiring companies in the space, I was just encouraging someone to apply there yesterday. :)
I just heard about this company for the first time. the energy does feel inspiring
Still waiting for their 10 inch homelab mini oxide servers
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.
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.
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.
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…
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.
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-.
> 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.
> 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.
"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.
> "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.
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.
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.
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.
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.
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
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.
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...
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.
in Sun's defense, that was in the 1990s, before the invention of the telephone.
Thank you for caring about us.
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.
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.
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.
Hiring process RFD: https://rfd.shared.oxide.computer/rfd/0003
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.
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.
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.
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.
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.
If most companies take that much time before giving you a rejection or not, then job hunting would require quitting your current job to make sufficient time for it. With ten companies you’d need to organize something like 3-4 weeks of vacation.
That is worst possible outcome thinking.
If you consistently fail (or give up) at the very last interview, there's something rather wrong.
Your median/average should be better.
The reason companies have that many interview hours spread across multiple slots is that then have fallout over the funnel.
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.
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.
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.
You do know: we are telling you. We advance very few candidates to interviews and hire a surprisingly large proportion of those who interview. The written materials are the primary filter.
https://news.ycombinator.com/item?id=50021846
https://news.ycombinator.com/item?id=50021016
Great, I'm glad to hear it.
> You do know
No, I did not know when I posted that comment. steveklabnik's comment was posted concurrently with mine, and I did not feel the need to scour the whole thread in case there happened to be an answer to this specific question from an Oxide employee. But thank you for the data point.
Sorry to come off a little abrupt!
No worries. It has actually always been my impression that Oxide does good work, even if I may think your hiring process is a bit on the onerous side. Keep up the good work!
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…
It sounds like the unemployed programmers have an advantage over the employed, when interviewing at 0xide.
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).
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※.
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.
※ - 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!
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).
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
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.
> Being rejected after investing so much time must also feel awful.
I did an interview process that was 6 hours, one hour per week, then flew me in for a 6 hour on-site. They decided not to take me at that point and provided no reason.
Right...so best interview process in the game for employers, not so much employees.
Is it not good for exceptionally talented employees who want to work with other employees who are also great at their job and good communication skills?
No, because you lose access to a ton of employee's who value their time more than spending 9 hours repeating the same stuff over and over.
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.
At least you know what the time commitment is up front. Not true of every company.
I feel like this topic comes up every single time 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.
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.
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).
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.
different things are different
Nine hours is crazy
You work 2000 hours in a year. You ideally have an employer you like and stay with for many years. That's not worth 9 hours of your time?
That’s not how it works for the applicant. Many people are applying to nearly 100 roles a month.
Suppose you get interviews on 10% of those. That’s 10 interview pipelines, and if every company had this policy, 90 unpaid interviewing hours.
Like the comment elsewhere in this thread, candidates will find other roles before your interview gauntlet concludes.
> Many people are applying to nearly 100 roles a month.
Spotted your first problem. Don't shotgun apply to anyone and everyone. You should only be applying to jobs you actually want.
That’s not how it works. Interviews are like a funnel. If you don’t pass the first interview they don’t schedule you for all of the other hours just to keep going. You get dropped from the pipeline.
When a company says they have 9 hours of interview time, that’s usually the maximum time if you make it through all the rounds. If you get that far, you’re highly likely to get an offer.
You would also be surprised at how many people will actually do 10-20 long interview rounds to try to maximize their chances for the best job.
There are almost two different bubbles of candidates: Those who refuse to do anything more than a couple quick calls, and those who will rearrange their life to spend days putting in work for each job they want. I think that’s fine and everyone should do what works for them, but if you think 9 hours of interviewing is going to turn candidates away from a company like Oxide you’d be very surprised to see the quantity and caliber of applicants who line up for jobs like this.
I think you also might need to adjust your expectations now that AI interview cheating is getting out of control. A lot of companies are moving back to on-site interviews. I’d happily do 3 x 3 hour video calls more than flying and staying at hotels and renting cars to get to an office in another city just to interview.
Maybe Oxide isn’t aiming to hire people who apply to 100 roles per month.
Agree. Shotgunning 100 applications a month is not a strategy for finding a good job. It says "I don't care where I work, or what the job is, here's my generic resume, please just hire me." And maybe you're that desperate, but IMO you'll get better returns spending more time on fewer/better opportunities.
Not saying we are or aren't looking for that kind of candidate, but I _will_ say that we're very keen on the motivation to join Oxide at all, and the role you're applying for specifically.
You get worse biases by favoring people that don't value their time IMO. Not too mention it doesn't favor working people with other obligations that can't afford to give away an entire shift to interview for a job they might not get.
A hundred roles a month and call backs on 10% of them? That's A) and insane number of applications and B) a really high call back rate.
I'm on the market right now due to a layoff and I have an agent that reviews linkedin every morning and cross references levels.fyi for role leveling and salary and then assess fit to my resume. I get around 5-10 _possible_ positions per day and with human judgement that's usually down to 0-2, averaging about 0.5 per day.
I hear back from probably close to 10% but that's with a highly targeted approach, not just spamming my resume everywhere. And my pipeline is freaking full. It's a full time job doing prep and participating in all the interviews.
The only interview so far that's been a huge time sink has been anthropic's. But that's because I chose it. Their take home I have the option to use between 2 and 8 hours and I used the full 8 hours because I'm highly motivated and the position is well fit to my career history.
That's a loaded question. How about just saying it for what it is. Are you willing to spend 9 hours today (not counting the other interviews you have to do for other companies) for a X% probability of getting a job at company A which you like Y amount.
If X and Y are large enough sure. Most of the time X is hidden and Y is hard to gauge.
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.
No they don’t.
They waste very large amounts of candidate time on an essay like assignment before you get to talk to someone.
Truth be told they already know from your resume if you’d be worth interviewing. That’s enough , and maybe a OA.
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.
No need for me to write a long paper, when HR probably took one look at my resume and sent out a rejection.
A friend encouraged me to write the paper, even if I didn't submit it, as a means of self-reflecting.
Are we talking about the same thing.
I apply for jobs because I want money. Not to reflect or learn about myself.
It’s just business, even if you do the song and dance to get hired they can still fire you later.
Oxide's process involves submitting writing with various questions about you, what you've done, and what you're looking for in your career. The process of doing so inherently means reflecting on the answers to those questions, and so some people find it a useful exercise.
OK.
But that should be done later in the process. I'd rather an LLM auto-reject my application vs spending 5 hours on a writing exercise.
Think about, I apply to a minimum of 5 jobs per day. If I need to spend 5 hours for each application I'm spending 25 hours a day on job applications. Obviously this isn't possible.
I think that you are (naturally) approaching it from your side, and they're (naturally) approaching it from theirs, and it sounds like it's not a fit. That's a successful outcome for a hiring process.
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.
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?
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.
We're building racks over here! And all our software is open source.
Username checks out.
I’m serious I can’t tell what it is. Something with all the benefits of on prem and cloud without the costs of either.
Change "something" to "a computer" and you got it!
It's a big ass computer (technically many computers in a rack) that gives you a cloud provider style API to manage on-premises infrastructure. Plug it in, connect to the web console or API, and provision yourself some sweet sweet virtual machines, disks, and VPCs.
Data center in a box
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".
Oxide are so good at comms.
And yet that seems like a caption Bryan could have written…
Comms can mean outward communication even if it’s not done or filtered by a comms team. In the case of Oxide it almost certainly means that.
But maybe not great at finance?
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.
Maybe they're not trying to be great at the tax avoidance game.
> Why are they paying taxes
"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.
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.
Hah, well, I stand corrected. And also, huge congratulations on profitability!
As someone who has applied less than 6 weeks ago, this is great news. I can't wait to hear back!
The post is about how they don't have the capital to safely expand production capacity, which is why they're raising more.
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.
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.
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.
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.
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 slower. Being common is irrelevant.
Raising a Series D is an attempt to permanently increase the velocity of their enterprise. The change in the cap table is negligible if they succeed.
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.
Can you imagine if they raised $445M of debt?
They said they are profitable aside from funding purchase orders, they don't need capital to fund growth. If they said they raised in order to grow faster and that they were not profitable then I would agree with you.
blog mentions the use of debt facilities, there's a smart mix of both debt and equity
with agentic coding lock in @ AWS and Google Cloud is evaporating fast
a few days ago I migrated a non-trivial firestore app to sqlite
10x less latency (10x requests / second)
migration took a few minutes (+ 2 days of prep)
just a few months ago that would have been infeasible or at least nerve wracking
SQLite isn’t equivalent to something like aurora.
Maybe the most thoughtful fundraising announcement I’ve seen. Focusing on all the right stuff.
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.
FYI previous discussion of the series D https://news.ycombinator.com/item?id=49174407
Probably I'm blind.. is there any form of imprint on their page? An address?
I don't think so, located in Emeryville, California
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: https://youtu.be/n2ze5RCy3TM?t=928
Timestamped to "the differentiator" (15:45) and "what are you guys doing about GPU?".
we have an FAQ Friday on this: https://oxide.computer/faq-friday/what-is-oxides-thinking-ar...
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!
> 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!).
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.
if these guys just capture 1% of spend that's on AWS, Azure & Google Cloud they will still be very big.
Yes but is that likely?
We want out of AWS. HPE can't fill the gap now. These guys have a good chance of getting considered.
We're racking hardware right now to move off the cloud providers and but it's just a (small tens-of-millions-of-dollars) test run to start so we didn't want to complicate things by learning anything Oxide-specific, but they are certainly on the radar as the vendor for a larger rollout.
With the major issues with the big cloud providers these days as well as high costs, I’d say there’s a decent shot. Their investors certainly think so.
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.
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.
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.
you still need pure compute when doing the agentic ai dance.
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.
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.
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.
So ideally the dilution is neutral to the value of the equity. In practice this is highly variable because the valuations are fuzzy numbers used for the raise, but you get the idea.
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.
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.
As a thought experiment:
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.
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.
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
Your lottery comparison isn’t logical. I think you’re just repeating the same misunderstanding I was trying to dispel above.
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.
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.
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.
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.
That's the scenario I said, where they share any winnings from their tickets too. You still have the same expected value.
> You still have the same expected value.
Yes, which makes the lottery comparison moot.
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.
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.
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.
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.
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.
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.
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
They add greatly to your expected chance of winning, given you have pooled winnings.
So do additional investment rounds as they theoretically increase the viability of the company.
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.
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.
Printing more money doesn’t come with an increase in GDP or assets.
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.
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.
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.
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.
That's enough that they can drive down to Central Computers and grab a 32GB stick.
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: https://news.ycombinator.com/item?id=30678324
Server racks which are vertically integrated and provide great cooling, are quiet, and fully vertically integrated software (including bootloaders, hypervisor, etc. -- no BIOS!).
This includes everything from the rack itself to the PDU/switch/BMC, to the actual server blade and its chassis.
All presented in a nice package to give you a on-prem cloud-like experience.
And this is hosted in an Oxide datacenter or shipped to the customer?
shipped to the customer
you buy one or more of the data-centre-rack-sized computers, hook em up to each other / your datacentre network, and you now have essentially a cloud services platform like AWS/Azure, in your own datacentre, under your control, with full visibility of what every part of the platform is doing (hypervisor, underlying bare metal kernel, firmware, bootloader, etc), because it's ALL open source, written from the ground up by them
I think it's pretty neat!
Shipped - hence on-premises.
Shipped to the customer, we don't offer leased/managed hardware or VM instances.
I think this blog covers it pretty well:
https://oxide.computer/blog/the-cloud-computer
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.
Looks like a mainframe computer and their selling point is that the operating system is open source.
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.
Couldn't happen to a better bunch of people.
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.
may the Sun never set
- Series B in Jul 2025 $100M
- Series C in Feb 2026 $200M
- Series D now $445M
I expect the next round soon :)
One has to hope they're not actually burning through their money every 6 months, but I've been disappointed before
They just paid income tax?
You can still be heavily cash flow negative while being Net Income positive. It's actually one of the big use cases for VC money; you have a flywheel of revenue but not enough cash to pay to service that revenue and actually get cash.
Well they are not, but this is a startup that's actually buying/creating computer hardware and the most expensive and competitive time in history to source it.
The economics are going to look different than all the sloppified enterprise SaaS startups that charge crazy amounts for a crappy data lake product on S3.
Previously, they’ve stated that they raised merely to give customers confidence that they are in it for the long haul. You don’t want to buy racks from a company that won’t be around tomorrow. Raising money is likely being used to create a war chest, with some amount of it being used to grow the team and operations, to fill demand, and support their customers. Those functions have to grow sustainably, but the demand also signals to investors that it’s working, and continued investment is a good move.
In reality, it could very well be investors just saying “we’re so happy with how things are going, we want more, take our money!!!”
$445M is a lot of money.
A legit business? Raising legit money?? In this economy???
Wake me up please
september has ended so
I really wish they had a SOHO offering, would love to run this with NextCloud and personal projects from home.
Their entire control plan is open source and you can run it on commodity hardware: https://github.com/oxidecomputer/omicron/blob/main/docs/how-...
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.
Congrats to the Oxide team!
Is this the new IBM?
hopefully they are.
IBM is more than 100 years old and has brought us a lot of innovations of the modern era.
To give a trivial example the relational model for databases was theorized by F. Codd while working at IBM Research (see https://en.wikipedia.org/wiki/A_Relational_Model_of_Data_for... for further details)
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 mean IBM is an amazing company. And this oxide is also doing something very elegant.
I'm not sure about the pricing.
Congrats!
Always happy to see Oxide growing. The way their company is run is pretty close to how I think all engineering orgs should run.
Hoping they hire for a position in my area of expertise some day!
Excellent news! It's wonderful to see a great company succeeding.
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.
https://oxide.computer/contact
Exactly, no pricing page. Not worth my time to get involved in contract negotiation as a dev when all I want to know is if it's even feasible to try out.
this is a good point, and we make trial environments available for you to try here: https://oxide.computer/remote-access