zwli2026

As an Android mobile driver engineer, my daily responsibilities include but are not limited to： 1.Debugging new hardware drivers 2.Collaborating with system engineers 3.Collaborating with project managers 4.Collaborating with test engineers 5.Writing technical documentation

I worked at Intel as an outsourced contractor, serving on two teams with primary responsibilities including： 1.Developing and maintaining Cactus, a CI/CD tool created by Shanghai Intel employees. However, due to Cactus's inferiority to Jenkins in multiple aspects, it was ultimately not released. 2.Writing small utilities for Jenkins using Python and Linux shell. 3.Completing Jenkins system integration tasks assigned by the project manager. 4.Maintaining virtual servers running on VMware vSphere. 5.Performing testing tasks on Intel NUC mini PCs.

1.Conduct Fortify source code audits and Anma source code audits, performing static analysis to identify vulnerabilities in source code 2.Research Android system hardening techniques, identifying security vulnerabilities in smali code through APK decompilation 3.Prepare relevant audit reports and research studies 4.Investigate the fundamental principles of Android APK hardening

I transitioned departments at TCL, holding positions as a System Integration Engineer and System Engineer. My primary responsibilities included: 1.Developing and maintaining Android system-related tasks 2.Completing system integration for Android phone projects, primarily integrating various patches per project manager requirements. This involved using Jenkins for versioning and release management, performing boot-up verification for new software versions, and conducting basic testing 3.Writing Python and Linux shell scripts for Jenkins utilities. I developed a Python script suite for merging MTK patches, enabling automatic download from the MTK FEX website, sequential merging by ascending patch ID, and automated email notifications upon completion. This script suite was scheduled via Linux crontab for background execution, forming the foundation of our software release workflow. 4.Established CAT audio testing rules and procedures for Android phones 5.Collaborated with BSP and system engineers to assist in issue troubleshooting 6.Managed retrofit functionality to ensure production lines correctly back up and restore calibrated hardware NV values during phone manufacturing 7.Managed mini software (APK) maintenance to ensure all core functions operated normally before trial production. Provided on-site support during trial production runs to resolve mini software issues and other production-blocking software problems. 8.Authored technical documentation and conducted relevant training for new employees.

I initially worked on MMI for MTK feature phones in the MDTV department, with responsibilities including: 1. Writing code to implement basic functions; 2. Fixing bugs within the code. Since mobile TV wasn't profitable, the company dissolved the MDTV department. Later, I transferred to the SanQi Software Department, where my primary tasks involved STK and GPS pre-research—porting STK and GPS functionalities originally developed for W-CDMA phone projects to data cards. Interaction between the firmware and Windows interface software was achieved via AT commands. The interface software would send an AT command to the firmware, which would receive and respond to the command, repackage the data, and transmit it back to the interface software through the COM port.