How to get a product associate interview and how to get on the job quickly

Well, first of all, you must appear to be experienced, you must understand how it works, and what you do.

The operation of the unit needs to be understood, dressed appropriately, not small, not too tender, to pretend to be mature, to interview the head of the blind with their own resume, Chinese, English each Qin Zhi.

In fact, the interview is mainly a communication process, there is no need to make it like an exam, maybe we will work together in the future, and we can take it with a very calm and serious attitude.

Write your resume with practical actions.

Make a list of the framework, what knowledge, skills, and experience are needed for your target career in the future, what you have, and what you don't have, and take the initiative to learn and improve by yourself, which is to write a resume with practical actions.

Use the idea of making a product to make a resume.

Many college students have not interned in an Internet company before graduation, and they basically have not experienced the complete process of designing products.

A good product: based on the needs of users, create products that attract users, and at the same time can be commercialized.

Similarly, a good resume: from the interviewer's point of view, give a document that matches the needs of the position, so that he can realize the value of the job seeker in a short period of time, and quickly admit you, so as to realize the personal realization of your resume.

Product Objectives. Who are the target users of the resume?

When writing a resume, the position you are applying for needs to be clearly expressed, and at the same time, you need to show some advantages in the position you are applying for. The job search position, which is the job search intention in the resume, plays a central role.

It's specific to each user and what their needs are.

If you try to get an offer with a resume, it is either a big bull, and the employer is actively fighting for you, or the company itself can't recruit people, and it is difficult to find a position that matches your own ability and salary.

Competitor analysis. The competition in the target market, what are the advantages of competitors against each other, and how to find new selling points on your resume, this is very important.

Resource analysis. What kind of resources do you have at hand to help you write a good resume, whether it is a past experience of a or a senior who provides you with information, etc.

Establish core functionality.

That is, on the resume, what are the specific advantages and functions to establish the advantages and attract the interviewer.

Product development and testing.

The experience on the resume is not a statement in the form of a running account, but a star rule, which clearly states in four sentences what kind of background, what kind of tasks you have received, what things you have done, and what results you have achieved.

Even if you can't find product-related experience, you can use experience that can cash out product capabilities, such as competitions, clubs, startups, etc.

Go live and publish. Analyze the delivery situation of each position, grasp the competitive pressure and ranking at any time, and improve yourself at the same time, you can also try a few other positions with a small competitiveness and high matching degree to give yourself more opportunities to choose.

According to my understanding, fresh graduates have a generic resume. That is to say, the content of the resume mainly includes the graduate's natural situation, professional learning situation, social practice situation, reward situation, work intention, etc. Graduates can simply submit their CVs containing these information to various recruiting units, from which they can select suitable candidates.

Therefore, there is no need to deliberately highlight the situation of wanting to apply for a certain unit or position in your resume, even if you do not mention the situation related to product assistant in your resume, as long as your basic qualities and conditions are excellent, it is easy to get the job. Of course, if you really care about working as a product assistant, just add a sentence or two to your resume.

A product assistant is primarily a product assistant who shares most of the product manager's chores, mostly2.Refinement of the frame diagram: Sketches and concept drawings are supplemented into a complete set of frame files.

3.Material collection collects some materials required by product managers such as marketing, operations, and cases.

4.Basic user research collects user feedback, observes users' words and deeds based on products and markets, and gives feedback to product managers in a timely manner.

5.Feedback skills: The assistant must learn how to communicate feedback to the product manager, and for the assistant, handling these four links can save at least 40% of the product manager's work time and energy.

Job Responsibilities:2. Assist the product manager to design product prototypes and write product requirements documents;

3. In-depth research on market and user needs, and continuously improve the user experience of products;

4. Cross-departmental coordination of UI, terminal, testing, operation and other teams, and work closely to achieve product goals;

5. Analyze product data, always pay attention to the situation after the product is launched, and propose solutions in time when problems are found;

The value of the role of an assistant is not to create, innovate, but to share, and the first condition for us to evaluate whether an assistant is good is how much time you can share with your product manager.

The promotion ability that an assistant needs to master is the following four skills.

1.Team communication.

Good communication with other roles in the design, R&D, QA, operations and other teams can be used to create a discussion atmosphere.

2.Progress follow-up.

Have a clear grasp of the implementation progress of the project, the status of completion, the remaining time, and the risk assessment of delays.

3.Product launches.

Begin to understand the product release rules of each channel and platform, and prepare the corresponding release materials.

4.Independent planning of small modules.

This link requires not only innovative thinking, but more importantly, to explore product thinking in a small module environment, to know that product thinking is a very comprehensive and wide thinking.

Imagine if you were a product manager, what would you like to have as a product assistant?

First of all, the most basic is the ability to use tools, such as Office, Axure, Visio, XMIND, etc.

Secondly, the product manager needs the help of the product assistant to write the document, which includes the product requirements document, the competitor analysis document, etc., and the ability to write the document is a must.

The most important thing is to have the ability to think logically. The logical thinking ability will be reflected in the business process diagram, information structure diagram, and page flow diagram, which is also the most training place for product assistants.

As a product assistant, the product manager does not need you to have deep thinking about the product at this stage, and the needs of the product manager are mainly reflected in the executive level, which can help the product manager solve some tedious, but not very complicated things.

So why do you want product assistants to have project experience?

Because screening is greater than culture. Those with project experience show that these executive level things can be done independently, and the cost of screening is much less than training.

If you want to gain practical experience in the project, you can go to the bald school to take a look, there are many courses suitable for product whites to share, a good practice project is the key to success or failure, is the stepping stone to the work of famous enterprises, determines the starting point of making products, and must pay attention to it.

First of all, if you want to be a qualified Internet product assistant, you must have the following requirements:

1. Daily operation and maintenance of products, according to various analysis, test results and user feedback, continuously improve the products that have been launched, and arrange project priorities.

2. Market competition analysis, analysis of competitors' products, and all related products inside and outside the industry.

3. Investigate user needs, collect feedback, analyze and screen, and analyze user behavior.

4. Work closely with the outsourcing technology R&D team to be responsible for the planning, design, implementation and operation of the product, and prepare product documentation.

5. Research the direction of product development, put forward new product plans, formulate and design new products or new functions required by users, and optimize existing functions or strategies to improve user experience.

1. Experience in planning, design and implementation of Internet products or software products;

2. Be good at transforming product design ideas into industrial-grade product design documents;

3. Good at organizing and writing product strategy documents, product requirements documents, and product interface framework documents;

Finally, the job responsibilities of a qualified product assistant are:

1. Proficient in using various product design tools. Proficient in Microsoft Office 2003 and 2007 Word, PowerPoint, Visio and other office software.

2. Organize and participate in the internal meetings of the product department and the joint meeting of multiple departments, and be responsible for sorting out the records and forming meeting documents.

3. Quickly complete high-quality product documents, including strategic document writing and sorting, product requirements documents and product framework design documents.

4. Serious and meticulous work attitude, good at communication and coordination.

5. Receive feedback from the marketing department, collect market information and customer information, form product improvement ideas, and write product improvement design documents.

1.Stay sharp. This can be applied to anything:

The product, the team, yourself. It's easy to get caught up in the details of a project and forget about the big picture. It is also easy to get caught up in the system management you have formulated for yourself and your team, and ignore the ineffectiveness of the system.

Take a step back and examine your assumptions, current practices, and performance; What you find will blow your mind.

Try asking yourself these questions:

Are we creating products that are solving the right problems? Is this the right way to solve the problem?

What is the long-term impact of this decision?

What are the unintended results?

How is the team running? Compared to team happiness, have you optimized the project process enough?

What do you need to improve in order to become a better leader?

2.Good adaptability. In addition to being sensitive, you also need to constantly adapt to new changes in information.

Such as product innovations, prototype failures, and changes in people's needs. If the product doesn't solve the right problem, change course. If a meeting no longer serves any purpose, cancel it.

3.Be proactive. I've once heard the metaphor that product management is like a process of filling in the gaps left by different roles.

I think that's a very important attitude to have. You are the boss. Do it or delegate it to someone else.

If you don't, no one else will. Product managers are subordinate to the service industry; Your role is to serve the team, and no work is trivial or trivial.

4.Understand the core issues. Many people think that product management is all about "having a good idea" or "adding function points".

Only by understanding this issue correctly can we go further. If you dig deeper into why people don't click the button, you'll know why the product isn't working as you expected it to, which may lead to a more definitive solution, which is to solve the problem the right way.

Ideas like "make the button bigger" may solve the superficial problem, but it won't solve the deeper problem. To solve this problem, I think it requires a combination of design research in psychology, ecosystems, and the social sciences. Also, keep learning from your peers, books, podcasts, TED Talks, and everything else you can.

5.Learn to balance. When you're making a decision, you're actually weighing the elements.

Every feature has a cost. Identify the most important modules of the project (e.g., development complexity, development time, visuals, usability, use case a, use case b), do a rough calculation of each module, and confirm how many resources you want to allocate to each module. Decide how much you value each module so that you can make the right decision.

Generally speaking, the assistant is responsible for the matters assigned by the superior, or sorting out the work arrangement that the superior needs to operate next;

First, you need to listen more and talk less, and you need to think about it before reporting it.

Second, during the work, the ability to be on call and obedient to do what is told;

Third, coordinate the normal work between various departments, and consider problems from the perspective of superiors.

1.It will look at your previous experience and ask you about some previous situations.

2.Not for the current position?

3.How to lead a team.

4.What's happening in the market?

5.If you take office after your thoughts, your goals, you have a rough approach.

Briefly talk about your previous work unit and work content.

Before the interview, look at the relevant job descriptions online.

Then, when you are interviewing, you will be able to polish your words and deeds a little.

It would be even better if there were a referee.