4 ms·
One thing to Google is "constructive dismissal". https://en.wikipedia.org/wiki/Constructive_dismissal#Changes_to_the_employment_relationship https://en.wikiped
by bbarnett 6y ago
One thing to Google is "constructive dismissal".
https://en.wikipedia.org/wiki/Constructive_dismissal#Changes_to_the_employment_relationship https://en.wikipedia.org/wiki/Constructive_dismissal#Changes...
I am not even remotely suggesting that you bring this up to management. However, the concept of 'Job changed, title and/or pay stayed the same', is well understood, and has legal connotations in both civil code, and employment legislation.
My point is, have your job duties changed significantly?
Are you managing other developers? Mentoring them? It sounds like you're leading projects, which isn't just 'Front-end Developer'.
Hence, you have been "constructively dismissed".
However!
You're getting paid for the role. This is why I'd not even remotely suggesting that you approach management from this angle, but I might if I was about to leave, due to insufficient pay raises for a changed role.
So mostly, this is to give you info that 'lots of thought has gone into changing roles, and title/pay as a result'. And maybe a string to pull at.
- bbarnett 6y agoReally though, I'd likely just take what others have suggested. Just write your resume with role titles comparative to what you've done. List those large projects you've lead, and write 'Project Lead' or some other blather. "Head developer of project $x', and so on.