Cobalt interview questions

I successfully passed the first round of the C# online assessment but was rejected after the first round of the virtual interview. The interview itself was a straightforward combination of technical concept questions and behavioral questions based on my past experience. This was the first time an interviewer told me I should be able to progress to the next round, only for me to be rejected before that even happened. While I am perfectly fine with being rejected for any job application, I feel that giving candidates false hope and making promises that can't be kept are not good practices. After I requested feedback regarding their decision, given that I had been told I should move forward, they responded by saying they felt I did not maintain a positive or gracious tone during the feedback request or in the previous interview. Upon reflecting on this, I acknowledge that there may have been a tone issue when requesting feedback after the rejection, but I don't believe this was an issue during the interview itself. Anyone who knows me can attest that I am always respectful and professional unless I feel treated unfairly. Additionally, I don't believe this was the true reason for my rejection, and I feel that it contradicts their company value of "Transparency."

My interview process at Cobalt was very comprehensive but it went smoothly and HR was very communicative throughout. The whole process is 4 rounds of interviews, where 3 of 4 are pretty standard interviews and one is a demo/presentation. The first interview was an HR phone screen to make sure you meet basic qualifications. The second interview was with the Director of Consulting and is a 30 minute video interview. This was a pretty standard interview, where they asked about my background, qualifications, and why I was interested in the position but it was pretty conversational - not reading off of a script. The third interview is a demo/presentation of the Microsoft product that Cobalt uses. If you have experience with this product, this portion of the interview should not be too difficult but still requires a few hours of preparation. I did not have experience with this product and thus spent many hours learning about the product before the demo. The demo is followed with some time for questions - most of these questions were not technical or related to the product, but rather how you arrived at your answers and what resources were used to prepare. It felt like this portion of the interview was very important for them to determine how you work, learn, and respond to ambiguous requirements. This is also important for candidates to assess whether they enjoy working with the product. The final interview was the following day and was pretty lighthearted, mostly just answering any final questions and tying up loose ends. I was provided an offer during this interview.