I have applied through "Curriculum Associates" web-site, the next day I have received an email from VP of Engineering re: HackerRank challenge to summarize the message: they care about your approach to questions, as well as Time Spent on db querying or coding (time is really important) and they encourage you to add notes as an explanation of your thought process. HackerRank challenge (timed 60 mins - one time deal) - it had 6 questions. Do not to copy text inside of HackerRank, and do not click outside of your challenge - that gets registered. "Human" does not review your actual challenge - if your answer is inncorrect do not spent time on notes and explanation - incorrect answer does not count. I did get an auto generated email from Curriculum Associates in about 15 mins after I finished the HackerRank challenge - team reviewed etc... since I worked on that challenge around 1 am, I doubt that their team reviewed or decided on anything. P.S.: You are encouraged to take "Sample Test" prior your actual challenge - it is timed and monitored consist of 3 easy questions - theory, sql, coding.

If you have been scheduled for a technical screen interview. The goal of this conversation is to help them identify candidates who can demonstrate capability and knowledge in quality and agile related process, and/or software test automation in an agile context. These interviews typically last between 45 and 60 minutes.

First: an online technical test on sql joins a programming problem and some basic testing questions. Second: Google hangouts technical test on shared doc, Java basics and sql basics - few questions on Joins, easy coding exercise- find duplicate in array and find highest product in a range of numbers which is a palindrome. Third: A series of discussions with 5-6 people, QA managers, vp and product owners. Questions would basically revolve around your current and previous projects and processes being followed. Define quality? An sql exercise. A discussion on a user story. A white board exercise where u need to figure out scenarios that needs to be tested. Interviews are easy but monotonous and unnecessarily long. Most of the time you will encounter similar questions from all or many interviewers.