Software Developer applicants have rated the interview process at Washington State University with 3 out of 5 (where 5 is the highest level of difficulty) and assessed their interview experience as 50% positive. To compare, the company-average is 80.7% positive. This is according to Glassdoor user ratings.
Candidates applying for Software Developer roles take an average of 14 days to get hired, when considering 2 user submitted interviews for this role. To compare, the hiring process at Washington State University overall takes an average of 28 days.
Common stages of the interview process at Washington State University as a Software Developer according to 2 Glassdoor interviews include:
One on one interview: 33%
Skills test: 33%
Background check: 17%
Group panel interview: 17%
Here are the most commonly searched roles for interview reports -
I applied online. The process took 3 weeks. I interviewed at Washington State University (Pullman, WA) in Aug 2011
Interview
My interview was laid-back and non-threatening, but did include very technical questions. The people involved included my new manager, a soon-to-be colleague, and other members of the tech team. Each of them were fully prepared with relevant questions, geared both toward my working knowledge of software development and my views on employment in the field.
Interview questions [1]
Question 1
I was given a somewhat mathematical software "problem" to solve. I do not remember the exact details, but it involved a good amount of interpretation as to what the best approach would be to find a solution that both produced accurate results and accomplished the (somewhat vague) objectives. While proving to be difficult, this problem was an excellent example of problems actually found on the job, and sparked a good deal of discussion between myself and the people interviewing me.
I applied online. The process took 1 week. I interviewed at Washington State University (Pullman, WA) in Jan 2009
Interview
Multiple interviewers.
First a basic check from a friend of the interviewer to determine if I understood some basic concepts of programming. Then to see if I could propose potential solutions to a primary task related to the job.
Second was with the people doing the hiring. These people knew what they wanted, but they didn't have any programming background, so questions were very open ended, and they asked that I teach them a basic concept of programming. From there hiring was quickly done.
Interview questions [1]
Question 1
The only difficult question was one related to the field. How do you match up strings that overlap? The answer I provided didn't really answer the question, but was designed to see if I could understand a potential solution.