Sr Java Developer Interview Questions

5,566 sr java developer interview questions shared by candidates

## Task 1 * Write a new Controller for maintaining cars. * Decide on your own how the methods should look like. * Entity Car: Should have at least the following characteristics: license_plate, seat_count, convertible, rating, engine_type (electric, gas, ...) * Entity Manufacturer: Decide on your own if you will use a new table or just a string column in the car table. * Extend the DriverController to enable drivers to select a car they are driving with. * Extend the DriverController to enable drivers to deselect a car. * Extend the DriverDo to map the selected car to the driver. ## Task 2 First come first serve: A car can be selected by exactly one ONLINE Driver. If a second driver tries to select a already used car you should throw a CarAlreadyInUseException. ## Task 3 Make use of the filter pattern to implement an endpoint in the DriverController to get a list of drivers with specific characteristics. Reuse the characteristics you implemented in task 1. ## Task 4 Security: secure the API. It's up to you how you are going to implement the security.
avatar

Senior Java Developer

Interviewed at Freenow by Lyft

3.6
Nov 28, 2017

## Task 1 * Write a new Controller for maintaining cars. * Decide on your own how the methods should look like. * Entity Car: Should have at least the following characteristics: license_plate, seat_count, convertible, rating, engine_type (electric, gas, ...) * Entity Manufacturer: Decide on your own if you will use a new table or just a string column in the car table. * Extend the DriverController to enable drivers to select a car they are driving with. * Extend the DriverController to enable drivers to deselect a car. * Extend the DriverDo to map the selected car to the driver. ## Task 2 First come first serve: A car can be selected by exactly one ONLINE Driver. If a second driver tries to select a already used car you should throw a CarAlreadyInUseException. ## Task 3 Make use of the filter pattern to implement an endpoint in the DriverController to get a list of drivers with specific characteristics. Reuse the characteristics you implemented in task 1. ## Task 4 Security: secure the API. It's up to you how you are going to implement the security.

Then there is a very long long test that consist of 4 tasks: ## Task 1 * Write a new Controller. * Decide on your own how the methods should look like. * Add new Entities and ## Task 2 First come first serve: One Entity can be selected by exactly one other Entity with some condition. If this condition is not met you should throw an Exception. ## Task 3 Make use of the filter pattern to implement an endpoint in a Controller to get a list Entities with specific characteristics. Reuse the characteristics you implemented in task 1. ## Task 4 Security: secure the API. It's up to you how you are going to implement the security. The guidelines were as follow: * All new entities should have an ID with type of Long and a date_created with type of ZonedDateTime. * The architecture of the web service is built with the following components: * DataTransferObjects: Objects which are used for outside communication via the API * Controller: Implements the processing logic of the web service, parsing of parameters and validation of in- and outputs. * Service: Implements the business logic and handles the access to the DataAccessObjects. * DataAccessObjects: Interface for the database. Inserts, updates, deletes and reads objects from the database. * DomainObjects: Functional Objects which might be persisted in the database. * TestDrivenDevelopment is a good choice, but it's up to you how you are testing your code. The tell you that you have about a week to solve it, but you wouldn't need longer than 2-3 hours.
avatar

Senior Java Developer

Interviewed at Freenow by Lyft

3.6
Dec 5, 2017

Then there is a very long long test that consist of 4 tasks: ## Task 1 * Write a new Controller. * Decide on your own how the methods should look like. * Add new Entities and ## Task 2 First come first serve: One Entity can be selected by exactly one other Entity with some condition. If this condition is not met you should throw an Exception. ## Task 3 Make use of the filter pattern to implement an endpoint in a Controller to get a list Entities with specific characteristics. Reuse the characteristics you implemented in task 1. ## Task 4 Security: secure the API. It's up to you how you are going to implement the security. The guidelines were as follow: * All new entities should have an ID with type of Long and a date_created with type of ZonedDateTime. * The architecture of the web service is built with the following components: * DataTransferObjects: Objects which are used for outside communication via the API * Controller: Implements the processing logic of the web service, parsing of parameters and validation of in- and outputs. * Service: Implements the business logic and handles the access to the DataAccessObjects. * DataAccessObjects: Interface for the database. Inserts, updates, deletes and reads objects from the database. * DomainObjects: Functional Objects which might be persisted in the database. * TestDrivenDevelopment is a good choice, but it's up to you how you are testing your code. The tell you that you have about a week to solve it, but you wouldn't need longer than 2-3 hours.

1 technical test(HackerEarth) - Pretty easy as only 1 coding problem is there 1st Technical round (Virtual Video Call)- Covered almost all important topics in Java, Springboot, Microservices, Database, Few tools and REST API performance related questions . 2nd Technical round(which was not part of the process defined earlier but came in after 1st Technical Interview) it was Virtual Video Call as well - The interviewer thought be in his own world. He asked subjective questions but expected only 1 answer. Almost all the questions asked by him were on the implementations done by him or seen by him in his projects and he expected I should know them. Not interested in knowing what I implemented and has experience on. Ran out of scheduled time and just dragging the interview even though he made up his mind in first 20mins not to select me. I am not writing this negative review because I was rejected, but to make people reading this be prepared for what would come your way if you are ever going to get interviewed at LoyLogic. Also, HR would call you only when they want to speak with your. Your calls would not be entertained.
avatar

Senior Java Developer

Interviewed at Loylogic

4.1
Jun 14, 2023

1 technical test(HackerEarth) - Pretty easy as only 1 coding problem is there 1st Technical round (Virtual Video Call)- Covered almost all important topics in Java, Springboot, Microservices, Database, Few tools and REST API performance related questions . 2nd Technical round(which was not part of the process defined earlier but came in after 1st Technical Interview) it was Virtual Video Call as well - The interviewer thought be in his own world. He asked subjective questions but expected only 1 answer. Almost all the questions asked by him were on the implementations done by him or seen by him in his projects and he expected I should know them. Not interested in knowing what I implemented and has experience on. Ran out of scheduled time and just dragging the interview even though he made up his mind in first 20mins not to select me. I am not writing this negative review because I was rejected, but to make people reading this be prepared for what would come your way if you are ever going to get interviewed at LoyLogic. Also, HR would call you only when they want to speak with your. Your calls would not be entertained.

Viewing 631 - 640 interview questions

See Interview Questions for Similar Jobs

Glassdoor has 5,566 interview questions and reports from Sr java developer interviews. Prepare for your interview. Get hired. Love your job.