What is it like to work at murex?

As a dev, it is very comfortable to work at Murex. The programming environment is very pure, and programmers are relatively respected, compared to other companies, such as. . . bank. . . There are many great people in the company, the learning atmosphere is very strong, the remuneration is very good, and they are among the best in the industry. The working hours are very flexible, but the workload is relatively heavy, but the situation is different for different groups. The workflow of our team is roughly like this. I still sprint every two weeks. Each sprint will start with estimating the story, which is the estimated workload in these two weeks. Then the sprint starts and everyone does their part. The last Friday afternoon is slack time, which is used to do what you want to do, such as supplementing knowledge, or optimizing the program in the company, or you have your own project, etc. At the end of each sprint, the team will discuss what we did well and what we didn’t do well. The boss will also have a separate conversation with you to summarize what we did well and what we didn’t do well in the past two weeks, or what you have done wrong. Unpleasant place. There is nearly an hour of study time every day, on average. The group will read technical books or take online courses together. The company will reimburse the expenses. Every morning starts with a daily standup, where everyone talks about what they did yesterday and what they will do today, and whether there are any difficulties. The advantage is that any problems are discovered in time. Currently, there are 15 to 30 minutes every morning. There is a technical expert who will share some java experience and so on, called daily java. In short, the learning atmosphere is very strong, the environment is very good, and the company is willing to spend money. There's been a lot of work lately, so I'm in a hurry, so don't mind. :) I saw a senior mentioned the content of the interview earlier, so I would like to add here that the dev interview after the company is no longer an old question that has not changed for thousands of years. I was recently caught as a guinea pig to test the company's dev interview system. Technical interviews will be conducted online on HackerRank. There are many practice questions above. You can complete the questions yourself and play HackerRank | Technical Recruiting for about an hour and a half. There are about 20 questions and two coding questions. It is a field test. The coding questions are still a bit difficult. You need to design a good algorithm and implement it. . And compile on the spot without a compiler. The rest are multiple choice questions. It mainly tests the familiarity with language and algorithms. But when I was testing, there were too few algorithm questions and design pattern questions, which were too dependent on language. So my suggestion to the company was to delete certain language-dependent questions. The language test itself is very boring. Add more design patterns and algorithm questions. But it's unclear whether companies will adopt it. . . But it can be guaranteed that the company is still very strict about recruiting people. My review suggestions are to read more about algorithms, practice more questions, and practice writing code on the whiteboard.