Interview Experience – Wissen Technology (Senior Java / Spring Boot) The interview process was lengthy and inconsistent. Initially, the process involved a HackerRank round followed by multiple technical interviews. I was rejected at the 3rd technical round, even though I was informed there would be up to 5 technical rounds, which felt excessive for a senior-level role. Later, I was again invited to an offline mass hiring test with around 50 candidates. The task was to write a complete Spring Boot application to read a CSV file, parse it into POJOs, and persist data into an H2 database — without internet access. This felt more like a memory-based elimination test rather than a real-world evaluation of engineering skills. The setup did not differentiate between experience levels, and senior candidates were assessed using the same process as juniors. The overall experience lacked clarity, respect for candidate time, and alignment with real-world development practices where documentation and tools are normally used. Suggestion: Streamline the interview process, reduce the number of technical rounds, and design evaluations that focus more on problem-solving and system understanding rather than memorization.

1.Coding round 2.Technical round 1 3.Technical round 2 4.Client round 5.Hr Discussion asked deep questions on oops and java collections and hashmap ,threads,inheritance solve Highest Average Score Among Students problem. again in round 2 was about springboot and microservices asked about dependency injection

Total 5 technical rounds, 1 st round being very basic and easy. Then comes technical rounds check basic knowledge and problem solving. Round 1 tech, round 2 tech , client round 1 , client round 2, hr round