3 Comments

The @CERN Track: Perfect ATS


At #TruGeneva I got to meet the Head of Recruiting for CERN James Purvis. It was interesting to hear the challenges they face in hiring some of the greatest brains in Europe if not the world. During the conversation James spoke about the challenge of what an ATS should look like in these social days. He produced this video for #TruMadrid, posing the question:

The conversation carried over to #truDublin and this summary was captured by SocialTalent who did a great job of mixing the final cut. Here is what #truDublin had to say after some added refreshment, Dublin style.

What are your views on what the perfect ATS might look like?

Bill

3 comments on “The @CERN Track: Perfect ATS

  1. Very interesting conversation here. I completely agree that the recruitment process is first and foremost, then the ATS follows. What wasn’t said though was that many firms change their process over time, so when choosing an ATS firms should be sure to pick one that not only conforms to their current process, but also provides the flexibility to change to a new process down the road. That can be as simple as changing some field names or which fields are required, or could even be providing a completely different workflow and user interface for different lines of business, but all on the same system.

    I also agree that UI should be easy. Unfortunately, recruitment is complex though, so most important here is that firms should choose an ATS that provides flexibility. That could be the ability to only surface certain task on menus, or where fields and data appear on a page. Firms should be able to make the UI of their ATS look how they want and not be tied to something that isn’t flexible.

    It’s also important when choosing an ATS to pick something that not only has a flexible UI, but one that is designed for how recruiters work. Recruiters tell me all the time that they are working on one thing, and need to jump to a different record to be able to, for example, lookup a client that just called, and still be able to return to the task they were working on before they got that call. So when you think about UI, think about having something that matches the interrupt driven nature of your day.

    On a similar front, it’s important to choose an ATS that doesn’t make you think about how to use it. This ties back to the comment in the video about the simplicity of Google. For example, when it comes to search, many ATS’ require users to think about how they are going to search (ie, boolean vs. keyword) or where in the database they want to search. That doesn’t make a lot of sense. It’s much easier to go to the search screen, and figure out what you are looking for, and search for it then having to figure out where it is in the database, or how you need to search for it. So if you are thinking about which ATS to use, please keep that in mind.

    Obviously, there is a deep topic with lots of facets. So thanks to Bill, Johnny and team for sharing some thoughts and surfacing this conversation here.

    Jonathan Wall
    @jwall
    Bullhorn Product Marketing

  2. Our new ATS can fulfill all CERN talent acquisition process for mining the resume of core scientists to support.

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

%d bloggers like this: