A qualified Java programmer must have experienced different projects walking in the industry technology front line, sometimes in addition to learning from others, but also need to be promoted by the environment, the right time and the right place, Java programmers can go further in the career path.

First: the nature of work

The most important purpose of work is to accumulate money. Making money comes in at least four forms:

1. Helping others earn money

2. Make money for yourself (SOHO)

3) Hire others to make money (business owner)

4. Let your money work (invest)

The first has the lowest threshold and risk. And apply for a job is just our own resources and ability is not enough to enter after several forms of money, by selling their labor ability for resources of the stage behavior.

Second: about job-hopping

Job-hopping is definitely not a strange word for IT people, almost all of them have practiced IT. First of all, I would like to emphasize that job-hopping is not bad, but frequent job-hopping is not good.

Job hopping is mandatory and encouraged in the first 4 years (2-3 companies recommended); Each company’s focus on technology is different, the development process control is not the same, the need for technical talent is not the same; Outsourcing companies, for example, want a code geek (I love hiring people who have done outsourcing, and feel that many people who have worked in outsourcing companies are very efficient); Small business companies, looking for a versatile programmer (can design and analyze, can write code, can deploy); Large companies want a solid technical, potential person (good English, good understanding, solid Java foundation); If you stay with a company long enough, you are likely to get stuck in a rut, and if you leave the company, your job search can sometimes hit a wall. It’s good for programmers to experience both companies! And I also feel that every time I look for a job, I am forcing myself to learn something.

And the key is, a job-hopping, the salary is higher —– a lot of people job-hopping are dissatisfied with the current salary.

Third: the significance of job-hopping

Job-hopping is actually a way for us to adjust ourselves in the form of part-time jobs to make money. By reasonably job-hopping, we can find the best match between market demand and self-realization, so as to achieve a good harvest in terms of money and growth. “Market needs” describes the employees the organization craves, “self-actualization” describes the life you want; When they overlap, the dream becomes reality.

Fourth: the principle of job-hopping

Never jump ship because the present is bad, but because the future is better. It’s the only way to keep going up.

Fifth: When is the best time to move on?

1. Think you’re the best programmer in the company and have nothing to learn from.

At this point, many people may be too confident, must treat their real strength correctly, do not overestimate their own. If that’s what you think, and you’re the best, then you can consider it. The other thing is to know that you’re not the best, that there are a lot of people in the company to learn from, and if they’re all busy, and no one wants to share their knowledge with you, and no one wants to help you, then you can make another plan.

2. If you don’t learn new skills and use the same old ones, you will become obsolete.

If you continue to develop with outdated skills, you will be eliminated from the market. There may be jobs that still use early versions of the language so you can continue to work, but you have to understand that being in a stagnant technology environment is far worse than working for a company that is constantly improving.

3. If you haven’t been making progress in the company

If you’ve been at a company for a long time and you don’t have a successful project, it’s not necessarily your fault. It could be because the company is dragging its feet, or whatever. If you don’t see a future for yourself in the coming months, this is a good time to consider staying with the company.

4. You’re being paid less and have less room for advancement than your peers.

Unless it’s below the market salary, for example, the company has a lot of good people who are willing to help you, and they can learn a lot of skills. If the salary is low and there’s nothing else to compensate for it, then it’s time to reconsider.

5. If your company treats you like dirt and doesn’t allow you to perform or advance.

If that’s the case, then the company doesn’t care about you, you’re not important, you’re expendable. They don’t think it’s worth the long-term investment in your body, so you can look for your new job right now.

6. You find that you’ve been at the company a long time, and your skills and materials haven’t changed much.

Every day is the same work, always only responsible for some trivial things, or really involved in a big project only let you take charge of the irrelevant part, such a long run will make you lose morale, become depressed. And pay has long been disappointing, so why should you stay?

7. You don’t have the same passion

Software development isn’t as fun as some people think. If your current job isn’t worth it and you have the opportunity to take on a new project to get motivated, you might as well change the status quo and work for a company that does.

No. 6: Pace and roadmap

For example, if the ultimate goal is a CTO, its roadmap might be:

Fresh Graduate -→ Junior Programmer → Team supervisor → Department Manager → Director →CTO

Then we will set a compliance capability and a reference time for each node. When our ability has begun to be competent for the next node, we will start to look for relevant opportunities, the best is to enter the next node in the current company, if the current company cannot provide, then we need to move forward by changing companies.

Of course, the roadmap can be adjusted, for example:

Fresh graduate → Junior Programmer → Team leader → CTO of startup company → CTO of Round B company → CTO of public company.

But no matter how you adjust, you should have a clear goal in your mind. We always consider other paths when the least risky path (such as our current company) for growth is not successful.

We are technical personnel, regardless of whether there is management ability or want to walk the management line, technology is the first, you think if a very poor technology leadership to you what you would think?

Seven: The seven core reasons for failing an interview

1. Ability is too high or too low for the position

It is normal to have no chance because of low ability, so will high ability also affect the recruitment? In fact, it depends on the stability and the needs of employing department leaders. Generally speaking, people with high ability have higher expectations for the position. Once the position can bring him little either in terms of salary or career growth, it is almost predictable to change jobs soon, and the long-term stability will be poor. And the demand of employing department leaders for the positions may not be too high, which is convenient for management and can be better cultivated. 51job.com user “Youran Xingyue” who has been working in HR for many years once mentioned: “Maybe the head of the department isn’t keen to find someone to share his responsibilities with and only needs an assistant, so the more perfect you are, the less likely the department will approve you.”

2. Past experience shows a tendency not to meet company expectations

Simply put, it’s a flaw in your past that doesn’t seem to have been completely erased and could affect your next job. Like to change jobs frequently, and still do; To take care of a family, it is difficult to take care of work; Entrepreneurial failure, the state has not been adjusted; Working years do not match the gold content of working experience; Job intentions are too confused, lack of career planning, etc.

3. Speech without focus

In other words, a lot of crap and nothing. If you can’t explain questions succinctly, the interviewer will wonder if you’re as sloppy as you are when you talk. So during the interview, you can ask the interviewer if you need to elaborate.

Explanation is also an art, the key is to identify the main points and drill down into detail if necessary. When it comes to business, think in terms of the business, without any technical jargon. Learn to explain problems in a clear and concise way. This is not a problem if you can keep the main idea in mind.

Too little and vague

Especially open-ended questions like, “Tell me about yourself” or “Tell me about a complex problem you’ve ever solved.”

The interviewer will assess your passion by your answers to these technical and non-technical questions. They will also judge your experience and abilities by simulating a team atmosphere and interacting with you.

If you can’t articulate the value your experience, accomplishments, and skills can bring to the organization, your competitiveness won’t work. So you need to be prepared for some of the most common open-ended questions and learn to sell yourself.

5. Not understanding basic technical issues

The interview is not a technical contest, and it’s not about who gets the most questions right, but there are some core “must know” Java and Web basics that you can’t miss. For example, for Java developers:

V does not know the difference between “==” and equals();

V does not know the convention when equals() and hashCode() methods are called implicitly;

V does not know OO concepts and design principles;

V does not handle multithreading well;

V does not know how to maintain state between HTTP client and server;

V can’t explain the high-level architecture of the application that you worked on;

V does not know SQL.

Can’t write simple code, can’t solve tough problems

As a developer, you should code for a given problem or situation based on your level of experience. Even if you don’t have a solution, you should share your ideas with the interviewer.

Of course this can be extremely nerve-racking during an interview, especially if time is limited, but you must remain calm and at least explain how you will attempt to solve the problem.

7. Bad manners and attitude

Be late, not appropriate dress, shaking hands shaking feet, without eye contact, too nervous, no questions, showed no interest in this job, “I know” arrogant attitude, belittle your present and former employers, irritable or depressed when technical problems, to find reasons not to accept his mistakes, a dispute with the interviewer, Poor body language, going with the flow without an opinion, being too mechanical, lying, being too loud to be a good listener, etc.

Eighth: good state of mind and body

Programmers must be responsible! This is very important. When encountering problems, we should not just kick the ball, but communicate with others seriously, put forward our own opinions, and contact customers to solve the problems. The technical problem is not a problem, it can always be solved, but the demand problem, we must figure out! Once requirements go wrong, a project can be delayed or fail. Programmer’s sense of responsibility determines his growth, a responsible talent may become the backbone, so that leaders trust.

Secondly, it is able to withstand pressure, we all know programmers to work overtime, pressure, all problems must not easily give up, reasonable according to the ability to deal with!

The body is the capital of the revolution, programmer is especially important, sit in front of the computer every day, it is easy to get fat, become a pear figure, all more exercise!

To some extent, do not job-hopping, in a development prospects or happy work for a long time to stay, not with young people than enthusiasm, this time to be steady, in the company as a senior IT practitioner, help optimize procedures, analysis of needs, for the project to give advice to solve problems.

** Warm tip: ** Write more technical documentation

It is good to write more technical documents —– in fact, it is the summary and improvement of your work experience

A person who is willing to share his knowledge can improve through constant thinking, and writing documents is very rewarding.

Write in the last

Of course, the interview is indispensable to brush the interview real questions (why important should all know it)

The following is a small series engaged in Java development and after layer upon layer of sorting out the interview question, the public number to obtain

​

​

Well, today’s share is here first, remember to pay attention to xiaobian, do not get lost;

Three things to watch ❤️

= = = = = = = =

If you find this article helpful, I’d like to invite you to do three small favors for me:

Like, forward, have your “like and comment”, is the motivation of my creation.

Follow the public account “Java Doudi” to share original knowledge from time to time.

Also look forward to the follow-up article ing🚀