Work is very 6, interview 1 face confused? You need to know these 3 things

Introduction

Every week my family will hold a review activity, reviewing my strengths, weaknesses, good work and bad. In the review activity, the husband can only think of his own advantages every time, and he feels that he is perfect. Well...that's not the case at all from my point of view.


For example, he is a classic double standard. If he works extra late, I wait for him, and then he complains, and he's going to get mad. I feel like I have to complain about the fact that I work overtime so naturally. If I work overtime late, he will also get into a rage, thinking that I just didn't plan well and things didn't work out, so I worked overtime. The actual situation is: my technical level is definitely not worse than his. I often help him at work, but he can help me. There is no thing that I need to work overtime. It is easy for him to do it without overtime.

Another example: he himself uses the gaslighting effect unconsciously. He made his own rules and felt that others should abide by them unconditionally and respect him. For example, if he did not lift the toilet lid when using the bathroom, he would also be furious, thinking it was immoral. I figured it out myself. The ratio of males to females in this toilet is 1:1. Why should we follow the standards of males?

Seeing this, do you think I have to change my husband? But my family members agreed that my husband was very nice, and even turned my elbows out, which made me treat my husband better. He also does a good job at work. I have witnessed every company he works for, and everyone recognizes him in every way. Does my description contradict other people's perceptions?

Saying this is to elicit my own point of view today: the work is very hard, and the interview is stunned. There is a point of view here. To stand out in an interview, you need to know these 3 things:

1. Cognitive limitations

2. Knowledge is not systematic

3. Ask if you don’t understand

Cognitive limitations

Everyone has their own cognitive limitations, and the process of continuous growth at work is the process of constantly expanding the pattern.

Let’s analyze this sentence: I know what they know when I’m working, and I know what they don’t. I’ve never encountered a technology stack and I can do it by looking at it. I’m confused when I ask the interview

From this sentence, it can be seen that this friend has a strong learning ability and is very smart. Let's take a look at the level and standard of software engineer title evaluation:

1. Apprentice programmer (AP: assistant programmer) 

  1. Graduated from a computer-related major; passed the national level 4 in English. 

  2. With strong learning ability, can write code to meet the company's work requirements. 

2. Programmer (P: programmer) 

basic requirements: 

  1. Bachelor degree, more than half a year of work experience; English passed the national level 4. 

  2. Meet the work commitment requirements; have certain communication skills and work responsibility.

Technical Ability Requirements: 

  1. Responsible for writing code, mastering a mainstream language/development tool, a mainstream operating system, and a mainstream database. 

  2. Understand and master the specifications and techniques of development assignments (PD design, coding and testing, etc.). 

  3. The quality of the code written is better.

  4. Be able to write documents as required, with clear structure and detailed and accurate content. 

  5. Have the business understanding ability and problem elaboration ability to independently understand the responsible module.

  6. Able to read ** technical documents. 

3. Senior Programmer (SP: senior programmer) 

basic requirements: 

  1. Obtain programmer qualification for more than 1 year; or meet programmer level standards and have more than 2 years of relevant industry work experience.

  2. Complete the annual workload indicators; have strong communication skills and sense of responsibility.

  3. The satisfaction of the projects undertaken is above satisfactory.

Technical Ability Requirements: 

  1. Proficient in a mainstream language and corresponding development tools; proficient in data structures.

  2. Possess good business understanding and technical investigation skills.

  3. Write high-quality code and have code review capabilities.

  4. Capable of detailed design.

  5. Familiar with system testing tools and have the ability to improve system problems.

  6. Be able to lead more than 2 employees to carry out work, and have successfully led more than 3 team projects/modules with no less than 5 person-months.

  7. The Chinese language reaches the advanced level or has the same level, and can read the Chinese literature and write technical documents in the Chinese language according to the requirements.

  8. Knowledge of quality management systems and project management.

Fourth, software engineer (SE: software engineer) 

basic requirements: 

  1. Acquired senior programmer qualification for more than 2 years; or meet the senior programmer level standard, and have more than 4 years of relevant industry work experience.

  2. Complete the annual workload indicators; have strong customer communication skills.

  3. Have been responsible for a project with more than 20 person-months or a project with a total of more than 60 person-months.

  4. The customer satisfaction of the project in charge is above satisfaction.

Technical Ability Requirements: 

  1. Proficient and proficient in using two or more development tools, at least one database knowledge, and at least one operating system knowledge.

  2. Ability to quickly complete technical investigations of new projects, to design complex algorithms, and to design reusable and flexible software structures.

  3. Have system design ability and system proposal ability.

  4. Have in-depth knowledge and rich experience in the technical framework of the system or project.

  5. Have industry knowledge in a certain field.

  6. Possess project leadership skills.

  7. * * language reaches * level or equivalent level, able to read and write * language technical documents, with simple oral communication skills.

  8. Master quality management system and project management knowledge.

Five, senior software engineer (SSE: senior software engineer) 

basic requirements: 

  1. Obtained software engineer qualification for more than 2 years; or meet the software engineer level standard, and have more than 6 years of relevant industry work experience.

  2. Complete the annual workload indicators; have strong customer communication skills.

  3. Responsible for a project with more than 50 person-months or a project with a total of more than 100 person-months.

  4. Led the project customer satisfaction above.

  5. Complete the annual training work.

Technical Ability Requirements: 

  1. Proficient and proficient in using two or more development tools, at least one database knowledge, and at least one operating system knowledge.

  2. Possess overall system design ability and system proposal ability.

  3. Have strong technical planning ability, technical guidance ability and ability to deal with difficult problems.

  4. Gain in-depth industry knowledge in a field.

  5. Possess large-scale project leadership skills.

  6. * language reaches * level and is equivalent to * level, proficient in conversation and writing * language technical documents.

  7. Proficient in quality management system and project management knowledge, and able to promote software development process improvement.

6. Chief Software Engineer (CSE: chief software engineer) 

basic requirements: 

  1. Acquired senior software engineer qualification for more than 2 years; or meet the senior software engineer level standard, and have more than 8 years of relevant industry work experience.

  2. More than 5 years of experience in project leader, accumulated more than 120 person-months of technical leader work.

  3. Led the project customer satisfaction above.

  4. Complete the annual training work.

  5. Strong communication skills, problem judgment and solution skills, and innovation skills.

Technical Ability Requirements: 

  1. Proficiency in at least one mainstream programming language. Master at least one kind of database or at least one kind of middleware. Proficiency in at least one operating system.

  2. Proficient in software requirements analysis/large-scale project planning. 

  3. Proficient in software system design. 

  4. Familiar with advanced project management and quality control of software, with the ability to analyze and avoid major quality problems. 

  5. Proficient in business knowledge related to at least one departmental project. 

  6. * language reaches * level or equivalent to * level, proficient in conversation and writing * language technical documents. 

If you want to meet the standard of programmers, you need to master a mainstream language/development tool, a mainstream operating system, and a mainstream database. What is mastery? In "In -depth understanding of the Java class loading mechanism, no more rote memorization ", I introduced the meaning of mastering a language; in " Summary: The Learning Realm and Route of Message Middleware MQ " I introduced the knowledge of mastering MQ meaning. Strong learning ability is AP level, mastery is P level. If you want to be like a duck to water in the interview, then we have to look at our knowledge and skills from the perspective of employment standards.

Knowledge is not systematic

Think from the bottom up, express from the top down . Structured thinking needs to be cultivated consciously at work. This kind of cultivation relies on a habit: often reflecting, often summarizing. Incorporate what you have learned and used into your own knowledge system through your own thinking.

In this way, when the interviewer asks a question, it is like manipulating the page and clicking search, and it has its own content to find a matching answer. Completing a task does not turn knowledge into ability, thinking does.

Ask if you don't understand

In some cases, failing to answer an interviewer's question may be a result of not knowing what the interviewer is asking. As an interviewer, there is a burden in my heart. I always feel that it is my own problem that I don't understand, and I dare not ask. This kind of thinking is unnecessary.

Think about whether we often encounter the following problems in our work:

caf8c7f4d0fbd8047b0eb1e0f96d36b2.png

All information is distorted during transmission. DDD places great emphasis on universal language, and for this reason. But universal languages ​​tend to be less universal. I have also heard some slang words in interviews before, and it has become a common practice within a certain company, and the interviewers themselves do not feel that they are speaking slang words. The outsiders were dumbfounded when they heard it. It didn't matter. Even if it's an industry term, if you don't answer it, it's already 0 points, and you can still deduct negative points, ask boldly!

Summarize

This article is a question raised by friends in the [Programming Lifetime] user group. Here I will talk about my personal views, excluding interview questions. Therefore, in the second chapter, I will send out the interview questions I have summarized before and the answers I have summarized. I have posted this pdf document in the user group, and you don't need to read the next article if you read it.

The biggest gain that people can get from books and articles is to open their horizons and see their own limitations. Well worth it if you can. But the door of some people's hearts is not so easy to open, and it needs constant sowing. Keep at it, and one day you will have an epiphany.

programming for a lifetime

Because the official account platform has changed the push rules, if you don't want to miss the content, remember to click "watching" after reading it, and add a "star", so that every time a new article is pushed, it will appear in your subscription list for the first time.

PDCA methodology , check if you miss the update: I will update the article every Wednesday around 8 pm, if you don't receive it, remember to open the [Programming Life] public account to find it (*^▽^*)

Guess you like

Origin blog.csdn.net/xiexiaojing/article/details/123343189