first came the phone interview, which was pretty easy. i was asked some basic testing questions like contents of test plan, what are test cases, test conditions, defect management strategies. i was interviewing for UAT position so it was more high-level and less technical. epending on who interviews you, you may or may not be invited for an in person interview, despite the straightforward q&a interview. i wa a little rusty and actually mixed up a couple of terms or deadpanned on a term that was so basic, like test data or scenario. luckily the manager who interviewed me could see that i had accenture and other consulting background, and given her similar pedigree, she figured i was just rusty and cut me some slack. another mgr would have not given me that slack, since i should have prepared for it. so i was invited for in person and i had 3 separate 1 on 1 interviews. pretty basic, just asked about my experiences, challenges with uat , clients. theyre big on non-traditional uat process, old days of uat usually involved inviting end users from all over US to spend 2 weeks of on site heavy testing of end to end scenarios . 8 hours a day . instead you work with multiple end users remotely , so they ask for experience on that or any insightful challenge/solution youve had related to that approach. also they ask some uat related basics , stuff that any qa/uat with a testing project under his/her belt would know. with uat, they look for communication too (and basically you're ability to motivate/enable your end users to execute tests - whether by black magic or conventional cliche-spewing automaton approach - which can sometimes be surprisingly difficult. but thats typical IT-people-person dilemma not difficult to overcome. i found out 2 days later, so they dont waste time, pretty efficient. then you go in to fill up forms from your contractor/recruiter office for criminal background check and drug test. :)