Within the company and context you are working I suspect it very fair to regard you as a test automation engineer, externally though when looking for a matching role I suspects it very depends on how you are using the tool.
What skills are you learning using the tool?
To what level does your test design impact the testing?
To what level are you involved in good automation practices?
Here are a couple of examples.
I used a couple over a decade back, almost play and record scripts, going through the main user flows of the application. When the product changed significantly, maybe a month maximum I’d throw away the scripts and spend a couple of hours re-recording them. They would catch some issues and offered a level of value. For me, I did not learn much, I did not use a lot of testing skill creating them and based on that I would not say I was a test automation engineer at all based on that.
If its just used as user/business flow coverage it was often more suitable for the business analyst to create these scripts and they definitely were not automation engineers.
When I use a code based tool, I’m still fairly light coding but I am in control of the architecture, re-usability, independence, startups, teardowns, data driven approaches, keyword driven approaches etc so I am more in control of good practices that may be built into the low code tool, in this case I feel I do fall into the automation engineer role more readily and importantly can transfer that to most frameworks low code or otherwise.
Now the tools have advanced but I think it will still depend on the skills you are using and the level of expertise you bring to the table.
I do not know the answers to the following questions but I suspect answers to these may determine if the term test automation engineer is a good match beyond your internal company view or if its something else to external hiring companies?
How much of what you learn and the skills required would transfer straight into a medium code solution?
Could the business analyst who knows the key user flows very well do the same job, what more do you bring to the table over them?
What do you personally learn each day that helps you improve what you are doing?
How capable are you of introducing good automation practices to any framework?
Do you feel you could be hired and transition fairly easily as a test automation engineer for a different framework with a medium level of code?
Its a really interesting topic though, I have though struggled with the idea of whether using these a lot would make me a better tester or better engineer over time without the code.
