Working as a tester does not provide any useful skills in terms of further employment as a developer?

Question

Software testing

Having studied the forums of testers, the corresponding answers on toster.ru, information on headhunter, I got the impression that
1) Working as a tester is not a launching pad for subsequent transition to developers. This is a separate area of ​​​​knowledge that provides a narrowly focused experience that is useful for a career as a tester, but not a programmer.
2) During working hours, the specialist will be busy mastering the tools and technologies that are necessary and useful in testing, but not in programming. That is, in order to develop as a developer, a specialist will have to study in his spare time (in the evenings, on weekends)? That is, working as a tester and preparing to leave for developers are two parallel processes, and not complementary?
3) For employers who are looking for developers (even juniors), the experience of a tester is nothing, and it is difficult to compete with those who initially have a specialized education or work experience as a developer?
4) Automated testing is a specific process that is loosely related to the tasks of writing program code, and therefore it cannot serve as a good preparation for working as a programmer.

Answer 1

Worked for two years in testing "converged systems" for mob. operators, before and after a web developer. Testers are ideally people with a completely different vision of the problem, and I never managed to see how they are ... if, of course, you are chasing a long ruble and some of your own prospects, or maybe you are dreaming of sheets of code, then another conversation .. but in general - then a good tester is welcome everywhere, he has his own skills, and he does not write code (well, almost), but he has sufficient "technical wisdom", which is always needed in life.
Taking a step back, it seems to me that a tester is sometimes a great path to further UX.
I'm not sure that I answered your question)
PS And on the points, in short, then:
1) Yes
2) Rather yes
3) Not a fact
4) Rather no

Answer 2

I have been autotesting for about 4 years.
Approximately 70% of my working time I wrote some kind of code.
Conventionally, 30% of the time for me personally, it was writing autotests and it seemed like the code was like that.
Another 30% had a fairly simple code so that it was more convenient to write autotests.
The rest of the time it is difficult to assess, there were not very difficult things, and there were more difficult ones.
Frameworks are mostly very specific, and of little use for conditionally back-end development. But it depends where you work, in some places you need to write a fairly high-quality code, with a very good load and, accordingly, optimization.

Answer 3

1. Yes
2. Not required
3. Not required
4. Not true

Answer 4

In a pure video, the work of a tester has little to do with programming directly from here and there is no step today a tester tomorrow a developer, just as there is no step today a salesman in IT tomorrow a developer, or say today an iron admin tomorrow a developer

Answer 5

1) Working as a tester is not a launching pad for subsequent development. This is a separate area of ​​​​knowledge that provides a narrowly focused experience that is useful for a career as a tester, but not a programmer.

Wrong.
This is a universal general developmental experience.
It is also useful for a developer to have an idea - how to write software so that it can be tested automatically. And then, it happens, they do such a thing that you can’t automatically test it in any way.
Wrong. You put too much emphasis on learning the tools.
It is clear that other things being equal, the experience of a developer is more useful than the experience of a tester.
But the experience of testers is far from zero, it is very useful.
Of course, we are talking about automated testing.
Other things being equal - a person without experience, but with a developer education or a person with experience in testing (automated, of course) - I would prefer to hire someone with experience.
Profile education can be safely multiplied by 0. Freshly minted graduates are brought to mind for at least another six months before they start to pay off at least a little.
The exception is the rare best universities. There are 1-2 of them in the country and miscalculated.
Wrong.
This will allow the developer to better understand all stages of software development.
And to make software that is more convenient for everyone in the team, and not just for him alone.