Good domain
A company wide holiday at the end of every quarter
This company is for those who are perfectly comfortable with 1) no work life balance 2) internal politics 3) negligible appraisals 4) constant management changes 5) outdated technologies 6) SDKs and JDKs that are open source, because the good ones are paid versions. 7) interviews where DS and Algo and latest technology knowledge will be tested, but not one bit of it will be applicable in your daily life in the organisation. 8) constant policy changes Please be ready to work in situations where 1) the underlying bugs are not resolved, but the existing UI will be given a new look and feel and new bugs will be introduced 2) releases will be planned without considering company wide holidays and employees will be expected to work throughout the weekend. 3) there is no fixed road map of anything.
Things are always in the pipeline, because nothing has been planned effectively. 4) you will be hired to work on one technology, but you will not get to work on that, because it will always be "in the pipeline". 5) all the new stories and epics will always be on a "strict" timeline where the management will come up with ridiculous timelines, and devs capacity and availability will not be taken into consideration. 6) QA team is overburdened/understaffed, so devs will be working on testing towards the end of the sprint and at times, throughout the sprint as well. 7) unit testing is non existent, because you will be testing everything manually, not via test files 8) automation testing is always in pipeline. 9) end of the day, it's a blame game. 10) management thinks that they are doing you a favour by employing you. 11) the person you were working with today will probably be fired tonight, in the name of performance.
The layoffs are to be expected any time of the year. You can expect to be laid off either as an individual or in mass. 12) there is constant chaos. 13) everything will be thrown on you in the name of Agile.
The previous review by a former employee posted in June, 2023 is absolutely correct, word to word. Also, you may be invited for a face to face round to get to know the team that you will be working with, but do keep in mind that there will be an HR representative in the same room, so there is no chance that the team members will be able to give you a clear picture, even if they want to.
Please treat your employees like human beings and not machines.
Consider employee availability before committing deadlines, code freezes and scrum capabilities.
Emergencies are emergencies, expecting someone to prioritise company over a personal emergency is unacceptable.
I had interviews with team members, hiring manager and HR. Team questions were mostly on technology stack. Hiring manager was mostly towards understanding team work. HR round was mostly towards payroll discussion.
The interview was mostly focused on the core concepts like OOPs concepts, core Java, and SQL queries. Since I was interviewing for an associate engineer position, the level of these questions was medium and focused mostly on how much practical under
The person who took interview should know that he is hiring for the role of development, not for the role of teacher as he was seeking more on definition than checking on the knowledge of the candidate.
I had interviews with team members, hiring manager and HR. Team questions were mostly on technology stack. Hiring manager was mostly towards understanding team work. HR round was mostly towards payroll discussion.
The interview was mostly focused on the core concepts like OOPs concepts, core Java, and SQL queries. Since I was interviewing for an associate engineer position, the level of these questions was medium and focused mostly on how much practical under
The person who took interview should know that he is hiring for the role of development, not for the role of teacher as he was seeking more on definition than checking on the knowledge of the candidate.