The first is FAE. The business will need a software technical window. When customers encounter software problems that the business cannot initially solve, I will help solve them. The problems are divided into bugs that require software RD intervention and difficulties that can be solved simply with documents or operation instructions. If you need to communicate with the software RD, I will discuss it internally. The second is to help the company apply for and pass the GMS certification. It will be necessary to clarify the audit information and other information with the Google window, and determine the needs and internal actions.

The biggest growth is the communication ability on the 2B side, which is very different from the communication method required by the previous 2C side.

The biggest gain is the experience of teamwork. In the past, there was a strong sense of hierarchy in large companies, and there were obvious barriers between departments. Now that there are relatively fewer people in the company, the experience of teamwork is richer.

On Fridays, I can leave work one hour earlier at 17:00. I really don't like traffic jams, so leaving work one hour earlier can help me avoid the rush hour, which I think is a very good welfare system.

The overall cooperation of the software team is quite harmonious. Everyone is in the same boat, understands each other's difficulties and works together.

The cross-team communication is also good. For example, when the business team receives questions from customers, they will filter them first and then transfer the problems that really cannot be solved to me. They will not directly add me to the group without any cause and effect. The overall communication is also quite immediate and smooth.

iMozen is a very challenging company, and the diverse challenges make the work more interesting.