Content creation departmentMr. T

interview

Reason for joining the company

In my previous job, I was involved in server operation, maintenance, and website programming at a company in another prefecture.
After that, when I returned to Kagawa for a carrier change, I was told that there was a job offer, and I was initially concerned about my lack of mechanical knowledge, but I was told that they were looking for someone with IT knowledge. When I heard this, I realized that I could make use of my skills, so I decided to apply.

Work I am in charge of

Currently, I belong to the Digitalization Promotion Group of the Content Creation Department, and I am in charge of web distribution of parts catalogs and manuals, and the creation (programming) of RPA tools for building project management software.

What I like about my work

I believe that the department I belong to, the Computerization Promotion Group, is currently in the process of building results and achievements since its establishment.
Technology is advancing day by day, and there is a lot to learn, but at the same time, I find it to be a stimulating environment. What appeals to me in my actual work is being involved in the creation of RPA tools and system construction. When I see my own programs running and can realize my thoughts through programming, it is rewarding.

Good things about joining the company

Previously, I was involved in creating parts catalogs. I had little experience and was unsure about many things, but with the guidance and support of my superiors and senior colleagues, I managed to get on with my work. Our company highly values teamwork.
Additionally, there is a corporate culture that encourages employees to challenge themselves, explore their strengths, and learn new things, such as languages and programming, with ample support.

SCHEDULEDaily schedule

  1. 8:25

    Business starts

  2. 8:40

    Email/schedule check

  3. 9:00

    Web distribution of parts catalogs and manuals

  4. 10:00

    Regular project meeting

  5. 11:00

    Programming

  6. 12:00

    break

  7. 12:45

    Programming

  8. 15:00

    break

  9. 15:10

    Regular group meeting

  10. 16:00

    Program operation test

  11. 16:30

    Meeting about operation test results

  12. 17:10

    Closing hour (overtime depending on work progress)