📢 A Second Look on How We Present Vacancies: Teardown

Dale Alexander Webb
Bad Practice
Published in
4 min readJan 3, 2017

--

At Persona we have recently discovered what our products are hired for and who has the pains our products solve. Following that we have redefined our product offerings and messaging. To get there, we need to strip down what we currently have and question whether each aspect has a future in the new definition or not.

The first area we looked at is the way our users advertise job vacancies on our site. We exported the headline data of 700 most recent vacancies, with a variation of vacancies that had no applicants, a few applicants and many [applicants].

Currently, we display 4 things as headline data for both users posting vacancies and users looking to apply. These are the title, employer, location and salary.

I went through the vacancies and tried to spot patterns within the data. Our current UI allows any text to be written for the headline data with any length, but the location input component does have the Google Maps service as an optional auto-complete to aid the user. So it was interesting to see what our users would write.

The Vacancy Title

We noticed that most titles are constructed from noun-noun compounds. However, the actual roles and responsibilities could differ significantly. The worst type of titles would consist of (from…

--

--