(no title)
akshitgaur2005 | 20 days ago
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.
sudomateo|18 days ago
> 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.
panick21_|18 days ago
https://www.youtube.com/watch?v=wN8lcIUKZAU