Absolutely yes. I've been testing for half a decade now, the past two years of which have been exclusively audio testing. About 18 months ago I started work as an embedded tester working side-by-side with the audio team at my studio. I got hooked up with a private office and a nice 5.1 system, wedged right in between five audio devs and the audio project manager. They include me in meetings and weigh QA opinions and perspective into their decisions.
Granted, I got damn lucky. Before I started testing audio exclusively, I managed to snag an internal temp position helping with audio design and voice implementation near the end of the production cycle. That helped a lot, both the experience as a developer and learning the tools. Since then, the studio (and industry) has moved from XACT to Wwise, but I've learned the latter thoroughly just from testing and picking up tricks from the sound guys themselves.
Now, I'm still an audio tester, but I did apply recently for an audio design job here at the studio. I was turned down because we're in the middle of a project and understaffed already, so they needed an experienced veteran to drop right in and hit the ground running. I'll definitely apply again once things slow down, but in the meantime, the audio team has offered to help me learn more of what I need to know to get the job eventually and boost up my portfolio in the process.
I'd definitely recommend trying to find a studio tester job rather than work for publisher QA... the pub guys are often generalized, worked into the ground, and never get a chance to move to full-time or even specialize in a specific field when they're on a project. Studio QA, on the other hand, are often fewer and more focused on their individual areas of expertise. Jump in, express an interest in audio testing, and boom. It'll happen before you even realize it.
Good luck to you!