Strong HR principles and takes good care of employees.
Takes risks with forward-looking project management practices like lean principles.
Very strong work ethics and very fair and safe work environments.
Everyone is extremely professional, takes constructive criticism individually and collectively very well.
Good work-life balance.
Very nice work environment and near Google-level office (in ergonomics, not playfulness).
Unambitious and puts 40 people to work on something for a year that you think you can do yourself in a month.
Have the willpower and skills to do much more than your post? Tough luck.
Rigid hierarchy. Managers eat among themselves. You will never be proud of what you create or showcase it to your friends. As enterprise software, design and UI will always be absolutely abysmal.
Individual opinions or ambitions don't matter. Raises are meaningless.
It seems like once managers reach a management position, they lose all interest and enthusiasm in the company and its products. They fall into the Dilbert-ian middle manager category. The company would hugely benefit from managers who care about what products are being developed, what the market is doing, and what employees are working on.
Two rounds of interviews were conducted. The first round included React and CSS-related questions. The second round was more system design focused. This involved discussing how to design an appointment system for a tennis course and which database
1. Complete a Java project. 2. Receive an email to schedule an interview. 3. Communicate with HR and the Manager, discussing your expectations, responsibilities, and career prospects. 4. Receive an email to confirm your availability for the final ste
Standard OOP questions. Questions relate to Java Spring and dependency injection. There was a coding question. Overall, the interview process was standard for tech companies. You just need to be yourself, and if you are stuck, the interviewer will
Two rounds of interviews were conducted. The first round included React and CSS-related questions. The second round was more system design focused. This involved discussing how to design an appointment system for a tennis course and which database
1. Complete a Java project. 2. Receive an email to schedule an interview. 3. Communicate with HR and the Manager, discussing your expectations, responsibilities, and career prospects. 4. Receive an email to confirm your availability for the final ste
Standard OOP questions. Questions relate to Java Spring and dependency injection. There was a coding question. Overall, the interview process was standard for tech companies. You just need to be yourself, and if you are stuck, the interviewer will