Hi everyone, and welcome to the Stop Refactoring channel.
In this issue, we share the relevant experience of programmer interviews .
It may be due to the peak of resignation in March, or the reason why graduates are preparing to find a job. Recently, some friends asked us about our interview experience.
The questions are varied:
Always nervous about interviews?
How to introduce projects and work experience?
How do you answer technical questions that you don't know?
Whether to choose a large company or a small company and so on.
Let me explain here first. In the following, we will analyze the reasons behind the problems and give some suggestions based on specific problems, but they may not be suitable for all scenarios and different people. If you have different experiences or ideas, please discuss them in the comment area.
Interview mentality
Many people will be nervous during interviews, especially programmers or students who have just started working, or when they want this job very much.
This kind of tension is difficult to eliminate, but in general, this tension will gradually disappear as long as the number of interviews increases , so it is necessary to submit more resumes and interview more times.
But rather than nervousness, we think that the mentality of the interview is more important. Many people think that they are being observed during the interview, and they want to perform better in order to be recognized.
There are often stories about being hired by a well-known company after picking up a piece of rubbish during the interview, or that a certain action during the interview will be seen by the interviewer to add points, and so on. These stories or notes are actually useless, and the interviewer is generally not so boring . After all, the interviewer still has his own job and is eager to go back to it.
In fact, the interview is an equal two-way selection process . The company wants to invite the right people, and you also want to find the right company.
Therefore, you can answer according to your real thoughts and experiences during the interview , and there is no need to carefully prepare or arrange some unreal experiences. After all, even if you cheat the interview, it will be difficult to pass the probationary period, which will waste more time.
How to introduce projects and work experience?
It is best to give a short and key introduction , such as participating in a mall APP project last year, responsible for the back-end development of the shopping cart module, what projects you participated in before, what you were responsible for, etc.
If you are a graduate, what competitions, small projects you participated in, what your graduation project is, etc. When the interviewer is more interested in which part , he will explain it in detail. Of course, it does not need to be particularly detailed, just pick the key points.
Why is this? Because it can reflect your communication skills .
Although it is written on the resume, except that the interviewer generally does not read the resume carefully, the interviewer can understand your communication skills through your introduction. Even for software development, communication skills are very important, which will virtually increase a lot of project costs.
How to answer technical questions that you don't know
The interviewer usually asks some in-depth technical questions. It is inevitable that there will be some questions that you don’t know, or situations that you can’t remember. In fact, don’t panic, because panic is useless and it’s too late to learn now.
For example, if the interviewer asks if you have used Elastic Search, you may not have heard of it.
At this time, it is enough to directly tell the real situation . After all, if you don't know how to pretend to understand, it will often be self-defeating.
Of course, it is also a good way to ask for advice humbly at this time, but a better way is to extend it to similar problems you know.
If you can simply ask about the application scenario of Elastic Search, the interviewer may say that it is a full-text search database.
When you hear the word database, you can take the initiative to share some learning or problem-solving experience . For example, although I have never used Elastic Search, I have used MySQL database. The database stores data, but the operation methods and application scenarios are endless. Same, so Elastic Search should also be quick to learn.
Although this can turn problems that you don't know into a springboard for active presentation, it is actually very difficult to achieve. After all, this is a negotiation skill, and it is often difficult for you to calm down.
Even if you can't do it , at least you must understand that work is not an exam. Of course, the more skills you have, the better, but what is more important is the ability to learn, the ability to learn quickly as needed .
Engineers in the software industry need to keep learning, and technical problems that they will not or have never encountered will accompany their entire career.
Therefore, for technical problems that you don’t know, there is no need or need to feel that you are not good enough , or that you can’t keep up with the industry.
deep problem solving process
Sometimes, the interviewer will ask you to talk about the more profound BUG or problem-solving process. We have also asked many interviewers this question, but there is a high probability that the interviewers are ignorant. In fact, it is no wonder, who will remember these solutions? What about the process of the problem.
But we still recommend that you prepare at least one problem-solving process on your own before the interview , it doesn't matter how simple the problem is,
The process of solving problems alone can not only reflect the authenticity of participating in the project, but more importantly, it can reflect the ability to solve problems alone.
Because work requires you to be responsible for a task independently, the ability to solve problems independently is very important
Whether to choose a large company or a small company
For the vast majority of cases, it is of course a large company, the bigger the better . If there are barriers to education and other factors, you can try to find channels such as expatriation.
Although there will be more excellent people in large companies, the more difficult it will be to compete for a position, your job may even be boring, and you may not make progress after working for a few years.
But a large company can at least broaden your horizons , understand the practices of top companies in the industry, and participate in larger projects. If you are good enough, joining a big company is also the path to career growth with the least risk.
More importantly, big companies can guarantee your income . This income may not necessarily be the highest offer, but generally they will not owe wages or make you work overtime inhumanely.
Although there are news of sudden deaths of employees of some large software companies, there are actually more small companies in arrears of wages and working overtime. It's just that it's too common to be called news.
Of course, small companies also have advantages. Your work may be more challenging and fulfilling . Maybe this small company is a unicorn, and your efforts may be extremely exaggerated.
But we still recommend not to choose a small company at least in the first few years when you start working , because you don’t have much knowledge about the industry and your ability to judge is insufficient . Many times you will be overwhelmed by the enthusiasm of others.
Although we are also a small company, we also hope to recruit high-quality and low-cost mobile phones, but we still want to give our most sincere suggestions.
Summarize
The above are some of the interview experiences we shared. Although some skills will be involved, we hope that you can understand the core competencies of this industry, such as communication skills, on-demand learning skills, and the ability to solve problems alone.
Because any company's employment cannot guarantee your smooth career. After all, you need to be hardworking yourself, and if you don't match your morality, there will be disasters.