DEV Community

Discussion on: How should I go about setting myself up for my "dream job" at Mozilla?

Collapse
 
ben profile image
Ben Halpern

I'm not sure why this didn't occur to me right away, but if you did exactly this, I'm pretty sure you could land yourself at Mozilla:

  • Begin contributing to Mozilla open source
  • Start telling people your dream is to work there (like this post, etc.)
  • Keep it up and it will happen

Contributing is definitely a roadmap in. Stating your intentions to work there eventually will speed up the process. I feel like you are further ahead of other candidates with less overall clarity.

As an aside, if you're looking for ways to do other interesting open source work with Rust, you're welcome to try and get some Rust code into the dev.to codebase via Helix or some other way. It could be a nice way to experiment with more performant code. πŸ˜„

Collapse
 
redoxeon profile image
Michael Harding

As an aside, if you're looking for ways to do other interesting open source work with Rust, you're welcome to try and get some Rust code into the dev.to codebase via Helix or some other way. It could be a nice way to experiment with more performant code. πŸ˜„

ooo yeah that's a good idea! I'll try giving it a look and see how it goes.

I think I'll be using those bullet points as well as some of the other things here as my personal objectives for the next good while.

Collapse
 
rhymes profile image
rhymes

As an aside, if you're looking for ways to do other interesting open source work with Rust, you're welcome to try and get some Rust code into the dev.to codebase via Helix or some other way. It could be a nice way to experiment with more performant code. πŸ˜„

Ah ah! This morning I was thinking that playing with DEV parsing code (the RSS feed parser for example) would be an interesting thing to do in Rust (or better attempt to do) if I'd find the time this summer :D

Rust is notoriously fast at parsing text

Go @redoxeon :D