3 ms·

A helpful tip for finding a new job that uses technologies you don't have professional experience with, but you want to learn... Say you want to learn Rust, bu

by mfrye0 7y ago

A helpful tip for finding a new job that uses technologies you don't have professional experience with, but you want to learn... Say you want to learn Rust, but all your experience is in Javascript. Most recruiters will immediately filter out your resume if you don't have the keyword "Rust" somewhere in the document. Before you start sending out your resume, spend a few weeks hacking on a Rust side project to learn some of the basics. Then on your resume, include a description at the top saying you're proficient in Javascript, but want the opportunity to work in Rust. Then include a "Side Projects" section at the bottom that lists your Rust experience. I've landed 3 jobs that way, where I'm hired for my experience with X, but under the condition I will have the opportunity to learn Y. Otherwise, it's easy to get trapped working with the same tech at a new job, and your skills eventually become obsolete over time.

mettamage 7y ago
This is blog post worthy, as I think this idea could fleshed out. Here are some questions in no particular order of importance, just curious (and showing some evidence this could be fleshed out): 1. How many times did you try it? 2. Why do you think it works? 3. How do you find companies that have both technologies? 4. Have you seen a difference in the willingness to let you learn the technology that you'd want to learn? 5. Do you know of times when this approach failed, if so why? 6. Are you of the opinion that if you'd spend 5 years working on JS for 100% of the time vs 5 years 50% of the time and 5 years 50% of the time on a technology that you'd like, that you would be as experienced in JS in both cases? Even if you're not, could people prove that you're not? Should you just say you've had 5 years of XP with JS? 7. Are there moments when this approach is strictly worse compared to a traditional approach despite it not failing, if so why? 8. Are there strategies that synergize well with this approach? Are there strategies that diminish the value of this approach (aka work against it somehow)? Alright, brainstorm time is over. I'd read your blog post about it, or having an email discussion would be awesome too (my email is in my profile, if you think it'd be fun).
- mfrye0 7y ago
  That's a good idea. I think a blog post explaining the strategy further could be helpful for a lot of devs. To be frank though, I really don't have time at the moment. My typical blog post takes a few days to write, and I'm completely swamped with work for the next couple months. Like 12-15 hours a day, no life sort of thing... With that said, I'd be open to chat with you or someone else about it, and they could run with it on their own. My email is hello --at-- michaelfrye.me
pry86 7y ago
That's exactly what I'm going/trying to do. I have around 12 years of experience as backend dev (PHP, SQL, queues, rest apis, e-commerce, docker - so basically whatever needed in the given company). I tried to apply for a Java (Spring Boot) position, but so far doesn't work. I sent few CVs already, but an answer is always no because of "lack of commercial experience". Although I say know Java 8 a bit, and basics of Spring Framework. And also being ok to have 30% salary cut.

by mfrye0 7y ago

mettamage 7y ago

This is blog post worthy, as I think this idea could fleshed out. Here are some questions in no particular order of importance, just curious (and showing some evidence this could be fleshed out): 1. How many times did you try it? 2. Why do you think it works? 3. How do you find companies that have both technologies? 4. Have you seen a difference in the willingness to let you learn the technology that you'd want to learn? 5. Do you know of times when this approach failed, if so why? 6. Are you of the opinion that if you'd spend 5 years working on JS for 100% of the time vs 5 years 50% of the time and 5 years 50% of the time on a technology that you'd like, that you would be as experienced in JS in both cases? Even if you're not, could people prove that you're not? Should you just say you've had 5 years of XP with JS? 7. Are there moments when this approach is strictly worse compared to a traditional approach despite it not failing, if so why? 8. Are there strategies that synergize well with this approach? Are there strategies that diminish the value of this approach (aka work against it somehow)? Alright, brainstorm time is over. I'd read your blog post about it, or having an email discussion would be awesome too (my email is in my profile, if you think it'd be fun).

mfrye0 7y ago
That's a good idea. I think a blog post explaining the strategy further could be helpful for a lot of devs. To be frank though, I really don't have time at the moment. My typical blog post takes a few days to write, and I'm completely swamped with work for the next couple months. Like 12-15 hours a day, no life sort of thing... With that said, I'd be open to chat with you or someone else about it, and they could run with it on their own. My email is hello --at-- michaelfrye.me

pry86 7y ago

That's exactly what I'm going/trying to do. I have around 12 years of experience as backend dev (PHP, SQL, queues, rest apis, e-commerce, docker - so basically whatever needed in the given company). I tried to apply for a Java (Spring Boot) position, but so far doesn't work. I sent few CVs already, but an answer is always no because of "lack of commercial experience". Although I say know Java 8 a bit, and basics of Spring Framework. And also being ok to have 30% salary cut.