Unfortunately the CEO cannot be trusted. The interview process was not what it seemed. Both the recruiter and myself were under the impression a formal meet and greet would be the final time to meet after two phone interviews before a possible offer letter. When arriving I found that meeting turned into a 3hr seven person blow by blow interview. Had I known I would have brought example work and further documentation to show that I could more than do the work explained. What the recruiter and I did not know what that they were also interviewing yet another person, this information is always good to know when being interviewed. Even after my last meeting I was told I would know in 24hrs if I got the job only to find out four days later. Finally after hearing why I wasn't picked it was clear to me they again were not being fully truthful. Do not say the interview was good to the recruiter and talk about cubicle space etc. only to say days later I am missing background in their technology later and I can't explain process. The CEO originally wanted someone who could fit the team & culture but later retracts to wanting someone who knows their tool stack and can work with their web interface. Also, beware that they think the new product line will take much less time to test due to the Cloud configuration. Their expectations on releasing that product are not built around anything as they do not have any formal process. It's like telling the mechanic the cost to fix the car will be $8.00. I'm the mechanic you didn't even hire yet but you know?. Every day they do not hire a person, it is a penalty to the one they do because "all" documentation for Test Plans and Test Cases need to be written and performed. Even with the help of a few contract testers the ambitious date cannot be met without some risk. They have a simple system they think is complicated, that is the good part. You're not really the QA Mgr but an analyst that sometimes leads when they release.