Tencent WeChat Business Group Summer Intern Interview
A detailed review of a Tencent WeChat backend internship interview, including process and technical questions.
A detailed review of a Tencent WeChat backend internship interview, including process and technical questions.
| Rank | Name | Score | Finish Time | Q1 (3) | Q2 (4) | Q3 (5) | Q4 (6) |
|---|---|---|---|---|---|---|---|
| 539 / 6242 | YoungForest | 18 | 1:09:53 | 0:05:43 | 0:13:09 | 0:24:01 | 1:04:53 1 |
If n is even, use one a and fill the rest with b;
if n is odd, use all a.
| Rank | Name | Score | Finish Time | Q1 (4) | Q2 (4) | Q3 (5) | Q4 (6) |
|---|---|---|---|---|---|---|---|
| 175 / 4729 | YoungForest | 19 | 1:05:07 | 0:21:38 | 0:39:43 | 0:50:40 | 1:05:07 |
Overall, the difficulty was not high, especially the last two problems, which were not as hard as they should have been.
The interview was done by DingTalk phone/video call, and the hand-written coding part was completed through Alibaba’s online platform.
There were two algorithm questions:
Implement the data structure for a doubly linked list.
twoSum: find the indices of two numbers in an array whose sum equals target.
The algorithm question was to compute Edit Distance (Levenshtein Distance). I had happened to encounter edit distance before while reading Grokking Algorithms, and it can be solved with DP. But this problem was a bit more complex: among many strings, find the string with the smallest distance. It can be understood as “Fuzzy matching”.
The rough statement was:
1 | 莱文斯坦距离,又称 Levenshtein 距离,是编辑距离的一种。指两个字串之间,由一个转成另一个所需的最少编辑操作次数。 |
| Rank | Name | Score | Finish Time | Q1 (4) | Q2 (5) | Q3 (5) | Q4 (6) |
|---|---|---|---|---|---|---|---|
| 333 / 6106 | YoungForest | 20 | 1:04:22 | 0:25:00 | 0:33:40 | 0:43:21 | 0:59:22 1 |
A contest about speed and being bug-free.
| Rank | Name | Score | Finish Time | Q1 (3) | Q2 (4) | Q3 (5) | Q4 (6) |
|---|---|---|---|---|---|---|---|
| 233 / 4347 | YoungForest | 18 | 0:41:39 | 0:03:32 | 0:13:58 1 | 0:24:13 | 0:31:39 1 |
The problems in this contest were relatively simple. It was another contest of speed and bug-free coding.
After missing contests for half a year, I cannot even get into the top 200 in a smaller biweekly contest anymore. Scary.
2020 is destined to be an unusual year for me, mainly because I am facing the two gates of graduation and job hunting. This is the most important challenge and task I have faced in the past two years. I have prepared for it for a long time, hoping that all the accumulation would finally pay off. Reality, however, did not go as I wished.
| Rank | Name | Score | Finish Time | Q1 (3) | Q2 (5) | Q3 (5) | Q4 (6) |
|---|---|---|---|---|---|---|---|
| 306 / 8105 | YoungForest | 19 | 1:36:07 | 0:02:47 | 0:23:09 | 0:54:53 1 | 1:26:07 1 |
In this contest I finally got AC at the last moment, which was extremely thrilling. Since joining the students in the China region, it has been hard for my weekly contest rank to enter the top 200. For example, this time I dropped from 229 to 306. I have to admit that domestic competition is fierce.
The main reason for the lower ranking was that I spent a lot of time debugging and trying things on the third problem, and almost had no time left to implement the last one. The recent lack of practice has also caused my debug ability and one-pass bug-free ability to drop sharply.