These titles are pretty meaningless in my opinion. Plus, what front-end developer means depends on who's looking anyways. Where I work, for example, my official

These titles are pretty meaningless in my opinion. Plus, what front-end developer means depends on who's looking anyways. Where I work, for example, my official job title is Senior Frontend Associate. What does this means exactly? I haven't got a fucking clue. But what boils down to on the day to day is this: I'll spend some time, turning mockups into static pages using HTML, CSS (and the occasional sprinkle of JS), but the bulk of my time is spent on implementation -- everything required to go from static site to a functional web application. Together with the other "Associates" on the team, we'll do everything from cutting the UI up into components, implementing business logic to handle behaviour and user interaction in these components, talking to the backend, and managing application state. So what we decide to call these roles isn't important. Rather, i think, we should focus on hiring for skills. This means that we should do a better job of describing the skill sets, that we are hiring for. If you are struggling to find work, you should invest time expanding your skill. Trying to restrict some arbitrary title to suit your comfort zone doesn't help either.