J'ai postulé en ligne. Le processus a pris 1 jour. J'ai passé un entretien chez Bodybuilding.com (Meridian, ID) en mars 2009
Entretien
Interviewing at Bodybuilding.com really drove home the fact that interviewing is as much a skill as giving an interview.
The interviewers were pretty clueless as to what they wanted for the interview. Indeed, the development manager threw in random, undesired programming technologies just to see who it might kick up.
The preliminary interview questions went ok and were easily answered. However, then the development manager allowed an underling to conduct the rest of the interview. This individual had obviously been through interviews and had a vague idea how interviews were conducted, but completely fell apart when it came time to conduct the interview.
His excuse was that clients can often be difficult to work with and can give conflicting requirements. However, most clients are at least halfway intelligent and have a vision of what they want. This interviewer had no such vision and was lacking even that much intelligence. And he obviously had come up with a couple questions he considered to be real zingers because he kept asking me questions *as I was escaping.*
Before dismissing my experience as a bad day or even sour grapes since I didn't get an offer (I wouldn't have accepted if I had to work with this guy), I have had a similar report from two other developers who interviewed with Bodybuilding.
Questions d'entretien [1]
Question 1
Design the object model of a system that only I know and I'm not going to give you any details.
Writing code on the whiteboard in front of a developer panel. Length was approximately 3 hrs. The questions were around design patterns, database design, and methodologies. Got to meet the current staff and get a feel for what a day in the life of their work would be.
Questions d'entretien [1]
Question 1
Write a SQL query showing Sales by region base off a table with sales records and another table with regions.
I spoke with a member of the HR team I believe the manager or recruiting. The call was around 25 minutes. It was a basic background overview and some technical question. The interview process moved pretty quick. I was contacted then had my phone interview a few days later.
I applied for the position in early June, and did not hear back from the company until early July. I was asked to set up a phone screen with a recruiter. I spoke to her over the phone. The recruiter introduced herself, and asked me about myself. While talking to Tawny she sounded like she genuinely cared about my work history and the things I'm passionate about outside of work. I imagine she talks to a lot of people a day, so making me feel like I was important was nice. We talked about my experience, my knowledge base, how I hone my skills and grow them. I know she has never been an engineer, but she was able to talk to me intelligently. When I asked her about the company, you could hear the passion in her voice about the company. She answered questions about the team, the culture, the different databases, and some of how the company is moving. I am currently waiting to hear how her talk with the hiring managers went, but she left me with the feeling that Bodybuilding.com is the company I want to work for!
Questions d'entretien [1]
Question 1
Have your worked in an Agile Environment before? How long were your typical sprints?
Thank you for taking the time to share your experience with us. Although we were unable to find your next career opportunity during the process, we want to stay connected and help you as new opportunities arise. - Nick, Talent Acquisition