Workplace reviews and discussion: 宏碁資訊服務股份有限公司

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.

宏碁資訊服務股份有限公司
Pros

1. 15 days of fully paid sick leave, with no documentation required when taking sick leave

2. Travel subsidies and occasional gifts

3. Located on the same floor as Daan MRT Station

Cons

1. Monthly salary is below the industry standard

2. Slow salary increases and limited opportunities for promotion

3. Extremely lean staffing: RD = SA + PG, but compensation is at the PG level

4. Responsibilities and authority are unclear. Supervisors only require that someone do the work, without caring who does it. They use delegation of authority as an excuse to make lower-level employees carry out tasks, but when resulting problems arise, they still only tell lower-level employees to figure out how to handle them.

(e.g. i. For project maintenance scheduling, the PM tells the PG to plan the schedule.

ii. For cost estimation, the PM tells the SA to independently assess the total workdays for PM + SA + PG, then tells the SA to use Excel formulas to calculate the actual amount and report it directly to the user.

iii. The PM tells the SA to discuss requirements directly with the customer.

)

5. There is a very high chance of being required to support projects using different technologies (e.g. someone who writes C# is assigned to maintain a Java project).

6. When user requests arrive by email, most supervisors do not first review and digest the content; instead, they simply pass the users’ emails directly to subordinates to handle.

7. Department policy follows a “user comes first” model. Even when users propose many unreasonable requests, if you want to reject them, you still have to come up with another solution as a substitute. In effect, this means fully accepting the users’ requests.

8. System development has no specification documents. The PM only tells you to look at the old program and rewrite it.

9. Outdated technology, insufficient development resources, extremely poor version control, and extremely poor integration → resulting in numerous problems after the system goes live.

10. No unified development standards → resulting in many ticking time bombs left in the code by former employees who have since left the company.

11. Takes on projects for government agencies

Reply
1
Agree
4
Disagree
0
Show all 1 replies