I frequently put my title on resumes as whatever the company I am applying for is calling it. There's so many names for the same thing. If we call it "programmer" at this job and they call it "software developer" at the place I'm applying to-- well, I can read the requirements in the ad. Usually it is similar enough to not matter. So I just put software developer even if that's not the title on my paystub. Gets me past computer and HR filter, but when they call me/past employer no one balks at the slight difference.
I've never met someone who was like "Programmer" and "Software Developer" are too different! Same with "Coder". "Software Engineer" in some countries would be a no-no but many places it's interchangeable. Further, I've done some research on the psychology behind it and usually "software developer" and "software engineers" is a better way to put it for negotiation if that's possible because you're seen more as someone who makes something rather than "really expensive computer guy".
I've seen companies that are real sticklers for that sort of thing claiming that if one falsifies that what else are they about? Yes,nit is asinine but it does happen
Well if anyone can be a stickler it'll definitely be that programmer that was once burnt by a rogue semicolon.
I'm sure it happens sometimes. I just haven't personally seen it with the roles "Software developer", "coder", and "programmer". That is effectively the same thing everywhere I've seen it. Now if I'm a programmer and say I worked in primarily QA or database position we have a problem, but there's no real nuance between those three titles.
