Skip to contentSkip to footer

Ingeniero Java Senior Interview Questions

Salaries
Interviews

5,782 ingeniero java senior interview questions shared by candidates

1st round: Questions based on Java Object methods for object identity use cases in Java collections. For example, how do you enforce object equality on a business entity so that a Set implementation takes care of the duplicate entity as per business semantics. 2nd round: Questions based on coding standards like "Is it necessary to use List list = new ArrayList() over ArrayList list = new ArrayList()?"
avatar

Senior Java Developer

Interviewed at Infrrd

4.1★
Jul 18, 2018

1st round: Questions based on Java Object methods for object identity use cases in Java collections. For example, how do you enforce object equality on a business entity so that a Set implementation takes care of the duplicate entity as per business semantics. 2nd round: Questions based on coding standards like "Is it necessary to use List list = new ArrayList() over ArrayList list = new ArrayList()?"

## 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.

Viewing 661 - 670 interview questions

Glassdoor has 5,782 interview questions and reports from Ingeniero java senior interviews. Prepare for your interview. Get hired. Love your job.