How to write project experience?

The project experience writing template should include the project name, duration, etc. Let’s take a look at the article to find out.

1. Project experience writing template

There are already relatively mature routines for writing project experience, which is generally the STAR principle, that is, you need to clearly explain the background, tasks, actions and results of the project. The STAR principle is, after all, just a framework writing principle. In terms of specific writing, I suggest you write according to the following structure:

The first is your project name.

This is the most basic content. The interviewer must at least know the name of the project. On the same line as the project name, write the duration of the project. For example, "2023.12~2024.02" means that the project starts in December 2023 and ends in February 2024.

Next, write the background and mission of the project.

Background refers to why you want to do this project, and the task is what you are going to do. The background of some projects is very simple and can be put together with the task to save space on your resume.

Here we need to remind you that you cannot simply look at the project background of data analysis from the perspective of a data analyst, that is, you cannot think that the project background requires the reconstruction of the underlying data, or that we need to analyze the decline in promotion rate. This kind of background is from the perspective of a data analyst, and in fact, it has been refined to a specific problem to be solved.

Your real project background should be from a business perspective, thinking about why you need to solve such a problem at present.

For example, you are actually given an analysis requirement that requires you to analyze the reasons for the decline in refund rate. The background of this requirement is not that the business side requires you to analyze this problem, but because the current sales are doing well in all aspects, only the refund rate is higher than that of the same industry, so the refund rate is currently the most effective means to improve sales efficiency. This is the real background of this requirement. As for the data analysis requirement for refund rate analysis that you received, it is already a task derived from this business background.

By the way, the perspective from which you write about the project background can often reflect your level.

If you have a higher vision and a more comprehensive perspective, and can see what problems your work solves for the overall business, then your rank is generally higher. If you only know what you have done but not why you did it, then you are probably a tool person, a tool person who is assigned to do something, and you do not understand the more comprehensive business background.

Therefore, the background of this project is not as simple as imagined. A well-written background can reflect a lot of your underlying level of cognition.

Next comes concrete action.

In this part we need to give some specific actions we took. I suggest you try to express them in a structured way.

For example, what you do can be divided into the first step, the second step, and the third step, or the project has three directions at the same time, namely direction one, direction two, and direction three. Using such a structured statement can make it easier for the interviewer to read the resume.

In the action section, you also need to add one more piece of information, which is the role you play in the project.

In a relatively large project, you are usually not the only one involved, but there are many people working on it at the same time. So you need to make it clear what role you play in the project? Generally speaking, there are three types of roles in a project, namely:

Project Hosting: Generally speaking, data analysts are unlikely to host analytical projects, but rather data product projects. For example, projects such as report development and visual dashboards. Such projects may be hosted by data analysts. If you host such projects, you will need to mobilize other resources, such as technical resources, data warehouse resources, business resources, etc.

Independent responsibility: This means that a task is assigned to you and you can do it well by yourself. For senior data analysts, independent responsibility is generally more common.

Participation: The last type is participation. Participation is the lowest level of participation in the entire project. It is only a small part of the entire project, or even just a specific person in charge. You may not be able to see the whole picture of the project.

Because of the differences in project roles, if you don't clearly state your role in the project in your resume, it is very likely that you will write about a large company-level project. In the end, the interviewer will find out that you only participated in a small part of it, maybe just the launch of a small report. In this case, this project is actually of no reference value, and the interviewer will think that your resume exaggerates the facts.

At the end of the project experience, write down the results of the project. This result must be quantified. If it is not quantified, it cannot reflect your professional quality.

Project experience polishing tips

Now that we have the project experience template, let's look at some polishing tips. Here are three polishing tips.

1. Polish 1: Merge

The first method of polishing is merging.

Merging means combining multiple projects of the same type. Some projects are not very difficult to do, so if you take them out separately, they are just mediocre and have no highlights. If there are many projects of the same type, you can merge two or more similar projects into one.

The benefits of doing this are, firstly, it can make the content of the project richer, and secondly, it can make the project look more difficult.

For example, I recently helped a classmate with resume coaching. He had two project experiences: one was about user churn analysis, which was a special analysis project. The other was about the effectiveness analysis of new user acquisition activities, which was an analysis of new users.

In his original resume, these two analyses were Project 1 and Project 2. During my communication with him, I found that the analysis methods of these two projects were very similar, both of which were to drill down and analyze users through dimensions such as behavior and attributes. So I suggested merging these two projects into one.

The reason is that these two projects are too similar, both of which are about analyzing user growth, and the analysis methods are similar. If you combine these two projects, then when you talk about the business background, actions, and results of this project, you can describe it from a broader perspective and in a more systematic way.

You can say that in the user growth business, you started with the AARRR model and first discovered the problem of new users and loss. So you started to work on the effectiveness of new user acquisition activities and analyze lost users. If you express it this way, the entire project will be more complete.

Of course, you may have questions. In actual work, these two projects are not actually the same project. So can I combine them together?

If the time interval between your projects is really long, more than 1 year, it is not recommended to merge them together.

If the time interval between these two projects is less than one year, I think they can be merged. Because the projects within one year are likely to serve the same business goal, which is a big project in a broad sense. Because a company generally has an annual goal, and this annual goal generally does not change. For example, the goal set this year is to attract new users, the goal for the second year is to improve user experience, and the goal for the third year is to attract old users, etc. In this year, what you do is essentially to serve such an annual business goal.

2. Polish 2: Multiple Types

The second way to polish is to have experience in various types of projects.

If two of your project experiences are report-related and the other two are special analysis, then your resume will look very repetitive. When employers read your resume, they will have many bad impressions, such as thinking that the project experience is too repetitive, doubting your planning and summarizing ability, thinking that what you do is too monotonous, and whether your vision is too narrow.

I generally recommend keeping three or four project experiences, and try not to keep them in the same direction. For each project direction, you should only keep one that you feel most satisfied with, the most representative, or the most memorable. You can also use the merging method mentioned above to merge similar projects into one large project.

If you have experience in projects in multiple different directions, then your work experience will seem richer. You will be involved in multiple directions, and at the same time, there will be priorities. Your focus is on a specific direction, and you are not completely unfamiliar with another direction. Your vision is still broad.

Various types of experience will also help with the next polishing method.

3. Polishing 3: Multiple Versions

The third method of polishing is to write multiple versions and adjust the structure and order of project experience according to the job you are applying for.

If you want to improve your resume's pass rate, just writing a resume is not enough. Your best approach is to adjust the content of your project experience according to the target position you are submitting your resume to.

In terms of adjustments, the simplest way is to adjust the order and priority of your original three or four different types of project experiences.

If Company A is more interested in the construction of a reporting system, then you should put the reporting system project at the forefront. If Company B is more concerned about the ability of special analysis, then you should put the special analysis project at the forefront. In this way, you can form many different versions. You can then choose to submit the corresponding version of your resume based on the different needs of the target company.

Another method is to make more detailed modifications to the content of the project experience. This method is a bit troublesome, so I will give you an example to help you understand.

For example, for a project like building a reporting system, different companies may have different focuses.

For traditional enterprises, their data construction is generally backward, and the difficulty of their data report construction is mainly focused on how to connect the production relationship of data, how to aggregate the data, and how to form an automated process. Therefore, your cross-departmental communication and coordination skills, data infrastructure and governance capabilities are valued.

In Internet companies, because the data system construction of Internet companies is relatively complete, the reporting system construction of Internet companies pays more attention to your indicator design ability. It sees whether you can extract a very systematic indicator system for the entire business and use simple data relationships to describe the entire business. Therefore, your business ability and extraction ability are required to be relatively high.

Therefore, when you are interviewing for a traditional company, you should highlight your cross-departmental communication, indicator cleaning, and data automation, and focus on writing about this part of the project experience.

If you are interviewing for this position in an Internet company, you should focus more on how you refine the business indicator system and your thinking on the entire business.

Author: Jason;

Source public account: Ternary Variance (ID: 686668)