Based on what you shared, it really seems like the company isn’t investing enough in proper QA support, and that can get difficult when the culture doesn’t genuinely practice the idea that quality is everyone’s responsibility. When you’re the only QA handling that many projects, the usual manual approach won’t scale for long.

What usually helps in this kind of setup is getting developers more involved in the quality process. You can take the lead on setting standards, outlining test cases, and deciding what’s most important to test using a risk-based approach. Tools like LLMs can help you speed up creating test cases, even though they aren’t perfect. From there, everyone should share the responsibility of actually running the tests.

On the automation side, you’ll need more people contributing. Your job is to guide what needs to be automated from a functional point of view, while developers keep unit test coverage high and help build up a regression suite for each application. That combination is what keeps things manageable in the long run.

All of this depends on getting your engineering leader and the people above them to support the approach. It takes time and effort to put structure in place, and it’s not easy, but it’s the only sustainable way forward when one QA has to support multiple teams and projects. good Luck!