A former EE PhD turned chip engineer shares his interview journey, detailing recruiter outreach, phone screens, and onsite challenges across Facebook, LinkedIn, and Google, while listing the algorithmic and system‑design problems he faced.
A former Alibaba insider recounts how the enigmatic engineer known as ‘Duo Long’—a non‑technical graduate turned P11 senior leader—single‑handedly designed and maintained critical systems like TFS, Tair, cache, and search, embodying relentless focus, self‑learning, and a true craftsman spirit.
In this talk, senior architect Neeke shares practical experiences and lessons on software architecture and refactoring, using bridge and building analogies to illustrate how business‑agnostic design, careful analysis of existing support points, and incremental restructuring can transform fragile systems into robust, maintainable solutions.
This article compiles detailed interview experiences for backend engineering roles at major Chinese tech firms, covering algorithm challenges, system design, networking, compiler concepts, and personal reflections that help candidates prepare effectively.
An in‑depth recap of Hong Xiaojun’s QCon presentation reveals how Meipai’s architecture evolved from a minimalist design to a highly scalable, high‑availability system, tackling MySQL bottlenecks, cache challenges, monitoring, CDN resilience, and technology migrations to support rapid growth to over a hundred million users.
The article discusses how to redesign a high‑traffic web order platform by addressing concurrency challenges, modularizing large systems, and reducing database load through caching, sharding, and eliminating costly transactions and joins.
This article presents a curated collection of seminal papers and resources covering operating systems, virtual machines, system design principles, distributed algorithms, overlay networking, and debugging techniques to help engineers deepen their understanding of system architecture and advance beyond growth bottlenecks.
Software architecture is described as a set of critical decisions about system organization, including the selection of components, their interfaces, and collaborative behavior, and as a compositional style that progressively assembles these elements into larger subsystems, a definition comprehensively presented by Booch, Rumbaugh, and Jacobson in the UML User Guide.
The article outlines the progressive skill set for operations engineers—T4 must master core operations, service metrics, and environment administration; T5 adds independent problem analysis, trade‑off judgment, and solution selection; T6 demands deep cross‑disciplinary knowledge, design elegance, data‑driven reasoning, and the ability to influence others, while also debunking common misconceptions about products, scripts, and platforms.
