Workplace reviews and discussion: 百商數位科技股份有限公司

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.