Holland America Java Software Development Engineer In Test (SDET) Interview Questions & Reviews
Getting an Interview
- Popular Job Titles:
- Driver Guide (2)
- Assistant Cruise Director (2)
- Direct Reservations/Inbound (1)
- Owner's Representative (1)
- Java Software Development Engineer In Test (SDET) (1)
- Senior Systems Analyst (1)
- Marketing (1)
- Kitchen Assistant (1)
- Event Manager (1)
- Restaurant Manager (1)
- Senior Sales Analyst (1)
- Personal Cruise Consultant (1)
Java Software Development Engineer In Test (SDET) Interview (Neutral Experience; Easy Interview)
I applied through a staffing agency and the process took 1 week - interviewed at Holland America in November 2010.
Interview Details – My staffing agency initially set me up for a phone interview (not a phone screen). It was very high level with some very generic questions about process within a Software Development Life Cycle. It was fairly brief (considering it was an interview, not a screen) at 30 minutes.
Holland America expressed interest after the phone interview, and my staffing agency set up an interview with me and their Dev team and their interim Director. Most of the questions designed to gauge my skillset relating to Quality and process were asked by the interim Director. Questions asked by the Dev team members were /slightly/ more technical. No white-boarding required. The interview was highly non-technical -- I gather the interview's primary objective was to check for a culture fit. As the interview ended, I asked if they had any questions they had forgotten/missed, anything they wanted to follow up on from earlier in the interview, or lingering questions regarding any aspect of what my skillset could bring to the company. They had none. The interview was scheduled for 45 minutes but it ran 1.5 hours.
They declined to extend an offer because
1. they perceived I was too rigid with certain tools and opinions, though I was not questioned about this.
2. When they asked me to talk about one of my favorite topics, they misinterpreted my enthusiasm as condescending.
The team lacks a permanent Director, though the interim Director seemed fairly sharp. The Development team is fairly "old-fashioned" in their Development techniques: Waterfall, no testing, no process. This role was created to address those issues and they sounded very interested in change, advice, and recommendations. The team members seemed very easy to get a long with, though the interview gave me the perception they might have some interpersonal communication issues.