I was always pretty good at landing junior level jobs. To give you a rough idea, I've done 14 interviews in my life and only 2 of them did not offer me the position. I'm at my 3rd job right now (turned down all the others). Also for reference I quit first one before the company went broke (I literally took the first job offered to me at the time, before doing other interviews I was invited to), 2nd one was just a 5-month project and I'm somewhat happy with my current job.

My rate of getting interviews per email sent is much lower (maybe 40-50%).

1.) CV. My CV is cool. It's a password protected website (I also generate a link that logs you in to save time for employers). It's a minimalistic one-page website with lots of cool features. It sets cookie that says Hi, it outputs messages to console, has fun comments in JS files, puts message in header. It also has "print friendly" button that hides unnecessary stuff (links, stuff that doesn't print well). If you click it 100 times you get an XKCD comic (and some prompts at 10/50 click). Just all around fun site that is also a very basic showcase of my work.

Granted most of the people don't even see the console.log messages. But I guarantee you two things a) those who do notice these details will want you more than some random guy b) you want the job more than some random job someone might offer you.

2.) Interviews. I'm extremely honest. I have zero problems saying "I'm sorry I've never heard/used this before" (which happened more often than I'd like to admit). As it turns out, our field is pretty big and people really don't expect you to know everything as far as they can see you've grasped different concepts before without big issues. But you need to show you're happy to learn. Not just willing, but happy. Make them know you're always happy to get more stuff under your belt. Humble yourself and show them you want to be as good as them in this technology.

Hell, I've been accepted for a job as RoR engineer and I've written maybe 10 lines of Ruby in my life. I told them that in the interview. I'm experienced in Laravel though (PHP framework). So I drew parallels and showed them that I'm familiar with the concepts. 2 weeks later they called me that I got the job :) Had to turn it down though.

I will also always try to ask about their stack/technologies they're using. Now I've been on interviews where their decisions were "uninformed" to say the least. For example, the guy interviewing me was going on and on about how the performance really matters. And they were using PHP (relatively new project). In cases like this (if you want the job) it is EXTREMELY important not to come off as arrogant, but still show that you're well informed. So I asked them how they decided for PHP, wouldn't Java/C# be more suitable. And they said that they were thinking about it, but ultimately decided for PHP as their developers had more experience. And, in order to not come off as arrogant, you need to find a way to (at least partially) agree with them. I said something along the lines: "Yeah, I can understand that. Sometimes you've got good developers on your hands and you need to implement some stuff quickly (which will require performance). You don't want to replace you good programmers and you don't have time to learn a whole new language/concept.".

But most most importantly - show enthusiasm. This will get you far. Show that that you enjoy this stuff, tell them about that hackathon, make them laugh with that irrelevant side project of yours that outputs morse code with belly buttons - where you were learning some new technology (or just improving on old ones), tell them about those local meetups you attended.

For junior positions people will always take someone who is easy to work with, will happily accept help (this is often more important than next one) and offer it too when possible and genuinely enjoy learning new technologies over someone who might be better on paper, but just doesn't show the above characteristics.