Good range of further training opportunities. Travel time is counted as working time. Few overtime hours.
The corporate culture promoted by IBM appears artificial and lacks credibility. The primary focus is on good quarterly figures, and for this, savings are often made in the wrong areas.
Projects are frequently not located within one's own federal state, leading to high travel expenses.
Too many inexperienced developers are hired. The ratio of senior to junior developers on projects is unbalanced.
One sees little of the actual company IBM. You are essentially sold onto a project where you then work 40 hours a week. Changing projects is not easily possible.
Evaluates: * Core Java & advanced concepts (streams, exception handling, generics) * Frameworks (Spring, Spring Boot, Hibernate) * Microservices & REST APIs * Databases (SQL, joins, indexing) * System design (for senior roles) * Tools & DevOps knowl
Varied questions, moving from general to specific in the primary language (Java). This was followed by general questions about other technologies. There was no code challenge, and the interview concluded with questions for the interviewer.
It was a technical discussion based on my experience, and there were no questions too complicated. I was asked mostly about Spring REST, Spring Boot, and Spring MVC. The interview was with two people.
Evaluates: * Core Java & advanced concepts (streams, exception handling, generics) * Frameworks (Spring, Spring Boot, Hibernate) * Microservices & REST APIs * Databases (SQL, joins, indexing) * System design (for senior roles) * Tools & DevOps knowl
Varied questions, moving from general to specific in the primary language (Java). This was followed by general questions about other technologies. There was no code challenge, and the interview concluded with questions for the interviewer.
It was a technical discussion based on my experience, and there were no questions too complicated. I was asked mostly about Spring REST, Spring Boot, and Spring MVC. The interview was with two people.