I applied online. The process took 6 days. I interviewed at Hearst (New York, NY) in Jan 2015
Interview
I was asked about my resume and how those jobs applied to what I was wanting to do at Hearst. This was pretty much standard interview questions and no curve balls. My interviewer was extremely nice and polite. Overall, it helped that I looked up who I would be speaking to on linkedin first so I knew where she came from and how to relate better to her past experiences. I was surprised how short the interview was, but was happy that it wasn't a two hour long interview.
I applied online. I interviewed at Hearst (Danbury, CT) in May 2015
Interview
Phone interview with recruiter, phone interview with hiring manager and in person interview with hiring manager. Spent about an hour plus interviewing. The position was not selling what I expected. The recruiter was very nice but, didn't explain what the product to be sold or the position. This position was 100% cold calling and no customer maintenance.
I applied through a recruiter. The process took 3 days. I interviewed at Hearst (New York, NY) in Jul 2015
Interview
Awful interview process. DO NOT waste your time interviewing for this role. I was invited to meet with the Devops team, there were no introductions about their roles or what they did nor the role was ever explained to me.
They start asking you questions and begin to type on their machines with no real human contact or trying to get to know you. Very robotic interview process guy just types behind their computer not even looking at you. This is awful I know you can take notes but you can take those notes later. The whole experience felt as if all my past work is being questioned. Lots of textbook questions where they expect textbook answers.
The funny thing is that these guys really take themselves very serious. Their stack is a CMS platform that is NOT difficult or complex technology and yet they take themselves too serious. The guys are awful at interviewing they do not try to get to know the person and get the best out of the interview. They do not give you any feedback into your answers and just type like robots and look at each other.
My advice to HR is to fix this issues with the interviewing process. Most great Devops engineers are NOT going out of the way to work with CMS technologies and Publishing but we go there with open minds to see if we can contribute and maybe join a great team, but sadly these guys might be nice people outside of work but they don't come across as nice.
so I think they did me a favor because I realized quickly that this would be an awful place to work and awful people to work with.
By the way there is a previous review of the interview process for this role. I wish i had read it before i went so I am writing my own to save someone else the headache.
Cheers
Interview questions [1]
Question 1
can you tell me what happens after someone enters a URL on a browser