Huawei Technologies Co., Ltd.

Role: Embedded Software Engineer

Department: Central Hardware Engineering Institute — 2012 Lab, Electromechanical Engineering Dept.

Period: December 2021 – January 2024

Location: Shenzhen, Guangdong, China

🎯 UniMOP Core Business Program Development

  • Situation: Wireless and optical access product lines had 10+ types of fan box components sharing the core UniMOP program (three-layer architecture: App — board-level tasks, Adapter — common driver layer, Port — unified MCU SDK interfaces). The codebase was large and required continuous development and maintenance to support multi-product delivery.
  • Task: Responsible for UniMOP framework-based development, system maintenance and version delivery, ensuring efficient coordination between products, hardware and host systems with stable performance.
  • Action: Developed modularly under the UniMOP three-layer architecture with strict code standards; covered the full lifecycle from code construction, integration testing to system maintenance and version delivery, ensuring reliability of each delivery.
  • Result: Contributed over 10,000+ lines of high-quality code, ensuring stable operation and on-time delivery of 10+ product types. Product and hardware system coordination efficiency significantly improved.

🎯 Galileo Fan Box Flagship Product Full-Process Development

  • Situation: The Galileo fan box — flagship product of the optical access line — needed an upgrade from standard to high-spec version. The standard version used unified control of 8 fans, which couldn't meet high-load local heat dissipation requirements. The new fan box must be compatible with existing slots.
  • Task: Lead full-process software development of the high-spec Galileo fan box, achieving independently controlled partitioned control while maintaining hardware slot compatibility, adding power adjustment and fan linkage speed control.
  • Action: Restructured the 8-fan unified control strategy into 4 independent modules with pairwise separate control; designed and implemented power adjustment and fan linkage speed control algorithms; introduced partitioned temperature control technology to specifically address local overheating.
  • Result: New fan box successfully maintained slot compatibility. Partitioned temperature control effectively solved local overheating issues, high-load stability significantly improved. The project substantially enhanced product performance and market competitiveness.

🎯 Cross-Department Collaboration

  • Situation: Product development involved multiple departments with different technical domains. Cross-department issue investigation was time-consuming, affecting product quality and delivery schedules.
  • Task: Break through cross-department technical barriers and establish a fast issue identification and resolution mechanism to improve overall product quality.
  • Action: Proactively learned other departments' domain knowledge and established cross-department communication channels; quickly identified and assisted in resolving technical issues through precise communication.
  • Result: Cross-department issue response speed significantly improved and product quality noticeably enhanced. Became a recognized bridge for cross-department collaboration within the team.

🎯 Documentation System Built from Scratch

  • Situation: The team relied on oral communication for technical information and project progress for a long time, lacking a systematic documentation system. Knowledge was hard to retain, new members struggled to get up to speed, and project traceability was poor.
  • Task: Build a complete work documentation system from zero and achieve standardized recording and knowledge retention of development activities.
  • Action: Proactively planned and established a documentation framework covering technical solutions, development processes, and issue records; continuously output high quality documentation and promoted the team's transition from oral to documentation-guided work style.
  • Result: Output 70+ documents. Team development efficiency and traceability greatly improved; laid a solid foundation for project management and knowledge sharing.

🎯 Team Documentation Integration

  • Situation: Each team member independently managed files and materials, lacking unified storage and version control. Frequent version confusion and data loss seriously affected project delivery punctuality.
  • Task: Establish a unified team material management solution to achieve centralized file management and version control.
  • Action: Led comprehensive team documentation integration, designed and implemented a centralized team space management solution, formulated file naming and version specifications, migrated existing materials and established a continuous maintenance mechanism.
  • Result: Thoroughly resolved version confusion and project delay issues. Team work efficiency and project delivery punctuality significantly improved.

← Back to Homepage

华为技术有限公司

岗位:嵌入式软件开发工程师

部门:中央硬件工程院 — 2012实验室 — 机电工程部

时间:2021年12月 – 2024年1月

地点:中国广东省深圳市

🎯 UniMOP 核心业务程序开发与维护

  • 情境:无线与光接入产品线拥有 10+ 种类风机盒组件,各组件共用核心业务程序 UniMOP(三层架构:App层—单板任务、Adapter层—公共驱动层、Port层—统一 MCU SDK 接口),代码库规模庞大,需持续开发维护以支撑多产品线交付。
  • 任务:负责 UniMOP 框架下的功能开发、系统维护与版本交付,确保产品与硬件及主控系统间的高效配合与稳定性能。
  • 行动:基于 UniMOP 三层架构进行模块化开发,严格遵循代码规范编写高质量代码;覆盖从代码构建、集成测试到系统维护和版本交付的全生命周期,确保每次交付的可靠性。
  • 成果:累计贡献超过 10,000+ 行高质量代码,确保了 10+ 种类产品的稳定运行与按时交付,产品与硬件系统的配合效率显著提升。

🎯 伽利略风机盒旗舰产品全流程开发

  • 情境:光接入产品线旗舰产品伽利略风机盒需要从标配版升级到高配版,但标配版采用 8 个风扇统一控制策略,无法满足高负荷场景下局部散热需求,且新风机盒必须兼容现有插槽。
  • 任务:领导高配版风机盒的软件全流程开发,实现分区独立控制,在兼容现有硬件插槽的前提下增加功率调整与风扇联动调速功能。
  • 行动:将 8 风扇统一控制策略重新架构为 4 个独立模块两两单独控制的分区策略;设计并实现功率调整与风扇联动调速算法;引入分区温控技术,针对性解决局部过热问题。
  • 成果:新风机盒成功兼容现有插槽,分区温控有效解决局部温度过高问题,高负荷稳定性显著提升;该项目使产品性能和市场竞争力大幅提高。

🎯 跨部门协作与技术问题攻关

  • 情境:产品开发涉及多部门协作,部门间技术领域差异大,跨部门问题排查耗时长,影响产品质量和交付进度。
  • 任务:需打通跨部门技术壁垒,建立快速问题定位和解决机制,提升整体产品质量。
  • 行动:主动学习其他部门领域知识,建立跨部门沟通渠道;通过精准沟通快速定位其他部门的常见问题,及时识别并协助解决技术难点。
  • 成果:跨部门问题响应速度大幅提升,产品质量显著改善,成为团队内公认的跨部门协作桥梁。

🎯 工作文档体系从零建设

  • 情境:团队长期依赖口头交流传递技术信息和项目进展,缺乏系统化文档,导致知识难以沉淀,新成员上手慢,项目可追溯性差。
  • 任务:需从零搭建完整的工作文档体系,实现开发活动的标准化记录与知识沉淀。
  • 行动:主动规划并建立文档框架,覆盖技术方案、开发流程、问题记录等维度;持续输出高质量文档,推动团队工作模式从口头交流逐步转向文档引导。
  • 成果:累计输出文档 70+ 篇,团队开发效率和可追溯性极大提升;为项目管理和知识共享奠定了坚实基础。

🎯 团队资料整合与集中管理

  • 情境:团队内各成员独立管理文件和资料,缺乏统一的存储和版本管理,频繁出现版本混乱和资料缺失,严重影响项目交付准时性。
  • 任务:需建立统一的团队资料管理方案,实现文件集中管理与版本控制。
  • 行动:引领团队进行全面资料整合,设计并实施团队空间集中管理方案,制定文件命名和版本规范,迁移存量资料并建立持续维护机制。
  • 成果:彻底解决版本混乱和项目延误问题,团队工作效率和项目交付准时性显著提高。

← 返回主页