Oxide's Sample-Driven Hiring for Balanced Engineers
Oxide assesses candidates via detailed work, writing, and analysis samples before interviews to evaluate aptitude, motivation, values, and the balance of collaboration and independence essential for integrated hardware-software systems.
Why Samples Trump Traditional Interviews
Oxide's hiring process stems from the challenge of building integrated hardware-software systems, requiring hires who balance intellectual puzzle-solving with collaboration, persuasion, humility, and realism. Traditional in-person interviews risk favoring surface traits, so Oxide insists on early, substantive evaluation through candidates' own creations. "The ultimate measure of us all is in the work we do," writes Bryan Cantrill, emphasizing self-directed output over oral exams. This front-loads assessment, disqualifying mismatches before interviews and ensuring hires share Oxide's mission of rethinking server-side computing.
Candidates submit 2-3 work samples (e.g., code/schematics for engineers, customer engagements for sales), writing samples (e.g., design docs, meeting summaries), and analysis samples (e.g., debugging reports, process improvements). Optional additions like presentation videos reveal teaching ability and Q&A handling. These reveal raw aptitude without performance pressure, contrasting rote algorithm quizzes that poorly predict production system design.
Balancing Traits Beyond Raw Smarts
Aptitude alone fails; Oxide evaluates education, motivation, values, and integrity via structured written responses. Formal education prioritizes completion over prestige—"the strongest candidate from a little-known school... is almost assuredly stronger than the weakest from a well-known school." Unconventional paths demand stronger artifacts. Informal education probes self-driven learning: "What is an example of something that you learned that was a struggle for you?"
Motivation ties to Oxide's clear mission; career arcs must show intrinsic drive for complex systems problems. "Why do you want to work for Oxide?" expects mission-aligned answers, not superficial appeal. Values match Oxide's list (Candor, Humor, Teamwork, Courage, Optimism, Thriftiness, Curiosity, Resilience, Transparency, Diversity, Responsibility, Urgency, Empathy, Rigor, Versatility) through stories of pride/happiness, violations, and tensions (e.g., Urgency vs. Rigor). Integrity relies on references from trusted circles, as bad actors can devastate trust-based cultures.
Quote: "They must be arrogant enough to see the world as it isn’t, but humble enough to accept the world as it is." (Bryan Cantrill, describing the paradoxical balance engineers need, highlighting why nuanced assessment beats archetypes.)
Rigorous Mechanics for Peer Parity
Every candidate submits identical materials: 1-3 each of work/analysis samples, writing/other per domain, plus answers to 8 reflective questions (e.g., proudest work, happiest/unhappiest moments, values examples). Evaluation per RFD 147 forms the bulk, with narrative reviews flagging issues. Strong submissions advance; even well-regarded referrals fail on weak materials.
Interviews (9 hours over 3 blocks) follow RFD access for transparency—many withdraw post-review. Interviewers review candidate materials and share theirs beforehand, fostering peer conversations. Pre-meetings coordinate on open questions from reviews. This reciprocity, suggested by an early employee, transforms interviews into mutual evaluations.
Quote: "In addition to interviewers reading a candidate’s materials, candidates are offered the interviewers' materials in advance... the conversation much more closely approximates a conversation between future peers." (On the innovative materials exchange, which levels the process and reveals character through Q&A in presentations.)
Tradeoffs are explicit: process is demanding (candidates invest time), but yields informed fits; rigid prompts ensure domain relevance without over-specification. For new roles, external practitioners advise samples. Failures like incomplete education signal potential grit issues, probed deeply.
Quote: "Work is not, in fact, a spelling bee, and one’s ability to perform during an arbitrary oral exam may or may not correlate to one’s ability to actually design, build, sell, or support production systems." (Critiquing aptitude tests, prioritizing exercised skills via samples.)
Results: High Bar, Mission-Aligned Team
This evolved from painful lessons, yielding a team of balanced practitioners. No metrics given, but process scales for small teams, emphasizing quality over volume. Candidates self-select via transparency, reducing mismatches. Post-podcast discussion with Gergely Orosz validated it externally.
Quote: "Motivation should be assessed as much by looking at a candidate’s career... their career arc should be clearly driving them to solve the problems that we solve." (Linking motivation to trajectory, ensuring resilience for crushing problems.)
Key Takeaways
- Request 2-3 work samples tailored by domain (code for engineers, engagements for sales) to gauge real aptitude over quizzes.
- Mandate writing and analysis samples to test reflection, creation, and debugging without recall bias.
- Probe education via completion and self-learning stories; discount prestige, amplify artifacts for non-traditional paths.
- Align on values with specific stories of reflection, violation, and tension; list yours explicitly like Oxide's 15.
- Exchange materials pre-interview for peer-like talks; allocate 9 hours across team for thoroughness.
- Front-load written evals (per separate rubric) to disqualify early; treat referrals no differently.
- Ask "Why us?" tied to mission; trace career arcs for intrinsic drive.
- For integrity, prioritize trusted referrals; verify basics even then.
- Consult domain experts for new role samples; assure presentation imperfections OK to assess teaching.
- Share internal docs (like RFDs) pre-interview for informed withdrawals.