Interview and promotion, there are some metaphysical things in it, commonly known as eye edge.

Others are due to timing, luck and other factors beyond our control.

There are also things that cannot be put on the table.

Apart from that, what are the things we can improve ourselves on?

For P6 and P7 positions in our factory, the dimensions to be examined in the interview are as follows

  1. Technology base

    This is very easy to memorize the eight-part essay and brush the question for a short time to improve, the interviewer also knows. So a lot of companies now add programming problems, just to balance things out. If you write good code, it is OK to memorize eight strands. If only eight good back, but the code is very water, generally can not pass.

  2. Project complexity

    Project complexity mainly includes two aspects, the first is business complexity and the second is technical complexity.

    A microfront-end project, for example, is a bit more technically complex than a single project.

    A product with 10 million users is slightly more complex than a business with 1 million users.

    A visual project is a bit more technically complex than a back-office management project.

  3. Communication and collaboration

    Communication expression, in fact, also pretty eye edge. And in fact, the proportion is relatively large.

    Most of a programmer’s time is spent communicating. Requirements clarification, solution review, battle with product and test, collaboration with peers, etc.

  4. The potential value

    Potential value looks at several aspects

    The first is initiative. Are there initiatives to initiate, such as proactive performance optimization, refactoring of solutions? One thing to note here is that most of the refactoring that resumes talk about isn’t really what it sounds like. It could be a component rewrite, far from refactoring.

    The second is the courage to do things. Be able to take the initiative to do something.

    The third is learning ability. This is reflected by years of work, and the match between the applicant’s technical depth and technical vision.

    The fourth is through promotion, which is the most powerful proof.

About the promotion

In fact, I am the kind of person who gets promoted slowly, I don’t spend much time in big factory. Small companies and large companies have different orientations.

At the boss level, the key to advancement is what you bring to the company. Benefits are no more than two ends, open source and throttling.

Open source is when you create something that drives traffic to customers, or directly generates financial revenue.

For example, you implemented a certain function, how much improved user satisfaction, how many customers drainage.

Throttling means reducing costs and increasing efficiency. For example, if you develop a tool that reduces the bug rate and speeds up compilation, you can do something in 2 days that used to take 5 days. A popular part of the front end is to do low code engines. The majority of development promotions actually focus on doing this stuff.

I have a case with me, a friend of mine. He worked in a big factory and was originally engaged in marginal business.

Resolve to do this when low code is most popular. I am not very optimistic about low code. I think it is KPI project, which is more burden than benefit for the front end.

But his finished product, at the end of the day, was marketed to the back-end team. Back-end teams often have uncomplicated front-end requirements, but no dedicated front-end staff. His package, which includes development and deployment, as well as remote debugging, allows the back end to quickly build an uncomplicated system.

The project eventually evolved from a side project into a platform for more than a dozen people.

Friends have been promoted in a short period of time.

This inspired me to rethink what initiative is.

I used to think that initiative was the courage to do something. Actively assume responsibility and take the lead.

A higher kind of initiative now is the boldness and ability to transform reality.

My personal experience, a lot of times we ridicule XX system do poor, XX technical solution is not perfect, XX management is not professional and so on…

There are things that we think are beyond our power to push or change, but sometimes it’s better to try, even a simple demo or pilot, than to wait for a better solution.