Software Engineer’s tool illustration

Why & How I Crossed Job from Aerospace Engineering to Software Engineering

Living my life doing what I love has been in my dream since I was a teenager. I love subjects which have something to do with riddles — which require empathy, imagination, analysis, systematic solution, evaluation, and iteration. However, crossing subjects from my background education to another subject was never been a part of my dream.

Why I crossed job?

During the end of college time, students would like to search for the next career they want to do. So did I. Applying for internships, part time jobs, full time jobs were my daily activities at night. I prioritized my applications as engineer/researcher to companies related to aerospace — airlines flight performance analysis, aircraft research & development, and drone research & development. Some rejected me, some I saw not interested to hire me.

In general, at that time they need new employee with slightly different attributes. The airlines said that they were not hiring employee who hold master degree. The aircraft company did not have empty position, and they were not doing any hiring activity at the moment. The drone company said that they need a highly-interested-in-electronics employee.

Being rejected to aerospace based companies, I rejected to discourage. I applied to companies with different industry subject. I sent an application for Simulator Developer position in a company which develop and sell simulators software and hardware to overseas clients. Thankfully, they called me for an interview. Me and the manager talks some things. I told him about my background, then he told me about the company and jobs there. He thought the most suitable job for me is Software Engineer. Then I showed him my portfolio in developing software (that was a book with MATLAB codes and screenshots of the running results).

In the end, still, I was rejected by the company. They tell me, “We have a ready-to-work position in software engineering, but we don’t use MATLAB here”. I think, they want me to know that they did not see me understand about software engineering, although I can write codes. But all the process I have passed with this company gave me new confidence that I could have a career in the software engineering-based industry.

Then, I made myself a Software Engineer.

How I made myself a Software Engineer?

When I chose to pursue career in the software engineering-based industry, I believed it stands on the general “engineering” idea as other subjects in engineering. On day-to-day basis, Me and the team would do problem solving with systematic sequences:

problem definition > root cause analysis > solutions proposal > exact solution selection > engineering process (design, develop, prototype, test, evaluate, and iterate or production) > user acceptance test and certification > mass production.

After that, I started to apply to software engineering positions available in ITB Career Center. Realizing that I need guidance to enter this industry, I searched for position where the company is willing to give training. Then I found one company who offer that exact advantage. I sent the application at one morning, and luckily the HR called me at the afternoon. What a fast response!

Then I followed the recruitment process from psychological test to technical test and from HR interview to user interview. All processes were done in one day. The tester told me that I have a good logical foundation (I use the “general engineering” idea above along the test), although I was weak in software engineering. He told me every software engineers will receive training every time there are new theories and practices that are required in a project. I felt grateful because the company offered me a contract for a Software Engineer position with some benefits.

In a nutshell, I accepted the offer, and joined them around 2 months later. I worked for them for 2 years. I thank them so much for every “mini lecture” sessions I got from the Director of Technology, the IT Development Manager, IT Development Supervisors, and colleagues. They helped me shape software engineering knowledge and skills. I learned software architectures, infrastructures, web servers, databases, user interfaces, programming, version controls, and project management from them. They also taught me the best practices for every subjects I have learned before.

Now I’ve left the company to work for another company. However, the services of the previous company were enormous. Moreover, they support me and wish me success. Therefore, I also wish success for the company and the people there.

--

--

--

Write for fun

Love podcasts or audiobooks? Learn on the go with our new app.

Recommended from Medium

Multi-cloud, Multi-region Kubernetes federation — Part 3

PHP 8 features I wish also existed in JavaScript

Multi-module project with SpringBoot

Linux basics for dummies

Asynchronous Communication

After a lot of hard work by our front-end developer and our graphic designer, our site https://www.v

Top 5 Developer Jokes Explained … Because We Don’t Get Them Either

Robert’s irreducible engineering ladder

Get the Medium app

A button that says 'Download on the App Store', and if clicked it will lead you to the iOS App store
A button that says 'Get it on, Google Play', and if clicked it will lead you to the Google Play store
fariz mamad

fariz mamad

Write for fun

More from Medium

Tech Job switch after 2–5 YOE

Transition to software engineering

Opportunity Cost In Your Engineering Career

How to Succeed as a New Software Engineer