Bytes in the interview was beating, I thought that good things would take a long time... I didn’t expect to perform poorly on three fronts, and missed the opportunity to join Bytes.

Background introduction

Byte is the first formal interview I participated in during my job hunting journey. Since I have been in Hong Kong for this period of time, I don't know why the network signal is not good every time I use the video. There is always a delay in the sound when I use the video, so I re-appointed the time several times. I thought that good things would take a long time, but I didn't expect to perform poorly on three fronts, and missed the opportunity to join the byte. I want to record my experience of this interview and make a summary for myself. Although the results are not as expected, it also made me deeply aware of my shortcomings and the areas that need to be learned and improved. I hope to sum up the experience and lessons this time, and continue to work hard in the future.

One side (1h30m)

On the one hand, I was a very approachable young lady. The first time I met, due to network problems, I didn’t face it in the afternoon after I re-appointed two days later. The interview experience was great. I felt that the questions asked were all comprehensive, and the basic knowledge covered aspects such as computing network, operating source, database, and data structure. In addition, when asking the project, I am also very comprehensive, and I will not ask some very tricky questions, but can dig deeper along with my answers.

Self introduction

Project introduction (mainly asked about the Challenge Cup project in the resume. After about half an hour, I have expanded a lot. The following is only a part)

(1) What work has been done
(2) What difficulties have been encountered and how to solve them
(3) As the person in charge, how to divide the work and how to coordinate the relationship between team members
(4) How to solve the problem when the ddl is approaching in the later stage and the task has not been completed
(5) If there is still such a project to you, what to do

Algorithm question : fast sorting

Database (approximately 5 or 6 questions): Select students who have failed subjects greater than or equal to 2

computer network

(1) TCP/IP four-layer structure
(2) The difference between http/https
(3) The difference between Post and Get
(4) Why should url be encoded
(5) Common coding rules
chat : work planning, advantages and disadvantages, which companies are currently invested in

Two sides (1h30m)

Self-introduction
project introduction

How to test the video player
The difference between pointer and reference
Polymorphism
Causes of web page freezing
The difference between APP and web testing

Software testing related : black box testing and white box testing and their respective test case design methods

Algorithm question : Enter 1234, the next higher order

Rhetorical question

Three sides (40h)

One thing to say, this interview experience is really much worse than the previous two. The interview was originally scheduled at three in the afternoon, but the temporary notice was changed to seven in the evening, and then the interviewer was still ten minutes late, saying that he had just finished the meeting. At the time, I thought the interviewer was so busy, but it was understandable. However, during the interview process, the interviewer had a black face and asked questions very jumpy. I felt that I had not seen my resume. During the process, I also said that I will look at your resume first. Mainly asked a lot of questions about operating system principles and data structures.

Self introduction

Which subject do you think is the best? (I can’t say that I learned the best, but I may be more interested in the computer network, and then I asked a few questions about the computer network)

What computer-related courses have I studied (I write all my resume, do I really not read it......)

Start to ask the operating system principle

(1) What is a deadlock
(2) Do you know what virtual memory is?
(3) Banker's Algorithm

Know which deep learning algorithms (I talked about the faster-rcnn and rcnn series of algorithms, and then introduced a wave. Then I asked if I know other algorithms besides image algorithms, such as Barabara. I didn’t hear clearly... I said I’m right on images. The recognition algorithm understands a little bit more because Bi Shi is doing the recognition)

Algorithmic questions :

Use linked lists to implement queues, requiring minimal time complexity and space complexity
One million numbers, which sorting algorithm is the fastest
Minimum time complexity of sorting algorithm

Do you think you have any shortcomings?

I have done the most fulfilling thing

Rhetorical question

Data sharing

Below are some of the materials I have collected.

These materials should be very comprehensive for friends of software testing. Many friends who review this material have also obtained offers from Dachang. I hope that it can also help you. Follow me on WeChat. No.: Programmer Erhei, you can get it directly for free.

to sum up

In general, the byte interview experience is still okay. After all, it is the first company I have faced. I am already very happy to be able to go to three sides. Although there were a lot of ups and downs in the process, I thought it would be a lot of trouble, and it was a pity that I couldn't get a satisfactory result in the end, but it really benefited a lot.

Although the experience of the three sides is not good, a large part of the reason is because of itself. The content of the review is not comprehensive enough. For example, the banker algorithm has a bachelor's degree but has not picked it up during the preparation process. There are also algorithmic questions that are actually a big shortcoming of mine.

In addition, there may also be reasons for luck. The three sides were supposed to be carried out a week ago, but because of the network delay that day, the interviewer at the time could not talk to me because the mobile phone was not around, so he re-appointed time.

Then I just finished a bunch of final, pre, and papers in this three fronts. Maybe I didn't prepare enough and I was a little panicked. It's a pity, but I won't be discouraged.

Next, I will continue to work hard, review well, organize the summary well, and brush more algorithmic questions. The most important thing is to maintain a good attitude and have confidence in yourself. Do everything, and then wait for something good to happen!