First of all, there's a difference between QA and testing (see the reply here). From what I can gather in your post, you seem to be testing, not assuring quality (but in practice, I reckon this terminology gets mixed up sometimes).
Secondly, the job content is much more important than the title. For example, for new testers, they'd shouldn't mind having "junior tester" on their payslip in their second or third year, as long as they keep learning all kinds of things (writing test plans, first steps in automation, ...). Better so than a title which sounds better while one's not progressing.
Assuming you're a tester, why not follow the ISTQB division of roles?
They're clear, simple and every test professional should understand what is meant by them.
Will you be performing test design and analysis reviews, next to test execution?
You're a test analyst then. Sometimes you'll also read software tester or software test engineer.
Will you be doing the above, but with automated tests? You're a technical test analyst. If it'll be a balanced mix of both, why not say (technical) test analyst?
You could also be leading a small team (test coordinator, test lead).
With 4 years of experience, test manager is a position you're probably not hunting right now.
Additionally, if you insist, you can have them add medior or senior, although it's more something for your resume than for an official job title.
functionality tester
, then moved fromquality assurance
, totest analyst
, tosoftware tester
, totechnical test analyst
... and they've basically had the same responsibilities. My favourite (so far) isSoftware Tester
, as it's self-explanatory and non-IT folk can pretty much guess what it involves, whereas the others are always followed up with a question like "oh, so what does that involve?" :)