Fairly easy interview process, technically barren. Access to competent senior leadership on occasion. Decent project structure.
CIC is regarded as lesser to mainstream IBM, so if you work for them, you will be seen as disposable or less competent.
CIC seen as lesser. I was unaware of the distinction, but having joined, I understand their view. CIC hires extremely underqualified developers.
It is almost shocking to work with 'developers' who do not even know what a variable is.
Avoid CIC at all costs. Work for mainstream if you can. Do not let them swindle you as they did me by portraying it as mainstream.
There are no benefits to it. Only the name on your CV will help.
Advertise CIC as it really is.
I applied through a recruiter at my school and then on the websites. Within a few days, I received an email stating there would be a phone screen. The phone screen involved discussing my skillsets and career aspirations. After a few more days, I w
I had a group video chat interview with the manager of the role I was applying for, as well as a prospective teammate. I did not feel uncomfortable, and the interviewers had a positive attitude. They seemed to have a huge appreciation for the company
All systems design questions primarily focused on infrastructure architecture and object-oriented programming (OOP) principles. The interviewer asked about: * Databases (relational vs. non-relational, indexing, normalization, transactions) * RE
I applied through a recruiter at my school and then on the websites. Within a few days, I received an email stating there would be a phone screen. The phone screen involved discussing my skillsets and career aspirations. After a few more days, I w
I had a group video chat interview with the manager of the role I was applying for, as well as a prospective teammate. I did not feel uncomfortable, and the interviewers had a positive attitude. They seemed to have a huge appreciation for the company
All systems design questions primarily focused on infrastructure architecture and object-oriented programming (OOP) principles. The interviewer asked about: * Databases (relational vs. non-relational, indexing, normalization, transactions) * RE