I've gone through the same process, not so much that I don't think I would be worth considering, but serious code and documentation examples aren't something I can really give out given that they're proprietary. this last winter I started a whole guest-kernel based syscall intermediation and distribution framework in rust just for the application. with all kinds of design documents. I was about 30% finished by the time I landed a job somewhere else :)

but I still applaud the intent. I self-selected out by giving into scope creep

▲

tonoto 3 hours ago | parent | next [-]

Oxide is one of very few companies where I felt that it is a company I really want to work for one day. I spent a decent amount of hours answering the questions and sent in the application, but never got any feedback and this was like 2-3 years ago. Spending time at regulated environments, I were in a similar situation that I could not really give out relevant information from the past. However, I have no regrets at all spending the time, as it was very useful for me personally to reflect over each question.

▲

TZubiri 7 hours ago | parent | prev [-]

I'd be interested in the context if you'd be willing to share.

It sounds from the outside like Oxide has an interview process that requires some low level engineering work to be delivered? Maybe I got that wrong.

▲

convolvatron 7 hours ago | parent [-]

no, they want a questionnaire, a coding sample, and an example of technical writing. there's a reasonable interpretation of that that doesn't involve writing a distributed unix.

	▲	TZubiri 7 hours ago \| parent [-]
		Sounds approachable, and something that would be evaluated based on merit. As usual, I'm assuming the assignment is evaluated based on a reasonable time-commitment. From what the recruiting experts tell me, it's a good strategy to spend as much time as possible, the deliverable is better, and the optics aren't bad either, it signals investment into the application instead of signalling spray and pray application broadcasting.