IDEXX Laboratories Senior Java Engineer interview questions

Location: Hoofddrop Review: They cannot afford you for your price tag, cheap. If you are willing to work for less money compared to your fellow folks in other companies go ahead. 1. Initial call with recruiter 2. Technical Interview 3. Technical assignment 4. 3 rounds interview first 30 mins with senior developer n test analyst technical), 30 mins with recruiter (pure waste of time), 30 mins with manager and lead (tehnical) Way too much judging by less eligible interviewers. They do not appreciate what you know and it doesn't matter. Only judge on what was not so good. The Recruiter The role of recruiter is unclear. She is so annoying with annoying questions. You will have to answer her questions in initial call and also in 3 rounds interview you have 30 min meeting to again answer her questions. No answers regarding salary or benefits or the hiring process. Too much time to spend on recruiter during a hiring process very unusual. She wants to know about your experience but could not understand anything what you say. She asks questions usually not asked by any recruiter and questions irrelevant to recruiter role. First Technical interview: What data type to use to store numbers? BigDecimal related question Type of data structures to use in application? How do you monitor data in your application? What are spring profiles? what is spring boot? what is dependency injection? Why to use micro services? what is docker? Technical assignment: They expect a lot from this assignment. For a screening assignment its way too much to ask for. They want backend, frontend, health checks, metrics etc etc. After submission, it will be reviewed by three developers and the feedback is shared. They judge you based of their personal preferences. The reviewers comments give me a sense theses guys are showing off. Keep in mind for reviewers, a screening assignment is not a code for your production deployments. One cannot spend all the time in the world for your free assignment submissions. If you can pay then expect a production ready code. 3 rounds interview : 30 min with senior developer and Test analyst technical). In this round the person claiming himself as senior developer opens the technical assignment and does code review related questions why its here, opens code and go to different code fragments and asks do you see whats wrong with this (Judging). Opening unit tests, why are these not declared in application.properties etc, opens an interface, no need to use public key word in interfaces. This is the interview, who are these guys? For eg: using @Autowired is bad and should not be used (The dumbest review ever and i heard it for the first time in my 8 years exp). We have multiple APIs with production deployed code using @Autowired for dependency injections, I dont know from which jungle they hired these people (claiming senior developers) from. Difference between relational and nosql database? Different type of testing? 3 rounds interview : 30 mins with recruiter. (unclear role of recruiter) Questions based on your previous project. what you do in your previous project. what are the issues. How you managed, how do you communicate to shareholders, how it was resolved. What are the causes of issue. When it was identified. Keeping this experience how you changed way of working. 3 rounds interview : 30 min with manager and lead (tehnical). Migrating data from one DB to another data base. What are three items to talk about during data migration? How do you validate the data quality? How do you map data you are consuming from other services? They want to hear technical answers not in general answers and actually what you do in coding to achieve something. I am not sure if these people even code to know hows its done to understand our answers.