Published on (UTC)
This post was submitted by a user and reflects their personal experience or opinion. The publication date is not an employment or interview date.
Interview experience:
At the time, I was interviewing for a programming-related position.
Perhaps because I am male, no particularly strange topics came up during the interview.
They asked the usual questions about why I wanted to take the job and what I knew.
Perhaps, as the reviews said, if you are a woman, there may be some strange and harassing questions.
At least during the time before I left the company, I never saw or heard of anything like that.
The practical test involved very simple database filtering syntax.
Although it was simple, I was not familiar with the syntax at the time.
I had not graduated from a specialized program either, and they even gave me time to look up the relevant usage online.
Work experience:
Since I knew almost nothing, the website I had to work on at the beginning included installing a LINUX system.
Things like mounting virtual devices and that terrifying command-prompt-like stuff,
as well as some software and plugins that needed to be installed, and so on.
Because my colleagues worked in different fields and were unfamiliar with these things, I had to figure everything out myself.
If I could not find the answer online, I had to find another way and ask people in outside groups.
In the process, I learned not only technical knowledge,
but also the skills and wisdom involved in asking questions.
I think this was the only time in my life that a company was willing to hire a complete beginner who knew so little.
After all, from an operator's perspective, you have to assess the possibility that things might become difficult to complete.
Although that period was painful, finding the answers and actually implementing them did give me a sense of accomplishment.
This is almost impossible in a large company—they would never let you do things this way XD
During this period, I also learned some aspects of management, which was quite interesting.
Unfortunately, because of my personality, I was unable to learn everything.
In the meantime, I also saw colleagues come and go, each for different reasons.
Looking at things now, the internet is full of one-sided criticism.
Perhaps my perspective is not objective enough, but sometimes we cannot stay in a greenhouse forever.
Do you want to think from an employee's perspective, or look at things from the perspective of a business operator?
I do not want to speak on the company's behalf, so I will remain reserved on this point.
Besides, taking a position would be unfair to others.
After all, I am not a woman, so I cannot speak for those who interviewed there.
Finally, what I want to say is:
Entering this company was both my good fortune and my misfortune.
Perhaps in this life, we may happen to gain an opportunity through a choice, while losing something else.
A unique company that can put this kind of pressure on you probably no longer exists.
This was a rare opportunity, and looking back now, I still treasure it deeply.
I also hope everyone can find a company or business that suits them or treats them well.
Interview experience:
I cannot think of any shortcomings.
For ordinary people, it might not be very challenging.
You did not need to be familiar with frameworks, and there were no difficult JS questions or questions about JS pipes, database usage, frontend techniques, and so on.
Oh... I suppose that is a shortcoming.
Work experience:
Overtime.
Because I could not get things done, working overtime was only natural (and, as others have said, it was indeed unpaid).
Of course, this was also a problem with my own abilities.
So I ended up going to the company on holidays to continue learning.
I also did not know how to use frameworks,
and companies that take on projects are usually focused on completing them as quickly as possible.
They do not pay much attention to the frameworks used in this regard.
I spent a lot of time secretly researching this, as well as how to bind values on the backend to prevent
attacks such as XSS and other ways of addressing network security.
However, this also seriously held back my own work progress.
I could only spend small amounts of time researching these things while completing what the company needed.
Perhaps the boss wanted to put pressure on me and assigned another case to me as well.
As a result, I had to handle not just two cases at once, but also deal with many bug-related issues.
By the time the project schedule was delayed, I had already given up.
I simply decided to take things as they came.
Because I could not get things done and did not want to work overtime,
it became a vicious cycle, and in the end, everything ended badly.