Oxide Computer Interview Guide (2026): No Leetcode, Just Your Materials

Oxide Computer Company builds the Oxide Cloud Computer, a rack-scale machine that gives enterprises a cloud-style experience on their own premises: custom boards, no traditional BIOS, and an open-source software stack written largely in Rust (the Hubris embedded OS on service processors, the Omicron control plane, the Propolis hypervisor, Crucible storage). It was founded in 2019 in Emeryville, California by Bryan Cantrill (of DTrace fame), Steve Tuck, and Jessie Frazelle, and it has raised heavily as shipping racks turned into real revenue: a $44M Series A led by Eclipse in 2023, a $100M Series B led by Thomas Tull’s US Innovative Technology Fund in July 2025, and a $200M Series C announced in February 2026, bringing total funding to roughly $389M. The business shapes hiring directly: Oxide co-designs hardware and software with a small, senior, writing-heavy team, records its decisions in public RFD documents, and hires the same way it works, through written argument rather than performance under a whiteboard timer.

Process

The process is documented in the company’s own RFD 3, “Oxide Hiring Process,” and on the careers page, so less hedging is needed here than for most startups. You apply to a specific open role and submit your materials with the application. The materials are then read by multiple Oxide employees; the company says review takes roughly three to six weeks, and Cantrill has said publicly that they get far more qualified candidates than open seats, so most decisions end at this stage. If your materials show a fit, you move to one-on-one conversations with several members of the team: long, substantive discussions about your work and theirs, not quiz sessions. Earlier versions of RFD 3 described multi-hour blocks, though the format likely varies by role. One unusual courtesy: employees who talk with you share their own hiring materials with you, so you can read the answers your interviewers wrote when they applied. After the conversations, the team huddles, makes a decision, and tells you the outcome. End to end, plan for one to two months, dominated by the materials review queue rather than scheduling.

What they actually ask

• Eight written questions, published in RFD 3. Four are about your history: the work you found most challenging and why, the work you are most proud of, and when you were happiest and unhappiest in your career and why.
• Three values questions keyed to Oxide’s published values (rigor, candor, curiosity, empathy, humility, urgency, and others from RFD 2): describe a time a value showed up in your work, a time one was violated in an organization you were part of, and a time two values came into conflict and how you resolved it. The eighth question is simply why you want to work at Oxide.
• Work samples (one to three): for engineers, real source code you wrote, ideally something you can link and discuss line by line. Reviewers care about what the artifact says about your judgment, not its size.
• Analysis samples (one to three): a written debugging story or systems analysis, such as a postmortem of a pathological performance problem. This is where hard-won systems depth shows.
• Writing samples: design documents or technical writing that demonstrate you can reason on the page. Oxide runs on RFDs, so clear prose is a first-class engineering skill there.
• What reviewers look for: specificity, self-awareness, and alignment with the values, backed by evidence. Reports from candidates and from Oxide’s own podcast discussions suggest vague or generic answers are the most common reason materials fail.

Levels and comp (2026)

There are no levels, no ladders, and effectively no titles. As of mid-2026 the careers page states that everyone at Oxide makes $275,000 USD regardless of location, with the noted exception that some sales positions carry a lower base plus commission. The number has been raised repeatedly since founding: it was $180,250 in 2021 and $201,227 in the 2023 to 2024 range before reaching the current figure, and Cantrill laid out the reasoning in the blog post “Compensation as a Reflection of Values.” Everyone, including the founders, draws the same salary. Equity is part of offers, but the company does not publish grant details the way it publishes salary, and grants reportedly vary, so ask directly and do not assume equity is uniform. Benefits include fully covered medical, dental, and vision premiums for employees and dependents, and the company is remote-first, requiring at least four hours of overlap with Pacific time. There is no salary negotiation, so the only thing left to compete on is your materials.

Prep priorities

Put nearly all your prep into the materials. Budget several sessions over a week or two, and treat the eight questions like essays that will be read by skeptical senior engineers, because they will be. Be specific: name the project, the failure, the tradeoff, and what you actually did. Read RFD 1 (how Oxide works), RFD 2 (values), and RFD 3 (the process itself) before writing a word, and skim the public RFD archive plus a few Oxide and Friends podcast episodes so your “why Oxide” answer sounds like you know what the company actually does. Pick work samples you can defend under close reading, and write an analysis sample the way you would a great postmortem, the same muscle behind a strong system design narrative. You do not need to grind coding patterns for Oxide, but genuine systems depth matters: Rust, operating systems, firmware, networking, or distributed storage, depending on the role, and prior Rust experience helps though the team has said strong systems people can learn it. For the conversations, prep like a thoughtful behavioral round with much more technical meat: expect to go deep on anything you submitted, and come with real questions, since you will have read your interviewers’ materials too.

Frequently Asked Questions

Does Oxide do coding interviews or leetcode? No. There is no algorithmic screen and no whiteboard coding. Your submitted code and analysis samples replace live coding, and the conversations probe the work you actually did.

Do I need to know Rust to get hired? Not strictly. Nearly all of Oxide’s software is Rust, and demonstrated Rust work strengthens an application, but the team has repeatedly said it hires strong systems engineers who can pick it up. Show depth somewhere real: kernels, firmware, databases, networking.

Is the salary really identical for everyone? Yes, per the careers page: $275,000 USD for every employee regardless of location, with some sales roles on a lower base plus commission. Founders included. Equity is the one component that varies, so ask about it.

How long does the process take? Materials review alone is quoted at three to six weeks because multiple employees read every submission. With conversations and the final huddle, one to two months is a reasonable expectation, and openings are infrequent, so watch the careers page for roles that match you.