Resume File Tips#
The resume file should be in PDF format, not a Word document or image.
The resume file name should follow the format: Job Position_Name_Phone Number, for example: Web Frontend Developer_Zhang San_13212345678.pdf.
I recommend a free platform for generating resumes that can help you quickly fill in the information below and create a resume: Developer's Inn - Resume
Personal Information#
Name / Age / Phone / Email (try to avoid QQ email, just in case) / Personal website, GitHub address / Work experience (x years) / Job position / Expected salary: (it's best to write negotiable, as it's better to secure an interview opportunity first; if they find you good after the interview, they might offer a higher salary)
For example:
Zhang San#
13212345678 | zhangsan@163.com | Beijing
https://github.com/your-own/(or your personal website)
x years of work experience | Web Frontend Developer | Salary negotiable
Skills List#
There are two ways to write it:
-
Pure Frontend Writing, suitable for those who only know frontend-related skills.
- Highlight your strengths, write about 5-10 points that you can talk about, such as "proficient in using ES6 syntax, can use and read xxx source code, have xxx achievements."
- Do not write statements like "can use axios to make requests," as axios can only make requests and nothing else; it’s like saying "I can use a kettle to boil water," which is essentially meaningless. Avoid writing such statements.
For example:
- Proficient in Vue2, Vue3, and the entire React ecosystem, with a personal understanding of their source code.
- Familiar with various component libraries corresponding to the tech stack, understanding their APIs and some discrepancies between performance and expectations.
- Solid foundational skills in JS, CSS, etc., with deep accumulation, fully aware of various API features, and best practices at hand.
- Proficient in using Chat GPT, Claude, and Gemini for collaborative development and optimization, mastering various elements of writing prompts, skilled at guiding AI to provide high-quality code.
- Excellent architectural ability and judgment, empowering AI for efficient collaboration: guiding AI to form high-quality solutions through precise questioning and clear boundaries.
- Proficient in using Echarts, AntV, and other visualization solutions.
- Proficient in ES6 (es2015 - es2022).
- Proficient in TypeScript, familiar with type programming.
- Proficient in various algorithms / familiar with some business-applicable algorithms, capable of performance optimization where appropriate.
- Proficient in Windi CSS, Tailwind CSS, UnoCSS, and other atomic CSS frameworks/engines.
- Proficient in frontend engineering, achieving xxx effects through engineering practices.
- Familiar with preprocessors like Less and Scss (if you only use preprocessors for basic functions like nesting CSS or writing variables, it's best to say "familiar").
-
Comprehensive Writing, suitable for those with a certain level of comprehensive ability, not limited to frontend skills.
- Do not break down skills too finely; the basic principle is still to highlight strengths and avoid meaningless statements.
For example:
- Full-Stack Development Ability: Mastering the full-stack development process, able to proficiently use NestJS and Go for backend development. For MySQL and Redis, capable of designing efficient database architectures and executing optimizations.
- Vue: Familiar with the Vue2 and 3 ecosystems and related tools, plugins, dependencies; deeply understand Vue source code and its operating mechanisms. Skilled at using various methods to enhance the performance and user experience of business applications.
- React: Familiar with the React ecosystem and related tools, plugins, dependencies; deeply understand internal mechanisms, able to efficiently solve complex frontend issues and optimize performance.
- Build Tools: Skilled in using modern build tools like Webpack, Vite, Rspack for modular development. Proficient in using excellent frontend engineering tools to enhance developer experience; capable of using module federation and other features to create flexible and efficient micro-frontend architectures, effectively reducing system complexity and improving project maintainability and scalability.
- UI Design and Aesthetic Ability: Possessing a certain level of UI design ability, capable of designing aesthetically pleasing and practical user interfaces; adept at combining cognitive bias knowledge with UI interfaces to create user-friendly product logic and interfaces.
- Operations and Automation Deployment Skills: Familiar with the configuration and optimization of Linux, OpenResty, and Docker. Skilled at using sh and Python scripts to enhance operational efficiency and system stability, with capabilities in automated deployment and system maintenance.
- AI Technology: Proficient in using AI technologies (such as ChatGPT, Claude, Gemini), skilled at using AI-based IDEs, having studied the generative AI course by "the father of Google Brain," adept at guiding AI to provide high-quality answers in most fields.
- Learning Ability: Enjoy reading documentation and source code of open-source projects, understanding their concepts. Possessing an international perspective and quality information sources, with various capabilities to solve network issues; able to quickly adapt to emerging solutions that benefit the business.
- Code Quality and Standards: Emphasizing code quality and standards, prioritizing readability and performance in code style, able to quickly integrate into the team's rhythm.
- Multi-Platform Development Experience: Familiar with cross-platform development for Web, mobile (mini-programs, public accounts), and desktop applications (electron, tauri).
Remember the above two methods.
When writing, follow the order of "proficient - skilled - familiar," what you write must withstand questioning; do not write randomly.
Project Experience#
Just write about 3 representative projects; do not write too many unnutritious projects.
Title: Project Name - Role (Frontend Developer) — Time (Project Start - Project End/Present)
For example:
xxx Mall - Frontend Developer — March 1, 2021 - July 20, 2021
Project Description: Use the STAR principle, which stands for Situation (context), Task (responsibility), Action (approach), and Result (outcome). Correspondingly, 【S】 what is the background of this project, which can be a project introduction or the problems and difficulties encountered, 【T】 what work needs to be done, what responsibilities you held, 【A】 how you solved these problems, and 【R】 what measurable results were achieved.
For example:
Project Description: The project timeline was very tight, needing to achieve xxx results under xxx conditions (this is S), I was responsible for xxx (development/coordination/…), needing to ensure users xxxxx (this is T) within this timeframe, I conducted xxx research, chose to develop using xxx methods, and did xxx (clever operations/some impressive techniques) in the project (this is A), ultimately completing the project before xxx, with a bug count of xxxx (this is R).
Project Responsibilities:
❌Do not write:
- Avoid writing "meaningless statements"; these are not derogatory but similar to the feeling of listening to a speech that seems to have content but actually lacks substance.
- Incorrect Examples:
- I was responsible for developing the navigation bar.
- I collaborated with the backend to develop the xxx page.
- I accurately replicated the design draft.
💡 Explanation: The issue with the above is: If you can't do these, then you can't complete the work, because similar demands will surely arise in the future; if you can complete it, others can too, so you lack competitiveness. The resume should highlight your competitiveness.
✅Must write:
- Because of you, the project achieved a certain effect; it’s an achievement, not just what you did (I made a navigation bar, homepage, etc.; the interviewer doesn't care what business you worked on in your last company; they only care about what you can bring to the company).
- Correct Examples:
- Completed the encapsulation of over ten basic components and more than twenty common functions, making functionality more aligned with business needs.
- Optimized packaging speed, improving it by 384% (63s -> 13s).
- Conducted performance optimization, increasing first-screen display speed by 1233% (4s -> 0.3s).
💡 Explanation: Remember one thing, write specific numbers!!! This reflects your value, and specific numbers serve as evidence. Besides being able to meet requirements, what else can you do that others cannot? Write it down, and you will have competitiveness. These things do not necessarily have to be what you did; in projects you have learned about or seen, as long as you can think of this optimization point at the right moment, can explain the principles or sequence, and can apply this optimization/function to other projects to achieve the expected effect, then this is yours. You can write it on your resume, and most likely no one will ask you to reproduce it on paper; the most important thing is to write achievements, not just what you did.
Work Experience#
List them out; if it's an outsourcing company, please indicate!!! Some companies conduct background checks, and if they find that the company paying your social security is not the one you wrote, it may negatively affect their impression of you. Some companies are sensitive to frequent job changes within a short period, so do not write too many.
For example:
- aaa Company (Outsourcing) - Frontend Developer — March 2021 - Present
- bbb Company - Frontend Developer — March 2020 - December 2020
Personal Description#
Highlight your strengths! ! ! Do not write something like "especially hardworking," as it is no different from saying "especially able to eat," write something practical.
For example:
- Strong information acquisition ability, with a strong ability to obtain capabilities.
- Strong problem-solving ability, responsible for work (a brief example to support this).
- Passionate about reading frontend books (if you have really read them). Each point should not exceed half a line, write examples to support them, and avoid empty statements.
- Possessing design aesthetics or a keen sense for products, the user experience of developed products is excellent, and work is meticulous.
Education Experience#
If your degree is quite impressive, you can place it near the top, even in the personal information section.
Conversely, it can be placed at the end; if the HR sees the degree and initially does not want it, but they are forced to read your resume and find it good, they may not care so much about the degree, thus gaining an interview opportunity.
For example:
Claden University - Bachelor in Chinese Language and Literature
Claden University - Master's in Software Engineering
End of Resume Section
Postscript: How to Write a Resume#
- Three main principles of a resume: clarity, brevity, necessity, leaving a good impression on the interviewer.
- Technical ability matching: meet the requirements of the employer, technical level must be up to standard.
- Highlight project strengths: within 10 seconds, the interviewer should discover highlights and have motivation to ask further.
Three Main Principles of a Resume#
- Clarity: The resume should be easy to understand, with simple formatting, such as clear information on school and graduation dates, years of work experience, relevant industry experience, job position, etc.
- Brevity: In work reports or job interviews, "highlighting key points" is a very important skill, beneficial for the interviewer to quickly grasp the key content you want to express. Very important parts can be appropriately bolded, and the resume should not exceed 2 pages. If you don't know how to do this, I recommend reading "The Pyramid Principle," which is excellent.
- Necessity: The resume should only contain necessary information that maximizes time-saving and efficiency for both parties. Ensure that the content in the resume is of interest to the interviewer. Basic information like place of origin, which is not important for interviews, should not be included. Some people include GitHub or blog links in their resumes; if the blog content is substantial, it can be included, but if it only contains a few interview notes, such links should not be included as they may lower your score. If you include a blog link, the interviewer will generally take a look, so prepare the blog content to avoid awkwardness during the interview. Some people list all similar projects in their project experience, such as A management backend, B management backend; in fact, these work contents have little difference, so writing one representative project is sufficient.
Technical Ability Matching#
This section highlights in-depth fields and core skills mastered, such as experience in performance optimization, monitoring, engineering, etc., mastery of Vue / React source code, understanding of network and browser principles, familiarity with data structures and algorithms, etc. Highlighting these contents can guide the interviewer toward the battlefield you have pre-set; if the resume does not allow the interviewer to find highlights, it becomes an exam where they ask and you answer, losing the initiative. Interviewers do not like to ask rote questions; if they cannot find highlights in the resume, they can only ask rote questions.
Highlight Project Strengths#
From some points in the project, showcasing your value is worth writing in the resume.
- Big data optimization.
- Improvement in development efficiency.
- Improvement in development quality.
- Performance optimization.
- User experience optimization.
- Complex & new scenarios.