I'm a Solution Architect and have been in the software development business for about 25 years now - I've seen it all, I've done most of it, and now I hire other people to do it for me.
(I didn't intend this to be a wall of text when I started writing, but hey, enjoy!)
So what am I looking for when I hire a developer - that depends on the position, and I mostly hire mid- to senior-level developers.
When I look for a junior, I'm looking for a developer at the lower end of the price bracket because I'm looking for someone I don't expect to be able to work alone on most complex tasks - they should be able to grow into the position and eventually into a mid-level position, but its going to take some time to get there. Junior developers are like potted plants - they need feeding and watering and looking after and they will grow nicely.
When I look for a mid-level developer, I'm looking for someone I can throw complex tasks, often multi-ticket based, at who will catch them and work on them with minimal interaction after that point - mid-level devs are often the workhorses of development teams. They know what they don't know, and they know what they need to know to get the task done - they go off and learn what they need to in order to complete the work. They will ask good questions, and they will take the answers and run with them. They can come up with reasonably accurate estimates on work and tickets. They will produce good acceptance tests, good documentation and won't take much time to come up to speed on a bit of the puzzle they haven't worked on before. A mid-level dev is like a fruit tree in its prime - they've been nurtured and now you are reaping the fruit.
When I look for a senior developer, I'm looking for someone who will work with me in defining the work that needs to be done - they will look out for the gritty implementation details while I set the larger picture and identify the moving parts which need to be built. They will mentor the junior devs, and work with the mid-level devs on more complex matters. A senior developer is like an old oak tree - they've been around long enough to know what works, what wont, and they've seen it all.
Basically, what I'm saying is it doesn't matter what cool things you list on your CV - that might get you in front of me, but it won't get you the job as a mid-level developer. Your tool set is not necessarily my tool set, or the tool set that you will be working with when you come on board.
You might need to adapt to new ways of using the same tools, you might need to speak up about how to use something in a better way, you might need to learn brand new things. My job in interviewing you for the position is determining what you can do, not what your CV says you can do.
I'm not going to ask you how good you are at something, because I've had devs say they are the best thing since sliced bread and subsequently couldn't work out how to butter that bread. I'm going to ask you questions to determine how well you are likely to fit in, how well you are going to grow, what your analytical skills are like and what your general attitude is. I'm not going to give you a test based on what you say you know on your CV.
Mid- and senior-level developers have a different mindset to juniors - they know when something is iffy or out of place, they know where to look for issues, they know when the code being written is bad, and they know what to test and what to document. They have experience to draw on, and they will do that regularly.
A mid-level dev will happily go on an on-call rota to fix P1 issues out of hours (with remuneration of course) with minimal support - a junior dev will be out of their depth and require support most of the time.
A mid-level dev will often lead a development team on smaller projects and produce good results.
Does that sound like you? Are you ready to take that step up, accept more pay but at the same time more responsibility?
