How badly did the test task?

Question

Java

Hello!
Not so long ago, I performed a test task for the position of java junior. They didn’t take a job, but they didn’t answer in what they “got along”. Therefore, please, whoever is not difficult, take a look at my code, and constructively criticize it so that I can understand what is wrong and fix it in the future.
Exercise:

Create and implement a Java web application. It is advisable to use Hibernate to work with the database, as well as use Spring to build the application.
It is possible to use any Framework.
Create an employee table in mysql or postres with first_name, last_name, second_name, age, experience and description fields to store the relevant data and implement the ability to search, add, change and delete them through the web interface.
If possible, use ajax for data modification and search and make minimal layout for the add and search form.

Sources here

Answer 1

a test task is not the only thing that is evaluated at an interview, sometimes a person is good, but there is a better candidate just with experience.

Answer 2

Not bad for a junior. From what I can see, the significant cons are:
Minor cons:

• extra files in the project (.idea/, target/, empl.iml)
• extra @Table(name="employee") and @Column(name="...") annotations in the Employee class - this is immediately done by the NamingStrategy setting (it may even be configured by default)
• in the Employee class, both constructors are not needed - an empty one is generated automatically (if there are no others), and a full one is not used
• in interfaces, it is not necessary to write public for methods - they are already public (and moreover, this cannot be changed)
• maven ( gradle rules :)