The real difficulty is not knowing what your job title should be, or indeed what it means. The problem is knowing what your client / employer / recruiter THINKS it means.
I stopped calling myself a front-end developer after last year when the consensus changed to mean ‘JavaScript programmer who knows three frameworks and dreams in Node.js and Grunt’ rather than someone who can build a site in HTML/CSS/jQuery.
My current title is UI/UX Engineer but the ‘engineer’ part just means ‘more senior to an analyst’ rather than anything concrete. But now I’m working exclusively on web applications rather than sites, removing ‘web’ and adding ‘UI/UX’ makes sense.
We struggled to name our newly-formed group at my current employer. We shifted from ‘UI’ to ‘UI/UX’ to ‘Inraction Design’ and finally simply settled on ‘Design’. We sit between the Business Analysts and the Development team in the SDLC, we analyze, wireframe, prototype and write production HTML/CSS. The only word that covers all of that accurately is Design.
The real difficulty is not knowing what your job title should be, or indeed what it means. The problem is knowing what your client / employer / recruiter THINKS it means.
I stopped calling myself a front-end developer after last year when the consensus changed to mean ‘JavaScript programmer who knows three frameworks and dreams in Node.js and Grunt’ rather than someone who can build a site in HTML/CSS/jQuery.
My current title is UI/UX Engineer but the ‘engineer’ part just means ‘more senior to an analyst’ rather than anything concrete. But now I’m working exclusively on web applications rather than sites, removing ‘web’ and adding ‘UI/UX’ makes sense.
We struggled to name our newly-formed group at my current employer. We shifted from ‘UI’ to ‘UI/UX’ to ‘Inraction Design’ and finally simply settled on ‘Design’. We sit between the Business Analysts and the Development team in the SDLC, we analyze, wireframe, prototype and write production HTML/CSS. The only word that covers all of that accurately is Design.