Tencent Software Engineer interviews, as candidates describe them, mix project deep-dives, LeetCode-style coding, and fundamentals such as networking and databases, usually ending with an HR conversation.
$140K
Avg. Base Comp
$160K
Avg. Total Comp
4-7 rounds
Typical Rounds
Not reported
Process Length
Candidates describe Tencent's Software Engineer interviews as friendly in tone but technically probing. The most repeated theme is depth over recitation: interviewers ask why you chose a tool or design, then follow up on edge cases. One candidate was pressed on how pm2 works internally and how they would debug it if it stopped. An internship candidate was asked to justify choices like Redis and Sentinel.
Coding shows up in several accounts. Reports mention quicksort, DFS and LeetCode medium-level questions. One Kuala Lumpur candidate described some questions as medium to hard. Another candidate said interviewers cared about the approach and trade-offs, not only a working answer.
Fundamentals vary by team. One candidate was quizzed in detail on TCP, including the three-way handshake and what happens if a server sends FIN without receiving an ACK. Another was asked about sockets and APIs. Others reported database optimization and indexing, cloud services, object-oriented programming, and scalable system design.
Process shape differs between reports. Examples include a phone screen followed by three technical rounds, five technical rounds plus two HR rounds, and a five-round process over about four weeks in Kuala Lumpur. Interviews there were conducted in Chinese. Several accounts in this set ended without an offer, so rehearse explaining your own projects clearly and be ready for follow-ups on every claim.
Synthesized from 8 candidate reports by our editorial team.
Had an interview recently?
Share your experience. Unlock the full guide.
Real interview reports from people who went through the Tencent process.
Share your own interview experience to unlock all reports, or subscribe for full access.
Sourced from candidate reports and verified by our team.
Topics based on recent interview experiences.
Featured question at Tencent
Select the 2nd highest salary in the engineering department
| Question | |
|---|---|
| P-value to a Layman | |
| Your Strengths and Weaknesses | |
| Top Three Salaries | |
| Employee Salaries | |
| Monthly Customer Report | |
| Subscription Overlap | |
| Merge Sorted Lists | |
| Empty Neighborhoods | |
| Rolling Bank Transactions | |
| Top 3 Users | |
| Comments Histogram | |
| Like Tracker | |
| Random SQL Sample | |
| Google Maps Improvement | |
| Integer to Roman | |
| Weighted Keys | |
| Raining in Seattle | |
| Flight Records | |
| Largest Salary by Department | |
| Size of Joins | |
| Retailer Data Warehouse | |
| Session Difference | |
| Permutation Palindrome | |
| Find the Missing Number | |
| Recurring Character | |
| Scrambled Tickets | |
| Employee Salaries (ETL Error) | |
| Hurdles In Data Projects | |
| Liked Pages |
Synthesized from candidate reports. Individual experiences may vary.
Candidates report an opening call or pre-screen covering your resume, strengths and weaknesses, and why you want the role. One candidate described it as conversational. Prepare a concise project summary, since later rounds typically build on it.
Several candidates report early technical rounds centered on past projects. Interviewers may ask about target users, architecture, and why you picked specific tools such as Redis, or how you handled challenges. Expect follow-ups on trade-offs rather than a list of technologies.
Candidates report coding problems including quicksort, DFS and medium-level questions, with one describing some as medium to hard. One said interviewers wanted the approach, trade-offs, and reasons for choosing an algorithm, not only a working solution.
Reports describe questions on TCP behavior, sockets and APIs, database optimization and indexing, cloud services, object-oriented programming, and designing scalable systems. Which topics appear likely depends on the team, so match your preparation to the job description.
One candidate reports that the process ended with an HR interview on culture fit and experience, after conversations with people from the WXG Mini-program team and other department leaders. Another mentions a group leader asking behavioral questions. Details such as location and stack may come up.
