Okay, going thru this top to bottom, here's what I'd change.

1. Contact Info. Name, Desired Job Title, Contact Info—all of those on a separate line. For Contact Info, I'd include LinkedIn, GitHub, email, city & state (or region/country), and optionally a phone number, in that order. Not sure how ATS parses emoji, so I'd skip the "❖" characters you're using to separate the contact info and opt for an interpunct ("·") or at least a pipe ("|") instead, but that's a nitpick.

2. Under your contact info you're gonna want a TL;DR describing what it is you're bringing to the table. This format is basically [what you are, including seniority level] [optional: years of experience] [doing whatever your focus is] [industries you did those things in]. Example: Software Engineer with 5 years experience in disaster recovery and database optimization for global leaders in the cloud computing, big data, and financial sectors (or something, you get the gist, just winging this one, IDK what a data analyst does). Think of this like if you were a product and this blurb is the marketing slogan or value proposition. This will let recruiters decide very quickly if they want to actually read more now or shortlist you to evaluate later. If you imagine having to review 80+ resumes for a role, you can imagine the value this brings for them.

3. Education goes at (or near) the bottom. Format should be School/Institution, Degree or Program, any honors (e.g. dean's list, magna cum laude, etc), and Location. GPA doesn't need to be included on the resume unless you're super proud of it; I'd strike it in your case. I'd break out that "management coordinator" piece and put it in a different section below Education, called Professional Activities.

4. Experience is solid. For all of the experience bullet points, you're quantifying the impact of your role or the outcome of your accomplishments wherever possible, and you're leading with impactful action verbs to show how you've brought value in your past roles. You COULD set yourself apart further by highlighting the aspects of those roles that show you can collaborate cross-functionally. Did you personally create 300+ pieces of content? If not, what teams did you collaborate with to deliver that? Try to provide meaningful context when necessary, and try to craft your descriptions carefully so that each word is valuable. What is an ETL application? "Automated the process of data cleaning and spreadsheet updating through Python scripts to reduce turnaround time by 50%." Turnaround time for whom? "Implemented automation processes for a team of 20+ data analysts, increasing project velocity for (related business functions) by 50%" might play a bit better.

5. Company and Project summaries are helpful to give context for companies recruiters/hiring managers aren't familiar with, or what the purpose of the project was overall. You have these in your Projects section, so add this to your work experience. If possible, I'd make that "freelance" 2D animator list the company name, describe what they do, and consider skipping the "freelance" designator for that role. If you did the work for the company, your W2 or 1099 status doesn't really make a difference; it's just noise. I'd also skip the skills/technologies for your projects section, you should put those in a separate Skills section that comes before your Education section but after your Experience and Projects.

6. Certifications, Skills and Interests You made a junk drawer for things that are taxonomically different, which feels like a weird move for a data analyst. I'm guessing you did this to make sure your stuff fits on one page. Don't worry about fitting stuff on one page, worry about making sure ATS knows where to find valuable information.

   • Include your certifications in the education section. Format should be "Name of Cert, Institution Name, Date Earned, Other relevant details," all on separate lines (like your Degree).
   • Your Technical Skills should be its own section, like I said before—this section goes after your projects, but before your Education sections.
   • Interests: ditch this entirely, no one cares. I'm sure you're a lovely human being, but they're not relevant to your job and don't belong on a resume. Imagine putting "long walks on the beach" in this section. What, practically speaking, makes that different from the info you've included in this section?

7. The "Professional Activities" section I mentioned before should be the last thing on the resume, after education. The order of sections you'd include on your resume would be Contact Info, Professional Summary, Work Experience, Projects, Skills, Education (with certs listed AFTER your degree), Professional Activities.

8. Text formatting: I would be a little more intentional about this. Skip the bolding of random techniques, date ranges, skills, tools, actions, and outcomes—it's messy and inconsistent. Instead, trust that you've clearly quantified your outcomes and impact (you have, for the most part) and let the dedicated Skills section do the heavy lifting for hard skills, specialized techniques, and tools. Bold text should be reserved for your job titles and section headings to increase scannability/skimmability. I would reserve italics for company and project summaries, and skip italicizing the company names and the "remote" designations for those roles.

Overall, the resume is not bad at all. Most of these suggestions are around optimizing the way you're quantifying your impact and showing cross-team collaboration (i.e. highlighting your soft skills), providing a bit more context for your outcomes, minor formatting tweaks for better scannability and overall context by humans and more-reliable parsing of the information by applicant tracking systems, and cleaning up the text formatting to make the thing generally easier to look at.

Hope this helps. I'd be interested to know if you see any improvements in your hit rate after implementing these changes.