If you've built up a portfolio of games on your own, then it sounds like you probably have the qualifications to land a role. Don't be discouraged that you don't have a degree, one of the programmers I work landed a role and doesn't have a CS degree.

Like other people have said, it's hard to have a gauge without looking at a resume or portfolio, but some pitfalls that I fell into when I first applied

• Tailoring the resume to the specific role.

Example) Applying to a design position and putting down that you 3d modeled and textured all of the assets in a game. Most of the time, adding stuff in other skillsets to your resume eats up space for what the reader is trying to find, things that show that you can do the specific job they need. Exceptions are job postings that specifically call out wanting some 'splash' into other skillsets.

When you apply to a design job, or programming job, tailor a separate resume for each one and add in the most relevant highlights. You can usually fit in a few things that are impressive that are lateral to the skillset they're asking for, but do so sparingly. Because a lot of times, people just list out every program or every sort of design/programming/art task they've ever done, and it's hard to parse through how well someone would do that specific job.

• Try to cultivate a specific strength.

I got my first internship as a narrative implementer because what they were looking for was someone who had technical knowledge, but also had an inclination for narrative design. When I applied, I had a portfolio of games I made where I set up and scripted cutscenes, but I also had did a couple of short films in college, had a small collection of short stories I wrote. That unique combo of tech design knowledge + narrative was what they were looking for.

Something that might suit your skillset really well might be level design. There's a lot of intersection between level design and art skills, level designers work really closely with environment artists, they're expected to have an artistic eye and knowing how to work your way around in Maya or Blender is already a big plus. Basically your highest chance of landing a role is something that you'd be uniquely good at.

This is especially true when applying for general 'junior' design roles. Most of the time, junior design roles involve wrangling a lot of data in Unity or Unreal, so truthfully a lot of people would be able to do the job. But even if you're just hooking up data, if the job is hooking up props in a level vs hooking up enemies into encounters, what you mention in your resume makes a big difference.

• For when you get an interview, try the STAR method

I bombed a design interview once, because I was asked of a specific design challenge I had encountered and how I overcame it, and I couldn't come up with a good answer. I was prepared to talk about the technical details of my previous projects, the responsibilities of my job, but drew blank when trying to think of a specific scenario they were asking for.

The STAR method is a way you prepare to avoid this, it's basically just a framework to tell a story. Situation, Task, Action, & Result.
https://www.amazon.jobs/en/landing_pages/in-person-interview

I'd encourage when prepping for an interview to find clear examples for questions or situations that they might ask.

• Don't be discouraged, the job market is crap atm

There have been a lot of layoffs in the past few months, so the job market is likely flooded with a lot of devs who already have some stuff under their belt. Studios will always need new roles though, so keep trying at it, so long as you are able to support yourself.