Programmers, network engineers, database administrators and other people constitute the main body of the IT Republic. This class is the reappearance of the industrial army of the 19th century in the 21st century, but the work part has changed from the body to the brain. Increasing unabated. In the smoky sea of program codes and the labyrinth of network software and hardware, they carried heavy burdens like porters more than two hundred years ago, and rushed through the night like prostitutes. With the rapid development of information technology, except for the lucky ones who climbed to the management level, the knowledge and skills of other people quickly become obsolete. New IT graduates are coming in groups like hungry termites, and the old people (in fact, not old, most of them) In their early thirties) were squeezed aside, replaced and abandoned, but the newcomers were not at all proud. This is also the prospect that most of them are not far away... This class is called the technical proletariat.
Do you feel the writing is true? In fact, looking back and thinking about it, with the development of the times, from the Internet to the mobile Internet to the so-called intelligent era of artificial intelligence, big data, cloud computing, the world may indeed need more and more programmers, and programmers are also more and more. The more, and then think about our own work, copying and pasting repeatedly every day, it is indeed like a porter on the dock, doing hard work every day, and this suffering is the suffering of the brain, not the suffering of the body.
And the sorrow we Android programmers face is not only the mid-life crisis, but the update iteration of information technology. Suddenly found that the industry has reduced Android development positions, and we are about to be unemployed!
1. Resume
If you think of yourself as a product, then your resume is the specification.
Writing a resume may seem simple, but it is not easy to write well. A good resume can help you stand out among a bunch of resumes.
I wrote an article on resume writing skills before. For the convenience of new readers, this time I condensed the essence of that article and added some new content. Old readers who have read the previous article can quickly browse this part.
1.1 Personal photos
The debate about whether to put photos in your resume has never stopped. Although programmers don't rely on their faces to eat, I still tend to put photos.
Usually when I look at my resume, if I see a picture of a young man very energetic, I might think: the code he wrote will probably be neat.
That's right, a photo is the first impression others have of you. Normal people like beautiful things. A photo that makes people look comfortable and even shines in front of you can increase the goodwill of others towards you.
So I personally suggest that as long as you look worthy of the audience, you can put photos in your resume, which can beautify your face appropriately, but don't make it a "fake".
1.2 Basic information
Basic personal information, such as name, education, email address, phone number, etc., just write this part normally, I just remind everyone not to miss the following bonus items in the eyes of interviewers.
- Most people only write their academic qualifications in their personal information, not the college they graduated from. If your school is famous, you can write your graduate school in this section.
- If you have a blog, Github, or official account related to your post, don't hesitate to write it here, it can appear that you love to learn, summarize and share.
- Let's talk about another technique. Take the official account as an example. If you are more productive, add a sentence after the official account name, for example: 50 original technical articles. Don't underestimate this explanation, it can be the icing on the cake.
1.3 Self-evaluation
Self-evaluation must take time to write carefully!
This is a comprehensive explanation of yourself, which is to re-understand yourself and let the other party know your strengths, goals, and values. And you don't write it for nothing, you can also use your self-introduction in the interview process in the future.
I see that most of the self-evaluation is basically like "bearing hardships and standing hard work, strong sense of responsibility, hard work, strong learning ability, team spirit...balabalabala".
Hey, I really suspect that this was a search on the Internet and then combined these words again. It's really uninteresting to read this kind of text, it's not convincing, anyone can write it like that. Can't you have more examples and figures?
Look at a few positive sentences:
- 7 years of experience in Java development and 5 years of experience in the Internet industry. He believes he has reached the level of a senior engineer and hopes to grow into an architect in the future. (Have goals and plans)
- A loyal fan of Minjian development and a practitioner of unit test-driven development, he will take the initiative to refactor the code and has a code cleanliness. (Have good coding habits)
- I love to read technical books. I read about 10 books a year. I recently read Domain Driven Design and Enterprise Application Architecture Mode. I love learning. I have completed 5 paid courses in geek time this year. (Love reading and learning)
- 2 years of team management experience, the team size is 15 people, the team atmosphere is harmonious, and the turnover rate of members is much lower than the company's average. Was selected as the company's outstanding team. (The team brought it pretty well)
1.4 Skill level
Once in an interview, the other party's resume wrote "Proficient in Spring, Redis...", which probably listed a long list of more than a dozen proficiencies. As a result, when I asked in the interview, I found that it was too watery. You have redefined proficiency.
Familiar, master, and proficient in these words, there is no uniform standard, don't write silly, don't make people think you are bragging.
If you are a newcomer and you don’t know what to do, I suggest you write this:
Mastering skills:
Development languages: xxx, xxx, xxx
Back-end framework: xxx, xxx, xxx
Database: xxx, xxx, xxx
Old programmers, write as long as you think you can write proficiently. If you have a lot of skills, don't forget to highlight the key points. What is the point? 1. Skills that are clearly required by the job and have a high degree of matching. 2. Skills with bright spots, such as: 3 years of experience in AAA framework; read BBB source code; published 5 CCC-related articles.
1.5 Project experience
The project experience is the key question in the interview process. When you write, pay attention to the following points:
- Project experience is two words here, project and experience. Most people only write project and ignore experience. Experience is what you did, how you did it, and the result of doing it. For example: Which parts of the project did you do? Are you a core person? Do it yourself, or lead the team? What's your growth after doing it? What happens after the project is delivered?
- If you have done a lot of projects, you must control the number of projects, otherwise the interviewer will not see the main point if you write a few pages of projects. Don't write on projects that are too early or too small. Choose large-scale ones, choose more for your participation, and choose ones that are more suitable for your position.
- Don't write low-recognition English abbreviations for the project name. You can understand it even if you write an ERP. If you write an SCF, it seems very foreign, but the ghost knows what it means.
1.6 Resume template
The resume template is simple and generous.
I have seen so many resumes, some of which are too fancy, and some have exaggerated covers. I want to close this kind of resume as soon as I open it.
The original intention of job seekers is to make their resumes look better and different from other resumes, but sometimes they become zuo when they show off too much. Especially newcomers, it is easy to exert too much effort in this regard.
study Exchange
If you feel that your learning efficiency is low and you lack correct guidance, you can join a technical circle with rich resources and a strong learning atmosphere to learn and communicate together !
There are many first-line technical experts in the group, as well as code farmers who are working in small factories or outsourcing companies. We are committed to creating an equal and high-quality Android communication circle. It may not be possible to make everyone's technology advance by leaps and bounds in the short term. In the long run, vision, pattern, and long-term development direction are the most important.
The 35-year-old middle-aged crisis is mostly caused by being led by short-term interests and squeezing out the value prematurely. If you can establish a correct long-term career plan from the beginning. After 35, you will only be more valuable than those around you.
The pattern and the direction of long-term development are the most important.
The 35-year-old middle-aged crisis is mostly caused by being led by short-term interests and squeezing out the value prematurely. If you can establish a correct long-term career plan from the beginning. After 35, you will only be more valuable than those around you.