As a Java interviewer--talk about a year's interview summary __java Foundation

Since the end of the year, as a small and medium-sized (200-500) Person of the Internet company's little Java technology interviewer.

Nearly 200 job seekers have been interviewed, as a programmer with a less technical depth. I'm still being mined.

Interviewer I will not say more, the forest is big what birds have, we all understand.

Briefly talk about some of the questions I often ask, and the purpose:

PS: I am not Daniel, is the contact with a wide range of, how many can chatter on two words ~

In addition, most of my face is within 3 years of working experience.

The mood is not very good, the writing is also very rotten, everybody when disperses the entertainment and entertainment to forget.

1. Do you do all the backstage at the front desk? 10 points

This is generally my first question, more than 90% of people will answer: "Do, backstage a little more, the front desk less"

This is not the answer I want, ghosts know how many programmers have to deal with the front desk, not to mention the background.

Met a smart person, he is so answer: the front desk js write more proficient, HTML frame template can also build a very neat and beautiful, but the special effects ability is worse

I don't want to talk about it too much, but I don't cut the score.

2. Business, what is business, and why transaction 10 points

Most interviewers will cite a variety of examples (such as bank savings, the most) to illustrate the problem, in fact they all understand.

But that's not the answer I'm looking for, and the only answer I'm looking for is "to ensure consistency and completeness of data", but only about 5% of people answer it.

This question may be about the analytical skills of the participants, the ability to summarize their language, and their understanding of the device.

Do not give a minus points, for example not to add points

3. Aspect oriented (AOP), what is the principle of 10 points

That's the mastery of the skill level.

Most of them are examples, what to find intermediary ah, in fact, is to cover up their understanding of a little implementation logic, but do not know how to achieve the source code.

But there is a Couba to the principle of the agency to speak out, very good.

Should not be reduced, give examples without points, the principle of double points.

4. How to communicate 10 points between two projects

A very basic question, the answer is a point, indicating that you have contacted or learned about the network

5. On the basis of the last question, how to solve the garbled, utf-8 and GBK can be directly converted 10 points

Most of the candidates here are basically starting to get into this nonsense. There is said to declare string code received, there are said to change the project code, a variety of various.

Furthermore, Utf-8 and GBK can be directly converted ...

The direct explanation is that they have not encountered such problems at all and do not understand the code.

You should not lose points, nonsense minus points, double the correct answer.

6. Brief description of the principle of a technology or design pattern 20 points

This is almost a split, but 90% of the people can not answer. I'm puzzled.

You should not lose points, you should add points

--------------------------------------------------------------------------------------------------------------- --------------

After asking these questions, I can probably judge the technical level of the candidate,

Basically over 50 points, and to meet the requirements of the second interview.

Although it does not explain the scope and depth of the job seeker's mastery of technology.

But at least it means he's a man of interest to programmers.

Because most of my interview is 3 years of work experience, so did not ask a few and Java not much contact with the problem

Occasionally come across some Couba, I will discuss with them about caching, database tuning, large data processing, concurrency issues.

The answer is to add points, can not answer I will guide, and then let them analyze their own program.

The basic thing here is to make sure that it is acceptable. The rest is about pay.

--------------------------------------------------------------------------------------------------------------- ---------------

Alas, actually wrote so much is want to grumble, noodles for two months, hundreds of people, only recruit to 2, 3 suitable.

Because my company recently developed relatively quickly, the project development cycle is relatively short, urgent need to come to the start.

But it was disappointing to have been in the interview for so long.

It feels like programmers are really going to love coding more and less.

The programmer is moving closer to the taxi Driver---driving (development module)-[process? What is a process.] -Send you to the place (complete the task)-more money.

Take the project with you and not be taken seriously by the leader.

Pay less than the new rookie. The heart is not the taste.

So come to grumble, everybody is lenient.

Other job seekers peer, hope to exercise their eloquence and technology more.

Meeting

Work hard.