Internal transfer process and review

After receiving the notice that the product development was stopped, HR gave different transfer options according to different job categories. The targets of my transfer were cloud engineers and PHP backend engineers, both of which overlapped and differed from me now.

The first interview is with cloud engineers. Based on my understanding of the job vacancy, I should be involved in the development of the page tools used by internal engineers, which is the tools I use now as a JAVA back-end engineer, such as when applying for subordinates after updating the program. Observing the operation of the docker container used by the department through the web page, and operating the limited access through the page when you do not have permission to directly view the inside of the database, these require cross-departmental cooperation and use the web interface to connect other cloud services. The technology is my plan. one of the development directions.

After the interview, the supervisors judged that the knowledge I possessed was too far from what the department actually needed to be a good fit. Including the SOP for developing programs and updating the environment, these rules I used before are actually defined and managed by the engineering director. The development process I thought was just packaged. Perhaps for this reason, the director of the cloud engineer judged that my technology and this position were not suitable and therefore did not pass.

After the interview, I talked with the current engineering director about this. He also felt a little pity that he disbanded before he could teach us how to use these tools.

The supervisor of the PHP back-end engineer interview has communicated before, so the interview is relatively easy, but because of the other party's responsibilities, there is no need to expect the other party to release water. After a brief interview, the supervisor gave me an assignment. The time was three working days. Using PHP laravel to connect the company's oauth2 login system, and after logging in, the user's information was retrieved and displayed on the screen. Beautiful no matter what. Just do as much as you can, not everything is required.

It was finally judged unsuitable for two reasons. First, because of my misunderstanding, I interpret the requirement as first connecting to the login system and then filling in the oauth2 part. "When you have doubts about the requirement, you should ask to confirm whether it is your own misunderstanding"; The second is about the misuse of echo. I should avoid using a function when I know it is not in line with my previous development experience, but I continue to use it when I feel strange. "I don't understand the program I wrote" is what I have this time. Big mistake.

Making such a mistake caused the transfer to fail, and my engineering supervisor was also a little surprised. It can only be said that it was a result of inexperience and ill-consideration.