Fill in the computer proficiency in the resume: be proficient in using PPT, Word, Excel and other OFFICE office software, and fill in the software you have learned in this major.
If you were an HR and faced with so many graduate resumes on the table, how would you choose?
A senior HR manager once told me: During the recruitment season, the average reading time of a resume will not exceed 10 seconds!
Therefore, your resume should not be fancy, it must be concise and to the point, and highlight your professional advantages!
The resume involves computer proficiency. If you are a student who has passed the computer level exam, just fill in the corresponding level and the relevant certificates obtained.
How do students who have not taken the exam fill in the form?
1. Proficient in using PPT, Word, Excel and other OFFICE office software;
2. Fill in the software you have learned in this major. For example, if you are an accounting major applying for a bank, you can fill in the financial Software mastery;
As long as it is not a position with special computer requirements, the above two points can basically be satisfied.
You can also write:
1. Have the ability to process words, mix graphics and text, and operate tables under Windows environment;
2. Be proficient in using WORD and EXCEL , PPT and other Office software.
The above two points actually express the ability to use computers and Office, but it is still more comfortable to write on a paper resume or application form. The subject can use it as a reference.
Resume guidance
As a web front-end engineer, if you want to find a high-paying job, you will always face various interviews, large and small. The key to a successful interview is an attractive resume.
In fact, technical positions generally focus on work experience. The web front-end position can be said to be more important in the company. HR usually looks at the applicant's project experience when selecting resumes. As well as work experience, etc., these experiences are enough to determine what level of web front-end engineer you are in the eyes of HR.
So I will take you to look at a resume from the interviewer's perspective.
1. Typos
Especially the spelling errors of technical words. This low-level mistake appears on the resume, and the impression score is directly 0.
These are all real examples I encountered during recruitment, and there are many more that I haven’t cut out. It's best not to make such low-level mistakes on your resume, which will give people the impression of amateurism.
Unless you are lucky and meet an interviewer who also has no pursuit.
2. Invalid link
If the link cannot be opened, just say goodbye.
“When I pasted the link, the old club’s project was still running normally. Later, it was none of my business if the project was taken down.”
The project belonged to the old club, but The resume is your own. Check your resume before submitting it. Links that cannot be opened, like typos, will give others the impression that your work is not rigorous.
3. Resume photo
Attach a resume photo, and your resume will be more recognizable.
Appearance is also a kind of competitiveness. If you are good-looking, God will reward you. Oh no, it’s just chasing after him to feed him. Why do you have to fight for your strength when you can obviously rely on your face to make a living? It is necessary to "sell" the hue appropriately.
If you are not confident about your appearance, ask the photo studio to help with post-processing. If it is not possible, open PS and process it yourself. Having a better mental outlook can make the interviewer pay more attention to your resume, which is an advantage.
4. Typesetting is very important
A resume is your first face in the workplace. It starts with appearance and gets stuck in talent. Without a good-looking appearance, who cares about your inner beauty. The layout should be concise, neat, and focused. Let the interviewer have a good reading experience, and it is convenient for you.
Good layout also means that you have good aesthetic ability, which is also the most scarce advantage of a front-end person. I like to work with front-end designers who have good aesthetic skills. There will always be areas that cannot be covered by the design draft, and the front-end designers need to control the design themselves.
The favorite skills of front-end people, such as responsive design, mobile adaptation for different devices and other scenarios, gradients, and dynamic effects design. These details are often not reflected in the design draft, and are left to the front-end itself. Control, or let the designer briefly describe it in a few sentences, and then implement it on the front end.
To put it bluntly, the boss is unwilling to spend money to recruit an interaction designer.
5. Personal website/technical blog
A personal website or technical blog is an absolute killer in interviews. It is what the interviewer likes to see the most. It can reflect your comprehensive skills. techinque level. If so, remember to include a link. If not, make one.
6. Expected salary
If you are confident in your abilities, write down your salary requirements.
This can help you actively screen out some poor companies that will bother you. The salary range should not be too large. Anyway, in the end, the company will make you an offer based on the "lowest value" of your expected range.
If you want an interview opportunity and are not confident in your abilities, just write in for interview.
Get an interview opportunity first. It’s not impossible if the interviewer is attracted by your appearance during the interview.
7. Professional skills
Technical items should be reasonably summarized and divided. Technical classification can show your knowledge and understanding of front-end technology. It is equivalent to telling the interviewer that you have thought about these technologies, rather than simply piling up technical terms. For example: Be proficient in object-oriented programming using Java language, have good programming habits, and be familiar with commonly used Java APIs, including collection framework, multi-threading (concurrent programming), I/O (NIO), Socket, JDBC, XML, and reflection. wait. Familiar with Java Web development based on JSP and Servlet, have in-depth understanding of the working principles and life cycles of Servlet and JSP, proficient in using JSTL and EL to write scriptless dynamic pages, and the use of Web components such as listeners and filters, as well as the MVC architecture pattern Experience in Java web project development. Have an in-depth understanding of Spring's IoC container and AOP principles, proficiently use the Spring framework to manage various web components and their dependencies, proficiently use Spring to manage transactions, logs, security, etc., and have used Spring MVC as the presentation layer technology And experience using the persistence support provided by Spring for Web project development, and familiar with Spring's integration of other frameworks. Proficient in using ORM frameworks such as Hibernate and MyBatis, familiar with the core APIs of Hibernate and MyBatis, and having an in-depth 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, have in-depth understanding of the application of Ajax technology in Web projects, and have used front-end MVC framework (AngularJS) and JavaScript template engine (HandleBars) for project development experience. Familiar with commonly used relational database products (MySQL, Oracle), and proficient in using SQL and PL/SQL for database programming. Familiar with object-oriented design principles, have in-depth understanding of GoF design patterns and enterprise application architecture patterns and relevant experience in actual development, proficient in using UML for object-oriented analysis and design, with TDD (test-driven development) and DDD (domain Driven design) experience. Familiar with the use of web servers and application servers such as Apache, NginX, Tomcat, WildFly, Weblogic, etc., and familiar with the configuration of multiple server integration, clustering and load balancing. Proficient in using product prototyping tool Axure, proficient in using design modeling tools PowerDesigner and Enterprise Architect, proficient in using Java development environment Eclipse and IntelliJ, proficient in using front-end development environment WebStorm, proficient in using software version control tools SVN and Git, proficient in using Use the project build and management tools Maven and Gradle.
8. Project experience
The focus is experience, not projects.
Write less about the product function description and more about the technology stack and implementation plan used in the project. That is what the interviewer wants to see. After all, we are not interviewing product managers, so why not write a competitive product analysis document?
9. Work experience
If you have been employed for a short period of time and left after about a month, and there are no highlights in your work, there is no need to write it down, which will make the interviewer think that you are very reluctant to change jobs. Frequent and unstable.
Which girl has not encountered a few scumbag men when she was young, and it is normal to encounter several scumbag companies when applying for a job. HR likes to use this point to block resumes, because they can't understand your technical content.
10. Self-evaluation
99% of people write that they love the front-end, and 99.99% of people feel that they are very responsible. Such descriptions are feeble and lackluster.
Everyone knows whether they love it or not. Everyone is just trying to make ends meet, so now it’s time to see who is more disguised than the other.
You can add a sentence to make it vivid, vivid, real and concrete immediately. For example: Love new technologies. I am learning serverless recently and often visit technical forums such as stackoverflow.
Love learning, love summarizing and sharing. Conducted multiple front-end technology sharing sessions within the department to share learning and work summaries.
Have your own technical blog (assuming you really have one) and frequently publish articles in the field of front-end technology.