1. There were few acceptance criteria and I did not violate any ones. 2. I've sent task and I end up did not wait for response (it's been 4 days of a silence). Just after pushing HR in the same day I've received response. 3. in the feedback was said: a) that I'd chosen bad desigh for scalability however without any evidence why. I know companies where suggested solution works successfully (exactly in the same situation!!!!)LOL. b) that I did not handle concurrency - it's truth, I even mentioned this fact in the task and I'd written that it can be refined. Guys, do you think it is possible to write well defined/well-tested/thread-safe design during 2 hours? LOL c) that using enum for some kind of entities like country.. in an app there were just 3 constant string values - is it bad candidate for Enum. I'd adhere to simple and transparent desigh without premature optimisation - becouse it a big evil ))) d) And one of my favorite formulation:"Write up would not work" - what? I've covered my code with Unit tests, and coverage was about 99%, I'd tested every single bit of code - and it will not work? LOL Guys, read please above carefully and make your decision wisely ;)
Senior Java Developer Interviews
Senior Java Developer Interview Questions
"Senior developers have years of experience in Java and have the knowledge and communication skills to mentor other developers. Companies prioritize strong technical skills and questions will focus on problem solving and critical thinking. A bachelor's degree in computer science or a related field, along with years of industry experience are standard."
5,296 senior java developer interview questions shared by candidates
How would you secure inter-service communication in microservices?
Questions about Java and SQL
Nothing difficult. expected for a technical interview
Rest, Spring Boot, Microservices, Docker
java opp micro services sql vs no sql ci/cd tools
Core Java Threading Exception handling
Business requirements: - Keep it very simple and meet today's demands only. - You don't need to implement any authentication. - We need two main features, which should be implemented by REST endpoints. The application should be able to; 1- Put some money from the customer's Takeaway Pay allowance in the restaurant's account. We don't need extra details like the customer's name, or the restaurant's address. 1.1- The application should validate that the customer has enough funds in their Takeaway Pay allowance for completing the transaction and that the transfer amount does not exceed their daily limit of 10 Euros. You can assume the limit gets topped up by an external source every day, or you can always be creative and implement your own solution. 2- Display the amount in customer and restaurant accounts
When would you usue ArrayList vs LinkedList
normal java interview questions and springboot framework
Viewing 2031 - 2040 interview questions