I found the interviewing process pretty unprofessional. For first phone interview, Recruiter told me that guy named Ryan will call me for phone interview. I waited and Ryan never called at the time, so I sent email to recruiter. Recruiter apologized and mentioned Ryan is busy guy and then asked for reschedule. Then second time, Ryan actually did call and asked lot of technical/process questions. Which I guess I answered pretty well. I noticed that Ryan wanted to move to next question before I would actually finish answering. Then he mentioned if I would be interested in Automation QA Engineer role rather than QA manager role, to which I asked him if interview is for manager role or not. then he said, they are looking for manager who can manage 50-60 QA engineers as company size is growing and I may be less experienced that. Here I was confused about how one person can manage that many engineers with out multiple manager hierarchy. anyhow, I was called for personal interview and I was told that there will be a programming test. So I went in there and following was my experience, I was supposed to ask for Ryan when I get there, so I did when I arrived there. To my surprise Ryan was not in office. So someone else (who did not knew that I was supposed to come in for interview) took me to conference room. Spent more than one hour asking me questions on my resume (From copy that I provided as he was unaware of interview). Then one more person spent another 45 minutes with me asking similar technical/process questions. Then someone talked to Ryan on phone and Ryan asked that person to give me written test. test had three probelms, 1. Write sort algorithm of your choice. So I wrote bubblesort. Simple enough. 2. Desing one employee table and write one query that returns employees and their respective managers. Simple enough. I created one table employee like empid empname mgrid and wrote query: SELECT t1.empname AS Employee, t2.empname AS Manager FROM employee t1, employee t2 WHERE t1.mgrid = t2.empid; 3. Implement doubly linkedlist and write unit tests to verify that your implementation in correct. I stumbled with this one. Linkedlists done long time back in school and being in QA management for quite long time, my programming skills got rusty I guess. My bad. It was a easy question but I stumbled because I was not in front of computer (was writing on paper) and offcourse google was not there to help. then Ryan came in. Saw my papers. and asked me to leave saying that seems like I can not do Object Oriented Programming, so I am under-qualified. So I left. all technical and other questions/answers did not matter just because I could not implement doubly linked list on paper. And on top of that I got branded that I will not be able to do OOP. Awesome....