Inexperienced in software development. At Bosch it was not a handicap.

VEHICLE MOTION
DIVISION

Junpei H.

Platform Software
Engineering Brake Systems
Engineering Software Department
Software Engineer
Joined Bosch in 2022

Gain experience in manufacturing, then take on new challenges at Bosch

I have been interested in automobiles since I was a junior high school student. I majored in mechanical engineering at university, so when I was looking for a job, I naturally wanted to work in the automotive industry. I had known about Bosch since I was a student, and I had applied for a job, but unfortunately I was not recruited as a new graduate, so I got a job at a manufacturer of resin parts related to automobiles.

At that company, I was involved in the design of parts around the fuel tank, and I felt that the work itself was very rewarding, but since the scale of development was shrinking due to the global trend of reducing carbon emissions, I casually registered with a recruitment agency. Bosch was suggested to me. I thought Bosch was out of my reach, but I was deeply moved that I could challenge myself as long as I had the experience of working hard.

However, a major concern was that I was offered the position of software engineer. My background is in mechanical design, so I did not have experience as a software engineer. However, I thought that if I had the chance to work at Bosch, I would like to take on the challenge. So I decided to go ahead and take on the challenge. I joined Bosch as a software engineer by emphasizing that I understood the business processes of the automotive industry and that I had the desire to learn.

Support system to learn skills even without experience in software

I am currently working as a software engineer developing software to control brakes. Although I started without experience, OJT was particularly useful for acquiring a basic knowledge of software. In addition to learning through practical work, I was able to systematically deepen my understanding while receiving detailed explanations of the process using examples of past operations and issues.

In addition, there are professionals in each field in the department, and the study sessions that are held from time to time have helped me acquire skills. It was very reassuring for me to have seniors nearby who were frank and readily available for advice. Bosch is an environment where I can understand why there are people like me who are active even though they have no software experience. The training environment is in place, so even if you have no experience in the industry, I think it is quite possible for you to succeed at Bosch depending on how hard and diligently you work.

When I was learning the new field of software, I tried to understand not only the surface, but also to understand the underlying principles behind the phenomenon. This can be said to be a basic stance in manufacturing, but I think I can make use of my experience at my previous job when learning software.

Understanding machines and software – Becoming the most sought after personnel in the industry

I only have been working as a software engineer for a short time, but I have already realized how interesting it is. Perhaps because I like to learn things I don't know, I discover new things almost every day, and I am able to approach my work with a fresh feeling. To be honest, even though I am still familiar with mechanical design, as automobiles move toward electrification and digitalization in the future, I believe that the knowledge of software that I am learning now will definitely be the sustenance, the core, of my future career.

Despite my lack of experience, I was able to challenge myself as a software engineer thanks to Bosch's large business scale and rich career diversity. In general, I think that it takes 3 to 4 years to learn a new technology, so I want to gain software experience in my current department for 3 to 4 years first and master the technology firmly. In the future, I would like to demonstrate my strengths as someone who understands both machines and software, and have various experiences and challenges within Bosch.

Daily Schedule

10:00-10:30

Start work

Check email, etc.

10:30-12:30

Meeting with customer

Discuss future development and existing issues

13:30-14:30

Team meeting

Share each member's progress, questions, and challenges

14:30-16:30

Software development

Perform specification analysis, software implementation, etc.

16:30-18:00

Simulation test

Check whether the implemented software works properly
(Using a dedicated simulation computer that simulates the signals inside an automobile)

18:00-19:00

Meeting with overseas sites

Share information with sites that are collaborating on development
Due to the time difference, the meeting is often in the evening

-20:00

Software development and simulation testing

Proceed with software development and simulation testing at own pace
Finish work