宇泰華科技股份有限公司

The interview process was fairly pleasant, but after talking with the CEO, I felt that I discovered a lot of problems.

The benefits seemed to consist of meals provided three times a day and transportation subsidies, which sounded pretty good.

The supervisor (？) from the same department seemed quite serious and dedicated when introducing the department's work. I thought they seemed like a nice person.

The CEO talked to me a lot about his dreams.

Then he told me many stories about successful entrepreneurs and said that his current product was just as impressive as the products invented by those great figures.

He didn't ask me anything about salary or anything like that, but from the conversation, I gathered that it was probably pretty bad XDDD

Because he admitted himself that an employee left for another company because it offered double the salary XDDDDDDD

Also, during the interview, he spoke rather unpleasantly about interviewees who rejected or disagreed with the CEO's ideas.

For example, he would often belittle other interviewees for lacking the vision to choose his company. He also belittled the companies of other very well-known entrepreneurs.

Personally, I feel that if the owner of a company keeps thinking that they are the best, I wouldn't really want to work under that kind of boss.

It feels like it would be a one-person show, with the boss's mood deciding everything.

And everyone underneath would just keep agreeing with him about how amazing he was.

Also, when I went to the interview, the HR person kept telling me the whole way there how great and amazing the CEO was and how full of dreams he was.

I didn't really feel comfortable saying anything to them.

So I just kept telling them:

Oh, he really does seem pretty impressive, and he's very different from other bosses—so unconventional XDDDD

Taking all of this into consideration, I felt it would be better to get away as quickly as possible. So when the CEO asked whether I was interested in pursuing our dreams together, I thought about it for a long time and then tactfully declined his invitation to join the team XDD

Before the interview, they first give you an assignment in the form of a ZIP file, which you have 1.5 hours to complete and return.

After passing the assignment, you go directly onsite for three rounds: HR -> team manager -> the company head (CEO?).

The conversations were all quite pleasant. There were no technical questions; they mainly discussed my experience and then asked more in-depth questions about areas they were interested in.

The only downside is that the salary offer was not very high, possibly because it depends heavily on seniority (they emphasized quarterly salary reviews).

A high degree of freedom; it’s fairly easy to try out new things.

Having three meals a day is really convenient, and there’s also milk and coffee (you can tell HR which restaurants you’d like to eat at).

You can genuinely take leave—it’s not just something they say.

You can directly see the results and data from your own code being used.

There is basically zero internal technical exchange within the engineering team… Everyone seems to be constantly chasing requirements.

Requirements > programming quality. Development time is often compressed, resulting in quite a lot of technical debt. If you’re a perfectionist, you’ll need to spend quite a bit of extra time dealing with it.

The acceptance process seems to have some issues; handoffs and system integrations can easily run into problems.

None of the systems I’ve encountered so far have tests written for them…

There is no code review, the code is quite messy, and the ways of using packages or underlying components are inconsistent.

This is a startup, so many things are not fully developed. If you only want to sit back and enjoy the benefits, a large company may be more suitable for you. If you want to create something, you can see whether there is any overlap with your career path. (It may feel a bit like setting foot on the New World of the Americas XD)

Free snacks, milk, and coffee

All types of leave are paid

Three meals provided

If you work overtime until a certain time, you can have snacks and take an Uber home

The company’s processes are chaotic; basically, whatever the boss says goes, and there are no real processes to speak of

The product has no distinctive features and has been burning money so far

It’s hard to say whether people with ability and ideas are valued, but those with a willingness to submit will definitely be valued

The HR staff were polite.

The work environment is nice.

The salary is acceptable.

The benefits are fairly good.

The interview area was too exposed and located in a central area, which made me feel insecure.

They told me directly that overtime would be required.

Despite being located in the science park, there is no parking subsidy for the park.

A network-connected Mac mini was provided for the coding test.

I interviewed for a frontend position at the company in 2018.

There was a coding test, but I was not informed in advance. The keyboard provided with the Mac mini was not very usable—the keys were stiff—so I used my own computer instead.

The coding test did not provide an environment. I chose React, and the build speed with CRA was acceptable.

I received no further response, and emails asking about the reason went unanswered.

There is a cup of water available to drink

The office is beautiful

The HR representative is very attractive

I applied online for the company's Junior Front-End and Back-End positions.

Afterward, HR called and said that I could interview for both positions, but for the coding test I could choose either React or Golang.

During the call, I told HR that I didn't know Golang, so React would give me a better chance to demonstrate my abilities.

At 2:00 on the day of the on-site interview, a different HR representative conducted the interview. As soon as I sat down, they first asked, “What would you like to ask?”

I was a little puzzled. Normally, both sides introduce themselves first and then begin asking each other questions. However, I started by asking about salary, working hours, company benefits, and so on.

(I later felt that this was my mistake. I should have first asked about the company's products, current plans, and future development before moving on to salary and benefits.)

I remember very clearly that this HR representative said:

“Salary”: I can't tell you; you can only discuss it with the CEO at the final stage.

“Working hours”: We have flexible working hours, with no clock-in system and no overtime pay.

Everything else is listed on 104 and follows the Labor Standards Act; you can look it up yourself.

In a moment, we'll test you on Golang. Is there anything else you'd like to ask?

At that point, I was actually somewhat displeased.

I had come a long way because I wanted to understand the company. Perhaps salary was not convenient to disclose by email, so I had no problem coming in person.

But for the other matters, I expected to hear something more specific, such as “What time does everyone usually arrive?”

Moreover, I had clearly said earlier that I wanted to be tested on React. Why had it changed to Golang?

The HR representative then said that, since that was the case, the company would pay my transportation expenses and I could stop the interview immediately.

They said, “From your attitude, I can tell that you are not suited to this company—or to the startup model.”

At that moment, I was speechless.

Just because you are a startup, does that mean you can bring someone in without explaining anything?

Besides, there must be some usual pattern for things like what time everyone generally arrives, right?

And, again, we had clearly agreed that I would be tested on React. How did it end up becoming Golang?

That has nothing to do with being a “startup,” does it?

Afterward, I apologized to that HR representative and said that perhaps my tone had been too sharp.

I wanted to understand what time most people arrived and left; I believed this was not an unanswerable question.

Only then did they say that most people arrived at 10 a.m. and left at 7 p.m.

I replied tactfully that perhaps I had not heard clearly and apologized.

They then said, “Are you going to apologize? This is very unfair to our company.”

But I had clearly just heard them say that the company had “flexible working hours.”

The reason I wanted to ask approximately what time people generally arrived and left was that this is a common HR way of glossing over the question.

However, I did not think too much about it at the time and simply apologized.

After the interview, though, when I thought back on it, I still believe they had not initially said, “Most of our people arrive at 10 a.m. and leave at 7 p.m.” They only said that afterward.

Afterward, we discussed Playsee's vision for development, including how it could compete with the two major giants, Facebook and Instagram.

I asked them how they would convince me to use Playsee instead of Facebook or Instagram.

To be honest, I could not hear a convincing reason in their answer.

As for the Golang coding test, of course I performed terribly.

How can you expect someone who only starts looking up variable declarations and loop syntax during the coding test to produce something good?

Moreover, there was no properly set-up environment for the coding test.

The candidate had to become familiar with their computer and find a usable environment, such as an online IDE.

It made me wonder how a coding test could be conducted so carelessly.

Shouldn't the company use a service such as CodePen or HackerRank instead?

Later, I opened the door to find HR and tell them that I wanted to use the restroom, but they were in a meeting.

When I returned from the restroom, I rang the doorbell twice. No one opened the door the first time; the second time, an engineer came out to let me in.

I then waited in the meeting room until 4:30, when their meeting ended, and a back-end manager hurried in.

During the interview, I expressed my confusion about the process, including why I was suddenly being tested on Golang, the conversation I had just had with HR, and what exactly I was being interviewed for.

The manager was very kind and said that although they knew I did not know Golang, they were willing to listen to my thought process and so on.

However, they also said that they were not clear about how the company had arranged the interview and were very surprised by my situation.

After we discussed and explained the coding-test questions, another manager came in.

However, this manager did not interact much, only looking at my résumé and asking about my expectations for the future.

Afterward, I asked the managers for business cards, but they said the company did not have any.

Therefore, even after the interview, I still did not know the names of the HR representatives or the managers.

I only knew the name of the HR representative who contacted me because we had exchanged emails.

Finally, I again expressed my apologies to HR.

I also offered some “suggestions” regarding the company's interview process, which had left candidates unclear about what was happening.

After I finished giving these suggestions, I knew very clearly that I would not join this company, and that there was about a nine-in-ten chance the company would not hire me.

Overall, this was a very poor and disappointing interview experience.

1. What the HR representative who contacted me said differed from what the on-site HR representative said, especially regarding the coding test.

2. The on-site HR representative said they did not have the authority to discuss many matters, which made the conversation very superficial.

3. HR directly stated that the interviewee's attitude was unsuitable for a “startup” company, and told me that I could accept the transportation reimbursement and end the interview immediately. If so, why insist on arranging an on-site interview instead of conducting a video interview first? A “startup” company should be more “tolerant” of video interviews, shouldn't it?

4. “Startup” may be an excuse for minor oversights, but it is not a “get-out-of-jail-free card.”

How to prepare for the interview:

1. Be well prepared for Golang.

2. Confirm with HR exactly what the on-site interview will cover.

3. Prepare your own environment, because they will not prepare one for you.

4. Adopt a “startup” mindset and tolerate every shortcoming.

Would I recommend this job? No. You can infer a great deal from the smallest details.

The HR girl is very cute

At the beginning of the interview, the young HR girl asked me to sit down in the meeting room. After I sat down, the very first thing she said was, "Is there anything you would like to ask?"... My inner thoughts at the time were, "Shouldn't you be the one to start the conversation first?... How could you ask me a question like that?!..." I then said that I had done a little research on the company's products. Only then did HR start talking about everything regarding the company. Next, another woman entered the meeting room and sat down. I don't know whether I failed to hear clearly or what, but as I recall, she did not clearly introduce which department she was the supervisor of. Then they started the standard interview process, chatting through a series of questions and answers. Finally, I brought up the compensation, but the female supervisor did not discuss it clearly either. Throughout the entire interview, I felt that neither of the two interviewers really knew how to conduct an interview.... After all, it is a startup company. In the end, I received a rejection email one week after the interview.

The HR staff were fairly friendly.

There was a hands-on computer test (they only asked whether I had brought a computer after I arrived; this was not mentioned beforehand).

The development environment on the testing computer had not been set up completely...

They said it was a startup, implying that overtime might be required, but also emphasized that working hours were very flexible.

When I asked HR about the average time employees leave work, they did not answer directly.

None

The link in the interview questions had a problem, yet HR did not provide sufficient notice.

A lot of time was wasted, and the entire interview process was also very strange. The interviewer seemed not to know how to conduct an interview.

The HR services are good.

I applied for a front-end position and was asked to write a mini application on the spot during the interview, but the computer didn’t even have the working environment set up. The technical interviewer repeatedly asked the same questions, and I couldn’t sense any leadership charisma. The company’s overall direction is also a big question mark. Not recommended. I really think they should consider Googling handout first instead of wasting interviewees’ time.

None

Constantly working overtime

Constantly working overtime

Constantly working overtime

The supervisor can't manage at all—it's absolutely terrible

Not a single thing the boss promised was delivered

The supervisors are the ones who get all the benefits

And the supervisor is very selfish. A company where you don't need to waste your time.