You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The options listed under 'category' sound like job titles, not categories. Because of this, it's pretty much impossible to have a full set. For example, we have “Junior Software Developer” but not "Software Developer" or "Senior Software Developer". We have the highly specific "Machine Learning Scientist" but no "Natural Language" or "Image Processing" scientist.
And many Python jobs will fall under multiple categories. For example, someone could take a managerial role on a project that utilizes machine learning and data analysis to do financial risk modeling.
We have the general “Engineer” along with the specific “Operations Engineer”, “Production Engineer”, “QA Engineer”, “Systems Engineer”, etc.
So, if I do a search under the non-specific “Engineer” category, all the specific engineering jobs will be omitted from my results page.
I could go on…
I suggest removing “Category” altogether. I think trying to get people to agree on categories will take months, and won't be worth the delay in deployment.
If you want to keep it, keep it extremely broad (e.g. web, scientific).
And if you want to have things like "Junior" and "Senior", create another field representing job level.
Should we scan the existing postings and try to expand the category and job types?
The text was updated successfully, but these errors were encountered: