Now that the idea has been settled, I agree to enter the Won project team. Although they are all engaged in outsourcing development, there are two different forms of development, the first is the common pure entrusting development, customers are not concerned about the requirements and expectations of their development work to be delivered to the entrusting company for development, they focus more on macro problems such as project progress, cycle, and quality. Another kind of development is buy-out. When the customer delivers the work to the entrusting Company, it also develops a list of corresponding developers and detailed issues about the development work, such as specific personnel plans, the customer will pay attention to the developer's development capabilities and so on.
In fact, in addition to the differences above, there is also a big difference between the two methods, that is, the difference in cost calculation, the first type of delegation is generally conducted by the developer's person/month or person/day, and the Development workload has been negotiated at the beginning of the project, as for how many people are arranged for development during the development process, the company does not require the customer to add development costs due to personnel changes. This method is called workload calculation. The second is to pay by the developer. in a certain stage, all the work of the developer will be done according to the customer's requirements, even if the customer does not have a job, he must pay for the work that occupies the developer. This is also a common way to count the number of people.
Previous development was a method of computing workload. The customer may not know who is doing development from the beginning to the end of the project, we only pay attention to the project information and the time point of every progress of the project. Most of the communication in the middle will also be done by Leader or Bridge SE (the first time we heard the Bridge SE statement was in Japanese companies, it is generally carried out by people with relatively high translation or Japanese skills), and communication is dominated by emails. However, the Won project team uses the head calculation method, so that all developers will have to go through the customer's interview, and the customer will have your technical skills and work experience, communication skills and other related questions are assessed. If the customer is satisfied with the comprehensive assessment, you can be sure to place you in the project team and add your name to the project contract, we call it "go to order" or "go to board.
I am not worried about the specific content of the interview. I still cannot remember the number of times I attended my work for so long, and I was interviewed by others, although it does not reach the level of "face-to-face", it is also a battle. In addition, when HR arranged for an interview with the customer, a CA (Communication Assistant) was also arranged to help me communicate with the customer. Because my English skills are relatively weak, I don't need to talk about it. If I use a Chinese PK, it's a piece of cake, but if I change to English, it may end up being speechless. Now there is a CA present, which is a burden for me.
The customer is in the United States and the interview is conducted through Skype meetings. The customer is responsible for the interview. It is said that he is a Chinese, nearly 50 years old, but he is not born in China and has lived in the United States for a long time, therefore, you cannot communicate in Chinese. The communication was smooth at the beginning. Although Skeyp was of low quality and had an accent in the customer's English, it was mainly for self-introduction and preparation in the past, it is relatively smooth. As soon as CA saw that our communication was still smooth, when she left the meeting just as she had something, the problem was exactly at this time. After I introduced myself, the customer asked a few questions, due to the noisy in Skpye and the customer's accent, it is hard for me to hear the customer's problem clearly. In addition, when the CA goes away, the customer becomes nervous, and the customer's problem is not understood, I couldn't answer the question myself. I saw the customer's eyes waiting for the answer through the video. I think he must have seen my eyes too. "Sorry." I can only make up for it with an apology. Although the customer repeat the problem once, the sudden tension still caused the customer to fail to hear about the customer's problems.
The interview was originally planned to be between 25 and 30 minutes, but we ended in about 15 minutes. Although the customer accepted my apologies with a smile, he still felt very embarrassed. I don't want to think about the results when I come out of the conference room, but I just want to figure out why it looks like this? It may be because of dependency. From the very beginning, CA was used as the default dependency. As a result, after CA leaves, it immediately becomes helpless and immediately becomes unable to control itself.
In fact, it is often difficult for people to succeed because of a retreat. They have been working in Japanese companies for so many years. Due to the translation, they have a great retreat, no matter whether you are communicating with the customer or sending emails, there is translation in everything. After a few years, your Japanese language is still in place. The interview result requires the customer to make an assessment based on his or her resume and other conditions. It is estimated that it will take several days for the results to come. Although the interview process is embarrassing, the more I am interested in this purpose. I still have hope before the results have always fallen.
