百商數位科技股份有限公司

The interview begins with an initial meeting with HR. HR mainly focuses on understanding your past work experience, such as the types of marketing-related work you were primarily responsible for, the areas you are particularly good at, and whether you have experience with course planning, content production, event execution, or other related work.

Because this position covers a fairly diverse range of responsibilities, it is not limited to general marketing copywriting or social media management. You will also work on course planning, instructor collaboration, video and audio content production, and the planning of online and offline events. HR will therefore also ask whether you have experience collaborating with different departments or external vendors, how you usually schedule your work, and how you handle unexpected situations.

Next is the interview with the hiring manager. This stage involves a more in-depth discussion of your past marketing planning experience. The manager will ask whether you have ever been responsible for a complete marketing project, and how you arranged everything from initial planning and content development to subsequent promotional execution. If you have experience promoting courses or products, you can also share how you planned promotional content, wrote copy, or increased exposure through social media and events.

There was also discussion of cross-departmental collaboration, such as how you would communicate requirements and confirm schedules when working with design, video and audio, or other teams to complete a project, as well as how you would coordinate when progress does not go as expected. The manager also wants to understand your familiarity with short-form videos, social media marketing, and online events. You do not necessarily need extensive experience in every area, but it seems they hope candidates have a basic understanding of different types of marketing operations and are willing to take on new responsibilities.

Overall, the impression was that the company hopes this position will involve more than simply executing marketing tasks. It requires a certain level of planning ability, including thinking from the perspective of a course or product about how to package content, attract the target audience, and combine different promotional methods and activities to achieve marketing results. The work is fairly diverse, with a broad range of areas to get involved in.

Overall, the interview atmosphere was fairly relaxed. The manager also learns about candidates’ ideas through their past work experience rather than limiting the discussion entirely to what is written on the résumé. If you have worked in marketing planning, social media content, event execution, or project coordination, you can share those experiences. Even if your industry background is not exactly the same, it seems possible to find connections between your experience and the role.

The company is some distance from the MRT station, so if you are in a hurry, it feels like the only way to arrive on time is to ride a YouBike.

The position I interviewed for was Android Engineer. The process started with an aptitude test, followed by a written test that took approximately 20 minutes. The written test was mainly intended to gain an initial understanding of the candidate’s technical abilities as an engineer, so it would be helpful to review the fundamentals of Java beforehand. After the written test, I had an interview with HR. This stage mainly focused on understanding my previous work experience, the development projects I had been responsible for, and why I wanted to change jobs. We also discussed which programming languages I had primarily used for development, my usual responsibilities, and the types of app projects I had previously participated in. Next was an interview with the hiring manager, who asked about my previous Android development experience, including the technologies I had mainly used, the types of apps I had developed, and my responsibilities during the development process. Since the company’s current development environment is still primarily based on Java, the manager also paid particular attention to my Java-related development experience during the interview. If your previous work has mainly involved Kotlin, you may need to elaborate more on your familiarity with Java and whether your past development experience can transition smoothly to the company’s current technical environment. Based on the job responsibilities, the company works on a fairly diverse range of app development projects, including finance, telecommunications, retail, and insurance, with investment and wealth management, stock, and insurance apps making up the majority. Therefore, in addition to basic Android development skills, an understanding of app interface design, feature implementation, and technologies related to network communication should also be important aspects of this position. Overall, the interview process was quite comprehensive. However, because most of my previous work experience involved developing with Kotlin while the company currently primarily uses Java, and considering the differences in the technologies used by both sides as well as how well I would adapt to the role, I ultimately decided to politely decline the offer.

The company takes on projects across a relatively diverse range of fields, involving different industries and types of products. It may take some time to become familiar with the requirements and development processes of each project. In addition, the development technologies currently used are fairly fixed; it would be better if there were more opportunities to apply or learn different technologies in the future.

At the beginning, you take an aptitude test on a computer, followed by an initial interview with HR. The interview mainly covers your previous work experience, the projects you have been responsible for, and the specific tasks you handled in those projects. They will also ask how you usually coordinate and collaborate with other departments, as well as how you typically handle vendor communication or situations where requirements need to be adjusted.

The subsequent interview with the hiring manager focuses more on sharing your past project experience, such as the types of projects you have participated in, the problems you encountered during execution, and how you coordinated resources and solved problems. In addition, the manager will ask about your understanding of financial products and related websites. The impression is that they want to assess the interviewee’s familiarity with the fintech field and whether they have relevant understanding and practical application skills.

Overall, the interview atmosphere is fairly standard. Most questions revolve around past experience and actual work situations. It is recommended that you organize in advance the specific responsibilities you handled in projects, your cross-departmental collaboration experience, and how you dealt with problems, as this will make it easier to perform well during the interview. The interview process provides a better understanding of the work involved in fintech-related projects, and the manager’s questions also offer further insight into the company’s expectations for project managers. For those who want to develop in fintech or related products, it is an opportunity to gain experience in a different field.

The overall work environment is acceptable. However, the office space and equipment feel somewhat dated, although they have basically everything needed.

This interview was for a Finance Specialist position. Overall, the interview process was similar to that of a typical company: HR conducted an initial interview, followed by an interview with the hiring manager. The initial interview mainly focused on understanding my personal background, field of study, and whether I had any relevant part-time or internship experience. Since I had just graduated and was looking for my first full-time job, I also discussed my expectations for future employment and my understanding of finance-related work with HR. During the subsequent interview with the manager, the focus was more on the actual job responsibilities. Based on the job title, I initially assumed the role would mainly involve handling accounting matters, invoices, and basic financial administrative tasks. However, after learning more about it, I found that the scope of work was actually quite broad. In addition to accounts receivable and payable management, invoice issuance, and preparing payment requests, the role also involved bank payments, petty cash management, preparing loan documents, and assisting accountants with audits and account reconciliations. Besides routine accounting tasks, the position also required handling administrative matters such as scanning and filing contracts, uploading documents to the system, managing company seals, and processing seal usage. It seemed to be a position that required balancing both financial operations and administrative procedures.

I feel that, in addition to requiring a basic understanding of numbers, this position also places great importance on being organized and having the patience to handle relatively tedious tasks. Since the work does not consist of just one type of task, I might need to handle invoices, payment requests, reconciliations, document organization, and other tasks assigned by the manager at the same time. Therefore, the ability to prioritize tasks and avoid overlooking details is also quite important. This interview also gave me a deeper understanding of the work of a Finance Specialist. I used to think that finance-related work mainly involved handling numbers and checking accounts, but after reviewing the actual job responsibilities, I realized that the scope of work for Finance Specialists can vary considerably between companies. In addition to basic finance and accounting tasks, this position also included many internal administrative procedures and document management duties, making it a role that involves interacting with different departments within the company. Becoming familiar with accounts receivable and payable, cash flow reconciliation, payment procedures, and the preparation of related reports should be helpful for understanding the company’s overall financial operations. However, I feel that this type of work would still require some time to become familiar with the company’s procedures, especially matters involving cash flow, profit sharing, and refunds. It is necessary not only to understand how to carry out the procedures, but also to know how the information should be checked and whom to contact when abnormalities occur. For people who already have experience in finance, accounting, or related administrative work, it should be easier to apply the experience they have accumulated in the past to the job.

In the end, I did not receive an offer. In my case, since I had just graduated and was looking for my first full-time job, I lacked direct practical experience in finance or accounting, so I suspect there may have been some gap between my experience and the level of experience and familiarity required for the position. Although many of the responsibilities listed in the job posting appeared to be learnable from the basics, the actual scope of work was fairly broad. The company may still have hoped that applicants would have a certain foundation or previous experience with similar procedures, allowing them to adapt more quickly after joining. Overall, the interview experience was quite positive. It also helped me understand more clearly what a Finance Specialist is actually responsible for and what the company expects from the position. For a recent graduate, this was also a valuable opportunity to learn about workplace requirements~

It would be helpful to provide a clearer explanation of the Finance Specialist’s day-to-day responsibilities, such as accounting tasks, accounts receivable and payable, expense reimbursement, and report organization, so that new employees can grasp the key aspects of the job more quickly.

I interviewed for a project manager position this time, and the overall process went quite smoothly. It started with an aptitude test, followed by an interview with HR, and finally a conversation with the hiring manager—about three stages in total. There was no separate written test.

The HR interview was more like a conversation, mainly covering my past work experience, reasons for changing jobs, and why I wanted to apply for this position. The overall atmosphere was quite relaxed, and they did not keep asking highly pressuring questions. Since the company is in the fintech industry and I happened to have previously worked on projects related to financial products, including experience following projects from requirements confirmation all the way through implementation, the manager kept exploring this area. For example, they asked how I handled problems, communicated with R&D, and responded to changes in requirements. The manager also discussed the current development of fintech and AI. Many companies are now starting to incorporate AI into existing products or services, but the real difficulty is not AI itself; it is how to organize the requirements clearly and then enable the technical team to implement them smoothly. After the conversation, I actually felt that this position was more challenging than I had originally imagined.

During the interview, they also asked how I would handle constantly changing customer requirements, and whether I had encountered any particularly difficult situations in projects I had handled before and how I ultimately resolved them. It would be helpful to prepare along these two lines. Although I ultimately did not receive an offer, it may have been because the company wanted to find a candidate whose background was a better fit for the job requirements and who had more extensive relevant practical experience. Overall, however, it was a good interview experience. The manager seemed to place considerable importance on real-world cases; compared with talking about theory continuously, sharing genuine experiences makes it easier to leave an impression.

If you do not live in Taipei City and commute by public transportation, the commute is relatively long.

This interview was for a project manager position. It began with a simple aptitude test, consisting mostly of straightforward, intuitive questions. After that, there was an interview with HR. The HR representative was quite friendly. The initial discussion mainly focused on my work experience, the responsibilities I had handled in the past, and why I wanted to apply for this position. During the interview with the manager, we discussed my project execution experience in greater depth, as well as my understanding of the fintech industry and related technology applications.

Since the company is involved in fintech, software development, and systems integration, in addition to being able to manage project schedules and coordinate across different departments, candidates also need to have a certain level of understanding of technology and actual business needs. If you have previously worked with financial systems, integrated third-party services, or participated in project planning and execution from 0 to 1, I think these would all be good examples to share during the interview. Projects often involve requirement clarification, feature planning, development and testing, and finally going live. Along the way, there are actually many matters that require communication and coordination—it is not simply a matter of assigning work and checking progress.

In particular, integrations involving payment flows or different systems may involve several different teams. Sometimes, a customer’s requirements do not completely align with what is technically feasible. In such cases, someone needs to clarify the requirements and help both sides find an executable approach. If you have similar experience, it can not only demonstrate your familiarity with the project process but also show the manager how you think through and handle problems.

Overall, the interview process was good. Both HR and the manager were quite friendly, and the interview also provided an opportunity to better understand the direction of the role. I think this type of position is worth considering for people who are interested in fintech, software systems, or AI applications. In particular, those who hope to do more than a single administrative or execution-focused job in the future, and instead gradually build up project planning and cross-disciplinary integration skills, may find opportunities for development in this role.

The office décor feels somewhat dated. However, HR mentioned that the offices on the 17th and 15th floors were expanded and have newer furnishings. I saw photos, and they seemed pretty nice.

This interview was for a project manager position, and overall, the process went quite smoothly. It started with an aptitude test, followed by a conversation with HR, and finally an interview with the manager. There was no additional written test.

The HR representative was very friendly. The initial conversation mainly covered basic work experience, reasons for changing jobs, and expectations for the next position. The interview with the manager went into more depth. In addition to discussing projects I had handled in the past, we also talked about fintech-related applications and the practical use of AI technology at work.

I got the impression that the company expects more from this position than simply tracking project progress, holding meetings, or organizing documents. They also hope candidates understand the technology and business requirements behind a project. For example, experience with system development, integrating third-party services, or participating in a project from 0 to 1 are all valuable topics to share.

If you have worked on payment flow integrations in a previous position, I think it would be worthwhile to prepare this part carefully. In addition to introducing the work you were responsible for, you could discuss why the integration was needed, what problems arose during the process, and how you communicated and coordinated with engineers or other departments to successfully launch the project.

After all, projects of this kind usually do not end once the functionality has been built. Requirements need to be confirmed beforehand, development progress tracked and testing arranged along the way, and problems coordinated and resolved when they arise. Therefore, the manager would probably also care about which parts of a project the candidate has actually participated in and how they handle problems.

Also, if you have experience driving a project from 0 to 1, that would be very suitable to share during the interview. For example, you could explain how an initial idea was gradually developed into clarified requirements and an execution plan, and how you coordinated with different teams step by step to complete the project. Compared with simply saying that you have project management experience, I think using a concrete example makes it easier for the manager to understand your abilities.

The AI aspect is also worth paying attention to. There are increasingly more possibilities for AI applications in the fintech sector, so in addition to knowing what AI can do, understanding how to truly apply the technology to products or practical business operations should also be an important part of the role. Possible areas to consider include improving the user experience, increasing operational efficiency, and integrating AI with existing systems.

Overall, I felt that the more challenging aspect of this position is the need to understand technology, business requirements, and project progress at the same time. Although a project manager does not necessarily need to write code, they should at least understand what the engineering team is doing and be able to clarify the needs of clients or internal teams before communicating them to different stakeholders.

Therefore, experience limited to tracking progress and arranging meetings may not be enough. Candidates who can further share how they handled system integrations, cross-department communication, or problems encountered during project execution should have an advantage.

Overall, the interview process was quite good. Both HR and the manager were very friendly, and the interview also provided an opportunity to better understand the responsibilities of the position. I would suggest that anyone interested in applying first prepare several concrete projects they have participated in, especially which parts they were responsible for, what difficulties they encountered, and how they ultimately resolved them. These should all be useful interview material.

I ultimately decided not to join, mainly because I later received an offer from another company. After considering the job responsibilities and daily commuting time, I ultimately chose the opportunity with the more convenient commute.

The position I applied for was AI Engineer at Baishang Digital Technology. I was initially a little nervous about the interview, but after going through the process, I felt that the overall atmosphere was more relaxed than I had expected. The interviewers were also quite friendly and did not make me feel too pressured. In addition to learning about my professional abilities, the interview also gave me a clearer understanding of the company’s business, work environment, and future development direction. The process began with a perceptual assessment. I had originally thought that the interview would immediately start with technical questions, so I was surprised to find that there was this additional step. It also gave me some time to adjust my state of mind. After completing the perceptual assessment, I proceeded to the HR interview. This stage mainly covered my previous work experience, motivation for seeking a job, future career plans, and expectations for the AI Engineer position. The HR representative was quite friendly, and the overall conversation felt more like a two-way exchange rather than simply answering questions, so the interview was not as stressful as I had imagined. The benefits were also introduced, including a guaranteed year-end bonus, additional bonuses through two performance evaluations, holiday allowances, overseas employee trips, health checkups, and more. One particularly distinctive benefit is that the company provides free dinner from Monday through Thursday, which is relatively uncommon but quite nice.

The final interview with the manager mainly focused on my past AI development experience, how I applied models, and my level of familiarity with related technologies. In addition to the basic concepts, I was advised to prepare projects I had actually worked on, such as how I selected models, processed data, and improved the quality of model responses. During the interview, I also gained a deeper understanding of how AI technology is applied in actual product development. After looking at Baishang Digital’s website, I learned that the company currently specializes in fintech and system integration. Working there would likely provide opportunities to encounter different types of application scenarios, which would also help me build my technical capabilities. Overall, the manager interview gave me a clearer understanding of the job responsibilities and allowed me to gain deeper insight into how the company applies AI technology and practical development capabilities. I also had the opportunity to exchange ideas about technical directions during the process, making it a valuable experience. I believe Baishang has strong industry experience and a solid direction for technological development. If someone hopes to continue improving their AI development skills in a related field, this position is worth considering. However, because most of my past experience involved participating in related projects or research at school, I had some exposure to similar technologies but relatively little practical experience applying them in the workplace. This may have been a gap between my background and the company’s current job requirements, so I ultimately did not receive an offer.

It seems that the company has certain requirements for practical experience applying AI-related technologies. If most of your past experience has involved participating in projects or research at school, you may still need to accumulate more hands-on application experience to better meet the job requirements.

I applied for the Project Manager position at Baishang Digital Technology. At the beginning of the interview, I first took a cognitive assessment, which was likely intended to understand the applicant’s basic cognitive and reaction abilities, as well as their personality fit, among other factors, and would serve as a reference. After completing the assessment, I interviewed with HR, primarily discussing my previous work experience, motivation for applying, career plans, and understanding of the project management role.

Since project managers need to coordinate with the sales, engineering, and design teams, in addition to project planning and execution abilities, communication, problem analysis, and adaptability are also important competencies. Through the two-way exchange during the interview, I was able to gain a better understanding of the company’s expectations for the position. We also discussed the company’s benefits, which include guaranteed year-end bonuses, performance evaluations and rewards, holiday bonuses, employee travel, health checkups, and other benefits. Overall, they sounded quite good.

Finally, I interviewed with the manager. The discussion mainly focused on my previous project management experience, requirements communication, cross-departmental collaboration, and potential problems that might arise during project execution. The company placed considerable emphasis on previous project-based work experience, as well as how applicants interact with clients, colleagues, and supervisors. Since Baishang Digital’s business covers areas such as fintech, systems integration, and AI software platforms, project managers need not only basic project execution abilities but also an ongoing understanding of digital product development processes and the ability to establish effective communication with technical teams. Overall, the manager interview gave me a more concrete understanding of the position and showed me that the company values project execution quality, teamwork, and work efficiency. My impression of the role is that it offers opportunities to work on project needs across different industries and participate in the complete process, from requirements confirmation and planning and execution to product delivery. This would help build practical cross-industry experience while further developing skills in requirements analysis, resource integration, and project risk management. In particular, in addition to its existing fintech products, the company continues to invest in the development of AI software platforms. For job seekers who hope to understand emerging technology applications and expand their experience in digital product management, I believe the position has considerable development potential. Later, I received an offer from another company, and the responsibilities of that position were more closely aligned with my previous work experience and professional background. After an overall evaluation, I ultimately decided to accept the other company’s offer. Nevertheless, my overall impression of this interview experience was still quite positive, and I gained a lot from it~

It seems more suitable for PMs with a certain amount of work experience and less suitable for newcomers who want to start learning from scratch.

For this engineering position interview, the overall process was a bit more comprehensive than I expected. It started with a perceptual assessment, which seemed to be designed to measure potential traits or something along those lines. After that, there was a 20-minute written test. Since the time was fairly limited, you had to get into the questions quickly. The questions focused more on conceptual understanding and practical application, and some of them really required a bit of thought. If you usually write code and are familiar with your own technical skills, you probably wouldn’t be completely unsure of how to approach them.

After the test, there was an interview with HR, mainly covering my résumé, previous work experience, why I wanted to join, and my understanding of the company and position. The conversation did not feel particularly stressful overall, and they also explained the company’s policies and benefits. After that, I interviewed with the department manager. The manager had considerable technical depth and kept asking detailed follow-up questions based on what I had written on my résumé, rather than just stopping at surface-level questions. They asked things like how projects were carried out, why I chose certain approaches, what problems I actually encountered, and which parts I was personally responsible for. If you list certain technologies or projects on your résumé, it felt like you really need to understand the technologies used throughout the development process, to demonstrate that you genuinely participated rather than only having superficial exposure. However, the manager did not seem intent on deliberately stumping me. It felt more like a technical discussion, with further questions and elaboration after each answer, so the conversation was actually quite worthwhile overall.

Overall, the interview process was fairly comprehensive, including the written test, HR interview, and manager interview. Although I was a little nervous at first, all of the interviewers were easy to communicate with. For people with hands-on development experience, I think preparing the projects you have worked on and the technical details is much more important than simply memorizing a bunch of common interview questions.

The company is a little distance from the MRT station, so it takes some time to walk there. Other than that, I personally thought everything else was okay.

After speaking with the supervisor, I felt that the job responsibilities aligned quite well with what I had originally expected. The overall interview atmosphere was also good, and the supervisor was very easy to talk to. The company benefits also seemed quite good, such as free dinners, overseas company trips, and occasional buffet meals at company gatherings. The atmosphere among employees also seemed good; I observed that many employees were holding meetings and discussions in the various open meeting spaces.

The office environment felt a bit old, and the restroom was also slightly small.

Overall, the interview experience was good. The manager directly explained the job responsibilities and team division of labor, and also discussed issues that had actually arisen, rather than simply going through the résumé question by question. The interview atmosphere was fairly relaxed, and communication was direct. The minor drawback was that there was quite a lot of information, so I had to identify the key points myself at the time. If you are interested in the position, I recommend learning about the job responsibilities beforehand and bringing relevant practical experience to the conversation, as that will make the interview more rewarding. Overall, it was a very positive interview experience.

The building feels somewhat old. The interior decoration is relatively traditional, and the soundproofing is also somewhat inadequate.

The company team has a harmonious atmosphere, and colleagues get along well with one another. When work-related problems arise, everyone is willing to help each other. Supervisors are willing to spend time guiding and teaching new employees, and they are also very patient in communication. The company provides new employees with stationery and a subsidy for pre-employment health examinations. Each employee is provided with one computer and one monitor, which is very convenient for office work; the office environment is relatively quiet and suitable for concentrating on work, but it is not dull. If you occasionally feel like chatting, you can start a conversation anytime without feeling particularly constrained. Meetings are also held regularly to confirm project progress and discuss problems encountered during implementation, allowing the team to identify issues and adjust direction promptly. Overall, the work atmosphere is comfortable and well suited to steadily building experience.

The nature and workload of the work vary across departments, and during peak seasons, some units may have a heavier workload. Project-based work requires communication and coordination with different departments, so it takes some time for everyone to adapt to working with one another.

I have been working as an R&D engineer at this company for nearly six years. The company's working hours are fairly flexible: employees can start work anytime between 8 and 10 a.m. This is convenient for people with longer commutes or those who get up a little later, as they can adjust their schedules freely. In addition, free dinners are provided from Monday to Thursday. The General Affairs team usually opens the bento-ordering form around 3 p.m. for employees to place their orders, and a different restaurant is selected each week. If you discover a new restaurant, you can also make a request to the General Affairs team, which is a nice benefit. The company also holds gatherings for events such as the Mid-Autumn Festival and Christmas. The Employee Welfare Committee chooses the restaurant—usually a fairly upscale buffet restaurant in the past—or arranges for catering to be brought in and set up.

As for relationships with colleagues, I get along quite well with everyone. When someone encounters an issue, colleagues are generally willing to help one another, making it a warm and supportive environment. Personally, I feel that the company's overall performance is relatively stable, and its systems are gradually becoming more complete. Employee benefits also seem to be continuously adjusted and have indeed improved. In addition, my manager's management style is relatively flexible and does not tend to interfere excessively with details. If I have an idea, I can bring it up for discussion. I feel that the work content is quite helpful for building practical experience. If you want to learn technical skills, this is a suitable place to develop and hone relevant experience.

The workload and level of busyness can vary between departments and depending on the number of projects. The work requires fairly quick reactions and efficiency, but it becomes manageable after a period of adjustment.

1. Both HR and the interviewing manager were friendly.

2. It seemed that they did not mind candidates switching from other industries.

3. The company benefits sounded pretty good (flexible work arrangements, free dinner boxes, etc.).

4. An opportunity to learn about finance-related information and products.

5. The environment looked clean, and employees do not need to clean it.

The position I interviewed for was PM. When I applied, I saw that they were hiring 1–4 people, which made me a little worried. I was afraid it might be a terrible company, and that was why they had so many openings…

However, strictly speaking, my previous industry was more related to food or catering. I mainly helped some foreign companies set up factories in Taiwan. Although I had several years of PM experience, I did not really have any connection with digital financial products or apps, so when I received the interview invitation after applying, I thought I might as well have a chat.

The interview process started with being taken to a meeting room to fill in basic information and details about my previous experience. The HR interviewer was quite friendly and went over my résumé in a conversational manner. They also asked why I wanted to transition from traditional industries to digital. I honestly said that I was not very familiar with financial processes. I had only self-studied some basic Python courses a while ago, and the concepts of the parameters were still quite vague to me, but I was interested. My main consideration was that the rise of AI has been a major direction in recent years and is also a trend for the future. HR said that was fine, and that they mainly looked at personal characteristics and one’s attitude toward learning.

(My personal consideration was also that the overall atmosphere in the tech industry might be more lively, and that it would be less likely to have a military-style work environment where even using your phone is not allowed….)

The second interview was with the department manager. That manager spoke a little slowly but was quite humorous and seemed very friendly. Maybe they were also worried about scaring candidates away? They openly said that the PM department was very busy. Although it was not the kind of military-style environment I had been worried about, where you cannot use your phone or eat, the workload was quite heavy. It was normal for each person to have more than 10 projects running at the same time, but the performance bonus sounded pretty good.

The main responsibility was managing the processes of app projects. There were also projects involving cooperation with government agencies or major companies such as Chunghwa Telecom and Mega Financial Holding. Since most of the projects involved apps or maintenance and operations, in addition to negotiating and communicating with external parties, the role also required extensive coordination with internal engineers, IT staff, and other relevant personnel. There could occasionally be plugin-related situations as well… so strong communication skills across different parties and good time management were very important.

I was asked whether I could adapt to an environment with frequent changes and a large volume of projects, where I would need to manage schedules and risks every day. I said that there had also been many similar tasks at my previous company, and that I was quite willing to take on the challenge of switching industries.

About a week later, I received a call from HR with an offer, and the salary met my expectations. However, at that time I had received another offer that was closer to home, so after considering it, I politely declined. I’m sharing the interview process as a reference for anyone interested in applying.

PS: At the end, I discreetly asked about the reason former employees had left. They said that because the company is related to financial products, most people pay attention to stocks, and it seemed that some left after achieving financial freedom.

1. It sounded like there were quite a lot of projects, although that is a common issue in the PM industry…

2. Too far from the MRT station.

3. I used the restroom, and it was somewhat far from the office area. It was near the emergency exit, which was inconvenient, and there were very few stalls.

I've been with this company for two or three years, and I've gotten along quite happily with my colleagues. It never feels too dull, and the overall atmosphere at the company is fairly simple and uncomplicated~

It's just that the commute to work every day is a bit far...

The experience of interviewing for the project management position was quite good.

My previous job was in a traditional industry, and the office was basically like a factory, so this time I paid more attention to the work environment when looking for a job.

The company is conveniently located, and the office environment is comfortable. I took a quick look at the hardware, pantry, and so on, and they seemed quite OK. It made a good first impression.

During the interview, the HR representative and the other interviewers were friendly. Their way of asking questions made me feel relaxed; they did not put on airs or seem cold and distant. It felt like there would be quite a lot of room to work independently and make my own contributions.

The office employees appeared to be relatively young overall, which was very different from my previous job~ The atmosphere also seemed pretty good.

It would be better if they could explain the job responsibilities in more detail~ But other companies have the same issue too.

Occasionally getting off work on time

The toilet is very retro

I don't know about Baishang, since they keep claiming that employees are the company's most important assets. Anyway, it's considered the same company as Xingxi.

As for Xingxi and the others, you'd better not go:

Baishang + Xingxi + Shuma Investment Advisory have 110 employees

Baishang probably has 80 or 90

Xingxi has around 12 or 13

Shuma probably has only 1 salesperson

When I interviewed at Xingxi, HR slowly said that they had more than 100 employees. Then the supervisor came in and asked a few simple yet abstract questions. After sharing a few ideas, the supervisor said that four experienced employees would train new hires. I received an offer that day, thought about it for a while, and joined.

Before joining, I called to ask HR about Xingxi and Baishang.

The answer I got was that HR had already left work at 6:00 p.m., so I assumed this was a normal company.

After joining, I discovered that the interviewers were from Baishang. The experienced employees at Xingxi were also extremely busy themselves, so they could only take a hands-off approach. Things kept being thrown at me from beginning to end. Later, I checked 1111 and found that Xingxi originally seemed to have more than 20 employees, right? So there were 20-plus new hires who had been lured in like me, while the others were mostly in their thirties.

The restroom was really the worst area. The water dispenser, refrigerator, and food steamer looked perfectly normal, but the toilet stalls had toilets that were close to breaking down, with no flush valves or bidet seats. The doors didn't have rotating handles; they had an extremely old-fashioned latch that was very difficult to open. I almost couldn't get out.

The group-chat situation also made me uncomfortable, because the clients were stock-market teachers, so we had to produce videos, apps, courses, and so on. Every day, the boss would ask us in the main group chat to leave comments under the videos and report back in the main group. Apart from Outlook, I had no way to contact the people assigned to train me. After dumping things on me, they would make a dramatic disappearance, and occasionally I would see them working alone, frantically, in the conference room.

In short, I feel pretty unlucky. I was lured into the company, the stock market crashed on my first day, an earthquake happened two days later, and then I was left to fend for myself. I immediately decided to leave before things got worse.

1. Convenient transportation

2. Friendly HR

3. Work laptop provided

1. It’s truly a traditional industry… even the toilet is close to breaking down. The onboarding notice said, “Welcome to our ‘family.’” In reality, it’s a mix of traditional industry + startup + tech… I thought I’d be able to work regular hours, but it turned out I had to work overtime even on holidays—with free overtime dinners.

2. I interviewed for a position at Galaxy Company, thinking it was product planning, but after joining I discovered I had to do everything and wear multiple hats. It seemed like I was responsible for anything remotely related… Am I really a planner? Or am I customer service, a social media editor, a marketing planner, a salesperson, and a video editor? During the interview, I was told I would mainly deal with clients and engineers, but suddenly I had to handle consumers…

3. During the interview, they said several people would train me, but in reality I was left to fend for myself. Every day, I was dumped a pile of documents, forms, and videos. They told me to study them thoroughly, and then that was it… Everyone else was extremely busy, either in meetings or answering phone calls. Within just a few days of joining, I was seriously overwhelmed; I was even worrying about work in my sleep…

4. I clearly said beforehand that I had no experience in this area, only some general work experience. I still got hired, but escaped after just a few days 🏃‍♀️ On my first day, I had lunch with a coworker, who even said, “You really need to think this through…”

5. The interviewer was an employee of the parent company next door… During the interview, I thought the decor was so “homey,” so maybe working there would be comfortable. In reality, it was just… yeah 😐

6. The people there seemed to think, “We’re paying you, so there’s nothing wrong with doing a little extra…” On my second day, customer service already asked me to learn about a huge number of things and even hoped I would support them on my “days off.” The business hours were clearly Monday through Friday, 9:00–18:00, and I wasn’t even in customer service…

7. The lunch break was only one hour, starting at 12:30. There weren’t many restaurants nearby either, so after eating, there was basically no time to rest during lunch…

8. I reported the situation to the HR manager, who had an expression that seemed to say, “That’s just how this job is.” Yeah 🤔 Wearing multiple hats and working overtime on weekdays and holidays was considered normal. To be honest, after the interview, I called the HR manager that evening to say I would accept the offer, because the person who answered the phone said the manager had left at 6:00. The official website also stated that weekday business hours ended at 6:00. Who would have known that the Galaxy department would be like this?

9. The person training me said I should start as an assistant because previous new hires couldn’t immediately plan a new app. I was asked to handle some administrative procedures, and then I had no idea what kind of assistant I actually was. I had thought that having worked at Kura Sushi meant I had pretty good stress tolerance, but after just a few days, I felt that the internal operations were a complete mess. It was entirely being held together by a few people with excellent stress tolerance. I couldn’t even smile on my first day, so it was better to run away.

The HR staff are quite friendly.

The team leader surnamed Tseng from the Project Department had an expression that made me wonder what exactly they were being arrogant about. During the interview, they kept making clicking sounds.

I really don't understand why some people take such a high-and-mighty attitude as interviewers. If they can't process things well enough to understand what I'm saying, is it really appropriate to blame others?

In short, the company seems to offer fairly good benefits, but I can only laugh at the fact that someone like this can become a team leader. It might be better not to join after all.

The interview questions weren’t difficult.

It felt like the supervisor tested me on technical questions they themselves weren’t very familiar with... They insisted that the interviewee’s answers were wrong, and when the interviewee argued their case with sound reasoning, the supervisor privately complained that the interviewee was being overly argumentative... Speechless.

Pros

The interviewer said this place is basically a contract-based job

There are no advantages....

A strange company; you can't find anyone normally.....

None

I interviewed with a very strange company for a Java engineer position. There was no written test; instead, two managers conducted the interview. One female manager kept asking whether I knew how to do certain things. At one point, I was simply trying to clarify what she meant, but she said that during the Q&A she felt I lacked “ambition” (I was probably wearing a giant question-mark expression at the time). Then she herself even got the “CR” in CRUD wrong. The entire interview ended in complete absurdity.

The technical manager wants to keep an overview, but their project management and technical concepts are both outdated, and they particularly like using people they are familiar with.

The company has a large workload and is quite demanding, but it offers opportunities to hone your skills. You need to be clear about what the project should be doing amid the mess; if you are influenced by people who are not very effective, things can go off track.