Today I will tell you one of the most concerned issues we usually care about, that is, why no one reads the resume you write after you submit it! Always sink into the sea! I invested hundreds of resumes on boss direct recruitment, and a large number of them have been read, but no one paid attention to you? Have you encountered many brothers?
It doesn’t matter, it’s all a trivial matter. A strong warrior must be able to face the bleak life. Today I will tell you the story behind the resume you wrote.
Today we will use a unique perspective to analyze a resume that java programmers often write, that is, gradually expand and disassemble a resume, and then examine every part of the resume from the perspective of the interviewer, so that you know what the interviewer feels when he sees your resume.
At the same time, we will give some resume optimization tips and key points to help you modify your resume better and make the interviewer shine!
First, let's take a look at a Java engineer's resume. The part that first caught the interviewer's eye is the professional and technical ability part that everyone usually writes. I wrote a section of the most common professional ability part for you here. Let's take a look:
Professional and technical ability
1, familiar with java, javascript, go, familiar with tomcat, weblogic and other server deployment
2, familiar with react, htmlhtml, css, jquery etc. front-end technology
3. Proficient in mysql, oracle and other databases, proficient in sql statements
4. Familiar with rocketmq, redishml2, kafka, zookeeper and other technologies
5. Familiar with spring, spring mvc, mybatis and other frameworks
6. Familiar with
6. linux, maven, intellij idea, githml2 and other tools
I wonder what you think after reading the above resume content? To be honest, some brothers probably feel that their writing skills are not as comprehensive as above, and some may feel that it is OK, because what they usually write is similar to the one above.
Some brothers may snort coldly, what's the point, this is far worse than me, but is it really far worse than this brother? That may not be true, because basically if you often recruit people to receive resumes, the above professional ability description is the most common.
So what will the interviewer think at this time? Let me describe the interviewer's inner dynamics at this time: "What's this? I can't see any highlights. Be familiar with java? What is familiar with java? Anyone who has worked for 1 year should be familiar with java. What is familiar with javascript? That's the script language , which writes scripts on the page. This tomcat and weblogic are also worth mentioning? Do you want to deploy tomcat and do java development?
In addition, what's wrong with the front-ends of react, html, css, jquery? What I'm asking is Java, not a front-end. Can MySQL and oracle be proficient in writing sql statements? This is too funny. Which java engineer can't do mysql. Rocketmq, redis, kafka, zookeeper and other technologies can be used? Have you learned some demo? Or go deep into the underlying source code level, have any experience in production optimization? I don't understand, can't tell.
is familiar with spring, spring mvc, mybatis? Do you need to be familiar with this? Anyone who can go out of campus and can work for half a year to develop should basically be familiar with it. What's going on? There are also Linux, maven, intellectuallij idea, git Aren't these all daily use things? Why do you need to write here?
Alas, this big brother is not good. It feels like he knows some basic techniques, and then he can only write some crud. Otherwise, let's just forget it and change his resume and take a look.
Have you seen the psychological dynamics of the interviewer above? The description of professional abilities in the resume that you are used to is likely to be this view in the eyes of others. To sum up, there are a lot of things that all Java engineers can do, making people think that you only know some basic technology and can write a little simple crud.
Here I will tell you a very critical word: Highlights . What does
mean? Imagine that you are a Chinese teacher who corrects the composition and writes it all the same after you criticize it. How could you give you a high score? You have to write something that makes the teacher's eyes shine. The same applies to the resumes of
. You have similar resumes. You are similar to others. Now you are not easy to find jobs, and layoffs are everywhere. There are few job positions in various companies. There are many programmers looking for jobs. Your resume is released. An interviewer wants to recruit. He may have to read hundreds of resumes to slowly screen for a position. So how can such an ordinary resume attract his attention? Why can he get an interview opportunity?
So, when writing professional technical skills, you must highlight your own technical skills, or you have read some source codes, then you can write down your experience of source code, or you have studied some complex principles and high-level characteristics, or you have had some in-depth production practices and online tuning, these are all manifestations of your technical capabilities.
Below I will write you a demonstration of professional and technical capabilities:
1. Familiar with the Java programming language, especially the concurrent source code in JDK. In-depth research on the hardware principles, memory barriers, and thread pool performance tuning, in-depth research on the implementation principles of JVM in the kernel JVM, master the high-performance tuning skills of Java programs, have experience in performance optimization in code
2, familiar with MySQL The high availability, high concurrency, and massive data architecture design of database has an in-depth understanding of the principle of MySQL master-slave replication of the kernel. At the same time, it has in-depth research on the principles of MySQL kernel-level data writing and index query, has experienced performance tuning of MySQL tens of millions of online large tables, and has 250 million practical experience in implementing database sub-tables
3. It has in-depth research on the source code of RocketMQ kernel, and has studied the optimization of RocketMQ high throughput data writing, the principle of Broker's high concurrency writing, the Consumer-side message Pull model and the Rebalance model. At the same time, it has deployed and maintained RocketMQ deployed by 8 8-core 16G machines. Cluster, and have had experience in in-depth production parameter tuning
4,...
5,...
I wonder how you feel after reading the above professional technical description? Do you think it caught the interviewer's attention in an instant? Do you feel that if you are an interviewer, you really want to come and talk to this young man at once? That’s right, there are skills in writing resumes, and everyone is constantly learning and improving their own skills.
---------------------------------------------------------------------------------------------------------------------- -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- 10
Kafka Message Middleware Kernel Source Code Lecture (1 Yuan Exclusive)
12 Practical Cases Take You to Play Java Concurrent Programming (1 Yuan Exclusive)
Elasticsearch No-Basic Introduction to Mastery (1 Yuan Exclusive)
Practical Skills Based on ShardingSphere's Library and Table Practical Skills (1 Yuan Exclusive)
