Why Huawei’s Software Development Structure Stifles Efficiency – Key R&D Lessons
The article analyzes Huawei’s software development organization, highlighting issues such as separation of architects from coding, multi‑layer management, rigid IPD processes, high communication overhead, inadequate tooling, and talent retention challenges, and proposes practical improvements for faster, higher‑quality delivery.
1. Organization
Architectural design SEs are separated from development; many architects lack coding skills, making true architecture design unrealistic. In Silicon Valley, architects stay embedded in product teams and can code fluently.
Developers are often low‑level and quickly promoted to management, reducing technical depth. Top engineers in the West remain technical specialists, enjoying higher respect and compensation.
Multiple management layers (PDT, PDU, various managers) create clear role definitions but also cause conflicting directions, high communication costs, and hinder rapid iteration.
Communication overhead is high due to numerous meetings, leaving developers little time for actual coding.
2. Process
The IPD process, suited for hardware, imposes long cycles and rigid metrics that can increase risk for fast‑moving software projects.
Security red‑lines, while well‑intentioned, become bottlenecks; waiting months for clearance can cripple product viability. Integrating security awareness into daily development (SDLC) is recommended.
3. Environment
Developers lack time to explore new technologies, relying on outdated tools. MOOCs and online platforms (Coursera, Udemy, edX, YouTube) provide abundant learning resources.
Languages like Go and Rust have become mainstream in leading tech firms, yet few Huawei engineers are familiar with them, risking a skills gap.
Technical qualification systems are cumbersome, with promotion often based on seniority rather than current expertise, leading to talent loss.
4. Tools
In leading companies, developers use MacBooks and have flexible environments for coding, building, reviewing, and testing anywhere.
Modern Git‑based code review and check‑in tools accelerate knowledge transfer and quality, whereas Huawei’s internal DTS bug‑tracking tool is rigid and poorly integrated.
Access to global knowledge bases (StackOverflow, GitHub, Google) is limited by internal proxy restrictions and language barriers, reducing resource quality.
Signed-in readers can open the original source through BestHub's protected redirect.
This article has been distilled and summarized from source material, then republished for learning and reference. If you believe it infringes your rights, please contactand we will review it promptly.
21CTO
21CTO (21CTO.com) offers developers community, training, and services, making it your go‑to learning and service platform.
How this landed with the community
Was this worth your time?
0 Comments
Thoughtful readers leave field notes, pushback, and hard-won operational detail here.