I would only call it a demotion for you since you want to be a software engineer, but so what?
Continuing to work in C++ doesn't seem to be preparing your for Java according to the places you've applied.
It is possible you will eventually find something staying in your current job.
How long you're willing to wait is up to you.
The next question is will having the role as a tester, be enough of a prerequisite for a developer.
One advantage you would have is experience as a software engineer in another language with the added benefit of Java experience even though it is as a tester.
There are no guarantees, but I would consider taking a job as a java tester only if the company, team and boss are better than where you are at.
Getting with a good company probably offers a better chance to become a Java software engineer through an internal position change than trying to explain to other companies how you split experience makes you a better candidate than someone who has already been a Java developer.
Personally, I find C++ developers to often (not always) have better insights to what is happening "under the hood" with their code and usually apply that in ways that someone who just knows Java does not.
Maybe you need to push that thought a little more in your next interview?
workplace.stackexchange.com/users/None/
Personally,I as a Software Engineer found the Software Engineering field to be more dominant and advance than testing whether it's manual or automated.
(Hopefully I am not being biased)Salary wise also
I believe Software Engineers make more than testers.
(On average) I am afraid working as a test engineer is not the most direct and efficient way to move from C++ to Java developer, unless you have so much of interest and enthusiasm to expand your Java skills outside your working environment.
(Such as reading related books or contributing to an open source Java application and use that in your resume)
workplace.stackexchange.com/users/65972/comxyz
Generally changing from software engineer to test engineer is not a demotion, and money is of course an excellent indicator for whether a career is pointed upward or downward, or at least this is true within an industry and field.
The reason is that the fields have converged in much of the methodology, skill and intelligence required.
It sounds like your resume is diverse in constructive ways that tell a story conducive to your goals.
This experience sounds wonderful.
workplace.stackexchange.com/users/None/
What kind of QA is this?
QA responsibilities vary widely.
Sometimes testing means manually clicking through an application and recording the result.
Sometimes testing means test automation, ie writing code to test other code.
Places that expect their test engineers to write code might use the SDET title: Software Developer Engineer in Test.
I think the SDET title helps keep you marketable as a software developer.
Eg "I provide business value by creating software; most recently the problem domain was test automation".
The first product at my last employer was a system and platform for front-end web application testing.
This was in the QA arena, but it was most definitely about developing and delivering code.
We later hired another dev who was focused on load testing.
Here again, in the QA arena, but the day-to-day was writing code to deliver a product.
There will be some people who don't immediately understand this kind of QA experience.
But you can market yourself.
You learn how to talk about your skills to other devs, non-coders, and non-technical people.
This is definitely anecdotal, but during my last job hunt I only talked to one person (a non-technical recruiter) who couldn't understand how a software developer might be part of QA.
The other couple dozen or so (including all other recruiters) understood and valued my skill set.
Finally, some practical advice..
ask these questions:
Is there any cross-over from QA engineers to product development?
what does that look like?
can I meet that person?
Do product developers ever cross-over to QA?
is that unusual?
why?
Are QA engineers expected to write code as part of the day to day?
And don't forget the Joel test .
Well, an updated version.
Ask about CI/CD.
Make sure you write code during at least one of your interviews.
Etc
workplace.stackexchange.com/users/9515/djeikyb
Yes, this is a demotion.
In general QA engineers are less valued and its typically treated as an entry level role at large corporations, with hires eventually moving into engineering or getting out (either pushed out or finding a developer job elsewhere).
It probably shouldn't be since a good QA engineer is very useful, but it will definitely be seen as such by people reading your resume later.
workplace.stackexchange.com/users/66714/Gabe Sechan
It seems you have experience doing A, applied for jobs doing B in which you have no experience and got rejected, and got offered a job doing C.
If you want to get experience doing B, you might apply for jobs doing A with a chance to learn B.
workplace.stackexchange.com/users/16101/gnasher729
Why should it be a demotion?
It's a valued field in the industry.
The only people who tend to look down on testers are programmers, just as testers look down on programmers (both considering the other the core of all their problems)...
If you're getting paid less as a junior test engineer than you were as a senior C++ programmer that's because you're going from a senior level job to a junior level job,
not because you're going from programming to testing.
Java experience could come in handy when working with Java based test tools, especially if you're expected to write unit tests for Java applications (though I'd expect that to be mostly done by the programmers, having a tester who can assist in it is very handy).
workplace.stackexchange.com/users/3429/jwenting
Generally speaking this is not a demotion.
A Test Engineer and a Software Engineer are two very different things.
Software Engineers often get paid more, but that would also be true if you compared a plumber to the HR person at a plumbing company.
Different careers have different pay rates.
That being said if you want to be a Software Engineer, experience as a Testing Engineer will not be as valuable to you.
Unless you have a good reason for switching, I would recommend staying the course with your current job until you have something that suits you more correctly.
workplace.stackexchange.com/users/61349/mwbl
I am a Software Engineer and have been specializing in C++ for several years. Due to market demand, I've been applying to several Java Developer positions but have been declined due to my lack of prior professional experience in the language. I have been offered a position as a Software Test Engineer that uses Java, but I am concerned that will send me down a different career path.   Money aside, how can i figure out if changing from a Software Engineer to a Test Engineer a demotion?
How do I tell if a position I am being offered is a Demotion?
workplace.stackexchange.com
<career-development><developer>
workplace.stackexchange.com/questions/92625
workplace.stackexchange.com/users/71314/Botso
This could be considered a demotion. The salary should be a good indication. The answer to this question is highly subjective and it is not easy to tell whether moving into a completely different job is up, down or sideways. It's very difficult to say with certainty whether this change amounts to a demotion.
The answer to this question is highly subjective and it is not easy to tell whether moving into a completely different job is up, down or sideways. It's very difficult to say with certainty whether this change amounts to a demotion.