Software testing interviewed ten companies a week, sharing interview experience

From the beginning of the interview, I divided the company size into 5 categories: 0-20 employees for start-up companies, 20-40 employees for small companies, 50-99 for small and medium companies, 100-499 for medium-sized companies that are about to go public, and 100-499 for listed companies .

Start-up companies

The start-up company I interviewed for the first time was particularly pitiful. I started the interview and asked me if I knew vuex? I said yes. The interviewer looked up at my face while reading the question. Ask me how did the company do content before? I said that I have to ask the product manager. Afterwards, I directly asked me about my own business, and it flashed in my mind, I am afraid that this person is not cheating on the code, right? I said, have you encountered this problem? They said yes, and ten thousand grass and mud horses galloped past them. Then he asked me another question. For example, if there is a table on the page, how can the front-end export excel. I said that our company provides the interface in the background, and the front-end does file download and export to excel. He asked how to do it without the back-end and front-end? I said this is not very good, will the performance of the front end be poor? Speaking of this, one of the interviewers said: Why can't the front end be done? The front end is omnipotent! The front end can do a lot of things! I thought about it, and I said no, I haven’t done it before, and I am humbly asking for advice, how did you export the front end? Another interviewer said: use plug-ins. I said, if I use a plug-in, I will do it, and then the interviewer interjected: Then why don't you say yes? I don't want to continue to rant, I'm not speculative, so I will call it with a plug-in? I asked how do you export without plug-ins? They didn't answer. Afterwards, I asked them about their business, and I said that your product is very similar to a company I interviewed yesterday, called Small Blackboard. They were surprised and said, have you ever interviewed at Small Blackboard? I say yes. Finally, before leaving, I reviewed their products from beginning to end, from the aspects of user usage scenarios, user convenience, network limitations, and operational complexity. Still too young to hold his breath. When he came out, he shed tears of grievance without disappointment. Therefore, choose a startup company carefully, and you must check the company before you go.

Summary: Small companies only care about whether you can use the framework to make products quickly. When they passed me, I also passed them.

 

Small companies

The small company for the second interview, observed before entering the door, the office did not turn on the lights, and it looked a little dark from the corridor. At that time, several people were sitting at the workstations, some were playing with their mobile phones, and some were working, giving people a lazy feeling. After I went in, a backend interviewed me and asked you to use vue? I said yes, let's briefly introduce the project. Afterwards, I turned on the computer and asked me the interview questions on Baidu. This is actually the first company I interviewed for. I think I am todomvc, the kind that writes only pages. Obviously I didn't answer anything, so I said ask me js, what's his answer to js? What I think in my heart is, what is there to ask about js? js is very important, isn't it? So he asked, let's talk about scope, closure, and prototype chain. I'm actually very angry. Isn't this man a hooligan? Is it okay to check the salary I want before asking? I said, I'm sorry, I didn't use it in my work, and I didn't delve into it. Then after I went back, I complained to the friends in the group, and I asked, why does this person always ask me about the framework, but js doesn't ask at all? My friend said not to go to this kind of company, the front end is just the workers on the assembly line as long as they can use the framework to make things.

medium company

Third, medium-sized companies, small blackboards, and those who are engaged in education, after going there, do interview questions first. The questions are as follows: (1) How to submit the post form? (2) Promise principle? Does ajax in jquery return promise? (3) How to get UA? (4) postion attribute? What is the difference between absolute and relative? (5) What is the difference between transition and transition in CSS3?

The questions are difficult or easy, the interviewer's level is not bad, a project manager and a front-end interview together. Then I asked about the part of the project I was responsible for and the technology stack. The working atmosphere is great, but since I have two years of experience (one and a half years of internship), I feel that the question is a bit deep. Needless to say, this company definitely did not want me. Let me talk about my level again, I think my level is average, the kind of todomvc. The only advantage is that the English is not bad, and the reading of CET-6 is 180, so the general documents can be understood.

Fourth, the company that is about to go public, the parent company has already gone public, the salary is 17 new, and the salary is adjusted twice a year. This company is an e-commerce company. On the one hand, I chatted casually, although the technology was flawed, but my English was good and I worked hard to match the company atmosphere, so I entered the second-face personnel. The focus is on the next three sides, the three sides are technical bosses, and the questions asked are not something that I, a fresh graduate, can bear. Ask, have you read the Vue source code? I said that I need to change the source code for what? Then ask me, do you know the restful protocol specification? How to get it? Then ask how many modes js has to create objects? To be honest, I don't know these things, because once I say yes, I have to reveal my secrets in a few words, and examine the breadth and depth of technical aspects in three aspects. I have neither. Summary: You can’t stop at nothing in learning. Don’t think that the interviewer will be misjudged, personnel and technical aspects will be misjudged. You need to accumulate more at ordinary times, not only in depth, but also in the breadth of technical aspects.

After going through interviews with the above 7 companies, the first 6 companies stayed in the first round of tours. I was on-the-job and asked for leave to go out for interviews. I interviewed two or three companies a day. To be honest, Shanghai is so big that my body can’t bear it. In those few days when I was particularly tired, my body and mind suffered a double blow. But it still hurts,

Summarize the interview

Summarize the interview. As follows: (1) The foundation is not solid. I only do my job well at work, and go back to work. However, the foundation cannot be improved at once, so I make a long-term plan and be taught by my seniors. I have to go through the high level several times when going out for interview , read more books, code more. (2) At the beginning of the interview, I didn’t know the interview routines, one was written or technical, the other was personnel, the third was boss, the depth and breadth of technology, and personal career planning, etc. Be sure to prepare for the written test, go through the written test questions on the Internet, and memorize what should be memorized. (3) Do not ignore the personnel aspect! ! The following will talk about how many times I have been cheated by career planning! (4) Summarize the interview questions, record them, and learn. And when it comes to technical aspects, practice guiding the interviewer closer to the field you know. If you follow the interviewer to ask, you will definitely ask what you don't know. (5) MOOC has a skill that is necessary for front-end job hopping. I can't remember the name, but the content is great, and it talks about classic interview questions.

After two weeks of rest, all interviews were rejected, and I went home to read books and code after get off work. In order to have enough time for interviews, I resigned at the end of March. Yes, it was a bare resignation. Then plan to interview a family one day. Write 1 year of work experience, because I think it is too difficult to ask for two years, and one year should be okay. Two years will require you to understand the three mountains of js.

Mainly talk about several companies that interviewed after resignation. One is to inform the special page technical support. It took less than a month for the foreign company to go through the process and go to the interview. I had a good chat before the phone interview, but the conversation about the career plan collapsed. I asked if I had a career plan? I said yes, I was too honest to be a product manager in 3 years, and then people said: Our job is quite different from that of a product manager, no matter what I say, there is no more.

One is doing the Internet of Things, in Zhangjiang Hi-Tech, one side is okay, and asked me what I do in the project, I am in charge of page login, personal center, and using echarts to make score pages, etc. Can you take charge of the project alone? I said it depends on the size of the project. One person used to be in charge of the company's official website, but the software system involved hundreds of pages, requiring the full cooperation of the front end. Ask me to build a vue project? In fact, I don't know how to do it, but I said that I have been watching it recently, and it can be used to build small projects with webpack. Later, we talked about salary. This salary structure is different from other companies and is more complicated. It is recommended that small partners stay away from companies with complicated salary distribution. Afterwards, the product manager was on the other side. Because the product was on a business trip, they chatted on the phone. They also talked about career planning. The chat went well. Received the offer the next day. With the offer in hand, I have more confidence in interviewing other companies.

Let me focus on the next company, which is engaged in high-end Internet education and training. But I didn't know it before, and I went to the interview without fear. On the one hand, a product manager and front-end technology leader first introduced the project. The front-end asked me some Vue-related questions about the project, because I prepared some knowledge about local storage after personal account login, how to verify and use the personal center form submission The difference between post and get.

 

Interview questions:

The next product asked me:

(1) You said that your previous company was responsible for part of the software testing, which ones? Back to: Responsible for black box testing, mainly process and function, part of which is page response, check the network to see the interface response time. Or some tools to help.

(2) What should you do if the product manager raises a demand that you cannot fulfill? Answer: You can do what you want. They laughed and said that you should persuade him, and I said yes, that is my inner monologue. I usually refute it, but I will come up with arguments to refute it from various aspects. For example, when I was in charge of the official website before, I separated the original mixed Developed a jsp page and added new functions. The design said to be a message board, or the message will be displayed at the bottom of the input, because the original message board does not have this function.

I said at the time, first, message boards are easy to say and there are simple ways to do it, but there are also difficult ways to do it. If you don’t know the design, you must look the best, so I said it can be done, but you go to the boss and tell the time I can't finish the official website on time.

Second, what our official website is doing is corporate display, not social networking. You are digressing.

Third, since I want to be a message board, if my message is not good for the company, should the front end judge the content or you stay in front of the database and delete the data one by one? If it is a front-end judgment, how can I judge? Can you determine which characters cannot be entered?

Fourth, if there is a malicious attack, brushing messages, malicious flooding, and increasing server load, will you be responsible? After speaking, he shut up. I gave another example. I said that sometimes the product manager has a big brain and some things can be done, but the performance is not good and it is troublesome to do. I will come up with other methods and convince him that there are many ways to solve the problem. , but I have to find one that I can do and is simple.

(3) What should you do if you don’t know how to do it at work? Who should you ask? Answer, you can throw the question in the community, but this method is not necessarily real-time, so I will put the question in the WeChat exchange group, there are 260 people, and everyone is very active. Continue to ask about the exchange group. I said it is the reading group of the official account created by Lao Shang. Forgive me for advertising, but I don’t have any kickbacks, just telling the truth. Keep chasing, what's the name of that official account? It's called the web front-end classroom. It is estimated that asking me about this question is to check whether I am real and not just made up. (4) How to maintain continuous learning? What methods do you use? Answer: I read books and watched videos, but I think it is better to learn from the teacher, so I signed up for Laoshang's on-the-job front-end course twice a week. At the same time, China MOOC Network also takes some courses as auxiliary learning.

two sides

Next came the second face, which lasted for an hour and a half! Later I found out that the interviewer on the second side is a master in C++ and a serial entrepreneur, Mr. Li. The specific name is not mentioned.

Here are the main questions:

(1) Your career plan is to make products in three years, why not directly find a job related to product managers?

Answer: First, I think the front end is closest to the user and can accumulate user experience.

Second, a product manager who does not understand technology is not a good product manager.

Third, I currently do not have the necessary skills for a product manager, so I am not suitable for finding a job.

Fourth, before I was an intern at the company and rotated in the company, I felt like a content porter when I was doing operations, and I couldn’t do the back-end. I really liked the product and started the front-end when I found the front-end very interesting.

Fifth, it is possible to go from difficult to simple, but it is not easy to go from simple to difficult, so I chose the front end for the product. You can calm down and learn technology. With limited energy, you can't do front-end work and consider products at the same time. At least there are no product-related plans at the moment.

(2) How was the technology in the previous team? Answer: Because the first six chapters of Elevation are enough for the work content of my previous job, and no one told me what to learn, so I had no direction in those few months, which was a waste. The technology is at the middle level in the team, after all, It's also there.

(3) Is the reason for your mediocre technology because you pay too much attention to the product? I said that if this is the case, I will not pass the probationary period, and we use jira to count work efficiency, and each task must be quantified to man-hours, so there is no need to pay too much attention, and I talked about the process, I pay attention The product lies in the period when the designer has completed the prototype and handed it to the front-end. I went back and forth several times to see if there were any logical errors or design loopholes.

(4) What about the output? Do you have a personal website? In fact, there are not many articles, I am a rookie. But I answer: there is a personal blog, which is a good way to record other people's codecademy exercises, and there is github, which records personal small demos.

(5) What advantages do you have? Don’t be shy during the interview. I replied: If the front-end is product-conscious, it can be divided into two types. One can be made for any prototype, and if there is a problem, it can be thrown out. The other is what I thought before I did it. A little more, to avoid finding that it is different from what the product wants after finishing. Second, the English is not bad, you can read the source document (I brag). Third, cheerful and easy to communicate.

(7) Have you ever learned C++? I was telling the truth at the time, I said that I had studied for half a semester, but I don't remember much. Otherwise, if you say yes, they will knock me out with just a few words.

(8) What books have you read about the product? The Kevin Kelly trilogy, Top of the Wave, and Tipping Point were read in college, so I didn’t bother to read them.

(9) Why choose the front end?

(10) How to engage in the front end? Not to mention what I said above. Then say do you have any questions? I said what are you doing now? Mr. Li said lightly, I have been typing codes for more than ten years, and I am currently a product manager.

This interview lasted for two full hours. Start at 4 o'clock and leave at 6 o'clock. After that, I interviewed a company with more than 100 people.

Summarize:

To sum up this job search, I submitted a total of 60 resumes, and the time span was 1 month. I received interview invitations from 13 companies, interviewed for 7 days, and interviewed about 10 companies. The first 6 companies took a round tour and entered from the 7th company. After the retest, after 2 weeks of rest, I met with 3 companies and received 2 offers. After selection, I joined the Internet education, why? The internal account can watch all the learning videos for free, and the benefits are hidden, hahaha. End.

Knowing yourself and finding the right direction is half the battle. It's not just technology but also attitude potential, right? Write down the number of years realistically, and you can’t eat hot tofu in a hurry; tell the interviewer that I’m sorry I can’t, not that I forgot, I don’t remember, I can’t remember, etc. From the confusion and self-denial of the first interview, to the hard work of various types of companies to learn to see the direction, I have gained a lot. I deeply feel that if I can find the right direction, go deep into the problems encountered, think and settle, the interview will be better. It will be much calmer. After all, the calmness and calmness of the interview comes from the usual steady progress.

Guess you like

Origin blog.csdn.net/MXB_1220/article/details/132030184