I have interviewed at least dozens of enterprises in China, first-line to second-line, and experienced all kinds of strange people,' technical manager' and' HR' ...
Think of many interesting recruitment companies, and I will always talk to you about many things during the interview. The process is short, but there is a lot of content and information.
This was especially true in a recent interview in Australia. The technical director asked me, what do you usually use as the development front end? ...
Novices, or people who have no project experience, usually say, I use jQuery, AngularJS and backbone. ...
Such an answer will interest the questioner. How to develop the front-end itself is a very general topic, from computers to mobile terminals, many things can be said.
This kind of question is actually easy to answer, but if you want to answer it well, you need a complete knowledge system to support it. You can refer to various front-end skill trees on the Internet.
I can probably answer this question. Generally, when writing a website, I will use the common MVC structure, and the ui will use Boostrap, Amazi UI and so on.
Angular JS, JQuery and ReactJS have been used on JS. Some special animation effects make use of the particle characteristics of canvas.
Background, all kinds of background languages, corresponding template grammar, there are a lot of grammar sugar, which is generally used to look up, and I have done some.
There are also code packaging tools. Testing, debugging, IDE, etc. You can say whatever you want. ......
It will be over in about two or three minutes here, and basically the technical interview has passed. After all, it is to write code. If you understand it, it is most important to have the habit of thinking logic.
Many details can be perfected in Google. After a long time, I naturally encountered many problems. Most people can say these words systematically, and naturally they understand a lot.
Big companies like to ask some so-called tricky questions in interviews. Test whether a person doesn't want to know a lot, but doesn't know why.
For example, you will ask how to reuse a long list in a web page to avoid taking up too much memory, whether you have encountered a performance bottleneck, and whether the comparison algorithm of ReactJS has been understood. How is the reading level of source code?
Speaking of which, I can't help but vomit, damn it, what should I do if I know? Every day, I write low-quality code that is constantly asked by the product manager to be deleted. ...
Instead of just writing a pixel-by-pixel code according to the design draft every day, or doing all kinds of so-called' exquisite' animations that are not commonly used in the market, be an overtime dog that goes against the demand. It's all work
The above questions are generally difficult for me, haha, because I often read many people's blogs, and they will all mention that I have done some search.
This is an ordinary, three-year-old engineer position, technical interview process, and something to answer.
Although it doesn't take a while to do it, it can be done right away. But it's still easy. Many people do it step by step. Even after five years. ...
It is also easy to do this, mainly by thinking more, reading more helpful documents and reading more codes. For example, how programmers practice books.
It is not difficult to master the thinking ability of the system, but it is rare to make persistent improvement and modification. Always keep the original pursuit.
Next, the five-year interview of senior technicians involves the design of architecture. I'm not a senior architect ... and I can't answer this question.
Push in here, better posture, Github. Many people are not good at expressing themselves. Just show them the code.
This is good, too. It is also a very good choice to maintain github by yourself, open up some small projects regularly and maintain some projects by yourself. As long as you look at the code style you write, you can express it well.
When I came to Australia, when I was overseas, I put github on my resume during the interview because my spoken English was not particularly CET-6, and the effect was very good. Looking for a job on the first day, interviewing the next morning, and joining in the afternoon.
The land here is vast and sparsely populated ... my luck is not generally good, but it is still a local listed company. ...
Once again, spit out the unfair treatment that may exist in the interview process. May be rejected, not necessarily because of ability, but also because of salary.
I still remember when I graduated a few years ago, I was asked by HR about my first job. Are there any requirements? I said the salary can't be less than 5K.
People began to teach me the truth of being a man. Young people don't aim too high, xxx, and then sent me an offer with a salary of 4500. I hope I can think about it.
Then there is an interview with a big first-tier company. After the technical interview, HR wanted to lower his salary and kept saying how good his company was. Yes, it's' Suning' _ _
"We generally only need 985,265,438+065,438+065,438+0, and you are just an ordinary one, which is already a special xxx ..."
If it is not suitable, just refuse it directly. Why bother others to highlight the advantages of big companies? But sister HR is also for the benefit of the company, so there is nothing to say.
To tell the truth, the technical level inside is really not so good. I see that Suning's iOS level is also very general ... this is not a particularly good company ... and it is not particularly good for technicians. ...
I work in the back end ... I don't usually write in the front end ... but the work here generally requires everything to be written, so I asked the above questions.
After asking, he didn't ask me back-end questions, but chatted with me about life. Do you usually cook? Do you have a girlfriend?
Anyway, spending more time to accumulate, think more and do more meaningful things will always make your career more and more smooth.
So is life. Life is short.
original author