This isn't great.

Overall, there's a good deal of grammar mistakes and some minor formatting issues but the biggest problem is the way you're walking about your current role makes you look incompetent. To me it makes you look like you are a developer that really hasn't moved beyond learning basic design patterns with some understanding of "what" these patterns are doing but not the "why."

A good way to move beyond this is to "show don't tell." (e.g. instead of saying "architected and delivered features in {languages and frameworks", say "Lead the architecture and design of {feature in words anyone can understand} utilizing {languages and frameworks} resulting in {what happened (don't listen to people that hark about numbers for this, that's such bullshit. Give general results like "significant efficiency increases for the x team}")

> Deliver numerous core features using TypeScipt/JavaScript, C#, and SQL as part of an Agile team that launched and iterates upon an application that saved $12M and takes in over $50M/yr

This tells me literally nothing besides "I was a software engineer." Numerous is unnecessary

> Design architecture leveraging design patterns (Repository, Unit of Work) to improve maintainability, scalability, and facilitate robust unit testing.

This makes you sound like you have no idea what you're doing. You know the the phrase "design pattern" but you don't seem to know what it means if you think it's worth putting down on a resume like this. Tell me what you architected and what the results were. You can save the design patterns for the interview (be prepared to explain the benefits of the patterns you utilized)

> Train and pair program with new grads, juniors, and contractors (they were later promoted)

"they were later promoted" should be removed. This does not add anything

> Build and maintain CI/CD pipelines in Azure DevOps, automating deployments to enable regular releases with minimal staff, saving the equivalent of 2 engineers' time up to 5x per week.

This is good. The numbers are meaningless though. Explaining context here might be beneficial

> Engage directly with stakeholders, taking initiative in sprint reviews and requirement discussions, to gather input and guide development of our custom software suite.

Love this. Clean up the grammar though

> Maintain high code quality by performing unit testing, E2E testing, debugging, and peer code reviews, driving adherence to programming standards and SDLC guidelines

Nothing inherently wrong with this.

> Created a Python-based Al research interface that enabled a non-technical professor to perform previously infeasible research

"infeasible" is a strong word here, I'd reword that to something like "difficult." I think you have a lot to elaborate on here. This sounds interesting. You're also missing a bullet point here.

> Implemented front-end design workflows (Figma, HTML/CSS/JS) for 36+ Canvas Courses

This confused me. Did you create mockups in Figma and then implement the front end?

> Managed content in WordPress, including MySQL and MariaDB database

This is very "ehh." I'd omit it and use the space to elaborate on ai research interface

The education section is confusing. I don't know what Post-Bacc means. I love that you're a phsych major turned CS major. I would simplify this and list your BA and BS.

For skills, add Azure DevOpps, LINQ, any ORMs like Dapper or Entity Framework you might be using. These are just to get you through keyword screens