If you were HR and faced with so many resumes of graduates on the table, what would you choose?
A senior HR manager once told me that in the recruitment season, the average reading time of a resume will not exceed 10 second!
So your resume should not be flashy, but concise and to the point, highlighting your professional advantages!
Computer skills are involved in the resume. If you are an admitted student, you can fill in the corresponding grades and relevant certificates obtained.
How do those students who have not taken the exam fill in?
1, skilled in using office software such as PPT, Word and Excel;
2. Fill in the software learned in this major. For example, accounting majors can apply for banks, and they can fill in proficient financial software;
As long as it is not a position with special needs for computers, the above two points can basically be met.
You can also write:
1, with the ability of word processing, mixed arrangement of pictures and texts and table operation in Windows environment;
2. Skillful use of office software such as WORD, EXCEL and PPT.
The above two points actually express that you can use computers and work, but it is more comfortable to write on a paper resume or application form. The subject can make a reference.
Resume guidance
As a web front-end engineer, if you want to find a well-paid job, you will always face various interviews, big and small. Among them, the key to a successful interview is an attractive resume.
In fact, technical positions generally pay more attention to work experience, and web front-end positions can be said to be more important in companies. When selecting a resume, hr usually looks at the candidate's project experience and work experience, which is enough to determine what level of web front-end engineer you are in hr's eyes.
So I'll show you a resume from the interviewer's point of view.
1. typographical error
Especially the spelling mistakes of technical vocabulary, such low-level mistakes appear on the resume, and the impression score is directly 0.
These are all real examples I encountered in the recruitment, and many of them have not been cut out. It's best not to make such low-level mistakes on your resume, which gives people the impression of two words: amateur.
Unless you are lucky, you meet an interviewer who also has no pursuit.
2. Invalid link
If the link can't be opened, say goodbye.
"When I glued the link, the project of my old club was still running normally, and it was none of my business to withdraw the project later."
The project belongs to my old employer, but my resume is my own. Check your resume before submitting it. Links that cannot be opened, like typos, will give others a feeling of being lax in doing things.
3. Resume photos
Attach a resume photo, and the resume will be more recognizable.
Yan value is also a kind of competitiveness. Being good-looking is God's reward. Oh no, it's just chasing food. Why fight for strength when you can eat by your face? It is necessary to properly "sell" the hue.
If you are not confident about your appearance, let the photo studio handle it for you in the back. It's really no good to turn on ps and handle it yourself. A better mental outlook can make the interviewer pay more attention to your resume, which is an advantage.
4. Typesetting is very important
Resume is your first face in the workplace. Starting from the face value, trapped in talent, without a good appearance, who cares about your inner beauty. Typesetting should be concise, neat and focused. Let the interviewer have a good reading experience, and it is convenient for you and him.
Good typesetting also means that you have good aesthetic ability, which is also the most scarce advantage of a front-end person. I like to cooperate with the front end with good aesthetic ability. There is always something that can't be covered in the design draft, and the front end needs to control the design itself.
Front-end people like to show off their skills, such as responsive design, mobile adaptation of different devices and other scenes, gradient and dynamic effect design. These details are often not reflected in the design draft, and are controlled by the front end itself, or simply described by the designer and then realized by the front end.
To put it bluntly, the boss is unwilling to spend money to recruit an interaction designer.
5. Personal website/technical blog
Personal website or technical blog is an absolute interview killer, which is the interviewer's favorite, and can better reflect your comprehensive technical level. If so, remember to attach a link. If not, make one.
6. Expected salary
If you have confidence in your ability, then write down the salary requirements.
This will help you actively screen out some bad companies to bother you, and the salary range should not be too large. Anyway, in the end, the company will give you an offer according to the "lowest value" of your expected range.
If you want an interview and you are not confident about your ability, write negotiable. Go to the interview first. It is not impossible for the interviewer to be attracted by your face value during the interview.
7. Professional skills
Technical items should be classified reasonably, and technical classification can show your cognitive and understanding ability of front-end technology. It is equivalent to telling the interviewer that you have thought about these technologies, rather than simply building up technical terms. For example:
Proficient in using Java language for object-oriented programming, good programming habits, familiar with commonly used Java API, including assembly framework, multithreading (concurrent programming), I/O(NIO), Socket, JDBC, XML, reflection, etc.
Familiar with Java Web development based on JSP and Servlet, deeply understand the working principle and life cycle of Servlet and JSP, skillfully use JSTL and EL to write scriptless dynamic pages, and have experience in developing Java Web projects using web components such as listeners and filters and MVC architecture mode.
Deeply understand Spring's IoC container and AOP principle, skillfully use Spring framework to manage various Web components and their dependencies, and skillfully use Spring to manage transactions, logs, security, etc. , have experience in developing Web projects using Spring MVC as presentation layer technology and persistent support provided by Spring, and be familiar with the integration of Spring with other frameworks.
Proficient in using ORM frameworks such as Hibernate and MyBatis, familiar with the core APIs of Hibernate and MyBatis, and have a deep understanding of Hibernate's association mapping, inheritance mapping, component mapping, caching mechanism, transaction management and performance tuning.
Proficient in using HTML, CSS and JavaScript for Web front-end development, familiar with jQuery and Bootstrap, deeply understand the application of Ajax technology in Web projects, and have experience in using front-end MVC framework (AngularJS) and JavaScript template engine (HandleBars) for project development.
Familiar with common relational database products (MySQL, Oracle), proficient in using SQL and PL/SQL for database programming.
Familiar with the principle of object-oriented design, have a deep understanding of GO of design pattern and enterprise application architecture pattern and relevant experience in practical development, skillfully use UML for object-oriented analysis and design, and have experience in TDD (test-driven development) and DDD (domain-driven design).
Familiar with the use of Web servers and application servers such as Apache, NginX, Tomcat, WildFly and Weblogic, and familiar with the configuration of various server integration, clustering and load balancing.
Proficient in using product prototype tools Axure, design modeling tools PowerDesigner and Enterprise Architect, Java development environments Eclipse and IntelliJ, front-end development environment WebStorm, software version control tools SVN and Git, project construction and management tools Maven and Gradle.
8. Project experience
The emphasis is on experience, not on projects.
Write less product function description and more technology stack and implementation scheme used in the project, which is what the interviewer wants to see. After all, we are not interviewing the product manager, so why not write a competitive product analysis document here?
9. Work experience
If a person has been employed for a short time and left in a month or so, there will be no bright spot in his work. There is no need to write this, it will make the interviewer feel that you are frequent and unstable.
It's normal for a girl who didn't meet a few love rat when she was young to meet a few scum companies when she applied for a job. Hr likes to use this as a resume, because they can't understand your technical content.
10. Self-evaluation
99% people write that they love the front end, and 99.99% people feel very responsible. This description is pale and powerless, and there is no bright spot.
Everyone knows whether you love it or not. Everyone is making a living. At this time, it depends on who is more like it than who is pretending.
You can add a sentence, and it will be vivid, vivid, true and concrete immediately. For example: love new technology. I've been studying serverless recently, and I often visit technical forums such as stackoverflow.
Love learning, summing up and sharing. Carry out front-end technology sharing meetings in the department for many times to share learning and work summary. Have your own technology blog (if there is one), and often publish articles in the front-end technology field.