善恩創新股份有限公司

None

The job description says the Chief Information Officer has extensive experience?

Don’t make me laugh—the basic concepts are so badly wrong, yet they still have the nerve to call themselves a CIO.

The salary offered is low too.

If you can’t even afford to pay, don’t expect to find any good talent.

Oh—I think I know why someone like this can still be a CIO.

The HR staff were very friendly, had done their homework on the interviewee, and also offered suggestions on and discussed my previous work projects with me.

The CTO's technical knowledge is inadequate.

They regard Spring Boot as a front-end technology,

saying that after seeing many large companies use Spring Boot as a back-end technology, the architecture of the entire program becomes very messy.

Therefore, they think Spring Boot should be used as a front-end technology.

I was completely puzzled???

The whole world uses Spring Boot as a back-end technology,

and only you use it as a front-end technology.

I really don't know whether you don't know what a front-end is, or whether you think you're the smartest person in the world and everyone else is an idiot.

I asked what framework and architecture were used to develop the back end.

The answer was Spring Web MVC.

I thought they meant that the control layer was developed using Spring MVC,

but they said no.

They said the entire back end used the Spring Web MVC architecture???

They don't even know that a web back-end architecture should be divided into a control layer, business layer, and data layer.

Are you planning to handle transactions or query the database in Spring MVC?

They don't even know the difference between Spring and Spring Boot.

Spring is lightweight to use, but its configuration is heavyweight.

Spring Boot preconfigures the configuration aspects and simplifies configuration through convention-based methods.

However, the CTO spoke as if Spring Boot were an upgraded version of Spring,

capable of doing more than Spring can do.

With Spring Boot, Spring can be discarded.

They even said this was because my English was poor,

and that if I read more explanations in English, I would know that they were right. = =

Those of you who are considering joining the technical team, please take note:

don't let your understanding be led astray.

============================

There are really far too many tests to take during the interview.

Before the interview, I completed an online Java coding test and aptitude test at home, which took me about two hours.

On the day of the interview, I took a Java multiple-choice test, an English test, a logic test, and an English typing test, which took me about an hour and a half.

I had high expectations of the company and was willing to spend so much time taking the tests because of that. In the end, however, I was very disappointed.