【Exclusive】 After five years, Recruitment Clues Reveal the Complete Picture: ByteDance is Quietly Restarting its Mobile Phone Development

According to Omdia Research, five years after shutting down its Smartisan smartphone business, ByteDance is re-entering smartphone core development in a new form.

This conclusion is drawn from a comprehensive analysis of ByteDance's official job postings. After comparing the specific responsibilities of hundreds of core positions, the fact is clear: ByteDance is not only focusing on developing lightweight AI applications at the edge, but is building a complete set of smartphone-level hardware and software infrastructure. The company is restructuring the upper layer's Agent interaction with the Android/RTOS system, delving into structural stacking, baseband, network communication, and has even progressed to the New Product Introduction (NPI) trial production phase aligned with contract manufacturing factory lines.

In hardware development and mass production, ByteDance's array layout is heading straight into the deep waters of the hardware supply chain. The Shenzhen research hub, located in the heart of the supply chain, is intensively releasing whole-machine processes, high-speed PCB interconnection, testing processes, and hardware baseband positions, fully integrating with contract manufacturing lines. Among these positions, the Structural Engineer role covers new device stacking, mid-frame, battery cover, and hinge design, listing flagship hardware development experience such as "foldable screens," "LIPO packaging," "IP68/IP69K" as bonus points; the whole-machine processes position requires mastery of DFM/DFA/DFS analysis, NPI trial production introduction, AOI inspection, as well as dispensing and soldering processes. These job descriptions are completely distinct from typical internet software development, presenting a clear profile of a large-scale hardware manufacturer.

On the system infrastructure side, Android system experts based in Beijing will oversee the end-to-end process from project initiation, system design, integrated development to mass production delivery, with responsibilities covering ODM/OEM integration, Android Framework, HAL, Vendor interface adaptation, Qualcomm platform optimization, and even overseeing factory flashing, aging, and production line testing. Simultaneously, the Mobile OS team is extensively recruiting SoC chip adaptation, BSP, RTOS kernel, WiFi driver, graphics engine, system power consumption, and DFX experts, almost dissecting and completely restructuring the underlying system framework of a smartphone.

The most direct breakthrough occurred in what was originally seen by outsiders as a purely software project, the "Bean Assistant" team. The Bean Assistant team's R&D focus is now extensively penetrating the hardware infrastructure, with positions covering touch driver, NFC, system thermal management, peripheral BSP, audio system, and sensor fusion. The key signal is in the recruitment of a Telephony RIL Modem Product Architect position by the team, requiring experience in Qualcomm or MediaTek (MTK) cellular network delivery, familiarity with Telephony systems, RIL drivers, field testing, CTA certification, and RF antenna development rhythm. This indicates that ByteDance's R&D scope has crossed the application layer and entered the core of mobile communication with baseband and wireless RF.

On the upper-layer interaction side, AI is reshaping the human-computer interface. The Agent software architect from the Mobile OS department will be responsible for designing a multi-Agent collaborative interaction framework to access internal and external intelligent entities via a unified standard protocol, achieving low-latency, multimodal dynamic decision-making; the perception and memory algorithm position within the Bean Assistant team will focus on user long-term memory, multimodal perception, and proactive service mechanisms. This confirms a deeper strategic ambition: ByteDance is not satisfied with merely preloading Bean Assistant as an app into terminals, but is attempting to reshape Bean Assistant as the primary entry point for the entire hardware system.