Hired a ‘5‑Year‑Experienced’ Developer Who Acts Like a Newbie—What Should You Do?

The author recounts joining an overseas company at 28 with a résumé claiming three years of embedded development; on the first day he faced a massive automotive infotainment codebase, unfamiliar proprietary frameworks, and scant documentation, leaving him feeling like a complete newcomer.

He concludes that "five years of experience does not equal five years of growth"—experience can be limited by a small company, repetitive tasks, or outdated tech stacks, making a five‑year résumé comparable to a one‑year skill level elsewhere.

To evaluate a new hire who seems like a "萌新", the author suggests examining three aspects: (1) learning attitude – does the person ask questions and seek resources or pretend competence? (2) basic ability – can they handle a simple task independently, produce decent code, and solve problems? (3) the company’s cultivation mechanism – does the organization provide mentorship, documentation, and a realistic onboarding period?

He recommends a one‑month adaptation phase where the newcomer is assigned low‑stakes tasks, paired with an experienced mentor, and not pressured to deliver major output; after this period, the manager can judge whether the individual is progressing.

If after a month the developer still cannot contribute, it likely reflects a capability gap; if they adapt quickly, the initial "newbie" impression was merely temporary. The author also warns against unrealistic expectations: expecting a five‑year hire to be immediately autonomous ignores the need to learn the business, codebase, and team dynamics.

Drawing from his own experience, the author notes that with time and guidance he progressed from being deemed "not good enough" to becoming a core technical member within months, emphasizing the importance of patience and structured support.

Final advice: avoid rushing to dismiss the hire; assign concrete tasks, maintain open communication, provide training opportunities, and reassess after three months. If no improvement is seen, consider replacement, but also reflect on whether the interview process adequately tested practical abilities beyond résumé years.