This is going to be long but I hope it helps.
As someone who had a lot of non-tech-related work experience prior to graduating and getting my first coding job, I'll just point out a hard truth I had to learn firsthand. You are spending way too much space in your resume on work experience that is completely unrelated to the job you want to have. Your resume says you are a web-developer, but your work experience says otherwise. If you are a web-developer, your resume needs to be full of web-development experience (at the personal-project level if no professional experience). Development is a skilled position and your resume should show that your skill-level is higher than your relative competition, or your drive to gain skill is higher than your competition.
For example, I'm a, gainfully-employed, full-stack web developer. I also used to work at a Barnes and Noble and a Pawn Shop in college. Yet, you won't find ANY of that on my resume. The reason being is that your resume should set you apart from your fellow applicants for the position you are applying for. They don't care where or what you did when you worked as a Barista (no offense), they care what type of code you write, how proficient you are in writing it, and what you are working on RIGHT NOW to get better at your craft considering you are entry-level. They want to see your passion for learning. The best way to detail that is with detailing your CURRENT passion projects. I would even include your dev.to post about how you did your drum machine project. It shows how you think about code. Link that on your resume as well.
Even if you do keep that work experience on your resume, just put your job title, company, and the date range you were employed. At the very least, take out ALL the bullet points. That part is non-negotiable. I would even honestly consider not including your work history whatsoever and, if they ask about it, just be honest about you wanting to make sure your resume detailed your experience in development, and not your experience in serving coffee or being a film librarian. They will respect that kind of explanation.
The most important thing you need to do is list the current projects you are working on and, if you aren't currently working on projects, work on 2-3 self-starters like your drum machine that are easy to manage over time. Use GIT to upload current React projects you are working on to a remote GitHub repository (get a github if you don't already have one). Have two to three projects listed and simply give brief descriptions of the technologies used in the projects.
Here is a real example from me when I didn't have experience:
React Hockey Project -
The hockey application I am currently building is a web application built using the React JS library. React JS takes advantage of virtual-DOM updating to make re-rendering of components fast while keeping the separation of concerns at the component level. I also take advantage of several React libraries such as Reactstrap (for bootstrapped React Web Components), and React-Router (for Client-side Routing). I also modified/customized third-party components, such as the React AutoSuggest component, to make searching fast and simple. I take advantage of ES6's new Async/Await keywords to simplify and optimize concurrent requests from the NHL API. For styling, I use new CSS3 features like CSS Grid to accomplish a responsive layout without media queries and achieves a mobile-first design pattern that is so necessary with the amount of mobile traffic to web pages today. Git was used for source-control and you can find/clone the repository (link here). This is a passion project that came out of wanting an 'on-the-go' NHL stats application that was faster than all other current solutions.
Doing something similar to the above says that you are passionate about development. That's how you want to come off. You want to come off as someone who sees problems, loves to fix them, and loves to find the best ways to fix them, and are eager to learn. The way you prove that last sentence is by detailing and getting into the details of personal projects, rather than irrelevant work history.
Sorry for the redundancy, it's just a fact in this business that cannot be overstated.
I am.....more than fine with removing non-relevant jobs. The only reason I had them on there is because I'm told that breaking up time is bad, but I'm totally ok with losing them if it makes my resume look more focused. This is extremely useful feedback, and very much appreciated!
No problem man. In my experience, employers generally don't really seem to care about an entry-level candidate's previous work experience, but they might care about the gap. Your concern with gaps could be addressed by something incredibly minimal, like the following:
Barista - Company Name - 2019 - Present (Don't even include months)
Film Librarian - Company Name - 2015-2019
Just throw that section at the bottom and don't make it the focus. I wouldn't waste any space describing the positions. Personally, I'd have about 75% of your main resume dedicated to describing your projects in detail and I guarantee you will have a much better response rate.
As long as your conveying this is the resume of a very busy entry-level developer who is constantly learning, you'll be just fine.
We're a place where coders share, stay up-to-date and grow their careers.
We strive for transparency and don't collect excess data.