CBTS Interview Questions
& Process

I was contacted by a recruiter online and sent my resume. After interviewing with the hiring manager, I received an offer, which I initially declined. The company then expressed strong interest, leading to negotiations and an agreeable compensation package, after which I accepted. The subsequent background check and drug test were completed, and a start date was confirmed. However, the Sunday before my scheduled start, HR informed me of a two-day delay. On the original start date, HR called to explain that the project funding had fallen through and the position was no longer available. This was a highly unprofessional and unethical experience, especially coming from a former managing consultant familiar with hiring practices. I strongly advise against this company due to this disingenuous hiring process and the significant time I invested.

I applied to CBTS on 11/26/2022 and got an email from the recruiter on 12/2/2022 to talk about the role. She set up a meeting with the hiring manager for 12/9/2022. I really enjoyed talking with the manager and got positive feedback. I sent a thank you note, and he responded saying he was impressed with my presentation and would make a decision soon. Two days later, I heard back about his decision. Even though I was disappointed, I thanked him and asked for feedback, which he kindly gave. Overall, it was a great interview experience.

This was for a CBTS developer gig, not a regular recruitment. The idea was to be a consultant hired by CBTS but working for their clients. I met the CBTS person right at the client's office where I'd be working. The interviewer seemed super prepared. They started by asking a few things to gauge my skills, then really dug into the technical aspects of what I knew. After that, we went into more general technical questions. We also covered some bigger-picture stuff, like what sparked my interest in software development. The next-to-last part was a quick and fun whiteboarding session where I got a simple problem, wrote some code, and then we tweaked it back and forth. It was way better than some other whiteboarding tests I've done. The interview wrapped up with me getting to ask my own questions. It was a long haul, over two hours straight, but I felt I got a solid understanding of the role. I didn't take the offer because I had a better one elsewhere, but this would have been a strong second option.

It was a pretty smooth process with two interview rounds. First, I had a chat with HR about my past work and to verify my certifications. Then, the second and final interview was with the hiring manager. This part was pretty straightforward, just a couple of specific questions, and the rest was mostly about getting to know me personally. Overall, it was a really easy and smooth interview experience. The only slight challenge was during the offer stage where the recruiter's accent made it a bit hard to understand, but we got through it. Honestly, one of the best interview processes I've been through.