Table of Contents
Part I-Basic requirements
- Using English as the project management language
- Adequate Excel skills
- Stable PC/Mac and internet accessibility
- Knowledge of the target language is required
- A fixed daily available time of 3-5 hours
- A good communicating ability, clear logic
Part II-Job responsibilities
Recruit from your own social network, classmates, acquaintances, etc.
Recruit from targeted social media platforms and groups.
Company will provide Ads support for senior team leaders to help recruit more people.
Session 1 training
Eg: Deliver assignments such as error collection appeal to the QA team members; submit system or permission problem with a professional, efficient way, etc.
Eg: Promote new candidate into moderate, promote moderate into QA, remove inactive account from the list, make and carry out the weekly plan, etc.
Part III-Common operation and knowledge
A. The job basics regard to inspection and payment
This project is for the labellers, both moderate and QA, to inspect pre recognized cases of the machine and make necessary changes according to the guideline. Moderate will take the first round and QA will then inspect the cases again to secure the overall accuracy and acceptance.
Both moderate and QA will be paid by the accumulation of the time duration of the good cases they produce. That is , the “current cut” time duration of any cases added together and past the inspection.
After Moderate and QA, every ~1k cases will be put into a batch randomly and inspected by the client. If it passes 90% accuracy the whole batch will be accepted; if not, the whole batch will be denied. The inspection is over batches rather than cases or individual.
Payment will be done monthly. Around the 25th of every month there will be a report for the 21th of last month to the 20th of this month, and this part will be paid on the 12th-15th of next month.
Eg: Work from Jun 21-Jul 20 will be paid around Aug 12.
However, for the new members, consider the length of the payment cycle, company is willing to pay certain amount in advance, after we see some stable production, and before the payment due date.
B. The preparation work
We currently use Gmail to register Lark and TCS accounts.
There are 2 parts of registration. The first part is for the team leader or candidates to register the real Gmail under required format; the second is for the team leader to submit this Gmail and the member’s name to apply for TCS permission
After the Gmail is registered, team leader should add the new members’ name and Gmail in shared Lark namelist file and inform supervisor to submit for TCS permission.
After the account is submitted, team leader should assist the new candidate to download and activate Lark and TCS.
When a moderate with good quality is promoted into QA, Team leader should submit his account again for QA permission
C. Session 1 training
Guideline and common errors study.
The team leader should get familiar with the TCS basic rules and arrange the guideline and common errors study.
-Deliver the guideline and common error files and arrange group study, discuss details of the guideline, and answer new candidates’ questions.
-Emphasize again on some common mistakes(numbers, punctuation, modal words, non target language, etc) will correct 70% of the new candidates’ mistakes.
-Deliver policy quiz and make sure they get it 100% correct.
Offline test and training
-Offline training materials are usually in the form of excel files
-The link column are links that’ll lead you to real TCS links(cases)
-Trainees are supposed to listen to the links, and then write the TEXT PART OF THE CORRECT TRANSCRIBE in the file and send it back
-The supposed to be correct answers provided by company are limited to the previous cut, and they might not be correct
D. Trouble shooting
Common problem includes “no permission” report from TCS app(for whom supposed to have permission already). Follow the standard procedure:
-Check the settings of TCS app, both “language” and “business line”. You’ll have to reopen the app and see whether this is really fixed in case of app bug.
-Check his log in route according to “prep tutorial” page
-Clear TCS cache and cookies, check internet connection, and reopen
-If still not working, record a screen and submit. The recording should be horizontal, a viewer can see every detail of the whole screen, preferably with native screen recorder of the computer.
Other commonly seen system errors include audio can’t load, the whole interface can’t load, etc. Please also follow the same reboot process first. TCS system have a large data flow and things could go jammed due to your physical location and internet status.
E. Error collection appeal
Error collection is an excel file that’ll be updated daily, it’s a collection of the failed QA
cases that inspected by the EVA. A QA must read and finish appeal in it first before he starts a day’s work. EC is both a study material and a conversation window for the QA and EVA to align with their standards. The company will have EC assessment irregularly to check team and members attitude towards EC
-Choose/write “no” if you agree with the EVA decision
-Choose/write “yes” if you don’t agree with the EVA opinion and think that you are right
-In case you choose “yes” please write down your reason, in English only regardless of the project language.
F. Weekly team status wrap up
-Conclusion of the past week
-Current team status
-Weekly plan for next week