Job Titles are limited

[VickiLanger]

There are several option for job titles, but I'm pretty sure this isn't even close to enough. If this survey is meant to be taken be all people who use JS, this will give incredibly skewed results. This is the same in both State of JS and State of CSS

The best option would be to allow people write in their job title.

This list is at least missing pentesting, devops, are, instructors, network stuff, infosec, SEO, and many more

For reference, here's the current job title question

      - id: job_title
        template: single
        allowother: true
        options:
          - id: cto
          - id: front_end_developer
          - id: full_stack_developer
          - id: back_end_developer
          - id: web_developer
          - id: web_designer

[SachaG]

I think it'll always be hard to capture every possible job. We did have a freeform textfield before but we removed it because we couldn't really do anything with the resulting data, since it wasn't normalized.

We could have a much more extensive list and then use an autocomplete field I suppose, that seems like a good solution for the future. But we'd have to find a source to use for such a list in the first place.

Or, we could also just remove the question altogether. I'm not sure we do anything super interesting with that data anyway, and job titles are pretty subjective…

[VickiLanger]

Agreed. It would be hard to capture every possible job title. I wonder if there is a list of job titles somewhere.

I agree, if you're not really using the data, it may not be worth having the question. I wonder though, are others using data from the results for anything? If they are, I wonder if a text field would be a better option in the interim.