I just graduated and want to find a job. As long as you are looking for a job, there will be an interview. So during the interview, what precautions should I pay attention to? Especially for professional and technical positions, such positions are generally in-service engineers, how to better understand the interviewer's questions during the interview, let's look down together.
It doesn’t matter whether you study at school, in a training institution or online, no matter which way you go, after a long period of study, you will soon practice, but when you are interviewing, you are still not sure, it’s okay to continue reading ~
one. What is Linux? Contact those Linux?
This is generally an introductory question. There are no requirements for applicants for this position. As long as you know that there is such an operating system in this world. You can follow the introductions in all books, introduce Linux to memorize, and then talk about Red Hat\ Ubuntu\ Centos, etc. Basically, you can pass the test. It is generally suitable for candidates with low academic qualifications and applying for positions such as IDC operation and maintenance.
two. Which scenarios will use Linux?
A little more advanced question mainly depends on what position you are in, or what position you are applying for. Let's take the test engineer as an example. There are the following scenarios where Linux will be used: 1. If the project fails to run, we can use the command: ps -ef|grep XXX (process name) to check whether the process on the Linux service is normal start up. 2. When encountering a BUG while running, we can use the command: tail -100f xxx.log to view the last 100 lines of log content, of course you can also -10 or -200, it depends on personal habits.
three. What are your favorite Linux commands?
The most important point of this question is, don't memorize a bunch of Linux commands by rote, it is meaningless to memorize these commands. Be sure to combine business scenarios and then bring out this command. For example, in the test engineer scenario mentioned in the second point above. You just imagine a scene in your mind, and the commands you often use can be poured out one after another like pouring beans. (Look at a directory pwd-enter the directory cd-create a folder mkdir-delete use rm-copy and move mv-view file content cat more. Or check the network card ifconfig-kill if the process does not respond) and so on. This is like having a screen, an immersive operation.
Four. Tell me about your understanding of this position
When you encounter this problem, you must do your homework in advance and know what position you are interviewing for. We will not fight unprepared battles. According to my personal understanding, I divide the positions into three categories: operation and maintenance, testing, and development.
1. Operation and maintenance: general IDC operation and maintenance, you know that there is a Linux system, and you can basically pass the test by memorizing common commands; advanced server operation and maintenance, this generally has 2-3 years of practical work experience and can operate proficiently Mainstream Linxu system Centos Redhat... Familiar with Shell scripts. To interview for this position, you need to proficiently list the tools and environment you use. You can talk about ELK log collection, monitoring and warning system Prometheus+Grafana. Let's talk about the daily service FTP provided to customers. The common environments are Java, maven, and Nodejs; there are also middleware such as eureka, fastdfs, and nacos. File sharing NFS has been deployed with various related services. It is best to combine docker, web, and actual projects; and advanced server operation and maintenance belongs to the industry ceiling, and they are all industry leaders. If you just graduated, you should start in the industry first 10 Think again next year.
2. Test class: Compared with development, the main difference between testing and development is the ability to write code. If you have a strong ability to write code and have a very deep understanding of Linux, you must show it during the interview. Start with the basics, proficiently describe the software testing process, common methods of test cases, tracking of bugs and defects. Then talk about various test workers
Tools: such as packet capture tool fiddier Charles interface testing tool postman performance testing tool jemeter loadrunner. A little more advanced is to talk about automatic test writing in Python language and jave language. The testing class is easy to reach the ceiling. If you have worked in the industry for 3-8 years and have not entered a large domestic factory, then the test architect and test director on the ceiling can only say goodbye to you.
3. Development class. This belongs to the category of entry-level high ceilings, and you can even go from ordinary development programmers to development directors, and later jump to company executives, or transfer to other tracks. Of course, this advancement is also difficult. Opportunities and one's own efforts are inseparable. The development interview is mainly about projects. Tell me what projects you have done. Once you talk about the whole development process, your level will naturally be reflected. Application development, embedded development, server background development, bottom-level development, how to choose each track depends on the skills you have mastered. The above are the common skills and questions in the linux interview compiled by "This is how Linux should be learned". To sum up, combined with your actual ability, try your best to move towards a higher level. The more types you come into contact with, the faster and more comprehensive your ability improvement will be. Never rest on your laurels, and strive to enter big factory. Let's work hard, brothers and sisters.