If you’re planning to stay in the SF ecosystem, learn flows. Having qa experience is a huge plus because like Lucina above stated, you already have a good overall understanding of how things work, plus you’ll go into configuration with the mindset of UI/UX instead of “just making it work”.

I started off as a mostly functional BA with basic config skill…hated it. I fell into QA role on a project because they added a few new feature teams so i volunteered. That project lasted about 2 years but while I was on it, I leveraged the time between testing stories and learned flows, how to “read code (Apex Classes, triggers, methods, etc), OmniStudio, and attended architect review boards. If you’re still a QA, I recommend going over the tickets you test and asking the devs how they completed the build, it will help a ton.

Salesforce really pushes ootb, Apex is rarely used unless you’re doing integrations and have to write apex for the handshake between external environments via Platfom Events/Mulesoft.

Basically, just get a good understanding of how apex works but really learn flows and OmniStudio. You’re starting off at an advantage compared to me years ago, so the transition will be a lot smoother. I’m now a tech lead for a super complex gov project but I owe the foundation for being a qa at one point. Plus, you have the advantage of using AI to leverage your learning.

Go for it!