It may depend on what you mean by automated testing.
Until 10 years ago automated testing using tools such as WinRunner was almost exclusively a System Test discipline. Agile and XP were in their infancy and automated unit testing wasn't common place. Generally the only automated testing going on was automated system and regression testing and this was being done within the test function.
TDD, Agile and so on have obviously changed that with developers increasingly writing automated tests but there is still a divide.
TDD and agile primarily focuses on unit testing - that is testing of individual modules, classes and routines at a code level. This is part of the developer role and - if System Testers are involved in the project - will have been completed prior to any release to the test team.
Automated System Testing (which I'll call it to distinguish the two) on the other hand covers full use cases from an end user perspective and tests through the UI. In my experience, this still remains the responsibility / remit of the test team and should do so as in large part the knowledge of what to test and how to test it (which are system test rather than developer expertise) is often more critical than how good the actual test code is.
So, the question is which are you doing. If it's TDD / agile / automated unit test then you're a developer / programmer, potentially one with a specific interest in automated test and TDD which you can highlight on your resume / CV.
If it's the later then yes, you are moving into system testing / QA and wearing two hats. If this is the case and you want to make your primary hat the developer one, I'd still call myself a developer but list the automated system test work amongst your skills and experience alongside your developer work.