Developer applicants have rated the interview process at Huawei Technologies with 3 out of 5 (where 5 is the highest level of difficulty) and assessed their interview experience as 100% positive. To compare, the company-average is 61.7% positive. This is according to Glassdoor user ratings.
Candidates applying for Developer roles take an average of 14 days to get hired, when considering 1 user submitted interviews for this role. To compare, the hiring process at Huawei Technologies overall takes an average of 30 days.
Common stages of the interview process at Huawei Technologies as a Developer according to 1 Glassdoor interviews include:
Other: 33%
Skills test: 33%
Group panel interview: 33%
Here are the most commonly searched roles for interview reports -
I applied online. I interviewed at Huawei Technologies
Interview
Hard Interview with 4 leet code type questions. 1 Easy, 2 Medium and 1 Hard. First question was regarding pointers, other 2 were regarding arrays, and the last one was a dfs question.
I applied through college or university. The process took 4 weeks. I interviewed at Huawei Technologies (Lahore) in Apr 2024
Interview
Huawei's interview process includes an online application, initial screening, technical assessment, one or more technical interviews, an HR interview, and a final offer. It evaluates technical skills, problem-solving, and cultural fit, and may take several weeks to complete.
I applied through college or university. The process took 1 week. I interviewed at Huawei Technologies (Shenzhen, Guangdong) in Mar 2025
Interview
I first completed a 90‑minute online coding assessment covering data‑structures, algorithms, and basic system‑design questions. After passing, I was invited to a virtual on‑site consisting of four back‑to‑back 45‑minute rounds: two deep‑dive algorithm sessions on a collaborative editor, one system‑design interview focused on designing a scalable URL‑shortener, and a final behavioral round with the engineering manager. Each technical round required explaining trade‑offs and writing fully‑working, unit‑tested Python. The interviewers were friendly but pressed for optimal complexity and edge‑case handling. Feedback arrived one week later; although I performed well on algorithms, the team felt my design lacked production‑level detail, so no offer was extended.
Interview questions [1]
Question 1
Describe how you would design a distributed rate‑limiter that supports burst traffic while ensuring fairness across millions of API clients.