Oxide raises $200M Series C(oxide.computer) |
Oxide raises $200M Series C(oxide.computer) |
> "So if we didn’t need to raise, why seek the capital? Well, we weren’t seeking it, really. But our investors, seeing the business take off, were eager to support it."
From this of course the VCs will back and support Oxide (they are mentally thinking that Oxide will move into supplying hardware for AI datacenters) eventually want their money back at many many multiples and the pressure is there to achieve this.
Can you even invest in Oxide?
I just wish Oxide wouldn't have to keep getting owned by VCs which would inevitably lead to enshittification to pay back the VCs.
If Oxide followed the model of Valve (100% founder and employee ownership, profitable, vast unlikelihood of enshittification or pressure to get acquired or IPO) then it would be a different situation.
I predict in less than 10 years Oxide exits by way of being acquired or an IPO. The enshittification would have already begun by then.
> You seem very sure of yourself in how business works! I'm curious now, how did you create your $100MM++ revenue hardware business? I'd love to learn from you. [deleted]
You don't need to create a $100MM++ revenue hardware business to know how this ends when you get into bed too many times with VCs.
We already know it is a huge capex spend (which is why they keep going to VCs) the question is, how many times does Oxide need to go back to VCs to keep raising (even though they said they didn't need to raise?)
I hope they become immensely profitable enough to buy out the VCs stakes and get control back and become independent.
But I am doubtful that Oxide will do that if they keep raising and they will just be sold down the river in less than 10 years.
How long until Oxide needs $2BN, $4BN or $8BN from VCs, further getting owned by them?
Amount of developers touching a specific piece of hardware is mostly unrelated to business success.
The real question is, are there big company with lots of money that buy your product.
And what are you offering and why are you offering it?
Who do you think will own whatever you're offering after you go public?
Are you hoping your VCs (or you) won't sell whatever your offering when an IPO happens?
They do both as they need many multiples to return the fund.
And it also sounds very predatory to me and not aligning with any startup's mission other than for the VCs to pressure Oxide to get acquired for over $20BN+ or go to the public markets.
Not even Hetzner did this. DigitalOcean could have followed Hetzner, but I guess VC money is very attractive and now DigitalOcean is now the slave of Wall St.
Going into deals with VCs and IPO'ing to Wall St. always leads to enshittification.
You and me both. They're doing neat stuff, but I wonder how many other potential customers feel that way too.
What is Oxide's market? It feels a bit like advanced alien technology that is ultimately a little too weird and expensive for most enterprises to adopt.
Happy to see their success. Especially so if you've been following their journey through their podcasts (easily the best tech podcast out there if you care about your craft; no filler, all killer).
This isn't the worst though, I recently went through an interview with another startup company, and after six interviews and a take-home project I found myself getting the same generic rejection. The CEO went out of his way to tell me he didn't like my resume since I've had to hop around a little bit to stay employed.
Concerns that should have been handled in the initial call, somehow get pushed back till after I've wasted monumental amount of time.
Things are looking up though, I'm starting a job soon and the entire interview process was more or less a 30 minute phone call with the technical manager. That's it, two days later or so I had a verbal offer. I don't need to change the world, I need to pay my rent.
The short stints on a resume is likely not the only reason you didn’t get to 100%, but unfortunately you should know that it’s seen as a pretty bad signal. The general expectation is 2 years minimum at a gig. If you have multiple short non-contract jobs it raises the concern that a candidate doesn’t commit to their jobs, or that they don’t do well at their jobs and are getting let go.
As they say, you can't get blood from a turnip.
Writing this comment reminded me of a personal experience, story time:
Many moons ago I interviewed at a mature startup in silicon valley, they shipped a tiered storage appliance and were in the process of pivoting to a new storage medium (think transitioning from spinning rust to SSDs, something like that).
This was in-person, and everything went swimmingly well, before departing they stated an intention to make an offer and I should expect an email w/offer attached within a week. I got an offer letter, and accepted immediately, as I was super excited about the stack I'd be playing with.
A week before the start date I get a call from a founder, they said I couldn't start because their funding round didn't come through. The economy was going through some sort of financial crisis and it was one of the many blood baths where silicon valley startups shuttered by the hundreds overnight. So in essence, this was a job I got fired from before I could even start, wee!
What followed was a pretty frustrating few months of interviewing and not getting anywhere.
But there is a silver lining to this story, that founder who called me sat on the board of other storage startups. One of them managed to get some water in this funding desert, and its founders reached out to me at his recommendation. I ended up building some great stuff over 4-5 years at that company.
Honestly these "reasons" they give are usually BS excuses when it basically amounts to they don't like your personality or looks.
The real reason might be “they didn’t like your vibes” or something like that
The original On The Metal podcast they did is incredible too. The interviews they had with computing legends are just fantastic.
I have this horrible "completionist" tendency and I got stuck on a 2021 episode where the audio needed post-processing and I just never got around to it.
I loved On the Metal and it was a bummer to fall behind on the new show.
I would try to apply but as far as I know they require 4 hours overlap with PST which excludes Europe
Wouldn't that depend less on where you are and more about your sleeping schedule? I generally go to bed around 04:00Z, up around 11:30Z sometime, seems that would work regardless of location, no?
The topics were good. The guests were great.
But Bryan Cantrill was just terrible at letting his guests actually talk.
Bryan, if you’re listening, please let your guests talk. We have a large amount of content on YouTube if we want to hear the Bryan Cantrill take on, well, anything and everything. And it’s often amusing and sometimes right.
People don’t tune in to a podcast with guests to hear the host pontificate. They tune in to hear the guest, and sometimes the guest/host dynamic. When the host talks over the guest, you don’t get either.
After the Jonathon Blow episode, I gave up. Dude had interesting things to say about C, C++, and Rust, but most of what we got was Bryan talking about Rust. I guarantee anyone tuning into the Oxide podcast knows Bryan Cantrill’s opinions about Rust. And firmware. And Oracle. And Linux. Etc. etc.
Let your guests talk.
I do try to get better at this stuff, and I re-listen to our episodes to improve as an interviewer. If it's been "a few years", maybe you haven't listen too much to Oxide and Friends? I think we've had some wonderful guests and great conversations over the span of the podcast -- though I also have no doubt that it's imperfect, for which you have my profound apologies!
And Jonathon Blow manages to talk enough ...
This is good news for them. I expect there will be more competition for positions there should any open up.
That said I like Bryan Cantrill as an engineer and leader, but I would never put him on a pedestal.
Listen to the words, don't follow "personalities", don't listen to specific individuals just because of their status. Not a single time have I been disappointed by an idol, because I've made the conscious choice of not having following any. Bunch of smart people say smart stuff all the time, until they don't. I read everything as if I don't know the author, I think more people should do this and less celebrity worship would make the entire ecosystem better. We need less of it, not more.
I am an undergraduate right now and looking at the people working there, it doesn't seem likely they would hire a fresh grad, I think I have found the yardstick I am going to measure myself by going forward, "Am I skilled enough that I could work at Oxide?". Hope more companies follow suit in putting the people forward!!
Anyway, I'm glad to hear of the raise because the team seems exceptional (judging by the posts you guys write and they have written prior to the company) and I love work in this area that simplifies hardware management. Good stuff, good luck, and congratulations!
have my expectations been shot by reading too much about Nvidia's latest and greatest, or does this seem quite low?
Step 1 could be to get Illumos running on a local x86-64 machine.
Their hardware is multiple generations behind at this point, however. I wonder if they’re starting to reduce the price because it’s hard to justify paying so much for old hardware. They could just be targeting customers who don’t care as much about performance or efficiency as they do the software stack.
I’m guessing for their current target market of existing enterprise software it doesn’t matter, but the ownership and economics stories are at least as compelling for matmul code.
Watch the QA.
Basically, they Nvidia ecosystem is to closed for them to add value. And competing with Nvidia is difficult so its not their focus.
What to do with so much money?
An AI product is of course the 'no-brainer', I would love to see them partner with Tenstorrent for the CPU/AI part. I think Bryan described this as Door 3 'doing something crazy'.
A product around AMD APU was talked about, but in a recent talk Brain said AMD doesn't seem to care about that product.
OpenTitan is now getting ready for production uses, maybe makes sense to switch to that in the future. Moving Hubris onto that shouldn't be to big of a lift.
A conventional server without DC bus bar maybe? Not talking about homelab server but something in a class where you can't have a whole rack and the bus bar. The main seller would be the fireware and software ontop to get people into the control plane ecosystem. And you could make Linux boot on it too for more market reach potentially. I'm not sure how much such a platform could share with current system.
An SSD or NIC with open fireware would be great, but not sure if you can develop that only for your own product or if you would want to sell it separatly to make sense. But that would be big departure from the current All-in-One product.
Amazing what you can do when all you try to do is make podcast. Maybe now they have money to bring back 'On the Metal'. I enjoyed the more structured interview style podcast about history of computing quite a bit. That said the more discussion oriented 'Oxide and Friends' is also nice.
Like do they sell a service or a product. Do they sell hardware, software or something else? it is very confusing.
Compute Sleds (Total) 16, 24, or 32
CPU Cores 1024–2048
Memory (DRAM) 8–32 TiB
Storage 465.75–931.5 TiB
Network Switches 2
Switching Capacity 12.8 Tbit/s
Power Shelves Up to 2
Power Supplies per Shelf 6 (5+1 or 3+3)
Typical / Max Power Draw 12 / 15 kW
Dimensions H × W × D 2354mm (92.7”) × 600mm (23.7”) × 1060mm (41.8”)
Weight Up to ~2,518 lbs (~1,145 kg)
Max Thermal Output 61,416 BTU/hr
Airflow Requirements 145.8 × kVA CFM
Disclaimer: I work at Oxide.
Total chaos.
For an organization that has definite goals and have to ship a product by a deadline, a flat structure can surely be detrimental to any progress. In an environment of competition (from outsiders) and scarcity, a flat structure will only create either chaos or an implicit form of hierarchy that is even more cruel than what should have been.
Oxide seem to be the best and most thorough in their space because they have chosen to own the stack from the firmware upwards. For someone who cares in that dimension they are a clear leader already on that basis alone, for other buyers who don’t, hopefully it also makes their product superior to use as well.
Oxide is a really nice platform. I keep trying to manipulate things at work to justify the buy in (I really want to play wiht their stuff), but they aren't going for it.
Didn't companies historically own their own compute? And then started offloading to so-called cloud providers? I thought this was a cost-cutting measure/entry/temporary solution.
Or is this targeting a scale well beyond the typical HPC cluster (few dozen to few hundred nodes)? I ask because those are found in most engineering companies as far as I know (that do serious numerical work) as well as labs or universities (that can't afford the engineers and technicians companies can).
Also, what is the meaning of calling an on-prem machine "cloud" anymore? I thought the whole point of the cloud was that the hardware had been abstracted (and moved) away and you just got resources on demand over the network. Basically I don't understand what they're selling if it's not what people already call clusters. And then if the machine is designed, set up and maintained by a third party, why even go through the hassle of hosting it physically, and not rent out the compute?
I don't know if it's true or not but it seems like our AWS bill is something like paying the full purchase price of the underlying hardware every month.
For the business guys they're focusing on price and sovereignty. Owning your business. For technical people they are focusing on quality. Not having to deal with integration bugs.
IIRC, Bryan Cantrill has compared the value proposition of an Oxide (rack?) to an IBM AS/400.
All I need is some financial backers and I'll happily document the whole thing on a blog and a youtube channel. Now accepting offers.
If you idea of installing a server is "terraform", you're not going to get it.
Traditional hosting still, to some extend, struggle to provide the API, on demand, drive requirements for modern developers, who expect to be able stand up a bunch of virtual machines in a minute or so, especially if you also want a new private network, maybe some IPs and storage pools.
Having a single provider for your entire stack, software, hardware and network avoids the annoying back and forth with vendors, blaming each other. Having just one support contract for your entire stack is a pretty large plus.
If you don't like vSphere (who does?) you can do all that in Proxmox.
https://newsletter.pragmaticengineer.com/p/the-history-of-se...
There is some company who for reason X and Y rather (or are obligated to) do on-prem for their hosting needs. But setting up a full (or several) racks, with all the required equipment for proper networking, storage, etc, can be quite the hassle. And if you want cloud-like functionality (completely API manageable virtual network, VM, storage pools, ...) it's another can of worm. Having a "plug'n'play" cloud-like system on-prem that do not require several engineers who know 10's of different vendors tech is definitely worth the premium for those company.
API driven, have "elastic resources", etc, etc. Rather than bolting together various solutions you get to have a "Cloud-like" stack in your own datacenter.
Slightly less pithy: they're selling rack-scale systems, with power, hardware, network, and control plane software all integrated. Something that presents to the user as something more like API to interact with than a pile of servers to be managed.
It’s a step higher than a vSphere/Proxmox cluster.
They also need to grow and iterate faster. Their software stack is great, but their hardware is quite dated in a fast moving industry. This limits them to domains that value their software and security but don’t need the latest hardware for performance and aren’t necessarily concerned with performance per dollar, which is a small market.
> ...it's not uncommon for us to be asked directly: "How do I know you won’t be bought?"
Raising ~infinite runway from investors who are already known quantities signals that you can safely buy into their product knowing they're not getting snapped up by $megacorp anytime soon. That's where the faster growth comes from--customers who feel secure in the knowledge that the company isn't going anywhere.
We can hope that this is the case for Oxide, though I don’t expect they are reliably profitable yet.
People with deep pockets and good reasons to want to keep certain parts of their infra very close to home. Also the kind of people that expect very highly skilled people to show up and get their in-house app running.
(I was an SGI HPC customer once. I still miss the old SGI. Sigh.)
No it’s not. Normally if you’re buying server hardware you don’t start with a CPU that’s already 5 years old and last-generation RAM that isn’t even manufactured at scale any more.
CPUs have advanced a lot in recent years. The jump from Zen 3 to Zen 5 is very substantial.
As group-of-cats racks, usually, which is a totally different thing. Way "back in the day" you'd have an IT closet with a bunch of individually hand-managed servers running your infrastructure, and then if you were selling really oldschool software, your customers would all have these too, and you'd have some badly made remote access solution but a lot of the time your IT Person would call the customer's IT Person and they'd hash things out.
Way, way, way back in the day you'd have a leased mainframe or minicomputer and any concerns would be handled by the support tech.
> I thought the whole point of the cloud was that the hardware had been abstracted (and moved) away and you just got resources on demand over the network.
This idea does that, but in an appliance box that you own.
> And then if the machine is designed, set up and maintained by a third party, why even go through the hassle of hosting it physically, and not rent out the compute?
The system is designed by a third party to be trivially set up and maintained by the customer, that's where the differentiation lies.
In the moderately oldschool way: pallets of computers arrive, maybe separate pallets of SAN hosts arrive, pallets of switches and routers arrive. You have to unbox, rack, wire, and provision them, configure the switches, integrate everything. If your system gets big enough you have to build an engineering team to deal with all kinds of nasty problems - networking, SAN/storage, and so on.
In the other really oldschool way: An opaque box with a wizard arrives and sometimes you call the wizard.
In this model: you buy a Fancy Box, but there's no wizard. You turn on the Fancy Box and log into the Deploy a Container Portal and deploy containers. Ideally, and supposedly, you never have to worry about anything else unless the Big Status Light turns red and you get a notification saying "please replace Disk 11.2 for me." So it's a totally different model.
Historically, companies got their compute needs supplied by mainframe vendors like IBM and others. The gear might have sat on premises in a computer room/data center, but they didn't really own it in any real sense.
> Basically I don't understand what they're selling if it's not what people already call clusters.
Is it really a cluster when the whole machine is an integrated rack and workloads are automatically migrated within the rack so that any impending failure doesn't disrupt operation? That's a lot closer to a single node.
[0] https://www.crassh.cam.ac.uk/wp-content/uploads/2025/01/Free...
[1] en.wikipedia.org/wiki/The_Cathedral_and_the_Bazaar
I don't think the Tyranny of Structurelessness is arguing in favour of hierarchy, or against other forms of organization than hierarchy.
I don't think it's arguing against "flat" or "anarchy" style organizations either.
In essence, I think it's asking us to do whatever we're doing better, more honestly, more effectively, and less stressfully. By acknowledging, clarifying, communicating, and seeking to understand the real operating structures, what's really going on. And then to improve them, using that understanding.
An actually flat organization might be good, I don't know. I've never seen one. I've been in some that claimed to be flat, and became stressful places to work, for the same usual reasons hierarchies can be unpleasant, including incompetent bosses (not called bosses). But I've also had some pleasant experiences in flat organizations, and I prefer it that way, if it's designed and run well.
In the non-hierarchical family you aren't just ordered to dress up and go see grandma, you're guilt tripped into feeling bad about not seeing grandma, until you do it out of "your own volition". In the non-hierarchy you're not just supposed to be outwardly obedient but free on the inside, you're supposed to be obedient on the inside too. They work well, really well. Unlike the traditional hierarchy the tyranny is absolute because it has no borders and doesn't have to acknowledge itself.
>However the problems with traditional hierarchies are so well known
exactly, because they're visible. Valve, despite its utopian conditions, is weirdly enough, very secretive
See perhaps Le Guin's novel:
I don't lie to myself, I know why I do this.
https://en.wikipedia.org/wiki/T%C3%A9l%C3%A9coms_Sans_Fronti...
Databases, K/V stores, crawlers, services, etc all still necessary besides GPU's. The closer to GPU's the better and if you have GPU's in your own DC.
https://www.nvidia.com/en-us/data-center/gb200-nvl72/ https://www.amd.com/en/blogs/2025/amd-delivering-open-rack-s...
It wasn't just the Jonathon Blow episode; that was just the point where I said "this is frustrating." For what it's worth, frustration came from knowing that this could be really good: your perspective is valuable, your topics were interesting, and your guests were excellent.
I find this a common mistake that people with strong opinions have when doing interview/guest style podcasts or shows. There's really an art to it; it's not easy to engage guests, keep the show interesting, and let the talk move in interesting ways. That's why Terry Gross and Howard Stern, in very different ways, have had such long and storied careers.
But it's something that people definitely get better at, and I have no doubt that you have. Again, I'll give it another listen.
From the inside, is Oxide a place where a fresh grad can actually be useful? Or is the "complexity floor" of hardware/software co-design so high that you really just need a few decades of experience to be effective? I'd love a reality check on whether I should keep Oxide as a long-term 10-year goal or if there’s a path for people starting out.
> From the inside, is Oxide a place where a fresh grad can actually be useful? Or is the "complexity floor" of hardware/software co-design so high that you really just need a few decades of experience to be effective?
I believe Bryan spoke about this publicly on podcast episodes in the past but the answer really is no and yes. Generally, the things we're working on at Oxide require a both depth and breadth of knowledge in various areas of the stack that early career folks don't yet possess. We also have limited bandwidth to assist early career folks because of our small company size. I know this sounds like gate keeping, but mostly everyone at Oxide wants to support early career folks. Unfortunately, the general consensus has been that we just don't have the bandwidth for it and it would be a disservice to a candidate to hire them and not support them the way they would need to be supported. That being said, we're getting bigger and will likely have more bandwidth to change this stance as time passes. If you see a role you'd be a good fit for I do recommend applying. The application process itself is valuable for the applicant.
Any evidence or proof? This can be said about anything, even about your comment.
Nobody is flawless and part of becoming an adult is learning to admire specific qualities rather than obsess over individuals.
One dichotomy categorisation I personally look for in people is: * likes heirachy versus * dislikes heirachy.
I suspect heroes are mostly relevant if you are a heirachy lover? I also believe that heirachy lovers are more likely to believe in evil puppetmaster conspiracies (anti-heroes if you will).
It is a lot harder to find heroes if you dislike authority because your heroes are more likely to avoid heirachical status ladders?
It's a contractor life for me, I work for money, not "purpose" or anything else.
Hell my Facebook (technically a fully owned subsidiary to be fair) interview loop was easier. I didn't get the job that time either, but at least it was straight up.
In previous HN threads they said something to the effect that they expect their applicants to have read what’s online about their equal base salary. Equity is not equally applied though.
Hopefully raising money helps them iterate faster on their hardware so they’re not so far behind.
Looking forward to the discounted DDR3 Opteron-based option.
> if they had gone with DDR5 it would have doubled
They charge a premium for their hardware due to the software. They have plenty of room for RAM price fluctuations. It would nowhere near double the price.
> Looking forward to the discounted DDR3 Opteron-based option.
I know you’re joking, but anything DDR3 based is really slow and power inefficient relative to current gen hardware.
SCOTUS has found non-protected categories can still be protected because they are "proxies" for protected categories. One of the classic examples of this are zip codes[0], which was found to be a proxy for race, because it has a "disparate impact" on people of particular races.
For some people, the 'wrong vibes' are often proxies for cultural things - all kinds of body language contribute to vibes and it's easy to accidentally (or on purpose...) discriminate against a whole categories based on vibes. If you tell a candidate "Hey we just didn't like your vibes as much as this other guy", it could affect your exposure to claims that you discriminated against them based on their race.
0: https://en.wikipedia.org/wiki/Texas_Department_of_Housing_an....
This was probably wrong, both in terms of interpreting the existing law and as a statement of what the law should be. Sometimes bad facts correlate with race; that should not be a reason to deny using the measure for e.g. hiring or lending.
I realise it may be somewhat beside your point, but that was a Kennedy+liberals vs conservatives ruling in 2015 - so the current SCOTUS would likely have ruled the other way, and decent odds they overrule it sooner or later. Scalia’s dissent was objecting to the entire idea of disparate impact analysis under the Fair Housing Act, so more likely that gets overruled than this specific application of that idea.
This was a statutory interpretation case though, so if SCOTUS overturns the decision, Congress could reverse that with ordinary legislation, no constitutional amendment required. But who knows whether that will turn out to be politically feasible.
https://en.wikipedia.org/wiki/Texas_Department_of_Housing_an...
(Also, you need to change the last period in the URL to %2E to stop HN from mangling it.)
I've heard Bryan and Co. call it a "mainframe for Zoomers," but it's much closer to what Nutanix or VxRail is/was doing than it is to an AS/400.
The result is a system that can handle years of operation with no downtime. The platform got very popular with huge retailers for this reason.
Then in later years the platform got the ability to run Linux or Windows VMs, so that they could benefit from the reliability features.
Given this, can you help me understand in what ways they are different?
When I went to the Nutanix website yesterday, the link showed that'd I'd previously visited them (not a surprise, I look up lots of things I see mentioned in discussions) but their website does an extremely poor job of explaining their business to someone who lacks foundational understanding, even once I'd started reading about "hyperconverged" just before.
Also check this out: https://www.linkedin.com/posts/bryan-cantrill-b6a1_unbeknown...
If you need a basic "vm platform", VMware, Proxmox, Nutanix, etc. all fit the bill with varying levels of feature and cost. Nutanix has also been making some fairly solid kubernetes plays, which is nice on hyperconverged infrastructure.
Then if you need a container platform, you go the opposite direction - Kubernetes/OpenShift and run your VMs from your container platform instead of running your containers from your VM platform.
As far as "hyperconverged"...
"Traditionally" with something like VMware, you ran a 3-tier infrastructure: compute, a storage array, and network switching. If you needed to expand compute, you just threw in another 1U-4U on the shelf. Then you wire it up to the switch, provision the network to it, provision the storage, add it to the cluster, etc. This model has some limitations but it scales fairly well with mid-level performance. Those storage arrays can be expensive though!
As far as "hyperconverged", you get bigger boxes with better integration. One-click firmware upgrades for the hardware fleet, if desired. Add a node, it gets discovered, automatically provisions to the rest of the configuration options you've set. The network switching fabric is built into the box, as is the storage. This model brings everything local (with a certain amount of local redundancy in the hardware itself), which makes many workloads blazing fast. You may still on occasion need to connect to massive storage arrays somewhere if you have very large datasets, but it really depends on the application workloads your organization runs. Hyperconverged doesn't scale compute as cheaply, but in return you get much faster performance.
Here is an answer by steveklabnik about this topic.
If the answer is no, then you might own the hardware on paper, but you don't control any of the software that makes said hardware useful.
If the answer is yes, on the other hand, then one must ask who is paying for those updates, because that can't be sustainable.
Two points about your last point. First, software improvements benefit all customers; as the business grows, the effective cost per customer shrinks. Also, most customers grow their Oxide deployment or will replace hardware after a depreciation cycle. The sustainability of investments into the software (and the product generally) is on solid ground.
Right now you're growing fast and swimming in VC money, so this is probably not an issue. At some point, though, you might find that even hardware depreciation cycles don't provide as much of a cushion as you hope they will. In an economic downturn, people might suddenly realize that Oxide hardware actually remains serviceable much longer than they expected. :)
what proprietary software stack? they just publish it all on https://github.com/oxidecomputer/ .
Company A got their funding pulled and shut down. Company B, where I was actually at for about a year and a half, switched owners and shutdown my entire office. Company C merged into it's main competitor and effectively fired most of us.
I will admit I was at one fantastic job and after around 3 years I probably could of stayed indefinitely. But back then I didn't recognize the value of a solid job. If you land somewhere and you're well liked by people, and able to do quality work, you really should just stay there instead of chasing slightly more money.
He wasn't my manager so I brushed over it and 6 months into working at DO they started 3 rounds of enormous layoffs that were handled so poorly even the executives doing the layoffs got removed by the board.
So I left and got to add another short stint at a company run by craven morons to my resume :)
That said, the general lack of emapthy from recruiting towards time invested and rejections is astonishing and seemingly cruel or emotionally negligent.
US corps are constrained I think by what they can reveal about denial reasons because they don't want to get sued for discrimination.
That said, it can often feel like, you were kept in the pool as an alt/negotiating foil if they didn't get their first pick, or needed to say "we have another candidate willing to take $YOUR_ASK-$BIG_DELTA.
I think we should approach the hiring gauntlet not as "workshop to see what it's like to work with these folks" but as "battle where we can divine the worst about the people we might choose to work with", but still remain sunny and positive while cannily noting any weirdness.
Hope that helps! :)
I don't feel disrespected or anything, just feels weird to spend that much time interviewing someone.
---
Sure, but one would think then the rejection email would have specifics around the interview and where the candidate did not perform well. Not nit picking on the job hops. If job hops were a deal breaker then why waste the candidate's time putting them through full rounds of interviews?
i'm sympathetic to you, it sucks, why cant we all be nice to each other, and my answer to that all is lawyers.
A little while later, the same company reached out and encouraged him to apply again. Five rounds later, and he got passed over a second time.
Fast forward two years and they reached out to him a third time. He's basically convinced that because he's black he's their token DEI interview candidate to make them feel better about themselves while internally promoting the people they actually want, but of course they wouldn't actually say that.
Takes time away from the day job and other candidates.
That sounds like it was a terrible place, but it was a good department in a somewhat hard nosed company. He ended up staying there 10 years.
Certainly we have lots of horrible inefficiencies in my team, but stringing along hiring was not one of them. I understand this is not universal even at our company.
There are plenty of great orgs out there that will soak with you before making assumptions, but as a rule most startups have fairly inexperienced management unless they are founded by a team that’s been through the rodeo a few times.
Oxide just recently talked about that actually the LLM people do want to buy Oxide. Because turns out, doing everything around LLMs also requires compute, and quite a lot of it. And when you already have to deal with massive issues to run a complex advanced Nvidia stack you might not also want to worry about what firmware bugs Supermicro is delivering.
If you are not one of the hyperscaler who already has all the CPU based infrastructure on their own cloud stack (google, amazon, facebook) then Oxide is quite interesting.
Also as for this shrinking/small market claim. About 50% of IT spend is still outside of the cloud. While nobody know the real number, its still a gigantic market, much bigger then most people realize. And it might not be shrinking because the bad economics of cloud are becoming increasingly clear to many company. Along with other trends such as making computing more local, not letting US companies control everything.
> You are like a fancier version of Dell or Supermicro.
Dell has a market cap of 80 billion $, Supermicro has 20 billion $. Must really suck to be them I guess. I'm sure Michael Dell wishes he had done something worthwhile with his live instead. I mean he could have worked for Digital Equipment Cooperation instead then he might not have ended up being such a loser.
I feel you are being really dismissive talking as if aiming for that is somehow not worth doing.
For a startup, if the thesis is to take market share away from those two, it's actually not such a good story. You need a product that is 10x better than the competition, and I'm not convinced that the enhancements to firmware, reliability etc. amount to a 10x jump in business value prop. You aren't making silicon. You are still ultimately a purveyor of other people's IP.
Maybe if people that bought Dell had a deep love for Dell products and were deeply integrated unable to move, but even then 10x is a waste exaggeration.
But if you have any serious academic literature that underlies this 10x claim I'm happy to take a look.
> You aren't making silicon. You are still ultimately a purveyor of other people's IP.
And neither does Dell and they are worth 80 billion $. And AMD doesn't make semiconductors, so they relay on other people IP. And TSMC doesn't make their lithographic machines or many other things, relaying on other people's IP. And all those materials relay on other people IP to be brought to market in the first place.
This is just a silly argument that for some reason puts CPU design companies as 'the real deal' and everybody else is somehow not good enough.
Historically good systems companies make just as good margin as most CPU design companies, specially those that don't have near monopolies.
> it's actually not such a good story
They are making inroads in a market that is 100s of billion $ large and people invested 300M$+ in them because they see costumer demand. If that's not good enough for you then I don't know what to tell you. I wish any of the starups I have worked at that kind of opportunity.
It seems to me you operate in a sense where anybody that doesn't go for a monopoly in a 5 trillion $ market is somehow not 'worthy' of being a startup. That just a very strange perspective on reality.
Yes, cloud is huge, etc. But there's a very big iceberg of on-prem.
I could get a spot in a colo, drop 2 fibers assigned to a few subnets, and be up and replicating our databases in a day or two. We have no need for GPU right now, but do need to often switch DB's to add cpu, ram, etc. Honestly, it would pay off in a year to 18 months, depending on the rumored prices, and colo costs.
There's a lot of stuff that even if you put majority in the cloud, you want local deployment for security (inc. "operate when internet is out" security/reliability) and latency reasons.
For various reasons, vmware was pretty strong contender in this. Oxide racks are comparable in "sanity of mind" in deployments, and last time I was in a company that could use that the only major breaker was lack of ability to ship a raw VLAN to a VM, to enable direct replacement of existing vmware stack. But if it's not already fixed, it is not particularly hard to fix.
And Oxide sells a complete hardware + software solution, including virtualization and SDN - essentially it's a physical equivalent of up to 32 node virtualization cluster per rack, with builtin SDN and SD-SAN, that already has features to combine for more.
Brian is trying to recreate Sun and using investor money to do so.
Good luck to them but I can't see it ending well.
- The Firefox browser on my Android tablet is close enough to a desktop one that I have no problem reading your blog post. The nag feels unnecessary, especially given it obscures part of the header. For what it’s worth, the tablet’s screen is 1600 real pixels wide @ 260 ppi, and Firefox for Android tells the CSS that the viewport is 800 “pixels” wide—if “pixels” were 1/96", then it would be somewhat below 600 “pixels”, so I don’t know where it’s getting that value from.
(And now I can’t stop thinking if I could make a thing in CSS that would look like a plain-text RFC on a desktop screen but gracefully reflow on a narrower screen.)
- The lightweight-markup parser seems to have gotten confused around the phrases “tests and whiteboarding” and “why I wasn’t a fit”.
- The HN link at the end doesn’t work (404) because you’re adding &ref=blog.webb.page to every external link and HN doesn’t appreciate extra parameters (from my earlier encounters with this kind of thing, neither does e.g. Wikipedia).
I made the screen size nag flush with the header. It's set to appear at 800px and below because that's when the design starts breaking. I don't have any Android devices to test what you're seeing unfortunately. A graceful reflow would be ideal! I'm sure it's possible but I don't have the energy to figure that out.
Because of the manual nature of the RFC-style formatting, Markdown doesn't wrap lines so I have to make those checks...I have a lot of posts so some fell through the cracks.
Thank you for taking the time to let me know about these bugs, I'll check 'em out!
They do now have "datacenter" single pane of glass interface, but a) it's very new b) no idea how the integration between different Proxmox VE clusters compares to integration between VMware clusters.