Completed by August 27, 2020
Richard is entering his second year in Computer Science with Honours at the University of British Columbia. During his previous work term with FACTSnet in the summer of 2019 as a Technical Lead, he deployed an effective OCR document scanning workflow that heightened productivity and reduced conflicts. This year, his role as a Technical Manager extends his responsibilities past the creation and usage of critical admin documents, timesheets, and allocations for company data. Richard strives to reinforce his leadership skills by ensuring that all employees and teams can efficiently and securely utilize technology and data in support of their projects. Currently, his major goal is to refactor legacy front-end code across numerous FACTSnet websites to ensure modularity, ease of maintenance, and future scalability.
This summer has truly been a phenomenal challenge for individuals and companies across the world, and we must recognize the efforts put forward by first responders, health workers, leaders, among others in working together to combat this difficult time. FACTSnet is fortunate to not be disrupted as severely as a lot of companies, but a transition to online meetings and remote work was imperative. From my familiarity of internal operations of the FACTSnet organization since my involvement last summer, I have demonstrated maturity and responsibility in ensuring that all processes and communication function as best as possible. While online meetings via Zoom became increasingly popular this summer, I have recognized how their business model limits free meetings to a duration of 40 minutes. More intrinsically back then, Zoom has suffered from allegations of poor security and weak AES-256-ECB encryption. The very similar feature set, added recording feature, and Google service integration of Google Meet is very pleasing. Thus, one of my core, recurring duties is the scheduling, hosting, and recording of every large FACTSnet meeting via Google Meet.
Ever since the start, I noticed that there existed a copious amount of disorientation among new hires as they tried to learn the reporting standards of FACTSnet within a few days of their orientation. What may have seemed to be common sense or habit to existing employees can easily confuse and demotivate employees in their onboarding process. Armed with the same experience that I encountered and eventually rectified last summer, I absorbed the perspectives of numerous employees who have emailed me about their concerns and requests for clarification. Subsequently, I took the liberty to completely rewrite the FACTSnet Start-up Guidelines and Reporting Standards document from the ground up to resolve as much of the confusion as possible. As a result of directing newer employees to this document, almost all of the duplicate questions have diminished about reporting instructions, the payment method, meetings, among others have diminished.
With fuel from the success of these changes, I similarly reworked various other admin documents, most notably the master reporting spreadsheet where all contact details and evaluations are saved, the reporting templates that get duplicated for new hires, the reporting checks procedure document that admins follow, the payroll spreadsheet, the start-up email, canned inquiries emails, and the messages that are sent by Google Drive when a file is shared. It became a natural responsibility of mine to ensure that new employees are set up as fluently and error-free as possible.
Along with the broad extent of my position in conjunction with the reliability and dependability of my work, I profoundly ensured that the payroll for the first pay period was conducted accurately and quickly. In addition, I have performed data entry using a significant number of employee consent forms to be saved in one of the federal government’s databases. One of the most important values that I acknowledge and uphold is data confidentiality, security, and privacy, which is why I consistently practice safe handling procedures that cannot be disclosed here.
No comments:
Post a Comment