Self-introduction and projects experience Good morning sir/madam, it’s my pleasure to introduce myself. My name is Hongxu Cui, 38 years old. I was born and raised in ShiJiaZhuang, HeBei province. In the summer of 2004, I graduated from Shan Dong University with a bachelor’s degree in Computer Science and Technology. Then I came to Beijing and continued my study on CST in Beijng University of Post and Telecommunication. I got a master’s degree three years later. Immediately after graduation, I started my career as a test engineer for Linux operating systems at CSSC, which is short for China Standard Software Corporation. I spent three and a half years there and was awarded the best employee in the second year. To pursue my dream of working in a foreign company, I got my second job at SEMC, which is Sony Ericsson Mobile Corporation. Its where both of my verbal and written communication skills in English were greatly improved. And as a scripts developer for automation tests on Android phones, I’m very experienced not only with programming in Java, Python and TCL languages, but also with designing and creating test framework. In addition, I am highly proficient with Linux commands and SQL. As for my personal qualities, I’m very self-driven, responsible and hardworking. I’m an analytical thinker, problem solver, and knowledge seeker. I’m a really good team player and I believe I have the combination of experience and enthusiasm to contribute to the success of this job. Thanks.

As for my detailed project experience, I’ll start with the latest one in Sony. To carry out Stability test automatically, which definitely can not be done manually, our team had developed a series of test cases in Java based on Android UIAutomator and structured the scripts into a delicately designed framework. In the framework, common functions and utilities were packaged and easy to be used by upper test procedures. Test configurations and parameters were also isolated with program logic. All these made the automation test scripts highly maintainable, reusable and easy to extend. We would do a smoke test whenever a stability test request arrived and made sure the test scripts were OK. If there was a problem, we would analyse the logs and made modifications without breaking the rule that ‘one script for all products’. Each of us did the same routine but was responsible for different products. As for the project experience in CSSC, I was wholly incharge of the certification and verification activities on the Linux enterprise operating system products, including x86, x64, Xen, non-Xen editions. There were only three of us but to run a huge coverage of functional test cases manually. So it was critical to make a good test plan. Normally when a new release was available each week, our team would design, develop and execute test plans, identify and verify defects using Bugzilla. We were also responsible for environment setup and maintenance. With the help of open source tools, we did some performance tests on Linux OS of different corporations to find out the gaps. I was also the one to organize and publish all the test results and data to the company in a report. That’s all. Thank you for listening.