You still have to know how blueprint nodes work, when to use them, and where. So while you’re not traditionally typing out code like a typical programming language, you’re still using logic to make things happen. I’d still call them a programmer, even if blueprint logic is pretty much limited to just UE4. C++ (as well as other languages) can be used universally and would be better for ‘real’ programming as it shows you’re not limited to just one piece of software.
Now if it was a simple click-and-drag editor where you just drag in images and most things are preset for you from a dropdown box, then I’d call them a designer. In the end, it doesn’t really matter (unintended LP reference there) how you define your title, if your game works and it is well optimized, then I say you did your duty.
Classifying one programmer from another based on their method is subjective from one person to the next. Blueprint, in my opinion, is a nice way for people to take a step into the programming world from a visual standpoint before diving into raw code. But of course, people learn in different ways at different paces. Again, arguments can go either way on this, but that’s just my perspective.